Database Info

[Q] Desire S Need to get back to stock on 3 UK

Hi everyone,
The microphone on my beloved Desire S has packed in and I need to return in for warranty repair.
It is currently rooted running Virtuous Unity. I don't think I should send it back with a custom ROM on it.
I would like to get it back to factory state before I send it, including HBOOT and recovery, but I can't find an RUU for 3UK.
Does anyone have any ideas how I can go about this?

iTroll said:
Hi everyone,
The microphone on my beloved Desire S has packed in and I need to return in for warranty repair.
It is currently rooted running Virtuous Unity. I don't think I should send it back with a custom ROM on it.
I would like to get it back to factory state before I send it, including HBOOT and recovery, but I can't find an RUU for 3UK.
Does anyone have any ideas how I can go about this?
Click to expand...
Click to collapse
Daft question, but, did you perform a full nandroid backup before you flashed you first custom which you still have on SD?

If not see post #1 of this thread All shipped ROMs
I believe that this RUU might suit...
RUU_Saga_H3G_UK_1.31.771.1_Radio_20.28b.30.0805U_3 8.03.02.14_M_release
further threads explaining how to
[Tutorial] How to restore stock ROM and S-On after AlphaRevX S-Off [31 july 11]
http://forum.xda-developers.com/showthread.php?t=1187231
along with many other useful info in the INDEX sticky thread within the development forum.

ben_pyett said:
If not see post #1 of this thread All shipped ROMs
I believe that this RUU might suit...
RUU_Saga_H3G_UK_1.31.771.1_Radio_20.28b.30.0805U_3 8.03.02.14_M_release
Click to expand...
Click to collapse
and if yes? how is the backup helping?

Nomader0 said:
and if yes? how is the backup helping?
Click to expand...
Click to collapse
Backup is helping in a couple of ways:
As it will be the actual stock version of ROM that he was supplied with it will enable him to confirm exactly which version of ROM that he'll need to return to etc.
Also, depending on how 'eagle eyed' the person in the repair centre is he may only need to return recovery and hboot back to original and simply remove the superuser application from it rather than re-flash RUU.

That's really great info guys!
So from reading the tutorial it looks like HBOOT is not replaced by the RUU and has to be restored manually with adb, is that right?
Thanks a lot!

iTroll said:
That's really great info guys!
So from reading the tutorial it looks like HBOOT is not replaced by the RUU and has to be restored manually with adb, is that right?
Thanks a lot!
Click to expand...
Click to collapse
I'm not 100% about this....But, I believe that some RUUs do replace the HBOOT, but, they're only ever able to upgrade the HBOOT version, so if you need to downgrade the hboot version, which you may need to do if you're software S-OFF'd. Then adb can be used to downgrade the HBOOT version as you've seen.
Which HBOOT version do you have?

ben_pyett said:
I'm not 100% about this....But, I believe that some RUUs do replace the HBOOT, but, they're only ever able to upgrade the HBOOT version, so if you need to downgrade the hboot version, which you may need to do if you're software S-OFF'd. Then adb can be used to downgrade the HBOOT version as you've seen.
Which HBOOT version do you have?
Click to expand...
Click to collapse
HBOOT-6.98.1002 (from AlphaRevX)
RADIO-38.03.02.14_M
The HBOOT linked in the tutorial above is 0.98.0000 right?
Will that work on mine?

iTroll said:
HBOOT-6.98.1002 (from AlphaRevX)
RADIO-38.03.02.14_M
The HBOOT linked in the tutorial above is 0.98.0000 right?
Will that work on mine?
Click to expand...
Click to collapse
Yes, that's correct version, follow as the tutorial says.....

[GUIDE][07/01] Flashing ICS FIRMWARE 3.12 base img files.

