Yesterday I had a received a phone call from a friend and upon ending the call I could not hang up. The screen had locked on the call screen. I waited and tried to use the power button to turn the screen off and then on to see if that would clear it but to no avail, so I had to do a battery pull.
I restarted the phone and first thing I noticed was that it was now telling me that I had 5% of my battery remaining, where the phone had been around 80% before the battery pull. Then pretty much everything started force closing, and it rebooted on its own. Upon restart it came up with the dialog box stating that "UIDs on system are inconsistent" and that I should wipe data, and has a button stating "I am feeling lucky". Then it’s endless pop ups of force closes. I finally get it to a point where I can try a factory reset via "Privacy" in settings but nothing changes.
I go into recovery and wipe data and cache partitions and it says it does so successfully, but when you reboot it has not. The phone goes into my "normal" home screen and settings, nothing has been restored back to outta the box state, and it does not prompt you to go through setup.
Other than I used Petes One Click root about 4 months ago the phone is stock, with no new apps installed just before this issue.
If you try to remove any applications, it says they are removed successfully, but when you reboot the phone they are all back as if nothing had happened.
Plug the phone into any computer and it is recognized, but the phone does not seem to know it is plugged into a PC... no "charging" or "mount SD" info.
I tried to do a factory image restore via RSDLite 5.6.4 using
cdma_solana-user 2.3.4 5.5.1_84_D3G-55 110812
It gets to step 3/18 and then tells me:
"Failed Flashing Process: 3/18 flash mbmloader "mbmloader.bin" Phone returned Fail"
I've used RSDL for flashing my OG, D2 and Dx's before with no issues.
RSDL's Flash error log shows:
Line 1041
ERROR: Phone[0000]: Unable to retrieve initialization values from INI file.
File: D:\GitProjects2\hdt_windows_flash\flash\code\flashdll\PST_FP_FlasthThread.cpp
Device ID:0
03/13/12 00:48:51 New Log Started For Software Download.
03/13/12 00:54:21 00001db8 Phone.cpp 1750 0 ERROR GetTechnology failed: ERROR.
03/13/12 00:54:46 The FlashLog key is turned off.
03/13/12 00:54:52 Multi upgrade started for 1 phones
03/13/12 00:54:57 [Device ID: 0] 1/18 flash mbm "allow-mbmloader-flashing-mbm.bin"
03/13/12 00:54:58 [Device ID: 0] 2/18 reboot-bootloader
03/13/12 00:55:03 [Device ID: 0] 3/18 flash mbmloader "mbmloader.bin"
03/13/12 00:55:04 ERROR: 3/18 flash mbmloader "mbmloader.bin" -> Phone returned FAIL. - on device ID 0.
03/13/12 00:55:04 [Device ID: 0] 3/18 flash mbmloader "mbmloader.bin" -> Phone returned FAIL.
03/13/12 00:55:04 ERROR: Failed flashing process. - on device ID 0.
03/13/12 00:55:04 Multi upgrade finished.
03/13/12 00:55:04 00001db8 Phone.cpp 514 0 ERROR Generic failure when sending command.
03/13/12 00:55:04 00001db8 Phone.cpp 1655 0 ERROR GetPhoneID failed: ERROR.
03/13/12 00:55:04 00001db8 Phone.cpp 514 0 ERROR Generic failure when sending command.
03/13/12 00:55:04 00001db8 Phone.cpp 1655 0 ERROR GetPhoneID failed: ERROR.
I then try Petes "One Click" easy unbrick and the command lines go through fine, all stating OK, and then it reboots the phone as it should. However instead of rebooting to the screen with the software box and the android with the yellow install bar, it goes to the white triangle with the exclamation point and little android. It will not go any further from that.
You can reboot the phone and it boots to the home screen, no set up, no removed programs...it looks as it did a few days ago before the issues started. However you will still get the force closes in a matter of minutes, the UID errors, and all the other issues.
Going to phone info shows the following.
System - 5.6.890
Baseband - N03.18.29P
Build - 5.5.1_84_D3G-55
I even tried to flash CM recovery and it will not do it. If you flash CWR through ROM Manager it will say it downloads and flashes successfully but it does not.
It seems as if the system has become unformat/flash/wipeable.
Suggestions? Clues!?
So you're on .890?
I'd try this first:
http://forum.xda-developers.com/showthread.php?t=1339816
File mirror: http://dl.dropbox.com/u/61707107/Ve...izon+DROID+3+OTA+5.6.890+to+phone_psouza4.zip
DoubleYouPee said:
So you're on .890?
I'd try this first:
http://forum.xda-developers.com/showthread.php?t=1339816
File mirror: http://dl.dropbox.com/u/61707107/Ve...izon+DROID+3+OTA+5.6.890+to+phone_psouza4.zip
Click to expand...
Click to collapse
That has already been tried, as noted above.
Ianscape said:
That has already been tried, as noted above.
Click to expand...
Click to collapse
It says you used RSDlite
DoubleYouPee said:
It says you used RSDlite
Click to expand...
Click to collapse
And then after it says I did the Fast/Easy unbrick
Ianscape said:
...I tried to do a factory image restore via RSDLite 5.6.4 using
....
I then try Petes "One Click" easy unbrick...
Click to expand...
Click to collapse
Did you try removing the ones that give you error from the .bat?
did you started in the correct flash mode?
power + M
ap fastboot??
Use the one in my signature, its also psouza but is different (the one in psouza thread never worked for me)
this one (post by chaoticweaponry file by roots wiki) works in the mode i ssaid
the multiupload link is dead i think, but in the last posts there is a dropbox
http://dl.dropbox.com/u/61707107/Ve...izon+DROID+3+OTA+5.6.890+to+phone_psouza4.zip
Pete's One Click Easy Unbrick sounds like a mash-up of his root tool and the quick unbricking script. Just to clarify, it was the MS DOS looking window that comes up after clicking "CLICK HERE TO FLASH etc."?
Hold "X" and power. When u get the triangle press both volume up and volume down @ the same time. Wipe data a couple times followed by wipe cache a couple times. Pull the battery, then use the easy unbrick method in fastboot. You will want to find a way to have a good if not full charge before you unbrick. Should do the trick.
~SU!C!D3~ \,,/.(*_*).\,,/
Sent from my UnLocked XT862 Droid 3 with full XT883 2.3.6 on Straight Talk GSM
I have bricked my phone numerous times recently and have found a very simple way to recover from it, without even having to plug it in to the computer. The OTA leak found here: http://forum.xda-developers.com/showthread.php?p=23223061 can be put on the root of your SD card and installed using the stock recovery. Power + x followed by volume up/down, wipe data, wipe cache, install zip from sd and selecting the OTA zip. I have recovered several times with this and it is pretty handy to be able to do it where ever you happen to be. Of course you will still have to root and reinstall your other goodies, but it works.
Side note: This OTA leak can NOT be rooted with the standard D3 root methods. You must use the D4 root method to gain root privileges.
gierso said:
did you started in the correct flash mode?
power + M
ap fastboot??
Use the one in my signature, its also psouza but is different (the one in psouza thread never worked for me)
this one (post by chaoticweaponry file by roots wiki) works in the mode i ssaid
the multiupload link is dead i think, but in the last posts there is a dropbox
http://dl.dropbox.com/u/61707107/Ve...izon+DROID+3+OTA+5.6.890+to+phone_psouza4.zip
Click to expand...
Click to collapse
Yes it was in ap fastboot. I will give the one in your sig a shot, as I have been using psouza's original zip. Maybe it will work *crossfingers*
redsox958 said:
Pete's One Click Easy Unbrick sounds like a mash-up of his root tool and the quick unbricking script. Just to clarify, it was the MS DOS looking window that comes up after clicking "CLICK HERE TO FLASH etc."?
Click to expand...
Click to collapse
Yes, it' the psouza Fast/Easy unbrick, using the moto-fastboot files, etc.
queberican351 said:
Hold "X" and power. When u get the triangle press both volume up and volume down @ the same time. Wipe data a couple times followed by wipe cache a couple times. Pull the battery, then use the easy unbrick method in fastboot. You will want to find a way to have a good if not full charge before you unbrick. Should do the trick.
Click to expand...
Click to collapse
That has been done several times, with no changes to the system. While Recovery states that it completes the wipe, it does not appear to wipe anything. I'm going to try the link gierso posted to see if this helps.
mikedyk43 said:
I have bricked my phone numerous times recently and have found a very simple way to recover from it, without even having to plug it in to the computer. The OTA leak found here: http://forum.xda-developers.com/show...php?p=23223061 can be put on the root of your SD card and installed using the stock recovery. Power + x followed by volume up/down, wipe data, wipe cache, install zip from sd and selecting the OTA zip. I have recovered several times with this and it is pretty handy to be able to do it where ever you happen to be. Of course you will still have to root and reinstall your other goodies, but it works.
Side note: This OTA leak can NOT be rooted with the standard D3 root methods. You must use the D4 root method to gain root privileges.
Click to expand...
Click to collapse
Good to know that you can try it from the SD. I may give that a shot as well. I have bricked my D2 over and over F'ing with it and have always been able to recover from it easily...figures that the first time my D3 does it and it tells me to go pound sand.
Thanks on the D4 note.
-
I'm setting this thing down for a day I need to take a step back so I can try the other file that gierso posted without throwing this thing against a wall.
Had this happen to my wife's Droid 3 and saw 1 post on another forum about a user it has happened to. After conversing with Motorola regarding my "Groundhog Day" issue (ie - no matter what you do, nothing changes on the phone... kinda like the movie Groundhog Day starring Bill Murray), the tech support reps came to the conclusion that somehow the NAND because write-protected. Neither RSD nor the Fast-FBZ nor Safe Mode would let me alter the phone in any way. I had to have the handset exchanged out under manufacturer's warranty...
Try on "AP Fastboot" mode
moto-fastboot -w
moto-fastboot erase system
moto-fastboot erase preinstall
moto-fastboot erase cache
moto-fastboot reboot-bootloader
now use the Psouza Fast/Easy unbrick.
If this does not help. than it would be better to go for a replacement.
Related
Ok so here's the rundown. I was trying my hand at making the elder scrolls:daedric runes font work for my phone. Got it pretty close, was using fresh type to change some of the preinstalled system fonts. (if you have any idea how i can install a custom font package that would be wonderful as well). but anyway, it asks me to reboot then bam, won't start up.
after reboot after reboot, i decide to say screw it, i pop it into recovery mode and factory reset it. I figure oh well, not much gets lost. turn it back on, still no luck. I give it another go, no luck that time either, i remove both the sim and the SD card and go again, still no money.
At this point i download the full fxz, and RSD lite 5.5 and i boot up into AP fastboot mode and procede to start flashing. Goes well till it hits about step 13 or 14 when then it says fail. I try to restart the phone thinking no big, it probably doesn't need webtop just to boot, now it says
Invalid CG OTV (CG: system): Invalid SP Data
Invalid CG OTV (CG: webtop): Invalid SP Data
Invalid CG Version (CG: webtop)
Invalid CG OTV (CG: webtop)
To make matters worse, regardless of what i try to flash ( at this point i'm not even sure if it's flashing) nothing seems to bring it past the AP Fastboot start screen. I've tried the minimal version, the full version with rsd lite. I've tried the standalone fastboot transfer method by moving each image file individually with the ADB daemon. What's infuriating is that each flash says success except for the full FXZ... yet it still never boots past the AP fastboot screen. I might be missing something, i was browsing the forum looking for answers nothing is coming up.
Ran across a few posts about a locked bootloader. Would that have any affect on this? Another few bits of useful info, my battery is full, i have an external charger, i'm running this on a laptop, i have access to a desktop but it's my room mate's and is in his room so i want to disturb him as little as possible, so unless it makes a profound difference i'd like to use my laptop. Any info would be great guys.
Looking forward to some help. I'm about exhausted.
Dhacker29's 1-click restore. Development.
Sent from my DROID BIONIC using xda premium
I've already tried that, and just tried again, finishes, says okay on all steps then when it asks me to root it reboots and goes to the same screen as i mentioned in OP.
bump?............
Solved it. For future reference, if the problem isn't solved with one click root you'll need to use the full version of the fxz. In addition, using the back of a desktop vs a Laptop makes ALL the difference! USE A DESKTOP.
Generalkenobi_2 said:
Solved it. For future reference, if the problem isn't solved with one click root you'll need to use the full version of the fxz. In addition, using the back of a desktop vs a Laptop makes ALL the difference! USE A DESKTOP.
Click to expand...
Click to collapse
where can you find the full fxz anymore? every link i click on for it says to contact administrator....can only find the minimal one without problem
Generalkenobi_2 said:
Solved it. For future reference, if the problem isn't solved with one click root you'll need to use the full version of the fxz. In addition, using the back of a desktop vs a Laptop makes ALL the difference! USE A DESKTOP.
Click to expand...
Click to collapse
i was able to get my Bionic to the point where i want it..however, whenever the phone powers up or reboots, it ALWAYS goes to the AP Fastboot Screen with the "flash failure" message...i have to turn the phone back off, hold both volume buttons down, press the power button, go into the menu screen and choose "normal POWERUP" and things go along fine.....what can i do to repair my Fastboot function so i don't have to go through this procedure every time. Have tried RSD Lite, but get the same flash failed message
kbatrph said:
i was able to get my Bionic to the point where i want it..however, whenever the phone powers up or reboots, it ALWAYS goes to the AP Fastboot Screen with the "flash failure" message...i have to turn the phone back off, hold both volume buttons down, press the power button, go into the menu screen and choose "normal POWERUP" and things go along fine.....what can i do to repair my Fastboot function so i don't have to go through this procedure every time. Have tried RSD Lite, but get the same flash failed message
Click to expand...
Click to collapse
I need help with this as well my bionic is doing the same thing. Im supposed to be selling it has anyone found a fix for this..?
all you have to do is successfully flash any file and it will stop giving you the flash failure message
IE pick a file flash it using fastboot and voila problem solved. I know this because i ran into this issue when messing with my bootloader research.
Flashing
I went back to stock and applied the update. I tried to root and failed so I tried to flash back to stock. I am stuck entering fastboot like you guys. I can start the phone in recovery but I am looking for a fix. I see that you wrote flash any file to get it to stop. Can you provide some specifics on how you did this and what file you flashed. The one I tried to flash will end in flash failure.
yeah sure:
put the files from the fxz in same folder as adb and fastboot. Reboot into fastboot mode make sure you have drivers for phone.
fastboot flash devtree device_tree.bin
simple and will not loose a thing doing this one.
should clear up your flash failure.
See attached file
denpth said:
yeah sure:
put the files from the fxz in same folder as adb and fastboot. Reboot into fastboot mode make sure you have drivers for phone.
fastboot flash devtree device_tree.bin
simple and will not loose a thing doing this one.
should clear up your flash failure.
Click to expand...
Click to collapse
ii get an error
---------- Post added at 06:42 PM ---------- Previous post was at 06:42 PM ----------
DDRR2 said:
See attached file
Click to expand...
Click to collapse
wont flash...wonder what someones suppose to do with that rar file???
can someone post the fill FXZ and how to flash it? I am hosed at Boot Failure
smilepak said:
can someone post the fill FXZ and how to flash it? I am hosed at Boot Failure
Click to expand...
Click to collapse
just got done fixing this isue myself with the bionic pathsaver method. make sure you read and follow all directions and it will work
DDRR2 said:
See attached file
Click to expand...
Click to collapse
I don't think anybody acknowledged that this works. Thank you to the developer.
I'm having the same issue updating from 886 to 893. The flash fails then boots up to the flash failure screen every time. This is fixed easily with the app above.
DDRR2 said:
See attached file
Click to expand...
Click to collapse
I can't thank you enough for this. When we get to heaven we'll meet Jesus, St. Peter, all the awesome devs out there and you my friend.
thanks that worked like a charm.
driod help
wrong place sorry
I keep on trying to flash ANYTHING to my bionic(stuck in ap fastboot with boot failure) and every time I go to flash something it keeps on shifting to "FAILED<remote: battery low>
I am at my wits end, I tried the fxz, and it failed, I tried the r3l3as3droot fix and it fails.... Can someone PLEASE help soon?
You've got to charge the battery. There are ways to do it by cutting off the end of a spare usb cable, and you can find that here somewhere.... I just don't remember where.
Try flashing via RSD lite. See if that works.
http://rootzwiki.com/topic/13105-a-easier-way-back-to-the-update-path/
Sent using xda premium
RSD fails almost immediately. I dont knwo what else to do. I think I officially bricked myself.
htcdesirezgeorge said:
RSD fails almost immediately. I dont knwo what else to do. I think I officially bricked myself.
Click to expand...
Click to collapse
Did you even read sreven.rn's post. You need to charge your battery. Fastboot/rsd will do nothing until you get that battery charged.
This post has the answer you seek
http://www.droidforums.net/forum/droid-x-tech-support/189467-need-help-dead-battery-trick.html
Sent from my DROID BIONIC using xda premium
That is a great tip dellenrules! I'll have to keep this one in mind.
Anyone know if the battery will charge in this FlashBoot mode?
I am on Battery Low, can't boot to phone screwed myself earlier with all the flashing. Not stuck at Flash Failed, can't RSD, can't flash via Flashboot because of low battery.
Wonder if I leave it there will it charge
smilepak said:
Anyone know if the battery will charge in this FlashBoot mode?
I am on Battery Low, can't boot to phone screwed myself earlier with all the flashing. Not stuck at Flash Failed, can't RSD, can't flash via Flashboot because of low battery.
Wonder if I leave it there will it charge
Click to expand...
Click to collapse
I'm 99% positive it will not charge in fastboot mode.
Crap. Was there like a USB hack somewhere that will get this to work? I can't remember. I am screwed!
HOW TO FIX A TOTALLY BRICKED BIONIC (& HOW TO McGUYVER CHARGE A DEAD BATTERY too)
I have prepared an uber zip file that contains all you need.
Wish I had it last night! I was up until 3am, worked on this for about 6 hours, and then this finally worked. I tried everything. fastboot, one click this, sd lite, etc. none of it worked.
You will praise me.
this worked - Got my phone back!
of course, I tried every solution in the world and was profoundly frustrated for hours and ran out of battery. but this WORKED. NOTHING else did.
I also had to do the McGuyver thing with an old blackberry usb charger.
snip the end off, strip the red and black wires, insert the red to positive on your battery (battery out of the phone!) insert black to negative, THEN plug in the charger. let it go for at least 1/2 hour.
my uper zip file - UNZIP THIS file to a FOLDER on YOUR DESKTOP.
http://dl.dropbox.com/u/12759680/fastboot.zip
also Manually copy files (update893 and update901) to your SD card!!!!!
(take out the micro sd, load the files onto it using an adapter.)
1. Put phone in Fastboot mode, connect to computer [hopefully you have the drivers installed. if not, search for Motorola_End_User_Driver_Installation_5.2.0_32bit or the 64 bit if that's your operating system
whenever there is a command, I copied it and pasted it in the command window (ctrl v does not work to paste, you must right click and then paste) dont copy the friggin quotation marks
2. Open a command terminal and go to the Stock folder ("cd C:\Documents and Settings\YOUR NAME\Desktop\fastboot")
3) type these commands in the terminal window and wait for the flashing to finish before going to the next line.
----> "moto-fastboot.exe flash webtop grfs.img" (This file will be flashed in 4 parts)
----> "moto-fastboot.exe flash preinstall preinstall.img"
----> "moto-fastboot.exe flash system system.img" (This file will be flashed in 2 parts)
----> "moto-fastboot.exe reboot"
be patient. some of these steps take a while and you think nothing is happening.
then you see some action in the command prompt box.
Then reboot into stock recovery (volume up+down and power; then select recovery then volume up)
When in recovery, hit both volume up+down, then go to wipe data
then flash update893.zip
If you come upon the triangle with the exclamation point and the android man, dont freak out, hit the power button, down volume, both volume at once, and eventually you will be in recovery.
you will so do a dance.
be patient. some of these steps take a while and you think nothing is happening.
then you see some action in the command prompt box.
wait a day. then, If you're feeling adventurous, reboot into stock recovery and flash 901!
I'm no maven, but I got my phone back and then to 901.
havent rooted again but I'm waiting for the developers to catch up to 901, which I downloaded and flashed after getting the damn phone back.
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: )
Reboot phone...
Invalid Flash mode (s) (Boot Failed)
0A.61
Battery OK
OK to Program
Transfer Mode:
USB Connected
Invalid CG Version (CG: boot)
is where I am at now
finally got these two installed
----> "moto-fastboot.exe flash preinstall preinstall.img"
----> "moto-fastboot.exe flash system system.img" (This file will be flashed in 2 parts)
----> "moto-fastboot.exe reboot"
once reboot, did wipe cache and wipe data
update 893, failed during verify data....
crap..
Ok, here is the deal. It is IMPOSSIBLE to revive your phone from the process that I did. UNDER NO CIRCUMSTANCES SHOULD YOU FLASH 5.5.901 AND THEN DO A FACTORY RESTORE OR RECOVER IN TO A CUSTOM ROM. DO NOT ATTEMPT OR YOU WILL IRREPARABLE BRICK YOUR PHONE!
htcdesirezgeorge said:
Ok, here is the deal. It is IMPOSSIBLE to revive your phone from the process that I did. UNDER NO CIRCUMSTANCES SHOULD YOU FLASH 5.5.901 AND THEN DO A FACTORY RESTORE OR RECOVER IN TO A CUSTOM ROM. DO NOT ATTEMPT OR YOU WILL IRREPARABLE BRICK YOUR PHONE!
Click to expand...
Click to collapse
What are you talking about when you say factory restore? Are you talking about doing a factory data reset?
Because many have done FDR's without a problem.
Have you tried the one click script that P3Droid and the guys at rootzwiki came up with to get everybody back on the upgrade path?
That's weird.
I returned to stock from 901 using the method in the first link I posted without a hitch.
FYI
Sent from my DROID BIONIC using xda premium
I believe the second post was the answer to your problem.. now second option is to cut a usb cable and connect the negative and positive cables to your battery and leave it for an hour or so to charge..
Sent from my DROID BIONIC using XDA App
This guy obviously doesn't want any help.
He pops in once in a while with a frantic nonsensical post and doesn't bother to read our posts that can help him.
nateohio said:
This guy obviously doesn't want any help.
He pops in once in a while with a frantic nonsensical post and doesn't bother to read our posts that can help him.
Click to expand...
Click to collapse
Oh no, I definitely wanted help BUT I was dumb and used my bionic as my sole internet connection. I have my insurance replacement now($100 down the drain). I had tried ALL of the fixes but non even remotely succeeded. What ended up happening was that I somehow made it where it would not even begin to flash files. I purchased an extended battery but yyyyyeeeeaaaaahhhhh lol, so now I have shiney new supplied for my new phone lol.
Oh wells, you win some and lose some.
Fails for me on first line
idivorceyou said:
I have prepared an uber zip file that contains all you need.
Wish I had it last night! I was up until 3am, worked on this for about 6 hours, and then this finally worked. I tried everything. fastboot, one click this, sd lite, etc. none of it worked.
You will praise me.
this worked - Got my phone back!
of course, I tried every solution in the world and was profoundly frustrated for hours and ran out of battery. but this WORKED. NOTHING else did.
I also had to do the McGuyver thing with an old blackberry usb charger.
snip the end off, strip the red and black wires, insert the red to positive on your battery (battery out of the phone!) insert black to negative, THEN plug in the charger. let it go for at least 1/2 hour.
my uper zip file - UNZIP THIS file to a FOLDER on YOUR DESKTOP.
http://dl.dropbox.com/u/12759680/fastboot.zip
also Manually copy files (update893 and update901) to your SD card!!!!!
(take out the micro sd, load the files onto it using an adapter.)
1. Put phone in Fastboot mode, connect to computer [hopefully you have the drivers installed. if not, search for Motorola_End_User_Driver_Installation_5.2.0_32bit or the 64 bit if that's your operating system
whenever there is a command, I copied it and pasted it in the command window (ctrl v does not work to paste, you must right click and then paste) dont copy the friggin quotation marks
2. Open a command terminal and go to the Stock folder ("cd C:\Documents and Settings\YOUR NAME\Desktop\fastboot")
3) type these commands in the terminal window and wait for the flashing to finish before going to the next line.
----> "moto-fastboot.exe flash webtop grfs.img" (This file will be flashed in 4 parts)
----> "moto-fastboot.exe flash preinstall preinstall.img"
----> "moto-fastboot.exe flash system system.img" (This file will be flashed in 2 parts)
----> "moto-fastboot.exe reboot"
be patient. some of these steps take a while and you think nothing is happening.
then you see some action in the command prompt box.
Then reboot into stock recovery (volume up+down and power; then select recovery then volume up)
When in recovery, hit both volume up+down, then go to wipe data
then flash update893.zip
If you come upon the triangle with the exclamation point and the android man, dont freak out, hit the power button, down volume, both volume at once, and eventually you will be in recovery.
you will so do a dance.
be patient. some of these steps take a while and you think nothing is happening.
then you see some action in the command prompt box.
wait a day. then, If you're feeling adventurous, reboot into stock recovery and flash 901!
I'm no maven, but I got my phone back and then to 901.
havent rooted again but I'm waiting for the developers to catch up to 901, which I downloaded and flashed after getting the damn phone back.
Click to expand...
Click to collapse
My phone goes strait to AP Fastboot Flash Mode (S)(Invalid CDT) at power up.
When I enter the first line of these instructions "moto-fastboot.exe flash webtop grfs.img" I get an error that states
load_file: could not allocate 1397489664 bytes
error: cannot load 'grfs.img'
Any ideas?
I was attempting to update my *.2233 build to the new *.242 last night using "House of Droid," when I completely screwed it up. For the purposes of this inquiry, we'll call it an accident... but I used the "Repair AP Fastboot error (flash cdt.bin) option. Now, when I attempt to boot, I get the following:
-----------------
AP Fastboot Flash Mode (S) (Flash Failure)
0A.61
Battery OK
OK to Program
Transfer Mode:
USB Connected
Invalid CG Version (CG: devtree)
-----------------
After hours of searching forums, I have tried the "FixCDT" application with no luck, tried to flash various versions of Android including my current build (2233), 232, 242 and 905_FXZ using RSD Lite all with the same return:
-----------------
Failed flashing process: 6/22 flash cdt.bin "cdt.bin" -> Phone returned FAIL
-----------------
When I attempt to use the FixCDT, I get the following error:
-----------------
"Writing 'cdt.bin'... INFOPreflash validation failure
FAILED <remote: >
-----------------
Is my phone toast, or is there hope?
Thanks!
i would suggest reading this forum
http://www.droidforums.net/forum/mo...-5-893-fxz-901-902-compatible-902-update.html
now remember with the .242 leak you are not able to downgrade back to anything lower than .235...
however, if you had not tried updating to .242, i would suggest downloading and installing rsd lite, than download and flash
http://www.4shared.com/zip/kQydtP-d/newvrz_xt875_59902xt875verizon.html
using rsd lite, that should fix your problem..
remember, if you have updated to .242 DO NOT FLASH THAT FILE.. WILL BRICK YOUR PHONE.
Thanks for your response. I never actually got to the point where I could flash the file. I "pushed" the update to the SDcard, messed up the CDT file and rebooted to discover it wouldn't flash or boot normally. I actually already have and have tried that particular file. I get the same "failed flashing process" error.
Thanks,
You need to use the reinstall 242 option. If you selected the 242 install option and then used the repair ap fastboot option you essentially just flashed the 242 Cdt.bin. You have no choice but to install 242 or you will stay bricked. I don't even want to know how you got into this situation....
Sent from my Xoom using Tapatalk 2
Thanks for your help guys, SamuriHL's suggestion fixed my poor phone.
Much appreciated!
Awesome! Glad it worked.
Sent from my Xoom using Tapatalk 2
How to "reinstall 242 option".
SamuriHL said:
You need to use the reinstall 242 option. If you selected the 242 install option and then used the repair ap fastboot option you essentially just flashed the 242 Cdt.bin. You have no choice but to install 242 or you will stay bricked. I don't even want to know how you got into this situation....
---------------
Hi SamuriHL, I have the same problem messed up the CDT file and rebooted to discover it wouldn't flash or boot normally. RSD Lite v5.7 failed flashing process 6/22. How do you do the "reinstall 242 option" with 902 / 905? Thanks,
Click to expand...
Click to collapse
You need to be very clear on what you were flashing when it failed. If you flash the wrong Cdt.bin it'll make things worse. What version were you on and what are you trying to go to? The option to repair the Cdt.bin is in my house of Bionic script once you make a selection for what you are trying to install.
Sent from my Xoom using Tapatalk 2
I did it too....
Hey guys.. I just did what the first poster did... I think that I ruined my phone.
I was running .905 rooted, and I downloaded HoB .244 and .246. I tried to install .244 and it sent the .zip to my sd-card, but then it wouldn't finish the install. It told me that I would have to use the stock recovery. I booted into stock recovery, and I tried to install it again. It got all the way to"Installing..." and then gave me an error message that had "targa" in it, and said something about not having the correct location or something. I used the "Repair AP Fastboot error" and now I am stuck at:
AP Fastboot Flash Mode (S) (Boot Failure)
0A.61
Battery Low
Cannot Program
Connect USB
Data Cable
Invalid CG Version (CG: devtree)
That screen comes up when I plug my phone into the wall charger, and when I plug my phone into my PC it is not recognized. furthermore if I plug it into my PC before I plugged it into my wall charger I just get a white LED notification light, and I cannot turn it on.. I just couldn't wait for the OTA ICS update any longer, and now I fear that I have bricked my phone.... Please help me.. anyone...
It's not bricked but you will need to charge the battery and it can't be done in the state your phone is in. So either get an external charger or research "non-standard battery charging methods". Once you do that, I suggest uninstalling the HoB fully, redownloading 7.2, FXZ, RSD 5.7, and 246 and install them in that order. You will have to tell it no to transfer, no to check the md5, no to reboot into AP Fastboot, and then start when it asks if you want to flash with RSD. It WILL NOT work until you put a charged battery in it.
Well I got a little bit closer... I realized that my phone wasn't being detected as plugged into my USB because I had a USB extender... I eft my phone on the charger earlier today, at the fastboot locked screen, and it didn't charge. I ran FixCTD and it tries to work, but then it says (FAILED: Remote Battery Low)...
It WILL NOT CHARGE in that state. You need to externally charge it. Otherwise you're just wasting your time.
SamuriHL said:
It WILL NOT CHARGE in that state. You need to externally charge it. Otherwise you're just wasting your time.
Click to expand...
Click to collapse
Thanks for the helpful suggestions I hope that I can fix my phone soon....
Once you charge the battery, reinstall the HoB as I suggested, and redo the install process, it'll work.
SamuriHL said:
Once you charge the battery, reinstall the HoB as I suggested, and redo the install process, it'll work.
Click to expand...
Click to collapse
I have a friend with a Moto Bionic too, and I am going to use his phone as a surrogate for my battery. I am so happy to hear that I didn't ruin my phone. I feel like I skipped a step in your instructions in the first place, and now I am paying for it lol. :silly:
CinderCloud said:
I have a friend with a Moto Bionic too, and I am going to use his phone as a surrogate for my battery. I am so happy to hear that I didn't ruin my phone. I feel like I skipped a step in your instructions in the first place, and now I am paying for it lol. :silly:
Click to expand...
Click to collapse
Skipping steps is never a good idea.
I re-downloaded everything, and I have a charged battery ready now. So I am supposed to install FXZ, 5.7, and then 246 right in a row now?
HoB 7.2, FXZ, RSD 5.7, and then 246 in that order, yes.
I installed all of them now. FXZ is working it's magic on my phone at this very moment! THANK YOU SOOO MUCH!!!!!
You're welcome. Enjoy!
Hey guys,
i did stupid things witch my razr i and now i'm completely lost…maybe someone can help?
I've been impatient enough to try to flash the leaked jb rom 3 days ago. That did'nt work
No, whenever i power up the phone it shows the red M logo and nothing happens.
I can power it down by holding vol+down and power for more than 4 seconds.
If i release the keys, it goes back to te red M,
If i keep holding vol+down it boot s into AP fastboot flash mode (secure boot) 20.0f
i can choose recovery and that'll work, but i don't have an update for external storage. rebooting from there leads to red M.
Normal Powerup, Factory and BP Tools are choosable, log says Booting into… but nothing happens after that, i'll stay in fastboot.
Power off works.
I tried to flash various images via »fastboot flash boot/recovery/system«, but nothing worked out.
I flashed the files from Razri_Root_Linux, two files (retail central europe) from here sbf.droid-developers, but nothing helped, every reboot leads to the red M.
I read about RSD-Lite, tried to install it under Win7, got it, but was lost after the Program always complained about an invalid xml.
Since i don't own that machine i went back to my linuxbox where i found sbf_flash, but i don't get it how to put the pieces together (which file/s to use)
Any hints on how to go from here?
[EDIT:] I downloaded 91.2.26001.Retail.en.EU.zip and did all the steps from flashandboot.bat, read
fastboot flash boot
fastboot flash system
fastboot flash recovery
next step ist to select recovery, did this an cwm comes up, sideloaded RAZRiRoot2.zip everything is pisitively quited, no errors are shown.
reboot leads to red M
wiped data/factory reset, reboot
red Logo.
I'm completely lost, please help
[\EDIT]
greetings, D.
I had same problem
Hello.
I had same problem because I did very stupid thing. I flashed homemade JB and because some apps don´t work I tried downgrade my i to ICS back....
My i stucked at the red M then I tried same thing as you and phone still booted into red M.
So I tried in windows cmd and FlashAndRoot.bat from this .zip "91.2.26001.Retail.en.EU - 4.1.2" it did nothing, but I tried to choose in fastboot mode BP Tools, then my i booted and started to flash JB what I can see in command window. Phone was still connected to PC. After next reboot my phone has work normally with JB.
I hope to help you. Let me know.
Lucki
Hi Lucki
thanks for jumping by.
Lucki_X said:
Hello.
So I tried in windows cmd and FlashAndRoot.bat from this .zip "91.2.26001.Retail.en.EU - 4.1.2" it did nothing, but I tried to choose in fastboot mode BP Tools,
Click to expand...
Click to collapse
I tried this, and display on razr i says »Booting into BP Tools mode…«
and nothing more happens, display stays on…
and after some time pc automounts a "cd-rom drive" with some motorola files (Autorun.inf MDMSetup.xml MotorolaDeviceManagerSetup.exe MDMSetup.ini MotorolaDeviceManager_2.2.28)
but it still won't reboot…
i don't know.
Hi.
I had opened command window, "FlashAndRoot.bat" was running (I pressed any key) process was running (it means freezing ) and at this time I chose in fastboot booting into BP tools mode. My phone did restart and after it "FlashAndRoot.bat" process started to flash JB. After flashing my phone is going normally with JB. But some apps don´t work in JB.
Lucki
Lucki_X said:
Hi.
I had opened command window, "FlashAndRoot.bat" was running (I pressed any key) process was running (it means freezing ) and at this time I chose in fastboot booting into BP tools mode. My phone did restart and after it "FlashAndRoot.bat" process started to flash JB. After flashing my phone is going normally with JB. But some apps don´t work in JB.
Lucki
Click to expand...
Click to collapse
Doesn't work. :crying:
since i use linux i opened FlashAndRoot.bat in texteditor and executed the comands from there in terminal
only chance for the script to stop and wait is IMHO(correct-me-if-i'm-wrong) "adb wait-for-device push RAZRiRoot2.zip /sdcard/RAZRiRoot2.zip & adb reboot bootloader"
but that message "Booting into BP Tools mode…" just stays there forever, or does it take longer than 5minutes?
dogo77 said:
but that message "Booting into BP Tools mode…" just stays there forever, or does it take longer than 5minutes?
Click to expand...
Click to collapse
In my case it booted within 10 second and ran.
I am noob, I am writing just my experience. I couldn´t give you another advice, sorry.
I'm not sure how far the real installation went, but i would find Windows computer, get RSD (6.0-6.14) and try to flash ICS first. If failed due to impossibility of downgrading, then try JB. While you are able to boot to Recovery - don't loose hope yet
okaban said:
I'm not sure how far the real installation went, but i would find Windows computer, get RSD (6.0-6.14) and try to flash ICS first. If failed due to impossibility of downgrading, then try JB. While you are able to boot to Recovery - don't loose hope yet
Click to expand...
Click to collapse
Yeah. I'm still stuck at the red logo, or indeed, at a blueish "Bootloader unlocked warnig" message since i was able to install parts of an image from sbf.droid-developers. But flashing always fails while trying to flash system.img_signed.
After reading and trying a lot these last days i think i have to install windows somewhere just to get rsd-lite to run.
sbf_flash for linux didn't work for me and fastboot gives stange warnings about "Invalid sparse file format at header magi"…
so i'll give rsd a try before i give up. As i read in posts by HSDPilot, this is the only tool that works
thanks for your help!
I have a stock Verizon Moto X (XT1060) that was running 4.4.4. I was on a flight Friday using the phone in airplane mode to run Spotify and Podkicker - noticed the phone was running a little hot so I shut the apps down for a while. Anyway, upon landing I take the phone off airplane mode and the usual minor flood of emails/texts/updates comes in. About 30 seconds after this the phone begins alternately flashing "Process android.process.acore has stopped" and "Process android.process.media has stopped." These cycled for about 5 displays of each, then would disappear for about 45 seconds, then start again. Tried resetting the phone, letting the battery die, no success.
Saturday I tried to navigate into settings to do a factory reset, but the screen froze whenever I tapped on the "backup and reset" menu. Could access all the other menus from settings (until the error cascade started again....). I was able to boot the phone into recovery mode and wiped the cache - nothing. Went back into recovery mode to do a factory reset and now I appear to be stuck in a boot loop - the Moto logo pops up, buzzes, and then does nothing for about a minute or two before trying again. I can get it into recovery mode and tried to wipe the cache and factory reset again, but still nothing.
Any thoughts? Tried looking at other threads but didn't seem to find anything like this. Thanks!
Try this cmd in fastboot
fastboot oem fb_mode_clear
http://forum.xda-developers.com/showthread.php?t=2738055
hbenz2008 said:
Try this cmd in fastboot
fastboot oem fb_mode_clear
http://forum.xda-developers.com/showthread.php?t=2738055
Click to expand...
Click to collapse
No luck, unfortunately. Still stuck on the Moto screen. I can force the phone to reset by holding down the power button and then get it into fastboot, my computer recognizes the fastboot device, and the code seems to have run fine. Thanks for the idea - any other thoughts?
If you can still get into fastboot mode you can try flashing only the stock 4.4.4 system.img via mfastboot. That will not wipe your data. If that does not work I would do a full return to stock via mfastboot or you can use rsd.
Thanks Travis I'll give it a shot. I never enabled USB debugging and never unlocked my phone before this happened - I imagine I'll need to try and unlock the bootloader first, no?
cmcgowan said:
Thanks Travis I'll give it a shot. I never enabled USB debugging and never unlocked my phone before this happened - I imagine I'll need to try and unlock the bootloader first, no?
Click to expand...
Click to collapse
No, don't need to unlock boot loader to flash the system.img just enable USB debugging in developer options. Tap build number 5 times to enable developer options. If you have never flashed anything before via fastboot rsd might be easier for you.
Thanks - I've used fastboot before on an older phone but never enabled USB debugging on this phone and now can't get to enable it since I'm stuck with this boot loop. Downloading the files from Moto now so will give it a shot tonight anyway. Can't really break it more than it's already broken since all I've got now is a shiny light up paperweight.
You will still need to download the stock images for 4.4.4 for Verizon and extract them. You can flash via rsd or simply flash just the system by running the command "mfastboot flash system system.img"
You will have to have the image file in the same folder as your mfastboot.exe I usually keep all mine in platform tools.
Sigh. Got everything downloaded but when I tried to flash either the boot image, recovery image, or system image, I ran into errors
Here's what displayed (sub boot/recovery for system - same basic error):
c:\{Path}\mfastboot flash system system.img
(bootloader) Variable not supported!
target max-download-size: 768MB
Multi-Flash is enabled!
sending 'system' (262144 KB)...
OKAY [16.793s]
writing 'system'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 17.756s
I was following option 5 from mark @ cdma forum's guide to return motox to stock (can't link b/c I don't have enough posts...) . No issues until I got to the flash boot boot.img step.
I'm assuming this is due to not having USB debugging enabled prior to my phone eating itself, though I'm not sure. Willing to try other things since I love my Moto X but my cheap replacement phone arrives tomorrow (hopefully) so at least its not the end of the world...
You are sure you got the 4.4.4 images? You did not try to downgrade right?
Yup. Definitely got the 4.4.4 images (went back to the Moto site and it will let me download the 4.4.4 immediately but made me request authorization for 4.4.2) and I know I was running the most recent version since I checked for an upgrade on my phone last week in the hope that Moto had released 5.0.
You are following this guide? http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
If USB debugging is not on you can manually boot you device to boot loader mode. Then fastboot or rsd should work fine.
---------- Post added at 11:36 PM ---------- Previous post was at 11:32 PM ----------
Moto X Restore and unbrick for any major US carrier: https://youtu.be/jhhktIkwi7Q
I appreciate the help...but still no luck. That's basically what I've been doing and I went back through following those instructions - at every step I get the "variable not supported" error and then it fails at the flash boot step with the error message I described earlier.
cmcgowan said:
I appreciate the help...but still no luck. That's basically what I've been doing and I went back through following those instructions - at every step I get the "variable not supported" error and then it fails at the flash boot step with the error message I described earlier.
Click to expand...
Click to collapse
You are opening the cmd screen from the same folder as your images and fastboot and mfastboot.exe correct? From your error it looks like your cmd screen is directed to your "C" drive.
Sorry, just didn't type out the whole thing - the cmd path is to the platform-tools folder where all of the files are also located...
Damn was hoping it was something simply like that. Have you tried rsd?
I haven't - didn't enable USB debugging and for whatever reason the package I downloaded from Moto doesn't include the XML file of instructions. Most of the links from the youtube video and some of the links from the XDA guide earlier are also dead so seems like I'm pretty much out of options. Thanks for all of your help - guess I'm going with the $80 replacement till I'm up for an upgrade!