Database Info

[Q] HTC SENSATION got completely stuck on boot (complicated)

correct RUU 3.32.161.11 in post #11
Hi people.
The thing at the moment is stuck at JuopunutBear. But better to start from begining...
I decided to flash a different rom into it. So i unlocked a bootloader, installed "4EXT Recoveryy Touch" and tried to flash it straight away without having any backup... then the device use to get stuck on boot logo (as i rear later because of "s-on") and enabling "smart flash" on 4ext might help... but it didn't worked for me so i decided to install "JuopunutBear" and get "s-off" (on device which does not boot up any more)...
But my plan failed because whatever i did it ends up on "JuopunutBear" screen.
i though this was going to work but it did not:
C:\Users\user\Desktop\ControlBearRelease_pyramid_ICS_WIN>controlbear.exe -r
======== ControlBear 0.8 beta for JuopunutBear S-OFF ==========
Restoring to normal mode
Searching for device.....
Found device... Please wait...
Device should be in normal boot mode....
Press ENTER to exit.....
changed nothing.
this is all info i can see on hboot:
PYRAMID PVT SHIP S-ON RL
HBOOT-1.27.0000
eMMC-boot
Jan 13 2012, 17:33:34
As far i can at first i need to get rid of "JuopunutBear" at first.. and then somehow to make the rom work... have no idea what to do next... is it possible to do fresh reinstall for all regardless what mess is there right now?
that is definitely the last time i play like this but now only thing i want is to get it working...
I would be glad for some advice. thank you!

An RUU will make your phone completely stock. As for the juopuonut s-off, it seems like you are using an old version of control bear.
Look here for ruu: http://forum.xda-developers.com/showthread.php?p=26541170
Sent from my HTC Sensation

AndroidSupporter318 said:
An RUU will make your phone completely stock. As for the juopuonut s-off, it seems like you are using an old version of control bear.
Look here for ruu: http://forum.xda-developers.com/showthread.php?p=26541170
Sent from my HTC Sensation
Click to expand...
Click to collapse
Well you opened my eyes but still...

