Database Info

I need assistance on how to get back to my stock Gingerbread ROM. HTC Sensation XE

I have my HTC Sensation XE which has originally the 2.3.4 Gingerbread.
I would like to have an assistance on how to do it?
Do I need to flash specific firmwares? Where could I get it? and is it safe to use the backup I made before with that Gingerbread Rom?
Thank you.
I used SUPERCID method.. Therefore I'm not exactly sure whats my CID number and RUU but im pretty sure its either HTC__038 or HTC__044 asia or wwe_asia.
If it helps , I had some Starhub apps, Singtel or whatever, so I assume its more of an HTC__044 CID number?
Thank you.

If you did superCID you don't need to worry about which ruu you use. There is a stock GB ruu link in the s-on section of the sticky guide to everything in the dev forum.
Sent from my HTC Pyramid using xda premium

stringer7 said:
If you did superCID you don't need to worry about which ruu you use. There is a stock GB ruu link in the s-on section of the sticky guide to everything in the dev forum.
Sent from my HTC Pyramid using xda premium
Click to expand...
Click to collapse
Thank you for the response. But im trying to get the OTA also.
That's why I want to be sure about my RUU. and CID ^^, Thank you.

ardom said:
Thank you for the response. But im trying to get the OTA also.
That's why I want to be sure about my RUU. and CID ^^, Thank you.
Click to expand...
Click to collapse
OK, you can find your original cid by entering "getprop ro.cid" in terminal emulator.
Sent from my HTC Pyramid using xda premium

stringer7 said:
OK, you can find your original cid by entering "getprop ro.cid" in terminal emulator.
Sent from my HTC Pyramid using xda premium
Click to expand...
Click to collapse
I had changed my CID when i rooted mine i used supercid method and changed it to 11111111 i forgot my original ru. Im nt sure exactly too if its wwe_asia or asia but im sure its either of the two. I had Starhub app too so i have a premonition that it could be htc__044 or asiawwe singapore version.
Im confused lol. I Want to go back to my stock ruu and cid. Or least the cid so i could restore my backup if possible. Then if ever i ota update. Less prblems could be encountered.
Sent from my HTC Sensation XE with Beats Audio

What are the steps I need to do?
Which to flash? any firmware?
THank you.

This is a prime example of making sure you check for the RUU BEFORE you flash anything new
Do what is said above and it will tell you your original CID. We can then see if we can find the RUU

Good luck. I just updated my xe to ics by simply reading a lot of posts on this site. And simply following all instructions.
At first tho, I mistakenly flashed sensation and not sensation xe. But again, found the correct files here on this site. All sorted and now have beats audio back, now with sense and ics latest.
So many helpful people here, so I hope you too get your fine sorted to the way you want yours. Although curious as to why you wanna go back to gb.
Surely ics is better?
Sent from my HTC Sensation XE with Beats Audio Z715e using XDA

hi
hi guys, do you have any link for official Gingerbread RUU 1.73 with beats audio for sensation XE? i just turn my sensation XE to s-on and flash the RUU but i flashed a wrong ruu.thanks guys.i want to update my sensation XE to ics through system update

Are you S-ON again now? If so, you'll need to S-OFF before you can flash the XE RUU (which you can find here):
https://www.yousendit.com/download/M3BtWmd2YWJ6NE5qQTlVag

Its already 1111111 for my CID. Im planning to go back to stock gb so i can get the ota ics and try it out.
Sent from my HTC Sensation XE with Beats Audio

Yes my phone is s-on again, so how do I flash the ruu?and just s-off? No need to do rooting?thanks

Help ~ Loop boot
I was gonna revert to my stock Gingerbread 2.3.4, I was trying to achieve ICS 4.x and Cyanogen mod 9, but I n00bed it up and wound up in a boot loop. I've read several different tutorials and I gathered I need to flash back to Stock GB. Do I just need a link to a Stock GB that fits my CID?
CID = T-MOB010
No Super CID
No RUU
Thanks much

