Develop Bugs

[Q] HTC One m8 unrooting

hi everyone.. i recently bought a used htc m8 and it is already rooted and therefore i cannot get the OTA lollipop update..
it is running android revolution HD 8.1 and clockworkmod..
I have no idea about rooting and unrooting and what the names i just mentioned above mean.. someone please help me get back to stock firmware... or help me convert my phone into google play edition lollipop...
please tell the method by which i can get rid of clockwordmod permanently and get back to stock firmware..
thanks in advance

hassaan08 said:
hi everyone.. i recently bought a used htc m8 and it is already rooted and therefore i cannot get the OTA lollipop update..
it is running android revolution HD 8.1 and clockworkmod..
I have no idea about rooting and unrooting and what the names i just mentioned above mean.. someone please help me get back to stock firmware... or help me convert my phone into google play edition lollipop...
please tell the method by which i can get rid of clockwordmod permanently and get back to stock firmware..
thanks in advance
Click to expand...
Click to collapse
Click this link. It will tell you how to convert your phone to GPE.

xunholyx said:
Click this link. It will tell you how to convert your phone to GPE.
Click to expand...
Click to collapse
sure
just help me please.. i have been trying for days now and i havent been able to fix my phone... every method i try i get stuck at one point or another....

hassaan08 said:
sure
just help me please.. i have been trying for days now and i havent been able to fix my phone... every method i try i get stuck at one point or another....
Click to expand...
Click to collapse
Okay. The instructions are in the link. Where are you getting stuck?

Telling someone that has no idea what they're doing to convert the phone isn't very good advice.
OP - do you understand anything about rooting and the commands used to root your phone?

EddyOS said:
Telling someone that has no idea what they're doing to convert the phone isn't very good advice.
OP - do you understand anything about rooting and the commands used to root your phone?
Click to expand...
Click to collapse
yes i do.. i tried a few things but got stuck in between cos i dont know this stuff in depth..
I tried to unroot by downloading the stock firmware for my phone..
the method i was following was to match my cid number etc which i got through getvar with the firmwares on xda.. that bit i did well but the method i was following said that now i had to copy and paste this firmware in my phone in the backups folder of clockwordmod.. now i couldnt find that folder.. even though the backup i made is occupying space on my phone but i cannot locate it when i try to copy paste the downloaded firmware..
can you tell me where i can find that or tell an alternate way to do this thing?

OK, can you connect your phone when in the bootloader and then use the command fastboot getvar all to get information about your phone and post it up here (making sure you hide the IMEI and serial number, of course)

EddyOS said:
OK, can you connect your phone when in the bootloader and then use the command fastboot getvar all to get information about your phone and post it up here (making sure you hide the IMEI and serial number, of course)
Click to expand...
Click to collapse
version: 0.5
version-bootloader: 3.16.0.0000
version-baseband: 1.15.2133156.UA13G
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
imei2: Not Support
meid: 00000000000000
product: m8_ul
platform: hTCBmsm8974
modelid: 0P6B10000
cidnum: HTC__002
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: ab0efa49
hbootpreupdate: 11
gencheckpt: 0
is this what you were asking for?

Indeed! OK, if you want go back to 100% stock, running on Sense as if you just got it out the box you can do the following:
First, download these files to the same location as fastboot:
4.16.401.10 RUU ZIP - https://drive.google.com/file/d/0B17smFr95pleU2NqcVB3NWxoNnM/view (rename it ruu.zip - not ruu.zip.zip!)
htc_fastboot - https://www.androidfilehost.com/?fid=95897840722646249 (doesn't need renaming)
1. Relock your bootloader - fastboot oem lock
2. Once done, reboot the bootloader to confirm it says 'RELOCKED' - fastboot reboot-bootloader
3. Once relocked, reboot the phone into RUU mode - fastboot oem rebootRUU
4. Once in RUU mode, flash the RUU ZIP using the HTC fastboot app - htc_fastboot flash zip ruu.zip
5. It will go through a few passes but once complete reboot the phone to the bootloader - fastboot reboot-bootloader
6. Once back at the bootloader, go into recovery and you should get the stock recovery not CWM. Hold volume up and press power to get the recovery menu and do a factory reset
7. Once the reset has finished, reboot the phone
You should now be working again on 100% stock Lollipop

help needed, new to rooting stuff
Hi forum members. This is my first post and and i am an infant in unlocking and rooting stuff. The reason I am researching these things is because of my HTC one m8. I got this phone used from a seller 6 months ago. I was expecting OTA updates but did not receive any till date. I am still running on 4.4.2 . So, after a bit of searching on forums, I learned about a thing called boot loader. And checked mine. To my surprise it was TAMPERED , UNLOCKED AND S-ON. Now I really don't know what that means. Some suggested to check if it's rooted, installed root checker and it said "device is not rooted" .
Can anyone pLease help me And explain me what all this means as it will be greatly appreciated.I only want to have OTA updates And need stock android. Thanks in advance

Best to start your own thread, and post up the same details as the OP in post #8, rather than confusing things in someone else's thread

EddyOS said:
Telling someone that has no idea what they're doing to convert the phone isn't very good advice.
OP - do you understand anything about rooting and the commands used to root your phone?
Click to expand...
Click to collapse
Read his OP. He asked how to convert, so I linked him. How is that bad advice?
Sorry for being off topic.

xunholyx said:
Read his OP. He asked how to convert, so I linked him. How is that bad advice?
Sorry for being off topic.
Click to expand...
Click to collapse
That was the second request, the first being to get it back to stock. I was just saying that if they're not familiar with rooting HTC devices then converting to GPe could potentially brick the device

It worked... thank you so much..
i hope liverpool get into the top 4 this season

hassaan08 said:
It worked... thank you so much..
i hope liverpool get into the top 4 this season
Click to expand...
Click to collapse
I'm an Arsenal fan but thank you anyway!

hey again
i unrooted my device and it seemed fine then but since day one the device is highly unstable.. I did the hard reset several times but have not been able to fix the problem.. suddenly all the data vanishes from the device and some features get locked ( brightness, power saver and others too). Please suggest what i should do?

Is there a way I can re-flash the stock lollipop with a different RUU file?

Nope, if you still have issues when stock you have a faulty phone

these are definitely sofware issues.. for example one in ten times when i format my device it starts working totally fine... but after a few days the same problem re-appears... the problem is that htc zoe add keeps popping up again and again.. and when it starts i cant adjust the brightness or the power saver options.. the rest of the phone works fine....
can you please suggest if i should convert my phone to GPE? or will it be too difficult a process for a rookie like me?

Sounds like a faulty phone, get it replaced

HTC M8 Android 6.0 rooting

Hi
I need to root my HTC M8 for a Project (using in a car as multimedia Device).
Unfortunately i already updated OTA to android version 6
I've tried Tools like rootking => not working!
How i can easily root my device? I'm not really an expert but i have some small basic know how..
Many thanks in advance for any hint
Kind regards
Andy

Kingroot should work, although there have been some mixed results.
Otherwise, you will need to unlock the bootloader by HTCDev.com, install TWRP 3.0, then in flash SuperSU 2.65 in TWRP to get root.

