Hello... Today i replace my battery. I lost all sensors. I have a brilliant idea, wipe all, system etc. reboot and BAM! HTC Logo loop... I try pwr+vol_up pwr+vol_down pwr+Vol_up+Vol down... I try ADB, fastboot and its not working.
I have S-ON
How to fix it? :")
Hanataji said:
Hello... Today i replace my battery. I lost all sensors. I have a brilliant idea, wipe all, system etc. reboot and BAM! HTC Logo loop... I try pwr+vol_up pwr+vol_down pwr+Vol_up+Vol down... I try ADB, fastboot and its not working.
I have S-ON
How to fix it? :")
Click to expand...
Click to collapse
You wiped system, which is the OS. So of course, you have no OS to boot to, now.
I assume you did this in TWRP. Any previously created TWRP backup to restore?
adb will only work in OS (which you don't have of course) and TWRP, and if debugging is enabled. Fastboot will only work in bootloader-fastboot mode (debugging not required to be enabled). So neither adb nor fastboot can be expected to work "stuck" on the HTC logo screen.
Hold power+vol up for a minute or so (I'm guessing you just didn't hold that combination long enough), until the screen goes dark, meaning it is about to reboot. The moment the screen goes dark (but before the HTC logo screen appears again), let go of those buttons, and only hold vol down. This should boot you to bootloader, where you can then use fastboot, or boot recovery. If you fail to see the bootloader screen, it is almost certainly a matter of you just not getting the timing right. You either started pressing vol down too late, or let go of it too early. Just repeat the process, until you get it right.
Related
I had CM7, S-OFF, CM7 r2 HBOOT I was at home, didn't touch pfone all night, and in the morning, after a call, back key stoped working. I tryed to restart phone, and it went to fastboot. I figured back button was stuck and i pushed back button so it maybe start working, but it didn't. It would always boot to fastboot, and volume keys are not working.
So, i disasembled the phone, took the buttons board out, and it still booted to fastboot.
Then i managed to turn the phone on, via CMD, using command fastboot reboot, and from menu, i rebooted to recovery, made backup and flashed CM7 again.
That didn't work.
In recovery, i tryed key test, back and search button were not working.
I returned everything to stock, still nothing.
I can only start the phone via fastboot reboot...
Help please...
Certainly sounds like back button is stuck down. Did you void your warranty by taking it apart or was it already void?
Sent from my HTC Desire using Tapatalk
No i don't have a warranty...
But i don't understand, if it is stuck, why does it start in fastboot, when i remove the button board...
It's stuck somewhere. To get to fastboot you have to hold back and press power...
Has the phone been wet recently?
Sent from my HTC Desire using Tapatalk
Maybe from tho cold, or moisture...Because of very low temps here, there was a lot of snow, and the phone was in the room with moisture...?
Wouldn't expect that to be enough. Maybe prudent to get a phone shop to look over it...
Sent from my HTC Desire using Tapatalk
That is my last solution...
try
Code:
fastboot oem boot
worked for me while holding back
if you don't have fastboot setup then unzip the file into c:\ and use the following
Code:
cd\
fastboot oem boot
What can i manage with that command?
I have fastboot, and with that command, i can start the phone, but i can do it also with fastboot reboot.
And when i restart the phone it goes to do fastboot, volume keys are not working...
Moca87 said:
What can i manage with that command?
I have fastboot, and with that command, i can start the phone, but i can do it also with fastboot reboot.
And when i restart the phone it goes to do fastboot, volume keys are not working...
Click to expand...
Click to collapse
Exactly.. you can turn on the phone, I thought this was your ultimate goal to do, doesn't fix anything.. just telling you that you can get it started that way.
Have you tried putting it in a bag of rice yet? if it is water damage it might help.
No, i haven't tried that. I put it on radiator, that's not very worm, and it's working, but it's not ok.
It can turn on normaly, but sometimes it's like, back button is pressed continuously and sometimes same thing happen with search button...
Hi guys
I've got a desire Hd, over 2 years old now so out of warranty. Not rooted, Android 2.3.5 (official ROM), Middle East ROM and relocked.
When i turn it on,After a minute or less, when it would normally show an android screen, the screen goes to bootloader. and when I wanna reboot it or enter to the recovery , the screen goes blank but the phone is still on, and the screen is still on but in a very dark grey. if you hold it on an angle the backlight appears to be on. But from that point nothing happens, the buttons no longer respond, and I have to remove the battery to turn it off.
Although I've tried to reset factory my phone but it didn't work and the screen goes blank again when the backlight is still on.
Thanks for your help.
PLease help me asap.
did u ever experience this problem?
What did you do to get it in this state?
bananagranola said:
What did you do to get it in this state?
Click to expand...
Click to collapse
nothing much. I've just removed the battery many times, because the Volume down didn't respond and I wanted to enter to the bootloader!!
any solution?!! :crying:
try this:
What happens after putting battery back whitout pressing the ON-Button?
If it's still off, try pressing once ON-Button AFTER holding Volume-UP till HBOOT comes... maybe your phone need that
OR:
Connect the phone (when its off) to PC. Then turn phone on. Flash the boot.img over PC with fastboot.exe (only boot.img, not hole ROM). I had the same troubles with every ROM i tried, i had to flash it manually.
ammo12 said:
try this:
What happens after putting battery back whitout pressing the ON-Button?
If it's still off, try pressing once ON-Button AFTER holding Volume-UP till HBOOT comes... maybe your phone need that
OR:
Connect the phone (when its off) to PC. Then turn phone on. Flash the boot.img over PC with fastboot.exe (only boot.img, not hole ROM). I had the same troubles with every ROM i tried, i had to flash it manually.
Click to expand...
Click to collapse
Does it needs any RUU to do this or the boot.img is already exist in my phone?! (my phone is S-ON and relocked)
and what's the exact command to flash boot.img not the whole ROM?
Transporter2009 said:
Does it needs any RUU to do this or the boot.img is already exist in my phone?! (my phone is S-ON and relocked)
and what's the exact command to flash boot.img not the whole ROM?
Click to expand...
Click to collapse
Once you're in the bootloader, and assuming your computer has the correct drivers and img files, type in CMD:
"fastboot flash boot boot.img"
I think I'm in a worse condition than you. My phone won't even boot into bootloader, have tried all the hardware keys (Vol+-, Home, Back, Menu) with Power button. I have even tried taking the volume cable out and pressing the buttons directly but my phone still goes into the boot animation and then blank screen with backlight on. My computer is also not recognizing the phone so adb doesn't work. I'm out of ideas, anyone got any?
cherhunghow said:
Once you're in the bootloader, and assuming your computer has the correct drivers and img files, type in CMD:
"fastboot flash boot boot.img"
I think I'm in a worse condition than you. My phone won't even boot into bootloader, have tried all the hardware keys (Vol+-, Home, Back, Menu) with Power button. I have even tried taking the volume cable out and pressing the buttons directly but my phone still goes into the boot animation and then blank screen with backlight on. My computer is also not recognizing the phone so adb doesn't work. I'm out of ideas, anyone got any?
Click to expand...
Click to collapse
I did it but unfortunately I faced with this Failure:
Code:
C:\Android>fastboot flash boot boot.img
sending 'boot' (2840 KB)... OKAY
writing 'boot'... INFOsignature checkin
FAILED (remote: signature verify fail)
what should I do then?? :crying:
and about your problem i think the Volume Key is the problem and it can be fix by replacing the volume key or even with a simple cleaning. don't worry
Would love some help, please. I have a completely stock HTC One M8 for Sprint. Last night I plugged in the phone to the AC charger (still had ~70% charge) and went to sleep. This morning the charge indicator was green as usual, but pressing the power button did nothing. Unplugged the phone from the charger and the LED remained green.
Tried press-hold power button for 10 seconds: no effect.
Tried press-hold power button and volume down. Select HBOOT, then RECOVERY. The phone vibrates and shows me the skateboarding androids, then reverts to the FASTBOOT menu.
Tried press-hold power button and volume down. Select HBOOT, then FACTORY RESET. The phone vibrates and shows me the skateboarding androids, then reverts to the FASTBOOT menu.
Tried requesting an Unlock_code.bin from HTCDev, then use fastboot to flash that. I see the transfer bar on my phone for an instant, but otherwise the display does not change. Still indicates *** LOCKED *** even though the fastboot command returned "OKAY".
Tried using abd.exe to list devices - none listed. Though fastboot.exe does return my serial number.
:fingers-crossed: Tried pres-hold power+volUP+volDWN for 2 minutes. Phone booted as normal, I swiped my unlock on the touchscreen, HTC Sync saw my phone, then the screen went black and I couldn't get it to boot. Sorry I did not notice what charge level the battery was in the GUI for the ~10 seconds the phone was on.
S-On
HBOOT-3.16.0.0000
RADIO-INVALID_VER_INFO
OpenDWP-INVALID_VER_INFO
OS-1.54.651.8
update - still won't boot, but ...
Update: still won't boot, but now I can get recover mode to run. Tried wiping cache partition and rebooting. Now it boots to the HTC (android) logo, then the Sprint animation plays, then the HTC One animation plays, though the audio portion only plays for the 1st second and cuts off suddenly. Then it just hangs there forever. I left it for an hour at that point just to make sure it wasn't booting really slowly.
Any way to boot from something on an SD card so that I can at least get my userdata partition backed up?
astaples said:
Update: still won't boot, but now I can get recover mode to run. Tried wiping cache partition and rebooting. Now it boots to the HTC (android) logo, then the Sprint animation plays, then the HTC One animation plays, though the audio portion only plays for the 1st second and cuts off suddenly. Then it just hangs there forever. I left it for an hour at that point just to make sure it wasn't booting really slowly.
Any way to boot from something on an SD card so that I can at least get my userdata partition backed up?
Click to expand...
Click to collapse
Sorry to say this, but all your data is gone since you factory reset from bootloader, that always wipe your phone. What recovery you had when you pressed it, if it was custom like trwp your internal sd is more likely corrupted. The easier option to get the phone back to working state is to run ruu if there is any for Sprint.
tominozh said:
...all your data is gone since you factory reset from bootloader, that always wipe your phone. What recovery you had when you pressed it, if it was custom like trwp your internal sd is more likely corrupted.
Click to expand...
Click to collapse
Thanks for the reply. Actually I listed my attempted fixes in order... i.e. I was able to get the phone to boot once for a few seconds - long enough to see my personal home screen and photos - after I had clicked on that factory reset option.
I have a theory. The RAM is bad. That would explain why sometimes it will partly boot and then get stuck, other times it will get stuck in a bootloop to the fastboot menu, and other times (only one time so far) it will completely boot. Also, if I go to the RAMDUMP option, at the bottom of that screen it shows mostly non-ASCII characters and vibrates every ~5 seconds. If I go to IMAGE CRC, it sometimes instantly shows 0x0 next to each device, other times takes a while to calculate believable values for each, and other times won't display anything and freezes.
Think that's plausible? Suppose there is any way to boot from sdcard and retrieve my userdata partition? I did not have a sdcard in when this originally happened, so all my family photos are in userdata and I haven't backed up since my 4-year old's birthday party last weekend.
Any way to get my userdata off this phone, or do an in place upgrade without hosing m
Anyone? Help?
I recently replaced my Cracked Screen on a Verizon m8. I was on a custom rom with twrp installed. After the initial boot, I was having problems with a speaker and went to try to boot to the bootloader to do a RUU, when I noticed that I can no longer access the bootloader screen. It was then when I noticed that not even my computer was recognizing the phone no more. It's as if the phone won't debug no more. I can still access my TWRP by rebooting straight to recovery thru a app or the apm it has on the custom rom im using. I've tried to flash other roms with no success to get access to these two things. I was wondering if anyone had a stock twrp of Verizon version. As for all my twrp are from custom roms. Or if anyone has had this problem before or if any suggestions im open to anything to try and get to the bootloader screen. It also doesn't even boot the two or 3 second boot up screen until you get to the roms boot up screen. It also doesn't goto the bootloader screeen when it try's to access the bootloader. Even when booting straight to recovery stays black until twrp actually shows up. So it's as if bootloader is completely being bypassed. You cant use the volume keys to access the recovery cause everything is blank. Although on first attempt to access bootloader screen when I was stuck there in black. I had to figit the keys a bunch of times to reboot, hoping that I didn't activated something in that screen that caused the phone not to debug. Any suggestions is more then welcome and if someone has a stock twrp of recent stock rom 4.605.9 I believe it is would be more then great. Cant find one other then in zip or exe version. Hoping maybe that might reactivate those two things. Thanks for taking the time to read my problem.
Debugging or adb works within OS, and its not a mode in itself. I think you mean you can't access bootloader-fastboot mode.
Casetheace said:
I was wondering if anyone had a stock twrp of Verizon version. As for all my twrp are from custom roms.
Click to expand...
Click to collapse
You mean stock recovery. TWRP is a specific custom recovery, therefore always a custom one.
I don't think stock recovery will change anything. Bootloader is on a completely different partition.
Its odd that you can't access bootloader. It must still abe intact, otherwise the phone would not work at all.
Did you try (in OS): adb reboot-bootloader
Are you s-off or s-on?
The phone is S off. I was able to get the phone to USB debug. I took it out of the shell and plugged in the USB cord and it debug instantly . So I'm guessing with that I had to damage something when I either took the phone out of the shell originally or when I replaced the screen. Cause you literally have to take every piece of the phone off and then reasamble the phone from scratch. Once i put the phone back in shell, i couldnt get it to usb debug no more. But I still can't access the bootlader, nor is the first boot screen on power up before the main boot up screen starts. Also has no display if I reboot to recovery using a app from the phone. You don't see the screen where the red text would show up saying rebooting to recovery, display starts when it begins to show twrp on display. But when I had the shell off, and was able to access USB debug, I was able to use adb commands from my computer from fastboot mode , but phone had no display. Was able to run a RUU, was able to use adb to reboot to boot loader, then was able to fastboot get varall command. Even flashed a twrp recovery install in fastboot under command prompt . So that tells me that the boot loader is operational. That it has to be some sort of power failure in booting that nots powering the display on initial boot for 2 to 3 seconds , no power on bootliader display, no power rebooting to boot loader or rebooting to recovery until it boots recovery. Any ideas what would cause this failure of power of display during boot loader processes? By the way , have twrp 2.87 . Its a Verizon build, but I'm on a T-Mobile sim.
I've installed live boot and attached a log. If anyone can help or maybe know why this might happen. Believe there is two boots, each with a separate power. Main boot is the initial power up last two or three seconds, and then system boot.. Believe main boot is sending power off display and then power on display on system boot.
Hello,
my friend gave me his HTC Desire 816 to fix it. Phone originally boots up in fastboot mode, but very slow and unresponsive. To describe it, when I push the power button to turn it on, only after 30 seconds the androids on skateboard image shows up and it takes approx 20 secs to get in fastboot. Then again, it has laggy menu in fastboot and I tried to do factory reset but after hitting it, it only shows androids on skateboards again only for few seconds then just turns off.
Phone has bootloader locked and It canno't boot normally.
Please help me and my friend.
Thanks community, you are the best!
Bump!
Try the htcdev unlock process and see if it works.
If so you should be able to put twrp 3.1.0.0 on it.
You can also try to
fastboot boot recovery.img
Replace recovery.img with whatever the exact filename is for the a5 twrp