Database Info

[Q][URGENT] Booting Loop problem, how can it be fixed?

How can this be fixed? I can still do the Vol Down + Power combination thing, but the phone will not load to my home screen via normal start up.
I have no idea how to fix this, seeing as it was caused by me applying a theme in Metamorph. I don't have SDK either...
I have a HTC Magic, 32B.
I'm trying to fastboot recover it right now, but even when my phone says FASTBOOT USB, the command prompt still says <Waiting for device>
I really need help.

I really need help right now, it's my only phone, and I'm not in the position to buy a new one.

Stuck at Motorola logo and RSD mode 3

I'm new to Xoom but gave unlocking and rooting a go. That was todays mistake! I flashed a 3g version of boot.img. Then I tried to flash back to stock img-file. Found out that it also was a 3g img-file. Flashed once more. Now it was a wifi-only boot.img. Now I'm stuck at the Motorola Dual Core logo with Starting RSD mode 3 written in top left corner. I can't shut this thing off or anything else but rebooting back to same screen. I really don't know what to do. I bought it yesterday from a man that bought it in the US a week ago so I can't go to the shop and I don't think there are any shop that can flash it for me because it's not available here in Sweden yet. Please help. I have RSD Lite installed and the correct drivers for the Xoom installed. I'm used to ADB but it can't find the device and fastboot doesn't see it either.
Edit. I can't go into fastboot mode.

Grab the wifi's boot.img off of here:
http://forum.xda-developers.com/showthread.php?t=1017398

http://forum.xda-developers.com/showthread.php?t=973355
This might be helpful. Not sure.

Don't worry you are in good company, even BRD had the same problem. Here's how he fixed it:
While I was in "RSD Mode 3" I did
Code:
fastboot flash boot boot.img
Even though there was no response from the device, I pressed Vol Down + power until the screen went black. I then quickly pressed and held Vol Up + power. The device then went into the bootloader, received the queued command from fastboot, and flashed the boot.img. Finally, I did
Code:
fastboot reboot
and was back in the game.
Guys, I think the moral of the story is to slow down and be careful with fastboot. You can bet i'll be a little more careful
Click to expand...
Click to collapse
Edit: Same advice as linked above by milehighclubAV8R

That doesn't do it. Propably it's some stupid misstake from me but I cannot do this because of " I pressed Vol Down + power until the screen went black". It wont get black. When I press Power + Vol down nothing happens. Am I doing something wrong. I have tried holding the buttons for about 30 seconds and nothing happens.

Did you just press the buttons or did you also enter the fastboot code as suggested?

First cmd command then pressing the buttons. When I reboot using power + vol up it starts into RSD mode 3. When rebooting it with power + vol up then vol down when black it starts into the logo screen without any text in the upper left corner. Can't even shut it down with long press on power button
Can I pull the battery? On my Galaxy S that's the way out if I get in a boot loop or need to redo a failed flash.

Not AFAIK, the unit is sealed and can't access the battery to pull it.
Perhaps ask in this thread - http://forum.xda-developers.com/showthread.php?t=973355, there may be more technical people seeing it there than in the general section.

OK. I will do that. Thank you for trying to help.

Press power+volume up. Hold it til it restarts. Let go of both buttons once you see the motorola logo then just press volume down once, and you should be then able to cycle through 3 different modes. Press volume down to cycle to different modes, volume up to select. Hope that helps.
Sent from my Xoom using XDA Premium App

Sorry but I can't cycle through anything. There are two modes. Either "Starting RSD mode 3" or nothing and RSDLite can't communicate with it so I belive that my xoom is dead. Sending it in for repair tomorrow. I'm giving up.

mine is stuck in the rsd mode 2. if i push and power and the up it will boot cycle if i the down button it says it is the the flashboot protocol mode, but i cannot get it to respond from the cmd window. my computer doesnt think its connected. i have the correct mot drivers. any help or is it bricked

Some people have been getting lucky with ADB commands however others have not been so luck. I myself am in the others category with one of my XOOMS.
Sucks, but some people have been able to get back. I however have not been so lucky with one of the WiFi XOOM's I have and did this purposely to see if maybe something can be done with it. Looks like we have to wait for all the files to be released......
Any day now Moto, util then people will continue to send these devices in and con the stores . For this, I applaud them.

