[Q] Boot Failure - Motorola Droid Bionic

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

Related

[Resolved] SBF Help

I kept trying the sbf and after my 20th try, I was able to advance past stage 13/18. Not sure why I got through on that try, but I'm glad that it worked
So I tried to sbf my droid 3 (XT862) this evening and goofed. I ran RSDLite 5.5 and entered AP Flashboot. I flashed the file found in http://forum.xda-developers.com/showthread.php?t=1255198 according to the instructions posted by techdigital in post #149. Because the link to moto-fastboot was omitted and the additional instructions cited using AP Fastboot, I only used AP fastboot (which is my fault for not reading more closely). The flash failed in RSDLite and now my phone is stuck in AP Fastboot Flash Mode (S) (Flash Failure). Would anyone be willing to explain to me how to fix this?
Forgot to mention that I am running Windows 7 x64
Additionally, I am getting the message:
Invalid CG OTV (CG: system): Invalid SP Data
Invalid CG OTV (CG: system, status: 0x004E)
Invalid CG OTV (CG: system)
I couldn't help you myself, but I know a guy who did the same thing. Dasnooterking and the other guys in #krazyk on IRC can help you out
Sorry mate i rarely visit this forum due to the lack of my ability to post....
Please let me know if you have worked out the issue if not get back to me
---------- Post added at 05:27 AM ---------- Previous post was at 05:15 AM ----------
eskimo monkey said:
I kept trying the sbf and after my 20th try, I was able to advance past stage 13/18. Not sure why I got through on that try, but I'm glad that it worked
Click to expand...
Click to collapse
sorry didnt see this.... not the ideal way to fix something but glad you got through it CHEERS
eskimo monkey said:
my phone is stuck in AP Fastboot Flash Mode (S) (Flash Failure). Would anyone be willing to explain to me how to fix this?
Click to expand...
Click to collapse
Use moto-fastboot to manually flash the preinstall image to your /preinstall partition and reboot, should get you out of the "flash failure" lock. If that doesn't work you can use moto-fastboot to flash each file to it's corresponding partition on your device. The preinstall flash worked for me in your situation though.

Atrix HD bootloader locked/recovery doesn't working, bricked?

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..

[Q] Help? Softbrick, stuck in AP Fastboot: Security Version Downgraded / Boot Failure

