Develop Bugs

Help with installing AT&T Ruu

I'm a very new android user, so please forgive my ignorance.
I'm using a sim unlocked AT&T M8 outside USA with a different carrier. Right now, the bootloader is Locked, CID is 11111111 and S-OFF. I've downloaded the official marshmallow AT&T RUU for m8 from htc website.
I follow the install instructions until the update actually starts. Then it stops after about 10-20 seconds and shows Error 155: unknown error and enters into the recovery steps (in the RUU). My current software number is 4.28.502.2 and im trying to update to RUU_M8_UL_M60_SENSE70_ATT_MR_Cingular_US_6.20.502.5
Can someone please help me out with this? I've been trying for over a week now. I will never receive the OTA's since I'm not using an AT&T sim. So RUU is the only other option left. Thanks a lot in advance.

http://forum.xda-developers.com/showpost.php?p=66886759&postcount=23

ckpv5 said:
http://forum.xda-developers.com/showpost.php?p=66886759&postcount=23
Click to expand...
Click to collapse
Thanks for your reply man, but im extremely lost here. Could you please guide me step by step? I've downloaded the firmware. Where do I put it? I've tried the adb folder. But it show error: can not locate firmware.zip.
Edit: Another question. Is that firmware applicable for my device?

The firmware is applicable BUT since you're using your device outside USA and not on AT&T carrier, S-Off .. the best thing for you to do is fully convert your device to other region, maybe a EU region or Dev Edition .. more suitable for you.
I read somewhere, with the latest firmware you may have calls problem due to Voice HD implemented by AT&T
If you're interested in converting, I will guide you (when I am available)

ckpv5 said:
The firmware is applicable BUT since you're using your device outside USA and not on AT&T carrier, S-Off .. the best thing for you to do is fully convert your device to other region, maybe a EU region or Dev Edition .. more suitable for you.
I read somewhere, with the latest firmware you may have calls problem due to Voice HD implemented by AT&T
If you're interested in converting, I will guide you (when I am available)
Click to expand...
Click to collapse
That would be very kind of you, thanks. Though, i think I've already messed up my phone. I finally got to update with the firmware in the link. The RUU was going on smoothly as well, until it reached 38% when Error 155 showed up again. The phone then went on to the bootloader screen with no options for fastboot, restore or such. I restarted it and entered the bootloader. My firmware is being shown as 6.20.502.5 but when rebooting the phone it won't go past the screen with the HTC logo. I'd be extremely grateful if you could help me out of this mess.
Also, when i open htc sync man, OS number and HTC Sense number shows up as blank, while the firmware number is shown as 6.20.502.5

Big-Bonsai said:
Also, when i open htc sync man, OS number and HTC Sense number shows up as blank, while the firmware number is shown as 6.20.502.5
Click to expand...
Click to collapse
Aren't you supposed to uninstall Htc Sync Manager before you run the RUU ?
That was clearly stated in link that I gave you earlier, and you also need PC with USB 2.0
Uninstall HTC Sync Manager but leave HTC USB drivers then try again to run RUU after you put the device on bootloader/fastboot mode.

ckpv5 said:
Aren't you supposed to uninstall Htc Sync Manager before you run the RUU ?
That was clearly stated in link that I gave you earlier, and you also need PC with USB 2.0
Click to expand...
Click to collapse
Yeah I did. I re-installed it later to see if it would show any information.

Most important is RUU must complete 100%, no error 155
I never use Htc Sync Manager, so I don't know what is shown there.

ckpv5 said:
Most important is RUU must complete 100%, no error 155
I never use Htc Sync Manager, so I don't know what is shown there.
Click to expand...
Click to collapse
So I'm gonna try the RUU again. I'll keep you updated. You've been a big help. Thanks a lot!!

Big-Bonsai said:
I'm a very new android user, so please forgive my ignorance.
I'm using a sim unlocked AT&T M8 outside USA with a different carrier. Right now, the bootloader is Locked, CID is 11111111 and S-OFF. I've downloaded the official marshmallow AT&T RUU for m8 from htc website.
I follow the install instructions until the update actually starts. Then it stops after about 10-20 seconds and shows Error 155: unknown error and enters into the recovery steps (in the RUU). My current software number is 4.28.502.2 and im trying to update to RUU_M8_UL_M60_SENSE70_ATT_MR_Cingular_US_6.20.502.5
Can someone please help me out with this? I've been trying for over a week now. I will never receive the OTA's since I'm not using an AT&T sim. So RUU is the only other option left. Thanks a lot in advance.
Click to expand...
Click to collapse
I don't know if it's the problem,but did you try the RUU after unlocking your bootloader as you are S-OFF?
I think it's supposed to be unlocked if you have S-OFF.
Edit:Just got to know that S-OFF devices have nothing to do with unlocked or locked bootloader.
Why don't you try a EU RUU?Mine was also a AT&T device,but I converted it.

Jongla said:
I don't know if it's the problem,but did you try the RUU after unlocking your bootloader as you are S-OFF?
I think it's supposed to be unlocked if you have S-OFF.
Edit:Just got to know that S-OFF devices have nothing to do with unlocked or locked bootloader.
Why don't you try a EU RUU?Mine was also a AT&T device,but I converted it.
Click to expand...
Click to collapse
Hey man, thanks for replying here. I sent you a pm. Could you please check?

