Database Develop

[Q] Milestone bricked? (boot loops, bootloader error)

Hello guys,
I hope you get not bored by these every day "I bricked my milestone" threads, but I do really need and would appreciate your help. So here is what's going on:
After Motorola delays the official 2.2 ROM again I decides to try CM6. I asked a friend, who has flashed his Milestone before, for an instruction and he gave me one.
I had an Milestone from O2 Germany with latest 2.36 update. First I made the recovery vulnerable. I downgraded to 2.34 and flashed the vulnerable-recovery only (of course the one for my 90.78 bootloader). I checked if the system was working right after every flash via RSD, and the phone bootet properly anytime. I applied the Androidiani update.zip and entered the OR. I wiped and applied the CM update via OR.
After I applied the CM update, the OR told me to reboot and so I did. I saw the Motorola logo and then the bootloader came up with an error message (Err:A5,70,39,00,27). I wanted to restore via Nandroid, but I no longer could enter the recovery (not to mention the OR). So I asked my friend again what to do and he told me to flash vulnerable recovery again via RSD (yes, I could enter bootloader mode) to be able to enter recovery again. After I flashed I could enter the recovery, but some new mad behavior appeared. The bootloader error disappeared, but every time I tried to boot, the phone ended up in boot loops (Motorola logo --> reboot --> Motorola logo --> reboot -->...).
Then I tried to restore via Nandroid. This seemed to work well, but after a reboot I got this bootloader error again.
To conclude:
flashing via RSD --> boot loops (recovery and bootloader work)
flashing via OR --> bootloader error (only bootloader works)
Some guy from android-hilfe.de told me to flash the bootloader, but I know this is very dangerous. So I went to the #milestone-modding irc-channel and asked for help. They gave me the advice to try to flash other sbf's, maybe an old 2.0. As I tried this today I got a new problem: the sbf file won't work. When I press 'start' in RSD everything starts as usual. But when the phone should show the message "sw update in progress" nothing happens and RSD get stuck on 0%. At the and I get the following message:
'ERROR: Flash failure: Phone[0000]: Error erasing subscriber unit. Device API Error: 0xE003003F Command: ERASE (Error Code: e003003f)'
So I did not proceed. Anybody a suggestion what to do? I'm really helpless.
Greetings Luke
PS: the forum search lead me to this thread. The problem sounds pretty similar.

Try flashing a 2.1 sbf. Let me know what happens. Please use RSDlite v4.6 or higher

vladstercr said:
Try flashing a 2.1 sbf. Let me know what happens. Please use RSDlite v4.6 or higher
Click to expand...
Click to collapse
Good advice. Latest rsd and drivers. Try a different machine...rsd is moody. Try the GOT sbf, it includes the vuln recovery. I have had problems with Win7 that got solved with a different machine with xp.
If all of this does not work, we need to try fastboot. But try the rest first...
Sent from my Milestone using Tapatalk

Hey, thanks for your replie
I did this 3 hours ago. I used the full sbf for the 2.36 update for the German o2 Milestone. I also tried DACH and other versions before.
The result is always, that I end up getting boot loops like described above. RSDLite tells me the file is successfully flashed and unlike a 2.0 sbf the Milestone shows the message "sw update in progress".
I'm using RSDLite 4.9.

LukeTS said:
Hey, thanks for your replie
I did this 3 hours ago. I used the full sbf for the 2.36 update for the German o2 Milestone. I also tried DACH and other versions before.
The result is always, that I end up getting boot loops like described above. RSDLite tells me the file is successfully flashed and unlike a 2.0 sbf the Milestone shows the message "sw update in progress".
I'm using RSDLite 4.9.
Click to expand...
Click to collapse
Try a different version of RSDlite on a different machine or operating system.

Caz666 said:
Good advice. Latest rsd and drivers. Try a different machine...rsd is moody. Try the GOT sbf, it includes the vuln recovery. I have had problems with Win7 that got solved with a different machine with xp.
If all of this does not work, we need to try fastboot. But try the rest first...
Sent from my Milestone using Tapatalk
Click to expand...
Click to collapse
You mean a GOT 2.1 or the 2.2 sbf?
Unfortunately I have no machine running XP at the moment. But I have a virtual XP running on my Win 7 Pro. But I guess it's no good idea to try to flash on this?!

LukeTS said:
You mean a GOT 2.1 or the 2.2 sbf?
Unfortunately I have no machine running XP at the moment. But I have a virtual XP running on my Win 7 Pro. But I guess it's no good idea to try to flash on this?!
Click to expand...
Click to collapse
There is no GOT 2.1
GOT is only 2.2. You can try GOT 2.2 sbf and RSD v4.6

Oh, okay =)
I thought there is a version by them.
Gonna try your advices and post the results.
Thank you so far

