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
Related
I will donate to the individual that unbricks my bionic...Plz a lil desperate!!
Hmm.. Maybe some more info. What were you doing when you bricked it? Any of the leaked updates installed?
djr4x4 said:
Hmm.. Maybe some more info. What were you doing when you bricked it? Any of the leaked updates installed?
Click to expand...
Click to collapse
i was back on 886 with updated kernel and radio. wanted to flash the ota but kept failing due to kernel. tried flashing the ota in stock recovery then in cwm to no avail. decided to format somethings in advanced just to see if it would help flash ota but no. after that i rebooted and bam! bricked. thing is i have been in this situatuation before and nothing would restore me except released and 4ever root but now nothing works. no phone going on 24 hours now...
Did the same thing. Used this method. if you can get to the fast boot by holding power and vol down (or power and volume up and down, then selecting fast boot) it will work
http://www.addictivetips.com/mobile/unbrick-motorola-droid-bionic-with-rsd-lite-5-5-guide/
netslum said:
Did the same thing. Used this method. if you can get to the fast boot by holding power and vol down (or power and volume up and down, then selecting fast boot) it will work
http://www.addictivetips.com/mobile/unbrick-motorola-droid-bionic-with-rsd-lite-5-5-guide/
Click to expand...
Click to collapse
rsd didnt work for me ever...i want to try it again but it says that the file is not supported...
got it but still a no go. it fails everytime right away
Is there anyway to flash the fxz file without rsd??maybe fastboot??but it needs to be in IMG format right? anybody?
You can flash individual files from that pacjage in fastboot. Try this.
Fastboot flash /system system.img
Make sure those files are in same folder as fastboot, you have the right drivers and ur in fastboot mode on phone. Do this for every file it will let u. keep ur money tho if this works im not on this forim to get paid. Worse comes to worse pm me a phone number and ill step u thru it over phone.
Sent from my DROID BIONIC using XDA App
Here's some general tips for making RSD Lite work for you. RSD Lite is the only tool that knows how to manipulate FXZ files, as it's Motorola's proprietary file format.
(1) All the files you should need (Either RSD Lite or Fastboot) will come from here: http://briefmobile.com/droid-bionic-receives-fastboot-recovery-files
(2) Running the 32-bit version of the Motorola drivers is recommended. RSD Lite is a native 32-bit app and has a better chance of playing nice if 32-bit Motorola drivers are installed.
(3) When running RSD Lite on Windows Vista or Windows 7, it is also recommended that when you open it that you right-click and choose "Run As Administrator".
(4) After installing the drivers and RSD Lite, reboot and then plug in your Bionic AFTER opening RSD Lite.
From there, you make sure that you start your Bionic in bootloader (aka fastboot) mode and then RSD Lite shouldn't have a problem detecting the device so you can flash in the FXZ file. The best version to use in your situation is the full one that's 685MB.
This is what you need. I personally don't use rsdlite.
http://forum.xda-developers.com/showthread.php?t=1279825
You will boot your phone into fastboot mode then flash it using this utility. Option 1 is what you need to use.
You can also try this: http://droidmodderx.com/bionic/too-easy-unbrick-bionic-with-oneclick-fastboot-restore/
Sent from my DROID BIONIC using Tapatalk
Remember to hit the "Thanks" button when someone helps you!
Terri M said:
You can also try this: http://droidmodderx.com/bionic/too-easy-unbrick-bionic-with-oneclick-fastboot-restore/
Sent from my DROID BIONIC using Tapatalk
Remember to hit the "Thanks" button when someone helps you!
Click to expand...
Click to collapse
i have tried all of those and still no luck. all i can think of is to flash the whole fxz file in fastboot. but it needs to be in .IMG format.
follow the steps in the first post of this thread. should get you back going.
http://www.mydroidworld.com/forums/droid-bionic-forum/9800-how-get-your-phone-back-upgrade-path.html
rgb2448 said:
follow the steps in the first post of this thread. should get you back going.
http://www.mydroidworld.com/forums/droid-bionic-forum/9800-how-get-your-phone-back-upgrade-path.html
Click to expand...
Click to collapse
did this multiple times but heck ill try it again...
brandonaspencer said:
did this multiple times but heck ill try it again...
Click to expand...
Click to collapse
Can you get in fastboot mode? Does it say flash failed? What did you format?
i tried to flash the ota. no go. formatted webtop. stuck in ap mode. says flash failure. at the bottom says invalid sp data and invalid cg webtop. wont flash anything...
You need to use the moto-fastboot.exe and flash the stock webtop partition back to your phone. That is a hacked version of fastboot that supports larger than 256MB partition sizes and will restore your webtop so the phone can boot.
You finally gave enough information about what you actually deleted/formatted and the exact error was so that you could be helped...congrats!
Hint: "moto-fastboot flash webtop grfs.img" from a directory that contains the moto-fastboot.exe and the 2 required .dll files and the grfs.img from the original FXZ.
cellzealot said:
You need to use the moto-fastboot.exe and flash the stock webtop partition back to your phone. That is a hacked version of fastboot that supports larger than 256MB partition sizes and will restore your webtop so the phone can boot.
You finally gave enough information about what you actually deleted/formatted and the exact error was so that you could be helped...congrats!
Hint: "moto-fastboot flash webtop grfs.img" from a directory that contains the moto-fastboot.exe and the 2 required .dll files and the grfs.img from the original FXZ.
Click to expand...
Click to collapse
THank you!
http://dl.dropbox.com/u/7632904/moto-fastboot-win32.zip
That is the moto-fastboot.exe and dll files you need.
I already gave you the syntax to use it above and you already have the FXZ so just put them all together in a folder with the grfs.img and navigate to that folder from command prompt once the phone is booted in fastboot mode and use the command above.
It will proceed to flash the grfs.img in 5 256MB chunks and a 6th smaller chunk and then use moto-fastboot reboot and it should boot normally if you haven't messed up anything else in the meantime.
Good luck!
cellzealot said:
http://dl.dropbox.com/u/7632904/moto-fastboot-win32.zip
That is the moto-fastboot.exe and dll files you need.
I already gave you the syntax to use it above and you already have the FXZ so just put them all together in a folder with the grfs.img and navigate to that folder from command prompt once the phone is booted in fastboot mode and use the command above.
It will proceed to flash the grfs.img in 5 256MB chunks and a 6th smaller chunk and then use moto-fastboot reboot and it should boot normally if you haven't messed up anything else in the meantime.
Good luck!
Click to expand...
Click to collapse
Sir you are a genuis and a scholar! you know there are two different fastboot recoveries?? I needed exactly what you said, so where can I send you the $25?
brandonaspencer said:
Sir you are a genuis and a scholar! you know there are two different fastboot recoveries?? I needed exactly what you said, so where can I send you the $25?
Click to expand...
Click to collapse
Keep it! Learn how to ask better questions with more complete information and tell everyone else to do likewise and you will save us all far more valuable time and effort...seriously.
Happy holidays!
Oh and also share the knowledge you get with others and use the thanks button...it's what this forum is for.
Thanks for the offer, but I'd really rather you just did as I suggested and enjoy your phone and learn to understand it better.
Win, win!
I slept in late or I would have answered, but Cellzealot definitely explained it well.
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?
Bricked my droid bionic about a day ago, and have been looking across the web to find a fix. Here is the current information I have on it:
- Low battery
- Boot mode selection menu 0a.53 (assuming stock recovery)
- Stock recovery options with 'apply update from sd, wipe data/factory reset, and wipe cache partition
- apply update with just about any zip returns 'E: Signature verification failed', including the ROM previously used.
- Able to enter BP sbf flash mode, but decide cannot communicate (maybe cable)
- Able to enter ap fastboot mode, and usb transfer mode is obtainable. Before battery was on low, could program. Now get 'cannot program'.
- In ap fastboot mode, with usb transfer mode active, PC unable to communicate. Attempted with apk, apktoolkit, and RSDlite
- Have backups made by clockwork recovery of the whole device
- Have copy of ROM zip used for previously running android instance.
- XT875 model
Willing to do just about anything to unbrick this phone. I love the phone, and I don't want to replace it. Unfortunately, my job requires me to be in constant communication so I've a need to fix it ASAP.
Edit:
Tried flashing multiple stock ROMs and other things from stock recovery with little luck, most returning invalid signature
Use an exact Moto cable. No substitutes! Check PC drivers or Moto Device Manager.
Sent from my GT-P3110 using Tapatalk
unbrick
zaros104 said:
Bricked my droid bionic about a day ago, and have been looking across the web to find a fix. Here is the current information I have on it:
- Low battery
- Boot mode selection menu 0a.53 (assuming stock recovery)
- Stock recovery options with 'apply update from sd, wipe data/factory reset, and wipe cache partition
- apply update with just about any zip returns 'E: Signature verification failed', including the ROM previously used.
- Able to enter BP sbf flash mode, but decide cannot communicate (maybe cable)
- Able to enter ap fastboot mode, and usb transfer mode is obtainable. Before battery was on low, could program. Now get 'cannot program'.
- In ap fastboot mode, with usb transfer mode active, PC unable to communicate. Attempted with apk, apktoolkit, and RSDlite
- Have backups made by clockwork recovery of the whole device
- Have copy of ROM zip used for previously running android instance.
- XT875 model
Willing to do just about anything to unbrick this phone. I love the phone, and I don't want to replace it. Unfortunately, my job requires me to be in constant communication so I've a need to fix it ASAP.
Edit:
Tried flashing multiple stock ROMs and other things from stock recovery with little luck, most returning invalid signature
Click to expand...
Click to collapse
You are going to need rsd lite on your PC. The fxz files for your current build. A Motorola brand USB cord. And the latest Motorola drivers.
---------- Post added at 05:02 PM ---------- Previous post was at 04:43 PM ----------
http://forum.xda-developers.com/showthread.php?t=2728352
See post #7 for the fxz build you will need to use.
Did fxz work for you?
Unbricking
I ran into same problem before, with Motorola it's a pain to do anything especially charging the batteries on it once it's been brick. If you search around this forum you can find a little article about a guy tweaking his ps3 controller to charger his battery. I wouldn't recommend doing this if you don't know what you're doing. But what I did was buy this little device that charges any phone battery I'm not sure if I can link a photo but i'll try it, not i'll give a name. In order to RSD and use ab fastboot mode on the xt875 you'll need at least 70-80 percent battery life, at least that's what the guys here on the forum recommend. But I've been able to unbrick my device only 40 percent battery life. Now once that battery is charge to a reasonable charge. You'll have to download the cdma targa file for your phone. I don't think anyone matters as long as it's the exact same or newer of your phone's original firmware. Extract the targa file and then run RSD lite click the ... button to open file and locate your extracted cfc file. Now you may run into some flashing issues with failure in step 5/10 and if you don't, don't worry about it. but if you do you'll have to open up the cfc file with wordpad and remove a few lines from. here are the lines that need to be removed; <step operation="oem" var="fb_mode_set" /> AND <step operation="oem" var="fb_mode_clear" />....there's another fail that happens but I haven't found anyone that had experience this problem. it seem like I was the only one that experience it. it has to do with something with the fail flash.bin or something I'm not sure. But I left a comment about this fix on this forum somewhere if you care to search for it. once you edit and remove those above mention lines save and run it again and it should operate flawlessly. I have also left a link down there for the edit cfc file and pictures of the device I was referring to about charging your batteries directly.
also you mention that it could be a cable thing. I read a lot of this but I've use the cable wires from my Samsung without any mishaps besides the above mention issues with 5/10 but this was a common problem that even thoses with a Motorola cable had faced. from what I know theses wires are exactly they're usb 2.0 wires and couldn't differ from each other that much. but it is probably better to use the exact cable than a non exact one. the reason it won't communicate is the battery is low as I have mention you'll have to charge this battery of yours to a decent 40 and up for it to run cause the process of re flashing can take anywhere 10-15 minutes and you don't want it to die in the middle of flashing your firmware. cause this I believe can lead to a hardbrick. the stock verification recovery will always have that return that value even from stock roms. Therefore it is recommend to use the RSD lite so you won't face that problem. I hope this helps.
Bricked
I thought my phone was history. The solution was using an actual Motorola USB cable. It made all the difference.
Maybe you installed an incorrect driver.
I'll start out by saying I was careless and had not read various threads before flashing things and causing my issues. I've already bought a replacement phone but I'd like to see if there's any chance to revive the Moto X or not.
What happened:
I had unlocked the bootloader years ago. I was running the (mostly) stock Lollipop 5.1 with XPosed, and got noticed of a security update.
After fully charging the battery, I flashed stock recovery over my custom recovery (TWRP) and then, without thinking, got the latest image from Motorola without realizing it was a 4.4.4 image.
I flashed the system partition using this image thinking it would remove SU and that I could install the update - this soft-bricked the phone when I tried to boot.
Too late, but at this point I re-flashed TWRP and ran a backup. I used adb to extract the backup and my other files from the /sdcard partition.
Factory Reset. The phone boot up at this point.
I tried flashing the logo, gpt.bin (I forgot that Lollipop changed how partitioning worked) and then did another Factory Reset. Phone boots fine.
I then tried restoring the data from my nandroid backup. Rebooted once, and phone seemed to start. And then it went black.
At this point, the phone does not appear to boot at all. I can't use Vol Down + Power to boot into Fastboot, and if I connect to a computer, it does not see the device... USUALLY.
If I connect via USB to my Windows computer, and try to boot into Fastboot, the green LED behind the volume will flash once and my computer will signal the "Hardware connected" sound. I can try to run 'adb reboot bootloader' but adb reports that it doesn't see any devices. My system events note a USB Input Device was added but don't get any further. Within 5 seconds, the "hardware disconnected" sound fires. About 20 seconds later, this will repeat on its own.
I just tried making a fastboot cable from a spare micro usb cable... I may have done it wrong - but it does not seem to have had any effect. The result is the same. It's possible I didn't solder the connection well, though (it was difficult exposing the terminals on my particular cable).
The screen is always black and never lights up in any way.
It kind of makes me think that the device is attempting to boot, fails, and cycles. Is there anything I can do?
At this point I am able to get into fastboot after bricking my XT1060DEV in a similar way. Follow the guide as best as you can in this post. Toward the end of that thread you can see the sequence of events that led me to at least fastboot mode.
Awaiting a response from someone who might know which gpt.bin and bootloader I can flash to have more than a blank phone. I'll try to keep you updated.
EDIT:
You might find it easiest to get QHUSB set up using this guide. This guide has been superseded by the previously posted one, but some people still report success following it.
PiArc said:
At this point I am able to get into fastboot after bricking my XT1060DEV in a similar way. Follow the guide as best as you can in this post. Toward the end of that thread you can see the sequence of events that led me to at least fastboot mode.
Awaiting a response from someone who might know which gpt.bin and bootloader I can flash to have more than a blank phone. I'll try to keep you updated.
EDIT:
You might find it easiest to get QHUSB set up using this guide. This guide has been superseded by the previously posted one, but some people still report success following it.
Click to expand...
Click to collapse
I may not have a chance for a few days, but I will try this. I did try to download the software on the second link you provided and some of the links on that page were broken.
I'm not going to lie, navigating those threads is harsh.
Towards the end of the first linked thread you can see a post with what ended up getting me into fastboot. It might be a decent little roadmap to guide you in the right direction (plus, I think the files I indicate in that particular post are all still up).
Keep us updated!
ohioDroid said:
I'll start out by saying I was careless and had not read various threads before flashing things and causing my issues. I've already bought a replacement phone but I'd like to see if there's any chance to revive the Moto X or not.
What happened:
I had unlocked the bootloader years ago. I was running the (mostly) stock Lollipop 5.1 with XPosed, and got noticed of a security update.
After fully charging the battery, I flashed stock recovery over my custom recovery (TWRP) and then, without thinking, got the latest image from Motorola without realizing it was a 4.4.4 image.
I flashed the system partition using this image thinking it would remove SU and that I could install the update - this soft-bricked the phone when I tried to boot.
Too late, but at this point I re-flashed TWRP and ran a backup. I used adb to extract the backup and my other files from the /sdcard partition.
Factory Reset. The phone boot up at this point.
I tried flashing the logo, gpt.bin (I forgot that Lollipop changed how partitioning worked) and then did another Factory Reset. Phone boots fine.
I then tried restoring the data from my nandroid backup. Rebooted once, and phone seemed to start. And then it went black.
At this point, the phone does not appear to boot at all. I can't use Vol Down + Power to boot into Fastboot, and if I connect to a computer, it does not see the device... USUALLY.
If I connect via USB to my Windows computer, and try to boot into Fastboot, the green LED behind the volume will flash once and my computer will signal the "Hardware connected" sound. I can try to run 'adb reboot bootloader' but adb reports that it doesn't see any devices. My system events note a USB Input Device was added but don't get any further. Within 5 seconds, the "hardware disconnected" sound fires. About 20 seconds later, this will repeat on its own.
I just tried making a fastboot cable from a spare micro usb cable... I may have done it wrong - but it does not seem to have had any effect. The result is the same. It's possible I didn't solder the connection well, though (it was difficult exposing the terminals on my particular cable).
The screen is always black and never lights up in any way.
It kind of makes me think that the device is attempting to boot, fails, and cycles. Is there anything I can do?
Click to expand...
Click to collapse
Try reflashing twrp via fastboot, install custom ROM -OR- download latest XML for your variant flash via rsd lite or manual flash.
Note: When using the XML you will lose everything, including data on internal storage.
Hopefully this helps ?
Also, if your phone stays black it's likely the battery is dead. Leave it hook up for awhile or keep trying to boot into fastboot(while plugged into outlet, not PC) and leave it for a couple of hours, should charge.
I'm speaking from personal experience, just without having Xposed framework, lol.
Sent from my Moto X using Tapatalk
Urbane powers off when not in cradle whenever I flash anything other than a stock img, with the exception of twrp. I can stay in TWRP and Bootloader without it being charged, and it works properly when it's on stock firmware, but if I flash a different boot.img, or a custom ROM, it shuts off whenever its not in the cradle. I know this forum is pretty much dead, but i hope hope HOPE someone can help me out here.
I hate to add to a list without contributing, but I'm having the same problem. How are you getting back to stock? I've tried flashing stock boot.img, recovery.img and system.img, still no luck. Clearly you didn't get an answer on here, but did you ever find an answer?
This was happening to me too. It was working for so long. Not sure what made it stop working.
I had the 4 cores boot img installed and it was working great till it wouldn't stay on for some reason. It was working for well over 6 months with no issues.
If the battery is the problem for you, this fix won't work. To know if this fix "COULD" work for you, jump straight to the second step, and take your watch off the cradle. Does the watch stay powered on while in fastboot mode? If yes, this fix "SHOULD" work, if not, you probably need to replace the battery.
Anyway, the following steps is what I did to get the watch working again, without it turning off out of the cradle:
These steps are assuming you have adb installed on your computer and know how to use it. If not, Google is your friend.
Went to this post and downloaded the images that were provided
Booted into the bootloader
If you can't get to the bootloader via adb, you can get to it with this method
Code:
fastboot flash boot boot.img
Code:
fastboot flash recovery recovery.img
Code:
fastboot flash system system.img
reboot to bootloader (even though you're still in bootloader)
Code:
fastboot oem lock
reboot to system
If you have a charge on the battery you should be able to take the watch off the cradle and it should be working now without powering off.
Hope this helps, and if it has please click the thanks!
xX5UN5H1N3Xx said:
I hate to add to a list without contributing, but I'm having the same problem. How are you getting back to stock? I've tried flashing stock boot.img, recovery.img and system.img, still no luck. Clearly you didn't get an answer on here, but did you ever find an answer?
Click to expand...
Click to collapse
I had this issue tried everything, ordered one battery from ebay, same result, then ordered from another site an original (more expensive) urbane battery and it worked
Check this link:
https://forum.xda-developers.com/g-w...tdown-t3729960
This fixed my phone with a similar issue.