Database Info

Please Help Me Not Brick My One S

Basically I deleted everything off my One S (System OS,Backups,My Data) So I need to run a RUU to get my phone back to stock
------------------------------
**** TAMPERED ****
**** UNLOCKED ****
VLE PVT SHIP S-ON RL
Hboot-2.13.0000
Radio-1.11.50.05.28
Open DSP-v31.1.0.45.0815
eMMC-boot
Nov 20 2012 , 15:44:03,-1
------------------------------
There is not compatible RUU for my one s so heres the steps I'm going to do ....
1) SuperCID My Phone Using This Tutorial
http://androidforums.com/one-s-all-things-root/690970-guide-supercid.html
2) Then Proceed With S-OFF using this tutorial
http://m.youtube.com/watch?v=fTp5uwURKdg
3) Relock Bootloader Using Hasoon2000's All in one toolkit and flash stock recovery (I Need Stock Recovery Image For Htc one s S4 Processor) I Will use this tutorial for steps 3/4
http://m.youtube.com/watch?v=SZuAjz4PIjU
4) Run The RUU (will I be unbranded if I SuperCID and S OFF my phone so I can run. A unbranded RUU ?)
I Also Need A RUU Which Is On JellyBean Not ICS
5)Unlock Bootloader and Root
Please can ou Anwser These Questions Please <3
ill I be unbranded if I SuperCID and S OFF my phone so I can run. A unbranded RUU ? I am currently branded to three uk
And can someone link me to stock recovery Image for htc one s S4 Processor
Is There Any JellyBean RUU if So Please Link me to them and tell me if I can use them after I have done SuperCID and s off
And let me know if there any problems in my method I am going to use
Thanks One S Community

Do the steps 1 & 2 just as you mentioned.
Then, once you're s-off, you don't need to relock your bootloader. But you need to flash stock recovery before you flash any RUU. You can download it here, and flash it in fastboot mode ('fastboot flash recovery ville_recovery_signed.img').
Being s-off you can easily change to any CID by typing 'fastboot oem writecid xxxxxxxx'. You'll find CIDs in this thread, also keep in mind that using SCID might brick your phone in case of an OTA coming in. But it's easy to change...
Then choose any RUU which is closest to what you need and run it from your desktop/laptop or click me for latest EU RUU.
As you're already rooted, there is no need for step 5. You'll still be s-off and unlocked afterwards.
You should be good to go then.

rootrider said:
Do the steps 1 & 2 just as you mentioned.
Then, once you're s-off, you don't need to relock your bootloader. But you need to flash stock recovery before you flash any RUU. You can download it here, and flash it in fastboot mode ('fastboot flash recovery ville_recovery_signed.img').
Being s-off you can easily change to any CID by typing 'fastboot oem writecid xxxxxxxx'. You'll find CIDs in this thread, also keep in mind that using SCID might brick your phone in case of an OTA coming in. But it's easy to change...
Then choose any RUU which is closest to what you need and run it from your desktop/laptop or click me for latest EU RUU.
As you're already rooted, there is no need for step 5. You'll still be s-off and unlocked afterwards.
You should be good to go then.
Click to expand...
Click to collapse
What should I change my CID to and will I be unbranded ? And can I use the ruu you provided the latest one .and I don't understand what you mean with the OTA Updates. I'm branded to three UK and for 8. Change T-MOB010 to 11111111 and save the file as mmcblk0p4MOD. Would I just find H3G and change it to 11111111

You don't need stock recovery to run an ruu, all you need is a locked bootloader
Sent from my HTC One S using xda app-developers app

