[Q] Help with SuperCID/unlocked but unable to s-off - AT&T, Rogers HTC One X, Telstra One XL

So I have finally decided to root my AT&T HOX and want to flash custom rom, and I am running into a little bit of problem hoping someone could help me out. I have researched maybe a hundred pages/threads and I thought I was ready, until I run into problem and realized there are still many situations that I could get into.
So here is what I did:
- I was originally on ATT 2.20.
1. Download and followed the X-Factor root exploit instruction, changed CID successfully, got the unlock token and successfully unlocked bootloader. (At this point, I 'remember' seeing I had S-OFF without doing any additional step)
2. Flashed recovery with TWRP 2.6.3.0.
3. Flashed CleanROM. Everything went smooth. But after half day of using, it started random reboot.
4. So I did some release on the CleanROM thread, and seeing people mentioned flashing the firmware from Turge would fix the random reboot problem. So I downloaded the firmware and I 'think' here are the steps I have done:
- fastboot oem lock
- fastboot oem rebootRUU
- fastboot flash zip <Turge firmware>
5. Here comes the problem, while flashing zip, I first got error about "remote: not allowed", then I tried it again and got "remote: 12 signature verify fail". Then it's the same error from that time on.
6. So I gave up, thinking to backout of RUU mode and research for another solution, but I couldn't get back to normal system boot, it always boot to bootloader, and now I start to notice it says "Tampered" and "S-On".
7. So I flash my unlocktoken again, now I got back to my system (CleanROM). But it still shows S-ON and Tampered.
8. Wanting to get S-OFF and not Tampered, so I tried to run the ATT RUU of 2.20, it failed many times without much useful error, (mostly unknown error), somehow I was finally able to get it flashed after I issued a "fastboot oem lock". Now I am back on ATT's 2.20 rom with SuperCID and no more Tampering but "RELOCKED".
9. Run X-Factor root exploit again hopping to get S-OFF again, but no luck, instead, it's now "UNLOCKED" and "Tampered" again. but realized I still have supersu, so I am rooted, and my TWRP is still there.
10. Run "revone" script trying to get S-OFF, but I got error code 1. According to revone's guide, error code 1 means I am likely to never get S-OFF again on my phone.
I have also read that:
- Having SuperCID and S-ON would brick the phone when trying to do a upgrade RUU or OTA.
- If I have S-OFF and back to S-ON then I will never get S-OFF again.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.14.0002
(bootloader) version-baseband: 0.19as.32.09.11_2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.20.502.7
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT25XW301606
(bootloader) imei: 359691044520966
(bootloader) product: evita
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ8310000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4053mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 1a7fdca3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
So my question is... is it true that my phone is just as-is and can never get S-OFF again? If I really cannot do S-OFF again, then I guess it's my own fault for not preparing enough, but just really wish i can still flash custom rom. So if there is still a way, i would like to give it a try.
Another question is, if I cannot do S-OFF again, how do I avoid running into the problem of a possible ATT OTA and brick my phone with the superCID, cuz seems like I cannot change the CID back without S-OFF.
If this issue was discussed before, I apologize, It's just too many information and scenario on the web and it's just not possible to read though all millions of pages.
Thanks.

1. All good, except that process doesn't give you s-off, that's an entirely different process.
2. All good.
3. All good.
4. Nowhere in the firmware instructions does it say you need to relock your bootloader so I'm not sure why you did that. You need to follow instructions exactly and not deviate from them. You actually need to have an unlocked bootloader, root, SuperCID, and s-off for the firmware to flash.
5. See above.
6. It says tampered because you still have root via Cleanrom, the tampered flag is normal. It says s-on because you never went through the s-off process.
7. All good.
8. The RUU wasn't needed at all.
9. Unlocked and tampered are completely normal for a phone with an unlocked bootloader and root.
10. That revone method isn't even for our phone (that's why it failed) so I don't know why you even tried that. Trying software/firmware/exploits for another device is a great way to brick your phone. Yes SuperCID + s-on + jb RUU = brick. If you get s-off and revert to s-on you can still get s-off again.
Conclusion:
You need to do a lot more research, it seems you're confused about what you're doing. It's very important to have a firm grasp on what you're doing when modifying your device because a lack of understanding leads to bricks, and leads to not being able to recover from situations you get yourself into. You never had s-off, but you absolutely can get s-off on your phone as long as you follow the right method, the Facepalm method (which is the only s-off method for this device).
Sent from my Evita

Related

[Q] FAILED (remote: not allowed) need a little help

