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] S-OFF F/W 3.14.531.17 (T-MOB) possible?

I have S4 Ville on firmware 3.14.531.17 and need to know if S-OFF is possible using whatever method available. Moonshine thread states that only 3.14.531.11 (T-MOB) is supported and haven't found any details in the Facepalm thread.
Anyone know for sure?

Bump
Sent from my One S using XDA Premium 4 mobile app

My steps I took: (don't know if all were necessary)
Made a backup (nandroid) in recovery and saved it to my pc to be safe.
flashed stock recovery
locked bootloader
ran a RUU.exe to get on the supported firmware.
unlocked bootloader
Then I ran moonshine.
flashed recovery I had before
Restored the backup in recovery and had my original setup plus I was now S-off.

tivofool said:
My steps I took: (don't know if all were necessary)
Made a backup (nandroid) in recovery and saved it to my pc to be safe.
flashed stock recovery
locked bootloader
ran a RUU.exe to get on the supported firmware.
unlocked bootloader
Then I ran moonshine.
flashed recovery I had before
Restored the backup in recovery and had my original setup plus I was now S-off.
Click to expand...
Click to collapse
Well gave this a shot and after 5 hours I am back on CM10.2 with S-ON and latest firmware still.
Thanks for the help though. Cheers.
Anyone else got any idea?

bump

Look for 3.14.531.11. It should be available somewhere. Lock the phone back and RUU it. Then you can unlock again and S-OFF with moonshine.

evrycard said:
Look for 3.14.531.11. It should be available somewhere. Lock the phone back and RUU it. Then you can unlock again and S-OFF with moonshine.
Click to expand...
Click to collapse
He probably cannot downgrade from *.17 to *.11.
I don't know what parts of the firmware moonshine needs. But you could try downgrade using a OTA or Nandroid.

Same here
I'm pretty much stuck with a One-S Bootloader unlocked with S-on.
I can't find a way to get S-Off. Just googling and throwing prayers in the sky someone develops a way.

pyrocide said:
Well gave this a shot and after 5 hours I am back on CM10.2 with S-ON and latest firmware still.
Thanks for the help though. Cheers.
Anyone else got any idea?
Click to expand...
Click to collapse
If that procedure took you 5 hours... Maybe s-off isn't for you.
Sent from my HTC One S using xda app-developers app

havikx said:
If that procedure took you 5 hours... Maybe s-off isn't for you.
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
It took me 5 hours total to begin finding all req's and trying the above method, finding it not to work, redoing the RUU *.17 and getting BACK on CM10.2 and having a phone to make calls with. The method above took maybe 20-30 minutes of double checking and making sure i didn't miss something.

Maybe PM this guy. He posted that it moonshine worked on .17.
http://forum.xda-developers.com/showpost.php?p=45955250&postcount=1091
Ask if he ran moonshine on Linux.

tivofool said:
Maybe PM this guy. He posted that it moonshine worked on .17.
http://forum.xda-developers.com/showpost.php?p=45955250&postcount=1091
Ask if he ran moonshine on Linux.
Click to expand...
Click to collapse
PM'd him for more info. Thanks!

So I was having problems getting s-off as well, eventually I got it done, but it was definitely a big trial and error process.
What I ended up doing was:
1) Get the 3.14.531.11 RUU from http://www.androidruu.com/index.php?developer=Ville (make sure you get the TMOUS one) This link is also provided in the first post in the Android development section
2) I ended up using Moonshine S-Off (http://forum.xda-developers.com/showthread.php?t=2325590) but I needed to use it in conjunction with running it on Ubuntu. Luckily I had a spare hard drive lying around. If you don't, I believe you can run it through the CD as well as long your burn the Ubuntu.iso on a disc. Plug in your phone to the computer and let it do its magic
3) From there, if you wanted to, you can change to SuperCID. Since you have s-off by then, you can change it from the fastboot usb in the bootloader with the line fastboot oem writecid 11111111 (double check, i'm just writing off the top of my head)
4) Then install roms and etc through the usual custom recovery
Note. I tried the Maximus HD, yes it was nice, but it didn't allow me to utilize my phone as a hotspot, so I ended up using the Dark Jelly rom instead. So far it's been very nice. The hotspot works, but the tethering portion is still unavailable. Just my two cents.

