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
Related
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
Hi everybody
I got a HTC Sensation XE from a friend of mine on which were some Custom ROM'S (InsertCoin, CM9, AOKP, AOKP by Frankinstine) flashed and now I want to flash the original HTC ROM because of warranty issues. Phone was unbranded before I got root.
I downloaded the RUU but if I double click it nothing happens.
I tried to flash InsertCoin or another ROM but now I'm hangin' on the bootscreen.
I got the following information:
fastboot getvar -all is showing me this:
version: 0.5
version-bootloader: 1.27.1100
version-baseband: N/A
version-cpld: None
version-microp: None
version-main: 3.33.401.106
serialno: ***********************
imei: *******************
product: pyramid
platform: HBOOT-8260
modelid: PG5813001
cidnum: HTC__102
battery-status: good
battery-voltage: 4156mV
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: 617f0a98
hbootpreupdate: 11
gencheckpt: 0
Bootloader shows this:
-Revolutionary-
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.27.1100
eMMC-boot
Jan 13 2012, 17:33:34
I got the RUU from here:
filefactory.com
and this is the one I used to flash:
RUU_PYRAMID_LE_ICS_35_S_HTC_Europe_3.33.401.153_Radio_1...
could somenone help me?
greets
bavguy
Thats a bad download - easy to tell with RUU's because they are exe files so if its a bad download it just doesnt run, try this one:
http://icxperia.com/jonny/RUU/HTC Sensation XE 3.33.401.153/
I'll try it
is there anything else I have to do, to get back the factory-state?
don't work
I downloaded the RUU but same problem as before. RUU don't starts?
what could be the problem?
bavguy87 said:
I downloaded the RUU but same problem as before. RUU don't starts?
what could be the problem?
Click to expand...
Click to collapse
maybe your not waiting long enough, the RUU doesnt start immediately, its in the background copying all the temporary files to temp folder.
How long?
how long should I wait?
also there is no process running in background.
At least Task-Manager shows any process.
bavguy87 said:
I downloaded the RUU but same problem as before. RUU don't starts?
what could be the problem?
Click to expand...
Click to collapse
Hi,
Did you try it when the phone is connected to the PC via fastboot USB (in the bootloader) ?
malybru said:
Hi,
Did you try it when the phone is connected to the PC via fastboot USB (in the bootloader) ?
Click to expand...
Click to collapse
Wont help, apparently the RUU isnt even starting up...
tried both
meanwhile I restored a nandroid backup with CM 9.1.0 and CM is running.
I tried both in the bootloader with fastboot and when system is booted but I still want to flash the Stock ROM.
bavguy87 said:
meanwhile I restored a nandroid backup with CM 9.1.0 and CM is running.
I tried both in the bootloader with fastboot and when system is booted but I still want to flash the Stock ROM.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1923629
That is stock 3.33.401.153
also not
this RUU is also not running
bavguy87 said:
this RUU is also not running
Click to expand...
Click to collapse
I mean the ROM is stock, just flash the ROM
deodexed or odexed?
which should I flash?
deodexed or odexed?
I currently loading the odexed one.
bavguy87 said:
which should I flash?
deodexed or odexed?
I currently loading the odexed one.
Click to expand...
Click to collapse
Odexed is fully stock but you cant flash any addons/mods/themes because they wont work with odexed ROMs, only deodexed
odexed is the right
so I can flash odexed. I just want Stock rom, unroot and s-on and then I will send it back to HTC.
is this right?
bavguy87 said:
so I can flash odexed. I just want Stock rom, unroot and s-on and then I will send it back to HTC.
is this right?
Click to expand...
Click to collapse
you cant S-ON with an unsigned hboot (juopunut or revolutionary hboots) as they will cause brick
what now?
I flashed the odexed Stock ROM and it is running.
for warranty issues I have to do s-on, unroot, stock recovery and Stock ROM, haven't I?
what should I do now?
just downgrade the base version, install ginger bread rom and then try flashing stock ruu. worked for me.
how?
and how does this work. do you get some links to downloads and guides for me?
bavguy87 said:
and how does this work. do you get some links to downloads and guides for me?
Click to expand...
Click to collapse
1.17 is HERE
You will need to flash a GB ROM at the same time.
ICS ROMS will not work on this firmware.
GB ROM is HERE
Before you do that,have you looked at THIS GUIDE
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
Heyy, so i was wondering if yous could help me. I have a stock HTC Sensation EU, t-mobile version, which I had updated to the latest version (4.0.3 I think). During the upgrade-process something went wrong and now it doesn't go past the HTC logo. S-ON. When in Hboot it shows no found something.img. What is the way to fix this?
If possible I'd like to root it as well and use the Cyanogenmod.
HI, is it possible to you to go In Recovery Mod or Fastboot???
If it's yes,
Go here :
[GUIDE][N00b] Flash a ROM from 100% Stock!
This is a guide that give u all the way to unlock ur bootloader, change your stock recovery with a custom one (4ext).
Then u'll be able to install a ROM custom.
Here u can found a lot of ROM Developped for HTC SENSATION.
Sensation Android Development
blogodoblogodo said:
HI, is it possible to you to go In Recovery Mod or Fastboot???
If it's yes,
Go here :
[GUIDE][N00b] Flash a ROM from 100% Stock!
This is a guide that give u all the way to unlock ur bootloader, change your stock recovery with a custom one (4ext).
Then u'll be able to install a ROM custom.
Here u can found a lot of ROM Developped for HTC SENSATION.
Sensation Android Development
Click to expand...
Click to collapse
Seems good, i´ll try it out
blogodoblogodo said:
HI, is it possible to you to go In Recovery Mod or Fastboot???
If it's yes,
Go here :
[GUIDE][N00b] Flash a ROM from 100% Stock!
This is a guide that give u all the way to unlock ur bootloader, change your stock recovery with a custom one (4ext).
Then u'll be able to install a ROM custom.
Here u can found a lot of ROM Developped for HTC SENSATION.
Sensation Android Development
Click to expand...
Click to collapse
So it worked, but it didn't. I managed to install a custom rom, but after 10 seconds (if it even was that much), the system crashes and reboots, only to do the same thing again.
I used a RUU as well but I got a signing error (132) when using the RUU. I then tried installing the RUU through fastboot and I got further. I did however got the error saying the CID wasn't matching. In the .txt file from the zip I had added my CID, So I thought it had to work.
There is no official rom for my cid (T-MOB003) unfortunately.
This is starting to give me a headache
Search for this HERE
blogodoblogodo said:
Search for this HERE
Click to expand...
Click to collapse
Well DEFINITELY not there.
Those are Sensation XL.
Here's for our Sensation http://forum.xda-developers.com/showthread.php?t=1672425
Hoooooooo, Nooo,
Sorry ,really sorry
I googled "T-MOB003 for SENSATION"
Sorry DrNickjen
Thank You Nicx59
Nicx59 said:
Well DEFINITELY not there.
Those are Sensation XL.
Here's for our Sensation http://forum.xda-developers.com/showthread.php?t=1672425
Click to expand...
Click to collapse
I have read that once, but I'll do it again; this time more thorougly.
The RUU I'm trying to install is RUU_PYRAMID_ICS_HTC_Europe_3.32.401.5_Radio_11.69.3504.00U_11.22.3504.07_M_release_246089_signed
fastboot getvar all returns
Code:
c:\Android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.18.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.50.114.2
(bootloader) serialno: xxx
(bootloader) imei: xxx
(bootloader) product: pyramid
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PG5813000
(bootloader) cidnum: T-MOB003
(bootloader) battery-status: good
(bootloader) battery-voltage: 4104mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 9d24123f
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Since my cidnum is not in the RUU, (and there isn't a RUU for my cid) I'll have to add it according to the guide. I'll get to that later. hboot version to install and version-main are both higher than currently installed, so that shouldn't be an issue.
My phone is S-ON, but unlocked so I'll have to relock it again. Followed instructions and device is *** RELOCKED ***. Displays, however, a security warning. I'll now proceed with the installation by executing the exe. If I'm right I should see an error.
Error: Customer ID incorrect, as expected. I'll now try to install manually.
Since my CID is different I'll change it in the .zip. 7z didn't allow me to change it in the archive itself so I've extracted the archive, changed android-info.txt to:
Code:
modelid: PG5813000
cidnum: HTC__001
cidnum: HTC__E11
cidnum: HTC__N34
cidnum: HTC__203
cidnum: HTC__102
cidnum: HTC__405
cidnum: HTC__Y13
cidnum: HTC__A07
cidnum: HTC__304
cidnum: HTC__032
cidnum: HTC__016
cidnum: T-MOB003
mainver: 3.32.401.5
hbootpreupdate:12
DelCache:1
Note: When pasting this my CID was placed on the same line as mainver. Inserted an enter and repasted in android-info.txt.
What I did as well was unlock the bootloader again, changed recovery to the file inside the rom.zip, and relocked the bootloader. I read this was a fix for the problem.
THIS POST IS IN PROGRESS
HI its not necessary to show ure imei, plz, edit your post and Erase it.
blogodoblogodo said:
HI its not necessary to show ure imei, plz, edit your post and Erase it.
Click to expand...
Click to collapse
Thanks.
Just Hit ThAnks Button
So For you, is it good???
blogodoblogodo said:
Just Hit ThAnks Button
So For you, is it good???
Click to expand...
Click to collapse
Nope. I gave up fot the day because I couldn't het the PG58IMG flashed. It didn't have an effect in hboot so I tried using fastboot but i got an unknown error. The tries installing ViperS 2.0, which succeeded. On boot, however, the system crashed and rebooted automatically, just like the other rom's i've tried.
If only I could get a rom working...
DrNickjen said:
Nope. I gave up fot the day because I couldn't het the PG58IMG flashed. It didn't have an effect in hboot so I tried using fastboot but i got an unknown error. The tries installing ViperS 2.0, which succeeded. On boot, however, the system crashed and rebooted automatically, just like the other rom's i've tried.
If only I could get a rom working...
Click to expand...
Click to collapse
actually if you are still on gingerbread firmware you can't boot any ics or jb rom
flash this rom from recovery
http://d-h.st/bqL
if you still want to upgrade to ics then S-OFF the device from here
http://revolutionary.io/
after that flash 3.33 universal from here
http://forum.xda-developers.com/showthread.php?t=1459767
follow the instructions to the letter
and before flashing check md5 sums(important)
then flash any ics or jb rom from recovery
rzr86 said:
actually if you are still on gingerbread firmware you can't boot any ics or jb rom
flash this rom from recovery
http://d-h.st/bqL
if you still want to upgrade to ics then S-OFF the device from here
http://revolutionary.io/
after that flash 3.33 universal from here
http://forum.xda-developers.com/showthread.php?t=1459767
follow the instructions to the letter
and before flashing check md5 sums(important)
then flash any ics or jb rom from recovery
Click to expand...
Click to collapse
Flashed it using Cwm, first did a full wipe and it installed fine. It then booted en got to a black screen and rebooted. Wiping Dalvik cache + /cache didn't work as a solution.
Same thing as any other .zip I've installed through recovery.
DrNickjen said:
Flashed it using Cwm, first did a full wipe and it installed fine. It then booted en got to a black screen and rebooted. Wiping Dalvik cache + /cache didn't work as a solution.
Same thing as any other .zip I've installed through recovery.
Click to expand...
Click to collapse
can you post your bootloader details again and what rom did you try to flash now?
also did you try to follow the steps i gave you?
rzr86 said:
can you post your bootloader details again and what rom did you try to flash now?
also did you try to follow the steps i gave you?
Click to expand...
Click to collapse
UNLOCKED
Pyramid PVT SHIP S-ON RL
HBOOT-1.18.000
eMMC-boot
August 2nd 2011
Tried to flash the rom you linked to and yes I have.
DrNickjen said:
UNLOCKED
Pyramid PVT SHIP S-ON RL
HBOOT-1.18.000
eMMC-boot
August 2nd 2011
Tried to flash the rom you linked to and yes I have.
Click to expand...
Click to collapse
change the recovery to 4ext
before flash the rom enable smartflash from 4ext
rzr86 said:
change the recovery to 4ext
before flash the rom enable smartflash from 4ext
Click to expand...
Click to collapse
I love you omg it worked <3 <3
So, what do I have to do in order to get e.g. Cyanogenmod running?
DrNickjen said:
I love you omg it worked <3 <3
So, what do I have to do in order to get e.g. Cyanogenmod running?
Click to expand...
Click to collapse
First make a full backup of your device through 4ext.
Then just flash the zips from one of the following releases:
android1234567's release (here you have to flash rom and kernel seperately)
albinoman887's releease
And last flash gapps from here
DrNickjen said:
I love you omg it worked <3 <3
So, what do I have to do in order to get e.g. Cyanogenmod running?
Click to expand...
Click to collapse
see my previous post of what to do now
S-OFF
flash 3.33 universal(check md5 sums before flashing)
flash cyanogenmod rom
done
note:when you achieve S-OFF you won't need anymore the smartflash feature
Hi there i tested these ROMS on mine HTC One S Ville S4 (International).
Here the Results:
Maximus 10.0.0 - http://forum.xda-developers.com/showthread.php?t=2445392
I´ve followed all steps but no luck, the phone reach splash screen and all i get is all 3 lights on the bottom and a green on the top illuminated.
LIBERTY ROM - The Sixth Element 4.4.2/4.4.3
Almost the same situation with Maximus Rom but with Black splash screen this time on the 2 versions of this Rom
At the moment i have the ViperOneS 3.2.0 but i would like test other Roms.
Here my specs:
----> Start <----
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.13.0000
(bootloader) version-baseband: 0.16.31501S.17_2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) serialno: SH24PW******
(bootloader) imei: ***************
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4010000
(bootloader) cidnum: HTC__304
(bootloader) battery-status: good
(bootloader) battery-voltage: 3873mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d92cc658
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.071s
----> End <----
you need a specific hboot to try the rom. i think is 2.15 and you have 1.13.. so..... i think that is the problem.
first of all you'd update all that is possible to lates ver. (hboot, recovery), may be you should try hboot 2.16 and roms for it...
grorg said:
first of all you'd update all that is possible to lates ver. (hboot, recovery), may be you should try hboot 2.16 and roms for it...
Click to expand...
Click to collapse
No luck with RUUs
vic_111 said:
No luck with RUUs
Click to expand...
Click to collapse
You will need to update HBOOT to version 2.15 or 2.16 depending on which rom you want to install. HTC__304 is Europe/Spain so the Europe RUU should be fine for you. Its pretty easy:
Download FIRMWARE HBOOT 2.15
Extract the included recovery and flash it using fastboot:
fastboot flash recovery recovery.img
Relock your bootloader (in case it's actually locked)
fastboot oem lock
Then flash the firmware215.zip:
fastboot oem rebootRUU
fastboot flash zip firmware215.zip
fastboot flash zip firmware215.zip (First time you probably get an error, so just retype the command!!!)
fastboot reboot-bootloader (to get back into bootloader mode)
LS.xD said:
You will need to update HBOOT to version 2.15 or 2.16 depending on which rom you want to install. HTC__304 is Europe/Spain so the Europe RUU should be fine for you. Its pretty easy:
Download FIRMWARE HBOOT 2.15
Extract the included recovery and flash it using fastboot:
fastboot flash recovery recovery.img
Relock your bootloader (in case it's actually locked)
fastboot oem lock
Then flash the firmware215.zip:
fastboot oem rebootRUU
fastboot flash zip firmware215.zip
fastboot flash zip firmware215.zip (First time you probably get an error, so just retype the command!!!)
fastboot reboot-bootloader (to get back into bootloader mode)
Click to expand...
Click to collapse
He's S-On, are you sure it'll work like this? Flashing firmware is not possible unless you're S-Off. He should first try to achieve S-Off via rumrunner or other method (since he's already using Viper or a close-to-stock ROM). Then he might try flashing 2.15/2.16 firmware
Rapier said:
He's S-On, are you sure it'll work like this? Flashing firmware is not possible unless you're S-Off. He should first try to achieve S-Off via rumrunner or other method (since he's already using Viper or a close-to-stock ROM). Then he might try flashing 2.15/2.16 firmware
Click to expand...
Click to collapse
I'm sure. Flashing "SIGNED" zips will totally work with S-ON.
LS.xD said:
I'm sure. Flashing "SIGNED" zips will totally work with S-ON.
Click to expand...
Click to collapse
I will give it a try , hope I don't get a brick
But I have two questions:
1What you mean "locked" I have my boot loader unlocked!
When I finish the flash process I can unlock again?
Sent from my HTC One S
vic_111 said:
I will give it a try , hope I don't get a brick
But I have two questions:
1What you mean "locked" I have my boot loader unlocked!
When I finish the flash process I can unlock again?
Sent from my HTC One S
Click to expand...
Click to collapse
You can unlock it at any time, but you will have to lock it before upgrade the firmware.
LS.xD said:
You can unlock it at any time, but you will have to lock it before upgrade the firmware.
Click to expand...
Click to collapse
No luck, upgraded sucessfully but now i have a blank screen blinking
Update: Should i update to 2.16? If yes where i can get it?
Update URGENT: I cant install any rom now help please
Update 2: I tried install 2.16 but unsucessfull
Update 3:Anyone can find a RUU for me , because i cant :crying:
Update 4: Well i am on ViperOneS again , somehow (flashed boot.img before aroma-installer),but i would like test Liberty one you think you can send me hboot 2.16 signed , i tried find but only for s-off
Update 5 [LAST ONE]: Finally i get it Liberty Rom works 100% thanks for all the help guys , REALLY!!!
vic_111 said:
No luck, upgraded sucessfully but now i have a blank screen blinking
Update: Should i update to 2.16? If yes where i can get it?
Update URGENT: I cant install any rom now help please
Update 2: I tried install 2.16 but unsucessfull
Update 3:Anyone can find a RUU for me , because i cant :crying:
Update 4: Well i am on ViperOneS again , somehow (flashed boot.img before aroma-installer),but i would like test Liberty one you think you can send me hboot 2.16 signed , i tried find but only for s-off
Click to expand...
Click to collapse
Update 5 [LAST ONE]: Finally i get it Liberty Rom works 100% thanks for all the help guys , REALLY!!!
vic_111 said:
No luck, upgraded sucessfully but now i have a blank screen blinking
Update: Should i update to 2.16? If yes where i can get it?
Update URGENT: I cant install any rom now help please
Update 2: I tried install 2.16 but unsucessfull
Update 3:Anyone can find a RUU for me , because i cant :crying:
Update 4: Well i am on ViperOneS again , somehow (flashed boot.img before aroma-installer),but i would like test Liberty one you think you can send me hboot 2.16 signed , i tried find but only for s-off
Update 5 [LAST ONE]: Finally i get it Liberty Rom works 100% thanks for all the help guys , REALLY!!!
Click to expand...
Click to collapse
I'm glad you finally made it. HBOOT 2.16 works with S-OFF only, thats why I uploaded 2.15. As @Rapier mentioned earlier, you can use rumrunner.us for easily getting S-OFF
Mind you that hboot 2.16 gives you shared internal storage. E.g. all free space is available to all partitions. This may come tot be necessary for you if flashing lollipop roms since the "foot print" of installed aps on lollipop becomes much larger. This has to do with runtime environment... Kitkat runs with Dalvik Cache whereas Lollipop runs with the Android Runtime aka ART.
So, staying on hboot 2.15 give you the old partition layout with approx. 1 GByte(??) free for apps and 7 as internal SD.
While hboot 2.16 serves all your free internal storage to all partitions. This saves you headache of internal space for apps running out.
(Someone may deel to fill in the technical gaps i left in)
Cheers , happy hboot 2.16 user.
Verstuurd vanaf mijn One S met Tapatalk