soldierforus said:
I was gonna revert to my stock Gingerbread 2.3.4, I was trying to achieve ICS 4.x and Cyanogen mod 9, but I n00bed it up and wound up in a boot loop. I've read several different tutorials and I gathered I need to flash back to Stock GB. Do I just need a link to a Stock GB that fits my CID?
CID = T-MOB010
No Super CID
No RUU
Thanks much
Click to expand...
Click to collapse
yes yes stock GB would do ..also ..you have stock ICS for that cid too want that ?
GB RUU for TMOB USA
ICS RUU for TMOB USA (post #1 section #3 has the link to RUU's)
but
care to explain more what happened ?..it probably might be a small solution
small details would do ..
complete details present in the bootscreen (a screenshot would do too)
also
a complete output of the following command (except IMEI and serail number)
fastboot getvar all
then i can give you a perfect solution

ganeshp said:
yes yes stock GB would do ..also ..you have stock ICS for that cid too want that ?
GB RUU for TMOB USA
ICS RUU for TMOB USA (post #1 section #3 has the link to RUU's)
but
care to explain more what happened ?..it probably might be a small solution
small details would do ..
complete details present in the bootscreen (a screenshot would do too)
also
a complete output of the following command (except IMEI and serail number)
fastboot getvar all
then i can give you a perfect solution
Click to expand...
Click to collapse
Sorry to double post, I thought this may be a dead thread since the previous post had a question and no reply in 4 months.
_____________________________________________
The Details:
Boot loop began after I flashed to firmware 3.32 using:
Universal Firmware 3.32 Universal (Non-TMOUS): Since I am on TMO, I gather I should have used the TMOUS flash?
DOWNLOAD: http://d-h.st/afS
MD5: 8f50e9f4f3fab7edcd4013015703f81c
From this tutorial: http://forum.xda-developers.com/showthread.php?p=21711154#post21711154
I later I found a cynaogen tutorial to help with boot loop and followed these steps:
1) Set to factory reset
2)Cleared Delvick (sp?) Cache
____________________________________________
Current Boot Screen:
Revolutionary
Pyramid PVT SHIP S-OFF RL
HBOOT 1.27.1100
RADIO-11.22.3504.07_M
OpenADSP-v02. 6. 0. 226.00.0131
eMMC-boot
_____________________________________________
Getvar all Results:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.27.1100
(bootloader) version-baseband: 11.22.3504.07_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.32.401.3
(bootloader) product: pyramid
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PG5810000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 3816mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 617f0a98
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.490s
So how do the RUU's function exactly? I read the glossary term in wiki, but I don't fully understand the concept. They will update my ROM through window? I guess I need to be able to kill this boot loop first though.
Thanks again

soldierforus said:
Sorry to double post, I though this may be a dead thread since the previous post had a question and no reply in 4 months.
_____________________________________________
The Details:
Boot loop began after I flashed to firmware 3.32 using:
Universal Firmware 3.32 Universal (Non-TMOUS): Since I am on TMO, I gather I should have used the TMOUS flash?
DOWNLOAD: http://d-h.st/afS
MD5: 8f50e9f4f3fab7edcd4013015703f81c
From this tutorial: http://forum.xda-developers.com/showthread.php?p=21711154#post21711154
I later found a cynaogen turoial to help with bootloop and followed these steps:
1) Set to factory reset
2)Cleared Delvick (sp?) Cache
____________________________________________
Current Boot Screen:
Revolutionary
Pyramid PVT SHIP S-OFF RL
HBOOT 1.27.1100
RADIO-11.22.3504.07_M
OpenADSP-v02. 6. 0. 226.00.0131
eMMC-boot
_____________________________________________
Getvar all Results:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.27.1100
(bootloader) version-baseband: 11.22.3504.07_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.32.401.3
(bootloader) product: pyramid
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PG5810000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 3816mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 617f0a98
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.490s
So How the RUU's function exactly. They will update my ROM through window? I guess I need to be able to kill this boot loop first though.
Thanks again
Click to expand...
Click to collapse
for RUU ..you need to connect the phone in bootloader to pc ..and then just double click on it ...that will do
one last try for flashing custom rom ..still not worked then go for RUU
btw what recovery you are using ?
if using cwm ...can you switch to 4EXT recovery ?
get the recovery image from the below db link (recovery.img inside the zip)
4EXT DB link
and flash it via fastboot
fastboot flash recovery recovery.img
got to the recovery
4EXT->wipe|format->format all partitions except sdcard
then back to main menu ...and flash the rom (what ever custom rom you want)
then reboot and see..if it still stuck at boot logo
then extract the boot.img from the rom zip file
and flash it manually
fastboot flash boot boot.img
then reboot
still stuck ?
then reflash the firmware (be sure to check the md5 of the firmware you have downloaded)
still stuck?
then RUU

No-Go
ganeshp said:
for RUU ..you need to connect the phone in bootloader to pc ..and then just double click on it ...that will do
one last try for flashing custom rom ..still not worked then go for RUU
btw what recovery you are using ?
if using cwm ...can you switch to 4EXT recovery ?
get the recovery image from the below db link (recovery.img inside the zip)
4EXT DB link
and flash it via fastboot
fastboot flash recovery recovery.img
got to the recovery
4EXT->wipe|format->format all partitions except sdcard
then back to main menu ...and flash the rom (what ever custom rom you want)
then reboot and see..if it still stuck at boot logo
then extract the boot.img from the rom zip file
and flash it manually
fastboot flash boot boot.img
then reboot
still stuck ?
then reflash the firmware (be sure to check the md5 of the firmware you have downloaded)
still stuck?
then RUU
Click to expand...
Click to collapse
So it wouldn't let me flash 4ext, it says: "cannot load 'recovery.img'" I didn't unzip it or even leave the zip in the root, I took only the recovery.img and left it in to sd root.
You said to flash the custom ROM, but this is my first attempt, and although I have downloaded CM9, the instructions I have read from other tutorials tell me I have to upgrade first to firmware 3.32, then to firmware 3.33, then I can install CM9, which will give me ICS/4.x Am I correct so far?
I don't even know if the 3.32 flash was a success (Do you?) since now I am in a boot loop. Could it be because I should have used the TMOUS instead of the non-TMOUS universal for 3.32? I picked the non-TMOUS because I didn't realize what TOUS stood for at the time, and the other link said universal (and the android-info had my cid/mid)
Also thanks for the RUU links, but I don't know what good the ICS will do if I don't have it yet. Those RUU's will do what exactly? Update to the latest ROM ? Also, is that for all roms or just 3rd party? Looking at the getvar log I sent you, I gather the 3.32 did work, So I should download the ICS 3.32 RUU link you sent me. That's what I am going to try now
EDIT
________________________________
I re-installed cm9, AND EUREKA!!!!!! My first custom ROM. Many thanks to all who helped! Now which RUU do I use, and how often should I run it?