Ok then. Just to make shure, you're on an S4 device?
Three UK means you're just around the corner... United Kingdom.
So everything 'EU' will be good for you and you should choose HTC__001 then (HTC Europe). If this works, you'll be unbranded.
If you're s-off you basically can flash any RUU you want, even the most exotic one (if there is any :laugh. And to get the point 'any' means older ones as well, e.g. ICS based ones. Being on HTC__001 or 11111111 with ICS on the other hand means that your device will find an Over The Air update to JB. If you choose to install it, it will install JB without problems on HTC__001 but a possible lot of trouble being on 11111111. As a result you might brick your phone, according to some posts here on XDA. So you should choose HTC__001 (8 digits).
At this point keep in mind, never ever use the latest TMO US JB RUU, as this may install write protection to mmcblk0p4 on one s phones!!! (Maybe not if you're already s-off, idk at this point...)
And yes, you can use the one RUU I linked to in my previous post. It worked here, why should it not work on other phones?
---------- Post added at 11:06 AM ---------- Previous post was at 11:05 AM ----------
k1llacanon said:
You don't need stock recovery to run an ruu, all you need is a locked bootloader
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Crap - it's way easier to flash stock recovery than changing cid and unlocking/relocking bootloader. And it works.

I'm going to run the ruu you provided me with will I have any problems with that and what should I change my CID To? Also I'm going to flash stock recovery and lock bootloader so there no probs

rootrider said:
Ok then. Just to make shure, you're on an S4 device?
Three UK means you're just around the corner... United Kingdom.
So everything 'EU' will be good for you and you should choose HTC__001 then (HTC Europe). If this works, you'll be unbranded.
If you're s-off you basically can flash any RUU you want, even the most exotic one (if there is any :laugh. And to get the point 'any' means older ones as well, e.g. ICS based ones. Being on HTC__001 or 11111111 with ICS on the other hand means that your device will find an Over The Air update to JB. If you choose to install it, it will install JB without problems on HTC__001 but a possible lot of trouble being on 11111111. As a result you might brick your phone, according to some posts here on XDA. So you should choose HTC__001 (8 digits).
At this point keep in mind, never ever use the latest TMO US JB RUU, as this may install write protection to mmcblk0p4 on one s phones!!! (Maybe not if you're already s-off, idk at this point...)
And yes, you can use the one RUU I linked to in my previous post. It worked here, why should it not work on other phones?
---------- Post added at 11:06 AM ---------- Previous post was at 11:05 AM ----------
Crap - it's way easier to flash stock recovery than changing cid and unlocking/relocking bootloader. And it works.
Click to expand...
Click to collapse
Sorry for being a pain it's just I don't want to brick my phone and could you explain this as I don't understand it
view plaincopy to clipboardprint?
adb pull /sdcard/mmcblk0p4
and hit enter.
NOTE THE SIZE OF THE FILE BEFORE THE NEXT STEP!
6. Open the file (mmcblk0p4) with your hex editor.
7. Look for offset 00000210 or 00000214 and you should see "T-MOB010" with your IMEI number after it.
NOTE: "T-MOB010" is the T-Mobile US version, depending on your carrier this will change, but it will still precede your IMEI. See the link at the end of this post for a list of other CID's.
MAKE SURE AT THIS POINT THAT THE FILE IS THE EXACT SIZE IT WAS BEFORE YOU HEX EDITED IT!
9. Now go back to your command prompt and type
view plaincopy to clipboardprint?
adb push mmcblk0p4MOD /sdcard/mmcblk0p4MOD
Shall I note the file size so if it. Example.txt(4642kb). I would note the file size and I would just change my CID to HTC__001 ?
And don't I need to get the fast boot files and softbin3 and stuff but the site doesn't provide me with anything could you link me to them ? I have literally no clue
And in HxD. editor will mine look like this http://dl.xda-developers.com/attach...3a77c716b8/51864687/1/0/8/2/7/9/0/hexedit.jpg
Wouldn't I change my CID To H3G__001 but I want to be unbranded

For s off, you need super cid 11111111
HTC_One_S | S-OFF | ViperOneS_2.2.0 | Black-Blue_Sense_Theme | Bulletproof_1.3

ryanshew said:
For s off, you need super cid 11111111
HTC_One_S | S-OFF | ViperOneS_2.2.0 | Black-Blue_Sense_Theme | Bulletproof_1.3
Click to expand...
Click to collapse
should i do
SUPERCID :111111
CHANGE CID :HTC__001
I want to make sure the possiblity of me bricking my phone is extremely low rootrider said change it to HTC__001
btw im a noob at this stuff so i kin off need it simple

Zaman-The-Man said:
should i do
SUPERCID :111111
CHANGE CID :HTC__001
I want to make sure the possiblity of me bricking my phone is extremely low rootrider said change it to HTC__001
btw im a noob at this stuff so i kin off need it simple
Click to expand...
Click to collapse
Hi,
In the order listed, these are the following steps you must do: (this guide assumes you have the HTC drivers installed and a working folder with adb and fastboot files. if you need them, ask)
1. SuperCID. (using the previous link you mentioned, or this link)
2. S-OFF (using the previous link you mentioned, or this link)
3. Get a stock recovery. I have provided one from the Jelly Bean RUU, download it here. MD5 Sum: ed56807cb765ada1d49e7e6e246aea63
Place it in your working folder (the place where adb and fastboot etc. files are).
4. Flash the stock recovery using the command:
Code:
fastboot flash recovery recovery.img
5. Change your cid to HTC__001, using the command:
Code:
fastboot oem writecid HTC__001
You have to be in FASTBOOT USB mode in the bootloader for the command to work.
5. Run a Jelly Bean 3.16 RUU from here:
http://androidfiles.org/ruu/securek...28_10.27.50.08L_release_301814_signed_2_4.exe
6. Done!
Hope it helps

usaff22 said:
Hi,
In the order listed, these are the following steps you must do: (this guide assumes you have the HTC drivers installed and a working folder with adb and fastboot files. if you need them, ask)
1. SuperCID. (using the previous link you mentioned, or this link)
2. S-OFF (using the previous link you mentioned, or
3. Get a stock recovery. I have provided one from the Jelly Bean RUU, download it here. MD5 Sum: ed56807cb765ada1d49e7e6e246aea63
Place it in your working folder (the place where adb and fastboot etc. files are).
4. Flash the stock recovery using the command:
Code:
fastboot flash recovery recovery.img
5. Change your cid to HTC__001, using the command:
Code:
fastboot oem writecid HTC__001
You have to be in FASTBOOT USB mode in the bootloader for the command to work.
5. Run a Jelly Bean 3.16 RUU from here:
http://androidfiles.org/ruu/securek...28_10.27.50.08L_release_301814_signed_2_4.exe
6. Done!
Hope it helps
Click to expand...
Click to collapse
First of all THANKS SO MUCH
and should i be in fastboot mode when doing supercid ? and what should i do for the md5 file ?
THANKS

Zaman-The-Man said:
First of all THANKS SO MUCH
and should i be in fastboot mode when doing supercid ? and what should i do for the md5 file ?
THANKS
Click to expand...
Click to collapse
Hi,
I forgot to link the instructions for S-OFF, my apologies. I have corrected that now.
You should not be in fastboot mode when doing supercid, I didn't realize this. You should be booted into Android. I understand the catch-22 you are having here, so you may want to flash a custom ROM like CM10 for the time being, and then do SuperCID with USB Debugging enabled in Settings.
The md5 file is used to check for corrupt downloads, you download the file and use a tool to check the file's MD5 sum on the PC. Then you match it to the one I gave you and see if it matches. The purpose of this is so that you don't accidentally flash a corrupt file.
Also, the CID you need to find is not T-MOB010, but H3G__001 (two underscores there, to make it 8 digits). Change that to 11111111 (8 digits, again)

usaff22 said:
Hi,
I forgot to link the instructions for S-OFF, my apologies. I have corrected that now.
You should not be in fastboot mode when doing supercid, I didn't realize this. You should be booted into Android. I understand the catch-22 you are having here, so you may want to flash a custom ROM like CM10 for the time being, and then do SuperCID with USB Debugging enabled in Settings.
The md5 file is used to check for corrupt downloads, you download the file and use a tool to check the file's MD5 sum on the PC. Then you match it to the one I gave you and see if it matches. The purpose of this is so that you don't accidentally flash a corrupt file.
Also, the CID you need to find is not T-MOB010, but H3G__001 (two underscores there, to make it 8 digits). Change that to 11111111 (8 digits, again)
Click to expand...
Click to collapse
do i need to relock bootloader wen running the ruu or just the flash stock recovery ?

Zaman-The-Man said:
do i need to relock bootloader wen running the ruu or just the flash stock recovery ?
Click to expand...
Click to collapse
you shouldn't need to

usaff22 said:
you shouldn't need to
Click to expand...
Click to collapse
cant i s off using hasoon2000 toolkit ? wouldnt that be easier ?
thanks

Zaman-The-Man said:
cant i s off using hasoon2000 toolkit ? wouldnt that be easier ?
thanks
Click to expand...
Click to collapse
No, you can't. The developer(s) of the S-OFF exploit don't want their work getting repackaged
Sent from my HTC One S using Tapatalk 2

usaff22 said:
No, you can't. The developer(s) of the S-OFF exploit don't want their work getting repackaged
Sent from my HTC One S using Tapatalk 2
Click to expand...
Click to collapse
Alright so
1) Do SuperCID : 11111111
2) S - OFF
3 Do ' fastboot oem writecid HTC__001 '
4) Flash Stock Recovery
5) Run RUU
looks like I'm sorted
But can I ask what shall If my device doesn't match this PJ4010000.zip ?

You can forget step 4. It's not needed with S-off.
Verstuurd van mijn HTC One S met Tapatalk

Zaman-The-Man said:
Basically I deleted everything off my One S (System OS,Backups,My Data) So I need to run a RUU to get my phone back to stock
------------------------------
**** TAMPERED ****
**** UNLOCKED ****
VLE PVT SHIP S-ON RL
Hboot-2.13.0000
Radio-1.11.50.05.28
Open DSP-v31.1.0.45.0815
eMMC-boot
Nov 20 2012 , 15:44:03,-1
------------------------------
Click to expand...
Click to collapse
Hi, I basically did the same thing as the OP. Deleted my backups by accident by choosing Factory Reset instead of Recovery. I think I am in an even worse position as I thought I had the right RUU as one point and needed to relock the bootloader. My bootloader screen looks like this at the moment.
------------------------------
*** TAMPERED ***
*** RELOCKED ***
*** Security Warning ***
VLE PVT SHIP S-ON RL
Hboot-2.13.0000
Radio-1.11.50.05.28
Open DSP-v31.1.0.45.0815
eMMC-boot
Nov 20 2012 , 15:44:03,-1
------------------------------
Can anyone tell me if this is a lost cause? Thanks.
This is the RUU I used -
OTA_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_1.11.50.05.28_10.27.50.08L_release_301852xf01hejl416oev96.zip.
Does anyone know if this is definitely the wrong one?