ckpv5 said:
Most important is RUU must complete 100%, no error 155
I never use Htc Sync Manager, so I don't know what is shown there.
Click to expand...
Click to collapse
Hello there. I kind of made it work. What I did was take the rom.zip from the ruu file and flash it via htc fastboot special. And it worked well. The only problem I'm facing now is that the boot animations are EXTREMELY slow. But once it's past that, everything seems pretty normal. I wiped the cache from recovery but that didn't help. Do you have any suggestions for me?

Big-Bonsai said:
\The only problem I'm facing now is that the boot animations are EXTREMELY slow. But once it's past that, everything seems pretty normal. I wiped the cache from recovery but that didn't help.
Click to expand...
Click to collapse
Meaning the boot animations are slow every time you boot, or just the first time (its unclear from what you've posted)? First time booting after RUU will be slow, due to cache being setup, etc. And clearing cache will cause that process to repeat when you start up again.
---------- Post added at 09:32 AM ---------- Previous post was at 09:30 AM ----------
Jongla said:
I think it's supposed to be unlocked if you have S-OFF.
Edit:Just got to know that S-OFF devices have nothing to do with unlocked or locked bootloader.
Click to expand...
Click to collapse
Neither of those statements is entirely correct.
With s-off, you can run an RUU with bootloader locked or relocked. Essentially, the check for the bootloader unlocked condition is bypassed with s-off.
But having the bootloader locked still means its locked (even with s-off). Meaning you can't do things like flash custom recovery with bootloader locked (even with s-off).

redpoint73 said:
Meaning the boot animations are slow every time you boot, or just the first time (its unclear from what you've posted)? First time booting after RUU will be slow, due to cache being setup, etc. And clearing cache will cause that process to repeat when you start up again.
Hello there. Thanks for the reply. What I meant was, the boot animations are slow every time I reboot the device.
Things I have already done:
1. Flashed the rom.zip again.
2. Factory reset.
3. Wiped the cache from recovery multiple times.
4. Restarted in all possible ways. Normal restart. Power off, wait 10 minutes and power on again. Pressed the power and volume up button for restarting. Reboot via fastboot.
I'd really appreciate if you could help me out.
Click to expand...
Click to collapse

redpoint73 said:
Meaning the boot animations are slow every time you boot, or just the first time (its unclear from what you've posted)? First time booting after RUU will be slow, due to cache being setup, etc. And clearing cache will cause that process to repeat when you start up again.
---------- Post added at 09:32 AM ---------- Previous post was at 09:30 AM ----------
Neither of those statements is entirely correct.
With s-off, you can run an RUU with bootloader locked or relocked. Essentially, the check for the bootloader unlocked condition is bypassed with s-off.
But having the bootloader locked still means its locked (even with s-off). Meaning you can't do things like flash custom recovery with bootloader locked (even with s-off).
Click to expand...
Click to collapse
Hello there. Thanks for the reply. What I meant was, the boot animations are slow every time I reboot the device.
Things I have already done:
1. Flashed the rom.zip again.
2. Factory reset.
3. Wiped the cache from recovery multiple times.
4. Restarted in all possible ways. Normal restart. Power off, wait 10 minutes and power on again. Pressed the power and volume up button for restarting. Reboot via fastboot.
I'd really appreciate if you could help me out.

Since you've already flashed the RUU again, I don't think there is much else you can do. Maybe its a common issue with the new build?

redpoint73 said:
Since you've already flashed the RUU again, I don't think there is much else you can do. Maybe its a common issue with the new build?
Click to expand...
Click to collapse
Man I searched EVERYWHERE. People dont seem to have any problems like this. What I did find out was that this might happen if the firmware or kernel numbers dont match (or something?). Can you tell me if I did anything wrong?

Big-Bonsai said:
What I did find out was that this might happen if the firmware or kernel numbers dont match (or something?).
Click to expand...
Click to collapse
That only applies to flashing ROMs in custom recovery. WHich is completely different from RUU. RUU re-writes all partitions, including firmware, kernel, ROM, and a bunch of others. So there isn't a possibility of a mismatch; as long as the RUU ran properly. And since you ran the RUU twice, you pretty much eliminated the possibility it didn't install completely.
Some other options you may consider:
1) Unlock the bootloader, flash TWRP custom recovery, flash a different ROM and see if the slow boot issue persists.
2) Change CID and/or MID (which you are free to do since you are s-off) and try another RUU; such as Developer's Edition or Euro.

redpoint73 said:
That only applies to flashing ROMs in custom recovery. WHich is completely different from RUU. RUU re-writes all partitions, including firmware, kernel, ROM, and a bunch of others. So there isn't a possibility of a mismatch; as long as the RUU ran properly. And since you ran the RUU twice, you pretty much eliminated the possibility it didn't install completely.
Some other options you may consider:
1) Unlock the bootloader, flash TWRP custom recovery, flash a different ROM and see if the slow boot issue persists.
2) Change CID and/or MID (which you are free to do since you are s-off) and try another RUU; such as Developer's Edition or Euro.
Click to expand...
Click to collapse
Thank you so much for the reply. I'd like to take your second suggestion. Can you please point me to the right direction? Or guide me through the steps. I don't know if it's asking too much of you. Thanks anyways.

