Related
Not sure why, but I restarted my phone today and now it just gets stuck at fastboot. None of the buttons work. If I take the battery out and put it back in it will just immediately reboot. I can't get it to stay off with the battery in.
If I plug it in, I can recognize the device using fastboot, and if I reboot the device using fastboot reboot I can get it to start properly, but none of the buttons are working. Power, Volume, Menu, Home, Back and Search all don't work. The OJ works, but pressing the button down does nothing.
I've tried flashing an RUU but it says it can't find the device. I can't get it to show up in ADB either, and even though USB Debugging is enabled, I don't get the notification that says it does.
Any ideas on what I can do?
If I hold power+volume down when I put the battery in it will switch to hboot, and I can get it back to fastboot with power+back, so the buttons should be working.
Can't you just run RUU when your in hboot or fastboot? If you can get to hboot surely you can go recovery, then you can use an RUU for defo since it should come up as being connected. Unless you have further issues.
I can get to hboot, but none of the buttons respond, so I can't get to recovery.
I managed to get a Telus RUU working from fastboot.
Now I'm using the 0.93 HBOOT, but nothing is working.
It won't boot into Android now though. My question is, since I flashed the official RUU am I still rooted? The phone is still under warranty, so I'm go to see what I can do about getting it repaired.
No, installing an RUU will remove root and wipe everything on the phone. I also believe that it changes it back to s-off, so if you sent it for repair as it is it should be fine
Sent from my HTC Desire using XDA App
Was trying to switch from TWRP to CWM (having trouble with TWRP installing CM nightlies). I installed the latest CWM via fastboot. Seemed to load OK, but when I tried to start up the recovery, it just rebooted after showing 'Entering Recovery...' in pink at the top.
Now I'm really stuck. No matter what I do, the phone starts up, shows Entering Recovery at the top, and then shuts down. I cannot enter the bootloader. I cannot start up the phone into the ROM (which is a TikTak ROM that was working fine). Basically, I'm unable to do anything.
When the phone is plugged in, no orange charge light comes on. Vol Down + Power doesn't work. Vol Up + Power doesn't work. Either way, the phone tries to enter recovery, then shuts down.
Is there anything else I can try? Is this phone bricked?
What was the fastboot command you did? It sounds like you flashed to the wrong partition, or flashed an m7 recovery instead of an m7wlv
Sent from my HTC6500LVWBLU using XDA Free mobile app
Uzephi said:
What was the fastboot command you did? It sounds like you flashed to the wrong partition, or flashed an m7 recovery instead of an m7wlv
Sent from my HTC6500LVWBLU using XDA Free mobile app
Click to expand...
Click to collapse
fastboot flash recovery <cwm.zip> (whatever it was called)
Same way I did it for TWRP which worked perfectly.
Really need a solution here, if there is one. Currently planning on just letting the battery drain and starting again...
mobilemedic20 said:
fastboot flash recovery <cwm.zip> (whatever it was called)
Same way I did it for TWRP which worked perfectly.
Really need a solution here, if there is one. Currently planning on just letting the battery drain and starting again...
Click to expand...
Click to collapse
If you can't get a charge light while it is off, DO NOT let it die! It will not charge while dead. When it is booting, can you do adb or fastboot commands from your PC? If so, try:
ADB/fastboot reboot bootloader
Sent from my HTC6500LVWBLU using XDA Free mobile app
Usually, the command: fastboot erase cache
Will resolve such issues, though it doesn't always work, depends on what's causing the actual issue.
But that is what I would suggest trying from fastboot.
Problem is I can NOT get into the boot loader at all, unless i'm missing something. Start phone, tries to load recovery, shuts off. That's it. Is there a way to get the bootloader to open? I seem to have no options.
mobilemedic20 said:
Problem is I can NOT get into the boot loader at all, unless i'm missing something. Start phone, tries to load recovery, shuts off. That's it. Is there a way to get the bootloader to open? I seem to have no options.
Click to expand...
Click to collapse
With device powered off,
Power + volume down
Even if partially powered on, trying to load recovery,....
Same process, hold volume down and power until it boots to hboot.
santod040 said:
With device powered off,
Power + volume down
Even if partially powered on, trying to load recovery,....
Same process, hold volume down and power until it boots to hboot.
Click to expand...
Click to collapse
Tried it man, vol down + power as much as you want. It starts, tries to enter recovery (for about 3 seconds) then goes dead. The thing is, even with the screen off and I plug it into the computer, the computer recognizes the phone a little... It says 'driver not recognized' (even though they're installed). So maybe it's actually partially on in the background, and locked up? That's why I'm hoping the battery running down will fix it.
I'm literally dusting off my old galaxy nexus to get that loaded up, because I need my phone. I'm worried the One is bricked.
***Edit / update - when I plug the phone in 'off' (not responsive) mode, and try fastboot anything, it hangs saying 'waiting for device'. Whatever that means.
mobilemedic20 said:
Tried it man, vol down + power as much as you want. It starts, tries to enter recovery (for about 3 seconds) then goes dead. The thing is, even with the screen off and I plug it into the computer, the computer recognizes the phone a little... It says 'driver not recognized' (even though they're installed). So maybe it's actually partially on in the background, and locked up? That's why I'm hoping the battery running down will fix it.
I'm literally dusting off my old galaxy nexus to get that loaded up, because I need my phone. I'm worried the One is bricked.
***Edit / update - when I plug the phone in 'off' (not responsive) mode, and try fastboot anything, it hangs saying 'waiting for device'. Whatever that means.
Click to expand...
Click to collapse
You are holding down on both the volume down and the power button for as long as your fingers can stand to?
It's not a quick press of both, but a steady hold down of both buttons, even if it tries to do the recovery loading , keep holding both down.
Make sure you are pressing them both FIRMly and for at least 30 seconds or more.
If you are already trying that, then disregard.
But the way it's behaving, it doesn't sound like you are.
If so, again, disregard, just making sure you are attempting one of the only possible methods you have, correctly.
As it won't do what it's supposed to if you do not continue to hold them down, even if that entering recovery screen comes up, you need to continue holding them down.
santod040 said:
You are holding down on both the volume down and the power button for as long as your fingers can stand to?
It's not a quick press of both, but a steady hold down of both buttons, even if it tries to do the recovery loading , keep holding both down.
Make sure you are pressing them both FIRMly and for at least 30 seconds or more.
If you are already trying that, then disregard.
But the way it's behaving, it doesn't sound like you are.
If so, again, disregard, just making sure you are attempting one of the only possible methods you have, correctly.
As it won't do what it's supposed to if you do not continue to hold them down, even if that entering recovery screen comes up, you need to continue holding them down.
Click to expand...
Click to collapse
Yes, that's what I've been doing - and if I hold it down for a longer time, the phone will just cycle through. Off, "Entering recovery", off, "entering recovery", etc every 10 seconds or so. It's clearly not working.
mobilemedic20 said:
Yes, that's what I've been doing - and if I hold it down for a longer time, the phone will just cycle through. Off, "Entering recovery", off, "entering recovery", etc every 10 seconds or so. It's clearly not working.
Click to expand...
Click to collapse
Well that's too bad. Sorry to hear you're having these issues.
I noticed in your first post in this thread, you said you did this:
fastboot flash recovery cwm.zip
Was the file actually a zip?
It should have been a .img file.
Just trying to figure out what happened, as it could help in finding a resolution.
As it stands right now, there is nothing really to go off of.
Anyone, still trying to recover my phone... Here's where I'm at. I figured out that while the phone is off, if I plug it in, I can access ADB via the computer's cmd prompt, but no fastboot (says 'waiting for device'). If I use ADB to reboot the bootloader or recovery, I get the same problem - phone resets, tries to enter recovery for 2 seconds, then back off again.
Can I somehow use ADB to get the phone working again?
mobilemedic20 said:
Anyone, still trying to recover my phone... Here's where I'm at. I figured out that while the phone is off, if I plug it in, I can access ADB via the computer's cmd prompt, but no fastboot (says 'waiting for device'). If I use ADB to reboot the bootloader or recovery, I get the same problem - phone resets, tries to enter recovery for 2 seconds, then back off again.
Can I somehow use ADB to get the phone working again?
Click to expand...
Click to collapse
If you borked your boot loader where you can't access it, there isn't much we can do to help. If the phone can't boot to the boot loader, we can't do anything to help. I think the only thing you can do is send it in for JTAG.
Sent from my One using XDA Free mobile app
Uzephi said:
If you borked your boot loader where you can't access it, there isn't much we can do to help. If the phone can't boot to the boot loader, we can't do anything to help. I think the only thing you can do is send it in for JTAG.
Sent from my One using XDA Free mobile app
Click to expand...
Click to collapse
'Send it in for JTAG'... sorry, what does this mean?
I'm also going to try bringing it to Verizon and claiming ignorance to see if I can get a warranty replacement. What's the downside, right?
adb shell
dd if=/sdcard/LOCATIONOFHBOOT/HBOOT.img of=/dev/block/nameofblock
should work, but i have no clue what the hboot block name is and that this way is really risky. Maybe a dev can chime in and help.
http://forum.xda-developers.com/showthread.php?t=2320271
maybe pm this guy for help?
synisterwolf said:
adb shell
dd if=/sdcard/LOCATIONOFHBOOT/HBOOT.img of=/dev/block/nameofblock
should work, but i have no clue what the hboot block name is and that this way is really risky. Maybe a dev can chime in and help.
http://forum.xda-developers.com/showthread.php?t=2320271
maybe pm this guy for help?
Click to expand...
Click to collapse
Appreciate the suggestion but have no idea how to proceed with this. Read that link, even more clueless.
Hello,
My friends own an htc m8. A non professional lab has flashed him Android Revoultion Rom (without making a wipe, he used to use stock rom before that)
Since than the device suffer from a lot of problem,we would like to flash a stock rom.
What's the problem? the device refuses to go into bootloader at all & than refuses to turn on, only after a while in the charger it does turn on.
But any attempt to make the device go into the bootloader, has failed.
tried also RUU - it won't load the bootloader, and the pc recognize him as QHSUSB_BULK if the device is off, which is soft brick as far a i know.
The device actually turn on after a while, than when i connect it to the PC, the pc does recognize him normally.
What's the best option to flash a recovery and a stock rom?
Thank you.
efi2222 said:
Hello,
My friends own an htc m8. A non professional lab has flashed him Android Revoultion Rom (without making a wipe, he used to use stock rom before that)
Since than the device suffer from a lot of problem,we would like to flash a stock rom.
What's the problem? the device refuses to go into bootloader at all & than refuses to turn on, only after a while in the charger it does turn on.
But any attempt to make the device go into the bootloader, has failed.
tried also RUU - it won't load the bootloader, and the pc recognize him as QHSUSB_BULK if the device is off, which is soft brick as far a i know.
The device actually turn on after a while, than when i connect it to the PC, the pc does recognize him normally.
What's the best option to flash a recovery and a stock rom?
Thank you.
Click to expand...
Click to collapse
There is definately some information missing here. Flashing a ROM without wiping will never get you into this state, unless maybe the ROM was meant for a different device.
It sounds more like a deleted bootloader partition, or borked eMMC.
It's bricked. You need to take it to a shop to see if they can JTAG it back to life.
Sorry.
xunholyx said:
There is definately some information missing here. Flashing a ROM without wiping will never get you into this state, unless maybe the ROM was meant for a different device.
It sounds more like a deleted bootloader partition, or borked eMMC.
It's bricked. You need to take it to a shop to see if they can JTAG it back to life.
Sorry.
Click to expand...
Click to collapse
Hey,
We don't know what they have done exactly
They device does turn on after a while... Can i just flash the whole bootloader through the computer anyhow? If the device is on, the computer does recognize him and i can use adb/transfer files.
In a few minutes when the device will turn on i'll write the software information
Edit:
Android version 6.0
HTC Sense Version 7.0
Software number Android Revoultion 51.0 by mike1986
kernel version: 3.4.0-perf-g708019f
[email protected] #1
SMP PREEMPT
baseband version: 1.25.2145000021.06_20.68.4196t.01_F
build number: 6.12.1540.4 CL662736 release-keys
forgot to mention WIFI and BT does not work. went to phone identify and wifi mac ddress if 02:00:00:00:00:00 and bluetooth address is: Unavailable
Thank you
efi2222 said:
Hey,
We don't know what they have done exactly
They device does turn on after a while... Can i just flash the whole bootloader through the computer anyhow? If the device is on, the computer does recognize him and i can use adb/transfer files.
In a few minutes when the device will turn on i'll write the software information
Edit:
Android version 6.0
HTC Sense Version 7.0
Software number Android Revoultion 51.0 by mike1986
kernel version: 3.4.0-perf-g708019f
[email protected] #1
SMP PREEMPT
baseband version: 1.25.2145000021.06_20.68.4196t.01_F
build number: 6.12.1540.4 CL662736 release-keys
forgot to mention WIFI and BT does not work. went to phone identify and wifi mac ddress if 02:00:00:00:00:00 and bluetooth address is: Unavailable
Thank you
Click to expand...
Click to collapse
Have you tried turning off the phone, and booting it by holding down power + vol down? That should take you to bootloader. It's not bricked if you can boot it.
Tried that already...Doesn't work. The device refused to turn on that way.
Tried also through adb/an app when the device was on (yeah it's rooted), than the device turned off and the computer see it as QHSUSB_BULK.
Than i have to plug it off the pc, connect to AC and after a while it's just turn on by itself....
efi2222 said:
Tried that already...Doesn't work. The device refused to turn on that way.
Tried also through adb/an app when the device was on (yeah it's rooted), than the device turned off and the computer see it as QHSUSB_BULK.
Than i have to plug it off the pc, connect to AC and after a while it's just turn on by itself....
Click to expand...
Click to collapse
Not sure about this. If you didn't have a bootloader, I don't think your phone would boot at all.
It does boot, but not normally.
Anyway, there's no way of getting into bootloader
Did you enable developer options and within those option check USB debugging, so it's enabled. If not got to "settings > about > software information > more" and tab the build number entry several times until you get prompt the developer options have been enabled. Then got to developer options and check USB debugging. Try running the RUU again. Many this already works. Otherwise we'd have to look further.
Send by the swarm intelligence of my coffee machine ?.
I hgve already enabled dev options. once the ruu tries go get into the bootloader, the device just turn off and i can see on pc device manager it's QHSUSB_BULK
efi2222 said:
It does boot, but not normally.
Click to expand...
Click to collapse
Meaning what, specifically? Stuck on HTC logo screen, or something else?
As long as the screen is on (on any screen), you can:
1) Hold Power + vol up for 20-30 second, which will force a reboot.
2) The moment the screen goes dark, let go of those buttons, and only hold vol down. Don't let go until the bootloader appears.
redpoint73 said:
Meaning what, specifically? Stuck on HTC logo screen, or something else?
As long as the screen is on (on any screen), you can:
1) Hold Power + vol up for 20-30 second, which will force a reboot.
2) The moment the screen goes dark, let go of those buttons, and only hold vol down. Don't let go until the bootloader appears.
Click to expand...
Click to collapse
Tried that yesterday but i have tried that again right now.
Does not work....doesn't load bootloader and the screeen remains black. Brick....
efi2222 said:
Tried that yesterday but i have tried that again right now.
Does not work....doesn't load bootloader and the screeen remains black. Brick....
Click to expand...
Click to collapse
I'm still confused about what you are describing, and I think others trying to help are confused also.
You said the phone boots, but not normally. I asked what that meant specifically (which you did not answer at all). Stuck on HTC screen?
So the screen is on, when you try the button sequence I suggested? Then when the screen goes black to reboot, it just stays black?
Hard to help, if you don't provide details and specifics.
The phone boot and you can use it, that's how i have provided information from the settings. If i try to reboot, the device does not turn on. only after about 5 minutes.
same for bootloader. if you try to get into bootloader from adb for example, than there is only a black screen and after a few minutes it's just load the OS normally. but no bootloader.
efi2222 said:
Tried that yesterday but i have tried that again right now.
Does not work....doesn't load bootloader and the screeen remains black. Brick....
Click to expand...
Click to collapse
So if you try the button combo I suggested, it eventually boots to OS? Are you still holding vol down when it boots to OS? If not, you should be (and let go too early).
---------- Post added at 01:28 PM ---------- Previous post was at 01:28 PM ----------
efi2222 said:
if you try to get into bootloader from adb for example, than there is only a black screen and after a few minutes it's just load the OS normally. but no bootloader.
Click to expand...
Click to collapse
What's the exact adb command? I'm sure you probably have it right, but just want to confirm.
It doesn't boot when i try the button combo... and after a few minutes it boot to OS.
also tried though an app because the device is rooted.... and also through RUU. The RUU restart the device and should make him to go into bootloader but it failes doing it.
adb reboot-bootloader
when the device is turned off the pc only see it as QHSUSB_BULK
efi2222 said:
It doesn't boot when i try the button combo... and after a few minutes it boot to OS.
Click to expand...
Click to collapse
It still really confusing how you are phrasing things "It doesn't boot . . . after a few minutes it boot"
Either it boots (just takes a long time; or boot OS, but not bootloader) or it doesn't.
Holding power + vol down makes it shutdown, right? Once the screen goes dark, hold only vol down and don't stop until you either see bootloader or the OS loads. Its not clear from the way you've typed it, but it sounds like you are pressing vol down for a while, then give up and let go, then it eventually loads OS.
I understand that it doesn't look like it wants to boot into bootloader, from any method. But we really need to eliminate all possibilities and be sure you can't do it with the button combo.
Its really unusual to see a device that can boot into OS, but not go into bootloader at all. I've never seen this once, after being on these forums extensively over the course of 4 different HTC Android devices.
redpoint73 said:
It still really confusing how you are phrasing things "It doesn't boot . . . after a few minutes it boot"
Either it boots (just takes a long time; or boot OS, but not bootloader) or it doesn't.
Holding power + vol down makes it shutdown, right? Once the screen goes dark, hold only vol down and don't stop until you either see bootloader or the OS loads. Its not clear from the way you've typed it, but it sounds like you are pressing vol down for a while, then give up and let go, then it eventually loads OS.
I understand that it doesn't look like it wants to boot into bootloader, from any method. But we really need to eliminate all possibilities and be sure you can't do it with the button combo.
Its really unusual to see a device that can boot into OS, but not go into bootloader at all. I've never seen this once, after being on these forums extensively over the course of 4 different HTC Android devices.
Click to expand...
Click to collapse
Yes, Holding power + vol down makes it shutdown. After the screen goes dark, i tried to hold only vol down. nothing happends. tried to hold it for a few minutes. nothing.
When i release it, only after a few minutes, the device load the OS by itself (if i try to press the power button it doesn't work at all)
efi2222 said:
When i release it, only after a few minutes, the device load the OS by itself
Click to expand...
Click to collapse
So how do you know whether releasing the button is a condition of it booting, or a coincidence?
For that matter, how do you know it won't go to bootloader if vol down is held when it finally powers on?
I'd say the answer to both those questions is: you don't know. At least, not for sure.
How long is a "few minutes"? 3 minutes? 10 minutes?
Maybe hold down the vol down button with some tape, if you can hold it down manually the whole time?
It's doesn't really Matter, as the adb/ruu/quick bot app should have be able to load the bootloader....
efi2222 said:
It's doesn't really Matter, as the adb/ruu/quick bot app should have be able to load the bootloader....
Click to expand...
Click to collapse
It does matter. As I already explained, you should eliminate all possibilities. At least I assume that someone who genuinely want to fix the phone would try every possibility.
You spent about as much time replying, as it would have taken to try my suggestion.
I agree, I don't think it will work. But you don't know if you don't try.
when i boot up my device it goes strait to the screen where u
boot to bootloader
boot to download mode
boot to recovery mode
ddr test
powerdown
when i select either except power down
it just boots back to the before mentioned white bootloader screen
i also tried 0PJAIMG.ZIP and put it in SDCard
i am s-off unlocked ---is it fixable or done for
(HTC M9 Verizon [ROM] Fluent ROM v4.0.0 -- Marshmallow 3.37.605.7 --
the Guy where i got it
said it happened
while ruu to
take off red letter boot warning where it gets to( flush
again immediately)----- it happened
Dayliter said:
when i select either except power down
it just boots back to the before mentioned
Click to expand...
Click to collapse
To clarify, are you saying that selecting any of the options except 'Power Down' cause you to reboot back into download mode?
computerslayer said:
To clarify, are you saying that selecting any of the options except 'Power Down' cause you to reboot back into download mode?
Click to expand...
Click to collapse
boot to bootloader white screen only if i slect boot to download it reboots to white bootloader screen everytime
Well, you've already tried RUU via sdcard. From your choice of ROM, it looks like you're using a Verizon-branded device - is that correct?
It may be worth connecting your phone to a PC and attempting to repair your phone using Verizon's Software Upgrade Assistant (start with HTC's Sync Manager) to repair the phone. Verizon provides instructions on it's website.
Assuming this works - and that's a bit of a long shot, given your symptoms - you'll almost certainly be returned to a S-ON state. If your phone is currently non-functional, that seems worthwhile but you'll have to make that decision.
HTC's Sync Manager come up auto when phone gets connected but cant get phone to connect to it good idea tho-i will leave it hooked awhile mabe it will --------
Dayliter said:
HTC's Sync Manager come up auto when phone gets connected but cant get phone to connect to it good idea tho-i will leave it hooked awhile mabe it will --------
Click to expand...
Click to collapse
I have a very similar problem. My phone is Unlocked and S-OFF. I tried to install TWRP after I had gone back to a standard rom. When I went to recovery it boot looped. To get back to bootloader I have to hold volume up and down if I try to go to download mode it boot loops if I power down with whilst connected to the computer it boot loops. I have tried to install a standard rom but get partition errors "remote: partition table doesn't exist". Does anyone have any Ideas?
I was at work the night before, and my capacitive buttons stopped responding, so I went for a restart in hopes they would kick back on, this just caused my phone to enter a boot loop. Soft resetting and hard resetting both continue the loop, trying to enter recovery mode throws me back into the loop, entering download mode locks the phone on the small HTC screen. I tried to flash the current RUU onto the phone, but it won't proceed with the install due to a low main battery error despite the fact I've had it charging for 6 hours. The only thing I can think of doing now is sending it back in hopes they fix it, but theres a lot of information I ignorantly haven't backed up, and now can't access before sending it back.
If anyone has any helpful tips or ways to move forward I would be grateful.
you might be able to intervene in the process. when the phone restarts (ideally right after it restarts), hold Volume Down until the grey HTC logo appears, From here, you are in the download menu (or what is now basically the fastboot). If you are stock, you can unlock the bootloader if you havent already and flash a custom recovery (TWRP). Being in TWRP will give you USB access to your phone. And it will provide the ability to flash ROMs, including stock ROMs. Beyond that, you could always try a factory reset from either the download or the bootloader, but not much else I think you can do.
Someone might have more information than me though
silegeek said:
you might be able to intervene in the process. when the phone restarts (ideally right after it restarts), hold Volume Down until the grey HTC logo appears, From here, you are in the download menu (or what is now basically the fastboot). If you are stock, you can unlock the bootloader if you havent already and flash a custom recovery (TWRP). Being in TWRP will give you USB access to your phone. And it will provide the ability to flash ROMs, including stock ROMs. Beyond that, you could always try a factory reset from either the download or the bootloader, but not much else I think you can do.
Someone might have more information than me though
Click to expand...
Click to collapse
Doing what you said flashes the grey HTC logo, but then goes back to looping.
Snickie12 said:
Doing what you said flashes the grey HTC logo, but then goes back to looping.
Click to expand...
Click to collapse
Try the same thing, but this time with Volume Up, hold it until the FTM menu appears. From here, you should be able to access the bootloader.
If that also does not work holding Volume Up and Down at the same time takes you straight into the bootloader. Sadly, unless you are S-OFF, there is not a lot you can do from this menu. I dont think it accepts the fastboot commands, particularly fastboot flash commands. But if you can get into the bootloader, and then try each option, download, recovery, etc.
If you get into the recovery, it will be stock (unless you flashed a custom ROM). You have to press volume up twice to access the options, but if you get stuck, hold volume down and power and the touch keys on the bottom flash. After about 15 flashes the phone reboots.
silegeek said:
Try the same thing, but this time with Volume Up, hold it until the FTM menu appears. From here, you should be able to access the bootloader.
If that also does not work holding Volume Up and Down at the same time takes you straight into the bootloader. Sadly, unless you are S-OFF, there is not a lot you can do from this menu. I dont think it accepts the fastboot commands, particularly fastboot flash commands. But if you can get into the bootloader, and then try each option, download, recovery, etc.
If you get into the recovery, it will be stock (unless you flashed a custom ROM). You have to press volume up twice to access the options, but if you get stuck, hold volume down and power and the touch keys on the bottom flash. After about 15 flashes the phone reboots.
Click to expand...
Click to collapse
Holding Volume up just continued the loop, I can get into the bootloader like you said, but theres not very many options, download locks the phone onto the HTC logo and doesn't proceed, the recovery option just restarts the phone into the loop.
Im afraid then, that I am out of suggestions for the time being.
Presumably your phone was charging whilst off, and not boot-looping?
Otherwise you can power down from the bootloader and try charging it. That may give you a better chance with the RUU
silegeek said:
Im afraid then, that I am out of suggestions for the time being.
Presumably your phone was charging whilst off, and not boot-looping?
Otherwise you can power down from the bootloader and try charging it. That may give you a better chance with the RUU
Click to expand...
Click to collapse
Whenever I plug it in while off, it shows the low battery icon and tries to turn itself on.
I had exactly the same problem...were you able to sort it out?
same problem except I can charge mine will I be able to ruu even if it is locked ?
isaac1993 said:
same problem except I can charge mine will I be able to ruu even if it is locked ?
Click to expand...
Click to collapse
Yes you can RUU with the bootloader locked. Actually it's the only way you can RUU.
Capt'n Mal said:
Yes you can RUU with the bootloader locked. Actually it's the only way you can RUU.
Click to expand...
Click to collapse
No,it's not. I'm bl ul,s-off,and I can ruu anytime.
Capt'n Mal said:
Yes you can RUU with the bootloader locked. Actually it's the only way you can RUU.
Click to expand...
Click to collapse
I thought it was charging but now fount out it wont charge
isaac1993 said:
I thought it was charging but now fount out it wont charge
Click to expand...
Click to collapse
Mine does not charge either...and RUU does not work because of the battery < 30%
The funniest thing is that I've never touched this phone either (stock, no s-off, no unlock, no custom recovery, just updated via OTA to get Nougat), it just ran out of battery during the night and found the boot loop the morning after when I plugged it. Can't believe it could turn into a f...ing brick by itself.
singlemalt said:
I had exactly the same problem...were you able to sort it out?
Click to expand...
Click to collapse
No, I had to send it back to HTC and within 2 weeks they sent it back to me completely wiped and reset to factory.
Snickie12 said:
No, I had to send it back to HTC and within 2 weeks they sent it back to me completely wiped and reset to factory.
Click to expand...
Click to collapse
Did they tell you what they did to fix it by chance? Thanks.
singlemalt said:
Did they tell you what they did to fix it by chance? Thanks.
Click to expand...
Click to collapse
No they didn't sorry.
singlemalt said:
Mine does not charge either...and RUU does not work because of the battery < 30%
The funniest thing is that I've never touched this phone either (stock, no s-off, no unlock, no custom recovery, just updated via OTA to get Nougat), it just ran out of battery during the night and found the boot loop the morning after when I plugged it. Can't believe it could turn into a f...ing brick by itself.
Click to expand...
Click to collapse
My friends s7 completly bricked doing the N update. If you havnt done anything to your phone just take it back and get a new one.
Same exact issue here after the Verizon OTA update.
Failed after the first reboot after the update.
The storage was pretty maxed, wonder if that has something to do with it.
silegeek said:
Try the same thing, but this time with Volume Up, hold it until the FTM menu appears. From here, you should be able to access the bootloader.
If that also does not work holding Volume Up and Down at the same time takes you straight into the bootloader. Sadly, unless you are S-OFF, there is not a lot you can do from this menu. I dont think it accepts the fastboot commands, particularly fastboot flash commands. But if you can get into the bootloader, and then try each option, download, recovery, etc.
If you get into the recovery, it will be stock (unless you flashed a custom ROM). You have to press volume up twice to access the options, but if you get stuck, hold volume down and power and the touch keys on the bottom flash. After about 15 flashes the phone reboots.
Click to expand...
Click to collapse
I have very similar htc 10 issue : (
https://www.reddit.com/r/HTC10/comments/9j8nyk/htc_10_oreo_stuck_in_boot_loop_i_can_only_access/
how do you do fastboot commands when only at bootloader screen when you cant access download mode or recovery : ( also my htc 10 was low on stoage space I must have corrupted the htc 10 oreo : (