Hi XDA-Fellows
1) thanks for all the help of this community so far
2) my problem: I had my HTC One M8 rooted, installed TWRP (I think in the end I had 2.7.8.0 as last version) and Cyanogenmod with a nightly build of around 18. March 2016 installed! THEN the big mistake happened. In advanced developers menu of cyanogenmod I activated the option that was called something like "on update of system also replace recovery software". That obviously was stupid.
Upon rebooting normally TWRP launched and installed the latest nightly. This time I see the white screen with HTC logo on it, red text in bottom, top part of the screen shows "ENTERING RECOVERY", 3 seconds later I see a black screen and every like 2 or 3 seconds it looks like the screen gets powered, it flashes darkgrey shortly (again, looks like it gets powered but instantly shuts off immediately).
This just can be stopped by pressing either P+U or P+D for like 10 seconds. Then again, white screen with HTC logo and ENTERING RECOVERY and the screen switch on/off-loop.
Is my device bricked? What can I do now?
Any help is appreciated.
Hi,
Can you enter to your bootloader ? So maybe you can just reflash it to see if it's going to work..
BelDev said:
Hi,
Can you enter to your bootloader ? So maybe you can just reflash it to see if it's going to work..
Click to expand...
Click to collapse
Yes I can enter bootloader. How should I go on from here on?
Well you just need to download the new TWRP from their web site https://dl.twrp.me/m8/ after that you put your device into bootloader and you plug your phone into your computer and download a toolkit from xda like htc one m8 toolkit and you follow the instructions..
BelDev said:
Well you just need to download the new TWRP from their web site https://dl.twrp.me/m8/ after that you put your device into bootloader and you plug your phone into your computer and download a toolkit from xda like htc one m8 toolkit and you follow the instructions..
Click to expand...
Click to collapse
Thanks. I will give it a try and give feedback.
It worked. I could enter bootloader, switched to FASTBOOT mode, installed ADB Drivers for windows and replaced recovery with latest TWRP! THanks a lot for your help! I thought I could throw away my M8
Well. It worked not completely. I was able to reboot my phone into the Cyanogenmod. But upon entering recovery mode (which I expected now to be TWRP) I get the same result again ... Screen off/on within seconds, repeating endlessly
I think you need to reflash the boot.img and the ROM completely. Because i don't know why do you have a black screen.
I activated root access for apps and tried ROM Manager first! It failed, then I used flashify which worked. Automatically downloaded latest TWRP (3.0.0.1) and flashed it, reboot into recovery. Everything works like a charm again! Thanks again for your help!
Related
Hi,
I rooted my phone about a year ago and recently wanted to update it and try a new ROM. Since I have no idea what the compatibility of of my old ROM I made a NAND backup then I reset it to the factory RUU version 3.29.651.5 and my phone was back to normal in the boot loader S was set as S-on.
I then proceeded to use the autoroot v2.5 in this thread: http://forum.xda-developers.com/showthread.php?t=838448. In the cmd prompt it said it was flashing the firmware, then said it was waiting for the device to boot up; however, the device did not boot up, I waited for approx 60 min and it was stuck on a black screen with the HTC logo in the middle and a small warning (triangle with exclamation point) in each corner. Now, it is permanently stuck on that screen. Even if I try to hold the volume down to get to the boot loader when it starts, it still goes to this screen.
What can I do to try to get out of this? I cant go back to my recovery to get my backup.
Thanks
Sorry if I incorrectly used some of the terms in this post.
alibabazhang said:
Hi,
I rooted my phone about a year ago and recently wanted to update it and try a new ROM. Since I have no idea what the compatibility of of my old ROM I made a NAND backup then I reset it to the factory RUU version 3.29.651.5 and my phone was back to normal in the boot loader S was set as S-on.
I then proceeded to use the autoroot v2.5 in this thread: http://forum.xda-developers.com/showthread.php?t=838448. In the cmd prompt it said it was flashing the firmware, then said it was waiting for the device to boot up; however, the device did not boot up, I waited for approx 60 min and it was stuck on a black screen with the HTC logo in the middle and a small warning (triangle with exclamation point) in each corner. Now, it is permanently stuck on that screen. Even if I try to hold the volume down to get to the boot loader when it starts, it still goes to this screen.
What can I do to try to get out of this? I cant go back to my recovery to get my backup.
Thanks
Sorry if I incorrectly used some of the terms in this post.
Click to expand...
Click to collapse
The first time I tried to Root my phone, I had the same problem with Toasts Root method. That's stock Recovery you're seeing.
I ended up having to use Unrevoked Linux version and swore I would never unroot again, and I haven't.
I've tried using unrevoked and several other methods. The problem is I think most of them rely on the phone being on with USB debugging enabled. I unfortunately can't get there. The one ray of hope I have is that the device is recognized in my device manager as "Android USB device - HTC bootloader". Is there any other way I could fix this?
alibabazhang said:
Hi,
I rooted my phone about a year ago and recently wanted to update it and try a new ROM. Since I have no idea what the compatibility of of my old ROM I made a NAND backup then I reset it to the factory RUU version 3.29.651.5 and my phone was back to normal in the boot loader S was set as S-on.
I then proceeded to use the autoroot v2.5 in this thread: http://forum.xda-developers.com/showthread.php?t=838448. In the cmd prompt it said it was flashing the firmware, then said it was waiting for the device to boot up; however, the device did not boot up, I waited for approx 60 min and it was stuck on a black screen with the HTC logo in the middle and a small warning (triangle with exclamation point) in each corner. Now, it is permanently stuck on that screen. Even if I try to hold the volume down to get to the boot loader when it starts, it still goes to this screen.
What can I do to try to get out of this? I cant go back to my recovery to get my backup.
Thanks
Sorry if I incorrectly used some of the terms in this post.
Click to expand...
Click to collapse
Are you holding power and volume down at the same time. Sounds like you are just holding volume. When you get to the bootloader I'd you see s-off all you will need to do is flash a PC36IMG of the recovery of your choice(I recommend twrp). Good luck!
Sent from my PC36100 using XDA Premium App
Also, no need to unroot for any rom. Once you are rooted you can flash anything you want. Compatibility wise, you may need to update a radio but that is just flashed in recovery.
Sent from my PC36100 using XDA Premium App
Thanks for the reply. Unfortunately I am holding power and volume down. Powering it on normally and powering it on while holding volume down both go to the same screen.
Good Morning All -
A few days ago, I dualbooted my N7 with Ubuntu. The installation went fine and the tablet was working with no issues over the last several days. Last night, I was using the tablet and set it down. I went to pick it up (roughly 5 minutes later) and the touch screen was unresponsive. I was at the lock screen but couldn't get it to unlock. I pushed the wrong key-combo first and the device took a screen shot.
I was able to reboot into fastboot and attempted to go to recovery. The device would just hang at the Google logo. I pushed a factory firmware update from my Ubuntu system and attempted to reset -- no joy. This morning, I used Nexus Root Toolkit from my Windows 8 machine to see if I could get it up. Root Tool kit worked fine, pushed the images over again and restarted but it continues to hang at the Google logo.
Looking for any other advice folks may have on getting the device to boot.
EDIT: I can get to the bootloader fine and the computer recognizes it.
Thanks!
Alright... I just attempted using NRT and flashing 4.4.2 instead of 4.4.3 to see if it would run through. No joy, again. Remains on the Google screen.
xbi0s said:
Alright... I just attempted using NRT and flashing 4.4.2 instead of 4.4.3 to see if it would run through. No joy, again. Remains on the Google screen.
Click to expand...
Click to collapse
Im having the same problem with an unlocked unit. I would bet if you tried to do a factory reset in the android recovery menu it would give you a huge error all having to do with cache.
antonio824 said:
Im having the same problem with an unlocked unit. I would bet if you tried to do a factory reset in the android recovery menu it would give you a huge error all having to do with cache.
Click to expand...
Click to collapse
I'm unable to get into the restore menu. Hangs at the Google logo when attempting to get there.
I've tried about any solution I could find... Bumping one last time before I torch the unit :\
Nothing can be done. Its something inside. If its the 2013 model, call and get it rma'd. Sorry man.
Sent from my LG-LS970 using XDA Premium HD app
Resurrecting this thread to keep a work log.
I made have made some progress but hitting another roadblock. I've been holed up at home due to an auto accident so I started tinkering with the N7 2013 again.
Using the Nexus Root Toolkit, I am able to launch "Boot Temporary - Custom Recovery" from the advanced options. The problem I now run into is TWRP's touchscreen will not work. I attempted to do volume up/down to see if I could select but it wouldn't. The software is not frozen as I can see the temperature changing.
Anyone have any thoughts or information on how to boot another custom recovery that uses button inputs? I appreciate any input.
Updates:
1. I was able to push TWRP via "fastboot flash recovery." It went to the Google Logo then loaded TeamWin screen. I started to see errors when the program launched. "Unable to mount..." multiple times then the device rebooted. Device stuck on the Google screen.
2. Shut the device down, booted back into Fastboot. Selected Recovery and it began loading again. This time, the app launched and worked. Touchscreen does not work but the CPU temp is fluctuating and minutes tick up.
Update 4:49PM Central:
1. I am able to install and boot into TWRP 2.8.0.1 through TWRP 2.7.1.1. Those versions load but of course touch screen does not work.
2. I have been unable to get CWM to load... It installs fine but I cannot boot into.
3. The factory recovery images also do not load.
I've just update my firmware using my thread http://forum.xda-developers.com/showthread.php?t=2696282
I'm S-On and followed every instruction. When the phone boot (everything was succesfull), it was stuck on the HTC welcoming screen.
Then I thought because the rom installed didn't match the new firmware, so I decided to unlock the bootloader, that too was fine. But then when the phone boot up, I again got stuck on the HTC welcoming screen. Then I tried adb to boot into the bootloader to flash the TWRP custom recovery, but nothing to do, adb is not recognising the phone. But the storage of my phone is appearing on windows explorer and the drives were successfully installed automatically.
What should I do, urgent please anyone
Thanks
92davin said:
I've just update my firmware using my thread http://forum.xda-developers.com/showthread.php?t=2696282
I'm S-On and followed every instruction. When the phone boot (everything was succesfull), it was stuck on the HTC welcoming screen.
Then I thought because the rom installed didn't match the new firmware, so I decided to unlock the bootloader, that too was fine. But then when the phone boot up, I again got stuck on the HTC welcoming screen. Then I tried adb to boot into the bootloader to flash the TWRP custom recovery, but nothing to do, adb is not recognising the phone. But the storage of my phone is appearing on windows explorer and the drives were successfully installed automatically.
What should I do, urgent please anyone
Thanks
Click to expand...
Click to collapse
[Resolved]
hold up and down volume keys then power button to switch off device. Then boot into bootloader through volume down and power button. Flash recovery and install rom. Panicked for nothing
I have a HTC One m8(Marshmallow 6.0) from Verizon. It's unlocked and I'm using it on the cricket network. I got S-off(sunshine) and put the latest TWRP on it. However ever root method(kingroot, kingoroot, etc) I try it's not working. Don't want to pay One Click Root $30 to root it. Any suggestions? Thanks
Download SuperSU from the app store and try the built in methods.
If neither work, you need the root installation zip and to flash it through TWRP>Install
I just rooted on a Verizon HTC One M8 with Marshmallow and was navigating to this forum to find a good rom and radio.
I got it done by downloading the supersu zip file and used TWRP to flash it. I wasn't rooted so I had to do it this way ... none of the apps will work if you aren't already rooted. Make sure you have downloaded the supersu .zip file and not the .adk file, otherwise it won't be available in supersu to flash.
I did that and now it's stuck on the verizon red screen. I tried factory resetting(fastboot). And that didn't work. The only way i seem to be able to get the phone to turn on is to let it die and charging it to like 2% and go into fastboot mode and if i reboot it.... it goes to the verizon red screen and just stays there.
Msmala85 said:
I did that and now it's stuck on the verizon red screen. I tried factory resetting(fastboot). And that didn't work. The only way i seem to be able to get the phone to turn on is to let it die and charging it to like 2% and go into fastboot mode and if i reboot it.... it goes to the verizon red screen and just stays there.
Click to expand...
Click to collapse
Try flashing current stable SuperSU 2.78 in zip version (flash with TWRP) from here: http://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703
Also, you need to be on a relatively recent TWRP version. Current is 3.0.2
https://dl.twrp.me/m8/
Also, no need to let the battery die, to restart to bootloader. Force a reboot by holding Power+Vol up for a minute or so. Once the screen goes dark to reboot, slide your finger from vol up, to vol down, to boot into bootloader.
Also, you should always do a TWRP backup before trying to root, so you can revert if something like this goes wrong.
Hi,
Trying to root the following unlocked phone of mine..
Current Mobile version : HTC Desire 816 A5_DWG "India" - Dual Sim
Software version : 3.14.720.1 / Marshmallow 6.0 with HTC Sense 7.0
I flashed 5/6 different TWRP/CWM versions via ADB/Fastboot as the phone is accessible... but when I try to enter the Recovery, in CWM the screen goes blank while with TWRP, the Phone actually starts an infinite boot loop with "Entering Recovery" -> Down - > "Entering Recovery".. the connected phone is not available to ADB/Fastboot during this time... and I have to wait for Phone battery to exhaust, so I can start the phone in Bootloader and restart as normal.. Can anyone point me to the actual TWRP/CWM or any other Recovery image for the model & version? The phone has no external card, not sure if that could be a limitation in the process? Also do I need to unlock the phone every time I put Stock Recovery back?
thanks in advance
I just stumbled upon your exact problem after flashing twrp-3.1.0-0-a5.img
I flashed the oldest version of TWRP I can find on twrp.me (twrp-2.7.1.0-a5.img) and now it's all okay.
BTW, while the phone looping the "entering recovery mode" process, you can hold both Up volume and Power button to boot normally instead of waiting for the battery to drain exhaust.
dduck2683 said:
I just stumbled upon your exact problem after flashing twrp-3.1.0-0-a5.img
I flashed the oldest version of TWRP I can find on twrp.me (twrp-2.7.1.0-a5.img) and now it's all okay.
BTW, while the phone looping the "entering recovery mode" process, you can hold both Up volume and Power button to boot normally instead of waiting for the battery to drain exhaust.
Click to expand...
Click to collapse
Thanks a lot for both the pointers... TWRP, the old version did work and also the up volume+ power is working fine.. But after getting into TWRP and wiping partitions & data, the system is now booting to always hung state (stuck on white HTC boot screen).. Can get to bootloader/fast boot, but ADB doesnt detect the device now.... When I enter TWRP, the phone is detected in adb in the "recovery mode" , but fastboot doesnt work.. How can the stock recovery/other recovery be installed at this hung state..
thanks in advance
If you have a ROM (or a backup image), you can flash it when you're in recovery mode; I don't think you need ADB to do that?
And also, what is the cid of your phone and what image did you use?
Sorry for the delay.
dduck2683 said:
I just stumbled upon your exact problem after flashing twrp-3.1.0-0-a5.img
I flashed the oldest version of TWRP I can find on twrp.me (twrp-2.7.1.0-a5.img) and now it's all okay.
BTW, while the phone looping the "entering recovery mode" process, you can hold both Up volume and Power button to boot normally instead of waiting for the battery to drain exhaust.
Click to expand...
Click to collapse
I have the same problem with latest version 3.1.0-0, though older versions working fine. Could you manage to get the latest version working? or the image file has bug?
panijsr said:
I have the same problem with latest version 3.1.0-0, though older versions working fine. Could you manage to get the latest version working? or the image file has bug?
Click to expand...
Click to collapse
It's quite difficult to find a suitable image for my phone so I ended up using the old version of TWRP. I don't really know if it's a bug in the image file or TWRP itself.
But then again, why do you want to use the latest version of TWRP?
dduck2683 said:
It's quite difficult to find a suitable image for my phone so I ended up using the old version of TWRP. I don't really know if it's a bug in the image file or TWRP itself.
But then again, why do you want to use the latest version of TWRP?
Click to expand...
Click to collapse
Previous versions of TWRP were not able to decrypt/ access my 'adopted SD-card' (merged with internal memory).
I was hoping , the latest version would be able to do that.