Wow, your problem still same me.
I was tried and solved:
_Flash with any rom you have
_Milestone will auto reboot after flash done and loop
_Don't worry about that, remove battery in 5s and re-plugin
_Turn on your milestone: hold X and POWER to access Recovery. Select Wipe and reboot

killed said:
Wow, your problem still same me.
I was tried and solved:
_Flash with any rom you have
_Milestone will auto reboot after flash done and loop
_Don't worry about that, remove battery in 5s and re-plugin
_Turn on your milestone: hold X and POWER to access Recovery. Select Wipe and reboot
Click to expand...
Click to collapse
Did that before and tried it now. Didn't work for me. But thanks for your advice
I also flashed 2.2 from GOT. I was able to flash with RSD and it did not fail. But there is still the boot loop. So nothing changed.
This time I did it with my Atom-netbook and used RSD 4.6.

Ok, so I think I need to try something else. Only flashing with RSD easily doesn't work for me. Like I said in my post before: GOT 2.2 and the advice from killed did not work. Still getting boot loops.
So what would you recommend me to do?

LukeTS said:
Ok, so I think I need to try something else. Only flashing with RSD easily doesn't work for me. Like I said in my post before: GOT 2.2 and the advice from killed did not work. Still getting boot loops.
So what would you recommend me to do?
Click to expand...
Click to collapse
You tried GOT 2.2.1 sbf and it didn't work? Can you access recovery? There was a suggestion of fast boot, but I don't know what that is (just in case you wanted to google it or something, not sure). Do you have the drivers installed for your computer?
You could try this:
milestonefail said:
for some people RSDLite doesnt work properly. One way to fix that is put the SDL.bat file (attatched as .txt, change to .bat before using) in the RSDLite installation folder, move the .sbf file you are using to the same folder, and drag that .sbf to SDL.bat.
)
Click to expand...
Click to collapse
Read the end of this post: http://forum.xda-developers.com/showpost.php?p=11372663&postcount=51 Read the end
Also look here for the link for the drivers: http://forum.xda-developers.com/showpost.php?p=11163403&postcount=27
Good luck! I am not responsible if anything happens to your device.

Yep, it didn't work. RSD said the flash passed, but I always get boot loops. I can access th recovery, but even nandroid in OR doesn't work (I get back to that bootloader error I described in my first post).
I also don't know what fastboot is, but just using google won't help me, because I don't know, what I meant to do with fastboot.
The drivers are installed. Without them I guess RSD wouldn't even recognize my phone.
I also tried the batch file you posted, but it didn't work. I wasn't able to start the flashing process. I guess, the only thing the batch file does is to start RSD with admin rights.
These are all methods I tried and they just don't work. I need something different to this usual helpful stuff. That's why I posted in this forum, because I tried everything and I'm helpless at the moment.
Thanks for your advice anyway. I hope someone has a solution soon.

fastboot most likely will do nothing for you if a nandroid backup fails. Fastboot is a way to flash individiual partitions in case your recovery or nandroid does not work.
It works like adb (command line from a conected computer) and requires nothing on the phone. But if nandroid works...it will not do anything different.
Basically, a nandroid is a collection of .img files (one per partition) that a script flashes in sequence. With fastboot, you could flash all of the .img files from computer command prompt.
I would:
1) try a different nandroid...download the latest leak (01/25 from the dev forum). It is in nandroid format. I would factory reset the phone first.
2) if this does not work, i would fastboot erase and the fastboot flash (look up the syntax) every .img in the nandroid backup. This is just in case you OR is corrupted in some way...not likely, but i am out ideas.
Sent from my Milestone using Tapatalk

Hey,
thanks for your reply.
Your first recommendation would probably not work. I tried 4 different Nandroid backups and every time I get the bootloader error.
Basically I have no idea what fastboot is, where I get it from and not to mention how to get it work, so I think this is no option for me.
Right now I have resigned. Nothing seems to work. I consider getting a new phone. But before I do this I wanna ask you one last question: can flashing the bootloader theoretically effect anything? I think my phone IS bricked at the moment, so I'm not anymore afraid of flashing the bootloader. But if it would even theoretically be impossible, that this would change anything, then it's just a waste of time. So does flashing 90.78 bootloader via RSD Lite change anything?
Thank you!

LukeTS said:
Hey,
thanks for your reply.
Your first recommendation would probably not work. I tried 4 different Nandroid backups and every time I get the bootloader error.
Basically I have no idea what fastboot is, where I get it from and not to mention how to get it work, so I think this is no option for me.
Right now I have resigned. Nothing seems to work. I consider getting a new phone. But before I do this I wanna ask you one last question: can flashing the bootloader theoretically effect anything? I think my phone IS bricked at the moment, so I'm not anymore afraid of flashing the bootloader. But if it would even theoretically be impossible, that this would change anything, then it's just a waste of time. So does flashing 90.78 bootloader via RSD Lite change anything?
Thank you!
Click to expand...
Click to collapse
Why give up without trying? I believe you should flash it to see if it changes anything...How worse than this can it get?
Please...do not take my words for granted...Inform yourself from other sources before you try this...and if you do let us know if you successfully managed to get your phone back!

