So, I'm currently S-OFF, bootloader unlocked, SuperCID, etc. I was originally on the 1.73 base/RUU, and then upgraded using the 3.18 RUU. I would like to revert back to the 1.73 RUU. Since I'm S-OFF, can I simply run the 1.73 RUU (the older version) without doing anything fancy? I just plug my phone up and run the 1.73 RUU, even though it's a MUCH older RUU than the one I last used?
Thanks.
Yes.
Though I did not have supercid when I did it. You should be able to with s-off no problem.
If you're worried just fastboot OEM writecid "whatever your cid was originally" minus the ""
Sent from my One X using xda app-developers app
exad said:
Yes.
Though I did not have supercid when I did it. You should be able to with s-off no problem.
If you're worried just fastboot OEM writecid "whatever your cid was originally" minus the ""
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Ok, and do I need to relock my bootloader before running the RUU if I'm S-OFF?
No, don't
Sent from my One X using xda app-developers app
i have s-off with 3.18 firmwares on it running custom aosp roms. i find the 3.18 radio to be the best for at&t. since i have ruu i haven't reverted hboot or anything besides downgrading the touchscreen. if you run aosp roms i would flash the cm10 3.18 cwm flashable zip, since most use the older 2.20 radio.
DvineLord said:
i have s-off with 3.18 firmwares on it running custom aosp roms. i find the 3.18 radio to be the best for at&t. since i have ruu i haven't reverted hboot or anything besides downgrading the touchscreen. if you run aosp roms i would flash the cm10 3.18 cwm flashable zip, since most use the older 2.20 radio.
Click to expand...
Click to collapse
I also have S-OFF , unlocked and go back and forth between the 3.18 and older RUU's , then flash radios that suit my area. At the time on 2.20, Clean Rom 5.1, with 3.18 radio. As I understand most posts on the deal, once S-OFF , you can do most anything as long as its a RUU for the particular phone , in this case the HTC one x Evita.
Related
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)
Hi everyone.
I've been having very bad problems with by battery life lately (I mean BAD) across nearly virtually all ROMs and configurations... so I'm thinking it's time to RUU and see if it solves the problem before sending my phone off.
Currently, I'm bootloader unlocked, SuperCID, S-OFF, rooted, custom recovery, etc.
I've done an RUU before, before I got S-OFF, and I know that if you have an unlocked bootloader you have to 're-lock' it before running the RUU.
Since I'm S-OFF, are there any other prerequisites to RUUing?
Can I simply re-lock my bootloader, RUU, then unlock my bootloader, root, and I'll be good?
And will I remain S-OFF throughout the RUU? Will my S-OFF mess anything up?
Hydromea said:
Hi everyone.
I've been having very bad problems with by battery life lately (I mean BAD) across nearly virtually all ROMs and configurations... so I'm thinking it's time to RUU and see if it solves the problem before sending my phone off.
Currently, I'm bootloader unlocked, SuperCID, S-OFF, rooted, custom recovery, etc.
I've done an RUU before, before I got S-OFF, and I know that if you have an unlocked bootloader you have to 're-lock' it before running the RUU.
Since I'm S-OFF, are there any other prerequisites to RUUing?
Can I simply re-lock my bootloader, RUU, then unlock my bootloader, root, and I'll be good?
And will I remain S-OFF throughout the RUU? Will my S-OFF mess anything up?
Click to expand...
Click to collapse
From what i understand, you don't even need to relock your bootloader, while S-OFF, but I did it anyway when I RUU'd.
RUUing will not mess with S-OFF or anything.
After RUUing, I also Took the latest OTA from Telus (I'm with Telus, you may not be) And I noticed ROMs using a 3.17 base run much smoother and with less bugs. I did not, however, notice much difference in battery life with AOSP roms.
Hope this helps ya
exad said:
From what i understand, you don't even need to relock your bootloader, while S-OFF, but I did it anyway when I RUU'd.
RUUing will not mess with S-OFF or anything.
After RUUing, I also Took the latest OTA from Telus (I'm with Telus, you may not be) And I noticed ROM using a 3.17 base run much smoother and with less bugs. I did not, however, notice much difference in battery life with AOSP roms.
Hope this helps ya
Click to expand...
Click to collapse
OK, so you mean that after RUUing, you took the OTA, and Sense 3.17 ROMs ran smoother and better than before you took the OTA?
I'm thinking about using the 3.18 RUU. Since I'm S-OFF, am I safe to use any RUU I want since I can revert easily?
As in, I can safely use the 3.18 RUU (which is currently regarded unrootable), and if it turns out to be bad I can just go back to an older RUU?
Basically, will using the 3.18 OTA/RUU mess anything up if I'm S-OFF?
Hydromea said:
OK, so you mean that after RUUing, you took the OTA, and Sense 3.17 ROMs ran smoother and better than before you took the OTA?
I'm thinking about using the 3.18 RUU. Since I'm S-OFF, am I safe to use any RUU I want since I can revert easily?
As in, I can safely use the 3.18 RUU (which is currently regarded unrootable), and if it turns out to be bad I can just go back to an older RUU?
Basically, will using the 3.18 OTA/RUU mess anything up if I'm S-OFF?
Click to expand...
Click to collapse
Yes, I did find Viper and clean rom both ran much better than they did previously.
I'm sorry, I don't know about the 3.18 OTA... Hopefully someone else here can shed more light?
Theoretically, Since you're S-OFF, you should be able to update just fine. I haven't seen anyone actually do it yet though. I would test if I could.
I didn't relock I just ruu'd and after the process was done I just pushed twrp to my phone in fastboot and flashed viper. Only took a few mins top
Sent from my Elemental Venomized S-off HTC One XL
If I decide to update to a complete 3.18 base, is it better to use a 3.18 RUU or OTA? And if I use the OTA, how exactly do I 'flash' it (it's a ZIP file). Do I just put it on the top level of my internal storage, and boot into recovery, and select 'update' or whatever?
Hydromea said:
If I decide to update to a complete 3.18 base, is it better to use a 3.18 RUU or OTA? And if I use the OTA, how exactly do I 'flash' it (it's a ZIP file). Do I just put it on the top level of my internal storage, and boot into recovery, and select 'update' or whatever?
Click to expand...
Click to collapse
I used the ruu for 3.18 and haven't regretted it yet. My battery life has gotten much better.
Sent from my Elemental Venomized S-off HTC One XL
OTA just downloads through the phone. IE: Go to settings about phone, check for updates and it updates. You don't have to do anything else, it prompts you and updates for you.
If there was already a 3.18 RUU that would be the fastest way. Telus is slow with releasing RUU's so I had to use ICS myself. Neither way should give you trouble.
Here's to hoping my phone doesn't brick. Running the RUU as we speak (bootloader unlocked, s-off, super-cid)...
Well it worked. Twrp 2.2.2.0 doesn't though. Ugh, 2.3x is so ugly.
Sent from my HTC One X
ECEXCURSION said:
Well it worked. Twrp 2.2.2.0 doesn't though. Ugh, 2.3x is so ugly.
Sent from my HTC One X
Click to expand...
Click to collapse
Did you use the 3.18 RUU?
ECEXCURSION said:
Well it worked. Twrp 2.2.2.0 doesn't though. Ugh, 2.3x is so ugly.
Sent from my HTC One X
Click to expand...
Click to collapse
If you're hellbent on TWRP 2.2.2.0, downgrade the touchscreen firmware.
Hydromea said:
Did you use the 3.18 RUU?
Click to expand...
Click to collapse
Yeah I did. Maybe I'll look into downgrading the touchscreen firmware.
Sent from my HTC One X
If I'm S-OFF and use the 3.18 RUU, in order to use AOSP-based 4.2.2 ROMs, will I have to downgrade my touchscreen firmware?
Hydromea said:
If I'm S-OFF and use the 3.18 RUU, in order to use AOSP-based 4.2.2 ROMs, will I have to downgrade my touchscreen firmware?
Click to expand...
Click to collapse
yes you will here is how
http://forum.xda-developers.com/showthread.php?t=2159863
If I use the 3.18 RUU, how will I obtain root afterwards?
I'm already S-OFF and bootloader unlocked BTW.
And since I'm S-OFF, can I easily revert back to an older RUU without any extra steps?
Hydromea said:
If I use the 3.18 RUU, how will I obtain root afterwards?
I'm already S-OFF and bootloader unlocked BTW.
And since I'm S-OFF, can I easily revert back to an older RUU without any extra steps?
Click to expand...
Click to collapse
after ruu just fastboot flash a recovery transfer a rooted rom to your phone and flash in recovery
and with s-off you can run any ruu dont even need to relock bootloader
jerrycoffman45 said:
after ruu just fastboot flash a recovery transfer a rooted rom to your phone and flash in recovery
and with s-off you can run any ruu dont even need to relock bootloader
Click to expand...
Click to collapse
What he said lol
Sent from my Elemental Venomized S-off HTC One XL
this is all great info i would like to thank all of you
does this go for the rogers model as well?
babarnard said:
this is all great info i would like to thank all of you
does this go for the rogers model as well?
Click to expand...
Click to collapse
Yes.
Just an update. I successfully ruu'd to 3.18, downgraded hboot to 1.09, downgraded the touchscreen firmware, installed twrp 2.2.2.0 and all is well.
I'm sort of back where I started but maybe something good has come of it.
Sent from my HTC One X
I cannot boot into ROM, but stuck at Bootloader. And I'm relocked.
The only thing I have is Fastboot USB.
I would like to RUU into a Stock ROM. How to do so?
Well ruu should be pretty self explanatory. If you are in the boot loader just run the ruu. Since you are relocked shouldn't take much work. Are you s-off? Why not just grab an AT&T ROM and flash it over. Sure it will be rooted, but delete the super user app
Sent from my Carbon-ize Evita using xda-developers app
Yeah, I just figured it. RUU was some executable file. I thought it was more complicated. No I'll just leave it like this and not S-Off, thanks. Apparently I'm not more than 30% battery though. But how do I see the battery from the Bootloader screen?
I dont believe you can. Only from recovery. Just let it charge for about 20-30 mins and you should be good
Sent from my Carbon-ize Evita using xda-developers app
If you have supercid and s-on running a ruu will brick your phone just a warning
Sent from my HTC One X using Tapatalk 2
How do I check if I have SuperCID or not?
And apparently the device name is GT-9100 which seems wrong...?
There is command in fastboot I think it is fastboot get cid but not sure do you have a att phone
Sent from my HTC One X using Tapatalk 2
Nope, I do not. I do not need to worry about that then.
No you should be ok att phones are the only ones that had to change there cids to unlock bootloader
Sent from my HTC One X using Tapatalk 2
Fastboot oem readcid
Sent from my One X using xda app-developers app
exad said:
Fastboot oem readcid
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Thanks couldn't remember what it was
Sent from my HTC One X using Tapatalk 2
Oh no! Can anyone please help me?
None of the RUUs work.
I'm Asian and I tried all:
1.88.707.2 ( Error 170, bad USB )
2.23.707.2 ( Error 170 )
This is the only one that I could select ROM and upgrade.
3.17.707.1 ( Less than 30% error is result of previous fail, so reboot. Actual Error 155 )
And I'm S-ON
hboot 1.09
radio 0.17a.32.09.16_2
OpenDSP - What's this and is it useful for my situation?
eMMC - boot
Apr 2 2012, 21:08:21
I think probably I can only install 3.17 RUU is because my last working ROM was CM10.1. After that I tried Sense ROMs but many failed hence I thought of doing Relock and RUU.
Is there any other thing I can do in my bootloader state? I tried Factory Reset.
Is it possible I attain S-OFF from here and flash recovery and flash OTA from there?
Or even better yet, can I try doing OTA from this state?
Aerodeath said:
And I'm S-ON
hboot 1.09
radio 0.17a.32.09.16_2
OpenDSP - What's this and is it useful for my situation?
eMMC - boot
Apr 2 2012, 21:08:21
I think probably I can only install 3.17 RUU is because my last working ROM was CM10.1. After that I tried Sense ROMs but many failed hence I thought of doing Relock and RUU.
Is there any other thing I can do in my bootloader state? I tried Factory Reset.
Is it possible I attain S-OFF from here and flash recovery and flash OTA from there?
Or even better yet, can I try doing OTA from this state?
Click to expand...
Click to collapse
I thought if you ran the ruu with s on you could brick...just obtain s off and then run the ruu
Sent from my Carbon-ize Evita using xda-developers app
I can't successfully S-OFF because I can't get into Android, stuck at bootloader.
And I'm not on AT&T, I don't need superCID and I can't change it to 11111111 either...
My CID is HTC__044
version-main is 1.88.707.2
Bootloader relocked
hBoot now 2.14?!
RUU_Evita_UL_hTC_Asia_WWE_1.88.707.2_R3_Radio_0.17a.32.09.16_2_10.88.32.17L_release_263455_signed should work but it didn't...
Never mind, everything seems to be working now.
It seemed that my hboot was too low to attempt RUU_EVITA_UL_JB_45_S_hTC_Asia_WWE_3.17.707.1_Radio_0.23a.32.09.29_10.128.32.34a_release_298958_signed and Running as Administrator helped too.
Aerodeath said:
I can't successfully S-OFF because I can't get into Android, stuck at bootloader.
And I'm not on AT&T, I don't need superCID and I can't change it to 11111111 either...
My CID is HTC__044
version-main is 1.88.707.2
Bootloader relocked
hBoot now 2.14?!
RUU_Evita_UL_hTC_Asia_WWE_1.88.707.2_R3_Radio_0.17a.32.09.16_2_10.88.32.17L_release_263455_signed should work but it didn't...
Never mind, everything seems to be working now.
It seemed that my hboot was too low to attempt RUU_EVITA_UL_JB_45_S_hTC_Asia_WWE_3.17.707.1_Radio_0.23a.32.09.29_10.128.32.34a_release_298958_signed and Running as Administrator helped too.
Click to expand...
Click to collapse
I'm telling you this because I don't want you to go through what I did.
I'm on a telus one x, did not need super cid to unlock my bootloader. I relocked and flashed stock recovery, ran RUU. The RUU completed successfully but my phone was a full brick. Only JTAG would have saved it.
If you want to RUU, re-unlock your bootloader, flash recovery, flash stock rooted sense rom, hex edit your CID to 11111111 and S-OFF, then RUU. It's a lot safer now that you've unlocked your bootloader and rooted.
exad said:
I'm telling you this because I don't want you to go through what I did.
I'm on a telus one x, did not need super cid to unlock my bootloader. I relocked and flashed stock recovery, ran RUU. The RUU completed successfully but my phone was a full brick. Only JTAG would have saved it.
If you want to RUU, re-unlock your bootloader, flash recovery, flash stock rooted sense rom, hex edit your CID to 11111111 and S-OFF, then RUU. It's a lot safer now that you've unlocked your bootloader and rooted.
Click to expand...
Click to collapse
It's okay, I was running an international One XL, and luckily RUU was smooth, now the problem is solved and my phone has been sold and changed hands .
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
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?