Develop Bugs

WiFi will not turn on after custom ROM installs

So, just for a bit of background info:
I found out about the release of Lollipop for the HTC One M8 is in February. Me, being the kinda impatient type, wanted it sooner! So, having never messed around with android devices before, thought "Why not now?" And dived in to some tutorials. After unlocking my bootloader, installing TWRP as the recovery, and installing a new ROM to do the S-Off with firewater, I learned a few things: Firewater doesn't work anymore, the next best (and seemingly only) alternative costs $25, my phone wasn't booting up anymore, and I hadn't made a backup.
So yeah, that sucked. After attempting to side load the ROM and a few different ROMS, I finally managed to find a stock ROM that worked on the first load and actually booted successfully at an acceptable rate.
<b>SO WHERE I'M AT NOW</B>
Everything is fine and dandy now, with the exception of one thing: the WiFi will not turn on. I will press the WiFi "switch," and it will only become greyed out. All of my other wireless connections will work, and I am not on airplane mode (I have even switched that on and off plenty of times as well). The only solution I could find through searching was to flash the boot.img that came in the ROM, and that didn't work.
As for specs, I'm a little inexperienced, so I don't know what to provide other than this:
HTC One M8
Carrier: AT&T
Not rooted, and don't plan on it
Boot loader is unlocked
I believe it is on a stock ROM
Does anybody know how to fix this? Any help would be appreciated!
Sent from my HTC One_M8 using XDA Free mobile app

Your firmware is mismatched with the ROM you flashed.
Either flash a ROM that matches your firmware, or RUU back to stock (need to relock bootloader with s-on to run RUU).
Also, why do so many folks skip the step of not making a nandroid backup? This should be a mandatory step before doing any mods or flashing a ROM. I don't ever leave my phone without a known good nandroid or at least a known good ROM.zip.

redpoint73 said:
Also, why do so many folks skip the step of not making a nandroid backup? This should be a mandatory step before doing any mods or flashing a ROM. I don't ever leave my phone without a known good nandroid or at least a known good ROM.zip.
Click to expand...
Click to collapse
OK, so I didn't exactly NOT make a backup... I just made the wrong type of backup. I'm new to all this, and for some reason my mind thought it was OK to back up all my DATA, not to make a backup image. I feel pretty stupid about that, and you're allowed to feel the same way about me.
Also, would you have instructions on finding a ROM that fits the firmware? Like I've said, I'm new to this and I also can't find anything about it - everything assumes that I know everything there is to know already! And the fact that'll AT&T doesn't release the M8 RUUs doesn't help either.
Sent from my HTC One_M8 using XDA Free mobile app

hardcore_spaghetti said:
OK, so I didn't exactly NOT make a backup... I just made the wrong type of backup. I'm new to all this, and for some reason my mind thought it was OK to back up all my DATA, not to make a backup image. I feel pretty stupid about that, and you're allowed to feel the same way about me.
Also, would you have instructions on finding a ROM that fits the firmware? Like I've said, I'm new to this and I also can't find anything about it - everything assumes that I know everything there is to know already! And the fact that'll AT&T doesn't release the M8 RUUs doesn't help either.
Sent from my HTC One_M8 using XDA Free mobile app
Click to expand...
Click to collapse
Who told you there were no RUUs for AT&T?
Here ya go:
http://dl3.htc.com/application/RUU_...20.51A.4198.01L_F_release_387305_signed_2.exe
---------- Post added at 07:38 PM ---------- Previous post was at 07:14 PM ----------
redpoint73 said:
Your firmware is mismatched with the ROM you flashed.
Either flash a ROM that matches your firmware, or RUU back to stock (need to relock bootloader with s-on to run RUU).
Also, why do so many folks skip the step of not making a nandroid backup? This should be a mandatory step before doing any mods or flashing a ROM. I don't ever leave my phone without a known good nandroid or at least a known good ROM.zip.
Click to expand...
Click to collapse
People don't like to follow instructions. I ALWAYS have a recent backup. If stuff goes bad, you can go back to the way it was before you screwed stuff up. It is the most basic step when flashing/modding; and it is always step #1 on any ROM/mod thread, but people like to skip it for some reason. I guess people like to learn the hard way.

xunholyx said:
Who told you there were no RUUs for AT&T?
Click to expand...
Click to collapse
Me and the people who were looking for AT&T-branded RUUs, not Cingular! I'll give it a try, thanks a lot!
Sent from my HTC One_M8 using XDA Free mobile app
EDIT:
It worked! Thank you so much for that RUU. My phone is running great now.