redpoint73 said:
Kingroot should work, although there have been some mixed results.
Otherwise, you will need to unlock the bootloader by HTCDev.com, install TWRP 3.0, then in flash SuperSU 2.65 in TWRP to get root.
Click to expand...
Click to collapse
Are there any good sites you can link me to? I want to root my m8 on 6.0 as well and King root didn't work for me. I have never rooted a phone before and there are so many sites out there that I don't even know where to start. Any help will be appreciated!

Ap3xGam3r said:
Are there any good sites you can link me to? I want to root my m8 on 6.0 as well and King root didn't work for me. I have never rooted a phone before and there are so many sites out there that I don't even know where to start.
Click to expand...
Click to collapse
The only website you need is XDA. It can be intimidating to navigate at first, like trying to sip out of a firehouse. But given a bit of time and patience, you'll find that XDA is a wealth of information, and a great community to boot. Other "root" websites are often poorly organized, outdated (both of which can lead to problems) and almost always just steal content (methods, downloads, etc.) from the devs here on XDA, while giving little or no credit. So you may as well get it here from the source.
Vomer's guide explains what to do: http://forum.xda-developers.com/htc-one-m8/general/vomerguides-m8-bootldr-unlock-s-off-t2800727
While a bit outdated, Sections 0 and 1 are still applicable. The only thing that I am aware of, that you should watch out for, is to use current version TWRP 3.0 from here: https://dl.twrp.me/m8/
Don't follow sections 2, etc. as they are no longer accurate (but no needed for root).

redpoint73 said:
like trying to sip out of a firehouse.
Click to expand...
Click to collapse
That made me laugh! :laugh:

redpoint73 said:
The only website you need is XDA. It can be intimidating to navigate at first, like trying to sip out of a firehouse. But given a bit of time and patience, you'll find that XDA is a wealth of information, and a great community to boot. Other "root" websites are often poorly organized, outdated (both of which can lead to problems) and almost always just steal content (methods, downloads, etc.) from the devs here on XDA, while giving little or no credit. So you may as well get it here from the source.
Vomer's guide explains what to do: http://forum.xda-developers.com/htc-one-m8/general/vomerguides-m8-bootldr-unlock-s-off-t2800727
While a bit outdated, Sections 0 and 1 are still applicable. The only thing that I am aware of, that you should watch out for, is to use current version TWRP 3.0 from here: https://dl.twrp.me/m8/
Don't follow sections 2, etc. as they are no longer accurate (but no needed for root).
Click to expand...
Click to collapse
I second this. XDA is tough to navigate at first, but once you realize what to search, which forums to be in, and READ through the pages. you will find what you need

redpoint73 said:
Kingroot should work, although there have been some mixed results.
Click to expand...
Click to collapse
Sorry to bother you again, but I just realized after I used kingroot (which failed), it changed my software status in the bootloader to "software status: modified", but the bootloader is still locked. Will this prevent me from installing future OTA updates? I'm scared I just ruined my phone...

Ap3xGam3r said:
Sorry to bother you again, but I just realized after I used kingroot (which failed), it changed my software status in the bootloader to "software status: modified", but the bootloader is still locked. Will this prevent me from installing future OTA updates? I'm scared I just ruined my phone...
Click to expand...
Click to collapse
No worries, m8 is done with OTA's, you probably will never again recieve OTA. Just go and unlock the bootloader via htcdev, flash twrp and supersu via twrp.
Follow this guide video https://www.youtube.com/watch?v=rEVSfwXsx-c
You'll wipe your internal storage w/ bootloader unlock.

Imotep95 said:
No worries, m8 is done with OTA's, you probably will never again recieve OTA. Just go and unlock the bootloader via htcdev, flash twrp and supersu via twrp.
Click to expand...
Click to collapse
Alright! Thanks for the info, much appreciated my friend One more question: How should I backup my phone before unlocking the bootloader to ensure all my app data, contacts, etc. are saved and ready to be restored after? Thanks again! I'm very new to this type of stuff as you can tell

Ap3xGam3r said:
Alright! Thanks for the info, much appreciated my friend One more question: How should I backup my phone before unlocking the bootloader to ensure all my app data, contacts, etc. are saved and ready to be restored after? Thanks again! I'm very new to this type of stuff as you can tell
Click to expand...
Click to collapse
Go with google backup. [emoji106]
Sent from my Sensation using Tapatalk

Ap3xGam3r said:
: How should I backup my phone before unlocking the bootloader to ensure all my app data, contacts, etc. are saved and ready to be restored after?
Click to expand...
Click to collapse
Lots of different methods for backing up various things, depending on one's personal preferences and needs. But just a few suggestions:
1) As previously suggested, backup contacts using Google/Gmail account (which is normally activated by default - but good to check that its activated).
2) Backup photos and other files to computer (just copy/paste to a folder on the computer).
3) Backup photos and files to cloud (Google Photos, Dropbox, etc.) - although the amount of files may exceed the "free" storage on some of these services.
4) App data (and a lot of other things) can be backed up with Helium app from the Play Store. I haven't used it personally, but others on XDA have suggested it. Helium is touted as a comprehensive backup app, that doesn't require root, and developed by the Clockworkmod team. I tend to use Titanium Backup (which requires root) for app data, as I don't keep my Android devices unrooted for long after buying them!

Imotep95 said:
Go with google backup. [emoji106]
Sent from my Sensation using Tapatalk
Click to expand...
Click to collapse
hey guys, I succesfully rooted and flashed twrp and supersu, but now my problem is that everything was working fine, and then suddenly my vibrate stopped working.....I factory reset my phone and it still isn't working? What is going on??

Ap3xGam3r said:
hey guys, I succesfully rooted and flashed twrp and supersu, but now my problem is that everything was working fine, and then suddenly my vibrate stopped working.....I factory reset my phone and it still isn't working? What is going on??
Click to expand...
Click to collapse
That is super weird.. In worst case scenario, your vibration motor died, but it has nothing to do with twrp/root..
Post your " fastboot getvar all " results without imei and serial number, so we can see what's going on and/if ruu is available.

Imotep95 said:
That is super weird.. In worst case scenario, your vibration motor died, but it has nothing to do with twrp/root..
Post your " fastboot getvar all " results without imei and serial number, so we can see what's going on and/if ruu is available.
Click to expand...
Click to collapse
version: 0.5
version-bootloader: 3.19.0.0000
version-baseband: 1.29.214500021.11G
version-cpld: None
version-microp: None
version-main: 6.13.631.7
version-misc: PVT SHIP S-ON
imei2: Not Support
meid: 00000000000000
product: m8_ul
platform: hTCBmsm8974
modelid: 0P6B16000
cidnum: ROGER001
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: 76df2b54
hbootpreupdate: 11
gencheckpt: 0

