Database Info

[Q] Will not go back to stock

Tampered
unlocked
Evita PVT ship s-on RL
Hboot-1.09.0000
radio-0.19as.32.09.09_L
OpenDSP-v28.1.0.32.0504
eMMC-boot
Apr 2 2012,21:08:24
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.09.0000
(bootloader) version-baseband: 0.19as.32.09.09_L
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) serialno: HT246W318545
(bootloader) imei: 359691041******
(bootloader) product: evita
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ8310000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4073mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: e964c535
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.064s
I bought this phone from someone and it already had CM10 on it. I want to return it back to stock and I have had no luck at all. I have exhausted every avenue I could think of. There is no backup for the original.
Once I remove root, re-lock it, run RUU it gets stuck at the HTC screen and does nothing. On the computer it says sending.........
As you can see the version-main: is blank, so I do not know the correct version to flash. No idea. Help
Currently running CM10 with Twrp recovery 2.3.1
Throwing info out there....
When i re-lock it it still says **tampered
**Locked
HTC brilliant screen shows underneath in red this is for development purposes.....
Give me ideas I will try it.

Wrong section boss
Sent from my HTC One XL using xda app-developers app

I need a ticket to One X Q&A, Help & Troubleshooting please.
Or close this one I will open over there.
sorry

Join Date: Feb 2010
smh still doing it wrong

CheesyNutz said:
Join Date: Feb 2010
smh still doing it wrong
Click to expand...
Click to collapse
It was an accident jack a**

Maybe edit out your imei number.
WR
Injected from My ViperXL

Did not know this was in development now, I would of thought One X Q&A, Help & Troubleshooting

Threads been lost in shuffle.
WR
Injected from My ViperXL

Palmetto_X said:
I need a ticket to One X Q&A, Help & Troubleshooting please.
Or close this one I will open over there.
sorry
Click to expand...
Click to collapse
The easy way to get it moved is to click on the report button and select thread move, one of the mods will move it to the Q&A section for you. :good:

My radio says??
radio-0.19as.32.09.09_L
This matches with this.........
RUU_EVITA_UL_ICS_40_S_hTC_Asia_WWE_2.23.707.2_Radio_0.19as.32.09.09_L_10.
My thinking is that I am flashing the wrong RUU. I dont know.
I unlocked it again, flashed the stock recovery.img, relocked it
Now I am going to try the RUU again
RUU_Evita_UL_ATT_US_1.44.502.1_Radio_0.15.3201.09_release_249105

Palmetto_X said:
My thinking is that I am flashing the wrong RUU. I dont know.
Click to expand...
Click to collapse
That is the first thing I thought of (flashing wrong RUU) when I first started reading your post. As long as your PC is recognizing the phone (sounds like it is) and the bootlaoder is locked (you said it was) then RUU failing is almost always becuase of the wrong RUU. You need the right RUU for your carrier version, and it has to be equal to or newer than the firmware and hboot currently on the phone.
Palmetto_X said:
RUU_EVITA_UL_ICS_40_S_hTC_Asia_WWE_2.23.707.2_Radio_0.19as.32.09.09_L_10.
Click to expand...
Click to collapse
I assume you have the AT&T version. If so, this is absolutely the wrong RUU. Its obviously for the Asian version. You need an AT&T RUU.
Palmetto_X said:
Now I am going to try the RUU again
RUU_Evita_UL_ATT_US_1.44.502.1_Radio_0.15.3201.09_release_249105
Click to expand...
Click to collapse
Where the heck did you get that? 1.44 firmware? You want ATT 1.73 or 1.85 (those match with hboot 1.09).
Try one of the RUU links in my Index thread: http://forum.xda-developers.com/showthread.php?t=1671237

redpoint73 said:
That is the first thing I thought of (flashing wrong RUU) when I first started reading your post. As long as your PC is recognizing the phone (sounds like it is) and the bootlaoder is locked (you said it was) then RUU failing is almost always becuase of the wrong RUU. You need the right RUU for your carrier version, and it has to be equal to or newer than the firmware and hboot currently on the phone.
I assume you have the AT&T version. If so, this is absolutely the wrong RUU. Its obviously for the Asian version. You need an AT&T RUU.
Where the heck did you get that? 1.44 firmware? You want ATT 1.73 or 1.85 (those match with hboot 1.09).
Try one of the RUU links in my Index thread: http://forum.xda-developers.com/showthread.php?t=1671237
Click to expand...
Click to collapse
Thanks I'll try that
Is there anything I can do with the ROM.zip that is extracted when you start the RUU....exe?
It is extracted to
C:\Users\%username%\AppData\Local\Temp\

