Develop Bugs

[Q] "clean install"

I got fed up with the problems my phone has been having since the Lollipop update and I decided to "reinstall" the whole thing. I've looked through lots of threads here and I more or less have an idea of what to do, but what troubles me is that most people point out that the phone will still not be the same as when it came from the shop.
So, could anyone please explain to me, how do I bring the phone back to its original maiden state. At this point, I don't even care if it would be Lollipop or KitKat, seeing that many people claim to have no problems with Lollipop.
It might well be that the problems I'm having are due to my meddling with the phone - i.e. disabling apps and restricting permissions. But at the same time, when I started backing up files to my PC in preparation to what I want to do with the phone, I found out that there are gigabytes of leftover data from apps that I had installed on KitKat. These apps are no longer installed on Lollipop, but their data (maps, dictionaries, etc.) are still there, despite the update and subsequent factory reset. And it certainly does not help that HTC Sync Manager erases records from my Outlook database instead of actually "syncing" the contacts with the phone.
I imagine what I need to do it to completely wipe the internal storage and flash the original HTC software there. Could anyone please confirm that this is possible and which method would be the safest?

Post the output of fastboot getvar all (minus your IMEI and serial number) first and we'll go from there

unifex_ said:
I got fed up with the problems my phone has been having since the Lollipop update and I decided to "reinstall" the whole thing. I've looked through lots of threads here and I more or less have an idea of what to do, but what troubles me is that most people point out that the phone will still not be the same as when it came from the shop.
So, could anyone please explain to me, how do I bring the phone back to its original maiden state. At this point, I don't even care if it would be Lollipop or KitKat, seeing that many people claim to have no problems with Lollipop.
It might well be that the problems I'm having are due to my meddling with the phone - i.e. disabling apps and restricting permissions. But at the same time, when I started backing up files to my PC in preparation to what I want to do with the phone, I found out that there are gigabytes of leftover data from apps that I had installed on KitKat. These apps are no longer installed on Lollipop, but their data (maps, dictionaries, etc.) are still there, despite the update and subsequent factory reset. And it certainly does not help that HTC Sync Manager erases records from my Outlook database instead of actually "syncing" the contacts with the phone.
I imagine what I need to do it to completely wipe the internal storage and flash the original HTC software there. Could anyone please confirm that this is possible and which method would be the safest?
Click to expand...
Click to collapse
Do as EddyOS says, he will guide you on the best which version to downgrade to (if your looking to do that). Honestly I didnt have any issues with Lollipop, its all good.
my suggestion of the easiest way to totally wipe up your internal memory is to unlock bootloader (if you've already unlocked it, then relock and unlock again), doing that will totally wipe your internal memory, as for ext. sd card, you can just format that.
Flashing original stock rom is done by an RUU.

EddyOS said:
Post the output of fastboot getvar all (minus your IMEI and serial number) first and we'll go from there
Click to expand...
Click to collapse
Thanks Eddy, I appreciate the help.
I attach an image of the fastboot output.

If you don't mind setting up the device from scratch, you just use the 4.19.111.2 RUU, available here:
https://drive.google.com/file/d/0B17smFr95pleNTFvYi1yNnJrcU0/view
You need a locked bootloader first, so use fastboot oem lock first otherwise it'll fail
1. Run the file as administrator
2. Connect the phone in fastboot mode to your PC
3. Follow the instructions
This will give you a 100% stock device, as if you just got it out the box

EddyOS said:
If you don't mind setting up the device from scratch, you just use the 4.19.111.2 RUU, available here:
https://drive.google.com/file/d/0B17smFr95pleNTFvYi1yNnJrcU0/view
You need a locked bootloader first, so use fastboot oem lock first otherwise it'll fail
1. Run the file as administrator
2. Connect the phone in fastboot mode to your PC
3. Follow the instructions
This will give you a 100% stock device, as if you just got it out the box
Click to expand...
Click to collapse
Great, that sounds uncomplicated enough. My bootloader is locked, as far as I know, at least I never did anything to unlock it. So I should be good to go.
One question though. At the moment, the phone is unlocked as far as SIM is concerned. I mean that although the CID is from T-Mobile Germany, I'm using O2 as the service provider. Will that RUU keep it that way, or it will make the phone locked towards T-Mobile SIM cards?
Thanks a lot.

It shouldn't put the SIM lock back on, if that's what you mean, but I can't say for certain it won't

EddyOS said:
It shouldn't put the SIM lock back on, if that's what you mean, but I can't say for certain it won't
Click to expand...
Click to collapse
In case it would, what would I have to do to unlock it? I don't have any T-Mobile SIM cards around here after all.

Buy a code, like you did last time

EddyOS said:
Buy a code, like you did last time
Click to expand...
Click to collapse
I did not buy any code, I bought a phone. That's how it came from the shop - SIM-unlocked. I had no idea it had the T-Mobile anything in it until I started looking around this forum and someone asked me about my CID.

If it was factory SIM-unlocked then it'll still be SIM-unlocked after flashing the RUU

EddyOS said:
If it was factory SIM-unlocked then it'll still be SIM-unlocked after flashing the RUU
Click to expand...
Click to collapse
Great, thanks! I'll let you know how it went.

OK, finally got the time to do it, but unfortunately, the RUU that I downloaded
EddyOS said:
If you don't mind setting up the device from scratch, you just use the 4.19.111.2 RUU, available here:
https://drive.google.com/file/d/0B17smFr95pleNTFvYi1yNnJrcU0/view
You need a locked bootloader first, so use fastboot oem lock first otherwise it'll fail
1. Run the file as administrator
2. Connect the phone in fastboot mode to your PC
3. Follow the instructions
Click to expand...
Click to collapse
did not work, I attach the screenshot with the error. Any ideas? The error was the same regardless of whether the phone was connected to the PC.

Yeah, it appears that RUU is corrupt

EddyOS said:
Yeah, it appears that RUU is corrupt
Click to expand...
Click to collapse
That's a pity. Do you know where can one find a proper RUU? I looked at the htcdev.com download section, they list the software I need, 4.19.111.2, but the download link brings me simply to the htc.de, where nothing can be downloaded, it's just their regular advertising site.
I also found a zip file with the 4.16.111.2 firmware on a German forum (basically, from a link in the xda thread with RUU and OTA collection), but to be honest, I'm not sure what to do with the bunch of img files.

The files on HTCDev are the kernel source so can't be flashed. Easiest thing to do for now is flash a ROM based on Lollipop until the proper RUU is re-posted

EddyOS said:
The files on HTCDev are the kernel source so can't be flashed. Easiest thing to do for now is flash a ROM based on Lollipop until the proper RUU is re-posted
Click to expand...
Click to collapse
How about the files from that site (German, though). I found that link on the xda thread for RUU collection.
http://www.handy-faq.de/forum/htc_o...ne_m8_firmwaresammlung_ruus_otas_backups.html
They have a list of various files, for 4.19.11.2 they have nandroid backups and signed firmware, but not a RUU.
Or could you suggest a well working ROM?

You could flash the backup, then the firmware to restore stock recovery and it should work

EddyOS said:
You could flash the backup, then the firmware to restore stock recovery and it should work
Click to expand...
Click to collapse
Could you help me with mine as well
from fastboot
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.25.21331147A1.06G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.20.631.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH445WM0----
(bootloader) imei: ----------------------
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B16000
(bootloader) cidnum: ROGER001
(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: dcdaa6e0
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.177s

ADB, Recovery and some issues

Hello XDA-Community,
I have an HTC One M8 (M8_UL) with the following details:
Software Status: Modified
*** UNLOCKED ***
And I have Cyanogenmod installed (latest nightly build 12.1-20151118-NIGHTLY-m8 Android 5.1.1) and TWRP 2.8.7.0
Now my GPS is not working since a while now (I can't really tell if it has even started when I moved to CM or if it happened afterwards).But GPS Status never gives me a single satellite. I have read in another topic here in the board, that getting back to Sense Stock could help. Then back to CM and everything could be fine.
But here my questions start:
1) What exactly does this S-ON mean?
2) So how do I know which firmware/recovery/system (I figured out that there is some difference between all this and that now my TWRP 2.8.7.0 obviously is my Recovery Tool installed at the moment.
3) What is RUU and OTA ? As I understood its like a Operating System Update out of windows? I once downloaded a version but it always claims my battery would not be full so it would not let me update/upgrade/recover?
4) Why is my version-main info empty? (see below)
Sorry for all these questions and thanks in advance for your help
C:\Users\fsc>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.25.214500021.06G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__102
(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: 3aa067db
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.053s
Click to expand...
Click to collapse

My answers below in blue font.
damarges said:
1) What exactly does this S-ON mean?
S-on/s-off is a HTC specific security flag. S-off means "security off" and in the past meant that all security checks are bypassed. On the M8, its a little more complicated than that, some things are bypassed, some are not. But it allows you to do things like flashing modified hboots, radios, unsigned RUUs and downgrade firmware. S-off is kind of a "back door" that HTC leaves for itself. But when exploited by users, such as the devs here at XDA, is handy for some pretty useful things. S-on is the "stock" condition, and means you don't have the ability to do these things. In order to get s-off, you need to use the sunshine method, which costs $25. But s-off is not required to flash ROMs, root, or return to stock.
2) So how do I know which firmware/recovery/system (I figured out that there is some difference between all this and that now my TWRP 2.8.7.0 obviously is my Recovery Tool installed at the moment.
Firmware number is indicated by main version in getvar output, or by the "OS" number on the bootloader screen.
If you want to go back to stock recovery, you will want the stock recovery file that matches your firmware number. But for what you describe, I don't think you need or want to flash stock recovery.
System is the ROM version number, and again if you are returning to stock, you should find the nandroid that has the same number as your firmware.
Don't confuse any of the above with the software number in the phone's settings (common mistake). That number is related to the current ROM. So if you flash a custom ROM, that number just corresponds to the custom ROM, not the firmware or stock ROM number.
3) What is RUU and OTA ? As I understood its like a Operating System Update out of windows? I once downloaded a version but it always claims my battery would not be full so it would not let me update/upgrade/recover?
RUU and OTA are related, but two very different things:
RUU = ROM update utility. Its a Windows executable, normally an official HTC tool that will completely re-image your phone to stock, every single partition, and will also wipe your phone. The CID and MID of your phone need to match what the RUU is intended for. Does not require stock ROM or stock recovery to run, but has to be same or greater version number than main version (or hboot) on the phone - meaning you can't "downgrade" (unless you have s-off). Relocking the bootloader is required to RUU (again, unless you have s-off).
OTA = over the air. Its an incremental OS update, sent out by HTC. It normally requires the software number directly proceeding it, meaning you need to install them in sequence, and can't skip any. And may not be a complete image, but simply a "patch". It also requires stock recovery to be present, as well as the stock ROM. No need to relock bootloader to OTA (unlike RUU). Also, OTA will not typically wipe the phone (but you should backup before OTA to be safe, as it does sometimes wipe data).
4) Why is my version-main info empty?
Common issue. This is usually because an outdated 2.7 version of TWRP was installed at some point, wiping out the main version info (known TWRP bug).
On the bootloader screen, does it read a number after "OS" in green letter?
Click to expand...
Click to collapse