This might work or it might not.
I had a bricked xoom too. no matter what fastboot i entered it wouldnt recognise it. all it would say is "waiting for device"
This is what i did.
Turn the xoom off
Do not connect you USB cable yet
Fastboot reboot-bootloader
It should say "waiting for devices"
Now plug your xoom
Turn on the xoom.
When you see the Motorola logo press volume down till you see "fastboot protocol"
Press volume up.
It recognise my xoom that way

couldnt turn mine off. let the battery run down. plugged it into power booted it up. no help. bricked

stevenege said:
Some people have been getting lucky with ADB commands however others have not been so luck. I myself am in the others category with one of my XOOMS.
Sucks, but some people have been able to get back. I however have not been so lucky with one of the WiFi XOOM's I have and did this purposely to see if maybe something can be done with it. Looks like we have to wait for all the files to be released......
Any day now Moto, util then people will continue to send these devices in and con the stores . For this, I applaud them.
Click to expand...
Click to collapse
I have to admit, I'm one of them. Sure is a nice way to tell Moto to hurry the F up. I can't say I felt great about it but I wasn't about to lose $600 either.

me to one of them

shipped mine back to the factory today. not sure what they can do to it. is there such a thing as a force flash or will they have to replace the firmare chip to make it work? unstable combo tegra and honeycomb, aint messin with mine anymore.

i just recovered mine from this. i flashed recovery with clockwork mod:
at the rsd 3 screen with the usb attached
fastboot flash recovery recovery.img
held the volume down while pressing the power off on until fastboot started flashing the recovery
fastboot reboot
xoom started in clockwork mod, did a restart and it worked
****This happened after attempting to load recovery from rom manager without flashing new recovery image.***

Did you happen to mention in your explanation about what went wrong with your xoom anything about unlocking or relocking?

[Q] Moto G not boot

Moto G not boot, it just gets in the bootloader screen warning

I'm having the exact same issue, just flashed the latest stable version of CM11 (with gapps obviously) from dhacker's thread in CWM.
Coming from 4.3 with the US version t-mobile moto g.
Stuck on the bootloader unlocked screen.
I thought for a while it was just that the first loadup takes awhile but has been 10 minutes now and am figuring something bad happened.
ignore all the italics, I'm an idiot
Edit: 25 minutes in, have tried connecting the phone to computer and running command prompts to it like I did to get into recovery, device not recognized under cmd "adb devices" or "fastboot devices" when connected to computer
Phone screen goes black for about 0.8 seconds when power button is held down and immediately pops back up into warning bootloader unlocked screen, trying to go into fastboot or anything like with volume down and power button achieves the exact same effect.
Any help would be greatly appreciated.
Edit2: If I hold the power button and down volume for 20 seconds (just ignore when the screen goes black and hold it for 20 seconds) it will boot into fastboot mode
Recovery seems to do nothing but the device is now recognized by the mototool all in one, I will report back if I figure out anything more useful, I am hoping the mototool will save me
Edit3: tried flashing stock recovery, my phone now says in pink "hab check failed for recovery", tried flashing CWM recovery, it seemed to work. I then clicked "fix boot logo" it worked. The phone is now showing the motorola logo but doesn't seem to be doing much else, I'll let it sit for a couple minutes.
Edit4: If none of this works at least you'll have an interesting read about how to further destroy your phone
Tried rebooting to recovery, the mototool thinks it did it but my phone stays stuck at the motorola logo. I then told it to check connection and it now thinks there is no longer a device connected. Tried turning the phone off again, went immediately back to the motorola screen. I seem to be in the same situation except the bootlogo is no longer that ugly text. Back into fastboot mode, lets see what else we can do.
I checked to see if it was recognized by command prompts now and it IS, if you go back under like you were unlocking the bootloader and open up a cmd prompt and type "fastboot devices" it's recognized in this fastboot mode. This has given me new optimism, I'm feeling hopeful that my device is not destroyed, hopeful and very hungry, I will report back in after getting food.
Edit5: I've realized that I have no idea where to go from here, while I can access command prompts I have no idea what commands to put in, I tried hitting "factory" under the fastboot in hopes that it would flash my factory recovery, no such luck, I'm back to the same situation, tried hitting BP tools next because I didn't know what it was and thought it would be helpful, no such luck, back to the same screen, my quickly inflated confidence is now waning, I do have hope that someone can fix this issue but I am thinking that someone is not me.
I hit the recovery button, I'm sure I had done this before but this time it worked, went to restore from sd card, and restored my backup I made right before all these issues, it recovered my device, I then restarted it and everything is good now.
Apparently I am an idiot, but that's okay because my phone is working again now, after only about an hour or something.
TO FIX YOUR ISSUE HOLD DOWN VOLUME AND POWER AT THE SAME TIME FOR 20 SECONDS, IGNORE WHEN THE SCREEN GOES BLACK, KEEP HOLDING FOR ALL 20 SECONDS, CHOOSE RECOVERY, THEN GO BACK TO YOUR BACKUP THAT YOU SAVED BEFORE FLASHING A NEW ROM, RESTART THE DEVICE AND NOW THE DAY IS SAVED