Ap3xGam3r said:
version: 0.5
version-bootloader: 3.19.0.0000
version-baseband: 1.29.214500021.11G
version-cpld: None
version-microp: None
version-main: 6.13.631.7
version-misc: PVT SHIP S-ON
imei2: Not Support
meid: 00000000000000
product: m8_ul
platform: hTCBmsm8974
modelid: 0P6B16000
cidnum: ROGER001
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: 76df2b54
hbootpreupdate: 11
gencheckpt: 0
Click to expand...
Click to collapse
Okay, you have S-ON...
First, make a nandroid backup in twrp and rename(optional) or add root just so u know it's rooted backup in internal or microsd or usb otg, then follow this thread to restore 100% stock non-rooted nandroid.
Download this nandroid: https://mega.nz/#!PRJRSBSY!BTmbWAqFZo2ncP1vmjTbPZnLZS0JvKcQKx-7BcWaFEE and follow guide here: http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
I used this method many times since i have also s-on One_M8.
Make sure that you have latest twrp 3.0.2.0.

Imotep95 said:
Okay, you have S-ON...
First, make a nandroid backup in twrp and rename(optional) or add root just so u know it's rooted backup in internal or microsd or usb otg, then follow this thread to restore 100% stock non-rooted nandroid.
Download this nandroid: https://mega.nz/#!PRJRSBSY!BTmbWAqFZo2ncP1vmjTbPZnLZS0JvKcQKx-7BcWaFEE and follow guide here: http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
I used this method many times since i have also s-on One_M8.
Make sure that you have latest twrp 3.0.2.0.
Click to expand...
Click to collapse
Do you think that flashing a custom rom may help as well?

Ap3xGam3r said:
Do you think that flashing a custom rom may help as well?
Click to expand...
Click to collapse
You may try before going to stock, yea. Just make sure you have twrp backup just in case tho. The fastest way is to flash CM13 and pico gapps or you can try sense based roms. :good:

Imotep95 said:
You may try before going to stock, yea. Just make sure you have twrp backup just in case tho. The fastest way is to flash CM13 and pico gapps or you can try sense based roms. :good:
Click to expand...
Click to collapse
Ok, thanks for the info. I guess if worst comes to worst I'll have to go get my phone repaired D: It seems like this is a common htc on m8 problem even without root.

Ap3xGam3r said:
Ok, thanks for the info. I guess if worst comes to worst I'll have to go get my phone repaired D: It seems like this is a common htc on m8 problem even without root.
Click to expand...
Click to collapse
I've seen few people with that issue, let me know how it goes w/ custom stuff. [emoji106]
Sent from my HTC One M8 using Tapatalk

Imotep95 said:
I've seen few people with that issue, let me know how it goes w/ custom stuff. [emoji106]
Sent from my HTC One M8 using Tapatalk
Click to expand...
Click to collapse
Ok so I am about to try to flash cm13 and pico gapps but I some questions: I read that you should wipe your system before flashing any rom; does this wipe my sd card too? and if I wanted to do a restore using the TWRP backup that I created, would I have to wipe before doing so as well? And last question: how do I know which pico gapps to install? Thanks and sorry if I am beginning to be annoying

HTC 10 non-standard behavior

Hello experts,
I'm in urgent need of some inspiration as I'm experiencing some very funky behavior of my HTC 10. I'm trying to get my phone back to stock and all my attempts at RUU flashing are failing. The phone has gotten up to a point, where I can't even flash TWRP anymore. Any help would be greatly appreciated.
Here's the story:
- some basic info about my device:
Code:
< waiting for device >
(bootloader) kernel: lk
(bootloader) product: htc_pmeuhl
(bootloader) version: 1.0
(bootloader) max-download-size: 1579200000
(bootloader) serialno: xxx
(bootloader) current-slot:
(bootloader) imei: xxx
(bootloader) version-main: 2.41.401.4
(bootloader) boot-mode: download
(bootloader) version-baseband: [email protected]
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 2PS620000
(bootloader) cid: HTC__034
all:
finished. total time: 0.064s
- due to some issues that we might get into later, I tried flashing the latest EXE RUU I found, which is RUU_PERFUM[email protected]61226_79.07_F_release_495903_signed_2.exe
- this one didn't go so well, since just before completing the flash, the RUU installer threw an error 155 at me and the phone was bricked. TWRP had been overwritten by stock recovery. At the time of doing this, the phone was S-On and Relocked. Thankfully the phone still was able to boot to download mode and was responding to fastboot commands.
- I unlocked the bootloader using Unlock_code.bin from HTCDev and proceeded to flash twrp, first 3.0.2-6 and then 3.0.2-5., both appearing to successfully flash
Code:
target reported max download size of 1579200000 bytes
sending 'recovery' (20852 KB)...
OKAY [ 1.711s]
writing 'recovery'...
(bootloader) HOSD CL#857212
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 1.810s]
finished. total time: 3.528s
- however, booting to recovery gave me a screen with HTC logo, saying "This build is for development purposes only " bla bla, for details see the pic below
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
- Thanks to djluisbento in this thread, I found a zip RUU called 2PS6IMG_PERFUM[email protected]61229_89.09_F_release_693552_signed and was able to flash it in download mode.
- the process didn't go 100% smoothly, as during the flash it threw a "[email protected]" message at me and finished with an overall message
Code:
33 RU_UPDATE_FIRMWARE_FAIL
33 RU_UPDATE_FIRMWARE_FAIL
FAIL33 RU_UPDATE_FIRMWARE_FAIL
as shown in the pic below
- Now, unlike with Flashing the EXE RUU, now the phone is able to boot into Android, which is running Nougat, however 3 major problems remain:
1. Can't flash TWRP as the HTC recovery stays there even after successfully flashing TWRP
2. Software status in bootloader stayed Modified, where I was looking to get back to Original
3. Double-tap to wake and camera shortcut are not working in android, which are symptoms of a problem I was trying to solve in the first place, where the touchscreen is not responding at all in Recovery mode. I had to use OTG mouse and keyboard to control TWRP when it was able to flash.
The 2 options I was considering at are:
1. Paying 25 USD for flashing a signed HTC RUU from this guy: http://llabtoofer.com/htc-ruu-flashing-service/, however I might end up with the same errors as when I was trying to flash my files, so not good.
or
2. Get Sunshine S-OFF and try flashing some of the older ZIP RUUs I found in my process, 1.30.401.1 or 1.90.401.1. If that doesn't work then I can at least hack the phone to get it back to Software status original and sending it back for Service. However, without TWRP and root, this is currently not possible.
Any advice to solve the 3 above mentioned pain points would be appreciated, as I've reached my limits.
Thanks.

