Related
hi all
i have htc one m8, unlocked rooted i had previousl had viperOne rom installed and decided to change to Sky Dragon ... i wiped all the data system sd card etc and then proceeded to install the rom, installed the rom and then rebooted, recovery asked root access seems missing so i clicked no to install root access and now it is stuck on the htc screen with the this build is for dev purposes in red and now i cant get into recovery or bootloader ? what to dooooo
MrH871 said:
hi all
i have htc one m8, unlocked rooted i had previousl had viperOne rom installed and decided to change to Sky Dragon ... i wiped all the data system sd card etc and then proceeded to install the rom, installed the rom and then rebooted, recovery asked root access seems missing so i clicked no to install root access and now it is stuck on the htc screen with the this build is for dev purposes in red and now i cant get into recovery or bootloader ? what to dooooo
Click to expand...
Click to collapse
i think their is no OS installed but i still should be able to access bootloader/recovery ?
MrH871 said:
i think their is no OS installed but i still should be able to access bootloader/recovery ?
Click to expand...
Click to collapse
I've had similar issues earlier today. Read my thread, maybe it'll help.
http://forum.xda-developers.com/showthread.php?t=2759524
EDIT: If the screen 'hangs' press power button + volume up, wait for the screen to turn black and press volume down. That should get you into your bootloader!
Niorun said:
I've had similar issues earlier today. Read my thread, maybe it'll help.
http://forum.xda-developers.com/showthread.php?t=2759524
EDIT: If the screen 'hangs' press power button + volume up, wait for the screen to turn black and press volume down. That should get you into your bootloader!
Click to expand...
Click to collapse
Need some help daorderdillon...I have an HTC One M8
I wanted to flash to the UNROOTED Google Play Edition...so I rooted, TWRP'ed and did the S-OFF
and then tried to flash the ROM while in RUU mode...it gave me back a "41 error"...
so I tried to change the ModelID in the android.txt file...flashed, and then my HTC One M8 kept going into the HTC logo screen with 4 triangle error screen
When I do fastboot oem reboot, it gets me back into the device - but any normal restart after, and I'm back in the HTC logo error screen
I can't go into recovery mode either - using the POWER and UP / DOWN buttons or through the software...
Stuck, and I really don't know what to do
Thanks in advance!
wikwikwik said:
Need some help daorderdillon...I have an HTC One M8
I wanted to flash to the UNROOTED Google Play Edition...so I rooted, TWRP'ed and did the S-OFF
and then tried to flash the ROM while in RUU mode...it gave me back a "41 error"...
so I tried to change the ModelID in the android.txt file...flashed, and then my HTC One M8 kept going into the HTC logo screen with 4 triangle error screen
When I do fastboot oem reboot, it gets me back into the device - but any normal restart after, and I'm back in the HTC logo error screen
I can't go into recovery mode either - using the POWER and UP / DOWN buttons or through the software...
Stuck, and I really don't know what to do
Thanks in advance!
Click to expand...
Click to collapse
Have you tried flashing a stock recovery via fastboot? Or flash TWRP again then flash a stock nandroid backup from the backup/recovery thread?
m8 white screen
Good evening community
I think I bricked my M8. Tryed to flash a custom ROM, unrooted and installed it but didn't liked and decided to go back to stock ROM. Went to TWRP and wiped one position more than needed - data. So now my M8 booted just into white screen with HTC logo, power off doesn't work at all, hard reset combination doesn't work, power on + volume up - doesn't work. It's always on and CMD says <waiting for device>
Who can help me?
Thank you in advance
Edit: got into bootloader, thanks to Niorun post edit.
djstammo said:
I think I bricked my M8.
Click to expand...
Click to collapse
For this phone, as long as the screen comes on, its almost certainly not bricked.
Being stuck with OS not booting is a common thing when flashing ROMs. It just happens from time to time for one reason or other. Folks that freak out about this (and think their phone is bricked) need to relax and learn some basic recovery steps.
djstammo said:
Went to TWRP and wiped one position more than needed - data. So now my M8 booted just into white screen with HTC logo
Click to expand...
Click to collapse
Wiping data will not make the phone get stuck on the HTC logo screen. Wiping data just erases user data. So the phone would have just booted into the OS, but with no previous user data present any longer. Failure to boot was for some other reason.
djstammo said:
power off doesn't work at all, hard reset combination doesn't work, power on + volume up - doesn't work. It's always on and CMD says <waiting for device>
Click to expand...
Click to collapse
Power + Vol Up reboots the phone, this should always function as long as the screen comes on.
Power + Vol Down to boot into bootloader similarly should always work as long as the screen comes on. Failure to do so is almost always a matter of user error, not performing the button combo correctly (either not pressing vol down fast enough, or letting go of it too early).
Power + Volume Down
So, in response to
Power + Vol Up reboots the phone, this should always function as long as the screen comes on.
Power + Vol Down to boot into bootloader similarly should always work as long as the screen comes on. Failure to do so is almost always a matter of user error, not performing the button combo correctly (either not pressing vol down fast enough, or letting go of it too early).
Click to expand...
Click to collapse
Pressing Power + Vol Up does show the HTC screen for me, then it goes black.
Pressing Power + Vol down doesn't do anything.
Am I following the instructions correctly?
CBribiescas said:
Pressing Power + Vol Up does show the HTC screen for me, then it goes black.
Pressing Power + Vol down doesn't do anything.
Am I following the instructions correctly?
Click to expand...
Click to collapse
Try it this way:
1) Reboot the phone using Power+Vol Up
2) The moment the screen goes dark to reboot and before the white HTC logo screen appears, let go of the buttons, and hold the Vol down button. Do not let go of vol down until you see the bootloader screen
3) If the bootloader doesn't appear, you either started pressing Vol Down too late, or let go of it too early. Just do the steps again until you get it right.
Clarification
I have to anticipate when the screen is going go from black to showing the white HTC logo? Then do vol down then?
htc m8 brick
i too am having issues with a bricked htc 0ne m8. We purchased the phone as-is really cheap. its freezes while booting up. i can get into fastboot and recovery just fine. i have been successful in installing ruu files but the ruu file doesn't fix the "boot loop" freeze at startup issue. The device is s-on still which sucks because i can't find a method of achieving s-off in fastboot mode. i was able to unlock the bootloader, hoping that it would help and now the ruu files won't work anyone. now i can't get the bootloader to lock through the method that htcdev.com tells me to use. ive also tried to install update through adb sideload through recovery without success.
so i have a s-on, unlocked bootloader htc m8 that i still can't get it to boot up.
any help would be appreciated.
redpoint73 said:
Try it this way:
1) Reboot the phone using Power+Vol Up
2) The moment the screen goes dark to reboot and before the white HTC logo screen appears, let go of the buttons, and hold the Vol down button. Do not let go of vol down until you see the bootloader screen
3) If the bootloader doesn't appear, you either started pressing Vol Down too late, or let go of it too early. Just do the steps again until you get it right.
Click to expand...
Click to collapse
It works perfectly. thanks!
CBribiescas said:
I have to anticipate when the screen is going go from black to showing the white HTC logo? Then do vol down then?
Click to expand...
Click to collapse
I just timed it (in my head, not with a stopwatch), and you have about 3 seconds while the screen is black, before the HTC logo screen appears. Plenty of time to let go of the power and vol up buttons, and hold the vol down button.
The reason I say "the moment the screen goes dark" is that some folk wait too long, and start pressing vol down when the HTC logo screen is already up. By then, its too late.
---------- Post added at 10:53 AM ---------- Previous post was at 10:41 AM ----------
w0dan812 said:
i too am having issues with a bricked htc 0ne m8. We purchased the phone as-is really cheap. its freezes while booting up. i can get into fastboot and recovery just fine. i have been successful in installing ruu files but the ruu file doesn't fix the "boot loop" freeze at startup issue. The device is s-on still which sucks because i can't find a method of achieving s-off in fastboot mode. i was able to unlock the bootloader, hoping that it would help and now the ruu files won't work anyone. now i can't get the bootloader to lock through the method that htcdev.com tells me to use. ive also tried to install update through adb sideload through recovery without success.
so i have a s-on, unlocked bootloader htc m8 that i still can't get it to boot up.
Click to expand...
Click to collapse
Need more info.
What hboot number?
What radio numer?
What CID (or original carrier version)?
What RUUs did you try?
Don't know what method HTCDev says to relock the bootloader, but as long as you can still get into fastboot mode, its simply the command: fastboot oem lock
Also, there is no other currently working s-off method aside from sunshine (which requires booting into OS) so you can stop looking for one.
I "Softbricked" my htc one m8 AT&T
i recently rooted it and made 4 back ups. I deleted two of them and tried to roboot to fastboot. but it says 'No OS installed" . My computers reconize it as a disk drive and when i click on it, it asks me to insert a disk...Please, ANYONE with information that will help, share
Craz Basics said:
i recently rooted it and made 4 back ups. I deleted two of them and tried to roboot to fastboot. but it says 'No OS installed" . My computers reconize it as a disk drive and when i click on it, it asks me to insert a disk...Please, ANYONE with information that will help, share
Click to expand...
Click to collapse
Download a ROM on your PC, transfer it to your extSD, put that in your phone and flash it in recovery.
MrH871 said:
hi all
i have htc one m8, unlocked rooted i had previousl had viperOne rom installed and decided to change to Sky Dragon ... i wiped all the data system sd card etc and then proceeded to install the rom, installed the rom and then rebooted, recovery asked root access seems missing so i clicked no to install root access and now it is stuck on the htc screen with the this build is for dev purposes in red and now i cant get into recovery or bootloader ? what to dooooo
Click to expand...
Click to collapse
Well, you say you can't get in the bootloader or recovery, have you tried to hold down the power button and volume up button, and then when the screen goes off switch to power and volume down? That should take you to your bootloader! If you can get there I would guess you would have a backup in recovery
---------- Post added at 10:01 AM ---------- Previous post was at 09:58 AM ----------
w0dan812 said:
i too am having issues with a bricked htc 0ne m8. We purchased the phone as-is really cheap. its freezes while booting up. i can get into fastboot and recovery just fine. i have been successful in installing ruu files but the ruu file doesn't fix the "boot loop" freeze at startup issue. The device is s-on still which sucks because i can't find a method of achieving s-off in fastboot mode. i was able to unlock the bootloader, hoping that it would help and now the ruu files won't work anyone. now i can't get the bootloader to lock through the method that htcdev.com tells me to use. ive also tried to install update through adb sideload through recovery without success.
so i have a s-on, unlocked bootloader htc m8 that i still can't get it to boot up.
any help would be appreciated.
Click to expand...
Click to collapse
As I said in another post. Try holding down the power button and volume up button, then when it turns off switch to power and volume down! That should take you to bootloader.
---------- Post added at 10:08 AM ---------- Previous post was at 10:01 AM ----------
redpoint73 said:
I just timed it (in my head, not with a stopwatch), and you have about 3 seconds while the screen is black, before the HTC logo screen appears. Plenty of time to let go of the power and vol up buttons, and hold the vol down button.
The reason I say "the moment the screen goes dark" is that some folk wait too long, and start pressing vol down when the HTC logo screen is already up. By then, its too late.
---------- Post added at 10:53 AM ---------- Previous post was at 10:41 AM ----------
Need more info.
What hboot number?
What radio numer?
What CID (or original carrier version)?
What RUUs did you try?
Don't know what method HTCDev says to relock the bootloader, but as long as you can still get into fastboot mode, its simply the command: fastboot oem lock
Also, there is no other currently working s-off method aside from sunshine (which requires booting into OS) so you can stop looking for one.
Click to expand...
Click to collapse
Try this, this is what I did to unlock and root mine along with installing twrp. You can change your recovery and relock the bootloader. It has an option to switch to s-off but idk if it works
http://forum.xda-developers.com/showthread.php?t=2699065
---------- Post added at 11:07 AM ---------- Previous post was at 10:08 AM ----------
wikwikwik said:
Need some help daorderdillon...I have an HTC One M8
I wanted to flash to the UNROOTED Google Play Edition...so I rooted, TWRP'ed and did the S-OFF
and then tried to flash the ROM while in RUU mode...it gave me back a "41 error"...
so I tried to change the ModelID in the android.txt file...flashed, and then my HTC One M8 kept going into the HTC logo screen with 4 triangle error screen
When I do fastboot oem reboot, it gets me back into the device - but any normal restart after, and I'm back in the HTC logo error screen
I can't go into recovery mode either - using the POWER and UP / DOWN buttons or through the software...
Stuck, and I really don't know what to do
Thanks in advance!
Click to expand...
Click to collapse
If it is rooted, you can download a app that should take you to recovery. I think ROM toolbox is one. Hope this helps good luck. I'm here if you need me
AndroidEducator said:
Hope this helps good luck. I'm here if you need me
Click to expand...
Click to collapse
Do you realize you are responding to old posts, the most recent of which is over 3 months old?
You also responded to my post, as if I was having an issue. I was the one giving help/advice.
---------- Post added at 09:51 AM ---------- Previous post was at 09:48 AM ----------
AndroidEducator said:
. It has an option to switch to s-off but idk if it works
Click to expand...
Click to collapse
It doesn't. The tool is very outdated, and I typically (virtually always) recommend against using it for that reason. The toolkit uses the old firewater s-off method, which hasn't worked since December 2014.
When I said there is no other working s-off method besides sunshine (and to stop looking for one), it was a statement of fact, not a guess.
I need some help, I have a m8 rooted and to make an update from htc (I have te stock rom) I have flash de stock recovery (te old one was the twrp) but now after the update de phone is stuck in the htc logo, I can enter in the fastboot but I dont know what to do and what direction I should take
Follow my steps if your phone is not booting up.
1. Lock bootloader if you have unlocked bootloader.
2. Download HTC One M8 4.16.401.10 Stock Lollipop RUU [0P6BIMG] ( search google because I can not post link since I am new forum member).
3. Rename the downloaded RUU to 0P6BIMG and send the zip file to your phone SD Card.
3.Reboot your phone in to the bootloader mode by powering off the phone and rebooting with Power button and volume down or use fastboot mode command : adb reboot-bootloader.
-This way our phone will automatically detect the RUU file that you pasted in SD card (step 3) and flash it.
Your HTC One M8 is alive
W_KuP said:
I need some help, I have a m8 rooted and to make an update from htc (I have te stock rom) I have flash de stock recovery (te old one was the twrp) but now after the update de phone is stuck in the htc logo, I can enter in the fastboot but I dont know what to do and what direction I should take
Click to expand...
Click to collapse
g510 said:
Follow my steps if your phone is not booting up.
1. Lock bootloader if you have unlocked bootloader.
2. Download HTC One M8 4.16.401.10 Stock Lollipop RUU [0P6BIMG] ( search google because I can not post link since I am new forum member).
3. Rename the downloaded RUU to 0P6BIMG and send the zip file to your phone SD Card.
3.Reboot your phone in to the bootloader mode by powering off the phone and rebooting with Power button and volume down or use fastboot mode command : adb reboot-bootloader.
-This way our phone will automatically detect the RUU file that you pasted in SD card (step 3) and flash it.
Your HTC One M8 is alive
Click to expand...
Click to collapse
The advice given here is good, except it assumes too many things. There is the assumption of S-On, and of current firmware version. Also, if you are using ADB to reboot to bootloader, the user might as well fastboot flash the RUU.zip, or run the RUU.exe that is also available.
@W_KuP, Post the results of fastboot getvar all (edit out your IMEI and serial# ~ that's private info)
If you are indeed on WWE/International firmware, that RUU.zip will work for you. Download link here.
If you are S-On, you will need to relock your bootloader first. In fastboot: fastboot oem lock. If you are S-Off there is no need to relock your bootloader.
I've got a head scratcher here. I've just bought an M8 for T-Mobile. I went through the HTCdev process of getting the Unlock_code.bin. Everything seemed to be working but when I went to flash the bin file, I can't select yes.
It brings up the option to unlock with the black screen and text on it. Then it has the "Yes" and "No" selection. Pressing volume up does nothing and pressing power does nothing. All I can do is toggle in between the two with volume down. Further, when I'm just sitting in fastboot, I can only use the volume down. The other two don't work there either.
Has anybody else had this occur? I've flashed the RUU again, tried to flash back to KK and failed (of course), and have been searching for hours.
So when you try to unlock bootloader what rom is installed in device? When I unlocked mine it was all done on pc inside the adb folder. What are you doing ? Step by step and let's get this thing unlocked
---------- Post added at 11:42 PM ---------- Previous post was at 11:38 PM ----------
Your device is only connected to pc and you don't flash anything on device itself, it's done in the cmd prompt
mattpedigo said:
I've got a head scratcher here. I've just bought an M8 for T-Mobile. I went through the HTCdev process of getting the Unlock_code.bin. Everything seemed to be working but when I went to flash the bin file, I can't select yes.
It brings up the option to unlock with the black screen and text on it. Then it has the "Yes" and "No" selection. Pressing volume up does nothing and pressing power does nothing. All I can do is toggle in between the two with volume down. Further, when I'm just sitting in fastboot, I can only use the volume down. The other two don't work there either.
Has anybody else had this occur? I've flashed the RUU again, tried to flash back to KK and failed (of course), and have been searching for hours.
Click to expand...
Click to collapse
Had same problem. Think the first reply is a bit confused where your at in your phone. If you relock your S off to back S on for ota or other reasons you then need to unlock it thru HTC dev .com . I had the same problem. What I did was just use the volume up button to the yes side for about a min while pressing power numerous times. Eventually I think I got the phone so confused it stuck there. Just be patient. For the first reply, hes unlocking the bootloader thru HTC where you recieve the token and use adb function. Nothing similar to sunshine at all when you first unlock it. Once sunshine unlocks it, you can relock it and UN lock it as pleased. Sunshine alters the phone to being shipped s off from the point of sale in case you have to unlock or relock for multiple reasons. Just stick to trying to force it to yes and power at the same time. It will do it. GL.
I have a HTC one M8 Sprint.
I unlocked the bootloader and flash new TWRP recovery.
After that i installed the CM13 Official nightly zip from my SD card. It succeeded and boot into the new os.
But it does not reconise my simcard.
I changed my CID to SuperCID before that but it still can't reconise my sim.
so i got frustrated and decide to go back to the stock HTC rom.
Being the idiot that i am i forgot to take a NANDROID backup.
So i relock bootloader,take the FIRMWARE and change it to 0P6BIMG and let the bootloader scan my SD card.
i flashed the Firmware and reboot. and now the phone is stuck on the Cyanogenmod bootanimation .
I tried to hold the power and the Volume down button to hard reboot it but it doesn't work.
Now it just stuck there. Not recognized by the computer. Can't use ADB commands to restart the phone to Bootloader.
What should i do now? Wait the battery to run out and then recharge and boot to bootloader ?
Update. I solved it by holding all 3 buttons at once and the phone can be turned off.
so I used the RUU to bring back my htc to stock. Problem solved :l
ChristopherXI said:
I tried to hold the power and the Volume down button to hard reboot it but it doesn't work.
Click to expand...
Click to collapse
That button combo only works (to boot into bootloader) when the phone is fully powered down. It won't work if the screen is on (including stuck on the boot splash screen).
To force a reboot (and go to bootloader) when the screen is on (including stuck on the boot splash screen), you need to:
1) Hold power + vol up for a minute or so, to force a reboot.
2) Once the screen goes dark to reboot, immediately let go of those buttons, and only hold vol down until you see the bootloader screen
3) If the phone just gets stuck on the boot splash again, you got the timing wrong, either started pressing vol down too late, or let go too early - just repeat the process until you get it.
---------- Post added at 09:21 AM ---------- Previous post was at 09:18 AM ----------
ChristopherXI said:
So i relock bootloader,take the FIRMWARE and change it to 0P6BIMG and let the bootloader scan my SD card.
i flashed the Firmware and reboot. and now the phone is stuck on the Cyanogenmod bootanimation .
Click to expand...
Click to collapse
This is the normal and expected result of flashing FIRMWARE.
Firmware is not the same as an RUU or ROM, so that may be the confusion there (somewhat common mistake).
Firmware is a very small package, and does not include the stock OS (ROM or system partition); but just a small collection of other partitions needed for the OS to work (hboot, recovery, radio, etc.)
Flashing stock/signed firmware renders the phone unable to boot as it expects RUU to be run afterwards. Alternately, flashing TWRP and installing a flashable ROM.zip also will get the phone running after flashing firmware.
redpoint73 said:
That button combo only works (to boot into bootloader) when the phone is fully powered down. It won't work if the screen is on (including stuck on the boot splash screen).
To force a reboot (and go to bootloader) when the screen is on (including stuck on the boot splash screen), you need to:
1) Hold power + vol up for a minute or so, to force a reboot.
2) Once the screen goes dark to reboot, immediately let go of those buttons, and only hold vol down until you see the bootloader screen
3) If the phone just gets stuck on the boot splash again, you got the timing wrong, either started pressing vol down too late, or let go too early - just repeat the process until you get it.
---------- Post added at 09:21 AM ---------- Previous post was at 09:18 AM ----------
This is the normal and expected result of flashing FIRMWARE.
Firmware is not the same as an RUU or ROM, so that may be the confusion there (somewhat common mistake).
Firmware is a very small package, and does not include the stock OS (ROM or system partition); but just a small collection of other partitions needed for the OS to work (hboot, recovery, radio, etc.)
Flashing stock/signed firmware renders the phone unable to boot as it expects RUU to be run afterwards. Alternately, flashing TWRP and installing a flashable ROM.zip also will get the phone running after flashing firmware.
Click to expand...
Click to collapse
I knew about the firmware. So i followed it up by using the RUU
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 : (
Recently I bricked my phone after flashing wrong boot.img. I can't get into bootloader and once the device turns on, I can't do anything except of waiting until the battery runs out of power. Is there any way to recover this phone?
First of all, it is not bricked. As long as the screen comes on (even if just stuck on the HTC logo screen) the device is likely recoverable. A true brick is a device that can only be recovered by opening up the phone (replace motherboard, JTAG, etc.). You are simply stuck in a condition, where it won't boot to the Android OS.
Bootloader is a protected partition, and therefore can't be over-written by something like flashing a boot.img, as long as your are s-on (default condition).
Bootloader therefore is most likely still working, you just aren't accessing it properly. You probably just aren't doing the proper button combo, to get the bootloader. Try this:
1) No need to wait for battery to drain. To reboot the phone simply hold power + vol up button, until the screen goes dark to reboot. May take up to a minute, before this happens, in a "stuck" condition.
2) The moment the screen goes dark to reboot, but before the HTC logo screen comes back on, let go of the power button, and simply slide your finger from vol up, to vol down. Keep vol down pressed, until you see the bootloader screen.
3) If you don't get the bootloader, you probably just got the timing wrong. You either started pressing vol down too late, or let go of vol down too early. Simply repeat Steps 1 and 2 above, until you get the timing correct.
From bootloader, you should be able to flash the correct boot.img
Although your comment that you flashed the "wrong boot.img" raises some questions:
a) How do you know it is the wrong boot.img? Where did you get it from?
b) Why did you flash this boot.img? What were you trying to accomplish? Is it a custom kernel, or trying to solve some other problem?
If you need help finding the right boot.img, in addition to answer the above questions a-b, you should also do fastboot getvar all, and post the results (delete IMEI and serial number before posting).
redpoint73 said:
First of all, it is not bricked. As long as the screen comes on (even if just stuck on the HTC logo screen) the device is likely recoverable. A true brick is a device that can only be recovered by opening up the phone (replace motherboard, JTAG, etc.). You are simply stuck in a condition, where it won't boot to the Android OS.
Bootloader is a protected partition, and therefore can't be over-written by something like flashing a boot.img, as long as your are s-on (default condition).
Bootloader therefore is most likely still working, you just aren't accessing it properly. You probably just aren't doing the proper button combo, to get the bootloader. Try this:
1) No need to wait for battery to drain. To reboot the phone simply hold power + vol up button, until the screen goes dark to reboot. May take up to a minute, before this happens, in a "stuck" condition.
2) The moment the screen goes dark to reboot, but before the HTC logo screen comes back on, let go of the power button, and simply slide your finger from vol up, to vol down. Keep vol down pressed, until you see the bootloader screen.
3) If you don't get the bootloader, you probably just got the timing wrong. You either started pressing vol down too late, or let go of vol down too early. Simply repeat Steps 1 and 2 above, until you get the timing correct.
From bootloader, you should be able to flash the correct boot.img
Although your comment that you flashed the "wrong boot.img" raises some questions:
a) How do you know it is the wrong boot.img? Where did you get it from?
b) Why did you flash this boot.img? What were you trying to accomplish? Is it a custom kernel, or trying to solve some other problem?
If you need help finding the right boot.img, in addition to answer the above questions a-b, you should also do fastboot getvar all, and post the results (delete IMEI and serial number before posting).
Click to expand...
Click to collapse
a) This is where i got it from: https:// androidfilehost.com/?fid=385035244224400814. The boot.img file was most likely not matching the system installed (LineageOS 16). It's stock boot.img for my device (propably).
b) I was trying to fix the problem, where I couldn't install Magisk, because when installing, it said that I have custom boot.img and cannot proceed. I could've ask first how to solve this instead of doing this, so I'm just an idiot.
DarkKnightComes said:
a) This is where i got it from: https:// androidfilehost.com/?fid=385035244224400814. The boot.img file was most likely not matching the system installed (LineageOS 16). It's stock boot.img for my device (propably).
b) I was trying to fix the problem, where I couldn't install Magisk, because when installing, it said that I have custom boot.img and cannot proceed. I could've ask first how to solve this instead of doing this, so I'm just an idiot.
Click to expand...
Click to collapse
It worked! Thanks for help!
DarkKnightComes said:
a) This is where i got it from: https:// androidfilehost.com/?fid=385035244224400814. The boot.img file was most likely not matching the system installed (LineageOS 16). It's stock boot.img for my device (propably).
b) I was trying to fix the problem, where I couldn't install Magisk, because when installing, it said that I have custom boot.img and cannot proceed. I could've ask first how to solve this instead of doing this, so I'm just an idiot.
Click to expand...
Click to collapse
a) I can't tell from the link alone, what that boot.img even is, and it seems that you don't either. Even if stock boot.img, what version number (there are many - and that matters). My advice (maybe already a lesson learned) is not to flash things, if you aren't 100% sure what they are.
b) I'm not a Lineage user, so I'm not familiar whether that is a known error or not. AFAIK, Lineage should be compatible with Magisk, so as you already figured, the error may be a result of custom kernel, another previously installed root method (SuperSU?) or some other mod. In which case, there are better ways to get back to a "clean" and correct boot.img, rather than flashing files which you are unsure of. Easiest way, is to simply dirty flash the Lineage ROM again. Either just the boot.img (which is included with the ROM.zip) of the whole ROM. Whole ROM is probably the best, as it will give you a clean ROM baseline, in case there is anything else modified (besides boot.img) that is interfering with Magisk. Dirty flash means flashing the file while keeping user data, only wipe cache and Dalvik.
---------- Post added at 09:12 AM ---------- Previous post was at 09:10 AM ----------
DarkKnightComes said:
It worked! Thanks for help!
Click to expand...
Click to collapse
What worked exactly? Getting into bootloader by the method I described, I pretty much figured would work. Did you also get the right boot.img flashed, and get it rooted with Magisk?
What worked exactly? Getting into bootloader by the method I described, I pretty much figured would work. Did you also get the right boot.img flashed, and get it rooted with Magisk?
Click to expand...
Click to collapse
I forgot about the Power+VolDown combination. I launched Recovery from bootloader and I just installed ROM on top of the previous one. The ROM that I have has Magisk integrated.