[fix] htc one s stuck in bootloop, volume down button not working [root][fix]

So here was my situation:
I was flashed the wrong piece of software (stupid me) and I was stuck in a boot loop. Unfortunately the volume down button on my HTC one S was not working so a simple boot into bootloader mode did not work!
Furthermore, I couldn't even get the phone OFF! Pressing the power button for minutes on end still ended up in the HTC constantly rebooting itself. (Worst thing ever!).
FIX:
Step 1: Power Off device
Although this may sound very easy to do, I could not get the device powered off via the power button(10-20 secs) so I had too do it the hard way.
Luckily, the One S being a sealed phone isn't actually hard to take apart. Its actually rather simple!
I used a video on youtube to disassemble then took out the battery for about 30 minutes. (Search "HTC ONE S fix" on Youtube and you'll find it. Sorry i can't post any links im a junior member!)
Step 2: Plug the USB cable into your PC
Put the battery in ( if you used the physical battery pull out of course)
With the device completely off plug the cable into the PC and run the command
Code:
adb devices
By doing this my device actually went straight to the recovery screen and the device was recognized on the computer.
Now the recovery screen i got wasnt very helpful as it continuously rebooted and eventually booted back to the white HTC screen.
HOWEVER, the fact that I could use ADB commands gave me hope.
Step 3: Reboot into bootloader using adb command
Code:
adb reboot bootloader
This is where I really saved myself i ran this command and got to the bootloader screen and I was able to actually work with that!
Step 4: Flash/ Restore Backup to your device and get it up and running!
Now there are a couple of ways you can choose to do this depending on your specific situation and resources available:
A) When in bootloader mode you can access the fastboot commands which will allow you to run any flashing commands that you need to rewrite whatever is corrupted (e.g boot.img)
B) If you have a working recovery simply select recovery and boot into recovery and flash either your nandroid backup or a new ROM as a whole
C) This is what i did, I ran a stock RUU which deteccted my phone and in 10 minutes my phone was up and running!!
Now I know this is a rather rare case, but I actually thought my phone was gone and the fact that I got it working really motivated me to put this out there so someone like me may be able to get their phone up and running again!
Forgive me this is probably my first real thread, Hopefully I continue to post how I fix some of the rarest occurrences I always seem to get myself into.
NO MORE BOOTLOOPS! Who says we need volume down buttons? LOL

bricked, can't get to bootloader or recovery, adb doesn't see phone either