Thanks a lot for these detailed descriptions. Makes it more clear to me.
Firmware number is indicated by main version in getvar output, or by the "OS" number on the bootloader screen.
Click to expand...
Click to collapse
>> as it is empty on my getvar output I don't know which firmware/recovery to choose?
On the bootloader screen, does it read a number after "OS" in green letter?
Click to expand...
Click to collapse
>> no. its just empty "OS- " thats it.
But for what you describe, I don't think you need or want to flash stock recovery.
Click to expand...
Click to collapse
>> no actually I don't want stock recovery. I am happy with TWRP. I actually just want to have my GPS issues fixed. else I am really happy with Cyanogenmod.
>> do you have knowledge on how to fix the GPS issue? or if returning to Sense ROM could fix it maybe?
So if I don't know my firmware/OS - number? how do I choose a proper nandroid backup? and does a nandroid backup does return my phone to sense ROM?

damarges said:
I am really happy with Cyanogenmod.
>> do you have knowledge on how to fix the GPS issue? or if returning to Sense ROM could fix it maybe?
Click to expand...
Click to collapse
I'm not a CM user on this device, so I'm not too familiar with the issue.
damarges said:
So if I don't know my firmware/OS - number? how do I choose a proper nandroid backup? and does a nandroid backup does return my phone to sense ROM?
Click to expand...
Click to collapse
I believe your firmware is 4.16.401.x (possibly "8" where the "x" is), based on your CID, and hboot and radio numbers indicating you are on Lollipop firmware.
Are you sure its a nandroid that is being discussed in the "fix" and not RUU to stock? If you direct me to the thread/post that discusses the fix, maybe I can take a look and see if I can figure anything out.
But yes, a stock nandroid for 4.16.401 will return you to the Sense ROM.