soldierforus said:
So it wouldn't let me flash 4ext, it says: "cannot load 'recovery.img'" I didn't unzip it or even leave the zip in the root, I took only the recovery.img and left it in to sd root.
You said to flash the custom ROM, but this is my first attempt, and although I have downloaded CM9, the instructions I have read from other tutorials tell me I have to upgrade first to firmware 3.32, then to firmware 3.33, then I can install CM9, which will give me ICS/4.x Am I correct so far?
I don't even know if the 3.32 flash was a success (Do you?) since now I am in a boot loop. Could it be because I should have used the TMOUS instead of the non-TMOUS universal for 3.32? I picked the non-TMOUS because I didn't realize what TOUS stood for at the time, and the other link said universal (and the android-info had my cid/mid)
Also thanks for the RUU links, but I don't know what good the ICS will do if I don't have it yet. Those RUU's will do what exactly? Update to the latest ROM ? Also, is that for all roms or just 3rd party? Looking at the getvar log I sent you, I gather the 3.32 did work, So I should download the ICS 3.32 RUU link you sent me. That's what I am going to try now
EDIT
________________________________
I re-installed cm9, AND EUREKA!!!!!! My first custom ROM. Many thanks to all who helped! Now which RUU do I use, and how often should I run it?
Click to expand...
Click to collapse
RUU is rom update utility.. It's official htc file
Ruu is complete software for your phone
It wipes everything.. Rom, recovery firmware.. Everything and flashes the corresponding stock One...
So when you run ics ruu.. You will have complete ics stock rom of tmobile US
And the recovery flash you did earlier was wrong..
You need to keep that recovery file in the adb folder (it should be in pc) Then the command will fetch the file.. As you have kept it on top of sdcard.. It can't find it..
Sent from my pyramid.. Through blazing fast sonic waves

[Q] Please help. Stuck in Bootloop!

Hi there.
Bootloader details are
***Unlocked***
PYRAMID PVT SHIP S-ON RL
HBOOT- 1.27.0000
eMMC- boot
Jan 13 2012, 17:33:34
I'm trying run a RUU which I downloaded and have had an
'ERROR [155]: UNKNOWN ERROR
The ROM Update Utility cannot update your android phone.
Please get the correct ROM Update Utility and try again.
The error may be because my bootloader is unlocked? But when I try to re-lock it it shows the "security warning" below "re-locked"
and then the RUU gives me ERROR [140]: BOOTLOADER VERSION ERROR
The RUU I'm trying to use is called RUU_Pyramid_hTC_Asia_WWE_1.35.707.1_Radio_10.43a.9 007.00U_10.51.9007.27_M3_release_198358_signed
Please help! I've been trying to Install MIUI all day and it is turning into a nightmare.. I don't want to lose this phone D:

You are 1.27 boot your kinda stuck you have to soff and that's not easy with 1.27 some ruu need super cid and soff
Sent from my Sensation using xda premium

craven667 said:
You are 1.27 boot your kinda stuck you have to soff and that's not easy with 1.27 some ruu need super cid and soff
Sent from my Sensation using xda premium
Click to expand...
Click to collapse
Thanks for the reply.
I figured this would be hard as I've tried alot already..
I read somewhere there was a way to get soff involving connecting a wire somewhere and it can be risky. Can you affirm this is the best bet to recover my device?
By the way when relocked bootloader gives me these details..
Radio-11.23.3504.07_M2
OpenADSP-v02.6.0.2226.00.0131
Using ADB CMD I discovered the Android Image is version: 3.32.707.1
I hope someone can give my a clue as to what my best bet is here.. at this point I just want a usable phone again.

There's a new unlock out there but I never used it unlocked 3 at hboot 1.18 sorry
Sent from my Sensation using xda premium