DISCLAIMER. Do it at your own risk.. I am not responsible for bricks....bla bla bla, usual stuff.
If in doubt-STAY AWAY!
Q/A First.
Do I HAVE to flash this FW? - YES, if you want to flash ICS 4.0.3 based rom. If not, it just won't boot. Latest firmware works with previous (2.3.4,2.3.5,4.0.1) roms.
Do I NEED SuperCID? - YES, it will help in case you need to revert and if your CID is not on the update.zip list
Will I lose S-OFF? - NO
Can I use this FW with earlier builds? - YES
Will I lose fastboot commands like flash splash1? - Yes
Is it safe? Never 100% but no fails so far. Flash at your own risk
Can I revert to previous hboot, like 1.17? Yes, make sure you are superCID.
Any disadvantages? None so far
Any advantages? More optimised fw/drivers for ICS. Users report faster ROM operation.
Why does it say ***LOCKED*** in bootloader? Because hboot is locked (don't panic)
Can I go back to **REVOLUTIONARY**? Yes, flash 1.17 HBOOT at the bottom of OP.
HOW TO
0. Make sure you are S-OFF and superCID. Check HERE
1. Download zip from HERE Credits to rmk40, this is FW I used).
2. Do nandroid backup.
3. Copy/paste PG58xxxxx to the root of your microSD
4. Make sure MD5 match!!! MD5 checker I use HERE
4. Make sure MD5 match again!!!
4. And once again, make sure MD5 match.
5. Reboot into bootloader (if you don't know how to do it, don't do any of that at all)
6. microSD will be scanned and will ask you if you want to update, press +vol for YES
7. Follow onscreen instructions.
8. Now just pull sd card out if you don't have microSD reader or delete PG58xxxx if you do. PG58 will prevent you from going into recovery if phone sees it.
9. Reboot into bootloader-go to recovery
10. Put your SD card back in
11. Reboot or flash new rom
12. You are done. Just delete that PG58 file so it doesn't stop you getting into recovery again.
REVERT TO 1.17 HBOOT
ziggy1001 said:
Direct link with MD5
http://forum.xda-developers.com/showpost.php?p=20681060&postcount=22
Click to expand...
Click to collapse
Paste on root of SD card, make sure MD5 matches. Repeat update from bootloader (steps 1-12 from above) and you should be done.
If anyone has anything to add, feel free.
Remember, if you flash RUU, then process is slightly different and will most likely involve unlocking via HTCDEV (haven't really looked into it)

This is for all Sensation's, right?

aNYthing24 said:
This is for all Sensation's, right?
Click to expand...
Click to collapse
Indeed. Mike provided img files from both RUUs. I'm pretty sure it's safe to mix and match, since we ran 1.73 RUUs on normal Senny, but wouldn't recommend risking it just in case. But there is always a brave one ... LOL Who is it gonna be this time?

I've already followed the steps as in mike1986's thread and all went well, but what is the benefit of reverting to 1.17 HBOOT?

piplewis said:
I've already followed the steps as in mike1986's thread and all went well, but what is the benefit of reverting to 1.17 HBOOT?
Click to expand...
Click to collapse
Advanced fastboot commands

nice work on the thread mate, do you want to include a note that mikes files will update the radio too, just make sure everyone is clear on what is updates

Does it improve performance noticeably? I'm just a bit overwhelmed, sorry.

Hawke84 said:
nice work on the thread mate, do you want to include a note that mikes files will update the radio too, just make sure everyone is clear on what is updates
Click to expand...
Click to collapse
So there will be no possibility of downgrading the radio?...our i have to revert to 1.17 to flash older radios?
I have 10.56 and i m satisfied with it...

jjdoctor said:
So there will be no possibility of downgrading the radio?...our i have to revert to 1.17 to flash older radios?
I have 10.56 and i m satisfied with it...
Click to expand...
Click to collapse
You can still do it via PG58 update, but not via fatboot flash radio radio_image_name.img

I want to try this so bad, but I am scared as heck! What do we need to know before doing this? Such as, what do we risk other than an all out brick? Will we be able to go back to what we have now?
Matt

tinky1 said:
Find 1.17 HBOOT in PG58xxxx in THIS THREAD (provided by ziggy1001)
)
Click to expand...
Click to collapse
Direct link with MD5
http://forum.xda-developers.com/showpost.php?p=20681060&postcount=22

Looks like it worked for me. I am restoring a ROM right now. After that, ill revert back to the previous bootloader. So far, so good!
So now, where do you guys see the improvements?
Matt

I just tried to flash it but it have me CID error... I used supercid by this method
http://forum.xda-developers.com/showthread.php?t=1192630
What could be wrong?

jjdoctor said:
I just tried to flash it but it have me CID error... I used supercid by this method
http://forum.xda-developers.com/showthread.php?t=1192630
What could be wrong?
Click to expand...
Click to collapse
I am getting ready to flash it, but I did supercid by the method in the sticky-noted post near the top of the Sensation forums.
[Guide] to Installing S-off, Unlocking, ClockWork, Root, SuperCID & S-on