I had a hell of a time getting S-OFF pyrocide
Just like you I had H-boot 2.15 and the .17 firmware
here is what you do... this worked for me
download this RUU http://forum.xda-developers.com/showthread.php?t=2279588
adb reboot bootloader
fastboot oem lock
run the RUU
after RUU is loaded and all done 15-20 min
unlock your bootloader with HTC Dev tools
Run moonshine
Works. Promise

tivofool said:
My steps I took: (don't know if all were necessary)
Made a backup (nandroid) in recovery and saved it to my pc to be safe.
flashed stock recovery
locked bootloader
ran a RUU.exe to get on the supported firmware.
unlocked bootloader
Then I ran moonshine.
flashed recovery I had before
Restored the backup in recovery and had my original setup plus I was now S-off.
Click to expand...
Click to collapse
i can say that this worked for me as well. i didn't relock bootloader before installing the 3.14.531.11 ruu though. still worked for me. also installed moonshine on windows. ( guess i'm lucky )

bnd10706 said:
I had a hell of a time getting S-OFF pyrocide
Just like you I had H-boot 2.15 and the .17 firmware
here is what you do... this worked for me
download this RUU http://forum.xda-developers.com/showthread.php?t=2279588
adb reboot bootloader
fastboot oem lock
run the RUU
after RUU is loaded and all done 15-20 min
unlock your bootloader with HTC Dev tools
Run moonshine
Works. Promise
Click to expand...
Click to collapse
You saved me so much time. Thanks!

bnd10706 said:
I had a hell of a time getting S-OFF pyrocide
Just like you I had H-boot 2.15 and the .17 firmware
here is what you do... this worked for me
download this RUU http://forum.xda-developers.com/showthread.php?t=2279588
adb reboot bootloader
fastboot oem lock
run the RUU
after RUU is loaded and all done 15-20 min
unlock your bootloader with HTC Dev tools
Run moonshine
Works. Promise
Click to expand...
Click to collapse
I do not understand meet all the requirement and I run it step by step and still gets stuck in step 3 moonshine I need urgent help, thanks

pyrocide said:
I have S4 Ville on firmware 3.14.531.17 and need to know if S-OFF is possible using whatever method available. Moonshine thread states that only 3.14.531.11 (T-MOB) is supported and haven't found any details in the Facepalm thread.
Anyone know for sure?
Click to expand...
Click to collapse
Test... click here
http://forum.xda-developers.com/showthread.php?t=2569755

[Q]Hboot/Firmware update 2.15 to 2.16 et al.
Sorry wrong thread.

[Q] A quick Q about Evita.

Hi there guys,
Not sure if any of y'all remember way-back-when, but at one point my AT&T One X went into (what seemed like) a bricked state. For 8 months, I didn't touch it, charge it, yada-yada-yada. About 2 weeks ago I decided to give it a go so I charged it for a half hour and the mo'fo' decided to work. I updated my ViperXL ROM to 4.2.0 because I enjoyed it for its features. Now I'm left to ask the question, do I have to update HBOOT to flash a JB 4.3 ROM? I'm still unsure because I feel like I remembered seeing somewhere that your HBOOT has to be a newer version to run 4.3.
Thanks and regards, worldindo1.
NOTE: My current HBOOT version is reading "1.14.002".

Yes you do need to upgrade, it's written in the install instructions for the ROMs. It isn't just the hboot you need to update though, you need to run an RUU to make sure everything gets updated.
Sent from my Evita

timmaaa said:
Yes you do need to upgrade, it's written in the install instructions for the ROMs. It isn't just the hboot you need to update though, you need to run an RUU to make sure everything gets updated.
Sent from my Evita
Click to expand...
Click to collapse
Hey timmaaa,
So just relock bootloader, RUU file, and then unlock it again? Do you know of anyone who has just the firmware upgrade files from the RUU so I can do it from my Linux laptop? Thanks a ton, now I know I wouldn't have any problems or possibly brick my device haha.
Regards, worldindo1.

You need Windows to run an RUU properly, so you'll need to hit up friend to use their PC. You don't need to relock the bootloader as long as you get s-off first so I suggest getting s-off, it's pretty important because s-on + SuperCID + jb RUU = brick.
Sent from my Evita

