Database Info

Possible to change "modelid" of HTC One S?

Hi guys! I have T-Mobile US version of One S and have changed to SuperCID and have the latest rom from Euro RUU 2.31. The model of my phone is different form european, so after checking I found the model to be PJ40110. I have first tried to make CID as HTC__001, but it wouldn't install RUU saying that model id doesn't match. Then I found txt file and saw that it needs a different model id, so this is when SuperCID came into play. Is there a way to change 'modelid' of the phone?
Thanks in advance!

In the build.prop
T-MobileUS HTC One S

fastboot write mid?
Sent from pixels to more pixels

usaff22 said:
fastboot write mid?
Sent from pixels to more pixels
Click to expand...
Click to collapse
I have tried the following command: fastboot oem writemid PJ4010000, the is the midel id I need to change to, but I get "Info[ERR] Command Error!!!" I know that this command is correct and looks like I would have to wait for S-OFF to make it work.

Charkatak said:
I have tried the following command: fastboot oem writemid PJ4010000, the is the midel id I need to change to, but I get "Info[ERR] Command Error!!!" I know that this command is correct and looks like I would have to wait for S-OFF to make it work.
Click to expand...
Click to collapse
Yes, I think it is only possible with the Engineering HBOOT, with S-OFF.
I don't think it is possible with HTCDev. You'll have to wait until we get S-OFF.
Sent from pixels to more pixels

usaff22 said:
Yes, I think it is only possible with the Engineering HBOOT, with S-OFF.
I don't think it is possible with HTCDev. You'll have to wait until we get S-OFF.
Sent from pixels to more pixels
Click to expand...
Click to collapse
- Now we have SOFF. What I did was I debranded the TMOUS HOS to WWE EU and flashed ICS rom.zip from RUU. All was fine till now and I have SOFF, relocked BL etc.
- Moreover, I do get notification for JB OTA and it also completes the download. However, it doesn't install as my MID is PJ4011000. EU RUU expects it to be PJ4010000.
- On searching, I found this thread. I tried issuing: sudo ./fastboot oem writemid PJ4010000 as well as sudo ./fastboot oem modelid PJ4010000. However, it still gives error:
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.012s]
finished. total time: 0.012s
- I have Ubuntu 12.04 on 64-bit 8 core machine (not sure if this is of any help but still thought of mentioning) which I am using for the playing with my HOS.
I guess now I need to find out how to change MID with SOFF.
Edit: I checked my build.prop and it has MID PJ4010000. So this MID is also stored somewhere apart from build.prop. Damn it !!

chota_shivaji said:
- Now we have SOFF. What I did was I debranded the TMOUS HOS to WWE EU and flashed ICS rom.zip from RUU. All was fine till now and I have SOFF, relocked BL etc.
- Moreover, I do get notification for JB OTA and it also completes the download. However, it doesn't install as my MID is PJ4011000. EU RUU expects it to be PJ4010000.
- On searching, I found this thread. I tried issuing: sudo ./fastboot oem writemid PJ4010000 as well as sudo ./fastboot oem modelid PJ4010000. However, it still gives error:
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.012s]
finished. total time: 0.012s
- I have Ubuntu 12.04 on 64-bit 8 core machine (not sure if this is of any help but still thought of mentioning) which I am using for the playing with my HOS.
I guess now I need to find out how to change MID with SOFF.
Click to expand...
Click to collapse
You need an Engineering HBOOT which supports those commands

usaff22 said:
You need an Engineering HBOOT which supports those commands
Click to expand...
Click to collapse
Thanks for the update.
I guess I am now *really* stuck on WWE ICS (for stock). Of course, I can flash any ROMs I want since I am SOFF, so not a big deal. I must say WWE ICS ROM is better than TMOUS with their bloat (which is anyway not useful to me at all since I am out of USA now).

chota_shivaji said:
Thanks for the update.
I guess I am now *really* stuck on WWE ICS (for stock). Of course, I can flash any ROMs I want since I am SOFF, so not a big deal. I must say WWE ICS ROM is better than TMOUS with their bloat (which is anyway not useful to me at all since I am out of USA now).
Click to expand...
Click to collapse
I'd bet money you could dd the correct partition from the phone change it with a hex editor and dd it back to the phone. I've done it with a handful of things and never had a problem.

I decrypted the zip and changed it to the US model. Run the RUU and before letting it install it to your phone, open up the temp directory and replace my zip with the 'rom.zip' in the temp folder. I will upload mine after I am home
Sent from my HTC One S using xda app-developers app