Hey guys, I did something really stupid.
I acquired an Atrix HD through a third party, network/sim unlocked it to work on T-Mobile, and tried to flash 4.1.2 Mexican Retail (MB886_niimx-user-4.1.2-9.8.2Q-50_MB886_NII_TA-2-16-release-keys-NII-MX) through RSD Lite 6.1.5 after removing the getvar command and.. it failed half way. I forgot to unlock the bootloader before flashing.
Now I'm stuck and I've tried almost everything to fix it. I've searched Google and XDA, in the process I have downloaded Myth Tools, sirhoover_atrixhd_utility, motochopper, motopocalypse, and moto-fastboot, tried them all to the best of my knowledge and nothing is working. I've even edited the XML file to exclude the files it fails on.
Common errors I encounter:
Fastboot reason: Boot failure
Fastboot reason: Flash failure
Partition (boot) Security Version Downgraded
Preflash Validation Failed for boot
Partition (system) Security Version Downgraded
PIV black validation for system failed
Invalid PIV image: system
Worst part is, I can't unlock my bootloader because I need ADB to do so! Recovery will give me ADB but only to sideload (available on certain recoveries I've managed to flash). If you have any ideas or information that could assist me in getting my phone back to normal, whether that's unlocking the bootloader through fastboot or flashing a stock rom sucessfully, I would greatly appreciate it! :good:
You don't need a unlocked bootloader to flash firmware through rsd.. Try flashing the stock att back.
Sent from my PACMAN MATRIX HD MAXX
deeje00 said:
You don't need a unlocked bootloader to flash firmware through rsd.. Try flashing the stock att back.
Sent from my PACMAN MATRIX HD MAXX
Click to expand...
Click to collapse
Thanks for your reply
I've tried flashing several stock firmwares already, I get preflash validation failed errors every time on boot.img and system.img
Here's the firmwares I have downloaded:
MB886_niimx-user-4.1.2-9.8.2Q-50_MB886_NII_TA-2-16-release-keys-NII-MX
MB886_bell-user-4.1.2-9.8.2Q-8_MB886_FFW-11-4-release-keys-BellMobility-CA
MB886_att-user-4.1.1-9.8.0Q-97_MB886_FFW-20-27-release-keys-ATT-US_BuildA
7.7.1Q-144_MB886_MR1-22_SIGNED_CFC
7.7.1Q-115_MB886_FFW-14_SIGNED_CFC
I wish I knew exactly the version I had before I started flashing, but unfortunately I do not..
DaveTheRave said:
Thanks for your reply
I've tried flashing several stock firmwares already, I get preflash validation failed errors every time on boot.img and system.img
Here's the firmwares I have downloaded:
MB886_niimx-user-4.1.2-9.8.2Q-50_MB886_NII_TA-2-16-release-keys-NII-MX
MB886_att-user-4.1.1-9.8.0Q-97_MB886_FFW-20-27-release-keys-ATT-US_BuildA
7.7.1Q-144_MB886_MR1-22_SIGNED_CFC
7.7.1Q-115_MB886_FFW-14_SIGNED_CFC
I wish I knew exactly the version I had before I started flashing, but unfortunately I do not..
Click to expand...
Click to collapse
Once your phone's OS has been upgraded, I don't think you can flash to an older firmware unless you have an unlocked bootloader. I'm not sure but that maybe the reason you're getting validation errors.
Did you try re-downloading the firmware?
audit13 said:
Once your phone's OS has been upgraded, I don't think you can flash to an older firmware unless you have an unlocked bootloader. I'm not sure but that maybe the reason you're getting validation errors.
Did you try re-downloading the firmware?
Click to expand...
Click to collapse
Just tried re-downloading everything on a brand new Windows install on a different computer, still having problems.
No matter how hard I try, I cannot get boot.img or system.img to flash from any Stock firmware, whether it's AT&T, Mex, or Bell
Using snap-fastboot:
snap-fastboot flash boot boot.img
sending 'boot' (10240 KB)...
OKAY [ 0.788s]
writing 'boot'...
Preflash validation failed
FAILED (remote failure)
snap-fastboot flash system system.img
sending 'system' (30720 KB)...
OKAY [ 2.343s]
writing 'system'...
Preflash validation failed
FAILED (remote failure)
I'm going to try making a Motorola Factory cable in the meantime. Any other suggestions?
EDIT: Factory cable didn't help.. is there a way to generate a higher security version? No matter what, the bootloader always displays Partition (boot/system) Security Version Downgraded
I really don't want this to end up being a paperweight
Is this where you got the firmware: http://sbf.droid-developers.org/dinara/list.php ?
Did you reboot each time you loaded a different set of fastboot files? Did you remove the previous fastboot files before installing a new set of fastboot files? Are you able to try this on a different computer?
I just got a new Atrix HD replacement and its showing firmware of 9.8.0Q-97_MB886_FFW-20 . Its not the same as the firmware available here: http://sbf.droid-developers.org/ .... I get the same error even after modifying the XML file in the SBF. Wonder if the last update caused an issue. Running into some similar issue with the replacement. Its not wanting to bootloader unlock.
Did you mount the system before installing?
Sent from my SAMSUNG-SGH-I537 using xda app-developers app
Found a fix for the AP Fastboot loop
List of commands to type in. ( in order)
1. adb reboot bootloader
2.fastboot oem fb_mode_set
3.fastboot oem fb_mode_clear
3.fastboot erase userdata
4.fastboot erase cache
5.fastboot reboot
Source:http://www.droidrzr.com/index.php/topic/17320-sticky-bit-fastboot/
Sorry I've been MIA, been busy with work.
TabascoTX said:
Found a fix for the AP Fastboot loop
List of commands to type in. ( in order)
1. adb reboot bootloader
2.fastboot oem fb_mode_set
3.fastboot oem fb_mode_clear
3.fastboot erase userdata
4.fastboot erase cache
5.fastboot reboot
Source:http://www.droidrzr.com/index.php/topic/17320-sticky-bit-fastboot/
Click to expand...
Click to collapse
Thanks for the reply! I wished this worked for me. After completing the steps successfully, I get:
Partition (boot) Security Version Downgraded
Fastboot Reason: Boot Failure
Code:
adb reboot bootloader
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
fastboot oem fb_mode_set
...
OKAY [ 0.006s]
finished. total time: 0.006s
fastboot oem fb_mode_clear
...
OKAY [ 0.005s]
finished. total time: 0.005s
fastboot erase userdata
erasing 'userdata'...
OKAY [ 3.095s]
finished. total time: 3.095s
fastboot erase cache
erasing 'cache'...
OKAY [ 1.669s]
finished. total time: 1.669s
fastboot reboot
rebooting...
finished. total time: 0.005s
audit13 said:
Is this where you got the firmware: http://sbf.droid-developers.org/dinara/list.php ?
Did you reboot each time you loaded a different set of fastboot files? Did you remove the previous fastboot files before installing a new set of fastboot files? Are you able to try this on a different computer?
Click to expand...
Click to collapse
That's exactly where I got my firmwares from. And to answer your question, I have tried this on different computers but I wasn't doing much rebooting when changing fastboot files.
DaveTheRave said:
...I have tried this on different computers but I wasn't doing much rebooting when changing fastboot files.
Click to expand...
Click to collapse
Try logging off and back on to see what happens. For me, using fastboot/adb commands on an x86 Win7 machine works more consistently than using an x64 Win7 machine.
TabascoTX said:
Found a fix for the AP Fastboot loop
List of commands to type in. ( in order)
1. adb reboot bootloader
2.fastboot oem fb_mode_set
3.fastboot oem fb_mode_clear
3.fastboot erase userdata
4.fastboot erase cache
5.fastboot reboot
Source:http://www.droidrzr.com/index.php/topic/17320-sticky-bit-fastboot/
Click to expand...
Click to collapse
When I run fastboot oem fb_mode_set, it just says "< waiting for any device >"
Sorry for the late reply. make sure you have adb installed and the drivers for the Atrix. Also,if possible and not in a boot loop or stuck in fastboot, device debugging should be enabled.
Boot problem
Hello here I have a problem and I made everything from my knowledge but It's not fixed.
I have a Motorola Droid Maxx X8 verison XI1080, version 4.4.4, built number SU4.21,
If I install or do something and I switch off and I turn on my phone it disappears as if it is never done and if I try to reinitialize the phone I have a error Fastboot Reason: Boot Failure
If I get the fastboot and I take recovery its said Boot up failed.
I did everything I flashed with RSD and I update it with Motorola update but still nothing we see that the flashing and the update works but on reboot Its has no effect on the phone its stays as if you did nothing.
Please help me! I look forward to a solution, I thank you more.
have u solved the problem
Please explain how u have solved the problem ,my moto g4 plus in same problems