timmaaa said:
You need Windows to run an RUU properly, so you'll need to hit up friend to use their PC. You don't need to relock the bootloader as long as you get s-off first so I suggest getting s-off, it's pretty important because s-on + SuperCID + jb RUU = brick.
Sent from my Evita
Click to expand...
Click to collapse
Howdy,
I am S-Off thankfully haha. I used XFactor back when it was still current. But I thought the main purpose of an RUU was to execute:
Code:
fastboot oem rebootRUU
fastboot flash zip (firmware).zip
Back when I had done some work with the HTC One V, we used unruu (for Linux) or on the Windows side, explored the RUU's %temp% folder to get the firmware files. Could I still issue those commands safely or have they changed how the RUU works? As well, since I'm S-Off, do I just issue all of the usual commands (minus the "fastboot oem lock") or ? Just making sure to do all of my homework before I jump in haha.
Regards, worldindo1.

Hang on, as far as I know Xfactor was a bootloader unlock exploit, that doesn't give you s-off. There's only one s-off method for our phone and that's the Facepalm method. Having an unlocked bootloader and having s-off are completely different. Can you please post your bootloader details?
Using unruu and pulling the RUU apart and flashing the firmware files is never how an RUU was supposed to be run, nor will it ever be. That's only doing a tiny portion of the job that actually running an RUU properly does. An RUU is an exe file which is meant to be run as an exe file, there is no other way to run it properly other than that. You connect your phone in fastboot mode and run the RUU in Windows and follow the prompts. Like I said though I really need to see your bootloader details (the first four lines) because I'm concerned you have s-off and bootloader unlock confused.
Sent from my Evita

timmaaa said:
Hang on, as far as I know Xfactor was a bootloader unlock exploit, that doesn't give you s-off. There's only one s-off method for our phone and that's the Facepalm method. Having an unlocked bootloader and having s-off are completely different. Can you please post your bootloader details?
Using unruu and pulling the RUU apart and flashing the firmware files is never how an RUU was supposed to be run, nor will it ever be. That's only doing a tiny portion of the job that actually running an RUU properly does. An RUU is an exe file which is meant to be run as an exe file, there is no other way to run it properly other than that. You connect your phone in fastboot mode and run the RUU in Windows and follow the prompts. Like I said though I really need to see your bootloader details (the first four lines) because I'm concerned you have s-off and bootloader unlock confused.
Sent from my Evita
Click to expand...
Click to collapse
Sorry about that my mind just drew a blank. I mixed up xfactor with facepalm haha. Yeah I'm s-off and bootunlocked.
Sent from Marianas Trench.

[Q] Brick or not?

HI all,
I tried to flashed the RUU but it seems that the version I flashed was lower than the one I had.
Now the screen is just black and I can not use the power + down vol to get to fastboot at all.
it will be greatly appreciated if I can get some guidance to get to the fastboot.
Cheers

What exactly did you flash? What does the phone show up on windows as? Does charge light come on when plugged into wall? Did the ruu complete? s-on or s-off?
You really didn't give much info.
Sent from my iPhone using Tapatalk

apology - duplicate post

bricked
thanks you for the response.
sorry I was not sure what info to give.
I was trying to flash RUU asia HK because I originally from STOCK turge but everytime I have a conversation my phone keep shuting down.
so I did (quoting from the instruction page):
Download HTC One X Stock Recovery
Download correct HTC One X boot.img and RUU based on CID. Download CID Getter from Google Play Store and run it, it will show your CID.
For this case, cidnum is HTC_044. The correct RUU is X.XX.707.X. Make sure you have downloaded the correct RUU.
Extract Fastboot.zip into a new folder, renamed the folder to Fastboot. Recommended to extract the folder to drive.
Copy and paste the downloaded stock recovery img and boot img into Fastboot folder.
Boot HTC One X into fastboot mode by press and hold Volume Down + Power button.
Connect your phone to the computer via USB cable.
At your computer, open up Command Prompt windows. (To OpenCommand Prompt –> Windows Logo–> Type CMD in search box –>Enter)
Type fastboot flash recovery endeavoru_recovery_signed.img , followed by fastboot reboot-bootloader and fastboot erase cache.
Once you flashed the stock recovery, continue to flash boot.img to your phone. Type fastboot flash boot boot.img, followed by fastboot reboot-bootloader and fastboot erase cache.
Now, relock the bootloader by typing fastboot oem lock, followed by fastboot reboot-bootloader and fastboot erase cache.
Your phone will restart after you have relock the bootloader.
Boot into Fastboot mode.
Double click the RUU, follow the updater instruction.
Wait the sending file to your phone, it normally takes 5-6 minutes.
Once the installation/update completes, your phone will automatically reboot.
when I last look at the details My CID is still 11111111 but status "RELOCKED" - it says also "EVITA PVT SHIP S-OFF RL"
HBOOT 2.14.0000
does this mean that I can safely run RUU:
RUU_EVITA_UL_ICS_40_S_hTC_Asia_HK_2.42.708.3_Radio_0.20os.32.09.15_10.113.32.28L_release_286715_signed.7z
If there still more things to do, would you kindly direct me to the correct link to follow.
THank you

