Hey guys, today i was using my DHD when a usual random reboot occurred, but this time the phone got caught in a bootloop, (I really have no idea why) as with Android 4.2 you now have to register a computer to the phone for ADB to become 'Online'. I know this isn't really a problem for others but my volume down key actually died last week, ADB isn't playing very nicely at all, as it comes up as 'Offline'. I really need your help guys, i have work tomorrow so i really need it. Anythings appreciated. Thanks guys.
Bump
humzaahmed155 said:
Hey guys, today i was using my DHD when a usual random reboot occurred, but this time the phone got caught in a bootloop, (I really have no idea why) as with Android 4.2 you now have to register a computer to the phone for ADB to become 'Online'. I know this isn't really a problem for others but my volume down key actually died last week, ADB isn't playing very nicely at all, as it comes up as 'Offline'. I really need your help guys, i have work tomorrow so i really need it. Anythings appreciated. Thanks guys.
Click to expand...
Click to collapse
If you are in a bootloop and therefore your device is not turning on, you won't be able to use adb commands. What about booting in hboot or recovery and reflashing the rom or a RUU?
glevitan said:
If you are in a bootloop and therefore your device is not turning on, you won't be able to use adb commands. What about booting in hboot or recovery and reflashing the rom or a RUU?
Click to expand...
Click to collapse
I thought about hboot and recovery, but my volume buttons are completely dead, so the phone will just go ahead and attempt to boot normally, back in the Nexus One days I could remove the battery and insert it again whilst plugging a usb cable in, that would get it into recovery, but it doesnt work (as guessed) with my DHD
humzaahmed155 said:
I thought about hboot and recovery, but my volume buttons are completely dead, so the phone will just go ahead and attempt to boot normally, back in the Nexus One days I could remove the battery and insert it again whilst plugging a usb cable in, that would get it into recovery, but it doesnt work (as guessed) with my DHD
Click to expand...
Click to collapse
It is not a wise decision to be messing with a broken device. I am afraid to say that until you can solve the volume rocker issue you won't be able to fix it.
glevitan said:
It is not a wise decision to be messing with a broken device. I am afraid to say that until you can solve the volume rocker issue you won't be able to fix it.
Click to expand...
Click to collapse
Yeah, i'll take it to repair tomorrow and get the volume keys sorted out, then i'll be able to reflash my rom, thanks for the reply though.
EDIT: I discovered that ADB is actually running when the phone is switched off, I typed adb reboot recovery, and it booted into recovery!
humzaahmed155 said:
EDIT: I discovered that ADB is actually running when the phone is switched off, I typed adb reboot recovery, and it booted into recovery!
Click to expand...
Click to collapse
If the device is off... How do you get into adv without power to the device?
Sent from my Reborn Desire HD in another dimension...
That thanks button doesn't bite
GuyInTheCorner said:
If the device is off... How do you get into adv without power to the device?
Sent from my Reborn Desire HD in another dimension...
That thanks button doesn't bite
Click to expand...
Click to collapse
The DHD was powered off, I plugged it into my PC and windows recognised it as "Android ADB Interface" I myself was quite surprised, the LEDs on the phone were flashing orange and green rapidly, I typed adb reboot recovery and it booted straight into recovery
Sent from my GT-I9305 using Tapatalk 2
humzaahmed155 said:
The DHD was powered off, I plugged it into my PC and windows recognised it as "Android ADB Interface" I myself was quite surprised, the LEDs on the phone were flashing orange and green rapidly, I typed adb reboot recovery and it booted straight into recovery
Sent from my GT-I9305 using Tapatalk 2
Click to expand...
Click to collapse
Nice, thanks for the heads up :good:
It works like that. Turn off the device, plug in USB cable and adb detects it. I don't know if that works on all devices, but it does on ours. It's an easy way to boot into recovery/bootloader if volume buttons are damaged. But this is too late.
Sent from my Nexus 7 using xda premium
sashank said:
It works like that. Turn off the device, plug in USB cable and adb detects it. I don't know if that works on all devices, but it does on ours. It's an easy way to boot into recovery/bootloader if volume buttons are damaged. But this is too late.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Thanks! Good to know, cause my volume buttons are borked.
Sent from my REVOlutionary Desire HD
thanks don't hurt ya know?
Related
Hello,
I've been using my rooted/unlocked Galaxy Nexus for a while now with no problems at all. Earlier today it rebooted for no reason when it was just sitting on my desk. The phone never actually booted and was stuck in a boot loop. I pulled the battery and restarted and went into the recovery menu to do a factory reset. Before I could select the recovery option my phone froze with an exclamation mark android on the screen. I pulled the battery again and now the screen doesn't turn on at all and the phone isn't recognized by my computer. I can't Adb, fastboot, or even Odin. However I can feel the phone vibrate when I power it on. Is there any hope for my phone?
I'm not too sure on this so I'd wait for someone for experienced to reply.
But I can say that it's very hard to brick a Galaxy Nexus. So have some hope.
How do you know you can't fastboot? Are you not able to pull the battery and boot into fastboot when connnected to a computer? Even if the screen doesn't show it, can you do "Fastboot devices" and see it in Command line?
If you can start it up and feel it vibrate, you're definitely not bricked.
Can you get into bootloader? Hold volume up+down and power on.
The android logo you recognised before with the '!' sign was 'Download mode'. If you can see anything on screen there should be no reason why you cant recover it. Don't worry your not bricked.
Same problem!!!
CuteFuzzyPuppy said:
Hello,
I've been using my rooted/unlocked Galaxy Nexus for a while now with no problems at all. Earlier today it rebooted for no reason when it was just sitting on my desk. The phone never actually booted and was stuck in a boot loop. I pulled the battery and restarted and went into the recovery menu to do a factory reset. Before I could select the recovery option my phone froze with an exclamation mark android on the screen. I pulled the battery again and now the screen doesn't turn on at all and the phone isn't recognized by my computer. I can't Adb, fastboot, or even Odin. However I can feel the phone vibrate when I power it on. Is there any hope for my phone?
Click to expand...
Click to collapse
Woke up during the night because the color start up screen was looping. Exact the same problem as CuteFuzzyPuppy. I pulled the battery and went wanted to do a restore both it can't fint volume E:. The files are listed, but when you push one it doesn't work. HELP!
coprotsap said:
Woke up during the night because the color start up screen was looping. Exact the same problem as CuteFuzzyPuppy. I pulled the battery and went wanted to do a restore both it can't fint volume E:. The files are listed, but when you push one it doesn't work. HELP!
Click to expand...
Click to collapse
Are you on stock? Have you unlocked the bootloader and rooted your device?
Yes to all
RTContent said:
Are you on stock? Have you unlocked the bootloader and rooted your device?
Click to expand...
Click to collapse
Meaning, I'm on latest Android Revolution (not stock), and it's unlocked and rooted. Thanks for any help on this!
coprotsap said:
Meaning, I'm on latest Android Revolution (not stock), and it's unlocked and rooted. Thanks for any help on this!
Click to expand...
Click to collapse
do you have clockworkmod recovery? restore a backup if u have one, or wipe data/factory reset, it will work for sure if it was only bootlooping
martonikaj said:
How do you know you can't fastboot? Are you not able to pull the battery and boot into fastboot when connnected to a computer? Even if the screen doesn't show it, can you do "Fastboot devices" and see it in Command line?
If you can start it up and feel it vibrate, you're definitely not bricked.
Click to expand...
Click to collapse
Thanks for the reply. If I hold the volume up, volume down, and power button with the battery in and with the USB unplugged I can feel a vibrate. When I plug the phone into my computer I don't see any fastboot devices. All the drivers are the same and I have tried several USB ports and cords.
If I remove the battery and connect the phone to my computer I hear constant USB connect/disconnect sounds and OMAP4440 constantly appears and disappears in the device manager. Still unable to detect the phone using fastboot or Odin.
What device do you see in device manager? My computer, properties, device manager (top left). It should say something like samsung galaxy Nexus adb device or something.
Sent from my Galaxy Nexus using Tapatalk
RTContent said:
What device do you see in device manager? My computer, properties, device manager (top left). It should say something like samsung galaxy Nexus adb device or something.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
OMAP4440, but it only appears when the battery is out and it constantly connects and disconnects.
CuteFuzzyPuppy said:
OMAP4440, but it only appears when the battery is out and it constantly connects and disconnects.
Click to expand...
Click to collapse
And with the battery in and loaded into the bootloader?
Sent from my Galaxy Nexus using Tapatalk
RTContent said:
And with the battery in and loaded into the bootloader?
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
Nothing at all.
any luck? I am having similar problems. Phone will not be recognized and I can't access the bootloader. Constant bootloops
i had a similar problem last saturday. Worked on fixing it until yesterday. It was a corrupted sd(from what I can tell) so I never was able to start up my phone again or flash anything to it. I am waiting on a warrenty replacement from samsung. At first I could get to fastboot ect but all flashing errored out. Pretty soon I could only get to a screen with a phone ......triange.....computer screen. Thats where I am at now. I even tried a usb jig to get it back to download mode (which works on lots of samsung devices to get them back from bricked to the oden screen) with no luck. I have seen a few posts saying it is confirmed to work on galaxy nexus, but I had no luck. no luck. On the bright side I was able to pull my droid 2 global out of bricked state yesterday which made me feel a bit better.
CuteFuzzyPuppy said:
Hello,
I've been using my rooted/unlocked Galaxy Nexus for a while now with no problems at all. Earlier today it rebooted for no reason when it was just sitting on my desk. The phone never actually booted and was stuck in a boot loop. I pulled the battery and restarted and went into the recovery menu to do a factory reset. Before I could select the recovery option my phone froze with an exclamation mark android on the screen. I pulled the battery again and now the screen doesn't turn on at all and the phone isn't recognized by my computer. I can't Adb, fastboot, or even Odin. However I can feel the phone vibrate when I power it on. Is there any hope for my phone?
Click to expand...
Click to collapse
Flash thw phone again. Happend to me on symbian.. so I flashed it,, your phone is not bricked
Sent from my Gnex
my phone is similar with yours.So did you solve it?
Hey guys, back with a new problem.
So the wife has been having issues with her power button for a while now, and its getting to the point where it is pretty much intolerable. Last time she killed her battery it took almost a half hour of button mashing to get her phone to boot back up, and I'm worried that next time she kills the battery, I wont be able to get it to boot again.
Does anyone know a way to boot the G2/Desire Z without a working power button (other than disassembling the phone and shorting the contacts in the power button)?
Her contract is up next month, but I'm sure she'll drop it, kill the battery, or have to do a battery pull between now and then, so any help is appreciated!
I'm not sure but I think I had my g2 powered down and pluged it into my laptop and it booted.
Sent from my G2 running the random rom of the day.
like the above mentioned, there was a flaw in one of the clockwork recoveries (can't recall the version off hand) that when the phone was powered off and you plugged it in it would automaticaly turn on. for you this wouldn't be a flaw so search the forum for someone complaining about this and just install that recovery. of course you will have to be rooted first if you aren't already
Sent from my HTC Vision using xda premium
I had that booting issue with the Clockwork Mod touch recovery for our phones. Guess it can be helpful in this situation. This is the thread with recovery info and this is how to flash recovery.
Not sure if the files linked to in our recovery thread still work but here is link to CWM-Touch 5.8.1.0
Couldn't she do adb reboot or no?
Chancee said:
Couldn't she do adb reboot or no?
Click to expand...
Click to collapse
not if the phone is powered off already. need to be on to use adb
Sent from my HTC Vision using xda premium
In Mimistry ROM you can wake and unlock your phone by pressing a trackball.
andriens said:
In Mimistry ROM you can wake and unlock your phone by pressing a trackball.
Click to expand...
Click to collapse
Firstly, I think you mean Andromadus Mimicry, not mimistry
Secondly, trackpad wake/unlock is a feature in most custom roms.
Thirdly, wake is completely different to booting, which is what the question was about. A (maybe somewhat vague) analogy would be, you've lost the ignition key for your car, and you're trying to start the engine by shifting to first gear.
demkantor said:
like the above mentioned, there was a flaw in one of the clockwork recoveries (can't recall the version off hand) that when the phone was powered off and you plugged it in it would automaticaly turn on. for you this wouldn't be a flaw so search the forum for someone complaining about this and just install that recovery. of course you will have to be rooted first if you aren't already
Click to expand...
Click to collapse
I think the version you're looking for is Clockworkmod 3.0.0.5, which should be available in the Rom Manager app (under flash older/other recovery). can't find a working link for the img itself.
-Nipqer
Hey, got a big probleme here:
while I tried to update my hboot from 1.36 to 1.39 the phone now stays at a black screen. It happened after it tried to go into RUU-mode. No silver HTC Logo will come up and when I unplug the USB cable and plug it again I can hear the Windows 7 sound for a new device.
What can I do now? Can't get into the bootloader with the normal "power + vol down" or anything else. I think I got enough battery because I've used the wall-charger for about an hour or more. Then suddenly the display won't turn on again while on my ROM. So I tried to reflash the boot.img and the ROM again but nothing seemed to help to get the phone booting into Android again.
I decided to try an hboot update with re- / and -unlocking to see if it helps. After re-locking and trying to get into RUU-mode I got the disaster I'm talking about.
Really appreciating your help here.
regards
While plugged in you can try both commands
Fastboot devices
Adb devices
If you see your device in either you can use the respective commands to reboot the bootloader
Fastboot reboot-bootloader
Adb reboot bootloader
Sent from my HTC One X using xda app-developers app
bagofcrap24 said:
While plugged in you can try both commands
Fastboot devices
Adb devices
If you see your device in either you can use the respective commands to reboot the bootloader
Fastboot reboot-bootloader
Adb reboot bootloader
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Thank you for your support, but Win 7 only shows the device as "unknown" in the USB devices and I can't see it in the list after executing both commands.
I thought I could try to let the battery die ?
By keeping the power button held for up to 20 seconds a battery pull is simulated. If this does nothing then something is seriously messed up with the bootloader as that is where the simulation for holding power is.
If you cannot get it to reboot this way then there is likely nothing you can do to resurrect your device.
Though it is weird that it is still been detected as a USB device
Sent from my HTC One X using xda app-developers app
bagofcrap24 said:
By keeping the power button held for up to 20 seconds a battery pull is simulated. If this does nothing then something is seriously messed up with the bootloader as that is where the simulation for holding power is.
If you cannot get it to reboot this way then there is likely nothing you can do to resurrect your device.
Though it is weird that it is still been detected as a USB device
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
I can hold it as long as I want but nothing will happen. I try to let the battery get empty.
Before I give up and get a new phone, I was hoping someone had a solution.
Little backstory on how the bootloop occurred, I flashed the latest Cyanogenmod 10.2 and everything seemed to be working fine minus the Google apps and SU. I realized that I forgot to flash the GAPPs also and was trying to figure out how I should boot into recovery (completely forgetting about adb). A friend said he could "fix" it and flashed a previous Cyan, leading me to the bootloop.
My power button has not worked for months which has only been a hinderance really, as I can still function with the volume rocker and gestures to turn the screen off and on.
But this is the one special case I was worried about where I would need my power button to boot into fastboot or recovery, and I am not able to.
I can get the phone on via plugging into computer, battery pull then put battery back in and wait, but that only leads to the bootloop.
Any help would be appreciated as I have tried anything I could think of as adb won't work in the bootloop for me.
Thanks.
AugustJuly said:
Before I give up and get a new phone, I was hoping someone had a solution.
Little backstory on how the bootloop occurred, I flashed the latest Cyanogenmod 10.2 and everything seemed to be working fine minus the Google apps and SU. I realized that I forgot to flash the GAPPs also and was trying to figure out how I should boot into recovery (completely forgetting about adb). A friend said he could "fix" it and flashed a previous Cyan, leading me to the bootloop.
My power button has not worked for months which has only been a hinderance really, as I can still function with the volume rocker and gestures to turn the screen off and on.
But this is the one special case I was worried about where I would need my power button to boot into fastboot or recovery, and I am not able to.
I can get the phone on via plugging into computer, battery pull then put battery back in and wait, but that only leads to the bootloop.
Any help would be appreciated as I have tried anything I could think of as adb won't work in the bootloop for me.
Thanks.
Click to expand...
Click to collapse
I don't know if it works but you can try to push vol up+vol down and plugging it in to a computer. If it boots as you say it may be boot into fastboot..
Sent from my Galaxy Nexus using XDA Premium HD app
mrgnex said:
I don't know if it works but you can try to push vol up+vol down and plugging it in to a computer. If it boots as you say it may be boot into fastboot..
Sent from my Galaxy Nexus using XDA Premium HD app
Click to expand...
Click to collapse
Sadly, that's one of the first things I tried.
Thanks for the idea though.
Hi there, I have a HTC Inspire 4G phone that is not working anddont know what to do, Actually I have knowledge in samsungs only, (download mode recovery etc) but this phone does not turn on at all, after pressing the power button there is a little red led at the left and turns on and thats it, pressing power and vol - doesnt do anything,
When I plugged it in the computer after 5 mins around the computer recognizes an "android phone" or "my htc" nothing else happens.
when I leave the phone alone, suddently it turns on vibrating constantyl and shows a white screen with a HTC green logo but nothing else happens
:silly: this is crazy right? , please help
Dc-18 said:
Hi there, I have a HTC Inspire 4G phone that is not working anddont know what to do, Actually I have knowledge in samsungs only, (download mode recovery etc) but this phone does not turn on at all, after pressing the power button there is a little red led at the left and turns on and thats it, pressing power and vol - doesnt do anything,
When I plugged it in the computer after 5 mins around the computer recognizes an "android phone" or "my htc" nothing else happens.
when I leave the phone alone, suddently it turns on vibrating constantyl and shows a white screen with a HTC green logo but nothing else happens
:silly: this is crazy right? , please help
Click to expand...
Click to collapse
What happened before this?
Did someone try doing something like down grading?
Your symptoms sound like someone tried to flash a froyo ruu on a device that had gingerbread on it which means your bootloader is possibly messed.
Sent from my GT-I9505 using xda app-developerfs app
some time ago was rooted, a friend of mine tried to format it, he selected all the delete options, and then it did not continue to boot
Dc-18 said:
some time ago was rooted, a friend of mine tried to format it, he selected all the delete options, and then it did not continue to boot
Click to expand...
Click to collapse
I haven't the slightest what you're trying to say here.
bananagranola said:
I haven't the slightest what you're trying to say here.
Click to expand...
Click to collapse
the 1 post is the original and current problem..
Is your bootloader unlocked? Is it S-Off? Did you flash a custom ROM? Did you wipe /system? What exactly did you do to get it into that state?
bananagranola said:
Is your bootloader unlocked? Is it S-Off? Did you flash a custom ROM? Did you wipe /system? What exactly did you do to get it into that state?
Click to expand...
Click to collapse
Im not really sure if the bootloader is unlocked since I didnt use this phone before, but pressing power button + vol- doesnt do anything, my friend who is the owner said that the phone was rooted he wiped everything in the system options, after that the phone did not start anymore and got the problems mentioned before
He might of formated something for the phone to boot up properly, tryed flashing ruu or ADB(ANDROID DEVICE BRIDGE)
Sent from my Desire HD using XDA Premium HD app
JustPlayingHard said:
He might of formated something for the phone to boot up properly, tryed flashing ruu or ADB(ANDROID DEVICE BRIDGE)
Sent from my Desire HD using XDA Premium HD app
Click to expand...
Click to collapse
That may work, is there any thread to see how to do this? Thanks for your help guys
Dc-18 said:
pressing power button + vol- doesnt do anything
Click to expand...
Click to collapse
Did you do that when the phone was off?
bananagranola said:
Did you do that when the phone was off?
Click to expand...
Click to collapse
Yep, removed the battery and tried but doesn't do anything
Dc-18 said:
Yep, removed the battery and tried but doesn't do anything
Click to expand...
Click to collapse
Wait, you tried that when the battery wasn't in the phone?
bananagranola said:
Wait, you tried that when the battery wasn't in the phone?
Click to expand...
Click to collapse
Nup, of course when the battery was on the phone, what I meant is I removed the battery and insert it again and tried but didn't work
Dc-18 said:
Nup, of course when the battery was on the phone, what I meant is I removed the battery and insert it again and tried but didn't work
Click to expand...
Click to collapse
It didn't turn on? What did it do?
bananagranola said:
It didn't turn on? What did it do?
Click to expand...
Click to collapse
Nothing at all