Database Info

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] loading kernel with hboot 1.14, firmware?

okay i have several questions, so please bear with me. I just can't find the answers to these, and i've been looking for days.
coming from stock android 2.20 firmware. i followed zedomax (on youtube) tutorial and unlocked the bootloader, installed the ViperX ROM (having to use fastboot boot.img, a process i still don't really understand, I thought the recovery was supposed to be able to load ROMs, apparently this is an issue with my version of hboot?), then installed goomanager and updated TWRP. Followed the instructions, have S-OFF. Made a recovery, used Titanium Backup.
However, i still had random reboots, drained battery overnight, and poor/dropped phone signal all the time. Reading in the ViperX thread it seems like people with my issues need to install a kernel (apparently with my firmware i need the beastmode?) and maybe a radio (or is radio and firmware combined, because several people seemed to say that and there's a folder about radio stuff in the kernel zip?) to fix these issues, however there are no installation instructions that i can find in the beastmode release thread and when i found the zip, put it on my internal storage, and tried to load it in TWRP, got the same error message as when i try to load a ROM that way. So it's an issue with hboot 1.14, which is an issue with my firmware (2.20?) And i've spent half the night trying to figure out which firmware i need to fix that, if it can be done. Can i fix my issue so i no longer need fastboot to load a ROM or kernel, and can do it directly from recovery?
sorry for a long rant. i'd love some help. i know there are some 'tools' that are supposed to get around this stuff but i'm trying to genuinely learn what it is i'm doing.

You should have no trouble flashing the Beastmode kernel regardless of your hboot because you're s-off. Which version of the kernel are you flashing? What is the filename? Are you absolutely sure you're s-off?
The recovery does load ROMs and kernels, but there is a restriction in place on hboots equal to or greater than 1.14 which doesn't allow the boot.img to be flashed through recovery. Hence the need to flash it via fastboot. This is only true for s-on devices though, s-off devices circumvent security checks and therefore allow the boot.img to be flashed during the recovery install.
Sent from my Evita

Signal drop and random reboots can either be solved by installing Beastmode kernel or updating to the 2.15 "firmware". Its typically not necessary to do both.
The term "firmware" is a bit confusing. But for the purposes of solving the signal drop and reboot issues on Sense 5 ROMs, the 2.15 firmware being referred to is not the ROM itself, but other modules that came packed with the Sense 5 OTA. The 2.15 "firmware" consists of radio, hboot, boot.img, as well as WiFi and media modules.
The file needed to updated to 2.15 firmware and instruction are included in the top post of Turge's stock ROM thread (SuperCID and S-off required): http://forum.xda-developers.com/showthread.php?t=2423735

timmaaa said:
You should have no trouble flashing the Beastmode kernel regardless of your hboot because you're s-off. Which version of the kernel are you flashing? What is the filename? Are you absolutely sure you're s-off?
The recovery does load ROMs and kernels, but there is a restriction in place on hboots equal to or greater than 1.14 which doesn't allow the boot.img to be flashed through recovery. Hence the need to flash it via fastboot. This is only true for s-on devices though, s-off devices circumvent security checks and therefore allow the boot.img to be flashed during the recovery install.
Sent from my Evita
Click to expand...
Click to collapse
Oh wow that was fast guys, I really appreciate the help.
I wish i could take a screenshot of the bootloader but it says plain as day to me :
*** TAMPERED ***
*** UNLOCKED ***
EVITA PVT SHIP S-OFF RL
CID-111111111
HBOOT-1.14.0002
RADIO-0.19as.32.09.11_2
OpenDSP-v29.1.0.45.0622
eMMC-boot
Jun 11 2012,14:36:28
I know there's a way to get phone info in cmd but i don't remember what the command is but if you tell me i'll get it for you
file name for the kernel (as far as i know, that thread was messy to me, i felt like most of it was way over my head and that made me nervous to use it) :
Beastmode_RELOADED_3.5.zip 13.0 MB

redpoint73 said:
Signal drop and random reboots can either be solved by installing Beastmode kernel or updating to the 2.15 "firmware". Its typically not necessary to do both.
The term "firmware" is a bit confusing. But for the purposes of solving the signal drop and reboot issues on Sense 5 ROMs, the 2.15 firmware being referred to is not the ROM itself, but other modules that came packed with the Sense 5 OTA. The 2.15 "firmware" consists of radio, hboot, boot.img, as well as WiFi and media modules.
The file needed to updated to 2.15 firmware and instruction are included in the top post of Turge's stock ROM thread (SuperCID and S-off required): http://forum.xda-developers.com/showthread.php?t=2423735
Click to expand...
Click to collapse
thank you for the info! I remember finding a link to that thread and being reluctant to install it because he didn't really label what it was, and the more i read about firmware/radio signals/kernals the more it seemed you you needed to be CERTAIN what you're doing before doing it. Will installing that firmware in the first post overwrite my Viper ROM and necessitate some kind of reinstallation or will i be good to go after that?

self.hating.att.slave said:
Will installing that firmware in the first post overwrite my Viper ROM and necessitate some kind of reinstallation or will i be good to go after that?
Click to expand...
Click to collapse
ROM will be untouched. It just install the modules I mentioned. But always backup your personal data and current ROM when flashing anything.
boot.img will be overwritten. But as you are so far unable to install the Beastmode kernel, it should just be the same kernel as ViperXL, anyway.

(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: HT245W302569
(bootloader) imei: 359691041642243
(bootloader) product: evita
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ8310000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4170mV
(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
all: Done!
Looks like it worked. It sounds like I should be cautiously optimistic at this point, but thanks again for your help.

I'm confident that it has worked, your hboot and radio are both updated.
Sent from my Evita

timmaaa said:
I'm confident that it has worked, your hboot and radio are both updated.
Sent from my Evita
Click to expand...
Click to collapse
Yeah, what I was referring to was the reception and battery/rebooting issues, and so far i haven't had a single one. Battery life is phenomenal, better than it ever was on stock Sense, and I'm really glad I did this. What a great rom. Thanks for your help again guys!

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

[Q] How do I remove S-On, Super CID, unroot and get completely back to stock

My phone has been having audio issues and I've ruled out everything on the software side.
Going to send it to HTC but I need to get back to stock obviously. Is there a specific order I should do these in? How does one get back to s-on? I assume removing super cid would be just like getting it only change the cid to HTC_001 or whatever, right?
How do I unroot?
And then of course I need to relock the bootloader, which if I'm not mistaken is as simple as running fastboot oem lock, right?
I basically need a step by step guide. I've searched around but haven't found everything exactly as I need it. Perhaps this could become a useful thread for others, with everything in one place.
Any help would be great, thanks in advance.

DRUMROT said:
My phone has been having audio issues and I've ruled out everything on the software side.
Going to send it to HTC but I need to get back to stock obviously. Is there a specific order I should do these in? How does one get back to s-on? I assume removing super cid would be just like getting it only change the cid to HTC_001 or whatever, right?
How do I unroot?
And then of course I need to relock the bootloader, which if I'm not mistaken is as simple as running fastboot oem lock, right?
I basically need a step by step guide. I've searched around but haven't found everything exactly as I need it. Perhaps this could become a useful thread for others, with everything in one place.
Any help would be great, thanks in advance.
Click to expand...
Click to collapse
IIRC the RUU for your device reverts all of that. Not 100% sure about the S-ON though.

I've read somewhere in another guild that it's necessary to first Relock your bootloader (using the oem lock command) and afterwards use the right RUU for your device...
I thought this could be helpful

Thanks for the tips.
Since I'm super cid, I can flash any RUU at this point. Any idea if locking my bootloader first will cause this to not be the case?

DRUMROT said:
Thanks for the tips.
Since I'm super cid, I can flash any RUU at this point. Any idea if locking my bootloader it first will cause this to not be the case?
Click to expand...
Click to collapse
I think to get S-OFF you have to use for example the All-in-one toolkit, I don't think relocking your bootloader will cause a S-on... But I think others may have more info about that. Planning on running an RUU for the first time myself

FantasyGamer said:
I think to get S-OFF you have to use for example the All-in-one toolkit, I don't think relocking your bootloader will cause a S-on... But I think others may have more info about that. Planning on running an RUU for the first time myself
Click to expand...
Click to collapse
Yeah, I'm assuming I'd have to do some more then just run the RUU.
I'd gladly give it a go but like I posted earlier, I'd like to know if there is a certain order to do this in. If I run the RUU before removing s-off, will that make things easier? Harder? No different?
Anyone?

Personally, I think it's easier to first run the RUU and then go back to S-ON, because while you're S-OFF you won't have problems with the RUU for your CID, and the All-in-one kit says that you need to run stock Rom and stock recovery before you can S-OFF. So actually, I don't think it's recommended first going S-ON and then running an RUU.

FantasyGamer said:
Personally, I think it's easier to first run the RUU and then go back to S-ON, because while you're S-OFF you won't have problems with the RUU for your CID, and the All-in-one kit says that you need to run stock Rom and stock recovery before you can S-OFF. So actually, I don't think it's recommended first going S-ON and then running an RUU.
Click to expand...
Click to collapse
Hmmm, all right. I've never used the all-in-one kit but I've noticed it has a "back to s-on" function so I'll give it a try. I'm on Linux so I need to run it in Wine (Windows emulator) so hopefully there's no hiccups.

DRUMROT said:
My phone has been having audio issues and I've ruled out everything on the software side.
Going to send it to HTC but I need to get back to stock obviously. Is there a specific order I should do these in? How does one get back to s-on? I assume removing super cid would be just like getting it only change the cid to HTC_001 or whatever, right?
How do I unroot?
And then of course I need to relock the bootloader, which if I'm not mistaken is as simple as running fastboot oem lock, right?
I basically need a step by step guide. I've searched around but haven't found everything exactly as I need it. Perhaps this could become a useful thread for others, with everything in one place.
Any help would be great, thanks in advance.
Click to expand...
Click to collapse
1)If you have put on a modified HBoot (such as to remove tampered or red warning) return to stock.
(only added this because if you S-on with modified HBoot it will brick your phone)
2)Run RUU.exe
3)Reset lock status flag
http://forum.xda-developers.com/showthread.php?t=2155955
4)S-ON your phone
http://androidforums.com/one-s-all-...-get-back-stock-moonshine-facepalm-s-off.html
---------- Post added at 01:15 PM ---------- Previous post was at 01:05 PM ----------
Edited that, If anyone notices a problem please post.