jjdoctor said:
I just tried to flash it but it have me CID error... I used supercid by this method
http://forum.xda-developers.com/showthread.php?t=1192630
What could be wrong?
Click to expand...
Click to collapse
Does your bootloader screen show **locked** in pink color ?

hsnmz said:
Does your bootloader screen show **locked** in pink color ?
Click to expand...
Click to collapse
Yes it shows Locked in pink... My hboot is now 1.20
My radio didn't upgrade... I still have 10.56....
I flashed it over Ultimite ROM... i thought it will erase my ROM but nothing changed....:-/
It flashed everything but showed cid error in last one... I don't know what was it....
So now i have to go back to 1.17, supercid using adb and fish 1.20 again?
I supercid using terminal emulator... I guess that didn't work...

jjdoctor said:
I supercid using terminal emulator... I guess that didn't work...
Click to expand...
Click to collapse
Wait, what?!
You tried to SuperCID via Terminal Emulator, while the phone was running? oO
What's wrong with following the instructions in the stickied guide and using adb?

Never in my life i used adb stuff... :-/
never tried to learn it either... But i guess i have to learn it now..
Now tell me what to do?
should i download hboot 1.17, flash it and then reflash 1.20 after supercid?

jjdoctor said:
Never in my life i used adb stuff... :-/
never tried to learn it either... But i guess i have to learn it now..
Now tell me what to do?
should i download hboot 1.17, flash it and then reflash 1.20 after supercid?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1192300 this is the thread I have followed time and time again with success step 4 is to do cid

is this firmware just relevent to ics roms or can it be used on 3.0/3.5 roms??????

Root 3.18 idea

Is there a way we can erase entire system OS, like a rooted device can using TWRP? If so after erasing system OS we can use older RUU? Afterwards then unlock bootloader and root, mission accomplished root successful. But does anyone know if you can do the erase system OS through the Command Prompt on platform-tools. If so how!? We might not be able to root 3.18 AT&T One X because AT&T are jerks but once we find a way to downgrade problem solved, maby that's the loop hole into the software I just don't know how to do it.

Wrong section
---------- Post added at 10:30 PM ---------- Previous post was at 10:29 PM ----------
And the answer is no ..

a box of kittens said:
Wrong section
---------- Post added at 10:30 PM ---------- Previous post was at 10:29 PM ----------
And the answer is no ..
Click to expand...
Click to collapse
Oops sorry about that. Can a moderator move it? Also your positive it cant be done?

Techinstein said:
Oops sorry about that. Can a moderator move it? Also your positive it cant be done?
Click to expand...
Click to collapse
no this is not going to work. You need root to be able to do anything like this, and this is not a way to root.

Erasing the OS wont make a difference, RUU contains everything including my grandmothers panties, not just a OS.

XsMagical said:
Erasing the OS wont make a difference, RUU contains everything including my grandmothers panties, not just a OS.
Click to expand...
Click to collapse
In that case can't you I or someone brick the one x on purpose. Then use the RUU? Then root and unlock and then mission accomplished?

Techinstein said:
In that case can't you I or someone brick the one x on purpose. Then use the RUU? Then root and unlock and then mission accomplished?
Click to expand...
Click to collapse
Nope BC without perm root you can only ruu to the version you were previously on.
Sent from my HTC One XL using Tapatalk 2

InflatedTitan said:
Nope BC without perm root you can only ruu to the version you were previously on.
Sent from my HTC One XL using Tapatalk 2
Click to expand...
Click to collapse
I used to be on ICS 1.14 then upgraded , but i tried factory reset and nothing happened. Well ruu 2.20 work to downgrade for me? Or other people with the same problem as me at least?

So you want to root your phone or downgrade from 3.18? Do you want to use CM rom or what?

jun10rocks said:
So you want to root your phone or downgrade from 3.18? Do you want to use CM rom or what?
Click to expand...
Click to collapse
I want to downgrade back. Then root. If you know how thanks! As said above I hade ICS before JB then it updat
ed to 2.14 and 3.18 firmware.

Techinstein said:
I want to downgrade back. Then root. If you know how thanks! As said above I hade ICS before JB then it updat
ed to 2.14 and 3.18 firmware.
Click to expand...
Click to collapse
You can't downgrade from 3.18 but some roms are based on older versions. What's wrong with 3.18?

jun10rocks said:
You can't downgrade from 3.18 but some roms are based on older versions. What's wrong with 3.18?
Click to expand...
Click to collapse
if you previously had s-off before the ota then you can unlock/root/and flash i downgraded to ics 2.20 after jb update no issues

