Related
Hi all, I had to re-install a stock rom from an HTC RUU. Prior to that I was HTC unlocked, HBOOT 1.27, firmware 3.33, rooted, custom ROMs.
Right now the bootloader is re-locked, HBOOT 1.29, european stock 3.33.401.106 with 11.76A.3504.00U_11.24A.3504.31_M radio.
The objective is to re-gain S-OFF and go trough all the way to custom ROM again.
I was thinking to execute fastboot oem writesecureflag 3
To my understanding this should clear off the relocked flag.
At this point to go to htcdev and proceed with that like I did already once.
Probably the above is too simple to work, but the whole JuopunutBear timing thing is a bit an issue having tried already in ther past.
Any help/feedback is greatly appreciated.
DiscreteTask said:
Hi all, I had to re-install a stock rom from an HTC RUU. Prior to that I was HTC unlocked, HBOOT 1.27, firmware 3.33, rooted, custom ROMs.
Right now the bootloader is re-locked, HBOOT 1.29, european stock 3.33.401.106 with 11.76A.3504.00U_11.24A.3504.31_M radio.
The objective is to re-gain S-OFF and go trough all the way to custom ROM again.
I was thinking to execute fastboot oem writesecureflag 3
To my understanding this should clear off the relocked flag.
At this point to go to htcdev and proceed with that like I did already once.
Probably the above is too simple to work, but the whole JuopunutBear timing thing is a bit an issue having tried already in ther past.
Any help/feedback is greatly appreciated.
Click to expand...
Click to collapse
fastboot oem writesecureflag 3 returns bootloader to S-ON, it wont help you.
The only way to S-OFF 1.2x.xxxx HBOOT versions is JuopunutBear S-OFF. Oh and did you know you dont have to be S-OFF to flash ROMs, search for the Flashing ROMs with S-ON guide and follow it.
Jonny, thank you for your input. To be honest I did not know that it was possible flashing with S-OFF, I will look into this.
From you answer I understand that JuopunutBear S-OFF can be used the same also in the case the device was already S-OFF and relocked.
Thanks again.
Jonny said:
fastboot oem writesecureflag 3 returns bootloader to S-ON, it wont help you.
The only way to S-OFF 1.2x.xxxx HBOOT versions is JuopunutBear S-OFF. Oh and did you know you dont have to be S-OFF to flash ROMs, search for the Flashing ROMs with S-ON guide and follow it.
Click to expand...
Click to collapse
DiscreteTask said:
Jonny, thank you for your input. To be honest I did not know that it was possible flashing with S-OFF, I will look into this.
From you answer I understand that JuopunutBear S-OFF can be used the same also in the case the device was already S-OFF and relocked.
Thanks again.
Click to expand...
Click to collapse
you have hboot version 1.29.0000 yes? This means that the easier revolutionary method wont work on your phone (revolutionary is GingerBread only), so the only possible way to S-OFF on your phone is with the JuopunutBear method.
To get rid of the relocked text on the bootloader you need to flash the JuopunutBear hboot (which you can only do after S-OFF) then run an RUU. This will make the text say "LOCKED" again
Forgive my noobness, Its been ages since I've had a HTC device to play with. I've been reading and just wanted to clarify my findings with some recent answers.
1. T-mobile ONE S, H-boot 2.15, and TMOB010 CID. 3.14.531.17 710rd.
I attempted to get Super CID, but it wouldnt stick. was trying to S-off via facepalm method, as Moonshine stated a different version required.
So my findings are its not possible, is that correct? Thats kinda leaning towards both super CID, and S-off
2. I got PacMan on the device, and am gonna update to the newest, am curious if I have to flash the boot.img after updating?
Again, I have read, and searched. If I missed something that's already around please let me know as I'm not looking to get spoonfed due to laziness.
HTC introduced a write protection for mmcblk0p4 with its 2.15.0000 (2.15.4444) bootloader. So these devices can't get SCID a 'regular' way. If there is a way to flash a working RUU version for moonshine, I don't know. You'll have to read again for these things in the moonshine/facepalm threads.
And yes on an s-on device you should always flash the kernel separately with 'fastboot flash boot boot.img'.
--- edit
e.g. check out post #4 here
rootrider said:
HTC introduced a write protection for mmcblk0p4 with its 2.15.0000 (2.15.4444) bootloader. So these devices can't get SCID a 'regular' way. If there is a way to flash a working RUU version for moonshine, I don't know. You'll have to read again for these things in the moonshine/facepalm threads.
And yes on an s-on device you should always flash the kernel separately with 'fastboot flash boot boot.img'.
--- edit
e.g. check out post #4 here
Click to expand...
Click to collapse
My phone is from Cincinnati Bell carrier and it was with 2.15.0000 hboot, but I did s-off because mmcblk0p4 was writable, so it is good to test is it writeable or not.
hello everyone, android user and my device s-off in the first year I want to do but how to do it without the support of htcdev? Is there a program available? When I unlock my device also has root? Am I going to root sturdy at the same time to s-off? I just want to get rid of device applications that official. 5 4.2.2 installed on my device, this device can sense it possible to root for?
Thank you.
I think you're confused as to what s-off is and unlocking is, they're two entirely different things. You don't use htcdev to get s-off. You use htcdev to unlock your bootloader, and no you cannot unlock your bootloader without htcdev. Unlocking your bootloader doesn't give you root, after unlocking the bootloader you must install a custom recovery and then you can gain root. After gaining root you can get SuperCID and then you can get s-off. If all you want to do is remove some system apps, then you'll just need to unlock the bootloader, install a custom recovery, and install root.
Sent from my Evita
You don't need s-off to delete bloatware (pre-installed apps). Just use HTCDev.com to unlock the bootloader. Then install custom recovery, then either flash SU or a rooted ROM to get root.
The process to s-off is simple (see Facepalm method in the Original Android Development subforum). However, it requires SuperCID. Since the CID is protected on Sense 5, you will not be able to SuperCID (and therefore S-off).
But as already mentioned, you don't need S-off to root and delete bloatware.
I'm at a loss and somewhat confused.
I read in one place that I need to s-off to update my radio, but in order to do that I need super-cid.
so I'm trying to change my cid from ROGER001 to 11111111.
Now I'm reading that I can s-off without super-cid? All I'd like to do is update my radio and kernel so my phone stops losing signal and stops rebooting. I should also mention that I already went to htcdev and unlocked my bootloader.
What I see in fastboot:
TAMPERED
UNLOCKED
Evita PVT SHIP S-ON RL
HBOOT-2.14.0000
RADIO-0.23a.32.09.29
OpenDSP-v31.1.0.45.0815
eMMC-boot
Viper Xl 4.2.0(amazing Rom btw)
HTC Sense 5.0
I have tried the script, it failed, manual method, that failed.
manual method gets me this result after I fastboot oem readcid(ok), fastboot oem writecid 11111111
... INFO elite_init_sd, SD card already power on
INFOsdhw_7xxx_open: id=0
INFO[SD_HW_ERR] SD: No device attached
INFO902910 902E20
FAILED (status read failed (No such file or directory))
I'd like to resolve this as my signal stops, and device reboots randomly.
telaphoneguy said:
Now I'm reading that I can s-off without super-cid?
Click to expand...
Click to collapse
Nope, wherever you read that, its completely incorrect.
It says right in the s-off method instructions, in big bold print that SuperCID is required: http://forum.xda-developers.com/showthread.php?t=2155071
If you are having trouble with s-off, the other solution to random reboots on Sense 5 is to install the Beastmode kernel.
Release the hounds!!
Sent from my One X using XDA Premium 4 mobile app
KungFuCracka94 said:
Release the hounds!!
Click to expand...
Click to collapse
I actually started to type "as mentioned in a bazillion different places" after my Beastmode statement in the previous reply. But I decided to be nice!
I checked out this link again: http://forum.xda-developers.com/showthread.php?t=1952038
i still get an error, it fails on step 6 with message [-] Failed.
I'll give beastmode another shot, i've tried it before, no success.
telaphoneguy said:
I checked out this link again: http://forum.xda-developers.com/showthread.php?t=1952038
i still get an error, it fails on step 6 with message [-] Failed.
I'll give beastmode another shot, i've tried it before, no success.
Click to expand...
Click to collapse
The x-factor exploit fails since its looking for the AT&T CID. For other CIDs, you need to edit it manually using the hex edit method.
If you have trouble with installing Beastmode, I think some folks have had to install Beastmode 2.0 before installing 3.5.
After many attempts, boot loops beastmode reloaded 3.5 finally took.
So now I need to ask if I need s-off, i've done everything except upgrade my radio.
I'll only update my radio if the antenna drops keeps dropping out.
Well, radio went out, no reboots yet, I'll see what else I can try.
no i want to only rooting device, this video help me ? cause title for htc one."but my device hox"
www.youtube.com/watch?v=kJYAS2KN17Y&list=WL2E6DAD3D0702FB02
No it won't work, it's not for this phone. Only ever use guides specifically for this device or you could brick it. As I've already told you, you absolutely cannot root this device without unlocking the bootloader through htcdev first. I'm not sure why you're still searching for ways to do it, they do not exist. There's no point in coming here for advice if you don't even listen to the answers you're given.
Sent from my Evita
timmaaa said:
I think you're confused as to what s-off is and unlocking is, they're two entirely different things. You don't use htcdev to get s-off. You use htcdev to unlock your bootloader, and no you cannot unlock your bootloader without htcdev. Unlocking your bootloader doesn't give you root, after unlocking the bootloader you must install a custom recovery and then you can gain root. After gaining root you can get SuperCID and then you can get s-off. If all you want to do is remove some system apps, then you'll just need to unlock the bootloader, install a custom recovery, and install root.
Sent from my Evita
Click to expand...
Click to collapse
Tnx so much if i think rooting need to s-off but you say "thats two entirely different" .. then why people use to s-off? for change rom ? and i find this video for root its working for my hox ? or only working htc one.. https://www.youtube.com/watch?v=kJYAS2KN17Y&list=WL2E6DAD3D0702FB02 again tnx. sorry for english
timmaaa said:
No it won't work, it's not for this phone. Only ever use guides specifically for this device or you could brick it. As I've already told you, you absolutely cannot root this device without unlocking the bootloader through htcdev first. I'm not sure why you're still searching for ways to do it, they do not exist. There's no point in coming here for advice if you don't even listen to the answers you're given.
Sent from my Evita
Click to expand...
Click to collapse
some people say me "when using htcdev for unlock your warranty get void" thats true ?
Absolutely nowhere within this forum does it say you need s-off to root, because you don't. I've already told you that. I can't view that video for some reason but unless it specifically says it's for the Evita don't use it. All you need is in the Everything Evita link in my signature, do not get information anywhere else, XDA is the only place you need to look.
As I've already told you, if you want to root you need to unlock your bootloader and install a custom recovery first. In the link I mentioned there are guides on how to do this, you need to follow the guide that pertains to your current firmware version.
Sent from my Evita
timmaaa said:
No it won't work, it's not for this phone. Only ever use guides specifically for this device or you could brick it. As I've already told you, you absolutely cannot root this device without unlocking the bootloader through htcdev first. I'm not sure why you're still searching for ways to do it, they do not exist. There's no point in coming here for advice if you don't even listen to the answers you're given.
Sent from my Evita
Click to expand...
Click to collapse
timmaaa said:
Absolutely nowhere within this forum does it say you need s-off to root, because you don't. I've already told you that. I can't view that video for some reason but unless it specifically says it's for the Evita don't use it. All you need is in the Everything Evita link in my signature, do not get information anywhere else, XDA is the only place you need to look.
As I've already told you, if you want to root you need to unlock your bootloader and install a custom recovery first. In the link I mentioned there are guides on how to do this, you need to follow the guide that pertains to your current firmware version.
Sent from my Evita
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1732980 i searched someone info for s-off "s-off, hboot and radio flash only happens if I need to make" sorry i ask much question cause im noob; then give me root link for sense 4.3.3 and hasoon2000's working for me ?
What are your bootloader details?
Sent from my Evita
Cid: htc_m27; Softwarenumber:4.18.401.2 , radio: .51204.167.31 hboot: 1.72.0000 s-on RL htc one x
You're not even in the right forum, this is the HTC One XL / at&t One X (Evita) forum. You need to ask in the HTC One X forum. They're different phones.
Sent from my Evita
[Q]~[HELP] SuperCID, Unlocked, Rooted, and S-OFF, how to restore to stock AT&T ROM?
Hi, geeks,
For my AT&T HTC One X, I have followed you guys all the way to here now: with SuperCID, Bootloader Unlocked (via HTC Dev), Rooted of course, and S-OFF (with touchscreen firmware down-graded).
Now I want to go back to AT&T stock ROM to use the ISIS wallet. Could you please tell me how? I am worried that my phone get bricked!
Thank you so much!
You can just flash a stock at&t ROM which you'll find in our Android Development section. Or you can run the 3.18 RUU. This will also flash stock recovery, hboot, radio, and other firmware modules. The ROM is probably the better and easier option.
Sent from my Evita
Thank you, timmaaa. Do I need to lock the bootloader and so on? I saw it somewhere but can't find the link now.
timmaaa said:
You can just flash a stock at&t ROM which you'll find in our Android Development section. Or you can run the 3.18 RUU. This will also flash stock recovery, hboot, radio, and other firmware modules. The ROM is probably the better and easier option.
Sent from my Evita
Click to expand...
Click to collapse
To run the RUU? No, because you're s-off you don't need to do any of that, just run the RUU through Windows.
Sent from my Evita
timmaaa said:
To run the RUU? No, because you're s-off you don't need to do any of that, just run the RUU through Windows.
Sent from my Evita
Click to expand...
Click to collapse
I'm doing the same thing, but to attempt to trade in my phone. I assume that after running the RUU I should relock the bootloader. I want to get rid of the red text.
*EDIT* nevermind. didn't realize that the RUU clears out the *TAMPERED* flag and gets rid of the red text. should be all good now.
One more question, timmaaa: after flashing RUU, the recovery partition will be replaced with the stock recovery, and the S-OFF and boot loader will be kept as it is (based on what I learned from other posts of you). What if I need to flash CM again? I am confused because not many people are doing what I am. Thanks!
timmaaa said:
To run the RUU? No, because you're s-off you don't need to do any of that, just run the RUU through Windows.
Sent from my Evita
Click to expand...
Click to collapse
Yes, the RUU will install the stock recovery. Your phone will still be s-off and will still have an unlocked bootloader. All you need to do is install TWRP recovery again and then you can flash any ROM you like. Full instructions on how to install a recovery can be found in my How-To Guide For Beginners thread, link in my signature.
Sent from my Evita
Hi, timmaaa, I got a RUU error 155 when flashing RUU_EVITA_UL_JB_45_S_Cingular_US_3.18.502.6_Radio_0.24p.32.09.06_10.130.32.34_release_signed_With_Partial.exe.
Seems I need to re-lock the bootloader, which I am reluctant to do. Do I miss anything?
timmaaa said:
Yes, the RUU will install the stock recovery. Your phone will still be s-off and will still have an unlocked bootloader. All you need to do is install TWRP recovery again and then you can flash any ROM you like. Full instructions on how to install a recovery can be found in my How-To Guide For Beginners thread, link in my signature.
Sent from my Evita
Click to expand...
Click to collapse
You don't need to relock if you're s-off. Are you using a 2.0 or 3.0 usb port? Are you using a HTC cable? Are you in fastboot mode? Have you uninstalled HTC Sync Manager?
Sent from my Evita
Hi, timmaaa, I am using USB2.0 on windows XP, with a regular cable, not in fastboot mode, and haven't uninstalled HTC Sync Manager.
I will try flash in fastboot mode again.
timmaaa said:
You don't need to relock if you're s-off. Are you using a 2.0 or 3.0 usb port? Are you using a HTC cable? Are you in fastboot mode? Have you uninstalled HTC Sync Manager?
Sent from my Evita
Click to expand...
Click to collapse
aaronDroid80 said:
I'm doing the same thing, but to attempt to trade in my phone. I assume that after running the RUU I should relock the bootloader. I want to get rid of the red text.
*EDIT* nevermind. didn't realize that the RUU clears out the *TAMPERED* flag and gets rid of the red text. should be all good now.
Click to expand...
Click to collapse
You need to make sure the person you are trading with understands the phone is s-off and bootloader unlocked, and what that means.
---------- Post added at 01:57 PM ---------- Previous post was at 01:54 PM ----------
BBS678 said:
One more question, timmaaa: after flashing RUU, the recovery partition will be replaced with the stock recovery, and the S-OFF and boot loader will be kept as it is (based on what I learned from other posts of you). What if I need to flash CM again? I am confused because not many people are doing what I am. Thanks!
Click to expand...
Click to collapse
If you think you might still want to flash custom ROMs, you need to ask yourself why you want to return to stock in the first place.
Going back to stock if you are s-off, custom recovery, etc. is a step backward, not forward. Aside from getting on the correct hboot, firmware, etc. (or selling/trading your phone like the guy above), there is no benefit to going through all the hassle to running the RUU to get back to stock. Just flash a stock rooted ROM as timmaaa originally mentioned.
EDIT: Missed the part in the OP where it mentioned ISIS. See my response below (#13).
An update (for the forum): In fastboot mode, I have flashed Stock RUU successfully, without locking boot loader. After this, even in stock ROM, ISIS still doesn't work. I think it's caused by the SuperCID and S-OFF.
Timmaaa, do you know how I can SAFELY get SuperCID and S-OFF fixed? Thank you!
BBS678 said:
Hi, timmaaa, I am using USB2.0 on windows XP, with a regular cable, not in fastboot mode, and haven't uninstalled HTC Sync Manager.
I will try flash in fastboot mode again.
Click to expand...
Click to collapse
BBS678 said:
An update (for the forum): In fastboot mode, I have flashed Stock RUU successfully, without locking boot loader. After this, even in stock ROM, ISIS still doesn't work. I think it's caused by the SuperCID and S-OFF.
Timmaaa, do you know how I can SAFELY get SuperCID and S-OFF fixed? Thank you!
Click to expand...
Click to collapse
Reading around, root seems to be the only mod that interferes with ISIS. Its unlikely that s-off would interfere with ISIS. SuperCID? Its possible. Changing from SuperCID is very easy with fastboot. Just search for the command.
Also, be aware that you need a ISIS compatible SIM ("secure element SIM") available from your carrier.
http://www.att.com/shop/apps/isis-mobile-wallet.html#fbid=xHuv6S8moS4
Could be. HTC One X is not available on att.com now, so your link can't explain at this moment.
From here, https://www.paywithisis.com/get-started.html, it says AT&T HTC One X is compatible.
In addition, I do have a ISIS compatible SIM card from AT&T. The reason I suspect it is due to CID is that it is “heard" from this forum that ISIS doesn't work if you put an AT&T SIM card in the T-mobile version of GN3 (unlocked).
redpoint73 said:
Reading around, root seems to be the only mod that interferes with ISIS. Its unlikely that s-off would interfere with ISIS. SuperCID? I suppose its possible, but my gut says no. Especially in light of the following:
I'm thinking it more the issue that the AT&T One X is not a "ISIS ready phone": http://www.att.com/shop/apps/isis-mobile-wallet.html#fbid=xHuv6S8moS4
Also, be aware that you need a ISIS compatible SIM ("secure element SIM") available from your carrier.
Click to expand...
Click to collapse
BBS678 said:
Could be. HTC One X is not available on att.com now, so your link can't explain at this moment.
From here, https://www.paywithisis.com/get-started.html, it says AT&T HTC One X is compatible.
Click to expand...
Click to collapse
Yes, I later realized that One X is not available at all anymore from AT&T (and that it is supposed to be ISIS ready), and revised my above response accordingly.
BBS678 said:
In addition, I do have a ISIS compatible SIM card from AT&T. The reason I suspect it is due to CID is that it is “heard" from this forum that ISIS doesn't work if you put an AT&T SIM card in the T-mobile version of GN3 (unlocked).
Click to expand...
Click to collapse
It could also be that they are looking at the phone model number. So SuperCID is a possibility, but not certain.
Its easy to change from SuperCID with a simple fastboot command. Just search this forum for the proper syntax.
---------- Post added at 02:43 PM ---------- Previous post was at 02:32 PM ----------
Here is the command to change from CID:
fastboot oem writecid CWS__001
(note that CWS__001 has two underscores)
Thank you! I learned from this forum that changing S-OFF to S-ON is very risky, and currently S-OFF relies on a SuperCID, so I think it's also risky to change the CID back. Have you ever tried? I need more opinions on this before I take the risk.
BBS678 said:
Thank you! I learned from this forum that changing S-OFF to S-ON is very risky, and currently S-OFF relies on a SuperCID, so I think it's also risky to change the CID back. Have you ever tried? I need more opinions on this before I take the risk.
Click to expand...
Click to collapse
I honestly doubt s-off is blocking ISIS. S-off is exclusively an HTC invention, and I doubt ISIS would care about such a thing. I would recommend to leave s-off alone.
I wouldn't say its "risky" to change CID. As long as you still have s-off, I don't see any reason to still have SuperCID. But even so, you can still use the correct exploit to change back to SuperCID.
Hi, timmaaa, could you please shed some lights on this (change back to stock CID) please? Thanks!
here is my other post about ISIS: http://forum.xda-developers.com/showthread.php?p=49822333
redpoint73 said:
I honestly doubt s-off is blocking ISIS. S-off is exclusively an HTC invention, and I doubt ISIS would care about such a thing. I would recommend to leave s-off alone.
I wouldn't say its "risky" to change CID. As long as you still have s-off, I don't see any reason to still have SuperCID. But even so, you can still use the correct exploit to change back to SuperCID.
Click to expand...
Click to collapse
Everything that @redpoint73 has said is correct. There's pretty much no risk involved in changing your CID back to stock, having s-off does not rely on SuperCID. You can try changing your CID using the command that redpoint gave before.
There's pretty much no risk involved with going from s-off to s-on either. I don't know where you read that but I believe you're misunderstanding the information. Personally I wouldn't go back to s-on though because I don't believe that is affecting your ability to run ISIS. Plus getting s-off again can be tricky sometimes.
Sent from my Evita
I was s-off already before and somehow it shows s-on now. I've tried rumrumner, revone, and firewater. They all success but it doesn't show s-off on the bootloader. On firewater it shows there really isn't a helluva lot to do here. bye bye. Which I use google and found that it means I have s-off already. Could it be a bootloader problem? I tried fastboot getvar all and it shows s-on.
It's cos you followed the install guide of insertcoin and flashed the hboot that was suggested.. That boot is a modded one by cmviennau am guessing which hides s-on and removes tampered flag etc
Braddison said:
It's cos you followed the install guide of insertcoin and flashed the hboot that was suggested.. That boot is a modded one by cmviennau am guessing which hides s-on and removes tampered flag etc
Click to expand...
Click to collapse
Sorry for late reply. I tried to flash a fuu to upgrade firmware and it failed. So I took the att ruu and then I took the ota to upgrade to kit kat firmware (hboot 2.22). Are there anything I could do?
It also shows tempered so I don't think it's a hboot that I flashed. Could it be bootloader issue?
Hmm? Well if it's shown as s-on but you are In fact s-off surely that's a bonus?
Try an app that requires s-off to check if you are, or maybe try supercid as you need s-off for that. That's all can suggest.
Braddison said:
Hmm? Well if it's shown as s-on but you are In fact s-off surely that's a bonus?
Try an app that requires s-off to check if you are, or maybe try supercid as you need s-off for that. That's all can suggest.
Click to expand...
Click to collapse
Yup, I have s-off and are there any hboot that will show s-off that I could flash? I know that I got s-off because I was able to change cid.
Edit: It also doesn't show the deveoper purpose thing. I didn't flash any hboot. This is like amazing. I don't know what to say. I didn't flash any different hboot after taking the at&t 4.4.2 ota.