Related
I need some help please. I seem to be in a pickle, though I’m not bricked. (At least, not yet.) So I rooted my phone last night, using [GUIDE][NOOB]Step-By-Step Instructions for New Stock Bionic Owners. Everything went great, and I got root. I followed the guide to get the .901 update, which went fine. Tried the ROM suggested, and liked it. Thought I would try Eclipse v2.1. I installed it, but I like Visual Voicemail, so I decided to use my Nandroid that I did right after root and revert back. Here is where problems started.
After the restore, it wouldn’t boot. Passed the Moto Dual Core logo and hung up. Allowed 10 minutes and after nothing, I flashed back to the backup I made after installing Eclipse. It booted fine. So I decided to go back to stock rom, debloat it how I like it and just run the debloated stock. Here is where problems started. I can’t find a flashable copy of the stock. Just a couple of guides on using RSD Lite. This is for Bricked Bionic’s, but I decided to try it, since one of the guides said it works to get back to OTA.
Downloaded the RSD Lite and the full system file to flash. I put my phone into the mode to flash (Power + Volume Down), unpacked the file with RSD Lite and tried to flash. Got an error.
Failed flashing process. Failed flashing process. 1/15 flash cdt.bin"cdt.bin"-> Phone returned FAIL.; phone connected.
Now, when I reboot my phone, it goes back to the Fasboot Flash Mode screen saing (Failed). I can boot into recover (Volume Up + Volume Down + Power) and do a Normal Boot, and it boots fine.
I tried a Factory Reset, and it just reset’s on Eclipse v2.1.
I want to simply get back to stock. Rooted or unrooted, I don’t care. I’ll reroot if I need to.
I also tried to download the STOCK Deodexed files. The links are dead. Figured if I went back to one of those stock images, I could unroot and see if everything was ok.
Suggestions?
Hmm..I think your mistake was in safeboot when you tried to go back to original back up you were suppose to toggle safe system so that it would be disabled. From there you would've been able to restore your original system and boot up just fine. It was mentioned in the guide through some posts.
Sent from my DROID BIONIC using Tapatalk
ms0chez said:
Hmm..I think your mistake was in safeboot when you tried to go back to original back up you were suppose to toggle safe system so that it would be disabled. From there you would've been able to restore your original system and boot up just fine. It was mentioned in the guide through some posts.
Sent from my DROID BIONIC using Tapatalk
Click to expand...
Click to collapse
So I need to turn Safe Mode off in SafeStrap and flash? I had thought about that, but I was worried about totally bricking the phone. I'm pulling SafeBoot now, and will try the flash.
EDIT...
SafeMode is off, and rebooted. I'm back to .875 Stock Rooted. So far, so good.
I can either flash from here (haven't tried yet) or stay here. When I boot, I'm still booting into Fastbook with (Flash Failure). Any way to get that off, other than flashing back to stock and locked through RSD Lite?
Your mistake was trying to restore from the un safe system. You can toggle safe system and you'll be ok. Or, reinstall a ROM to your safe system.
To clarify: don't flash a ROM with safe system disabled. toggle back to safe mode, and then pickup my directions from the format /system step. You can try another ROM no problem then.
I bet you can find the visual voicemail APK and add it whichever ROM. Copy paste into system/app directory.
Thanks. I'm used to flashing with the Thunderbolt and the XOOM. Not used to safestrap, just normal CWM.
Any idea how to stop the phone from booting into Fastboot? Having to do it the long way still. I'd be happy staying this way, if I can get that resolved.
Actually the problem was you tried to restore to a backup of a pre .901 system which has different radios which flashing doesn't like.
As for the flash failure, get the fxz files and put them in a folder with adb and fastboot. Then run this command in a prompt:
fastboot flash device_tree.bin
When you get a flash failure you just need to flash something to fix it; flashing device_tree.bin won't affect anything.
Its one solid file with a weird extension. Is there a way to unpack it? I am out right now and don't know the extension by heart.
Its a zip, just extract it
Sent from my DROID BIONIC using XDA App
Now, I'm scratching my head. (Again) I've worked with ADB with my Xoom, so I'm not a noob at that part. ADB doesn't see my phone. My computer does, and the phone know's it's plugged in. However when I try to flash the file, it can't find the device. I checked "adb devices" and it's not on the list.
So I decided to go ahead and flash completely back to stock with RSD Lite. Still get's the same error message. (I did check the MD5 SUM on the file. It's correct.) Safe Mode is off in Safestrap. Here is what the Fastboot screen looks like on my phone.
AP Fastboot Flash Mode (S)
0A.61
Battery OK
OK to Program
Transfer Mode:
USB Connected
Since I've not seen the Fastboot screen on this phone until this started, I don't know if the (S) has meaning. Like, it thinks the phone's still in SafeMode?
I noticed one of the options in safestrap is to disable safestrap. Thought about trying that, but.... Unsure.
I heres how the story starts: I renamed all of my backups to what they are instead of the dates. so when i went to restore back to stock .902 from eclipse 2.2 to apply the .904 update, i couldnt. so i was advised that i needed to FXZ back. well, i tried. this is what it tells me "failed flashing process Failed flashing process. flash devtree "device_tree.bin" -> Size data retured by phones does not match what was expected.; phone connected" well, after that i hit the start button again in RSDlite and it did this "flash mbm "allow-mbmloader-flashing-mbm,bin"" and it did that for close to two hours...then my computer just shut off...so i booted back up and tried again...nothing. still did the same mess. so i realized maybe my RSD is old, so i scoured the webz looking for the newest, and i finally found it. installed, rebooted, and tried again. same message. i've tried about two diffrent downloads, same mess. i would try more but ALL of them are not working. i had someone send me the one i have, and the other from eclipse rom.com...
when i turn on the phone it goes to the fastboot screen and says flashing failed. i figured a way around it by holding down the volume buttons and turning it on it will give me the option to boot normally. but every boot it takes me to the fastboot page..its so annoying..
Any help?
edit; RSD version is 5.6 and the moto drivers are 5.5 i think..
Sounds like you ended up with a corrupted FXZ package. Try this one:
http://dl.dropbox.com/u/6725402/VRZ_XT875_5.9.902.XT875.Verizon.en.US_CFC_01.xml.zip
TANKS MAN!
this did the trick!
now, to redo my backups
imma do a .902 stock, and a .904 stock
then flash back to .902 and flash eclipse. then back up eclipse
then wait for the new eclipse on .904 and when its out all ill have to do is flash .904, then new eclipse
I'm on stock .890 (rooted) and I noticed the official .906 update available on my phone today by going into system updates. It downloaded, and I had it install. The phone automatically rebooted to do the install and gets stuck at the AP Fastboot Flash Mode (s) (Boot Failure) Invalid CG Version.
If I restart the phone again, it boots into Android and I can get to my home screen, but after about 5 - 10 seconds it just reboots back into the Boot Failure screen above. I'm stuck in this loop.
The fact that it does boot back into the current .890 android, (for about 10 seconds) leads me to think this can be fixed easily? How can I stop it from trying to automatically reboot back into AP Fastboot?
Any suggestions on how to get out of this?
I have no idea how to fix this since I haven't played with my Droid yet. You could try booting into recovery and try wiping delvik cache and partition and if that doesn't work download a stock version of the rom or a custom one and flash it is what I would do. It seems like your filesystem got corrupted from the root
Sent from my XT860 using XDA
HEMItude said:
I'm on stock .890 (rooted) and I noticed the official .906 update available on my phone today by going into system updates. It downloaded, and I had it install. The phone automatically rebooted to do the install and gets stuck at the AP Fastboot Flash Mode (s) (Boot Failure) Invalid CG Version.
If I restart the phone again, it boots into Android and I can get to my home screen, but after about 5 - 10 seconds it just reboots back into the Boot Failure screen above. I'm stuck in this loop.
The fact that it does boot back into the current .890 android, (for about 10 seconds) leads me to think this can be fixed easily? How can I stop it from trying to automatically reboot back into AP Fastboot?
Any suggestions on how to get out of this?
Click to expand...
Click to collapse
I would use RSD lite to flash 5.6.890 by booting with M+Power and then AP Fastboot mode.
Atrixn00b said:
I have no idea how to fix this since I haven't played with my Droid yet. You could try booting into recovery and try wiping delvik cache and partition and if that doesn't work download a stock version of the rom or a custom one and flash it is what I would do. It seems like your filesystem got corrupted from the root
Sent from my XT860 using XDA
Click to expand...
Click to collapse
This won't work because he doesn't have root or boot/safe strap installed and you can't wipe partitions/dalvik through stock recovery.
ohhh makes sense. haha
I'm still confused about the difference between x+power and m+power
Would this be something Motofail one click could fix?
DoubleYouPee said:
I'm still confused about the difference between x+power and m+power
Click to expand...
Click to collapse
X+Power gets you to stock android recovery. M+Power gets you to the selection menu where you can boot into AP Fastboot mode to flash, or boot into BP Tools to access Bootstrap (Hash's in particular).
MerCiLeSS28 said:
Would this be something Motofail one click could fix?
Click to expand...
Click to collapse
Most likely not because he can't access the phone to connect via Charge Only nor is he able to install Boot/Safe Strap. Maybe root through ADB and push it that way? Maybe...
I was able to get into Clockwork. During that brief few seconds that it would boot back into Android, I was able to quickly use the Boot Into Recovery option. As using the hard key combinations wouldn't work, it just kept bringing me back to the AP boot failure.
Once in Clockwork, I was able to do a factory wipe and cache clears. After that, I could succesfully boot into the OS and gain access to the device without it continually trying to reboot. But it didn't help....as I tried to download and install the OTA to .906 it restarted the device to atempt the install and it brought me right back to the same boot failure loop.
My final resolution was to use psouza4's 890 update script to get back to a complete fresh stock image of .890. Once I did that, the official OTA to .906 installed perfectly. I re-rooted and was good to go.
There was probably a much simpler solution, but I didn't know it. Plus I felt better starting over from scratch anyway.
Not sure exactly what it was causing it...probably my own stupidity.
so I rooted my Atrix HD (running 4.1.1) and decided to flash a custom ROM, so after installing a recovery and downloading a ROM I wanted, I flashed it.
problem is, I forgot to unlock the bootloader
after I flashed the ROM, I rebooted the phone and it booted into AP Fastboot
I tried using RSD Tool to flash the 4.1.1 firmware I found at sbf.droid-developers but it fails and says "Failed flashing process. Failed flashing process. 1/23 flash partition "gpt_main0.bin" -> Phone returned FAIL; phone connected"
I already edited the xml file and removed the two lines containing max-download-size
also it says low battery on the Fastboot screen and I assume it's not charging at all when plugged in on the Fastboot screen so this may be a problem in the very near future or may already be a problem
am I totally screwed? how can I fix this?
buttwhole said:
so I rooted my Atrix HD (running 4.1.1) and decided to flash a custom ROM, so after installing a recovery and downloading a ROM I wanted, I flashed it.
problem is, I forgot to unlock the bootloader
after I flashed the ROM, I rebooted the phone and it booted into AP Fastboot
I tried using RSD Tool to flash the 4.1.1 firmware I found at sbf.droid-developers but it fails and says "Failed flashing process. Failed flashing process. 1/23 flash partition "gpt_main0.bin" -> Phone returned FAIL; phone connected"
I already edited the xml file and removed the two lines containing max-download-size
also it says low battery on the Fastboot screen and I assume it's not charging at all when plugged in on the Fastboot screen so this may be a problem in the very near future or may already be a problem
am I totally screwed? how can I fix this?
Click to expand...
Click to collapse
I had the exact same problem, I could not get it to work no matter what I did, I finally got it working by using MythTools http://forum.xda-developers.com/showthread.php?t=2262726 That ones recovery got it working for me, I hope you can get it fixed, but don't give up, it took me about 6-7 hours before I fixed it lol, I ended up flashing stock ICS and then it finally came back for me.
And no, it does not charge in fastboot, or at least it doesn't seem to, and battery seems to drain rapidly, I'd say let it charge on USB for a while while it's off and start trying again
Silentwidow said:
I had the exact same problem, I could not get it to work no matter what I did, I finally got it working by using MythTools http://forum.xda-developers.com/showthread.php?t=2262726 That ones recovery got it working for me, I hope you can get it fixed, but don't give up, it took me about 6-7 hours before I fixed it lol, I ended up flashing stock ICS and then it finally came back for me.
And no, it does not charge in fastboot, or at least it doesn't seem to, and battery seems to drain rapidly, I'd say let it charge on USB for a while while it's off and start trying again
Click to expand...
Click to collapse
tried this, doesn't work
still fails to boot (Fastboot Reason: Boot Failure)
whenever I plug it in it automatically turns on and goes to Fastboot so I can't charge it with the screen off
buttwhole said:
tried this, doesn't work
still fails to boot (Fastboot Reason: Boot Failure)
whenever I plug it in it automatically turns on and goes to Fastboot so I can't charge it with the screen off
Click to expand...
Click to collapse
a couple more details
I tried this with both 4.0.4 and 4.1.1
the tool extracts them, asks me if I'm ready to flash, I say yes, then it asks me if I'm in normal mode or fastboot mode to which I answer fastboot
the only difference between 4.0.4 and 4.1.1 is at this point on 4.0.4 it asks me if I'm flashing 4.0.4 ICS
after that it says "Starting flash process..." and reboots my phone into fastboot again (and it lists the fastboot reason as sticky bit instead of boot failure)
and stays on this for about a minute, then asks if I want to use stock or CWM recovery (stock), then it says flashing stock and it reboots my device...
...which reboots back into fastboot with reason listed as boot failure
also I tried following /showthread.php?t=2231249 to a T but the same thing that I described in the OP happened
Did you try to flash system using fast boot?
Sent from my MB886 using xda premium
ai6908 said:
Did you try to flash system using fast boot?
Sent from my MB886 using xda premium
Click to expand...
Click to collapse
no, I just tried with RSD and Myth Tools
edit- I tried flashing with fastboot and it failed because the battery is too low
I ordered a factory cable and will report back when that gets here
I got my fastboot cable today. flashed 4.1.1 with RSD, no problems encountered
feels good having a working phone again
now I can add this fastboot cable to my collection of stuff I had to buy when I ****ed up big (my Galaxy S download mode jig comes to mind)
edit- so frustrating
the AOKP ROM I want to use is laggy in general use
the CM10.1 and PACman ROMs I tried are a lot smoother but aren't as customizable
buttwhole said:
I got my fastboot cable today. flashed 4.1.1 with RSD, no problems encountered
feels good having a working phone again
now I can add this fastboot cable to my collection of stuff I had to buy when I ****ed up big (my Galaxy S download mode jig comes to mind)
edit- so frustrating
the AOKP ROM I want to use is laggy in general use
the CM10.1 and PACman ROMs I tried are a lot smoother but aren't as customizable
Click to expand...
Click to collapse
Yea the CM10.1 skrillex night isn't bad, but the camcorder doesn't work, I personally am going to Mexico Retail and just wiping out a bunch of system apps and replacing the 4.1 apps with 4.2.
Silentwidow said:
Yea the CM10.1 skrillex night isn't bad, but the camcorder doesn't work, I personally am going to Mexico Retail and just wiping out a bunch of system apps and replacing the 4.1 apps with 4.2.
Click to expand...
Click to collapse
gl
buttwhole said:
gl
Click to expand...
Click to collapse
Wasn't too bad, I have it running right now, ended up using ATT retail instead, just because of the "LTE" on the 4g symbol(I know!), but I pretty much wiped out all Motorola apps and deodexed it, runs smooth without issue, and it's fast, but I really want the Tablet UI!
Search for Tablet UI...see below thread as well...
http://forum.xda-developers.com/showthread.php?p=38670671
Have a NAND backup before you use this...
If you end up doing this, please report your results and any issues you run into. I have tried some tablet ui stuff(roms that offer it) and haven't found a huge value in doing it...
Though, a full fledged tablet UI would be cool to try out. I'll probably end up trying it at some point, but if you take a first stab, any tips/tricks with what you did would be helpful.
thanks!
Maam.
Hi everyone. I have a problem I can't seem to resolve. I tried updating to the OTA jellybean update a couple weeks ago, it seemed to go ok. I then tried to go back to an earlier version of eclipse rom I was using. Now when I power on the phone I get AP Fastboot Flash Mode (S) (Flash Failure). I can select normal boot and it will go into my ICS Rom that I have loaded in slot 1 after going thru my safestrap recovery program. So the phone is not unusable, just very annoying to use. My question is, how can I get the fastboot flash mode flash failure warning to not show up every time I reboot the phone? I've tried loading the Stock JB Rom from verizon, Blur_Version.6.7.246.xt875.verizon.en.us with RSD Lite, but when I try to extract the files with RSD, I get the error "Please check input file. Either XML format is wrong or image files associated with it are missing." I just want to be able to get a stock rom back on my phone, without any errors when I boot it, I don't care if I have root, safestrap, or anything else, I just want a properly working phone. Any suggestions how to get rid of the boot flash failure warning? Thanks!!!! Richard
Update.... Looks like I really screwed it up now. Tried to rsd lite a JB rom, got about 1/2 way, to copying system image, then hung up. Now when I reboot, it won't even go into recovery or normal mode... Stoopid operator malfunction..... Any suggestions on which rom I can try to install via RSD Lite to help get it back going? It will still go into AP fastboot mode.
He's dead, Jim. Nothing is working, no rom will load, they either fail or hang up. Now both of my batteries are dead, and it won't even try to do anything. Any suggestions?? Guess I'm in the market for another phone. Maybe some of the gurus on here have some advice. Thx.
He's alive, Jim!!!!!
rlg999 said:
He's dead, Jim. Nothing is working, no rom will load, they either fail or hang up. Now both of my batteries are dead, and it won't even try to do anything. Any suggestions?? Guess I'm in the market for another phone. Maybe some of the gurus on here have some advice. Thx.
Click to expand...
Click to collapse
Thanks to some other posts on here, http://forum.xda-developers.com/showthread.php?t=2236980 I tried installing the system and preinstall img files manually thru moto fastboot. They seemed to hang up after a few minutes, but I tried to install the files anyway. Afterwards, I was able to get into recovery mode and do a system wipe and reinstall the JB rom that I had on my SD card. Now a couple hours later, I got the pageplus 4g issue fixed again, and just finished rooting it with the tutorial on XDA http://forum.xda-developers.com/showthread.php?t=2256439.
You guys are awesome! Thanks for all your hard work.