Htc One M8 back to stock UK - One (M8) Q&A, Help & Troubleshooting

not sure what ruu file to get, so here are my settings if someone could post one that will work for me, my phone is from UK but i live in canada and my phone is unlocked

Since the phone is SuperCID, I think you can use most any M8 RUU (exceptions would be CDMA M8, dual SIM, etc.). One possibility is the Euro MM RUU here: http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Oddly, the phone was apparently made s-on after SupCID (which requires s-off). So lower version number RUUs than the presently installed firmware are not allowed (no "downgrading"). But that is probably not too relevant, as most folks want to either stay on the present version, or flash a newer one.
Also, do yourself a favor and stop using the toolkit. Especially for something as easy as fastboot getvar all. The toolkit is obsolete (almost 2 years old), and the outdated components can cause a lot of issues. I can see from your missing main version, that you probably used the outdated TWRP version included with the toolkit (as newer TWRP builds don't typically have this bug).
Also, you should obscure the IMEI and serial numbers on your screenshot. These are personal data, that should never be posted online.

the ruu link in tht post doesnt work its expired

Xtenchen said:
the ruu link in tht post doesnt work its expired
Click to expand...
Click to collapse
the link works as it should
works for me now
Sent from my HTC M8 using XDA Labs

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 on Bluegrass Cellular

Back in August, I got a HTC One M9 from Bluegrass Cellular. (The phone came with Android 5.1) I decided to root it and try a custom ROM. I downloaded a snapshot for CM13 himawl. (Since that's the variant according to Download mode) I flashed it in TWRP only to get an error about sbl1. I since found an unofficial nightly of cm12.1 himawl built on November 17, 2015. It flashed and works fine to this day, but I'd like to have newer features and better security. How would I go about doing this? I can't seem to find the correct RUU. I tried the unlocked RUU to see if it would work, but it was to no avail. I'm S-on if that helps.
purplekid97 said:
Back in August, I got a HTC One M9 from Bluegrass Cellular. (The phone came with Android 5.1) I decided to root it and try a custom ROM. I downloaded a snapshot for CM13 himawl. (Since that's the variant according to Download mode) I flashed it in TWRP only to get an error about sbl1. I since found an unofficial nightly of cm12.1 himawl built on November 17, 2015. It flashed and works fine to this day, but I'd like to have newer features and better security. How would I go about doing this? I can't seem to find the correct RUU. I tried the unlocked RUU to see if it would work, but it was to no avail. I'm S-on if that helps.
Click to expand...
Click to collapse
I'm pretty sure that in order to use a Marshmallow-based ROM (ie, CM 13), you need the Marshmallow firmware first. I imagine the same will be true for Nougat ROMs....though I don't think we've got anything beyond stock just yet.
I imagine that if you were able to achieve S-OFF on your phone, you could apply the appropriate RUU to get you up to the latest available firmware for your phone. To be clear, I don't know what that is (I'm not familiar with the himawl models) - but it should be possible.
computerslayer said:
I'm pretty sure that in order to use a Marshmallow-based ROM (ie, CM 13), you need the Marshmallow firmware first. I imagine the same will be true for Nougat ROMs....though I don't think we've got anything beyond stock just yet.
I imagine that if you were able to achieve S-OFF on your phone, you could apply the appropriate RUU to get you up to the latest available firmware for your phone. To be clear, I don't know what that is (I'm not familiar with the himawl models) - but it should be possible.
Click to expand...
Click to collapse
I believe that's what's going on here. I'm just trying to see if there are any alternatives or RUU's known to work with my s-on phone before I resort to the $25 investment of Sunshine.
purplekid97 said:
I believe that's what's going on here. I'm just trying to see if there are any alternatives or RUU's known to work with my s-on phone before I resort to the $25 investment of Sunshine.
Click to expand...
Click to collapse
Just for the fact you get an extra chance to unbrick if it goes wrong is worth the $25. IMO S-OFF is a necessity for htc phones.
Beamed in by telepathy.
I tried the test in the Sunshine app, but it said to flash stock or near stock rom. I mistakenly didn't backup my stock ROM before flashing cm12.1. Anyone know a ROM I could flash to s off?
purplekid97 said:
I tried the test in the Sunshine app, but it said to flash stock or near stock rom. I mistakenly didn't backup my stock ROM before flashing cm12.1. Anyone know a ROM I could flash to s off?
Click to expand...
Click to collapse
You're on Android 5, right? Android Revolution HD 14, which is built off of stock Android 5.1.0, should do the trick.
Very important sidenote: Don't change the MID/CID or the firmware of this device! It's a CDMA one and therefore not compatible with the GSM firmwares like the dev edition or the WWE one. Otherwise you'll end up with a fancy new paperweight. Just stay with the SKU (the three numbers between the second and the third dot in the firmware version) it is currently using since not even the different CDMA firmwares/devices are compatible with each other.
Sent from my HTC One M9 using XDA Labs
Flippy498 said:
Very important sidenote: Don't change the MID/CID or the firmware of this device! It's a CDMA one and therefore not compatible with the GSM firmwares like the dev edition or the WWE one. Otherwise you'll end up with a fancy new paperweight. Just stay with the SKU (the three numbers between the second and the third dot in the firmware version) it is currently using since not even the different CDMA firmwares/devices are compatible with each other.
Click to expand...
Click to collapse
In my case, the SKU is 605. Is there a newer 605 I can update to access Marshmallow? I recall when I was stock, I tried to update to MM through OTA in settings, but apparently my carrier never approved the update. 5.1 appeared to be the "latest."
605 is the verizon-branded firmware. There definitely is an android m update for your phone.
Sent from my HTC One M9 using XDA Labs
Flippy498 said:
605 is the verizon-branded firmware. There definitely is an android m update for your phone.
Click to expand...
Click to collapse
Awesome! With my CID being LRA__001 would I be able to flash this?
0PJAIMG_HIMA_WL_M60_SENSE70_VZW_MR_VERIZON_WWE_3.3 [email protected]_CNV_1.26_002 _release_469809_signed_1 zip
The problem is it looks like it's WWE which you said wouldn't work.
purplekid97 said:
Awesome! With my CID being LRA__001 would I be able to flash this?
0PJAIMG_HIMA_WL_M60_SENSE70_VZW_MR_VERIZON_WWE_3.3 [email protected]_CNV_1.26_002 _release_469809_signed_1 zip
The problem is it looks like it's WWE which you said wouldn't work.
Click to expand...
Click to collapse
It's Verizon WWE. That's not the same as sku 401 (WWE).
Either you try that one or you download the exe from the HTC US website.
I can't say for sure whether it'll work. According to the sku the RUU should be flashable. You'll need to try by yourself. An alternative would be contacting llabtoofer's RUU service. However that one isn't for free. (Either search for it via google or use the direct link in my google sheet if you want to use that service.)
Sent from my HTC One M9 using XDA Labs
here's your RUU
KhurshidAbbas said:
I mistakenly flashed verizon firmware and now I've lost the network signals, My phone is currently in boot loop, restarting at it's own, I can't use open Mobile Networks App, My networks are not working at all, Some expert told me it's because I flashed wrong Radio.img along with rest of firmware.
Please provide me with stock firmware for Bluegrass Cellular.
I've lost every hope.
Click to expand...
Click to collapse
Source:
https://forum.xda-developers.com/one-m9/general/stock-nand-backup-ota-update-collection-t3132698
Download:
https://www.androidfilehost.com/?fid=24591023225177985
Flippy498 did all the work. I just did some searching
rename to 0PJAIMG.zip place on sd card and reboot should fix it
Again its Flippy498's work

Mobile data not available (disconnected)

Hi. I have a M9 with model id 0PJA100. I bought it unlocked and s-off. One day, I flashed this rom named ICE with android nougat. After that, I cannot use my mobile data. I installed back stock rom to this phone and it is still the same. I can answer call and sms but I cannot get any mobile data. Today, I flashed Viper M9 v6 (nougat) and during the setup, I got H+ signal only for a few second and then it dissapeared. I dont really understand the problem and managed to install a lot of rom before. If anyone have any idea that can possibly make this device working, please reply to this thread. I hate to use my 5s as daily driver.
abdinsyakirin said:
Hi. I have a M9 with model id 0PJA100. I bought it unlocked and s-off. One day, I flashed this rom named ICE with android nougat. After that, I cannot use my mobile data. I installed back stock rom to this phone and it is still the same. I can answer call and sms but I cannot get any mobile data. Today, I flashed Viper M9 v6 (nougat) and during the setup, I got H+ signal only for a few second and then it dissapeared. I dont really understand the problem and managed to install a lot of rom before. If anyone have any idea that can possibly make this device working, please reply to this thread. I hate to use my 5s as daily driver.
Click to expand...
Click to collapse
Has your phone's firmware been updated to Nougat? What OS version does your phone report?
computerslayer said:
Has your phone's firmware been updated to Nougat? What OS version does your phone report?
Click to expand...
Click to collapse
I came from marshmallow stock rom 3.37 firmware but verizon version since i thought that my phone is verizon edition. Do i need to flash stock nougat before changing to nougat based custom rom?
Access point names. Change it to what you carrier uses or get them to send it to your phone.
abdinsyakirin said:
I came from marshmallow stock rom 3.37 firmware but verizon version since i thought that my phone is verizon edition. Do i need to flash stock nougat before changing to nougat based custom rom?
Click to expand...
Click to collapse
Yes you do. If you flash a nougat based rom over marshmallow it wont boot.
Beamed in by telepathy.
shivadow said:
Access point names. Change it to what you carrier uses or get them to send it to your phone.
Yes you do. If you flash a nougat based rom over marshmallow it wont boot.
Beamed in by telepathy.
Click to expand...
Click to collapse
I've changed the apn but still the same. I will try flashing nougat based firmware and then give u my feedback. U have any link for the firmware?
abdinsyakirin said:
Hi. I have a M9 with model id 0PJA100.
Click to expand...
Click to collapse
abdinsyakirin said:
I came from marshmallow stock rom 3.37 firmware but verizon version since i thought that my phone is verizon edition.
Click to expand...
Click to collapse
That's not the Verizon MID. Don't flash anything unless you definetely know which version of the M9 you own.
abdinsyakirin said:
U have any link for the firmware?
Click to expand...
Click to collapse
Did Verizon already release the android N update? I haven't heard of it, yet.
shivadow said:
If you flash a nougat based rom over marshmallow it wont boot.
Click to expand...
Click to collapse
Are you sure? I know that this was the case when you tried to use an android M rom with an android L firmware. However, I haven't heard of such cases after people flashed an android N rom on an android M firmware. Sometimes newer HTC stock roms/stock-based custom roms are booting fine on older firmware versions (but that doesn't mean that there won't be any other issues due to the mismatch of the rom base and the current firmware).
Flippy498 said:
That's not the Verizon MID. Don't flash anything unless you definetely know which version of the M9 you own.
Did Verizon already release the android N update? I haven't heard of it, yet.
Are you sure? I know that this was the case when you tried to use an android M rom with an android L firmware. However, I haven't heard of such cases after people flashed an android N rom on an android M firmware. Sometimes newer HTC stock roms/stock-based custom roms are booting fine on older firmware versions (but that doesn't mean that there won't be any other issues due to the mismatch of the rom base and the current firmware).
Click to expand...
Click to collapse
Yes i just know that my phone is an international version. Before this i thought it was verizon m9. Verizon did not release any nougat based firmware. But i think there is international version of nougat available
For the marshmallow to nougat question, i encountered some issues with the other rom. Some roms doesnt boot up and some others stuck on setup wizard since wifi cannot be enable.
So do u think i need to flash international version of nougat on my phone? Will it fix this mobile network problem.
abdinsyakirin said:
So do u think i need to flash international version of nougat on my phone? Will it fix this mobile network problem.
Click to expand...
Click to collapse
If you already flashed a Verizon firmware then you definetely need to flash a GSM RUU and should hope that your phone didn't get damaged unrecoverably. GSM devices and CDMA firmware (or vice versa) aren't compatible with each other.
Did you change your CID or your MID somewhen in the past? If not then please boot to download mode and tell us what version is stated behind "OS". If you did then I hope you wrote down your original MID and CID. At the moment I'd recommend you to flash whatever RUU belongs to your original firmware version since the issues you describe shouldn't happen if you use the correct stock rom.
After all reception problems on the stock rom got solved we can think about updating your phone to android 7 but at the moment we should only make one step at a time.
Flippy498 said:
If you already flashed a Verizon firmware then you definetely need to flash a GSM RUU and should hope that your phone didn't get damaged unrecoverably. GSM devices and CDMA firmware (or vice versa) aren't compatible with each other.
Did you change your CID or your MID somewhen in the past? If not then please boot to download mode and tell us what version is stated behind "OS". If you did then I hope you wrote down your original MID and CID. At the moment I'd recommend you to flash whatever RUU belongs to your original firmware version since the issues you describe shouldn't happen if you use the correct stock rom.
After all reception problems on the stock rom got solved we can think about updating your phone to android 7 but at the moment we should only make one step at a time.
Click to expand...
Click to collapse
My phone has SuperCID. Based on download mode, the OS- 3.37.605.13. Model ID 0PJA100 as stated before. I think the OS version is vzw not wwe since i flashed the vzw before. Actually, I bricked this device after i had my "mobile data disconnected" problem and asked somebody to help me fix it, and he flashed that firmware version (it is my fault since i thought this phone is verizon m9).
So, should I fully flash the wwe 3.35 firmware? Or what?
That's odd. I would have expected the current MID to be 0PJA30000. Did the MID get changed back to its original state after you flashed the Verizon RUU? Normally the M9 shouldn't accept a RUU if the MID doesn't match. Even the SCID won't change this fact, anymore, as it did on older HTC phones. Or are you talking about the original MID of the phone that is stated on the backside of the phone? I assume the answer to this question is yes since the MID you're talking about is two zeros too short for being a digital MID. Only the engraving on the backside of the phone uses this short version of MIDs.
Revert the SCID to one of the CIDs that belong to SKU 401 (but don't choose the demo unit CID HTC__002), if needed revert the MID to the one that belongs to this SKU and then flash the 3.35.401.12 RUU. Instructions can be found in the FAQ section of the ReadMe thread (the stickied one in the Q&A section and the General section).
After you flashed the GSM RUU your phone should be working normally, again, if the Verizon RUU didn't damage it unrecoverably. In addition, you should be able to install two OTAs (the latter is the update for Android 7) via the software update function of the phone.
Sent from my HTC One M9 using XDA Labs
Flippy498 said:
That's odd. I would have expected the current MID to be 0PJA30000. Did the MID get changed back to its original state after you flashed the Verizon RUU? Normally the M9 shouldn't accept a RUU if the MID doesn't match. Even the SCID won't change this fact, anymore, as it did on older HTC phones. Or are you talking about the original MID of the phone that is stated on the backside of the phone? I assume the answer to this question is yes since the MID you're talking about is two zeros too short for being a digital MID. Only the engraving on the backside of the phone uses this short version of MIDs.
Revert the SCID to one of the CIDs that belong to SKU 401 (but don't choose the demo unit CID HTC__002), if needed revert the MID to the one that belongs to this SKU and then flash the 3.35.401.12 RUU. Instructions can be found in the FAQ section of the ReadMe thread (the stickied one in the Q&A section and the General section).
After you flashed the GSM RUU your phone should be working normally, again, if the Verizon RUU didn't damage it unrecoverably. In addition, you should be able to install two OTAs (the latter is the update for Android 7) via the software update function of the phone.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
Oh yes the MID changed to 0PJA30000, sorry for my last reply, that one i referred to the back engraving of m9. Im gonna change the CID and flash the firmware version u talked about. I will give you an update once I done it.
Flippy498 said:
That's odd. I would have expected the current MID to be 0PJA30000. Did the MID get changed back to its original state after you flashed the Verizon RUU? Normally the M9 shouldn't accept a RUU if the MID doesn't match. Even the SCID won't change this fact, anymore, as it did on older HTC phones. Or are you talking about the original MID of the phone that is stated on the backside of the phone? I assume the answer to this question is yes since the MID you're talking about is two zeros too short for being a digital MID. Only the engraving on the backside of the phone uses this short version of MIDs.
Revert the SCID to one of the CIDs that belong to SKU 401 (but don't choose the demo unit CID HTC__002), if needed revert the MID to the one that belongs to this SKU and then flash the 3.35.401.12 RUU. Instructions can be found in the FAQ section of the ReadMe thread (the stickied one in the Q&A section and the General section).
After you flashed the GSM RUU your phone should be working normally, again, if the Verizon RUU didn't damage it unrecoverably. In addition, you should be able to install two OTAs (the latter is the update for Android 7) via the software update function of the phone.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
I dont get any mobile network, even worse than before. I flashed 3.35.401.12 like u told so. Do i need to flash it manually by extracting the folder and flash all the img inside it independently? If u have any suggestion let me know.
UPDATE: Actually i dont think the problem is with verizon firmware since I had the problem after I flashed ICE nougat rom (I came from SDreamTeam Sense8 rom). After that I bricked the device and told other person to help me flash vzw firmware because I thought it was verizon m9. This problem is very weird and i dont know how to relate the ICE rom with my current problem. OP of ICE rom said the rom not compatible with verizon m9 but since this phone is not verizon m9, i dont think there should be a problem right?
The RUU needs to get flashed via the SD card method that is described in the ReadMe thread.
As written there and in some of my posts in this thread, GSM devices and CDMA firmware (or vice versa) aren't compatible with each other due to the different partition layouts. Therefore, cross-flashing can lead to unrecoverable damages.
I can't tell you what happened while you've been using ICE and therefore I can't tell you whether your phone had been in a recoverable state at that time. However, chances are high that flashing a Verizon RUU instead of the correct GSM RUU was the nail in the coffin of your phone. Sorry, that I don't have better news.
Edit: Oh, and please remove the quote from your last post. It's not necessary to quote me every time you post here.
Flippy498 said:
That's not the Verizon MID. Don't flash anything unless you definetely know which version of the M9 you own.
Did Verizon already release the android N update? I haven't heard of it, yet.
Are you sure? I know that this was the case when you tried to use an android M rom with an android L firmware. However, I haven't heard of such cases after people flashed an android N rom on an android M firmware. Sometimes newer HTC stock roms/stock-based custom roms are booting fine on older firmware versions (but that doesn't mean that there won't be any other issues due to the mismatch of the rom base and the current firmware).
Click to expand...
Click to collapse
Exactly that, it's not worth the risk seeing as many people have reported that their phone won't boot after mismatching roms to base firmware. Updating to a nougat custom rom to a marshmallow firmware would be bad as the api's are completely different and would explain the non booting situation.
So, until someone can confirm that flashing a nougat custom rom over a marshmallow base is 100% safe I'm going to swing with "yes I'm sure".
Beamed in by telepathy.
shivadow said:
So, until someone can confirm that flashing a nougat custom rom over a marshmallow base is 100% safe I'm going to swing with "yes I'm sure".
Click to expand...
Click to collapse
Re-read what I posted. I never said that it would be "100% safe" *. Of course there'll be problems due to the mismatch. I was only asking whether there have been reports about bootloops. (Btw, Android n and Android m don't differ as much as Android m and Android l did.) And according to this post the brick didn't happen directly after flashing the nougat rom.
However, I searched through the dev section yesterday and according to the Viper thread and the 4.x TWRP Backup thread people have been able to boot nougat roms on Android m. A lot of them faced problems. E.g. I have read about many user who used the old firmware and faced overheating and/or battery drain problems in the backup thread. They all needed to root their rom for getting rid of the problems. (Altough I personally can't explain why SuperSU should be able to fix those problems...) It seems like users with the newer firmware on the other hand don't necessarily have to face these issues. Take my phone as an example. It's running just fine without any heat and/or battery problems.
* Although I think that the usage of "safe" might imply that flashing a rom might damage your phone and that's not the case. The worst things that can happen are a bootloop or if the rom is booting fine some lags/bugs. Only flashing an incompatible firmware (via a RUU or a firmware pack) leads to damages.
Edit: Don't know how I could forget that but the answer to the OP's original problem with the reception on ICE is probably explained with Q1 of the FAQ section.
Sent from my HTC One M9 using XDA Labs
Flippy498 said:
After you flashed the GSM RUU your phone should be working normally, again, if the Verizon RUU didn't damage it unrecoverably. In addition, you should be able to install two OTAs (the latter is the update for Android 7) via the software update function of the phone.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
Since u didn't reply, i assume my device now damaged unrecoverably right?
EDIT: SORRY, I DID NOT GET ANY NOTIFICATION AND DONT READ THIS FORUM. VERY SORRY MY BAD. I AM VERY NEWBIE IN THIS KIND OF THINK.
Flippy498 said:
Edit: Don't know how I could forget that but the answer to the OP's original problem with the reception on ICE is probably explained with Q1 of the FAQ section.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
Thanks for the reply. Again sorry for my previous quote just now. Yes i read that q&a section and i did not have any of the problem except no mobile internet data. I can receive and make a phone call. Only mobile internet data. I am from 3.35 firmware if i am not mistaken since there was no official update after I purchased the phone. But NOW, I faced the problem after flashed GSM RUU. I do it twice, through exe and sdcard method. I also changed my CID and MID as u told me to.
The thing is that we don't know your original CID and your original firmware version. Not every SKU had a 3.35.x firmware version. That's why I'm guessing what the first problem might have been. If you say that there hasn't been any update at that time you probably used one of the SKUs that didn't have a 3.35.x firmware since those are the majority of SKUs that received the Android n update at a later time. But again, I can only assume what happened.
The problems you're facing now are probably a consequence of the cross-flashing. If flashing a GSM RUU could fix them then they're unrecoverable.
Sent from my HTC One M9 using XDA Labs
Flippy498 said:
The thing is that we don't know your original CID and your original firmware version. Not every SKU had a 3.35.x firmware version. That's why I'm guessing what the first problem might have been. If you say that there hasn't been any update at that time you probably used one of the SKUs that didn't have a 3.35.x firmware since those are the majority of SKUs that received the Android n update at a later time. But again, I can only assume what happened.
The problems you're facing now are probably a consequence of the cross-flashing. If flashing a GSM RUU could fix them then they're unrecoverable.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
So if i can find my original firmware version, i can solve this problem (if the verizon does not damage it) by flashing that version on my phone right? The only thing that I remember on my phone after i bought it is, it does not have any bloatware such as kid mode app, and when i clicked on software update, it said "please connect to XXXX to check an update" or something like that. XXXX referred to service provider in usa but i dont remember what company it was. I think there are still hope to recover this device.
I don't think that we can recover the phone even if we knew it's original firmware. That's why they're called "unrecoverable" damages.
For a GSM M9 it doesn't matter which RUU you flash (as long as it isn't a CDMA RUU). So if one GSM RUU didn't fix the situation then a different one won't be able to do so, either. And that's the reason why the ReadMe thread warns everybody not to cross-flash firmware files.
That part of my last post you're referring to was an explanation why I think that you faced problems with ICE. It has nothing to do with your current situation.
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

Can someone please point me in the direction....

Of the last/latest/final?? UK HTC M9 RUU Full stock.
Is there such a thing or do I have to use some mutated version of it?
I know the US have Fullstock RUU's but I cant find a UK one.
I'm expecting around 2GB size. With all the firmware, full wipe etc...
Thanks in advance!
Indeed there is for the wwe version (401) https://androidfilehost.com/?fid=817550096634758268
I have the file on my external sdcard for those moments where your phone thinks it's a toaster.
A lot will depend on whether your phone is locked to carrier or not. Carrier versions are hard to find.
shivadow said:
Indeed there is but I don't have any links. I have the file on my external sdcard for those moments where your phone thinks it's a toaster.
A lot will depend on whether your phone is locked to carrier or not. Carrier versions are hard to find.
Click to expand...
Click to collapse
Lol, I've Super CID it so no it's not locked to carrier.
I've Googled and only managed to find the US version from the HTC support site.
I've emailed HTC support so will wait for them.
Thanks
Htc has never provided and is never going to provide RUUs for their non-US devices. They even stopped providing US RUUs since the U11. If you own a non-US HTC device or a US model that is at least as young as the U11 then you rely on the files that get leaked on websites like ir-file or easy-firmware. The file that is linked above is a re-upload of such a leaked RUU since ir-file and easy-firmware require you to pay per download.
Sent from my HTC U12+ using XDA Labs
Flippy498 said:
Htc has never provided and is never going to provide RUUs for their non-US devices. They even stopped providing US RUUs since the U11. If you own a non-US HTC device or a US model that is at least as young as the U11 then you rely on the files that get leaked on websites like ir-file or easy-firmware. The file that is linked above is a re-upload of such a leaked RUU since ir-file and easy-firmware require you to pay per download.
Sent from my HTC U12+ using XDA Labs
Click to expand...
Click to collapse
Thanks Flippy, and I don't suppose the M9 is getting Oreo either...so I might as well stick with the last unlocked/developer edition RUU that I got from HTC/US/Support and root my phone again, yes?
And is there any way of getting rid of that Emergency app thing....?
eskimosound said:
I don't suppose the M9 is getting Oreo either...
Click to expand...
Click to collapse
Every HTC flagship reaches its EOL state two years after its launch. For the M9, this date was in spring 2017. In other words, unless you plan to flash an Oreo-based custom rom you won't see Android 8 on your M9.
eskimosound said:
so I might as well stick with the last unlocked/developer edition RUU that I got from HTC/US/Support and root my phone again, yes?
Click to expand...
Click to collapse
Aternatively, you can use the RUU that got linked above. It's the latest unbranded European RUU. It doesn't matter which SKU you use. The differences are almost non-existent.
(Sidenote: There is no WWE SKU. SKU 401 equals the unbranded European version, 708 the unbranded Asian/Hongkong version, 709 the unbranded Asian/Taiwanese version, 710 the unbranded Australian version and 617 the unbranded US American version.)
eskimosound said:
And is there any way of getting rid of that Emergency app thing....?
Click to expand...
Click to collapse
Which emergency app are you talking about?
Flippy498 said:
Every HTC flagship reaches its EOL state two years after its launch. For the M9, this date was in spring 2017. In other words, unless you plan to flash an Oreo-based custom rom you won't see Android 8 on your M9.
Aternatively, you can use the RUU that got linked above. It's the latest unbranded European RUU. It doesn't matter which SKU you use. The differences are almost non-existent.
(Sidenote: There is no WWE SKU. SKU 401 equals the unbranded European version, 708 the unbranded Asian/Hongkong version, 709 the unbranded Asian/Taiwanese version, 710 the unbranded Australian version and 617 the unbranded US American version.)
Which emergency app are you talking about?
Click to expand...
Click to collapse
I will try that RUU linked above....
The emergency Red/Orange Triangle that is linked to E911 in settings....says it cannot be removed and I believe it is so USA citizens can get Red, Amber and Yellow terrorist threat alerts!!
Even when rooted I can't find it to remove and it seems to have cropped up in Marshmallow and Nougat HTC OS's
Wait, so you don't own a European M9? If that's the case and the phone is S-ON then you won't be able to use the 401 RUU. And in case it's an American CDMA variant, you won't be able to use that RUU without damaging the phone, either, even if the phone is S-OFF.
Please take a look at the ReadMe thread. It contains all information you'll need for finding the correct RUU for your phone.
I've never heard of such an app. I've never owned a US M9, either, though.
Sent from my HTC U12+ using XDA Labs
Flippy498 said:
Wait, so you don't own a European M9? If that's the case and the phone is S-ON then you won't be able to use the 401 RUU. And in case it's an American CDMA variant, you won't be able to use that RUU without damaging the phone, either, even if the phone is S-OFF.
Please take a look at the ReadMe thread. It contains all information you'll need for finding the correct RUU for your phone.
I've never heard of such an app. I've never owned a US M9, either, though.
Sent from my HTC U12+ using XDA Labs
Click to expand...
Click to collapse
Thanks for your concern Flippy, no chill, I've got an International M9, (At leased that's whay the guy in China told me)
I've Unlocked Bootloader, S-Off (using Sunshine) and it was rooted until yesterday when I upgraded the Firmware to the Latest 4.30.617.12 and installed the RUU_HIMA_UL_N70_SENSE80_ATT_MR_NA_Gen_Unlock_4.30.617.12 exe.
Now the phone has unrooted itself and got rid of TWRP, Software Status saying Official (Fabulous)
So yep, I am aware though that, that is a USA RUU that's why I wanted the European one, however that linked one above is an earlier version....so still not the latest but it might have OTA if its official...?
It is the latest build. The numbering always differs between the SKUs.
And RUUs overwrite every partition on your phone. That's why you lost root and TWRP and the phones status got reset to official by flashing the US RUU.
Sent from my HTC U12+ using XDA Labs
Flippy498 said:
It is the latest build. The numbering always differs between the SKUs.
And RUUs overwrite every partition on your phone. That's why you lost root and TWRP and the phones status got reset to official by flashing the US RUU.
Sent from my HTC U12+ using XDA Labs
Click to expand...
Click to collapse
Thanks Flippy yep just rerooted now charging phone before I flash..
shivadow said:
Indeed there is for the wwe version (401) https://androidfilehost.com/?fid=817550096634758268
I have the file on my external sdcard for those moments where your phone thinks it's a toaster.
A lot will depend on whether your phone is locked to carrier or not. Carrier versions are hard to find.
Click to expand...
Click to collapse
Am I being stupid, I'm trying to flash this in TWRP, says file is corrupt....should I be adb sidelining it?
Please read the ReadMe thread. Being a *.zip archive doesn't equal being flashable via TWRP.
Sent from my HTC U12+ using XDA Labs
Flippy498 said:
Please read the ReadMe thread. Being a *.zip archive doesn't equal being flashable via TWRP.
Sent from my HTC U12+ using XDA Labs
Click to expand...
Click to collapse
It's not having it flippy, the zip file is corrupt. I've downloaded three times on three separate devices and I'm getting the same error.
More than that, I cannot actually extract the zip!
Flippy498 said:
Please read the ReadMe thread. Being a *.zip archive doesn't equal being flashable via TWRP.
Sent from my HTC U12+ using XDA Labs
Click to expand...
Click to collapse
And what I also need to do is downgrade my firmware or at least change it to the international version but I can't do that because I am getting a weird error....10 but bot the 10 mentioned in sneakyghosts firmware thread.
It's saying something about wrong device or hardware..
But I think that's just because I've got US firmware in it
As said before, read the ReadMe thread. You can't flash RUUs via TWRP and you can't unzip them the normal way since they're encrypted. All you're describing is expected behavior. The file is working fine. I've already used it several times.
And error 10 indicates that you didn't change your MID. A step by step guide for converting your phone can be found in the ReadMe thread, as well.
Sent from my HTC U12+ using XDA Labs
Flippy498 said:
As said before, read the ReadMe thread. You can't flash RUUs via TWRP and you can't unzip them the normal way since they're encrypted. All you're describing is expected behavior. The file is working fine. I've already used it several times.
And error 10 indicates that you didn't change your MID. A step by step guide for converting your phone can be found in the ReadMe thread, as well.
Sent from my HTC U12+ using XDA Labs
Click to expand...
Click to collapse
Hi Yep Flippy, thanks 10 RU_MODELID_FAIL.
Yeah, I have to change my MID using fastboot oem writemid and I think I have to change it to 0PJA10000 but I'm not entirely sure. At the moment the MID is 0PJA11000 (Dev Edition) for whatever reason I think the International version is 0PJA10000.
Can you or anyone confirm this or tell me how to determine?
I cannot extract the Zip file to have a look!
Yes, that's the correct MID. It's mentioned in above the downloads in the RUU section of the ReadMe thread, as well.
Flippy498 said:
Yes, that's the correct MID. It's mentioned in above the downloads in the RUU section of the ReadMe thread, as well.
Click to expand...
Click to collapse
Thank you Flippy, I have never been so happy to see the words "English (United Kingdom)"
As a quick note HTC said this:
Good day,
Thank you for contacting HTC Email support department.
Sadly we do not have an end user RUU's, if you need a software reflash you can do that through our repair center, you can double check the phone shipping country by replying back with the imei number or serial number and we will be able to provide more accurate information.
lol
shivadow said:
Indeed there is for the wwe version (401) https://androidfilehost.com/?fid=817550096634758268
I have the file on my external sdcard for those moments where your phone thinks it's a toaster.
A lot will depend on whether your phone is locked to carrier or not. Carrier versions are hard to find.
Click to expand...
Click to collapse
Hey thanks Shivadow, without your lovely RUU, I would not have been able to complete my mission. I am aware that you went out of your way to find that link so my most sincere gratitude.

Categories

Resources