hardcore_spaghetti said:
Me and the people who were looking for AT&T-branded RUUs, not Cingular! I'll give it a try, thanks a lot!
Click to expand...
Click to collapse
I don't know why they still use the "Cingular" name in the RUU title. But regardless, you will find the AT&T RUUs listed in a variety of places, including the HTC website:
http://www.htc.com/us/support/htc-one-m8-att/news/
---------- Post added at 09:19 AM ---------- Previous post was at 09:10 AM ----------
hardcore_spaghetti said:
OK, so I didn't exactly NOT make a backup... I just made the wrong type of backup. I'm new to all this, and for some reason my mind thought it was OK to back up all my DATA, not to make a backup image. I feel pretty stupid about that, and you're allowed to feel the same way about me.
Click to expand...
Click to collapse
Well, at least you thought to make a backup of some sort, which is better than a lot of folks. My rant was aimed at folks who (all too often) know well that they should make a backup, and don't bother to do so. Than are all "Uh oh, I can't boot now and didn't make a backup. What should I do?"
Modding the phone with no backup plan and no plan to recover = a bad idea.
hardcore_spaghetti said:
Also, would you have instructions on finding a ROM that fits the firmware? Like I've said, I'm new to this and I also can't find anything about it - everything assumes that I know everything there is to know already!
Click to expand...
Click to collapse
The information is all here if you read and search enough; but I'll admit the concept of "firmware" is a bit confusing.
The short answer: Boot into bootloader, and unless you've tampered with hboot in some way (not possible with s-on) the hboot number will correspond with your current firmware version, which will also tell you what software based ROMs you can run properly:
hboot 3.16 = 1.x software
hboot 3.18 = 2.x software
hboot 3.19 = 3.x software
If you look at the title or top post of each custom ROM, they will usually call out what software version the ROM is based. So you just need to find one that corresponds to your hboot number, flash it, and everything should work find. If you are looking at a specific ROM, and still can't determine what software version its based, just post a link here and we will answer that.
If you are currently on hboot 3.16 (1.x firmware) you can also relock the bootloader and run the 2.23 RUU to update to the 2.x firmware; and then be able to run 2.x software based ROMs. But with s-on, you can't update to 3.x firmware yet, until AT&T releases the corresponding OTA and/or RUU. There are methods to update to 3.x firmware with s-off.
You can read more technical info about firmware here: http://forum.xda-developers.com/htc-one-m8/development/progress-fuu-m8-t2813792

redpoint73 said:
Your firmware is mismatched with the ROM you flashed.
Either flash a ROM that matches your firmware, or RUU back to stock (need to relock bootloader with s-on to run RUU).
Also, why do so many folks skip the step of not making a nandroid backup? This should be a mandatory step before doing any mods or flashing a ROM. I don't ever leave my phone without a known good nandroid or at least a known good ROM.zip.
Click to expand...
Click to collapse
Hey about that your firmware doesn't match the rom HOW COULD I KNOW?

Void tracer said:
Hey about that your firmware doesn't match the rom HOW COULD I KNOW?
Click to expand...
Click to collapse
You would only know by reading or searching. But its discussed on many threads, including the various custom ROM threads (sometimes in one of the top posts of the ROM thread).
For the most part, if you are changing to a higher software number (first number in the string: 1.x to 2.x, 3.x , etc.) you will need to update your firmware accordingly. This goes mostly for Sense ROMs; although some GPE or AOSP ROMs also require certain firmwares or at least an updated hboot. Again, check the specific ROM thread for details.

redpoint73 said:
You would only know by reading or searching. But its discussed on many threads, including the various custom ROM threads (sometimes in one of the top posts of the ROM thread).
For the most part, if you are changing to a higher software number (first number in the string: 1.x to 2.x, 3.x , etc.) you will need to update your firmware accordingly. This goes mostly for Sense ROMs; although some GPE or AOSP ROMs also require certain firmwares or at least an updated hboot. Again, check the specific ROM thread for details.
Click to expand...
Click to collapse
i still don't understand .... i went for a rom called revolutionhd and got stuck in boot loop,, spent around 8 hours trying different things , after that i got lucky that a rom called maxiumushd worked , i am s-on the dev says S-on will probably face a certain problems one of them is camera issue and files disappeared , that i fixed by the way he mentioned it should be fixed , but the wifi fix You must update firmware to latest 4.xx.xxx.x i don't understand , by installing his rom didn't i update to that version? the 4.xx.xxx.x ? or i must be at the same version before i flash a rom with that version? if yes, now roms are modding the current software? not also upgrading? and in my case i was 4.4.4 i think what should i do? i can't upgrade to lolipop? i didn't study for my finals thinking the device got bricked please help me out this is the second day ...