Idea but I'm no hacker so I could be very very wrong.......
Techinstein said:
Is there a way we can erase entire system OS, like a rooted device can using TWRP? If so after erasing system OS we can use older RUU? Afterwards then unlock bootloader and root, mission accomplished root successful. But does anyone know if you can do the erase system OS through the Command Prompt on platform-tools. If so how!? We might not be able to root 3.18 AT&T One X because AT&T are jerks but once we find a way to downgrade problem solved, maby that's the loop hole into the software I just don't know how to do it.
Click to expand...
Click to collapse
As far as I know the only reason you can't use lower ruus is because of the hboot.(could be wrong)
Also i think you can unlock bootloader with root and maybe get twrp (might be wrong)
So use this to downgrade to 1.09 http://forum.xda-developers.com/showthread.php?t=1982442 (not sure it will work for your hboot)
then use the hboot 1.09's respective ruu.. I think 1.85.
root 1.85 then wham rooted.
But this is just a guess made by a guy who doesn't do these things. I'm honestly more of a hardware guy than software.
But the only to find out is for a guy who knows about software to tell me I'm an idiot or for you to try it one an actual xl.

Unless you're s-off you CAN NOT ruu down.... Only up my brother... OP hasn't been 100% clear if he's s-off or not....
If he has a telus or rogers phone he can unlock the bootloader without root. ATT models HAVE to have root access, if not htcdev will let you know your device isn't supported.
If you were unlocked BEFORE taking the update, should you be able to still have held on to the original unlock token you might be able to fastboot it again and unlock, fastboot twrp, flash rom or SU..... Although I can almost guarantee I'm wrong lol
If you were rooted, unlocked, and took the ota you should have bricked. So is there a chance you had s-off?
Sent from my One X using Tapatalk 2

oops forgot one thing
boss1019 said:
As far as I know the only reason you can't use lower ruus is because of the hboot.(could be wrong)
Also i think you can unlock bootloader with root and maybe get twrp (might be wrong)
So use this to downgrade to 1.09 http://forum.xda-developers.com/showthread.php?t=1982442 (not sure it will work for your hboot)
then use the hboot 1.09's respective ruu.. I think 1.85.
root 1.85 then wham rooted.
But this is just a guess made by a guy who doesn't do these things. I'm honestly more of a hardware guy than software.
But the only to find out is for a guy who knows about software to tell me I'm an idiot or for you to try it one an actual xl.
Click to expand...
Click to collapse
oops i forgot makesure you have a linux installation everything you need to have is in the thread

does he want to downgrade to root? because 3.18 is rootable

jun10rocks said:
does he want to downgrade to root? because 3.18 is rootable
Click to expand...
Click to collapse
As of right now 3.18 is not rootable
Sent from my HTC One X using xda app-developers app

Megadoug13 said:
As of right now 3.18 is not rootable
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
I updated to the 3.18 update and rooted the phone or was there a newer update because I got the update about 2 weeks ago.

InflatedTitan said:
Unless you're s-off you CAN NOT ruu down.... Only up my brother... OP hasn't been 100% clear if he's s-off or not....
If he has a telus or rogers phone he can unlock the bootloader without root. ATT models HAVE to have root access, if not htcdev will let you know your device isn't supported.
If you were unlocked BEFORE taking the update, should you be able to still have held on to the original unlock token you might be able to fastboot it again and unlock, fastboot twrp, flash rom or SU..... Although I can almost guarantee I'm wrong lol
If you were rooted, unlocked, and took the ota you should have bricked. So is there a chance you had s-off?
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
S-Off is the only reason i did not brick when running the 3.18 RUU on my current device also why not just hook up an otg cable with a pj83img.zip and flash a radio with a modified mainver in the android-info.txt? thats how i have meen modifying the mainver in almost every htc device since the Touch Diamond

The reason you can't wipe the whole phone is that important portions of the firmware are write-protected without s-off.
If you were s-off before, you haven't lost root, you just need to push your custom recovery back on and then flash a rooted rom.

What is the correct method to avoid brick?

Hi guys, I've been off from this forum for quite some time.....And I see alot of Dev along the way.....ok to the point.....I believe I have Hboot 1.09 rooted with superCID when I Did hex editing CWS__001 to 111111 (unlocked bootloader) now in order to update to newest firmware what is the best or the right way to do it? For everyone that success updated their phone without bricking it. A Guide that would be very much appreciated and link that's would be helpful for me or other user ......Thanks
Swyped from T3DRO1CS RedHoXence

