Database Info

back to stock firmware onex at&t

As the title says. I just bought a hox at&t version and did a root metod and it failed. The phone is still save and I can normally use it. Now I want to re-flash the stock firmware that the phone was runing the first time I used it. I am scared with the fact about I wouldn't update to Jelly Bean beacuse it might contains any corrupt file due the failed root.
Is there a detailed how to'' guide? I only see guys in here says about flash RUU.
please help!

If you are going to give up that easily, than maybe root is not for you.
What firmware number (1.85, 2.20, etc.) is the phone now? What root method did you try? Root method varies by firmware version, so its a common mistake to use the wrong one. Also, even with the correct method, you may need multiple attempts before its successful (not necessarily due to anything you are doing wrong).
If you truly want to return to stock, just find the RUU for your version number. Download to your computer. Connect the phone via USB. Then just run the RUU. Its an .exe, no guide needed.
Links to the RUUs are on my Index thread: http://forum.xda-developers.com/showthread.php?t=1671237

thanks for the reply!! now I'm downloading the RUU, but if I do Root and want to come back stock again, only flash the correct RUU file? What about bootloaders (relock)? and kernel?

jics91 said:
thanks for the reply!! now I'm downloading the RUU, but if I do Root and want to come back stock again, only flash the correct RUU file? What about bootloaders (relock)? and kernel?
Click to expand...
Click to collapse
all you need to do is "fastboot oem lock" and run the ruu at the fastboot screen.

jics91 said:
but if I do Root and want to come back stock again, only flash the correct RUU file? What about bootloaders (relock)? and kernel?
Click to expand...
Click to collapse
RUU flashes everything: Stock recovery, radio, kernel, and I believe hboot. It will also wipe the phone, so backup anything you want to keep. As DvineLord said, your bootloader needs to be locked. Other than that, just run the RUU, and it does the rest.
---------- Post added at 01:56 PM ---------- Previous post was at 01:54 PM ----------
jics91 said:
now I'm downloading the RUU,
Click to expand...
Click to collapse
Make sure you dowload the right RUU for your firmware version. RUU will only run if the RUU is the right CID, and same version number or a later one (older RUU will not run).

[Q] Flashing RUU on s-off?

Didn't find to much related to specifically to what I want to do.
I was tinkering with my software and messed something up and won't boot.
I can seem to find a strict stock rooted rom from t-mobile
Can I do the following without messing up my phone?
I already have s-off and twrp and a none working rom.
I want to relock bootloader, flash ruu
unlock again and flash recovery and root file.
I think this should work without messing up the phone and I should still have s-off right?

M9x3mos said:
Didn't find to much related to specifically to what I want to do.
I was tinkering with my software and messed something up and won't boot.
I can seem to find a strict stock rooted rom from t-mobile
Can I do the following without messing up my phone?
I already have s-off and twrp and a none working rom.
I want to relock bootloader, flash ruu
unlock again and flash recovery and root file.
I think this should work without messing up the phone and I should still have s-off right?
Click to expand...
Click to collapse
I've ran an RUU a couple times and still had S-off when it was done. It should not impact that at all.

Or you can skip all that and just flash the t mobile ROM in the dev section.
But, yeah, you will keep soff through the ruu
HTC_One_S | S-OFF | ViperOneS_2.2.0 | Black&Blue_Inverted_Sense | Bulletproof_1.4
Inverted Sense _4+_and_5_click me

No need to relock bootloader if s-off. You should flash stock recovery so and use a CID according to your RUU file.

Stock recovery not needed.
Just ruu away
Verstuurd van mijn HTC One S met Tapatalk

Oooh
I also thought too you needed to re lock to flash a ruu.
I guess that is only if not s off then.
Just need to match cid though still.

SCID will work with any RUU. But you shouldn't use it if you insist to upgrade by OTA... Some people reported a brick this way.