Palmetto_X said:
Is there anything I can do with the ROM.zip that is extracted when you start the RUU....exe?
It is extracted to
C:\Users\%username%\AppData\Local\Temp\
Click to expand...
Click to collapse
Don't know.
But it brings up a good point. If you just want to return to a stock Sense ROM, and keep custom recovery, etc. then just flash a stock rooted ROM, which can be found in the Development section.
http://forum.xda-developers.com/showthread.php?t=1671237
Or for that matter, just flash a custom ROM like CleanROM or ViperXL, that are based on stock Sense, but cleaned up of bloat, and with some cool extra features.

redpoint73 said:
Don't know.
But it brings up a good point. If you just want to return to a stock Sense ROM, and keep custom recovery, etc. then just flash a stock rooted ROM, which can be found in the Development section.
http://forum.xda-developers.com/showthread.php?t=1671237
Or for that matter, just flash a custom ROM like CleanROM or ViperXL, that are based on stock Sense, but cleaned up of bloat, and with some cool extra features.
Click to expand...
Click to collapse
Same response after I tried to flash bot RUU 1.8 & 1.7. Hung at HTC
I flashed TWRP recovery and deleted everything
I also tried to flash from the ROM.zip in the RUU 1.8 boot_signed.img & system.img
fastboot flash boot boot_signed.img
that went fine
fastboot flash system system.img
I got
FAILED (remote: data length is too large)?
I wonder if that is what is hanging it in RUU
stock rooted ROM as in which ones? Something like this radavs-pablo11-TelstraJB-stock?

Palmetto_X said:
stock rooted ROM as in which ones? Something like this radavs-pablo11-TelstraJB-stock?
Click to expand...
Click to collapse
That is a stock rooted one, yes. In my index thread I posted previously, they are all listed under "Stock Rooted (Odexed/De-Odexed)" below "CUSTOM ROMs"
Here is the link again: http://forum.xda-developers.com/showthread.php?t=1671237
You can flash any of them. But the AT&T ones are the easiest to get up and running (1.85, 2.20). The others, you will need to manually enter AT&T's APN info to get a cellular data connection.
And please click the "Thanks" button for any of my posts you found helpful.
---------- Post added at 04:02 PM ---------- Previous post was at 03:56 PM ----------
Palmetto_X said:
Same response after I tried to flash bot RUU 1.8 & 1.7. Hung at HTC
Click to expand...
Click to collapse
Strange. Its an AT&T branded version? It actually says has the AT&T logo on the front of the phone, over the top of the screen?

redpoint73 said:
Strange. Its an AT&T branded version? It actually says has the AT&T logo on the front of the phone, over the top of the screen?
Click to expand...
Click to collapse
Yes it is AT&T at the top of the phone

Palmetto_X said:
Yes it is AT&T at the top of the phone
Click to expand...
Click to collapse
Odd, then I don't know why the 1.73 and 1.85 RUUs are not working, as long as you have the AT&T CID or SuperCID.
Just try flashing a stock rooted ROM from TWRP, like I suggested above. To me, its really the best place to be if the phone is new to you, and you might want to later flash any custom ROMs or mods. You get to start off with the stock ROM to get familiar with the phone, before seeing what features or mods you might want in a custom ROM. But the phone would still be bootloader unlocked, rooted, and custom recovery, so it will be ready to go when you are ready for some mods.

redpoint73 said:
Odd, then I don't know why the 1.73 and 1.85 RUUs are not working, as long as you have the AT&T CID or SuperCID.
Just try flashing a stock rooted ROM from TWRP, like I suggested above. To me, its really the best place to be if the phone is new to you, and you might want to later flash any custom ROMs or mods. You get to start off with the stock ROM to get familiar with the phone, before seeing what features or mods you might want in a custom ROM. But the phone would still be bootloader unlocked, rooted, and custom recovery, so it will be ready to go when you are ready for some mods.
Click to expand...
Click to collapse
Ran the 2.2 RUU from another machine and got it going. Thank you very much for your help