dc211 said:
I'd bet money you could dd the correct partition from the phone change it with a hex editor and dd it back to the phone. I've done it with a handful of things and never had a problem.
Click to expand...
Click to collapse
Hey thanks for the update. I agree with you on this point. Do you know what partition holds the MID in HOS?
Sent from my HTC One S using xda app-developers app
---------- Post added at 07:19 AM ---------- Previous post was at 07:16 AM ----------
leald said:
I decrypted the zip and changed it to the US model. Run the RUU and before letting it install it to your phone, open up the temp directory and replace my zip with the 'rom.zip' in the temp folder. I will upload mine after I am home
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Fantastic !! Would you mind sharing how to decrypt the zip? In any case awaiting for your rom.zip which has TMOUS MID in android_info.txt extracted EU JB RUU and decrypted .
Sent from my HTC One S using xda app-developers app

chota_shivaji said:
Hey thanks for the update. I agree with you on this point. Do you know what partition holds the MID in HOS?
Sent from my HTC One S using xda app-developers app
---------- Post added at 07:19 AM ---------- Previous post was at 07:16 AM ----------
Fantastic !! Would you mind sharing how to decrypt the zip? In any case awaiting for your rom.zip which has TMOUS MID in android_info.txt extracted EU JB RUU and decrypted .
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Ill try and upload it tonight but it might not be up until tomorrow morning because of its side. And actually you will have to "fastboot oem writecid HTC__001" asi already repackaged the zip before thinking I would have to add a tmobile cid, sorry
Sent from my HTC One S using xda app-developers app

leald said:
Ill try and upload it tonight but it might not be up until tomorrow morning because of its side. And actually you will have to "fastboot oem writecid HTC__001" asi already repackaged the zip before thinking I would have to add a tmobile cid, sorry
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
- I think you misunderstood me.
- My HOS is de-branded and has CID = HTC__001 from TMOUS & SOFF. I am on 2.31 EU stock ICS. The only hurdle now for me to use JB OTA/RUU/rom.zip is MID.
- So, what I am looking for is: rom.zip from JB EU RUU with android_info.txt changed for TMOUS MID and decrypted. Once I get that, I can use via RUU mode of fastboot.

chota_shivaji said:
- I think you misunderstood me.
- My HOS is de-branded and has CID = HTC__001 from TMOUS & SOFF. I am on 2.31 EU stock ICS. The only hurdle now for me to use JB OTA/RUU/rom.zip is MID.
- So, what I am looking for is: rom.zip from JB EU RUU with android_info.txt changed for EU MID and decrypted. Once I get that, I can use via RUU mode of fastboot.
Click to expand...
Click to collapse
- I found this thread http://forum.xda-developers.com/showthread.php?t=2084470 which has a tool to decrypt the JB RUU. It uses the libcrypt on Linux host machine to decrypt the rom.zip. It looks like for many phones JB RUU is encrypted.
- The tool mentions that it supports HTC One S (ville).
- I tried this tool to decrypt the rom.zip from JB EU RUU. It runs fine and I am able to get the decrypted rom.zip with MID = TMOUS in android_info.txt. However, I have not flashed it yet as I am not brave enough to face a brick (even though my signature mentions JB, I am still on ICS).
Can someone try this tool and flash as well? It needs Linux machine to compile and generate the binary to be useful.
Please note: I am not responsible if you brick your HOS due to this. You have been warned, do not attempt if you don't understand what you are doing.

Charkatak said:
Hi guys! I have T-Mobile US version of One S and have changed to SuperCID and have the latest rom from Euro RUU 2.31. The model of my phone is different form european, so after checking I found the model to be PJ40110. I have first tried to make CID as HTC__001, but it wouldn't install RUU saying that model id doesn't match. Then I found txt file and saw that it needs a different model id, so this is when SuperCID came into play. Is there a way to change 'modelid' of the phone?
Thanks in advance!
Click to expand...
Click to collapse
I think you should put the breaks on your project. Why exactly are you trying to change your MID anyways. If it's to get a RUU to run I'd suggest that you not go forward with your plan. There is no real reason to run an RUU if you have S-off other then to "start over" on a clean install of everything.
You can flash any: rom, firmware, radio, and hboot you choose so why change the model ID to run a RUU. Which is something I've NEVER seen anyone do in this forum to run a RUU. What's the full name of the RUU you want to run?
It looks like you're doing all this just to get to the official Jelly Bean release is that your goal? If so why not just flash it without using a RUU?

If so why not just flash it without using a RUU?[/QUOTE]
because the JB zip won't flash in a Tmous device because of different model id..

cyriantherockstar said:
because the JB zip won't flash in a Tmous device because of different model id..
Click to expand...
Click to collapse
Why not just install the rom that someone made compatible with TWRP then flash the firmware separately?

you can hex mod the mmcblk0p6 partition. it has a string pj0011000 in there somewhere as well as a spaced out string p j 0 0 1 1 0 0 0. if you edit those out, you should be fine to flash the ruu. first you need to supercid and s off though.