madzur said:
Hello experts,
I'm in urgent need of some inspiration as I'm experiencing some very funky behavior of my HTC 10. I'm trying to get my phone back to stock and all my attempts at RUU flashing are failing. The phone has gotten up to a point, where I can't even flash TWRP anymore. Any help would be greatly appreciated.
Here's the story:
- some basic info about my device:
- due to some issues that we might get into later, I tried flashing the latest EXE RUU I found, which is RUU_PERFUM[email protected]61226_79.07_F_release_495903_signed_2.exe
- this one didn't go so well, since just before completing the flash, the RUU installer threw an error 155 at me and the phone was bricked. TWRP had been overwritten by stock recovery. At the time of doing this, the phone was S-On and Relocked. Thankfully the phone still was able to boot to download mode and was responding to fastboot commands.
- I unlocked the bootloader using Unlock_code.bin from HTCDev and proceeded to flash twrp, first 3.0.2-6 and then 3.0.2-5., both appearing to successfully flash
- however, booting to recovery gave me a screen with HTC logo, saying "This build is for development purposes only " bla bla, for details see the pic below
- Thanks to djluisbento in this thread, I found a zip RUU called 2PS6IMG_PERFUM[email protected]61229_89.09_F_release_693552_signed and was able to flash it in download mode.
- the process didn't go 100% smoothly, as during the flash it threw a "[email protected]" message at me and finished with an overall message as shown in the pic below
- Now, unlike with Flashing the EXE RUU, now the phone is able to boot into Android, which is running Nougat, however 3 major problems remain:
1. Can't flash TWRP as the HTC recovery stays there even after successfully flashing TWRP
2. Software status in bootloader stayed Modified, where I was looking to get back to Original
3. Double-tap to wake and camera shortcut are not working in android, which are symptoms of a problem I was trying to solve in the first place, where the touchscreen is not responding at all in Recovery mode. I had to use OTG mouse and keyboard to control TWRP when it was able to flash.
The 2 options I was considering at are:
1. Paying 25 USD for flashing a signed HTC RUU from this guy: http://llabtoofer.com/htc-ruu-flashing-service/, however I might end up with the same errors as when I was trying to flash my files, so not good.
or
2. Get Sunshine S-OFF and try flashing some of the older ZIP RUUs I found in my process, 1.30.401.1 or 1.90.401.1. If that doesn't work then I can at least hack the phone to get it back to Software status original and sending it back for Service. However, without TWRP and root, this is currently not possible.
Any advice to solve the 3 above mentioned pain points would be appreciated, as I've reached my limits.
Thanks.
Click to expand...
Click to collapse
You're flashing the wrong TWRP. Please go read the TWRP thread and download the appropriate version.

Captain_Throwback said:
You're flashing the wrong TWRP. Please go read the TWRP thread and download the appropriate version.
Click to expand...
Click to collapse
Hey Captain, thanks for the tip, managed to flash the unofficial twrp, which works with Nougat, however my painpoints 2 and 3 are still valid. Any ideas, especially on the recovery mode being unresponsive to touch?

madzur said:
Hey Captain, thanks for the tip, managed to flash the unofficial twrp, which works with Nougat, however my painpoints 2 and 3 are still valid. Any ideas, especially on the recovery mode being unresponsive to touch?
Click to expand...
Click to collapse
You sure you don't have a hardware problem? That's what it sounds like.

Captain_Throwback said:
You sure you don't have a hardware problem? That's what it sounds like.
Click to expand...
Click to collapse
Not sure about the HW problem. As I mentioned, I had a cracked screen, did a nandroid backup, brought the phone to service, when it came back, TWRP couldn't register any touches.
Booting to Android touch is working just 100% (except for double-tap to wake), in recovery, no touch is registered. When I bring the phone back to service, they tell me it's not their fault, as they tested the display with another phone and all was well, plus my software status says Modified, so they are saying it's a sw problem and warranty is void.
Hence my struggle to get the phone back to stock and prove to them even with Stock SW, there is a problem... Don't know what else to do.

madzur said:
Not sure about the HW problem. As I mentioned, I had a cracked screen, did a nandroid backup, brought the phone to service, when it came back, TWRP couldn't register any touches.
Booting to Android touch is working just 100% (except for double-tap to wake), in recovery, no touch is registered. When I bring the phone back to service, they tell me it's not their fault, as they tested the display with another phone and all was well, plus my software status says Modified, so they are saying it's a sw problem and warranty is void.
Hence my struggle to get the phone back to stock and prove to them even with Stock SW, there is a problem... Don't know what else to do.
Click to expand...
Click to collapse
Well, the options you listed aren't really necessary. If those RUUs that you flashed weren't signed, they wouldn't have even started to install on a locked, S-ON device. So I don't see how trying to flash another signed RUU will make a difference.
It is possible to downgrade your device without S-OFF. I believe the method is detailed somewhere in the 'install an OTA with system corrupt message' thread. You'll have to search though it to find it. But again, if you have an emmc or hardware problem of some sort, I don't see how any RUU will install, if the latest signed ones have failed.

Captain_Throwback said:
Well, the options you listed aren't really necessary. If those RUUs that you flashed weren't signed, they wouldn't have even started to install on a locked, S-ON device. So I don't see how trying to flash another signed RUU will make a difference.
It is possible to downgrade your device without S-OFF. I believe the method is detailed somewhere in the 'install an OTA with system corrupt message' thread. You'll have to search though it to find it. But again, if you have an emmc or hardware problem of some sort, I don't see how any RUU will install, if the latest signed ones have failed.
Click to expand...
Click to collapse
Thanks, I'll have a look through that thread and see what I can come up with.
In the meantime, is there any line of argumentation I could use when speaking to the service, against their story about SW being "Modified". They are saying "Modified" means the phone had been rooted and they are not responsible if something is not working. I haven't been able to find explanation of when these statuses change from Original, to Modified or Tampered. Could you please point me in the right direction? Thanks

madzur said:
Thanks, I'll have a look through that thread and see what I can come up with.
In the meantime, is there any line of argumentation I could use when speaking to the service, against their story about SW being "Modified". They are saying "Modified" means the phone had been rooted and they are not responsible if something is not working. I haven't been able to find explanation of when these statuses change from Original, to Modified or Tampered. Could you please point me in the right direction? Thanks
Click to expand...
Click to collapse
Nope, that only happens well, when you've modified the software by installing an unsigned image like a custom recovery or kernel or made modifications to system. So getting an RUU to flash is really the only way to restore it back to official status.

Managed to get the phone fixed by original HTC service. They supposedly installed factory sw on it, however bootloader still says Software status: modified. I installed the HTC RUU myself, bootloader still says Modified. Any ideas why?

Same thing
madzur said:
Managed to get the phone fixed by original HTC service. They supposedly installed factory sw on it, however bootloader still says Software status: modified. I installed the HTC RUU myself, bootloader still says Modified. Any ideas why?
Click to expand...
Click to collapse
I'm having the exact problem you listed in your OP. I just had the screen and battery replaced. I'm trying to go from Viper 5.11 to LeeDroid and oreo. Can't get any RUUs to work. [email protected] when trying to just reflash 2.51.617.32 firmware. FAIL33 RU_UPDATE_FIRMWARE_FAIL. I'm S-Off. US Unlocked phone.
I'm well past warranty with HTC at this point too.
Any suggestions?