Updating EU RUU from 2.31.401.5 to 3.16.401.8 (going from a CM10.1 version)
Well here is what I've done if it can help some. No warranty that it'll work for everyone, but let's go:
First thing : I've started with CM10.1, S-OFF, SuperCID (11111111) and TWRP 2.5.0.0
I DID NOT relock the bootloader and NOT put back the original Recovery
1) I've put back my original CID (EU Bouygues eg. HTC__203. You should put your original one). Fortunately, I had the original mmcblk0p4 file backup (just copy back the original file to /dev/block. See here : http://forum.xda-developers.com/showthread.php?p=26516911#post26516911).
2) once my original CID has been put back (still S-OFF and TWRP and not relock), I've started in bootloader mode the RUU_Ville_U_ICS_40_S_HTC_Europe_2.31.401.5 and let things run
3) after the installation and reboot, I went to Parameters/Update/Check to force the JB update 3.16.401.8 download.
4) I've let the JB update to be performed (several reboot): all went fine. Going into fastboot, I'm still Unlocked / S-OFF / HTC__203 (original) / Radio 1.11.50 and HBOOT 2.15.000. Sounds good !
5) I went back into fastboot to re-flash the TWRP 2.5.0.0 (fastboot flash recovery openrecovery-twrp-2.5.0.0-ville.img)
6) I then reboot into Recovery : now TWRP is back ! In TWRP, try to reboot into bootloader. TWRP will warn you that you're not ROOT and suggest to install root on your phone. Hit YES.
7) Reboot normally your phone : you should have now a Super SU Installer icon in your apps. Open it, choose install via TWRP, and you're good to go! You've now the latest HTC JB sense version with root.
Optional :
-You can perform a full TWRP backup (with Sense/original CID) in case of further HTC update (?)
-You can put back your SuperCID if wanted
Now if you want to test the CM10.1-3.4 kernel here http://forum.xda-developers.com/showthread.php?t=2302248, it's booting fine (after full wipe)
Voilà !
Hope this helps

yeah
with the tmo model I can get the JB ruu right from HTC
I have just been having issues that I want to get stock and maybe root.
Will double check CID and just flash then.
I think hboot and radio on jb equivlent already but will try that.
Thank you

I wanted to post a little warning here, and relate what happened with my RUU update. First, I'm unlocked, s-off, Hboot 1.13.0000, superCID (11111111), running TWRP 2.5.0.0.
So I read somewhere that the latest RUU may not install correctly if on an older Hboot so I fastboot flashed the latest 2.15, no problems. Then I found a decrypted ROM that Hasoon2000 had posted thinking that this would give me the firmware I wanted, I believe this was based off of RUU_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_Radio_1. 11.50.05.28_10.27.50.08L_release. I then Fastboot flashed: (I didn't relocking bootloader or changing CID but I did first flash stock recovery because I wasn't sure it I needed to or not)
1. fastboot erase cache
3. fastboot oem rebootRUU
4. fastboot flash zip "name of ROM".zip
The script ran and everything flashed successfully, so I reflashed TWRP 2.3.3.0 and the phone booted just like stock ROM. At this point I checked the Hboot and it was 2.04 something! with a 1.11?? radio. (So this told me I likely wouldn't have needed to first flash the 2.15 Hboot not sure about this tho) I then tried to restore my backed up SDcard and here is where I ran into problems. My SDcard/internal storage only had 48.6MB of space! Nothing I did would change it I worked with this for several hours last night before giving up and this morning I thought to try running a different Tmobile RUU. Found this thread http://forum.xda-developers.com/showthread.php?t=2250573 and downloaded this Firmware package: http://www.filedropper.com/firmware_1 and ran the same fastboot commands (changed recovery back to stock which I probably wouldn't have needed to do...??) and everything flashed perfectly (I needed to run the "fastboot flash zip firmware.zip" the second time, which is normal). I now have my SDcard back with Hboot 2.15, radio 1.13, superCID and s-off yet, "hopefully" am ready to flash the new 3.4 updated stuff!
I suspect the reason for my problems lay in my flashing a euro ROM/RUU, but I really don't know that for sure. This is just what happened to me. Hope this helps a bit!

i believe i have an issue that is too challenging for me. i flashed the lates trickdroid and for some reason i couldnt get my radio to show. my baseband version was unknown. i tried to flash a new radio tto no avail. finally i flashed the jb ruu and now the rom will work for a couple of minutes and then reboot still with unknow baseband radio version. im s off with super cid. any thing to help woul be appreciated.

Did you run the ruu exe or how did you flash it?
Sent from my HTC VLE_U using xda premium

Clom801 said:
i believe i have an issue that is too challenging for me. i flashed the lates trickdroid and for some reason i couldnt get my radio to show. my baseband version was unknown. i tried to flash a new radio tto no avail. finally i flashed the jb ruu and now the rom will work for a couple of minutes and then reboot still with unknow baseband radio version. im s off with super cid. any thing to help woul be appreciated.
Click to expand...
Click to collapse
Have you tried the fastboot flash zip firmware.zip method? It's working great at updating firmware for all the AOSP ROMs.