Never mind, didn't read properly. Will edit and repost.
Sent from my Evita
---------- Post added at 10:48 PM ---------- Previous post was at 10:44 PM ----------
Your first problem is that you're flashing things that aren't intended for your device. The recovery you flashed is for the Endeavoru, you have the Evita. The second problem is it looks like you're getting your information from the wrong place, to go back to stock you don't need to flash a recovery or a boot.img, all you need to do is flash the right RUU for your device. What RUU did you already run? I need the exact filename. Does your phone power on at all? Can you reach the bootloader?
Sent from my Evita
---------- Post added at 10:51 PM ---------- Previous post was at 10:48 PM ----------
I see you're looking at all kinds of different threads at the moment, that isn't going to help because I don't think you know exactly what you're doing, you don't know what you've done, and you don't know how to recover from it. Your best bet is to stay in this thread and I'll try to help you work out what's gone wrong.
Sent from my Evita

RUU_ENDEAVOR_U_JB_45_S_hTC_Asia_HK_3.14.708.28_Radio_5.1204.162.29_release_299865_signed.exe
this is the one I ran earlier.
The progress is that I somehow manage to get to fastboot by pressing the vol down and power .
I am trying to download : RUU_EVITA_UL_JB_45_S_hTC_Asia_WWE_3.17.707.1_Radio_0.23a.32.09.29_10.128.32.34a_release_298958_signed.exe at the moment but it seems that the first download did not complete - so I am downloading again,
is this what I need to do? just run the RUU?
Cheers

ardabelati said:
RUU_ENDEAVOR_U_JB_45_S_hTC_Asia_HK_3.14.708.28_Radio_5.1204.162.29_release_299865_signed.exe
this is the one I ran earlier.
The progress is that I somehow manage to get to fastboot by pressing the vol down and power .
I am trying to download : RUU_EVITA_UL_JB_45_S_hTC_Asia_WWE_3.17.707.1_Radio_0.23a.32.09.29_10.128.32.34a_release_298958_signed.exe at the moment but it seems that the first download did not complete - so I am downloading again,
is this what I need to do? just run the RUU?
Cheers
Click to expand...
Click to collapse
U should download one that has the same radio as yrs also it will take fast download speed otherwise it will keep breaking up. t took me 4 attempts before I manage to download it yesterday (same file as one u r trying) good luck cheers!