Void tracer said:
i still don't understand .... i went for a rom called revolutionhd and got stuck in boot loop,, spent around 8 hours trying different things , after that i got lucky that a rom called maxiumushd worked , i am s-on the dev says S-on will probably face a certain problems one of them is camera issue and files disappeared , that i fixed by the way he mentioned it should be fixed , but the wifi fix You must update firmware to latest 4.xx.xxx.x i don't understand , by installing his rom didn't i update to that version? the 4.xx.xxx.x ? or i must be at the same version before i flash a rom with that version? if yes, now roms are modding the current software? not also upgrading? and in my case i was 4.4.4 i think what should i do? i can't upgrade to lolipop?.
Click to expand...
Click to collapse
Your confusion is a bit understandable. The term "firmware" is confusing. Its true that in the past, the term "firmware" has sometimes been used interchangeably with "ROM". However in this case (and most frequently when talking about this phone), we are not talking about the ROM; but rather we are talking about a number of other modules including hboot, radio, recovery, WiFi, Bluetooth and others that actually do not get flashed with the ROM. And in fact, most of these modules can't be modified by "unofficial" means unless you have s-off.
HTC has also developed a somewhat contrived situation on their recent devices, in that while they claim to be "friendly to the mod community" by letting users unlock the bootloader and flash ROMs; they also have been in the habit of making significant updates to the firmware for every major software update (update from from Android 4.4.2 to 4.4.3, etc). And if you don't update the firmware when flashing a ROM of a higher software base, you are going to run into some major issues as you have seen (most commonly broken WiFi and extreme long boot times).
For a little more explanation on firmware vs. ROM, the following link has some good info: http://forum.xda-developers.com/showthread.php?p=52484527
You can still update the firmware with s-on by installing your version's OTA of (if available) RUU. You can also flash a firmware.zip if one has been posted for your CID that is still HTC signed/encrypted. But many firmware zips are not signed, and in that case you can't flash it unless you have s-off.
Void tracer said:
i didn't study for my finals thinking the device got bricked please help me out this is the second day ...
Click to expand...
Click to collapse
You can erase the notion in your mind that this phone is ever bricked, if the screen comes on. As long as the screen comes on, this phone is virtually always recoverable. And usually not that hard, just involves knowing the correct steps.
Also one of the cardinal rules of flashing ROMs, is always have a known good nandroid backup before flashing. Having a known-good nandroid to revert to resolves a lot of "OMG I bricked the phone" moments.

redpoint73 said:
Your confusion is a bit understandable. The term "firmware" is confusing. Its true that in the past, the term "firmware" has sometimes been used interchangeably with "ROM". However in this case (and most frequently when talking about this phone), we are not talking about the ROM; but rather we are talking about a number of other modules including hboot, radio, recovery, WiFi, Bluetooth and others that actually do not get flashed with the ROM. And in fact, most of these modules can't be modified by "unofficial" means unless you have s-off.
HTC has also developed a somewhat contrived situation on their recent devices, in that while they claim to be "friendly to the mod community" by letting users unlock the bootloader and flash ROMs; they also have been in the habit of making significant updates to the firmware for every major software update (update from from Android 4.4.2 to 4.4.3, etc). And if you don't update the firmware when flashing a ROM of a higher software base, you are going to run into some major issues as you have seen (most commonly broken WiFi and extreme long boot times).
For a little more explanation on firmware vs. ROM, the following link has some good info: http://forum.xda-developers.com/showthread.php?p=52484527
You can still update the firmware with s-on by installing your version's OTA of (if available) RUU. You can also flash a firmware.zip if one has been posted for your CID that is still HTC signed/encrypted. But many firmware zips are not signed, and in that case you can't flash it unless you have s-off.
You can erase the notion in your mind that this phone is ever bricked, if the screen comes on. As long as the screen comes on, this phone is virtually always recoverable. And usually not that hard, just involves knowing the correct steps.
Also one of the cardinal rules of flashing ROMs, is always have a known good nandroid backup before flashing. Having a known-good nandroid to revert to resolves a lot of "OMG I bricked the phone" moments.
Click to expand...
Click to collapse
Thanks you big time for explaining this to me i did go to a nandroid backup of my same cid/mid and everything was good , restored using twrp i still have the wifi issue ... i tried to flash the latest OTA and it failed (after going to stock) i really don't know what to do googled everything .. do u think i should make a thread for it?