TheArtiszan said:
Did you run the ruu exe or how did you flash it?
Sent from my HTC VLE_U using xda premium
Click to expand...
Click to collapse
i ran the RUU. i tried the TMOUS ICS and EU JB
---------- Post added at 06:58 PM ---------- Previous post was at 06:57 PM ----------
el_smurfo said:
Have you tried the fastboot flash zip firmware.zip method? It's working great at updating firmware for all the AOSP ROMs.
Click to expand...
Click to collapse
is that the new method posten in the development section? i will try
ok, tried it and it didnt work. still shows no signal with an x ans reboots after a couple minutes

You can try the tmous jb one.
That might be better as not a downgrade.
Not sure about the eu one but that could be why the ics one is not working.
Sent from my HTC VLE_U using xda premium

Clom801 said:
i ran the RUU. i tried the TMOUS ICS and EU JB
---------- Post added at 06:58 PM ---------- Previous post was at 06:57 PM ----------
is that the new method posten in the development section? i will try
ok, tried it and it didnt work. still shows no signal with an x ans reboots after a couple minutes
Click to expand...
Click to collapse
Interesting thought... Try a cm based ROM. They use a radio in a different system folder. If it still doesn't work, sounds more like a hardware failure.

[Q] Can't update firmware, Unlocked/Tampered S-ON

I want to be able to flash the latest CM10.1 for my AT&T HTC One X. Details about the phone-
Unlocked with HTCDev. Hboot 1.14.0002. Have latest TWRP flashed. Says TAMPERED, UNLOCKED, and S-ON.
I tried a RUU to update the Hboot, but that didn't work.
How can I update the firmware so I can run latest ROMs like CM10.1? I've looked at similar questions, but the answers were for the International Version of the HTC One X.
Any help or suggestions are appreciated.

seth50k said:
I want to be able to flash the latest CM10.1 for my AT&T HTC One X. Details about the phone-
Unlocked with HTCDev. Hboot 1.14.0002. Have latest TWRP flashed. Says TAMPERED, UNLOCKED, and S-ON.
I tried a RUU to update the Hboot, but that didn't work.
How can I update the firmware so I can run latest ROMs like CM10.1? I've looked at similar questions, but the answers were for the International Version of the HTC One X.
Any help or suggestions are appreciated.
Click to expand...
Click to collapse
S-off
Run 3.18 ruu (no need to relock with s-off)
Relash recovery
Flash cm10
Sent from my HTC One XL using xda premium

31ken31 said:
S-off
Run 3.18 ruu (no need to relock with s-off)
Relash recovery
Flash cm10
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
Ok, so here's the 2nd question. Somehow I managed to wipe whatever ROM I had on here (CleanROM I think), so it doesn't boot to anything. I've tried flashing CleanROM 6 and 3.20.401.1 Odexed, both error out in TWRP.
I'm assuming I've managed to softbrick it?

seth50k said:
Ok, so here's the 2nd question. Somehow I managed to wipe whatever ROM I had on here (CleanROM I think), so it doesn't boot to anything. I've tried flashing CleanROM 6 and 3.20.401.1 Odexed, both error out in TWRP.
I'm assuming I've managed to softbrick it?
Click to expand...
Click to collapse
Not sure 3.20.401.1 is but what did you do? You didn't do factory reset from bootloader did you?

RollTribe said:
Not sure 3.20.401.1 is but what did you do? You didn't do factory reset from bootloader did you?
Click to expand...
Click to collapse
I might have. What I was trying to do is clean out the phone to sell it, then get it updated, etc. I know in TWRP I ran probably every type of wipe, and I may have run Factory reset from the bootloader. It was a while ago and I set it aside, and now i've come back to it trying to get this phone sorted out.

seth50k said:
I might have. What I was trying to do is clean out the phone to sell it, then get it updated, etc. I know in TWRP I ran probably every type of wipe, and I may have run Factory reset from the bootloader. It was a while ago and I set it aside, and now i've come back to it trying to get this phone sorted out.
Click to expand...
Click to collapse
If you did, then you're not gonna be able to so anything with ROMs. Run an ruu, reunlock, and report back.

RollTribe said:
If you did, then you're not gonna be able to so anything with ROMs. Run an ruu, reunlock, and report back.
Click to expand...
Click to collapse
I've tried running RUU, it gets about halfway and fails. Do I need to flash the stock recovery and relock first, then run a RUU?

U need to relock the bootloader
Use command prompt
"Fastboot oem lock" from fastboot then run the ruu.... I recommend getting s-off as well is very easy and fast and it will save u a lot of troubles in the future plus u will not have to lock the bootloader to flash an ruu
Sent from my HTC One X using xda premium