C:\Users\user\Desktop\ControlBearRelease_pyramid_ICS_WIN>fastboot getvar cid
cid: VODAP001
finished. total time: 0.003s
C:\Users\user\Desktop\ControlBearRelease_pyramid_ICS_WIN>fastboot getvar version
-main
version-main: 3.32.161.52
finished. total time: 0.003s
C:\Users\user\Desktop\ControlBearRelease_pyramid_ICS_WIN>
tried all steps till 4.4.2 With a PC, via fastboot USB and at the end i got an error
C:\Users\user\Desktop>fastboot flash zip PG58IMG.zip
sending 'zip' (437337 KB)... OKAY [ 64.719s]
writing 'zip'... INFOsignature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 139.619s
i found the rom, extracted it from exe file (boot.zip) then i needed to modify "android-info.txt" because there are just rally old rom`s with a proper signature. But i could only view and extract archive (if i archive it back it won't work) but not change files inside of them... i tried a couple of them and got the same problem that i can't modify them with any archiver ("archive is corrupt") so i just carryed on with extracting and archiving even when i read that it won't work... windows default archiver does not work, 7-zip as well, winRAR either... am i using a wrong archiver or there is some other way of getting everything done properly? i am totally lost

gyrtaz said:
C:\Users\user\Desktop\ControlBearRelease_pyramid_ICS_WIN>fastboot getvar cid
cid: VODAP001
finished. total time: 0.003s
C:\Users\user\Desktop\ControlBearRelease_pyramid_ICS_WIN>fastboot getvar version
-main
version-main: 3.32.161.52
finished. total time: 0.003s
C:\Users\user\Desktop\ControlBearRelease_pyramid_ICS_WIN>
tried all steps till 4.4.2 With a PC, via fastboot USB and at the end i got an error
C:\Users\user\Desktop>fastboot flash zip PG58IMG.zip
sending 'zip' (437337 KB)... OKAY [ 64.719s]
writing 'zip'... INFOsignature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 139.619s
i found the rom, extracted it from exe file (boot.zip) then i needed to modify "android-info.txt" because there are just rally old rom`s with a proper signature. But i could only view and extract archive (if i archive it back it won't work) but not change files inside of them... i tried a couple of them and got the same problem that i can't modify them with any archiver ("archive is corrupt") so i just carryed on with extracting and archiving even when i read that it won't work... windows default archiver does not work, 7-zip as well, winRAR either... am i using a wrong archiver or there is some other way of getting everything done properly? i am totally lost
http://forum.xda-developers.com/showthread.php?p=26541170
Click to expand...
Click to collapse
you are SON
so you need the correct RUU based on your CID/MiD/Version-Main ..
downloading any RUU and just modifying the android-info.txt wont do any good (it only works when you are SOFF)

ganeshp said:
you are SON
so you need the correct RUU based on your CID/MiD/Version-Main ..
downloading any RUU and just modifying the android-info.txt wont do any good (it only works when you are SOFF)
Click to expand...
Click to collapse
my current non-working version is 3.32.161.52
and the best i could find is 1.24.161...
i can't downgrade and can't put anything custom because i it is SON... so it is dead end for me.
is it possible to put some fake ROM by force (like copying files somewhere or smth...) even if it would not work but which would be seen as an "1.24.161..." when i would try to install it properly?
Just brain storming sorry if i am not telling anything clever...

It should be this one: http://hotfile.com/dl/176652525/e42....23.3504.07_M2_release_256146_signed.exe.html
If this one is not it, then try looking at the two sites that were listed in the ruu thread I gave you.
Sent from my HTC Sensation
---------- Post added at 10:43 AM ---------- Previous post was at 10:36 AM ----------
Actually, the link above is for Australian vodaphone users.
This one is general, not branded. It is for European users: http://hotfile.com/dl/158597479/f24...1.22.3504.07_M_release_252064_signed.exe.html
Sent from my HTC Sensation
---------- Post added at 10:45 AM ---------- Previous post was at 10:43 AM ----------
Also, the version number 1.2x is the gingerbread RUU's. 3.32 is for ICS RUU's
Sent from my HTC Sensation

AndroidSupporter318 said:
It should be this one: hotfile.com/dl/176652525/e4290a8/RUU_PYRAMID_ICS_Voda-Hutch_AU_3.32.862.13_Radio_11.69A.3504.00U_11.23.3504.07_M2_release_256146_signed.exe.html
If this one is not it, then try looking at the two sites that were listed in the ruu thread I gave you.
Sent from my HTC Sensation
Click to expand...
Click to collapse
i have checked these links you gave before and there was just gingerbread if i try to find exactly by uk wodafone
will try these too... thanks

AndroidSupporter318 said:
It should be this one: http://hotfile.com/dl/176652525/e42....23.3504.07_M2_release_256146_signed.exe.html
If this one is not it, then try looking at the two sites that were listed in the ruu thread I gave you.
Sent from my HTC Sensation
---------- Post added at 10:43 AM ---------- Previous post was at 10:36 AM ----------
Actually, the link above is for Australian vodaphone users.
This one is general, not branded. It is for European users: http://hotfile.com/dl/158597479/f24...1.22.3504.07_M_release_252064_signed.exe.html
Sent from my HTC Sensation
---------- Post added at 10:45 AM ---------- Previous post was at 10:43 AM ----------
Also, the version number 1.2x is the gingerbread RUU's. 3.32 is for ICS RUU's
Sent from my HTC Sensation
Click to expand...
Click to collapse
Didn't worked out...
How do you think if i unlock the bootloader again is it possible to delete the partition containing OS trough recovery and maybe than having a blank device i would be able to install any version of RUU..? Need some sort of other solution in this situation...

Hmm... can you try to format all partitions from recovery and then try ruu again?
Sent from my HTC Sensation

gyrtaz said:
Hi people.
The thing at the moment is stuck at JuopunutBear. But better to start from begining...
I decided to flash a different rom into it. So i unlocked a bootloader, installed "4EXT Recoveryy Touch" and tried to flash it straight away without having any backup... then the device use to get stuck on boot logo (as i rear later because of "s-on") and enabling "smart flash" on 4ext might help... but it didn't worked for me so i decided to install "JuopunutBear" and get "s-off" (on device which does not boot up any more)...
But my plan failed because whatever i did it ends up on "JuopunutBear" screen.
i though this was going to work but it did not:
C:\Users\user\Desktop\ControlBearRelease_pyramid_ICS_WIN>controlbear.exe -r
======== ControlBear 0.8 beta for JuopunutBear S-OFF ==========
Restoring to normal mode
Searching for device.....
Found device... Please wait...
Device should be in normal boot mode....
Press ENTER to exit.....
changed nothing.
this is all info i can see on hboot:
PYRAMID PVT SHIP S-ON RL
HBOOT-1.27.0000
eMMC-boot
Jan 13 2012, 17:33:34
As far i can at first i need to get rid of "JuopunutBear" at first.. and then somehow to make the rom work... have no idea what to do next... is it possible to do fresh reinstall for all regardless what mess is there right now?
that is definitely the last time i play like this but now only thing i want is to get it working...
I would be glad for some advice. thank you!
Click to expand...
Click to collapse
Hi! Are you still looking for the right RUU? If I got it right you need the Vodafone UK one. You can download it from HERE That will work with your phone. I have the same RUU and always used it when I had to. Boot your phone into Bootloader, then select Fastboot. Make sure on the screen it does say Fastboot USB, then run the RUU and let it finish. Ohh! And don't forget to relock your bootloader before running the RUU. "fastboot oem lock"

AndroidSupporter318 said:
Hmm... can you try to format all partitions from recovery and then try ruu again?
Sent from my HTC Sensation
Click to expand...
Click to collapse
i think i am able to wipe something if i unlock it again but i have no idea what and what effects it is going to make if i do and if i am not going to delete too much (like HBOOT itself) and stuff like that...
is that way possible at all in my condition? is there any tutorials about doing so?
I just unlocked it again. i have some options..:
wipe data/factory reset
wipe cache
wipe catce + dalvik
wipe dalvik cache
wipe battery stats
format system
format data
format boot
format all partitions (except sdcard)
format sdcard
is deleting something going to make me able of installing gingerbread ruu? (because in theory just this old rom is good to my device)
is there anything useful in this list?

If you do a full wipe that's not going to effect hboot but all your data and the installed rom itself. That means you will not have a usable rom flashed on your phone so it will automatically boot into bootloader. But try to download the ruu I linked and follow the steps. If it doesn't work then we can figure out something else.
Sent from your back garden! Don't look back!

matekaneve said:
Hi! Are you still looking for the right RUU? If I got it right you need the Vodafone UK one. You can download it from HERE That will work with your phone. I have the same RUU and always used it when I had to. Boot your phone into Bootloader, then select Fastboot. Make sure on the screen it does say Fastboot USB, then run the RUU and let it finish. Ohh! And don't forget to relock your bootloader before running the RUU. "fastboot oem lock"
Click to expand...
Click to collapse
[RED]OH WOW MATE!!! YOU ARE MY HERO SINCE NOW! EVERYTHING WORKED JUST AS IT SHOULD[/RED]
anyway it is still interesting to me what can you delete with these functions of "4eXT" in the list and if my theory about deleting something and installing gingerbread is right? if yes what should i wipe or format?

When you are flashing roms, in 4ext recovery, there is an option to format all partitions. By doing so you can achive a fresh and clean install of the chosen rom. It does not affect your hboot or your firmware. It only ereases the partitions roms are using. To install gingerbread roms or ruu, you must flash the appropriate gingerbread firmware first. To do so, you must achive s-off first. As you already have 3.32 firmware installed you are "only" able to flash all the currently available ice cream sandwich and jelly bean roms. Hope this helps.
Sent from your back garden... Don't look back!

matekaneve said:
When you are flashing roms, in 4ext recovery, there is an option to format all partitions. By doing so you can achive a fresh and clean install of the chosen rom. It does not affect your hboot or your firmware. It only ereases the partitions roms are using. To install gingerbread roms or ruu, you must flash the appropriate gingerbread firmware first. To do so, you must achive s-off first. As you already have 3.32 firmware installed you are "only" able to flash all the currently available ice cream sandwich and jelly bean roms. Hope this helps.
Sent from your back garden... Don't look back!
Click to expand...
Click to collapse
aha... so if i would not have got any version above 3.32.161 my phone would be pretty much doomed..?
just asking for basic knowledge if i would have any similar problems in the future.. should i seek some info for bricked phone recovery then?

gyrtaz said:
aha... so if i would not have got any version above 3.32.161 my phone would be pretty much doomed..?
just asking for basic knowledge if i would have any similar problems in the future.. should i seek some info for bricked phone recovery then?
Click to expand...
Click to collapse
Honestly, do not worry about bricking your device, just enjoy the freedom rooting gave you. If something goes wrong, you can always use that ruu. The latest voda UK version is 3.32.161.(52)? The main thing is the first 3 digits: 3.32-> ics firmware, ...161-> Vodafone UK code. The last numbers don't matter. Always make sure you flash the correct rom according to your firmware version and your device
Btw. You can install roms require 3.32 or 3.33 firmware! Enjoy flashing!
Sent from my HTC Sensation Z710e using xda app-developers app

matekaneve said:
Honestly, do not worry about bricking your device, just enjoy the freedom rooting gave you. If something goes wrong, you can always use that ruu. The latest voda UK version is 3.32.161.(52)? The main thing is the first 3 digits: 3.32-> ics firmware, ...161-> Vodafone UK code. The last numbers don't matter. Always make sure you flash the correct rom according to your firmware version and your device
Btw. You can install roms require 3.32 or 3.33 firmware! Enjoy flashing!
Sent from my HTC Sensation Z710e using xda app-developers app
Click to expand...
Click to collapse
Come on... I am about learning stuff and knowing. Maybe some day helping someone else. You can tell someone who doesn't really care to not worry instead of telling a short proper answer... sorry i am not trying to be offensive but it was one of the "try using google" sort of answers and that was how i feel about it...
THANKS FOR ALL THE HELP YOU ALL :highfive:

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] Installing RUU, which one to choose