You got seriously lucky. You ran an RUU intended for the HTC One X (codename Endeavoru), you don't have that phone. You have the HTC One XL / at&t One X (codename Evita), they're completely different phones. Note how the first RUU you ran has Endeavoru in the filename, that's bad, really bad, don't ever flash anything that doesn't have the Evita codename within the filename. If it has Evita in the filename it's for your phone, if it has anything else don't touch it, burn it, run away. Like I said, you're incredibly lucky your phone isn't bricked right now.
I can only assume that you're a bit confused and have been hopping between the two forums for these phones. In future stay within this device forum that you're posting in now, don't ever go anywhere else. You don't even need to visit other websites because, seriously, everything you'll ever need is right here within this device forum. Plus other sites don't properly distinguish between the models which causes confusion.
Anyway. The second RUU that you've listed there is perfectly fine for your phone. I can't guarantee that it's going to work though because previously running the wrong RUU could have really messed things up on your phone. But your only hope is to cross your fingers and run it now. Let me know how it all goes.
Sent from my Evita
---------- Post added 28th November 2013 at 12:12 AM ---------- Previous post was 27th November 2013 at 11:49 PM ----------
ndmuni said:
U should download one that has the same radio as yrs also it will take fast download speed otherwise it will keep breaking up. t took me 4 attempts before I manage to download it yesterday (same file as one u r trying) good luck cheers!
Click to expand...
Click to collapse
What are you talking about? He doesn't need to use an RUU with the same radio/baseband that's currently on his device, that's just wrong. Firstly the idea of an RUU is to update your device, therefore traditionally you'd be updating to a newer radio version than the one that's currently installed. With s-on you can only run an RUU that contains a firmware version that's equal to or greater than your current firmware. This user has s-off though so he can run any RUU that he wants to, including earlier ones (RUU'ing backwards). I don't know where you got the idea that you need to run an RUU with the same radio as your existing radio but it's just plain wrong, and you really shouldn't be telling people that.
Sent from my Evita

ndmuni said:
U should download one that has the same radio as yrs
Click to expand...
Click to collapse
False. With s-on, you can only run RUUs for your CID, and with the same or latter hboot and firmware number. So if you were having trouble flashing an RUU, its probably because you were s-on and trying to either flash another carrier's RUU, or an older version.
The OP is s-off, so therefore all security checks are off. He can flash the RUU for any carrier, any version. As long as its meant for our device (EVITA), of course.

Hi guys
Thank you for all the guidance.
I got the 4.1.1 on my phone now and phone is use-able. I can not thank you guys enough for the help.
After i finished RUU flash the phone detected the new firmware update. When i dowloaded and tried to update, it says that the phone has been modified and they can not run/install the update. When i checked my boot it shows :
"relocked"
cid is still 111111.
Evita pvt ship s-off RL
HBOOT: 2.14
radio : 0.23a.32.09.29
Do i need to do more installation before my phone can get the update from HTC like the one coming out from the factory?
Cheers.
Arda
Sent from my HTC One XL using Tapatalk

You need to change your CID back to the stock CID to take the OTA update.
Sent from my Evita

timmaaa said:
You need to change your CID back to the stock CID to take the OTA update.
Sent from my Evita
Click to expand...
Click to collapse
I searching in the forum about changing CID. But it seems that is all about how to change CID to 111111. Is there any tutorial to revert back to original CID?
Do i need to sort out my s-off first before changing CID?
Thank you in advance.
Regards
Arda

You said in a previous post that you're s-off. So are you s-off or s-on? Please boot into bootloader and post your bootloader details again.
Sent from my Evita

Hi Timmaa
I believe I am S-OFF - when I look at the bootloader screen it said S-OFF.
Do I need to flash anything at all to get my CID back to original?
On that note I was looking at the RedPoint73 resource guide page but I am not able to find the tutorial to make the CID back to original.
Any info is greatly appreciated.
Cheers

All you need to do is issue a fastboot command:
Code:
fastboot oem writecid xxxxxxxx
The x's represent the new CID.
Sent from my Evita

Hi Timmaa
I believe I am S-OFF - when I look at the bootloader screen it said S-OFF.
Do I need to flash anything at all to get my CID back to original?
On that note I was looking at the RedPoint73 resource guide page but I am not able to find the tutorial to make the CID back to original.
Any info is greatly appreciated. I have attached the screen shot
Cheers

I did :
fastboot oem writecid 622 but it came back with ....INFOfail: [writecid] invalid CID
I flashed the RUU_EVITA_UL_JB_45_S_hTC_Asia_WWE_3.17.707.1_Radio_0.23a.32.09.29_10.128.32.34a_release_298958_signed.exe
was the 622 number incorrect?
cheers

No, 622 isn't a CID. A correct CID consists of eight characters, that's why I put eight x's in my example. What model is your phone? You need find the right CID for your model and change it to that. You need to be more careful, you're attempting things without knowing what you're doing again, you're in serious danger of damaging your phone.
Sent from my Evita

timmaaa said:
No, 622 isn't a CID. A correct CID consists of eight characters, that's why I put eight x's in my example. What model is your phone? You need find the right CID for your model and change it to that. You need to be more careful, you're attempting things without knowing what you're doing again, you're in serious danger of damaging your phone.
Sent from my Evita
Click to expand...
Click to collapse
Hi Timmaa
My phone is HTC ONE XLTE
I use CID Getter and it came up with HTC__622, so I entered that into the fastboot command and it changed my CID but when I try to flash the new update downloaded directly through the phone it came up with the messsage below after verifying the phone.
not sure why.....( pls see attached)

So you ran the RUU.exe? You didn't extract it or anything? What have you done to the phone since then?
Sent from my Evita