You misunderstood me. I wanted to try it, but if someone would have said that it's a waste of time, then I wouldn't have done it.
So I tried it, but flashing the bootloader (90.78 --> 90.78) didn't change anything. Still getting boot loops.
What do you think. Try a downgrade to 90.73? Is a downgrade even possible?

LukeTS said:
You misunderstood me. I wanted to try it, but if someone would have said that it's a waste of time, then I wouldn't have done it.
So I tried it, but flashing the bootloader (90.78 --> 90.78) didn't change anything. Still getting boot loops.
What do you think. Try a downgrade to 90.73? Is a downgrade even possible?
Click to expand...
Click to collapse
I dont think that is possible. I've read here on the forum somewhere that downgrading the bootloader is not possible...but you should search, maybe you find that it's possible.
Anyhows, I dont think your phone is lost, I just think we're missing something!

I also think it's not possible. I've read this in some forums, too.
It seems that it isn't lost. I was happy, as I found out, that I can enter recovery and bootloader. I thought it could easily be restored. But then nothing worked for me. So we must miss something, but I have no clue what.

What do you mean by:
"Then I tried to restore via Nandroid. This seemed to work well, but after a reboot I got this bootloader error again."
Are you sure you have enough battery?
You could try restoring a nandroid from other recovery. Replace the recovery from your sd-card. If you use Androidiani 3.3 try an older version of it or another OpenRecovery.

[Q] [SOLVED] AP Fastboot Flash Mode (s) (Boot Failure)

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

Unable to flash ANYTHING please help!

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?

[Q] Almost as good as a brick - No wipe, no SBF

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.

[Q] Bricked razr i help - locked bootloader

Well, this is embarrassing...
Current Status:
After a factory wipe and reinstalling (phone was OK after that) and an OTA, i managed to nearly brick my razr.
Currently every time i start it lands in fastboot (according to RSD Lite mode S) with the message fastboot reason: flash failed
after 'fastboot reboot-bootloader' i can operate the menus but only changing the console type and power off work, everything else results in a freeze.
Reflashing CFC_signed_customer_8.7.1I-110_IFW-DE-32_O2DE.xml.zip or 31 is not possible, since the OTA update apparently changed boot[1], gpt[2], and few other things to version "8.7.1I-110_IFW-DE-39" (the only thing i can flash from those are the recovery partitions and from the new one the gpt.bin)
Custom fastboot also does not work, since i'm not eligible according to Motorola ( tis was my first thought to check the custom boots & finally unlock the bl *g*)
I already ordered the factory adapter (hey, you never know, when you're gonna need one) & My Battery still has ~3.9v left, so i think a few tries should not hurt that much : >
TL;DR, Here's my question:
1) is it possible to patch the images provided in CFC_signed_customer_8.7.1I-110_IFW-DE-32_O2DE.xml.zip with the binary patches from Blur_Version.81.5.32002.XT890.O2.en.DE (updates to: 8.7.1I-110_IFW-DE-39_O2DE) and then maybe re-flash them to get my razr back from the near death zone?
2) should i hope and pray that Motorola announces JB upgrade and provides us with the full system images within the next few days?
3) can anyone find a full system image / full update with the version: 8.7.1I-110_IFW-DE-39_O2DE ?
References:
[1]: from update-script:
assert(apply_patch("MTD:boot:11534336:affeb8868070f6e6f061143b662e03b5bf65b2f3:11534336:19bf404a393a50d08a809affd45df5692e36e1db",
"-", 19bf404a393a50d08a809affd45df5692e36e1db, 11534336,
affeb8868070f6e6f061143b662e03b5bf65b2f3, package_extract_file("patch/boot.img.p")));
[2]: There is a brand new gpt.bin file within the OTA package
Cheerio,
Andy

The Problem is, without unlocking your Bootloader, you can't downgrade the Boot. img.
I would suggest you to grap the 39002 O2 Homemade Fastboot from Mattlgroff and flash only the Boot. img out of it. If you're an lucky guy, you're able to boot after that.
An Guy from my Home Forum tried the downgrade from 40002 today with an locked boot loader. RSD stopped @ point 1 GPT. His solution to boot his phone again was to flash the gpt.bin out of the 40002 OTA .zip.
So your only chance to get your phone back is to find flashable Images from the 39002 or 40002 because of the secure Level.
The easiest way is to unlock the device, I can downgrade to any FW. Or you'll have to wait for an updated Fastboot File to flash with RSD.

