INFOPreflash validation failure
If I keep getting this in MotoRooter does that mean I can't get out of Fastboot? I keep seeing that error when flashing the system, boot.
Man, what'd I do wrong?
from what I'v gathered it means your trying to flash the wrong img version, so if your trying 886 try 893 or the other way around
Eluvatar said:
from what I'v gathered it means your trying to flash the wrong img version, so if your trying 886 try 893 or the other way around
Click to expand...
Click to collapse
In dhacker's mac motorooter program the option I chose was 1. Root, Restore and Forever Root a Bionic.
It says, "This works with all Bionics (886 and 893 rev)."
Maybe something happened in the process of the /system wipe and restore?
I'm having this same issue, were you able to resolve it?
I'm having the same problem as well when using Released Root. I'm trying to restore back to 886 and forever root but the fast boot keeps failing...
I'm up and running now with dead batteries. try installing the radio.zip file.
I haven't been able to root and maintain it, so I keep going back down to .886.
I can't root .893 with forever root. I may try to manual root I seen in the thread list.
I got the cdt. bin error and had to fastboot it with adb commands.
I wish I was smart enough to JUST LEAVE IT ALONE.
half the links to files have been shutdown by the MAN and it's really p*ssing me off.
Related
Hi all,
My Bionic is having a bit of a tiff that I feel like I've searched for days for an answer. I was rooted and lost root at random w/o flashing or updating the system at all!
Firstly I'll post my system information:
System Version: 5.9.901.XT875.Verizon.en.US
Baseband Version: Unknown
Webtop Version: (Okay this one is tricky...) Its got 1 square symbol then ELF then 3 more squares ... a bunch of random spaces with a A and 2 4's......
Kernel Version: 2.6.35.7-g83f1a47
[email protected] #1
Mind you I have tried the one click methods and manual operation of those methods both to no success. It even says successful in AP Fastboot mode and in command prompt but everytime I restart my phone it is in EXACTLY the same state (also carries over if I uninstall an app and restart the phone).
Also when using the one click method it proceeds to push everything but only after saying Error: Device not found
Formating Internal Storage doesn't work either... for some reason it keeps restoring everything (to the .901 messed up state it's in) EVEN if i delete the WHOLE contents of the SD card over USB on my desktop... I'm REALLY at a loss... I also went through an entire FXZ flash with no errors and it still stayed in exactly the same condition with no changes...
ANY help with this would be MUCH appreciated
Thanks!
Have you tried this;
http://forum.xda-developers.com/showthread.php?t=1427945
Follow those instruction to the 'T' and it should work. (Credit to the OP)
I did this probably 10 times this past weekend and got the phone down to .886 then was able to apply 43v3r root and update to .901. I flashed a .901 compatible rom and it brought me back to .894. i will probably re-flash later.
One thing to remember, charge your battery to 100% before proceeding because the flashing process uses your battery even when plugged into USB.
Good luck and set aside a night to do this.
ErisDroid? said:
Have you tried this;
http://forum.xda-developers.com/showthread.php?t=1427945
Follow those instruction to the 'T' and it should work. (Credit to the OP)
I did this probably 10 times this past weekend and got the phone down to .886 then was able to apply 43v3r root and update to .901. I flashed a .901 compatible rom and it brought me back to .894. i will probably re-flash later.
One thing to remember, charge your battery to 100% before proceeding because the flashing process uses your battery even when plugged into USB.
Good luck and set aside a night to do this.
Click to expand...
Click to collapse
Thanks for the reply! I tried this before and when you posted I tried it again. Failed on recovery and booted into the EXACT same system (and EVERYTHING else for that matter) it had before... it's like I can't change a thing no matter how hard I try. I sent a PM to the OP of that link though, so hopefully he comes through !
No go.. I give up ... Best Advice don't freeze system apps, if you lose root you're screwed.... Verizon is going to warranty my Bionic and MOTO can suck it.
i did not see any instructions about this so i figured i would ask instead of turning my phone into a paperweight and yes i looked at the noob section and it states everything from 896 and 893 so i didn't find a solution to my question
bfitzpatrickd2d said:
i did not see any instructions about this so i figured i would ask instead of turning my phone into a paperweight and yes i looked at the noob section and it states everything from 896 and 893 so i didn't find a solution to my question
Click to expand...
Click to collapse
You need to use the pathsaver. This will put you back on 886, then root and install 43v3r root, then update to 893, and then potentially 901 from there. Read up on how to use the pathsaver.
Instructions and more here: http://forum.xda-developers.com/showthread.php?t=1433783
Can you explain to me how this pathsaver does how it works a bit lost at this point
Sent from my DROID BIONIC using XDA App
Pathsaver was for folks that updated to leaked builds that were never officially supported and put us off the OTA (over the air) update path.
Its basically a batch to push the old builds to your phone allowing you to root/permaroot and give you the files needed to run the 893 and 901 updates from stock recovery on your phone once you're back at 886, effectively putting you back on the "OTA update path", thus aptly named "pathsaver".
hth
ok that makes a bit more sense so its like updating a "official" signed ota backwards more or less that makes sense i am really new to locked bootloaders everything seems so damn complicated cause when i had my charge and my epic all i had to do is plug in usb get a .pit file flash odin and bam i was rooted with cwm recovery installed it was magic... so this is super complicated and really can't afford to brick my phone..
Hopefully someone knows this answer...
i've tried both BPS, forever root and 1-click. i've found no answer to this and if it's out there could someone please point me in the right direction?? I apologize beforehand therefore if said answer is out there. I used BPS went right to .893, right to .901. lost root. I tried the other ways (to save time I did if you need specifics i'll give them) to no avail. This is the message I get:
unable to chmod read-only file system. Screen shot attached. thanks
Gossett said:
i've tried both BPS, forever root and 1-click. i've found no answer to this and if it's out there could someone please point me in the right direction?? I apologize beforehand therefore if said answer is out there. I used BPS went right to .893, right to .901. lost root. I tried the other ways (to save time I did if you need specifics i'll give them) to no avail. This is the message I get:
unable to chmod read-only file system. Screen shot attached. thanks
Click to expand...
Click to collapse
I think you need to use the pathsaver, and then once you get to 893 apply root, and 43v3r root, then go to 901.
Yesterday my Droid Bionic received the stock 902 OTA update. Prior to the update it was running 893. I had rooted the phone via the manual Zerg method. However after this update I no longer have root. The manual Zerg method does not appear to be working after the update to 902. During step 2 after typing ./zerg it gives the error message "Cannot copy boomsh.: Permission denied". ADB is installed on my computer. Is the only way to obtain root after the 902 OTA update to flash back to stock then ForeverRoot?
Thank You,
DGSafewright
Droid Bionic
Stock ROM with 902 Update
same problem
You need to run the 4ever root after the zerg rush manual root. You'll have to go back down to forever root if you want it.
greeneink said:
You need to run the 4ever root after the zerg rush manual root. You'll have to go back down to forever root if you want it.
Click to expand...
Click to collapse
Is there a "best" method to do that from .902?
I don't think there's any other way other than going back to 893 and make sure you have forever root from p3 as i heard other keep root scripts/apps weren't reliable
Many people have this issue too when they manual update to 901 and no1 figure out how to root while on 901
Only way is to go back to 893 - root - forever root
Many people tend to misunderstand when they manual root 893 they'll also have forever root its 2 separate thing
Zanzaras said:
Is there a "best" method to do that from .902?
Click to expand...
Click to collapse
What I did was took 893 FZX file, unzip it, and then take the 902update file, unzip it, and copy the cdt.bin file from 902 to the 893 FZX. I then ran that with RSD 5.6, and that brought me back to 893. I then used rota893 from this thread http://rootzwiki.com/topic/13807-root-ota-55893-aka-rota893/
That gave me 4ever root, and then I used stock recovery to run 902update. Everything worked for me.
But be warned that RSD will wipe the internal sdcard. Follow this post to avoid wiping.
http://forum.xda-developers.com/showpost.php?p=22316177&postcount=93
My phone was bricked with a "Invalid CG" message it would not even boot up. This did not happen until the 902 update. I had to follow the guide here http://forum.xda-developers.com/showthread.php?t=1433783 and run the fix.bat to get it working again.
I lost root when flashing the 902update.zip Was running rooted stock .901 4ever rooted prior to flashing.
lawtalking said:
What I did was took 893 FZX file, unzip it, and then take the 902update file, unzip it, and copy the cdt.bin file from 902 to the 893 FZX. I then ran that with RSD 5.6, and that brought me back to 893. I then used rota893 from this thread http://rootzwiki.com/topic/13807-root-ota-55893-aka-rota893/
That gave me 4ever root, and then I used stock recovery to run 902update. Everything worked for me.
But be warned that RSD will wipe the internal sdcard. Follow this post to avoid wiping.
http://forum.xda-developers.com/showpost.php?p=22316177&postcount=93
Click to expand...
Click to collapse
I'm assuming the FXZ file you used was the one from Daywalker04? Just replace the CDT.bin file with the one from the version you are currently running.
IHC said:
I'm assuming the FXZ file you used was the one from Daywalker04? Just replace the CDT.bin file with the one from the version you are currently running.
Click to expand...
Click to collapse
Top file I'm this thread
http://forum.xda-developers.com/showthread.php?t=1417116
Did forever root on 893, then just updated to 902 and also lost root.
My question is, can I just flash my stock 893 backup?
Sent from my DROID BIONIC using Tapatalk
YeloSub7 said:
Did forever root on 893, then just updated to 902 and also lost root.
My question is, can I just flash my stock 893 backup?
Sent from my DROID BIONIC using Tapatalk
Click to expand...
Click to collapse
Not sure. I used RSD to flash back to 893, then ran rota893.
When using RSD you must take the cdt.bin file from the 902update file and put it in the FZX file for 5.893.
Maybe moving the ctd.bin file from the .902 update to my stock .893 android and flashing that?
Just don't have computer access right now and want to fiddle around...
EDIT: I think I answered my own question. I think the cdt.bin file only applies to updates and not a nandroid. But I would still appreciate some clarification. Thanks all so far.
Sent from my DROID BIONIC using Tapatalk
Had .893 on the Bionic and it was rooted with the command line method from:
http://www.mydroidworld.com/topic/9...-upgrade-path/page__view__findpost__p__103640
Now it has the .902 OTA update and lost root in the process.
I've tried the same command lines that worked with .893, but it doesn't work:
[email protected]_targa:/data/local$ ./zerg
./zerg
[**] Zerg rush - Android 2.2/2.3 local root
[**] (C) 2011 Revolutionary. All rights reserved.
[**] Parts of code from Gingerbreak, (C) 2010-2011 The Android Exploid Crew.
[+] Found a GingerBread ! 0x00016118
[*] Scooting ...
[*] Sending 149 zerglings ...
[*] Sending 189 zerglings ...
[-] Hellions with BLUE flames !
[1] + Stopped (signal) ./zerg
[email protected]_targa:/data/local$ mount -o rw,remount /dev/null /system
mount -o rw,remount /dev/null /system
mount: Operation not permitted
[1] Segmentation fault ./zerg
[email protected]_targa:/data/local$
I also tried the Tehsusenoh all-in-one zip file, but it doesn't work either.
No, you can not flash a back up because it is for a different system number and more importantly a different radio. The easiest way is to make sure your .902 file is on your sd card then use p3's bionic pathsaver file with bbb's fix extracted in it. Run bbbrunme and it will take you back and also forever root you. It will then leave you in stock recovery where you well first update 893 then your 902 file back to back without a reboot, you will ignore the 901 update file. Good luck
Sent from my DROID BIONIC using Tapatalk
Thanks for the reply... so here is my dilemma...
Ok so I was on .893 with 4ever root via tehRoot 1.1
I updated to .902 and lost root for some reason.
Trying to go back to .893 (even tried .886) via the .893 FXZ. I downloaded the latest drivers (the same drivers worked to root in .893 originally, so I know they are that works). Using RSD I have tried flashing a dozen times and it only gets to flashing 1/22 for a few minutes, and then FAILS saying...
"Failed flashing process. Failed flashing process. 1/22 flash mbm "allow-mbmloader-flashing-mbm.bin" -> USB error occured while reading/writing.; phone connected."
Please help!! My goal is to be at .902 with root.
Have you tried path saver?
Sent from my DROID BIONIC using XDA App
smokedkill said:
Have you tried path saver?
Sent from my DROID BIONIC using XDA App
Click to expand...
Click to collapse
yes... found the problem
I tried different USB ports with no luck. Tried it on my wifes laptop and BAM! It worked! I am now seeing the official OTA for .902 on the phone. Going to flash this instead of the leaked .902. Hopefully I keep root this time!
EDIT: IT worked this time! Now at .902 with root. Thanks for all who helped develop for the BIONIC!
B.E.McAllister said:
No, you can not flash a back up because it is for [...] a different radio.
Click to expand...
Click to collapse
Just for the record, you can restore different systems to different radio firmwares. I did it back when we were messing around with the 5.7.893 radio and I restored a Liberty ROM backup I made on 5.5.886. There was no method of downgrading the radio firmware at that time so I didn't bother. I had 5.5.886 system and whatever radio came with 5.7.893.
Don't quote me on those version numbers... that was back in September I think, so my memory is a bit hazy that far back.
New root exploit
Do a search for rooting droid 4... its called motofail... at least that's what Dan is calling it...
I was in the same boat as all of you... I had even forever rooted and still lost root.
So I tried this method and it worked like a charm... and quickly... much more quickly then zerg.
Hope this helps!
Well hello, start right out. My bionic is stuck in ap fastboot. I was running .905 stock, and I had rooted it previously. Decided to try eclipse 3.0 last night. Installed bootstrap recovery, I did research beforehand, did everything the multiple threads told me to. Installed bionic bootstrap. Rebooted into recovery, wiped numerous times after nanbackup. Rom flashed fine, but rebooted and it would not go past the Motorola symbol and dual core screen. Let it sit at that screen for about 20 minutes, pulled the battery. Tried rebooting into recovery and found it doesn't work like previous phones I rooted. Did research, and found out about the recovery issue, and how to try to restore phone to stock. Downloaded rsd and tried .905 came back passed, just goes into ap fastboot and says can't find files (doesn't t say exactly that, I'm at work, ill put up what exactly it says after work). Tried going back to .902 rsd gives error that doesn't have enough resources (8gb ram, i7 processor and 1tb hdd, I should have enough space). Tried going all the way back to .893 fails on cdt.bin, got theoryroms released something (not sure what it's called, it has a brick fixer, rooter, and takes it back to stock) fails on infopreflash validation. Not sure where I need to go to from here. I any help would be great. Thanks in advance
Sent from my Thunderbolt using xda premium
homicidalspoon said:
Well hello, start right out. My bionic is stuck in ap fastboot. I was running .905 stock, and I had rooted it previously. Decided to try eclipse 3.0 last night. Installed bootstrap recovery, I did research beforehand, did everything the multiple threads told me to. Installed bionic bootstrap. Rebooted into recovery, wiped numerous times after nanbackup. Rom flashed fine, but rebooted and it would not go past the Motorola symbol and dual core screen. Let it sit at that screen for about 20 minutes, pulled the battery. Tried rebooting into recovery and found it doesn't work like previous phones I rooted. Did research, and found out about the recovery issue, and how to try to restore phone to stock. Downloaded rsd and tried .905 came back passed, just goes into ap fastboot and says can't find files (doesn't t say exactly that, I'm at work, ill put up what exactly it says after work). Tried going back to .902 rsd gives error that doesn't have enough resources (8gb ram, i7 processor and 1tb hdd, I should have enough space). Tried going all the way back to .893 fails on cdt.bin, got theoryroms released something (not sure what it's called, it has a brick fixer, rooter, and takes it back to stock) fails on infopreflash validation. Not sure where I need to go to from here. I any help would be great. Thanks in advance
Sent from my Thunderbolt using xda premium
Click to expand...
Click to collapse
Did you get this fixed? PM me, if you need help.
Stuck in Fastfoot
eye__dea said:
Did you get this fixed? PM me, if you need help.
Click to expand...
Click to collapse
Will do, thank you.
Thanks to Eye_Dea my phones boots and is updated once again,
For anyone who happens to come across this post needing to know how to fix your bionic, this is what he told me to do:
Go to this link:
h t t p://www .droidforums .net/forum/motorola-droid-bionic/197374-5-5-5-893-fxz-901-902-compatible-902-update.html
Download the 893 FXZ, flash it using RSD. My bionic booted after that and I OTA'd to 905. If your's does not boot he told me to then flash 902 (download from the same place) using RSD, and it should boot after that.
Big shoutout to Eye_Dea he pointed me in the right direction and got my phone working again. Thank you again man.
Glad to see you're back up. For anyone else in this situation, just FXZ to .905 directly.
crobs808 said:
Glad to see you're back up. For anyone else in this situation, just FXZ to .905 directly.
Click to expand...
Click to collapse
Well, this will be true for most people...it did not work in his situation. The OP had tried the 902 fxz and the 905 fxz using 2 different RSDlite versions and the moto-fastboot method. All of which failed for him and he was about to give up.
Luckily, I had seen this before and I knew if he used the 893 fxz it would work. He was able to boot 893 and take the OTA's to 905.
eye__dea said:
Well, this will be true for most people...it did not work in his situation. The OP had tried the 902 fxz and the 905 fxz using 2 different RSDlite versions and the moto-fastboot method. All of which failed for him and he was about to give up.
Luckily, I had seen this before and I knew if he used the 893 fxz it would work. He was able to boot 893 and take the OTA's to 905.
Click to expand...
Click to collapse
There's two or three bad .905 FXZ files floating around out there. My bet is he got a bad one. Even the one on DoirdHive's rombot is a corrupted upload right now. THIS one is the correct one (680 MB) and you should only use RSD Lite 5.7
You can FXZ any Bionic to .905, in any state running ICS .232 or less.
crobs808 said:
There's two or three bad .905 FXZ files floating around out there. My bet is he got a bad one. Even the one on DoirdHive's rombot is a corrupted upload right now. THIS one is the correct one (680 MB) and you should only use RSD Lite 5.7
You can FXZ any Bionic to .905, in any state running ICS .232 or less.
Click to expand...
Click to collapse
Not sure what 905 fxz he tried since i didnt give it to him. However, using the 902 fxz should of fixed him in theory as well. I think it was the fact that he was getting cdt.bin errors because he was trying to use old methods and the 893 fxz fixed that.
I have seen issues with RSDlite 5.7 too and when people went back to 5.6 everything flashed appropriately.
OK, I must be lucky then. FXZ'd to 905 about 10 times now on 32-bit WinXP and 64-bit Win7 and no probs. I'll count my blessings
I always put the FXZ file in the root of the C drive then 'Run as admin' on RSDLite.
worked like a charm
homicidalspoon said:
Thanks to Eye_Dea my phones boots and is updated once again,
For anyone who happens to come across this post needing to know how to fix your bionic, this is what he told me to do:
Go to this link:
h t t p://www .droidforums .net/forum/motorola-droid-bionic/197374-5-5-5-893-fxz-901-902-compatible-902-update.html
Download the 893 FXZ, flash it using RSD. My bionic booted after that and I OTA'd to 905. If your's does not boot he told me to then flash 902 (download from the same place) using RSD, and it should boot after that.
Big shoutout to Eye_Dea he pointed me in the right direction and got my phone working again. Thank you again man.
Click to expand...
Click to collapse
this worked surprisingly well i wasn't sure anything was going to work. Thank you!
My phone is on 905 and was rooted using Pete's One Click and then I did the Forever root. I decided that I wanted to flash ICS 232 so I used Petes Root Tools to remove root and it appeared to work. I attempted to flash 232 but got an error saying "Signature verification failed" After more checking I though the forever root might be my problem. I had assumed that the unroot tool would remove this, but when I looked, the extra lines were still there. I attempted to root again so that I could remove the forever root lines, but now I cannot root. In step 3 I get the error "adb could not be granted root access." I then tried SamuriHL_House of Bionic script and that failed with the same "Signature verification failed."
What should be my next step?
Thanks in advance for any help.
dkelly701 said:
My phone is on 905 and was rooted using Pete's One Click and then I did the Forever root. I decided that I wanted to flash ICS 232 so I used Petes Root Tools to remove root and it appeared to work. I attempted to flash 232 but got an error saying "Signature verification failed" After more checking I though the forever root might be my problem. I had assumed that the unroot tool would remove this, but when I looked, the extra lines were still there. I attempted to root again so that I could remove the forever root lines, but now I cannot root. In step 3 I get the error "adb could not be granted root access." I then tried SamuriHL_House of Bionic script and that failed with the same "Signature verification failed."
What should be my next step?
Thanks in advance for any help.
Click to expand...
Click to collapse
Full fxz to 905 is your best bet at this point.
SonicJoe said:
Full fxz to 905 is your best bet at this point.
Click to expand...
Click to collapse
Would that be better then a factory reset?
Doing the fxz to .905 is better than factory reset because it requires the completely unmodified stock files. If I remember correctly the forever root method leaves something inside the system that doesn't go away even with a factory reset. The same goes for safestrap. An fxz to .905 fixes both of those issues.
0001001- 0000011- 0010011
I. C. S
elreydotcom said:
Doing the fxz to .905 is better than factory reset because it requires the completely unmodified stock files. If I remember correctly the forever root method leaves something inside the system that doesn't go away even with a factory reset. The same goes for safestrap. An fxz to .905 fixes both of those issues.
0001001- 0000011- 0010011
I. C. S
Click to expand...
Click to collapse
Thanks.