Big-Bonsai said:
Thank you so much for the reply. I'd like to take your second suggestion. Can you please point me to the right direction? Or guide me through the steps.
Click to expand...
Click to collapse
Which version do you want to "convert" to?
Dev Ed is easy, it shares the same model ID (MID) as AT&T, and you already have SuperCID. So all you would need to do is run the MM Dev Ed RUU: http://dl3.htc.com/application/RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4.exe
Euro is a bit more steps, you would need to change to the Euro MID: http://forum.xda-developers.com/showthread.php?t=2708581
Then run Euro MM RUU, noting that relocking bootloader is not needed for you (since you have s-off): http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6

[Q] How can I update my M9

Hey guys,
I came here as I got a replacement M9 (refurbished - for an old and well used M8) which I tried to update but it won't let me do the OTA's or even the RUU's to get from 5.1 to 6 (which even my M8 had). I even
got the Zip files for the 2-part update and copied them on the phone, using the manual update option in the boot-menu (manual update from sd-card).... but all of that doesn't work because of an "Error 7" .
After trying factory reset and what the "basic user" does in cases like this I found out that my phone had already been "tampered" with as it is "S-Off" and the all 1's CID (Super-CID ? as far as I read something
like that). I don't need OTA possibilities but at least the option to update it somehow :/ ... any suggestion?

Arcdar said:
Hey guys,
I came here as I got a replacement M9 (refurbished - for an old and well used M8) which I tried to update but it won't let me do the OTA's or even the RUU's to get from 5.1 to 6 (which even my M8 had). I even
got the Zip files for the 2-part update and copied them on the phone, using the manual update option in the boot-menu (manual update from sd-card).... but all of that doesn't work because of an "Error 7" .
After trying factory reset and what the "basic user" does in cases like this I found out that my phone had already been "tampered" with as it is "S-Off" and the all 1's CID (Super-CID ? as far as I read something
like that). I don't need OTA possibilities but at least the option to update it somehow :/ ... any suggestion?
Click to expand...
Click to collapse
1) Change your MID to the developer MID (i.e., fastboot oem writemid 0PJA11000)
2) Change your CID to the developer CID (i.e., fastboot oem writecid BS_US001)
3) Flash this RUU: http://www.htc.com/us/support/htc-one-m9/news/
EDIT: See here: http://forum.xda-developers.com/att-one-m9/general/att-developer-edition-ruu-how-to-t3086948

efrant said:
1) Change your MID to the developer MID (i.e., fastboot oem writemid 0PJA11000)
2) Change your CID to the developer CID (i.e., fastboot oem writecid BS_US001)
3) Flash this RUU: http://www.htc.com/us/support/htc-one-m9/news/
EDIT: See here: http://forum.xda-developers.com/att-one-m9/general/att-developer-edition-ruu-how-to-t3086948
Click to expand...
Click to collapse
Thank's so much!
I'll try it tomorrow

Arcdar said:
Thank's so much!
I'll try it tomorrow
Click to expand...
Click to collapse
Hey,
I'm sorry I reply that late but I needed enough time to try everything out and do a full backup before that. I tried that today and somehow it tells me that it doesn't work - again
Bootloader:
-Software status is official
-Locked
-s-off
CID: BS__US001
MID: 0PJA10000
I also tried it with CID: HTC__001
I downloaded the 2.08GB file you linked and they talk about but it always tells me it can't update it. Same if I get the EU/Unlocked RUU's from HTC and try to go from 5.1 to 6 (the 2 step install process or with the one-RUU for 6).
I'm really sad/fed up/angry by now.... I even had 6.0 on my One M8 ... and just can't get 6 work on my One M9

Arcdar said:
Hey,
I'm sorry I reply that late but I needed enough time to try everything out and do a full backup before that. I tried that today and somehow it tells me that it doesn't work - again
Bootloader:
-Software status is official
-Locked
-s-off
CID: BS__US001
MID: 0PJA10000
I also tried it with CID: HTC__001
I downloaded the 2.08GB file you linked and they talk about but it always tells me it can't update it. Same if I get the EU/Unlocked RUU's from HTC and try to go from 5.1 to 6 (the 2 step install process or with the one-RUU for 6).
I'm really sad/fed up/angry by now.... I even had 6.0 on my One M8 ... and just can't get 6 work on my One M9
Click to expand...
Click to collapse
Not sure if it's a typo on your part, but the MID is wrong. You have it for Wwe. that could be the issue, unless it's a typo, then it's not.

squ89r97 said:
Not sure if it's a typo on your part, but the MID is wrong. You have it for Wwe. that could be the issue, unless it's a typo, then it's not.
Click to expand...
Click to collapse
my bad, a typo - here in the forum, not on my phone. the RUU-Installer that was linked for that still doesn't work

HTC one m9 STUCKED. NO Recovery Mode, NO Download mode,but still booting into android