djgreyghost said:
I'm having the exact problem you listed in your OP. I just had the screen and battery replaced. I'm trying to go from Viper 5.11 to LeeDroid and oreo. Can't get any RUUs to work. [email protected] when trying to just reflash 2.51.617.32 firmware. FAIL33 RU_UPDATE_FIRMWARE_FAIL. I'm S-Off. US Unlocked phone.
I'm well past warranty with HTC at this point too.
Any suggestions?
Click to expand...
Click to collapse
Found a solution!
https://forum.xda-developers.com/htc-10/how-to/8-0-htc-10-oreo-firmware-t3756126
The first firmware file listed under the section:
US Unlocked:
modelid: 2PS650000
cidnum: BS_US001
cidnum: BS_US002
This one worked! ---> 2.51.617.32--3.16.617.2_S-On_firmware.zip - Can be used on S-On devices to incrementally update firmware from 2.51.617.32 and will replace Twrp with stock recovery
It didn't try to do anything with tp_SYN3708.img and so it passed without errors. I first tried the third file and it failed with the same error. I am a little concerned that the file that worked didn't update as many things as the file that failed. But the phone now lists 3.16.617.2 as the OS version and the 4 March version of Leedroid is up and running and everything seems to be working, so I'm just gonna go with it!
I hope this helps someone else.

djgreyghost said:
Found a solution!
https://forum.xda-developers.com/htc-10/how-to/8-0-htc-10-oreo-firmware-t3756126
The first firmware file listed under the section:
US Unlocked:
modelid: 2PS650000
cidnum: BS_US001
cidnum: BS_US002
This one worked! ---> 2.51.617.32--3.16.617.2_S-On_firmware.zip - Can be used on S-On devices to incrementally update firmware from 2.51.617.32 and will replace Twrp with stock recovery
It didn't try to do anything with tp_SYN3708.img and so it passed without errors. I first tried the third file and it failed with the same error. I am a little concerned that the file that worked didn't update as many things as the file that failed. But the phone now lists 3.16.617.2 as the OS version and the 4 March version of Leedroid is up and running and everything seems to be working, so I'm just gonna go with it!
I hope this helps someone else.
Click to expand...
Click to collapse
Pretty sure you saved my phone from extinction :good: I'm not sure I would of tried the S-On version.

djgreyghost said:
I'm having the exact problem you listed in your OP. I just had the screen and battery replaced. I'm trying to go from Viper 5.11 to LeeDroid and oreo. Can't get any RUUs to work. [email protected] when trying to just reflash 2.51.617.32 firmware. FAIL33 RU_UPDATE_FIRMWARE_FAIL. I'm S-Off. US Unlocked phone.
I'm well past warranty with HTC at this point too.
Any suggestions?
Click to expand...
Click to collapse
I'm having a similar issue with tp_SYN3708.img failing being stuck at 50% until ti gives up and gives me an error. The phone works fine but I just don't like the idea that this file isn't being flashed. I was coming from 3.16.709.3 Asia and switched over to 3.16.617.2 US. If anyone has any ideas on how to fix this I'll be happy to hear them.

Dukenukemx said:
I'm having a similar issue with tp_SYN3708.img failing being stuck at 50% until ti gives up and gives me an error. The phone works fine but I just don't like the idea that this file isn't being flashed. I was coming from 3.16.709.3 Asia and switched over to 3.16.617.2 US. If anyone has any ideas on how to fix this I'll be happy to hear them.
Click to expand...
Click to collapse
The fix for me was to buy a new HTC 10.
I found a seller on ebay who was selling new in box phones for UK and then used xda instructions to convert the phone to a US phone.

djgreyghost said:
The fix for me was to buy a new HTC 10.
I found a seller on ebay who was selling new in box phones for UK and then used xda instructions to convert the phone to a US phone.
Click to expand...
Click to collapse
Guess I'll be installing LineageOS then. The phone works fine like this, but it bothers me that I can't flash it completely.

Ok the problem with [email protected] is that you installed an aftermarket screen and that causes the failure. The solution is to remove the tp_SYN3708.img file from the rom and then flash it, but I'm still working on how to do that. The tp_SYN3708.img file is specifically for flashing the screen and the screen I have is Chinese replica, so of course it doesn't work. So my options are to remove the file and flash that way or to get another LCD screen. I'd rather find a software solution as looking for an original HTC 10 screen is probably harder than it sounds.

Installing the original OS with SD card or autoload

Dear friendly xda-developer people,
my HTC One M8 went out because of an empty battery. When I restarted, it only boots the bootloader. The security mode isn't working as well. I tried all I could think of and now I just want to install the original OS on the phone in hope that it will work again.
When I boot up the phone it says it is "OS-6.12.161.4". I am from Germany and I guess it is a vodafone branded HTC. So I do not find the right software on the official US website. I tried to google a different version and all I could find was a software to which the phone anwsers when I try to install the .zip via SD-card "Image Update Fail! Device halted due to Large Image update fail!"
I will post the complete screen of the boot below.
Any ideas what I could do? I tried to update it via PC, that didn't work as well. I think I need the right software and the one I found might just be the wrong one. I also tried to unlock it, but relocked it because I read, that I can not install the original software if it is unlocked.
If I can not install the original os: Is it possible to install something else that just works like the original OS? I can not use Google Products than?
I am really thankful for any advice.
Greetings
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

What is the background of this device? Did it have a stock "official" HTC ROM on there when you had the "no OS" issue? Was it ever bootloader unlocked before you unlocked it to try to solve this problem?
Best for us to see more details about the phone. Do fastboot getvar all, and post the results (delete IMEI and serial number before posting).
ghostmag said:
I tried to google a different version and all I could find was a software to which the phone anwsers when I try to install the .zip via SD-card "Image Update Fail! Device halted due to Large Image update fail!"
I tried to update it via PC, that didn't work as well. I think I need the right software and the one I found might just be the wrong one.
Click to expand...
Click to collapse
You absolutely need to use an RUU (ROM Update Utility) that is intended for your M8 version's (Vodaphone) carrier ID (CID) as well as the version number 6.12.161.4. Another version number means it is made for a different CID, and will fail by definition. HTC phones are quite strict about version number checking.
In your case, I don't think that there exists an RUU for the Vodaphone version. But you can install the stock OS by other means (see below).
ghostmag said:
If I can not install the original os: Is it possible to install something else that just works like the original OS?
Click to expand...
Click to collapse
While your Vodaphone version M8 doesn't have an RUU, there is another way to get back to the stock ROM. You can unlock the bootloader again, than install TWRP and a stock TWRP backup from the collection.
https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Only need to do through Step 9, then reboot and it should boot to the OS. The remaining steps were only for getting official OTA updates (which is no longer relevant).
ghostmag said:
I can not use Google Products than?
Click to expand...
Click to collapse
I think you mean a ROM straight from Google? Google doesn't make complete ROMs for any device, except for Pixel devices (and the old Nexus devices). For any other device manufacturer, at least some part of the ROM needs to be customized for the specific hardware configuration. But you do have some options, if you want a ROM that is more lightweight then the HTC Sense interface:
Even though we don't have a "pure" Google ROM; what we do have for the M8, is something called the Google Play Edition (GPe). Which even though made by HTC, is designed to feel like a "pure Google" ROM. Once you have the bootloader unlocked and TWRP installed, you can install this the same way as a custom ROM. Follow the part of the thread labelled "Flashable GPe ROM". You can't flash as an RUU, since you are s-on.
https://forum.xda-developers.com/showthread.php?t=2708589
Another option is Lineage custom ROM. Lineage custom ROM is somewhat similar to a Google OS. Although at this point, it does have enough modifications, that I can't really consider it a "pure Google" experience. But it is much more lightweight than a Sense ROM. Very similar to installing the GPe ROM, once you have the bootloader unlocked, install TWRP and flash the ROM.