If you ruu with s-on and supercid you brick.
Be careful with your advice breeze. You'll cause him a brick.
Sent from my One X using xda app-developers app

breezedragon said:
U need to relock the bootloader
Use command prompt
"Fastboot oem lock" from fastboot then run the ruu.... I recommend getting s-off as well is very easy and fast and it will save u a lot of troubles in the future plus u will not have to lock the bootloader to flash an ruu
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Yeah, but you need a ROM working to even do the s-off process. So getting a ROM loaded is my main priority at this point. I can get into Bootloader/Fastboot, and I can still get to TWRP. Flashing a ROM from TWRP isn't working, and neither is running the latest RUU from fastboot. I get ERROR 159 when I try to run the latest RUU. So do I need to fastboot oemlock, then try again?
Perhaps running the RUU that was previously on it would work? 2.20, is what firmware was on it last.

seth50k said:
Yeah, but you need a ROM working to even do the s-off process. So getting a ROM loaded is my main priority at this point. I can get into Bootloader/Fastboot, and I can still get to TWRP. Flashing a ROM from TWRP isn't working, and neither is running the latest RUU from fastboot. I get ERROR 159 when I try to run the latest RUU. So do I need to fastboot oemlock, then try again?
Perhaps running the RUU that was previously on it would work? 2.20, is what firmware was on it last.
Click to expand...
Click to collapse
Yeah, you have to run the same/later ruu if you're not S-Off. And you'll have to relock and you can flash stock recovery to be safe (but I think it flashes for you).
---------- Post added at 02:12 PM ---------- Previous post was at 02:11 PM ----------
exad said:
If you ruu with s-on and supercid you brick.
Be careful with your advice breeze. You'll cause him a brick.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
That's not necessarily true, I've ruu'ed with s-on and SuperCID and was fine. It is risky, though.

Unlock, flash a sense rooted rom, soff and then ruu up to 3.18
Sent from my One X using xda app-developers app

RollTribe said:
Yeah, you have to run the same/later ruu if you're not S-Off. And you'll have to relock and you can flash stock recovery to be safe (but I think it flashes for you).
---------- Post added at 02:12 PM ---------- Previous post was at 02:11 PM ----------
That's not necessarily true, I've ruu'ed with s-on and SuperCID and was fine. It is risky, though.
Click to expand...
Click to collapse
I'm able to run the 2.20 RUU so far after relocking, it's about 3/4 of the way done. After this i'll try the latest RUU, then go from there to re-unlock, then S-OFF, THEN reflash TWRP?

seth50k said:
I'm able to run the 2.20 RUU so far after relocking, it's about 3/4 of the way done. After this i'll try the latest RUU, then go from there to re-unlock, then S-OFF, THEN reflash TWRP?
Click to expand...
Click to collapse
Yup, you can swap the last two if you want

RollTribe said:
Yup, you can swap the last two if you want
Click to expand...
Click to collapse
Well shoot...got so close. 2.20 RUU worked, then I did the latest RUU, which completed fine, but now the phone won't turn on, and won't even show a red LED charging indicator. WTF...

seth50k said:
Well shoot...got so close. 2.20 RUU worked, then I did the latest RUU, which completed fine, but now the phone won't turn on, and won't even show a red LED charging indicator. WTF...
Click to expand...
Click to collapse
Yep, looks like it's bricked. http://forum.xda-developers.com/showthread.php?t=2181929

seth50k said:
Well shoot...got so close. 2.20 RUU worked, then I did the latest RUU, which completed fine, but now the phone won't turn on, and won't even show a red LED charging indicator. WTF...
Click to expand...
Click to collapse
Yeah, you have to s-off before running latest ruu. Damn sorry if I was unclear man.

RollTribe said:
Yeah, you have to s-off before running latest ruu. Damn sorry if I was unclear man.
Click to expand...
Click to collapse
It's alright, just a little surprised given the fact that HTC allows you to unlock and such, but their own RUU bricks the phone if in such a state.
I think it might be under warranty still, might try that route. Thanks for the help.

Sorry about your phone. It's Jtagg or new phone.
---------- Post added at 02:34 PM ---------- Previous post was at 02:34 PM ----------
seth50k said:
It's alright, just a little surprised given the fact that HTC allows you to unlock and such, but their own RUU bricks the phone if in such a state.
I think it might be under warranty still, might try that route. Thanks for the help.
Click to expand...
Click to collapse
They state on their site that after unlocking the bootloader, RUU/OTA could brick you.
If you plan to try warranty with HTC, do not mention that you unlocked. They will charge you 200 straight up no matter what you say.