What is the purpose of updating the firmware? If you just want to be on the latest Android 4.2.2 Sense 5 update you can flash one of the ROMs from our development section.
Sent from my Evita

ted77usa said:
Hi guys, I've been off from this forum for quite some time.....And I see alot of Dev along the way.....ok to the point.....I believe I have Hboot 1.09 rooted with
superCID (unlocked bootloader) now in order to update to newest firmware what is the best or the right way to do it? For everyone that success updated their phone without bricking it. A Guide that would be very much appreciated and link that's would be helpful for me or other user ......Thanks
Swyped from T3DRO1CS RedHoXence
Click to expand...
Click to collapse
Only real reason to upgrade with ruu is if you want to run certain cm10 roms. Being they require 2.14 hboot and certain firmware updates to run properly.
Sent from my HTC One XL using XDA Premium 4 mobile app

ted77usa said:
Hi guys, I've been off from this forum for quite some time.....And I see alot of Dev along the way.....ok to the point.....I believe I have Hboot 1.09 rooted with
superCID (unlocked bootloader) now in order to update to newest firmware what is the best or the right way to do it? For everyone that success updated their phone without bricking it. A Guide that would be very much appreciated and link that's would be helpful for me or other user ......Thanks
Swyped from T3DRO1CS RedHoXence
Click to expand...
Click to collapse
You just need to s-off, then run the ruu. You won't have to relock bootloader anymore before ruu anymore after you s-off, you just need to reflash recovery and flash your rom afterwards. S-off is super easy also takes only minutes.

DvineLord said:
You just need to s-off, then run the ruu. You won't have to relock bootloader anymore before ruu anymore after you s-off, you just need to reflash recovery and flash your rom afterwards. S-off is super easy also takes only minutes.
Click to expand...
Click to collapse
Any link please.....
timmaaa said:
What is the purpose of updating the firmware? If you just want to be on the latest Android 4.2.2 Sense 5 update you can flash one of the ROMs from our development section.
Sent from my Evita
Click to expand...
Click to collapse
Swyped from T3DRO1CS RedHoXence

Search for "Facepalm s-off" within our forum.
Sent from my Evita

ted77usa said:
Any link please.....
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1671237

timmaaa said:
Search for "Facepalm s-off" within our forum.
Sent from my Evita
Click to expand...
Click to collapse
redpoint73 said:
http://forum.xda-developers.com/showthread.php?t=1671237
Click to expand...
Click to collapse
So like u guys suggested.....either updated firmware to 2.15 or just flash the jb sense 5 ROM with beastmode kernel on top to overcome the signal drop and bootloop issue.
In case I'm fail.....would I be able to go back to bootloader using power + volume down? then recovery ...and restore my backup?
Swyped from T3DRO1CS RedHoXence

Yeah that's right, if you're going to update the firmware you'll need s-off first though. And yes, you can always get to the bootloader (and then recovery) issuing that button combo.
Sent from my Evita

timmaaa said:
Yeah that's right, if you're going to update the firmware you'll need s-off first though. And yes, you can always get to the bootloader (and then recovery) issuing that button combo.
Sent from my Evita
Click to expand...
Click to collapse
In order to do s-off I need supercid first right? And seem like I already have supercid when I did hex editing cws__001 to 111111 but it not show on my bootloader since I'm still S-ON right?
Is there any way to check if I'm supercid?
Swyped from T3DRO1CS RedHoXence

ted77usa said:
In case I'm fail.....would I be able to go back to recovery using power + volume down? And restore my backup?
Click to expand...
Click to collapse
That button combo gets you into bootloader. From there you can boot recovery. There is no button combo for recovery.
The 2 are related, but separate, and completely different things.
But yes, depending on what "fails" you should be able to get to recovery and restore your nandroid.
Keep in mind, that since you are S-on, you will need to flash boot.img for the ROM using fastboot, and same thing if you try to restore a nandroid. One more reason why S-off should be considered.
---------- Post added at 02:23 PM ---------- Previous post was at 02:21 PM ----------
ted77usa said:
In order to do s-off I need supercid first right? And seem like I already have supercid when I did hex editing cws__001 to 111111 but it not show on my bootloader since I'm still S-ON right?
Is there any way to check if I'm supercid?
Click to expand...
Click to collapse
I already answered that question when you posted it in another, non-related thread.

