I am in need of some serious help. My AT&T M8 won't boot past the HTC logo screen and won't allow me to go into recovery or the hboot screen. I believe I may have wiped the OS on it; this is the only thing I can think of that makes sense. Furthermore, when I try to power down the device by long pressing the power button, it doesn't respond at all. It just stays on the logo screen. It was so bad that I just left it plugged in overnight and I don't have a clue as to how long it took to power off because I fell asleep before it did. If there's a video tutorial out there that someone has or simply a link that can show me how to install something via backdoor on this device, that would be great!
alpinesun said:
I believe I may have wiped the OS on it; this is the only thing I can think of that makes sense. !
Click to expand...
Click to collapse
Recount as best you can, all the steps that got the phone to this point.
What were you trying to do when this happened?
Also, need much more info in order to help:
1) bootloader unlocked?
2) custom or stock recovery
3) custom ROM?
4) what hboot number?
5) s-on or s-off
6) did you make a nandroid with custom recovery?
alpinesun said:
Furthermore, when I try to power down the device by long pressing the power button, it doesn't respond at all. It just stays on the logo screen.
Click to expand...
Click to collapse
Hold power and vol up for several seconds to force a reboot. The moment the screen goes dark to reboot, let go of those buttons, and just hold vol down. Don't let go until the hboot screen appears.
Thanks already. I didn't realize I had to hold down the volume down button after it goes dark. It got me into twrp. I believe I should be good from here after I download a new rom to sideload. But to give you a run down, I was prepping the phone to sell it by wiping the data and installing the rom the guy said he wanted on it. When I was going thru the normal procedure to install the rom (wipe, flash, etc) that's when the phone started sticking on the logo screen. My assumption was that I downloaded a bad rom, so since then I've been trying to get back into twrp so I can load a new rom and finally was able to after you told me this. I'll report back if a new rom actually didn't help the situation. I only thought I wiped the OS because something similar happened with my Note when I was tinkering and that was the result.
alpinesun said:
I'll report back if a new rom actually didn't help the situation.
Click to expand...
Click to collapse
If you need any further help, please answer all the questions I previously asked.
Good luck.
redpoint73 said:
Recount as best you can, all the steps that got the phone to this point.
What were you trying to do when this happened?
Also, need much more info in order to help:
1) bootloader unlocked?
2) custom or stock recovery
3) custom ROM?
4) what hboot number?
5) s-on or s-off
6) did you make a nandroid with custom recovery?
Hold power and vol up for several seconds to force a reboot. The moment the screen goes dark to reboot, let go of those buttons, and just hold vol down. Don't let go until the hboot screen appears.
Click to expand...
Click to collapse
So, it seems I'm still having the problem, even while trying to install cyanogen. Here are the answers to those questions...
1) bootloader unlocked?... YES
2) custom or stock recovery... TWRP
3) custom ROM?... It was a custom AOSP Rom
4) what hboot number?... 3.16.0.0000
5) s-on or s-off... S-OFF
6) did you make a nandroid with custom recovery?... It was erased
Any help you can give from this point would be awesome. Thanks again!
alpinesun said:
So, it seems I'm still having the problem, even while trying to install cyanogen.
Click to expand...
Click to collapse
Failure to flash ROMs can often be solved with fastboot erase cache, then install TWRP by fastboot again. Update TWRP version, if you are using an outdated one.
Also, if you try to flash any ROMs based on Sense software beyond version 1.x (huge majority of them are past 1.x at this point) you will likely experience extremely long boot times (10 minutes or more) and broken WiFi due to outdated firmware. But CM should be okay.
alpinesun said:
6) did you make a nandroid with custom recovery?... It was erased
Click to expand...
Click to collapse
It was erased, or you wiped it?
Okay. Do you suggest trying an older sense rom to see if it works? The last time touched the phone was when I picked up my Note 4, so I will look for something that predates that.
As for the nandroid being erased, I can only assume it was my actions that caused it to be deleted, but I don't recall intentionally doing it.
alpinesun said:
Okay. Do you suggest trying an older sense rom to see if it works?
Click to expand...
Click to collapse
Sure, it couldn't hurt. With your current firmware, you will need a ROM based on 1.x software. There aren't a heck of a lot of those left. But there are a few. GoldenEye is one I can personally vouch for, since I was running it for a while back in the day:
http://forum.xda-developers.com/showthread.php?t=2705640
But I would definitely recommend just trying fastboot erase cache and re-install TWRP first. I've lost count how many times suggesting this simple fix has helped other users here on XDA, when ROMs fail to flash.
alpinesun said:
As for the nandroid being erased, I can only assume it was my actions that caused it to be deleted, but I don't recall intentionally doing it.
Click to expand...
Click to collapse
Fair enough. Just FYI, don't do a factory reset in bootloader (in the OS settings or recovery is OK). On modded phones this may cause the internal storage to become corrupted. Nandroids have sometimes been lost this way. This may or may not be what happened to you. Just wanted to throw that out there.
Also, there has been the occasional occurrence of internal storage being corrupted, possibly by TWRP. It may not even have been something you caused.
Related
My Incredible is in a bootloop. I have gone back to stock. The phone will work for a few minutes then just reboot non-stop. I did a factory reset and that did not help.
I can't keep the phone on long enough to do anything. The irony in all of this is that it started to do this 2 weeks after I became eligable for an upgrade...
Smells fishy...now I either wait for Incredible 4G or get the Rezound.
[email protected] Verizon...
Do you have a recovery on the phone still or did you get rid of it when returning to stock? I'm not sure I've heard of this before but if you post the status of your hboot that might be able to help someone help you.
and personally between the two I would go with the Incredible 4G but that's just me being loyal to HTC i guess.
Recovery is gone/does not work. I'll post the HBOOT version later, don't have the phone atm.
binaryhat said:
Recovery is gone/does not work. I'll post the HBOOT version later, don't have the phone atm.
Click to expand...
Click to collapse
Post hboot version, s-on or off, and current android version.
cmlusco said:
Post hboot version, s-on or off, and current android version.
Click to expand...
Click to collapse
Will do tomorrow...left the phone at work.
S-off
HBOOT-0.92
Radio-2.15.00.07.28
Stock Android
I know it sounds very round-about but you may need to flash CWM back on to the phone so you can flash unrevoked's s-on tool, I don't know for sure that this is what is causing the problem but you want s-on when you are in stock, especially if you plan on giving the phone to Verizon- if it has been messed with they won't want to handle it because they will say it is not their problem. (I have heard that Verizon has admitted to not checking very carefully, but it can't hurt to be careful yourself)
How can I flash CWM if I can't keep the phone on for more than a minute?
sounds like your kinda having the same problem i am having. the difference is my is s-on. i can get to hboot but when i try to go to recovery from there it comes up with a bunch of errors. and mine just bootloops at the droid eye.
that is a very valid point. It still can't hurt to try, I remember when I rooted my phone, it didn't take all that long to flash CWM.
You also might want to consider booting into safe mode to see if that keeps in on longer, I am copying and pasting these instructions from technipages.com because xda won't let me post links until they trust me more or something:
Sometimes services and apps you install on your HTC Droid Incredible can interfere with its functionality. If you’ve reached a point where the phone freezes at startup or malfunctions in a way that you can’t remove the problem, Safe Mode is the answer. Booting in Safe Mode will load only software and drivers from factory defaults. This should allow you access to remove whatever ails your smartphone.
1. Turn the device off. If the power button doesn’t do the trick, remove and replace the battery.
2. Power the device on.
3. When the logo appears, press and hold the Menu button.
4. Continue holding the Menu button until you see the home screen.
The words Safe Mode should appear in the lower left corner if you performed the steps correctly.
Click to expand...
Click to collapse
I apologize if you don't have any luck, but I am only trying to help
I'll try safe mode (should have) and see if that works.
binaryhat said:
I'll try safe mode (should have) and see if that works.
Click to expand...
Click to collapse
Does the phone shut off when your in hboot too? You need to do as sugested and flash cwm thru hboot, and then see if you can access recovery long enough to wipe everything in mounts and storrage except sd and emmc, then flash superuser, and a rom.
scoobntaz1996 said:
sounds like your kinda having the same problem i am having. the difference is my is s-on. i can get to hboot but when i try to go to recovery from there it comes up with a bunch of errors. and mine just bootloops at the droid eye.
Click to expand...
Click to collapse
Whats your hboot and android version? Have you tried an ruu?
EDIT: Nevermind i forgot i was allready talking to you in the other thread.
So I have my old phone, and wanted to use it as a media player. I chose to use UberSonic RC3, however after I've flashed this, it will sit at the bootloader if it's plugged in, until I unplug the phone and reset it and let it boot up. Hboot 2.18.0001 with S-off as well, so everything flashed right from what it seems, though if I hold Vol up and Power on it keeps vibrating but no screen. Anyone else run into this? Could it be that I've got a bad flash on the bootloader partly causing any issues?
Thanks
gdeeble said:
So I have my old phone, and wanted to use it as a media player. I chose to use UberSonic RC3, however after I've flashed this, it will sit at the bootloader if it's plugged in, until I unplug the phone and reset it and let it boot up. Hboot 2.18.0001 with S-off as well, so everything flashed right from what it seems, though if I hold Vol up and Power on it keeps vibrating but no screen. Anyone else run into this? Could it be that I've got a bad flash on the bootloader partly causing any issues?
Thanks
Click to expand...
Click to collapse
Volume up + power doesn't do anything. When powered off, volume down + power will pull up the bootloader. What recovery are you using?
Sent from my EVO using xda premium
TWRP 2.3.3.0 . Sorry I was exhausted last night and knew I would miss something of key relevance, when typing the post it. When I do it, I just get the 3 vibrates and nothing. The big problem for me is that the phone won't get past the bootloader when plugged in to a source though, however, if we can figure out both things, that would be awesome. The other thing is that my bootloader has been unlocked via HTC Dev as well as the S-off. Is that a big no no?
Edit:
I Just updated to 2.5.0.0 via GooManager. Same issues still occur so I'm pretty sure it's not recovery causing the issue, but then again I'm not an expert with it either.
gdeeble said:
TWRP 2.3.3.0 . Sorry I was exhausted last night and knew I would miss something of key relevance, when typing the post it. When I do it, I just get the 3 vibrates and nothing. The big problem for me is that the phone won't get past the bootloader when plugged in to a source though, however, if we can figure out both things, that would be awesome. The other thing is that my bootloader has been unlocked via HTC Dev as well as the S-off. Is that a big no no?
Edit:
I Just updated to 2.5.0.0 via GooManager. Same issues still occur so I'm pretty sure it's not recovery causing the issue, but then again I'm not an expert with it either.
Click to expand...
Click to collapse
Have you tried a different recovery?? mainly just to rule it out completely... i highly recommend SmelkusMod of AmonRa, http://forum.xda-developers.com/showthread.php?t=1661543.
angryITman said:
Have you tried a different recovery?? mainly just to rule it out completely... i highly recommend SmelkusMod of AmonRa, http://forum.xda-developers.com/showthread.php?t=1661543.
Click to expand...
Click to collapse
I have tried a few, including the one you mentioned. It still does the 3 buzzes with vol + and power, and will still continue to stick on the bootloader and reboot there. I think it might be the rom but hard to tell. Do keep in mind, I have S-off and did the HTCDev unlock so.
gdeeble said:
I have tried a few, including the one you mentioned. It still does the 3 buzzes with vol + and power, and will still continue to stick on the bootloader and reboot there. I think it might be the rom but hard to tell. Do keep in mind, I have S-off and did the HTCDev unlock so.
Click to expand...
Click to collapse
did you double check the MD5 after you downloaded UberSonic?? maybe its just a bad download. check it with MD5 Check Utility, or any other version. or try another rom. make sure to Wipe Data/Factory Reset & Wipe Dalvik Cache.
angryITman said:
Have you tried a different recovery?? mainly just to rule it out completely... i highly recommend SmelkusMod of AmonRa, http://forum.xda-developers.com/showthread.php?t=1661543.
Click to expand...
Click to collapse
angryITman said:
did you double check the MD5 after you downloaded UberSonic?? maybe its just a bad download. check it with MD5 Check Utility, or any other version. or try another rom. make sure to Wipe Data/Factory Reset & Wipe Dalvik Cache.
Click to expand...
Click to collapse
It seems that it works fine when it's not plugged in. It's like the bootloader is jacked up when it detects power. I'm gonna try to do a full system wipe and reflash it though to ensure 100% that it's not that.
Hello, I recently flashed sphongle on my HTC ONE V, and it was working fine. I later installed gapps, which was also working fine (downloaded a few app and recovered my contact etc... using Titanium) for a while until I rebooted the phone. After this I could not get past the loading screen for sphongle. I do not know if Gapps was the issue, but I used version 20130301.
I then went to the my CWM recovery menu and did a factory reset, cleared the cache and tried restoring to the backup I made before I flashed the ROM. After doing this I could not get past the HTC menu. After doing all of this I now cannot access the bootmenu, it instead goes straight to the recovery menu when I hold down the power and volume down button as one would do to access the bootmenu. Because I can't access the bootmenu, I can't use an RUU.
If anyone has any suggestions or ideas I would be very happy.:fingers-crossed:
I'll try to answer any questions people have.
CWM is more trouble than its worth. it doesnt have a boot to bootloader option like twrp? you are in a fix without the ability to access hboot
No it doesn't have the option sadly.
Curtis1973 said:
you are in a fix without the ability to access hboot
Click to expand...
Click to collapse
Yep that's pretty much jist of it.
whick kernel are you using ?
I'm using HELLBOY-2013-06-29-4.2
Managed to figure it out myself.:victory:
nostalgickitty said:
Managed to figure it out myself.:victory:
Click to expand...
Click to collapse
im curious what you did to get back in to hboot. it may be something users may need to learn how to do if they ever encounter this issue.
24339642 120
Curtis1973 said:
im curious what you did to get back in to hboot. it may be something users may need to learn how to do if they ever encounter this issue.
Click to expand...
Click to collapse
Honestly It's pretty embarrassing, and shows my inexperience at this, but the whole time I tried booting to hboot, my phone was plugged into my computer. Once I unplugged it I could boot into hboot no problem. I guess this would be helpful for new users to know.
Hi,
I have an HTC One M8 (AT&T) . I had 5.02 on it earlier today and wanted to upgrade it. I don't have service so can't use the ATT Updated. I unlocked the boot loader and loaded a boot.img. Now my phone turns on the the HTC and goes to the HTC screen. It does says that the image should not be distribute outside of HTC.
Any help in getting past this?
You didn't brick. You didn't install a ROM. You just installed the kernel when you flashed boot.img, which is like 1% of what it takes to have a working OS. A kernel is about 25 MB, where a Sense ROM is around 1.5 GB.
You're not the only person to make this mistake. But I'm at a loss to understand why folks think that a boot.img is the same as a ROM. They are 2 completely different (although related) things.
Flash the entire ROM. No need to flash boot.img seperately (it flashes with the ROM/system partition).
Also, the red text on the boot screen is perfectly normal, once you've installed a custom recovery (TWRP).
Any particular ROM you recommend? What you say makes sense, as to how I got there, I was following a set of steps.
redpoint73 said:
You didn't brick. You didn't install a ROM. You just installed the kernel when you flashed boot.img, which is like 1% of what it takes to have a working OS. A kernel is about 25 MB, where a Sense ROM is around 1.5 GB.
You're not the only person to make this mistake. But I'm at a loss to understand why folks think that a boot.img is the same as a ROM. They are 2 completely different (although related) things.
Flash the entire ROM. No need to flash boot.img seperately (it flashes with the ROM/system partition).
Also, the red text on the boot screen is perfectly normal, once you've installed a custom recovery (TWRP).
Click to expand...
Click to collapse
salevine said:
Any particular ROM you recommend? What you say makes sense, as to how I got there, I was following a set of steps.
Click to expand...
Click to collapse
Where did you get the boot.img, was it from a ROM?
What steps were you following? I know you can't link, due to not enough posts. But you can describe if its an XDA thread, describe the guide, ROM thread, or process in question. Just saying you were "following a set of steps" doesn't really tell us anything.
I actually managed to finally get it fixed. Just in case anyone else has the issue, here is what I had to do. I left it on until the battery completely died. Then I was able to finally get it on and into HBOOT. Since I had made the mistake of installing TWRP but not making a backup, I could not restore from a backup. I took the SD card out of my phone and downloaded venomROM and put it on my SD card. I then was able to get into HBOOT, Recover and install using TWRP and the ROM from the SD card. All is well now.
redpoint73 said:
Where did you get the boot.img, was it from a ROM?
What steps were you following? I know you can't link, due to not enough posts. But you can describe if its an XDA thread, describe the guide, ROM thread, or process in question. Just saying you were "following a set of steps" doesn't really tell us anything.
Click to expand...
Click to collapse
salevine said:
I actually managed to finally get it fixed. Just in case anyone else has the issue, here is what I had to do. I left it on until the battery completely died. .
Click to expand...
Click to collapse
No need to have done that (let the battery die) but I guess if it worked, power to you. I would have pointed out how to reboot, but got sidetracked when you asked for ROM recommendations, and referenced some guide, but not telling us what guide, which confused the conversation.
For future reference, next time, hold power+vol up to force a reboot (may need to hold a minute or so, in the case of stuck on HTC logo screen or similar condition). The moment the screen goes dark, slide your finger from vol up, to vol down (no need to keep holding power button at this point) and keep holding vol down until bootloader screen appears. If it doesn't, just repeat, as you got the timing wrong (either started pressing vol down to late, or let go of it too early).
Whatever guide you were following was wrong (or possibly for an older device) as you don't need to flash boot.img seperately, unless the intent is to install a custom kernel (different thing from flashing a ROM).
I've seen already this thread suggested by XDA thread locator.
https://forum.xda-developers.com/htc-one-m8/help/verizon-htc-one-m8-stuck-htc-logo-t3163088
But I'd try to explain as simple as possible the whole situation which happened hours ago.
Don't know what happened but my mothers phone went off and restarted with htc one logo on it and nothing else later.
Power button itself doesnt work and is not responding.
Configuration PWR + VOL UP gives me restart but no recovery mode, giving me sound effect of restarting phone and ONE logo on it without any other reaction whatsoever.
PWR + VOL DWN zero reaction
PWR + VOL UP & DOWN pressed together restarting the phone and then gives me HTC ONE LOGO and nothing else.
when Phone is plugged in to the computer and I'm forcing the phone to restart it shows me new Device on the computer as a CD Driver every time.
So I think there is still hope to get this guy back to life.
It's running on custom rom but unknown version because it was purchased as a refurb from ebay 2 years ago and it was running just fine utill this very day.
I'm absolutely noob with flashing twrping etc so please ELI5 if possible, any type of help will be much appreciated.
Thanks in advance.
Hey, I had this same problem a couple of days ago. Here's what I did to get the phone into fastboot, from where you can install a recovery, factory reset etc.
1. Hold the power button + vol up button for about 10-20 seconds. This should shut down the phone.
2. Hold the power button + vol down button to restart the phone back into fastboot.
If you can get into fastboot, there are plenty of guides which can help you flash a twrp image. If you want me to give you some instructions on that just reply and let me know. Good luck!
Note that this phone doesn't have download mode (as some other Android devices do); nor is there a button combo to go directly to recovery. But you can almost certainly still get to bootloader, and from there boot recovery. In the current condition, you can get to bootloader by:
1) Hold Power+ vol up (as you have been) to restart the phone.
2) Once the screen goes dark (signaling it is about to reboot) let go of the buttons, and only hold vol down
3) Don't let go of vol down until the bootloader screen appears.
4) If the above sequence fails, its virtually always because the user just didn't get the timing right (either started pressing vol down too late, or let go too early). Just repeat steps 1-3 until you get to bootloader.
Once in bootloader, try to reflash the ROM, or restore a TWRP backup (if you have one). Spontaneously stuck on HTC logo screen is often a result of the OS/ROM becoming corrupt or otherwise damaged, and flashing/restoring the ROM will often fix it.
Thanks @redpoint73 I've managed to get to the preinstalled recovery.
Sadly reflashing/factory reset failed few times due corrupted files.
I'm ok with the fact that I lost the data on the phone since most of it was stored on the cloud.
Now I need ROM to flash on the phone thru recovery but I don't know which one would you reccomend.
It's my mom's phone so basically reliabilty and robustness over flashing lights and numerous unnecessary functions.
Version of android doesn't really matter.
Thanks again for help so far.
Can I put the rom I'm about to flash on external SD Card or I have to transfer it thru computer to the phone?
TWRP might be extra helpful or the recovery it's functions are just fine?
Shewie said:
Thanks @redpoint73 I've managed to get to the preinstalled recovery.
Sadly reflashing/factory reset failed few times due corrupted files.
I'm ok with the fact that I lost the data on the phone since most of it was stored on the cloud.
Now I need ROM to flash on the phone thru recovery but I don't know which one would you reccomend.
Click to expand...
Click to collapse
I'd need to know more about the phone in order to give any suggestions.
With the phone connected to computer, boot into fastboot mode, and (assuming you have fastboot setup on your computer) do the command: fastboot getvar all
Then post the results (delete IMEI and serial number before posting).
Also, what version TWRP (if that is the recovery installed)?
Shewie said:
Can I put the rom I'm about to flash on external SD Card or I have to transfer it thru computer to the phone?
Click to expand...
Click to collapse
You will be able to flash a ROM from the SD card, if using TWRP.
Shewie said:
TWRP might be extra helpful or the recovery it's functions are just fine?
Click to expand...
Click to collapse
Not sure what is being asked here (can't quite understand). Are you saying that another recovery besides TWRP is presently installed?
@redpoint73 I don't have TWRP but this...
Maybe pictures will justify the real situation.
I don't have the fastboot preinstalled on computer. (yet)
I wouldn't mind link to the pack with "must have" to complete the process
Shewie said:
@redpoint73 I don't have TWRP but this...
Maybe pictures will justify the real situation.
I don't have the fastboot preinstalled on computer. (yet)
Click to expand...
Click to collapse
You have what is called the "stock recovery" or official HTC recovery.
You can't flash anything but OTA updates, or other official (HTC) signed zips with this. You need a "custom" recovery like TWRP in order to flash things like custom ROMs. So I'm curious what you meant before when you posted:
Shewie said:
Thanks [MENTION=660462]Sadly reflashing/factory reset failed few times due corrupted files.
Click to expand...
Click to collapse
What exactly were you trying to "reflash", what were the exact steps, and the results (specific error messages, etc.).
I did the factory reset but it didn't help still stucking at ONE logo like posted initially. So this is basically the situation right now. I was able to get to recovery but nothing else.
Shewie said:
I did the factory reset but it didn't help still stucking at ONE logo like posted initially. So this is basically the situation right now. I was able to get to recovery but nothing else.
Click to expand...
Click to collapse
Okay, so you're confusing the terms. Factory reset doesn't flash/reflash anything (flash meaning to install some firmware or software to the device). The only thing that factory reset does is wipe user data.
At this point, I'd suggest the best/easiest course of action in the current conditions (stock recovery, locked bootloader) would be to run the RUU intended for your device. Your device is the AT&T version, so the RUU can be found at the bottom of the page (and instructions on how to install): http://www.htc.com/us/support/htc-one-m8-att/news/
RUU is a complete factory image. You download to a PC (PC required, won't work on Mac or Linux) connect the phone (booted into bootloader-fastboot mode) then just run the RUU, and it will do the rest.
I'm confidant this will get the phone up and running. Your mom may not like all the AT&T branding and apps, if it wasn't there before, and AT&T is not her carrier (one of the main reasons for these devices to have custom ROM - to remove carrier branding). But we can cross that bridge (if need be), after we get the phone working.
Installed Software, downloaded RUU from website provided, turned phone into fastboot before installing RUU.
Something started happening with the phone during installation but installation itself cant be finished, it's an endless process of update, phone is already plugged 3rd hour or so to the computer but the update status remain the same.
Should I try different approach?
Shewie said:
Installed Software, downloaded RUU from website provided, turned phone into fastboot before installing RUU.
Something started happening with the phone during installation but installation itself cant be finished, it's an endless process of update, phone is already plugged 3rd hour or so to the computer but the update status remain the same.
Should I try different approach?
Click to expand...
Click to collapse
It just gets stuck sometimes. Just kill the process, and start the RUU again. It will probably work fine on the next try. It's a bit scary, as it says not to stop the process or disconnect the phone while it's running. But if it gets stuck like this, there isn't anything else you can do.
Good News, it's working. But it's bloated to the bones. How I can get rid of the carrier unnecessary software?
I was to afraid to kill the process during update to avoid scenario of bricking my phone completely.
But It's working!