Shunun said:
Hi there.
Bootloader details are
***Unlocked***
PYRAMID PVT SHIP S-ON RL
HBOOT- 1.27.0000
eMMC- boot
Jan 13 2012, 17:33:34
I'm trying run a RUU which I downloaded and have had an
'ERROR [155]: UNKNOWN ERROR
The ROM Update Utility cannot update your android phone.
Please get the correct ROM Update Utility and try again.
The error may be because my bootloader is unlocked? But when I try to re-lock it it shows the "security warning" below "re-locked"
and then the RUU gives me ERROR [140]: BOOTLOADER VERSION ERROR
The RUU I'm trying to use is called RUU_Pyramid_hTC_Asia_WWE_1.35.707.1_Radio_10.43a.9 007.00U_10.51.9007.27_M3_release_198358_signed
Please help! I've been trying to Install MIUI all day and it is turning into a nightmare.. I don't want to lose this phone D:
Click to expand...
Click to collapse
the RUU you are using wont run...because you are s-on...right now based on your HBOOT ...you might have 3.32 firmware....and the RUU you are using has 1.35 firmware (see after WWE_<this is firmware> in the RUU name)...
that's why you are getting that bootloader error..
the best solution for your case is to use ICS RUU..
to get that i need your cid
steps to get cid
1.keep the phone in fastboot and connect it to pc (phone reads "fastboot usb")
2.go to your adb/fastboot folder and type
"fastboot getvar all" without quotes
and post all the results...except serial number and imei
I'll find you the correct RUU for you..which might/will avoid bootloop..after you gave me those details

Okay, I ran the command. Here is what I have.
C:\AndroidSDK\tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.27.0000
(bootloader) version-baseband: 11.23.3504.07_M2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.32.707.10
(bootloader) serialno: ************
(bootloader) imei: **************
(bootloader) product: pyramid
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PG5813000
(bootloader) cidnum: HTC__044
(bootloader) battery-status: good
(bootloader) battery-voltage: 3893mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 617f0a98
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.516s
C:\AndroidSDK\tools>
You might want to know that since trying that RUU I have also tried one called
RUU_PYRAMID_LE_ICS_35_S_hTC_Asia_TW_3.32.709.108_R1_Radio_11.69A.3504.00U_11.23.3504.07_M2_release_251682_signed
It gave me ERROR [156]:IMAGE ERROR
Thanks for your help

please edit your post by removing,,,the serial number and imei present in the list
also the other RUU...wont run because the cid's are not matching...and there is No ICS RUU ...yet in your case...
so the choice left is ...to run a custom rom ?
fine with you ?
this the guide ...you need to follow to get ARHD custom rom
guide to flash roms with S-oN
please follow this guide step by step...and you'll have a custom ROM by end of it
.That guide is wriiten by a friend of mine ...and i helped him to make it pretty noob-free...follow that guide and let me know ..if you got any problem

So u know there's a kinda beta s-off but I would wait if it was me your call
Sent from my Sensation using xda premium

ganeshp said:
please edit your post by removing,,,the serial number and imei present in the list
also the other RUU...wont run because the cid's are not matching...and there is No ICS RUU ...yet in your case...
so the choice left is ...to run a custom rom ?
fine with you ?
this the guide ...you need to follow to get ARHD custom rom
guide to flash roms with S-oN
please follow this guide step by step...and you'll have a custom ROM by end of it
.That guide is wriiten by a friend of mine ...and i helped him to make it pretty noob-free...follow that guide and let me know ..if you got any problem
Click to expand...
Click to collapse
THANKS!!!
Through following your friends/your guide I was able to flash rom
rmk-pyramid-stock_ics_3.32.401.3-v1
I really don't understand why I couldn't do this before when I was using clockworkmod recovery... Although it may have been because I didn't flash the appropriate Boot.img..?
So from what I've read, being S-on on FW3.32 I cannot flash roms that aren't 3.32 as well, would that be correct?
I don't understand how I'm supposed to know which are 3.32 or not..
I really want MIUI still.
Perhaps you could provide link to the MIUI rom which is 3.32..? would it be the latest?
kind regards and thanks for you help and time

[Q] FAILED (remote: not allowed) need a little help

Hello!
Just got my hands on a desire S from someone who said they bricked it, i dont think it is though.
I can access fastboot/HBOOT but it doesnt seem to have a custom recovery installed, shows the stock recovery or download mode logo, the screen goes blank and vibrates 7 times.
Every time i try to flash anything through fastboot it gives me the error in the heading
FAILED (remote: not allowed)
The ROM just doesnt boot and shows T mobile logo indefinitely (must be a bootloop) but the phone doesnt have any Tmo logos on the body.
more details
SAGA PVT SHIP S-OFF RL
HBOOT-0.98.0002
RADIO-3805.06.02.03_M
eMMC-boot
I read about ENG S-off but i dont know what this phone has, maybe its just radio S-OFF cos its Tmo and doesnt have a recovery though i dont understand what the 7 vibrates mean either.
little help please?
even more details
(bootloader) version: 0.5
(bootloader) version-bootloader: 0.98.0002
(bootloader) version-baseband: 3805.06.02.03_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.47.110.3
(bootloader) serialno: HT15TTJ01262
(bootloader) imei: 356708041646975
(bootloader) product: saga
(bootloader) platform: HBOOT-7230
(bootloader) modelid: PG8810000
(bootloader) cidnum: T-MOB005
(bootloader) battery-status: good
(bootloader) battery-voltage: 3653mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 0e35ea5b
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0

7 vibrations most likely mean overheating, and this can't be cured by any means.
The phone is S-OFF, but doesn't have Engineering HBOOT - so you can't use fastboot, it won't allow you (just what it says).
Your best bet is to try a stock RUU and see if it helps.

