I have a Bionic that's stuck on the red Motorola/dual-core logo. If I turn the phone on normally, it displays the logo and the soft keys light up after a few seconds, but nothing else happens. I've tried flashing both .893 and .902 to no avail, as both successfully flash but then dump me back to the boot screen. I'm also unable to get to recovery as the recovery option from the pre-boot menu also leaves me hanging at the Motorola logo.
Any ideas?
UPDATE: Have tried flashing using both RSD Lite and the fastboot command through the terminal on Mac OS X, no dice.
How long have you waited? First boot after FXZ can take several minutes....
Sent from my rooted BIONIC running ICS 6.7.235 via Tapatalk 2
johnlgalt said:
How long have you waited? First boot after FXZ can take several minutes....
Sent from my rooted BIONIC running ICS 6.7.235 via Tapatalk 2
Click to expand...
Click to collapse
I'll try it again, but I waited a little under 10 minutes last time.
Sounds possibly bricked. Be careful not to drain your battery so don't leave out on too long because you can't fxz with a low battery.
Were you doing something that might have caused this?
Sent from my DROID BIONIC using xda app-developers app
I would download the newly released 905 FXZ and flash it, unmodified. Don't try to save your data or your internal memory. Just run the full FXZ.
rue225 said:
Sounds possibly bricked. Be careful not to drain your battery so don't leave out on too long because you can't fxz with a low battery.
Were you doing something that might have caused this?
Sent from my DROID BIONIC using xda app-developers app
Click to expand...
Click to collapse
It's actually my friend's—it bricked itself during an OTA (not sure which) and he gave it to me to try and fix as he managed to get a replacement without them asking for an exchange. And about the battery, I have a handy universal charger so I'm not worried
SonicJoe said:
I would download the newly released 905 FXZ and flash it, unmodified. Don't try to save your data or your internal memory. Just run the full FXZ.
Click to expand...
Click to collapse
Will do, thanks.
Alright, flashed the 905 FXZ (stock, no changes) and it's been stuck at the Motorola logo for about 15 minutes now. Slight progress, though, as now when I plug the phone in the computer recognizes a bunch of USB devices (USB Composite Device, Motorola LTE BP Modem, Motorola QC BP Modem, Motorola USB Modem, Motorola USB Networking Driver, and Motorola QC Diag Port).
Any suggestions?
Try a windows machine. Maybe it would end up different. Ive fxz'd my bionic 15 times or so. Never had boot after fxz take more than 5 min. Also make sure youre using a motorola cable. Mac, im clueless, really, but i imagine as long as you have the latest motorola drivers and the newest version of rsd lite, it would work no sweat. I just dont know if the fxz file would be different, but id imAgine not
Sent from my DROID BIONIC using xda premium
In fact if you need a fxz that is 100% for sure,
http://db.tt/kNuGZ8Od . I have used this same one every time with zero glitches or hiccups. Its .902 with no mods so it wipes internal too.
Sent from my DROID BIONIC using xda premium
kitcostantino said:
In fact if you need a fxz that is 100% for sure,
http://db.tt/kNuGZ8Od . I have used this same one every time with zero glitches or hiccups. Its .902 with no mods so it wipes internal too.
Sent from my DROID BIONIC using xda premium
Click to expand...
Click to collapse
I've been using Windows (dual booting), along with that same FXZ and nothing seems to be working. I also tried the newly released 905, same result. Think it's a hard brick?
I dont know. Do you have the newer (red m, not black m) version of rsd lite? Are ya using the Motorola drivers and the moto device helper? http://db.tt/yR5ZCAqa i have both installed on my phone tweaking windows xp sp3 machine.
Me personally, i dont want to believe in hard bricking, but maybe its possible.
kitcostantino said:
I dont know. Do you have the newer (red m, not black m) version of rsd lite? Are ya using the Motorola drivers and the moto device helper? http://db.tt/yR5ZCAqa i have both installed on my phone tweaking windows xp sp3 machine.
Me personally, i dont want to believe in hard bricking, but maybe its possible.
Click to expand...
Click to collapse
I do have the newest version of RSD Lite. I've got the Moto drivers, but no device helper (which I'll try next).
Can you find out from your friend...what OTA he was flashing and what exactly happened? And if he had safestrap installed? With some more information, you may be able to recover. Honestly though...you have done pretty much everything to try and recover.
possiable fix
eye__dea said:
Can you find out from your friend...what OTA he was flashing and what exactly happened? And if he had safestrap installed? With some more information, you may be able to recover. Honestly though...you have done pretty much everything to try and recover.
Click to expand...
Click to collapse
I have had my droid bionic for almost a year i bought it bricked on the Droid logo would not boot past that, its been a year and i havent been able to fix this phone i have repaired 9 phones for personal use in the mean time. long story short after a year of fxz flashing driver updates house of moto using i figured out that if i flash the phone with cdma_targa_9.8.2O-72_VZzW-22_cfc.xml then factory reset in recovery it will boot to droid logo, this is where it gets weird it will sit here all night but if i pull my sd card it will almost immediately go to the red eye then boot. hope this helps :]
Boot it WITHOUT the sd Card? You can't RSD the JellyBean firmware if it was previously on the ICS firmware unless ICS firmware is "clean/virgin" (i.e. unmodified).
You may need to go all the way back to Gingerbread or ICS. I'd try House of Bionic's ICS flashing procedure.
Related
I have a bionic that i system updated to 5.9.902 a couple days after i got it. Then i made the mistake of coming here and messing up my phone because i have no idea what I'm doing
I installed safestrap and did the whole noob step by step guide. Installed eclipse and a couple other roms. For some reason i wiped my internal and external storage. I have no backups of anything.
I've tried releasedroot, petes, rds lite with the 902 xml. I got stuck all the time with what seemed to be a driver issue.
I just want to return this thing to stock and stop messing with it
As of now when I press power i go straight to ap fast boot flash failure screen. I press power to power off and hold vol up and down to boot into recovery but just pick the normal boot option. Phone then boots into what seems to be my stock 902. I dont know if im rooted anymore.
If i could rid my phone of this flash failure and safestrap, i would be stupid happy
Anyone out there willing to help a total noob? If any more info is needed I'd be happy to provide
Sent from my DROID BIONIC using XDA
What error did you receive using rsdlite?
When you go into your phone settings..can you verify your on 902?
I'm at work now but it was some sort of usb failure. It got stuck on 1/22 mbm something.
Yes as of right now im on 902.
Is there a tutorial on how to completely remove usb drivers? Even though rsdlite says I'm connected, I don't see my phone drivers in device manager. That's where I think I'm going wrong but not really sure.
Sent from my DROID BIONIC using XDA
Cool. I'm at work too. When would you be available?
About 5pm est ... thanks alot dude
Sent from my DROID BIONIC using XDA
Send me a PM when your available.
I tried to pm you but xda force closed. I replied to, i believe, your hotmail
Sent from my DROID BIONIC using XDA
No matter what I try I cannot get past this screen.
//merickk.smugmug.com/Other/Misc/Miscellaneous-Stuff-1/i-P8ZBVg4/0/L/0626120050-L.jpg
I've even tried to moto-flash the mbm and cdt files from a downloaded leak file and no luck there either.
Formatting the internal memory after FXZing back to 902 and installing the leak on a fresh formatted SD card with only the leak file on it after OTAing to 905 doesn't work either. I've tried 6 or 7 2233 files, and a couple 2231 files as well as a couple different 902 FXZ files.
ICS is there somewhere otherwise I don't think it'd get that far into the boot process and charge the battery.
When I do a battery pull and try to reboot, it just sits at the Droid screen.
Pulling the battery while plugged in takes me to the Dual Core screen where it sits.
When sitting at the starting applications screen I am able to get tactile feedback when pressing and holding the home key but after sitting for an hour or so there is no feedback from the home key. No response from any of the other keys. The keys are also lit up.
This has happened every time with every leak file I've flashed the exact same way.
Does anyone have any suggestions?
Quite a conundrum... Maybe you should wait for the OTA to come out, let it brick your phone, then take it to Verizon and demand to trade it in for a phone with good battery life and no data drops? lol. If I were in your shoes and it looked like the ICS update was gonna make my phone eligible for a warranty replacement, I'd use that as an opportunity to let Verizon spring for a new device. Just sayin'.
My guess is you either currently have or have had CWM recovery installed. If so.... uninstall safestrap/bootstrap, then use root explorer go to/system/bin and delete 2 files... "hijack" and "logwrapper", then change the name of "logwrapper.bin" to just "logwrapper" once you have done that, reboot into stock recovery and try again!
Thats the only thing i can think of, i know the above will solve the problem of getting the error when attempting to flash. Sounds like yours flashed but just wont finish booting.
Sent from my DROID BIONIC using xda app-developers app
XperianceIT said:
My guess is you either currently have or have had CWM recovery installed. If so.... uninstall safestrap/bootstrap, then use root explorer go to/system/bin and delete 2 files... "hijack" and "logwrapper", then change the name of "logwrapper.bin" to just "logwrapper" once you have done that, reboot into stock recovery and try again!
Thats the only thing i can think of, i know the above will solve the problem of getting the error when attempting to flash. Sounds like yours flashed but just wont finish booting.
Sent from my DROID BIONIC using xda app-developers app
Click to expand...
Click to collapse
i have the same problem , did this work for the OP?
So I tried to flash the 229 while still on 2233 but of course it didn't work. I then tried to flash the 902 using the pathsaver and and stuck in bootloop. I can access recovery though and other flashing tools. All I have access to is my laptop running Ubuntu because I'm 1000 miles from home. Any help here?
Your best bet is going to be flashing back to 902 using your cmd prompt and flashing each item one by one. I had to do that while i was out training in the middle of nowhere. It takes a little longer, but works. There also use to be a tool for linux/mac sort of like rsd but all the links i found when i was training were dead links, hence why i flashed each item seperatly.
Sent from my DROID BIONIC using xda app-developers app
I feel like an idiot because just last year I was manually flashing other peoples Bionics, but I don't remember how to do it. Do you know of any walkthroughs?
darkstarsinner said:
I feel like an idiot because just last year I was manually flashing other peoples Bionics, but I don't remember how to do it. Do you know of any walkthroughs?
Click to expand...
Click to collapse
here's a link you can try
http://www.droidhive.com/forums/index.php?/topic/87-902-bionic-pathsaver-for-windowslinuxmac/
i usually use windows but this link have linux/mac version too
good luck
Those are both great links, thats where i found most of my info for recovering mine when i bricked it. I lost everything on mine. I only had fastboot... lol. I ended up actually taking a little info from multiple topics then pieced it all together and managed to accomplish what i needed. There wasnt any specific topic that worked 100% for me, not to mention all the dead links i ran into for almost everything i needed to do it within linux/OSX/Mac
sent from my DROID BIONIC via XDA App
I appreciate that but the link to the files are dead. Somebody needs to make a new legal hosting site lol. As a side note, I pulled the SD card and put a couple of update files on it then booted into recovery. From here I was able to flash both updates with zero issues, however the bootloop still remains. WTH??
I fixed it. I pulled the SD card and put both the 905 and 229 update on it. I then placed it back into the phone, booted recovery and flashed both updates (flashed 905 rebooted still bootloop, then flashed 229 rebooted). My Bionic is currently booting up now. Made it past the Dual Core screen fairly quickly too!
Let us know if it finished loading and if your good to go. If not i can see what i can do about uploading the files i used if i still have them. I know i do on my mac but that is in a connex on its way to me from fort irwin at the moment, but i think i saved most of them on my tablet too.
sent from my DROID BIONIC via XDA App
I'm good now bud. Up and running ics leak 229 flawlessly. But thank you for attempting to help!
Sent from my DROID BIONIC using Xparent Red Tapatalk 2
No problem, glad you got it resolved.
sent from my DROID BIONIC via XDA App
I need to brick my phone for a warranty claim. I was running the .206 ICS leak on my phone, but started having bad connection issues and the power button on top kept getting stuck. I called verizon to get a warranty replacement for my phone, and told them it stayed at the red eye during bootup. I tried to fastboot to GB since I heard that will brick it, but it fails at step 6/18 flash cdt.bin
any suggestions?
Use Droid 4 utility. I would have just told them it gets stuck on the dual core screen. I don't think they will care much though...
Sent from my XT894 running ICS
danifunker said:
Use Droid 4 utility. I would have just told them it gets stuck on the dual core screen. I don't think they will care much though...
Sent from my XT894 running ICS
Click to expand...
Click to collapse
that worked, thanks!
Running a completely stock VZW Moto X on the latest update (4.4.2). Woke up this morning to a half dozen or so app updates, including Active Display and Moto Help. I updated these two, and then an update for Beautiful Widgets started after. My phone then locked up and restarted. Now, it loads through the boot screen and then loads the Verizon screen, then the device goes black. I've tried wiping cache, to no avail. Any suggestions? I've installed the Moto X drivers via the Moto site, but the device isn't being recognized via ADB. I would really really really like to retrieve my files from the phone before doing a full factory reset...
Haven't seen anyone else report this....
Sent from my XT1060 using Tapatalk
Same symptoms on unlocked dev edition
I can't for sure tie it to an update, but the only thing that I did on my Moto X today was enable Motorola Connect. In the ensuing ~3 hours my phone bit it and would get to the Motorola Unlocked Bootloader screen and stop. Tried to boot to custom recovery, but it wouldn't work. Tried reloading TWRP, but gave access error on write but it seems to have fixed it enough to let TWRP open. TWRP showed list of access errors, like the memory had been corrupted. Need to find 4.4.2 image and load it back on via FB, as recovery has no data now.
stastnysnipes26 said:
Haven't seen anyone else report this....
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
omaharper said:
I can't for sure tie it to an update, but the only thing that I did on my Moto X today was enable Motorola Connect. In the ensuing ~3 hours my phone bit it and would get to the Motorola Unlocked Bootloader screen and stop. Tried to boot to custom recovery, but it wouldn't work. Tried reloading TWRP, but gave access error on write but it seems to have fixed it enough to let TWRP open. TWRP showed list of access errors, like the memory had been corrupted. Need to find 4.4.2 image and load it back on via FB, as recovery has no data now.
Click to expand...
Click to collapse
You have a totally separate problem from the OP. I don't have an unlocked boot loader and haven't done a ton of research on the risks of unlocking the consumer edition. 4.4.2 images are posted all around the forums. I would start there.
Sent from my XT1060 using Tapatalk
Thanks. You are right, not the same problem, when my phone soft bricks when I haven't been doing anything to it I get twitchy. I have the DE and have tried (a bunch of times) using RSD Lite and fastboot to push files back to phone, but after reboot everything looks to be reverted back like if WP was enabled, which it isn't. I will take a cruise thru the forums looking for similar issues, but any suggestions would be appreciated
stastnysnipes26 said:
You have a totally separate problem from the OP. I don't have an unlocked boot loader and haven't done a ton of research on the risks of unlocking the consumer edition. 4.4.2 images are posted all around the forums. I would start there.
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
omaharper said:
Thanks. You are right, not the same problem, when my phone soft bricks when I haven't been doing anything to it I get twitchy. I have the DE and have tried (a bunch of times) using RSD Lite and fastboot to push files back to phone, but after reboot everything looks to be reverted back like if WP was enabled, which it isn't. I will take a cruise thru the forums looking for similar issues, but any suggestions would be appreciated
Click to expand...
Click to collapse
If you have a Dev edition fast boot stock vzw files, fast boot OEM unlock and reflash SU. simple as that.
Sent from my XT1060 using Tapatalk
Yup. Have gone thru that procedure several times, but phone won't get past the bootloader unlocked screen, and even after flashing stock (with stock recovery partition) TWRP still shows up, so some write to memory isn't sticking. It's very strange, used same procedure on this phone when upgrading to 4.4.2 from 4.2.2 and on other phones with no problem. Since TWRP can't access the flash, I am wondering if I actually have a corrupted memory module. If I can't get things working, I will start a thread. Don't want to hijack this one. Thanks.
stastnysnipes26 said:
If you have a Dev edition fast boot stock vzw files, fast boot OEM unlock and reflash SU. simple as that.
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
As an update to the original post...
My phone "magically" booted at some point while it was sitting on my table. It's been working since then, but I tried to restart today and the thing won't boot up again. No idea what causes this and adb still isn't working with the phone in recovery mode.
Well I'm from the old school of if a car won't start you check 3 things spark fuel air. So in the case of our phones I always say fxz if an fxz fails to fix the problem than I lean towards a hardware failure. I have never had an fxz not fix a software issue. And I have bricked more than my fair share of devices several times.
I just did my custom order of the Moto X today. I hope I won't run into any issues. I'm switching from the iPhone 5S.
Sent from my XT1058 using Tapatalk
..
Y
thesandman00 said:
As an update to the original post...
My phone "magically" booted at some point while it was sitting on my table. It's been working since then, but I tried to restart today and the thing won't boot up again. No idea what causes this and adb still isn't working with the phone in recovery mode.
Click to expand...
Click to collapse
Have you tried fastboot?
Also getting the drivers to work can be tricky. You have to install them and then use device manager while you're phone is plugged in to get it working.
Sent from my XT1060 using Tapatalk