chota_shivaji said:
- I found this thread http://forum.xda-developers.com/showthread.php?t=2084470 which has a tool to decrypt the JB RUU. It uses the libcrypt on Linux host machine to decrypt the rom.zip. It looks like for many phones JB RUU is encrypted.
- The tool mentions that it supports HTC One S (ville).
- I tried this tool to decrypt the rom.zip from JB EU RUU. It runs fine and I am able to get the decrypted rom.zip with MID = TMOUS in android_info.txt. However, I have not flashed it yet as I am not brave enough to face a brick (even though my signature mentions JB, I am still on ICS).
Can someone try this tool and flash as well? It needs Linux machine to compile and generate the binary to be useful.
Please note: I am not responsible if you brick your HOS due to this. You have been warned, do not attempt if you don't understand what you are doing.
Click to expand...
Click to collapse
correct me if i am wrong here, but why dont you just take the rom.zip from the ruu, decrypt it and change the androidinfo.txt and change the model id to say the one you need. then rezip it with winrar or 7zip and feed it to the hboot... you are s-off so it shouldnt ask any questions regarding the signiture of the zip file, but i am not sure about the compression.

untrueparadox said:
you can hex mod the mmcblk0p6 partition. it has a string pj0011000 in there somewhere as well as a spaced out string p j 0 0 1 1 0 0 0. if you edit those out, you should be fine to flash the ruu. first you need to supercid and s off though.
Click to expand...
Click to collapse
Has anyone had success doing this?

[Q] Relocked bootloader & it show Fastboot menu

hi Guyzz
im new to Android phone
i've Unlock Bootloader from HTC Dev, roorted my HTC Explorer,
i've relocked bootloader of my HTC Explorer through this command "fastboot oem lock" but facing some issues like
after relocking bootloader my phone does not starts it show fastboot menu again n again, i tried many time by removing battery but same issue occurs
After applying all those solutions that found on google notthing happens
help me guyzzzz

If you relock your bootloader, you should flash stock ROM (with stock kernel) and stock recovery. Otherwise the phone will be stuck at the HBOOT screen with a "Security Warning" message

relock bootloader
Sachin Thomas said:
If you relock your bootloader, you should flash stock ROM (with stock kernel) and stock recovery. Otherwise the phone will be stuck at the HBOOT screen with a "Security Warning" message
Click to expand...
Click to collapse
Oh thats great but how can i do this sir....?
Plz describe in detail

ammarraza94 said:
Oh thats great but how can i do this sir....?
Plz describe in detail
Click to expand...
Click to collapse
Why are you trying to do this? You have lost your warranty by unlocking the bootloader. Re-locking will not make any difference.
If you are trying to return to stock ROM, unlock your bootloader and flash this:
http://forum.xda-developers.com/showthread.php?t=2225776
Or if you really want to re-lock it find an RUU appropriate for your radio version and run it after re-locking

Sachin Thomas said:
Why are you trying to do this? You have lost your warranty by unlocking the bootloader. Re-locking will not make any difference.
If you are trying to return to stock ROM, unlock your bootloader and flash this:
http://forum.xda-developers.com/showthread.php?t=2225776
Or if you really want to re-lock it find an RUU appropriate for your radio version and run it after re-locking
Click to expand...
Click to collapse
Hello,
Yes Sir i don't have Warranty...& how can i flash stock ROM (with stock kernel) and stock recovery

ammarraza94 said:
Hello,
Yes Sir i don't have Warranty...& how can i flash stock ROM (with stock kernel) and stock recovery
Click to expand...
Click to collapse
Download RUU and run it after relocking

Sachin Thomas said:
Download RUU and run it after relocking
Click to expand...
Click to collapse
hi Dear this is my Radio Version & HBoot Version
HBOOT-1.01.0000
RADIO-1.10.80.13M2
Can i Apply this RUU on my Phone
"RUU_Pico_HTC_Europe_1.28.401.1_Radio_10.35d.80.09H_1.11.82.17_release_230964_signed"

ammarraza94 said:
hi Dear this is my Radio Version & HBoot Version
HBOOT-1.01.0000
RADIO-1.10.80.13M2
Can i Apply this RUU on my Phone
"RUU_Pico_HTC_Europe_1.28.401.1_Radio_10.35d.80.09H_1.11.82.17_release_230964_signed"
Click to expand...
Click to collapse
What's your device's CID? Type "fastboot getvar cid" in fastboot mode to find out

Sachin Thomas said:
What's your device's CID? Type "fastboot getvar cid" in fastboot mode to find out
Click to expand...
Click to collapse
CID: HTC__Y13
finished. total time: 0.000s

