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] Stuck at HTC logo after failed stock update

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

Htc sensation xe

hi im using Viper s
sense 5
i got a couple of problems
first i got bootloops
when i first flashed it
so tried different kernels
like viper 3.0.0 3.1.0 3.1.1 3.1.2...
and so on all of them
luckily viper 3.1.1 Kernel Worked
so i flashed it and the camera dose not load when i ht the camera app it launches but show black screen and the closes
no notifications or anything
also wifi is bricked (
rom is pretty smooth and great btw
im on S-off firmware 3.33
hboot 1.27.11< something like that
recovery i have is latest touch http://forum.xda-developers.com/showthread.php?t=2542506
latest TWRP
had CWM tried switching to this one no joy ://
Please help i don't want my love my sensation phone to die i've been holding it for some time now "years"
and it served me well i want to keep it at least until HTC releases a newer version of HTC ONE like the M8 or something like that
Thank you team Venom ARHD Cyanogem mod for keeping this phone alive
and thank's to everyone who tries to help me <3
Love Bio .:good::good::good::good:

biohazzard9 said:
hi im using Viper s
sense 5
i got a couple of problems
first i got bootloops
when i first flashed it
so tried different kernels
like viper 3.0.0 3.1.0 3.1.1 3.1.2...
and so on all of them
luckily viper 3.1.1 Kernel Worked
so i flashed it and the camera dose not load when i ht the camera app it launches but show black screen and the closes
no notifications or anything
also wifi is bricked (
rom is pretty smooth and great btw
im on S-off firmware 3.33
hboot 1.27.11< something like that
recovery i have is latest touch http://forum.xda-developers.com/showthread.php?t=2542506
latest TWRP
had CWM tried switching to this one no joy ://
Please help i don't want my love my sensation phone to die i've been holding it for some time now "years"
and it served me well i want to keep it at least until HTC releases a newer version of HTC ONE like the M8 or something like that
Thank you team Venom ARHD Cyanogem mod for keeping this phone alive
and thank's to everyone who tries to help me <3
Love Bio .:good::good::good::good:
Click to expand...
Click to collapse
Update recovery to 4ext and then flash vipers 5
Don't flash other kernel. .

Itsakash said:
Update recovery to 4ext and then flash vipers 5
Don't flash other kernel. .
Click to expand...
Click to collapse
i've tried no help
but thanks for the help
anymore tips you got ?

biohazzard9 said:
i've tried no help
but thanks for the help
anymore tips you got ?
Click to expand...
Click to collapse
flash the boot.img of viperS 5 rom

rzr86 said:
flash the boot.img of viperS 5 rom
Click to expand...
Click to collapse
i've all related viper kernels that are Jelly bean Including the original boot.img Viper 5.0.0

biohazzard9 said:
i've all related viper kernels that are Jelly bean Including the original boot.img Viper 5.0.0
Click to expand...
Click to collapse
ok redownload the viperS ROM and flash it
if it fails again format your sdcard
note: use 4ext for viper 5

sorry double post

rzr86 said:
ok redownload the viperS ROM and flash it
if it fails again format your sdcard
note: use 4ext for viper 5
Click to expand...
Click to collapse
already did that download but used different SD card like a blank one
and still no help..
thanks for the help
anymore fixes ?

biohazzard9 said:
already did that download but used different SD card like a blank one
and still no help..
thanks for the help
anymore fixes ?
Click to expand...
Click to collapse
this happens only with vipers 5 rom?
post the out put of this command
fastboot getvar all

rzr86 said:
this happens only with vipers 5 rom?
post the out put of this command
fastboot getvar all
Click to expand...
Click to collapse
it happens with revolutionary the one similar to viper 3
sense 4.x Jellybean From sebastianFM
i'm guessing it's because they have the same kernel
-----------------------------------------------------------------------------------
c:\Android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.27.1100
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.33.401.106
(bootloader) serialno: *****************************
(bootloader) imei: *************************
(bootloader) product: pyramid
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PG5813001
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3823mV
(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.491s
-------------------------------------------------------------------------------

i don't know mate
try this use an ruu.exe
then install 4ext again
then the rom
see how it goes
note: remove your imei and serial number

rzr86 said:
i don't know mate
try this use an ruu.exe
then install 4ext again
then the rom
see how it goes
note: remove your imei and serial number
Click to expand...
Click to collapse
thanks for the help
appreciate it
might give that a go

Strange :what:
If other roms works den no use of ruu
I'm out of idea
Hmm
Check md5 of downloaded Rom and flash with all default option( don't select anything ,just accept t&c )
If above method not work den try rzr68s suggestion

Itsakash said:
Strange :what:
If other roms works den no use of ruu
I'm out of idea
Hmm
Check md5 of downloaded Rom and flash with all default option( don't select anything ,just accept t&c )
If above method not work den try rzr68s suggestion
Click to expand...
Click to collapse
MD5 is OK
i believe its a kernel issue
Thanks for the help might give that a go

[Q] Wifi does not work in many custom rom

Hello guys,
I have tried many custom roms and wifi just worked on few of them like "ICE DS v 8.0 FINAL", "Balele v2.1 | ICS 4.0.4 | CM9" and etc . My phone is S-On and HTCDev unlocked . I want to use roms like "PACMan" and "Fallout" if I could
I have read "How to fix wifi error" and I should say :
I'm sure about flashing appropriate boot.img after installing.
I use "4EXT_Recovery_v2.2.7_RC5" and there is no "SmartFlash" in its options.
Apps like "WiFix" didn't work.
So Radio, Kernel and HBOOT remain.
Could you help me ?

Are you flashing the boot.img from the rom in fastboot?

ktks.m said:
Hello guys,
I have tried many custom roms and wifi just worked on few of them like "ICE DS v 8.0 FINAL", "Balele v2.1 | ICS 4.0.4 | CM9" and etc . My phone is S-On and HTCDev unlocked . I want to use roms like "PACMan" and "Fallout" if I could
I have read "How to fix wifi error" and I should say :
I'm sure about flashing appropriate boot.img after installing.
I use "4EXT_Recovery_v2.2.7_RC5" and there is no "SmartFlash" in its options.
Apps like "WiFix" didn't work.
So Radio, Kernel and HBOOT remain.
Could you help me ?
Click to expand...
Click to collapse
Are you s-on or s-off? What is your mid ( fastboot get var all ) ? Does WiFi work on your stock ROM? If so what ROM version is it, if its a ruu can you link to it please.
Sent from my HTC Desire S using Tapatalk

teadrinker said:
Are you flashing the boot.img from the rom in fastboot?
Click to expand...
Click to collapse
yes

heavy_metal_man said:
Are you s-on or s-off?
Click to expand...
Click to collapse
As I mentioned , my phone is S-ON.
heavy_metal_man said:
What is your mid ( fastboot get var all ) ?
Click to expand...
Click to collapse
I didn't get your point (mid ?) If you meant the version of ADT , I use "adt-bundle-windows-x86_64-20140321".
heavy_metal_man said:
Does WiFi work on your stock ROM? If so what ROM version is it, if its a ruu can you link to it please.
Click to expand...
Click to collapse
Yes, WIFI works on stock ROM, This is the stock rom and It is a RUU :
http://dl4.htc.com/RomCode/Source_and_Binaries/RUU_SAGA_ICS_35_S_HTC_EU_14.01.401.2_20.76.30.0835_3831.19.00.110_275068.zip
WIFI Also works on custom ROMs that are based on this RUU . Like this ROM :
http://forum.xda-developers.com/showthread.php?t=1567715
Also it works on CM9 custom ROMs like this :
http://forum.xda-developers.com/showthread.php?t=2037680

Did you flash a different kernel after rom installation? If so, you have to flash the boot.img from the kernel you installed

teadrinker said:
Did you flash a different kernel after rom installation? If so, you have to flash the boot.img from the kernel you installed
Click to expand...
Click to collapse
As I mentioned , I'm sure about flashing appropriate boot.img after installation. It's not the reason.

ktks.m said:
As I mentioned , my phone is S-ON.
I didn't get your point (mid ?) If you meant the version of ADT , I use "adt-bundle-windows-x86_64-20140321".
Click to expand...
Click to collapse
Your mid is a device identifier that denotes region specific devices. Some phones are released under the same name but have slight hardware differences based on their intended market. Its possible that your device has a different WiFi card, and needs a different driver. If you perform the Fastboot command I stated above it will give you a lot of info including your mid.
Have you tried to gain s-off up until now? It would rule out any issues with Fastboot flashing the boot.img of roms.
Sent from my HTC Desire S using Tapatalk

heavy_metal_man said:
Your mid is a device identifier that denotes region specific devices. Some phones are released under the same name but have slight hardware differences based on their intended market. Its possible that your device has a different WiFi card, and needs a different driver. If you perform the Fastboot command I stated above it will give you a lot of info including your mid.
Have you tried to gain s-off up until now? It would rule out any issues with Fastboot flashing the boot.img of roms.
Sent from my HTC Desire S using Tapatalk
Click to expand...
Click to collapse
version: 0.5
version-bootloader: 2.02.0002
version-baseband: 3831.19.00.110
version-cpld: None
version-microp: None
version-main: 14.01.401.2
serialno: xxxxxxx
imei: xxxxxxx
product: saga
platform: HBOOT-7230
modelid: PG8810000
cidnum: HTC__J15
battery-status: good
battery-voltage: 3914mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-90dc471e
hbootpreupdate: 12
gencheckpt: 0
Also I prefer keeping S-ON If it's possible.

ktks.m said:
version: 0.5
version-bootloader: 2.02.0002
version-baseband: 3831.19.00.110
version-cpld: None
version-microp: None
version-main: 14.01.401.2
serialno: xxxxxxx
imei: xxxxxxx
product: saga
platform: HBOOT-7230
modelid: PG8810000
cidnum: HTC__J15
battery-status: good
battery-voltage: 3914mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-90dc471e
hbootpreupdate: 12
gencheckpt: 0
Also I prefer keeping S-ON If it's possible.
Click to expand...
Click to collapse
Hmmmm. If you install a rom your having an issue with, does the wifi start up or get stuck on turning on?
Sent from my Nexus 7 using Tapatalk

heavy_metal_man said:
Hmmmm. If you install a rom your having an issue with, does the wifi start up or get stuck on turning on?
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
It get stuck.

I installed another ROM and WIFI works .
cm-10-20121116-EXPERIMENTAL-saga-NK111
Android Version = 4.1.2 .
I haven't found the reason of my problem yet . I guess the problem would be related to the kernel versions.
I realized ROMs in CM7, CM9, CM10 and "ICE DS v 8.0 FINAL" don't have problem,
Also ROMs in CM10.1 CM10.2, CM11, Ported ROMs and other ROMs based on ICS official like Fallout have problem.
Thank you all

hmm, this could be why my Wifi also gets stuck at connecting.
it can see the wifi signal, but as soon as i click connect, signal falls and nothing happens.
was working (mostly) on stock rom 2.3.5 Sense 3, did not work on CM11 r2 (devil-kin), or on Mokee open source [both 4.4]
still does not work on 4.2 based aokp redefined v3.
it seems i might have to try one of the roms u mentioned here or go back to stock.
@ktks.m, @teadrinker, @heavy_metal_man
is it possible to flash a working kernel on the current rom i am using ?
i am s-on too, and would need to downgrade my hboot if i want to s-off.
thanks

I couldnt get my wifi working,
but this reverse tethering windows tool helped me.
forum.xda-developers.com/showthread.php?t=1371345
those who can live with updating while connected to USB, can try this.

I am now using PAC v23 rom and surprisingly, my Wifi started working in this rom !!

Problem with Custom Roms

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