Hi,
My battery has been acting up for almost half a year now and my usage time is half of what it was when i got it. I have been installing several different ROMs and kernels so I am at a lost on what's wrong. So I have decided to install a RUU to see if a total reset can fix my phone.
I found this page: http://www.androidfiles.org/ruu/?developer=Ville
Does anybody know which RUU from the link is the newest/best? Will I get updates from HTC when I do this?
Currently running trickdroid 10.3.2, bricked kernel, twrp 2.3.3, S-OFF and superCID - is there anything in particular I should know before doing this?
I have never installed a RUU before, hope somebody can help

anyone? Or perhaps just a part answer

teamet said:
anyone? Or perhaps just a part answer
Click to expand...
Click to collapse
Choose RUU according to your CID.
Must restore original CID to avaoid having problems with OTA updates.
If you receive OTA updates with superCID, a brick is going to welcome you.
Sent from my HTC One S using Tapatalk 4 Beta

khan.orak said:
Choose RUU according to your CID.
Must restore original CID to avaoid having problems with OTA updates.
If you receive OTA updates with superCID, a brick is going to welcome you.
Sent from my HTC One S using Tapatalk 4 Beta
Click to expand...
Click to collapse
Ok so i am in a similar fix.
I obtained S-Off/superCID the very next day i got my One S .. things were running smooth on stock. Looked out for some ROMS and finally installed one. Now I want to revert to my stock ROM while maintaining S-off/root. My problem is only that i don't find this ROM stable or the kernel .. just want to revert to stock.
Live in Pakistan, hence i doubt OTA is going to ever cause me any trouble. Could you please recommend which RRU should i install?
Would really appreciate some help from a fellow countryman

