Database Info

[Q] Downgrade hboot 1.23 to 1.17.011?

Hello, i'm sorry for my bad english, I'm french and I'm a little lost with my new phone, I've upgraded my Htc Sensation Hboot 1.17.011 to Hboot 1.23, but I want to restaure to 1.17.0011...It is possible to do that? Where can I found that firmware?
Hope you will understand my question, if you can give me a little help please, and I'm very sorry for my english but I think it's better than the google trad...
thank you everyone

If you want to stay on a 4.0.3 rom, you cannot downgrade to 1.17 as they won't boot without it.
But in the dev section, in the partition info thread, there is an boot flash able version of the 1.17 hboot somewhere in it.
Sent from my HTC Sensation

Thanks, I just want to install the Elegancia Rom but when I tried the boot bug and stop at the boot animation, you said in the dev section, in the partition info thread...is that one http://forum.xda-developers.com/showthread.php?t=1412618 ? and what I've to download please?
thanks

So you upgraded your firmware to 3.12, no? You need that to run any ICS Rom. Why do you need hboot 1.17? You still can flash Roms whith hboot 1.23 as long as you are s-off and supercid. Anyway, you can find hboot 1.17 here http://forum.xda-developers.com/showthread.php?p=20681060&postcount=22
Cheers
Sent from my Kindle Fire using Tapatalk

@ar4l, thanks, and yes I can flash but when I reboot my phone it freeze at the boot animation, it's the 3.12 firmware but Elegancia is not an ICS rom isn't it?

