Hi guys, have a Bionic I just got into the shop and it does not boot up all the way, just too the "droid" letters and just stays there. The guy said it did that after he took the ICS OTA, guess I have to take him at his word. Here's what I did:
Make sure battery was charged
Used the Factory fastboot cable just in case
Downloaded the Fastboot files for .246 and running RSD v5.7
Finished the flash and didn't boot, went into recovery and wiped data and cache, still nothing stays there for hours.
Any hope for this thing? Seems like it should work with the RSD and the correct fastboot files.
thanks
Edit: Used different cable and it powered right up. DOh
Related
Hi,
Full version as a note. Droid 1
Flashed clockworkmod recovery (2.5.0.1), went fine. Made a backup of stock rooted ROM, worked fine. Next flashed bugless beast .6, while clearing data & cache, no problem.
Now i want to flash to cm - trying out different ROMs - trying to reboot into recovery or flash another ROM both fail to get me to a bootloader. Instead i see the motorola boot logo for 30-45 seconds, followed by what looks like a regular boot (motorola M, then Droid eye, & booted.). I have also tried fixing permissions.
If anyone has any idea why this is happening or can direct me to a forum link it would be greatly appreciated. Sorry if this is in the wrong section, and yea I've tried looking through the forums for a while.
Thanks
just a little baby sized pump...
This happened to me too after working perfectly for several months. All of the sudden I just couldn't get to clockwork. I am running CM7 Nightlies. After not being able to fix the issue for several days I decided that a full wipe via the .sbf method was in order. I've got everything up and running again but it was an annoying process. Can anyone out there help us to understand why this happened so we don't have to deal with this again?
Do you have a link for the method you described about? That would be really helpful!
An ever so slightly larger bump
I really am not trying to be lazy, but all the .sbf methods I've read so far seem require you getting to a boot loader. If I could get to a boot loader this wouldn't be a problem, as I made a back up of my stock ROM. I have a functioning bugless beast ROM, just no recovery / boot loader, and no way to flash back to my recovery.
And possibly solved..
One: Please pardon my ignorance, doing these things on my Eris was far easier, or at least what I got used to.
Two: Please also ignore the word boot loader in my previous posts, as it was the recovery console that I could not get to load. Sorry Again.
Three: Its magically working. My methods were unscientific to say the least, but the Droid is now in "ClockworkMod's Recovery v2.5.0.1".
Things I finally did:
NOTE - I DO NOT BELIEVE ANY OF THIS TO BE THE PROPER ORDER OF THINGS. PLEASE VERIFY WITH SOMEONE FAR MORE INTELLIGENT THAN ME. THE FOLLOWING REFLECTS THE PROCESS I DID, AND SHOULD PROBABLY NOT BE FOLLOWED UNLESS A MOD ACTUALLY SAYS THIS WAS CORRECT
1. Pulled Battery, hold power button down for a few seconds, and then put back in
2. Hold Up on D-pad while holding the Power Button
3. You see the following
Code:
bootloader 2c.7c
battery ok
ok to program
connect usb
data cable
4. Connect USB data cable to PC running RSD Lite. You will also want a .sbf recovery file from a trusted source.
5. Select the .sbf in RSD Lite. Tell it to start. I used the clockwork recovery only .sbf
*** Where things got officially weird for me ***
6. The .sbf file I told it to load seemed to work, as the progress bar moved. The phone almost instantly rebooted, back to the ROM I was running minutes earlier. Clockwork had not been working previously trying to reboot into recovery, but almost instantly upon trying this time, I was in recovery mode.
NOTE - The USB cable was still plugged in as well. I don't know which combination of things actually got this to work, but it did.
Hope this helps someone else out.
So here's what happened from the beginning:
I used Safestrap to try out ICS on this thing and got a backup of my original rom and everything went smooth. While on ICS (one of the CM9 nightly builds, 6/29 i think) i decided to go back to my unsafe system, the original gingerbread, it was my understanding that we were able to switch between the two with no problems. When i switched, i was in a bootloop so i tried to restore my backup which had magically disappeared. After that, i decided to try and go back to the original stuff through flashing the FXZ (VRZ_XT894_6.5.1-167_DR4-1_M1-219_1FF_01.xml). got the idea and followed the instructions of a video on youtube by droidforums "HOW TO Unbrick Factory Reset Droid4 D4 via Flashing FXZ in Fastboot". now im stuck in bootloop and have no recovery to flash anything and i dont know what to do from here. anything i can do other than take it to a verizon store and play dumb? all i need is to get this thing working again, gingerbread, ICS or jellybean, idc which lol
thanks in advance
Random94 said:
So here's what happened from the beginning:
I used Safestrap to try out ICS on this thing and got a backup of my original rom and everything went smooth. While on ICS (one of the CM9 nightly builds, 6/29 i think) i decided to go back to my unsafe system, the original gingerbread, it was my understanding that we were able to switch between the two with no problems. When i switched, i was in a bootloop so i tried to restore my backup which had magically disappeared. After that, i decided to try and go back to the original stuff through flashing the FXZ (VRZ_XT894_6.5.1-167_DR4-1_M1-219_1FF_01.xml). got the idea and followed the instructions of a video on youtube by droidforums "HOW TO Unbrick Factory Reset Droid4 D4 via Flashing FXZ in Fastboot". now im stuck in bootloop and have no recovery to flash anything and i dont know what to do from here. anything i can do other than take it to a verizon store and play dumb? all i need is to get this thing working again, gingerbread, ICS or jellybean, idc which lol
thanks in advance
Click to expand...
Click to collapse
I would try downloading the fastboot files again, from here,
http://sbf.droid-developers.org/cdma_maserati/VRZ_XT894_6.5.1-167_DR4-1_M1-219_1FF_01.xml.zip
Then download Motorola USB drivers from here,
http://www.mymotocast.com/download/MDM?platform=windows
Finally, download RSDLite from here,
http://www.mediafire.com/?5mvfxv88twuvh34
Then, boot your droid 4 by holding the VOL DOWN + POWER briefly then release the POWER button and you should be on a black bootloader screen (NOTE: if it boots to the Moto symbol here, shut it down holding the buttons until it turns off then immediately release and hold them down again)
Scroll down to AP Fastboot using the VOL DOWN key then press VOL UP to select it
Once in this mode plug your phone into the usb on your computer and after windows installs drivers run rsdlite
RSDlite should detect your device and you can flash the fastboot file by browsing to it
It should take about 10 minutes or so, and you should have a factory phone again
While i was wating for this to download i decided to check out the recovery from that menu. i did a factory reset and rebooted and it booted up fine. i gues something on there was from ics and was screwing things over? Idk points is it worked lol. thanks so much for the reply though
So I have a rooted Atrix HD that I tried to restore to stock using the original fastboot files from this thread:
http://forum.xda-developers.com/showthread.php?t=1853522&page=2
I ended up getting error messages with the 1st xml file so I used the modified one in Post #14 of the same thread.
Phone appears to flash properly but gets stuck at AT&T logo and RDS makes me power cycle the phone after an eternity.
When I do and get back into fastboot it says pass and thinks everything is good.
Bad news for me is I'm stuck at the AT&T logo and can't move forward.
I can still get into boot mode selection menu so that appears to be good but I'm at a loss on how to recover this thing into a working phone again.
Anyone have any insight?
Battery life was right around 50% when I started.
Maybe RDS puked since it wasn't at 75%?
Any help would be greatly appreciated.
Make you are using the latest version of RDS 6.1.4 and make sure that your cable is perfect and that your phone is detecting properly.
I think I figured out part of my problem.
Used the modified xml file for 144 with the MB886_att-user-4.1.1-9.8.0Q-97_MB886_FFW-20-27-release-keys-ATT-US_BuildA.xml.zip file.
RDS lets it flash but never gets past the AT&T logo.
Now if I try to go back and flash with the right file for the modified XML I get 1/24 flash partition "gpt_main0.bin" -> Phone returned FAIL.
I think I might have borked this phone......
windago said:
I think I figured out part of my problem.
Used the modified xml file for 144 with the MB886_att-user-4.1.1-9.8.0Q-97_MB886_FFW-20-27-release-keys-ATT-US_BuildA.xml.zip file.
RDS lets it flash but never gets past the AT&T logo.
Now if I try to go back and flash with the right file for the modified XML I get 1/24 flash partition "gpt_main0.bin" -> Phone returned FAIL.
I think I might have borked this phone......
Click to expand...
Click to collapse
That fastboot is not for Retail AT&T devices.
Well after booting phone into BP tools to let it charge all night I attempted to reflash this morning with a full battery and a new USB cable using the MB886_att-user-4.1.1-9.8.0Q-97_MB886_FFW-20-27-release-keys-ATT-US_BuildA.xml.zip file and we're back in and now on 4.1.1.
Time will tell if we're back to normal for good.
What is the BP tools you mentioned? Because I've known that it's imposible to charge the phone while it is stcuked into bootloop or even being in the Bootloader screen.
jics91 said:
What is the BP tools you mentioned? Because I've known that it's imposible to charge the phone while it is stcuked into bootloop or even being in the Bootloader screen.
Click to expand...
Click to collapse
BP Tools is the fifth option available when I boot into the boot mode selection menu by pressing Vol Up/Vol Down + Power.
Boot Mode Selection Menu (10.9B)
Available Boot Modes:
Normal
Recovery
AP Fastboot
Factory
BP Tools
I ended up plugging the phone into my Galaxy S3 wall charger last night and then selecting BP Tools when I entered the Boot Mode Selection Menu.
A simple battery icon appeared telling me I had 9% battery left.
This morning after keeping it plugged in all night I had 100% battery.
As I stated earlier after a full charge I was able to flash using RSD lite and now have a working phone again.
windago said:
BP Tools is the fifth option available when I boot into the boot mode selection menu by pressing Vol Up/Vol Down + Power.
Boot Mode Selection Menu (10.9B)
Available Boot Modes:
Normal
Recovery
AP Fastboot
Factory
BP Tools
I ended up plugging the phone into my Galaxy S3 wall charger last night and then selecting BP Tools when I entered the Boot Mode Selection Menu.
A simple battery icon appeared telling me I had 9% battery left.
This morning after keeping it plugged in all night I had 100% battery.
As I stated earlier after a full charge I was able to flash using RSD lite and now have a working phone again.
Click to expand...
Click to collapse
Congrats. I know exactly how that feels. I was in a similar situation not too many days earlier! It is a little sad that there is very little help online when you get stuck when trying something on this phone. You end up having to figure things out by yourself.
windago said:
Well after booting phone into BP tools to let it charge all night I attempted to reflash this morning with a full battery and a new USB cable using the MB886_att-user-4.1.1-9.8.0Q-97_MB886_FFW-20-27-release-keys-ATT-US_BuildA.xml.zip file and we're back in and now on 4.1.1.
Time will tell if we're back to normal for good.
Click to expand...
Click to collapse
So flashing this worked for you? I think someone tried this a week or so ago and it bricked their phone.
Sent from my MB886
ReverseZero said:
So flashing this worked for you? I think someone tried this a week or so ago and it bricked their phone.
Sent from my MB886
Click to expand...
Click to collapse
Please no one try that file... it will only work on bootloader-unlocked Atrix HD devices since it is not a build meant for retail AT&T devices.
Makes sense. Don't think I'll be trying that.
Sent from my MB886
As mattlgroff stated:
Please do not flash the file I linked to/reference to in my OP.
He's a developer and has much more insight into the workings of these files then I do.
I'm not sure why mine worked but I defer to his statement about not flashing that particular file.
I was on stock JB. Rooted with new exploit. Installed bootstrap and custom ROM. Wanted to get back to stock, so I uninstalled bootstrap, and flashed MB886_att-user-4.1.1-9.8.0Q-97_MB886_FFW-20-27-release-keys-ATT-US_BuildA.xml.zip.
RSD failed with 'getvar' and 'oem'. I then edited the xml, removed 'getvar' and 'oem', and retried the flash. RSD failed at system.img.
I then booted the phone into fastboot and did the whole thing manually thru fastboot and terminal. This time everything went through okay. I rebooted the phone into stock recovery and erased cache. But now the phone is stuck in bootloop on the red m logo.
What am I missing?
I am having trouble to flash back to stock ICS with RSD lite everytime i use it and connect my phone it says USB connected but that is it. I cannot find the associated file anywhere to flash back to stock any ideas?
All, please help !!!!
I bought a droid bionic on ebay (seller didn't mention that the software is corrupted) now tired to install ICS using RSD 5.7, it installed correctly, but the phone boots up and gets stuck on the "Droid" screen. Nothing happens from there. I can go to AP boot and/or recovery but can't do anything about it. Please help !!!! Searched the web for two days but no solution. I loaded the following file with RSD, downloaded from different site and tried atleast 5 times.
VRZ_XT875_6.7.246.XT875.Verizon.en.US_CFC_01.xml.z ip
SamuriHL's House Of Bionic
READ all the OP until you understand it. Any question you can have is probably addressed in the threads. HOB scripts automate most of the things you can screw up.
Good Luck
What happens when you try to use the stock recovery?
rahm0809 said:
All, please help !!!!
I bought a droid bionic on ebay (seller didn't mention that the software is corrupted) now tired to install ICS using RSD 5.7, it installed correctly, but the phone boots up and gets stuck on the "Droid" screen. Nothing happens from there. I can go to AP boot and/or recovery but can't do anything about it. Please help !!!! Searched the web for two days but no solution. I loaded the following file with RSD, downloaded from different site and tried atleast 5 times.
VRZ_XT875_6.7.246.XT875.Verizon.en.US_CFC_01.xml.z ip
Click to expand...
Click to collapse
The FXZ file, for some reason, won't wipe the /data partition. Your best bet is to boot into Stock Recovery, wipe data, power down. Then boot up into flash mode for RSD Lite. Reflash and then everything should be okay.
The device was probably on Gingerbread and the ICS flash caused the OS to freak out when it saw a /data folder full of Gingerbread things without any sort of preparation laid down.
I could have sworn the FXZ always wipes data...Well, the unmodified FXZ. And it erases internal storage, too....
Sent from my ASUS Transformer Infinity TF700 running Android JB (rooted) via Tapatalk HD
EDIT: Everything booted up after while, just took a really long time for it to completely boot.
I had my xt1060 Verizon Dev Edition rooted and unlocked running Android 5.1. I wanted to flash it back to factory, so I downloaded "XT1060_GHOST_VERIZON_5.1_LPAS23.12-39.7-1_cid2_CFC.xml.zip" from firmware.center. Then I used the commands from Motorola's Restore to Factory guide, to flash the files.
That caused a bootloop to occur and have the screen to stay at the warning bootloader unlocked screen. So then I downloaded "XT1060_GHOST_VERIZON_5.1_LPA23.12-39.7_cid2_CFC.xml.zip" and tried that, and still the same thing.
I had an old copy of "MOTXT1060DEV_4.4-13.11.1Q2.X-69-3_1FF-CID2.xml" which I've used before to flash back to factory and I tried that. And now whenever I try to boot it up, it'll go into motorola's recovery and the image of the Android opened up keeps flashing on the screen, assuming that it's in a bootloop.
Up until this point I've been using osx-fastboot to flash the files, so I pulled out my old Windows laptop which had a copy of RSD Lite in it, and attempted to flash "XT1060_GHOST_VERIZON_5.1_LPAS23.12-39.7-1_cid2_CFC.xml.zip", which I tried the first time. I was able to get through that successfully, however it still did the same thing as before where the recovery was stuck in a bootloop.
I found this thread on here, and I followed the instructions for RSD Lite and the manual flash, neither worked did the same thing as when after I tried RSD Lite the first time. However the manual flash got farther, but is just sitting at the Verizon boot screen, and that's where it is right now for the last 15 minutes.