Hi, everybody, This is my first thread in this wonderfull comunity.
I own a HTC one m9 Hima UHL
-Android 5.0.2
-Sense 7.0
-Soft. version: 1.10.709.2
-MID: 0PJA11000 (the original was 2PRG10000)
-CID: 11111111 (the original was HTC__621)
-What is really great is that I GOT S-OFF AND BOOTLOADER UNLOOKED (also rooted by KINGO app)
As the title says I can boot into android and use my phone normally, but due to a several tries to update my phone to android Nougat, I surelly did something wrong
-RUU.EXE NOT WORKING (I just tried with RUU1.36.709.3.exe)
Not because of the version, is bause I can not enter in download mode, afeter running the wizard it just reboot the device.
-I DO CAN ENTER TO BOOTLOADER MODE
But anithing to do from here, if I go to to recovery (latest TWRP installed when download mode still working) or download mode, It goes to the same place "nowere", just appear a message bellow about flashing unoficial Rom, and legal stuffs, etc......
PLEASE ANY HELP (about something not tried yet) WILL BE TOTALLY APPRECIATE
I JUST WANT TO TAKE MY PHONE TO STOCK AGAIN (keeping the s-off and boatloader)
PS:
I read that once getting s-off and bootloader unlocked, it would be normal to "Cross-Flash firmware", so what I was trying to do before messing all up was to install a different firmware (different SKU or region, e.g. 3.x.617.x), and once there apply the recent released 4.19.617.1. (If somebody can correct me about this as well it would be great, but my priority now is to reset my phone to factory, no problem about personal data loss)

jhon222 said:
Hi, everybody, This is my first thread in this wonderfull comunity.
I own a HTC one m9 Hima UHL
-Android 5.0.2
-Sense 7.0
-Soft. version: 1.10.709.2
-MID: 0PJA11000 (the original was 2PRG1000)
-CID: 11111111 (the original was HTC__621)
-What is really great is that I GOT S-OFF AND BOOTLOADER UNLOOKED (also rooted by KINGO app)
As the title says I can boot into android and use my phone normally, but due to a several tries to update my phone to android Nougat, I surelly did something wrong
-RUU.EXE NOT WORKING (I just tried with RUU1.36.709.3.exe)
Not because of the version, is bause I can not enter in download mode, afeter running the wizard it just reboot the device.
-I DO CAN ENTER TO BOOTLOADER MODE
But anithing to do from here, if I go to to recovery or download mode, It goes to the same place "nowere", just appear a message bellow about flashing unoficial Rom, and legal stuffs, etc......
PLEASE ANY HELP (about something not tried yet) WILL BE TOTALLY APPRECIATE
I JUST WANT TO TAKE MY PHONE TO STOCK AGAIN (keeping the s-off and boatloader)
PS:
I read that once getting s-off and bootloader unlocked, it would be normal to "Cross-Flash firmware", so what I was trying to do before messing all up was to install a different firmware (different SKU or region, e.g. 3.x.617.x), and once there apply the recent released 4.19.617.1. (If somebody can correct me about this as well it would be great, but my priority now is to reset my phone to factory, no problem about personal data loss)
Click to expand...
Click to collapse
First of all: Please reduce the size of the text in your post. It's hard to read.
You can flash RUUs for different regions with S-OFF but you don't own a M9. The M9 has 0PJA***** model IDs. Your phone's original model ID is 2PRG1000. It's probably a M9+ or a M9+ Prime Camera edition or something like that. These devices are completely different than the M9. Therefore you shoudn't flash any M9 files on your phone unless you want a fancy new paperweight.
I recommend you reverting your MID and your CID back to their original values and try to flash a RUU for your device. (I don't know whether there is one you could use. I don't own your device and therefore have no knowledge about the file that are available for it.) If you can't find a suitable RUU you'll need to contact Llabtoofer's RUU Service.

Flippy498 said:
First of all: Please reduce the size of the text in your post. It's hard to read.
You can flash RUUs for different regions with S-OFF but you don't own a M9. The M9 has 0PJA***** model IDs. Your phone's original model ID is 2PRG1000. It's probably a M9+ or a M9+ Prime Camera edition or something like that. These devices are completely different than the M9. Therefore you shoudn't flash any M9 files on your phone unless you want a fancy new paperweight.
I recommend you reverting your MID and your CID back to their original values and try to flash a RUU for your device. (I don't know whether there is one you could use. I don't own your device and therefore have no knowledge about the file that are available for it.)
Click to expand...
Click to collapse
Dear sir, @Flippy498
Im really greatful for your answer, I can not understand why I did not see what is obvious, It is not the model I thought...
Besides de MID, the product is not Hima, but HIMARUHL, the ram 2gb and Camera 13mp... (yeahh Im very silly)
I searched over Internet and badly there is not too much information about this especific MID number (2PRG10000), wich I think now belonges to a "HTC ONE M9E". Beyond the fact that there is a RUU available or not, I think I can not install one, because once an ruu.exe is runned this one tried to enter to download mode, wich is unavailable, then reboot and throw the error "USB communication failed", Before messing up the phone, the RUU.exe throwed the "signature error" WICH I UNDERSTAND NOW, because I was trying tu run the wrong one; so I appreciate if you suggest me another way different to ruu.exe installing.
Thanks for your great attendance.