Can't flash JB roms on HTC One S C2

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

:thumbup:
Sent from my Evita

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

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

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

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

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

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

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

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

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

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

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

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

How To Update Firmware

I decided to write this, even though it was already written by SO many people already, to have it in an easily accessible spot
YOU MUST ALSO BE SUPERCID!!
YOU MUST BE S-OFF!!!!!!! http://forum.xda-developers.com/showthread.php?t=2155071
So here we go!
2.15 Firmware: http://www.androidfilehost.com/?fid=23060877490004040
2.18 Firmware: https://www.androidfilehost.com/?fid=23329332407572084
Download the firmware zip. Put it in a folder where you have the fastboot sdk tool
Plug your phone in with USB Debugging
Reboot into bootloader:
adb reboot bootloader
Click to expand...
Click to collapse
Open a command window in the folder with fastboot sdk
Once the phone gets to bootloader, go into fastboot
Check if fastboot commands are working:
fastboot devices
Click to expand...
Click to collapse
Now the fun starts:
fastboot oem rebootRUU
fastboot flash zip <WhateverYouCalledYourFirmwareZip.zip>
Click to expand...
Click to collapse
if it shows FAILED (remote: 90 hboot pre-update! please flush image again immediately)":
fastboot flash zip <WhateverYouCalledYourFirmwareZip.zip>
Click to expand...
Click to collapse
If it ends with "INFO..... OK", reboot to the bootloader:
fastboot reboot-bootloader
Click to expand...
Click to collapse
Verify everything was successful by running:
fastboot getvar all
Click to expand...
Click to collapse
This is what you're supposed to see:
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.15.0000 (2.18.0000 if you used the 2.18 zip)
(bootloader) version-baseband: 1.31a.32.45.16_2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.08.111.2 (5.18.xxx.x if you used 2.18 zip)
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) product: evita
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ8310000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4140mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-de589c6eef
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
Reboot into Android:
fastboot reboot
Click to expand...
Click to collapse
Reboot into Recovery:
fastboot reboot-recovery
Click to expand...
Click to collapse
Thanks to Turge and everyone else who helped with this firmware and Sense 5
Thanks @24ky for 2.18 firmware zip
CLICK THANKS IF I HELPED!!!!!!

I might be wrong, but this probably belongs in the General section as it isn't your own development.
Sent from my Evita

Moved to General.

Yeah sorry guys. Was in a rush to create this between classes and wasn't paying attention to the section.
Sent from my HTC One XL using XDA Premium 4 mobile app

Worked fine
I saw this in other threads but used this one since it was right there at the top. Everything went fine, thanks