G.Rabbani said:
Ok so i am in a similar fix.
I obtained S-Off/superCID the very next day i got my One S .. things were running smooth on stock. Looked out for some ROMS and finally installed one. Now I want to revert to my stock ROM while maintaining S-off/root. My problem is only that i don't find this ROM stable or the kernel .. just want to revert to stock.
Live in Pakistan, hence i doubt OTA is going to ever cause me any trouble. Could you please recommend which RRU should i install?
Would really appreciate some help from a fellow countryman
Click to expand...
Click to collapse
Yes, you're right. Latest 4.2.2 Custom ROMs are having some bugs at the moment.
I need to know some details before I recommend anything.
1. S3/S4 version processor? (CPU-Z from play store will tell you that)
2. CID & MID (CID getter from play store will tell you that)
3. Last Stock firmware you had/installed?
4. HBOOT version?
Sent from my Nexus 7 using Tapatalk HD

khan.orak said:
Yes, you're right. Latest 4.2.2 Custom ROMs are having some bugs at the moment.
I need to know some details before I recommend anything.
1. S3/S4 version processor? (CPU-Z from play store will tell you that) -----> S4
2. CID & MID (CID getter from play store will tell you that) -----> 11111111
3. Last Stock firmware you had/installed? -----> JB 4.1.1
4. HBOOT version? -----> 2.15.0000
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Thanks for the response I've responded to your queries inline.