jhon222 said:
Dear sir, @Flippy498
Im really greatful for your answer, I can not understand why I did not see what is obvious, It is not the model I thought...
Besides de MID, the product is not Hima, but HIMARUHL, the ram 2gb and Camera 13mp... (yeahh Im very silly)
I searched over Internet and badly there is not too much information about this especific MID number (2PRG10000), wich I think now belonges to a "HTC ONE M9E". Beyond the fact that there is a RUU available or not, I think I can not install one, because once an ruu.exe is runned this one tried to enter to download mode, wich is unavailable, then reboot and throw the error "USB communication failed", Before messing up the phone, the RUU.exe throwed the "signature error" WICH I UNDERSTAND NOW, because I was trying tu run the wrong one; so I appreciate if you suggest me another way different to ruu.exe installing.
Thanks for your great attendance.
Click to expand...
Click to collapse
Your phone seems to have a mediatek processor. Those devices need to get handled a bit different than snapdragon devices. However, I absolutely have no experiences with mediatek devices. If I were you I'd contact the service I linked in my earlier post...

HTC M8 Downgrading

Dear XDA developers, professionals and programmers:
Recently I came across a good deal (HTC M8 in mint condition) and bought it. It was running Android 4.4.4 and I was happy with it till I read that it could be updated to Marshmallow. I followed a few links and after some time discovered that it was originally bought from the USA and locked to AT&T even though the installed rom was WWE. Stupidly I downloaded Marshmallow update for AT&T (RUU) from the HTC website and ran the installer. The installer completed successfully and the phone now runs Marshmallow with Sense7.
Since the rom was filled to brim with useless AT&T crap that does not work outside AT&T network I decided to switch to developer WWE rom but the RUU refused to install on the phone (I have S-Off)
After doing a bit more reading I discovered it was because my new rom has a software number 6.20.502.5 while the RUU I would like to install has a software number of 6.12.1540.4
I googled and googled and searched and searched but could not find a single tutorial to explain how I can replace my current rom with the WWE version which has less bloatware and takes it easy on the RAM.
Can someone kindly explain (or redirect me to a link) of how to downgrade HTC M8 from image version 6.20.502.5 to image version 6.12.1540.4 or in layman's terms how to replace AT&T rom with Developer rom? BTW both roms are Marshmallow. I do not wish to install TWRP or CM so if there is a way besides this I'd be grateful. If not then I don't see any other options and I'd still be grateful
Awaiting your generous replies

What you want is not really a "downgrade" per se. While the AT&T version number is "larger" than the Dev Ed (6.20 versus 6.12), that is mostly just because it came later due to AT&T's slowness in approving the software. I don't think there is much (if anything) that is actually "newer" or "updated" in the AT&T stock ROM (versus Dev Ed). It just has (as you know) all the AT&T branding and bloatware crap.
What is keeping you from flashing the Dev Ed RUU 6.12.1540 is that your carrier ID (CID) needs to match the RUU (even with s-off). Therefore, you need to change your CID to that of the Dev Edition (or alternately SuperCID), which is easy since you already have s-off. You will however need root to do this, so either flash TWRP and SuperSU/Magisk to root, or you can run adb shell with run while booted to TWRP. Either way, you will need to install TWRP: https://forum.xda-developers.com/htc-one-m8/general/change-wwe-m8-to-dev-edition-ota-t2826567
No need to change the Model ID (MID) since the AT&T version and Dev Edition have the same MID.
After that, you should be able to run the Dev Ed RUU.

Sorry .. correction. No need root/twrp to change CID, only change MID need these.
Simply reboot to bootloader/fastboot then run command
To Dev Ed CID
fastboot oem writecid BS_US001
To SuperCID
fastboot oem writecid 11111111
Can't remember if this only can be done on unlocked bootloader. If can't, try this command first
fastboot oem rebootRUU
the follow by the above.
If still can't then need a unlocked bootloader to proceed.

ckpv5 said:
Sorry .. correction. No need root/twrp to change CID, only change MID need these.
Click to expand...
Click to collapse
Ah yes, obviously I was mixing up my methods to change CID versus MID.
Thanks for clarifying, yet again.

Thank you
Many thanks to you gentlemen for your generous assistance and helpful instructions. I really appreciate it. All the best