Hello!
Just got my hands on a desire S from someone who said they bricked it, i dont think it is though.
I can access fastboot/HBOOT but it doesnt seem to have a custom recovery installed, shows the stock recovery or download mode logo, the screen goes blank and vibrates 7 times.
Every time i try to flash anything through fastboot it gives me the error in the heading
FAILED (remote: not allowed)
The ROM just doesnt boot and shows T mobile logo indefinitely (must be a bootloop) but the phone doesnt have any Tmo logos on the body.
more details
SAGA PVT SHIP S-OFF RL
HBOOT-0.98.0002
RADIO-3805.06.02.03_M
eMMC-boot
I read about ENG S-off but i dont know what this phone has, maybe its just radio S-OFF cos its Tmo and doesnt have a recovery though i dont understand what the 7 vibrates mean either.
little help please?
even more details
(bootloader) version: 0.5
(bootloader) version-bootloader: 0.98.0002
(bootloader) version-baseband: 3805.06.02.03_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.47.110.3
(bootloader) serialno: HT15TTJ01262
(bootloader) imei: 356708041646975
(bootloader) product: saga
(bootloader) platform: HBOOT-7230
(bootloader) modelid: PG8810000
(bootloader) cidnum: T-MOB005
(bootloader) battery-status: good
(bootloader) battery-voltage: 3653mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 0e35ea5b
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0
7 vibrations most likely mean overheating, and this can't be cured by any means.
The phone is S-OFF, but doesn't have Engineering HBOOT - so you can't use fastboot, it won't allow you (just what it says).
Your best bet is to try a stock RUU and see if it helps.
Download a PG88IMG.zip from an eng hboot, copy it to root of sd (cardreader), boot to bootloader and let it do his job.
Afterwards delete the zip boot to bootloader once more and flash a recovery with fastboot.
I would use a ruu only if those steps fail.
Swyped because PC is under full load or to far away
Tectas said:
Download a PG88IMG.zip from an eng hboot, copy it to root of sd (cardreader), boot to bootloader and let it do his job.
Afterwards delete the zip boot to bootloader once more and flash a recovery with fastboot.
I would use a ruu only if those steps fail.
Swyped because PC is under full load or to far away
Click to expand...
Click to collapse
Hey Tectas I tried your method,
went here
http://forum.xda-developers.com/showthread.php?t=1178001
and got the first radio which had the same number as mine ie this one
From the 1.31.832.3 RUU:
20.28d.30.0805U_3805.04.02.01
says cid incorrect.
shall i try all the ones with 3805 in them? cos i really have no clue which one is right for me considering i dunno which RUU is compatible with this phone
raheeljessa said:
Hey Tectas I tried your method,
went here
http://forum.xda-developers.com/showthread.php?t=1178001
and got the first radio which had the same number as mine ie this one
From the 1.31.832.3 RUU:
20.28d.30.0805U_3805.04.02.01
says cid incorrect.
shall i try all the ones with 3805 in them? cos i really have no clue which one is right for me considering i dunno which RUU is compatible with this phone
Click to expand...
Click to collapse
No, not radio, leave it untouched yet, the hboot is what you need
Check my signature, I personally would recommend this one
Swyped because PC is under full load or to far away
even for this PG88IMG.zip which is the 1mb hboot file it says cid incorrect update fail press power to reboot
Tectas said:
No, not radio, leave it untouched yet, the hboot is what you need
Check my signature, I personally would recommend this one
Swyped because PC is under full load or to far away
Click to expand...
Click to collapse
even for this PG88IMG.zip which is the 1mb hboot file it says cid incorrect update fail press power to reboot
Ok then try it with a ruu, sry that i took your time for nothing
Tectas said:
Ok then try it with a ruu, sry that i took your time for nothing
Click to expand...
Click to collapse
how do i do that? sorry i seem to know nothing
Do you know from which regions your phone is?
Try in fastboot : fastboot getvar all, and Google your main version then download the appropriate file from this link
http://forum.xda-developers.com/showthread.php?t=1002506
Once you are sure you have the right RUU, you might have to make a goldcard to get rid of the CID error
The whole point of having "right" RUU is to avoid this error - having RUU for his specific region gets rid of CID error message. Otherwise he just needs any RUU and goldcard.
Jack_R1 said:
The whole point of having "right" RUU is to avoid this error - having RUU for his specific region gets rid of CID error message. Otherwise he just needs any RUU and goldcard.
Click to expand...
Click to collapse
I have what seems to be the right RUU..
now when i try to install it, the RUU installer hangs and the phone also hangs.
I should reiterate that my phone DOES NOT BOOT into the rom, has what may be boot loop error. If i could access android i wouldnt be asking any of these questions as from in there all this is easy peasy!
i'm trying booting into Hboot and fastboot to install this. as far as i remember it doesnt work here so how else can i go about it?
once again, no custom recovery, no eng bootloader, no working android rom
Thanks to all of you who tried to help by the way
raheeljessa said:
I have what seems to be the right RUU..
now when i try to install it, the RUU installer hangs and the phone also hangs.
I should reiterate that my phone DOES NOT BOOT into the rom, has what may be boot loop error. If i could access android i wouldnt be asking any of these questions as from in there all this is easy peasy!
i'm trying booting into Hboot and fastboot to install this. as far as i remember it doesnt work here so how else can i go about it?
once again, no custom recovery, no eng bootloader, no working android rom
Thanks to all of you who tried to help by the way
Click to expand...
Click to collapse
3 possibilities:
1. Let the ruu run without attached device till the only option is to close the program, search in your temp folder for the rom.zip, copy it to another folder, close the program, copy it to sd and try to flash it the same way you did before with the hboot (rename the rom.zip to PG88IMG.zip before you flash it)
2. Do the same like at 1. but create a goldcard before
3. Do the same I described before with hboot, but create a goldcard before
Swyped because PC is under full load or to far away
If the RUU installer hangs - your chances aren't too good.
If it hangs on "rebooting to bootloader" - boot to FASTBOOT manually and start RUU while in fastboot mode.
If it hangs updating - chances are you're another case of faulty eMMC.
gave the phone to some guy in the market. says he'll take 5£ to open it and check it out and let me know whats wrong.
the RUU rom.zip file when renamed to pg88img.zip or whatever does work as its the only zip file it detects in hboot mode,
it starts the update, heats up like an angry mountain and then sucks its battery off..
thanks you guys for all the help. I'll update you on what was the actual problem when this guy tells me so you know what these symptoms are for in future
Have you tried using the gold card? As it has already been stated that it should get rid of the wrong cid issue.
Sent from my HTC Desire S using XDA

