Related
RSD completes but I still have CM10 no matter what I do.
I am having problems with my phone so I was gonna go back to stock but I realized RSD completes but the phone still boots into CM10 and factory reset/wipe does nothing in recovery.
What can I try?
Flash another rom?
sent from my thumbs
Firstly there is a dedicated CM10 Q&A thread so you could have avoided a new thread & be getting more responses. Now you can post in there with more details of your phone original stock firmware to the steps you worked up to CM10 & finally what fxz are you flashing to go back to stock so that some one may be able to help you.
sounreal said:
RSD completes but I still have CM10 no matter what I do.
I am having problems with my phone so I was gonna go back to stock but I realized RSD completes but the phone still boots into CM10 and factory reset/wipe does nothing in recovery.
What can I try?
Click to expand...
Click to collapse
Open the XML file using a text editor and check if there is a line containing system.
As a solution, you may open a command prompt in that folder using shift+right click. Put your phone in fastboot mode. Type and hit enter.
Code:
fastboot flash system system.img
Sent from my ME865 using Tapatalk 2
RAD7 said:
Firstly there is a dedicated CM10 Q&A thread so you could have avoided a new thread & be getting more responses.
Click to expand...
Click to collapse
Excuse you but I know you are pretty helpful around here I'm removing cm 10 and going back to stock. I know what I'm doing yet its not working something is physically wrong with the phone I guess. Cm10 worked perfectly fine for about 6 months on the phone. im using whatever att fxz ICS file that is posted. At one point in time I had 3 atrix 2s all on cm10 and I removed them all by rsd to ICS. I have tried every version I could fine of rsd and att fxz file.
Ravikirancg said:
Open the XML file using a text editor and check if there is a line containing system.
As a solution, you may open a command prompt in that folder using shift+right click. Put your phone in fastboot mode. Type and hit enter.
Code:
fastboot flash system system.img
Sent from my ME865 using Tapatalk 2
Click to expand...
Click to collapse
I'm super late... but I flashed everything. Including boot.img preinstall.img radio.img recovery.img fromInlineFlashing_Edison_67.21.125_CFC_P3_APBP and they all say something like
C:\Users\TheOwner\Downloads\InlineFlashing_Edison_67.21.125_CFC_P3_APBP.xml>fast
boot flash system system.img
target reported max download size of 1056964608 bytes
sending 'system' (491264 KB)...
OKAY [ 23.743s]
writing 'system'...
OKAY [ 14.976s]
finished. total time: 38.719s
I never get a error message. I reboot and CM10 is still on the phone. I how I delete the partitions and then reformat them?
C:\Users\TheOwner\Downloads\InlineFlashing_Edison_67.21.125_CFC_P3_APBP.xml>fast
boot format system
formatting 'system' partition...
FAILED (remote: protocol error)
FAILED (remote: protocol error)
finished. total time: -0.000s
C:\Users\TheOwner\Downloads\InlineFlashing_Edison_67.21.125_CFC_P3_APBP.xml>fast
boot erase system
erasing 'system'...
(bootloader) Command restricted
FAILED (remote: )
finished. total time: 0.016s
sounreal said:
I'm super late... but I flashed everything. Including boot.img preinstall.img radio.img recovery.img fromInlineFlashing_Edison_67.21.125_CFC_P3_APBP and they all say something like
C:\Users\TheOwner\Downloads\InlineFlashing_Edison_67.21.125_CFC_P3_APBP.xml>fast
boot flash system system.img
target reported max download size of 1056964608 bytes
sending 'system' (491264 KB)...
OKAY [ 23.743s]
writing 'system'...
OKAY [ 14.976s]
finished. total time: 38.719s
I never get a error message. I reboot and CM10 is still on the phone. I how I delete the partitions and then reformat them?
C:\Users\TheOwner\Downloads\InlineFlashing_Edison_67.21.125_CFC_P3_APBP.xml>fast
boot format system
formatting 'system' partition...
FAILED (remote: protocol error)
FAILED (remote: protocol error)
finished. total time: -0.000s
C:\Users\TheOwner\Downloads\InlineFlashing_Edison_67.21.125_CFC_P3_APBP.xml>fast
boot erase system
erasing 'system'...
(bootloader) Command restricted
FAILED (remote: )
finished. total time: 0.016s
Click to expand...
Click to collapse
You are like a year late lol
alright,
could you tell me what was your stock version?
and the version name?
and what version of RSD are you using?
Uzayr said:
You are like a year late lol
alright,
could you tell me what was your stock version?
and the version name?
and what version of RSD are you using?
Click to expand...
Click to collapse
4.0.4... I don't remember... A year ago I tried every RSD I could find. After I could not get it to format using fastboot I tried to brick it with RSD using the wrong Asia firmware. They did not do anything.
sounreal said:
4.0.4... I don't remember... A year ago I tried every RSD I could find. After I could not get it to format using fastboot I tried to brick it with RSD using the wrong Asia firmware. They did not do anything.
Click to expand...
Click to collapse
i had similar problems using an older version of rsd/
so i suggest you try RSD Lite 6 and up and see if it works for you.
Alright, could you tell if you A2 is at&t or retail?
i'll try my best to salvage the right fxz for you.
I'm sure I have RSD 6 lite but just so we are on the same page... Can you give me a link to the correct RSD 6 LITE? Oh yeah and its a ATT Atrix 2
sounreal said:
I'm sure I have RSD 6 lite but just so we are on the same page... Can you give me a link to the correct RSD 6 LITE? Oh yeah and its a ATT Atrix 2
Click to expand...
Click to collapse
Link for RSD Lite 6.1.4
http://forum.xda-developers.com/showthread.php?t=2637338
And also for the fxz file..i suggest you try the third link in this page
http://sbf.droid-developers.org/phone.php?device=17
if you were already on 4.0.4 before you flashed cm
I had RSD 6.1.4 installed but I tried 6.1.6 and the same thing happened. Once RSD completed the phone rebooted to the stock android recovery. I Hit the volume keys to bring up the menu and hit reboot... Still have CM 10...
sounreal said:
I had RSD 6.1.4 installed but I tried 6.1.6 and the same thing happened. Once RSD completed the phone rebooted to the stock android recovery. I Hit the volume keys to bring up the menu and hit reboot... Still have CM 10...
Click to expand...
Click to collapse
wait a minute...you don't need to hit the volume keys in recovery.
after fxz the phone should reboot to recovery and complete the other half of the setup.
I read if it and did not touch it once it got to the stock recovery... After about 2 mins it rebooted and I still had CM 10.
Hi, I am fairly new here but I have been around (just leeching, LOL) since my SE X10 Mini.
You could try using RSDLite 5.3.1.
I used it just this morning when I got black screen after flashing things after AOSB.
Just make sure you have the latest Moto Drivers.
Good luck! :good:
Cheers,
Rae
Raeshabu said:
Hi, I am fairly new here but I have been around (just leeching, LOL) since my SE X10 Mini.
You could try using RSDLite 5.3.1.
I used it just this morning when I got black screen after flashing things after AOSB.
Just make sure you have the latest Moto Drivers.
Good luck! :good:
Cheers,
Rae
Click to expand...
Click to collapse
Nope that did not help I still have cm10.
Yesterday, I was going to flash CM11.
After I flash boot.img of cm11 with fastboot, it can't return to recovery again!!:crying:
It only can boot into fastboot, cannot boot in to system or recovery, also cannot charging!!:crying:
When I want to flash back to stock boot.img, it said:
C:\adt-bundle-windows-x86_64-20131030\sdk\tools>fastboot flash boot boot.img
sending 'boot' (10240 KB)... OKAY [ 1.189s]
writing 'boot'... INFOBattery Low!!
FAILED (remote failure)
finished. total time: 1.430s
C:\adt-bundle-windows-x86_64-20131030\sdk\tools>fastboot flash boot boot.img
sending 'boot' (10240 KB)... OKAY [ 1.187s]
writing 'boot'... INFOBattery Low!!
FAILED (remote failure)
finished. total time: 1.435s
C:\adt-bundle-windows-x86_64-20131030\sdk\tools>
Click to expand...
Click to collapse
When I flash RSD, it said:
Faild flashing process. 1/23 flash partition "gpt_main0.bin" -> USB error occurred while reading/writing.
Click to expand...
Click to collapse
What can I do?:crying: Sorry for my bad English.
[email protected] said:
Yesterday, I was going to flash CM11.
After I flash boot.img of cm11 with fastboot, it can't return to recovery again!!:crying:
It only can boot into fastboot, cannot boot in to system or recovery, also cannot charging!!:crying:
When I want to flash back to stock boot.img, it said:
When I flash RSD, it said:
What can I do?:crying: Sorry for my bad English.
Click to expand...
Click to collapse
Can you try RSD using a different cable/port/computer entirely?
That's an odd and unfortunate error to receive. You put the device in fastboot mode before running RSD?
arrrghhh said:
Can you try RSD using a different cable/port/computer entirely?
That's an odd and unfortunate error to receive. You put the device in fastboot mode before running RSD?
Click to expand...
Click to collapse
Not Yet
Yes
At first, I put my PQ in fastboot mode and running RSD 6.1.5...
(asanti_c_sprint-user-4.1.2-9.8.2Q-122_XT897_FFW-5-6-release-keys-cid9.xml)
(without <step operation="getvar" var="max-download-size" />s)
...than flash recovery-clockwork-6.0.1.3-asanti.img with fastboot,
after that, Flash cm-11-20131209-NIGHTLY-xt897.zip and failed (2-3 times)
Than I take the boot.img from it and flash it with fastboot, at last: #1
[email protected] said:
Not Yet
Yes
At first, I put my PQ in fastboot mode and running RSD 6.1.5...
(asanti_c_sprint-user-4.1.2-9.8.2Q-122_XT897_FFW-5-6-release-keys-cid9.xml)
(without <step operation="getvar" var="max-download-size" />s)
...than flash recovery-clockwork-6.0.1.3-asanti.img with fastboot,
after that, Flash cm-11-20131209-NIGHTLY-xt897.zip and failed (2-3 times)
Than I take the boot.img from it and flash it with fastboot, at last: #1
Click to expand...
Click to collapse
Ok, you should not have done the boot.img flash.. not sure why you did that.
Now, you should restore with RSD. It sounds like RSD has worked in the past, but is no longer? Have you tried multiple FXZ files? If you are downgrading, there are additional lines to remove from the .xml file.
arrrghhh said:
Ok, you should not have done the boot.img flash.. not sure why you did that.
Now, you should restore with RSD. It sounds like RSD has worked in the past, but is no longer? Have you tried multiple FXZ files? If you are downgrading, there are additional lines to remove from the .xml file.
Click to expand...
Click to collapse
I restore my phone like this and it said:
Failed flashing process. 1/23 flash partition "gpt_main0.bin" -> Phone returned FAIL.
Click to expand...
Click to collapse
PS: Not「Faild flashing process. 1/23 flash partition "gpt_main0.bin" -> USB error occurred while reading/writing.」like #1
[email protected] said:
I restore my phone like this and it said:
PS: Not「Faild flashing process. 1/23 flash partition "gpt_main0.bin" -> USB error occurred while reading/writing.」like #1
Click to expand...
Click to collapse
Could be even an error on your HDD.
Try to do a deep chkdsk of your hard drive
chkdsk /f /r c: (assuming your main partition is called C: )
and / or try a different FXZ (say the ICS one)
Hi,
I really need some help. I had a stock 5.0.2 Lollipop and an unlocked device when I decided to flash CM 12.1. I get into the bootloader and tried to flash the recovery image but it always get the error "Mismatch partition size" witch I ignored because of the posts and suggestion here. But when I selected recovery from the bootloader it didn't load. At first it just restarted normally. I've tried every single possible custom recovery but none worked. Now I've tried something different. fastboot boot recovery.img to try to flash the rom. But it just appear a battery with a question mark on it. The only thing I can flash is a stock rom 4.4.3 that doesn't have any service at all.
Thanks for your help :fingers-crossed:
I think you get that error because your recovery is outdated (use latest twrp from here), try to flash by using "fastboot flash recovery yourfilename.img"
try that and see if you still had any problems
sayash5 said:
I think you get that error because your recovery is outdated (use latest twrp from here), try to flash by using "fastboot flash recovery yourfilename.img"
try that and see if you still had any problems
Click to expand...
Click to collapse
Can you tell me the version to download it? The link is broken.
sayash5 said:
I think you get that error because your recovery is outdated (use latest twrp from here), try to flash by using "fastboot flash recovery yourfilename.img"
try that and see if you still had any problems
Click to expand...
Click to collapse
same error, still can't enter recovery, it is just like power-off. should i try to rebuild the recovery specially for xt1033 and not for xt1032?
lung1 said:
same error, still can't enter recovery, it is just like power-off. should i try to rebuild the recovery specially for xt1033 and not for xt1032?
Click to expand...
Click to collapse
sorry the latest twrp was here, try this and see if it works
sayash5 said:
sorry the latest twrp was here, try this and see if it works
Click to expand...
Click to collapse
same error, same behaviour
lung1 said:
same error, same behaviour
Click to expand...
Click to collapse
flash from bootloader not from the recovery, power + down
sayash5 said:
flash from bootloader not from the recovery, power + down
Click to expand...
Click to collapse
I flash from bootloader, I can't enter to recovery, that's my problem. If I can't get into recovery I can't flash any ROM.
lung1 said:
I flash from bootloader, I can't enter to recovery, that's my problem. If I can't get into recovery I can't flash any ROM.
Click to expand...
Click to collapse
weird, if you cant get into recovery that means there isnt any recovery in first place but when you flashed twrp from bootloader, it should be there or the twrp didnt really flashed..
sayash5 said:
weird, if you cant get into recovery that means there isnt any recovery in first place but when you flashed twrp from bootloader, it should be there or the twrp didnt really flashed..
Click to expand...
Click to collapse
Exactly, it is like the bootloader doesn't let me to flash it. If I try to flash a stock recovery it lets me to do that, but not any other.
lung1 said:
Exactly, it is like the bootloader doesn't let me to flash it. If I try to flash a stock recovery it lets me to do that, but not any other.
Click to expand...
Click to collapse
maybe the bootloader is locked? what is your bootloader current version?
sayash5 said:
maybe the bootloader is locked? what ia you r bootloader current version?
---------- Post added at 08:24 PM ---------- Previous post was at 08:22 PM ----------
maybe the bootloader is locked? what is your bootloader current version?
Click to expand...
Click to collapse
AP Fastboot Flash mode (S)
41.19 (sha-291b089, 2015-02-09 12:46:46)
CPU: MSM8226 CS
eMMC> 16GB Toshiba RV=06 PV=01TY=17
DRAM: 1024MB Samsung S4 SDRAM DIE=4GB
Battery OK
Device is UNLOCKED. Status Code: 3
lung1 said:
AP Fastboot Flash mode (S)
41.19 (sha-291b089, 2015-02-09 12:46:46)
CPU: MSM8226 CS
eMMC> 16GB Toshiba RV=06 PV=01TY=17
DRAM: 1024MB Samsung S4 SDRAM DIE=4GB
Battery OK
Device is UNLOCKED. Status Code: 3
Click to expand...
Click to collapse
hmm seems fine, what about the log when you try to flash twrp?
C:\Users\RazvanCristian\Desktop>fastboot flash recovery twrp-2.8.6.0-falcon.img
target reported max download size of 536870912 bytes
sending 'recovery' (10184 KB)...
OKAY [ 0.426s]
writing 'recovery'...
OKAY [ 0.554s]
finished. total time: 0.987s
and on the device is:
cmd: getvar: partition-type:recovery
cmd:getvar:max-download-size
cmd:download:009f2000
cmd:flash:recovery
Mismatched partition size (recovery)
lung1 said:
C:\Users\RazvanCristian\Desktop>fastboot flash recovery twrp-2.8.6.0-falcon.img
target reported max download size of 536870912 bytes
sending 'recovery' (10184 KB)...
OKAY [ 0.426s]
writing 'recovery'...
OKAY [ 0.554s]
finished. total time: 0.987s
and on the device is:
cmd: getvar: partition-type:recovery
cmd:getvar:max-download-size
cmd:download:009f2000
cmd:flash:recovery
Mismatched partition size (recovery)
Click to expand...
Click to collapse
Try flash using mfastboot.exe from this thread http://forum.xda-developers.com/showthread.php?p=47820707
Same result. I want to mention again that it is an xt1033 not xt1032.
lung1 said:
C:\Users\RazvanCristian\Desktop>fastboot flash recovery twrp-2.8.6.0-falcon.img
target reported max download size of 536870912 bytes
sending 'recovery' (10184 KB)...
OKAY [ 0.426s]
writing 'recovery'...
OKAY [ 0.554s]
finished. total time: 0.987s
and on the device is:
cmd: getvar: partition-type:recovery
cmd:getvar:max-download-size
cmd:download:009f2000
cmd:flash:recovery
Mismatched partition size (recovery)
Click to expand...
Click to collapse
I dont see any problem here, it is flashed successfully and the mismatched partition is nothing serious, what you do after this?
perhaps after trying to go recovery, you should wait a little waiting for the twrp to load, let phone may sleep for a while
sayash5 said:
I dont see any problem here, it is flashed successfully and the mismatched partition is nothing serious, what you do after this?
perhaps after trying to go recovery, you should wait a little waiting for the twrp to load, let phone may sleep for a while
Click to expand...
Click to collapse
I will load a video.
Hello,
I think my XT1541 (16GB/2GB Retail GB) with locked bootloader might be hard-bricked.
I was running the stock 5.11 firmware when I did the 6.0 update and since then my phone is stuck in a bootloop.
Motorola won't repair it because I had to replace the screen and the phone is out of warranty.
I can access the bootloader but if I select recovery mode the phone just keeps bootlooping and I can't get into recovery.
I followed the instructions here to flash a stock firmware using fastboot. All the steps complete successfully but after rebooting, the phone is still stuck in a bootloop and I can't get into recovery.
I wanted to install a custom recovery but I'm unable to unlock my bootloader because of this error:
Code:
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
Obviously I can't check that option as the phone won't boot.
So, is it hard bricked? Is there anything I can do to get my phone to work again?
Thanks a lot for your help!
How many system images do you need to flash? Sometimes there can be more than 6, sometimes there can be fewer.
sticktornado said:
How many system images do you need to flash? Sometimes there can be more than 6, sometimes there can be fewer.
Click to expand...
Click to collapse
I know, I flashed the correct number of system images that were in the zip file.
Thanks,
rent0n said:
Hello,
I think my XT1541 (16GB/2GB Retail GB) with locked bootloader might be hard-bricked.
I was running the stock 5.11 firmware when I did the 6.0 update and since then my phone is stuck in a bootloop.
Motorola won't repair it because I had to replace the screen and the phone is out of warranty.
I can access the bootloader but if I select recovery mode the phone just keeps bootlooping and I can't get into recovery.
I followed the instructions here to flash a stock firmware using fastboot. All the steps complete successfully but after rebooting, the phone is still stuck in a bootloop and I can't get into recovery.
I wanted to install a custom recovery but I'm unable to unlock my bootloader because of this error:
Code:
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
Obviously I can't check that option as the phone won't boot.
So, is it hard bricked? Is there anything I can do to get my phone to work again?
Thanks a lot for your help!
Click to expand...
Click to collapse
If u are bootlooping when trying to enter recovery , then prolly the recovery is the issue. I'd suggest flash the recovery.IMG again and then proceed with flashing the rest of the .IMG files.
prasi.ram10 said:
If u are bootlooping when trying to enter recovery , then prolly the recovery is the issue. I'd suggest flash the recovery.IMG again and then proceed with flashing the rest of the .IMG files.
Click to expand...
Click to collapse
So basically:
Code:
fastboot flash recovery recovery.img
fastboot reboot
and then check if I can access recovery? Or issue that command and then all the other fastboot commands in the guide?
prasi.ram10 said:
If u are bootlooping when trying to enter recovery , then prolly the recovery is the issue. I'd suggest flash the recovery.IMG again and then proceed with flashing the rest of the .IMG files.
Click to expand...
Click to collapse
So basically:
Code:
fastboot flash recovery recovery.img
fastboot reboot
and then check if I can access recovery? Or issue that command and then all the other fastboot commands in the guide?
rent0n said:
So basically:
Code:
fastboot flash recovery recovery.img
fastboot reboot
and then check if I can access recovery? Or issue that command and then all the other fastboot commands in the guide?
Click to expand...
Click to collapse
I tried that and it didn't work. When I try to go into recovery mode the phone keeps bootlooping.
One thing I noticed is that when I try to format cache or userdata I get this error:
Code:
$ fastboot format cache
formatting 'cache' partition...
Formatting is not supported for filesystem with type 'raw'.
FAILED ()
finished. total time: 0.013s
I think there might be something wrong with the file system in my partitions. How can I manually format my partitions?
Thanks,
man , if you really need recovery, type fastboot boot recovery.img . It will temporaily boot you into stock recovery. Wipe cache and data there
therealduff1 said:
man , if you really need recovery, type fastboot boot recovery.img . It will temporaily boot you into stock recovery. Wipe cache and data there
Click to expand...
Click to collapse
Thanks, but this is what I get when I try do do that:
Code:
$ fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.736s]
booting...
FAILED (remote failure)
finished. total time: 0.746s
There must be a way to restore this phone to a working state! I can't believe it's so messed up after an official update...
rent0n said:
Thanks, but this is what I get when I try do do that:
Code:
$ fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.736s]
booting...
FAILED (remote failure)
finished. total time: 0.746s
There must be a way to restore this phone to a working state! I can't believe it's so messed up after an official update...
Click to expand...
Click to collapse
What os were you running when the phone screwed up ?
therealduff1 said:
What os were you running when the phone screwed up ?
Click to expand...
Click to collapse
I was running 5.1.1 when I got the notification for the 6.0 update.
I've noticed that trying to flash 5.1.1 firmware with fastboot gives me errors (preflash validation failed) while the 6.0 work "fine" (i.e.: I get OKAY after every step but then the phone is always stuck in a bootloop).
Thanks!
DO NOT ATTEMPT TO DOWNGRADE BOOTLOADER.IMG OR GPT.IMG !!!!!!! DONT FLASH LOLLIPOP VERSION OF THOSE FILES ON A DEVICE RUNNING 6.0
plz tell me u didnt flash those files..
therealduff1 said:
DO NOT ATTEMPT TO DOWNGRADE BOOTLOADER.IMG OR GPT.IMG !!!!!!! DONT FLASH LOLLIPOP VERSION OF THOSE FILES ON A DEVICE RUNNING 6.0
plz tell me u didnt flash those files..
Click to expand...
Click to collapse
Well I wasn't sure what version I was running to be honest so I think I tried to flash the gpt.img from 5.1.1 at some point but it failed with the preflash validation failure. I've always only flashed the 6.0 firmware files.
rent0n said:
Well I wasn't sure what version I was running to be honest so I think I tried to flash the gpt.img from 5.1.1 at some point but it failed with the preflash validation failure. I've always only flashed the 6.0 firmware files.
Click to expand...
Click to collapse
Have you gave this a try?
heavy_metal_man said:
Have you gave this a try?
Click to expand...
Click to collapse
Yes, no luck unfortunately.
I think I might have flashed the 5.1.1 bootloader after all - is there any way to recover from there?
Thanks,
Bump!
Does anyone have any other suggestion please?
Thanks,
Last bump
I'm going to sell this on eBay as non-working then unless someone comes up with a clever solution?
Thanks for your help!
Try flashing once more starting with the gpt.bin (that should hopefully take care of raw partition error) and skipping the bootloader altogether. Also, may be worthwhile to try mfastboot.exe instead of fastboot.exe.
I have this same issue, but I haven't flash 5.1.1 Files, I Only tried with 6.0 Brazil Retail.
I also tried to flash gpt to get rid of the "raw" partition, everything goes ok but still displaying that error. Anyone can help?
I got the same problem with my Moto E 2015... If I find a solution I will reply it in this topic..
I executed fastboot -i 0x2A96 oem unlock before flashing. I also checked fastboot getvar unlocked so result is following.
>fastboot getvar unlocked
unlocked:
finished. total time: 0.002s*
And one more thing when I flashed cache , userdata , recovery , boot. It is all fine, there is no error. But this error occurs only when i tried to flash system. My Phone was stopped working due some decryption error and internal memory is showing as 0Mb in TWRP. I had followed my threads but no luck.
>fastboot -i 0x2A96 flash system system.img
target reported max download size of 268435456 bytes
erasing 'system'...
OKAY [ 0.018s]
sending sparse 'system' 1/4 (261218 KB)...
OKAY [ 8.737s]
writing 'system' 1/4...
**FAILED (remote: flash write failure)**
finished. total time: 9.167s
Might be Because Of Corrupted Data Partion.
atulsam said:
I executed fastboot -i 0x2A96 oem unlock before flashing. I also checked fastboot getvar unlocked so result is following.
>fastboot getvar unlocked
unlocked:
finished. total time: 0.002s*
And one more thing when I flashed cache , userdata , recovery , boot. It is all fine, there is no error. But this error occurs only when i tried to flash system. My Phone was stopped working due some decryption error and internal memory is showing as 0Mb in TWRP. I had followed my threads but no luck.
>fastboot -i 0x2A96 flash system system.img
target reported max download size of 268435456 bytes
erasing 'system'...
OKAY [ 0.018s]
sending sparse 'system' 1/4 (261218 KB)...
OKAY [ 8.737s]
writing 'system' 1/4...
**FAILED (remote: flash write failure)**
finished. total time: 9.167s
Click to expand...
Click to collapse
It Might Possible That Your Data Partition Has Been Corrupted. Download The Official Cynogen OS Zip. Extract it. In That Look For Data. And In same Folder, Press Shift&Right Click in empty Sapce And Open Command window Here. Connect Your Device In Fasboot Mode. Flash That Data Using command. And then Flash System.img by Normal Method. Hope It will Worked For Yu.
Please see the image attached.
Animdk said:
It Might Possible That Your Data Partition Has Been Corrupted. Download The Official Cynogen OS Zip. Extract it. In That Look For Data. And In same Folder, Press Shift&Right Click in empty Sapce And Open Command window Here. Connect Your Device In Fasboot Mode. Flash That Data Using command. And then Flash System.img by Normal Method. Hope It will Worked For Yu.
Click to expand...
Click to collapse
Please see the following image attached which is shared on drive.
Code:
https://drive.google.com/file/d/0B8Dudx72Yu9iamFLUzZOY1Y1TjQ/view?usp=sharing
atulsam said:
Please see the following image attached which is shared on drive.
Code:
https://drive.google.com/file/d/0B8Dudx72Yu9iamFLUzZOY1Y1TjQ/view?usp=sharing
Click to expand...
Click to collapse
Try Out My Method It Should Be Work.
And rather than Using Original USB Cabel, Use Good Original cabel. Sometimes Original USB Become Loose.
It may not be USB problem.
Animdk said:
Try Out My Method It Should Be Work.
And rather than Using Original USB Cabel, Use Good Original cabel. Sometimes Original USB Become Loose.
Click to expand...
Click to collapse
I am using amazon basics cable , this is not usb problem because data is flashing properly but system is not. And Internal memory showing as 0 Mb in TWRP, but SdCard is showing as it is.
I downloaded official tool kit and OS . I tried with two different img but result is same for both.
atulsam said:
I am using amazon basics cable , this is not usb problem because data is flashing properly but system is not. And Internal memory showing as 0 Mb in TWRP, but SdCard is showing as it is.
I downloaded official tool kit and OS . I tried with two different img but result is same for both.
Click to expand...
Click to collapse
Do Yu Tried For The Flasing Of Only Data Partition, It Might Fix Your Problem.....Otherwise, Sorry Bro....I don't Have Any Further Knowledge About This....
Animdk said:
Do Yu Tried For The Flasing Of Only Data Partition, It Might Fix Your Problem.....Otherwise, Sorry Bro....I don't Have Any Further Knowledge About This....
Click to expand...
Click to collapse
Yes I have tried that , data is flashing successfully. Since there is no system flashing so cant start my phone.
I am having the exact same problem
how did you resolve the issue
BOTDeveloper said:
I am having the exact same problem
how did you resolve the issue
Click to expand...
Click to collapse
Sorry, I did not solve yet.
How did it happened?? I'm scared if i overcome this. Cuz recently i unbricked my device from dead hardbrick
exact same issue
atulsam said:
Sorry, I did not solve yet.
Click to expand...
Click to collapse
exact same problem here please update here if you abe to fix it.
Same problem.............. Is there no one from this group to help us........... :'(
Same Probelm
Please someone help , if you have resolved the same . TIA
Guys ..ur problem solved ? Post reply
@ Heartstoler1991 - Not yet .. Please help someone ..
Same problem. Please share the solution if anyone solved it.
I found a pretty easy method but it doesn't let me post the link so send a mail to [email protected] and I give you the link!
Edit: it finally let me post it: https://forum.xda-developers.com/yu-yuphoria/help/bricked-t3174710
Good luck mates
Razor10707 said:
I found a pretty easy method but it doesn't let me post the link so send a mail to [email protected] and I give you the link!
Edit: it finally let me post it: https://forum.xda-developers.com/yu-yuphoria/help/bricked-t3174710
Good luck mates
Click to expand...
Click to collapse
Tried this method already.
Doesn't work, it gives the same exact error.
I have same problem
help me any body any solution