Hi,
my phone died yesterday because the battery was empty - so I charged it a little but the phone won't turn back on. The only thing I see are the touch buttons flashing when I hold the power button. And when I hold it long enough, the screen just flashes... When I tried to connect it my computer I got the ADB to work - I even managed to get to the recovery one time (i used the command adb reboot recovery for almost a hundred times before it came on). I wiped everything, reinstalled the rom (TrickDroid 4.0.0), but when I tried to reboot it nothing changed... it's still not working. Fastboot is not working.
Is there anything I can do about it?
Thanks.
Mmm, are you using CWM perhaps? If so, once you get the phone into fastboot - flash twrp.
Some suggestions you can try:
keep trying vol- + power untill you get into fastboot, it should work eventually.
Charge the phone a bit, unplug the usb cable, try and boot it <- This worked for me when my phone acted up like this, took a couple of tries though.
Have you tried spamming adb reboot bootloader ? That should also put you into fastboot eventually.
Once in fastboot, reflash the boot.img for the rom as well.
And once it works again, dont let the battery go flat, this seems like quite a common issue when the battery runs out.
Thanks for suggestions - I wrote a script that tired adb reboot bootloader every 20s .. and after like 400 runs it booted - I have no idea what this is about - but I should buy a new phone...
Tahnks again!
K got this HTC from a friend of me, was working before, had it rooted and fixed with custom rom
It was S-on on v1.27
k now gonna try to explain what's going wrong:
When i shut down the phone, put battery out, back in, connect to usb, i get the phone recognized by ADB (my HTC phone)
when i type adb reboot-bootloader, device responds and boots into fastboot mode
when i use vul up i get Fastboot usb on screen
from this point i can't get any further, device doesnt respond from any button action except for vol up.
Device is not recongized in windows now (windows 8 64bit) got the famous error 43
So in ADB everything is fine, but in fastboot nothing is working/responding
when i pull battery out, then put it back in, i can succesfully boot with volup en power, then i get everything running (custom rom from before) but it says safe mode
Any ideas what i can do to get this thing back on it's feet?
regards,
Robin
robin-sips said:
K got this HTC from a friend of me, was working before, had it rooted and fixed with custom rom
It was S-on on v1.27
k now gonna try to explain what's going wrong:
When i shut down the phone, put battery out, back in, connect to usb, i get the phone recognized by ADB (my HTC phone)
when i type adb reboot-bootloader, device responds and boots into fastboot mode
when i use vul up i get Fastboot usb on screen
from this point i can't get any further, device doesnt respond from any button action except for vol up.
Device is not recongized in windows now (windows 8 64bit) got the famous error 43
So in ADB everything is fine, but in fastboot nothing is working/responding
when i pull battery out, then put it back in, i can succesfully boot with volup en power, then i get everything running (custom rom from before) but it says safe mode
Any ideas what i can do to get this thing back on it's feet?
regards,
Robin
Click to expand...
Click to collapse
In bootloader(fastboot mode) no buttons will works except vol up,down and power..
If you want to flash a custom rom then
First goto bootloader
Now enter to recovery by using vol down and then power button to ok.
Place a Rom.zip in sdcard format cache/dalvik , all partition except sd and then flash rom..
ahsan64 said:
In bootloader(fastboot mode) no buttons will works except vol up,down and power..
If you want to flash a custom rom then
First goto bootloader
Now enter to recovery by using vol down and then power button to ok.
Place a Rom.zip in sdcard format cache/dalvik , all partition except sd and then flash rom..
Click to expand...
Click to collapse
problem was that none of the button's where responsive, i found the cause of this, volume buttons are damaged (the strip inside was broken)
So now i have a new problem much wurse i think
only power button works, so i did a complete reinstall with ruu, booted up fine, but always in safe mode for some strange reason,
Now after shutdown, i can't get the phone on anymore, only goes to Hboot, and there is nothing responsive, non eof the buttons work, can't use vol buttons because they are broken.
Adb is not responding either, only getting HTC Android USB device in my device list....
I think the phone is ready for trash? :S
robin-sips said:
problem was that none of the button's where responsive, i found the cause of this, volume buttons are damaged (the strip inside was broken)
So now i have a new problem much wurse i think
only power button works, so i did a complete reinstall with ruu, booted up fine, but always in safe mode for some strange reason,
Now after shutdown, i can't get the phone on anymore, only goes to Hboot, and there is nothing responsive, non eof the buttons work, can't use vol buttons because they are broken.
Adb is not responding either, only getting HTC Android USB device in my device list....
I think the phone is ready for trash? :S
Click to expand...
Click to collapse
in bootloader adb doesn't work only fastboot
so when you are in hboot screen try this command
fastboot reboot (in the hboot screen should say fastboot usb)
rzr86 said:
in bootloader adb doesn't work only fastboot
so when you are in hboot screen try this command
fastboot reboot (in the hboot screen should say fastboot usb)
Click to expand...
Click to collapse
can't get into adb anymore so i think the phone is dead unless we repair the volume buttons right?
robin-sips said:
can't get into adb anymore so i think the phone is dead unless we repair the volume buttons right?
Click to expand...
Click to collapse
since you are dealing with a hardware problem then yes
but try this
boot normally(even on safe mode)
connect it to pc and type
adb reboot bootloader
it will take you directly into fastboot mode
then type fastboot reboot
see how it goes and check volume button from there(to confirm the hardware issue)
otherwise repeat the procedure but instead of fastboot reboot run the ruu.exe again
Hey guys,
I've seen some solutions for my kind of problem but none of them seems to start at my frustrating point.
After I rooted my HTC One S I was able to reboot my device and everything went fine.
The problem occured just when my battery was depleted and the phone got turned off I had no chance to restart it.
The LED did not show me it was charging and it did nothing, when I pressed the power button or the volume/power combination.
So i connected it to my laptop and tried to check my devices through adb.
It says my device is in recovery mode.
Using the fastboot reboot command I was always able to reboot my phone and everything was just fine.
I thought it was alright, as I just had to pay attention not to use up my battery, when not at home.
Today my phone just decided to turn off. It refuses to boot up even with the fastboot help from my PC.
It just says: < waiting for device >
certainly I'm unable to post a link to a screenshot I made of my cmd.
Thank you for all kind of help
I flashed CM12 a few days ago on my rooted HTC sensation, with unlocked bootloader, S-OFF etc.
The install has not gone too well, and most of the programs started force closing, to the point where all the android can do is shut down, restart, or go into aircraft mode by holding the power button.
I can not send the phone an adb reboot-bootloader option, because the phone wont prompt me to authorize my PC for remote commands, and I cant get into the bootloader of the phone by powering on with volume down + power, because the volume down button is faulty.
Is there anything else I can do to recover the device and re flash, such as placing a file or script on the SD card for when it boots??
Thanks for any suggestions/help.
mi16chap1 said:
I flashed CM12 a few days ago on my rooted HTC sensation, with unlocked bootloader, S-OFF etc.
The install has not gone too well, and most of the programs started force closing, to the point where all the android can do is shut down, restart, or go into aircraft mode by holding the power button.
I can not send the phone an adb reboot-bootloader option, because the phone wont prompt me to authorize my PC for remote commands, and I cant get into the bootloader of the phone by powering on with volume down + power, because the volume down button is faulty.
Is there anything else I can do to recover the device and re flash, such as placing a file or script on the SD card for when it boots??
Thanks for any suggestions/help.
Click to expand...
Click to collapse
Have you tried turning the phone off, plugging it into the computer, turning the phone on, and keep on sending the adb reboot-bootloader command as the phone is booting up? I've heard that this works as the phone will eventually get it at one point while its booting up.
Hi, ive been having problems with my pixel 7, it seemed like no matter how i flashed it it still wouldnt work 100 percent properly. even if i used android flash tool. So today i flashed the disable-verity/verification flags and then booted into system and I turned off auto system updates and did adb reboot bootloader. It didnt reboot into the bootloader but instead shut off and showed the icon for a battery that wasnt charged. holding voldown and power did notheing immidiately so I unplugged the usb and held power and volume down. It went into the bootloader, however this time the readon was not vol down pressed but "bootonce-bootloader" instead. anyone ever see this or know what this means?
PochiRaccoon said:
Hi, ive been having problems with my pixel 7, it seemed like no matter how i flashed it it still wouldnt work 100 percent properly. even if i used android flash tool. So today i flashed the disable-verity/verification flags and then booted into system and I turned off auto system updates and did adb reboot bootloader. It didnt reboot into the bootloader but instead shut off and showed the icon for a battery that wasnt charged. holding voldown and power did notheing immidiately so I unplugged the usb and held power and volume down. It went into the bootloader, however this time the readon was not vol down pressed but "bootonce-bootloader" instead. anyone ever see this or know what this means?
Click to expand...
Click to collapse
Question: Is your Pixel Carrier Locked?
It's my first post leave some comments if you find it helpful...
I was using a Linux box with a BLU oem USB c charger.. wait till the battery percentage shows 0% or 1% hold the volume down button while pressing the power button just get to the bootloader and ..
Once your able to connect it using fastboot... Either use fastboot reboot recovery or select it from the boot menu..
Download the platform tools from Google.. also the latest OTA for your device.. extract the zip to a your Desktop then toss the compressed OTA... In that folder open terminal or cmd... Run adb sideload OTA.zip..
Reboot one more time to manually enter recovery WIPE DATA nd Factory Reset..
Reboot back to bootloader fastboot reboot sideload or reenter recovery>apply OTA from adb..
Adb devices should return device and sideload... Issues the command adb sideload OTA.zip one last time... Nd your back in business... My friend