Related
hi friends
ı have a problem on radio flash. i cannot install ruu rom or flash radio to my sensation. hboot information of my phone:
unlocked
s-on
hboot 1.23.0000
radio 11.65
cid HTC_M27
I have tried so many ways for making super cid, flashing original ruu file and flashing radio. i have locked bootloder in order to flash ruu and i have tried two ruu file. these 3.25 europe ruu and 1.45 turkey ruu. When I install 3.25 ruu , I get the error wrong cid and when I install 1.45 ruu , I get the error hboot. in addition, when i make super cid i get fat error. is there any way for make super cid or change cid of ruu official rom.
please help.
You need to read up a bit and start again
http://forum.xda-developers.com/showthread.php?t=1192300
zahdekar said:
hi friends
ı have a problem on radio flash. i cannot install ruu rom or flash radio to my sensation. hboot information of my phone:
unlocked
s-on
hboot 1.23.0000
radio 11.65
cid HTC_M27
I have tried so many ways for making super cid, flashing original ruu file and flashing radio. i have locked bootloder in order to flash ruu and i have tried two ruu file. these 3.25 europe ruu and 1.45 turkey ruu. When I install 3.25 ruu , I get the error wrong cid and when I install 1.45 ruu , I get the error hboot. in addition, when i make super cid i get fat error. is there any way for make super cid or change cid of ruu official rom.
please help.
Click to expand...
Click to collapse
have you already tried step 4 here?
matt95 said:
have you already tried step 4 here?
Click to expand...
Click to collapse
yes ı tried repeatedly. but always ı get fat error in adb.
do you want to upgrade to 3.25 right?
---------- Post added at 12:48 AM ---------- Previous post was at 12:46 AM ----------
http://forum.xda-developers.com/showthread.php?t=1459767
look here...search HTC part 2...there is your cid HTC__M27 download 3.24 file and install it
yes ı want to update to 3.25 and install any radio.
zahdekar said:
yes ı want to update to 3.25 and install any radio.
Click to expand...
Click to collapse
i have found the 3.24 file try installing it and do supercid with that hboot
ok i tried. but not work. hboot is still 1.23
zahdekar said:
ok i tried. but not work. hboot is still 1.23
Click to expand...
Click to collapse
i think you already know it but just to be sure...you have to download the file i attached you before and then put that file on your sdcard and then reboot in bootloader....have you done so?
zahdekar said:
hi friends
ı have a problem on radio flash. i cannot install ruu rom or flash radio to my sensation. hboot information of my phone:
unlocked
s-on
hboot 1.23.0000
radio 11.65
cid HTC_M27
I have tried so many ways for making super cid, flashing original ruu file and flashing radio. i have locked bootloder in order to flash ruu and i have tried two ruu file. these 3.25 europe ruu and 1.45 turkey ruu. When I install 3.25 ruu , I get the error wrong cid and when I install 1.45 ruu , I get the error hboot. in addition, when i make super cid i get fat error. is there any way for make super cid or change cid of ruu official rom.
please help.
Click to expand...
Click to collapse
dude, you are s-on, you can't flash radios sorry. Shoulda used revolutionary.
yes i downloaded part 2, 3.24 zip file and placed root of sd card. flashed in fastboot.i got " wrong file or no file" error.
zahdekar said:
yes i downloaded part 2, 3.24 zip file and placed root of sd card. flashed in fastboot.i got " wrong file or no file" error.
Click to expand...
Click to collapse
are you sure that it is your cid? type this on cmd and tell me what it says: fastboot getvar cid (obviusly you have to be on fastboot mode)
Behold_this said:
dude, you are s-on, you can't flash radios sorry. Shoulda used revolutionary.
Click to expand...
Click to collapse
ok. but revolutionary dont support hboot 1.23.
matt95 said:
are you sure that it is your cid? type this on cmd and tell me what it says: fastboot getvar cid (obviusly you have to be on fastboot mode)
Click to expand...
Click to collapse
C:\android-sdk-windows\platform-tools>fastboot getvar cid
< waiting for device >
cid: HTC__M27
finished. total time: 0.003s
zahdekar said:
C:\android-sdk-windows\platform-tools>fastboot getvar cid
< waiting for device >
cid: HTC__M27
finished. total time: 0.003s
Click to expand...
Click to collapse
that's strange man...the one i provided should work...hmmm
zahdekar said:
ok. but revolutionary dont support hboot 1.23.
Click to expand...
Click to collapse
That's correct. You screwed yourself when you updated to ics firmware with s-on (or you set s-on after flashing though i can't figure out why). You are stuck for now until revolutionary supports the new hboot or until a new update that is supported comes out. You can now only upgrade, no downgrading for you, until s-off.
Behold_this said:
That's correct. You screwed yourself when you updated to ics firmware with s-on (or you set s-on after flashing though i can't figure out why). You are stuck for now until revolutionary supports the new hboot.
Click to expand...
Click to collapse
well if he could find the right fw witout supercid it could upgrade
Do I have to wait for the update of revolutionary? i can install custom 4.0.1 ice rom. but it is very slow and i cannot install official rom.
zahdekar said:
Do I have to wait for the update of revolutionary? i can install custom 4.0.1 ice rom. but it is very slow and i cannot install official rom.
Click to expand...
Click to collapse
Well I think revolutionary will not support that one... They are supporting the newer why support an older one?
Sent from my HTC Sensation XE with Beats Audio using Tapatalk
matt95 said:
Well I think revolutionary will not support that one... They are supporting the newer why support an older one?
Sent from my HTC Sensation XE with Beats Audio using Tapatalk
Click to expand...
Click to collapse
ok. thanks for help. if you find a way. please share on this post. OK?
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
Hi,
I'm trying to go to the stock rom because I have to return my phone because I have battery problems and dust behind my screen.
But when I try to flash a stock rom it doesn't work. It says that I using the wrong image update.
Current image is 1.11.401.110 and I want to go to the lastest stock rom 3.32.401.105
What do I have to do?
Thanks
What was the original CID ? What CID do you now have ?
1.11.401....... wow that seems really old.
x.xx.401.... will need CID "HTC__001" or SuperCID "11111111".
What exactly does it say when you run the RUU ? Does it connect OK to the Sensation, does it say what the existing version is on the phone ?
gol_n_dal said:
What was the original CID ? What CID do you now have ?
1.11.401....... wow that seems really old.
x.xx.401.... will need CID "HTC__001" or SuperCID "11111111".
What exactly does it say when you run the RUU ? Does it connect OK to the Sensation, does it say what the existing version is on the phone ?
Click to expand...
Click to collapse
I at the moment I have SuperCID so '11111111'.
My sensation was connected correctly to the pc
And do you need my Hboot version or my firmware?
My Hboot: 1.27.1100
Firmware: 3.33 full package
Greetz
tommeke19 said:
I at the moment I have SuperCID so '11111111'.
My sensation was connected correctly to the pc
And do you need my Hboot version or my firmware?
My Hboot: 1.27.1100
Firmware: 3.33 full package
Greetz
Click to expand...
Click to collapse
OK I don't understand where 1.11.401.110.... figures in the situation. If I understand correctly that is a custom ROM based off a different platform with Sense 4.0. Probably wrong though..
Are you fully S-OFF (clutching at straws here). Assuming you are you should be able to install an RUU easily. I recently went from 3.32.161.... to 3.32.401.. then back to 1.27.161... with no issues at all.
I'm sure someone more able than me can help you here.
GL
tommeke19 said:
I at the moment I have SuperCID so '11111111'.
My sensation was connected correctly to the pc
And do you need my Hboot version or my firmware?
My Hboot: 1.27.1100
Firmware: 3.33 full package
Greetz
Click to expand...
Click to collapse
ok you are SOFF seeing that you have revolutionary HBOOT ..
so when returning stock ...its better to flash the correct stock...which can be found using CID
but as you have supercid now ...you need to know your original cid or the carrier/country the phone is linked to ..for finding the proper stock RUU
this guide helps you in fiding the proper stock RUU and it has flashing instructions too
Hi,
I followed the link and tried to get my CID but I only get 11111111 so i don't know what I have to download now
Install "cid getter" from the market.
AFAIK the entry for "ro.cid" should tell you your original CID.
e.g. It says VODAP001 for me while "fastboot getvar cid" gives "11111111".
tommeke19 said:
Hi,
I followed the link and tried to get my CID but I only get 11111111 so i don't know what I have to download now
Click to expand...
Click to collapse
from which country you bought the phone from and to which carrier it is linked to ?
Thanks everyone for helping me, but after using google I've found a site and found the solution.
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.
Hello My Dear Learners & Teachers....:angel:
my question is my At&t HOX is on 4.0.3 ICS Wanted To Install JB i went to htc site and got the RUU Link
(RUU_EVITA_UL_JB_45_S_Cingular_US_3.18.502.6_Radio_0.24p.32.09.06_10.130.32.34_release_signed_With_Partial)
The Filename mentioned ... want to know is it correct RUU for my At&t HOX?
My Current Info is
Software Number "1.85.502.3" | Radio 0.17.32.09.12 | Hboot 1.09.0000
That is the right RUU for the AT&T version.
Is your phone stock or modded?
xoreg93 said:
Hello My Dear Learners & Teachers....:angel:
my question is my At&t HOX is on 4.0.3 ICS Wanted To Install JB i went to htc site and got the RUU Link
(RUU_EVITA_UL_JB_45_S_Cingular_US_3.18.502.6_Radio_0.24p.32.09.06_10.130.32.34_release_signed_With_Partial)
The Filename mentioned ... want to know is it correct RUU for my At&t HOX?
My Current Info is
Software Number "1.85.502.3" | Radio 0.17.32.09.12 | Hboot 1.09.0000
Click to expand...
Click to collapse
If you have Super CID, do not run the RUU. It will brick your phone.
If you're not sure, type the following command into your command line:
fastboot oem
readcid
redpoint73 said:
That is the right RUU for the AT&T version.
Is your phone stock or modded?
Click to expand...
Click to collapse
Sent from my HTC One XL using XDA Premium 4 mobile app
//JavaJ said:
If you have Super CID, do not run the RUU. It will brick your phone.
Click to expand...
Click to collapse
If the phone is s-on, yes that is right.
First of All Thanksss
yeahhhh its S-on
and please let me know why super cid will brick?? I thought super cid means any ruu will work..lol :silly:
and no mine is not super cid ... so I will upgrade it. :highfive:
SuperCID just means that at&t phones were able to unlock via htcdev because the at&t CID was blocked. SuperCID + s-on + jb RUU = brick. This is because a CID check that occurs halfway through the RUU update doesn't allow the RUU to finish, therefore ending up with a partially completed RUU, which means a bricked phone.
Sent from my Evita
xoreg93 said:
and please let me know why super cid will brick?? I thought super cid means any ruu will work..lol :silly:
Click to expand...
Click to collapse
What timmaaa mentioned is basically a bug. The RUU shoudn't run halfway like that, but for some reason on JB RUUs, it does (past RUUs were fine with SuperCID).
But also, what you said above is not true. SuperCID will not allow "any" RUU to work. It only bypasses CID check. Trying to run a RUU for an older hboot will fail version check. You need s-off to run "any" RUU.
thanksssss ALL Update Successful.....