Database Info

Will at&t ruu 2.20.502.7 will work on supercid 1111111 at&t hox to get back to stock?

Will at&t ruu 2.20.502.7 will work on supercid 1111111 at&t hox to get back to stock?
I am having at&t htc one x bootloader with :
**** tampered ****
**** unlocked ****
evita pvt shp s-on rl
hboot-1.09.0000
radio-0.19as.32.09.09_l
opendsp-v28.1.0.32.0504
emmc-boot
apr 2 2012,21:08:24
installed twrp 2.2.0 recovery and stock rooted rom 2.23707.2 asia generic.
Now the problem is, i am facing the mobile signal(not wifi) dropping issues and i have to revert back to at&t stock rom, i have downloaded the official at&t ruu 2.20.502.2.....exe,
but i am concerned with the doubt that will the ruu will work 100% on supercid 111111 without any problem after relocking the bootloder or do i have to revert back the stock at&t cid, and if yes then what is the procedure to revert back the stock at&t cid???????

If you ever want to unlock the bootloader again leave the cid alone. BTW you can just flash the radio from the new ota if you want. There's a thread in development section with radios

gunnyman said:
If you ever want to unlock the bootloader again leave the cid alone. BTW you can just flash the radio from the new ota if you want. There's a thread in development section with radios
Click to expand...
Click to collapse
thanks for the help,appreciable. But i don't want to flash just the radio, coz i already did that, but it did not solve my problem. So the question still continues..Can i run Ruu with the current supercid 111111 or do i have to revert it back to stock???
SORRY FOR BAD ENGLISH. ITS NOT MY FAMILIAR LANGUAGE.

You don't have to change cid to flash the ruu just relock the bootloader

gunnyman said:
you don't have to change cid to flash the ruu just relock the bootloader
Click to expand...
Click to collapse
thanks for the help,

Are you already on 2.20? If not, why not run 1.85 RUU?

thedauntlessone said:
Are you already on 2.20? If not, why not run 1.85 RUU?
Click to expand...
Click to collapse
good question.

thedauntlessone said:
Are you already on 2.20? If not, why not run 1.85 RUU?
Click to expand...
Click to collapse
Doesn't look like the op is on 2.20, the hboot for 2.20 is 1.14.0002.

Absolutely Right, i am not on 2.20,
Sent from my HTC One XL using xda app-developers app

Sir this is not about 2.20 or 1.85, i just want to confirm is, if running a ruu on supercid 111111 will work 100% or do i have to revert to the region's cid of the ruu am using.
I dont want that ruu should get interupt by any reason nd i brick my phone coz i dont have any warranty or insurance on it.
SORRY 4 THE BAD ENGLISH, ITS NOT MY NATIVE LANGUAGE.
Sent from my AT&T HTC One X using xda app-developers app

hemsmaverick said:
Sir this is not about 2.20 or 1.85, i just want to confirm is, if running a ruu on supercid 111111 will work 100% or do i have to revert to the region's cid of the ruu am using.
I dont want that ruu should get interupt by any reason nd i brick my phone coz i dont have any warranty or insurance on it.
SORRY 4 THE BAD ENGLISH, ITS NOT MY NATIVE LANGUAGE.
Sent from my AT&T HTC One X using xda app-developers app
Click to expand...
Click to collapse
your question has been answered multiple times.
SuperCID will allow you to run the 2.20 RUU. The reason we're cautioning you is because once you do that, you will lose the ability to flash new radios at all and you'll have to flash a kernel in fast boot.
Also once you do this update to 2.20 you can't go backward to 1.85 even WITH SuperCID because the update includes a new HBOOT.

gunnyman said:
your question has been answered multiple times.
SuperCID will allow you to run the 2.20 RUU. The reason we're cautioning you is because once you do that, you will lose the ability to flash new radios at all and you'll have to flash a kernel in fast boot.
Also once you do this update to 2.20 you can't go backward to 1.85 even WITH SuperCID because the update includes a new HBOOT.
Click to expand...
Click to collapse
ok what will happen if i extract the rom.zip from the ruu and will extract and replace the hboot with earlier one and also the recovery with custom one and will rezip it and rename it as PJ83.img and will copy it to storage and run it in the current boot loader. will relock it before running the process.
Will this work and will i b able to flash the stock rom with same boot loader and custom recovery?
I AM AWARE INSTEAD OF DOING THIS I CAN JUST FLASH THE STOCK ROOTED 2.20 ROM FROM TWRP BUT I JUST WANT TO INCREASE MY TECHNICAL KNOWLEDGE AND WORK.

