I bought this phone outright, and I don't like the Telstra network so I put an Optus SIM in. Which works just fine, however I now have an issue which may or may not be related. I have unlocked my bootloader, and have obtained root. I cannot get s-off however, tried all the methods in this forum. And when I try to install a new Rom, such as cm10 and all nightly versions, venom viper, and all other Roms I have tried I cannot get passed the start up logo (or I just get a pure black screen). Yes I have waited and waited for extended periods of time but it won't load. No I'm not new to rooted phones, and have followed all insructions properly. Pls help me, I really hate all the Telstra bloatware on my phone.
Sent from my HTC One XL using xda app-developers app
you have to fastboot flash the boot.img when you are s-on
Only problem is I used that stupid one xl one click toolbox for my root. Which has completely stuffed me up.I should have done it the hard way like I did with my incredible s. I just got lazy. Don't suppose you know how to get s-off, without the one click fixes. Unfortunately they arnt working on this phone to acheive s-off
Sent from my HTC One XL using xda app-developers app
pretty sure you need supercid to s-off here is the s-off thread
http://forum.xda-developers.com/showthread.php?t=2155071
and how to get supercid on non att
http://forum.xda-developers.com/showthread.php?t=2212737
Thank you will give it a try tomorrow.
Sent from my HTC One XL using xda app-developers app
your welcome
jerrycoffman45 said:
you have to fastboot flash the boot.img when you are s-on
Click to expand...
Click to collapse
Not necessarily. It depends on your hboot version I believe.
I've never had to flash the boot image and I haven't done s-off.
@OP - did you need to s-off for any specific reason? You don't need to do this to flash a custom ROM. It's not required unless you want to reove the tampered text from the boot loader.
It makes life easier to have s-off. Besides I have issues with not having full access to something I have bought outright....lol
Sent from my HTC One XL using xda app-developers app
I s-off'd my HOXL because it makes it much safer from my own boneheaded mistakes. If I had done something silly like flashing the OTA RUU then I wouldn't be completely screwed.
Sent from my HOXL!
Related
oi.
Have found 2 topics on my matter, but none offer a reasonable explanation, so I'm going to ask again in hope of getting one.
http://forum.xda-developers.com/showthread.php?t=1084683
http://forum.xda-developers.com/showthread.php?t=491350
The later one is only for some G1, so I guess it'd brick my phone, which I do not really feel doing.
So basically my question is:
1. After using Revolutionary to get s-off, will I EVER be able to get back to stock, i.e. S-ON, firmware?
2. Also, if I would use Revolutionary and HTC decides to push out an unlocked bootrom, can I switch to that one afterwards?
3. If the above is true, would some well-experienced user post a guide how to gain factory-like phone ?
This one talks about s-off and s-on. Not sure about switching bootloaders though.
http://forum.xda-developers.com/showthread.php?t=1192565
Just run an RUU to undo it.
Sent from my PG86100 using XDA Premium App
In that thread are people saying that ruu does not restore warranty i'll wait for htc to officially unlock the device then
Thanks for the insight
Sent from my HTC Sensation Z710e using XDA Premium App
Hi, as my nexus s has recently been lost i decided its time to put a custom rom on my one s, i was about to unlock the bl on it and noticed the tamper banner on the bl screen, its also s-off with a cid of 11111111, i have attatched a pic of the bl screen for reference, As far as i know the one series cant as of yet cannot be s-off'ed like the older htc devices, how would this be possible on my device? It was bought from brand new quite a while ago and until now has always run the the stock rom with no root etcetc.. The only thing i can think of is i had it unlocked not long after purchasing it but not sure what method the shop used. When i access the bootloader on my one s i can choose what to do fastboot or recovery etc etc but on this one s i get the red htc disclaimer like pictured below when i select recovery, i have the latest cwm touch flashed but cannot get into it.. So how can i access recovery?? any help would be appreciated
Sorry about image quality its taken on an old webcam
Your bootloader is still locked, that would be my guess. That's why the pink banner at the top says "locked". Unlock that and you should have access to recovery.
Sent from my H1S using XDA Premium.
I have since unlocked the bootloader, and still getting the same problem, recovery just won't load, as with old HTC devices such as sensation, desire s, DHD bootloader unlock was not relevant if you had s-off not sure about the one series, my main question is how it's become s-off in the first place
Sent from my HTC One S using xda premium
Keep the bootloader locked, don't use the HTCDev method to unlock it. You're extremely lucky to have S-OFF, this means that you can easily get your warranty back running an RUU, changing CID and fastboot oem writesecureflag 3. This will make it S-ON again, and no trace of it being S-OFF will be there.
The current method is HTCDev, which submits a Unique Device Identifier so they can decline your warranty due to an unlocked bootloader.
S-OFF is better than HTCDev for flashing ROMs, as it means you don't have to flash the boot.img seperately.
usaff22 said:
Keep the bootloader locked, don't use the HTCDev method to unlock it. You're extremely lucky to have S-OFF, this means that you can easily get your warranty back running an RUU, changing CID and fastboot oem writesecureflag 3. This will make it S-ON again, and no trace of it being S-OFF will be there.
The current method is HTCDev, which submits a Unique Device Identifier so they can decline your warranty due to an unlocked bootloader.
S-OFF is better than HTCDev for flashing ROMs, as it means you don't have to flash the boot.img seperately.
Click to expand...
Click to collapse
Hi thanks for your responce. Since I took those pics the bl has been unlocked, warranty I'm not too fussed about, the main issue I have is how its become s-off in the first place, and when I try to boot cwm I get the red message pictured in my first post, I've tried to flash a recovery via fastboot and.Rom manager and no luck what so ever, I've tried com touch and cwm standard aswell as twrp I have the s4 device and Im stuck lol. Jeez I miss my nexus already
Sent from my HTC One S using xda premium
PEP-C is a friend of mine, I've just purchased the above mentioned one s for £150 but that's irrelevant, I have owned HTC devices before but never have I seen that red message pictured in the first post, it appears every time the phone boots up, any suggestions? My mate said he's had it from new but I'm not so sure.
Sent from my HTC One S using xda premium
furrabbit.nh said:
PEP-C is a friend of mine, I've just purchased the above mentioned one s for £150 but that's irrelevant, I have owned HTC devices before but never have I seen that red message pictured in the first post, it appears every time the phone boots up, any suggestions? My mate said he's had it from new but I'm not so sure.
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
Its a new thing HTC is doing. Normally pops up when you have a modified kernel/recovery.
Sent from my HTC One S using xda premium
Posted in error
Sent from my HTC One S using xda premium
usaff22 said:
The current method is HTCDev, which submits a Unique Device Identifier so they can decline your warranty due to an unlocked bootloader.
Click to expand...
Click to collapse
Man... I hate HTC sometimes haha
Sent from my SGH-T999 using xda premium
Sgt-Hartley said:
Ahh thanks for clearing that up, I did wonder, all though it does show up even on a fully stock system, no root, stock recovery, as you can see from the pics in first post the BL was still locked when those snaps were taken, even though its s-off it would not let me flash a recovery for him without unlocking the BL after I typed the fastboot command it said not allowed or something similar.
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
I have no idea how its like that, but that's normally why it shows up.
Maybe it has to do with it being S-off?
I do know however, that with S-off you can remove the red text. I'm sure someone here would know what to do.
Sent from my HTC One S using xda premium
xxquicksh0txx said:
I have no idea how its like that, but that's normally why it shows up.
Maybe it has to do with it being S-off?
I do know however, that with S-off you can remove the red text. I'm sure someone here would know what to do.
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
You can remove it, but messing around with it could brick your phone. I wouldn't even think about it.
Sent from my HTC One S using Tapatalk 2
---------- Post added at 08:23 AM ---------- Previous post was at 08:21 AM ----------
PEP-C said:
Hi thanks for your responce. Since I took those pics the bl has been unlocked, warranty I'm not too fussed about, the main issue I have is how its become s-off in the first place, and when I try to boot cwm I get the red message pictured in my first post, I've tried to flash a recovery via fastboot and.Rom manager and no luck what so ever, I've tried com touch and cwm standard aswell as twrp I have the s4 device and Im stuck lol. Jeez I miss my nexus already
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
Try flashing a stock recovery, then flash the one from modaco. Apparently that one works best
Sent from my HTC One S using Tapatalk 2
It is a s4 device right ? According to the hboot its a s4
Sent from my HTC VLE_U using xda app-developers app
Mine is s off too and also with the red text when booting
Sent from my HTC One S using xda premium
gock said:
Mine is s off too and also with the red text when booting
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
Consider yourself extremely lucky too, I'd die to have S-OFF
Sent from my HTC One S using Tapatalk 2
Sure does seem to be a rash of s-off devices popping up lately. Maybe we'll get lucky and somebody will wander over to the forums and help us with the method(s).
diabolusmiles said:
Sure does seem to be a rash of s-off devices popping up lately. Maybe we'll get lucky and somebody will wander over to the forums and help us with the method(s).
Click to expand...
Click to collapse
Why cant a dev ever get lucky lol.
Darknites said:
Why cant a dev ever get lucky lol.
Click to expand...
Click to collapse
Even if a Dev gets lucky, there's nothing no one can do about it. It's how it got there that's important, not whether you have it or not.
Sent from my HTC One S using Tapatalk 2
gock said:
Mine is s off too and also with the red text when booting
Click to expand...
Click to collapse
You get the red text if your boot image is not signed by HTC. Regardless of s-on/off.
And afaik, you get **TAMPERED** if your recovery image is not HTC signed.
touch of jobo said:
You get the red text if your boot image is not signed by HTC. Regardless of s-on/off.
And afaik, you get **TAMPERED** if your recovery image is not HTC signed.
Click to expand...
Click to collapse
I have ***TAMPERED *** and I have the stock recovery and a locked bootloader. The only thing I have is su.bin and superuser.apk
Sent from my HTC One S using Tapatalk 2
usaff22 said:
I have ***TAMPERED *** and I have the stock recovery and a locked bootloader. The only thing I have is su.bin and superuser.apk
Sent from my HTC One S using Tapatalk 2
Click to expand...
Click to collapse
The s-off device of mine had tampered before I even unlocked the bootloader or even flashed custom recovery, I only bought it to sell but no I'm unsure, the one s and one x both seem to be.doing well even without s-off. As for the red message it only appears with custom Rom on my device, if on stock its not there.
Edit: Just to clear things up I now own the device mentioned in the first post
Edit 2: does anyone know if xtc clip can s-off the one series? Can't find any updated info
Sent from my HTC One S using xda premium
---------- Post added at 06:11 PM ---------- Previous post was at 06:07 PM ----------
gock said:
Mine is s off too and also with the red text when booting
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
Did you ever get your phone sim unlocked via a third party company, if so what method did they use?
Sent From My HTC One S-Off
---------- Post added at 06:17 PM ---------- Previous post was at 06:11 PM ----------
aditya. said:
It is a s4 device right ? According to the hboot its a s4
Sent from my HTC VLE_U using xda app-developers app
Click to expand...
Click to collapse
Yes it's s4
Sent From My HTC One S-Off
Does anybody have AT&T stock 2.20 nandroid backup? I'm trying to make my phone complete stock for a reason. I cannot flash RUU, because previously I flashed Asian 2.42 RUU, and that's why its not letting me to downgrade even with super cid. Backup would be appreciated if anybody can provide it.
Thanks in advance.
Sent from my HTC One XL using xda premium
Nandroid is not going to return you to stock like an RUU would. You would still be rooted and have custom recovery.
What you are asking for would not really have any different result than flashing a stock rooted ROM, so you can do that, if you just want to get the ROM back to stock.
redpoint73 said:
Nandroid is not going to return you to stock like an RUU would. You would still be rooted and have custom recovery.
What you are asking for would not really have any different result than flashing a stock rooted ROM, so you can do that, if you just want to get the ROM back to stock.
Click to expand...
Click to collapse
To be more specific, I want complete stock, non rooted, odexed and with AT&T bloatware backup, that some people my have as a backup.
Sent from my HTC One XL using xda premium
kaiser347 said:
To be more specific, I want complete stock, non rooted, odexed and with AT&T bloatware backup, that some people my have as a backup.
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
No one is going to give you their nandroid, since that would have all their personal settings and Google password.
The 2.20 AT&T RUU should work. Are you sure you've got HTC sync installed?
iElvis said:
No one is going to give you their nandroid, since that would have all their personal settings and Google password.
The 2.20 AT&T RUU should work. Are you sure you've got HTC sync installed?
Click to expand...
Click to collapse
I'm not noob, and I pretty sure know how to run RUU. I have all the drivers installed. And currently running JB custom ROM on 2.42 ICS firmware with 1.14 bootloader. I can not run AT&T 2.20 RUU, because I will getting bootloader error. You will have same problem if you run different region RUUs with newer firmware. I don't want personal information. Some people may have clean stock nandroid without any personal stuff.
I had the same problem with my ONE S and there were people who had such nandroids, and they did help me with it.
That's why we call it community. We try to help each other as much as we can.
Sent from my HTC One XL using xda premium
kaiser347 said:
I'm not noob, and I pretty sure know how to run RUU. I have all the drivers installed.
Click to expand...
Click to collapse
Relax man. He's asking for the easy stuff first, since the best solution is very often the easiest one. Better to ask the seemingly 'obvious' question right off the bat, rather than go down some complicated road needlessly.
Re-installing HTC Sync fixes up the issue for the huge majority of people with RUU errors. Not in your case, as you are correct that trying to run the RUU with a lower hboot version number that what is already installed, will cause it to fail. But he is just trying to be helpful.
redpoint73 said:
Relax man. He's asking for the easy stuff first, since the best solution is very often the easiest one. Better to ask the seemingly 'obvious' question right off the bat, rather than go down some complicated road needlessly.
Re-installing HTC Sync fixes up the issue for the huge majority of people with RUU errors. Not in your case, as you are correct that trying to run the RUU with a lower hboot version number that what is already installed, will cause it to fail. But he is just trying to be helpful.
Click to expand...
Click to collapse
I'm relaxed, thank you for understanding me. The reason for this request is that there might be, and its might be an update from At&t in a future eventually. I'm just trying to be prepared for this, because I can not run 2.20 RUU and the only way to get this future update would be from a system setting. I like clean stock, rooted Rom with all the unneeded apps uninstalled. Once I got the update I can just unlock the bootloader and root it and install insecure kernel along.
Sent from my HTC One XL using xda premium
Here is a ruu link, hope it helps
http://forum.xda-developers.com/showthread.php?t=1671237
Sent from my HTC One XL using xda premium
I didnt't realize 2.42 contained an updated hboot. That would obviously prevent running an earlier ruu. Sorry for the confusion.
iElvis said:
I didnt't realize 2.42 contained an updated hboot. That would obviously prevent running an earlier ruu. Sorry for the confusion.
Click to expand...
Click to collapse
It seems hboot is the same 1.14 in both 2.20 and 2.42 RUUs. I think with the latter some other partitions were updated as well, which prevent downgrading.
Sent from my HTC One XL using xda premium
DESERT.TECH said:
Here is a ruu link, hope it helps
http://forum.xda-developers.com/showthread.php?t=1671237
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
Thank you for the link. I do have a RUU. But can not install.
Sent from my HTC One XL using xda premium
So i got my phone's bootloader relock and i flash the stock recovery but i cant access it i dont know why but whatever thats my issue
I wanna go back to stock but i cant run the RUU bcuz i have a Mac
So is there anyway to flash a stock ruu or rom from fastboot or the bootloader i remember doing it in the htc evo once and it worked like a charm
I need your help guys im trying to bring back my phone bcuz the power button is not working properly
So yea thats my issue any help or recommendations are much appreciated thnks
Sent from my HTC One XL using xda app-developers app
Doesn't ruu require windows? You try a virtual machine to emulate windows. What exactly are you trying to do? Are you trying to achieve s off?
Sent from my Carbon-ize Evita using xda-developers app
yankee minaj said:
So i got my phone's bootloader relock and i flash the stock recovery but i cant access it i dont know why but whatever thats my issue
I wanna go back to stock but i cant run the RUU bcuz i have a Mac
So is there anyway to flash a stock ruu or rom from fastboot or the bootloader i remember doing it in the htc evo once and it worked like a charm
I need your help guys im trying to bring back my phone bcuz the power button is not working properly
So yea thats my issue any help or recommendations are much appreciated thnks
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
Are you S-OFF already?
Is this an AT&T one X? you would have had to supercid to root, if you RUU and you are not S-OFF you will brick.
To RUU, you'll need windows be it through a VM or another PC.
You can flash an OTA through stock recovery if you download the zip but if you're superCID that will also brick you.
I have S-on Relock hboot 1.09
I guess im gonna ask a friend to let me borough hes windows laptop i think thats the easiest way to go back
Sent from my HTC One XL using xda app-developers app
exad said:
Are you S-OFF already?
Is this an AT&T one X? you would have had to supercid to root, if you RUU and you are not S-OFF you will brick.
To RUU, you'll need windows be it through a VM or another PC.
You can flash an OTA through stock recovery if you download the zip but if you're superCID that will also brick you.
Click to expand...
Click to collapse
And the SuperCid i really dont know about that but i try root checker and i still have root
Sent from my HTC One XL using xda app-developers app
yankee minaj said:
I have S-on Relock hboot 1.09
I guess im gonna ask a friend to let me borough hes windows laptop i think thats the easiest way to go back
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
If it's an AT&T phone it definately is SuperCID and will brick if you RUU unless you S-OFF first.
So what do you recommend mate do i have to go and do the s-off
Sent from my HTC One XL using xda app-developers app
yankee minaj said:
So what do you recommend mate do i have to go and do the s-off
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
Yep. re-unlock, flash recovery, flash a stock rooted rom, S-OFF, then RUU
exad said:
Yep. re-unlock, flash recovery, flash a stock rooted rom, S-OFF, then RUU
Click to expand...
Click to collapse
ok so i am S-off and i just run the ruu and thats it? and by the way what kind of Ruu should i run im running JB custom rom
dont ask me why or how i got S-off i just want my phone to be replace
thanks mate
Just run any one xl ruu for your carrier. There's a few ruu threads if you click the link to the resource compilation thread in my signature and scroll down to the RUU section.
Sent from my One X using xda app-developers app
Scenario:
HTC One XL from ATT, running 3.18 software. I have applied SuperCID (verified 11111111), procured unlock token from HTC Dev, unlocked booloader (confirmed "TAMPERED", "UNLOCKED" at bootloader), installed custom recovery (TWPR 2.3.3.1).
The problem is, when I push any custom ROMs to the device, and reboot, they get stuck in boot indefinitely. For example, Cyanogenmod 10.1 just shows me spinning splash screen. I have perused the relevant forums/posts, and can't seem to get past this. I had the same issue with the 2.20 software, as well.
I have a working backup of the stock ROM, but I despise the bloatware ATT included, and would really like to get rid of the stock ROm, if at ALL possible.
If anyone can shed some light on this, I'd be grateful!
Sticky: http://forum.xda-developers.com/showthread.php?t=2136172
q18
I should also mention, aosp will not work with your hboot if it's 2.14 unless you s-off and downgrade your touchscreen firmware.
Sent from my HTC One X using xda app-developers app
Thanks
exad said:
Sticky: http://forum.xda-developers.com/showthread.php?t=2136172
q18
I should also mention, aosp will not work with your hboot if it's 2.14 unless you s-off and downgrade your touchscreen firmware.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Thanks you, good sir. Hboot IS 2.14, in fact. I have been attempting to S-off the device, but failing in that, as well. I will research taht some more. Again, thank you for your input!