redpoint73 said:
Are you sure its a nandroid that is being discussed in the "fix" and not RUU to stock? If you direct me to the thread/post that discusses the fix, maybe I can take a look and see if I can figure anything out.
Click to expand...
Click to collapse
The links I used to gather information:
https://www.reddit.com/r/cyanogenmod/comments/3gw7fm/htc_one_m8_cm121_the_gps_doesnt_work/
On http://forum.xda-developers.com/showthread.php?t=2701376 I can not find a nandroid stock backup that is working. The link to 4.16.401.10 - TWRP Thanks to sneakyghost is not working anymore on mega :/
How do I create a nandroid backup myself (after hopefully I get fixed everything)?

I could replace my Cyanogenmod with a stock nandroid backup of htc sense. but it did not fix the GPS problem. Still not a single satellite to receive :/
Even erase modemst1 and erase modemst2 did not fix anything :/
Anyone has a hint what to do?

Htc One M8 help

So here's my predicament, a long while ago i had installed a rom to my phone assuming i had done everything correctly. This ROM i installed is the Bad Boys One M8 L Sense 7 v 1.0, it is currently still what I'm currently using. What I've been trying to do for days now to return my phone back to stock. My bootloader is unlocked and s-off. I have been unable to install any ROM whatsoever besides the current bad boyz rom. Also when trying to use sunshine, it seems to also encounter problems. If anyone can offer some help or a method to go about fixing this it would greatly appreciated.