ammarraza94 said:
CID: HTC__Y13
finished. total time: 0.000s
Click to expand...
Click to collapse
According to this page HTC__Y13 corresponds to HTC_Europe
http://mobility.forumsee.com/a/m/s/p12-9502-061490--operator-name-and-cid-classification-for-mozart-roms-ansar.html
So I think you'll be able to use the European RUU. The installation will not continue if it's incompatible, it'll show Error [131]

Sachin Thomas said:
According to this page HTC__Y13 corresponds to HTC_Europe
http://mobility.forumsee.com/a/m/s/p12-9502-061490--operator-name-and-cid-classification-for-mozart-roms-ansar.html
So I think you'll be able to use the European RUU. The installation will not continue if it's incompatible, it'll show Error [131]
Click to expand...
Click to collapse
Hello
Sir which RUU Can i Use. What do u Prefer..?
"RUU_Pico_HTC_Europe_1.17.401.2 Radio_10.30.80.09 H_1.10.80.13M2 release_221180_signed"
"RUU_Pico_HTC_Europe_1.28.401.1 Radio_10.35d.80.09 H_1.11.82.17 release_230964_signed"
These Is My Phone Details
"HBOOT-1.01.0000"
"RADIO-1.10.80.13M2"
"CID: HTC__Y13 .finished. total time: 0.000s"

You can use any RUU that contains a radio that's newer than your current radio version

Sachin Thomas said:
You can use any RUU that contains a radio that's newer than your current radio version
Click to expand...
Click to collapse
pls i need a little help.
my phone cvid is : VODAP304
i've noticed that theres not this on that site you gave ->http://mobility.forumsee.com/a/m/s/...cid-classification-for-mozart-roms-ansar.html
maybe thats why i keep gettint the "error131" whenever i try to install a RUU...
i'm from portugal, so i'm using a europe ruu everytime i try to install, but i keep getting that error131 and saying that i should install a version compatible with my phone... idk what to do... can you help me?

[S-Off] Convert to HTC USA Unlocked 1.12.617.6

this guide is probably not user friendly. im a long time htc user, and am just showing how i successfully converted my ATT A9 to the USA Unlocked A9 version 1.12.617.6
this should work for any A9 with the MID: 2PQ912000
if you have another MID like 2PQ910000, it may work but i cannot test -see step 2b (thanks @alray)
i also cannot test to see if this ACTUALLY unlocks the phone, because i dont have a nanosim from another carrier
finally, i am not responsible if you mess your device up and make it unusable, this worked for me.
i used SuperCID, 11111111, but this also may work with the cid of the unlocked phone, BS_US001.
Note: if youre using a different cid and/or mid you will not be able to install OTA updates. (thanks @htconeXX and @JochenP)
Extra Note: if you used superCID already, you can change it and try OTA again without reflashing, given you have not modified /system (tested by me)
prerequisites:
1.12.617.6 RUU: Here
drivers, bootloader unlocked from htcdev, s-off using sunshine YES PAY FOR IT IT WORKS AND THEYRE GREAT PEOPLE theroot.ninja
fastboot and ability to use command line
steps:
step 1: boot into DOWNLOAD MODE
this is the BLACK SCREEN that you can get to from the bootloader
from cmd, run
Code:
adb reboot bootloader
(or use the hardkey method)
which which will take you to the WHITE BOOTLOADER SCREEN
from there, navigate to "reboot to download mode" using the volume buttons and select with the power button
or
by turning off the phone, and holding the power + volume down buttons until you see the htc logo
step 2 change cid
once youre in the BLACK DOWNLOAD MODE screen, from your computer run
Code:
fastboot oem writecid BS_US001
from the command line (or fastboot oem writecid 11111111 for SuperCID)
(step 2b if your mid is something other than 2PQ912000 you can change it with the command
Code:
fastboot oem writemid 2PQ912000
which should allow you to flash the RUU (thanks @alray) )
then run
Code:
fastboot reboot-bootloader
step 3 go back into download mode, verify it says the cid youve chosen , and run the RUU you downloaded from above. follow the onscreen instructions to update your phone to 1.12.617.6
step4: re root, install recovery.
supersu BETA now supports /system-less root
you can find the TWRP flashible package here: http://forum.xda-developers.com/showpost.php?p=64161125&postcount=3
SYSTEMLESS SUPERSU is no longer beta, its WIP, and the post can be found HERE
the most recent supersu as of 12/31/15 is v2.65
(any supersu should suffice, but you know what they say, latest is greatest)
First flash twrp
Code:
fastboot flash recovery <recovery.img>
then boot into recovery and FORMAT YOUR DATA PARTITION
IGNORE PASSWORD PROMPT
GOTO WIPE>FORMAT DATA> and TYPE YES
reboot recovery
then sideload <supersu>.zip you downloaded earlier
go to advanced> adb sideload in TWRP
then from your computer run
Code:
adb sideload <supersu>.zip
which will patch your bootloader, and root your device

