RUU failures with S-ON, ATT worked, tmobile/developer failed - One (M9) Q&A, Help & Troubleshooting

Greetings,
My M9 wouldn't let me up update with OTA updates via the normal interface -- it was citing the idea that the system was modified. I bought the (GSM) phone off ebay (in an unlocked state), so anything's possible.
Anyway, I've successfully flashed my phone with one RUUs from this page (and failed to flash with two others):
www dot htc dot com/us/support/rom-downloads.html
I believe the one I have currently installed is the HTC ATT RUU, available as follows. In addition to it being the file I succesfully installed, android reports my software number to be 3.38.502.41. Unfortunately, I have TMobile, and the data isn't working outside of just using the Wi-Fi access point (which happens to be at my home). I may be able to fix that by playing around with APNs (or something along those lines), but I'd rather start with an applicable ROM instead.
dl3 dot htc dot com/application/RUU_HIMA_UL_M60_SENSE70_ATT_MR_Cingular_US_3.38.502.41.exe?_ga=1.133164366.132867555.1482870735
Ideally, I'd like to upgrade the software to the developer version:
dl3 dot htc dot com/application/RUU_HIMA_UL_N70_SENSE80_ATT_MR_NA_Gen_Unlock_4.23.617.1.exe?_ga=1.137291504.132867555.1482870735
But, I may need to settle for the TMobile version:
dl3 dot htc dot com/application/RUU_HIMA_UL_M60_SENSE70_TMUS_MR_TMOUS_3.39.531.41.exe?_ga=1.228975068.132867555.1482870735
When I try to install either of the TMobile or Developer versions, I receive the "Error 132 Signarure [problem]" (I forget the exact wording, but that meaning is accurate. From what I groked in the xda readme thread (thanks for that), it seems I may have the wrong firmware.
Do you know how I can switch the ROM to one of the above two options? My bootloader info is below the signature.
Thanks,
David
HTC Download Mode Info:
htc_himaulatt PVT S-ON
LK-1.0.0.0000
RADIO-01.01_U11440801_96.01.51207A_F
OpenDSP-15.6.1.00522.8994_1026
OS-3.38.502.41
Nov 2 2016,21:10:37(682052)

You need S-OFF if you want to convert your phone to a different version. With S-ON you have no choice and need to stick with AT&T RUUs. A conversion guide can be found in the ReadMe thread.
Aside from that, you can't flash a 4.x RUU on a phone with firmware 3.x. HTC changed its encryption keys between those two firmware versions. More information about RUUs can be found in the ReadMe thread, as well.

Uh oh, per what you said, I tried sunshine, but to no avail. Will keep researching. Thanks!

To close out this thread, I was able to get my phone working by setting up the APNs for TMobile. Two relevant pages for that.
US-APN:
support dot t-mobile dot com/docs/DOC-2090#subhead1
International APN for when traveling (I'm guessing I'll need this):
support dot t-mobile dot com/docs/DOC-16171
For the sake of completeness and search engines, I'll state what I would have needed to do, had that not worked. Thanks to @autoprime, @beaups, and @Flippy498 for the help.
(0) Attempt to install sunshine -- this didn't work, because I didn't have root enabled in my rom, so I have to do (1)-(4)
(1) unlock bootloader -- go to htcdev dot com
(2) twrp
(3) supersu
(4) sunshine
(5) follow steps to change cid
(6) maybe relock bootloader (this is dangerous -- see the readme)
(7) install the tmobile or dev image (based on which cid I used in (5))

Related

can't flash ROM or update

I recently got my hands on a One M9 but I'm having trouble updating anything on it. I check for updates and it says there aren't any available. However, my software version is 1.14.531.1, which is older than anything I've seen in any threads anywhere.
Here's the readout from fastboot getvar all:
kernel: lk
product: htc_himaul
version: 1.0
vzwisLTE:
vzwmid: HTC
max-download-size: 800000000
imei:
battery-status: good
version-main: 1.14.531.1
boot-mode: download
version-bootloader: 1.0.0.0000
mid: 0PJA12000
cid: 11111111
It doesn't say it here, but the phone is s-off.
I started by following the instructions at Cyanogenmod: unlocked, installed TWRP, installed ROM. However, it wouldn't install the ROM. It failed at the point where it tries to verify the device. I changed the recovery to the Cyanogenmod recovery and tried again, but that didn't work either. After a bit of reading, I thought that perhaps I needed to update the bootloader and that a RUU update might do the trick. I got the most recent one from HTC and ran it. It stalled where it says "sending" at 0%. I put the ROM.zip on the SD card to try it that way. That also failed. I relocked the bootloader and tried the RUU again with the same result.
I've wondered if I need to update the firmware per this thread http://forum.xda-developers.com/one-m9/development/firmware-t3068243 but I'm still new to the HTC world and not sure if that's it or if I'm just guessing. The firmware files I found there are much smaller than I expected, so I'm not sure what exactly they will update or if they'll fix the problem or just make it worse.
Can anyone tell me where to go from here, or at least point me in the right direction?
You can't flash offical firmwares unless your phone is stock. I think you should be ok flashing unsigned zips though. I couldn't tell you if htc do incremental or if you can just flash the latest. Flippy's thread might shine a light on something.. Your Cid is supercid.
Beamed in by telepathy.
So, are you saying that if I go back to the stock recovery that I should be able to use the RUU to update everything? There are a bunch of stock recoveries here, but none of them match my phone. The oldest ones there are several versions newer than mine and none match my CID. Can I still use one of them or do I need to find one that matches my phone exactly?
When I got the phone there was an SD card in it with a 0PJAIMG.zip file and a text file with a very long name with the software version (1.14.531.1) in it. Fortunately I saved them. I put those files back on and tried flashing that 0PJAIMG file and this time it worked. It seems to have removed the recovery I put on it and now it looks completely stock, with a locked bootloader and everything. Updating with the latest RUU still doesn't seem to work, however. It's still stalled at "sending" and 0%.
I would like to try a different RUU that's a smaller jump, but I haven't had any luck finding one yet.
OTA updates are incremental. A RUU on the other hand contains the whole firmware that has been distributed for its SKU until the point that RUU got released. Besides it contains the whole system. That's why RUUs are so big.
Sneakyghost's files lack some parts of the official firmware packs since they're not meant to get flashed if you want to get back to stock. They're meant to get flashed if you want to update your phone's firmware without reverting it's system back to stock since this way is less time consuming if you want to flash a new custom rom afterwards. That's why they're so much smaller than a RUU. Besides, they're unsigned and you won't be able to use them without S-OFF.
I personally don't like the *.exe versions of RUUs since they use fastboot and many users aren't able to set up their adb/fastboot environment correctly. Therefore, I neither support flashing RUU.exe files nor fastboot flashing of RUU.zip files. However if you extract the RUU.zip from the latest x.xx.531.x RUU.exe you could flash it via a SD card. I don't have a direct link to a guide for the extraction at the moment but there should be several here on xda which you should be able to find via google. It doesn't matter if they're written for an older HTC phone since the steps you need to do are always the same. Instructions for flashing a RUU via SD card can be found in my google sheet (which is linked in my signature).
And one last thing: The SCID prevents the M9 from installing OTAs. Therefore, you should revert it back to its original CID if you want to install any OTA.
Personal opinion: Since you can't use RUUs with a different MID than the one of your phone although you use the SCID (that was possible on older HTC phones) and you aren't able to install OTAs if you use it (that was possible on older phones, too) I personally don't think that there is any benefit left in using it.
Edit: I forgot to mention that there is a dedicated forum for the T-Mobile US M9 here on xda which can be found with the xda search function. You might find the files you need over there. Due to that other forum the T-Mobile US variant of the M9 isn't that much supported here in the forum for the international variant.
Sent from my HTC One S using XDA Labs
Thanks for the info on the T mobile forum. I wasn't aware of that and thought this was the only forum for the M9 here. I'll look for it.
I've already tried using the SD card method and that also failed.
I haven't changed the CID. It was the superCID when I got it. I don't think the previous owner changed it either because the phone seems unused. It still has the barcode sticker on the back and it's clearly be barely handled at all. The phone was originally a test unit or something because it has a serial number engraved on the front and it runs some HTC reporting software. It's rooted out of the box. I'm trying to replace the ROM to get rid of that extra software. I just mention that to explain why it's already rooted, s-off and superCID.
drfarmkid said:
Thanks for the info on the T mobile forum. I wasn't aware of that and thought this was the only forum for the M9 here. I'll look for it.
I've already tried using the SD card method and that also failed.
I haven't changed the CID. It was the superCID when I got it. I don't think the previous owner changed it either because the phone seems unused. It still has the barcode sticker on the back and it's clearly be barely handled at all. The phone was originally a test unit or something because it has a serial number engraved on the front and it runs some HTC reporting software. It's rooted out of the box. I'm trying to replace the ROM to get rid of that extra software. I just mention that to explain why it's already rooted, s-off and superCID.
Click to expand...
Click to collapse
I would say the phone is modified. As far as I know, test units don't need S-OFF or the SCID since they simply use different firmware versions than normal units. You can change every version of the M9 into a test unit by applying for HTCs beta program.
What was the error that got shown when the SD card method failed? Did you try to flash the correct RUU.zip for your phone? As mentioned before your MID needs to match even if the phone has the SCID. Therefore, you can only use x.xx.531.x RUUs.
Edit: I forgot to mention that every S-OFFed device runs that reporting software you mentioned if that device is running the stock rom. That Software gets triggered by the S-OFF flag.
Sent from my HTC One S using XDA Labs
Well, I managed to find the 1.32.531.33 RUU in the forum for the T-mobile variant (thanks flippy498 for bringing it to my attention) and that ran just fine. Once that was done I tried running the RUU I downloaded earlier from HTC (3.39.531.31) and it worked fine. It seems the problem was indeed that I just needed something that was a smaller jump. I've seen no mention of any software version earlier than 1.32 anywhere in this forum, so I wonder if my phone was an early test unit or something that the version 1.14 mine had was an earlier pre-release version or something and that is why I had the problems I did.
Thanks for the info regarding the reporting software running on all s-off phones. I saw something about red text in other threads and wondered if that's what it referred to. Now I know.

HTC One M9 stuck in Flight Mode after Nougat OTA

Hey there,
I own a HTC One M9 with Stock ROM, not rooted, nothing modified. Recently I got the Nougat OTA update as a notification (don't know why not earlier...).
It did update without any problems, but after it, it occured to me that it didn't get any signal. WiFi, bluetooth and everything else works fine, it even recognizes my SIM card.
In the settings, the "flight mode" is grey and permanently "setting off" and I can't set it on or off.
(But strangely, if I hold the power button, it says "airplane mode off", same within the status bar/quick settings.)
I don't know much about flashing etc (nearliy nothing), but I read as most threads which seemed to be similar as I could. Even if some people had the problem with the One X and M8, I couldn't find a solution for me...
I rebootet the phone several times, did the "battery pull out simulation" with power and volume keys, did a factory reset in the settings, wiped cache partition within the recovery mode. Even tried booting in safe mode and a factory reset within the recovery mode.
Nothing works, the airplane mode is still stuck at "setting off" and I don't get any cell phone signal or mobile internet.
Phone /software information:
- Model: HTC One M9; OPJA100
- Not rooted
- "LOCKED"
- htc_hiauhl PVT S-ON
- Software status: Official
- Android-Version: 7.0
- Software-Version: 4.18.111.2
- OpenDSP-20.7.3.00545.8994_1012
- Kernel-Version: 3.10.84-perf-ga97f624
[email protected] #1
SP PREEMPT
- Android safety-patch: 01. Nov. 2016
-Baseband-Version: 01.01_U114401011_117.00.61117G_2_F
- Build-Nr.: 4.18.111.2 CL839204 release-keys
I hope, that it will be fixed, if I flash the Stock ROM myself, but I didn't find one with the same software-version and do not know how to do this.
Any suggestions, what could be wrong and how I manage to fix it?
Thank you all for your help!
Flashing instrtructions can be found in the ReadMe thread. The catch is that no one contributed a RUU or a TWRP backup for your current firmware version, yet.
Therefore, I only see the following solutions at the moment (which all aren't available for free - sorry):
Getting S-OFF and flashing the 3.x RUU for your SKU. (Infos are located in the ReadMe thread.)
Contacting Llabtoofer's RUU service. (A link can be found in the further reading section of the ReadMe thread.)
Searching on sites like ir-file or easy-firmware for the needed RUU. (If you choose this option you'll need your phone's codename which is HIMA_UHL.)
I was able to unlock the Bootloader, flashed TWRP, got S-OFF (didn't get Root, but I don't know why...tried several SuperSU versions...) and changed the CID to be able to flash RUUs without the T-Mobile branding.
But I'm not sure which RUU I can use for flashing with a SD card.
Those I found were only 3.xx with SKU "111", but the actual version is 4.xx.
I thought with S-OFF I would be able to flash early every RUU?
Can someone explain this to me and give me an advice which RUU (preferably a non-branded Nougat one) I can flash and where to get it?
Thank you all in advance for you help!
As written in my last post, no one contributed 4.x files for your SKU, yet.
All needed information and files should be available in the ReadMe thread. There's a conversion guide, the RUU section contains all infos you might need in regard to RUUs and the further reading section contains a link to a spreadsheet with with all SKUs and their meanings.
Sent from my HTC One M9 using XDA Labs
Thanks again!
I did read those threads, but got a bit confused afterwards... :/
E .g. easy-firmware has a RUU 4.xxx with SKU "111", and as I understood, I can also use free 4.xxx RUUs with SKU "401", because I got S-OFF and changed the CID?
Sorry to bother
That's correct. You can use 401 RUUs thanks to S-OFF, now.
The catch with ir-file and easy-firmware is that their files aren't available for free. Most RUUs in the ReadMe thread got bought on one of those sites in the past.
Since you already paid for S-OFF I'd suggest you to not pay once more. Either convert to SKU 401 or use the infos in the RUU section of the ReadMe thread for flashing the 3.x RUU for your current SKU.
Sent from my HTC One M9 using XDA Labs
Now I got it, thank you!
I tried flashing it with a RUU_4.28.401.3 (worked on the second try, first one didn't find the file).
Flashing worked without problems (checked the phone info), but it's still stuck in the flight mode.
No changes there... :crying:
Is there a chance, that it's still a software issue, maybe with Nougat itself?
Or do I have to "bury" it, because sending to be repaired isn't worth it's value?
If it was a general Nougat problem on the M9 then there would be more threads like this one... Sorry, that I can't provide better news.
Sent from my HTC One M9 using XDA Labs

Cant update from: 3.35.617.31, Getting errors with RUU, Cant OTA

Hello,
I have bought HTC One M9 off Aliexpress.
I bought it as developer version. When it came I started OTA upgrade. It downloads and then it says update cannot be performed because of modified system.
I cant even use RUU to get it working, I receive error 132. While chatting to HTC support their run my IMEI by their system. It came back as T-Mobile (US) version. Even though on back of my phone is engraved -
Model: OPJA110 which should mean it is developer version.
On my download mode it states: S-on, official system and locked bootloader.
Can anyone give me some tips how to get the newest system installed?
I have been trying for past 2 days without any luck to figure it out.
Any help is appreciate.
EDIT: Forgot CID:11111111 MID: 0PJA11000
Thank you very much.
Please read the ReadMe thread. It'll explain the causes of your issues and contains the needed files and instructions for fixing it. (C.f. the conversion guide, the RUU and the OTA section)
The most important infos: OTAs aren't installable while the phone is using the SuperCID and firmware 4.x RUUs aren't flashable on phones with firmware 3.x or lower due to new encryption keys.
Sent from my HTC One M9 using XDA Labs
Thanks for your time.
Flippy498 said:
Please read the ReadMe thread. It'll explain the causes of your issues and contains the needed files and instructions for fixing it. (C.f. the conversion guide, the RUU and the OTA section)
The most important infos: OTAs aren't installable while the phone is using the SuperCID and firmware 4.x RUUs aren't flashable on phones with firmware 3.x or lower due to new encryption keys.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
I have read ReadMe.
So that means I need to S-OFF my phone using SunShine (other oprions?)
Then changing CID to BS_US001 (because Im running .617. system)
Then I can flash RUU (3.35.617.31)
And after that I can use OTA updates?
Do I need to unlock bootloader through HTCdev or is enough to check OEM Unlocking under developer options?
Thank you again for your time.
Oh, I missed that you're S-ON. Follow the unlocking/rooting guide in the same thread.
If you're lucky the previous owner used Sunshine, as well, so that you don't have to pay, again. (The license is saved on their servers and gets linked to the device.) The alternatives to Sunshine are a Java card, an XTC clip or similar tools which are way more expensive.
It doesn't matter which of the CIDs that belong to SKU 617 you use. They both work fine.
Alternatively, you could send the device back to the seller and ask for a refund. He obviously modified the phone and didn't restore the phone to a stock state properly before he sold it. The phone definetly was S-OFF in the past since no HTC phone gets shipped with the SuperCID. And if the IMEI belongs to a T-Mobile M9 according to HTC then the MID got changed with the help of S-OFF, as well. The backside can actually get replaced, too, if you know how to do it.
After you restored a CID that corresponds to your SKU you should be able to receive OTAs, again. Just for safety reasons I'd flash a 3.x RUU, as well, if I were you. The differences between the GSM versions of the M9 are so minor that you can convert the phone from one version to another. Therefore, you don't need to use the T-Mobile firmware and can stick with the dev one if you want.
Flippy498 said:
Oh, I missed that you're S-ON. Follow the unlocking/rooting guide in the same thread.
If you're lucky the previous owner used Sunshine, as well, so that you don't have to pay, again. (The license is saved on their servers and gets linked to the device.)
It doesn't matter which of the CIDs that belong to SKU 617 you use. They both work fine.
Alternatively, you could send the device back to the seller and ask for a refund. He obviously modified the phone and didn't restore the phone to a stock state properly before he sold it. The phone definetly was S-OFF in the past since no HTC phone gets shipped with the SuperCID. And if the IMEI belongs to a T-Mobile M9 according to HTC then the MID got changed with the help of S-OFF, as well. The backside can actually get replaced, too, if you know how to do it.
After you restored a CID that corresponds to your SKU you should be able to receive OTAs, again. Just for safety reasons I'd flash a 3.x RUU, as well, if I were you. The differences between the GSM versions of the M9 are so minor that you can convert the phone from one version to another. Therefore, you don't need to use the T-Mobile firmware and can stick with the dev one if you want.
Click to expand...
Click to collapse
Ok, Im gona pay that 25 bucks, it doesnt really matter.
So, I should start with unlocking bootloader via HTCdev.
After that I need to use SunShine.
Changing CID.
Flashing 3.x RUU.
And then doing OTA.
Is that all correct?
And should I install TWRP or stay on stock recovery after unlocking bootloader?
Really appreciate your time.
Correct.
Just follow the guides in the ReadMe thread starting from this post till the end of the conversion guide. (Theoretically, you can skip the backup part and save some time since you should be able to use the 3.x RUU even with the SuperCID on your phone.)
Flippy498 said:
Correct.
Just follow the guides in the ReadMe thread starting from this post till the end of the conversion guide. (Theoretically, you can skip the backup part and save some time since you should be able to use the 3.x RUU even with the SuperCID on your phone.)
Click to expand...
Click to collapse
Thanks,
is there a point in TWRP backup? Wont it stop OTA updates? On my other phone (Ulefone Metal) It is not possible to get OTA with custom recovery.
It actually is possible on the M9 and newer HTC phones as long as the system partition doesn't get modified, beforehand. (Further info can be found in the OTA section of the ReadMe thread.)
However, flashing a RUU restores everything on the phone back to stock (including the recovery). That's why I suggested flashing one after changing the CID.
Sent from my HTC One M9 using XDA Labs
Flippy498 said:
It actually is possible on the M9 and newer HTC phones as long as the system partition doesn't get modified, beforehand. (Further info can be found in the OTA section of the ReadMe thread.)
However, flashing a RUU restores everything on the phone back to stock (including the recovery). That's why I suggested flashing one after changing the CID.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
Thank you, I did as I said.
After flashing 3.x RUU OTA was successful.
That updated my system to: 4.16.617.6.
After that I continued by flashing latest RUU (4.30.617.12).
Everything went well. Until this point. When I booted the device I got to choose language. But there are just few (20 or so) available.
Unfortunately no Czech which I want. On previous version (4.16.617.6) there was huge list to choose from, including Czech.
Im still using 617 edition.
Where is the problem? Is here a way to get Czech lang. working again?
One again thank you for your time and effort
HTC probably removed the languages from the selection. Don't ask me why. I have no clue.
You could try setting up the phone in English and then switching to Czech via the app MoreLocal2. There's a thread about the app somewhere hidden on xda (sorry, I don't have a direct link at hand). You should be able to find it via google.
Sent from my HTC One M9 using XDA Labs

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.

S-OFF, Bootloader locked - need help to get OTA updates

Hi folks, I've read the Flippy498's M9 ReadMe thread and understand most of it but still need a helping hand from you more experienced folk in order to update the software on the M9.
I bought a "like new" M9 a few months ago from a seller somewhere in Asia (Hong Kong I think). I know, bad idea, but I had a tight budget. The phone has lollipop - I've been happily using it in the UK but now a few apps I need won't install (apps to access work email etc. since lollipop isn't supported by these apps).
I know the phone has been tinkered with (S-OFF and supercid) - but I'm not sure why (to unlock?). I get an OTA update notification, but it won't apply (see screenshot). I've included a couple more informational screenshots below.
Bootloader locked, S-OFF
0PJA100 (this is written on the back of the phone as well - no reason to believe it's a frankenphone)
htc_himulatt PVT S-OFF
CID-11111111
LK-1.0.0.0000
RADIO-01.01_XXX
OpenDSP-XXX
OS-2.11.617.258
My situation might be similar to these folks, neither of who had any luck:
https://forum.xda-developers.com/one-m9/help/unlock-bootloader-android-6-0-software-t3741019
https://androidforums.com/threads/phone-wont-update.1157270/
I don't want root (banking apps fail). I might be wrong, but I think my work apps won't function with TWRP - rather not chance it.
I'd like to update the phone's software as simply as possible. (Note that the Ebay listing said that they recommend I do not update - not sure why)
Questions:
I'm aware that the CID is incorrect. If I change it to something else (what?) - will the update work? If so this seems to be the simplest method.
Is this a CDMA phone?
Is it possible that the phone becomes locked after updating? Right now I can use it in the UK and 4G works.
Would you recommend some other method? Like changing the CID and flashing an RUU (which one will work? I'm aware that version numbers need to match.)
The phone seems to default to Canadian English - not a big deal - would I be better converting it to another edition?
Thank you very much for any help/advice you can offer. I've rooted, installed custom recoveries and flashed loads of ROMS (on an S3 - nothing as complicated as the M9). If any further information is required I will provide this ASAP.
You didn't buy a CDMA device and your issue isn't similar to the ones you linked.
At the moment, there are two problems that are preventing your phone from being able to install OTAs:
You're using the SCID (11111111). Unlike on previous HTC models, OTAs will abort when they notice this CID.
Your current firmware doesn't match the system version you're using. The firmware that is shown in download mode belongs to the developer edition (SKU 617). The OTA on the other hand belongs to the Canadian Telus version (SKU 661). OTAs will abort if they notice such a mismatch as seen on the pic that shows your phone's stock recovery.
In addition to that, the firmware with SKU 617 actually belongs to the 0PJA11000 (hima_ulatt - a US model) while you own the 0PJA10000 (hima_uhl - the International model) according to the engraving on its backside. Since both are GSM versions and the differences are almost non-existent, cross-flashing is absolutely no problem, though.
I'd recommend you to follow the conversion guide that can be found in the ReadMe thread. Use one of the European RUUs that share the same decryption keys as your current firmware. (In other words a 2.x or a 3.x RUU for SKU 401.) Due to problem 2 you won't be able to solve your issue just by changing the CID. You'll need to flash a RUU for fixing that.
Since SKU 401 belongs to the unbranded European firmware you don't have to fear a sim lock or something similar.
Flippy498 said:
You didn't buy a CDMA device and your issue isn't similar to the ones you linked.
At the moment, there are two problems that are preventing your phone from being able to install OTAs:
You're using the SCID (11111111). Unlike on previous HTC models, OTAs will abort when they notice this CID.
Your current firmware doesn't match the system version you're using. The firmware that is shown in download mode belongs to the developer edition (SKU 617). The OTA on the other hand belongs to the Canadian Telus version (SKU 661). OTAs will abort if they notice such a mismatch as seen on the pic that shows your phone's stock recovery.
In addition to that, the firmware with SKU 617 actually belongs to the 0PJA11000 (hima_ulatt - a US model) while you own the 0PJA10000 (hima_uhl - the International model) according to the engraving on its backside. Since both are GSM versions and the differences are almost non-existent, cross-flashing is absolutely no problem, though.
I'd recommend you to follow the conversion guide that can be found in the ReadMe thread. Use one of the European RUUs that share the same decryption keys as your current firmware. (In other words a 2.x or a 3.x RUU for SKU 401.) Due to problem 2 you won't be able to solve your issue just by changing the CID. You'll need to flash a RUU for fixing that.
Since SKU 401 belongs to the unbranded European firmware you don't have to fear a sim lock or something similar.
Click to expand...
Click to collapse
Thank you Flippy498 - that's just the type of clarification I was looking for! I'll follow your instructions and let you know how I get on. (It might be a few days before I get the block of time I need to do this properly, but I will certainly feed back.) Thanks again.
Hi Flippy498 - just thought I'd check in and let you know how I got on. I followed your instructions exactly and everything is sorted now - I have a fully updated stock M9.
In the unlikely event anyone else finds themselves in this particular situation, and for reference - here are the steps I followed:
Installed a fully functional adb/fastboot environment as per the ReadMe section "Setting up ADB/Fastboot/HTC_Fastboot correctly".
Changed the CID and MID (as outlined here "How to convert your M9 to a different version": https://forum.xda-developers.com/showthread.php?p=71421945#post71421945). For reference the CID I used was HTC__001, the MID was 0PJA10000.
Used the 2.10.401.1 RUU (https://www.androidfilehost.com/?fid=24269982087011324)
Used the SD card method outlined in the ReadMe section titled "RUU Section"
Flash went perfectly. OTA updates all came through as expected. Job done!
Thank you very much Flippy498 - your explanation was crucial to allaying my fears of bricking the device, and giving me the confidence to go through with it. :good:
r2mahara said:
Hi Flippy498 - just thought I'd check in and let you know how I got on. I followed your instructions exactly and everything is sorted now - I have a fully updated stock M9.
In the unlikely event anyone else finds themselves in this particular situation, and for reference - here are the steps I followed:
Installed a fully functional adb/fastboot environment as per the ReadMe section "Setting up ADB/Fastboot/HTC_Fastboot correctly".
Changed the CID and MID (as outlined here "How to convert your M9 to a different version": https://forum.xda-developers.com/showthread.php?p=71421945#post71421945). For reference the CID I used was HTC__001, the MID was 0PJA10000.
Used the 2.10.401.1 RUU (https://www.androidfilehost.com/?fid=24269982087011324)
Used the SD card method outlined in the ReadMe section titled "RUU Section"
Flash went perfectly. OTA updates all came through as expected. Job done!
Thank you very much Flippy498 - your explanation was crucial to allaying my fears of bricking the device, and giving me the confidence to go through with it. :good:
Click to expand...
Click to collapse
This description was very uselfull to me, this summer (July 2021) I purchased 2 brand new HTC One M9 in Sealed packages from a Danish auction house, they was both european phones, but both of them had the folloving configuration:
Locked bootloader
S-ON
Developer version 3.35.617.12
Supercid 11111111
MID 0PJA11000
I need firmware 4.x in order to use the latest Android 11 version of one of the following: crDroid, LineageOS or Ice Cold Project.
I could have lived with the developer version but the super CID 11111111 prevented me from getting to version 4.x
I did the following.
1) For the first phone I registered with HTC developer site in order to get the code to unlock the phone, later on I learned the Sunshine app also unlock the phone, much easier Also I did not need to root the phone because Sunshine App did that temporary, for 25$ this app did some very dificult stuff for me in an rather easy way.
2) From the RUU section I downloaded and flashed 3.35.617.31 on the first phone (still with S-ON) using the SD card method, because there was an OTA file that could bring me to 4.14.617.6, but the update complained about the Super CID 11111111, there was no way around it, I had to use Sunshine app.
3) The first phone I S-OFF'ed with Sunshine locked at the white HTC boot screen, I was unable to power it down, I reached out to support and they adviced med to power the device down by pressing all 3 keys VOL Up/Down and power for 60 seconds and then uninstall Sunshine app, reboot the phone and install it again, then everything went as expected.
4) Now I wanted to get to a 3.x version that will allow me to change to 4.x via OTA file
4a) for both phones I used the SD Card method
4b) for the first phone I had already flashed 3.35.617.31, now I changed the CID to BS_US001
4c) the other phone I changed to H3G__G04, MID to 0PJA10000, and flashed 3.35.771.12
5) Now I was reddy to get to 4.x version
5a) For the phone with version 3.35.617.31 I loaded the OTA file from SD Card to 4.14.617.6, after that I changed the MID to 0PJA10000 and the CID to HTC__001 and flashed a european RUU 4.28.401.3
5b) For the phone with version 3.35.771.12 I loaded the OTA file from SD Card to version 4.30.771.2
5c) For both OTA files I experienced that the script stopped at the last line before completion, I had to power off and run the OTA file once more, where both cases completed as expected.
6) now I have two phones that are ready to go to Android 11, I expect that I wil leave the one with version 4.30.771.12 with the original latest HTC version and keep it as a spare phone, the other one I will use to load Android 11 and Gapps
I hope the can be usefull to someone else in a similar situation.

Categories

Resources