There are two versions of elegantia, one on GB and oneon ICS 4.0.3.
The second one requires the new 3.12 firmware with Hboot 1.23, the first one can run with both.
You really don't need to downgrade. If you have the boot bug is because you probably didn't flash the Firmware 3.12.401.2 following the correct procedure, First you should SUPERCID (step 4), reinstall 3.12.401.2 firmware from the thread you mentioned, reinstall whichever rom you want.
In alternative, if you don't want to SuperCID, you can follow mike1986's instructions to manually add your CID and MID to the firmware package:
1. Check your CID using fastboot getvar cid and MID using fastboot getvar mid
2a. If your CID and MID are supported by default, navigate to point 3.
2b. If your CID or MID is not supported by default, do this: (you do it at your own risk)
2c. Open PG58IMG.zip (don't extract it)
2d. Open android-info.txt in text editor
2e. Add your cidnum: <your CID> or modelid: <your MID> to the list, save file and close archive
3. Place PG58IMG.zip on your SD card
4. Boot your device holding power button + vol down button
5. Follow instructions on the screen
Click to expand...
Click to collapse

keep re booting after firmware upgrade , PLEASE HELP...

My HTC sensation keep re-booting after i download a firmware upgrade , to flash ICS ROM , and i can't flash any other rom , it keep re-booting , it says CID incorrect
HTC SENSATION
S-OFF
HBOOT- 1.27.1100
RADIO - 10.14.9035.01_M

someone_hill said:
My HTC sensation keep re-booting after i download a firmware upgrade , to flash ICS ROM , and i can't flash any other rom , it keep re-booting , it says CID incorrect
HTC SENSATION
S-OFF
HBOOT- 1.27.1100
RADIO - 10.14.9035.01_M
Click to expand...
Click to collapse
Hi,
Take a little time and read THIS THREAD carefully.

supercid
This also happened to me, you cannot flash ICS roms on your sensation without doing SuperCID.
Follow step number 4 to SuperCID but you would be better to go from the start and make sure you have either done already, or follow the steps closely before doing supercid.
Once you have supercid you will be ready to flash anything.
http://forum.xda-developers.com/showthread.php?t=1192300

someone_hill said:
My HTC sensation keep re-booting after i download a firmware upgrade , to flash ICS ROM , and i can't flash any other rom , it keep re-booting , it says CID incorrect
HTC SENSATION
S-OFF
HBOOT- 1.27.1100
RADIO - 10.14.9035.01_M
Click to expand...
Click to collapse
If you flashed the latest firmware to be able to flash an ics rom, and now want to flash a non ics from you won't be able to. You will need to downgrade your firmware to flasha non ics rom afterwards. See link in my sign for firmware link

supercid
highlander1v said:
This also happened to me, you cannot flash ICS roms on your sensation without doing SuperCID.
Click to expand...
Click to collapse
I don't think this is necessarily true, i was able to flash leedroid ics using mike's guide on changing cidnum and not using supercid.

someone_hill said:
My HTC sensation keep re-booting after i download a firmware upgrade , to flash ICS ROM , and i can't flash any other rom , it keep re-booting , it says CID incorrect
HTC SENSATION
S-OFF
HBOOT- 1.27.1100
RADIO - 10.14.9035.01_M
Click to expand...
Click to collapse
Which method did you use? I think you have put the PG58IMG.zip on the root of your sd card. Just delete the file . You will be fine.
One more thing, the firmware update did not happen as the CID is not listed that particular firmware. Check your CID using fasboot command .( after deleting the PG58IMG.zip ) then download a compatible firmware package which includes your CID and flash it.
Hope you know how to use fastboot command. If not no problem . Just do a search in the forum....
EDIT:
Yes. No need to do superCID . Download the compatible firmware. Add your CID in the android-info.text in firmware zip file and save it.

[Q] wrong image when flashing any firmware

hello
i'm trying to flash the Firmware 3.32.401.x & 3.32.401.10x RUU from this post http://forum.xda-developers.com/showthread.php?t=1412618 by mike1986 because i want to update the rom Android Revolution HD 6.6.2 XE (Audio Beats)
but whenever i do that, it says ...no image or wrong image PG58IMG.zip
can someone help me, i'm really new with it.
my phone's current settings
build number 3.25.401.101 CL275847 release-keys
baseband: 11.69.3504.00U_11.22.3504.07_M
kernel: 3.0.16-g5e58c5e
software: android revolution HD 6.2.1 XE by mike1986

You need to be slightly more specific than that. What have you done so far, step-by-step?
Edit: did you place PG58IMG.zip in the root folder of your SD card and did you check the md5sum of your PG58IMG.zip?

yeah more info would be helpful.
make sure you dont rename the image PG58IMG.zip.zip (sometimes windows hides filename extensions)

my phone is original before
Last time i rooted it, s-off ...flash the firmware 3.25 to install mike's 6.21 ICS rom and it worked well
so now i want to update to 6.62 rom, i downloaded the firmware 3.32 to my sdcard root...press the volumn down + power button to hboot and flash the firmware
but it keeps say that. how can i upgrade the firmware?
thanks

Have you checked if the file is really named PG58IMG.zip (stupid question, I know, but there was one time I ended up with PG58IMG (1).zip)? Alternative try downloading the file again (could be a bad download) or format your SD card before downloading the file again.

yes, i can confirm the name is correct, i formatted my card many times, tried new sdcard also.
downloaded the file many times..any idea?

hope someone can help me

are you SuperCID ?? if you are not the firmware must be matched

azzledazzle said:
are you SuperCID ?? if you are not the firmware must be matched
Click to expand...
Click to collapse
+1 to that
check the cid first
to verify CID use fastbbot command
"fastboot getvar cid"
this should give you the cid

yes, i have writtend the cid ...it's 11111111
any other possible reason?
Thanks guys

hixiaolin said:
yes, i have writtend the cid ...it's 11111111
any other possible reason?
Thanks guys
Click to expand...
Click to collapse
wrong image error comes when cid doesn't matches
and no image comes when the name is not proper
can you verify which error you are getting
Also check md5 of the firmware it might be a bad download
also if possible screen shot would be better
confirm the cid again once using fastboot command

The error:
SD Checking...
Loading...[PG58DIAG.zip]
No image!
Loading...[PG58DIAG.nbh]
No image or wrong image!
Loading...[PG58IMG.zip]
Then it says:
Parsing...[SD ZIP]
[1] RECOVERY
Do you want to start update?
if i choose yes, it updates done but the latest 3.32 version not appear.
--------------------------------
here's what i did to confirm the cid
cd C:\adb
adb devices
adb reboot-bootloader
fastboot getvar cid
it shows cid 11111111
i checked md5 and it's match. Any other help please?
Thanks

anyone please help me

In that case you have already flashed the firmware from PG58IMG.zip. The "no image" and "wrong image" are referring to the other 2 files, which you aren't flashing, so that's perfectly fine. The build number under Phone Settings doesn't reflect the firmware; it comes from the ROM itself. Try flashing ARHD 6.62 XE and see if it works.

hunter890 said:
In that case you have already flashed the firmware from PG58IMG.zip. The "no image" and "wrong image" are referring to the other 2 files, which you aren't flashing, so that's perfectly fine. The build number under Phone Settings doesn't reflect the firmware; it comes from the ROM itself. Try flashing ARHD 6.62 XE and see if it works.
Click to expand...
Click to collapse
+1 for that ....ohoohhh it seems you've wasted much time thinking that you didn't flashed firmware but you did ..anyways njoy ARHD
sent from my blazing fast pyramid through sonic waves

Returning to Stock few questions.

So I am returning to stock from this build:
ROM: CyanogenMod 9 RC1
FIRMWARE: 3.32.401.x & 3.32.401.10x
Radio:/ 11.22.3504.07_M
Hboot: 1.27.1100
And I have a few questions because reading the guides just didn't help me:
1. I can't understand completely the name of the RUU's: RUU_Pyramid_HTC_Europe_1.27.401.3_Radio_10.42.9007.00P_10.11.9007.15_M_release_192183_signed.exe
1.27.401.3 - is this HBOOT version?
10.42.9007.00P_10.11.9007.15 - This is radio but why does it have 2 values?
192183- What is this?
2.
If you have S Off, this doesn't matter, but you should always try to flash the oldest RUU, so that it is easier to S Off later, unless you don't intend to perform S Off again.
Click to expand...
Click to collapse
I am S Off and I want to return my phone to S-on for warranty purposes then S-Off again so I must flash the oldest RUU right? If it is this is the situation how to determine the oldest RUU by HBOOT version?
3. Firmwares? What about them does the RUU overwrites the firmware should I downgrade firmware before flashing older RUU and can it be done? Is there such thing as firmware and RUU compatibility? If there is which firmware corresponds to which RUU, the firmwares have version that are not mentioned anywhere else?
4. Which RUU's I can flash and which I can't? I mean what should I look for to be suitable? Should I install RUU that has the same HBOOT version as mine or I can install older like I am ICS and I want to install GB RUU so I can S-Off easier latter?
So I am a little confused about downgrading and picking suitable versions of everything.
I decided to try without matching anything just downloading the RUU with the oldest hboot and flash it. It's RUU_Pyramid_HTC_Europe_1.27.401.3_Radio_10.42.9007.00P_10.11.9007.15_M_release_192183_signed.exe and my device info is in the beggining of the thread. So in FASTBOOT i run .exe and I get
error: -5001. Please make sure you have finished any previous setup and closed other applications.
Click to expand...
Click to collapse
Is the problem with compatibility or something else?

Okay seems I've asked too much. Well I want to understand all those things but for now this is what I need to know:
Will flashing this RUU: RUU_PYRAMID_ICS_HTC_Europe_3.32.401.5_Radio_11.69.3504.00U_11.22.3504.07_M_release_246089_signed.exe
On this Phone:
ROM: CyanogenMod 9 RC1
FIRMWARE: 3.32.401.x & 3.32.401.10x
Radio: 11.22.3504.07_M
Hboot: 1.27.1100
Will be successful and can I S-off and Root again easy latter?

SsBloodY said:
So I am returning to stock from this build:
ROM: CyanogenMod 9 RC1
FIRMWARE: 3.32.401.x & 3.32.401.10x
Radio:/ 11.22.3504.07_M
Hboot: 1.27.1100
And I have a few questions because reading the guides just didn't help me:
1. I can't understand completely the name of the RUU's: RUU_Pyramid_HTC_Europe_1.27.401.3_Radio_10.42.9007.00P_10.11.9007.15_M_release_192183_signed.exe
1.27.401.3 - is this HBOOT version?
10.42.9007.00P_10.11.9007.15 - This is radio but why does it have 2 values?
192183- What is this?
2. I am S Off and I want to return my phone to S-on for warranty purposes then S-Off again so I must flash the oldest RUU right? If it is this is the situation how to determine the oldest RUU by HBOOT version?
3. Firmwares? What about them does the RUU overwrites the firmware should I downgrade firmware before flashing older RUU and can it be done? Is there such thing as firmware and RUU compatibility? If there is which firmware corresponds to which RUU, the firmwares have version that are not mentioned anywhere else?
4. Which RUU's I can flash and which I can't? I mean what should I look for to be suitable? Should I install RUU that has the same HBOOT version as mine or I can install older like I am ICS and I want to install GB RUU so I can S-Off easier latter?
So I am a little confused about downgrading and picking suitable versions of everything.
I decided to try without matching anything just downloading the RUU with the oldest hboot and flash it. It's RUU_Pyramid_HTC_Europe_1.27.401.3_Radio_10.42.9007.00P_10.11.9007.15_M_release_192183_signed.exe and my device info is in the beggining of the thread. So in FASTBOOT i run .exe and I get Is the problem with compatibility or something else?
Click to expand...
Click to collapse
SsBloodY said:
Okay seems I've asked too much. Well I want to understand all those things but for now this is what I need to know:
Will flashing this RUU: RUU_PYRAMID_ICS_HTC_Europe_3.32.401.5_Radio_11.69.3504.00U_11.22.3504.07_M_release_246089_signed.exe
On this Phone:
ROM: CyanogenMod 9 RC1
FIRMWARE: 3.32.401.x & 3.32.401.10x
Radio: 11.22.3504.07_M
Hboot: 1.27.1100
Will be successful and can I S-off and Root again easy latter?
Click to expand...
Click to collapse
1. RUU naming convention
RUU_Pyramid_<an extra LE in the name if XE>_HTC_<country/cariier>_<rom main version>_Radio_<radio version>_release_<release version>_signed.exe
dont bother about release version ..we dont need that
the only concerns are ..
country/carrier -> which determines the cid
rom main version ->explains whether youy are on GB or ICS (lesser the version ..older it is ...only between same country/carrier RUU's)
radio version -> tells the radio
2.oldest RUU ..ive explained earlier ..the main version should be least ..but this comparison is only valid if the country/carrier matches
eg:
in case of
RUU_pyramid_tmous_1.52.xx
and
RUU_pyramid_europe_1.27.xx (you cant say which one is oldest)
3.no firmware questions when we are talking about RUU (firmware arises when you talk about custom roms)
RUU has everything ...it wipes everything and converts it to stock (RUU cant touch the SOFF and CID though ..they can be changed only manually ..i.e. by we doing it manually by commands)
4.which RUU ..is you decide by CID ...
if you are supercid ..and dont know the original cid
you need to select the RUU based on your country and carrier
there is an excellent guide on RUU and it explains everything
here is the link to it ...do read it
(it helps you in finding right RUU too )
RUU RELEATED INFO AND FLASHING GUIDE
also remember by flashing RUU ..you wont lose SOFF ...unless you change it manually ..to know how to change it please refer the above guide
also i believe this answer ..answers your second post questions too

Thanks a lot! But I still got the problem with error I mentionted in the 1st post (error 5001) I tried with 1.27 and 1.28 HTC-Pyramid-Europe. What should I do is flashing through safe mod possible.
Sent from my HTC Sensation using xda app-developers app

SsBloodY said:
Thanks a lot! But I still got the problem with error I mentionted in the 1st post (error 5001) I tried with 1.27 and 1.28 HTC-Pyramid-Europe. What should I do is flashing through safe mod possible.
Sent from my HTC Sensation using xda app-developers app
Click to expand...
Click to collapse
im confused
did you mean you solved it ? or are you asking me how to bypass that error ?
anyways
you need to keep the phone connected to pc in bootloader/fastboot and then run the RUU.exe
Also ..if you did HTC-DEV unlock ..relock the bootloader (fastboot oem lock) and run the RUU.exe

I can't solve the problem. I connect it in bootloader/fastboot and try to run the RUU.exe. And I did revolutionary S-OFF.

Hey no idea that
error: -5001. Please make sure you have finished any previous setup and closed other applications.
is pretty annoying.

What is the CID currently on the phone ?
The RUU with xxx.401.xxxx IRC will require SuperCID (11111111) or a CID of HTC__001.
1.27... will end up installing HBOOT 1.17.0008 (just gone through the process on my replacement replacement phone.
As mentioned earlier you'll keep S-OFF and your existing CID after installing the RUU.
As far as the comms are concerned have you got the latest HTC drivers on the PC ?
---------------snip-------------
anyways
you need to keep the phone connected to pc in bootloader/fastboot and then run the RUU.exe
Also ..if you did HTC-DEV unlock ..relock the bootloader (fastboot oem lock) and run the RUU.exe
---------------snip-------------
I've recently run a few RUUs on my phone to get to a state where I could have a carrier backup, just in case (I forgot to get one immediately after S-OFF/custome recovery, doh). At no point did I re-lock the bootloader, I unlocked it (HBOOT 1.27.0000) and it's stayed unlocked the whole time, always worked perfectly. I also didn't have the phone in bootloader/fastboot mode, it was just on the home screen, again worked perfectly. I guess YMMV.

I am super CID.

gol_n_dal said:
I've recently run a few RUUs on my phone to get to a state where I could have a carrier backup, just in case (I forgot to get one immediately after S-OFF/custome recovery, doh). At no point did I re-lock the bootloader, I unlocked it (HBOOT 1.27.0000) and it's stayed unlocked the whole time, always worked perfectly. I also didn't have the phone in bootloader/fastboot mode, it was just on the home screen, again worked perfectly. I guess YMMV.
Click to expand...
Click to collapse
regarding RUU running normally ..you should have usb debugging enabled ..and need to have proper drivers too to recognize the device ..
running from fastboot no hassle there.. (most 155 errors can be prevented from running from fastboot)
couple of people were thrown error 99 when they ran RUU with unlocked bootloader ..so relock is a safer bet to prevent that error too

[Q]debranding tmobile htc one s problems

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.