G.Rabbani said:
Thanks for the response I've responded to your queries inline.
Click to expand...
Click to collapse
Okay that's good but I need to know the original CID that the phone was shipped with.
Also, I'll need to know MID (Model ID). You can find it out via CID GETTER. When you open the app search for the line [ro.aa.modelid]: PJxxxxxxx that's the model ID
Sent from my Nexus 7 using Tapatalk HD

khan.orak said:
Okay that's good but I need to know the original CID that the phone was shipped with.
Also, I'll need to know MID (Model ID). You can find it out via CID GETTER. When you open the app search for the line [ro.aa.modelid]: PJxxxxxxx that's the model ID
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Thanks a lot for the hint. The CID on the top in CID getter was showing all ones. Ok so following is the information i made out from the verbosity, related to CID and Model ID and all of the rest that made sense to me.
ro.aa.cutomizationid: 452550
ro.aa.maincid: HTC__001
ro.aa.modelid: PJ4010000
ro.baseband: 1.11.50.05.28
ro.bootloader:2.15.0000
ro.aa.project: Ville_U_JB_45_S
ro.aa.rid: 386

G.Rabbani said:
Thanks a lot for the hint. The CID on the top in CID getter was showing all ones. Ok so following is the information i made out from the verbosity, related to CID and Model ID and all of the rest that made sense to me.
ro.aa.cutomizationid: 452550
ro.aa.maincid: HTC__001
ro.aa.modelid: PJ4010000
ro.baseband: 1.11.50.05.28
ro.bootloader:2.15.0000
ro.aa.project: Ville_U_JB_45_S
ro.aa.rid: 386
Click to expand...
Click to collapse
Ok. I deem this RUU to be the most suitable for you, which is Here.
Just run the RUU and it will do the job for you.
A word or two of caution here:
1. The RUU will erase everything.
2. After the RUU, you might want to change your CID back to HTC__001 because it has been rumored that HTC will release JellyBean 4.2.2 + Sense 5 for the One S. If you update the ONE S via OTA with SUPERCID, you will brick your device.
And anyway, SuperCID is not necessary at all for flashing Custom ROMs.
3. You will lose the Root for sure. But you can flash custom recovery + SuperSU again after going stock.
Edit: Oh! and match the MD5 hash of the downloaded file and the one on the server. MD5 checking utility is on XDA somewhere.
Edit 2: The CID in all cases comprises of 8 characters. i.e HTC__001 (8 chars), BM___001 (8 chars, my CID) etc. So when changing the CID, be sure to have an 8 character CID.
regards

khan.orak said:
Ok. I deem this RUU to be the most suitable for you, which is Here.
Just run the RUU and it will do the job for you.
A word or two of caution here:
1. The RUU will erase everything.
2. After the RUU, you might want to change your CID back to HTC__001 because it has been rumored that HTC will release JellyBean 4.2.2 + Sense 5 for the One S. If you update the ONE S via OTA with SUPERCID, you will brick your device.
And anyway, SuperCID is not necessary at all for flashing Custom ROMs.
3. You will lose the Root for sure. But you can flash custom recovery + SuperSU again after going stock.
Edit: Oh! and match the MD5 hash of the downloaded file and the one on the server. MD5 checking utility is on XDA somewhere.
regards
Click to expand...
Click to collapse
Thanks a lot brother!
Will follow your instructions. I was following a guide (All in one tool kit for ONE S) to achieve S-OFF for rooting and following that procedure the CID was reset as well. Not sure whether i can achieve S-OFF without meddling with the CID .... This being my first HTC after SGS and SGS2.