Update
Good day all:
Sorry to bother again but it failed again! I downloaded fastboot adb and followed the procedure, put the phone in fastboot mode and the CID was already 11111111 and still it refused to accept the RUU. Please find attached a photo of my fastboot screen, hope it can help determine where the problem is on my phone. [ The following errors occurred with your submission:
To prevent spam on the XDA forums, ALL new users prevented from posting outside links in their messages. After approximately 10 posts, you will be able to post outside links. Thank you for understanding!] Site refused to allow me to attach the photo link so I'll just write everything here
*****Software Status - Official******
******LOCKED******** (Even though I can use a non AT&T sim normally)
MS_UL_CA PVT SHIP S-OFF
CID~11111111
HBOOT - 3.19.0.0000
Radio - [email protected](long number)
OPENDSP - v56.2.2. (loooooooong number)
OS-6.20.502.5
eMMC Boot - 2048MB
*end of pic*
On the official HTC site in the support section where they post the RUUs it states the following.
"Before you proceed, please confirm that this software upgrade to 6.12.1540.4 is a newer version than what is currently loaded on your device. If it is the same version, there is no need to reload the software. Navigate to the Home screen then tap All apps > Settings > About and locate the Software information . If your Software number is less than 6.12.1540.4 , you should proceed with the upgrade." end of quote
This paragraph is what let me to believe it is the software version that is stopping me from changing RUUs and why I called this post a downgrade (even though I know it's not)
Can any of you good gentlemen help me out a bit more? I'm willing to answer any questions to further clear the picture of my predicament.
Thank you again

Bootloader is fine, still ATT.
Explain more on the error that you have when you tried installing RUU.
Do note - to run RUU you need PC with USB 2.0;
Latest htc usb drivers which you'll get when you installed latesr htc sync manager (uninstall sync manager but leave all drivers to proceed RUU installation)

ckpv5 said:
Bootloader is fine, still ATT.
Explain more on the error that you have when you tried installing RUU.
Do note - to run RUU you need PC with USB 2.0;
Latest htc usb drivers which you'll get when you installed latesr htc sync manager (uninstall sync manager but leave all drivers to proceed RUU installation)
Click to expand...
Click to collapse
Thank you for your reply:
the RUU I'm trying to install is the developer RUU that I downloaded off the HTC official website. It is the same website I downloaded the AT&T RUU from which installed fine, upgrading the phone's OS from Android 4.4.4 to Android 6.0.
I have several laptops each running a different OS (Windows 7 which I use mostly and have been using for this process) Windows 10, Linux and Solaris.
I did download and install HTC Sync but disabled it's auto run when I noticed every time I plug my phone in it pops up. So that's disabled not uninstalled, but it didn't interfere in the RUU installation of the ATT update and it doesn't pop up when I try to install the developer update.
The Error get is as follows:
Upon running the RUU it does all the necessary checks and then asks me if I would like to install the update, I click on "I Agree" and next, then it puts the phone in boot mode (black screen with HTC written in grey) and after it begins the process by popping up a screen that says: Current info about your Android phone: Image Version: 6.20.502.5 select one below and the update button. After I click on it another screen pops up: Verify that you want to update the Rom version from image version 6.20.502.5 to image version 6.12.1540.4 Clicking on Next another windows shows explaining what happens when I click on Next. When I click next it puts the phone in boot mode and begins by Reading header, sending............................................. then it pops another screen that says update failed and I have to click on recovery and press the power button on my phone for 10 seconds to turn it off

Sir Lucifer said:
On the official HTC site in the support section where they post the RUUs it states the following.
"Before you proceed, please confirm that this software upgrade to 6.12.1540.4 is a newer version than what is currently loaded on your device. If it is the same version, there is no need to reload the software. Navigate to the Home screen then tap All apps > Settings > About and locate the Software information . If your Software number is less than 6.12.1540.4 , you should proceed with the upgrade." end of quote
This paragraph is what let me to believe it is the software version that is stopping me from changing RUUs and why I called this post a downgrade (even though I know it's not)
Click to expand...
Click to collapse
You can't really take the "official" HTC info literally, anymore. By having s-off and SuperCID, you are so far off the "official" path, that most of the rules no longer apply.
S-off bypasses version check (flashing older RUUs is allowed). In fact, you can RUU all the way back to Kitkat if you wanted with s-off (not recommended - just making a point).
---------- Post added at 09:56 AM ---------- Previous post was at 09:52 AM ----------
Sir Lucifer said:
The Error get is as follows:
Upon running the RUU it does all the necessary checks and then asks me if I would like to install the update, I click on "I Agree" and next, then it puts the phone in boot mode (black screen with HTC written in grey) and after it begins the process by popping up a screen that says: Current info about your Android phone: Image Version: 6.20.502.5 select one below and the update button. After I click on it another screen pops up: Verify that you want to update the Rom version from image version 6.20.502.5 to image version 6.12.1540.4 Clicking on Next another windows shows explaining what happens when I click on Next. When I click next it puts the phone in boot mode and begins by Reading header, sending............................................. then it pops another screen that says update failed and I have to click on recovery and press the power button on my phone for 10 seconds to turn it off
Click to expand...
Click to collapse
The RUU stalling out while "sending" is a common bug. Did you simply try running the RUU again? A lot of times, it will work on subsequent attempts.
The fact it got that far, means to me that it passed (or bypassed) any version or CID checks. Otherwise, it never would have gotten to the point of "sending". Instead, it would have told you something like "Error 140" with a description of what the problem was, and aborted the install before ever "sending".

redpoint73 said:
You can't really take the "official" HTC info literally, anymore. By having s-off and SuperCID, you are so far off the "official" path, that most of the rules no longer apply.
S-off bypasses version check (flashing older RUUs is allowed). In fact, you can RUU all the way back to Kitkat if you wanted with s-off (not recommended - just making a point).
---------- Post added at 09:56 AM ---------- Previous post was at 09:52 AM ----------
The RUU stalling out while "sending" is a common bug. Did you simply try running the RUU again? A lot of times, it will work on subsequent attempts.
The fact it got that far, means to me that it passed (or bypassed) any version or CID checks. Otherwise, it never would have gotten to the point of "sending". Instead, it would have told you something like "Error 140" with a description of what the problem was, and aborted the install before ever "sending".
Click to expand...
Click to collapse
Have tried it 5 times already, results are the same. I'm downloading the RUU again, maybe my download was corrupt. Will get back to you later with any results. Thank you for your patience and time. Much appreciated

redpoint73 said:
You can't really take the "official" HTC info literally, anymore. By having s-off and SuperCID, you are so far off the "official" path, that most of the rules no longer apply.
S-off bypasses version check (flashing older RUUs is allowed). In fact, you can RUU all the way back to Kitkat if you wanted with s-off (not recommended - just making a point).
---------- Post added at 09:56 AM ---------- Previous post was at 09:52 AM ----------
The RUU stalling out while "sending" is a common bug. Did you simply try running the RUU again? A lot of times, it will work on subsequent attempts.
The fact it got that far, means to me that it passed (or bypassed) any version or CID checks. Otherwise, it never would have gotten to the point of "sending". Instead, it would have told you something like "Error 140" with a description of what the problem was, and aborted the install before ever "sending".
Click to expand...
Click to collapse
Maybe my downloaded RUU is corrupt, I'll download another time and if it gives me the same problem I'll look for another source. I will keep you posted, thank you very much good man.

RUU Broken on HTC's website
Dear all:
After downloading the developer RUU for the second time and trying to install it again (Marshmallow for those of you who have just joined us) off the HTC support site I failed miserably at changing my firmware using that RUU. After a series of searches on the internet and darknet I came across a post on reddit dot com titled M8 marshmallow RUU from HTC is broken and the article was dated last year. Searching further I found a similar post on a Chinese website that stated the same thing. So in conclusion the developer RUU on HTC's site is damaged as confirmed by a few users/developers on both reddit and the Chinese website.
Sorry for wasting all your time gentlemen. I am very grateful (and very lucky) having assistance from good people like yourselves who have taken from their time to help a complete stranger. Much obliged gentlemen. And thank you all again

Cannot be the RUU is broken.
Another way to do this :
1. Install Dev Edition firmware. You can get the fw_6.12.1540.4.zip from - https://forum.xda-developers.com/showpost.php?p=60218734&postcount=5
2. Instead of using RUU exe, you can use RUU zip (rom.zip) to install RUU. I remember long time ago someone had same problem like you. Asked him to use zip format RUU and it was successful.
I believe there is RUU.zip somewhere on XDA. Can't search now as I'm on mobile.
You can get your own RUU.zip which is actually rom.zip yourself. Just run RUU.exe (no need to connect phone). Once it opens the agreement page, go to %temp% thru your search/run windows menu.
It's better to clear your temp directory first so easy to find 2 newly created folder when you run RUU.exe
The rom.zip is inside one of the folder. Copy that to your desktop.
Then follow this on how to install - https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
There are 3 methods but I prefer the htc_fastboot because easily can see any error if any.
So step 1 firmware & step 2 RUU (rom.zip)

Sir Lucifer said:
Dear all:
After a series of searches on the internet and darknet I came across a post on reddit dot com titled M8 marshmallow RUU from HTC is broken and the article was dated last year. Searching further I found a similar post on a Chinese website that stated the same thing. So in conclusion the developer RUU on HTC's site is damaged as confirmed by a few users/developers on both reddit and the Chinese website.
Click to expand...
Click to collapse
Did those threads specifically mention RUU 6.12.1540.4? If not, then you realize this device has dozens of RUUs for the M8? Most of which have been confirmed many times over to work properly.
My experience, is that 95% of the time, the problem with RUU running is with the PC. Try re-installing HTC drivers, different USB port, turn off USB 3.0. Also try a different USB cable, or if possible another PC.
Downloading the RUU again (as you tried) is not a bad idea. They do sometimes get corrupted while downloading. But if you download another time, and it still fails, the problem is probably not the RUU.
You should also verify your PC has Visual C++ installed, as the RUU exe requires it. The error your are encountering doesn't sound like the C++ problem. But it won't hurt to verify, anyway. Link here, but confirm it's the right install for your Windows version: https://forum.xda-developers.com/showpost.php?p=60021580&postcount=4
Or of course, you can use the RUU.zip method stated by ckpv5, which avoids all the of the above possible pitfalls. You'll need to search for the 6.12.1540.4 zip, as I don't know where it is off hand, either.

Downloaded Again
redpoint73 said:
Did those threads specifically mention RUU 6.12.1540.4? If not, then you realize this device has dozens of RUUs for the M8? Most of which have been confirmed many times over to work properly.
My experience, is that 95% of the time, the problem with RUU running is with the PC. Try re-installing HTC drivers, different USB port, turn off USB 3.0. Also try a different USB cable, or if possible another PC.
Downloading the RUU again (as you tried) is not a bad idea. They do sometimes get corrupted while downloading. But if you download another time, and it still fails, the problem is probably not the RUU.
You should also verify your PC has Visual C++ installed, as the RUU exe requires it. The error your are encountering doesn't sound like the C++ problem. But it won't hurt to verify, anyway. Link here, but confirm it's the right install for your Windows version: https://forum.xda-developers.com/showpost.php?p=60021580&postcount=4
Or of course, you can use the RUU.zip method stated by ckpv5, which avoids all the of the above possible pitfalls. You'll need to search for the 6.12.1540.4 zip, as I don't know where it is off hand, either.
Click to expand...
Click to collapse
I did download the developer RUU again, I also downloaded the Metro PCS RUU which has a software number of 6.20.531.5 and it installed just fine but refused to see the sim card so I reinstalled AT&T
I am an electronics engineer so yes my laptops are always up to date on flash, oracle, C++, Perl, Java, etc

ckpv5 said:
I believe there is RUU.zip somewhere on XDA. Can't search now as I'm on mobile.
Click to expand...
Click to collapse
redpoint73 said:
You'll need to search for the 6.12.1540.4 zip, as I don't know where it is off hand, either.
Click to expand...
Click to collapse
Sir Lucifer said:
I did download the developer RUU again, I also downloaded the Metro PCS RUU which has a software number of 6.20.531.5 and it installed just fine but refused to see the sim card so I reinstalled AT&T
I am an electronics engineer so yes my laptops are always up to date on flash, oracle, C++, Perl, Java, etc
Click to expand...
Click to collapse
I have the RUU.zip
You can download it from here :good:

Sir Lucifer said:
I also downloaded the Metro PCS RUU which has a software number of 6.20.531.5 and it installed just fine but refused to see the sim card so I reinstalled AT&T
Click to expand...
Click to collapse
That is the T-Mobile RUU. MetroPCS merged with T-Mobile, so it's a bit one and the same. But most everyone will call that RUU/version T-Mobile. It will change band support (as flashing any other RUU will). So if it was working before on the AT&T RUU(or Dev ED will support the same bands) I would not mess with random RUUs, unless we suggest them specifically.

CID MID OS differences

Dear friends my phone has following informations from download mode .
cid is matching with US UNLOCKED
mid is matching with TW UNLOCKED
os is 3.16.401.2 afaik belongs to HTC__034 but leedroid rom has been installed.
Im having some troubles with rom and i want to back stock.
In this case which ruu or exe i must install?
Im S-OFF i tried to convert supercid but i got some errors in fastboot command screen.
I will be extreamly appriciated for your helps my friends.

alicine said:
Dear friends my phone has following informations from download mode .
cid is matching with US UNLOCKED
mid is matching with TW UNLOCKED
os is 3.16.401.2 afaik belongs to HTC__034 but leedroid rom has been installed.
Im having some troubles with rom and i want to back stock.
In this case which ruu or exe i must install?
Im S-OFF i tried to convert supercid but i got some errors in fastboot command screen.
I will be extreamly appriciated for your helps my friends.
Click to expand...
Click to collapse
What was error with trying to supercid?
Here's a nice tutorial
https://forum.xda-developers.com/htc-10/how-to/guide-supercid-htc-10-t3374484
You can change mid too so not sure what exactly device it is, but I'm guessing us locked, based on your firmware of 3.16.401.2
I think that is the newest firmware.
I would go ahead and flash that RUU.
https://androidfilehost.com/?fid=673956719939830809
https://forum.xda-developers.com/htc-10/help/waiting-ruu-oreo-europe-t3769317/page5

andybones said:
What was error with trying to supercid?
Here's a nice tutorial
https://forum.xda-developers.com/htc-10/how-to/guide-supercid-htc-10-t3374484
You can change mid too so not sure what exactly device it is, but I'm guessing us locked, based on your firmware of 3.16.401.2
I think that is the newest firmware.
I would go ahead and flash that RUU.
https://androidfilehost.com/?fid=673956719939830809
https://forum.xda-developers.com/htc-10/help/waiting-ruu-oreo-europe-t3769317/page5
Click to expand...
Click to collapse
Thank you very much for your quick answer .
Fastboot was giving me an error "Waiting for device" for all other commands except fastboot devices
i tried in my dekstop computer (win10) i succeed to change MID and CID . and after i flashed the file that you aimed.
This time im having [email protected] and [email protected] i believe this is a hardware failure.
Because non of sensors are working. :crying::crying::crying:

alicine said:
Thank you very much for your quick answer .
Fastboot was giving me an error "Waiting for device" for all other commands except fastboot devices
i tried in my dekstop computer (win10) i succeed to change MID and CID . and after i flashed the file that you aimed.
This time im having [email protected] and [email protected] i believe this is a hardware failure.
Because non of sensors are working. :crying::crying::crying:
Click to expand...
Click to collapse
Were sensors working before?
What did you change cid/mid to?
I would do supercid and change mid to match the RUU which is us locked, 2PS620000 iirc
Hopefully that will fix things up.
I also suggest flashing RUU using sdcard method, but fastboot works fine just make sure to use htc_fastboot not fastboot, for ruu
https://drive.google.com/file/d/0B8L4pkbzdlR3eTlJSjdKVEdHX1U/view
Do a quick search though to confirm that's the mid u want that matches that Ruu.
Sorry I should have mentioned earlier.

When I take the phone first, was having sensor issues. I was thinking it's because of leedroid rom and sensors were driving crazy. Screen was closing itself, ice screen was appearing and back and other button blinking itself home button was not working etc. I barely acces to main screen
*#*#3424#*#* I couldn't diagnose hw so somehow I installed an app to see how sensors were behaving.
I couldn't read values so I thought that it's because of rom.
That's why as you said I change cid to supercid mid to 2PS620000.
After that I used sd card method from download mode and I installed the rom.
After the process I recieved the errors that I mentioned above
As final conclusion when mobile phone has leedroid rom, hw somehow damaged and was working strange because sensors.hub was there.
With clean installation sensor.hub didn't installed and hw is not working. And not behave strange.
It's my theory. I'm searching schematics for sensors to define where is exactly failure is.