redpoint73 said:
What is the background of this device? Did it have a stock "official" HTC ROM on there when you had the "no OS" issue? Was it ever bootloader unlocked before you unlocked it to try to solve this problem?
Best for us to see more details about the phone. Do fastboot getvar all, and post the results (delete IMEI and serial number before posting).
You absolutely need to use an RUU (ROM Update Utility) that is intended for your M8 version's (Vodaphone) carrier ID (CID) as well as the version number 6.12.161.4. Another version number means it is made for a different CID, and will fail by definition. HTC phones are quite strict about version number checking.
In your case, I don't think that there exists an RUU for the Vodaphone version. But you can install the stock OS by other means (see below).
While your Vodaphone version M8 doesn't have an RUU, there is another way to get back to the stock ROM. You can unlock the bootloader again, than install TWRP and a stock TWRP backup from the collection.
https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Only need to do through Step 9, then reboot and it should boot to the OS. The remaining steps were only for getting official OTA updates (which is no longer relevant).
I think you mean a ROM straight from Google? Google doesn't make complete ROMs for any device, except for Pixel devices (and the old Nexus devices). For any other device manufacturer, at least some part of the ROM needs to be customized for the specific hardware configuration. But you do have some options, if you want a ROM that is more lightweight then the HTC Sense interface:
Even though we don't have a "pure" Google ROM; what we do have for the M8, is something called the Google Play Edition (GPe). Which even though made by HTC, is designed to feel like a "pure Google" ROM. Once you have the bootloader unlocked and TWRP installed, you can install this the same way as a custom ROM. Follow the part of the thread labelled "Flashable GPe ROM". You can't flash as an RUU, since you are s-on.
https://forum.xda-developers.com/showthread.php?t=2708589
Another option is Lineage custom ROM. Lineage custom ROM is somewhat similar to a Google OS. Although at this point, it does have enough modifications, that I can't really consider it a "pure Google" experience. But it is much more lightweight than a Sense ROM. Very similar to installing the GPe ROM, once you have the bootloader unlocked, install TWRP and flash the ROM.
Click to expand...
Click to collapse
First of all: Thank you very very much for your time and effort answering me. I highly appreciate that.
I will try to deliver fastboot getvar-data as soon as I am able to get back to a Windows or Ubuntu PC.
I now was able to install a TWRP backup. Your link is very helpful.
Sadly, my sound isn't working anymore now. I guess every 20 reboots or so it does work, but I can not replicate that.
Also I can not make videos and can not record audio. I then tried to install Cynagenmod which had the same problem and then I tried Lineage OS which had the same problem as well.
Do you have an idea what I can do to fix that? I read about upgrading radio, but that sounds like an easy-to-brick-my-phone way.
In case that helps: Background of the phone is just stock "official" HTC ROM as far as I know.
Since I was able to install other OS, the part of the screenshot above where you can read "OS-6.12.161.4" is just "OS" and nothing else anymore.
Regarding the topic that I wanted the original firmware: I thought Gapps are only available on official firmware. Since I know that a custom OS can run them as well, I do not care about the OS. I thought LineageOS and Cynagenmod were both lovely and would try out everything that does the job.
Any idea how it is possible that the sound / recording videos and sound don't work with three different OS?
Greetings

My responses below in red font:
ghostmag said:
Sadly, my sound isn't working anymore now. I guess every 20 reboots or so it does work, but I can not replicate that.
Also I can not make videos and can not record audio. I then tried to install Cynagenmod which had the same problem and then I tried Lineage OS which had the same problem as well.
Might be a firmware issue. When I say "firmware", I am referring to a specific package (usually a file named firmware.zip) that contains certain partitions necessary for the ROM to work (radio, hboot, recovery, and others), but does actually not contain the ROM itself. On that note, it is probably best for you to stop thinking of the term "firmware" as interchangeable with the ROM. If you mean ROM, just say ROM. No need to call it something else, and doing so will just cause confusion. It is best to use specific terms (stock ROM, RUU, stock TWRP backup, etc.).
Random sound or video issues can sometimes be a result of old/damaged firmware. It is probably useful to flash the firmware (more on this below).
Do you have an idea what I can do to fix that? I read about upgrading radio, but that sounds like an easy-to-brick-my-phone way.
You can't flash a radio (alone) with s-on. And not worth getting s-off ($25 US by sunshine app) just to flash a radio. What you can do, is flash the whole firmware zip, and see if that helps. But I'd like to get the full getvar output, to make sure which firmware is the correct one for your version M8. As you mentioned, flashing the wrong radio can be catastrophic.
In case that helps: Background of the phone is just stock "official" HTC ROM as far as I know.
Since I was able to install other OS, the part of the screenshot above where you can read "OS-6.12.161.4" is just "OS" and nothing else anymore.
What version TWRP did you install? If you followed the guide closely, you should have used TWRP 2.8.7 or later. No number being shown for OS version is sometimes a result of flashing Lineage (known bug), or an old version of TWRP.
Click to expand...
Click to collapse

redpoint73 said:
My responses below in red font:
Click to expand...
Click to collapse
I got the getvar all reaction now:
(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) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: VODAP102
(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
Click to expand...
Click to collapse
The first time I tried working with TWRP I installed an older version - sadly don't remember which one. I installed a version of Cynagenmod with it. Then I accidentally crashed TWRP somehow so I had to install it again so I am using 3.3.0-0 right now because I thought it's best to install the newest version I could find.
Should I try again installing a different version of TWRP?
Sidenote: I now have the problem that WLAN doesn't work a lot of times. I need to reboot around 5 times so WLAN works. I guess that is another issue because of the mistakes I made while installing different OS.
Thanks again for your time.

ghostmag said:
The first time I tried working with TWRP I installed an older version - sadly don't remember which one. I installed a version of Cynagenmod with it. Then I accidentally crashed TWRP somehow so I had to install it again so I am using 3.3.0-0 right now because I thought it's best to install the newest version I could find.
Should I try again installing a different version of TWRP?
Click to expand...
Click to collapse
TWRP 3.3.0-0 should be okay. I agree, using the latest version is typically the best thing to do.
What I would try, is the following. Note that you will lose all data on the phone when you do this, so plan accordingly, if there is any data on the phone you want to keep (backup to cloud, computer, etc.):
1) Flash the firmware fw_6.12.161.4 from here (instruction on how to flash firmware, near the bottom of the post): https://forum.xda-developers.com/showpost.php?p=60218734&postcount=5
2) After flashing firmware, you will need to unlock the bootloader again. Either use the same unlock bin code you used before (flash with fastboot command). Or go through the process on HTVDev.com, to get a new code.
3) Flash TWRP back to the device (flashing stock firmware wipes TWRP, so you need to put it on there again).
4) Restore stock TWRP backup 6.12.161.4, using TWRP. https://forum.xda-developers.com/showpost.php?p=60211240&postcount=3
Not sure if this will solve your problems, but I'm hoping it will. This process will put a stock ROM and corresponding firmware on the device (a clean slate, as it were).