S-OFF, LOCKED, Can't root

I've bought a phone which has S-OFF, ***LOCKED***, which I'm trying to root. I've seen many guides, read them but they are all from the point you have S-ON. I've tried manual ADB install of CWM but that fails, permission denied.
Any advice before I brick it ? The phone seems to be in a quasi state...not sure how I progress.
C:\Android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.00.0002
(bootloader) version-baseband: 3822.10.08.04_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.10.401.8
(bootloader) product: saga
(bootloader) platform: HBOOT-7230
(bootloader) modelid: PG8810000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3963mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: ebd3df7d
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0
are you sure you are S-OFF? If so, you can try a pre-rooted rom.(Flash a recovery first)
http://forum.xda-developers.com/showthread.php?t=1183684
Have the same problem. It says ***Locked*** S-OFF. Don't know what to do. Before made RUU I have rooted my phone succesfully (one click root), but now can't do that in the same way. ;/
I wasn't sure if S-OFF was really off but everything I tried was failing. This was from a Win7 64 bit, I switch to Win7 32bit PC and SuperOneClick worked then!
I've got root, CWM recovery installed and all sorted so thank. Not sure why 64bit Windows 7 was causing a problem, nothing indicated it was but a 32 bit pc everything worked perfectly.
How you switch to windows 32bit?
Generally, when S-OFF, the only thing needed to be able to do just about anything - is to use a special PG88IMG.ZIP that includes latest reengineered bootloader and custom recovery.
I'm not sure if there is one in this forum, but it's easy to create.
Jack_R1 said:
Generally, when S-OFF, the only thing needed to be able to do just about anything - is to use a special PG88IMG.ZIP that includes latest reengineered bootloader and custom recovery.
I'm not sure if there is one in this forum, but it's easy to create.
Click to expand...
Click to collapse
Where could I get this? Or how it is called? Because I have no clue what I need to enter in google.
To begin with, search for PG88IMG.ZIP to understand, what it is and what it does.
You need to unlock the bootloader, the ***locked*** indicates its still locked. Use HTCDev or some other tool to unlock your bootloader. Not sure how S-off works for this phone, it might have just been re-locked, so try "fastboot oem unlock" i think is the command and it should unlock
Then you can flash a recovery image and then flash a zip file containing the su binary and app via recovery
Sent from my HTC One X using Tapatalk 2
Just flash a ROM from the INDEX
Do you have a custom recovery?
Swyped from my DesireS
stumpyz9 said:
You need to unlock the bootloader, the ***locked*** indicates its still locked. Use HTCDev or some other tool to unlock your bootloader. Not sure how S-off works for this phone, it might have just been re-locked, so try "fastboot oem unlock" i think is the command and it should unlock
Then you can flash a recovery image and then flash a zip file containing the su binary and app via recovery
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
Please, do not give suggestions when you don't know how things work - see the bold part of your own post. You wouldn't want someone that doesn't know exactly how motor works to fix your car, would you?
If he has S-OFF, there is no need to unlock bootloader and void warranty. Moreover, having S-OFF is better and more powerful than having unlocked bootloader. All the info is in the stickies, and you should go read them too.
Jack_R1 said:
Please, do not give suggestions when you don't know how things work - see the bold part of your own post. You wouldn't want someone that doesn't know exactly how motor works to fix your car, would you?
If he has S-OFF, there is no need to unlock bootloader and void warranty. Moreover, having S-OFF is better and more powerful than having unlocked bootloader. All the info is in the stickies, and you should go read them too.
Click to expand...
Click to collapse
Dont talk to me like i dont know what im talking about. Ive rooted and messed with plenty of phones. I based my advice off of my experience. Just because i dont know all of the specifics of a particular device doesnt really matter, all of HTCs devices operate basically the same. So maybe you shouldnt be worried about me and more worried about helping this guy like everyone else is. Its not up to you to decide if he wants to take my advice or not, thats for him to decide.
Sent from my HTC One X using Tapatalk 2
stumpyz9 said:
Dont talk to me like i dont know what im talking about. Ive rooted and messed with plenty of phones. I based my advice off of my experience. Just because i dont know all of the specifics of a particular device doesnt really matter, all of HTCs devices operate basically the same. So maybe you shouldnt be worried about me and more worried about helping this guy like everyone else is. Its not up to you to decide if he wants to take my advice or not, thats for him to decide.
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
You basically wrote that you don't know what you're talking about, and by suggesting to unlock bootloader on S-OFF phone you made it obvious beyond any doubt. Indeed, all of HTC devices operate the same, all of HTC devices have bootloader security, all of them more or less since eMMC introduction block write access to /system in bootloader, all of them can be unblocked by turning S-OFF or unlocking the bootloader.
Unlocking the bootloader voids the warranty and prevents /boot from being flashed from recovery, subjecting the user to constant kernel flashing through FASTBOOT for any ROM he wants to flash, while S-OFF allows full and undisturbed recovery functionality. Thus, bootloader unlock is inferior solution that should be avoided if possible, and suggesting it for a phone that already has S-OFF is BAD/not smart/pick whatever negative adjective you want.
Of course, all that is written in stickies, as I said, but I guess that you can't be bothered reading before writing, and when suggested to do so, prefer going all defensive. Yes, you don't know what you're talking about. I'm glad you rooted zillion devices, if you think it makes you know everything - read the info above again.
I already did my part to help the guy, and I don't have enough time for people that want everything laid out for them. If he's willing to use some Google and read - he'll get to his solution using my pointer, or somebody will point him to the relevant guide (and there is one in INDEX thread, AFAIK). The old debate of giving someone a fish vs teaching him fishing. I picked my side a long time ago.
Guys, don't be angry at each other
Thank you, you both helped me a lot. Big thanks )
Rooted my phone. If it's interesting I can tell how
NX3 said:
I've bought a phone which has S-OFF, ***LOCKED***, which I'm trying to root. I've seen many guides, read them but they are all from the point you have S-ON. I've tried manual ADB install of CWM but that fails, permission denied.
Any advice before I brick it ? The phone seems to be in a quasi state...not sure how I progress.
C:\Android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.00.0002
(bootloader) version-baseband: 3822.10.08.04_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.10.401.8
(bootloader) product: saga
(bootloader) platform: HBOOT-7230
(bootloader) modelid: PG8810000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3963mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: ebd3df7d
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
Lucky!
Looks like you're S-OFF'd and have SuperCID, which means you should be able to install any rom you like.
If I'm guessing correctly you have ENG hboot 2.00?
Just ignore the ***Locked***, as you're S-OFF'd you should do anything. How did you try to flash cwm?
Fastboot flash recovery?
(bootloader) version-bootloader: 2.00.0002
(bootloader) cidnum: 11111111
(bootloader) security: off
Click to expand...
Click to collapse
It looks like a xtcclip s-off so you've got a permanent s-off regardless which hboot you use.
Hi guys, i have the same problem. I'm *****Locked***** but s-off, so i made this: http://forum.xda-developers.com/showthread.php?t=1525100 but as i'm s-offed i don't need the 2nd pass (i think).. so in 3rd pass when i make this, the cmd tells me that im not allowed to install the recovery. What's wrong?
Read the answer in your original thread