To all: Guys, no need to use S-Off for RUU. I DON'T KNOW WHO THE F*** CREATED THE PROCESS OF S-OFFING FOR RUUs AS WHEN I RESTORE STOCK LAST YEAR, IT WAS A SIMPLE BOOTLOADER RELOCK, AND RUU WE GO. IF WE S-OFFED, WE S-ON USING ONE-TOUCH STUFF.
To folaxstar: Well, you got as far as him. However, you got the COMPLETELY WRONG RUU. Technically, IT'S NOT AN RUU AT ALL. It is a Android 4.1 Sense 4.5/+ update for European unlocked HTC One S.
Do a "fastboot getvar cid" without the quotes (of course). You should get a CID that looks like the following: T-MOB010(T-Mobile US, as an example, it might not match what you got). Someone could determine the correct RUU.

Firmware Update Q&A [extra noob friendly]

WARNING*WARNING*WARNING
do this at your own risk! This is for s4 only!!
It has been brought to my attention that there might be a mid (model id) conflict
With flashing this and me along with others are trying to narrow down the issue. Thanks to @real187 for bring this to my attention.
I'm
S-off
Cid 11111111
MID PJ4011000
And had no problems flashing this firmware but others with same setup have reported soft brick.
OK I think @mkinney88 may have pin pointed where the soft brick may be coming from. If you s-off using facepalm, flash the firmware.zip and get soft bricked try this.
1. Get back to s-on (warning read directions several times before doing you CAN hard brick your phone) ~ http://forum.xda-developers.com/showthread.php?p=38267667
2. Get s-off with moonshine ~ http://forum.xda-developers.com/showthread.php?p=42613403
First off this is mostly ment for the T-Mobile branded phones but ill try and help all please let me know when asking questions if you have a T-Mobile or HTC branded phone (it has it right on the front of phone ).
I'm starting this thread to have a place for noobs and long time users to ask and answer questions. This is going to be as noob friendly as possible but please keep questions firmware related only. So lets get started.
i really dont know how to make it any clearer then @mkinney88 did in his rom OP. all credit goes to him these institutions.
By: Mkinney88 (UnKnown_ROMS)
--> Unlock your device
Step1. download and use this program to unlock your bootloader http://forum.xda-developers.com/show....php?t=1604677
Step2. SuperCID your phone so you can S-OFF and so you can also write the T-MOB010 CID if you are on a different carrier and want to run this ROM. You will need to be CID T-MOB010 if you want to run the firmware.zip Follow this to SuperCID http://forum.xda-developers.com/show...1#post26516911
Step3. After you have sucessfully unlocked your bootloader and SuperCID you can either S-OFF your phone or Not, it is up to you. I would recommend you achieve S-OFF so you can flash radios, kernels, and boot.img's. Follow this to achieve S-OFF http://forum.xda-developers.com/show....php?t=2155135
If everything went well you should be able to reboot into bootloader using the All In One Tool and in the top left your bootloader should say Unlocked, S-OFF, CID-1111111
--> Writing T-MOB010 CID
If you did everything right then your all set. Next you will want to run the fastboot command " fastboot oem writecid T-MOB010 " and reboot into bootloader again. Now in the top left it should say CID-T-MOB010. If you have made it this far you are doing great. Now we are going to run the firmware.zip package to ensure everything works without a problem.
--> Flashing the firmware.zip
Now if you are coming from STOCK OEM LOCKED T-MOBILE PHONE that already has Andorid 4.1.1 Jelly Bean on it then you do not need to do this step. You must be CID T-MOB010 to flash this or S-OFF CID 11111111 (I had no problem flashing firmware with s-off and Cid 11111111 but others have reported problems so if you don't want to chance it write your Cid to T-MOB010)
1. fastboot oem lock
2. fastboot erase cache
3. fastboot oem rebootRUU
4. fastboot flash zip firmware.zip, and you might get an error
5. fastboot flash zip firmware.zip again and it should pass and install a bunch of files should take about 2 minutes.
6. the phone does NOT reboot on its own so #7
7. fastboot reboot or fastboot reboot-bootloader
--> UNLOCKING BOOTLOADER AGAIN
Now we need to unlock the bootloader again so just do step 1 again but you will already have the Unlock_code.bin from the first time you unlocked you phone so no need to get another one from HTC but if for some funny reason it doesn't work you will need to just resubmit for a new one.
--> CUSTOM RECOVERY
After doing all the above steps you will need to install the custom recover. You will need to use TWRP 2.3.3 to insure no problems. Here is the link to download it http://techerrata.com/file/twrp2/vil....3.0-ville.img after you download it go to the DIR where you have the HTC One S All-In-One Toolkit v3.5 extracted. example: C:\Users\yourusername\Downloads\One_S_All-In-One_Kit_v3.5\One_S_All-In-One_Kit_v3.5\Data\Recoveries and in the Recoveries folder rename the downloaded twrp2.3.3.img to TWRPS4.img and replace the one that is in the folder and then proceed to install the recovery,
now youve followed that and now your stuck ether getting errors or phone is now acting all erratic? that's why you're here. go ahead ask any question you want about firmware noobish,dumb,anything as long as its firmware related. (sorry i cant tell you how to get the cute girl at the mall)
this is just a crude start ill add and refine as we get going.
please do don't ask firmware questions in development threads ask here.
If you want to see mkinney88's full guide go here paste bin

Downloads
FIRMWARE ZIP DOWNLOAD
https://drive.google.com/folderview?id=0B-BYnLh2sosKamRwaUJJS05oU3M&usp=sharing or http://db.tt/Wua8mDS2
Credit go's to mkinney88 for the firmware

Bricks
First off if you can get into bootloader then you don't have a hard brick.
If your phone is in the black screen of death there may be hope but we're still trying to figure that one out.
If your phone doesn't respond to any input from you (power, power+volume down) then congratulations you have a hard brick but don't through it in the junk drawer just yet, you can have it jtag repaired (they open phone plug into main board and flash everything)
Here's the link (you do have to pay for this)
http://forum.xda-developers.com/showthread.php?p=37136553

One more just in case

rc420head said:
I'm starting this thread to have a place for noobs and long time users to ask and answer questions. This is going to be as noob friendly as possible but please keep questions firmware related only. So lets get started.
i really dont know how to make it any clearer then @mkinney88 did in his rom OP. all credit goes to him these institutions.
By: Mkinney88 (UnKnown_ROMS)
--> Unlock your device
Step1. download and use this program to unlock your bootloader http://forum.xda-developers.com/show....php?t=1604677
Step2. SuperCID your phone so you can S-OFF and so you can also write the T-MOB010 CID if you are on a different carrier and want to run this ROM. You will need to be CID T-MOB010 if you want to run the firmware.zip Follow this to SuperCID http://forum.xda-developers.com/show...1#post26516911
Step3. After you have sucessfully unlocked your bootloader and SuperCID you can either S-OFF your phone or Not, it is up to you. I would recommend you achieve S-OFF so you can flash radios, kernels, and boot.img's. Follow this to achieve S-OFF http://forum.xda-developers.com/show....php?t=2155135
If everything went well you should be able to reboot into bootloader using the All In One Tool and in the top left your bootloader should say Unlocked, S-OFF, CID-1111111
--> Writing T-MOB010 CID
If you did everything right then your all set. Next you will want to run the fastboot command " fastboot oem writecid T-MOB010 " and reboot into bootloader again. Now in the top left it should say CID-T-MOB010. If you have made it this far you are doing great. Now we are going to run the firmware.zip package to ensure everything works without a problem.
--> Flashing the firmware.zip
Now if you are coming from STOCK OEM LOCKED T-MOBILE PHONE that already has Andorid 4.1.1 Jelly Bean on it then you do not need to do this step. You must be CID T-MOB010 to flash this or S-OFF CID 11111111
1. fastboot oem lock
2. fastboot erase cache
3. fastboot oem rebootRUU
4. fastboot flash zip firmware.zip, and you might get an error
5. fastboot flash zip firmware.zip again and it should pass and install a bunch of files should take about 2 minutes.
6. the phone does NOT reboot on its own so #7
7. fastboot reboot or fastboot reboot-bootloader
--> UNLOCKING BOOTLOADER AGAIN
Now we need to unlock the bootloader again so just do step 1 again but you will already have the Unlock_code.bin from the first time you unlocked you phone so no need to get another one from HTC but if for some funny reason it doesn't work you will need to just resubmit for a new one.
--> CUSTOM RECOVERY
After doing all the above steps you will need to install the custom recover. You will need to use TWRP 2.3.3 to insure no problems. Here is the link to download it http://techerrata.com/file/twrp2/vil....3.0-ville.img after you download it go to the DIR where you have the HTC One S All-In-One Toolkit v3.5 extracted. example: C:\Users\yourusername\Downloads\One_S_All-In-One_Kit_v3.5\One_S_All-In-One_Kit_v3.5\Data\Recoveries and in the Recoveries folder rename the downloaded twrp2.3.3.img to TWRPS4.img and replace the one that is in the folder and then proceed to install the recovery,
now youve followed that and now your stuck ether getting errors or phone is now acting all erratic? that's why you're here. go ahead ask any question you want about firmware noobish,dumb,anything as long as its firmware related. (sorry i cant tell you how to get the cute girl at the mall)
this is just a crude start ill add and refine as we get going.
please do don't ask firmware questions in development threads ask here.
If you want to see mkinney88's full guide go here paste bin
Click to expand...
Click to collapse
Don't flash the firmware on SuperCID which leads to brick, which can be recovered though

vatsaman said:
Don't flash the firmware on SuperCID which leads to brick, which can be recovered though
Click to expand...
Click to collapse
Bricks can't be recovered (unless you jtag) , you had a soft brick.
I had no problem doing this with s-off and Cid 11111111.
But I remember you from other threads and I have a few questions.
1. Is your phone t-mobile branded or htc? 2. When you first did the firmware update what was your hboot version?
-----------------------------------------
Friends don't let friends post without searching first!

I put a note of this in op just now, thanks for the warning, I'm trying to figure out why some can do this Cid 11111111 and some can't.
-----------------------------------------
Friends don't let friends post without searching first!

rc420head said:
Bricks can't be recovered (unless you jtag) , you had a soft brick.
I had no problem doing this with s-off and Cid 11111111.
But I remember you from other threads and I have a few questions.
1. Is your phone t-mobile branded or htc? 2. When you first did the firmware update what was your hboot version?
-----------------------------------------
Friends don't let friends post without searching first!
Click to expand...
Click to collapse
Yeah mine was a softbrick. If you stroll over, u can find many people in my queue. May be it is happening only for people who got S-OFF with the Facepalm way. I was on Hboot 1.14 and so a T Mob branded one.
Also you will see a warning in Facepalm thread that flashing firmware on SuperCID phones likey causes a brick.

vatsaman said:
Yeah mine was a softbrick. If you stroll over, u can find many people in my queue. May be it is happening only for people who got S-OFF with the Facepalm way. I was on Hboot 1.14 and so a T Mob branded one.
Also you will see a warning in Facepalm thread that flashing firmware on SuperCID phones likey causes a brick.
Click to expand...
Click to collapse
Something else is going on. I used facepalm, and Cid 11111111 to flash firmware twice now with no issues and started same as you hboot 1.14
-----------------------------------------
Friends don't let friends post without searching first!

thank you!

I'm on Stock JB 4.1.1 and my CID is BM___001, rooted, unlocked BL.
There is no RUU for this CID and only a JB OTA, The radio version and software version match with those of the phone.
my question is: Without S-OFF and SuperCID, Can I use the OTA.zip to be flashed for getting stock ROM? e.g if I am on CM 10.1 and I want to revert back to stock, can I use the OTA.zip?

khan.orak said:
I'm on Stock JB 4.1.1 and my CID is BM___001, rooted, unlocked BL.
There is no RUU for this CID and only a JB OTA, The radio version and software version match with those of the phone.
my question is: Without S-OFF and SuperCID, Can I use the OTA.zip to be flashed for getting stock ROM? e.g if I am on CM 10.1 and I want to revert back to stock, can I use the OTA.zip?
Click to expand...
Click to collapse
I'm not sure if I understand your question. So let me ask a few questions.
What hboot are you on?
What carrier are you using?
Are you wanting to try cm 10.1 and afraid for losing stock?
What is stock just HTC sense 4+ or is there carrier added stuff?

rc420head said:
I'm not sure if I understand your question. So let me ask a few questions.
Click to expand...
Click to collapse
ok I'll try to make it clearer.
What hboot are you on?
Click to expand...
Click to collapse
I'm on hboot 2.15.0000
What carrier are you using?
Click to expand...
Click to collapse
This phone is from Bell Mobility Canada, but I'm not using this carrier.
Are you wanting to try cm 10.1 and afraid for losing stock?
Click to expand...
Click to collapse
Exactly!! this is what I was asking. There isn't any RUU for stock JB 4.1.1, for the CID BM____001.
What is stock just HTC sense 4+ or is there carrier added stuff?
Click to expand...
Click to collapse
Stock sense is 4+ and is heavily bloated. It has got apps like DropBox, Let's Play Golf, Friend Stream, HTC Media Link HD, Polaris Office etc.

khan.orak said:
ok I'll try to make it clearer.
I'm on hboot 2.15.0000
This phone is from Bell Mobility Canada, but I'm not using this carrier.
Exactly!! this is what I was asking. There isn't any RUU for stock JB 4.1.1, for the CID BM____001.
Stock sense is 4+ and is heavily bloated. It has got apps like DropBox, Let's Play Golf, Friend Stream, HTC Media Link HD, Polaris Office etc.
Click to expand...
Click to collapse
OK since your on hboot 2.15 there's no need to upgrade firmware.
Since there is no RUU for stock the next best thing would to to make a back-up of stock using a custom recovery I would recommend twrp 2.3.3 (if you need help with this just ask that's what this thread is for)
Then I would copy the back up to your pc for safe keeping (you might even want to back it up on a cloud too I'd recommend goggle drive or Dropbox)

rc420head said:
OK since your on hboot 2.15 there's no need to upgrade firmware.
Since there is no RUU for stock the next best thing would to to make a back-up of stock using a custom recovery I would recommend twrp 2.3.3 (if you need help with this just ask that's what this thread is for)
Then I would copy the back up to your pc for safe keeping (you might even want to back it up on a cloud too I'd recommend goggle drive or Dropbox)
Click to expand...
Click to collapse
Thanks for the reply, really much appreciated.
I already have rooted the device and custom recovery TWRP 2.5. Though I am considering to downgrade it to 2.3.30. Now I made a backup of stock ROM. (System + Boot Partition)
So is this the only way I can get to stock?
I read somewhere that the following method could be used too(?)
S-OFF ---> Run an older RUU for Bell Mobility (probably ICS RUU) ---> Then update OTA.
Is this valid?

khan.orak said:
S-OFF ---> Run an older RUU for Bell Mobility (probably ICS RUU) ---> Then update OTA.
Is this valid?
Click to expand...
Click to collapse
Yes, if an older RUU is available for your CID just get S-OFF first then use it. Then you'll be able to update via OTA.
Sent from my HTC VLE_U using xda app-developers app

ardax said:
Yes, if an older RUU is available for your CID just get S-OFF first then use it. Then you'll be able to update via OTA.
Sent from my HTC VLE_U using xda app-developers app
Click to expand...
Click to collapse
Big thanks! :good:

vatsaman said:
Yeah mine was a softbrick. If you stroll over, u can find many people in my queue. May be it is happening only for people who got S-OFF with the Facepalm way. I was on Hboot 1.14 and so a T Mob branded one.
Also you will see a warning in Facepalm thread that flashing firmware on SuperCID phones likey causes a brick.
Click to expand...
Click to collapse
This is very interesting to me because I have a unbranded one s from a small spinoff of T-mo in Iowa. I got s-off with facepalm and SuperCID at the same time, then on hboot 1.13. Now recently I upgraded hboot to 2.15 with a euro RUU, soft bricked but was able to recover with only a firmware flash. (details are a bit fuzzy right now) I didn't relock the bootloader, but did install stock recovery. Ever after this stunt I've had tons of problems with radio disconnects. I first thought my problem was hardware, but I just got it back from a very good repair shop and the same thing. Although better on a different carrier, I suspect only because the better carrier has stronger signal. I'm ready to try a older RUU or euro firmware or just about anything, this phone only has service 10% of the time where it used to be 100% right now I'm running the latest Trickdroid 10.3.2 Changing the fast.dormancy=2 helped a tiny bit but it's something more fundamental than that I'm thinking... Sugg anyone??
Prolly should add I'm using the euro 1.15 radio. Thanks
Edit, looks like maybe my problems may only be build prop related, if I change to.til.radio.svn=19 to 5 I get an instant connection, but only G...
ro.ril.hsdpa.category=28
ro.ril.hsupa.category=7
ro.ril.fast.dormancy.rule=0
ro.ril.radio.svn=5
Sent from my HTC One S using xda app-developers app

ardax said:
Yes, if an older RUU is available for your CID just get S-OFF first then use it. Then you'll be able to update via OTA.
Sent from my HTC VLE_U using xda app-developers app
Click to expand...
Click to collapse
Yes this will also work (I was under the impression no ruu's were available)
khan.orak said:
Big thanks! :good:
Click to expand...
Click to collapse

forgiven90 said:
This is very interesting to me because I have a unbranded one s from a small spinoff of T-mo in Iowa. I got s-off with facepalm and SuperCID at the same time, then on hboot 1.13. Now recently I upgraded hboot to 2.15 with a euro RUU, soft bricked but was able to recover with only a firmware flash. (details are a bit fuzzy right now) I didn't relock the bootloader, but did install stock recovery. Ever after this stunt I've had tons of problems with radio disconnects. I first thought my problem was hardware, but I just got it back from a very good repair shop and the same thing. Although better on a different carrier, I suspect only because the better carrier has stronger signal. I'm ready to try a older RUU or euro firmware or just about anything, this phone only has service 10% of the time where it used to be 100% right now I'm running the latest Trickdroid 10.3.2 Changing the fast.dormancy=2 helped a tiny bit but it's something more fundamental than that I'm thinking... Sugg anyone??
Prolly should add I'm using the euro 1.15 radio. Thanks
Edit, looks like maybe my problems may only be build prop related, if I change to.til.radio.svn=19 to 5 I get an instant connection, but only G...
ro.ril.hsdpa.category=28
ro.ril.hsupa.category=7
ro.ril.fast.dormancy.rule=0
ro.ril.radio.svn=5
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Yeah disabling the fast dormancy solved all my problems. :good:

[Q] Cannot flash any roms!

I've searched far and wide, and I found a lot of threads regarding the specifics of my problem, but none that solve it. A point in the right direction is much appreciated.
I have an AT&T HTC One X (used to be S-OFF now S-ON), unlocked, HBOOT 1.12.0002 CID 1111111
I've been running CM 10.1.3 for a while now and it's very glitchy and causes random reboots and freezes. I've been trying to upgrade to 10.2 or try a variety of different roms. When flashing I kept getting the following error: E:Error executing updater binary in zip..
I lived with the rom for a while because of the error, but today got fed up. I googled it and found out TWRP was probably the problem so I downgraded to 2.3.3.0. Then I got a (Status 7) error which means either that the ROM is not for the Evita (not true) or TWRP is out of date (true but necessary). I tried getting the .zip to stop checking what phone it was, didn't work.
SO I wonder if I have to upgrade HBOOT? I google it and try this guide.
It all worked up until the adb part, where at first it said the device was not there, then that it was offline, then it said permission denied. So I tried again thinking I did something wrong, but after flashing zip it said "FAILED(remote:99 unknown fail).
Now my phone is S-ON and stuck in bootloop. I'll flash boot.img and hopefully it will be fine, but I just want to know what the hell is wrong with my phone, any ideas? I cannot possibly continue with this stupid ROM as it's driving me nuts, but PHONE NOT COOPERATING.
Thanks!!!!!

Flashing boot.img did not work. I'm in bootloop hell.

mollysue said:
I've searched far and wide, and I found a lot of threads regarding the specifics of my problem, but none that solve it. A point in the right direction is much appreciated.
I have an AT&T HTC One X (used to be S-OFF now S-ON), unlocked, HBOOT 1.12.0002 CID 1111111
I've been running CM 10.1.3 for a while now and it's very glitchy and causes random reboots and freezes. I've been trying to upgrade to 10.2 or try a variety of different roms. When flashing I kept getting the following error: E:Error executing updater binary in zip..
I lived with the rom for a while because of the error, but today got fed up. I googled it and found out TWRP was probably the problem so I downgraded to 2.3.3.0. Then I got a (Status 7) error which means either that the ROM is not for the Evita (not true) or TWRP is out of date (true but necessary). I tried getting the .zip to stop checking what phone it was, didn't work.
SO I wonder if I have to upgrade HBOOT? I google it and try this guide.
It all worked up until the adb part, where at first it said the device was not there, then that it was offline, then it said permission denied. So I tried again thinking I did something wrong, but after flashing zip it said "FAILED(remote:99 unknown fail).
Now my phone is S-ON and stuck in bootloop. I'll flash boot.img and hopefully it will be fine, but I just want to know what the hell is wrong with my phone, any ideas? I cannot possibly continue with this stupid ROM as it's driving me nuts, but PHONE NOT COOPERATING.
Thanks!!!!!
Click to expand...
Click to collapse
Since you are S-On with SuperCID, I would say to revert back to your original CID and then flash the appropriate RUU. Make sure you definitely change back to your original CID, as trying to run the RUU with S-ON and SuperCID will brick your phone. You can then re-SuperCID your phone, unlock the bootloader, and try a new custom ROM. I would also recommend getting back to S-OFF after doing all of the above.
Sent from my HTC One XL using XDA Premium 4 mobile app

Hang on, there's something very fishy here. The hboot 1.12 is not an Evita hboot, that's an Endeavoru hboot. Please post your hboot details (the first five lines in bootloader), and please post the full filename of the ROM you're flashing.
I believe you're confused as to which device you actually have, and you're potentially trying to flash a ROM that isn't meant for your device.
Sent from my Evita

mollysue said:
I've searched far and wide, and I found a lot of threads regarding the specifics of my problem, but none that solve it. A point in the right direction is much appreciated.
I have an AT&T HTC One X (used to be S-OFF now S-ON), unlocked, HBOOT 1.12.0002 CID 1111111
I've been running CM 10.1.3 for a while now and it's very glitchy and causes random reboots and freezes. I've been trying to upgrade to 10.2 or try a variety of different roms. When flashing I kept getting the following error: E:Error executing updater binary in zip..
I lived with the rom for a while because of the error, but today got fed up. I googled it and found out TWRP was probably the problem so I downgraded to 2.3.3.0. Then I got a (Status 7) error which means either that the ROM is not for the Evita (not true) or TWRP is out of date (true but necessary). I tried getting the .zip to stop checking what phone it was, didn't work.
SO I wonder if I have to upgrade HBOOT? I google it and try this guide.
It all worked up until the adb part, where at first it said the device was not there, then that it was offline, then it said permission denied. So I tried again thinking I did something wrong, but after flashing zip it said "FAILED(remote:99 unknown fail).
Now my phone is S-ON and stuck in bootloop. I'll flash boot.img and hopefully it will be fine, but I just want to know what the hell is wrong with my phone, any ideas? I cannot possibly continue with this stupid ROM as it's driving me nuts, but PHONE NOT COOPERATING.
Thanks!!!!!
Click to expand...
Click to collapse
Code:
adb version
How u get S-ON again anyway after S-OFF......FAILED 99 : check your adb version by entering this on your adb folder......most likely u got 1.0.29 version which is always show device offline....u need to update it to 1.0.31 version ....check other Q&A thread.....it been talking over and over again......if u do first XDA rules.....READ. As per timmaaa requested ......in case u dont know ...... power off your phone.....then hold both power button+vol down for few second and only let go power button while u still holding vol down.....this will bring u to bootloader
timmaaa said:
Hang on, there's something very fishy here. The hboot 1.12 is not an Evita hboot, that's an Endeavoru hboot. Please post your hboot details (the first five lines in bootloader), and please post the full filename of the ROM you're flashing.
I believe you're confused as to which device you actually have, and you're potentially trying to flash a ROM that isn't meant for your device.
Sent from my Evita
Click to expand...
Click to collapse
I thought so.....hboot 1.12......

timmaaa said:
Hang on, there's something very fishy here. The hboot 1.12 is not an Evita hboot, that's an Endeavoru hboot. Please post your hboot details (the first five lines in bootloader), and please post the full filename of the ROM you're flashing.
I believe you're confused as to which device you actually have, and you're potentially trying to flash a ROM that isn't meant for your device.
Sent from my Evita
Click to expand...
Click to collapse
Good catch Timmaaa!
Sent from my HTC One XL using XDA Premium 4 mobile app

//JavaJ said:
Since you are S-On with SuperCID, I would say to revert back to your original CID and then flash the appropriate RUU. Make sure you definitely change back to your original CID, as trying to run the RUU with S-ON and SuperCID will brick your phone. You can then re-SuperCID your phone, unlock the bootloader, and try a new custom ROM. I would also recommend getting back to S-OFF after doing all of the above.
Sent from my HTC One XL using XDA Premium 4 mobile app
Click to expand...
Click to collapse
****, what's my original CID, I didn't write it down?
Hang on, there's something very fishy here. The hboot 1.12 is not an Evita hboot, that's an Endeavoru hboot. Please post your hboot details (the first five lines in bootloader), and please post the full filename of the ROM you're flashing.
I believe you're confused as to which device you actually have, and you're potentially trying to flash a ROM that isn't meant for your device.
Sent from my Evita
Click to expand...
Click to collapse
I must have read it wrong then, SORRY.
It says:
EVITA PVT SHIP S-ON RL
HBOOT-1.140002
RADIO-0.19as.32.09.11_2
OpenDSP-v29.1.0.45.0622
eMMC-boot
Jun 111 2012

timmaaa said:
Hang on, there's something very fishy here. The hboot 1.12 is not an Evita hboot, that's an Endeavoru hboot. Please post your hboot details (the first five lines in bootloader), and please post the full filename of the ROM you're flashing.
I believe you're confused as to which device you actually have, and you're potentially trying to flash a ROM that isn't meant for your device.
Sent from my Evita
Click to expand...
Click to collapse
ted77usa said:
Code:
adb version
How u get S-ON again anyway after S-OFF......FAILED 99 : check your adb version by entering this on your adb folder......most likely u got 1.0.29 version which is always show device offline....u need to update it to 1.0.31 version ....check other Q&A thread.....it been talking over and over again......if u do first XDA rules.....READ. As per timmaaa requested ......in case u dont know ...... power off your phone.....then hold both power button+vol down for few second and only let go power button while u still holding vol down.....this will bring u to bootloader
I thought so.....hboot 1.12......
Click to expand...
Click to collapse
No I have "Android Debug Bridge version 1.0.31".

Ah ok, that makes more sense! Are you absolutely sure the ROM you're flashing is an Evita ROM? Where did you download it and what is the full filename?
You said the phone was s-on but not anymore? Why did you return it to s-on? You're gonna need to get s-off again so you can RUU up to 3.18 so you can flash the recent aosp ROMs. When you get the error 99 after flashing the zip, just force a reboot back to bootloader by holding volume down and power together. Once you're back in bootloader you can start again (without the adb reboot bootloader command because you're already in bootloader) and you should get error 92 now. Now, before you give the adb soffbin commands you need to make sure the screen is unlocked and stays unlocked, also make sure usb debugging is enabled in developer options. If it's an aosp ROM you'll also need to grant root access to adb in developer options.
For now my suggestion would be to download a Sense ROM, preferably Android 4.0 or 4.1, this should at least boot and enable you to get s-off on your phone again. Don't forget top flash the boot.img via fastboot.
Sent from my Evita
---------- Post added at 07:27 PM ---------- Previous post was at 07:25 PM ----------
mollysue said:
No I have "Android Debug Bridge version 1.0.31".
Click to expand...
Click to collapse
Your adb version is fine, you can leave that the way it is.
Sent from my Evita

mollysue said:
****, what's my original CID, I didn't write it down?
I must have read it wrong then, SORRY.
It says:
EVITA PVT SHIP S-ON RL
HBOOT-1.140002
RADIO-0.19as.32.09.11_2
OpenDSP-v29.1.0.45.0622
eMMC-boot
Jun 111 2012
Click to expand...
Click to collapse
Well if u said is right on OP......U bought AT&T HTC ONE X it should have AT&T LOGO in the front......if u do that mean your original CID I believe if I'm not mistaken are CWS__001 . If I were u ......I just keep continue try S-OFF first by going back to Android 4.0 ICS Rom and flash original rom boot.img manually from fastboot and check my other Q&A THREAD coz I had same error with u.......but I'm S-OFF now
Swyped From BlueICESense_JBE

ted77usa said:
Well if u said is right on OP......U bought AT&T HTC ONE X it should have AT&T LOGO in the front......if u do that mean your original CID I believe if I'm not mistaken are CWS__001 . If I were u ......I just keep continue try S-OFF first by going back to Android 4.0 ICS Rom and flash original rom boot.img manually from fastboot and check my other Q&A THREAD coz I had same error with u.......but I'm S-OFF now
Swyped From BlueICESense_JBE
Click to expand...
Click to collapse
ted77usa said:
Well if u said is right on OP......U bought AT&T HTC ONE X it should have AT&T LOGO in the front......if u do that mean your original CID I believe if I'm not mistaken are CWS__001 . If I were u ......I just keep continue try S-OFF first by going back to Android 4.0 ICS Rom and flash original rom boot.img manually from fastboot and check my other Q&A THREAD coz I had same error with u.......but I'm S-OFF now
Swyped From BlueICESense_JBE
Click to expand...
Click to collapse
I decided to boot into recovery and flash CM 10.0.0, and so I got out of bootloop. It's very glitchy, the keyboard keeps crashing, but it "works".
Now I'm trying to get S-OFF using this tool. At first it didn't work, so I changed the CID back to original. Now I get the following error:
Before we continue:
Ensure your phone is rooted.
Disable "Fast boot" on the phone under Settings -> Power.
Enable "USB Debugging" under Settings -> Developer Options.
Make sure your HTC One XL is connected to your mac via a USB cable.
When you're ready, press return to continue...
Copying your misc partition to your sdcard partition...
Unknown id: if=/dev/block/mmcblk0p4
Copying the file to your computer so we can work with it...
remote object '/sdcard/mmcblk0p4' does not exist
Making a backup copy here too...
cp: tmp/mmcblk0p4: No such file or directory
Changing CID to Super CID in local copy...
unable to read input file tmp/mmcblk0p4 at /Users/user/Downloads/OneXL_SuperCID_Mac_v1_1/bin/HOX_bin_partition_edit.pl line 22.
ERROR
There was a problem converting the CID in the local copy of your binary partition
and we can not continue.
Press return to exit
It might be that I did not disable fastboot, but that is because the option is just not available on the phone, there is no "Power" category. I did enable debugging, but there was no notification in the menu bar making me maybe think that the OS is just too glitchy for this to work.
I didn't know what else to do, tried unlocking the bootloader through HTCDev but when I got to step 13 the notification did not come on screen like it was supposed to and so that was unsuccessful. I guess this was a silly idea.
I'm trying to be as descriptive as possible in case this happens to anyone else!
Cannot find stock Android 4.1 as suggested, for some reason. I found this, but I have a mac and .exe files mean nothing to me. I figure 10.0.0 has to be as stable as it gets with what I have, so I reflashed and boot.img. Now I'm stuck in bootloop again! Am I not meant to have nice things?
Could you suggest a rom to download and flash? After that I'll try S-OFF via Facepalm again.

mollysue said:
I decided to boot into recovery and flash CM 10.0.0, and so I got out of bootloop. It's very glitchy, the keyboard keeps crashing, but it "works".
Now I'm trying to get S-OFF using this tool. At first it didn't work, so I changed the CID back to original. Now I get the following error:
Before we continue:
Ensure your phone is rooted.
Disable "Fast boot" on the phone under Settings -> Power.
Enable "USB Debugging" under Settings -> Developer Options.
Make sure your HTC One XL is connected to your mac via a USB cable.
When you're ready, press return to continue...
Copying your misc partition to your sdcard partition...
Unknown id: if=/dev/block/mmcblk0p4
Copying the file to your computer so we can work with it...
remote object '/sdcard/mmcblk0p4' does not exist
Making a backup copy here too...
cp: tmp/mmcblk0p4: No such file or directory
Changing CID to Super CID in local copy...
unable to read input file tmp/mmcblk0p4 at /Users/user/Downloads/OneXL_SuperCID_Mac_v1_1/bin/HOX_bin_partition_edit.pl line 22.
ERROR
There was a problem converting the CID in the local copy of your binary partition
and we can not continue.
Press return to exit
It might be that I did not disable fastboot, but that is because the option is just not available on the phone, there is no "Power" category. I did enable debugging, but there was no notification in the menu bar making me maybe think that the OS is just too glitchy for this to work.
I didn't know what else to do, tried unlocking the bootloader through HTCDev but when I got to step 13 the notification did not come on screen like it was supposed to and so that was unsuccessful. I guess this was a silly idea.
I'm trying to be as descriptive as possible in case this happens to anyone else!
Cannot find stock Android 4.1 as suggested, for some reason. I found this, but I have a mac and .exe files mean nothing to me. I figure 10.0.0 has to be as stable as it gets with what I have, so I reflashed and boot.img. Now I'm stuck in bootloop again! Am I not meant to have nice things?
Could you suggest a rom to download and flash? After that I'll try S-OFF via Facepalm again.
Click to expand...
Click to collapse
Well try any ICSbase rom......i did tried cleanrom 4.2 ICS base Rom sense 4.......but since u on 1.14 hboot u need to extract boot.img from original Rom to your working adb/fastboot folder and push it manually from fastboot.....
1.put ICS of your choice inside ur SD card
2.copy or extract boot.img from Rom you about to flash and place it inside your working adb/fastboot folder.
3.connect your phone to PC and make sure USB debugging check....and HTC driver install properly
4. Flash Rom from recovery and choose go back> reboot> bootloader and this would bring u to fastboot USB mode if u have correct driver install and USB debugging check .
5. Go to your adb/fastboot folder hold shift+right click > open command Window .....and enter code to push boot. img tru fastboot......I forgot the code...but I'm sure timmaaa knew out of his head......
6.if successfull......reboot system and u should have working ics sense 4 Rom
7.play with it a day or too before u attempt facepalm S-OFF and in the mean time do more reading.......
Swyped From BlueICESense_JBE

ted77usa said:
Well try any ICSbase rom......i did tried cleanrom 4.2 ICS base Rom sense 4.......but since u on 1.14 hboot u need to extract boot.img from original Rom to your working adb/fastboot folder and push it manually from fastboot.....
1.put ICS of your choice inside ur SD card
2.copy or extract boot.img from Rom you about to flash and place it inside your working adb/fastboot folder.
3.connect your phone to PC and make sure USB debugging check....and HTC driver install properly
4. Flash Rom from recovery and choose go back> reboot> bootloader and this would bring u to fastboot USB mode if u have correct driver install and USB debugging check .
5. Go to your adb/fastboot folder hold shift+right click > open command Window .....and enter code to push boot. img tru fastboot......I forgot the code...but I'm sure timmaaa knew out of his head......
6.if successfull......reboot system and u should have working ics sense 4 Rom
7.play with it a day or too before u attempt facepalm S-OFF and in the mean time do more reading.......
Swyped From BlueICESense_JBE
Click to expand...
Click to collapse
Thanks!!!! The rom worked. I'm going to let it sit for a while before doing any more tampering. At least I have a working phone *happy dance*

[Q] My HTC One X AT&T has signal issues and random reboots

Hi everybody i flash my htc one x at&t with android 4.2.2 (sense5), i used urdroid version --------->(http://forum.xda-developers.com/showthread.php?t=2331373) and now my phone lost the signal and random reboots, i heard that the problem is the kernel but i don't know what kernel i should install. hope you can help me.
Thanks.
EVITA PVT SHIP S-ON RL
HBOOT-1.14.0002
RADIO-0.19as 32.09.11_2
OpenDSP-v29.1.0.45.0622
eMMC-boot

Please search properly before posting next time, the answer has been discussed dozens of times in every single Sense 5 ROM thread.
1. Search before posting.
Use one of our search functions before posting or creating a new thread. Whether you have a question or just something new to share, it's very likely that someone has already asked that question or shared that news.
Click to expand...
Click to collapse
You can flash the Beastmode kernel to fix the problem but the real solution is to flash the 2.15 firmware package. You'll find it (along with detailed instructions) in Turge's stock Sense 5 ROM thread in our Android Development section.
Sent from my Evita

Thanks for the answer
Could you send me the link please
Sent from my HTC One XL using xda app-developers app

I told you exactly where to find it, I'm not going to go and find it for you, that's something you can do for yourself. In the time it took you to write that post your could have already found it and downloaded it.
Sent from my Evita

Thanks dude, i downloaded the beastmode kernel and flash it but now when my phone is starting stuck on at&t logo and then reboot. Do you know why my phone do that?
I'm not super cid and i'm S-ON
Thanks for your answers.

There are a certain group of phones that have a slow SoC, basically they can't handle the Beastmode kernel. You'll need to get s-off and flash the firmware instead. If you need links just look in the Everything Evita thread in my signature. You should bookmark that thread, it contains links to pretty much everything you'll ever need.
Sent from my Evita

Thanks, i'm thinking return to stock rom. Do i have relock my bootloader right? And then run RUU or what do you recomend me to do?

Whatever you do don't run any RUU yet. If you want to return to stock you need to get s-off first. I know you think you don't have SuperCID but if your phone is an at&t model then there's no way you could have unlocked your bootloader without SuperCID. Basically, s-on + SuperCID + jb RUU = brick. So lets check your CID. I'm assuming you have adb/fastboot installed on your PC? If not you need to do that first. Once you have it installed you can connect your phone in fastboot mode (reboot to bootloader and connect), then you need to open a command prompt from within your fastboot folder on your PC (open folder where fastboot.exe is located, shift + right click, select open command prompt here), then issue this command:
Code:
fastboot oem readcid
Tell me what it says.
Sent from my Evita

I was reading about s-off and super cid but I'm new doing this and sounds a little hard to do so don't you think it's better if I install a stock backup
That will solve my problem?

You were right I'm super-cid my cid is: 11111111

S-off is very easy if you already have SuperCID. The biggest obstacle is installing adb/fastboot, if you haven't already. Otherwise, don't worry about being new. We all were at one time. Just read up and understand the process, and follow the instructions carefully, and you will be fine.
---------- Post added at 12:52 PM ---------- Previous post was at 12:50 PM ----------
arthur2820 said:
don't you think it's better if I install a stock backup
Click to expand...
Click to collapse
I don't see how that is in any way "better". If you s-off, all you then need to do is install the 2.15 firmware package, and the signal drop and random reboot issues will disappear.
If you went through the trouble to be able to flash custom ROMs, let's keep it that way.

arthur2820 said:
I was reading about s-off and super cid but I'm new doing this and sounds a little hard to do so don't you think it's better if I install a stock backup
That will solve my problem?
Click to expand...
Click to collapse
arthur2820 said:
You were right I'm super-cid my cid is: 11111111
Click to expand...
Click to collapse
I thought so. Getting s-off is pretty easy, all you need to do is follow some instructions and enter some fastboot and adb commands. Basically, if you can read and type you can do it. As Redpoint said you do need adb/fastboot installed, if you don't already have those you can Google search 'minimal adb and fastboot' and the first result should be a thread that explains how to install it very easily.
We all started somewhere, it might seem a bit daunting at first but I guarantee you it isn't as hard as it seems. Once you get learning it becomes really easy to understand. If you have any questions and can't find answers after some thorough searching just ask, you've got some good people here to assist you.
Sent from my Evita

Thanks I'll try it, could you send me the link of adb/fastboot installer? I guess that the only thing I have to do to install 2.15 formaware it's get s-off
Sent from my HTC One XL using xda app-developers app

See my post right above yours, I've told you what to search for.
Sent from my Evita

i found this thread http://forum.xda-developers.com/showthread.php?t=2155071 i've downloaded the zips bit in the step number 1 i don't know whats means "working directory" the thread it's the correct to get s-off?
how can i flush the image? (step 5)

That's one of the two s-off methods, yes. Your working directory is the folder on your PC where you have adb.exe and fastboot.exe located. You have those installed now right? In order to open the command prompt from that location just shift + right click anywhere in the folder then select open command prompt here.
Sent from my Evita

yes i've installed minimal adb and fastboot. the other method it's easier?

The method you're already using is fine, I used that method and it took me about ten minutes.
Sent from my Evita

ok. mmm but what means flush image again immediately?
Do i have to put the 2 zips in the working directory?

Did you read the instructions? It details exactly what you need to do, follow those directions to the letter. It tells you which zip needs to stay in zip format and which zip needs to be extracted. It tells you what commands to type when the command prompt returns text.
Sent from my Evita

[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.