redpoint73 said:
That button combo gets you into bootloader. From there you can boot recovery. There is no button combo for recovery.
The 2 are related, but separate, and completely different things.
But yes, depending on what "fails" you should be able to get to recovery and restore your nandroid.
Keep in mind, that since you are S-on, you will need to flash boot.img for the ROM using fastboot, and same thing if you try to restore a nandroid. One more reason why S-off should be considered.
---------- Post added at 02:23 PM ---------- Previous post was at 02:21 PM ----------
I already answered that question when you posted it in another, non-related thread.
Click to expand...
Click to collapse
On nandroid backup files I saw boot.emms and recovery.emms files do do I still need to flash boot.img seperately incase in failing ? Or just restore my backup? I'm sorry that's y i reposted here and deleted the other post......
Swyped from T3DRO1CS RedHoXence

As long as you have a backup of the boot.img you can flash it via fastboot after restoring your system backup. You need to rename it to boot.img though. It's probably worth getting s-off to be honest, it only takes a few minutes and it'll save you a ton of hassle in the future.
Sent from my Evita

ted77usa said:
On nandroid backup files I saw boot.emms and recovery.emms files do do I still need to flash boot.img seperately incase in failing ?
Click to expand...
Click to collapse
You will still need to flash it with hboot.
boot.img will not flash in recovery, due to the s-on limitations.

redpoint73 said:
You will still need to flash it with hboot.
boot.img will not flash in recovery, due to the s-on limitations.
Click to expand...
Click to collapse
Just wondering why on ICS ROM I can restore my back up without flashing boot .img with S-ON?
Swyped from T3DRO1CS RedHoXence

ted77usa said:
Just wondering why on ICS ROM I can restore my back up without flashing boot .img with S-ON?
Click to expand...
Click to collapse
Because the boot.img that was still on the phone was the same (or similar enough) that it worked with the ROM that was on your nandroid.
BTW, of course I meant "flash with fastboot" not hboot.

he was on hboot 1.09 that is why he didn't need to flash boot.img separately.

DvineLord said:
he was on hboot 1.09 that is why he didn't need to flash boot.img separately.
Click to expand...
Click to collapse
That's what I thought......
Swyped from T3DRO1CS RedHoXence

DvineLord said:
he was on hboot 1.09 that is why he didn't need to flash boot.img separately.
Click to expand...
Click to collapse
Ahh, crap. Forgot that boot.img was flashable in recovery on hboot 1.09. That hboot was so long ago, and rarely pops up here anymore. And it was the hboot I was on at one time!
Forget everything I said about boot.img!
But if you ever update hboot to any version 1.14 or higher, everything I said becomes true again.
Sent from my HTC One XL using xda app-developers app

redpoint73 said:
Ahh, crap. Forgot that boot.img was flashable in recovery on hboot 1.09. That hboot was so long ago, and rarely pops up here anymore. And it was the hboot I was on at one time!
Forget everything I said about boot.img!
But if you ever update hboot to any version 1.14 or higher, everything I said becomes true again.
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
So your saying is better to keep my 1.09 hboot for now like timmaa said on earlier post.....just install JB ROM sense 5 and flash beastmode kernel on top of it if I have signal drop and reboot issue......
Swyped from T3DRO1CS RedHoXence

[Q]~[HELP] SuperCID, Unlocked, Rooted, and S-OFF, how to restore to stock AT&T ROM?

[Q]~[HELP] SuperCID, Unlocked, Rooted, and S-OFF, how to restore to stock AT&T ROM?
Hi, geeks,
For my AT&T HTC One X, I have followed you guys all the way to here now: with SuperCID, Bootloader Unlocked (via HTC Dev), Rooted of course, and S-OFF (with touchscreen firmware down-graded).
Now I want to go back to AT&T stock ROM to use the ISIS wallet. Could you please tell me how? I am worried that my phone get bricked!
Thank you so much!

You can just flash a stock at&t ROM which you'll find in our Android Development section. Or you can run the 3.18 RUU. This will also flash stock recovery, hboot, radio, and other firmware modules. The ROM is probably the better and easier option.
Sent from my Evita

Thank you, timmaaa. Do I need to lock the bootloader and so on? I saw it somewhere but can't find the link now.
timmaaa said:
You can just flash a stock at&t ROM which you'll find in our Android Development section. Or you can run the 3.18 RUU. This will also flash stock recovery, hboot, radio, and other firmware modules. The ROM is probably the better and easier option.
Sent from my Evita
Click to expand...
Click to collapse

