Related
Hello All,
I am looking for some assistance on how to restore my bricked Droid Bionic, I updated to .893 and was trying to roll back to .886 so I can do the 4ever root hack before updating again to .893 however while trying to use rsd lite my device went into a soft brick state.
I have searched this forum and other places and tried the following however nothing seems to work, it keeps failed at flashing boot:
http://briefmobile.com/droid-bionic-receives-fastboot-recovery-files
http://rootzwiki.com/topic/5484-r3l3as3droot-and-43v3r-root-for-the-bionic-v21/page__st__630
http://www.mydroidworld.com/forums/...-your-phone-back-upgrade-path.html#post106072
http://forum.xda-developers.com/showthread.php?t=1262540
RSD lite 5.5/6
bionic_minimal_fxz.tar\bionic_minimal_fxz\default_flash_targa.xml and full
Any hope or is my device bricked for good.
Thank you.
i am on the same boat ahah now that my batter is low status, I was able to do the USB hack to get it to charge in AP Fastboot mode..still screwed at bootloader
So does that mean we are in need of a new phone from verizon?
have no fear! read this
http://forum.xda-developers.com/showthread.php?t=1412339&page=2
It does seem like it. I think I screwed up pretty bad. I am stuck at AP loop..
Currently at AP Fastboot (Boot Failured)
Invalid CG (CG:Boot)
Tried to fastboot stock or even FXZ, it starts and failed and screwed me over to
AP Flash Failed Mode...
---------- Post added at 09:01 PM ---------- Previous post was at 09:00 PM ----------
idivorceyou said:
http://forum.xda-developers.com/showthread.php?t=1412339&page=2
Click to expand...
Click to collapse
Funny you wrote that, i was going through the exact same process in at the moment. Already McGyver the USB cable
Dude I went through all that. Try my recipe. Click my link, download the zip from my dropbox. Follow instructions. Should work!
I tried something like that but not in the same order so I will give that try and report back.
idivorceyou said:
Dude I went through all that. Try my recipe. Click my link, download the zip from my dropbox. Follow instructions. Should work!
Click to expand...
Click to collapse
No dice for me
failed at flashing Web Top Frfs.img
Load_file: could not allocate xxxx
Pass preinstall.img
Failed system.img
Writing system .... INFOPreflash Validation Failure
FAILED (remote: )
@idivorceyou DUDE YOU R THE MAN!!!!
If we ever cross paths in NYC and I know its you I will buy you a few beers, it WORKED. Now I am back to where I was before, now I need to try and get root on .893 which was not possible that's why I started this whole thing in the first place of trying to downgrade to .886 to apply the 4ever root.
smilepak said:
No dice for me
failed at flashing Web Top Frfs.img
Load_file: could not allocate xxxx
Pass preinstall.img
Failed system.img
Writing system .... INFOPreflash Validation Failure
FAILED (remote: )
Click to expand...
Click to collapse
I failed with that earlier in the night and I tried this
[mydroidworld.com/forums/droid-bionic-forum/10577-bionic-path-saver-1-click-method as well as the fastboot_fix file. Here is what the file does:
fastboot flash devtree device_tree.bin
fastboot reboot
Click to expand...
Click to collapse
infolookup said:
I failed with that earlier in the night and I tried this
[mydroidworld.com/forums/droid-bionic-forum/10577-bionic-path-saver-1-click-method as well as the fastboot_fix file. Here is what the file does:
fastboot flash devtree device_tree.bin
fastboot reboot
Click to expand...
Click to collapse
did that 20 times today too..it fixed that part and advance me one step further..and some else failed and bring me back to square one.
So far, the only thing that stick is the mini FXZ 901 at the bottom of this post
http://rootzwiki.com/topic/4603-fxz-fastboot-recovery/page__st__138
but now different error on boot failed. hahaha
crap
---------- Post added 28th December 2011 at 12:21 AM ---------- Previous post was 27th December 2011 at 11:55 PM ----------
Finally...this got me at least being able to boot into android for once
Extract the files below from there respective fxz file and try the commands listed. You must use the updated moto-fastboot.exe app. I just have it renamed to fastboot.exe.
files from 5.5.893 tar.gz file posted above (credit to realbbb):
fastboot flash boot boot.img
fastboot flash recovery recovery.img
files from stock 5.5.866 fxz file:
fastboot flash system system.img
fastboot flash preinstall preinstall.img
fastboot flash radio radio.img
fastboot flash webtop grfs.img (might not be necessary, but I did it)
Boot the phone into fastboot mode. I put all of the files in the same folder and flashed them one after the other. Then "fastboot reboot". I booted up fine and shortly thereafter had a notificaton of an available update. I then used R3L3AS3D to root and 4ever root and allowed the update. So far everything is working great and I'm on the OTA path again.
Click to expand...
Click to collapse
infolookup said:
@idivorceyou DUDE YOU R THE MAN!!!!
If we ever cross paths in NYC and I know its you I will buy you a few beers, it WORKED. Now I am back to where I was before, now I need to try and get root on .893 which was not possible that's why I started this whole thing in the first place of trying to downgrade to .886 to apply the 4ever root.
Click to expand...
Click to collapse
So pleased I could help (sorry this didn't work for everyone)
There are so many well intentioned posts with solutions but none really works for the total bricked bionic. So I saved my steps and uploaded my files and swore to help anyone else avoid - as much as possible - what I went through.
Would love to have root again but with 901 installed, golauncher and some manic app restoring, the phone works great.
For now I am on 893, and since development was stopped on the KIN3TX rom which I was using I am now about to take a nandroid backup, and flash with the new http://rootzwiki.com/forum/343-eclipse/ Eclipse rom.
after my restore, I downloaded and flashed the "official" 901 update "Blur_version.5.5.893.xt875.verizon.en.us".
don't know if released root will get me rooted. Too nervous to try anything else right now!
I just don't have the patience to spend another night in front of the computer cursing at my failed fastboot efforts. It works now. Supposedly, due to .901, it is better. bloaty, but better.
waiting for the dev gurus to create an easy way to root .901 and for the roms that are made with it.
For some reason, when I navigate I get errors and I'm typing the path where the file is stored, the desktop. What am I doing wrong?
Hello,
I need a bit of help if possible. I have a freind with a Bionic who just tried to reflash to stock. Now he only gets a message of:
AP Fastboot Flash Mode (S) (Boot Failure)
Invalid CG OTV (CG: system): Invalid SP data
Invalid CG HAB (CG: system, status: 0X0035)
Invalid CG OTV (CG: system)
If I try to boot into recovery I get the Moto logo and then back to this screen. I have tried reflashing with RSD Lite and everything seems to go well and when it reboots it says pass on RSD but I still get the same screen.
Any ideas?
Thank you,
a72mz said:
Hello,
I need a bit of help if possible. I have a freind with a Bionic who just tried to reflash to stock. Now he only gets a message of:
AP Fastboot Flash Mode (S) (Boot Failure)
Invalid CG OTV (CG: system): Invalid SP data
Invalid CG HAB (CG: system, status: 0X0035)
Invalid CG OTV (CG: system)
If I try to boot into recovery I get the Moto logo and then back to this screen. I have tried reflashing with RSD Lite and everything seems to go well and when it reboots it says pass on RSD but I still get the same screen.
Any ideas?
Thank you,
Click to expand...
Click to collapse
I've seen this before. I think I has something to do with the FXZ.
TRY HERE
give me second links down
After flashing during the reboot is comes up with the same screen the errors this time are:
Invalid CG OTV (CG: cdrom): Invalid SP Data
Invalid CG OTV (CG: system): Invalid SP Data
Invalid CG HAB (CG: system, status:0X0035)
Invalid CG OTV (CG: system)
and after manually rebooting the phone I get the same error i originally got.
Hmmm... Try Released Root
I tried to just restore it and came up with this error:
sending 'system' (491264KB)... OKAY
writing 'system' ... INFOPreflash validation failure
FAILED (remote: )
* Wiping data and cache
erasing 'userdata'... OKAY
erasing 'cache'... OKAY
then it reboots the phone and stays in AP Fastboot mode and the batch file says that it is back to stock. But that is not the case sadly...
a72mz said:
I tried to just restore it and came up with this error:
sending 'system' (491264KB)... OKAY
writing 'system' ... INFOPreflash validation failure
FAILED (remote: )
* Wiping data and cache
erasing 'userdata'... OKAY
erasing 'cache'... OKAY
then it reboots the phone and stays in AP Fastboot mode and the batch file says that it is back to stock. But that is not the case sadly...
Click to expand...
Click to collapse
Okay.. I was expecting that.
Now Try the FXZ
If Nothing
Run Released Root Again(I know... But it does DO Something.. Just not Sure yet What)
Then Go Here
When i run Released should I just do the restore option (#4) or should i do full root?
a72mz said:
When i run Released should I just do the restore option (#4) or should i do full root?
Click to expand...
Click to collapse
option 4 unless you want root
still the same thing. Is there any difference between the FXZ from the first try and the newest one you asked me to try?
a72mz said:
still the same thing. Is there any difference between the FXZ from the first try and the newest one you asked me to try?
Click to expand...
Click to collapse
The FXZ puts you on Stock .902
The flashme.zip puts you on Stock 5.5.886
Did you put the phone on Ap Fastboot? If no... Hold Volume Down.. Hold power button for 2 seconds.. let go..
Neither of these options work if your phone is in "boot failure"
Sent from Heaven but I have no clue why I'm on Earth
the phone was in flash mode for all of them
a72mz said:
the phone was in flash mode for all of them
Click to expand...
Click to collapse
Damn... dude I'm stumped.. Try Released Root again then the flashme.zip through RSD lite again. Then read me exactly what it says.
Sent from Heaven but I have no clue why I'm on Earth
Try these fastboot images through RSD lite
http://bandbinnovations.com/xda/bionic/bionic_minimal_fxz.tar.gz
Sent from Heaven but I have no clue why I'm on Earth.
can't flash the new files since there is no xml file should i move them into to .902 fxg and flash that?
a72mz said:
can't flash the new files since there is no xml file should i move them into to .902 fxg and flash that?
Click to expand...
Click to collapse
Sorry I posted the wrong link the first time. That one is correct. Extract it using Winrar
Sent from Heaven but I have no clue why I'm on Earth.
There is one way to fix any phone in any condition and get it to what is now the stock build, 5.9.902 and that is to use RSD Lite and the full 5.9.902 xml.zip.
Any of the other methods are now legacy, unnecessary and likely to fail for a variety of reasons, depending on what state your phone is in.
This will recover a Bionic on any firmware version with signed images of the current build and will not fail on any incremental versions of any of the signed partitions because it has the latest files with the latest signatures.
the minimal flash didnt work RSD lite said it fialed flashing boot.img phone returned fail; phone connected
and as for flashing the full .902 xml we have already tried that with no succsess I believe
a72mz said:
the minimal flash didnt work RSD lite said it fialed flashing boot.img phone returned fail; phone connected
and as for flashing the full .902 xml we have already tried that with no succsess I believe
Click to expand...
Click to collapse
Did you run Released root then the minimal flash?
i did not but i just reran it and still fails while trying to flash boot.img
a72mz said:
i did not but i just reran it and still fails while trying to flash boot.img
Click to expand...
Click to collapse
Okay I've got to figure this out.. Even If I have to brick my phone..
Tell me system were you on.. What Rom and or Theme before this happened
Hi guys! How are you? I hope you are fine, because I'm not lol.
Well, I'm new in this things, but I can install CM9 and 7 in my old devices thanks to your guides and tutorials, I really apreciated!.
But now, I'm stucking with my new phone, because I flashed wrong and I don't know what to do.
Ok let's start to explain my problem:
My phone is stucked in the fastboot screen and no advance. When I press "pwr vol+-" and select Recovery, nothing happens, only showme the "Motorola Dual Core Technology logo" and returns to fastboot.
...........................................................................
AP FastBoot Flash Mode (S)
10.98(*) (sha-2e68372, 2012-11-17 23:33:08)
Device is LOCKED. Status Code: 0
Battery OK
Connect USB
Data Cable
FastBoot Reason: Sticky bit factory_fastboot
...........................................................................
Ok, and when try to enter to recovery screen "pwr, vol+-" it's show me:
...........................................................................
Invalid Flash Mode (S)
10.98(*) (sha-2e68372, 2012-11-17 23:33:08)
eMMC Info: Size 8GB
Device is LOCKED. Status Code: 0
Battery OK
Connect USB
Data Cable
Partition (Boot) Security Version Downgraded
Fastboot Reason: Boot Failure
...........................................................................
Sometimes, indicate "Batery Low"...its very frustrating because I love my ohine but I can't make work and I don't know what is happend...
I see some tutorials, specialy from @sleevydude, to unlock the bootloader, but the "fastboot.exe" appears and dissapears, and I can't acces to program tools...
Another big problem, I'm from Argentina, and my language is spanish, after all, my english is good, and I can understand 90% if you say something...sorry if that is offtopic or something.
I've tryed with the metod from TheMythTeam, but doesn't work...keep stucked...
Ok guys, I hope you help me...miss my phone so much
Well you can't open the fastboot.exe because it's not a regular program. You just open a command Window in the folder it's located in.
Sent from my PACMAN MATRIX HD MAXX
It looks to me like your device has a locked bootloader.
What rom did you try to flash? What did you use to flash it?
deeje00 said:
Well you can't open the fastboot.exe because it's not a regular program. You just open a command Window in the folder it's located in.
Sent from my PACMAN MATRIX HD MAXX
Click to expand...
Click to collapse
Thanks mate, I'm testing the commands, but maybe I'll look at the tutorials carefully!
Soon I will have them new, wishing luck! :good:
audit13 said:
It looks to me like your device has a locked bootloader.
What rom did you try to flash? What did you use to flash it?
Click to expand...
Click to collapse
Hi! this ROM..
MB886_att-user-4.1.1-9.8.0Q-97_MB886_FFW-20-27-release-keys-ATT-US_BuildA.xml
I've used RSD Lite...but I think the problem is the bootloader locked...like you said!
Ok, I trying again...let's see what I can do.
Thanks for answer :good:
Ok...I found a new problem, and suspect this is the big problem of all problems!
My computer can't recognize the device, I successfully installed Motorola USB drivers (2.3.9 version) and when I trying to unlock the bootloader ussing Motopocalypse by Dan, doesn't happens...shows the follow message:
Waiting for device...
* daemon not running. starting it now in port 5037 *
* daemon started successfully *
And then, nothings is happens!...not show anything more....
Any suggestions?
Please hel me! :crying:
What OS was originally on the phone? Without an unlocked bootloader, I don't think you can flash an earlier rom version if the original rom version was higher.
I think those zip files needs to flashed via cwm, but I'm not 100% sure. I think that's how I got the Mexico Retail onto my Atrix HD.
You could try this: http://forum.xda-developers.com/showthread.php?t=2299113 or http://forum.xda-developers.com/showthread.php?t=2259661
Stock roms: http://forum.xda-developers.com/showthread.php?t=2209660
audit13 said:
What OS was originally on the phone? Without an unlocked bootloader, I don't think you can flash an earlier rom version if the original rom version was higher.
I think those zip files needs to flashed via cwm, but I'm not 100% sure. I think that's how I got the Mexico Retail onto my Atrix HD.
You could try this: http://forum.xda-developers.com/showthread.php?t=2299113 or http://forum.xda-developers.com/showthread.php?t=2259661
Stock roms: http://forum.xda-developers.com/showthread.php?t=2209660
Click to expand...
Click to collapse
I try manually, but I keep getting the same errors as the automatic method, and not to do, should I throw it away and buy a new motherboard or buy on eBay?
As the phone is AT & T USA, I have no warranty here in Argentina ...
I'm really frustrated .....
Here are the errors:
> fastboot flash system system.img.ext4
sending 'system' (262144 KB) ...
OKAY [19.854s]
writing 'system' ...
Preflash validation failed
FAILED (remote failure)
finished. Total time: 20.155s
> fastboot flash boot boot.img
sending 'boot' (10240 KB) ...
OKAY [0.865s]
writing 'boot' ...
Preflash validation failed
FAILED (remote failure)
finished. Total time: 1.137s
if anyone knows anything more, or want help clarify that this LOCKED BOOTLOADER
Wipe and Restore
Checkout my post on this thread. Just skip making a backup.
http://forum.xda-developers.com/showthread.php?t=2394238
PM me and click Thanks if I helped.
lucasantarella said:
Checkout my post on this thread. Just skip making a backup.
http://forum.xda-developers.com/showthread.php?t=2394238
PM me and click Thanks if I helped.
Click to expand...
Click to collapse
Thanks! I would try and let's see what happens!
**sorry for my bad english**
Reactorzero said:
I try manually, but I keep getting the same errors as the automatic method, and not to do, should I throw it away and buy a new motherboard or buy on eBay?
As the phone is AT & T USA, I have no warranty here in Argentina ...
I'm really frustrated .....
Here are the errors:
> fastboot flash system system.img.ext4
sending 'system' (262144 KB) ...
OKAY [19.854s]
writing 'system' ...
Preflash validation failed
FAILED (remote failure)
finished. Total time: 20.155s
> fastboot flash boot boot.img
sending 'boot' (10240 KB) ...
OKAY [0.865s]
writing 'boot' ...
Preflash validation failed
FAILED (remote failure)
finished. Total time: 1.137s
if anyone knows anything more, or want help clarify that this LOCKED BOOTLOADER
Click to expand...
Click to collapse
Try using fastboot binaries from skeevy 's thread..
Sent from my MB886 using xda app-developers app
Reactorzero said:
Hi guys! How are you? I hope you are fine, because I'm not lol.
Well, I'm new in this things, but I can install CM9 and 7 in my old devices thanks to your guides and tutorials, I really apreciated!.
But now, I'm stucking with my new phone, because I flashed wrong and I don't know what to do.
Ok let's start to explain my problem:
My phone is stucked in the fastboot screen and no advance. When I press "pwr vol+-" and select Recovery, nothing happens, only showme the "Motorola Dual Core Technology logo" and returns to fastboot.
...........................................................................
AP FastBoot Flash Mode (S)
10.98(*) (sha-2e68372, 2012-11-17 23:33:08)
Device is LOCKED. Status Code: 0
Battery OK
Connect USB
Data Cable
FastBoot Reason: Sticky bit factory_fastboot
...........................................................................
Ok, and when try to enter to recovery screen "pwr, vol+-" it's show me:
...........................................................................
Invalid Flash Mode (S)
10.98(*) (sha-2e68372, 2012-11-17 23:33:08)
eMMC Info: Size 8GB
Device is LOCKED. Status Code: 0
Battery OK
Connect USB
Data Cable
Partition (Boot) Security Version Downgraded
Fastboot Reason: Boot Failure
...........................................................................
Sometimes, indicate "Batery Low"...its very frustrating because I love my ohine but I can't make work and I don't know what is happend...
I see some tutorials, specialy from @sleevydude, to unlock the bootloader, but the "fastboot.exe" appears and dissapears, and I can't acces to program tools...
Another big problem, I'm from Argentina, and my language is spanish, after all, my english is good, and I can understand 90% if you say something...sorry if that is offtopic or something.
I've tryed with the metod from TheMythTeam, but doesn't work...keep stucked...
Ok guys, I hope you help me...miss my phone so much
Click to expand...
Click to collapse
I just realized that your system image says ".ext4" Fastboot does not normally format a partition as ext4 by default, maybe never at all. Make sure you have the correct Fastboot files.
Best of luck!
---------- Post added at 10:40 AM ---------- Previous post was at 10:31 AM ----------
Reactorzero said:
Thanks! I would try and let's see what happens!
**sorry for my bad english**
Click to expand...
Click to collapse
Just to try, flash this Fastboot package with RSD Lite 6.1. I have a feeling this will work.
Package: http://sbfdownload.droid-developers..._FFW-20-27-release-keys-ATT-US_BuildA.xml.zip
** I take no responsibility for any damage done to your phone. **
---------- Post added at 10:49 AM ---------- Previous post was at 10:40 AM ----------
The reason I believe my blast post will work is because your error while trying to flash says
.................................................. .........................
Invalid Flash Mode (S)
10.98(*) (sha-2e68372, 2012-11-17 23:33:08)
eMMC Info: Size 8GB
Device is LOCKED. Status Code: 0
Battery OK
Connect USB
Data Cable
Partition (Boot) Security Version Downgraded
Fastboot Reason: Boot Failure
.................................................. .........................
Click to expand...
Click to collapse
You are flashing a downgraded version of the boot image. If you came from 4.1.1 and are now trying to flash a 4.0.4 boot image, it will fail. Try to flash the package in my last post
lucasantarella said:
I just realized that your system image says ".ext4" Fastboot does not normally format a partition as ext4 by default, maybe never at all. Make sure you have the correct Fastboot files.
Best of luck!
---------- Post added at 10:40 AM ---------- Previous post was at 10:31 AM ----------
Just to try, flash this Fastboot package with RSD Lite 6.1. I have a feeling this will work.
Package: http://sbfdownload.droid-developers..._FFW-20-27-release-keys-ATT-US_BuildA.xml.zip
** I take no responsibility for any damage done to your phone. **
---------- Post added at 10:49 AM ---------- Previous post was at 10:40 AM ----------
The reason I believe my blast post will work is because your error while trying to flash says
You are flashing a downgraded version of the boot image. If you came from 4.1.1 and are now trying to flash a 4.0.4 boot image, it will fail. Try to flash the package in my last post
Click to expand...
Click to collapse
Hi mate, many thanks! I would try your way of flashing, I'm nothing to loose in this point...let's see what happens now and I tell you later, thanks again for your answer
Aingaran said:
Try using fastboot binaries from skeevy 's thread..
Sent from my MB886 using xda app-developers app
Click to expand...
Click to collapse
It doesn`t works in this case...flashing with snapdragon's fastboot :crying:
Did my RSD method work? Have you attempted it yet?
Sent from my Atrix HD
Hello
I have the same problem...
The bootloader is locked, the phone not rooted. I try to flash with RSD lite and Mexico Retail rom, but RSD give an error.
And the message is:
Partition (Boot) Security Version Downgraded
Fastboot Reason: Boot Failure
Thank your for help!
First try and get to stock. Then get Mexican retail.
Sent from my GT-P3110 using xda app-developers app
lucasantarella said:
First try and get to stock. Then get Mexican retail.
Sent from my GT-P3110 using xda app-developers app
Click to expand...
Click to collapse
When I try go back to stock, the phone (and RSD) get a message:
"downgraded security version
update gpt_main version failed
preflash validation failed for GPT"
RSD:
"Failed flashing process. 1/23 flash partition "gpt_main0.bin" -> Phone returned FAIL.
tomchy said:
When I try go back to stock, the phone (and RSD) get a message:
"downgraded security version
update gpt_main version failed
preflash validation failed for GPT"
RSD:
"Failed flashing process. 1/23 flash partition "gpt_main0.bin" -> Phone returned FAIL.
Click to expand...
Click to collapse
Make sure you are using the 4.1.1 fastboot package for RSD Lite. Also make sure you are using RSD Lite 6.1.
tomchy said:
When I try go back to stock, the phone (and RSD) get a message:
"downgraded security version
update gpt_main version failed
preflash validation failed for GPT"
RSD:
"Failed flashing process. 1/23 flash partition "gpt_main0.bin" -> Phone returned FAIL.
Click to expand...
Click to collapse
Unzip the rom zip and open .xml file and remove the line having flash partition gpt_main0.bin and save it, zip again using red, you will be able to flash now..
I tried to go back to Stock with factory images from Motorola Unlocked. When i try fastboot flash partition gpt.bin it shows Preflash Validation Failed and Failed to erase partition error. I cannot even go into recovery I am stuck anyone please help!.
I am getting Failed to erase partition error when i try to flash anything!.
vignesh245 said:
I tried to go back to Stock with factory images from Motorola Unlocked. When i try fastboot flash partition gpt.bin it shows Preflash Validation Failed and Failed to erase partition error. I cannot even go into recovery I am stuck anyone please help!.
I am getting Failed to erase partition error when i try to flash anything!.
Click to expand...
Click to collapse
If you are in bootloader mode you should be able to get into recovery. Just hit volume down to scroll to recovery and then volume up to select recovery.
---------- Post added at 06:41 PM ---------- Previous post was at 06:40 PM ----------
vignesh245 said:
I tried to go back to Stock with factory images from Motorola Unlocked.
Click to expand...
Click to collapse
Just remember - you cannot downgrade the bootloader or the partition table!!
JulesJam said:
If you are in bootloader mode you should be able to get into recovery. Just hit volume down to scroll to recovery and then volume up to select recovery.
---------- Post added at 06:41 PM ---------- Previous post was at 06:40 PM ----------
Just remember - you cannot downgrade the bootloader or the partition table!!
Click to expand...
Click to collapse
It's not going into recovery or rebooting the only thing I see is the fastboot menu!! What ever I do to flash it says failed to erase partition!! can you tell me why this error in fastboot!
vignesh245 said:
It's not going into recovery or rebooting the only thing I see is the fastboot menu!! What ever I do to flash it says failed to erase partition!! can you tell me why this error in fastboot!
Click to expand...
Click to collapse
What should I do now!! to get my phone back working!
vignesh245 said:
It's not going into recovery or rebooting the only thing I see is the fastboot menu!! What ever I do to flash it says failed to erase partition!! can you tell me why this error in fastboot!
Click to expand...
Click to collapse
well the last guy who got that error had to format his data partition but he had an unlocked bootloader with TWRP and could get into TWRP.
What happens when you connect your phone in bootloader mode to your PC, open a command shell and type:
fastboot devices
Does it return your device's serial number?
---------- Post added at 07:16 PM ---------- Previous post was at 07:15 PM ----------
vignesh245 said:
What should I do now!! to get my phone back working!
Click to expand...
Click to collapse
You should not be trying to flash a lower version of the partition table!!!!
You may have to do a factory reset.
---------- Post added at 07:18 PM ---------- Previous post was at 07:16 PM ----------
vignesh245 said:
I tried to go back to Stock with factory images from Motorola Unlocked. When i try fastboot flash partition gpt.bin it shows Preflash Validation Failed and Failed to erase partition error.
Click to expand...
Click to collapse
gpt.bin is the partition table. If you were trying to flash a lower version partition table than your bootloader version, you cannot do that!!!
What is your bootloader version?
JulesJam said:
well the last guy who got that error had to format his data partition but he had an unlocked bootloader with TWRP and could get into TWRP.
What happens when you connect your phone in bootloader mode to your PC, open a command shell and type:
fastboot devices
Does it return your device's serial number?
---------- Post added at 07:16 PM ---------- Previous post was at 07:15 PM ----------
You should not be trying to flash a lower version of the partition table!!!!
You may have to do a factory reset.
Click to expand...
Click to collapse
Thanks for the reply!!
Yes it returns a Serial number in fastboot! How flash the correct partition?.
vignesh245 said:
Thanks for the reply!!
Yes it returns a Serial number in fastboot! How flash the correct partition?.
Click to expand...
Click to collapse
Is Motorola Device Manager installed on your computer? If not, install it:
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
Then connect your phone in fastboot mode to your computer and run MDM and see if MDM can repair your phone.
Also - are you using version 2 of mfastboot to flash?
vignesh245 said:
Thanks for the reply!!
Yes it returns a Serial number in fastboot! How flash the correct partition?.
Click to expand...
Click to collapse
its 60.11
vignesh245 said:
its 60.11
Click to expand...
Click to collapse
I am using normal fastboot ! and I have MDM install will try to repair using MDM !!
vignesh245 said:
its 60.11
Click to expand...
Click to collapse
That is the lollipop 5.0 bootloader. What version of stock were you trying to flash? Kit Kat 4.4.4? If so, that is what happened here - you tried to downgrade the partition table. You cannot downgrade the partition table once you upgrade the bootloader.
---------- Post added at 07:41 PM ---------- Previous post was at 07:40 PM ----------
vignesh245 said:
I am using normal fastboot ! and I have MDM install will try to repair using MDM !!
Click to expand...
Click to collapse
OK let me know how it goes.
JulesJam said:
That is the lollipop 5.0 bootloader. What version of stock were you trying to flash? Kit Kat 4.4.4? If so, that is what happened here - you tried to downgrade the partition table. You cannot downgrade the partition table once you upgrade the bootloader.
---------- Post added at 07:41 PM ---------- Previous post was at 07:40 PM ----------
OK let me know how it goes.
Click to expand...
Click to collapse
Thanks for the clarity in reply!!
Where can i get the stock rom and Files for lolipop 5.0 ?? So I can get back to my stock recovery!
vignesh245 said:
Thanks for the clarity in reply!!
Where can i get the stock rom and Files for lolipop 5.0 ?? So I can get back to my stock recovery!
Click to expand...
Click to collapse
Did MDM not fix your phone? Are you on the XT1095?
http://www.graffixnyc.com/motox.php#
Also, I don't know what build you are, there looks to be more than 1 build for 5.0. Check out the support thread that the link above links too.
JulesJam said:
Did MDM not fix your phone? Are you on the XT1095?
http://www.graffixnyc.com/motox.php#
Also, I don't know what build you are, there looks to be more than 1 build for 5.0. Check out the support thread that the link above links too.
Click to expand...
Click to collapse
MDM did not fix my phone yes I am on Xt1095.
Thanks will try it and let you know
vignesh245 said:
MDM did not fix my phone yes I am on Xt1095.
Click to expand...
Click to collapse
OK, it is probably the custom recovery.
JulesJam said:
OK, it is probably the custom recovery.
Click to expand...
Click to collapse
I am getting Preflash validation failed and I found I have 22.21.11 version installed using MDM. and it says in pink color error in phone as failed to downgrade primary_apt.
Can you help me with this now??
vignesh245 said:
I am getting Preflash validation failed and I found I have 22.21.11 version installed using MDM. and it says in pink color error in phone as failed to downgrade primary_apt.
Can you help me with this now??
Click to expand...
Click to collapse
I would not mess around with the partition table. See if you can do
fastboot format data
fastboot format cache
To wipe your data and cache partitions.
JulesJam said:
I would not mess around with the partition table. See if you can do
fastboot format data
fastboot format cache
To wipe your data and cache partitions.
Click to expand...
Click to collapse
I cannot do that it says the error as in the attached screenshot!
When I select recovery using volume up it says ||boot up failed||
Can Motorola help my situation Mine is a pure edition?
||version downgraded for primary_gpt||
vignesh245 said:
Can Motorola help my situation Mine is a pure edition?|
Click to expand...
Click to collapse
Yes. It is still under warranty. I would get a warranty replacement. If you can't flash anything in BL mode and can't get into recovery and MDM can't repair your phone, idk what else to do.
Motorola should let everyone who unlocks their bootloader know you can't downgrade the bootloader or partition table. They should release the factory images of every version of Android for a device and let people know they have to stick to the version for their bootloader
Quite frankly, this is Motorola's fault for not doing that.
JulesJam said:
Yes. It is still under warranty. I would get a warranty replacement. If you can't flash anything in BL mode and can't get into recovery and MDM can't repair your phone, idk what else to do.
Motorola should let everyone who unlocks their bootloader know you can't downgrade the bootloader or partition table. They should release the factory images of every version of Android for a device and let people know they have to stick to the version for their bootloader
Quite frankly, this is Motorola's fault for not doing that.
Click to expand...
Click to collapse
Thanks a lot will contact motorola get my device replaced !.
vignesh245 said:
I cannot do that it says the error as in the attached screenshot!
When I select recovery using volume up it says ||boot up failed||
Can Motorola help my situation Mine is a pure edition?
||version downgraded for primary_gpt||
Click to expand...
Click to collapse
try using the "erase" command instead of format, I've found on my PC format works, but on Mac I need to use erase.
Long story short, woke up with my N6 stuck at the bootloader screen and cannot do anything at it. I can only see my serial number and if I try anything else, it reloads bootloader. I am trying to flash back to a stock 6.0.1 image, however I keep getting this error while trying to do so.
C:\Program Files (x86)\Android\android-sdk\platform-tools> fastboot flash bootloader bootloader-shamu-moto-apq8084-71.15.img
(bootloader) has-slot:bootloader: not found
target reported max download size of 536870912 bytes
sending 'bootloader' (10387 KB)...
OKAY [ 0.332s]
writing 'bootloader'...
(bootloader) flashing partition ...
(bootloader) This may take a few seconds if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Failed to write primary GPT.
(bootloader) Failed to flash partition
FAILED (remote failure)
finished. total time: 11.542s
I have tried Nexus Root Toolkit, tried flashing all and tried flashing each image one by one but I still get this "(bootloader) Failed to flash partition FAILED (remote failure)" on all attempts. Phone does show up if I try fastboot devices, and I have tried this on two different computers. Device is also unlocked as well, and I even tried flashing older versions of Lolipop but they all give me the same error. Drivers work fine, and I have everything up to date in terms of bootloader and Andriod SDK. I am starting to think that there is physical damage inside the phone, however I do not know how or why this occurred randomly. Any help would be awesome, as I am very new to flashing images onto my phone and frankly I am 99% sure that my warranty is out, and I really don't want to pay $175 cost .
You can try to use minimal adb and fastboot drivers, unpack for example latest npreview 5 factory Image into same folder and flash each .IMG step by step with cmd window, i always flash this way, if everything else fails.
http://forum.xda-developers.com/showthread.php?t=2317790
And here method 2:
http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
May this helps you
coremania said:
You can try to use minimal adb and fastboot drivers, unpack for example latest npreview 5 factory Image into same folder and flash each .IMG step by step with cmd window, i always flash this way, if everything else fails.
http://forum.xda-developers.com/showthread.php?t=2317790
And here method 2:
http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
May this helps you
Click to expand...
Click to collapse
I've already tried method 2 before so I tried method 1 with the program, and it gives me the same exact error as before. Thanks for the help though, it was worth a shot!
Are you able to enter twrp ? Try to reflash Bootloader through twrp
coremania said:
Are you able to enter twrp ? Try to reflash Bootloader through twrp
Click to expand...
Click to collapse
I did not have TWRP installed on my phone since I had it completely stock and unrooted, so I tried installing it in the hopes of that some chance it would work and I could access it. Still getting the same error as before (grumble grumble). It is starting to look like more of a physical problem to me, but thanks for the advice. Here is what I got...
Microsoft Windows [Version 10.0.10586]
(c) 2015 Microsoft Corporation. All rights reserved.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp.img
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (11585 KB)...
OKAY [ 0.468s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 6.380s
Bootloader is unlocked i guess, may your Bootloader is messed up, did you try to flash only one Factory Image ? Corrupt Download possible ?
What happens if you try unlock command
Try to flash the latest full ota with these steps.
https://developers.google.com/android/nexus/ota
Since you already in the bootloader, select recovery and fpllow the steps from there.
blanco2701 said:
Try to flash the latest full ota with these steps.
https://developers.google.com/android/nexus/ota
Since you already in the bootloader, select recovery and fpllow the steps from there.
Click to expand...
Click to collapse
This was going to be my suggestion!!
Sent from my Nexus 6 using XDA-Developers mobile app
coremania said:
Bootloader is unlocked i guess, may your Bootloader is messed up, did you try to flash only one Factory Image ? Corrupt Download possible ?
What happens if you try unlock command
Click to expand...
Click to collapse
Any image I even try to flash I get the error with, no matter what order or which one I pick. I redownloaded the image again and still nothing, so I don't think it's a corrupt download. What is the unlock command? Sorry for being a noob, never heard of it since all my knowledge is from reading tons of flashing guides on the internet lol.
blanco2701 said:
Try to flash the latest full ota with these steps.
https://developers.google.com/android/nexus/ota
Since you already in the bootloader, select recovery and fpllow the steps from there.
Click to expand...
Click to collapse
Alright, I downloaded the OTA file and got the process to about 47% when suddenly I keep running into the error of "E:Can't open /cache/recovery/log" then followed by more things it can't open. I tried the OTA twice and it gets stuck on that same exact spot. I tried the wipe data/factory reset option from the recovery mode and I get a similar error of "Can't mount", "Can't open", "failed to mount" the recovery log. It seems like there is a problem with the recovery log files (or the folder) on my phone, but I have no idea what that means. I will mess around with some more and try Googling the source of error, but thank you for the help.
fastboot oem unlock
With this command you can unlock your Bootloader, better read here
first http://forum.xda-developers.com/showpost.php?p=56938530&postcount=1 , if have 47% done, may you can use twrp now. Good luck
Did you try the erase function from bootloader that may or may not help??
Sent from my Nexus 6 using XDA-Developers mobile app
coremania said:
fastboot oem unlock
With this command you can unlock your Bootloader, better read here
first http://forum.xda-developers.com/showpost.php?p=56938530&postcount=1 , if have 47% done, may you can use twrp now. Good luck
Click to expand...
Click to collapse
Oh yes, my device has already been unlocked from the start so that wasn't a problem. I still get the same error when I try to flash anything, including TWRP which means I have to install the OTA. The problem is a get a separate error when I try to install the OTA, which the only solution being to flash my device (or at least that is what most people have been saying when I googled the can't open cache recovery error) so this is a giant goose chase which leads me back to the start :/. I will keep trying however, I refuse to give up after going this far!
holeindalip said:
Did you try the erase function from bootloader that may or may not help??
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
Should I try fastboot erase cache and then fastboot format cache? Would refresh the cache on there? I only just learned the erase command so I am not exactly sure what I should try.
Should be able to erase any partition if your unlocked
http://androidforums.com/threads/list-of-fastboot-command.714676/
Sent from my Nexus 6 using XDA-Developers mobile app
I don't know the commands to erase everything from the bootloader but I would try this:
Flash latest twrp and boot into recovery.
Assuming you don't care about anything that's on the phone, go to advance wipe and wipe EVERYTHING lol... reboot into bootloader and try to flash everything from scratch. If this doesn't work, I'll guess your phone have problems.
holeindalip said:
Should be able to erase any partition if your unlocked
http://androidforums.com/threads/list-of-fastboot-command.714676/
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
I get the same failure error while trying to format and erase, so I am guessing something is really wrong with my phone or the bootloader is messed up beyond repair. I guess it could be the cable I am using as well, that is one thing I did not take into factor so I will try with another cable if I find a spare. Flashing might be beyond my solution at this rate though... Thanks anyways for the help.
blanco2701 said:
I don't know the commands to erase everything from the bootloader but I would try this:
Flash latest twrp and boot into recovery.
Assuming you don't care about anything that's on the phone, go to advance wipe and wipe EVERYTHING lol... reboot into bootloader and try to flash everything from scratch. If this doesn't work, I'll guess your phone have problems.
Click to expand...
Click to collapse
I really should have had TWRP installed before I guess lol, but I still get the same failure error. My phone has more problems than a teenager going through puberty I swear, thanks for the help though.
Yes try another cable, if it stops at 47%, the Bootloader should be replaced. May try everything without simcard, don't ask me why, i read something similiar in a Moto forum
fastboot erase recovery doesn't help ?
---------- Post added at 19:58 ---------- Previous post was at 19:34 ----------
http://forum.xda-developers.com/nexus-6/general/to-save-bricked-nexus-device-t3334660 otherwise try this, but read completely first, adb sideload with a npreview ota rom may help you.
coremania said:
Yes try another cable, if it stops at 47%, the Bootloader should be replaced. May try everything without simcard, don't ask me why, i read something similiar in a Moto forum
fastboot erase recovery doesn't help ?
---------- Post added at 19:58 ---------- Previous post was at 19:34 ----------
http://forum.xda-developers.com/nexus-6/general/to-save-bricked-nexus-device-t3334660 otherwise try this, but read completely first, adb sideload with a npreview ota rom may help you.
Click to expand...
Click to collapse
I tried it with another wire and nothing changed, and then I tried taking out my sim card and trying it.... and it worked! It flashed everything normally and loaded up just fine. I don't know whether I should be furious or happy but thank you and everyone who helped. Who would have known just taking out the sim card could have saved me 2+ days of stressing and trail and error. Once again thanks, you really saved me lol.
You're welcome, nice your phone works again !
Don't forget to activate oem unlock and debugging in the Developer options, and flash twrp, so maybe more save for upcoming problems
skipsoft android toolkit maybe help you in future