Download a PG88IMG.zip from an eng hboot, copy it to root of sd (cardreader), boot to bootloader and let it do his job.
Afterwards delete the zip boot to bootloader once more and flash a recovery with fastboot.
I would use a ruu only if those steps fail.
Swyped because PC is under full load or to far away

Tectas said:
Download a PG88IMG.zip from an eng hboot, copy it to root of sd (cardreader), boot to bootloader and let it do his job.
Afterwards delete the zip boot to bootloader once more and flash a recovery with fastboot.
I would use a ruu only if those steps fail.
Swyped because PC is under full load or to far away
Click to expand...
Click to collapse
Hey Tectas I tried your method,
went here
http://forum.xda-developers.com/showthread.php?t=1178001
and got the first radio which had the same number as mine ie this one
From the 1.31.832.3 RUU:
20.28d.30.0805U_3805.04.02.01
says cid incorrect.
shall i try all the ones with 3805 in them? cos i really have no clue which one is right for me considering i dunno which RUU is compatible with this phone

raheeljessa said:
Hey Tectas I tried your method,
went here
http://forum.xda-developers.com/showthread.php?t=1178001
and got the first radio which had the same number as mine ie this one
From the 1.31.832.3 RUU:
20.28d.30.0805U_3805.04.02.01
says cid incorrect.
shall i try all the ones with 3805 in them? cos i really have no clue which one is right for me considering i dunno which RUU is compatible with this phone
Click to expand...
Click to collapse
No, not radio, leave it untouched yet, the hboot is what you need
Check my signature, I personally would recommend this one
Swyped because PC is under full load or to far away

even for this PG88IMG.zip which is the 1mb hboot file it says cid incorrect update fail press power to reboot

Tectas said:
No, not radio, leave it untouched yet, the hboot is what you need
Check my signature, I personally would recommend this one
Swyped because PC is under full load or to far away
Click to expand...
Click to collapse
even for this PG88IMG.zip which is the 1mb hboot file it says cid incorrect update fail press power to reboot

Ok then try it with a ruu, sry that i took your time for nothing

Tectas said:
Ok then try it with a ruu, sry that i took your time for nothing
Click to expand...
Click to collapse
how do i do that? sorry i seem to know nothing

Do you know from which regions your phone is?
Try in fastboot : fastboot getvar all, and Google your main version then download the appropriate file from this link
http://forum.xda-developers.com/showthread.php?t=1002506

Once you are sure you have the right RUU, you might have to make a goldcard to get rid of the CID error

The whole point of having "right" RUU is to avoid this error - having RUU for his specific region gets rid of CID error message. Otherwise he just needs any RUU and goldcard.

Jack_R1 said:
The whole point of having "right" RUU is to avoid this error - having RUU for his specific region gets rid of CID error message. Otherwise he just needs any RUU and goldcard.
Click to expand...
Click to collapse
I have what seems to be the right RUU..
now when i try to install it, the RUU installer hangs and the phone also hangs.
I should reiterate that my phone DOES NOT BOOT into the rom, has what may be boot loop error. If i could access android i wouldnt be asking any of these questions as from in there all this is easy peasy!
i'm trying booting into Hboot and fastboot to install this. as far as i remember it doesnt work here so how else can i go about it?
once again, no custom recovery, no eng bootloader, no working android rom
Thanks to all of you who tried to help by the way

raheeljessa said:
I have what seems to be the right RUU..
now when i try to install it, the RUU installer hangs and the phone also hangs.
I should reiterate that my phone DOES NOT BOOT into the rom, has what may be boot loop error. If i could access android i wouldnt be asking any of these questions as from in there all this is easy peasy!
i'm trying booting into Hboot and fastboot to install this. as far as i remember it doesnt work here so how else can i go about it?
once again, no custom recovery, no eng bootloader, no working android rom
Thanks to all of you who tried to help by the way
Click to expand...
Click to collapse
3 possibilities:
1. Let the ruu run without attached device till the only option is to close the program, search in your temp folder for the rom.zip, copy it to another folder, close the program, copy it to sd and try to flash it the same way you did before with the hboot (rename the rom.zip to PG88IMG.zip before you flash it)
2. Do the same like at 1. but create a goldcard before
3. Do the same I described before with hboot, but create a goldcard before
Swyped because PC is under full load or to far away

If the RUU installer hangs - your chances aren't too good.
If it hangs on "rebooting to bootloader" - boot to FASTBOOT manually and start RUU while in fastboot mode.
If it hangs updating - chances are you're another case of faulty eMMC.

gave the phone to some guy in the market. says he'll take 5£ to open it and check it out and let me know whats wrong.
the RUU rom.zip file when renamed to pg88img.zip or whatever does work as its the only zip file it detects in hboot mode,
it starts the update, heats up like an angry mountain and then sucks its battery off..
thanks you guys for all the help. I'll update you on what was the actual problem when this guy tells me so you know what these symptoms are for in future