Jdp2510 said:
So here's my predicament, a long while ago i had installed a rom to my phone assuming i had done everything correctly. This ROM i installed is the Bad Boys One M8 L Sense 7 v 1.0, it is currently still what I'm currently using. What I've been trying to do for days now to return my phone back to stock. My bootloader is unlocked and s-off. I have been unable to install any ROM whatsoever besides the current bad boyz rom. Also when trying to use sunshine, it seems to also encounter problems. If anyone can offer some help or a method to go about fixing this it would greatly appreciated.
Click to expand...
Click to collapse
For Sunshine to work, flash MaximumHD , or you could also flash ViperOneM8 (suggested by JCase, one of the Sunshine devs) for it to work.
If you want to go back to stock, you need to provide more info. Post the results of fastboot getvar all here (minus your IMEI and serial#), and I or someone else here will be able to give you proper directions.

xunholyx said:
For Sunshine to work, flash MaximumHD , or you could also flash ViperOneM8 (suggested by JCase, one of the Sunshine devs) for it to work.
If you want to go back to stock, you need to provide more info. Post the results of fastboot getvar all here (minus your IMEI and serial#), and I or someone else here will be able to give you proper directions.
Click to expand...
Click to collapse
I have tried the maximus hd with it getting stuck at the recovery screen. As for the other I'll do what i can to figure out that info for you

Jdp2510 said:
I have tried the maximus hd with it getting stuck at the recovery screen. As for the other I'll do what i can to figure out that info for you
Click to expand...
Click to collapse
Not much to figure out.
Hook your phone up to your PC, get into ADB/fastboot, and enter the command fastboot getvar all.

xunholyx said:
Not much to figure out.
Hook your phone up to your PC, get into ADB/fastboot, and enter the command fastboot getvar all.
Click to expand...
Click to collapse
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.09.20.0209
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.25.651.18
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 99000499318193
(bootloader) product: m8_whl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B70000
(bootloader) cidnum: SPCS_001
(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: 0f94b3b7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

I've tried running the appropriate RUU; I've tried flashing other roms with no success; I just can't seem to get the correct directions on what I need to do. If anyone has any ideas it will all be very appreciated.

Jdp2510 said:
I've tried running the appropriate RUU; I've tried flashing other roms with no success; I just can't seem to get the correct directions on what I need to do. If anyone has any ideas it will all be very appreciated.
Click to expand...
Click to collapse
You are S-On, so to run the RUU successfully you'll need to re-lock your bootloader first.
In fastboot : fastboot oem lock
Then run the RUU again

I did try that but it kept failing, I'll try one more time.

Like I thought, it failed again, error 155:
ERROR [155~159]: IMAGE ERROR
One of these error messages will appear when you use the incorrect RUU to update and the image file size is larger than the Flash ROM size. In this case, download the correct RUU version and try again.
I'm downloading the correct RUU. http://www.htc.com/us/support/rom-downloads.html - The HTC One M8.

Jdp2510 said:
Like I thought, it failed again, error 155:
ERROR [155~159]: IMAGE ERROR
One of these error messages will appear when you use the incorrect RUU to update and the image file size is larger than the Flash ROM size. In this case, download the correct RUU version and try again.
I'm downloading the correct RUU. http://www.htc.com/us/support/rom-downloads.html - The HTC One M8.
Click to expand...
Click to collapse
Error 155 is common for MM RUUs, as there is a peculiarity with the MM RUUs, in which you can't upgrade from LP (or KK for that matter) by RUU unless you first run the MM firmware.zip.
Try flashing the full signed firmware 6.20.651.3 from the following thread (with instructions on how to flash) then run the RUU 6.20.651.3 again:
http://forum.xda-developers.com/showthread.php?t=2729173
Or your other option is to flash the 4.25.651.18 RUU (same thead) and OTA to MM.
---------- Post added at 11:10 AM ---------- Previous post was at 11:08 AM ----------
Jdp2510 said:
I have been unable to install any ROM whatsoever besides the current bad boyz rom.
Click to expand...
Click to collapse
Hard to know what you are talking about, if you don't supply the required specifics (what ROMs exactly).
But only ROMs that specifically support Sprint, will work on your phone, due to kernel differences between Sprint and most other versions of the M8.
Running the MM RUU isn't going to change this fact. It seems your goal is to be able to install other ROMs?

What kind of specifics do you need?

I haven't been able to get any other roms to work. The ruu meant for my phone keeps failing, the name of the ROM is what details my phone says,

Jdp2510 said:
What kind of specifics do you need?
Click to expand...
Click to collapse
I already asked exactly what ROMs you tried.
You say you can't get "any ROMs" to work, and only name one (that does work).
You probably are trying to flash ROMs that don't support the Sprint version M8.
---------- Post added at 10:05 AM ---------- Previous post was at 10:04 AM ----------
Jdp2510 said:
The ruu meant for my phone keeps failing, the name of the ROM is what details my phone says,
Click to expand...
Click to collapse
Yup, and it will keep failing, if you just try the same thing over and over.
Did you try to do as I suggested in my post #10 above (flash MM firmware.zip, then try the RUU again)?

Sprint M8 Stock Roms

Hi, I made this post in the Sprint section a few days ago, but figured I'd post here as well to see if maybe this section has more traffic. If that's not allowed, I apologize in advance.
https://forum.xda-developers.com/sprint-htc-one-m8/help/stock-roms-t3669676
Basically, I'm looking for a stock rom for Sprint that would work with 1.54.651.8 firmware. All the links I can find on the forums seem to be dead.
Alternatively, a nandroid backup or way to extract the rom from the 1.54.651.8 RUU I do have (but won't successfully flash for whatever reason)
Any help would be appreciated. Thanks!

A custom ROM would need to support the Sprint M8, and be based on 4.4.2. Most any newer (newer than KitKat) ROMs will suffer major incompatibility with your ancient firmware, including extreme long boot time or no boot, and broken WiFi.
Suggest stocking with updating the firmware. Is the device s-on or s-off?
Problems with the RUU while "sending" are usually on the PC side. Try to re-install HTC drivers, try another USB port (USB 2.0 works best), and try another cable. Or even try another PC if possible.

Yeah I was able to find one custom 4.4.4 ROM (It was labelled 4.4.2, but it works so I guess it's close enough). There are just a few issues with it and I've always been more of a stock person anyway so I'd rather use a stock rom if I have the option.
As far as updating firmware, I am S-ON - I only originally rooted for a wifi hotspot app, so I didn't have a need to go S-OFF.
I guess it wouldn't hurt to give the RUUs a shot on a different computer. I'll just have to talk a friend into letting me install the drivers and giving it a go. One thing I'm not sure about - is it safe to go straight to the lastest RUU on HTC's site? I was willing to try it back when I had no rom at all, but now that I have a custom rom that mostly works, I'd rather not totally crap the bed.

Fuhcue said:
I guess it wouldn't hurt to give the RUUs a shot on a different computer. I'll just have to talk a friend into letting me install the drivers and giving it a go. One thing I'm not sure about - is it safe to go straight to the lastest RUU on HTC's site?
Click to expand...
Click to collapse
You can "skip" RUUs, and go the latest. However, you may (probably) need to update to the Marshmallow firmware anyway, before you can RUU. There is a strange limitation on most US version M8, where the RUU will fail with Error 155, if you try to go to Marshmallow from any former version (be it Kitkat or Lollipop) without first updating the firmware.
So the steps would be:
1) Relock bootloader
2) Flash to Marshmallow signed firmware (Sprint), in fastbootRUU mode
3) RUU to Marshmallow
4) Unlock bootloader again
5) Flash TWRP, root, and do whatever mods you want
Seeing as RUU will also wipe the phone. All this might be more than you want to do, if you are fairly happy with the phone as it is.