RollTribe said:
That's not necessarily true, I've ruu'ed with s-on and SuperCID and was fine. It is risky, though.
Click to expand...
Click to collapse
But was it the 3.18? It applies specifically for the AT&T 3.18 (and for some 3.17 JB RUUs on other carriers, and reported by some folks on this forum).
If you were able to run the 3.18 RUU successfully with SuperCID and S-on, I believe this is the first I've heard of it.
---------- Post added at 12:37 PM ---------- Previous post was at 12:33 PM ----------
seth50k said:
It's alright, just a little surprised given the fact that HTC allows you to unlock and such, but their own RUU bricks the phone if in such a state.
Click to expand...
Click to collapse
SuperCID as implemented on the AT&T One X is a mod/hack, and therefore not explicitly "allowed" by HTC. They can't really be held responsible for the effects of it.
SuperCID shouldn't be "expected" to brick under these conditions (worked fine with pre-JB RUUs), and nobody here has really been able to explain exactly why the phone bricks from SuperCID. But unfortunately, it does.

[Q] Relock Bootloader - Fido

Hi,
I want to know if in case I want to relock my bootloader, what's the RUU for? and how can I find one for my carrier? I'm with Fido (Canada), I'm s-on, hboot 2.15, rooted and running CarbonRom. I have the stock OS backup on my pc, and I was reading the steps to go back to stock with a locked bootloader.
Thanks

lucasmedaffy said:
I am on Fido and recently soft-bricked my phone.
I just went back to stock using the OTA ROGERS JB RUU (I found it online). It was a bit more complicated because the OTA zip doesn't have a RUU utility to flash it. There is a thread that will walk you through the steps; XDA's search is down or I would locate it. It took a bit of time but worked.
Click to expand...
Click to collapse
So you say the Rogers RUU will work? and I must use the ruu to lock the bootloader right?
Thanks!

elias.acab said:
So you say the Rogers RUU will work? and I must use the ruu to lock the bootloader right?
Thanks!
Click to expand...
Click to collapse
If you just want to relock the bootloader you can use fastboot
Code:
fastboot oem lock
But, this is probably not what you want to do, right?
RUU = ROM UPGRADE UTILITY. It's an .exe file that lets you install the stock rom on your phone. The RUU needs to match your hboot (and carrier). Get the RUU here:
http://www.androidruu.com/index.php?developer=Ville
Requirements:
- min 30% battery
- HTC drivers installed (devices is recognized by windows)
- USB debugging enabled
- Charging only mode
Hope this helps.

Thank you guys for that!! Theres something I still dont get, and its if I got the backup of the stock os (I dont really wanna relock the bootloader), I dont need the ruu right? But if I want to install the stock os and relock the bootloader (without using the backup) I do need the ruu, am I right?
Thanks
Sent from my One S

lucasmedaffy said:
I followed these instructions: http://forum.xda-developers.com/showthread.php?t=2394165
and I used this RUU: http://www.androidfiles.org/ruu/get....27.50.08L_release_301897nn5lu23br8cg9q7l.zip
Unfortunately I couldn't use the older RUU because they were for ICS (IceCream Sandwich), not JB (JellyBean) and wouldn't install. As I mentioned, it is a few more hoops but the directions are very clear and it worked for me.
Good luck!
EDIT: If you just want to relock your bootloader, you can follow the above step (which is part of flashing the RUU and included in the instructions in the thread I linked to). If you want to reflash stock, follow the full instructions.
Click to expand...
Click to collapse
Thank you guys so much for that!! Theres something I still dont get, and its if I got the backup of the stock os (I dont really wanna relock the bootloader), I dont need the ruu right? But if I want to install the stock os and relock the bootloader (without using the backup) I do need the ruu, am I right? The Ruu installs the stock os for me?
Thanks, and sorry for asking too many questions
Sent from my One S