Hello, I just unlocked bootloader, flashed custom recovery (clockwork 6.0.4.8), and gained root on my HTC One S. I then attempted to install a custom ROM, (cyanogen 12.1).
After installing and telling Clockwordmod to reboot, I believe I am in a boot loop. The white HTC screen pops up and then goes to black and stays there. When I plug my phone into my computer, I get the connection and chime, and a new device appears in Device Manager called "HTC MTP Device." When I am in fastboot mode, my phone is shown as "Android ADB Interface" in device manager, so this is different. This leads me to believe that my phone is not dead or off, it is on with a blank screen. I do not believe my computer will recognize a device that is not powered on.
I have HTC Sync Manager and I have the option for it to automatically pop up when a device is connected. It pops up, but with an error saying HTC Sync Manager could not connect to your phone.
I am able to hard-reset the phone, by holding down the Power button for several seconds. However, this just repeats the process (White HTC logo screen, then black screen). I am not able to enter bootloader or recovery by holding down Volume and Power. I have tried Volume Up + Power, Volume Down + Power, and Volume Up + Volume Down + Power.
Also adb no longer recognizes my device, so I can not interact with the phone that way either.
Currently, my only idea is to allow my phone to die so I can try booting it into recovery from power off. But if there are any other ideas that would be great.
Right before I rebooted, after installing the ROMs, I got a message saying something like "Root possibly lost, do you want to fix root." I said yes, could this be part of the issue?
I am on Windows 10.

t1j said:
Hello, I just unlocked bootloader, flashed custom recovery (clockwork 6.0.4.8), and gained root on my HTC One S. I then attempted to install a custom ROM, (cyanogen 12.1).
After installing and telling Clockwordmod to reboot, I believe I am in a boot loop. The white HTC screen pops up and then goes to black and stays there. When I plug my phone into my computer, I get the connection and chime, and a new device appears in Device Manager called "HTC MTP Device." When I am in fastboot mode, my phone is shown as "Android ADB Interface" in device manager, so this is different. This leads me to believe that my phone is not dead or off, it is on with a blank screen. I do not believe my computer will recognize a device that is not powered on.
I have HTC Sync Manager and I have the option for it to automatically pop up when a device is connected. It pops up, but with an error saying HTC Sync Manager could not connect to your phone.
I am able to hard-reset the phone, by holding down the Power button for several seconds. However, this just repeats the process (White HTC logo screen, then black screen). I am not able to enter bootloader or recovery by holding down Volume and Power. I have tried Volume Up + Power, Volume Down + Power, and Volume Up + Volume Down + Power.
Also adb no longer recognizes my device, so I can not interact with the phone that way either.
Currently, my only idea is to allow my phone to die so I can try booting it into recovery from power off. But if there are any other ideas that would be great.
Right before I rebooted, after installing the ROMs, I got a message saying something like "Root possibly lost, do you want to fix root." I said yes, could this be part of the issue?
I am on Windows 10.
Click to expand...
Click to collapse
Just in case anyone stumbles on this. You can boot into the bootloader by Holding down the Power Button for several seconds, the soft buttons will blink, indicated ensuing reboot, when they stop blinking, hold Volume Down until you get to the bootloader menu. The phone does not need to be powered off for this. From there, adb/fastboot will recognize your phone, and you can factory reset if needed.
However, I figured out my problem. On older HTC models, including the HTC One S, you have to manually flash the boot.img file that is included in the zip for your ROM.
But now I've made it to the cyanogenmod boot screen and am stuck there. sigh. i've been at this literally all day.

In the end, I just flash a different rom, specially Candy5 as found here: http://forum.xda-developers.com/htc-one-s/development/rom-t2964931 and it worked.
It's possible I accidentally flashed a rom that was incompatible with my device, not sure.
EDIT: I also switched from CWM to TWRP. Not sure if that helped.

t1j said:
Just in case anyone stumbles on this. You can boot into the bootloader by Holding down the Power Button for several seconds, the soft buttons will blink, indicated ensuing reboot, when they stop blinking, hold Volume Down until you get to the bootloader menu. The phone does not need to be powered off for this. From there, adb/fastboot will recognize your phone, and you can factory reset if needed.
However, I figured out my problem. On older HTC models, including the HTC One S, you have to manually flash the boot.img file that is included in the zip for your ROM.
But now I've made it to the cyanogenmod boot screen and am stuck there. sigh. i've been at this literally all day.
Click to expand...
Click to collapse
I have broken volume down button, what can i do? face the same problem
What does it mean by manually flash boot.img? After flashing a custom rom, do not reboot first but flash the boot.img via twrp which can be found in zip for the rom?