Hey guys,
I own an original unlocked M9 (1.32.617.30) and want to convert it to the international model for the quicker updates.
Just got it S-OFF and wanted to make sure I got the rest of the steps right:
1. Change MID to 0PJA10000
2. Change CID to 11111111 (or to HTC__001? which is better?)
3. Run 1.32.401.17 RUU (is it possible to run 1.40.401.8 RUU instead? or do I need to flash a 1.32 base first?)
Cheers! Trying to avoid a bricked phone :angel:
Jhonys said:
Hey guys,
I own an original unlocked M9 (1.32.617.30) and want to convert it to the international model for the quicker updates.
Just got it S-OFF and wanted to make sure I got the rest of the steps right:
1. Change MID to 0PJA10000
2. Change CID to 11111111 (or to HTC__001? which is better?)
3. Run 1.32.401.17 RUU (is it possible to run 1.40.401.8 RUU instead? or do I need to flash a 1.32 base first?)
Cheers! Trying to avoid a bricked phone :angel:
Click to expand...
Click to collapse
Who is your carrier?
You shouldn't need to change your mid. Just change to super cid and you can flash the latest firmware and any custom rom you want.
If you're AT&T, the 401 firmware should work seamlessly, you just probably will not get voLte. If you're tired mobile, 401 firmware should also work, but no Wi-Fi calling (you should confirm this because I'm really not sure). If you're Verizon or Sprint, I have no idea, but I think you're sol and have to wait until they release an update. .
Edit: nevermind about carrier stuff. Didn't see that you have dev edition. 401 firmware should all work.
jollywhitefoot said:
Who is your carrier?
You shouldn't need to change your mid. Just change to super cid and you can flash the latest firmware and any custom rom you want.
If you're AT&T, the 401 firmware should work seamlessly, you just probably will not get voLte. If you're tired mobile, 401 firmware should also work, but no Wi-Fi calling (you should confirm this because I'm really not sure). If you're Verizon or Sprint, I have no idea, but I think you're sol and have to wait until they release an update. .
Edit: nevermind about carrier stuff. Didn't see that you have dev edition. 401 firmware should all work.
Click to expand...
Click to collapse
I'm not in the US, but europe. I've bought the phone through HTC US and that's why i'm on 617.
Regarding the MID, it is only because it is listed as a step here: http://forum.xda-developers.com/att-one-m9/general/att-developer-edition-ruu-how-to-t3086948
And when you say "flash latest firmware" what do you mean exactly? should I install 1.40 RUU or 1.32.401.17 RUU first? I really want to know Im flashing the right file now that i'm S-OFF.
Jhonys said:
I'm not in the US, but europe. I've bought the phone through HTC US and that's why i'm on 617.
Regarding the MID, it is only because it is listed as a step here: http://forum.xda-developers.com/att-one-m9/general/att-developer-edition-ruu-how-to-t3086948
And when you say "flash latest firmware" what do you mean exactly? should I install 1.40 RUU or 1.32.401.17 RUU first? I really want to know Im flashing the right file now that i'm S-OFF.
Click to expand...
Click to collapse
Gotcha. I didn't understand your desires. I thought you were basically asking how to upgrade your firmware and flash a rom. Probably you should ask in that thread and maybe clsA or someone else in that thread can give you specific advise. I assume you're looking to convert to stock 401/0PJA10000 and receive official otas?
This might help you as well.. its an A,B, C ... guide
http://www.droidviews.com/how-to-restore-htc-one-m9-to-stock/
From what Im aware, I thought Sunshine 3.17 only supports 501... arent we on 502?
Thanks guys I followed the guide from clsA and it worked perfectly. :good:
Yup! If you have a GSM M-9 than it's easy as pie! S-OFF, Super CID, Flash Firmware, Flash Rom! BAM! DONE!
Related
Q&A for [OTA] 1.32.401.15 + Firmware + NoRedText ABOOT + RUU
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [OTA] 1.32.401.15 + Firmware + NoRedText ABOOT + RUU. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
HTC One M9
Hello,
I wonder why the HBOOT is now called ABOOT with the One M9.. is it just because it`s new design.. or are there more changes that we should be careful with?
Thanks a lot
pipapoananas said:
Hello,
I wonder why the HBOOT is now called ABOOT with the One M9.. is it just because it`s new design.. or are there more changes that we should be careful with?
Thanks a lot
Click to expand...
Click to collapse
I think its mainly like the HBOOT on the M8, maybe only a name change, but i can't say, because i did not diff the files and i'm not really into digging into
bootloader images, i only do the needed edits and then i'm done.
Mismatched MID and CID
Hello. I just got S-off on my HTC one M9 Developer Edition in order to flash this firmware, but found (through getvar all) that my MID and CID are not the same. Why is this, and is there a way to fix it?
MID: OPJA11000
CID: BS_US002
BananaMasamune said:
Hello. I just got S-off on my HTC one M9 Developer Edition in order to flash this firmware, but found (through getvar all) that my MID and CID are not the same. Why is this, and is there a way to fix it?
MID: OPJA11000
CID: BS_US002
Click to expand...
Click to collapse
Of course they're not the same it wouldn't be good for your device if they were.
MID: a combination of numbers, letters and/or additional characters that identify your the device (as for example a HTC M9)
CID: a combination of numbers, letters and/or additional characters that identify the country of origin of your device and whether it's branded and sold by a carrier or not.
For example the MID and CID of an european M9 which is unbranded and sold in Germany are 0PJA10000 (that's a zero at the beginning not an O) and HTC__102.
Edit: Both, your MID and your CID, are the correct ones for the developer edition.
Sorry
Flippy498 said:
Of course they're not the same it wouldn't be good for your device if they were.
MID: a combination of numbers, letters and/or additional characters that identify your the device (as for example a HTC M9)
CID: a combination of numbers, letters and/or additional characters that identify the country of origin of your device and whether it's branded and sold by a carrier or not.
For example the MID and CID of an european M9 which is unbranded and sold in Germany are 0PJA10000 (that's a zero at the beginning not an O) and HTC__102.
Edit: Both, your MID and your CID, are the correct ones for the developer edition.
Click to expand...
Click to collapse
I didn't mean mismatched as in not the same, I meant as in unable to flash this firmware for that reason (that they do not match any provided MID or CID).
BananaMasamune said:
I didn't mean mismatched as in not the same, I meant as in unable to flash this firmware for that reason (that they do not match any provided MID or CID).
Click to expand...
Click to collapse
Ok, sorry for missunderstanding your post. Well, the x.xx.401.xx firmware versions are meant to be used on the international version of the M9 which can be identified by the supported MID and CIDs. You could change both IDs using fastboot commands but since the hardware of the U.S. variants is slightly different* I don't think it is a good idea to flash this firmware on your phone. In the worst case you might get a nice new paperweight if your phone is not compatible with that firmware. Besides I don't think it'll take too long until the official 1.40.xxx.xx firmware is going to be distributed via the OTA function of the stock HTC rom.
*Blame the fact that U.S. carriers use the CDMA network standard while most other parts of the world are using GSM.
Isn't it GSM?
Flippy498 said:
Ok, sorry for missunderstanding your post. Well, the x.xx.401.xx firmware versions are meant to be used on the international version of the M9 which can be identified by the supported MID and CIDs. You could change both IDs using fastboot commands but since the hardware of the U.S. variants is slightly different* I don't think it is a good idea to flash this firmware on your phone. In the worst case you might get a nice new paperweight if your phone is not compatible with that firmware. Besides I don't think it'll take too long until the official 1.40.xxx.xx firmware is going to be distributed via the OTA function of the stock HTC rom.
*Blame the fact that U.S. carriers use the CDMA network standard while most other parts of the world are using GSM.
Click to expand...
Click to collapse
Last I checked, only Verizon and Sprint are CDMA. Does Developer Edition include that functionality?
BananaMasamune said:
Last I checked, only Verizon and Sprint are CDMA. Does Developer Edition include that functionality?
Click to expand...
Click to collapse
Seems like you're right. As far as I read the developer edition is almost the same as the AT&T version which uses GSM. I thought every U.S. carrier uses CDMA. Nevertheless there must be a difference since your MID differs from the international one. If the hardware were the same there would be no need to use a different MID. Of course you could try installing the 1.40.401.xx firmware using the commands in the hide box but I cannot garantee that it will work or that your phone is still usable afterwards. I would actually suggest you to ask here whether you won't brick your phone by flashing the x.xx.401.xx version.
Code:
fastboot oem writecid <input desired CID without "<" and ">"here>
Code:
fastboot oem writemid <input desired MID without "<" and ">" here>
Edit: Seems like it won't "hurt" your phone to convert it to the international version.
developer editions on GSM
Hi all
i am wondering if the 1.32.617.30 developer firmware and RUU stuff will work on a GSM phone or more to the point a European phone.
The phone in question is mine it is unlocked and s-off and on super sid i just wanna make sure i still get phones call and stuff
any help or advise would be great
thanks guys
Hi thabks..is there any release date for the internatuonal 2.10 ruu??
Hi guys, need help here
I relocked my M9 and make it S-ON. im using firmware 2.7.401.1 I cannot install from any RUU, it seems there is no RUU that match with my firmware. I make mistake should S-ON the device later, but i already did it, so now i cannot use the phone because there is no OS on it.
I try to unlock bootloader, and cannot retrieve the token when using fastboot oem get_identifier_token. I read that since 5.1 you need to turn on unlock option in developer options, but i cannot do that, since the OS is already wiped
Is there any solution for this ?
Thanks.
when will we have the ruu zip 2.10.401.1 so we may be able to apply the SDCARD method to have a full clean stock flash?
I would like to have flashed in this way instead of going all the hard way in flashing ruuzip stock 1.40 and then upgrading by ota´s.
Thanks for all efforts, Nepht Legion.
need help to remove red text
Hi,
I have a HTC m9 asian variant ( on the download menu i get 2.1.709.1) . I have an unlocked bootloader, twrp , root, S-off, supercid installed.
I am running Maximus 6.0 rom based on 2.1.401.
I need to get the red text removed and have tried all the mentioned ways via adb to no success. I have very limited knowledge in this area, Can someone please help me ?
Thanks in Advance.
hi peep's, can we downgrade firmware with s-on and locked boot-loader. or do i need s-off and unlocked boot-loader sorry noob to htc devices regard's Joe.
joecool666 said:
hi peep's, can we downgrade firmware with s-on and locked boot-loader. or do i need s-off and unlocked boot-loader sorry noob to htc devices regard's Joe.
Click to expand...
Click to collapse
hi, you need s-off and a locked bootloader to be able to do that
maxx2210 said:
hi, you need s-off and a locked bootloader to be able to do that
Click to expand...
Click to collapse
okay thanks for your time and help regard's Joe.
Hi All,
Apologies if this is the wrong thread to post this in, just wanted to find out if anyone else has tried to manual install an ota on a M9 s-off.
I copy it to my SD and select to install it via stock recovery. It checks the file and starts the update and not once have i spotted an error, but once it is back up and running android, it is still on the old version.
I'm currently trying to go from 2.10.401.1 to 2.10.401.180, and if I go to aboot, it actual says the new version, but the OS version is still the old.
I would seem that the system partition isn't being updated.
Is there something i'm doing wrong? I tried the usual, googling and searching xda, but haven't found a solution yet.
Thanks
Sent from my HTC One using Tapatalk
Anyone can tell me how to extract the firmware from an OTA zip so I could upgrade my M9 firmware while being S-on? Thank you
Sent from my HTC One M9 using Tapatalk
http://forum.xda-developers.com/showthread.php?t=3378388
Sent from my HTC One M9 using XDA-Developers mobile app
Hi all,
I have recently surrendered and got s-off using sunshine.
I managed to RUU the AT&T ROM, but I want to get a clean unbranded ROM, that is unrooted - basically a factory-reset unbranded phone.
is that possible?
every RUU except the ATT one doesnt work for me...
thanks in advance.
mishumashu said:
every RUU except the ATT one doesnt work for me...
Click to expand...
Click to collapse
You'll need to change the CID and MID to run another carrier's RUU.
Alternately, instead of an RUU, you can flash a custom ROM, or stock ROM (such as stock DevEd MM ROM posted in Development), which will work fine on LP firmware. This would require an unlocked bootloader and custom recovery.
redpoint73 said:
You'll need to change the CID and MID to run another carrier's RUU.
Alternately, instead of an RUU, you can flash a custom ROM, or stock ROM (such as stock DevEd MM ROM posted in Development), which will work fine on LP firmware. This would require an unlocked bootloader and custom recovery.
Click to expand...
Click to collapse
is there any risk involved in changing my MID to a Europe one assuming the device is AT&T from the US?
any danger in running that RUU?
I already have TWRP and am unlocked.
Forgot to mention that because of my work I cant use a custom ROM (had Viper till now)..
mishumashu said:
is there any risk involved in changing my MID to a Europe one assuming the device is AT&T from the US?
any danger in running that RUU?
Click to expand...
Click to collapse
As long as you follow the instruction carefully and exactly, there is little risk in changing the CID and MID. For the MID in particular, be sure to get the location correct for the parameter you are changing (the instructions advise to cut and paste the command, to prevent a typo) otherwise you can do some permanent damage.
Once you've changed to the proper CID, MID, running the Euro RUU is not any more risk than running an AT&T one. The phones are the same in hardware.
redpoint73 said:
As long as you follow the instruction carefully and exactly, there is little risk in changing the CID and MID. For the MID in particular, be sure to get the location correct for the parameter you are changing (the instructions advise to cut and paste the command, to prevent a typo) otherwise you can do some permanent damage.
Once you've changed to the proper CID, MID, running the Euro RUU is not any more risk than running an AT&T one. The phones are the same in hardware.
Click to expand...
Click to collapse
cool, will give it a go, thanks!
Hey guys! I´ve got my 10 S-off'ed and model changed from HTC__060 (Indian) to HTC_001 (WWE), re-locked bootloader and tried to run RUU but get error 155 (latest RUU http://dl3.htc.com/application/RUU_...17.2.exe?_ga=1.123429256.280992434.1479770968 ).
I'm currently on 1.95.400.3 , I´m trying to run RUU as it's the easiest way to get everything back to stock. MID was and stills being 2PS620000 . Any help would be appreciated! Thanks!
btw I assume I won't get any radio issues, am I right?
philohtc said:
Hey guys! I´ve got my 10 S-off'ed and model changed from HTC__060 (Indian) to HTC_001 (WWE), re-locked bootloader and tried to run RUU but get error 155 (latest RUU http://dl3.htc.com/application/RUU_...17.2.exe?_ga=1.123429256.280992434.1479770968 ).
I'm currently on 1.95.400.3 , I´m trying to run RUU as it's the easiest way to get everything back to stock. MID was and stills being 2PS620000 . Any help would be appreciated! Thanks!
Click to expand...
Click to collapse
I duno why ypu would relock bootloader but anyways the RUU you are trying to flash is for US devices. Seeing you changed cid to WWE you need the latest x.xx.401.x RUU. it can be found in a zip you can rename the zip to 2PS6IMG.zip and place on external sd card, boot to downlaod mode and follow the prompts. Atm i dont think the latest is available but just flash the newest you can find then take the ota.
yldlj said:
I duno why ypu would relock bootloader but anyways the RUU you are trying to flash is for US devices. Seeing you changed cid to WWE you need the latest x.xx.401.x RUU. it can be found in a zip you can rename the zip to 2PS6IMG.zip and place on external sd card, boot to downlaod mode and follow the prompts. Atm i dont think the latest is available but just flash the newest you can find then take the ota.
Click to expand...
Click to collapse
Yeah i'll try that, what about radio? Won't vary or give trouble?
philohtc said:
Yeah i'll try that, what about radio? Won't vary or give trouble?
Click to expand...
Click to collapse
The radio is included in RUU. I dont know if your network will be effected or not, you will have to find out yourself. You can flash a different radio if need be.
philohtc said:
Yeah i'll try that, what about radio? Won't vary or give trouble?
Click to expand...
Click to collapse
you can always flash the HTC__060 radio.img after the International RUU (1.xx.401.x) and see if that gives you service.
I know for Verizon, we can flash the US Unlocked RUU (1.xx.617.x) and then the latest Verizon radio.img and it gives working service.
I would:
1) flash latest .401 RUU
2) boot and see if you have service
3) if not boot to download mode and:
fastboot flash radio HTC__060_radio.img
yldlj said:
I duno why ypu would relock bootloader but anyways the RUU you are trying to flash is for US devices. Seeing you changed cid to WWE you need the latest x.xx.401.x RUU. it can be found in a zip you can rename the zip to 2PS6IMG.zip and place on external sd card, boot to downlaod mode and follow the prompts. Atm i dont think the latest is available but just flash the newest you can find then take the ota.
Click to expand...
Click to collapse
andybones said:
you can always flash the HTC__060 radio.img after the International RUU (1.xx.401.x) and see if that gives you service.
I know for Verizon, we can flash the US Unlocked RUU (1.xx.617.x) and then the latest Verizon radio.img and it gives working service.
I would:
1) flash latest .401 RUU
2) boot and see if you have service
3) if not boot to download mode and:
fastboot flash radio HTC__060_radio.img
Click to expand...
Click to collapse
Finally ended up booting into download mode setting cid to BS__001 and set MID 2PS650000 before running US Unlocked/ Developer RUU. I can only get 3.5G (also called as H+ or 4G). But I'm not able to get LTE. I'm from Argentina (South America), and my M9 from T-Mobile works great on LTE. Now on the HTC 10 I'm actually on 1.96.617.20. Any thoughts? As I runned that RUU I would see no reason on flashing Verizon radio, I'm I right? Thanks!
philohtc said:
Finally ended up booting into download mode setting cid to BS__001 and set MID 2PS650000 before running US Unlocked/ Developer RUU. I can only get 3.5G (also called as H+ or 4G). But I'm not able to get LTE. I'm from Argentina (South America), and my M9 from T-Mobile works great on LTE. Now on the HTC 10 I'm actually on 1.96.617.20. Any thoughts? As I runned that RUU I would see no reason on flashing Verizon radio, I'm I right? Thanks!
Click to expand...
Click to collapse
I think you are correct, but I have no idea. I would flash a ROM such as Viper, Leedroid, Ice, etc.. and choose T-Mobile. This will add into the ROM the necessary components to help get you LTE. Right now you are on the RUU Stock US Unlocked 1.96.617.20 ROM, so it isn't going to fully support T-Mobile.
(What is your carrier? Why do you ask about flashing Verizon radio? Only flash Verizon radio if you are on Verizon network)
--It sounds as though you are on T-Mobile network, so first step flash ROM that supports T-Mobile as mentioned above, and if need, we can try flashing the T-Mobile radio.img next.
andybones said:
I think you are correct, but I have no idea. I would flash a ROM such as Viper, Leedroid, Ice, etc.. and choose T-Mobile. This will add into the ROM the necessary components to help get you LTE. Right now you are on the RUU Stock US Unlocked 1.96.617.20 ROM, so it isn't going to fully support T-Mobile.
(What is your carrier? Why do you ask about flashing Verizon radio? Only flash Verizon radio if you are on Verizon network)
--It sounds as though you are on T-Mobile network, so first step flash ROM that supports T-Mobile as mentioned above, and if need, we can try flashing the T-Mobile radio.img next.
Click to expand...
Click to collapse
Hey! My M9 was debranded from T-Mobile to Dev Edition. And still worked like a charm. I'm on Movistar Argentina, LTE bands here are AWS 4 and band 28. Don't see the reason it ain't working to be honest, maybe a config problem? First time I ever buy an European variant.
philohtc said:
Hey! My M9 was debranded from T-Mobile to Dev Edition. And still worked like a charm. I'm on Movistar Argentina, LTE bands here are AWS 4 and band 28. Don't see the reason it ain't working to be honest, maybe a config problem? First time I ever buy an European variant.
Click to expand...
Click to collapse
You may not get those bands because of hardware. I think this has been mentioned before especially with band 28
yldlj said:
You may not get those bands because of hardware. I think this has been mentioned before especially with band 28
Click to expand...
Click to collapse
I thought of following this guide http://forum.xda-developers.com/one-m9/general/how-to-change-network-bands-gsm-devices-t3135401 maybe it's locked? Thanks!
Hi guys
I'm having an issue with my M) unit. It's a Demo unit and I have S-OFF using sunshine and SuperCid.
Installed TRWP and restored bonesy stock backup, but the demo software is still present.
I though changing the CID was enough as CID 02 was triggering it.
But it's not the case.
Any help is appreciated.
Thanks.
elmalote said:
Hi guys
I'm having an issue with my M) unit. It's a Demo unit and I have S-OFF using sunshine and SuperCid.
Installed TRWP and restored bonesy stock backup, but the demo software is still present.
I though changing the CID was enough as CID 02 was triggering it.
But it's not the case.
Any help is appreciated.
Thanks.
Click to expand...
Click to collapse
I'm presuming it will still have the demo firmware installed, but as you're super cid and soff, you can now flash a "normal" stock firmware to rid it.
squ89r97 said:
I'm presuming it will still have the demo firmware installed, but as you're super cid and soff, you can now flash a "normal" stock firmware to rid it.
Click to expand...
Click to collapse
But I restored his backup, not mine? What is it checking on if not CID?
elmalote said:
But I restored his backup, not mine? What is it checking on if not CID?
Click to expand...
Click to collapse
Well, I'm thinking the actual firmware.
I searched google, found this.
https://forum.xda-developers.com/one-m9/help/removing-demo-content-t3063179
squ89r97 said:
Well, I'm thinking the actual firmware.
I searched google, found this.
https://forum.xda-developers.com/one-m9/help/removing-demo-content-t3063179
Click to expand...
Click to collapse
Unfortunately the links on that post no longer exist.
But if I find the firmware and flash, it'll remove the demo, is that correct understood?
elmalote said:
Unfortunately the links on that post no longer exist.
But if I find the firmware and flash, it'll remove the demo, is that correct understood?
Click to expand...
Click to collapse
From what I read in that thread provided, yes.
elmalote said:
Hi guys
I'm having an issue with my M) unit. It's a Demo unit and I have S-OFF using sunshine and SuperCid.
Installed TRWP and restored bonesy stock backup, but the demo software is still present.
I though changing the CID was enough as CID 02 was triggering it.
But it's not the case.
Any help is appreciated.
Thanks.
Click to expand...
Click to collapse
If you're looking to change your device SKU, your CID and MID have to match. SuperCID is no accepted by HTC's software packages (RUUs and OTAs). Check out the Readme thread for everything you need.
computerslayer said:
If you're looking to change your device SKU, your CID and MID have to match. SuperCID is no accepted by HTC's software packages (RUUs and OTAs). Check out the Readme thread for everything you need.
Click to expand...
Click to collapse
So if I want to change my SKU, I need to change the CID to HTC__F08 (which is the Danish one) and what about the MID?
I have read the ReadMe, but I'm not sure how they are related and what needs to be done with the MID.
I want to restore this one https://forum.xda-developers.com/on...m9-4-14-617-6-stock-root-twrp-backup-t3518149 and use it without the Demo software.
elmalote said:
So if I want to change my SKU, I need to change the CID to HTC__F08 (which is the Danish one) and what about the MID?
I have read the ReadMe, but I'm not sure how they are related and what needs to be done with the MID.
I want to restore this one https://forum.xda-developers.com/on...m9-4-14-617-6-stock-root-twrp-backup-t3518149 and use it without the Demo software.
Click to expand...
Click to collapse
Maybe I'm missing something but you're S-OFF so what you're planning to do at the moment doesn't make any sense. Why do you want to use a 617 system/backup on a 401 firmware? Change your MID and your CID to the ones that belong to SKU 617 and flash the latest 617 RUU. (Be aware that you can't use 4.x RUUs if your still using firmware 3.x or below. In that case you need to use a 3.x RUU for SKU 617 and install the OTAs via the software update function, afterwards.) This way you minimize lags and bugs that may arise if firmware version and system version mismatch. And not to forget that you'll be able to install future OTAs which you wouldn't be able to do if you just restore the backup you linked in your last post.
Alternatively (if you want to keep the European SKU), you simply need to flash the 3.35.401.12 RUU and to install the OTAs for the European android N update. However, you need to be aware that CID HTC__F08 doesn't exist on the M9 (as far as I know). The by SKU 401 supported CIDs are HTC__001, HTC__J15, HTC__102, HTC__Y13, HTC__A07, HTC__032, HTC__016, HTC__M27, HTC__002 and HTC__031. So you need to change your current CID to one of those that got mentioned in the last sentence or you won't be able to flash the RUU.
Flippy498 said:
Maybe I'm missing something but you're S-OFF so what you're planning to do at the moment doesn't make any sense. Why do you want to use a 617 system/backup on a 401 firmware? Change your MID and your CID to the ones that belong to SKU 617 and flash the latest 617 RUU. (Be aware that you can't use 4.x RUUs if your still using firmware 3.x or below. In that case you need to use a 3.x RUU for SKU 617 and install the OTAs via the software update function, afterwards.) This way you minimize lags and bugs that may arise if firmware version and system version mismatch. And not to forget that you'll be able to install future OTAs which you wouldn't be able to do if you just restore the backup you linked in your last post.
Alternatively (if you want to keep the European SKU), you simply need to flash the 3.35.401.12 RUU and to install the OTAs for the European android N update. However, you need to be aware that CID HTC__F08 doesn't exist on the M9 (as far as I know). The by SKU 401 supported CIDs are HTC__001, HTC__J15, HTC__102, HTC__Y13, HTC__A07, HTC__032, HTC__016, HTC__M27, HTC__002 and HTC__031. So you need to change your current CID to one of those that got mentioned in the last sentence or you won't be able to flash the RUU.
Click to expand...
Click to collapse
Yes I am S-OFF.
Basically I just want stock software, everything stock. Also the recovery. I just dont want the demo software.
I have RUU_HIMA_UHL_L50_SENSE70_HTC_Europe_1.32.401.17_Radio_01.01_U11440261_56.02.50306G_2_F_release_429340_signed_2_4 can I just flash this or is it not possible? I have flashed ICE M9 custom ROM right now.
I can't fint the 3.35.401.12 RUU anywhere :/ only the ZIP, is it usable?
Thanks a lot for your help.
The *.exe files are nothing more than the *.zip files with a fancy installer that flashes the *. zip via htc_fastboot.
Read the ReadMe thread. It contains flashing instructions for the *.zip files.
Sent from my HTC One S using XDA Labs
I've read here of people converting their non GPE edition to GPE..and then being able to go back to Sense... I'd be interested in doing the opposite.. Go to sense and have the option to go back to GPE... Is this doable? Downloaded this "RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4" ... Is this what I need? and if so also should I update firmware? I helped my dad upgrade to Marshmallow on ATT&T branded phone but his would not work until we updated firmware. If firmware needs updating can a kind soul provide a link?
+1
You need S-OFF for converting it.
jeeprcreepr said:
Downloaded this "RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4" ... Is this what I need? and if so also should I update firmware?
Click to expand...
Click to collapse
That RUU would be one possibility to "convert" to Sense. But as already stated, you need s-off (sunshine is the only working method - $25 US), and you need to change your CID to flash that RUU (possibly change MID also, but probably not).
You may or may not need to flash firmware first. Sometimes the Marshmallow RUU will flash if the phone already has Marshmallow firmware. But since it's a different MM firmware (and GPE at that), you may need to flash the firmware 6.12.1540.4 before the RUU will work. Error 155 when trying to flash the RUU will typically indicate you need to flash the firmware. You can get the firmware here: https://forum.xda-developers.com/showpost.php?p=60218734&postcount=5
Also note that flashing the RUU will change radio baseband, and therefor the frequency band support. That RUU is the US Dev Edition, which has the same band support as the AT&T version M8. And that is different from the band support on the GPE version. So depending on your region/carrier, that may or may not affect your band reception.