[Q] Questions regarding un-rooting.

Verizon Moto X (2013) 4.2.2 Build number: 13.11.1Q2.X-69-3
Hey guys, for the past week I have been trying to un-root my moto x and have been unable to with several different methods.
I first tried RSD Lite, but no matter what I try over and over RSD Lite is not detecting my phone and I havent come across a way to fix that
I then moved on and tried to un-root using Fastboot following this tutorial. For some reason when my when I try, gpt.bin fails.
I then moved on to the Moto X Toolkit. Since this is basically just an automated way of doing fastboot I wasnt to hopeful, and of course it too failed.
Here is what i get when the process fails
Code:
writing 'recovery' ...
Preflash validation failed
FAILED <remote failure>
writing 'system' ...
Preflash validation failed
FAILED <remote failure>
writing 'boot' ...
Preflash validation failed
FAILED <remote failure>
What can I do to fix this? Any help is greatly appreciated!!
paradoxfreq;56816079I then moved on and tried to un-root using Fastboot following [URL="https://www.youtube.com/watch?v=ZtRSrQrzIPI&list=UUVLBNAjddTt6AAPL5141Ybg" said:
this tutorial[/URL]. For some reason when my when I try, gpt.bin fails.
Click to expand...
Click to collapse
Start the phone in FastbootAP/Bootloader mode
Either post a picture of it, or tell me what the number on the second line is.
Also boot normally, Go App Drawer -> Settings -> About... and post the number that SYSTEM VERSION starts with.
KidJoe said:
Either post a picture of it, or tell me what the number on the second line is.
Also boot normally, Go App Drawer -> Settings -> About... and post the number that SYSTEM VERSION starts with.
Click to expand...
Click to collapse
System Version: 140.45.5.
In the command window.
Code:
C:\adb>fastboot devices
T062801FWT fastboot
C:\adb>fstboot flash partition gpt.bin
<bootloader> Variable not supported!
target reported max download size of 805306368 bytes
sending 'partition' <32 KB>...
OKAY [ 0.247s]
writing 'partition' ...
FAILED <remote failure>
finished. total time: 1.078s
On my phone.
Code:
getvar partition-type: partition
downloading 32768 bytes
done
[COLOR="Red"]downgraded security version
update gpt_main version failed
preflash validatoin failed for GPT[/COLOR]
Thank you for the Reply!
I asked you to boot into FastbootAP/Bootloader and tell me the number on the second line. (its the bootloader version and it IS EXTREMELY important in this case).
You didn't tell me that. Why?
KidJoe said:
I asked you to boot into FastbootAP/Bootloader and tell me the number on the second line. (its the bootloader version and it IS EXTREMELY important in this case).
You didn't tell me that. Why?
Click to expand...
Click to collapse
Oh okay, sorry I didnt realize that was what you meant.
So this is what youre looking for correct?
AP Fastboot Flash Mode (S)
30.B2 (sha-0086aae, 2013-10-17 15:07:32)
paradoxfreq said:
Oh okay, sorry I didnt realize that was what you meant.
So this is what youre looking for correct?
AP Fastboot Flash Mode (S)
30.B2 (sha-0086aae, 2013-10-17 15:07:32)
Click to expand...
Click to collapse
Ok, you have some conflicting info posted.
Post 1 you say you have 4.2.2 Build number: 13.11.1Q2.X-69-3. (I thought 13.11.1Q2.X-69-3 was 4.4)
But in Post 3 you say System Version: 140.45.5. (which is 4.4)
Now, the bootloader version being 30.b2 goes along with 4.4.
the GPT.BIN failing to flash usually indicates that you are trying to DOWNGRADE. There are warnings everywhere saying you shouldn't, The only time its safe to downgrade is if you have 4.4 on your phone and are following the SlapMyMoto process. But since you're trying to un-root, you shouldn't be following SlapMyMoto.
So what are you trying to flash exactly?
At this point, DO NOT ATTEMPT to flash anything but 4.4, 4.4.2 or 4.4.4 on your phone! You need to do a FULL flash, and I would suggest manually using mFastboot, with the extra commands (see option 5 at -> http://mark.cdmaforums.com/MotoX-ReturnToStock.html ). Because of the GPT.BIN downgrade failures at this point, I would suggest 4.4.2 or 4.4.4 and NEVER try to flash anything older.

Pretty sure I just bricked my wife's G5S Plus

First let me start by saying, I KNOW...
This all started when her signal started to jump around. She was unable to access 4g or anything. I had Pixel Perfect (or something like that) on it. I was going back to stock so it just 'worked.' Stupidly I grabbed the G5's firmware, no G5S. Strangely I was able to flash everything (ugh!). This has result in a lot of pain for me. I am now unable to flash the proper firmware, no matter how hard I try.
I can reflash bootloader, boot, recovery. But i am unable to flash system, oem or GPT (which I think is required here).
Flashing GPT gives me:
HTML:
target max-sparse-size: 256MB
sending 'partition' (45 KB)...
OKAY [ 0.034s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'gpt.default.xml'
FAILED (remote failure)
finished. total time: 0.122s
Flashing oem gives me a failed validation, but a "image is too large" on the screen. Booting into recovery works but I'm unable to do anything as there is no file system. The SD Card also isn't working.
If anyone has some ideas, I'd appreciate it. I'm thinking I could possibly put a external SD card in but since I'm unable to write gpt, I think I'm screwed.
Please...anyone got an idea?
natalic said:
First let me start by saying, I KNOW...
This all started when her signal started to jump around. She was unable to access 4g or anything. I had Pixel Perfect (or something like that) on it. I was going back to stock so it just 'worked.' Stupidly I grabbed the G5's firmware, no G5S. Strangely I was able to flash everything (ugh!). This has result in a lot of pain for me. I am now unable to flash the proper firmware, no matter how hard I try.
I can reflash bootloader, boot, recovery. But i am unable to flash system, oem or GPT (which I think is required here).
Flashing GPT gives me:
target max-sparse-size: 256MBsending 'partition' (45 KB)...OKAY [ 0.034s]writing 'partition'...(bootloader) Validating 'gpt.default.xml'(bootloader) Security version downgrade(bootloader) Image primary_gpt failed validation(bootloader) Preflash validation failed(bootloader) Cancelling 'gpt.default.xml'FAILED (remote failure)finished. total time: 0.122s
Flashing oem gives me a failed validation, but a "image is too large" on the screen. Booting into recovery works but I'm unable to do anything as there is no file system. The SD Card also isn't working.
If anyone has some ideas, I'd appreciate it. I'm thinking I could possibly put a external SD card in but since I'm unable to write gpt, I think I'm screwed.
Please...anyone got an idea?
Click to expand...
Click to collapse
Flash newest software version
61-5
Adi5 said:
Flash newest software version
61-5
Click to expand...
Click to collapse
Got a link? I'm using:
NPSS26.116-45-5_cid50
I'm panicing here
https://androidfilehost.com/?fid=673956719939831738
Adi5 said:
https://androidfilehost.com/?fid=673956719939831738
Click to expand...
Click to collapse
This will be new enough to supercede the one from the G5's firmware since that is 137 vs 116?
natalic said:
This will be new enough to supercede the one from the G5's firmware since that is 137 vs 116?
Click to expand...
Click to collapse
Flash this one from afh should be flashed without error
Adi5 said:
Flash this one from afh should be flashed without error
Click to expand...
Click to collapse
I REALLY hope so
adi5 said:
flash this one from afh should be flashed without error
Click to expand...
Click to collapse
you saved me man...i am so thankful! It worked!!!
Hey, I have exactly the same problem but no luck with flashing 61-5. I can access fastboot from a PC but unfortunately nothing showing on the screen.

Categories

Resources