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.
Related
Ok so here's the rundown. I was trying my hand at making the elder scrolls:daedric runes font work for my phone. Got it pretty close, was using fresh type to change some of the preinstalled system fonts. (if you have any idea how i can install a custom font package that would be wonderful as well). but anyway, it asks me to reboot then bam, won't start up.
after reboot after reboot, i decide to say screw it, i pop it into recovery mode and factory reset it. I figure oh well, not much gets lost. turn it back on, still no luck. I give it another go, no luck that time either, i remove both the sim and the SD card and go again, still no money.
At this point i download the full fxz, and RSD lite 5.5 and i boot up into AP fastboot mode and procede to start flashing. Goes well till it hits about step 13 or 14 when then it says fail. I try to restart the phone thinking no big, it probably doesn't need webtop just to boot, now it says
Invalid CG OTV (CG: system): Invalid SP Data
Invalid CG OTV (CG: webtop): Invalid SP Data
Invalid CG Version (CG: webtop)
Invalid CG OTV (CG: webtop)
To make matters worse, regardless of what i try to flash ( at this point i'm not even sure if it's flashing) nothing seems to bring it past the AP Fastboot start screen. I've tried the minimal version, the full version with rsd lite. I've tried the standalone fastboot transfer method by moving each image file individually with the ADB daemon. What's infuriating is that each flash says success except for the full FXZ... yet it still never boots past the AP fastboot screen. I might be missing something, i was browsing the forum looking for answers nothing is coming up.
Ran across a few posts about a locked bootloader. Would that have any affect on this? Another few bits of useful info, my battery is full, i have an external charger, i'm running this on a laptop, i have access to a desktop but it's my room mate's and is in his room so i want to disturb him as little as possible, so unless it makes a profound difference i'd like to use my laptop. Any info would be great guys.
Looking forward to some help. I'm about exhausted.
Dhacker29's 1-click restore. Development.
Sent from my DROID BIONIC using xda premium
I've already tried that, and just tried again, finishes, says okay on all steps then when it asks me to root it reboots and goes to the same screen as i mentioned in OP.
bump?............
Solved it. For future reference, if the problem isn't solved with one click root you'll need to use the full version of the fxz. In addition, using the back of a desktop vs a Laptop makes ALL the difference! USE A DESKTOP.
Generalkenobi_2 said:
Solved it. For future reference, if the problem isn't solved with one click root you'll need to use the full version of the fxz. In addition, using the back of a desktop vs a Laptop makes ALL the difference! USE A DESKTOP.
Click to expand...
Click to collapse
where can you find the full fxz anymore? every link i click on for it says to contact administrator....can only find the minimal one without problem
Generalkenobi_2 said:
Solved it. For future reference, if the problem isn't solved with one click root you'll need to use the full version of the fxz. In addition, using the back of a desktop vs a Laptop makes ALL the difference! USE A DESKTOP.
Click to expand...
Click to collapse
i was able to get my Bionic to the point where i want it..however, whenever the phone powers up or reboots, it ALWAYS goes to the AP Fastboot Screen with the "flash failure" message...i have to turn the phone back off, hold both volume buttons down, press the power button, go into the menu screen and choose "normal POWERUP" and things go along fine.....what can i do to repair my Fastboot function so i don't have to go through this procedure every time. Have tried RSD Lite, but get the same flash failed message
kbatrph said:
i was able to get my Bionic to the point where i want it..however, whenever the phone powers up or reboots, it ALWAYS goes to the AP Fastboot Screen with the "flash failure" message...i have to turn the phone back off, hold both volume buttons down, press the power button, go into the menu screen and choose "normal POWERUP" and things go along fine.....what can i do to repair my Fastboot function so i don't have to go through this procedure every time. Have tried RSD Lite, but get the same flash failed message
Click to expand...
Click to collapse
I need help with this as well my bionic is doing the same thing. Im supposed to be selling it has anyone found a fix for this..?
all you have to do is successfully flash any file and it will stop giving you the flash failure message
IE pick a file flash it using fastboot and voila problem solved. I know this because i ran into this issue when messing with my bootloader research.
Flashing
I went back to stock and applied the update. I tried to root and failed so I tried to flash back to stock. I am stuck entering fastboot like you guys. I can start the phone in recovery but I am looking for a fix. I see that you wrote flash any file to get it to stop. Can you provide some specifics on how you did this and what file you flashed. The one I tried to flash will end in flash failure.
yeah sure:
put the files from the fxz in same folder as adb and fastboot. Reboot into fastboot mode make sure you have drivers for phone.
fastboot flash devtree device_tree.bin
simple and will not loose a thing doing this one.
should clear up your flash failure.
See attached file
denpth said:
yeah sure:
put the files from the fxz in same folder as adb and fastboot. Reboot into fastboot mode make sure you have drivers for phone.
fastboot flash devtree device_tree.bin
simple and will not loose a thing doing this one.
should clear up your flash failure.
Click to expand...
Click to collapse
ii get an error
---------- Post added at 06:42 PM ---------- Previous post was at 06:42 PM ----------
DDRR2 said:
See attached file
Click to expand...
Click to collapse
wont flash...wonder what someones suppose to do with that rar file???
can someone post the fill FXZ and how to flash it? I am hosed at Boot Failure
smilepak said:
can someone post the fill FXZ and how to flash it? I am hosed at Boot Failure
Click to expand...
Click to collapse
just got done fixing this isue myself with the bionic pathsaver method. make sure you read and follow all directions and it will work
DDRR2 said:
See attached file
Click to expand...
Click to collapse
I don't think anybody acknowledged that this works. Thank you to the developer.
I'm having the same issue updating from 886 to 893. The flash fails then boots up to the flash failure screen every time. This is fixed easily with the app above.
DDRR2 said:
See attached file
Click to expand...
Click to collapse
I can't thank you enough for this. When we get to heaven we'll meet Jesus, St. Peter, all the awesome devs out there and you my friend.
thanks that worked like a charm.
driod help
wrong place sorry
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
I keep on trying to flash ANYTHING to my bionic(stuck in ap fastboot with boot failure) and every time I go to flash something it keeps on shifting to "FAILED<remote: battery low>
I am at my wits end, I tried the fxz, and it failed, I tried the r3l3as3droot fix and it fails.... Can someone PLEASE help soon?
You've got to charge the battery. There are ways to do it by cutting off the end of a spare usb cable, and you can find that here somewhere.... I just don't remember where.
Try flashing via RSD lite. See if that works.
http://rootzwiki.com/topic/13105-a-easier-way-back-to-the-update-path/
Sent using xda premium
RSD fails almost immediately. I dont knwo what else to do. I think I officially bricked myself.
htcdesirezgeorge said:
RSD fails almost immediately. I dont knwo what else to do. I think I officially bricked myself.
Click to expand...
Click to collapse
Did you even read sreven.rn's post. You need to charge your battery. Fastboot/rsd will do nothing until you get that battery charged.
This post has the answer you seek
http://www.droidforums.net/forum/droid-x-tech-support/189467-need-help-dead-battery-trick.html
Sent from my DROID BIONIC using xda premium
That is a great tip dellenrules! I'll have to keep this one in mind.
Anyone know if the battery will charge in this FlashBoot mode?
I am on Battery Low, can't boot to phone screwed myself earlier with all the flashing. Not stuck at Flash Failed, can't RSD, can't flash via Flashboot because of low battery.
Wonder if I leave it there will it charge
smilepak said:
Anyone know if the battery will charge in this FlashBoot mode?
I am on Battery Low, can't boot to phone screwed myself earlier with all the flashing. Not stuck at Flash Failed, can't RSD, can't flash via Flashboot because of low battery.
Wonder if I leave it there will it charge
Click to expand...
Click to collapse
I'm 99% positive it will not charge in fastboot mode.
Crap. Was there like a USB hack somewhere that will get this to work? I can't remember. I am screwed!
HOW TO FIX A TOTALLY BRICKED BIONIC (& HOW TO McGUYVER CHARGE A DEAD BATTERY too)
I have prepared an uber zip file that contains all you need.
Wish I had it last night! I was up until 3am, worked on this for about 6 hours, and then this finally worked. I tried everything. fastboot, one click this, sd lite, etc. none of it worked.
You will praise me.
this worked - Got my phone back!
of course, I tried every solution in the world and was profoundly frustrated for hours and ran out of battery. but this WORKED. NOTHING else did.
I also had to do the McGuyver thing with an old blackberry usb charger.
snip the end off, strip the red and black wires, insert the red to positive on your battery (battery out of the phone!) insert black to negative, THEN plug in the charger. let it go for at least 1/2 hour.
my uper zip file - UNZIP THIS file to a FOLDER on YOUR DESKTOP.
http://dl.dropbox.com/u/12759680/fastboot.zip
also Manually copy files (update893 and update901) to your SD card!!!!!
(take out the micro sd, load the files onto it using an adapter.)
1. Put phone in Fastboot mode, connect to computer [hopefully you have the drivers installed. if not, search for Motorola_End_User_Driver_Installation_5.2.0_32bit or the 64 bit if that's your operating system
whenever there is a command, I copied it and pasted it in the command window (ctrl v does not work to paste, you must right click and then paste) dont copy the friggin quotation marks
2. Open a command terminal and go to the Stock folder ("cd C:\Documents and Settings\YOUR NAME\Desktop\fastboot")
3) type these commands in the terminal window and wait for the flashing to finish before going to the next line.
----> "moto-fastboot.exe flash webtop grfs.img" (This file will be flashed in 4 parts)
----> "moto-fastboot.exe flash preinstall preinstall.img"
----> "moto-fastboot.exe flash system system.img" (This file will be flashed in 2 parts)
----> "moto-fastboot.exe reboot"
be patient. some of these steps take a while and you think nothing is happening.
then you see some action in the command prompt box.
Then reboot into stock recovery (volume up+down and power; then select recovery then volume up)
When in recovery, hit both volume up+down, then go to wipe data
then flash update893.zip
If you come upon the triangle with the exclamation point and the android man, dont freak out, hit the power button, down volume, both volume at once, and eventually you will be in recovery.
you will so do a dance.
be patient. some of these steps take a while and you think nothing is happening.
then you see some action in the command prompt box.
wait a day. then, If you're feeling adventurous, reboot into stock recovery and flash 901!
I'm no maven, but I got my phone back and then to 901.
havent rooted again but I'm waiting for the developers to catch up to 901, which I downloaded and flashed after getting the damn phone back.
No dice for me
failed at flashing Web Top Frfs.img
Load_file: could not allocate xxxx
Pass preinstall.img
Failed system.img
Writing system .... INFOPreflash Validation Failure
FAILED (remote: )
Reboot phone...
Invalid Flash mode (s) (Boot Failed)
0A.61
Battery OK
OK to Program
Transfer Mode:
USB Connected
Invalid CG Version (CG: boot)
is where I am at now
finally got these two installed
----> "moto-fastboot.exe flash preinstall preinstall.img"
----> "moto-fastboot.exe flash system system.img" (This file will be flashed in 2 parts)
----> "moto-fastboot.exe reboot"
once reboot, did wipe cache and wipe data
update 893, failed during verify data....
crap..
Ok, here is the deal. It is IMPOSSIBLE to revive your phone from the process that I did. UNDER NO CIRCUMSTANCES SHOULD YOU FLASH 5.5.901 AND THEN DO A FACTORY RESTORE OR RECOVER IN TO A CUSTOM ROM. DO NOT ATTEMPT OR YOU WILL IRREPARABLE BRICK YOUR PHONE!
htcdesirezgeorge said:
Ok, here is the deal. It is IMPOSSIBLE to revive your phone from the process that I did. UNDER NO CIRCUMSTANCES SHOULD YOU FLASH 5.5.901 AND THEN DO A FACTORY RESTORE OR RECOVER IN TO A CUSTOM ROM. DO NOT ATTEMPT OR YOU WILL IRREPARABLE BRICK YOUR PHONE!
Click to expand...
Click to collapse
What are you talking about when you say factory restore? Are you talking about doing a factory data reset?
Because many have done FDR's without a problem.
Have you tried the one click script that P3Droid and the guys at rootzwiki came up with to get everybody back on the upgrade path?
That's weird.
I returned to stock from 901 using the method in the first link I posted without a hitch.
FYI
Sent from my DROID BIONIC using xda premium
I believe the second post was the answer to your problem.. now second option is to cut a usb cable and connect the negative and positive cables to your battery and leave it for an hour or so to charge..
Sent from my DROID BIONIC using XDA App
This guy obviously doesn't want any help.
He pops in once in a while with a frantic nonsensical post and doesn't bother to read our posts that can help him.
nateohio said:
This guy obviously doesn't want any help.
He pops in once in a while with a frantic nonsensical post and doesn't bother to read our posts that can help him.
Click to expand...
Click to collapse
Oh no, I definitely wanted help BUT I was dumb and used my bionic as my sole internet connection. I have my insurance replacement now($100 down the drain). I had tried ALL of the fixes but non even remotely succeeded. What ended up happening was that I somehow made it where it would not even begin to flash files. I purchased an extended battery but yyyyyeeeeaaaaahhhhh lol, so now I have shiney new supplied for my new phone lol.
Oh wells, you win some and lose some.
Fails for me on first line
idivorceyou said:
I have prepared an uber zip file that contains all you need.
Wish I had it last night! I was up until 3am, worked on this for about 6 hours, and then this finally worked. I tried everything. fastboot, one click this, sd lite, etc. none of it worked.
You will praise me.
this worked - Got my phone back!
of course, I tried every solution in the world and was profoundly frustrated for hours and ran out of battery. but this WORKED. NOTHING else did.
I also had to do the McGuyver thing with an old blackberry usb charger.
snip the end off, strip the red and black wires, insert the red to positive on your battery (battery out of the phone!) insert black to negative, THEN plug in the charger. let it go for at least 1/2 hour.
my uper zip file - UNZIP THIS file to a FOLDER on YOUR DESKTOP.
http://dl.dropbox.com/u/12759680/fastboot.zip
also Manually copy files (update893 and update901) to your SD card!!!!!
(take out the micro sd, load the files onto it using an adapter.)
1. Put phone in Fastboot mode, connect to computer [hopefully you have the drivers installed. if not, search for Motorola_End_User_Driver_Installation_5.2.0_32bit or the 64 bit if that's your operating system
whenever there is a command, I copied it and pasted it in the command window (ctrl v does not work to paste, you must right click and then paste) dont copy the friggin quotation marks
2. Open a command terminal and go to the Stock folder ("cd C:\Documents and Settings\YOUR NAME\Desktop\fastboot")
3) type these commands in the terminal window and wait for the flashing to finish before going to the next line.
----> "moto-fastboot.exe flash webtop grfs.img" (This file will be flashed in 4 parts)
----> "moto-fastboot.exe flash preinstall preinstall.img"
----> "moto-fastboot.exe flash system system.img" (This file will be flashed in 2 parts)
----> "moto-fastboot.exe reboot"
be patient. some of these steps take a while and you think nothing is happening.
then you see some action in the command prompt box.
Then reboot into stock recovery (volume up+down and power; then select recovery then volume up)
When in recovery, hit both volume up+down, then go to wipe data
then flash update893.zip
If you come upon the triangle with the exclamation point and the android man, dont freak out, hit the power button, down volume, both volume at once, and eventually you will be in recovery.
you will so do a dance.
be patient. some of these steps take a while and you think nothing is happening.
then you see some action in the command prompt box.
wait a day. then, If you're feeling adventurous, reboot into stock recovery and flash 901!
I'm no maven, but I got my phone back and then to 901.
havent rooted again but I'm waiting for the developers to catch up to 901, which I downloaded and flashed after getting the damn phone back.
Click to expand...
Click to collapse
My phone goes strait to AP Fastboot Flash Mode (S)(Invalid CDT) at power up.
When I enter the first line of these instructions "moto-fastboot.exe flash webtop grfs.img" I get an error that states
load_file: could not allocate 1397489664 bytes
error: cannot load 'grfs.img'
Any ideas?
I love my bionic, and it has plenty of life left in it. Except for the fact that I screwed it up. Here's what happened: I had it rooted, had bootstap installed, backed up my system using the bootsrap recovery, and then tried to install a CM 10.1 zip file I found from somewhere on these forums. It gets to the load screen and then I see the blue CM wheel that NEVER stops turning (at least not within the 4 hours or so I let it run). No problem I say, I'll just reload my backup. Oh wait, you need a working system to do that. DOH!! So now, if I let it boot normally I get the perpetual CM boot screen. I've downloaded several other ROMs and tried to use the stock recovery to install them but it keeps saying "signiture not verified" or some such other nonsense which leads me to believe that's not an option. I've spent quite a bit of energy googling and going through forums on how to fix this, but all I can find are how to's with old outdated links.
If someone has a current link to whatever .xfz file I need or some other magical way to fix this, I would be indebted to you. As I said, I love this phone (it still looks and functions like new otherwise) and it seems like in it's current state I should be able to fix it somehow but I may be on my way to the Verizon store a little earlier than planned if I cant figure this out. Any takers?
Sounds very similiar to my issue.. no response to mine yet either.
Here's a link for your RSD
http://sbf.droid-developers.org/cdma_targa/VRZ_XT875_6.7.246.XT875.Verizon.en.US_CFC_01.xml.zip
Use RSD Lite to restore your phone. Google is your friend. Read & follow all instructions. I am in no way responsible for what you do to your phone.
Best of luck!
Low battery when trying to program bootloader.
Ok, I made somewhat of a noob mistake here. I read somewhere that there was an ICS ROM that could be flashed on the safe side using Bootstrap. Thing is, I couldn't remember or find the one I'd read about. Long story short, I flashed Icarus 1.8.3 on safe side using Bootstrap, which didn't work. I wiped everything there is to, including System. Big No No. Phone no likey Icarus on safe side (I know, the instructions said Safestrap 3.11 only). My question, other than buying a spare battery charger to charge the battery without the phone, can I charge it using the phone? I can boot into stock recovery, bootloader, and the screen where you select Normal Boot, Fast Flash, etc. I'll buy the charger if need be, but I'd rather not shell out the $50 or so for it if I don't have to. Thanks in advance.
:thumbup:
Edited to reflect personal unbrick success:
For those of you looking for a way to flash the SBF/FXZ file from within a Linux environment:
There's a "manual" method suggested at a different site using fastboot; unzip the zip archive (SBF file) and flash the listed/pertinent files/images individually to the device. It's still written up with windows-users in mind, but I don't see why it wouldn't work in Linux. Hope that helps someone.
Here's the jist of the commands that were involved in succesfully unbricking my Droid Bionic using the appropriate SBF file for my Android version:
Code:
fastboot flash mbm allow-mbmloader-flashing-mbm.bin
fastboot reboot-bootloader
fastboot flash mbmloader mbmloader.bin
fastboot flash mbm mbm.bin
fastboot reboot-bootloader
fastboot flash cdt.bin cdt.bin
fastboot erase cache
fastboot erase userdata
fastboot flash lbl lbl
fastboot flash ebr ebr
fastboot flash mbr mbr
fastboot flash devtree device_tree.bin
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash cdrom cdrom
fastboot flash preinstall preinstall.img
fastboot flash webtop grfs.img (skip this step if you are using a JB fxz)
fastboot flash radio radio.img
fastboot reboot
Obviously, don't forget that you have to be in fastboot mode to use the `fastboot` command (Hardware keys: VolUp +Power)
**Once again, I was lucky enough to stumble upon a posting by someone else on androidforums. Feel free to check it out at the above-mentioned link, perhaps you could adapt it to your own situation in times of despair.
Remember, that RSD file is an ICS ROM. If you already have JB on your Bionic, (most do) do not attempt flashing the ICS RSD or you will most likely "hard brick" your Bionic
Mr. HQ said:
Remember, that RSD file is an ICS ROM. If you already have JB on your Bionic, (most do) do not attempt flashing the ICS RSD or you will most likely "hard brick" your Bionic
Click to expand...
Click to collapse
Yup...they have a neatly organized list view of the SBF files, for all of the different android versions for the Droid Bionic (XT875), as well as a huge number of other devices.
Here's the section for the Bionic: http://sbf.droid-developers.org/cdma_targa/list.php
I can't exactly speak for how to solve the original problem, but for others who may search here. I use safestrap on my phones (3 between the kids and I all Bionics) and I put a newer version of Cyanogenmod on one phone just yesterday and I had the same problem. after trying a few things and still having the stuck boot, I deleted the ROM1 (this was the ROM slot I was using) slot and re-created it. Next I reinstalled CM10.1.3 and it booted. Safestrap is a great way to flash custom ROMS in my opinion I would recommend it highly!
Thanks for this one
Mr. HQ said:
Remember, that RSD file is an ICS ROM. If you already have JB on your Bionic, (most do) do not attempt flashing the ICS RSD or you will most likely "hard brick" your Bionic
Click to expand...
Click to collapse
Glad I read this post....
Xt875 hard brick
I know that this thread is pretty old and I figure I'd try it out just incase. I hard brick my droid bionic and now it does not boot up at all i tried to install a firmware and I believe it was the wrong one and now the screen is blank there's still a lot of battery life in it before it brick how can I fix this. Is this where I use the jtag or whatever it's called to unbrick. Phone does not boot up can't access ab fastbooy or recovery
SPheDaGhost said:
I know that this thread is pretty old and I figure I'd try it out just incase. I hard brick my droid bionic and now it does not boot up at all i tried to install a firmware and I believe it was the wrong one and now the screen is blank there's still a lot of battery life in it before it brick how can I fix this. Is this where I use the jtag or whatever it's called to unbrick. Phone does not boot up can't access ab fastbooy or recovery[/
are you sure your battery is good? you need to externally charge your bat, sometimes when phone is not functioning properly the bat will rapidly discharge, i dont know how clever you are but you can cut the end off an old charger and achieve a recharge by cleverly connecting the cut off leads to the bat
Click to expand...
Click to collapse
Have a external battery charger
hugh a said:
SPheDaGhost said:
I know that this thread is pretty old and I figure I'd try it out just incase. I hard brick my droid bionic and now it does not boot up at all i tried to install a firmware and I believe it was the wrong one and now the screen is blank there's still a lot of battery life in it before it brick how can I fix this. Is this where I use the jtag or whatever it's called to unbrick. Phone does not boot up can't access ab fastbooy or recovery[/
are you sure your battery is good? you need to externally charge your bat, sometimes when phone is not functioning properly the bat will rapidly discharge, i dont know how clever you are but you can cut the end off an old charger and achieve a recharge by cleverly connecting the cut off leads to the bat
Click to expand...
Click to collapse
I have a external batter charger (see attachment) already, although I do know how to make one myself. It was less time consuming to go to the store and buy one. Plus it was only 5 bucks which isn't that bad. This external battery charger also displays the percent of battery life remaining. But I'll do what you suggest and see if that works out. Another strange thing is that if I plug the usb cord without the battery the charging (white) light comes on, which before it never did.
I know that the bionic droid xt875 uses the targa firmwares. I crashed my device flashing the spyder given to me by a source here on this forum. I was trying use my bionic with a gsm network so I follow this other guide. before I had followed this guide I had run through the proper proceedures of edit build.prop and radiocomm nv edit...etc.etc.. I was only managing to get no service on the HWB so I found an article pertaining to my particular model and tried it and subsequently it failed and now I'm stuck with a nice little paper weight.
Any other suggestions with this matter would be greatly appreciated. I'll keep you posted if the conditions changes.
Click to expand...
Click to collapse
Hello.
I have a Kindle Fire HD that will power on. When plugged into the wall or the pc the logo flashes up for about 5 secs before the device switches back off. I have tried to reset it by holding down the power for 20 secs releasing and pressing it again, but nothing. Any help with this matter would be great!!!
Thank you.
You tried a fastboot cable? And are you sure the battery isn't dead?
Sent from my LG-P769 using Tapatalk
Thanks for the reply.
It's not the battery no. I do not have a fastboot cable I will get one and try.
Cheers.
I got the fastboot cable now when it's plugged in with the new cable to the computer it comes on with "fastboot" on the screen, about 6 seconds later it powers off again.
mrshizz said:
I got the fastboot cable now when it's plugged in with the new cable to the computer it comes on with "fastboot" on the screen, about 6 seconds later it powers off again.
Click to expand...
Click to collapse
leave it plugged into a charger for a bit, don't remember if it will charge off a fastboot cable or not but this is good news so far, its been sitting long enough i could see the battery being deadish so if you can get it to stay in fastboot longer you can restore it back to stock and get it running again.
Left it to charge all night, I can get SR Tool to start but it still powers off after a few secs. I have tried a different battery with the same result. I have also noticed there is no indication that it charges (Not sure if there should be one)
Well this sounds a bit more familiar now, I could throw a guess and say the bootimg is corrupt. You may be able too fix this though I advise using Ubuntu to do it because of the lack of driver issues and a better response time. If you run something like
Code:
fastboot -I 0x1949 flash boot boot.img
with the kindle unplugged, and plug in the fastboot cable when it says waiting for device, then it should attempt to flash the boot image again, and even if it fails it might give a better result, because I have seen what happens if a bad kernel flash happens before, usually it will kick the device straight into fastboot mode, so in your case it could be beneficial neither way possibly.
Sent from my Amazon Tate using Tapatalk
I have managed to flash the bootloader with the above method but still the problem persists. Thanks for the help with this matter, it is very much appreciated.
Interesting, that wasn't the bootloader though, that was more like the kernel +intramfs. If you want to give a shot at reflashing the bootloader you can download the one used in hashcode's 2nd bootloader process you use for downgrading. Just remember to verify it's md5sum or your kindle could brick even worse to the point soldering would be involved to fix it. Just flash it using the command he mentions in the tutorial.
Sent from my Amazon Tate using Tapatalk
ragigi and
Done as above, Still the same problem.
It said on both occasions that it successfully flashed correct?
Sent from my LG-P769 using Tapatalk
Yeah, It say's it flashed fine, On both occasions. Thanks.
That is odd then. Its not following standard fixing procedures... I have no guesses as to why it would still do that after successfully flashing the bootloader and the boot image. You might have to wait for someone with more experience to help. Or ask around in the freenode irc channel, hashcode may know more about what's up but someone else here might have an idea as well. I can't think of any other partitions that should cause this issue. In don't believe the boot0block being corrupt could do this, there are a few others I don't know what do but I don't think they should be responsible either but Idk. Sorry I can't be of much more help.
Sent from my Amazon Tate using Tapatalk
Cheers for all the help, Sold it on eBay now so will use that cash to buy another, less time consuming.