Have you tried using the gold card? As it has already been stated that it should get rid of the wrong cid issue.
Sent from my HTC Desire S using XDA

Can't flash JB roms on HTC One S C2

First of, a bunch of thanks to you for helping me get from a complete and utter noob to a just complete noob. Managed to root, install roms and get out of a LOT of soft bricks (i just don't give up!) with your awesome help, all by searching older posts. However, this time i find myself in a pickle.
I own an HTC One S C2 with Hboot 2.0.9, had stock ICS when i bought it with no option to update to JB (which is why i rooted it in the first place). Something about this particular version of the phone not being updated by HTC global, which i found out about after i bought it, duh. Anyway. I've tried installing JB roms from this thread http://forum.xda-developers.com/showthread.php?t=2239265 with no luck. Phone just keeps getting into HTC logo screen loops. Right now i am on backtobasics v3 rom. Here's how i tried installing them JB roms and also the rom i am using right now (using TWRP 2.4.1 because newest version wouldn't work with backtobasics rom):
(note: some roms had sliiiightly different directions, i just followed each and every one's description closely)
1) Download Rom.zip
2) Extract boot.img from Rom.zip to fastboot folder
3) Enter Recovery
4) Mount SD card
5) Copy Rom.zip to SD card
6) Unmount
7) Wipe data, system, cache, dalvik cache and factory reset
8) Install Rom.zip
9) Reboot Bootloader
10) Go to fastboot USB mode
11) dem commands: fastboot flash boot boot.img then fastboot erase cache then fastboot reboot
12) BOOM! HTC LOGO LOOPS!
I've also tried installing a RUU but i couldn't find any for my CID. Then i thought about getting a SuperCID but, frankly, i scrached that thought the minute i saw the how to do it thread. Here's the phone info
version-bootloader: 2.09.0001
version-baseband: 16.05.20.24_M
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
serialno: FA335W400602
imei: 352911052281278
product: villec2
platform: HBOOT-8260
modelid: PJ4021000
cidnum: BSTAR301
battery-status: good
battery-voltage: 4170mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: f616909f
hbootpreupdate: 11
gencheckpt: 0
Thank you, in advance, for any advice you may be able to provide me with

Mkay, since i got no answer i went back to searching again! Unfortunately, i still have no asolution to my problem
From what i understand i have to: find a RUU to get from android version 4.0.3 up to JB version. Then i will be able to flash JB roms. But there is no RUU for CID BSTAR301.
I did find a thread with nandroid backup for a BSTAR301 which updates the version without a RUU but it was for HTC One X, i guess i shouldn't use that at all.
I am thinking about doing a SuperCID to install a RUU, then get back to my actual CID and flash a custom JB rom..
Would appreciate any advice

Tateh said:
Mkay, since i got no answer i went back to searching again! Unfortunately, i still have no asolution to my problem
From what i understand i have to: find a RUU to get from android version 4.0.3 up to JB version. Then i will be able to flash JB roms. But there is no RUU for CID BSTAR301.
I did find a thread with nandroid backup for a BSTAR301 which updates the version without a RUU but it was for HTC One X, i guess i shouldn't use that at all.
I am thinking about doing a SuperCID to install a RUU, then get back to my actual CID and flash a custom JB rom..
Would appreciate any advice
Click to expand...
Click to collapse
Yes, in your case S-OFF, Changing CID to something which has a JB RUU would do the trick. I think SuperCID is not necessary.
Sent from my Nexus 7 using Tapatalk HD

heakit Purpose
khan.orak said:
Yes, in your case S-OFF, Changing CID to something which has a JB RUU would do the trick. I think SuperCID is not necessary.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
THANK you! Currently trying to S-OFF it!

Tateh said:
THANK you! Currently trying to S-OFF it!
Click to expand...
Click to collapse
did you get S-OFF?

Not yet.. So exhausted. I tried the moonshine method but, just like trhe instructions state, i should have JB and be on stock for it to work properly, which is not possible since my phone has a BSTAR301 CID and is stuck on 4.0.3 with no stock roms available.
From what i've read, my only hope of S-OFF is to wait for the fellas working on Revolutionary method for S-OFF to release the correct version for this phone. I just hope it's soon and I thank them for their efforts, i'm so disappointed at this phone

Tateh said:
Not yet.. So exhausted. I tried the moonshine method but, just like trhe instructions state, i should have JB and be on stock for it to work properly, which is not possible since my phone has a BSTAR301 CID and is stuck on 4.0.3 with no stock roms available.
From what i've read, my only hope of S-OFF is to wait for the fellas working on Revolutionary method for S-OFF to release the correct version for this phone. I just hope it's soon and I thank them for their efforts, i'm so disappointed at this phone
Click to expand...
Click to collapse
same here. I just wrote to them asking for that

S-OFF done
I did S-OFF already. Now i need to know what CID put in my phone?? and which RUU install on it??
My MID is: PJ4021000
so i don't know if the Europe RUU's work in my phone. Maybe the radio have problem or no?? because the RUU say MID version: PJ4020000. Someone knows about this??