To run the RUU? No, because you're s-off you don't need to do any of that, just run the RUU through Windows.
Sent from my Evita

timmaaa said:
To run the RUU? No, because you're s-off you don't need to do any of that, just run the RUU through Windows.
Sent from my Evita
Click to expand...
Click to collapse
I'm doing the same thing, but to attempt to trade in my phone. I assume that after running the RUU I should relock the bootloader. I want to get rid of the red text.
*EDIT* nevermind. didn't realize that the RUU clears out the *TAMPERED* flag and gets rid of the red text. should be all good now.

One more question, timmaaa: after flashing RUU, the recovery partition will be replaced with the stock recovery, and the S-OFF and boot loader will be kept as it is (based on what I learned from other posts of you). What if I need to flash CM again? I am confused because not many people are doing what I am. Thanks!
timmaaa said:
To run the RUU? No, because you're s-off you don't need to do any of that, just run the RUU through Windows.
Sent from my Evita
Click to expand...
Click to collapse

Yes, the RUU will install the stock recovery. Your phone will still be s-off and will still have an unlocked bootloader. All you need to do is install TWRP recovery again and then you can flash any ROM you like. Full instructions on how to install a recovery can be found in my How-To Guide For Beginners thread, link in my signature.
Sent from my Evita

Hi, timmaaa, I got a RUU error 155 when flashing 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.exe.
Seems I need to re-lock the bootloader, which I am reluctant to do. Do I miss anything?
timmaaa said:
Yes, the RUU will install the stock recovery. Your phone will still be s-off and will still have an unlocked bootloader. All you need to do is install TWRP recovery again and then you can flash any ROM you like. Full instructions on how to install a recovery can be found in my How-To Guide For Beginners thread, link in my signature.
Sent from my Evita
Click to expand...
Click to collapse

You don't need to relock if you're s-off. Are you using a 2.0 or 3.0 usb port? Are you using a HTC cable? Are you in fastboot mode? Have you uninstalled HTC Sync Manager?
Sent from my Evita

Hi, timmaaa, I am using USB2.0 on windows XP, with a regular cable, not in fastboot mode, and haven't uninstalled HTC Sync Manager.
I will try flash in fastboot mode again.
timmaaa said:
You don't need to relock if you're s-off. Are you using a 2.0 or 3.0 usb port? Are you using a HTC cable? Are you in fastboot mode? Have you uninstalled HTC Sync Manager?
Sent from my Evita
Click to expand...
Click to collapse