Void tracer said:
Thanks you big time for explaining this to me i did go to a nandroid backup of my same cid/mid and everything was good , restored using twrp i still have the wifi issue ... i tried to flash the latest OTA and it failed (after going to stock) i really don't know what to do googled everything .
Click to expand...
Click to collapse
You probably installed the nandroid that didn't match with your firmware, so you are going to have the same issue as with a custom ROM: Your current firmware version doesn't match the software (OS) version.
What CID, what hboot number? What nandroid did you restore?
Void tracer said:
do u think i should make a thread for it?
Click to expand...
Click to collapse
We've already been back and forth on your issue on this thread, and its relevant to this thread's topic. So NO I don't think you should make a new thread.

redpoint73 said:
You probably installed the nandroid that didn't match with your firmware, so you are going to have the same issue as with a custom ROM: Your current firmware version doesn't match the software (OS) version.
What CID, what hboot number? What nandroid did you restore?
We've already been back and forth on your issue on this thread, and its relevant to this thread's topic. So NO I don't think you should make a new thread.
Click to expand...
Click to collapse
I believe its correct here is the link to the thread : http://forum.xda-developers.com/showthread.php?t=2701376
go to nandroid backups then all other CIDS i grabbed the htc__59 here is my phone info :
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.19.21331147A1.09G
(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: 0P6B11000
(bootloader) cidnum: HTC__059
(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: 5e4b24e4
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

Void tracer said:
I believe its correct here is the link to the thread : http://forum.xda-developers.com/showthread.php?t=2701376
go to nandroid backups then all other CIDS i grabbed the htc__59
Click to expand...
Click to collapse
Yes, but which one did you use exactly? There are 3 different software numbers available for your CID on the stock nandroid thread: 1.54, 2.22 and 3.32.

redpoint73 said:
Yes, but which one did you use exactly? There are 3 different software numbers available for your CID on the stock nandroid thread: 1.54, 2.22 and 3.32.
Click to expand...
Click to collapse
newest which is 3.32

Void tracer said:
newest which is 3.32
Click to expand...
Click to collapse
Your hboot (3.18) corresponds with 2.22, you want to restore that nandroid.
The 3.32 nandroid doesn't match with your 2.22 firmware. That is why WiFi is still broken.

redpoint73 said:
Your hboot (3.18) corresponds with 2.22, you want to restore that nandroid.
The 3.32 nandroid doesn't match with your 2.22 firmware. That is why WiFi is still broken.
Click to expand...
Click to collapse
so i download 2.2 and i am good to go?

Void tracer said:
so i download 2.2 and i am good to go?
Click to expand...
Click to collapse
Yes, you should be.

redpoint73 said:
Yes, you should be.
Click to expand...
Click to collapse
Hey man just installed it everything works TY big time , but umm now i want to update to the maximushd rom and i have to update as i understood to match the android version of the rom itself , i am s-on and unlocked, now i have to re-lock to flash it ? and then unlock again to flash the rom??

Void tracer said:
Hey man just installed it everything works TY big time , but umm now i want to update to the maximushd rom and i have to update as i understood to match the android version of the rom itself , i am s-on and unlocked, now i have to re-lock to flash it ? and then unlock again to flash the rom??
Click to expand...
Click to collapse
What you want to do now, is apply any available OTA updates available for your CID. You will need to update to 3.x software (Android 4.4.4) than to 4.x (Android 5.0, Lollipop). Do you know if Lollipop has been rolled out for your version?
The OTA will also update your firmware (not just the ROM). Then once you are on Lollipop firmware, you will be able to run any custom Lollipop ROMs.
You do not need to relock the bootloader to install the OTA. And I do not recommend you do so (its better unlocked).
Reason for that, once you are OTA updated to Lollipop, you can then re-install custom recovery (you need an unlocked bootloader for that) then you can install a custom ROM (such as MaximumHD as you asked).

[Q] Returning to stock, international M8

I unlocked the bootloader (offical version, S-ON) and flashed Dirty Unicorns Marshmallow ROM. The battery life is plain horrible, but I'm not sure if that's because of the ROM or the phone. Now I want to flash it back to stock, mainly because my M8 shut itself off twice yesterday when I used GPS due to overheating (had to hold it near AC in the car so it wouldn't shut down again).
I read a lot of guides, but I'm really confused because HTC complicated it so much (I'm not inexperienced in flashing, had two Sony devices and a Xiaomi). Can anyone help me out?
Sent from my One M8

sunbriel said:
I unlocked the bootloader (offical version, S-ON) and flashed Dirty Unicorns Marshmallow ROM. The battery life is plain horrible, but I'm not sure if that's because of the ROM or the phone. Now I want to flash it back to stock, mainly because my M8 shut itself off twice yesterday when I used GPS due to overheating (had to hold it near AC in the car so it wouldn't shut down again).
I read a lot of guides, but I'm really confused because HTC complicated it so much (I'm not inexperienced in flashing, had two Sony devices and a Xiaomi). Can anyone help me out?
Sent from my One M8
Click to expand...
Click to collapse
What does it say next to "OS" in your bootloader menu?

xunholyx said:
What does it say next to "OS" in your bootloader menu?
Click to expand...
Click to collapse
"OS-" so basically nothing.
Sent from my One M8

sunbriel said:
"OS-" so basically nothing.
Sent from my One M8
Click to expand...
Click to collapse
That's because you are using an old version of TWRP (2.7.x.x) that had a bug that the firmware version wouldn't be listed.
Hook up your phone to your PC and get into fastboot. Enter fastboot getvar all and post the readout here, minus your serial# and IMEI

xunholyx said:
That's because you are using an old version of TWRP (2.7.x.x) that had a bug that the firmware version wouldn't be listed.
Hook up your phone to your PC and get into fastboot. Enter fastboot getvar all and post the readout here, minus your serial# and IMEI
Click to expand...
Click to collapse
Code:
version: 0.5
version-bootloader: 3.19.0.0000
version-baseband: 1.29.214500021.1
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
product: m8_ul
platform: hTCBmsm8974
modelid: 0P6B10000
cidnum: HTC__032
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: 76df2b54
hbootpreupdate: 11
gencheckpt: 0

First of all, update to the current TWRP version 3.0. As @xunholyx indicated, the OS number being blank means you used a really old TWRP version, which can cause a lot of issues. Then flash the ROM again (after default wipe in TWRP - data, cache and Dalvik) and see if that helps.
Or try another ROM.
If you still want to return to stock, you can get the TWRP stock backup here: http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
What you want is 6.12.401.4
Although, standard operating procedure for any ROM flashing would have dictated that you made a nandroid (TWRP backup) of the stock ROM before flashing anything. If you had done so, you could have simply restore that backup to return to the stock ROM.

Thanks for the help.
Well, I didn't create a nandroid backup of stock ROM since I thought that going back to factory settings was as easy as with Sony or Xiaomi devices. This HTC stuff is way too messed up, and I don't understand why they made it that way. I didn't expect that, tbh.
Edit: just checked, the TWRP version I have is 3.0.2-0.

sunbriel said:
Thanks for the help.
Well, I didn't create a nandroid backup of stock ROM since I thought that going back to factory settings was as easy as with Sony or Xiaomi devices. This HTC stuff is way too messed up, and I don't understand why they made it that way. I didn't expect that, tbh.
Edit: just checked, the TWRP version I have is 3.0.2-0.
Click to expand...
Click to collapse
Your OS/version-main will remain blank until you flash firmware. Just flashing the newer recovery on its own won't do that

sunbriel said:
Well, I didn't create a nandroid backup of stock ROM since I thought that going back to factory settings was as easy as with Sony or Xiaomi devices. This HTC stuff is way too messed up, and I don't understand why they made it that way. I didn't expect that, tbh.
Click to expand...
Click to collapse
You should never assume anything is the same between Android manufacturers; they each have their own quirks. And you should always make a backup before flashing a ROM, root, or other mods.; doesn't matter what the manufacturer.
Returning to stock by flashing a stock TWRP backup is not complicated. Since you've already achieved unlocking the bootloader, flashing custom recovery, and custom ROM; you can certainly handle restoring to stock with a TWRP backup. You basically just download the backup file, unzip the folders, put the folders in the proper place on the phone, then Restore the backup in TWRP. The instructions in the thread I link just break it down into steps, for you convenience. But it all just boils down to getting the backup on the phone (since you didn't make one yourself) and restoring it. I even figured out what version number you needed, and told you. So how much easier do you want it?
Your version also has an RUU (HTC specific restore tool), which will return you to stock after relocking the bootloader. But to be honest, its not that complicated to restore the TWRP backup as already suggested.

I already restored everything to stock and sold the phone. The battery life was horrible even on stock (mostly below 3h SOT with very light usage).
You say I should always make a nandroid. That's true, but for instance with Sony, even if you soft brick your phone, you just downlpad a ftf file and flash it with Flashtool. Also, another reason why I didn't make a nandroid backup of stock is because I didn't have anything worth backing up - it was pure stock without any of my apps installed since the phone was freshly bought off craigslist.
Sent from my X98 Air II using Tapatalk

sunbriel said:
You say I should always make a nandroid. That's true, but for instance with Sony, even if you soft brick your phone, you just downlpad a ftf file and flash it with Flashtool. Also, another reason why I didn't make a nandroid backup of stock is because I didn't have anything worth backing up - it was pure stock without any of my apps installed since the phone was freshly bought off craigslist.
Click to expand...
Click to collapse
The point of making a nandroid prior to any mods is to backup the stock ROM, not just your personal data.
Always know how to revert to stock, before you start messing with the phone. And how to do that varies with each device. That's all I'm saying.

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.

No SIM Detected Suddenly

I know this is a common issue for the HTC One M8, but my phone stopped recognising any SIM card all of a sudden. It happened right after the battery got discharged fully (sudden power off), though I'm not ruling out the possibility that recent drops might have contributed to this.
I already tried the scotch tape solution to no avail as well as wiping cache and dalvik and rebooting a bunch of times with, without, and with other SIM cards in.
I'm running this Google Play Edition flashable ROM with the corresponding firmware, unrooted and s-on.
Should I go straight to re-flashing the same firmware and ROM? Is there anything I could attempt before having everything wiped?
One weird note that I've also noticed in another post: if I go to "phone info" the IMEI and phone number show as "unknown", but I can see them with fastboot getvar all. Also in "phone info", the "TURN OFF RADIO" button doesn't seem to be doing anything when pressed. Any alternative way to do it?
Thank you! :fingers-crossed:

AlexanderGrey said:
I'm running this Google Play Edition flashable ROM with the corresponding firmware, unrooted and s-on.
Should I go straight to re-flashing the same firmware and ROM? Is there anything I could attempt before having everything wiped?
Click to expand...
Click to collapse
The RUU provided in the GPE thread you linked, would be my suggestion. Should be same (or similar) to flashing the ROM and firmware. But with the RUU, you are sure to have all partitions (around 40) returned to "factory stock" (at least for GPE version) condition.
You might also try another RUU (return to Sense) or another ROM. But in any case, you should backup your data and prepared to fully wipe. Trying to migrate data across ROMs is only going to complicate matters, and you will never be sure that the SIM issue is due to the some incompatibility with your existing user data.

redpoint73 said:
The RUU provided in the GPE thread you linked, would be my suggestion. Should be same (or similar) to flashing the ROM and firmware. But with the RUU, you are sure to have all partitions (around 40) returned to "factory stock" (at least for GPE version) condition.
You might also try another RUU (return to Sense) or another ROM. But in any case, you should backup your data and prepared to fully wipe. Trying to migrate data across ROMs is only going to complicate matters, and you will never be sure that the SIM issue is due to the some incompatibility with your existing user data.
Click to expand...
Click to collapse
Thanks for the quick reply.
I haven't gone the GPe RUU route as that would require s-off, which I'm not planning to get. I forgot to mention I've been using this ROM & firmware for over 2 months without any issues.
I'm not very familiar with the topic of backup - although I've flashed ROMs in the past I've always done a clean install. Could you please elaborate? Would I be able to save installed apps with a backup via TWRP? Or would you advise against that?

AlexanderGrey said:
I haven't gone the GPe RUU route as that would require s-off, which I'm not planning to get. I forgot to mention I've been using this ROM & firmware for over 2 months without any issues.
Click to expand...
Click to collapse
You wouldn't have been able to flash the GPE firmware s-on, unless it is a signed zip and you have an actual GPE version M8 (correct CID and MID). The requirements for flashing the firmware are same as the RUU.
Please do fastboot getvar all, and post the results (delete IMEI and serial number before posting) so we can see more info about the device.
AlexanderGrey said:
I'm not very familiar with the topic of backup - although I've flashed ROMs in the past I've always done a clean install. Could you please elaborate? Would I be able to save installed apps with a backup via TWRP? Or would you advise against that?
Click to expand...
Click to collapse
There are lots of ways to backup data, each with their pros and cons. So how you do it is up to you.
A TWRP backup of app data is only going to work if you are just restoring the same ROM. So if you are flashing the RUU/ROM same as you have now, then it will work.
But if you try another ROM, it's usually not a good idea to try to "migrate" app data using TWRP. Different ROMs store their app data in different ways, and trying to migrate the data across different ROMs via TWRP backup is asking for trouble. In those cases, I use Titanium Backup for apps and app data (requires root). There are other options, but Titanium is tried and true (for most) and it is what I personally use.
Other data, like photos, videos you took, and any other media you want to keep (music, ringtones, porn) you can just copy to a computer, SD card, cloud solutions etc. Again, there are lots of options.

redpoint73 said:
You wouldn't have been able to flash the GPE firmware s-on, unless it is a signed zip and you have an actual GPE version M8 (correct CID and MID). The requirements for flashing the firmware are same as the RUU.
Please do fastboot getvar all, and post the results (delete IMEI and serial number before posting) so we can see more info about the device.
There are lots of ways to backup data, each with their pros and cons. So how you do it is up to you.
A TWRP backup of app data is only going to work if you are just restoring the same ROM. So if you are flashing the RUU/ROM same as you have now, then it will work.
But if you try another ROM, it's usually not a good idea to try to "migrate" app data using TWRP. Different ROMs store their app data in different ways, and trying to migrate the data across different ROMs via TWRP backup is asking for trouble. In those cases, I use Titanium Backup for apps and app data (requires root). There are other options, but Titanium is tried and true (for most) and it is what I personally use.
Other data, like photos, videos you took, and any other media you want to keep (music, ringtones, porn) you can just copy to a computer, SD card, cloud solutions etc. Again, there are lots of options.
Click to expand...
Click to collapse
Thanks for the info on backing up, I should have been more specific though. I've used Titanium Backup in the past a little bit, but recently I've opted to keep my phone unrooted mostly for some banking apps I use. Backing up with TWRP sounds good to me as I'd like to keep the same ROM (ideally) and would not want to go through reinstalling everything.
My phone is not a GPE version however the ROM I currently use is compatible with all M8 versions (except dual-sim) and with s-on. Here's the info:
(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: 6.12.401.4
(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: HTC__002
(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

AlexanderGrey said:
My phone is not a GPE version however the ROM I currently use is compatible with all M8 versions (except dual-sim) and with s-on. Here's the info:
(bootloader) version-main: 6.12.401.4
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__002
Click to expand...
Click to collapse
The GPE firmware never flashed (maybe you flashed it, and it failed to install). Otherwise, the version-main number would have changed to a GPE version number (5.07.1700.15 as noted in the firmwares you linked). And as mentioned, it isn't possible to flash GPE firmware while s-on (firmware for a different CID, MID).
Now, none of this explains your SIM issue. Maybe start by simply "dirty" flashing the GPE ROM (keep user data, just wipe cache and Dalvik) and see if there is any change.

redpoint73 said:
The GPE firmware never flashed (maybe you flashed it, and it failed to install). Otherwise, the version-main number would have changed to a GPE version number (5.07.1700.15 as noted in the firmwares you linked). And as mentioned, it isn't possible to flash GPE firmware while s-on (firmware for a different CID, MID).
Now, none of this explains your SIM issue. Maybe start by simply "dirty" flashing the GPE ROM (keep user data, just wipe cache and Dalvik) and see if there is any change.
Click to expand...
Click to collapse
Hmm you're right, my memory is playing tricks on me. I remember flashing a new firmware however, because I was having issues with the wi-fi and bluetooth before it. After some searching I think I used this one, am I right?
I'll try a quick firmware flash as you indicated, and will get back with the results a bit later. Thanks!

AlexanderGrey said:
Hmm you're right, my memory is playing tricks on me. I remember flashing a new firmware however, because I was having issues with the wi-fi and bluetooth before it. After some searching I think I used this one, am I right?
Click to expand...
Click to collapse
That would be my guess, yes.
AlexanderGrey said:
I'll try a quick firmware flash as you indicated, and will get back with the results a bit later. Thanks!
Click to expand...
Click to collapse
Flashing firmware requires you to relock the bootloader (since you are s-on) which will wipe your data.
As I mentioned in my last response, you might try to just "dirty flash" the GPE ROM (keep the current firmware) just to see what happens, before taking any measure which cause your data to be wiped.
I would still recommend to backup your data before even a dirty flash - you can't be too safe!

AlexanderGrey said:
Hmm you're right, my memory is playing tricks on me. I remember flashing a new firmware however, because I was having issues with the wi-fi and bluetooth before it. After some searching I think I used this one, am I right?
I'll try a quick firmware flash as you indicated, and will get back with the results a bit later. Thanks!
Click to expand...
Click to collapse
Unfortunately, no visible change . Still no SIM detected.

redpoint73 said:
That would be my guess, yes.
Flashing firmware requires you to relock the bootloader (since you are s-on) which will wipe your data.
As I mentioned in my last response, you might try to just "dirty flash" the GPE ROM (keep the current firmware) just to see what happens, before taking any measure which cause your data to be wiped.
I would still recommend to backup your data before even a dirty flash - you can't be too safe!
Click to expand...
Click to collapse
Sorry, I meant re-flashing the ROM. That's what I did so far.

AlexanderGrey said:
Sorry, I meant re-flashing the ROM. That's what I did so far.
Click to expand...
Click to collapse
You may consider flashing the Euro RUU 6.12.401.4 form here: https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
This will put your phone on a fully stock software/firmware "baseline" (for your phone's original configuration). If the SIM problem persists after that, I would have to think it was a hardware issue.
RUU as you know, will wipe the phone. So backup your data accordingly, before relocking the bootloader and running the RUU.

redpoint73 said:
You may consider flashing the Euro RUU 6.12.401.4 form here: https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
This will put your phone on a fully stock software/firmware "baseline" (for your phone's original configuration). If the SIM problem persists after that, I would have to think it was a hardware issue.
RUU as you know, will wipe the phone. So backup your data accordingly, before relocking the bootloader and running the RUU.
Click to expand...
Click to collapse
Thanks redpoint, that's the same one I have installed currently, right?
I guess ultimately I'll have to bite the bullet and try it if I want to figure out if it's a software or hardware issue.

AlexanderGrey said:
Thanks redpoint, that's the same one I have installed currently, right?
Click to expand...
Click to collapse
Same version number as the currently installed firmware. But what you flashed before is just firmware (about 80 MB) which includes hboot, radio, recovery, boot.img, and several others (maybe about 10 partitions?). The RUU (about 1.5 GB) will restore a complete factory image (every partition - about 40 of them).

redpoint73 said:
Same version number as the currently installed firmware. But what you flashed before is just firmware (about 80 MB) which includes hboot, radio, recovery, boot.img, and several others (maybe about 10 partitions?). The RUU (about 1.5 GB) will restore a complete factory image (every partition - about 40 of them).
Click to expand...
Click to collapse
Ah I understand now, I was not aware of that previously.
I was also planning to replace my battery so I might just do that first and have a look if anything looks unusual around the SIM card tray.
Thanks for all the help, I'll come back with a conclusion after a day or two when I get the chance .

redpoint73 said:
Same version number as the currently installed firmware. But what you flashed before is just firmware (about 80 MB) which includes hboot, radio, recovery, boot.img, and several others (maybe about 10 partitions?). The RUU (about 1.5 GB) will restore a complete factory image (every partition - about 40 of them).
Click to expand...
Click to collapse
Update: after replacing the battery I flashed the RUU and the same ROM back on.
Good news is the SIM card works now . I'm just a bit concerned about this happening again. Since you've seen quite a few cases on this forum I wanted to ask: do you think this is a common issue with that particular ROM?
I searched for SIM card issues in the thread of that ROM but the only legit ones I saw were the cases where people only installed the ROM without updating the firmware (so their wifi and bluetooth was not working either).
Cheers.

AlexanderGrey said:
Good news is the SIM card works now . I'm just a bit concerned about this happening again. Since you've seen quite a few cases on this forum I wanted to ask: do you think this is a common issue with that particular ROM?
Click to expand...
Click to collapse
Nothing that I am aware of. Running GPE ROM with Sense firmware might not be ideal. But I don't recall seeing any similar cases (no SIM).

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.