I have heard that JB update for BSTAR is now available.
Sent from my HTC One S using Tapatalk 4 Beta

khan.orak said:
I have heard that JB update for BSTAR is now available.
Sent from my HTC One S using Tapatalk 4 Beta
Click to expand...
Click to collapse
Yeah it's done. But I would change CID not have to wait for another update Brightstar in so long.

gustavoegg said:
Yeah it's done. But I would change CID not have to wait for another update Brightstar in so long.
Click to expand...
Click to collapse
Be sure to match MID or you'll end up having problems with future updates.
Sent from my HTC One S using Tapatalk 4 Beta

Episcopal yupdfir
khan.orak said:
Be sure to match MID or you'll end up having problems with future updates.
Sent from my HTC One S using Tapatalk 4 Beta
Click to expand...
Click to collapse
Where i can find a RUU for Model ID: PJ4021000?? Because i need update for OTA after install the RUU

gustavoegg said:
Where i can find a RUU for Model ID: PJ4021000?? Because i need update for OTA after install the RUU
Click to expand...
Click to collapse
You have to manually check the ANDROID-INFO.TXT to match CID + MID
Sent from my HTC One S using Tapatalk 4 Beta

Tateh said:
First of, a bunch of thanks to you for helping me get from a complete and utter noob to a just complete noob. Managed to root, install roms and get out of a LOT of soft bricks (i just don't give up!) with your awesome help, all by searching older posts. However, this time i find myself in a pickle.
I own an HTC One S C2 with Hboot 2.0.9, had stock ICS when i bought it with no option to update to JB (which is why i rooted it in the first place). Something about this particular version of the phone not being updated by HTC global, which i found out about after i bought it, duh. Anyway. I've tried installing JB roms from this thread http://forum.xda-developers.com/showthread.php?t=2239265 with no luck. Phone just keeps getting into HTC logo screen loops. Right now i am on backtobasics v3 rom. Here's how i tried installing them JB roms and also the rom i am using right now (using TWRP 2.4.1 because newest version wouldn't work with backtobasics rom):
(note: some roms had sliiiightly different directions, i just followed each and every one's description closely)
1) Download Rom.zip
2) Extract boot.img from Rom.zip to fastboot folder
3) Enter Recovery
4) Mount SD card
5) Copy Rom.zip to SD card
6) Unmount
7) Wipe data, system, cache, dalvik cache and factory reset
8) Install Rom.zip
9) Reboot Bootloader
10) Go to fastboot USB mode
11) dem commands: fastboot flash boot boot.img then fastboot erase cache then fastboot reboot
12) BOOM! HTC LOGO LOOPS!
I've also tried installing a RUU but i couldn't find any for my CID. Then i thought about getting a SuperCID but, frankly, i scrached that thought the minute i saw the how to do it thread. Here's the phone info
version-bootloader: 2.09.0001
version-baseband: 16.05.20.24_M
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
serialno: FA335W400602
imei: 352911052281278
product: villec2
platform: HBOOT-8260
modelid: PJ4021000
cidnum: BSTAR301
battery-status: good
battery-voltage: 4170mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: f616909f
hbootpreupdate: 11
gencheckpt: 0
Thank you, in advance, for any advice you may be able to provide me with
Click to expand...
Click to collapse
Hi, I have same problem with you. Have you got any solution?

Unfortunately not yet, I switched back to my old xperia ray while i wait for the revolutionary team to release a version for HTC One S

[Q] HTC One X (Evita) 3.18 RUU for S-ON

I have had this great phone for around 3-4 months now. In the second week of owning it, I already unlocked the bootloader and rooted my phone. It is not S-OFF, because I'm under the impression that you need to buy extra hardware.
What I want to know is if there is any way that I can flash 3.18 RUU on my AT&T branded (but I use T-Mobile) evita? If there is, can you provide me with a link?
Again, I'm already rooted and I'm bootloader unlocked. Thanks

You don't need to buy any hardware or modify your phone physically to gain s-off, all you need to do is follow the instructions on this thread.
If you have SuperCID (which you most likely do) and try to RUU while you're s-on you'll brick your phone. So my advice is to go to the s-off thread I linked to before, and follow the instructions.
Once you've done that you can run the 3.18 RUU.
Sent from my Evita

Thanks, mate. I appreciate the fast answer. Naturally, I hate being left behind; and seeing that most of the new ROMs require S-Off for the 3.4 kernel, I decided it was time to upgrade. I'll give it a try, as I'm currently trying to flash a ROM because I mistakenly flashed one of ^. Now, it's stuck on the the HTC splash screen, and I guess it's just the first boot scenario. However, it has taken a curious amount of time.

Yeah it's pretty much gonna be essential from now on anyway so you might as well get it outta the way.
What ROM did you try to flash? Also, what firmware/hboot are you currently on?
Sent from my Evita

I tried flashing CarbonROM. It gave me that (Status 7) error so I figured it was the 3.4 kernel giving me problems. After that, I tried flashing a previous version of CarbonROM, and it'd just stay stuck in the splashscreen (This is the ROM that I was discussing in my previous post). Now I tried to flash RageXL, and it's bootlooping. So I'm figuring that I should just go to a stock ROM and get this procedure done, and THEN flash a custom ROM. #BadLuckw3r3w0lv33