G.Rabbani said:
Thanks a lot brother!
Will follow your instructions. I was following a guide (All in one tool kit for ONE S) to achieve S-OFF for rooting and following that procedure the CID was reset as well. Not sure whether i can achieve S-OFF without meddling with the CID .... This being my first HTC after SGS and SGS2.
Click to expand...
Click to collapse
No problem at all.
Ok. Some interesting info for you again:
- S-OFF/SuperCID is not necessary for Rooting/Custom Recovery/Flashing Custom ROMs. You must have missed something.
- Just need to Unlock bootloader to Root/Flash custom recovery/custom ROM

khan.orak said:
No problem at all.
Ok. Some interesting info for you again:
- S-OFF/SuperCID is not necessary for Rooting/Custom Recovery/Flashing Custom ROMs. You must have missed something.
Click to expand...
Click to collapse
Hain ??
For all I have read, the reason for going after S-Off to begin with is essentially to gain capability to flash customer roms. I feel sorry for being a consistent bother, but could you please guide me towards a thread where I can learn rooting without messing with S-Off ...

G.Rabbani said:
Hain ??
For all I have read, the reason for going after S-Off to begin with is essentially to gain capability to flash customer roms. I feel sorry for being a consistent bother, but could you please guide me towards a thread where I can learn rooting without messing with S-Off ...
Click to expand...
Click to collapse
haha... Yes..
Well the All-in-One-Toolkit by Hasoon2000 is the one you have to follow. But no S-OFFing/SuperCID.
You just need the bootloader unlocked to get Rooted/Custom ROM/Recovery.
Since you have already unlocked the bootloader, I think it's not necessary to use the AIO toolkit again.
What we need is this:
- Run the RUU. (Run it first, and if it gives you errors, you might need to Relock your bootloader which is quite simple).
[For the latter part] - Then if you want to Root you stock ROM, we will have to flash custom Recovery, which again is quite simple and can be flashed from fastboot. I'll guide you on this part later when you are stock again. No biggy.

khan.orak said:
haha... Yes..
Well the All-in-One-Toolkit by Hasoon2000 is the one you have to follow. But no S-OFFing/SuperCID.
You just need the bootloader unlocked to get Rooted/Custom ROM/Recovery.
Since you have already unlocked the bootloader, I think it's not necessary to use the AIO toolkit again.
What we need is this:
- Run the RUU. (Run it first, and if it gives you errors, you might need to Relock your bootloader which is quite simple).
[For the latter part] - Then if you want to Root you stock ROM, we will have to flash custom Recovery, which again is quite simple and can be flashed from fastboot. I'll guide you on this part later when you are stock again. No biggy.
Click to expand...
Click to collapse
YOU ARE THE MAN! :good:
Take care bro. I'll catch up with you tomorrow after going through the RUU part :highfive:

G.Rabbani said:
YOU ARE THE MAN! :good:
Take care bro. I'll catch up with you tomorrow after going through the RUU part :highfive:
Click to expand...
Click to collapse
glad I could help
Sent from my HTC One S using Tapatalk 4 Beta

khan.orak said:
glad I could help
Sent from my HTC One S using Tapatalk 4 Beta
Click to expand...
Click to collapse
AOA Orak,
I installed the RUU and am back to stock now. Using the toolkit installed TWRP S4 recovery but when i try to go into recovery a red triangle with an exclamation mark appears; the phone stays with it for a while and then reboots to normal desktop. Tried it a number of times with the same result. Since i am unable to go into recovery, i cannot flash the supersu.zip and thus no root :/ Should I go for CWM?

G.Rabbani said:
AOA Orak,
I installed the RUU and am back to stock now. Using the toolkit installed TWRP S4 recovery but when i try to go into recovery a red triangle with an exclamation mark appears; the phone stays with it for a while and then reboots to normal desktop. Tried it a number of times with the same result. Since i am unable to go into recovery, i cannot flash the supersu.zip and thus no root :/ Should I go for CWM?
Click to expand...
Click to collapse
W/S
Okay first you boot into bootloader and tell me the details ..
To go into bootloader, turn off device, then hold power + vol down ... A white background with details..
Post them here.
Sent from my HTC One S using Tapatalk 4 Beta