redpoint73 said:
TWRP 3.3.0-0 should be okay. I agree, using the latest version is typically the best thing to do.
What I would try, is the following. Note that you will lose all data on the phone when you do this, so plan accordingly, if there is any data on the phone you want to keep (backup to cloud, computer, etc.):
1) Flash the firmware fw_6.12.161.4 from here (instruction on how to flash firmware, near the bottom of the post): https://forum.xda-developers.com/showpost.php?p=60218734&postcount=5
2) After flashing firmware, you will need to unlock the bootloader again. Either use the same unlock bin code you used before (flash with fastboot command). Or go through the process on HTVDev.com, to get a new code.
3) Flash TWRP back to the device (flashing stock firmware wipes TWRP, so you need to put it on there again).
4) Restore stock TWRP backup 6.12.161.4, using TWRP. https://forum.xda-developers.com/showpost.php?p=60211240&postcount=3
Not sure if this will solve your problems, but I'm hoping it will. This process will put a stock ROM and corresponding firmware on the device (a clean slate, as it were).
Click to expand...
Click to collapse
Dear friend,
I followed your guide and right now I am at step 3)
While looking for the newstest TWRP.img-file the phone is booting Android and is installing Apps right now. I even heard at startup sound. Is it possible, that I won't need the following steps and it just got the stock firmware from my last install?

ghostmag said:
I followed your guide and right now I am at step 3)
While looking for the newstest TWRP.img-file the phone is booting Android and is installing Apps right now. I even heard at startup sound. Is it possible, that I won't need the following steps and it just got the stock firmware from my last install?
Click to expand...
Click to collapse
Yes, it is possible you don't need to do anything further.
As I warned before, be careful about using the term "firmware". It seems you are using it synonymously with "ROM" again. If you accomplished Step 1 (as designated in my last response) you flashed the stock firmware. The stock ROM should still be there from the TWRP backup you restored previously. Nothing you have done so far, would have overwritten the stock ROM that you restored, so it is still there.
You previously restored the proper number 6.12.161.4 stock TWRP backup?

redpoint73 said:
Yes, it is possible you don't need to do anything further.
As I warned before, be careful about using the term "firmware". It seems you are using it synonymously with "ROM" again. If you accomplished Step 1 (as designated in my last response) you flashed the stock firmware. The stock ROM should still be there from the TWRP backup you restored previously. Nothing you have done so far, would have overwritten the stock ROM that you restored, so it is still there.
You previously restored the proper number 6.12.161.4 stock TWRP backup?
Click to expand...
Click to collapse
Yes, I did and it all works fine now. Even the battery is much better than before.
Thank you very very much for your time and help. If you ever come to Germany, let me know and I will buy you a drink or something
Kind regards and have a good life
ghostmag

HTC One M8 stuck at HTC logo screen

Hi,
First of all, this was supposed to be my first flash. So I am very new and confused. (I get that you probably have loads of those... I am sorry)
I got a HTC One M8 that was already rooted and S-OFF, had SuperCID and everything. And I hate the 4.4.4 Android, plus no OTA updates are available to me (when I tried to check, it gets stuck). So I wanted to flash in a LineageOS 16.0. I unlocked the bootloader, got TWRP 2.8.7.0, pasted the Lineage 16.0 ZIP file, and wanted to flash it. But, I got an error "Error executing updater binary in zip [zip filename]", and so I went to check the instructions to install.
https://forum.xda-developers.com/htc-one-m8/development/rom-lineageos-16-0-htc-one-m8-t3837538
Here it says this:
- Reboot to recovery (TWRP by @Captain_Throwback) - Direct link
- Wipe /system, /data and /cache
- Install LineageOS zip package
and I did that to see if it changes anything, Nope, it didn't. I tried to reboot the phone to get it fixed (someone in another thread suggested getting an md5 file for it).
And after the reboot I am stuck on HTC logo screen, can't shut it down at all. I can't use ADB because it doesn't see the device, so I can't getvar all. I do remember that my version-bootloader was 3.19.0.0000, but that's all.
I am not asking for a full guide on what to do, because it's probably impossible, but can anyone at least tell me how to proceed next? I'd love to turn off the phone and at least try to do something with TWRP. (I didn't have a backup, yes I am an idiot)
EDIT: Holding volume up and power button to do the reset just turns off the screen for a few secs then goes to HTC logo screen again.

Okay, I waited for it to discharge so I can get to the bootloader. I will post getvar when it charges.
EDIT: here we go
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.08.20.0916
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.30.651.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) imei2: Not Support
(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
I basically just want anything to work now, even stock will be okay (but 6.0 at least)

1st edit your last post & remove your IMEI/MEID unless you want it stolen...
when you wiped /system in TWRP & your zip didn't flash, u lost your ROM
easiest way to get the phone back up & working is to flash the RUU, looks like you currently have 3.30.651.2 (very old)
here is the 3.30.651.2 exe version: https://androidfilehost.com/?fid=95784891001604379
or to update to the latest version 6.20.651.3:
http://dl3.htc.com/application/RUU_M8_WHL_M60_SENSE70_SPCS_MR_Sprint_WWE_6.20.651.3.exe

OMJ said:
1st edit your last post & remove your IMEI/MEID unless you want it stolen...
Click to expand...
Click to collapse
Yeah, I forgot, thanks for reminding.
So do I just run the .exe with my phone plugged in my PC while in bootloader? Or do you mean TWRP/adb flashing?

gr0za said:
Yeah, I forgot, thanks for reminding.
So do I just run the .exe with my phone plugged in my PC while in bootloader? Or do you mean TWRP/adb flashing?
Click to expand...
Click to collapse
yes, run exe from pc while connected to phone

OMJ said:
yes, run exe from pc while connected to phone
Click to expand...
Click to collapse
3.30.651.2 worked, 6.20.651.3 did not ( I tried it first). To be honest I'm so damn glad it works, because I ain't a Sprint user, but somehow Orange works. Got all the bloaty Google Aps that I don't give an f about, but at least it's working. Hopefully I can go to 6.20 next, I'm gonna try. BTW, will flashing GApps remove all the unnecessary Sprint apps? Or do I have to do something different with it? (I don't need neither the GApps not the Sprint apps, but this phone seems to be a Sprint one and I guess I have to deal with it)
EDIT: yeah, 6.20 doesn't work, it gives me Error 155 - Error updating ROM. I remember hitting up HTC live support once in desperation, and the guy told me I have to upgrade to Lollipop first. But where do I even find a RUU for that?

gr0za said:
3.30.651.2 worked, 6.20.651.3 did not ( I tried it first). To be honest I'm so damn glad it works, because I ain't a Sprint user, but somehow Orange works. Got all the bloaty Google Aps that I don't give an f about, but at least it's working. Hopefully I can go to 6.20 next, I'm gonna try. BTW, will flashing GApps remove all the unnecessary Sprint apps? Or do I have to do something different with it? (I don't need neither the GApps not the Sprint apps, but this phone seems to be a Sprint one and I guess I have to deal with it)
EDIT: yeah, 6.20 doesn't work, it gives me Error 155 - Error updating ROM. I remember hitting up HTC live support once in desperation, and the guy told me I have to upgrade to Lollipop first. But where do I even find a RUU for that?
Click to expand...
Click to collapse
yeah I vaguely recall the RUU checks your current version & must be a certain level, so you'll probably need to flash a 4.x.651.x RUU 1st
GApps probably only adds Google apps, I doubt it removes anything. once you get up to 6.20, you can root the phone (I recommend Magisk) then use a file explorer like Root Explorer to mount /system & then delete the bloat u dont want. You can also do this in twrp.
the other option is to flash a custom ROM that removes the bloat....my ROM removes bloat but retains pertinent Sprint apps