Ae3NerdGod said:
if you have another MID like 2PQ910000, it may work but i cannot test
Click to expand...
Click to collapse
Someone did it in the ruu thread.
Code:
fastboot oem writemid 2PQ912000
nice guide :good:

alray said:
Someone did it in the ruu thread.
Code:
fastboot oem writemid 2PQ912000
nice guide :good:
Click to expand...
Click to collapse
very useful. didnt know it was that easy on the a9. someone had to mess with hex to change the mid on the m8 i believe

Works with mobile Europe this method?,Thanks
Enviado desde mi HTC One A9 mediante Tapatalk

jureca said:
Works with mobile Europe this method?,Thanks
Enviado desde mi HTC One A9 mediante Tapatalk
Click to expand...
Click to collapse
Should work on any UHL variant

alray said:
Should work on any UHL variant
Click to expand...
Click to collapse
Ok Thanks.
Enviado desde mi HTC One A9 mediante Tapatalk

If it helps, I have an s-off, unlocked bootloader supercid and was able to flash this on a at&t branded a9

Hi Ae3NerdGod
you don't have to use adb reboot bootloader and - adb reboot download boots direct to download mode

htconeXX said:
If it helps, I have an s-off, unlocked bootloader supercid and was able to flash this on a at&t branded a9
Click to expand...
Click to collapse
yep, like said above, this should work on any UHL variant.

Can you remove my at&t branding too? Lol that'd be awesome. Nice guide. I'll be doing this when my at&t one arrives
Sent from my Nexus 5 using Tapatalk

alray said:
yep, like said above, this should work on any UHL variant.
Click to expand...
Click to collapse
Well with supercid s-off and stock unlocked rom, the 6.0.1 update will not take, downloads but wont install. I think I need to teh CID for a US unlocked phone.

cid AND mid
Gesendet von meinem HTC One A9 mit Tapatalk

SU 2.65 Beta is out. I would recommend you use 2.64 system less from here on out anybody to start with. There are issues with 2.63 (non-systemless) and trying to then go system less. More steps to ensure a proper installation.
2.65 Beta you can install right on top of 2.64 Beta in TWRP recovery. I tested this, no issues.
http://forum.xda-developers.com/showpost.php?p=64161125&postcount=3

htconeXX said:
Well with supercid s-off and stock unlocked rom, the 6.0.1 update will not take, downloads but wont install. I think I need to teh CID for a US unlocked phone.
Click to expand...
Click to collapse
JochenP said:
cid AND mid
Gesendet von meinem HTC One A9 mit Tapatalk
Click to expand...
Click to collapse
This is accurate, i will update OP with these notes.
techlogik said:
SU 2.65 Beta is out. I would recommend you use 2.64 system less from here on out anybody to start with. There are issues with 2.63 (non-systemless) and trying to then go system less. More steps to ensure a proper installation.
2.65 Beta you can install right on top of 2.64 Beta in TWRP recovery. I tested this, no issues.
http://forum.xda-developers.com/showpost.php?p=64161125&postcount=3
Click to expand...
Click to collapse
i personally dont like systemless, ive been removing it afterwards and manually rooting, but ill update the OP.

@Ae3NerdGod would you you. Know if i s-off a sprint Htc a9 and convert it with your method... Would that sim unlock the device?

Google~Android said:
@Ae3NerdGod would you you. Know if i s-off a sprint Htc a9 and convert it with your method... Would that sim unlock the device?
Click to expand...
Click to collapse
Do NOT try to convert a Sprint/CDMA device! It will break completely break mobile data because the radio firmware is incompatible.

Captain_Throwback said:
Do NOT try to convert a Sprint/CDMA device! It will break completely break mobile data because the radio firmware is incompatible.
Click to expand...
Click to collapse
But wudnt returning the stock sprint wit ruu fix it?? I want to at least give it a shot..

I successfully converted by AT&T to USA unlocked thank you for the post. Only issue an facing is I can't delete pictures from my gallery is telling me about permissions on my system but I have gone thru the app and made sure it was active.
Sent from my HTC One A9 using Tapatalk

Convert from China to US
Work great for me
Thank you

Followed the guide and successfully converted my AT&T to US unlocked using SuperCID thanks to @Ae3NerdGod ran 1.55.617.4 Dev Edition RUU from @Captain_Throwback and updated to 6.0.1, re-rooted and installed Xposed on the stock ROM. I can confirm that all are working fine:good:

HTC ONE Unlocked OTA 1.57.617.41 Download

Latest HTC One A9 Unlocked Edition OTA
OTA_HIA_AERO_UL_M60_SENSE7GP_ATT_MR_NA_Gen_Unlock_1.57.617.41-1.57.617.32_release_480058icet4xqcwsg0zr0g.zip
http://d-h.st/YwvS

techlogik said:
Latest HTC One A9 Unlocked Edition OTA
OTA_HIA_AERO_UL_M60_SENSE7GP_ATT_MR_NA_Gen_Unlock_1.57.617.41-1.57.617.32_release_480058icet4xqcwsg0zr0g.zip
http://d-h.st/YwvS
Click to expand...
Click to collapse
I have European version 1.56 , how can I install this?
Sent from my HTC One A9 using XDA-Developers mobile app

If you want to install this update you need to S-OFF your phone and change CID and MID using fastboot command from download mode:
fastboot oem writecid 11111111
fastboot oem writemid 2PQ912000
Then you will be able to flash US firmware.

Anybody have a valid TRWP system image for 1.57.617.32?
I took one but it still failed the verity check.

NuShrike said:
Anybody have a valid TRWP system image for 1.57.617.32?
I took one but it still failed the verity check.
Click to expand...
Click to collapse
Oh well, I flashed the .32 RUU and restored data from TWRP/FlashFire, flash this update, and I think I'm done.

NuShrike said:
Oh well, I flashed the .32 RUU and restored data from TWRP/FlashFire, flash this update, and I think I'm done.
Click to expand...
Click to collapse
Did you use FlashFire to only restore data? Just curious.

qooob said:
If you want to install this update you need to S-OFF your phone and change CID and MID using fastboot command from download mode:
fastboot oem writecid 11111111
fastboot oem writemid 2PQ912000
Then you will be able to flash US firmware.
Click to expand...
Click to collapse
This OTA will not flash if you're superCID. You must use the US unlocked or developer CID specifically to flash this OTA (BS_001 or BS_002).
The RUU will flash if you are superCID, but 1.57.617.41 RUU hasn't been officially (or unofficially that I'm aware of) released yet.

eelpout said:
Did you use FlashFire to only restore data? Just curious.
Click to expand...
Click to collapse
I used FlashFire generated backup in TWRP to restore data.
Of course internal-storage was still wiped, but I manually back that up these days (with SyncMe app), and don't put anything there, if possible.

qooob said:
If you want to install this update you need to S-OFF your phone and change CID and MID using fastboot command from download mode:
fastboot oem writecid 11111111
fastboot oem writemid 2PQ912000
Then you will be able to flash US firmware.
Click to expand...
Click to collapse
Will it really work? My phone will work properly? How to get S-OFF? Will S-On be back after I flash? Do I need to root?

It worked for me.
To get S-Off I used SunShine S-Off. You can disabled S-Off by running command `fastboot oem writesecureflag 3`. You need root to run SunShine.
After getting S-Off be careful not to mess HBOOT otherwise your phone will be hard-bricked and non-recovereable at home (you would need a programmer (device)).

qooob said:
If you want to install this update you need to S-OFF your phone and change CID and MID using fastboot command from download mode:
fastboot oem writecid 11111111
fastboot oem writemid 2PQ912000
Then you will be able to flash US firmware.
Click to expand...
Click to collapse
Will I get OTA?

MVince25 said:
Will I get OTA?
Click to expand...
Click to collapse
Yes, you should. You will need to relock the bootloader and s-on to make OTA work as far as I remember.

Convert UHL to UL
Hi, I have an European Unlocked A9, stock firmware 1.56.401.70. Also, I am S-off, SuperCid, and my device has 2GB of RAM. Can I use US Unlocked RUU to convert my HTC? I want to use 1.57.617.52 software. Is it ok to convert? The US unlocked version has 3GB RAM... Thanks !

qooob said:
Yes, you should. You will need to relock the bootloader and s-on to make OTA work as far as I remember.
Click to expand...
Click to collapse
bro OTA no need S-ON just relock bootloader

Converting AT&T carrier unlocked HTC One A9 from stock 1.27.502.5 to Nougat

Hey All,
Apologies if this is obvious but I couldn't figure it out myself looking at the FAQ's etc.
I just purchased a new HTC One A9 which was carrier unlocked by AT&T, and I want to convert from the RUU version they use (1.27.502.5) to the latest version that HTC has released on their website - 2.18.617.10 .
However, when I go to do this using that RUU, I get signature error 132. My phone is bootloader locked and S-ON, but from reading a little, I thought that shouldn't matter because I have a US phone, and you only need to change the CID/MID stuff (whatever those are) if you're in a different region?
How would I go about doing this? From reading through a bunch of posts, do I first need to switch to an unlocked version of Marshmallow, before then upgrading to Nougat?
Edit: Upon further reading, does the fact that the 502 in my current version does not match 617 in the one I wish to upgrade to mean that I can't do this with S-on? Do I need S-off? If so, how do I do that? Is it only by purchasing sunshine?
Thank you for your time!
Best,
-BBsmitz

bbsmitz said:
Hey All,
Apologies if this is obvious but I couldn't figure it out myself looking at the FAQ's etc.
I just purchased a new HTC One A9 which was carrier unlocked by AT&T, and I want to convert from the RUU version they use (1.27.502.5) to the latest version that HTC has released on their website - 2.18.617.10 .
However, when I go to do this using that RUU, I get signature error 132. My phone is bootloader locked and S-ON, but from reading a little, I thought that shouldn't matter because I have a US phone, and you only need to change the CID/MID stuff (whatever those are) if you're in a different region?
How would I go about doing this? From reading through a bunch of posts, do I first need to switch to an unlocked version of Marshmallow, before then upgrading to Nougat?
Edit: Upon further reading, does the fact that the 502 in my current version does not match 617 in the one I wish to upgrade to mean that I can't do this with S-on? Do I need S-off? If so, how do I do that? Is it only by purchasing sunshine?
Thank you for your time!
Best,
-BBsmitz
Click to expand...
Click to collapse
In order to convert to another carrier version, you must change your CID and MID to match the RUU version you want to flash. .617 uses the same MID as .502 so you'll need to change your CID only from CWS__001 to BS_US001. Changing CID does requires S-OFF (Sunshine is the best way unless you know someone with a XTC2Clip box).
You'll also need to update your firmware to Nougat before flashing the Nougat RUU because of the signature change implemented in Nougat.
Everything explained here:
https://forum.xda-developers.com/showpost.php?p=63640734&postcount=2
Read faq 1-2-3-4

alray said:
In order to convert to another carrier version, you must change your CID and MID to match the RUU version you want to flash. .617 uses the same MID as .502 so you'll need to change your CID only from CWS__001 to BS_US001. Changing CID does requires S-OFF (Sunshine is the best way unless you know someone with a XTC2Clip box).
You'll also need to update your firmware to Nougat before flashing the Nougat RUU because of the signature change implemented in Nougat.
Everything explained here:
https://forum.xda-developers.com/showpost.php?p=63640734&postcount=2
Read faq 1-2-3-4
Click to expand...
Click to collapse
Okay thanks so much Two more quick questions.
1) Does changing to S-off have any consequences in terms of a future update? I'm guessing it will void my warranty, but say I wanted to go back to using AT&T's version of android. Would the fact that my phone is now S-off prevent me from using their RUU (assuming I change the CID back.) I guess my question is, warranty aside, is there really any negative to turning S-off?
2) This is more out of curiosity. HTC One Phones that were sold unlocked/developer that are currently running Marshmallow can be upgraded to Nougat without flashing the firmware to 2.xx.xxx.x right? So if I was to change my current CID to that of a developer One A9, and install that Marshamallow RUU say (1.57.617.60), why wouldn't I be able to simply update from within the OS as they do?
Thanks again for your time.
Best,
Bbsmitz

bbsmitz said:
Okay thanks so much Two more quick questions.
1) Does changing to S-off have any consequences in terms of a future update?
Click to expand...
Click to collapse
No, after converting to another version, you'll receive ota updates for that version.
I'm guessing it will void my warranty,
Click to expand...
Click to collapse
Yes an no. There's always the possibility to revert back to your original version and hide everything you've done.
but say I wanted to go back to using AT&T's version of android. Would the fact that my phone is now S-off prevent me from using their RUU (assuming I change the CID back
Click to expand...
Click to collapse
You would simply have to revert your CID back to CWS__001 and flash the at&t ruu. Changing the cid is easily done.
I guess my question is, warranty aside, is there really any negative to turning S-off?
Click to expand...
Click to collapse
S-off gives you full control and access to all partitions which mean there is no more mechanism preventing you to flash incompatible software/firmware on your phone. Once s-off, be sure to understand what you're doing before flashing files. The risk is limited if you'll only be converting to another version or flashing custom roms but if you're going to explore a little deeper yeah it can be dangerous.
2) This is more out of curiosity. HTC One Phones that were sold unlocked/developer that are currently running Marshmallow can be upgraded to Nougat without flashing the firmware to 2.xx.xxx.x right? So if I was to change my current CID to that of a developer One A9, and install that Marshamallow RUU say (1.57.617.60), why wouldn't I be able to simply update from within the OS as they do?
Click to expand...
Click to collapse
All A9 can simply be updated from the OS, not only the unlocked/dev version. The reason why you need to flash the firmware first before flashing a RUU is that HTC changed their encryption signature in Nougat. That mean your phone need the new decryption key to be able to flash Nougat RUU. Flashing the firmware first will update your phone with the new key, making it able to flash Nougat RUU.
There is a firmware.zip file inside ota updates. When you install an ota update from the OS, the first thing that is flashed on your phone is that firmware.zip. So no you don't need to manually flash the firmware because it's done automatically in the ota process.
Yes you could flash the 1.57.617.30 ruu and do the ota update after. It's just faster to flash the Nougat firmware first and the Nougat RUU instead of flashing the Marshmallow RUU and downloading + installing 2 ota udpates, well that's my opinion. Both methods will give the same result.

alray said:
No, after converting to another version, you'll receive ota updates for that version.
Yes an no. There's always the possibility to revert back to your original version and hide everything you've done.
You would simply have to revert your CID back to CWS__001 and flash the at&t ruu. Changing the cid is easily done.
S-off gives you full control and access to all partitions which mean there is no more mechanism preventing you to flash incompatible software/firmware on your phone. Once s-off, be sure to understand what you're doing before flashing files. The risk is limited if you'll only be converting to another version or flashing custom roms but if you're going to explore a little deeper yeah it can be dangerous.
All A9 can simply be updated from the OS, not only the unlocked/dev version. The reason why you need to flash the firmware first before flashing a RUU is that HTC changed their encryption signature in Nougat. That mean your phone need the new decryption key to be able to flash Nougat RUU. Flashing the firmware first will update your phone with the new key, making it able to flash Nougat RUU.
There is a firmware.zip file inside ota updates. When you install an ota update from the OS, the first thing that is flashed on your phone is that firmware.zip. So no you don't need to manually flash the firmware because it's done automatically in the ota process.
Yes you could flash the 1.57.617.30 ruu and do the ota update after. It's just faster to flash the Nougat firmware first and the Nougat RUU instead of flashing the Marshmallow RUU and downloading + installing 2 ota udpates, well that's my opinion. Both methods will give the same result.
Click to expand...
Click to collapse
Edit2: I figured out the problem. I had to boot into the bootloader and then run
Code:
htc_fastboot oem rebootRUU
before I could run the RUU sucessfully. Am leaving the rest of this post up just so that other people googling this have a touch point.
Okay so I've used Sunshine to turn s-off and unlock my bootloader. I then changed my CID to BS_US001.
I then tried to install the HTC version of Marshmallow (maybe silly, but heard people having issues with Nougat and the battery) using the RUU.exe file. It started successfully, but then halfway though, after it had transferred the ROM over, it threw an ERROR155 and aborted, leaving my phone with an empty progress bar, and that circular green arrow icon in the middle. I used the command line to restart my device and had to factory wipe it, but otherwise not the worse for wear.
I tried googling it; do I need to relock my bootloader for the RUU.exe files to work? I think the Sunshine FAQ recommended against doing that. Is this a risky step?
Edit: Here are some instructions I found from the HTC One M8 firmware flashing thread. My error says "unknown" but I imagine its similar.
For “Error 155 relock bootloader" do:
- Since my thread works only with S-OFF phones anyway, this error can be read as: you need to S-OFF first!
- Error 155 can mean that you need SuperCID. On a few occasions this was shown when the RUU/FUU refused to run because of a wrong region lock.
- Lately, Error 155 has occurred when a FUU was launched from within android. When encountering a FUU error 155 with the process stalling after the rebootRUU (stuck at black screen with silver HTC logo), please just restart the FUU and leave the phone in that mode, or reboot the phone, then reboot to bootloader, then do “htc_fastboot oem rebootRUU” and then launch the FUU again (thanks @anarchychris for pointing it out).
- run the fastboot command “htc_fastboot oem lock" - only applies to S-ON phones that want to update the firmware with a stock OTA package (not offered on this thread!!). Stock OTA files sometimes need a locked bootloader.
Click to expand...
Click to collapse

help
Is this guide convert AT&T bindings factory unlocked htc? I cant access wifi hotspot. also cant run RRU.

hiii i have htc one a9300 by mistak i wipe every thing including internal memory now my fon sows that no "os install are you sure wanto reboot " please tell me wat to do now

AT&T conversion
alray said:
In order to convert to another carrier version, you must change your CID and MID to match the RUU version you want to flash. .617 uses the same MID as .502 so you'll need to change your CID only from CWS__001 to BS_US001. Changing CID does requires S-OFF (Sunshine is the best way unless you know someone with a XTC2Clip box).
You'll also need to update your firmware to Nougat before flashing the Nougat RUU because of the signature change implemented in Nougat.
Everything explained here:
https://forum.xda-developers.com/showpost.php?p=63640734&postcount=2
Read faq 1-2-3-4
Click to expand...
Click to collapse
How do I get started to do this. How do I find out my mid Cid and if I need to change? How do I flash firmware first? I have android 6.0 software 1.27.502.5. I have done a run before but never changed from a carrier. I went to the link above but I don't know what some if this means and where to start and what steps to take in order.