hemsmaverick said:
ok what will happen if i extract the rom.zip from the ruu and will extract and replace the hboot with earlier one and also the recovery with custom one and will rezip it and rename it as PJ83.img and will copy it to storage and run it in the current boot loader. will relock it before running the process.
Will this work and will i b able to flash the stock rom with same boot loader and custom recovery?
I AM AWARE INSTEAD OF DOING THIS I CAN JUST FLASH THE STOCK ROOTED 2.20 ROM FROM TWRP BUT I JUST WANT TO INCREASE MY TECHNICAL KNOWLEDGE AND WORK.
Click to expand...
Click to collapse
won't work because RUU's include a signature check and if you alter the files in any way, that signature check will fail.

gunnyman said:
won't work because ruu's include a signature check and if you alter the files in any way, that signature check will fail.
Click to expand...
Click to collapse
ok, well as per ur earlier suggestion, i have flash the radio incl ril files from at&t 1.85, asia 2.23, currently on a o2 2.29.
But signal dropping solution has not been resolved.
I have dropped the plan of running ruu and will install custom rom tn special edition 3.6
can u suggest me the best radio for better mobile signals? (i am from india -region asia)

How to update from 1.85 to 2.20?

I have my phone rooted since the first days of having it.
Never taken OTA update so it's still on 1.85 and it's unlocked but S-ON.
Has TWRP 2.4.3.0 and custom kernel and ROM.
Wanted to try some new roms that require new 2.20 and S-OFF.
Found a method to root 2.20 and get S-OFF, but my question now is how to safely upgrade from my existing condition 1.85/S-ON to 2.20?
Thanks

Why don't you just s-off, then RUU to 3.18, flash TWRP 2.3.3.1, downgrade touchscreen firmware, and then you can flash whatever you want.
Sent from my Evita

timmaaa said:
Why don't you just s-off, then RUU to 3.18, flash TWRP 2.3.3.1, downgrade touchscreen firmware, and then you can flash whatever you want.
Click to expand...
Click to collapse
Agree. Just S-off now, then run the 3.18 RUU.
If you are on 1.85, 2.20 is just an obsolete and unnecessary middle step, at this point.

Thanks to you both. Would you point me to see off procedure for 1.85?
Or it is the same as for 2. 20?
Thanks again
Sent from my HTC One X using xda app-developers app

Soff is the same regardless of software version. There's a sticky in the original android development section.
Sent from my HTC One X using xda app-developers app

[Q] Revert back to stock

I am looking for a Stock T-Mobile Jelly Bean image that won't brick my phone. I tried searching for one, but I couldn't find anything or I found RUUs for outdated versions of HBoot. I am trying to revert back to stock, but I am sorta scared to do so with an outdated RUU. I have HBoot version 2.15 and Radio version 1.13.50.05.31. Thanks in advance.

Would this be the RUU I have to download? http://bugsylawson.com/files/file/1...531-10305008l-release-309489-signed-ics-2exe/
I would just prefer a nandroid backup of the stock image that I can just flash with CWM.
I downloaded the RUU, I just need to know if that is the correct one for my phone before I use it. I really don't want a bricked phone. I checked the MD5sum already and it matches, that is the only thing holding me back.
Sent from my One S using xda premium