Ok. Yep it's the fact that you haven't yet upgraded via the RUU that these ROMs won't boot. Try flashing something like MagioRom or ViperXL just to get the s-off procedure done.
Sent from my Evita

Hmph. I'm pretty sure I've downloaded the latest Google and HTC USB drivers. Still, when I enter "adb reboot bootloader", this pops up:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device offline
I have enabled USB debugging on my HOXL. Perhaps, it's the HTC Sync Manager? I have no clue beyond that point. I even tried restarting my phone AND computer.
EDIT: Nevermind, I just manually rebooted to the bootloader and continued from there. I am now S-Off

:thumbup:
Sent from my Evita

Btw.... If I helped you, please press the thanks button.
Sent from my Evita

Help me please
timmaaa said:
You don't need to buy any hardware or modify your phone physically to gain s-off, all you need to do is follow the instructions on this thread.
If you have SuperCID (which you most likely do) and try to RUU while you're s-on you'll brick your phone. So my advice is to go to the s-off thread I linked to before, and follow the instructions.
Once you've done that you can run the 3.18 RUU.
Sent from my Evita
Click to expand...
Click to collapse
Can i install 2.20 firmware after installing 3.8 firmware.. I have s-off and unlocked bootloader and had my AT&T htc one x evita rooted before i installed 3.18 firmware... please help i cant root my phone on 3.18....

hirias said:
Can i install 2.20 firmware after installing 3.8 firmware.. I have s-off and unlocked bootloader and had my AT&T htc one x evita rooted before i installed 3.18 firmware... please help i cant root my phone on 3.18....
Click to expand...
Click to collapse
If you are already s-off, just install custom recovery, then flash a rooted ROM or SU to get root.
Sent from my HTC One XL using xda app-developers app

Will this RUU work if I have a locked bootloader and s-on?

Chudawg62 said:
Will this RUU work if I have a locked bootloader and s-on?
Click to expand...
Click to collapse
As I said earlier in the thread, SuperCID + s-on + jb RUU = brick.
Sent from my Evita

guys can you please help me here?
my phone is
*** LOCKED ***
EVITA PVT SHIP S_OFF RL
CID-11111111
HBOOT-1.14.0002
RADIO-0.19as.32.09.11_2
OpenDSP-v29.1.0.45.0622
eMMC-boot
Junn 11 2012,14:36:28
i dont understand thiss phone that well so can you please tell me if its safe to install the stock jellybean RUU on my phone?

Yes you're s-off so you can run the RUU with minimal risk.
Sent from my Evita

3.17 or 3.18?
Hi,
First off, thanks everyone - this forum has provided me a wealth of information.
I'm wondering if I can run non-sense based roms (ex. Cyanogenmod 10.2 or 11) without downgrading the touchpanel firmware. Here are my phone specs:
C:\Android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.15.0000
(bootloader) version-baseband: 1.31a.32.45.16_2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.08.111.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT27XXXXXXXX
(bootloader) imei: 359691XXXXXXXXX
(bootloader) product: evita
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ8310000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4050mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: dirty-de589c6eef
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
Currently running ViperXL Android 4.2.2, stock kernel. Had to upgrade to HBOOT 2.15 to get rid of the random reboots and signal drop.
Before I upgraded HBOOT from 2.14 to 2.15 I was pretty sure I was on 3.17. I'm not even sure how to check this again? Would the upgrade to hboot 2.15 put me on 3.18? Sorry for the n0ob questions, help would be appreciated.

Current aosp ROMs no longer require you to down the ts firmware, they haven't since about June. You're a bit confused about the terminology, you didn't just upgrade to the 2.15 hboot, you upgraded to the 2.15 firmware, so you're currently on the 2.15 firmware. The hboot is only one component of the firmware as a whole.
Long story short, yes you can flash non-sense ROMs.
Sent from my Evita.

timmaaa said:
You don't need to buy any hardware or modify your phone physically to gain s-off, all you need to do is follow the instructions on this thread.
If you have SuperCID (which you most likely do) and try to RUU while you're s-on you'll brick your phone. So my advice is to go to the s-off thread I linked to before, and follow the instructions.
Once you've done that you can run the 3.18 RUU.
Sent from my Evita
Click to expand...
Click to collapse
can i run this RUU if i'm on CM10.2 ? and it says it will delete ALL from my phone, do i need to flash a rom and gapps right after i did that or will it still boot on CM10.2 ?

The RUU returns your phone to a stock configuration (ROM/recovery). You need to flash TWRP recovery again afterwards and then your ROM.
Sent from my Evita.

timmaaa said:
The RUU returns your phone to a stock configuration (ROM/recovery). You need to flash TWRP recovery again afterwards and then your ROM.
Sent from my Evita.
Click to expand...
Click to collapse
it doesn't work, i'm getting the usb connection error (170) but the cmd adb devices works just fine and the rumrunner s-off procedure went fine too...maybe i'm missing something ?