Hi,
My phone got the red triangle and exclamation mark after upgrading my firmware. I believe this was due to it wiping the custom recovery which was TWRP. I have tried to reinstall TWERP but I get stuck on the entering recovery screen.
I have tried to install twrp a couple of times with no joy but I have a copy of philz recovery and this installed 1st time.
Any ideas? I have tried clearing the cache in fastboot but am stuck.
I have no phone as the rom I install is on the ext sd card and Philz touch will not mount the ext sd card.
Thanks in advance
Ugg
uggitt said:
My phone got the red triangle and exclamation mark after upgrading my firmware. I believe this was due to it wiping the custom recovery which was TWRP. I have tried to reinstall TWERP but I get stuck on the entering recovery screen.
Click to expand...
Click to collapse
You reverted to stock recovery, which flashing firmware will always do, unless its a modded firmware which has the stock recovery removed.
Confirm that your bootloader is UNLOCKED (which is needs to be to flash recovery).
Also, if you update to Lollipop firmware (which is usually the reason for updating firmware) you need to use one of the more recent TWRP versions. I recommend TWRP 2.8.7.
Older TWRP versions do not work on LP, and fail to install properly is the mode of failure. Similarly, Philz does not work on LP.
EDIT: To clarify TWRP build.
I have checked and the bootloader is unlocked, s-off and super cid.
The problem is I cannot get twrp to load up. I install it with fasboot and all goes well but when I try to get into recovery it just stays on the entering recovery screen.
I have tried to reinstall the latest firmare using the'Firmware Flashing without the panic attacks' guide as I have always used and this seems to install ok and then tried to install twrp again ( I have tried the latest and the previous copy) but no joy. I can though install philz recovery and that boots up fine.
So still stuck trying to get twrp installed.
Also if I reboot the phone hangs while starting upon the htc screen with red text but the phone is actually working behind this, just cant see the normal desktop/startup screen. If i hold the power button so the screen goes off and the hold the power button to turn it on the screen comes to life.
For information, I am on Android HD 41.0 as this is the only rom I had on the internal sd
What numbers listed on hboot screen:
- hboot number
- radio baseband
- OS
And what version TWRP are you trying to install?
Hi,
Here is the info from getvar and thank you for your help:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.16.2133156.UA15G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.54.401.10
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: FA459WM******
(bootloader) imei: ********************
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 098a72e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Twrp versions tried are 2.8.7.0 and 2.8.6.1 from https://twrp.me/devices/htconem8gsm.html
redpoint73 said:
Older TWRP versions do not work on LP, and fail to install properly is the mode of failure. Similarly, Philz does not work on LP.
Click to expand...
Click to collapse
I beg to differ, no problems running 2.8.5.0 or 2.8.6.0 on lollipop for me. Installed via fastboot or flashify.
uggitt said:
Here is the info from getvar and thank you for your help:
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.16.2133156.UA15G
(bootloader) version-main: 1.54.401.10
Click to expand...
Click to collapse
Your firmware flash never properly "stuck".
Your getvar data indicates you are on the original version firmware (1.54) which is over a year old. The current firmware would have updated you to hboot 3.19, radio 1.2xxx, and main version 4.16.401.
This also explains why Philz works, and the current versions of TWRP do not work. The current TWRP versions only work on Lollipop firmware; and only older TWRP versions work with your 3.16 firmware.
Try running the 4.16.401 firmware twice, this is often necessary to get it to flash properly. Then once you've confirmed you are on hboot 4.16, radio 1.2xxx, main version 4.16.401, then try TWRP 2.8.7.
---------- Post added at 03:19 PM ---------- Previous post was at 03:14 PM ----------
ashyx said:
I beg to differ, no problems running 2.8.5.0 or 2.8.6.0 on lollipop for me. Installed via fastboot or flashify.
Click to expand...
Click to collapse
True, a few of the recent builds will work on LP. But older ones than that won't work, trust me. I forget the breakoff point exactly, which is why I recommended the most current version (2.8.7). And once the most current version is known to be stablen (which 2.8.7 is), its usually the best recommendation.
I didn't mean to state that 2.8.7 is the only version that works. But I see how it can be interpreted that way (and have edited the previous post for clarity). For some reason, I constantly see folks still trying to flash much older TWRP builds (2.7 or so) onto Lollipop (which won't work).
And it turns out the OP had the opposite issue (trying to flash newer version TWRP on really old firmware hboot 3.16).
Thank you, I will try and flash the firmware again. Have you a link for this. I have been getting it from the ARHD Firmware page but not sure if its corrupt.
uggitt said:
Thank you, I will try and flash the firmware again. Have you a link for this. I have been getting it from the ARHD Firmware page but not sure if its corrupt.
Click to expand...
Click to collapse
4.15.401 (Euro) firmware is probably the most commonly downloaded and installed firmware from that collection. So it should be fine.
You probably just flashed the firmware once; when twice is often needed.
I managed to get the updated firmware on my phone eventually. I had to download from another link and it flashed first time.
Twrp installed straightaway and I am back on S.Rom.
Thank you for all your help, much appreciated
ugg..
Related
Hello everyone,
My friend has tried to get into the rooting scene and without proper knowledge he managed to get himself stuck on the boot screen.
I offered him my help, since I thought that this would be an easy fix because the phone still has access to the TWRP recovery.
What I didn't know is that the phone was branded and S-on. The CID is: VODAPE17.
ADB works in recovery mod !
To sum it up:
CID: VODAPE17
The bootloader is unlocked
S-on
Acces to custom recovery
no backup
adb works
fastboot works
What I have tried:
I tried to get the device S-off with HTC dev. But it required me to boot up the phone, so that didn't work out.
I have found a nand backup that should work with this CID on this page: http://forum.xda-developers.com/showthread.php?t=2701376&page=5
This one: 3.29.161.9 - TWRP Thanks to Petert87 (what does that number: 3.29.1619 mean?)
I unpacked the file. Send it to the internal storage and renamed it to a backup that I had made myself (otherwise TWRP wouldn't recognize it?).
After wiping I restored the backup, but to my surprise the phone still was stuck on the HTC one logo when I tried to boot it!
I tried to get as much information from the phone as possible.
This is what I got:
version: 0.5
version-bootloader: 3.19.0.0000
version-baseband: 1.25.214500021.06G
version-cpld: None
version-microp: None
version-main: 4.19.161.2
version-misc: PVT SHIP S-ON
product: m8_ul
platform: hTCBmsm8974
modelid: 0P6B10000
cidnum: VODAPE17
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: 3aa067db
hbootpreupdate: 11
gencheckpt: 0
My question
Can anyone help me to get this phone running again? I don't really know what to do anymore.
Every bit of help is appreciated very much! :good:
Thank you in advance!
Sietse
After flashing countless amounts of customs roms I still don't make any progress.
I have even tried to flash the boot.img of a custom rom separately with fastboot but that didn't work either.
Something is preventing this phone from booting, but I don't know what
Does anyone have idea's? They will be greatly appreaciated!
Download and install latest TWRP from their website, not playstore. Do full wipe including system, then format data typing yes to confirm. Download compatible ROM to extSD, mount extSD in TWRP and install from extSD. That's what I would try. Your firmware looks up to date..
flyera343 said:
Download and install latest TWRP from their website,
Click to expand...
Click to collapse
Agree, this is very important. Some older versions of TWRP won't work with the current hboot. You can drive yourself crazy flashing a hundred ROMs, and it still won't work.
Same issue here. Latest firmware. S-ON. Every custom ROM causes a boot loop. Luckily I had a nandroid of stock ROM (5.0.1) so I can always go back to stock.
petrjanda said:
Same issue here. Latest firmware. S-ON. Every custom ROM causes a boot loop. Luckily I had a nandroid of stock ROM (5.0.1) so I can always go back to stock.
Click to expand...
Click to collapse
As already stated by myself and another, make sure TWRP is up to date (2.8.7). Outdated TWRP is the most common cause for many ROMs bootlooping.
Hey there.
I'm fairly new-ish to the Android modification scene. I've had android phones for a while but only recently started rooting etc one my One M8. I've got the Bootloader Unlocked with S-Off and am also on just the stock rom (or I was as I'm in the middle of attempting to get custom roms. :L). My custom recovery is TWRP 2.8.7.0, the latest and the roms I have been trying to install so far are the latest SkyDragon v10 Sense 7 and ViperOne 4.6.0 roms.
In TWRP, when doing this, it will go through the custom installation setup stuff and afterwards it will go into a never ending bootloop for around an hour before I decide to hold volume up and power to switch it off.
Now, before I do the initial installation of the rom, I have wiped data, system, cache and the Dalvik. Regardless, it still causes a boot loop. I have switched the phone off and waited 30 seconds. Still a bootloop. I have gone back into recovery and re-wiped the cache and dalvik and still get this bootloop.
Another thing to note, I have a pending update which is to fix the something which I received at the end of August for the OTA thing and when I put stock recovery back onto the phone to try and do an OTA for that as well, I get the same issue. The only difference is that due to that being the official rom, it also has sound during the bootup but one thing to note (aside from it doing exactly the same and doing a bootloop), the boot animation sound is also delayed by 5 seconds or so, unlike before the update where it plays at the same time as the boot animation.
I am able to successfully restore my TWRP backup of my OS before it attempts something like this and was last working but that's as far as it goes.
I am at a complete loss as I am following any and all tutorials I can find online to the letter and yet I am still having no luck here.
Can anyone assist me on this? It would be much appreciated. Thank you in advance and for reading.
ThatOneJoshy said:
I am able to successfully restore my TWRP backup of my OS before it attempts something like this and was last working but that's as far as it goes.
Click to expand...
Click to collapse
That show your TWRP backup is not stock enough or it is a rooted stock and that is why the OTA failed.
You need a pure non-rooted backup or RUU to successfully update.
What's your device details ?
Run command fastboot getvar all and post here minus the serial & imei no.. maybe someone will be able to point you to right direction.
ckpv5 said:
That show your TWRP backup is not stock enough or it is a rooted stock and that is why the OTA failed.
You need a pure non-rooted backup or RUU to successfully update.
What's your device details ?
Run command fastboot getvar all and post here minus the serial & imei no.. maybe someone will be able to point you to right direction.
Click to expand...
Click to collapse
It's stock firmware that came on the phone, although it is rooted with SuperSU. Whenever I looked online, every forum board said that having a rooted phone wouldn't prevent an OTA, although having a custom recovery would so I would flash the stock recovery back onto the phone and do the update that way which would in turn create this boot loop.
My RUU is/ should be exactly the same as I haven't done anything to change it and also, the updates still come through and are downloaded that way. It also installs (so I think as it goes through the normal process of updating that my phone has always done showing an image of an updating phone with a loading bar at the bottom whilst rebooting a couple of times).
In terms of the details requested, I'm not sure if it will be affected by the rom I just tried installing again for ViperOneM8, but they can be found below:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.25.214500021.06G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.16.401.13
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: ************
(bootloader) imei: ****************
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: f063fb42
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
The version I am on on the stock rom is 4.16.401.10. I'm not sure why that is showing, unless it's because of the ViperoneM8 mod I installed which also features the same patch released by HTC apparently.
Yeah, almost everyone say the same thing and those forum are correct for ROMs prior to lollipop.
On lollipop .. root works differently that is why you can't do update on a rooted lollipop stock ROM.
The only suggestion I have is keep your TWRP backup.
Restore a non-rooted 4.16.401.10 TWRP backup and its stock recovery and do the update. After the update, restore your saved data and re-root or install any ROM that you like.
I have one backup in my thread : http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Read these thread on how people solved their same problem as yours
http://forum.xda-developers.com/htc-one-m8/help/os-sos-t3192177
http://forum.xda-developers.com/htc-one-m8/help/stuck-boot-ota-update-t3192441
Hi,
Having issues trying to put SuperSU on my M8. Heres what I've done:
- Unlocked bootloader
- Fastbooted TWRP on the phone
- Tried Flashing the ROM, says No OS installed. Rebooting stops at Android screen
- Tried downloading RUU and going back to stock, however the RUU tells me that there's an error and it can't continue.
- Tried switching between TWRP and CWM.
- Tried sideloading from my pc with a few different versions of SuperSU
Nothing seems to work.
Can anyone point me in the right direction?
Any help will be greatly appreciated.
If there's any more information you would like me to provide, just let me know.
Thanks Again,
Nick
My responses below in red font:
varioushalifax said:
Having issues trying to put SuperSU on my M8. Are you trying to root the stock ROM, or flash a custom ROM? Because they are 2 different things, with different approaches. And your steps described below contradict each other on this matter..
Heres what I've done:
- Unlocked bootloader
- Fastbooted TWRP on the phone What version TWRP?
- Tried Flashing the ROM, says No OS installed. Rebooting stops at Android screen Which ROM exactly? Did you try another ROM? Did the ROM install properly (any error messages in TWRP when you flashed?
- Tried downloading RUU and going back to stock, however the RUU tells me that there's an error and it can't continue. What RUU (exact file name)? What was the error message and error number? These are important, as they tell you why the RUU failed.
- Tried switching between TWRP and CWM. Not recommended. CWM hasn't been updated in a long time, and can cause some problems in itself.
- Tried sideloading from my pc with a few different versions of SuperSU If you have no OS, flashing SuperSU isn't going to help matters.
Click to expand...
Click to collapse
Additonally, do fastboot getvar all, so we can see more info about the phone. Delete IMEI and serial number before posting.
Are you trying to root the stock ROM, or flash a custom ROM?
Originally I tried to put SuperSU2.37 on there, that didn't work, so I tried SuperSU2.77, which failed. I then tried to RUU to stock, which I'm having issues with also.
- What version TWRP?
3.0.2-0
- Any error messages in TWRP when you flashed?
It doesn't show any errors. After it's finished it says No OS Installed, are you sure you want to reboot?
- What RUU (exact file name)?
RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4.exe
Error 155
Please get the correct RUU and try again.
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.12G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__203
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Thanks again,
Nick
redpoint73 said:
My responses below in red font:
Click to expand...
Click to collapse
your method to solve problems to the point by red font is very nice master redpoint. :good:
varioushalifax said:
Originally I tried to put SuperSU2.37 on there, that didn't work, so I tried SuperSU2.77, which failed.
Click to expand...
Click to collapse
SuperSU version 2.37 is really old. Not sure how you even came about it (old toolkit maybe?), that version probably wouldn't work on Lollipop, much less your current Marshmallow firmware.
SuperSU 2.77 should be okay, its current and updated for MM. I might suggest the latest "STABLE" version, which is 2.76 from here. But honestly, they are all pretty stable from what I've seen, and it probably wouldn't make a huge difference wither way (the version 2.77 should be ok). And it seems like the main problem is that we need to solve the "No OS" issue before proceeding.
varioushalifax said:
It doesn't show any errors. After it's finished it says No OS Installed, are you sure you want to reboot?
Click to expand...
Click to collapse
My guess, is that you did something to delete the OS, that maybe you missed when listing the steps you did. Since, I can't see how OS could be wiped/missing with what you indicated. At least up until you tried RUU, since if you relocked the bootloader to RUU (which is a requirement unless you have s-off), that wipes the OS (so maybe you just have the order of steps you tried, mixed up?).
varioushalifax said:
RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4.exe
Error 155
Click to expand...
Click to collapse
That RUU isn't for your version. Maybe the "WWE" in the file name has you confused, but its actually for the US Developer's Edition. What you need would have version number with "401" instead of "1540", but you would only know that from experience or reading it somewhere on the forums.
You should be able to use the following RUU (zip format, not exe - so follow the instructions to flash): http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Alternately, restore the stock TWRP backup 6.12.401.4 using the file and instructions here: http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Not sure whether your bootloader is currently relocked or unlocked, as you haven't indicated, either way. It needs to be relocked to RUU, or alternately it needs to be unlocked to do the TWRP stock backup method.
---------- Post added at 09:35 AM ---------- Previous post was at 09:17 AM ----------
umesh.lk said:
your method to solve problems to the point by red font is very nice master redpoint. :good:
Click to expand...
Click to collapse
Haha, I find that a good way to respond to numerous statements or questions in a previous post; rather than using multiple quotes. And red just seems to stand out well, compared to other colors! But love your observation.
Thanks so much!
I wasn't sure which files i needed for that walkthrough, until you told me which ones.
Phone is back up and working fine.
Thanks again mate
I'm currently running CM12.1 on my HTC One M8, and have been successfully doing so for the past 6 months.
I decided to try and install CM13 today after all this time, and the CM13 and Gapps install were clean (i.e. TWRP reported it as successful) Then when I clicked reboot system, it loads into fastboot for some reason, not into the normal reboot screen.
Even after rebooting 5 or 6 times, it still repeatedly goes back into fastboot. Anyone had a similar problem who could help me out ?
I backed up, therefore am back to 12.1 for now.
Make sure you firmware is compatible, and you're using a compatible version TWRP.
If so, try another nightly, and try a different gapps. I don't use CM13 on my M8, but us it on my Samsung Tab Pro 8.4. On that, I've found CM13 to be finicky about gapps version. I've had most luck with Open Gapps, and the smaller gapps packages (pico, nano).
Also, make sure you wipe data, cache, and Dalvik. Trying to migrate data from CM12>Cm13 probably won't work, and cause no boot (as often the case with moving between major build changes).
redpoint73 said:
Make sure you firmware is compatible, and you're using a compatible version TWRP.
If so, try another nightly, and try a different gapps. I don't use CM13 on my M8, but us it on my Samsung Tab Pro 8.4. On that, I've found CM13 to be finicky about gapps version. I've had most luck with Open Gapps, and the smaller gapps packages (pico, nano).
Also, make sure you wipe data, cache, and Dalvik. Trying to migrate data from CM12>Cm13 probably won't work, and cause no boot (as often the case with moving between major build changes).
Click to expand...
Click to collapse
Apologies for the noobish response, but how can I check the compatibility of the firmware and TWRP? TWRP version is 2.7, I assumed that would be fine to install CM13 with?
Sugz said:
Apologies for the noobish response, but how can I check the compatibility of the firmware and TWRP? TWRP version is 2.7, I assumed that would be fine to install CM13 with?
Click to expand...
Click to collapse
TWRP 2.7 is over 2 years old. That is probably your problem right there, or at least part of it.
Do fastboot getvar all, and post the results (delete IMEI and serial number before posting) and we'll take a look to see if the firmware needs to be updated, as well (will also tell us which updated version TWRP to install).
redpoint73 said:
TWRP 2.7 is over 2 years old. That is probably your problem right there, or at least part of it.
Do fastboot getvar all, and post the results (delete IMEI and serial number before posting) and we'll take a look to see if the firmware needs to be updated, as well (will also tell us which updated version TWRP to install).
Click to expand...
Click to collapse
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.24.30336021.13G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m8_dugl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B64000
(bootloader) cidnum: HTC__J15
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 49d38c68
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Heres what i got with that command..
I just don't understand how CM12 was so easy to install, and this has caused so many problems.
Sugz said:
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.24.30336021.13G
Click to expand...
Click to collapse
Looks like from the above info you are on Lollipop firmware (hboot, radio, etc.) which should be okay with CM13, I believe (read the CM13 thread to confirm).
I recommend (with LP firmware) to flash TWRP 2.8.7 from here (includes the required TWRP img file, and instructions to flash with fastboot - if you don't already know how): https://twrp.me/devices/htconem8gsm.html
Sugz said:
I just don't understand how CM12 was so easy to install, and this has caused so many problems.
Click to expand...
Click to collapse
I'm guessing you haven't updated CM12 either in 6 months. Or if so, it wasn't updated for current firmware or recovery versions (not personally aware)?
But its very normal for newer CM versions to fail if you haven't updated hboot and/or TWRP versions. This is for your protection, to ensure proper compatibility. All the software/firmware components need to be updated, not just the ROM.
On that same note, whenever flashing a new ROM (and a major update of CM applies) its often a good idea to read through the specific ROM thread (not the whole thing, but at least skim through the more recent several pages) to see what firmware, TWRP versions are required, installation or other bugs, etc.
Thank you for your help. Turns out that I was completely stupid in installing the HTC One M8 ROM, instead of the M8 dual sim ROM which is what caused all these problems in the first place.
Successfully installed CM13 now with Gapps, functioning greatly.
Sugz said:
Thank you for your help. Turns out that I was completely stupid in installing the HTC One M8 ROM, instead of the M8 dual sim ROM which is what caused all these problems in the first place.
Successfully installed CM13 now with Gapps, functioning greatly.
Click to expand...
Click to collapse
You should still update your TWRP version. Using version from over 2 years ago, is asking for trouble. If not now, then at some point down the road.
Hi guys I have an HTC ONE M8 running 4.4.4 with TWRP and Root installed and a few weeks ago I tried to go into TWRP and clear cache and dalvik-cache and such, as usual. When I did that and rebooted the phone, the phone is stuck on the HTC logo and I can only boot into bootloader mode and also into TWRP. Also TWRP is also saying I have lost root access.
What can I do to fix this problem can I restore back to 4.4.4 as a new device and re-root it and install TWRP? How do I get out of this mess? It is S-ON and Software Status is MODIFIED.
No matter how long I leave the phone it will stay on the logo until it dies or until I boot into bootloader.
Thank You Guys I Have Lost Hope Honestly.
IF ANYONE CAN HELP ME PLEASE PROVIDE THOROUGH INSTRUCTIONS! THANK YOU!
First of all, the fact the screen comes on at all, means it almost certainly not bricked, and recoverable. You just can't boot into OS, and with TWRP installed, that is not too serious a problem.
On the other hand, once you have TWRP installed, the first thing you should always do before rooting or other mods, is to use TWRP make a backup of system and boot.img. And even after successful root, it's good to make a backup of the rooted ROM. If you had a TWRP backup o the phone, in an event like this (no boot into OS) you can simply boot into TWRP, and restore the backup.
If you have no backups, you can download the proper one from the collection: https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
You can then restore using the instructions from that same thread. You only need to do steps 4-9 to get the phone running again, then reboot. Steps 1-3 relate to installing TWRP (which you already have). Steps 10 and on, are optional as they will install stock recovery to the phone, which will allow you to update to more current Android version (which will eventually get you up to Marshmallow).
If you need help determining what version number TWRP backup to restore from the above linked collection, then do fastboot getvar all, and post the results (delete IMEI and serial number before posting).
Another option is to RUU back to stock (if your version M8 has an RUU) if you are okay with the phone being wiped. If you are s-on, you will need to relock the bootloader in order to RUU. Then after RUU, unlock the bootloader again, install TWRP and root the phone.
TechMan123456 said:
few weeks ago I tried to go into TWRP and clear cache and dalvik-cache and such, as usual.
Click to expand...
Click to collapse
What does "and such" mean? Did you wipe anything besides cache and Dalvik?
redpoint73 said:
First of all, the fact the screen comes on at all, means it almost certainly not bricked, and recoverable. You just can't boot into OS, and with TWRP installed, that is not too serious a problem.
On the other hand, once you have TWRP installed, the first thing you should always do before rooting or other mods, is to use TWRP make a backup of system and boot.img. And even after successful root, it's good to make a backup of the rooted ROM. If you had a TWRP backup o the phone, in an event like this (no boot into OS) you can simply boot into TWRP, and restore the backup.
If you have no backups, you can download the proper one from the collection: https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
You can then restore using the instructions from that same thread. You only need to do steps 4-9 to get the phone running again, then reboot. Steps 1-3 relate to installing TWRP (which you already have). Steps 10 and on, are optional as they will install stock recovery to the phone, which will allow you to update to more current Android version (which will eventually get you up to Marshmallow).
If you need help determining what version number TWRP backup to restore from the above linked collection, then do fastboot getvar all, and post the results (delete IMEI and serial number before posting).
Another option is to RUU back to stock (if your version M8 has an RUU) if you are okay with the phone being wiped. If you are s-on, you will need to relock the bootloader in order to RUU. Then after RUU, unlock the bootloader again, install TWRP and root the phone.
What does "and such" mean? Did you wipe anything besides cache and Dalvik?
Click to expand...
Click to collapse
The MTP Device Driver is not installing on my PC for some reason. It is saying installation failed on the MTP Device window on my computer.
TechMan123456 said:
The MTP Device Driver is not installing on my PC for some reason. It is saying installation failed on the MTP Device window on my computer.
Click to expand...
Click to collapse
MTP device driver?
What does it say next to "OS" in your bootloader?
Also, if you can boot to recovery you should be able to restore a backup
xunholyx said:
MTP device driver?
What does it say next to "OS" in your bootloader?
Also, if you can boot to recovery you should be able to restore a backup
Click to expand...
Click to collapse
There is no OS installed at all for some reason! When I try to download a backup I need to flash it and the only way to do so is by having the MTP Driver installed in order to drag it into TWRP and flash the backup. I can't do so because it fails to install my MTP Driver.
TechMan123456 said:
There is no OS installed at all for some reason! When I try to download a backup I need to flash it and the only way to do so is by having the MTP Driver installed in order to drag it into TWRP and flash the backup. I can't do so because it fails to install my MTP Driver.
Click to expand...
Click to collapse
you can use a card reader to put the rom or the backup on external sd card
or use an OTG USB flash memory
also connect the device to pc while you are in recovery this should work by it self no need to install MTP driver
which OS you have on your pc ??
TechMan123456 said:
There is no OS installed at all for some reason! When I try to download a backup I need to flash it and the only way to do so is by having the MTP Driver installed in order to drag it into TWRP and flash the backup. I can't do so because it fails to install my MTP Driver.
Click to expand...
Click to collapse
No OS is usually an easy fix. Download a ROM on your PC, put it onto your extSD, and flash the ROM in recovery. The reason you have no OS is because you wiped system in TWRP. If you do that, you need to flash a ROM after or you'll have no OS on a reboot.
It's best to never wipe system in TWRP as this is done by default in recovery when you flash a ROM. There will be the odd instance that it is suggested to wipe it ( I've never seen that with HTC based ROMs), but if it isn't then don't.
---------- Post added at 08:52 PM ---------- Previous post was at 08:47 PM ----------
TechMan123456 said:
There is no OS installed at all for some reason! When I try to download a backup I need to flash it and the only way to do so is by having the MTP Driver installed in order to drag it into TWRP and flash the backup. I can't do so because it fails to install my MTP Driver.
Click to expand...
Click to collapse
Ahhh, reding it a second time I realize you mean OS is blank in your bootloader. You should also update your TWRP version
TechMan123456 said:
The MTP Device Driver is not installing on my PC for some reason. It is saying installation failed on the MTP Device window on my computer.
Click to expand...
Click to collapse
Not clear which drivers you are trying to install, the HTC drivers from their website, the ones which load from the phone, built-in Windows drivers, etc.?
Try going to HTC's website, and download HTC Sync, which will also install the drivers. If you already have this installed, try uninstalling, and re-install.
Alternately, the Android MTP device drivers built-in to Windows is a generic version of drivers which can often get at least adb/fastboot working, and probably also allow you to drag/drop to internal storage in TWRP. If these drivers are the ones failing to install, it would imply there is something wrong with your Windows installation (which there isn't a lot we can help you with) rather than anything with the phone.
hey
i also have the same problem in boot-loader OS is blank
i have downloaded the nandriod backup and restored it using TWRP but after successful restore i didn't get the os back and again it goes to boot-loader and show OS blank
Arslan8997 said:
hey
i also have the same problem in boot-loader OS is blank
i have downloaded the nandriod backup and restored it using TWRP but after successful restore i didn't get the os back and again it goes to boot-loader and show OS blank
Click to expand...
Click to collapse
How did you pick a nanddroid backup to download, if you don't know the OS number?
Do fastboot getvar all, and post the results (delete IMEI and serial number before posting).
Also, what version TWRP?
redpoint73 said:
How did you pick a nanddroid backup to download, if you don't know the OS number?
Do fastboot getvar all, and post the results (delete IMEI and serial number before posting).
Also, what version TWRP?
Click to expand...
Click to collapse
I also try RUU sprint version ROM but it didn't work
TWRP v2.7.0.2
bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.09.20.1112
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: XXXXXXXXXXXX
(bootloader) imei: XXXXXXXXXXXXXXX
(bootloader) imei2: Not Support
(bootloader) meid: XXXXXXXXXXXXX
(bootloader) product: m8_whl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B70000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 8a0f02ff
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Arslan8997 said:
I also try RUU sprint version ROM but it didn't work
Click to expand...
Click to collapse
You need to be more specific:
What version number of file name of the RUU you tried? Zip format or exe format? If zip format, did you flash by fastboot, or SD card method?
Did you get an error message, if so, what did it say exactly? If no error message, what was the mode of failure (what happened exactly - be detailed - at what exact point did the RUU fail, status of the phone, etc.)? Saying "It didn't work" doesn't give us any info to troubleshoot why it failed, or how to get it to work.
Also, you did not provide all the info requested (questions I asked you in my last response):
redpoint73 said:
How did you pick a nanddroid backup to download, if you don't know the OS number?
Click to expand...
Click to collapse
redpoint73 said:
You need to be more specific:
What version number of file name of the RUU you tried? Zip format or exe format? If zip format, did you flash by fastboot, or SD card method?
Did you get an error message, if so, what did it say exactly? If no error message, what was the mode of failure (what happened exactly - be detailed - at what exact point did the RUU fail, status of the phone, etc.)? Saying "It didn't work" doesn't give us any info to troubleshoot why it failed, or how to get it to work.
Also, you did not provide all the info requested (questions I asked you in my last response):
Click to expand...
Click to collapse
RUU_M8_WHL_M60_SENSE70_SPCS_MR_Sprint_WWE_6.20.651.3.exe
this i have try to install but faild to install it give error of to pick the correct rom
when i check the ruu log there was an error of (status read failed (Too many links))
Status of phone is
bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.09.20.1112
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: XXXXXXXXXXXX
(bootloader) imei: XXXXXXXXXXXXXXX
(bootloader) imei2: Not Support
(bootloader) meid: XXXXXXXXXXXXX
(bootloader) product: m8_whl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B70000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 8a0f02ff
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Arslan8997 said:
RUU_M8_WHL_M60_SENSE70_SPCS_MR_Sprint_WWE_6.20.651.3.exe
this i have try to install but faild to install it give error of to pick the correct rom
when i check the ruu log there was an error of (status read failed (Too many links))
Click to expand...
Click to collapse
You need to flash the firmware 6.20.651.3 in order for the RUU to install (firmware and RUU are different things - so don't confuse the two). The firmware and how to flash are described here (as well as all the Sprint RUUs): https://forum.xda-developers.com/showthread.php?t=2729173
Just a heads up, if you don't know already: No need to relock the bootloader to do this (flash either firmware or RUU) since you are s-off, and no benefit in doing so. Plus, relocked bootloader gives you less options to recovery, so it is not recommended to relock it in your case.
Also, in regards to your original question (no boot after restoring TWRP backup): you never answered my question of how you picked a TWRP backup to download and restore (which I asked twice before). Now that I see you have the Sprint version M8, I will guess that you tried to restore the incorrect version backup. Sprint version uses different kernel from most other M8 versions. So if you don't restore the proper one, no boot is the expected outcome. Also, even if Sprint, it would have to be the same version you were on before (Kitkat) which is another reason it would not boot.