khan.orak said:
W/S
Okay first you boot into bootloader and tell me the details ..
To go into bootloader, turn off device, then hold power + vol down ... A white background with details..
Post them here.
Sent from my HTC One S using Tapatalk 4 Beta
Click to expand...
Click to collapse
Ok so i figured it out in the meanwhile .. I had locked the bootloader before running the RUU. Unlocked it, installed recovery and flashed SU successfully.
So now I have two questions:
1- Do i need to re-lock the bootloader? If yes, will I still be able to flash custom roms?
2- How do i revert my original CID value? Will 'fastboot writecid HTC__001' do the trick? Are there any pre-requisites for it?

G.Rabbani said:
Ok so i figured it out in the meanwhile .. I had locked the bootloader before running the RUU. Unlocked it, installed recovery and flashed SU successfully.
So now I have two questions:
1- Do i need to re-lock the bootloader? If yes, will I still be able to flash custom roms?
2- How do i revert my original CID value? Will 'fastboot writecid HTC__001' do the trick? Are there any pre-requisites for it?
Click to expand...
Click to collapse
- Okay before anything, i would advise to flash TWRP 2.3.3.0 recovery and you will avoid many issues currently being faced with 2.5.0.0.
You can find 2.3.3.0 Here.
If you need help on flashing, ask away.
- now your questions:
1. No and No
2. You have to boot into bootloader and then go into FASTBOOT and write the command
fastboot oem writecid HTC__001
BTW, I assume you have adb+fastboot files on your PC?
Sent from my Nexus 7 using Tapatalk HD

khan.orak said:
fastboot oem writecid HTC__001
Click to expand...
Click to collapse
This only works if you are S-OFF
hTConeS | SoFF | ChaRmAnDrOiD | BuLLetprOOf
Inverted Sense 5 Theme Updates+Tweaks
Inverted Sense 4+

[Q] Set Telstra HTC One XL to s-off

Hi guys, first time poster - I want to install the following custom rom...
http://forum.xda-developers.com/showthread.php?t=2442946
... and being new to android modding, do not want to brick it by doing something wrong.
I gather i need to set up superCID and then set to s-off - would anyone be able to point me in the right direction on how to do these correctly for a Telstra phone?
My phone is rooted with CWM, from whati gather (it says "ClockworkMod recovery" in recovery mode).
Thanks

jacen72 said:
Hi guys, first time poster - I want to install the following custom rom...
http://forum.xda-developers.com/showthread.php?t=2442946
... and being new to android modding, do not want to brick it by doing something wrong.
I gather i need to set up superCID and then set to s-off - would anyone be able to point me in the right direction on how to do these correctly for a Telstra phone?
My phone is rooted with CWM, from whati gather (it says "ClockworkMod recovery" in recovery mode).
Thanks
Click to expand...
Click to collapse
You might already have SuperCID, you can use a fastboot command to check. The command is:
Code:
fastboot oem readcid
If it comes back as anything other than 11111111 you can use this method to get SuperCID.
Once you have SuperCID you can use this method to get s-off.
Sent from my Evita

timmaaa said:
You might already have SuperCID, you can use a fastboot command to check. The command is:
Code:
fastboot oem readcid
If it comes back as anything other than 11111111 you can use this method to get SuperCID.
Once you have SuperCID you can use this method to get s-off.
Sent from my Evita
Click to expand...
Click to collapse
Thanks, i will take a closer look soon. Is it true that for Telstra phones the CID needs to be 22222222, or is 11111111 okay as well?

jacen72 said:
Thanks, i will take a closer look soon. Is it true that for Telstra phones the CID needs to be 22222222, or is 11111111 okay as well?
Click to expand...
Click to collapse
The 22222222 CID only applies to at&t phones trying to unlock their bootloader via htcdev, this is because at&t stock CID (cws__001) plus 11111111 CID have been blocked at htcdev. For your purposes 11111111 will be fine.
Sent from my Evita

