Related
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
I have this HTC one S, I am not sure which network phone is it. I bought is from someone else and he had no idea about network.
Right now when i press factory reset from volume down + power button. it brought me at this screen which say clockwork Mod recovery v 5.8.1.5
I am able to select only first 2 options which are reboot system now and install zip from sdcard . When i pressed install zip from sdcard its not doing anything and bringing me back on same screen
Could you please help me installing stock rom on this phone. ?
Thanks in advance guys
AW: [Q] Trying to get HTC one S on stock rom? Please help ?
If you turn ur phone on with holding power and volume down you should be in your bootloader.
Can you tell us what stands on the top?
Locked/unlocked/relocked and which hboot version?
Sent from my HTC One S using xda premium
this is the info
Tampered
Unlocked
VLE PVT ship s-on RL
HBOOT-1.08.0000
Radi-0.16.31501S.06_3
open DSP-v23.1.0.32.0323
eMMC boot
Mar 21, 2012, 16:01:09
Just curious to know what this information means , please let me know each line if possible. Appreciate your help
AW: [Q] Trying to get HTC one S on stock rom? Please help ?
Tampered: no stock recovery
Unlocked: your bootloader is looked
VLE: Ville: HTC One S
S-ON: security on
Radio: your radio Version
You have to lock your bootloader.
Download the all in one toolkit which you can find in the development section. There are all necessary files.
Be sure you have installed the HTC sync driver.
1. Connect your mobile To your pc when your are in the screen where you can see hboot version etc.
2. There should be "hboot USB" in blue.
3. Navigate to hboot and press power.
4. It should change to "fastboot USB" in red.
5. Then open the all in one toolkit on your PC.
6. Open the folder where ADB and fastboot exe are located.
7. Press shift and right click somewhere in the folder and open the command line.
8. Then type in "fastboot oem lock"
9. If you take a look to your phone you should see that the "unlock" changed To "relocked"
That was the first step.
10. Go To the development section in this forum and look for the wwe europe ville ics ruu 2.31 or sth like that.
11. Download the file
12. Doubleklick the file
13. Follow the instructions
14. Let the ruu install everything
15. If everything works fine you should be on official ICS 4.0.4 with Sense 4.1 now
Good luck!
I hope I wrote an easy understandable instruction.
If u experience any problems feel free to post it here.
I'm sure I or someone else can help you.
Sent from my HTC One S using xda premium
NQNH , thanks a lot for this easy and nice explanation, its really helpful for a noob like me. I have few more questions but lets resolve this issue first. Okay I tried all steps you mentioned and it worked like a charm. just got stuck at final step. Please help.
In CMD i got this
'C:\Users\Owner\Desktop\HTC' is not recognized as an internal or external comman
d,
operable program or batch file.
C:\Users\Owner\Desktop\HTC custom rom procedure\One_S_All-In-One_Kit\data>fastbo
ot oem lock
...
(bootloader) Lock successfully...
(bootloader) TZ_HTC_SVC_DISABLE ret = 534642032 (0x1FDDFD70)
FAILED (status read failed (Too many links))
finished. total time: 0.941s
C:\Users\Owner\Desktop\HTC custom rom procedure\One_S_All-In-One_Kit\data>
This is the error message when i tried step 8, but when i checked the screen it shows relocked now , seems like it worked okay.
i tried this file
http://forum.xda-developers.com/showthread.php?t=1941402
Everytime i runs this RUU application file , after passing thru all steps it says ROM utility stopped working, Seems like i am almost done but just stuck at last point.
Hello NQNH, i tried it one more time and finally passed thru that screen. it started ROM update utility but got back with this error msg
Error (131) customer ID error
The ROM update utility cannot update your android phone
please get the correct ROM update utility and try again
I am using RUU : 1.0.6.2012
please let me know if i can use any other utility
AW: [Q] Trying to get HTC one S on stock rom? Please help ?
What do you get when you type in
fastboot getvar cid
?
Try this RUU
http://www.androidfiles.org/ruu/sec...02.31_10.09a.50.04L_release_275655_signed.exe
Sent from my HTC One S using xda premium
I tried RUU which you suggested , Thanks NQNH but sorry this time it came back with error (130) , model ID error.
fastboot getvar cid : BM___001
AW: [Q] Trying to get HTC one S on stock rom? Please help ?
Seems that you have a branded phone. (Bell Mobile Canada?)
This ruu should run fine:
http://www.androidfiles.org/ruu/sec...02.04_10.08g.50.04L_release_280275_signed.exe
Sent from my HTC One S using xda premium
Thanks Thanks Thanks Thanks a lotttttttttt, I don't know if pressing thanks button is good enough to appreciate your help. I learnt a lot from this session. If you don't mind , just for curiosity can i ask you few more questions,
Tampered (Does it mean somebody tried to install custom rom on it or something else ? )
Unlocked
VLE PVT ship s-on RL ( does S-on means this phone is unlocked or some thing else ? )
HBOOT-1.08.0000 ( is it same like version number in iphone , is it baseband version number, where i can find this number in phone settings ? )
Radi-0.16.31501S.06_3
open DSP-v23.1.0.32.0323 ( don't know what it means , please explain )
eMMC boot ( don't know what it means , please explain )
Mar 21, 2012, 16:01:09 ( is it manufacturing date or date when it was tempered )
Thanks again for your help ..
bindudhindsa said:
Thanks Thanks Thanks Thanks a lotttttttttt, I don't know if pressing thanks button is good enough to appreciate your help. I learnt a lot from this session. If you don't mind , just for curiosity can i ask you few more questions,
Tampered (Does it mean somebody tried to install custom rom on it or something else ? )
Unlocked
VLE PVT ship s-on RL ( does S-on means this phone is unlocked or some thing else ? )
HBOOT-1.08.0000 ( is it same like version number in iphone , is it baseband version number, where i can find this number in phone settings ? )
Radi-0.16.31501S.06_3
open DSP-v23.1.0.32.0323 ( don't know what it means , please explain )
eMMC boot ( don't know what it means , please explain )
Mar 21, 2012, 16:01:09 ( is it manufacturing date or date when it was tempered )
Thanks again for your help ..
Click to expand...
Click to collapse
glad to hear that I helped you.
Tampered means that someone already changed something on the phone (unlocked/relocked/custom recovery)
A comparison should be.. if you bought a new pc and if you open the case you have to break the seal. The "Tampered" say that you had break this seal on the phone (e.g. by unlocking the bootloader)
S-ON means that the security flags are on. Its a system protection so nobody can manipulate system data.
S-ON + locked bootloader -> you can do nothing, no root, no custom things
S-ON + unlocked bootloader -> you can flash custom recovery, root, custom rom (you can see an unlocked bootloader as a compromise between S-ON and S-OFF
S-OFF -> you can do everything what you want, change bootloaderGUI, bootanimations, splashscreens.
Unlocked means that you bootloader is unlocked. If its locked you cant install custom recovery, root and custom firmware. It has to be locked when you install a RUU.
You cant find your HBOOT version in your phone settings because its the version of the bootloader.
the bootloader is independed from the rom you are on. Its like the BIOS from your PC and your ROM is Win7 where you either cant find the bios version.
Radio is the module which is responsible for mobile data etc.
no/wrong/corrupt radio = no network/no signal
openDSP .. i don't know
eMMC boot, I guess that this is the partition where the bootloader is located.. but I'm not sure.
Mar 21, 2012, 16:01:09 is the date when .. difficult to explain .. when the development of the RUU was finished?
if I wrote something wrong please correct me.
Thanks a lot for this very helpful information. Appreciate your help. Kind of person like you are the reason these forums are running successfully and helping novice people like me. Thanks again.
AW: [Q] Trying to get HTC one S on stock rom? Please help ?
Thanks for your words
Sent from my HTC One S using xda premium
Hello.
I'm having same problem with getting back on stock firmware...
After trying to flash into CM10, i got stock in CM boot logo.
So trying to get back to original using RUU.
But it just looks like I can not get right one...
I did everything like in posts above, and when I enter "fastboot getvar cid" I got "HTC_Y13"
Any idea which RUU is correct for that?
I'm still trying, so maybe it will be fools luck... Or maybe someone can put me on point?
auronn said:
Hello.
I'm having same problem with getting back on stock firmware...
After trying to flash into CM10, i got stock in CM boot logo.
So trying to get back to original using RUU.
But it just looks like I can not get right one...
I did everything like in posts above, and when I enter "fastboot getvar cid" I got "HTC_Y13"
Any idea which RUU is correct for that?
I'm still trying, so maybe it will be fools luck... Or maybe someone can put me on point?
Click to expand...
Click to collapse
your cid is a unbranded eu cid.
try any unbranded eu ruu (3.16 or earlier)
Hello everyone,
So, 2 days in front of PC, reading forums and trying. No luck... So try to post it here.
I want to flash to CM10.
Bootloader is unlocked.
Recovery is installed (TWRP S4)
Root is done.
Security S-ON.
When I try to install CM10, everything went fine, but when It have to reboot it just stuck in CM booting logo loop...
And since you can't remove memory card on HTC One S, I think I have no other option how to reinstall stock firmware. And my problems starts...
I relocked bootloader.
Download already like five different RUU's...
The problem is, I can not locate my version, it's blank...
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.15.0000
(bootloader) version-baseband: 1.11.50.05.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT23NW410019
(bootloader) imei: 359901040772549
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4010000
(bootloader) cidnum: HTC__Y13
(bootloader) battery-status: good
(bootloader) battery-voltage: 4124mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-64bedd38
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
So everytime I start RUU, in the screen Current information about your Android phone" "Image version" is blank and the one with "Verify that you want to update the ROM version" "From Image Version" is blank...
When I push "Next" it goes "Checking", then "Rebooting Bootloader", "Erasing User Data" and "Sending".
When it comes to "Updating Signature" I'm getting error code...
Phone is bought in Norway, and by checking cid: HTC_Y13, I can see that it's HTC-Nor. So which one of RUU's I have to use?
I also tried to flash zip RUU, using One_S_All-In-One_Kit_v3.5 with same no luck...
Really don't know what to do... Any help would be appreciated...
Thank you in advance!
real187 said:
your cid is a unbranded eu cid.
try any unbranded eu ruu (3.16 or earlier)
Click to expand...
Click to collapse
Thank you, I'm downloading and will try this now:
RUU_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_Radio_1.11.50.05.28_10.27.50.08L_release_301814_signed_2_4.exe
Already tried those:
RUU_Ville_U_ICS_40_S_HTC_Europe_2.31.401.5_Radio_1.06es.50.02.31_10.09a.50.04L_release_275655_signed.exe
RUU_VILLEC2_U_ICS_40_HTC_Europe_1.11.401.110_Radio_16.12.20.02U_16.05.20.16_M2_release_263510_signed.exe
RUU_VILLEC2_U_ICS_40_HTC_Europe_1.11.401.109_Radio_16.12.20.02U_16.05.20.16_M2_release_263131_signed.exe
RUU_VILLEPLUS_U_JB_45_HTC_Generic_1.14.999.50_Radio_1.10r.50.05.19_10.22a.50.08L_release_294323_signed.exe
And also:
OTA_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_1.11.50.05.28_10.27.50.08L_release_301852xf01hejl416oev96.zip
using One_S_All-In-One_Kit_v3.5 with no luck...
Does any body can tell me the difference between Ville, VilleC2 and VillePlus?
real187 said:
your cid is a unbranded eu cid.
try any unbranded eu ruu (3.16 or earlier)
Click to expand...
Click to collapse
Thank you a lot!!!
This one worked:
RUU_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_Radio_1. 11.50.05.28_10.27.50.08L_release_301814_signed_2_4 .exe
auronn said:
Hello everyone,
So, 2 days in front of PC, reading forums and trying. No luck... So try to post it here.
I want to flash to CM10.
Bootloader is unlocked.
Recovery is installed (TWRP S4)
Root is done.
Security S-ON.
When I try to install CM10, everything went fine, but when It have to reboot it just stuck in CM booting logo loop...
And since you can't remove memory card on HTC One S, I think I have no other option how to reinstall stock firmware. And my problems starts...
I relocked bootloader.
Download already like five different RUU's...
The problem is, I can not locate my version, it's blank...
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.15.0000
(bootloader) version-baseband: 1.11.50.05.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT23.......
(bootloader) imei: 3599...............
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4010000
(bootloader) cidnum: HTC__Y13
(bootloader) battery-status: good
(bootloader) battery-voltage: 4124mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-64bedd38
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
So everytime I start RUU, in the screen Current information about your Android phone" "Image version" is blank and the one with "Verify that you want to update the ROM version" "From Image Version" is blank...
When I push "Next" it goes "Checking", then "Rebooting Bootloader", "Erasing User Data" and "Sending".
When it comes to "Updating Signature" I'm getting error code...
Phone is bought in Norway, and by checking cid: HTC_Y13, I can see that it's HTC-Nor. So which one of RUU's I have to use?
I also tried to flash zip RUU, using One_S_All-In-One_Kit_v3.5 with same no luck...
Really don't know what to do... Any help would be appreciated...
Thank you in advance!
Thank you, I'm downloading and will try this now:
RUU_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_Radio_1.11.50.05.28_10.27.50.08L_release_301814_signed_2_4.exe
Already tried those:
RUU_Ville_U_ICS_40_S_HTC_Europe_2.31.401.5_Radio_1.06es.50.02.31_10.09a.50.04L_release_275655_signed.exe
RUU_VILLEC2_U_ICS_40_HTC_Europe_1.11.401.110_Radio_16.12.20.02U_16.05.20.16_M2_release_263510_signed.exe
RUU_VILLEC2_U_ICS_40_HTC_Europe_1.11.401.109_Radio_16.12.20.02U_16.05.20.16_M2_release_263131_signed.exe
RUU_VILLEPLUS_U_JB_45_HTC_Generic_1.14.999.50_Radio_1.10r.50.05.19_10.22a.50.08L_release_294323_signed.exe
And also:
OTA_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_1.11.50.05.28_10.27.50.08L_release_301852xf01hejl416oev96.zip
using One_S_All-In-One_Kit_v3.5 with no luck...
Does any body can tell me the difference between Ville, VilleC2 and VillePlus?
Click to expand...
Click to collapse
Firstly, I would recommend removing part of your IMEI and Serial Numbers from your post, it could be used in bad ways by other people.
Ville is the HTC One S with a Snapdragon S4 chipset, clocked at 1.5GHz (dual core) otherwise known as z520e. (You have this phone)
VilleC2 is what became of the HTC One S when HTC ran out of Snapdragon S4 chipsets in many parts of the world due to a shortage. It has a Snapdragon S3, clocked at 1.7GHz (dual core) otherwise known as z560e.
VillePlus is a Special Edition version of the HTC One S, only available in Taiwan. It has the same processor as the Ville, except comes in a white body instead of the normal grey or black options and has 64GBs of internal storage. The other two have 16GBs internal storage. This phone is quite rare.
You should try RUUs only that say ville, and not VillePlus or VilleC2. These won't work and may even irreversibly damage your phone.
OTAs only work when you already have a previous firmware version. Let's say you were on ICS, a Jelly Bean FOTA is released (firmware over the air) and installs ("flashes") on top of your existing ICS installation, keeping your apps and data.
RUUs wipe all data and wipe everything on the phone when installing through a USB connection.
Could you specify what error code you get on the RUUs?
----
The reason why CM10 didn't boot is because you didn't flash the boot.img.
You need to extract the boot.img from the CM10 zip and put that into your "working folder" (the folder with adb and fastboot files in it)
Open up a command prompt / terminal in that folder and type
fastboot flash boot boot.img
when you are in FASTBOOT USB mode in the bootloader.
Go to Fastboot. Plug in your USB with the phone. Now, ctrl and r --> type cmd --> cd to C:/where your adb is --> fastboot read cid
Then type the 8 digit string that you get. It would help us determine your network provider.
i have a sensation 4g that I had rooted , super cid, and s-off using revolutionary method ,i'm thinking i have a wrong s-on / soft brick maybe that returned my phone to s- on but still rooted and super cid , I have tried the junopbear s-off method , various ruu , and everything else I could find after doing much research with no luck , in the process i lost super cid and now have T-MOB010 cid with htc unlock and rooted .
the problem I think I have had trying to run a ruu to just put back to stock is that I have hboot 1.29 with version 1.50.531.1 and cid T-MOB010 and cannot find a ruu that will match those or update without an error
version: 0.5
(bootloader) version-bootloader: 1.29.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.50.531.1
(bootloader) product: pyramid
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PG58*****
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 3868mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 705f86f6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
any ideas or help on how to either s-off or return to stock and start from scratch would be appreciated
(I have tried kgs , all in one toolkit, control bear windows and linux in a virtual box, various ruu 3.33,1.50,3.32, all error , control bear says cowardly refusing to s off error code B2 B6 41 C9 have flashed stock rooted ics with stock recovery and with 4ext touch with smart flash )
try this ruu
http://hotfile.com/dl/147174878/5c8...0.14.9035.01_M_release_223976_signed.exe.html
or this one
http://shipped-roms.com/download.ph...0U_11.23.3504.07_M2_release_256085_signed.exe
also what error do you have when using ruu.exe?
rzr86 said:
try this ruu
http://hotfile.com/dl/147174878/5c8...0.14.9035.01_M_release_223976_signed.exe.html
or this one
http://shipped-roms.com/download.ph...0U_11.23.3504.07_M2_release_256085_signed.exe
also what error do you have when using ruu.exe?
Click to expand...
Click to collapse
yeah I have tried both of those and I get error 155
also have run as admin and tried PG58IMG.zip method
also I had unlocked the phone so it is a t-mobile but has a strait talk (t-mobile) sim , before I lost s-off i had flashed a PG58IMG that had hboot 1.29.000 , firm 3.33.401.106 , radio 11.76c.3504.00p_11.29A.3504.18_M_PG58IMG so not sure why version changed to 1.50.531.1
was fine till I was messing around with partitioning my sd a couple days later had to pull the battery and when I turned it on it went to bootloader with locked bootloader and s on
watters33 said:
yeah I have tried both of those and I get error 155
also have run as admin and tried PG58IMG.zip method
also I had unlocked the phone so it is a t-mobile but has a strait talk (t-mobile) sim , before I lost s-off i had flashed a PG58IMG that had hboot 1.29.000 , firm 3.33.401.106 , radio 11.76c.3504.00p_11.29A.3504.18_M_PG58IMG so not sure why version changed to 1.50.531.1
was fine till I was messing around with partitioning my sd a couple days later had to pull the battery and when I turned it on it went to bootloader with locked bootloader and s on
Click to expand...
Click to collapse
error 155 AFAIK is a connection issue
when you connect the device to pc from bootloader before using the ruu.exe in the hboot screen must say fastboot usb
did you check that?
Yes always made sure it said fastboot usb
Sent from my HTC Sensation 4G using xda app-developers app
watters33 said:
Yes always made sure it said fastboot usb
Sent from my HTC Sensation 4G using xda app-developers app
Click to expand...
Click to collapse
Hmm,
Then see if your bootloader says locked or relocked
If it is unlocked you must relock it
Sent from my HTC Sensation Z710e using xda premium
rzr86 said:
Hmm,
Then see if your bootloader says locked or relocked
If it is unlocked you must relock it
Sent from my HTC Sensation Z710e using xda premium
Click to expand...
Click to collapse
yes I relocked it to run the ruu tried unlocked and relocked with 4ext recovery and stock recovery
watters33 said:
yes I relocked it to run the ruu tried unlocked and relocked with 4ext recovery and stock recovery
Click to expand...
Click to collapse
give a try with these drivers
http://forum.xda-developers.com/showthread.php?p=36523572
http://d-h.st/v0p
http://forum.xda-developers.com/showthread.php?t=1668276&highlight=tool (second post->old info(click to show content and you will see somewhere a link for htc drivers)
try each one and see if you have success with ruu installation
Hi all,
I successfully unlockes, rooted and S-off my Sensation XE and I think I also SIM-unlocked the phone.
To be able to do this, I had to downgrade my bootloader from 1.29.0000 to 1.17.000 to be able to S-Off it.
I also restored the original backup from the SD card. I never had any errors.
The poblem now is that the phones gets into endless cycles of rebooting and I'm not able to switch it on. I can still asily get into the bootloader. I think the problem lies in the Bootloader version and I tried to find my phone's up-to-date hboot version (I guess it has to be 1.29.1111 now). Any help would be highly appreciated. Links and easy explanation as I'm still a noob please.
Many thanks.
Output of my fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.17.1111
(bootloader) version-baseband: 10.14.9035.01_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.45.531.1
(bootloader) serialno: ********************
(bootloader) imei: *******************
(bootloader) product: pyramid
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PG58*****
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3800mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 92e53710
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
wmgamd said:
Hi all,
I successfully unlockes, rooted and S-off my Sensation XE and I think I also SIM-unlocked the phone.
To be able to do this, I had to downgrade my bootloader from 1.29.0000 to 1.17.000 to be able to S-Off it.
I also restored the original backup from the SD card. I never had any errors.
The poblem now is that the phones gets into endless cycles of rebooting and I'm not able to switch it on. I can still asily get into the bootloader. I think the problem lies in the Bootloader version and I tried to find my phone's up-to-date hboot version (I guess it has to be 1.29.1111 now). Any help would be highly appreciated. Links and easy explanation as I'm still a noob please.
Many thanks.
Click to expand...
Click to collapse
Hi,
If you can get into bootloader,can you please post what it says there?
malybru said:
Hi,
If you can get into bootloader,can you please post what it says there?
Click to expand...
Click to collapse
Thanks for the quick reply. It says:
-Firmware-1.17-
Pyramid PVT SHIP S-OFF RL
HBOOT-1.17.1111
RADIO-10.14.9035.01_M
eMMC-boot
Jun 2 2011,22:31:39
wmgamd said:
Thanks for the quick reply. It says:
-Firmware-1.17-
Pyramid PVT SHIP S-OFF RL
HBOOT-1.17.1111
RADIO-10.14.9035.01_M
eMMC-boot
Jun 2 2011,22:31:39
Click to expand...
Click to collapse
Hi,
You are on GB.
Follow THIS THREAD in order to update your firmware and recovery.
Then, flash a new ROM.
malybru said:
Hi,
Follow THIS THREAD in order to update your firmware and recovery.
Then, flash a new ROM.
Click to expand...
Click to collapse
Thanks. Will do and keep you posted with the results.
Success. :good:
All I needed was the firmware update. My old ROM is back and working.
Thanks a million. you're a star.
wmgamd said:
Success. :good:
All I needed was the firmware update. My old ROM is back and working.
Thanks a million. you're a star.
Click to expand...
Click to collapse
how did you downgrade from hboot 1.29 to 1.17?
boyriot said:
how did you downgrade from hboot 1.29 to 1.17?
Click to expand...
Click to collapse
you can downgrade when you are on S-OFF
boyriot said:
how did you downgrade from hboot 1.29 to 1.17?
Click to expand...
Click to collapse
Hi, I used the same link in the begining of this post, added by malybru and downloaded the firmware 1.17 initially and flashed it. I then followed this link:
http://forum.xda-developers.com/showthread.php?t=1864053 (only the S-off section though as I've rooted and unlocked my phone earlier via HTCDev.com). Then I restored the backup.
when it didn't work as decribed in the begining of my post, I downloaded the newest firmware, but my mistake was that I left the old file (1.17) in the download folder on my pc which led to automatic addition of ''(1)'' to the end of the newest firmware file name. this led to the phone not seeing it as a firmware file and hence not using it.
When Malybru posted the same link, I had more confidence in the file and retried the file 1 more time and this time, I noted the change to the firmware name and corrected it. It all work like a charm.
Good luck.
rzr86 said:
you can downgrade when you are on S-OFF
Click to expand...
Click to collapse
but the OP said, he had to downgrade first before to be able to S-Off it.
so that mean, he was S-ON when downgrading right?
boyriot said:
but the OP said, he had to downgrade first before to be able to S-Off it.
so that mean, he was S-ON when downgrading right?
Click to expand...
Click to collapse
i just read again the OP
you are right
OP how did you downgrade while on S-ON?
rzr86 said:
i just read again the OP
you are right
OP how did you downgrade while on S-ON?
Click to expand...
Click to collapse
Sorry for the confusion. On careful recounting the steps I took, I did indeed S-off it first, using the link in my last post before being able to downgrade. The reason I downgraded was because when using the file PG58DIAG.nbh, I used to get an error msg about S-OFF, so I S-offed it but I kept getting the same error msg; so when researched online, I noticed that another cause for this error could be the wrong firmware so then I had to downgrade...
So I guess you're right rzr86.
Resolved!
Apparently it was due to the fact that I installed Xposed Framework that causes the update process to fail.
I try to manually update the OTA.zip via stock recovery and found out that the process stopped at
"assert failed apply_patch_check( /system/bin/app_process."
Click to expand...
Click to collapse
Further checks showed that Xposed replaced the app_process file and causes it to fail checksum. I then copied /system/bin/app_process.orig back to /system/bin/app_process.
After that, the update was a breeze. The recovery used was from 3.15.707.4 (extracted from OTA.zip).
I've also S-OFF and Super-CID during my testing process.
If your update process stops after 25%, usually some checksum error has happened. Use manual update to determine the error message.
________________________________________________________________________
I'm having a problem updating my Butterfly to Android 4.3 from 4.2.2
My current firmware is 2.33.707.3 and the upgrade version is 3.15.707.4.
On my current phone, I have unlock my bootloader, flash recovery to TWRP 2.6.3.0 as well as rooted it. Due to inexperience, I did not backup my original recovery.
As per gleamed from this forum, I've tried to flash recovery from other stock ROM to proceed with the OTA update.
Steps taken:
Clicked Install now on the OTA message
Phone reboots to recovery
Phone icon with Green exclamation mark appears
Bottom part blue progress bar appears
Upon 30 to 40% progress, the screen changes to Red exclamation mark and update is stopped.
Edit: Did a Factory reset, problem remains.
I've tried the following recovery from other stock ROM without success.
Recovery from 3.15.707.4 (extracted OTA zip in phone's Download folder)
Recovery from 1.19.707.1 (extracted from DLXB1_U_JB_45_hTC_Asia_WWE_1.19.707.1_V0.0)
Recovery from 2.28.709.2 (extracted from OTA_DLXB1_U_JB_50_S_hTC_Asia_TW_2.28.709.2-1.18.709.3)
Recovery from 1.12.707.1
Recovery from 2.33 (from @Bassie39's OTA collection)
Recovery from 2.28.709.3
I've searched high and low for stock Recovery from 2.33.707.3 but unable to locate it.
Any tips or suggestion apart from S-OFF and update firmware, PL99img.zip update via bootloader, look in the OTA collection?
Code:
Model: Butterfly x920d
Android Version: 4.2.2
HTC Sense: 5.0
Software number: 2.33.707.3
CID: 044
[I][B]Bootloader Menu[/B][/I]
*** TAMPERED ***
*** UNLOCKED ***
DELUXE_UB1 PVT SHIP [B]S-ON[/B] RH
[B]HBOOT-1.54.0000[/B]
RADIO-3A.28.306.09
OpenDSP-V10.120.274.0520
[B]OS-2.33.707.3[/B]
eMMC-boot 2048MB
Aug 16 2013
[B][I]Fastboot getvar all results[/I][/B]
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 3A.28.306.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.33.707.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: x
(bootloader) imei: x
(bootloader) meid: x
(bootloader) product: deluxe_ub1
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PL9911000
(bootloader) cidnum: HTC__044
(bootloader) battery-status: good
(bootloader) battery-voltage: 3856mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0c6295fdaf
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
A list of posts with the same problem:
[Q] Help In Updating To 4.3 - Unsolved
Followed @bluheart suggestion - Not working
Try this buddy
Do everything as written.
bluheart said:
Try this buddy
Do everything as written.
Click to expand...
Click to collapse
@bluheart, How do I go from S-OFF to update my OTA? Is Rumrunner better?
Any help or advice would be very appreciated.
Sent from my HTC Butterfly using Tapatalk
Firewater or Rumrunner are equally effective.
I liked Firewater as its very simple to use.
What's the next step after having S-Off?
Sent from my HTC Butterfly using Tapatalk
kemikelx said:
What's the next step after having S-Off?
Sent from my HTC Butterfly using Tapatalk
Click to expand...
Click to collapse
Super cid
Sent from my HTC Butterfly s using XDA Premium 4 mobile app
After supercid flash the TW (Taiwan) firmware not the WWE (World Wide Edition) so that you get faster updates as this is a Taiwanese company. WWE gets updates a lot later (2-4 months later) so think about that.
abhinav.tella said:
After supercid flash the TW (Taiwan) firmware not the WWE (World Wide Edition) so that you get faster updates as this is a Taiwanese company. WWE gets updates a lot later (2-4 months later) so think about that.
Click to expand...
Click to collapse
Yes, This means I have to change the CID to HTC__621? But would this affect my Carrier settings?
kemikelx said:
Yes, This means I have to change the CID to HTC__621? But would this affect my Carrier settings?
Click to expand...
Click to collapse
No, I have done this with my old Butterfly without any bad effects or signal problems.
bluheart said:
Firewater or Rumrunner are equally effective.
I liked Firewater as its very simple to use.
Click to expand...
Click to collapse
Firewater didn't work. Instead I used Rumrunner.
Hope things worked out, and also I hope you took my advice and switched to Taiwan RUU.
You don't have to change CID if you are supercid which is 11111 something like that, you can install any RUU.
Sent from my LG-LS980 using XDA Premium 4 mobile app
abhinav.tella said:
Hope things worked out, and also I hope you took my advice and switched to Taiwan RUU.
You don't have to change CID if you are supercid which is 11111 something like that, you can install any RUU.
Sent from my LG-LS980 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I'm trying to find a way to install the Taiwanese RUU on my phone. Looking around this forum but some of the instructions are contradictory.
Any help or useful links to share?
kemikelx said:
I'm trying to find a way to install the Taiwanese RUU on my phone. Looking around this forum but some of the instructions are contradictory.
Any help or useful links to share?
Click to expand...
Click to collapse
Go to the unlock thread page 9, I posted a detailed S-Off procedure. Any further questions regarding TW firmware they can answer.