So, little question for myself.
Do I need to first Relock my bootloader?
Or can I just go and run an RUU? (I'm S-OFF)

FantasyGamer said:
So, little question for myself.
Do I need to first Relock my bootloader?
Or can I just go and run an RUU? (I'm S-OFF)
Click to expand...
Click to collapse
No, it doesn't need to be locked when S-OFF.
The most important is running the RUU that matches your CID. (since you are s-off it is easy to change the CID to whatever you want, and thus run whatever RUU you want)

i have bought a used htc one s and it had sense 5.5 based JB4.2.2 rom but i want to downgrade to stock firmware. kindly tell me which RUU i should use and how should i procede.
HBOOT shows tampered, unlocked and S-ON
and here is other details
Code:
sudo fastboot getvar all
[sudo] password for hasan:
(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: SH267W
(bootloader) imei: 35990
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4010000
(bootloader) cidnum: VODAP304
(bootloader) battery-status: good
(bootloader) battery-voltage: 4111mV
(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!
finished. total time: 0.061s
I tried RUU 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 on windows 8.1 64bit but it is not detecting the phone at all
currently I am on linux so i hope you guys can suggest something relevant
thanks a lot

rejects going to stock !

ok here's the thing..
i lost my backup for the stock rom which came with my HTC One XL,and i've been facing alot of issues with custom roms ,the major thing was the capacitive buttons stopped working without a reason !
now being S-ON,unable to go back to stock except with RUU's with the matching CID,,ok so i tried searching for the right RUU with matching CID which is J15 and the only one i found on androidRUU website didnt work for me as its a different hboot version (not sure if that's why it refused or not but thats what i understood from reading in the forums)
so i spent hours and hours trying to find the correct RUU with matching CID and hboot version but was invain,,
another option searching for NANDROID,,still didnt find any matching results
tried getting SuperCID to make it easier to find a matching RUU,,but i found in order to get SuperCID i need to be S-OFF,,and in order to get S-OFF i need to get SuperCID first...its a bit frustrating i know
also another weird thing that when i tried to relock the bootloader,it says "FAILED (status read failed (Too many links))"
so any help on how to either :
1.Full stock restore either with a matching RUU or NANDROID
2.Getting a full stock rom with the latest firmware update so that hopefully the capacitive buttons work again..
would be really appreciated
and here are my info :
version: 0.5
version-bootloader: 2.10.0000
version-baseband: 3.12.38.00.24
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
product: evita_utl
platform: HBOOT-8960
modelid: PJ8350000
cidnum: HTC__J15
battery-status: good
battery-voltage: 3848mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-b27b8968
hbootpreupdate: 11
gencheckpt: 0

lordofegypt said:
ok here's the thing..
i lost my backup for the stock rom which came with my HTC One XL,and i've been facing alot of issues with custom roms ,the major thing was the capacitive buttons stopped working without a reason !
now being S-ON,unable to go back to stock except with RUU's with the matching CID,,ok so i tried searching for the right RUU with matching CID which is J15 and the only one i found on androidRUU website didnt work for me as its a different hboot version (not sure if that's why it refused or not but thats what i understood from reading in the forums)
so i spent hours and hours trying to find the correct RUU with matching CID and hboot version but was invain,,
another option searching for NANDROID,,still didnt find any matching results
tried getting SuperCID to make it easier to find a matching RUU,,but i found in order to get SuperCID i need to be S-OFF,,and in order to get S-OFF i need to get SuperCID first...its a bit frustrating i know
also another weird thing that when i tried to relock the bootloader,it says "FAILED (status read failed (Too many links))"
so any help on how to either :
1.Full stock restore either with a matching RUU or NANDROID
2.Getting a full stock rom with the latest firmware update so that hopefully the capacitive buttons work again..
would be really appreciated
and here are my info :
version: 0.5
version-bootloader: 2.10.0000
version-baseband: 3.12.38.00.24
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
serialno: HT2CNW302531
imei: 354370050060697
product: evita_utl
platform: HBOOT-8960
modelid: PJ8350000
cidnum: HTC__J15
battery-status: good
battery-voltage: 3848mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-b27b8968
hbootpreupdate: 11
gencheckpt: 0
Click to expand...
Click to collapse
Long story short, there is no RUU for your CID. But there is a thread in our General Section that contains stock backups for your device.
I'll also just clear up some confusion you seem to have about s-off and SuperCID. There are two s-off methods for the Evita, Facepalm and Rumrunner. Facepalm requires SuperCID to work, Rumrunner does not require SuperCID to work. If you don't have SuperCID and want it you can use the Rumrunner s-off method to get s-off and then change your CID using a fastboot command.
Either way, don't use any of the RUUs that match other CIDs, they'll most likely brick your phone. Just find the thread in General and you'll be able to download a nandroid backup.
Sent from my Evita

timmaaa said:
Long story short, there is no RUU for your CID. But there is a thread in our General Section that contains stock backups for your device.
I'll also just clear up some confusion you seem to have about s-off and SuperCID. There are two s-off methods for the Evita, Facepalm and Rumrunner. Facepalm requires SuperCID to work, Rumrunner does not require SuperCID to work. If you don't have SuperCID and want it you can use the Rumrunner s-off method to get s-off and then change your CID using a fastboot command.
Either way, don't use any of the RUUs that match other CIDs, they'll most likely brick your phone. Just find the thread in General and you'll be able to download a nandroid backup.
Sent from my Evita
Click to expand...
Click to collapse
and concerning that backup you're talking about,,does it have to be matching my CID or any of my details ? or just any backup is fine ?

The backup I'm talking about is specifically for the middle eastern variant of this phone.
Sent from my Evita

timmaaa said:
The backup I'm talking about is specifically for the middle eastern variant of this phone.
Sent from my Evita
Click to expand...
Click to collapse
thx for the help,,ok so currently i found the needed NANDROID,,made the restore and am back to stock android 4.1.1 with relocked bootloader and stock recovery flashed,,i tried searching for software updates and it says no updates found when my neighbor got the same device and he recieved an update for 4.2.2 ??
however am not quite sure if the stock recovery flashed successfully or not ,,in the fastboot it said that the flashing was successful but when i tried to access the recovery from the boot it just went blank screen ,,is that ok and am not supposed to enter the stock recovery but then why it doesnt make the update ? or there's something wrong with the recovery i got ?

You should be able to enter the stock recovery, I believe there's something wrong with the recovery you flashed.
Sent from my Evita

ngiyal 457
timmaaa said:
You should be able to enter the stock recovery, I believe there's something wrong with the recovery you flashed.
Sent from my Evita
Click to expand...
Click to collapse
ok i found the recovery ,flashed it and able to access the recovery nw,,but in order to do so i had to unlock the bootloader again other wise it will just keep on booting into the bootmode which is kinda wierd...
anyway you got any ideas why am unable to receive the OTA ?

I'm not sure why you're not receiving it, sorry. If you can find the OTA you can install it manually.
Sent from my Evita

timmaaa said:
I'm not sure why you're not receiving it, sorry. If you can find the OTA you can install it manually.
Sent from my Evita
Click to expand...
Click to collapse
surprisingly i just got an update for the "people" app through searching for software updates (not through playstore)...does that mean that my OTA is working fine and its just a delay or something like that for the full software,,or this app update has nothing to do with the OTA's ?

The people app itself is separate from the OTA.
Sent from my Evita

j15 version of evite doesn't recieve 4.2.2 update yet
i have the same of your phone and i flashed stock ROM of telstra and it works fine for me

madoooz said:
j15 version of evite doesn't recieve 4.2.2 update yet
i have the same of your phone and i flashed stock ROM of telstra and it works fine for me
Click to expand...
Click to collapse
Could I ask where you got that stock Rom and for a link as well. With a bit of help from lag I managed to factory reset and lose my backup just before I was going to get in on my pc, imagine my excitement. So this would be greatly appreciated.
Thank You

jnthnbgg said:
Could I ask where you got that stock Rom and for a link as well. With a bit of help from lag I managed to factory reset and lose my backup just before I was going to get in on my pc, imagine my excitement. So this would be greatly appreciated.
Thank You
Click to expand...
Click to collapse
Just have a look in our Android Development section, you'll find it in there, along with some great custom ROMs you might want to try.
Sent from my Evita

jnthnbgg said:
Could I ask where you got that stock Rom and for a link as well.
Click to expand...
Click to collapse
All the links you will likely ever need are here:
http://forum.xda-developers.com/showthread.php?t=1671237
jnthnbgg said:
With a bit of help from lag I managed to factory reset and lose my backup just before I was going to get in on my pc, imagine my excitement.
Click to expand...
Click to collapse
Did you factory reset in hboot and corrupt the SD? Because a factory reset in recovery or in the OS should not wipe the SD (including nandroids).

redpoint73 said:
All the links you will likely ever need are here:
http://forum.xda-developers.com/showthread.php?t=1671237
Did you factory reset in hboot and corrupt the SD? Because a factory reset in recovery or in the OS should not wipe the SD (including nandroids).
Click to expand...
Click to collapse
Yes it did it in Hboot of all things while I had Clean Rom installed which was giving me grief (blackscreen after HTC load screen)

jnthnbgg said:
Yes it did it in Hboot of all things while I had Clean Rom installed which was giving me grief (blackscreen after HTC load screen)
Click to expand...
Click to collapse
What are your bootloader details? I might be able to diagnose why you were having problems before the factory reset.
Sent from my Evita

timmaaa said:
What are your bootloader details? I might be able to diagnose why you were having problems before the factory reset.
Sent from my Evita
Click to expand...
Click to collapse
Well I know it is the S-On as I saw even though I was doing all according to the instructions I could find. I had Unlock, SU CID, just could not get that S-OFF. I tried it manually, via the toolkits people have out there, using a 2.0 USB cable. But without the S-OFF I did not get the firmware installed so that was my source of headache with that I just had a bit of lag in the bootloader screen and i click one to many times past recovery and viola up the crick without a canoe lol

Once you have a ROM installed, forget the toolkits and get s-off manually, it's really easy. There are two methods you can try:
Facepalm S-off
Rumrunner S-off
Sent from my Evita

timmaaa said:
Once you have a ROM installed, forget the toolkits and get s-off manually, it's really easy. There are two methods you can try:
Facepalm S-off
Rumrunner S-off
Sent from my Evita
Click to expand...
Click to collapse
So going the route of Palm as I can not get adb to connect but I can fastboot USB, The first attempt ends with FAILED remote:92 supercid! please flush image again immediately. The second attempt ends in FAILED remote:99 unknow fail

You're gonna need to get adb working, both methods require it. I'm in a good mood so I'm gonna give you the solution to the error 99 problem, but please in future search properly before posting, the solution to that problem has been posted dozens of times in the Facepalm thread.
When you get error 99 after flashing the zip, you need to force a reboot to the bootloader and start the process again and you should get error 92 again.
Why isn't adb working? What ROM are you on? Have you updated your drivers? Do you have usb debugging turned on in Developer Options?
Sent from my Evita