[Q] Trying to get HTC one S on stock rom? Please help ?

I have this HTC one S, I am not sure which network phone is it. I bought is from someone else and he had no idea about network.
Right now when i press factory reset from volume down + power button. it brought me at this screen which say clockwork Mod recovery v 5.8.1.5
I am able to select only first 2 options which are reboot system now and install zip from sdcard . When i pressed install zip from sdcard its not doing anything and bringing me back on same screen
Could you please help me installing stock rom on this phone. ?
Thanks in advance guys
AW: [Q] Trying to get HTC one S on stock rom? Please help ?
If you turn ur phone on with holding power and volume down you should be in your bootloader.
Can you tell us what stands on the top?
Locked/unlocked/relocked and which hboot version?
Sent from my HTC One S using xda premium
this is the info
Tampered
Unlocked
VLE PVT ship s-on RL
HBOOT-1.08.0000
Radi-0.16.31501S.06_3
open DSP-v23.1.0.32.0323
eMMC boot
Mar 21, 2012, 16:01:09
Just curious to know what this information means , please let me know each line if possible. Appreciate your help
AW: [Q] Trying to get HTC one S on stock rom? Please help ?
Tampered: no stock recovery
Unlocked: your bootloader is looked
VLE: Ville: HTC One S
S-ON: security on
Radio: your radio Version
You have to lock your bootloader.
Download the all in one toolkit which you can find in the development section. There are all necessary files.
Be sure you have installed the HTC sync driver.
1. Connect your mobile To your pc when your are in the screen where you can see hboot version etc.
2. There should be "hboot USB" in blue.
3. Navigate to hboot and press power.
4. It should change to "fastboot USB" in red.
5. Then open the all in one toolkit on your PC.
6. Open the folder where ADB and fastboot exe are located.
7. Press shift and right click somewhere in the folder and open the command line.
8. Then type in "fastboot oem lock"
9. If you take a look to your phone you should see that the "unlock" changed To "relocked"
That was the first step.
10. Go To the development section in this forum and look for the wwe europe ville ics ruu 2.31 or sth like that.
11. Download the file
12. Doubleklick the file
13. Follow the instructions
14. Let the ruu install everything
15. If everything works fine you should be on official ICS 4.0.4 with Sense 4.1 now
Good luck!
I hope I wrote an easy understandable instruction.
If u experience any problems feel free to post it here.
I'm sure I or someone else can help you.
Sent from my HTC One S using xda premium
NQNH , thanks a lot for this easy and nice explanation, its really helpful for a noob like me. I have few more questions but lets resolve this issue first. Okay I tried all steps you mentioned and it worked like a charm. just got stuck at final step. Please help.
In CMD i got this
'C:\Users\Owner\Desktop\HTC' is not recognized as an internal or external comman
d,
operable program or batch file.
C:\Users\Owner\Desktop\HTC custom rom procedure\One_S_All-In-One_Kit\data>fastbo
ot oem lock
...
(bootloader) Lock successfully...
(bootloader) TZ_HTC_SVC_DISABLE ret = 534642032 (0x1FDDFD70)
FAILED (status read failed (Too many links))
finished. total time: 0.941s
C:\Users\Owner\Desktop\HTC custom rom procedure\One_S_All-In-One_Kit\data>
This is the error message when i tried step 8, but when i checked the screen it shows relocked now , seems like it worked okay.
i tried this file
http://forum.xda-developers.com/showthread.php?t=1941402
Everytime i runs this RUU application file , after passing thru all steps it says ROM utility stopped working, Seems like i am almost done but just stuck at last point.
Hello NQNH, i tried it one more time and finally passed thru that screen. it started ROM update utility but got back with this error msg
Error (131) customer ID error
The ROM update utility cannot update your android phone
please get the correct ROM update utility and try again
I am using RUU : 1.0.6.2012
please let me know if i can use any other utility
AW: [Q] Trying to get HTC one S on stock rom? Please help ?
What do you get when you type in
fastboot getvar cid
?
Try this RUU
http://www.androidfiles.org/ruu/sec...02.31_10.09a.50.04L_release_275655_signed.exe
Sent from my HTC One S using xda premium
I tried RUU which you suggested , Thanks NQNH but sorry this time it came back with error (130) , model ID error.
fastboot getvar cid : BM___001
AW: [Q] Trying to get HTC one S on stock rom? Please help ?
Seems that you have a branded phone. (Bell Mobile Canada?)
This ruu should run fine:
http://www.androidfiles.org/ruu/sec...02.04_10.08g.50.04L_release_280275_signed.exe
Sent from my HTC One S using xda premium
Thanks Thanks Thanks Thanks a lotttttttttt, I don't know if pressing thanks button is good enough to appreciate your help. I learnt a lot from this session. If you don't mind , just for curiosity can i ask you few more questions,
Tampered (Does it mean somebody tried to install custom rom on it or something else ? )
Unlocked
VLE PVT ship s-on RL ( does S-on means this phone is unlocked or some thing else ? )
HBOOT-1.08.0000 ( is it same like version number in iphone , is it baseband version number, where i can find this number in phone settings ? )
Radi-0.16.31501S.06_3
open DSP-v23.1.0.32.0323 ( don't know what it means , please explain )
eMMC boot ( don't know what it means , please explain )
Mar 21, 2012, 16:01:09 ( is it manufacturing date or date when it was tempered )
Thanks again for your help ..
bindudhindsa said:
Thanks Thanks Thanks Thanks a lotttttttttt, I don't know if pressing thanks button is good enough to appreciate your help. I learnt a lot from this session. If you don't mind , just for curiosity can i ask you few more questions,
Tampered (Does it mean somebody tried to install custom rom on it or something else ? )
Unlocked
VLE PVT ship s-on RL ( does S-on means this phone is unlocked or some thing else ? )
HBOOT-1.08.0000 ( is it same like version number in iphone , is it baseband version number, where i can find this number in phone settings ? )
Radi-0.16.31501S.06_3
open DSP-v23.1.0.32.0323 ( don't know what it means , please explain )
eMMC boot ( don't know what it means , please explain )
Mar 21, 2012, 16:01:09 ( is it manufacturing date or date when it was tempered )
Thanks again for your help ..
Click to expand...
Click to collapse
glad to hear that I helped you.
Tampered means that someone already changed something on the phone (unlocked/relocked/custom recovery)
A comparison should be.. if you bought a new pc and if you open the case you have to break the seal. The "Tampered" say that you had break this seal on the phone (e.g. by unlocking the bootloader)
S-ON means that the security flags are on. Its a system protection so nobody can manipulate system data.
S-ON + locked bootloader -> you can do nothing, no root, no custom things
S-ON + unlocked bootloader -> you can flash custom recovery, root, custom rom (you can see an unlocked bootloader as a compromise between S-ON and S-OFF
S-OFF -> you can do everything what you want, change bootloaderGUI, bootanimations, splashscreens.
Unlocked means that you bootloader is unlocked. If its locked you cant install custom recovery, root and custom firmware. It has to be locked when you install a RUU.
You cant find your HBOOT version in your phone settings because its the version of the bootloader.
the bootloader is independed from the rom you are on. Its like the BIOS from your PC and your ROM is Win7 where you either cant find the bios version.
Radio is the module which is responsible for mobile data etc.
no/wrong/corrupt radio = no network/no signal
openDSP .. i don't know
eMMC boot, I guess that this is the partition where the bootloader is located.. but I'm not sure.
Mar 21, 2012, 16:01:09 is the date when .. difficult to explain .. when the development of the RUU was finished?
if I wrote something wrong please correct me.
Thanks a lot for this very helpful information. Appreciate your help. Kind of person like you are the reason these forums are running successfully and helping novice people like me. Thanks again.
AW: [Q] Trying to get HTC one S on stock rom? Please help ?
Thanks for your words
Sent from my HTC One S using xda premium
Hello.
I'm having same problem with getting back on stock firmware...
After trying to flash into CM10, i got stock in CM boot logo.
So trying to get back to original using RUU.
But it just looks like I can not get right one...
I did everything like in posts above, and when I enter "fastboot getvar cid" I got "HTC_Y13"
Any idea which RUU is correct for that?
I'm still trying, so maybe it will be fools luck... Or maybe someone can put me on point?
auronn said:
Hello.
I'm having same problem with getting back on stock firmware...
After trying to flash into CM10, i got stock in CM boot logo.
So trying to get back to original using RUU.
But it just looks like I can not get right one...
I did everything like in posts above, and when I enter "fastboot getvar cid" I got "HTC_Y13"
Any idea which RUU is correct for that?
I'm still trying, so maybe it will be fools luck... Or maybe someone can put me on point?
Click to expand...
Click to collapse
your cid is a unbranded eu cid.
try any unbranded eu ruu (3.16 or earlier)
Hello everyone,
So, 2 days in front of PC, reading forums and trying. No luck... So try to post it here.
I want to flash to CM10.
Bootloader is unlocked.
Recovery is installed (TWRP S4)
Root is done.
Security S-ON.
When I try to install CM10, everything went fine, but when It have to reboot it just stuck in CM booting logo loop...
And since you can't remove memory card on HTC One S, I think I have no other option how to reinstall stock firmware. And my problems starts...
I relocked bootloader.
Download already like five different RUU's...
The problem is, I can not locate my version, it's blank...
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.15.0000
(bootloader) version-baseband: 1.11.50.05.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT23NW410019
(bootloader) imei: 359901040772549
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4010000
(bootloader) cidnum: HTC__Y13
(bootloader) battery-status: good
(bootloader) battery-voltage: 4124mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-64bedd38
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
So everytime I start RUU, in the screen Current information about your Android phone" "Image version" is blank and the one with "Verify that you want to update the ROM version" "From Image Version" is blank...
When I push "Next" it goes "Checking", then "Rebooting Bootloader", "Erasing User Data" and "Sending".
When it comes to "Updating Signature" I'm getting error code...
Phone is bought in Norway, and by checking cid: HTC_Y13, I can see that it's HTC-Nor. So which one of RUU's I have to use?
I also tried to flash zip RUU, using One_S_All-In-One_Kit_v3.5 with same no luck...
Really don't know what to do... Any help would be appreciated...
Thank you in advance!
real187 said:
your cid is a unbranded eu cid.
try any unbranded eu ruu (3.16 or earlier)
Click to expand...
Click to collapse
Thank you, I'm downloading and will try this now:
RUU_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_Radio_1.11.50.05.28_10.27.50.08L_release_301814_signed_2_4.exe
Already tried those:
RUU_Ville_U_ICS_40_S_HTC_Europe_2.31.401.5_Radio_1.06es.50.02.31_10.09a.50.04L_release_275655_signed.exe
RUU_VILLEC2_U_ICS_40_HTC_Europe_1.11.401.110_Radio_16.12.20.02U_16.05.20.16_M2_release_263510_signed.exe
RUU_VILLEC2_U_ICS_40_HTC_Europe_1.11.401.109_Radio_16.12.20.02U_16.05.20.16_M2_release_263131_signed.exe
RUU_VILLEPLUS_U_JB_45_HTC_Generic_1.14.999.50_Radio_1.10r.50.05.19_10.22a.50.08L_release_294323_signed.exe
And also:
OTA_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_1.11.50.05.28_10.27.50.08L_release_301852xf01hejl416oev96.zip
using One_S_All-In-One_Kit_v3.5 with no luck...
Does any body can tell me the difference between Ville, VilleC2 and VillePlus?
real187 said:
your cid is a unbranded eu cid.
try any unbranded eu ruu (3.16 or earlier)
Click to expand...
Click to collapse
Thank you a lot!!!
This one worked:
RUU_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_Radio_1. 11.50.05.28_10.27.50.08L_release_301814_signed_2_4 .exe
auronn said:
Hello everyone,
So, 2 days in front of PC, reading forums and trying. No luck... So try to post it here.
I want to flash to CM10.
Bootloader is unlocked.
Recovery is installed (TWRP S4)
Root is done.
Security S-ON.
When I try to install CM10, everything went fine, but when It have to reboot it just stuck in CM booting logo loop...
And since you can't remove memory card on HTC One S, I think I have no other option how to reinstall stock firmware. And my problems starts...
I relocked bootloader.
Download already like five different RUU's...
The problem is, I can not locate my version, it's blank...
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.15.0000
(bootloader) version-baseband: 1.11.50.05.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT23.......
(bootloader) imei: 3599...............
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4010000
(bootloader) cidnum: HTC__Y13
(bootloader) battery-status: good
(bootloader) battery-voltage: 4124mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-64bedd38
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
So everytime I start RUU, in the screen Current information about your Android phone" "Image version" is blank and the one with "Verify that you want to update the ROM version" "From Image Version" is blank...
When I push "Next" it goes "Checking", then "Rebooting Bootloader", "Erasing User Data" and "Sending".
When it comes to "Updating Signature" I'm getting error code...
Phone is bought in Norway, and by checking cid: HTC_Y13, I can see that it's HTC-Nor. So which one of RUU's I have to use?
I also tried to flash zip RUU, using One_S_All-In-One_Kit_v3.5 with same no luck...
Really don't know what to do... Any help would be appreciated...
Thank you in advance!
Thank you, I'm downloading and will try this now:
RUU_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_Radio_1.11.50.05.28_10.27.50.08L_release_301814_signed_2_4.exe
Already tried those:
RUU_Ville_U_ICS_40_S_HTC_Europe_2.31.401.5_Radio_1.06es.50.02.31_10.09a.50.04L_release_275655_signed.exe
RUU_VILLEC2_U_ICS_40_HTC_Europe_1.11.401.110_Radio_16.12.20.02U_16.05.20.16_M2_release_263510_signed.exe
RUU_VILLEC2_U_ICS_40_HTC_Europe_1.11.401.109_Radio_16.12.20.02U_16.05.20.16_M2_release_263131_signed.exe
RUU_VILLEPLUS_U_JB_45_HTC_Generic_1.14.999.50_Radio_1.10r.50.05.19_10.22a.50.08L_release_294323_signed.exe
And also:
OTA_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_1.11.50.05.28_10.27.50.08L_release_301852xf01hejl416oev96.zip
using One_S_All-In-One_Kit_v3.5 with no luck...
Does any body can tell me the difference between Ville, VilleC2 and VillePlus?
Click to expand...
Click to collapse
Firstly, I would recommend removing part of your IMEI and Serial Numbers from your post, it could be used in bad ways by other people.
Ville is the HTC One S with a Snapdragon S4 chipset, clocked at 1.5GHz (dual core) otherwise known as z520e. (You have this phone)
VilleC2 is what became of the HTC One S when HTC ran out of Snapdragon S4 chipsets in many parts of the world due to a shortage. It has a Snapdragon S3, clocked at 1.7GHz (dual core) otherwise known as z560e.
VillePlus is a Special Edition version of the HTC One S, only available in Taiwan. It has the same processor as the Ville, except comes in a white body instead of the normal grey or black options and has 64GBs of internal storage. The other two have 16GBs internal storage. This phone is quite rare.
You should try RUUs only that say ville, and not VillePlus or VilleC2. These won't work and may even irreversibly damage your phone.
OTAs only work when you already have a previous firmware version. Let's say you were on ICS, a Jelly Bean FOTA is released (firmware over the air) and installs ("flashes") on top of your existing ICS installation, keeping your apps and data.
RUUs wipe all data and wipe everything on the phone when installing through a USB connection.
Could you specify what error code you get on the RUUs?
----
The reason why CM10 didn't boot is because you didn't flash the boot.img.
You need to extract the boot.img from the CM10 zip and put that into your "working folder" (the folder with adb and fastboot files in it)
Open up a command prompt / terminal in that folder and type
fastboot flash boot boot.img
when you are in FASTBOOT USB mode in the bootloader.
Go to Fastboot. Plug in your USB with the phone. Now, ctrl and r --> type cmd --> cd to C:/where your adb is --> fastboot read cid
Then type the 8 digit string that you get. It would help us determine your network provider.

[Q] HTC One S having issue with CM10.1

Hi all!
Im in a big pickle here and I cant get myself out at the moment.
First hand.. The info
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.13.0000
(bootloader) version-baseband: 0.17.31501S.10_2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4011000
(bootloader) cidnum: ROGER001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3917mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d92cc658
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.093s
Now i've been running cyanogenmod 10 stable since I started rooting etc...
And it's been amazing, but now since there has been a release candidate for 10.1, I was looking into updating it.
I ran into an issue where my boot-loader was not accepted , therefor i would run into an error on Clockwork mod stopping me from flashing 10.1
The bad thing was that I erased my previous installation without backing up the stock and CM10.
So now i'm left with no system. Though I can get into Fastboot and ADB via recovery.I
For some reason if I try to flash CM10 (The rom and the boot file) the cyanogenmod logo will continue spinning.
I tried to fiddle around with my RUU afterwards because I currently have S-On. But i later learned that i need superCID.
^(Which i learned that you need your phone on to alter it to the 8 "1"s) Which i cant do because i have no system.
I might have already altered some files guessing that my boot-loader is named "dirty-d92cc658" and im afraid that I messed up something internally.
So anyways. Im here with my Ville S4 plugged in on fastboot not knowing what to do.
Any Help would be amazing , thank you
Did you try a RUU for Rogers? Not sure if there is one but try to find a RUU that matches your cid
c19932 said:
Did you try a RUU for Rogers? Not sure if there is one but try to find a RUU that matches your cid
Click to expand...
Click to collapse
Do I need to have superCID to flash RUU's ?
Mozziliac said:
Do I need to have superCID to flash RUU's ?
Click to expand...
Click to collapse
If you have a RUU for your specific phone, no, you just need to lock the bootloader.
Have USB debugging turned on (unless running ruu when your phone is in fastboot usb mode)
If you can't find one for Rogers, then yes you have to be super cid to run another RUU.exe (after that change your cid back so an OTA update doesn't brick your phone)
If your phone is on Jellybean, you need to run a JB ruu, if it's Ice Cream Sandwich it won't run. Unless you are supercid I guess.
Khan.orak has a guide for OTA zips to return to stock that you might want.
http://forum.xda-developers.com/showthread.php?p=44365370
Ville / VilleC2 RUU, OTA and Stock Nandroid Collection
http://forum.xda-developers.com/showthread.php?t=2200930
tivofool said:
If you have a RUU for your specific phone, no, you just need to lock the bootloader.
Have USB debugging turned on (unless running ruu when your phone is in fastboot usb mode)
If you can't find one for Rogers, then yes you have to be super cid to run another RUU.exe (after that change your cid back so an OTA update doesn't brick your phone)
If your phone is on Jellybean, you need to run a JB ruu, if it's Ice Cream Sandwich it won't run. Unless you are supercid I guess.
Khan.orak has a guide for OTA zips to return to stock that you might want.
http://forum.xda-developers.com/showthread.php?p=44365370
Ville / VilleC2 RUU, OTA and Stock Nandroid Collection
http://forum.xda-developers.com/showthread.php?t=2200930
Click to expand...
Click to collapse
How can I superCID my phone if I cant boot into the rom?
I've never superCid, can't help you there.
Good news is you can get into bootloader still.
You could fastboot flash a boot.img and flash a rom in recovery.
Just need to mount usb storage in recovery to put the rom.zip on your phone.
Edit: reread that you tried that but rom didn't boot. Hopefully you waited 5-10 min for first load.
try wipedata/factory reset from CWM like 3 times then flashing?
Good luck to ya.
Edit 2: kind of wondering if you can run the Rogers RUU with that low of a bootloader (version-bootloader: 1.13.0000)
Maybe someone can chime in, because that would be nice not having to SuperCid.
Alright so I seemed to get it running on CM 10 by switching recoveries and flashing it's boot.
Then I was able to superCID the phone, which then lead my into S-off'ing it.
Then I was able to update the hboot firmware to 2.15
Cleared the cache and installed the new kernel and flashed cyanogenmod 10.1 rc
Everything went well after that. I did run into a laggy issue, which I then fixed by switching the CPU governor to ondemand instead of interactive.
Thanks for the post guys

[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

Categories

Resources