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?
Related
I was dumb enough to root my phone and try using some custom roms just to get a black notification bar and a couple other things. Thats literally all I wanted. Used Cyan, couldnt get notification bar to change color so went back to original. Anyways thought I'd try flashing the black desire bar or w/e, and failed.
Tries booting up and gets half stuck on the nexus 'X' animation loop. It gets really laggy and studders, never fully completing the loop. So I say eff it after fifteen or so minutes and reboot to recovery. Only it's the stock android recovery, not that clockwork one? So I'm lost, can't flash back to original, and decide i'll just try the factory reset. I have no time for this stuff at this point, and just want my phone so I can talk to people.
Did factory reset/wipe option, and still nothing, stuck on boot. Don't know what to do and I would greatly appreciate some help or advice. Honestly would be so sad if this $500 phone is a paperweight.
Dude relax,
1.First boot to superboot
2.Flash your clockwork (Or any other recovery). DONT REBOOT.
3.Go straight to recovery,
4.Restore your nandroid back up,
--- If you dont have back up then you have to download rom what you want (Stock froyo can be found some where in htc site)
--- Select mass storage option in the recovery and copy there the zip file, then flash it.
Tadaa everything is working again
Read my signature, "unroot / restore your Nexus", and execute. If you have ever updated to FRG83, you might be out of luck and no PASSIMG.ZIP will flash. In this case, you'll need to connect using ADB and run flash_image to flash recovery (most probably you'll get adb shell even if your phone isn't finishing boot - just make sure you run adb shell early enough in the boot). Once you've flashed the recovery, get into it and proceed with a custom ROM. If you flash stock again, your recovery will be lost again. If you didn't set up ADB (enable "USB Debugging" option on your phone) - then you're seriously out of luck. If you have it, but don't know how to use it - spend time reading and understanding "flashing Recovery" guide in the same place from my signature (Wiki), and if you have any further questions along the way - ask here.
You're not booting up because you've screwed up framework-res.apk and possibly some other system files - so you're stuck in boot loop. Need to read and understand what you're doing before you're doing it. It's really not that hard, and not willing to spend enough time understanding things "pays off" if mishaps happen - and they happen.
elkyur said:
Dude relax,
1.First boot to superboot
Tadaa everything is working again
Click to expand...
Click to collapse
He can't boot! Do you read what I read? He's stuck in a bootloop! What boot are you talking about?!
Take your time reading before you rush answering with wrong and incomplete instructions that won't get the OP anywhere. A good portion of mishaps happens because of instructions like these.
This is alot for me to take learn in such quick time to be honest.
I can't even get adb to recognize my phone and i've followed all the steps. My computer makes the noise that something has been plugged in through USB, but nothing else. Under that program to uninstall drivers, I try uninstalling them, but they just stay there, nothing changes.
As for the USB debugging and me being ****ed, I'm pretty sure I left that on.
Maybe it would help me if I told you more about what I know and what I've done.
Literally just followed the step by step instructions from this site theunlockr.com/ to root my phone and use a custom rom.
In the process it made me install PDANet (again probably means nothing, but I don't know).
If adb isn't recognizing my phone, I can't flash using it. Again thank you for the help, as I really am clueless about most stuff like this.
Most of the time when doing anything that could possibly do any harm to a device, I am very cautious. I have hacked several PSP's and didn't think this would be much different...
I read all about the rooting, and knew full well all i wanted to do was get a new notification bar, I didn't really read into the rest as I had no desire or use for that information. Then everything went well, and I learnt how easy it was to go back if I screwed up or didn't like what I had flashed. Not to mention people saying it's near impossible to brick your phone unless your really trying to. Maybe that was just me being ignorant, this could not have happened at a worse time. And I cannot thank you enough for your help thus far.
Thank you for the help. Your guides were very helpful. But unfortunately every step of the way I have run into some sort of problem.
When trying to install the sdk drivers, it won't let me install the amd64 or the i386, but only both of them together. As in it selecting usb_drivers installs (where both of the seperate drivers can be found). I don't know if this is right or not.
When typing in "fastboot devices", "HT036P901361 decives" shows up, but when viewed in USBDeview, 2 of the 3 HT036P901361 drivers show as not connected. The only one that shows as connected is the "vendor specific" one.
Also adb devices, shows nothing.
So again, I'm asking for advice or help.
Edit: So I can reboot fastboot through my computer, but cannot flash anything,
typing in "flashboot flash recovery recovery.img" I get a "cannot load recovery.img".
My recovery.img file is saved on the root of the SD card which is in the phone. Is this the correct way to do it? If so I assume it's still because of the issue stated at the beginning of this post (before edit).
Edit 2: Okay decided to try this
fastboot flash recovery C:\CWrecovery.img (where its located on my hdd), and it starts then says failed infoSignature.
volsey said:
Thank you for the help. Your guides were very helpful. But unfortunately every step of the way I have run into some sort of problem.
1. When trying to install the sdk drivers, it won't let me install the amd64 or the i386, but only both of them together. As in it selecting usb_drivers installs (where both of the seperate drivers can be found). I don't know if this is right or not.
2. When typing in "fastboot devices", "HT036P901361 decives" shows up, but when viewed in USBDeview, 2 of the 3 HT036P901361 drivers show as not connected. The only one that shows as connected is the "vendor specific" one.
3. Also adb devices, shows nothing.
So again, I'm asking for advice or help.
4. Edit: So I can reboot fastboot through my computer, but cannot flash anything,
typing in "flashboot flash recovery recovery.img" I get a "cannot load recovery.img".
My recovery.img file is saved on the root of the SD card which is in the phone. Is this the correct way to do it? If so I assume it's still because of the issue stated at the beginning of this post (before edit).
Edit 2: Okay decided to try this
fastboot flash recovery C:\CWrecovery.img (where its located on my hdd), and it starts then says failed infoSignature.
Click to expand...
Click to collapse
Let's get one thing straight. You need to read more, I guess, because you still don't know the basics - and with the lack of knowledge, it's going to be hard to help you.
Fastboot commands and driver only work when you're booted into bootloader - which is, 3 droids on skateboards on white screen and text menu, get there by booting with trackball or volumedown button pressed.
adb works only when you're booting the OS - which means, you don't touch anything and let the phone boot. Right when boot animation starts, adb should also start.
1. That's correct.
2. Are you booting into bootloader? There should be no other way to view fastboot driver. In that case, DON'T boot to bootloader, just reboot your phone and let it loop, and only then try "adb devices". If it works - use the "flash_image" method to flash recovery.
3. Read (2) above.
4. If your bootloader isn't unlocked (does it show a padlock below Nexus logo when you boot?), you won't be able to flash non-standard recovery through fastboot. You might be able to flash a complete system image through fastboot, though. Download a factory image, FRF91 for example, unzip it, then do "fastboot flash system system.img", "fastboot flash boot boot.img", and reboot.
When you flash something, you should open the Command prompt in the same directory as the file you're trying to flash! Or use full path for the image you're flashing. And it should be on the computer, not on SD card.
If everything fails - just unlock your bootloader and fastboot flash anything you want.
I am using bootloader.
C:\android-sdk-windows\tools>fastboot flash system system.img
sending 'system' (58570 KB)... OKAY [ 8.293s]
writing 'system'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 15.014s
That's the error I'm getting everytime.
I got the system.img from hXXp://developer.htc.com/adp.html, I tried looking for FRF91 but could only find megaupload links, and I had exceeded my limit somehow.
As for adb, still getting no devices when I leave it to boot by itself even though I've:
Uninstalled the 3 drivers, unplugged/rebooted, plugged back in/turned back on, and it automatically installs the wrong drivers again too quickly to do anything about it. I've gone into advanced system settings and checked it to never install system drivers automatically. Tried updating drivers, all say they're up to date.
1)So is bootloader not an option for me? Or is there something else I haven't tried? Why am I getting the signature errors?
2)Is it the drivers that are keeping adb from recognizing my phone? How do I fix this?
Any suggestions?
Ok, looks like USB debugging isn't on. In that case, there are exactly 2 options:
1) from here:
http://developer.htc.com/
Download FRG83 image for Nexus, rename to PASSIMG.ZIP, put on the root of your SD card (you can't use the phone for it, so use SD card reader), reboot into bootloader, it'll ask you to flash system image, answer "yes", wait for it to flash. Keep the phone powered. WAIT.
2) if it doesn't work - you're out of luck. "fastboot oem unlock" it is. Then you can flash whatever you want with fastboot.
help anyone, i tried to flash the bionic following directions to a T, i get an error message when using the full install at 9/15 saying the data size is not what was expected. i get the same error at 4/5 on the minimal fxz files. I do not understand how to use the fastboot method as i get error messages saying that the option of "fastboot" is not recgonized as a function or a process. Please anyone with answers?
What are you trying to do flash stock?
Sent from my DROID BIONIC using xda premium
yea, i deleted some of the stock apps that i didnt use or couldnt use. but i inadvertanlgy deleted the app which allows for hdmi mirror mode so i wanted to flash back to stock thinking it would reinstall whatever i removed and now the phone is stuck on the ap fastboot screen
crxlvr said:
yea, i deleted some of the stock apps that i didnt use or couldnt use. but i inadvertanlgy deleted the app which allows for hdmi mirror mode so i wanted to flash back to stock thinking it would reinstall whatever i removed and now the phone is stuck on the ap fastboot screen
Click to expand...
Click to collapse
Have u any adb experience?
Sent from my DROID BIONIC using XDA Premium App
crxlvr said:
yea, i deleted some of the stock apps that i didnt use or couldnt use. but i inadvertanlgy deleted the app which allows for hdmi mirror mode so i wanted to flash back to stock thinking it would reinstall whatever i removed and now the phone is stuck on the ap fastboot screen
Click to expand...
Click to collapse
downloads the Android sdk. Install to cmakes things easier in the long run) once installed download fast boot to the
Tool folder in the sdk folder. In windows start search for "cmd" right click and copy, past inside the "tool" folder. Open it from the tool folder. You're are doing this to make it easier. Your directory in cnd will be set already to the correct directory, something like c:/sdk/..../tool/
Download the fastboot imgs in tools folder. Open cMD from tool folder. Then type your command to send the imgs u need.
Sent from my DROID BIONIC using XDA Premium App
thanks for the tip, ill try it out now ill let you know how it goes
---------- Post added at 10:29 PM ---------- Previous post was at 10:15 PM ----------
naturally it seems as though the phone will not charge now so when i run the first command it holds on the waiting for device screen
So after many failed attempts, it seems that I am failing for my battery not being fully charged as I got an error saying battery low, phone >fail, so i think that is my issue. I will try to use a battery only charger and use the fastboot flash method and will report back when i learn something.
Yes, to flash anything u need battery charged, the problem is that the OS needs to load to charge the bat, do if your phone is soft bricked ur in a pickel, I hear u can swap your bat for a charged one at vzw.
Sent from my DROID BIONIC using XDA Premium App
If you fastboot the boot.img and system.img you can successfully flash without a full battery. Takes all of 5 minutes.
Just saying.
Or you could pick up a standalone battery charger:
http://www.amazon.com/Motorola-89508N-Battery-Charger-BIONIC/dp/B005C31FIG
That one comes with a battery, I'm a pretty heavy user so it's nice to know I have a fully charged battery waiting for me when I get home from work
DroidTh3ory said:
If you fastboot the boot.img and system.img you can successfully flash without a full battery. Takes all of 5 minutes.
Just saying.
Click to expand...
Click to collapse
How are you doing this? I'm running Ubuntu and when I run:
./fastboot flash boot boot.img
I get this reply:
sending 'boot' (8192 KB)... FAILED (remote: Battery Low)
mikecheat04 said:
How are you doing this? I'm running Ubuntu and when I run:
./fastboot flash boot boot.img
I get this reply:
sending 'boot' (8192 KB)... FAILED (remote: Battery Low)
Click to expand...
Click to collapse
I have done it 10+ times.... I'm not sure what the tolerance is for fastboot compared to RSDlite, but RSD lite kept failing when I had a VERY low battery. What I did, was have everything ready for fastboot, pulled the battery, put it back in, and plugged in the wall charger. It opened up with boot errors of course. I let it sit on the charger for about 5 minutes, quickly unplugged, the USB from the WALL, into my laptop, and hit enter on the fastboot, sent and wrote, same with system.
I don't know if it didn't have time to read the state or what. But it worked.
DroidTh3ory said:
I have done it 10+ times.... I'm not sure what the tolerance is for fastboot compared to RSDlite, but RSD lite kept failing when I had a VERY low battery. What I did, was have everything ready for fastboot, pulled the battery, put it back in, and plugged in the wall charger. It opened up with boot errors of course. I let it sit on the charger for about 5 minutes, quickly unplugged, the USB from the WALL, into my laptop, and hit enter on the fastboot, sent and wrote, same with system.
I don't know if it didn't have time to read the state or what. But it worked.
Click to expand...
Click to collapse
You the man DroidTh3ory! I tried this with my standard battery and it didn't work, it was totally freakin dead. As soon as I'd unplug from the wall it'd turn off. Luckily I still had my extended battery that had just enough charge to do the job. It copied over the boot.img and system.img then did the clear cache/data and I got the damn battery low error again. Pulled the battery, put it back in, plugged power in from wall, switched over to PC and did the command again and it took! Now I'm back up and running. Gonna root and do a nandroid backup and keep my standard battery fully charged and in a safe place in case this ever happens again!
mikecheat04 said:
You the man DroidTh3ory! I tried this with my standard battery and it didn't work, it was totally freakin dead. As soon as I'd unplug from the wall it'd turn off. Luckily I still had my extended battery that had just enough charge to do the job. It copied over the boot.img and system.img then did the clear cache/data and I got the damn battery low error again. Pulled the battery, put it back in, plugged power in from wall, switched over to PC and did the command again and it took! Now I'm back up and running. Gonna root and do a nandroid backup and keep my standard battery fully charged and in a safe place in case this ever happens again!
Click to expand...
Click to collapse
Glad you got it!!.... You have summon your inner Ninja but it works. Lol
DroidTh3ory said:
If you fastboot the boot.img and system.img you can successfully flash without a full battery. Takes all of 5 minutes.
Just saying.
Click to expand...
Click to collapse
It really took all of 5 minutes. Somehow I goofed and soft bricked my Bionic. My battery was at a miserable 10%. Luckily I have an extended battery and I was able to use the fastboot method. Worked like a charm. Thanks!
None of the instructions on fastbooting mentioned the need for the AdbWinApi.dll to be included in the fastboot-images folder. So I'm mentioning it now. Otherwise you'll get an error asking for that particular .dll.
Same Problem - Solved
I had the same problem. Followed all the instructions and I was getting really frustrated. Then I read a tip about moving the img file to the C: root directory - BINGO BANGO BINGO. Work the first time.
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
Ok I’ve trying for days now to get my bionic to load the boot.img and every method has failed. I have tried RD lite both files ,Fast boot recovery by dhacker and R3l3AS3DRoot_V2_Windows. I accidently wiped webtop and now just boots to AP. Is there a way to manually open a term window and push this boot.img ? I’ve read a lot about ADB . Anyways Battery is good for now, it was full when I went stupid. I was rooted and fovever rooted on .893
Opened a cmd and tried sending flashboot boot.img answers back
boot 8192kb
INFOPreflash Validation failure
Failed (Remote)
System.img completes fine.
I've tried different computers and countless web sites
I don't believe you can fastboot flash the boot.img because of the locked bootloader. What happen is you pull the battery out and hold both volume buttons and power at same time and then select reboot normal. If you deleted your webtop you need to fastboot the grfs.img
rgb2448 said:
I don't believe you can fastboot flash the boot.img because of the locked bootloader. What happen is you pull the battery out and hold both volume buttons and power at same time and then select reboot normal. If you deleted your webtop you need to fastboot the grfs.img
Click to expand...
Click to collapse
Hey Thanks for replying, I was reading about that last night here---->mydroidworld.com/forums/droid-bionic-forum/9800-how-get-your-phone-back-upgrade-path
After reading what you said i went ahead and pushed that webtop.img to my and now it boots up. Now i just need to get root back, i've seen others at this point so it shouldn't be to tough.
! TuNaCaN ! said:
Hey Thanks for replying, I was reading about that last night here---->mydroidworld.com/forums/droid-bionic-forum/9800-how-get-your-phone-back-upgrade-path
After reading what you said i went ahead and pushed that webtop.img to my and now it boots up. Now i just need to get root back, i've seen others at this point so it shouldn't be to tough.
Click to expand...
Click to collapse
Go to the second post on the back on upgrade path and there is a one click root
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.