aaronDroid80 said:
I'm doing the same thing, but to attempt to trade in my phone. I assume that after running the RUU I should relock the bootloader. I want to get rid of the red text.
*EDIT* nevermind. didn't realize that the RUU clears out the *TAMPERED* flag and gets rid of the red text. should be all good now.
Click to expand...
Click to collapse
You need to make sure the person you are trading with understands the phone is s-off and bootloader unlocked, and what that means.
---------- Post added at 01:57 PM ---------- Previous post was at 01:54 PM ----------
BBS678 said:
One more question, timmaaa: after flashing RUU, the recovery partition will be replaced with the stock recovery, and the S-OFF and boot loader will be kept as it is (based on what I learned from other posts of you). What if I need to flash CM again? I am confused because not many people are doing what I am. Thanks!
Click to expand...
Click to collapse
If you think you might still want to flash custom ROMs, you need to ask yourself why you want to return to stock in the first place.
Going back to stock if you are s-off, custom recovery, etc. is a step backward, not forward. Aside from getting on the correct hboot, firmware, etc. (or selling/trading your phone like the guy above), there is no benefit to going through all the hassle to running the RUU to get back to stock. Just flash a stock rooted ROM as timmaaa originally mentioned.
EDIT: Missed the part in the OP where it mentioned ISIS. See my response below (#13).

An update (for the forum): In fastboot mode, I have flashed Stock RUU successfully, without locking boot loader. After this, even in stock ROM, ISIS still doesn't work. I think it's caused by the SuperCID and S-OFF.
Timmaaa, do you know how I can SAFELY get SuperCID and S-OFF fixed? Thank you!
BBS678 said:
Hi, timmaaa, I am using USB2.0 on windows XP, with a regular cable, not in fastboot mode, and haven't uninstalled HTC Sync Manager.
I will try flash in fastboot mode again.
Click to expand...
Click to collapse

BBS678 said:
An update (for the forum): In fastboot mode, I have flashed Stock RUU successfully, without locking boot loader. After this, even in stock ROM, ISIS still doesn't work. I think it's caused by the SuperCID and S-OFF.
Timmaaa, do you know how I can SAFELY get SuperCID and S-OFF fixed? Thank you!
Click to expand...
Click to collapse
Reading around, root seems to be the only mod that interferes with ISIS. Its unlikely that s-off would interfere with ISIS. SuperCID? Its possible. Changing from SuperCID is very easy with fastboot. Just search for the command.
Also, be aware that you need a ISIS compatible SIM ("secure element SIM") available from your carrier.
http://www.att.com/shop/apps/isis-mobile-wallet.html#fbid=xHuv6S8moS4

Could be. HTC One X is not available on att.com now, so your link can't explain at this moment.
From here, https://www.paywithisis.com/get-started.html, it says AT&T HTC One X is compatible.
In addition, I do have a ISIS compatible SIM card from AT&T. The reason I suspect it is due to CID is that it is “heard" from this forum that ISIS doesn't work if you put an AT&T SIM card in the T-mobile version of GN3 (unlocked).
redpoint73 said:
Reading around, root seems to be the only mod that interferes with ISIS. Its unlikely that s-off would interfere with ISIS. SuperCID? I suppose its possible, but my gut says no. Especially in light of the following:
I'm thinking it more the issue that the AT&T One X is not a "ISIS ready phone": http://www.att.com/shop/apps/isis-mobile-wallet.html#fbid=xHuv6S8moS4
Also, be aware that you need a ISIS compatible SIM ("secure element SIM") available from your carrier.
Click to expand...
Click to collapse

BBS678 said:
Could be. HTC One X is not available on att.com now, so your link can't explain at this moment.
From here, https://www.paywithisis.com/get-started.html, it says AT&T HTC One X is compatible.
Click to expand...
Click to collapse
Yes, I later realized that One X is not available at all anymore from AT&T (and that it is supposed to be ISIS ready), and revised my above response accordingly.
BBS678 said:
In addition, I do have a ISIS compatible SIM card from AT&T. The reason I suspect it is due to CID is that it is “heard" from this forum that ISIS doesn't work if you put an AT&T SIM card in the T-mobile version of GN3 (unlocked).
Click to expand...
Click to collapse
It could also be that they are looking at the phone model number. So SuperCID is a possibility, but not certain.
Its easy to change from SuperCID with a simple fastboot command. Just search this forum for the proper syntax.
---------- Post added at 02:43 PM ---------- Previous post was at 02:32 PM ----------
Here is the command to change from CID:
fastboot oem writecid CWS__001
(note that CWS__001 has two underscores)

Thank you! I learned from this forum that changing S-OFF to S-ON is very risky, and currently S-OFF relies on a SuperCID, so I think it's also risky to change the CID back. Have you ever tried? I need more opinions on this before I take the risk.

BBS678 said:
Thank you! I learned from this forum that changing S-OFF to S-ON is very risky, and currently S-OFF relies on a SuperCID, so I think it's also risky to change the CID back. Have you ever tried? I need more opinions on this before I take the risk.
Click to expand...
Click to collapse
I honestly doubt s-off is blocking ISIS. S-off is exclusively an HTC invention, and I doubt ISIS would care about such a thing. I would recommend to leave s-off alone.
I wouldn't say its "risky" to change CID. As long as you still have s-off, I don't see any reason to still have SuperCID. But even so, you can still use the correct exploit to change back to SuperCID.

Hi, timmaaa, could you please shed some lights on this (change back to stock CID) please? Thanks!

here is my other post about ISIS: http://forum.xda-developers.com/showthread.php?p=49822333
redpoint73 said:
I honestly doubt s-off is blocking ISIS. S-off is exclusively an HTC invention, and I doubt ISIS would care about such a thing. I would recommend to leave s-off alone.
I wouldn't say its "risky" to change CID. As long as you still have s-off, I don't see any reason to still have SuperCID. But even so, you can still use the correct exploit to change back to SuperCID.
Click to expand...
Click to collapse

Everything that @redpoint73 has said is correct. There's pretty much no risk involved in changing your CID back to stock, having s-off does not rely on SuperCID. You can try changing your CID using the command that redpoint gave before.
There's pretty much no risk involved with going from s-off to s-on either. I don't know where you read that but I believe you're misunderstanding the information. Personally I wouldn't go back to s-on though because I don't believe that is affecting your ability to run ISIS. Plus getting s-off again can be tricky sometimes.
Sent from my Evita