Madcat8686 said:
I saw this in other threads but used this one since it was right there at the top. Everything went fine, thanks
Click to expand...
Click to collapse
can you do update to firmware 2.15 with S-ON and no SuperCID (it's still Roger001)?
cause I'm getting lost connection and random reboots with Viper XL 4.2.0
I tried Beastmode kernel but WiFi stopped working..

No you can't. Maybe it's time you got SuperCID and s-off, it's a good thing to have anyway.
Sent from my Evita

timmaaa said:
No you can't. Maybe it's time you got SuperCID and s-off, it's a good thing to have anyway.
Sent from my Evita
Click to expand...
Click to collapse
believe me I want to!
but I'm not sure how to do it yet.
(chicken-egg situation, lol)
I've read conflicting things, like you have to have SuperCID first before you S-off..
but then I read that you need to S-off first
which one is it?

If you can't read and understand the instructions in the S-OFF thread you are not ready
Sent from my HTC One XL

Get s-off before they patch it in the next update. Besides, you can fully customize your systems with kernels easily
Did I mention no fastboot commands?
Sent from my HTC One XL using XDA Premium 4 mobile app

clockwars said:
believe me I want to!
but I'm not sure how to do it yet.
(chicken-egg situation, lol)
I've read conflicting things, like you have to have SuperCID first before you S-off..
but then I read that you need to S-off first
which one is it?
Click to expand...
Click to collapse
It's stated pretty clearly in the s-off thread that you must have SuperCID first. I'm not sure where you think you read that s-off is required for SuperCID but that's 100% incorrect.
Sent from my Evita

timmaaa said:
It's stated pretty clearly in the s-off thread that you must have SuperCID first. I'm not sure where you think you read that s-off is required for SuperCID but that's 100% incorrect.
Sent from my Evita
Click to expand...
Click to collapse
no offence!
I'm not accusing anyone of anything! lol
and I'm obviously not an Android guru..
As you can see from my number of posts, I'm not a regular here!
so I wasn't following the progress of things..
and I'm not familiar with the specific thread you guys mention.
I was mostly using Google,
and trying to find someone with a Rogers version, to see how they did it.
And almost every bit I found would read "SuperCID for S-off" so I assumed that you need an S-off device in order to get SuperCID..

Ok, I wouldn't suggest going to any site for info other than XDA, you could end up with incorrect information as other sites don't properly distinguish between models. Long story short, stay on XDA and specifically within this forum.
You can get SuperCID using hex edit method. Then you can get s-off using Facepalm S-off.
Sent from my Evita

clockwars said:
no offence!
I'm not accusing anyone of anything! lol
and I'm obviously not an Android guru..
As you can see from my number of posts, I'm not a regular here!
so I wasn't following the progress of things..
and I'm not familiar with the specific thread you guys mention.
I was mostly using Google,
and trying to find someone with a Rogers version, to see how they did it.
And almost every bit I found would read "SuperCID for S-off" so I assumed that you need an S-off device in order to get SuperCID..
Click to expand...
Click to collapse
You are definitely on the right site but you need to read through the directions and understand what they mean. It's important that you know just what S-Off and Super CID mean to the phone before you try these procedures out. Taking a test drive without getting ALL the steps (and there are more) in order and correct CAN and WILL brick your phone. Bottom line...spend the time researching what you need to do to get where you want to be. Good luck out there.

Madcat8686 said:
You are definitely in the right sight but you need to read through the directions and understand what they mean. It's important that you know just what S-Off and Super CID mean to the phone before you try these procedures out. Taking a test drive without getting ALL the steps (and there are more) in order and correct CAN and WILL brick your phone. Bottom line...spend the time researching what you need to do to get where you want to be. Good luck out there.
Click to expand...
Click to collapse
Yeah I can see this site is a wealth of information.
A lot of brilliant people here!
timmaaa said:
Ok, I wouldn't suggest going to any site for info other than XDA, you could end up with incorrect information as other sites don't properly distinguish between models. Long story short, stay on XDA and specifically within this forum.
You can get SuperCID using hex edit method. Then you can get s-off using Facepalm S-off.
Sent from my Evita
Click to expand...
Click to collapse
thanks a million!
you sir are a true gentleman.
I followed the SuperCID instructions and everything seemed to work perfectly.
Now when I type: fastboot oem readcid in fastboot I get: (bootloader) cid: 11111111
which is great, but I also have an app called CID Getter (with a cupcake icon), and that app is telling me that my CID is [ROGER001].
Before I go any further, I need your help!
what does it mean?
I rebooted in fastboot again and fastboot oem readcid command still gives me 11111111

CID Getter doesn't display the correct CID, I'm not sure where it pulls it from but it's incorrect. The 11111111 you get from the fastboot command is your true CID so you can go ahead and proceed with s-off.
Sent from my Evita

Hi i am pretty new to the forums but have been flashing roms for awhile. I have super cid and s-off and recently upgraded to 2.15 after I was having a lot of random reboots/boot loops/no signal on CM10.2, CarbonJB, Beanstalk. I could only get my phone to boot with the 2.14 hboot when i flashed KickDroid but there were still no signal problems and some random reboots.
This seems to be fixed with the 2.15 hboot but I've been wanting to return to a pure android rom for awhile. I hear 2.15 does not work with any non-sense roms and indeed when i tried to flash CM10.2 again it would bootloop. I have heard however, in random threads throughout the forums that i could possibly use 2.15 hboot along with the Beastmode kernel to run Beanstalk.
Does anybody who is more knowledgeable than me at these things know which roms are now compatible with the 2.15 update?

Hailfire said:
Hi i am pretty new to the forums but have been flashing roms for awhile. I have super cid and s-off and recently upgraded to 2.15 after I was having a lot of random reboots/boot loops/no signal on CM10.2, CarbonJB, Beanstalk. I could only get my phone to boot with the 2.14 hboot when i flashed KickDroid but there were still no signal problems and some random reboots.
This seems to be fixed with the 2.15 hboot but I've been wanting to return to a pure android rom for awhile. I hear 2.15 does not work with any non-sense roms and indeed when i tried to flash CM10.2 again it would bootloop. I have heard however, in random threads throughout the forums that i could possibly use 2.15 hboot along with the Beastmode kernel to run Beanstalk.
Does anybody who is more knowledgeable than me at these things know which roms are now compatible with the 2.15 update?
Click to expand...
Click to collapse
AOSP-wise, I'm pretty sure CFX is 2.15 compatible
Sent from my HTC One XL using XDA Premium 4 mobile app

CM10.2 is definitely compatible with the 2.15 firmware package, the bootloop was likely caused by the current bugs with the ROM itself.
Sent from my Evita

timmaaa said:
CM10.2 is definitely compatible with the 2.15 firmware package, the bootloop was likely caused by the current bugs with the ROM itself.
Sent from my Evita
Click to expand...
Click to collapse
4.3 just wasn't a good run for aosp
Sent from my HTC One XL using XDA Premium 4 mobile app

Help i killed my Phone:D

I was on Maximus HD 10.0
Then i tried another rom. but i don't like, so i downloaded 10.2 latest nightly but it on my internal storage-->full wipe-->and then i can't install cm10.2 then i want to but another rom on my internal storage but i can't put anything on the phone without an running rom...
then i changed my recovery to CWM 6. cause i knower there was an option to mount usb storage, but it don't work nothings happened when i click on it. Pleas help me i can do nothing
Some more Infos:C:\test>fastboot getvar all
version: 0.5
version-bootloader: 2.16.0000
version-baseband: 1.20.50.05.16
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-OFF
serialno: *************
imei: **************
product: vle
platform: HBOOT-8960
modelid: PJ4010000
cidnum: 11111111
battery-status: good
battery-voltage: 4128mV
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-4958290506
hbootpreupdate: 11
gencheckpt: 0
all: Done!
finished. total time: 0.078s

Jojo1992 said:
I was on Maximus HD 10.0
Then i tried another rom. but i don't like, so i downloaded 10.2 latest nightly but it on my internal storage-->full wipe-->and then i can't install cm10.2 then i want to but another rom on my internal storage but i can't put anything on the phone without an running rom...
then i changed my recovery to CWM 6. cause i knower there was an option to mount usb storage, but it don't work nothings happened when i click on it. Pleas help me i can do nothing
Some more Infos:C:\test>fastboot getvar all
version: 0.5
version-bootloader: 2.16.0000
version-baseband: 1.20.50.05.16
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-OFF
serialno: SH26RW404047
imei: 359901049107937
product: vle
platform: HBOOT-8960
modelid: PJ4010000
cidnum: 11111111
battery-status: good
battery-voltage: 4128mV
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-4958290506
hbootpreupdate: 11
gencheckpt: 0
all: Done!
finished. total time: 0.078s
Click to expand...
Click to collapse
I hope this Infos can help to solve my Problem, i have access via Fastboot!
The best would be if i can go back to stock.

Jojo1992 said:
I hope this Infos can help to solve my Problem, i have access via Fastboot!
The best would be if i can go back to stock.
Click to expand...
Click to collapse
You need the old firmware like you had before you updated to Maximus.
Run a RUU.exe and clear storage/factory reset in bootloader when you have the stock recovery back on.
From your other thread I posted more details
http://forum.xda-developers.com/showpost.php?p=47586067&postcount=7

tivofool said:
You need the old firmware like you had before you updated to Maximus.
Run a RUU.exe and clear storage/factory reset in bootloader when you have the stock recovery back on.
From your other thread I posted more details
http://forum.xda-developers.com/showpost.php?p=47586067&postcount=7
Click to expand...
Click to collapse
i downloaded an RUU:
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
then i make this:
fastboot devices
fastboot oem lock
then start RUU, but error no connection to device but in cmd i get a connection

I have a CID 111111 is that the Problem?

Jojo1992 said:
I have a CID 111111 is that the Problem?
Click to expand...
Click to collapse
I've never changed my CID, no need to. So I'm not an expert.
But from what I have read here:
"You can use any ruu while s-OFF, just simply plug phone to computer and run ruu. No need to relock bootloader.
For the supercid, it is recommended to change it back to original with fastboot command.
Fastboot oem write cid xxxxxxxx.
There has been a few bricks takin Jb ota while still supercid. "
So, not a problem, unless you install a OTA (over the air) update while SuperCid.
Here's a good guide from another forum
http://androidforums.com/one-s-all-things-root/691874-guide-how-run-ruu-your-htc-one-s.html
Glancing at that, I noticed it recommends running the RUU on the PC as administrator, maybe it's something simple like that.

tivofool said:
I've never changed my CID, no need to. So I'm not an expert.
But from what I have read here:
"You can use any ruu while s-OFF, just simply plug phone to computer and run ruu. No need to relock bootloader.
For the supercid, it is recommended to change it back to original with fastboot command.
Fastboot oem write cid xxxxxxxx.
There has been a few bricks takin Jb ota while still supercid. "
So, not a problem, unless you install a OTA (over the air) update while SuperCid.
Here's a good guide from another forum
http://androidforums.com/one-s-all-things-root/691874-guide-how-run-ruu-your-htc-one-s.html
Glancing at that, I noticed it recommends running the RUU on the PC as administrator, maybe it's something simple like that.
Click to expand...
Click to collapse
I changed my CID back to HTC__102
and tried zwo different RUU.exe one ICS on JB but both have an error...
i relocked my boot loader how can i unlock again?

Jojo1992 said:
I changed my CID back to HTC__102
and tried zwo different RUU.exe one ICS on JB but both have an error...
i relocked my boot loader how can i unlock again?
Click to expand...
Click to collapse
When trying the RUU did you go to bootloader (fastboot USB)?
To Unlock
Locate your Unlock_code.bin on your pc, probably saved it somewhere or it is still in your fastboot folder.
Type this into your command prompt window fastboot flash unlocktoken Unlock_code.bin
or go through the process of getting a new one http://forum.xda-developers.com/showthread.php?t=1583427
Nice tool (Windroid)
http://forum.xda-developers.com/showthread.php?t=2471151

tivofool said:
When trying the RUU did you go to bootloader (fastboot USB)?
To Unlock
Locate your Unlock_code.bin on your pc, probably saved it somewhere or it is still in your fastboot folder.
Type this into your command prompt window fastboot flash unlocktoken Unlock_code.bin
or go through the process of getting a new one http://forum.xda-developers.com/showthread.php?t=1583427
Nice tool (Windroid)
http://forum.xda-developers.com/showthread.php?t=2471151
Click to expand...
Click to collapse
Yes I was in fast boot USB
I will try it one time again and when it don't work then unlock again

Jojo1992 said:
Yes I was in fast boot USB
I will try it one time again and when it don't work then unlock again
Click to expand...
Click to collapse
Oh yeah, I've also read from someone that they got error 155 then they flashed stock recovery and relocked bootloader and then RUU proceeded to work.

tivofool said:
Oh yeah, I've also read from someone that they got error 155 then they flashed stock recovery and relocked bootloader and then RUU proceeded to work.
Click to expand...
Click to collapse
I unlocked and now i could flash:
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
that worked for me.
So which is the latest CM what i could install now?
Hboot: 1.14.0002
UNLOCKED
S-OFF
Running:
Android 4.0.4 HTC Sense4.1 Softwarenumber:2.31.401.5

Jojo1992 said:
I unlocked and now i could flash:
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
that worked for me.
So which is the latest CM what i could install now?
Hboot: 1.14.0002
UNLOCKED
S-OFF
Running:
Android 4.0.4 HTC Sense4.1 Softwarenumber:2.31.401.5
Click to expand...
Click to collapse
Glad you were able to get the RUU working. But right now you won't be able to flash many ROMs with that low of a Hboot. You will need to update the firmware.
Since you put your CID back, you would have to put back stock recovery and relock bootloader. Then you could go through settings and do the OTA to update to 2.15 hboot.
Or...this firmware update thread
http://forum.xda-developers.com/showthread.php?t=2322755

tivofool said:
Glad you were able to get the RUU working. But right now you won't be able to flash many ROMs with that low of a Hboot. You will need to update the firmware.
Since you put your CID back, you would have to put back stock recovery and relock bootloader. Then you could go through settings and do the OTA to update to 2.15 hboot.
Or...this firmware update thread
http://forum.xda-developers.com/showthread.php?t=2322755
Click to expand...
Click to collapse
where can i find stock recovery?
flash it like this or?: fastboot flash recovery recover.img
and relock bootloader with: fastboot oem lock ???

Jojo1992 said:
where can i find stock recovery?
flash it like this or?: fastboot flash recovery recover.img
and relock bootloader with: fastboot oem lock ???
Click to expand...
Click to collapse
There is a stock recovery here
http://www.modaco.com/topic/353006-...ch-recovery-for-the-htc-one-s-stock-download/
The SECOND download is the stock one
Unless you change the name of the recovery the command will probably look more like this:
fastboot flash recovery ville_recovery_signed.img
And yes
fastboot oem lock
after you have flashed the stock recovery of course

tivofool said:
Since you put your CID back, you would have to put back stock recovery and relock bootloader. Then you could go through settings and do the OTA to update to 2.15 hboot.
[/url]
Click to expand...
Click to collapse
Or he could just change cid to HTC__001 and flash jb ruu. (The European version)
Sent from HTC One S using android 4.2.2 sense 5

tominozh said:
Or he could just change cid to HTC__001 and flash jb ruu. (The European version)
Sent from HTC One S using android 4.2.2 sense 5
Click to expand...
Click to collapse
That don't work
I tried:
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
I will try it over ota now --> my Handy ist loading the update 4.1.1 i will report as soon as it is ready
Ok edit:
Hboot 2.15.0000
Unlocked
can i now flash CM10.2?
O.T.: Is CM10.2 running stable?

Jojo1992 said:
That don't work
I tried:
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
I will try it over ota now --> my Handy ist loading the update 4.1.1 i will report as soon as it is ready
Ok edit:
Hboot 2.15.0000
Unlocked
can i now flash CM10.2?
O.T.: Is CM10.2 running stable?
Click to expand...
Click to collapse
Eh.. It is stable besides for some bootlooping. Like you start it up and it bootloops a few times before finally loading. I like the Avatar Rom which is CM 10.2 based, and noticed a little bootlooping. But it wasn't terrible, just something that happened a few times.
So if that doesn't bother you, go for it. Other than that you would need to stick with sense based roms for stability.
Gosh, so many to choose from you will have to try some out.
http://forum.xda-developers.com/showthread.php?t=2243895

tivofool said:
Eh.. It is stable besides for some bootlooping. Like you start it up and it bootloops a few times before finally loading. I like the Avatar Rom which is CM 10.2 based, and noticed a little bootlooping. But it wasn't terrible, just something that happened a few times.
So if that doesn't bother you, go for it. Other than that you would need to stick with sense based roms for stability.
Gosh, so many to choose from you will have to try some out.
http://forum.xda-developers.com/showthread.php?t=2243895
Click to expand...
Click to collapse
Is the Avatar Rom really 10.2 based? cause on their page they tell 10.1 based or?
but i can install now any rom or?
with the flashed rue which i have actually i don't get mobile internet working. just wlan

Jojo1992 said:
Is the Avatar Rom really 10.2 based? cause on their page they tell 10.1 based or?
but i can install now any rom or?
with the flashed rue which i have actually i don't get mobile internet working. just wlan
Click to expand...
Click to collapse
Ya, guess you are right, 10.1
You can flash any as long as they don't require hboot 2.16 (which they state in the first page OP)

tivofool said:
Ya, guess you are right, 10.1
You can flash any as long as they don't require hboot 2.16 (which they state in the first page OP)
Click to expand...
Click to collapse
ok thank you very much for the help!