timmaaa said:
The 22222222 CID only applies to at&t phones trying to unlock their bootloader via htcdev, this is because at&t stock CID (cws__001) plus 11111111 CID have been blocked at htcdev. For your purposes 11111111 will be fine.
Sent from my Evita
Click to expand...
Click to collapse
Thanks for the info - i know i need to superCID as i checked last night and CID was TELST001 (from memory). Will use 11111111.

No problems, did you use the fastboot command the check your CID? I only ask because there are apps available which claim to display your CID but they show the original CID, not the current one.
Sent from my Evita

timmaaa said:
No problems, did you use the fastboot command the check your CID? I only ask because there are apps available which claim to display your CID but they show the original CID, not the current one.
Sent from my Evita
Click to expand...
Click to collapse
I tried so many things last night i couldn't tell you exactly what i did, haha! Will try your way and see what it says.
A quick question - in regard to the facepalm link, it says "Download patcher and unzip it in your working directory" - can this be any folder on my phone (eg: Downloads)? I'm also guessing the other file (OneX.zip) goes in the same directory?

No you place the extracted patcher files and the PJ8312000-OneX.zip into your fastboot folder on your pc.
You need to have adb/fastboot and HTC drivers installed on your pc to do the s-off process.
Sent from my Evita

jacen72 said:
I tried so many things last night i couldn't tell you exactly what i did, haha
Click to expand...
Click to collapse
You should keep better track of things you are doing or you will end like NASA on Apollo 1 and not knowing what went wrong.
To repair something you need to know what you did to break it.

Big thanks timmaaa, have upgraded successfully!
twistedddx, you're not wrong - i should have kept an eye on what i was doing. Luckily for me, all went well!
Thanks again.

Glad to see you got it all sorted mate.
Sent from my Evita

Hi guys, since updating Android, i seem to find my service connection (no service) is being lost fairly easily - is there something i need to do in regard to this, or is it just me?!
Cheers

Which ROM are you on?
Sent from my Evita

timmaaa said:
Which ROM are you on?
Sent from my Evita
Click to expand...
Click to collapse
the one from the following link:
http://forum.xda-developers.com/showthread.php?t=2442946

You either need to update your firmware to 2.15 or just flash the Beastmode kernel.
Sent from my Evita

timmaaa said:
You either need to update your firmware to 2.15 or just flash the Beastmode kernel.
Sent from my Evita
Click to expand...
Click to collapse
Thanks, when you talk about beastmode, is the following link what you are referring to?
http://forum.xda-developers.com/showthread.php?t=1797251
Also, with firmware 2.15 - i would actually like to keep it as stock as possible, so perhaps the firmware upgrade would be the better option? I have found a link that looks like it goes to the correct download:
http://forum.xda-developers.com/showthread.php?p=45646878 - (see last post)
Would i be right in saying the instructions for updating the kernel would be the same as at the following link:
http://forum.xda-developers.com/showthread.php?t=2423735 - (OPTIONAL: Installing the Firmware)
Thanks again for your help.

The first link is incorrect, you can find the Beastmode kernel in our development section. The kernel you just install in recovery.
The last link you quoted is where you'll find the 2.15 firmware, and the install instructions see in the first post on that thread (it's a manual install using fastboot).
Sent from my Evita

timmaaa said:
The first link is incorrect, you can find the Beastmode kernel in our development section. The kernel you just install in recovery.
The last link you quoted is where you'll find the 2.15 firmware, and the install instructions see in the first post on that thread (it's a manual install using fastboot).
Sent from my Evita
Click to expand...
Click to collapse
Thanks - looks easy enough. Can i ask what why i would install Beastmode instead of the firmware upgrade? From what i gather, it is to overclock the CPU?

You can leave the Beastmode settings stock, it's just an easier and safer fix rather than upgrading firmware. You can OC if you wish to of course. There's always a small risk involved with anything that touches your hboot.
Sent from my Evita

timmaaa said:
You can leave the Beastmode settings stock, it's just an easier and safer fix rather than upgrading firmware. You can OC if you wish to of course. There's always a small risk involved with anything that touches your hboot.
Sent from my Evita
Click to expand...
Click to collapse
Thanks, maybe i will install beastmode instead then if it will help fix my connection issues. Sorry, but would you be able to point in the direction of where it is in the development section, i cannot seem to find it.
I promise if this works you wont have to hear my noob questions anymore!!

[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