elias.acab said:
Hi,
I want to know if in case I want to relock my bootloader, what's the RUU for? and how can I find one for my carrier? I'm with Fido (Canada), I'm s-on, hboot 2.15, rooted and running CarbonRom. I have the stock OS backup on my pc, and I was reading the steps to go back to stock with a locked bootloader.
Thanks
Click to expand...
Click to collapse
Your Stock backup will work (you will also need to fastboot flash the boot.img if you are S-ON) to bring you back to your stock ROM.
RUU does that and a whole lot more that a simple backup can do.
Such as:
HBoot
Returns to stock recovery (which in turn will allow to correct partitions and fix unmountable sdcard)
Radio update
Boot.img
Splash screen
Or you could say it updates: Boot/System/Data/Recovery/Radio
---------- Post added at 05:05 PM ---------- Previous post was at 04:55 PM ----------
elias.acab said:
Thank you guys so much for that!! Theres something I still dont get, and its if I got the backup of the stock os (I dont really wanna relock the bootloader), I dont need the ruu right? But if I want to install the stock os and relock the bootloader (without using the backup) I do need the ruu, am I right? The Ruu installs the stock os for me?
Thanks, and sorry for asking too many questions
Sent from my One S
Click to expand...
Click to collapse
If you run your backup and then relock the bootloader, The bootloader will still say "tampered" I believe. This is because the modified recovery will still be there. You would need to unlock the bootloader and flash stock recovery to remove the "tampered" (i think)
So yeah, theoretically it will be just like running a RUU, if you restore your backup, fastboot flash boot.img, flash stock recovery. (assuming you haven't changed radio or hboot)

tivofool said:
Your Stock backup will work (you will also need to fastboot flash the boot.img if you are S-ON) to bring you back to your stock ROM.
RUU does that and a whole lot more that a simple backup can do.
Such as:
HBoot
Returns to stock recovery (which in turn will allow to correct partitions and fix unmountable sdcard)
Radio update
Boot.img
Splash screen
Or you could say it updates: Boot/System/Data/Recovery/Radio
---------- Post added at 05:05 PM ---------- Previous post was at 04:55 PM ----------
If you run your backup and then relock the bootloader, The bootloader will still say "tampered" I believe. This is because the modified recovery will still be there. You would need to unlock the bootloader and flash stock recovery to remove the "tampered" (i think)
So yeah, theoretically it will be just like running a RUU, if you restore your backup, fastboot flash boot.img, flash stock recovery. (assuming you haven't changed radio or hboot)
Click to expand...
Click to collapse
Thank you again, I really appreciate it!!, I totally get it now I'll make sure I re-read these steps when I feel like I wanna go back to stock.

[Q] Stuck on Hboot/fastboot with full stock phone

Hi guys,
My sister sent me her HTC One SV aka K2-UL i offered her from expansys on june, it is stuck on Hboot
*** LOCKED***
K2_UL XA SHIP S-ON RL
HBOOT-2.00.0000
eMMC Boot
...
I can go to Fastboot USB ( or AC )
She 's worst than a noob so phone is stock, up to date but non-root non-unlock, still S-ON and so on.
just once phone reboot and stay stuck...
From here i can navigate but after reboot i'm still here.
I tried :
factory reset and recovery (with rom renamed PL80DIAG but would be too easy...)
RUU but RUU asked for bootloader so stuck on "waiting for bootloader"
go to htc dev to unlock bootloader but after flash unlock token ( unlock token check successfully) but : Nothing happens and still writtten ***Locked*** then if I "fastboot oem unlock" it says failed :<remote : loading custom splash failed>
fastboot flash boot.img but nothing works since still S-on and locked bootloader (superCID is out too)
flash custom recovey or even fresh stock recovery but nothing worked for the same reasons...
Do you guys have any idea of something i could do?
Thanks for your answer and forgive my English I'm French

As long as you are ***LOCKED*** you can quiet do nothing.
To use our available RUU you must also be unlocked & S-Off.

Somewhat the same situation
I am stuck here:
***Tampered***
***Unlocked***
K2_PLC_CL PVT Ship S-ON RL
HBOOT -1.01.0000
Radio - 1.12.00.0208
OpenDSP - v.7.2.0221.1123
eMMC - boot
Feb 8 2013, 16:29:40:-1
I can get into Fastboot as well as bootloader, I CANNOT GET INTO RECOVERY. I have tried to restore with the respective RUU files from the All things HTC ONE SV forum. I have also tried to flash the recovery boot and radio img files through fastboot usb. NONE of this has worked for me. I really enjoyed this phone before I went and made it all FUBR. If there is anyway to get it to boot to any recovery or rom, i will much appreciate it. Thanks for all your help from previous posts as well as any future help I get from information posted here.

Related to your hboot, you should be able to flash any recoveries, but i usually recommend this one.
What command do you use to flash recovery and do you get an output from "fastboot devices"?

Thedc24 said:
I am stuck here:
***Tampered***
***Unlocked***
K2_PLC_CL PVT Ship S-ON RL
HBOOT -1.01.0000
Radio - 1.12.00.0208
OpenDSP - v.7.2.0221.1123
eMMC - boot
Feb 8 2013, 16:29:40:-1
Click to expand...
Click to collapse
Oops you already are 4.2.2. I have a system.img and a boot.img that I can make into a rom.zip to flash via the OEM-RUU mode.

eduardog131 said:
Oops you already are 4.2.2. I have a system.img and a boot.img that I can make into a rom.zip to flash via the OEM-RUU mode.
Click to expand...
Click to collapse
HBOOT 1.01 is ICS (4.0.x).
Sent from my C525c using Tapatalk

Modding.MyMind said:
HBOOT 1.01 is ICS (4.0.x).
Sent from my C525c using Tapatalk
Click to expand...
Click to collapse
Well then I was right then I was wrong. Sorry. HBOOT versions for the Sensation are stuck in my mind.
Sent from my HTC Sensation

Thanks a million for the replies. I was able to lead the recovery and get into it (the most progress i have had in a year with this phone). With that being done. When I go into recovery I am unable to mount the internal storage. I am not too sure of the procedures I need to go through to get this thing functional again. I have been tinkering with my S3 for the last few months, but with KNOX on now I am looking to Jump ship completely from both verizon and samsung. Enough rambling, Like I said thanks for the help, any assistance in getting this thing to boot to a ROM would be much appreciated.
BTW
I used the fastboot flash recovery recovery.img
I have tried this before with no success. This time it worked.
I also flased the Radio and Boot img for ICS.
Thanks.

Thedc24 said:
Thanks a million for the replies. I was able to lead the recovery and get into it (the most progress i have had in a year with this phone). With that being done. When I go into recovery I am unable to mount the internal storage. I am not too sure of the procedures I need to go through to get this thing functional again. I have been tinkering with my S3 for the last few months, but with KNOX on now I am looking to Jump ship completely from both verizon and samsung. Enough rambling, Like I said thanks for the help, any assistance in getting this thing to boot to a ROM would be much appreciated.
BTW
I used the fastboot flash recovery recovery.img
I have tried this before with no success. This time it worked.
I also flased the Radio and Boot img for ICS.
Thanks.
Click to expand...
Click to collapse
If you want I can just skip you to 4.2.2. You don't need to reflash recovery and stuff. I will make a package that will update HBOOT and radios. And system/boot.img.
Sent from my HTC Sensation

He first needs to be S-off, to flash radio & hboot. I have made a 4.1.2 rom for cricket, must be linked in my index thread. Wipe all, flash the rom, flash boot.imgwith fastboot and hope that little baby is booting.
If yes, use moonshine.io or rumrunner.us to get S-off.
Then we will do next steps.

old.splatterhand said:
He first needs to be S-off, to flash radio & hboot. I have made a 4.1.2 rom for cricket, must be linked in my index thread. Wipe all, flash the rom, flash boot.imgwith fastboot and hope that little baby is booting.
If yes, use moonshine.io or rumrunner.us to get S-off.
Then we will do next steps.
Click to expand...
Click to collapse
Wow! Awsome! This bad boy booted. I was able to flash the rom through recovery. This is much further than I expected to get with this device. Now when I try to go S-Off with either moonshine or rumrunner I get an error saying not able to make adb connection. When I use fastboot devices my device will show up...if i do adb devices nothing...Would love to have S-Off and SU installed. But like I said this is much further than I expected to get so anything further is icing on the cake. Thanks in Advance.

Is Usb-Debugging enabled?
Any output from adb devices? HTC Sync installed (for the drivers)?

old.splatterhand said:
Is Usb-Debugging enabled?
Any output from adb devices? HTC Sync installed (for the drivers)?
Click to expand...
Click to collapse
He can just use the Naked Driver for the adb driver. http://forum.xda-developers.com/showthread.php?t=2263822

Ok I DID have USB debugging enabled. After messing with the drivers and my Windows 8 computer, I have came to the conclusion that it is something with the drivers and their compatibility with Windows 8. Either way moonshine or rumnunner never worked for me in a windows 8 environment. I dual boot ubuntu 12.04 anyway, it saw my device just fine adb and fastboot. I ran moonshine and it went through all the testing stages, but was never able to completely run...so I still have no S-Off. Do I need to update Hboot or anything? Also am I able to load a custom rom on this device with S-ON? I have been looking but I do not see many out for this device at all, which is a shame because I feel as though it is very comparable to my GS3. It would be nice to see a nice AOSP ROM on this device. But all take any updates I can for the device, hopefully it will help with the issue I have will cell reception dropping all the time. Thanks

To answer some of your questions:
- you can't update hboot because you are not stock and not S-off
- there are indeed not much roms to flash, but you could do with S-on (and unlocked bootloader)
- if you would flash the Sense 5/Android 4.2.2 rom, you would have noizy sound, without the firmware files (which you need S-Off to flash)
Another way for getting S-off (which should work with your hboot), is facepalm.
But the part of changing CID to SuperCID is very risky, read carefully and only do, when you are sure you understand, what to do!!!

old.splatterhand said:
To answer some of your questions:
- you can't update hboot because you are not stock and not S-off
- there are indeed not much roms to flash, but you could do with S-on (and unlocked bootloader)
- if you would flash the Sense 5/Android 4.2.2 rom, you would have noizy sound, without the firmware files (which you need S-Off to flash)
Another way for getting S-off (which should work with your hboot), is facepalm.
But the part of changing CID to SuperCID is very risky, read carefully and only do, when you are sure you understand, what to do!!!
Click to expand...
Click to collapse
Thanks for all the help! I am now SuperCID with S-OFF, Facepalm worked like a charm. Would it be possible to put slimrom on this device? Anyway thanks for all the help, I am going to check out some ROMS..as far as flashing goes, I am assuming how I have my phone now I should be able to flash any rom that is compatible with the device.
---------- Post added at 05:46 PM ---------- Previous post was at 05:24 PM ----------
eduardog131 said:
If you want I can just skip you to 4.2.2. You don't need to reflash recovery and stuff. I will make a package that will update HBOOT and radios. And system/boot.img.
Sent from my HTC Sensation
Click to expand...
Click to collapse
Yea that would be cool. I am assuming I would just flash it through recovery?

Thedc24 said:
Thanks for all the help! I am now SuperCID with S-OFF, Facepalm worked like a charm. Would it be possible to put slimrom on this device? Anyway thanks for all the help, I am going to check out some ROMS..as far as flashing goes, I am assuming how I have my phone now I should be able to flash any rom that is compatible with the device.
---------- Post added at 05:46 PM ---------- Previous post was at 05:24 PM ----------
Yea that would be cool. I am assuming I would just flash it through recovery?
Click to expand...
Click to collapse
You're completely S-OFF? The radios and new HBOOT update need to be flashed in RUU mode. Let me get my bearings and you can flash everything. (adb reboot oem-42 or fastboot oem rebootRUU is a way to get to RUU mode.)
Sent from my HTC Sensation using Tapatalk

eduardog131 said:
You're completely S-OFF? The radios and new HBOOT update need to be flashed in RUU mode. Let me get my bearings and you can flash everything. (adb reboot oem-42 or fastboot oem rebootRUU is a way to get to RUU mode.)
Sent from my HTC Sensation using Tapatalk
Click to expand...
Click to collapse
Yes I am completely S-OFF with CID 111111 and SU. The phone has been working good, Cricket service is not all that great in my area. I see there is a software update 2.04.1050.5 (15.1 MB), I am assuming if i run this update it will most likely wipe everything I just did. Is this correct?

Thedc24 said:
Yes I am completely S-OFF with CID 111111 and SU. The phone has been working good, Cricket service is not all that great in my area. I see there is a software update 2.04.1050.5 (15.1 MB), I am assuming if i run this update it will most likely wipe everything I just did. Is this correct?
Click to expand...
Click to collapse
I think. Anyways, download this: http://www.mediafire.com/download/maa60jha4eod834/rom.zip
Contents of said rom.zip:
4.2.2 system.img with root.
4.2.2 stock boot.img.
4.2.2 stock recovery.
New HBOOT and radios and stuff.
If you get an error (flush again or something.), then just resend the command. (fastboot flash zip path/to/rom.zip)

eduardog131 said:
I think. Anyways, download this: http://www.mediafire.com/download/maa60jha4eod834/rom.zip
Contents of said rom.zip:
4.2.2 system.img with root.
4.2.2 stock boot.img.
4.2.2 stock recovery.
New HBOOT and radios and stuff.
If you get an error (flush again or something.), then just resend the command. (fastboot flash zip path/to/rom.zip)
Click to expand...
Click to collapse
Downloading now. I will let you know how it goes...thanks a million.
This is what I got when I tried to flash the rom:
sending 'zip' (691470 KB)...
OKAY [ 37.267s]
writing 'zip'...
FAILED (remote: not allowed)
finished. total time: 37.301s
I dont understand if I am S-Off and super CID.