Hokay, apparently i had a typo yesterday when i tried to unlock the bootloader
But, now after trying the custom fastboot, i still land in fastboot with reason: Sticky bit fastboot
and all other menus still cause a freeze : /

If you're now unlocked, get an EU FW, regardless what Version. Open the XML with Notepad + or any similar Programm and delete ONLY the complete Line that contains MOTOBOOT. Save the XML and start RSD 6.1.4.
After that you should be good to go.

HSD-Pilot said:
If you're now unlocked, get an EU FW, regardless what Version. Open the XML with Notepad + or any similar Programm and delete ONLY the complete Line that contains MOTOBOOT. Save the XML and start RSD 6.1.4.
After that you should be good to go.
Click to expand...
Click to collapse
Purrrrfect, i owe you a bottle of wine.
Problem solved : >

Yeah, I'm glad I could help you out... RazR I Nr. 8 > Strike

bricked
hi guys the same thing happen to me i cant use rsd or fastboot because it says stigki bit fastboot.and in rsd it fails tryin to flash boot. im in mexyco i was using the new ota for 30006 that would be 40002. i just try to erASE THE BOOT LINE AND IT DIDNT WORKIT SAID THE SAME. HELP

So you're on 40002 and tried to flash back with RSD and your Bootloader is locked?
RSD failed on step one, right?

brick
Yes sir. Iwas on 40002 and with the rsd i was trying to go back to stock 30006,but on step 3 it says fail. Then i try to fastboot 40002 but it tqkes me again to fastboot and its freezes when i try to open a command like normal boot or recovery. I tried to eras the lineinside of motoboot where it says motoboot like the guy you just helped. But in my case still gets stuck on step 3in the rsd. So could you send me images of how erase the line of motoboot on text editor?? Im boot unlocked.

You mean 31006...Here ya go (unpack it > i can't attach an .xml)

Thank u sir. So i flash this on rsd,right? Vause i think that this is the one i have.the last digits are 31 on mine an starts cfc . Something else. I cant really tell u cause im at work but tonight i'll try ur method. Hope it works.

http://www.mediafire.com/download.php?ud9kowzk1uw2bcb
Use RSD 6.1.4 and copy the xml into the fastbootfolder. That's all...BTW: Charge your battery if possible or hope you got enough juice!

unbricked
thank you sir. everything like new!!!!!!!!
i"ll buy u some beers.

my razr i is workin now but i cant update the ota for the 31006 thats going to take me to 40002??

You're trying to update regular over the Phone or the manual over the leaked Update.zip? If you're trying it over the leaked zip, than beware. There's one if you're coming from 31006 and one from 32002.
Sent from my XT890

I go into software update, then i download the file, its like 50mb. Then it goes into rwcovery but the android dies and says aborted. So then i tried in recovery mode to flash zip blur ota 310006 but it happen the same. So i decided to stay in mis rom the 31006 from sept. But i was wondering if now i could flash in fastboot another rom like 40002? I saw u guy have the ota update for that rom.
---------- Post added at 03:04 PM ---------- Previous post was at 02:07 PM ----------
I go into software update, then i download the file, its like 50mb. Then it goes into rwcovery but the android dies and says aborted. So then i tried in recovery mode to flash zip blur ota 310006 but it happen the same. So i decided to stay in mis rom the 31006 from sept. But i was wondering if now i could flash in fastboot another rom like 40002? I saw u guy have the ota update for that rom.

Thank you - you're the best
HSD-Pilot said:
If you're now unlocked, get an EU FW, regardless what Version. Open the XML with Notepad + or any similar Programm and delete ONLY the complete Line that contains MOTOBOOT. Save the XML and start RSD 6.1.4.
After that you should be good to go.
Click to expand...
Click to collapse
My RAZR i works again thanks to HSD-Pilot. You saved my life.
THANK YOU
Roman

how found fastbootfolder me friend, sorry im newbie and me phone is death, please help

Razr i black screen after update phone not getting on
After i have unlock bootloader and root the phone....i have to do a fresh update to last Jelly Bean....phone have got turno of for starting insatll the update....and have rest like that...............When i press Power or Power and Vol Down is just doinf a short vibrate and the Notification led stay On for 10 sec after led OFF and a short vibrate.....>>Connecting to PC no getting any device on RSD or Fastboot and in Windows detect as a MEDFIELD device for wich no driver i found anywhere.........Phone was having 100% POWER before doing all this....adn i have try on several Pc with diferent Windows and diferent 32 or 64 bit with all RSD, drivers Sdk, etc installled and same results.....if anyone have a ideea how to repair will be a really expert on this modding devices....thank you and ...HELP