OMJ said:
yeah I vaguely recall the RUU checks your current version & must be a certain level, so you'll probably need to flash a 4.x.651.x RUU 1st
GApps probably only adds Google apps, I doubt it removes anything. once you get up to 6.20, you can root the phone (I recommend Magisk) then use a file explorer like Root Explorer to mount /system & then delete the bloat u dont want. You can also do this in twrp.
the other option is to flash a custom ROM that removes the bloat....my ROM removes bloat but retains pertinent Sprint apps
Click to expand...
Click to collapse
Alright, once I flashed the Sprint RUU, all of a sudden I have OTA updates. I'm getting to 6.20 now, so everything's fine.
Yeah, I will consider removing them the way you said. Also, I don't really need any Sprint apps, as I am not a Sprint client anyway, but I reckon some are better left unchecked. Much, much appreciated for the help and the links.

gr0za said:
(bootloader) version-main: 3.30.651.2
Click to expand...
Click to collapse
This was the main problem with flashing Lineage, your firmware (hboot, radio, etc.) was much too old. The current ROMs are not compatible with the old firmware. Now that you're updated to Marshmallow, I'll bet Lineage will install correctly (of course, you need to install TWRP again, etc.).
---------- Post added at 01:01 PM ---------- Previous post was at 12:59 PM ----------
gr0za said:
Holding volume up and power button to do the reset just turns off the screen for a few secs then goes to HTC logo screen again.
Click to expand...
Click to collapse
Hold vol up and power button to force a reboot. The moment the screen goes dark, signaling it is about to reboot, slide your finger from vol up, to vol down, and don't let go. This should get you into bootloader.
As long as the screen comes on, you can get into bootloader. Exception is, if your vol rocker is broken!
---------- Post added at 01:04 PM ---------- Previous post was at 01:01 PM ----------
OMJ said:
yeah I vaguely recall the RUU checks your current version & must be a certain level, so you'll probably need to flash a 4.x.651.x RUU 1st
Click to expand...
Click to collapse
Version check is okay if the RUU is same or greater version number (and skipping versions is usually okay). You can't go backwards (downgrade), is all.
There was a peculiar requirement on Marshmallow RUUs for US carrier versions of the M8. It is required to flash the appropriate Marshmallow firmware by fastboot, before the RUU would work, if coming from Lollipop or lower.

redpoint73 said:
This was the main problem with flashing Lineage, your firmware (hboot, radio, etc.) was much too old. The current ROMs are not compatible with the old firmware. Now that you're updated to Marshmallow, I'll bet Lineage will install correctly (of course, you need to install TWRP again, etc.)
Click to expand...
Click to collapse
Are you sure of this? I have a Sprint variant. And I found conflicting info whether Lineage works on Sprint or doesn't work.

gr0za said:
Are you sure of this? I have a Sprint variant. And I found conflicting info whether Lineage works on Sprint or doesn't work.
Click to expand...
Click to collapse
Not 100%, as I don't personally own the Sprint version M8. But what I can say:
1) The Lineage 16 thread says: "Builds are compatible with all M8 single SIM variants (m8ul, m8vzw and m8spr)."
Now the identifier "m8spr" isn't a correct one I've ever seen attached to the M8. But I think they mean the Sprint variant. Correct product ID would be M8_whl.
2) Instance of custom ROMs not working on M8 CDMA variants (Sprint and Verizon) are mainly due to the fact that those variants use a different Sense kernel. So mostly only applied to Sense ROMs. AOSP ROMs (in particular Lineage) which use their own kernel, work okay with the CDMA variants, far as I've seen.
3) Your firmware is so out to day, it will not work with any of the current ROMs. And when I say current, I mean any from the past several years. You should definitely update the firmware in any case, as it will cause lots of problems with custom ROMs, and no good reason to stay on the old firmware. Once firmware is updated, it is not hard to flash TWRP and try Lineage again. I think it will work, and there is certainly no harm in trying, even if it doesn't. The worst case scenario is that you flash a more updated (Marshmallow) version of the stock Sprint ROM. Which is still better than where you started with all this.

redpoint73 said:
2) Instance of custom ROMs not working on M8 CDMA variants (Sprint and Verizon) are mainly due to the fact that those variants use a different Sense kernel. So mostly only applied to Sense ROMs. AOSP ROMs (in particular Lineage) which use their own kernel, work okay with the CDMA variants, far as I've seen.
3) Your firmware is so out to day, it will not work with any of the current ROMs. And when I say current, I mean any from the past several years. You should definitely update the firmware in any case, as it will cause lots of problems with custom ROMs, and no good reason to stay on the old firmware. Once firmware is updated, it is not hard to flash TWRP and try Lineage again. I think it will work, and there is certainly no harm in trying, even if it doesn't. The worst case scenario is that you flash a more updated (Marshmallow) version of the stock Sprint ROM. Which is still better than where you started with all this.
Click to expand...
Click to collapse
I updated the firmware. I now have this:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.09.20.1112
(bootloader) version-main: 6.20.651.3
But the SIM doesn't work with Lineage anyway, just flashed in anew and tried. The old Sprint 6.0 ROM that I RUU'd has the same issue. Could it be the radio version, or the firmware? Because it used to work, with some troubles, but still.

gr0za said:
Could it be the radio version, or the firmware? Because it used to work, with some troubles, but still.
Click to expand...
Click to collapse
The radio is part of the firmware. Not sure why your SIM would have troubles with the newer radio (if that is the case).
You can try this: https://forum.xda-developers.com/htc-one-m8/general/how-to-convert-cdma-m8-sprint-vzw-gsm-t3303812
Or you can try flashing back to RUU 3.30.651.2 and see if there is any change.

redpoint73 said:
The radio is part of the firmware. Not sure why your SIM would have troubles with the newer radio (if that is the case).
You can try this: https://forum.xda-developers.com/htc-one-m8/general/how-to-convert-cdma-m8-sprint-vzw-gsm-t3303812
Or you can try flashing back to RUU 3.30.651.2 and see if there is any change.
Click to expand...
Click to collapse
Omg, how come I didn't see this thread. Thanks so much, I will try once I get back home.
I hope this thread isn't problematic, because I moved the goalpost since creating it. But I'd rather not create a thread every time I have a problem...

gr0za said:
I hope this thread isn't problematic, because I moved the goalpost since creating it. But I'd rather not create a thread every time I have a problem...
Click to expand...
Click to collapse
The problems are all related, and probably the same root cause (Sprint version, firmware, etc.). I agree it is most appropriate to keep everything to this one thread.