I have ran that RUU with the same hboot and radio as you. Why do you think it would brick your phone? you haven't supercid and have locked your bootloader right?
(didn't download from that site though)
http://forum.xda-developers.com/showthread.php?t=2094414

Okay, thank you for the reassurance. I just am pretty paranoid about bricking my phone. I have been looking up how to use RUUs for the last day or so, I just couldn't find anything on how to select the right one. Thanks again.
I just checked out your link and I am downloading now. I do not have SuperCID and I will be looking my boot loader.
Sent from my One S using xda premium

OccupyDemonoid said:
Okay, thank you for the reassurance. I just am pretty paranoid about bricking my phone. I have been looking up how to use RUUs for the last day or so, I just couldn't find anything on how to select the right one. Thanks again.
I just checked out your link and I am downloading now. I do not have SuperCID and I will be looking my boot loader.
Sent from my One S using xda premium
Click to expand...
Click to collapse
If you are on TMOB US then it's for you. Furthermore, you can match thr CID of your phone to that in the RUU.exe --> Firmware.zip --> android-info.txt.
You'll have to extract firmware.zip from temporary files when you run RUU without connecting phone.
Sent from my Nexus 7 using Tapatalk HD

I ended up using that RUU that was linked earlier in this thread and everything went fine. I just don't have the stock recovery. I guess that isn't that much of a problem though.
Sent from my HTC VLE_U using xda premium

OccupyDemonoid said:
I ended up using that RUU that was linked earlier in this thread and everything went fine. I just don't have the stock recovery. I guess that isn't that much of a problem though.
Sent from my HTC VLE_U using xda premium
Click to expand...
Click to collapse
The RUU installs the Stock Recovery automatically. You don't have to do anything extra.
You can find stock recovery (if you want to keep it for any purpose) inside the RUU (extraction would require you to run the RUU and then extract the recovery from Temporary Files)
OR
you can find it in the forums.

Hmmm, that's strange. Oh well I guess. When I tried to go into the recovery it just showed a red exclamation mark with a phone under it. I don't really need a recovery right now. Thanks for letting me know where I can find it.
Sent from my HTC VLE_U using xda premium

OccupyDemonoid said:
Hmmm, that's strange. Oh well I guess. When I tried to go into the recovery it just showed a red exclamation mark with a phone under it. I don't really need a recovery right now. Thanks for letting me know where I can find it.
Sent from my HTC VLE_U using xda premium
Click to expand...
Click to collapse
I believe that is the stock recovery. The red exclamation mark is telling you that you don't have access to it. Perfectly normal.

tivofool said:
I have ran that RUU with the same hboot and radio as you. Why do you think it would brick your phone? you haven't supercid and have locked your bootloader right?
(didn't download from that site though)
http://forum.xda-developers.com/showthread.php?t=2094414
Click to expand...
Click to collapse
Can I also run this same RUU as quoted in this thread ?
I have the same radio but different hboot ...
SuperCID = HTC__001 <---- I got this right now, I will have to put in TMO CID before I run RUU, is that true?
VLE PVT SHIP S-ON RL
HBOOT-1.13.0000
RADIO-1-13.50.05.31
I would like to go back to Stock becuase after rooting and putting custom ROM (AOKP, I lost 4g, it was working before)

DroidLuvver said:
Can I also run this same RUU as quoted in this thread ?
I have the same radio but different hboot ...
SuperCID = HTC__001 <---- I got this right now, I will have to put in TMO CID before I run RUU, is that true?
VLE PVT SHIP S-ON RL
HBOOT-1.13.0000
RADIO-1-13.50.05.31
I would like to go back to Stock becuase after rooting and putting custom ROM (AOKP, I lost 4g, it was working before)
Click to expand...
Click to collapse
Yes, I think it will give you an error with that cid. Someone could correct me, but with s-off you can run whatever ruu you want.

tivofool said:
Yes, I think it will give you an error with that cid. Someone could correct me, but with s-off you can run whatever ruu you want.
Click to expand...
Click to collapse
I am planning on changing the CID to match what's in the firmware and then running this RUU but... what about my hboot.. it's different than what you guys have. Its 1.13

DroidLuvver said:
I am planning on changing the CID to match what's in the firmware and then running this RUU but... what about my hboot.. it's different than what you guys have. Its 1.13
Click to expand...
Click to collapse
It will install the newer hboot to 2.15

tivofool said:
It will install the newer hboot to 2.15
Click to expand...
Click to collapse
So I should be able to run the RUU with lower boot like mine and it will upgrade the boot to 2.15 -
Is it true that with 2.15 hboot, modifying the CID is not allowed ?
Any reason why I should stay with 1.13 HBOOT and not go to 2.15 Hboot? Meaning any disadvantages of upgrading to HBOOT 2.15 ?

Well, say you updated your phone via ota & your cid is European or something. And all of the ruus for that CID are lower hboots. If u are s-on and and needed to ruu you wouldn't be able to.
But there is a guide to run a ota.zip for those people, so it isn't hopeless.
So not too many disadvantages.
In fact I just installed the newest Rom and firmware today. So my hboot is 2.16.
And the gossip is that update will be officially put out by HTC in a few weeks.
Sent from my HTC One S using Tapatalk 2

Remember this.
if you want to go stock again in future (warranty purpose)
some providers have only provided an ota (only ruu with lower hboots) when upgrading to jb. So downgrading gets hard
It's not that easy to flash an ota as is a ruu.
If your s-off downgrading is no issue.
Verstuurd van mijn HTC One S met Tapatalk

Relock and RUU for o2 Germany One XL

I have a One XL with o2 Germany Branding (CID: O2___102)
HBOOT 2.14
S-ON
ROM installed: CM 10.1
I want to relock it and flash a Stock ROM. Reason is that I want to send it to warranty.
As far as I know the HBOOT of the ROM must not be older than 2.14 and I can't find an appropriate ROM.
1. fastboot oem lock
2. launch RUU (I tried some, but it did't work)
Do I have to flash a Stock Recovery after that?

Running an RUU returns the phone to being completely stock, including recovery. I hope your don't have SuperCID or you're gonna brick. Click the link in my signature, you'll find RUU threads there.
Sent from my Evita

timmaaa said:
Running an RUU returns the phone to being completely stock, including recovery. I hope your don't have SuperCID or you're gonna brick. Click the link in my signature, you'll find RUU threads there.
Sent from my Evita
Click to expand...
Click to collapse
And what if none of these RUUs work?
O2:
OTA_EVITA_UL_JB_45_S_O2_DE_3.17.207.1_0.23a.32.09. 29_10.128.32.34a_release_2990766qakrzbj4mpslnsy.zi p
OTA_EVITA_UL_ICS_40_S_O2_DE_2.29.207.1-1.92.207.3_release_272963z2vl7cdycjk01nm4.zip

fly23 said:
And what if none of these RUUs work?
O2:
OTA_EVITA_UL_JB_45_S_O2_DE_3.17.207.1_0.23a.32.09. 29_10.128.32.34a_release_2990766qakrzbj4mpslnsy.zi p
OTA_EVITA_UL_ICS_40_S_O2_DE_2.29.207.1-1.92.207.3_release_272963z2vl7cdycjk01nm4.zip
Click to expand...
Click to collapse
Those are ota updates... A ruu is an exe file that is run from Windows
Sent from my HTC One XL using xda app-developers app

The available o2 RUUs are too old
Sent from my One X using Tapatalk 4

So you run an older RUU and then take OTAs, you can't just flash OTA files, it won't work. You need to return the phone to being completely stock first though, s-on, original CID, locked bootloader, original recovery.
Sent from my Evita

I tried this file: RUU_EVITA_UL_ICS_40_S_O2_DE_2.29.207.1_Radio_0.19as.32.09.20_3_10.107.32.25L_release_272946_signed.exe, it didn't work (contentual: Error 170, USB Error)
The XL is S-ON (never was S-OFF), bootloader is relocked (fastboot oem lock), then I launched the RUU.exe.
What I read is, that I can't flash older ROMs (what ever that means). So, what can I do if the o2-RUUs are to old? Can I downgrade the HBOOT?
edit: Can I downgrade HBOOT with the JET (http://forum.xda-developers.com/showthread.php?t=1940512) and then ran a RUU?

from maximus hd to cyanogenmod 11

hi guys, i was undecided about the rom. im on maximus hd now but i want also kitkat, and so install the last snapshot (the monthly cyanogenmod release). what do you think? and what i have to do now for install it? i wnat to go back to 2.15 hboot, please help me

Anyone?
Sent from my HTC One S using XDA Premium 4 mobile app

no one can help me?

Maybe this can help you to go back to hboot 2.15.
For CM follow the instructions in the first post of this thread.
The latest snapshot can be found here. GAPPS can be found e.g. here or here.

I'm a bit confused.
Currently on Hboot 2.16 , S-Off, TWRP 2.8.0.1 and maxumiusHD.
Can I install official CM 10.2?

CaptainMaki said:
I'm a bit confused.
Currently on Hboot 2.16 , S-Off, TWRP 2.8.0.1 and maxumiusHD.
Can I install official CM 10.2?
Click to expand...
Click to collapse
CM 10.2 doesn't support hboot 2.16. BTW using the search function doesn't hurt.

Flippy498 said:
CM 10.2 doesn't support hboot 2.16. BTW using the search function doesn't hurt.
Click to expand...
Click to collapse
We want to go back to 2.15
Sent from my HTC One S using XDA Premium 4 mobile app

Yeah, I understood that. All you got to do is following the instructions in the first link I posted in my first answer. ?

in an italian forum i have see that i can flash the hboot for downgrade, without installing the RUU.. here the link if you understand something http://www.androidiani.com/forum/ht.../354323-guida-s4-upgrade-downgrade-hboot.html
so what i have to do?

djinn0 said:
in an italian forum i have see that i can flash the hboot for downgrade, without installing the RUU.. here the link if you understand something http://www.androidiani.com/forum/ht.../354323-guida-s4-upgrade-downgrade-hboot.html
so what i have to do?
Click to expand...
Click to collapse
Well, I've always been using a RUU if I wanted to downgrade so I don't know which way is the best. All I can say is that I never had any problems with downgrading by using RUU_Ville_U_ICS_40_S_HTC_Europe_2.31.401.5_Radio_1.06es.50.02.31_10.09a.50.04L_release_275655_signed.exe and the CID HTC__102. Maybe it's not the fastest way (you need to upgrade by official OTA's afterwards to get hboot 2.15) but it works.

I have to change the cid for return to 2.15?
Sent from my HTC One S using XDA Premium 4 mobile app

djinn0 said:
I have to change the cid for return to 2.15?
Sent from my HTC One S using XDA Premium 4 mobile app
Click to expand...
Click to collapse
If you use RUU_Ville_U_ICS_40_S_HTC_Europe_2.31.401.5_Radio_1 .06es.50.02.31_10.09a.50.04L_release_275655_signed.exe for downgrading then yes. Otherwise you'll brick your phone by installing the official OTA's while you are on CID 11111111.

So first installing the RUU then return to my cid? And then i can install cm?
Sent from my HTC One S using XDA Premium 4 mobile app

1. Return to your CID (in my case HTC__102)
2. Use the corresponding RUU (in my case RUU_Ville_U_ICS_40_S_HTC_Europe_2.31.401.5_Radio_1 .06es.50.02.31_10.09a.50.04L_release_275655_signed.exe; your Phone has to be in fastboot USB mode; maybe you have to relock your bootloader)
3. Install official OTA's to get from ICS to JB with hboot 2.15 (with CID 11111111 this step will brick your phone)
4. Unlock bootloader if needed
5. Return to Super CID if you want (actually not needed since you only need it for facepalm s-off as far as I know)
6. Flash TWRP/CWM (I prefer TWRP)
7. Flash latest CM snapshot
8. Flash GAPPS
9. Enjoy
It's not the fastest way but I never had problems as the 3G loss that is mentioned in some threads. More or less these are the same steps that are mentioned in the link I posted in my first answer.

And If i install the jb ruu?
Sent from my HTC One S using XDA Premium 4 mobile app

I've never used any other RUU than the one I mentioned above. So I don't know whether a JB RUU can brick your phone while you are on Super CID. Nevertheless the steps you need to do are the same with a JB RUU except that you can leave out the installation of the original OTA's.

Flippy498 said:
I've never used any other RUU than the one I mentioned above. So I don't know whether a JB RUU can brick your phone while you are on Super CID. Nevertheless the steps you need to do are the same with a JB RUU except that you can leave out the installation of the original OTA's.
Click to expand...
Click to collapse
i have sucessfully installed the ICS RUU but now my bootloader is 1.14 not 2.15... it automatically get updated with the jb OTA?

Flippy498 said:
1. Return to your CID (in my case HTC__102)
2. Use the corresponding RUU (in my case RUU_Ville_U_ICS_40_S_HTC_Europe_2.31.401.5_Radio_1 .06es.50.02.31_10.09a.50.04L_release_275655_signed.exe; your Phone has to be in fastboot USB mode; maybe you have to relock your bootloader)
3. Install official OTA's to get from ICS to JB with hboot 2.15 (with CID 11111111 this step will brick your phone)
4. Unlock bootloader if needed
5. Return to Super CID if you want (actually not needed since you only need it for facepalm s-off as far as I know)
6. Flash TWRP/CWM (I prefer TWRP)
7. Flash latest CM snapshot
8. Flash GAPPS
9. Enjoy
Click to expand...
Click to collapse
See step 3. Just download them via "About" -> "Software updates" in the system menu.