redpoint73 said:
Seeing as RUU will also wipe the phone. All this might be more than you want to do, if you are fairly happy with the phone as it is.
Click to expand...
Click to collapse
I don't so much mind the wipe, but I am a bit nervous about updating the firmware since that sounds like it could leave me in limbo if the RUU still didn't want to work for whatever reason. I guess I'll search around for where I can get that firmware and the procedure of how to do it and see how comfortable I feel with it in case I go that route.
If I knew for sure that it would all go through, I'd be fine with the reset. But that seems to take the attractive part of the RUU away in that it's no longer an "all in one" or one step process. (Not counting unlocking/relocking the bootloader since that's a quick and easy thing).

Fuhcue said:
I guess I'll search around for where I can get that firmware and the procedure of how to do it and see how comfortable I feel with it in case I go that route.
Click to expand...
Click to collapse
The firmware is posted in the same thread as the RUUs. And instructions on how to flash, as well.
https://forum.xda-developers.com/showthread.php?t=2729173
Fuhcue said:
If I knew for sure that it would all go through, I'd be fine with the reset. But that seems to take the attractive part of the RUU away in that it's no longer an "all in one" or one step process. (Not counting unlocking/relocking the bootloader since that's a quick and easy thing).
Click to expand...
Click to collapse
You can also opt for the Lollipop RUU (does not require flashing the firmware first). While not the latest, it's obviously more updated than what you presently have. And most of the current MM ROMs should work with LP firmware. There isn't much difference in the firmware it seems, for LP versus MM. Much different from KK to LP, which causes the problems I mentioned earlier (if you try to run KK firmware with LP or MM ROMs).
For maximum compatibility, matching the firmware is usually best. But I was running LP firmware with MM ROMs for a while (was simply to lazy to flash the MM firmware or RUU).

Ok so it sounds like the easiest option for me at this point is to grab a Lollipop RUU and try to flash it from a new computer with a fresh install of all the drivers. That way, at least if it fails to recognize my phone like the newest one did, I'll still be where I currently am with the stock (though outdated) firmware and custom rom.
Otherwise, I'll keep my fingers crossed that someone stumbles across this thread that has a meticulous archive of all old stock Sprint roms
Thanks so much for all your help and answering my questions so quickly. Much appreciated.

Hi
This is Sudheer from INDIA
i got Sprint HTC one M8 Harman Kardon from my friend.
after jail break it's supported Indian GSM sims there after only outgoing calls are working incoming calls are not working.
after so much of web search i unlock boot loader using HTC All in one and i enter into twrp wipe all system,cache and data. now its' hang on startup white screen not booting. yesterday i am trying to install os from following reference.
forum.xda-developers.com/showthread.php?t=2729173
finally i got 155 error Unsupported RUU. Please help me to come out with step by step guide because i am new for installing android phones.

Krishna Sudheer said:
after jail break it's supported Indian GSM sims there after only outgoing calls are working incoming calls are not working.
Click to expand...
Click to collapse
"Jail break" is a term specific to only iPhones. There is not such thing as "jail break" on an Android device. I assume you mean s-off, or some other mod? I can only guess, if you don't use the specific and proper terminology.
Krishna Sudheer said:
after so much of web search i unlock boot loader using HTC All in one and i enter into twrp wipe all system,cache and data. now its' hang on startup white screen not booting.
Click to expand...
Click to collapse
All in one Toolkit is obsolete, you shouldn't be using it. It contains a very old version of TWRP which will cause problems for many folks.
System partition is the OS/ROM. Should be obvious, that wiping the system partition results in no OS. Can't boot to an OS that isn't there any more. If you didn't know what the result would be from wiping a partition, you should be touching it in the first place!!!! Those options are listed under "Advanced" for a reason. If you aren't an advanced user, don't mess with them, unless you are following directions form an experienced user, or know what the result is going to be.
Krishna Sudheer said:
forum.xda-developers.com/showthread.php?t=2729173
finally i got 155 error Unsupported RUU. Please help me to come out with step by step guide because i am new for installing android phones.
Click to expand...
Click to collapse
Not enough info to know why the RUU failed. You linked a post with multiple RUUs, so we don't know which one you tried. We also don't know your current phone configuration.
Which version number RUU did you try? For HK version, you typically will need to flash the one that contains the digits "654". The RUU with digits "651" is for non-HK Sprint version. Assuming CID/MID has not been modified (which we don't know, if you don't provide more info).
Post specific info about your phone. Do fastboot getvar all, and post the results (delete IMEI and serial number before posting).
If the phone is s-on, you need to lock it in order to RUU. I don't know if you are s-on of s--off.
You can't run a lower number (downgrade) RUU unless you have s-off. Again, I don't know what version number RUU you tried, your current version number on the phone, or whether you are s-on or s-off.

Hi Sir,
Thank you for replying. Sim Unlocked from mobile store. actually I also don't know witch method they are using to unlock. After unlocking network signals showing in GSM mode. When I am changing to LTE mode again signals disappeared. In GSM mode incoming calls are not working. SMS both incoming and outgoing working fine.
I tried to change CID and s-off but it's not working.
TWRP I used version v2.7.0.2 these recovery installed from all in one twrp (sprint). when i come back in to bootloader it will asking No OS installed are you sure you wish to reboot?
My mobile model is HTC one M8 HK (831C) Sprint Internal storage is 32GB.
I download and used to flash following files.
1. signed_6.20.654.3_firmware.zip
2.RUU_M8_WHL_M60_SENSE70_SPCS_MR_Sprint_WWE_Harman_6.20.654.3.exe
3.0P6BIMG_Sprint_HTC_One_M8_Harman_6.20.654.3_RUU.zip
What was I do is
First Re-locked bootloader using with all in one and rename firmware as 0P6BIMG.ZIP then flash from SD Card Installed Successfully. Bootloader also showing OS version 6.20.654.3
Next using exe file "RUU_M8_WHL_M60_SENSE70_SPCS_MR_Sprint_WWE_Harman_6.20.654.3.exe" everything going well when the process bar reaching to 100% then it's showing error 155. I Checked the error guide provide by exe file there Unsupported RUU please try again with supported RUU.
Next using with ZIP file "0P6BIMG_Sprint_HTC_One_M8_Harman_6.20.654.3_RUU.zip" flash from SD Card it will showing not enough memory but internal is full empty.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.09.20.1112
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid:
(bootloader) product: m8_whl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B70000
(bootloader) cidnum: SPCS_004
(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: 205bdca3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.031s
Kindly check and do the needful. Let me know how to install OS and where witch rom I use to install.

My responses below in red font:
Krishna Sudheer said:
After unlocking network signals showing in GSM mode. When I am changing to LTE mode again signals disappeared. In GSM mode incoming calls are not working. SMS both incoming and outgoing working fine.
LTE is difficult (maybe impossible) to get working in cases where the device is not intended for your region/carrier (which I assume is the case, that you are not located in US, on the Sprint carrier). GSM should work (as you indicated) as well as 3G (HSPA) provided that your carrier uses a band(s) supported by the Sprint version M8
I tried to change CID and s-off but it's not working. I don't know what that means "it's not working". Most folks who say they have trouble with getting s-off, are trying the hopeless waste of time, which is trying to usethe long obsolete "free" s-off method of firewater. It's never going to work.
Also, you should also be careful here, when changing CID. Only use a Sprint CID, or SuperCID with a Sprint firmware/RUU. Trying to use any other firmware or RUU will result in a radio brick (possibly permanent).
TWRP I used version v2.7.0.2 these recovery installed from all in one twrp (sprint). when i come back in to bootloader it will asking No OS installed are you sure you wish to reboot? That version is too old (over 4 years) and you should have used current TWRP. This was probably caused by using the toolkit (which I mentioned is not advised anymore). Old versions of TWRP was not compatible with Sprint M8 (it had it's own "CDMA" version TWRP) and it probably caused the wrong partition to be overwritten.
What was I do is
First Re-locked bootloader using with all in one and rename firmware as 0P6BIMG.ZIP then flash from SD Card Installed Successfully. Bootloader also showing OS version 6.20.654.3 Try flashing firmware again, the number should show up in getvar all (below) under "version-main". Flashing firmware twice is usually a good idea.
Next using exe file "RUU_M8_WHL_M60_SENSE70_SPCS_MR_Sprint_WWE_Harman_6.20.654.3.exe" everything going well when the process bar reaching to 100% then it's showing error 155. I Checked the error guide provide by exe file there Unsupported RUU please try again with supported RUU.
Error 155 is common, if flashing a US Marshmallow RUU, without being on the matching firmware. Flashing firmware again, as indicated above, may solve it.
Next using with ZIP file "0P6BIMG_Sprint_HTC_One_M8_Harman_6.20.654.3_RUU.zip" flash from SD Card it will showing not enough memory but internal is full empty.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.09.20.1112
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: firmware number should appear here
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid:
(bootloader) product: m8_whl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B70000
(bootloader) cidnum: SPCS_004
(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: 205bdca3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.031s
Click to expand...
Click to collapse

HTC One M8 stuck on HTC screen

Hi all.
Got a HTC one m8 in and it appears to be stuck on the HTC screen, I can get into bootloader fine, have tried to reflash via SD card but i get a CID error.
Can anyone direct me to what ROM i need to be installing? Its a UK version.
Thanks in advance.

Jabbah said:
Hi all.
Got a HTC one m8 in and it appears to be stuck on the HTC screen, I can get into bootloader fine, have tried to reflash via SD card but i get a CID error.
Can anyone direct me to what ROM i need to be installing? Its a UK version.
Thanks in advance.
Click to expand...
Click to collapse
What does it say next to "OS" in your bootloader menu?

Jabbah said:
have tried to reflash via SD card but i get a CID error.
Can anyone direct me to what ROM i need to be installing? Its a UK version.
Click to expand...
Click to collapse
Tried to flash what? Can't troubleshoot what you did wrong, unless you tell is what you tried to flash. RUU, firmware.zip, or something else? What is the version number and file name?
That is in addition to the info requested in the previous reply.
Also, if you know how, do fastboot getvar all, and post the results (delete IMEI and serial number before posting) so we can see more info about the device.

redpoint73 said:
Tried to flash what? Can't troubleshoot what you did wrong, unless you tell is what you tried to flash. RUU, firmware.zip, or something else? What is the version number and file name?
That is in addition to the info requested in the previous reply.
Also, if you know how, do fastboot getvar all, and post the results (delete IMEI and serial number before posting) so we can see more info about the device.
Click to expand...
Click to collapse
Tried to flash a stock UK rom.
I have no idea how to use that command sorry.
os is 6.12.61.4

(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.61.4
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: ORANG001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!

Jabbah said:
Tried to flash a stock UK rom.
Click to expand...
Click to collapse
Still too vague for us to have any idea what you tried to flash.
I asked some specific questions for a reason; some of which you seem to have missed or ignored. I'm not just typing to exercise my fingers!
redpoint73 said:
RUU, firmware.zip, or something else?
What is the version number and file name?
Click to expand...
Click to collapse
"Stock UK ROM" can mean a number of things. If you are talking about RUU, then calling it a "stock ROM" is not the right term (and confusing) since RUU is a complete image containing something like 41 partitions, with the ROM being only one of those partitions.
In fact, if you are referring to RUU, I don't think your version M8 (or most UK versions, for that matter) has a valid RUU. So you are likely in fact not even trying to flash a stock UK ROM. Which also explains the CID error.
On a positive note, good work figuring out how to do fastboot getvar all. If you can provide more info on what you tried to flash, we can make some progress!

redpoint73 said:
Still too vague for us to have any idea what you tried to flash.
I asked some specific questions for a reason; some of which you seem to have missed or ignored. I'm not just typing to exercise my fingers!
"Stock UK ROM" can mean a number of things. If you are talking about RUU, then calling it a "stock ROM" is not the right term (and confusing) since RUU is a complete image containing something like 41 partitions, with the ROM being only one of those partitions.
In fact, if you are referring to RUU, I don't think your version M8 (or most UK versions, for that matter) has a valid RUU. So you are likely in fact not even trying to flash a stock UK ROM. Which also explains the CID error.
On a positive note, good work figuring out how to do fastboot getvar all. If you can provide more info on what you tried to flash, we can make some progress!
Click to expand...
Click to collapse
Thanks for the replies, ive actually gotten somewhere today, Ive installed twrp, and installed the latest Lineage ROM which booted fine .
But.... Not detecting sim card
Always something haha

Another option (especially now that you have unlocked the bootloader, and installed TWRP), is restore stock TWRP backup 6.12.61.4 from here:
https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
No need to do Step 3, nor Steps 10 or after (only relevant to get OTA updates - which no longer applies to this device). Just reboot.
Jabbah said:
Thanks for the replies
Click to expand...
Click to collapse
There is a button for that.

Quick update, Restored stock TWRP as you suggested, performed simunlock and am now a happy chappy with a working M8
Now, Whats the best ROM to use for it ? Is it worth installing Lineage ROM?
David.

Jabbah said:
Quick update, Restored stock TWRP as you suggested, performed simunlock and am now a happy chappy with a working M8
Now, Whats the best ROM to use for it ? Is it worth installing Lineage ROM?
Click to expand...
Click to collapse
Glad the TWRP restore worked out for you.
No such thing as a "best ROM". Each individual user has different preferences and tastes. That's the reason there are different ROM choices. If there was a "best ROM", nobody would ever need anything else, right?
I am not personally a Lineage user (so good example right there how one person's opinion may not apply to you). But if you flash it again, I assume you can (or will) have the same problem with SIM not detected. I think I've seen other folks with the problem on Lineage (again, I don't really keep up with that ROM), so you should check the thread to see if there is a fix for that issue.

redpoint73 said:
Glad the TWRP restore worked out for you.
No such thing as a "best ROM". Each individual user has different preferences and tastes. That's the reason there are different ROM choices. If there was a "best ROM", nobody would ever need anything else, right?
I am not personally a Lineage user (so good example right there how one person's opinion may not apply to you). But if you flash it again, I assume you can (or will) have the same problem with SIM not detected. I think I've seen other folks with the problem on Lineage (again, I don't really keep up with that ROM), so you should check the thread to see if there is a fix for that issue.
Click to expand...
Click to collapse
Got around the sim not detected issue, the phone was simlocked to orange, it just didnt pop up with the enter unlock code dialogue.
Ill try a few see what they are like
Thanks again for your help.

Jabbah said:
Got around the sim not detected issue, the phone was simlocked to orange.
Click to expand...
Click to collapse
Understood. I would not have expected the "SIM not detected" error in that case. So thanks for clarifying.
Jabbah said:
it just didnt pop up with the enter unlock code dialogue.
Click to expand...
Click to collapse
Stock (Sense) ROM is needed to unlock SIM. Which you either figured out, or stumbled upon the solution by luck! :good: