Hey guys. I have the latest 1.50.401.1 European stock ROM with stock recovery and all (S-ON, CID HTC__001). I installed this a while ago from the lastest European RUU 1.50.401.1 without any issues. I bought the phone at 2nd hand from a guy who installed some custom ROM on it so I flashed that RUU to return to stock (not T-Mobile stock ROM though, which was originally on the phone).
Now I'm trying to install RUU_PYRAMID_ICS_HTC_Europe_3.32.401.5_Radio_11.69. 3504.00U_11.22.3504.07_M_release_246089_signed.exe which is the lastest ICS RUU I think and the installer comes up with an error about my model ID. MID is PG5810000 (Sensation 4G - TMobile).
Also, I received the OTA after I went back to S-ON and fiddled with the CID yesterday (after running the first RUU a while ago it seems S-OFF didn't go away, not sure if it was supposed to in the first place). The CID is now HTC__001. Not sure what is was originally though. Anyway, I got the ICS OTA and tried to install, but after downloading it aborted the installation with the attached error.
Any ideas? I've been told that I need MID to be PG5813000 to install the ICS RUU, but why did the GB RUU work in the first place?
I want to install either the OTA (would be better) or the RUU, so if anyone has anything to say, I appreciate it.
Thanks!
hi all....i recently bought a t mobile htc one s and i am planning on debranding it....i dont live in the US and i dont need any of t mobiles services....my plan is to debrand it and get stock htc rom on it...i dont plan on using the phone rooted, so i want to be able to get OTA updates and everything, basically i want it to be like stock european htc one s....i google and found this link http://forum.xda-developers.com/showthread.php?t=1674202
after i rooted my phone i followed the steps in the link and was able to change my cid to HTC__001 from T-MOB010. i downloaded the european 2.31 RUU from http://www.filecrop.com/Ruu-HTC-One-S.html and when i ran it i got error code 130....my model id (PJ4011000) is different from the one the RUU is meant for (PJ4010000). so i was unable to debrand. i googled on how to change the modelid and read somehwere that i had to modify my build.prop file....followed the steps in this link http://forum.xda-developers.com/showthread.php?t=1236732 and changed the model id to PJ4010000 from PJ4011000 wherever it appeared in the build.prop file and pushed it back onto the phone, but still the ruu is giving the same error code 130.
i couldnt find any more links to help so i am posting it here. anyone have any ideas ? thanks
p.s i installed the stock recovery and the stock boot using fastboot and relocked the boot loader before trying to install using ruu. and the 2.31 ruu is compatible with HTC__001
anand_s said:
hi all....i recently bought a t mobile htc one s and i am planning on debranding it....i dont live in the US and i dont need any of t mobiles services....my plan is to debrand it and get stock htc rom on it...i dont plan on using the phone rooted, so i want to be able to get OTA updates and everything, basically i want it to be like stock european htc one s....i google and found this link http://forum.xda-developers.com/showthread.php?t=1674202
after i rooted my phone i followed the steps in the link and was able to change my cid to HTC__001 from T-MOB010. i downloaded the european 2.31 RUU from http://www.filecrop.com/Ruu-HTC-One-S.html and when i ran it i got error code 130....my model id (PJ4011000) is different from the one the RUU is meant for (PJ4010000). so i was unable to debrand. i googled on how to change the modelid and read somehwere that i had to modify my build.prop file....followed the steps in this link http://forum.xda-developers.com/showthread.php?t=1236732 and changed the model id to PJ4010000 from PJ4011000 wherever it appeared in the build.prop file and pushed it back onto the phone, but still the ruu is giving the same error code 130.
i couldnt find any more links to help so i am posting it here. anyone have any ideas ? thanks
p.s i installed the stock recovery and the stock boot using fastboot and relocked the boot loader before trying to install using ruu. and the 2.31 ruu is compatible with HTC__001
Click to expand...
Click to collapse
Try it without installing the recovery and boot before the RUU. There is no need to do that. Just relock and run the RUU, it will restore the boot and recovery for you.
Sent from my HTC One S using xda app-developers app
Lemme know how it goes. Might do this as well
Sent from my HTC VLE_U using xda app-developers app
Same here. I am trying to debrand the T-Mobile US as well. Thanks.
Sent from my HTC VLE_U using xda app-developers app
troby86 said:
Try it without installing the recovery and boot before the RUU. There is no need to do that. Just relock and run the RUU, it will restore the boot and recovery for you.
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
hmmm......i thought the model id is stored in the build.prop file, dont know how this can fix that....i heard the ruu checks for cid and the modelid...i am passing the cid check, its the model id where i get stuck....anyways will try it out and let you guys know....its my only phone currently so might be a few days
Guys, I have debranded my T-Mobile One S just a couple weeks ago. Unless you have a Super-CID and locked (relocked) bootloader, you won't be able to install a European RUU on T-Mobile One S. On the other hand, MID is stored not only in build.prop file but in areas inaccessible unless you are S-OFF, so you can flash European RUU but you still won't be able to OTA and will have to wait for the new update RUU when (if ever, you know what I'm talking about) it comes out.
You can find how to Super-CID in this post.
Is debranding needed in order to flash custom ROM ?
No. You just need to root the phone to install custom rom.
Sent from my HTC VLE_U using xda app-developers app
Confused
roadhero said:
Guys, I have debranded my T-Mobile One S just a couple weeks ago. Unless you have a Super-CID and locked (relocked) bootloader, you won't be able to install a European RUU on T-Mobile One S. On the other hand, MID is stored not only in build.prop file but in areas inaccessible unless you are S-OFF, so you can flash European RUU but you still won't be able to OTA and will have to wait for the new update RUU when (if ever, you know what I'm talking about) it comes out.
You can find how to Super-CID in this post.
Click to expand...
Click to collapse
I am a bit confused with the above update and the thread here . The OP in the thread claims that he was able to de-brand his TMOUS HOS without SuperCID of 11111111.
Can somebody please clear the confusion?
Also, after de-branding, does the WiFi work on HOS which was previously TMOUS branded?
roadhero said:
Guys, I have debranded my T-Mobile One S just a couple weeks ago. Unless you have a Super-CID and locked (relocked) bootloader, you won't be able to install a European RUU on T-Mobile One S. On the other hand, MID is stored not only in build.prop file but in areas inaccessible unless you are S-OFF, so you can flash European RUU but you still won't be able to OTA and will have to wait for the new update RUU when (if ever, you know what I'm talking about) it comes out.
You can find how to Super-CID in this post.
Click to expand...
Click to collapse
hmmm....i wasnt able to flash the european RUU...as mentioned it gave me an error (code 130, model id not matching or something)....so forget OTA updates, even flashing the RUU was impossible with my current model id....i did consider going the super cid route but i heard that the jelly bean OTA update bricks phones with super cid...thats why i wanna get a more 'legitimate' cid like HTC__001....
chota_shivaji said:
I am a bit confused with the above update and the thread here . The OP in the thread claims that he was able to de-brand his TMOUS HOS without SuperCID of 11111111.
Can somebody please clear the confusion?
Also, after de-branding, does the WiFi work on HOS which was previously TMOUS branded?
Click to expand...
Click to collapse
yeah the OP in that thread was able to debrand....and i think he used the HTC__001 cid ...dont know what the model number of his phone is....i think it might be matching with the one in the european RUU (PJ4010000)....does anyone know of any unbranded RUU that supports the model id PJ4011000 ??
I was able to flash my htc one s T-Mobile us with RUU_Ville_U_ICS_40_S_HTC_Europe_2.31.401.5_Radio_1.06es.50.02.31_10.09a.50.04L_release_275655 using superCID 11111111 it work perfectly however it is impossible to install the OTA update JB_45_S_HTC_Europe_3.16.401.8.
yw2012 said:
No. You just need to root the phone to install custom rom.
Sent from my HTC VLE_U using xda app-developers app
Click to expand...
Click to collapse
yw2012 thanks for your answer.
I suppose that no problem exists with this phone, a custom ROM could be flashed :
HTC One S
T-MOB101
HBOOT-1.14.0002
RADIO-1.09es.50.02.07_2
Android version : 4.0.4
HTC Sense version : 4.1
Software number : 2.38.111.10
Baseband version : 1.09es.50.02.07_2_10.09d.50.04L
Build number : 2.38.111.10 CL97613 release-keys
Bootloader unlocked
Rooted with SuperSU
ROM Stock
Well, I'd like to confirm that there's no way to flash a European RUU on USA T-Mobile device unless you Super-CID. There are also European T-Mobile branded phones, e.g. T-Mobile Germany. Those ones can be debranded using generic HTC__001 CID.
Small statistic report from fellow community (Not my own work):
1. HTC One S (Z520e) 1&1 Germany : CID: HTC__102 GER -> CID changed to 11111111 Super CID -> OTA --> OK!
2. HTC One S (Z520e) T-Mobile Germany : CID: T-MOB101 - TMD -> CID changed to HTC__102 GER -> OTA --> OK!
Few things you need to obey strictly when OTA to be safe, based on current brick reports:
1. Locked/relocked bootloader
2. Everything stock, no root, no custom recovery:
Code:
Radio: 1.06es.50.02.31_10.09a.50.04L
HBOOT: 1.14.0002
Recovery: Stock
ROM: Stock 2.31.401.5
3. CIDs:
Code:
cidnum: 11111111
cidnum: HTC__001
cidnum: HTC__E11
cidnum: HTC__203
cidnum: HTC__Y13
cidnum: HTC__102
cidnum: HTC__405
cidnum: HTC__304
cidnum: HTC__A07
4. FULLY CHARGED, CHARGING/SYNC CABLE DETACHED, leave the phone alone and let it apply the OTA update
So if I get it correctly, I can change my T-Mobile US HTC one s to cid HTC__001 and I can debrand it and still have OTA?
Sent from my HTC VLE_U using xda app-developers app
roadhero said:
Well, I'd like to confirm that there's no way to flash a European RUU on USA T-Mobile device unless you Super-CID. There are also European T-Mobile branded phones, e.g. T-Mobile Germany. Those ones can be debranded using generic HTC__001 CID.
Small statistic report from fellow community (Not my own work):
1. HTC One S (Z520e) 1&1 Germany : CID: HTC__102 GER -> CID changed to 11111111 Super CID -> OTA --> OK!
2. HTC One S (Z520e) T-Mobile Germany : CID: T-MOB101 - TMD -> CID changed to HTC__102 GER -> OTA --> OK!
Few things you need to obey strictly when OTA to be safe, based on current brick reports:
1. Locked/relocked bootloader
2. Everything stock, no root, no custom recovery:
Code:
Radio: 1.06es.50.02.31_10.09a.50.04L
HBOOT: 1.14.0002
Recovery: Stock
ROM: Stock 2.31.401.5
3. CIDs:
Code:
cidnum: 11111111
cidnum: HTC__001
cidnum: HTC__E11
cidnum: HTC__203
cidnum: HTC__Y13
cidnum: HTC__102
cidnum: HTC__405
cidnum: HTC__304
cidnum: HTC__A07
4. FULLY CHARGED, CHARGING/SYNC CABLE DETACHED, leave the phone alone and let it apply the OTA update
Click to expand...
Click to collapse
Thanks a lot for the vital info. i never tried flashing the RUU using super cid. i will try.
some more things of concern. lets say i change my cid to super cid (11111111) and am able to flash the 2.31 european RUU
1) does wifi/cellular radio of the t mobile US one s work with the european RUU?
2) and lets say i follow all the steps you recommended before an OTA update, the jelly bean OTA update wont brick my phone? is this right ? is there anyone who has successfully updated to jelly bean while on super cid ?
yw2012 said:
So if I get it correctly, I can change my T-Mobile US HTC one s to cid HTC__001 and I can debrand it and still have OTA?
Sent from my HTC VLE_U using xda app-developers app
Click to expand...
Click to collapse
sorry, i dont seem to get what you said. changing the cid will let you flash a different RUU but as people mentioned in this thread, you cant install an european RUU with generic cid like HTC__001 on a Tmobile US phone (cause of differing model id i presume). you can however install using super cid (i havent verified this myself and ofcourse i claim no responsibility ). but i dont know whether you can successfully update using OTA while on supercid
anand_s said:
Thanks a lot for the vital info. i never tried flashing the RUU using super cid. i will try.
some more things of concern. lets say i change my cid to super cid (11111111) and am able to flash the 2.31 european RUU
1) does wifi/cellular radio of the t mobile US one s work with the european RUU?
2) and lets say i follow all the steps you recommended before an OTA update, the jelly bean OTA update wont brick my phone? is this right ? is there anyone who has successfully updated to jelly bean while on super cid ?
sorry, i dont seem to get what you said. changing the cid will let you flash a different RUU but as people mentioned in this thread, you cant install an european RUU with generic cid like HTC__001 on a Tmobile US phone (cause of differing model id i presume). you can however install using super cid (i havent verified this myself and ofcourse i claim no responsibility ). but i dont know whether you can successfully update using OTA while on supercid
Click to expand...
Click to collapse
- I got the rom.zip from the RUU.exe.
- This .zip has a file called android-info.txt which mentions the "modelid: PJ4011000".
- I wonder if somehow you are able to edit this .zip and change modelid to match the current in phone, you might be able to do OTA update on HTC__001 unbranded phone from TMOUS.
As usual this is just a speculation with no real data to back it up. So use it on your own risk. I am not responsible to any damage this does to your phone :fingers-crossed:
yw2012 said:
So if I get it correctly, I can change my T-Mobile US HTC one s to cid HTC__001 and I can debrand it and still have OTA?
Sent from my HTC VLE_U using xda app-developers app
Click to expand...
Click to collapse
No, you won't even be able to run a European RUU in this case.
anand_s,
to answer your questions,
1) wifi/cellular radio works like a charm with the european RUU.
2) you will receive a request to receive a European JB OTA, it will even download but it will give you a message that you have different software on the phone and it won't install, so everything's fine with that, you'll just have to run a European JB RUU if it becomes available.
And yes, you are right regarding everything else. There's OTA on SuperCID, but MIDs mismatch and it does not install, it does not break your phone either.
I personally have US T-mobile One S S4, have unlocked bootloader, SuperCID and running a european RUU 2.31.
starting Jan26 unlocking phones will be ilegal in US
for all you people from US, if you want to unlock and debrand your phone I strongly suggest doing it today; tomorrow it will be a crime
http://www.techspot.com/news/51439-...ne-will-become-a-crime-starting-saturday.html
wtf is that? you really have lots of control freak people walking freely on the streets, and even worse, they're writing laws . . .
chota_shivaji said:
- I got the rom.zip from the RUU.exe.
- This .zip has a file called android-info.txt which mentions the "modelid: PJ4011000".
- I wonder if somehow you are able to edit this .zip and change modelid to match the current in phone, you might be able to do OTA update on HTC__001 unbranded phone from TMOUS.
As usual this is just a speculation with no real data to back it up. So use it on your own risk. I am not responsible to any damage this does to your phone :fingers-crossed:
Click to expand...
Click to collapse
This does not work, unfortunately. I tried it (the RUU extracts everything well before actually flashing, so at the last 'Next' dialog, I unzipped rom.zip in the temp folder, changed the MID in android_info.txt from PJ4010000 to PJ4011000, saved, and zipped it again), but no luck. This time, the RUU process fails with Error 132 (Signature error) rather than Error 130 (model ID error).
This is with changing CID from T-MOB010 to HTC__001. I'm now trying 11111111.
Edit: Changing the CID to 11111111 works, so you can flash the European 2.31 RUU for model ID PJ4010000 to the T-Mobile (US) One S with model ID PJ4011000. I didn't dare update to the Jelly Bean OTA (it showed up as available) thanks to this thread.
jenesuispasbavard said:
This does not work, unfortunately. I tried it (the RUU extracts everything well before actually flashing, so at the last 'Next' dialog, I unzipped rom.zip in the temp folder, changed the MID in android_info.txt from PJ4010000 to PJ4011000, saved, and zipped it again), but no luck. This time, the RUU process fails with Error 132 (Signature error) rather than Error 130 (model ID error).
This is with changing CID from T-MOB010 to HTC__001. I'm now trying 11111111.
Edit: Changing the CID to 11111111 works, so you can flash the European 2.31 RUU for model ID PJ4010000 to the T-Mobile (US) One S with model ID PJ4011000. I didn't dare update to the Jelly Bean OTA (it showed up as available) thanks to this thread.
Click to expand...
Click to collapse
- First of all thanks for all the updates. Moreover thanks for the brick-after-jb-update-on-super-cid thread.
- I wonder does it makes sense to de-brand TMOUS to European version at this point of time, if we are not able to do JB update.
- I think this should be attempted when the RUU for European JB is available. Not sure thought if that will help.
Hi all,
I am currently stuck with a crashing version of CM9.1 on my HTC Sensation.I did not backup a rom.
It keeps boot looping when i try other roms and flashing the boot.img does not help.
CM9 seems to work but when it enters into the OS,it works for about 10 seconds before it freezes,crashes and restarts the phone.
I'm looking for a HTC__044 (SE ASIA WWE ) CID RUU which has a version > 1.50.401.1 OR any other alternative to help me solve my predicament.I'm kinda stuck.I'vetried finding for an SE ASIA WWE RUU but it's really hard to find these days.
My device stats are as follows:
UNLOCKED (via HTC DEV)
PYRAMID
S-ON
HBOOT IS 1.18
RADIO is 10.14.9035.01_M
Version-main is 1.50.401.1
I tried various methods like revolution.io to S-OFF and S-ON methods like enabling the last line in 4ext Recovery on the tools page (forgot what it was).
Help greatly appreciated.
Thanks.
knightoftomorrow said:
Hi all,
I am currently stuck with a crashing version of CM9.1 on my HTC Sensation.I did not backup a rom.
It keeps boot looping when i try other roms and flashing the boot.img does not help.
CM9 seems to work but when it enters into the OS,it works for about 10 seconds before it freezes,crashes and restarts the phone.
I'm looking for a HTC__044 (SE ASIA WWE ) CID RUU which has a version > 1.50.401.1 OR any other alternative to help me solve my predicament.I'm kinda stuck.I'vetried finding for an SE ASIA WWE RUU but it's really hard to find these days.
My device stats are as follows:
UNLOCKED (via HTC DEV)
PYRAMID
S-ON
HBOOT IS 1.18
RADIO is 10.14.9035.01_M
Version-main is 1.50.401.1
I tried various methods like revolution.io to S-OFF and S-ON methods like enabling the last line in 4ext Recovery on the tools page (forgot what it was).
Help greatly appreciated.
Thanks.
Click to expand...
Click to collapse
Hi,
You have GingerBread radio and firmware.
You are trying to load an ICS ROM.
It will not work.
You need to flash a GB ROM.
Look HERE
Try that first.
I Have gotten help before with this site maybe I can understand this:
In the past I bought an HTC One m7 used with Hboot 1.44 Tmobile sim unlocked. I used an app called Revone v2.11 to S-off the phone. I used the command "Fastboot oem writeCID 11111111 and then flashed it with the ATT RUU from HTC1gurus website with Hboot 1.55. After the flash, it did fix the Wifi glitch that the phone had but it sucked as att so I then flashed it to HTC Euro ver 1.20 RUU from the same site giving the device Hboot version of 1.43 but the Wifi glitch was still fixed.
I got another HTC one m7 tmobile that was upgraded to 4.3 version with hboot 1.55, Set it to S-Off with rumrunner and changed the CID to 11111111 as well as I have a One T6UL Taiwan version that I set S-Off with Rumrunner as well and changed CID 11111111 but when I try to flash anything to Either of the 2 devices that both our set to S-off and both set to Super CID I get " Error, Reading Signature in zip failed" "Too Many Links". I can flash the newer M7 with the T-mobile RUU for android 4.3, HBOOT version 1.55 but if I try to run the HTC euro RUU that I ran on the first HTC one even on the Same computer it gives me "Unknown Error". or if I try to flash the extracted zip from the RUU.exe I get the "Too Many Links" error that I stated above.
Basically my questions are: If the devices our set to S-off and they have the super CID set, Why cant I flash any firmware old or new? I mean it worked on the first One M7 that I bought. Does Rumrunner not really set the device to S-off??
Hi there,
From what I've searched all discussions about T6UL is for HTC One MAX not M7. Are you sure about that?
Thanks
Hi everyone,
My A9 originally has CID TELST001 and MID 2PQ910000 (S-off and unlocked bootloader). I followed this guide (https://forum.xda-developers.com/one-a9/development/s-off-convert-to-htc-usa-unlocked-1-12-t3271861) to convert it to US model (CID: BS_US001 and MID: 2PQ912000)
I stopped at step 3, just go back to stock with RUU which I downloaded from HTC website (and I did lock bootloader when running RUU while keeping CID and MID as US model). However, the red text regarding to development purpose keeps appearing when I reboot the phone. Is it related to s-off status? From what I have read so far, as long as the kernel is stock then the red message should be gone. However, in my case, restoring via stock RUU does not erase the red message
Would someone please let me know if I did something wrong with RUU process? Cheers
As long as kernel,system and recovery is all stock the message should disappear... There is no reason to relock bootloader if s-off when running an ruu. Did you revert back to telstra ruu or use the unlocked developer ruu? Possible if ran ruu for telstra and kept unlocked cid/mid,maybe cause of your issue... Not sure though... Could be wrong...
Wonders_Never_Cease said:
As long as kernel,system and recovery is all stock the message should disappear... There is no reason to relock bootloader if s-off when running an ruu. Did you revert back to telstra ruu or use the unlocked developer ruu? Possible if ran ruu for telstra and kept unlocked cid/mid,maybe cause of your issue... Not sure though... Could be wrong...
Click to expand...
Click to collapse
I ran unlocked/developer RUU actually, since Telstra does not release RUU for A9. I guess this is the problem. Even with official firmware, if original CID does not match the firmware, it will trigger the red message. I have no idea how to test this theory until I get ahold of TELST001 RUU (which is unfortunately impossible atm)
Change cid/mid to Developer/Unlocked and rerun Developer RUU, If you have run the RUU the firmware is converted to Developer/Unlocked...If converted you really do not need anything from Telstra on the phone...If you have CID 11111111...Change to one below...If you have twrp installed... Replace with stock recovery
MID: 2PQ912000
CID: BS_US001