Hi folks
I managed to successfully S-off my mini a few weeks ago using Ramrunner however I've seen the threads about people using Revone.
I'm curious as to What the difference is between them both and is there any advantage to using one over the other?
Thanks
Braddison said:
Hi folks
I managed to successfully S-off my mini a few weeks ago using Ramrunner however I've seen the threads about people using Revone.
I'm curious as to What the difference is between them both and is there any advantage to using one over the other?
Thanks
Click to expand...
Click to collapse
I'm no expert in these things, but I'm guessing one s-off is the same as another s-off. I know revone also allows you to remove certain flags from the bootloader like "tampered". Dunno if rumrunner also does this. But that's all cosmetic. As long as your s-off worked your all good to go.
Sent from my HTC One using Xparent Green Tapatalk 2
yeah kinda thought they done the same thing. i might give the revone a bash as i would quite like to get rid of "tampered" in bootloader (a bit fussy with little things like that lol)
cheers
Braddison said:
yeah kinda thought they done the same thing. i might give the revone a bash as i would quite like to get rid of "tampered" in bootloader (a bit fussy with little things like that lol)
cheers
Click to expand...
Click to collapse
I'm proper OCD about things like that. But be careful because I don't know whether running 2 different s-off methods could conflict somehow. Maybe someone with a little more knowledge than me can confirm this or not?
Sent from my HTC One using Xparent Green Tapatalk 2
Revone is only for hboot 1.44 and rumrunner is for all other hboots. To use revone commands you have to be on 1.44 hboot
Hope this helps!
Sent from my SGH-I337 using xda app-developers app
@Klown80 Thanks for the info... Hmm I'm on Hboot 2.19.0000 so i will just leave it as is....not worth taking the risk of bricking for the sake of some red text. cheers
Braddison said:
@Klown80 Thanks for the info... Hmm I'm on Hboot 2.19.0000 so i will just leave it as is....not worth taking the risk of bricking for the sake of some red text. cheers
Click to expand...
Click to collapse
Yeah Hboot 1.44 is for the HTC One (M7), not the Mini. Lol, sorry I was on my phone earlier and didnt realize what forum I was in.
If you ever want to s-on back then go with revone. I use the revone method and it was easy.
I used rumrunner. Easy, as always.
what method is best for 2.19 hb?
Anybody know, these tools support all hboot? And if my device s- off, can i repair my IMEI?
Sent from my MI 2S using XDA Premium 4 mobile app
@abzboi - Can I ask you how you go back to S-ON?
Did you use this command after REVONE "fastboot oem writesecureflag 3"?
Thanks.
JaroslavHruska said:
@abzboi - Can I ask you how you go back to S-ON?
Did you use this command after REVONE "fastboot oem writesecureflag 3"?
Thanks.
Click to expand...
Click to collapse
Sorry for late reply. I was using REVONE before and I used fastboot oem writesecureflag 3. It should work for rum runner too. If not s-off it with REVONE again and do that. You'll have to downgrade to hboot 2.19 to use revone.
Do you have any steps how to restore to full stock status?
Sent from my HTC One mini using Tapatalk
Related
I have read the tut for brick/unbrick and downgrade hboot in dev section. And if I read it good there are 2 methods of downgrade hboot
1) brick/unbrick device and downgrade hboot (first post tutorial)
2) change CID and run RUU with lower hboot (second post tutorial)
If these are the options I think the second is the easiest way to downgrade hboot, but why are most people downgrading there devices by bricking it? Are there advantages or disadvantages for each method?
Edit I have hboot 2.15 and want downgrade to hboot 1.06
Sent from my HTC One S using xda app-developers app
Changing cid seems to have caused a few bricks for some people when trying to update to official JB OTA.
So would you advice to use the first method, although I already OTA updated to JB?
Sent from my HTC One S using xda app-developers app
I have downgrad by the first method and i have test all the way to hard brick my phone
And I can say that it's impossible to hard brick your phone with this tutorial.
willembos said:
So would you advice to use the first method, although I already OTA updated to JB?
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
I think the issue happend when the cid was already changed on ICS, and you tried to update to JB. Changing it when you already are on JB shouldnt be any problem.
But I havnt done any downgrading myself, so I dont know... Its just what Ive read.
willembos said:
I have read the tut for brick/unbrick and downgrade hboot in dev section. And if I read it good there are 2 methods of downgrade hboot
1) brick/unbrick device and downgrade hboot (first post tutorial)
2) change CID and run RUU with lower hboot (second post tutorial)
If these are the options I think the second is the easiest way to downgrade hboot, but why are most people downgrading there devices by bricking it? Are there advantages or disadvantages for each method?
Edit I have hboot 2.15 and want downgrade to hboot 1.06
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Just to be clear there is ONLY one way to downgrade hboot and that is with what you call option 1.
For what you describe as option 2 that ONLY applies AFTER you do option 1. If you want to run a RUU AFTER you've completed the downgrade you also have to do what is stated in the second post. Although it's much easier to use the the all in one tool kit reset your main version. This is achieved by and pressing the "Main version fix" button using the all in one toolkit. That will save you trouble of pulling mmcblkp23, hex editing it, then pushing it back to the phone.
Alright I understand it, I will read the tut again and try with my nooby knowledge of linux to downgrade
Sent from my HTC One S using xda app-developers app
willembos said:
Alright I understand it, I will read the tut again and try with my nooby knowledge of linux to downgrade
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
It's a pretty straight forward method. Try not to panic if you encounter a problem. The good news is that it's almost impossible to truly "brick" this phone. Just take a step back and reread the instructions paying close attention to the details. Post your questions about the process in the main thread, the people that follow it typically have a higher level of understanding then the forum overall.
If you don't have the required 10 posts to be able to post in the development sections go post some BS ones somewhere in XDA so you can get into that thread.
Oke thanks :thumbup:, it sounds doable to downgrade with these instructions
Sent from my HTC One S using xda app-developers app
And the tenth post
Sent from my HTC One S using xda app-developers app
I was told to change my CID to supercid and run a 2.31 RUU before doing the downgrade.
LibertyMonger said:
I was told to change my CID to supercid and run a 2.31 RUU before doing the downgrade.
Click to expand...
Click to collapse
I said that because at the time it would have made your phone up to date before doing the downgrade but he is already on JB so that RUU wont work and only needs to do the downgrade.
Darknites said:
I said that because at the time it would have made your phone up to date before doing the downgrade but he is already on JB so that RUU wont work and only needs to do the downgrade.
Click to expand...
Click to collapse
Oh ok.Yeah don't listen to me then! Lmao. I was told that before you started helping me and that's why I got swayed and changed my cid to HTC__001. But then you helped me to get supercid. Thanks Bud.
LibertyMonger said:
Oh ok.Yeah don't listen to me then! Lmao. I was told that before you started helping me and that's why I got swayed and changed my cid to HTC__001. But then you helped me to get supercid. Thanks Bud.
Click to expand...
Click to collapse
lol np dude.
Darknites said:
lol np dude.
Click to expand...
Click to collapse
so what about downgrade from 2.15? Anyone?
You could just s off. Its pretty easy
Sent from my Nexus 4 using xda app-developers app
Will soff enable to either downgrade hboot easier now or prevent the hassle of flashing boot.img first?
Sent from my Nexus 4 using xda app-developers app
joho5 said:
Will soff enable to either downgrade hboot easier now or prevent the hassle of flashing boot.img first?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Yes yes
joho5 said:
Will soff enable to either downgrade hboot easier now or prevent the hassle of flashing boot.img first?
Click to expand...
Click to collapse
Yes, but not automatically. You need to wait for the fixes to be released.
iElvis said:
Yes, but not automatically. You need to wait for the fixes to be released.
Click to expand...
Click to collapse
Awesome...thanks.
Sent from my Nexus 4 using xda app-developers app
Chongo confirmed he is able to flash a rom without the need for fastboot... Can anyone else confirm this? He has hboot 2.14, can someone with hboot 1.14 give it a shot?
Sent from my HTC One X using Tapatalk 2
joho5 said:
Awesome...thanks.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Actually, as IT mentioned, I think I'm wrong about flashing. I believe s-off removes all flashing restrictions. Downgrading is no longer necessary.
It's the fun stuff that will take some time.
iElvis said:
Actually, as IT mentioned, I think I'm wrong about flashing. I believe s-off removes all flashing restrictions. Downgrading is no longer necessary.
It's the fun stuff that will take some time.
Click to expand...
Click to collapse
What can we expect now that we have s-off? Or rather, what would YOU like to see. I'm curious what the typical One X user wish list would be?
Also, I saw you post in the boot animations thread. Did you get it to work? Which animation did you pick?
i still haven't ran the s-off exploit yet. i also slept over 30 hours and missed the release. i was going to wait to run it until some hacks came out that use s-off but i guess not having to fastboot boot.img is good enough. ill run it in abit seems super easy, looks like basically a hacked up ruu =) i guess that is why it is called facepalm.
I see the ruu contains a radio does it cause any problems with at&t?
DvineLord said:
I see the ruu contains a radio does it cause any problems with at&t?
Click to expand...
Click to collapse
Interesting. S-Off means the radio is fully flashable (even for those on hboot 1.14). So I would think you can just flash another radio, if there are any issues.
DvineLord said:
i also slept over 30 hours and missed the release.?
Click to expand...
Click to collapse
Whoa. Sick or something? Or just sleep a lot?
'busa said:
What can we expect now that we have s-off? Or rather, what would YOU like to see. I'm curious what the typical One X user wish list would be?
Click to expand...
Click to collapse
Dual boot, anyone? I would love to be able to go both ways (Sense and AOSP )
iElvis said:
Dual boot, anyone? I would love to be able to go both ways (Sense and AOSP )
Click to expand...
Click to collapse
+100000000 yes!
Sent from my One X using Tapatalk 2
iElvis said:
Dual boot, anyone? I would love to be able to go both ways (Sense and AOSP )
Click to expand...
Click to collapse
totally forgot about dual boot, been wanting to do this forever.
iElvis said:
Dual boot, anyone? I would love to be able to go both ways (Sense and AOSP )
Click to expand...
Click to collapse
And upcoming Ubuntu?
DvineLord said:
i still haven't ran the s-off exploit yet. i also slept over 30 hours and missed the release. i was going to wait to run it until some hacks came out that use s-off but i guess not having to fastboot boot.img is good enough. ill run it in abit seems super easy, looks like basically a hacked up ruu =) i guess that is why it is called facepalm.
I see the ruu contains a radio does it cause any problems with at&t?
Click to expand...
Click to collapse
The ruu doesn't actually install. It would need to run that a few times to fully install it. Basically we are telling the phone we are going to RUU, which in HTC's stupidity, unlocks the emmc partitions to be writable. Then the RUU fails when it finds superCID. So we cancel out of the ruu status, but the emmc partitions are still unlocked, and we turn the security flash off with soffbin3. And ya, that's why it's called facepalm
DvineLord said:
totally forgot about dual boot, been wanting to do this forever.
Click to expand...
Click to collapse
Are yall using that dual boot program from the market? And is it confirmed working?
Sent from my now S-Off HTC OneXL
im running the 1.85 now for the heck of it. i found that fastboot oem lock works differently then i remember it, you issue the command and it goes to a black screen. just make sure you go back into fastboot before running the ruu.
elfysrfr said:
Are yall using that dual boot program from the market? And is it confirmed working?
Sent from my now S-Off HTC OneXL
Click to expand...
Click to collapse
https://play.google.com/store/apps/...SwyLDEsImNvbS5kcngyLmJvb3RtYW5hZ2VyLmxpdGUiXQ..
You mean this program? boot manager lite?
954wrecker said:
https://play.google.com/store/apps/...SwyLDEsImNvbS5kcngyLmJvb3RtYW5hZ2VyLmxpdGUiXQ..
You mean this program? boot manager lite?
Click to expand...
Click to collapse
That's the one. I tried using it a long time ago with one of my old HTC's and it never acted right for me.
Just wondering if anyone got any dual boot working yet.
Sent from my now S-Off HTC OneXL
Oooh, I would love to be able to dual-boot between Sense and AOSP...hopefully that's now a real possibility.
InflatedTitan said:
Chongo confirmed he is able to flash a rom without the need for fastboot... Can anyone else confirm this? He has hboot 2.14, can someone with hboot 1.14 give it a shot?
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
I'm running hboot 1.14 and can confirm that I've flashed CM10.1 (and restored a nandroid including the boot partition) without needing to fastboot flash the boot.img.
Seems like those running 1.14 are pretty rare around these parts...or maybe just quiet.
Edit: Restore was to AOSPA 2.54 (JB 4.1.2).
With S-off achieved, it seems like it would be worthwhile to bring everything up to the latest version. Is it possible to just push 2.14 to your phone without relocking or any of that jazz?
Why would you want the latest hboot? It offers nothing useful.
Now the 2.14 users can downgrade firmware to get rid of the touch panel junk
mirGantrophy said:
Why would you want the latest hboot? It offers nothing useful.]
Click to expand...
Click to collapse
Well, that was my unstated question: Is there any reason to do it? I guess the answer is no.
iElvis said:
Well, that was my unstated question: Is there any reason to do it? I guess the answer is no.
Click to expand...
Click to collapse
well s-off turns off security.. so 1.14 users have no reason to downgrade, but 2.14 users can downgrade and then RUU downgrade to fix the touch screen issue
Grim what happened to your pink hair?
Sent from my VENOMized HoxL
area51avenger said:
Grim what happened to your pink hair?
Sent from my VENOMized HoxL
Click to expand...
Click to collapse
Same place where my hox is going.
mirGantrophy said:
well s-off turns off security.. so 1.14 users have no reason to downgrade, but 2.14 users can downgrade and then RUU downgrade to fix the touch screen issue
Click to expand...
Click to collapse
Why do we have no reason to downgrade?
Sent from my HTC One XL using xda app-developers app
dethpikil said:
Why do we have no reason to downgrade?
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
because 1.14 and 2.14 hboot prevented kernel/radio flashing in recovery.. with s-off, every partition is unlocked with no write protection.. so now you can flash in recovery on any hboot
mirGantrophy said:
because 1.14 and 2.14 hboot prevented kernel/radio flashing in recovery.. with s-off, every partition is unlocked with no write protection.. so now you can flash in recovery on any hboot
Click to expand...
Click to collapse
Wait, I don't have to do anything special apart from achieving soff to avoid flashing the bootimg separately? Or do you mean that it's now possible, but waiting on a near future fix?
Sent from my HTC One XL using xda app-developers app
dethpikil said:
Wait, I don't have to do anything special apart from achieving soff to avoid flashing the bootimg separately? Or do you mean that it's now possible, but waiting on a near future fix?
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
if you are s-off at this very moment... you can flash any rom right now, and will NOT have to worry about the boot.img.. except hboot 2.14, they have a few extra steps
say bye bye to fastboot and flashgui
iElvis said:
With S-off achieved, it seems like it would be worthwhile to bring everything up to the latest version. Is it possible to just push 2.14 to your phone without relocking or any of that jazz?
Click to expand...
Click to collapse
Would be a good idea to try the updated firmware and see if it makes any diff/
At least for the ones that dont use aosp roms.
InflatedTitan said:
if you are s-off at this very moment... you can flash any rom right now, and will NOT have to worry about the boot.img.. except hboot 2.14, they have a few extra steps
say bye bye to fastboot and flashgui
Click to expand...
Click to collapse
What extra steps are needed with 2.14?
Sent from my Elemental Venomized S-off HTC One XL
majortaylor said:
What extra steps are needed with 2.14?
Sent from my Elemental Venomized S-off HTC One XL
Click to expand...
Click to collapse
none if s-off
I thought touchscreen didn't work with aosp when on 2.14? Soff fixes this also? If so I think ima update the sh¡t out of this phone
Sent from my HTC One X using Tapatalk 2
InflatedTitan said:
I thought touchscreen didn't work with aosp when on 2.14? Soff fixes this also? If so I think ima update the sh¡t out of this phone
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
no.. the hboot has nothing to do with the touch screen. that's the firmware from something else
So if I ruu.... I Take the highest update, keep s-off, fastboot twrp and flash roms no problems?
Sent from my HTC One X using Tapatalk 2
InflatedTitan said:
So if I ruu.... I Take the highest update, keep s-off, fastboot twrp and flash roms no problems?
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
Yeah,
but which ruu with the latest firmware?
I dont think there's any available.
I'm on 1.85, hboot 1.09..
I was just gonna run the 1.85 ruu... Take the 2.20 ota (or whichever one is most recent)
Once I'm updated, since I'm s-off, I figure I could easily fastboot twrp recovery... Flash rooted Rom.
Any objections? This is my first s-off device so I'm a noob
Sent from my HTC One X using Tapatalk 2
InflatedTitan said:
So if I ruu.... I Take the highest update, keep s-off, fastboot twrp and flash roms no problems?
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
if you RUU to the JB update you WONT have touchscreen on AOSP. doesnt matter if you are s-off
mirGantrophy said:
if you RUU to the JB update you WONT have touchscreen on AOSP. doesnt matter if you are s-off
Click to expand...
Click to collapse
Well damn Grimm you just said a few posts back it didn't matter!!! Haha ima stay put, I'm too confused so I'll play it safe
Anyway I'm on att, so I wouldnt recieve the JB ota right?
Sent from my HTC One X using Tapatalk 2
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!
I don't plan on re-locking bootloader, so I was wondering if changing my CID back to stock would cause any problems. Didn't think it would but I thought I should ask around. Also, AT&T's CID is CWS__001, right?
Thanks
Doesn't matter if you are s-off. Why do you want to change it?
DvineLord said:
Doesn't matter if you are s-off. Why do you want to change it?
Click to expand...
Click to collapse
Eh, just in case I might need to send it in for hardware repairs. I edited my hboot to look exactly like stock. This was the last thing to make it perfect lol
Thanks for the reply. I feel terrible asking questions here cause I know I should know this stuff by now and all you guys that help out over here get enough of this crap as it is.
jacobas92 said:
I don't plan on re-locking bootloader, so I was wondering if changing my CID back to stock would cause any problems. Didn't think it would but I thought I should ask around. Also, AT&T's CID is CWS__001, right?
Thanks
Click to expand...
Click to collapse
Yeah that's the cid.
Fastboot oem writecid CWS_001
Think that's the command
Sent from my HTC One XL using xda premium
*CWS__001
Sent from my Evita
Don't forget the second underscore. There's 8 characters in CID.
Sent from my evita
Thanks guys, I got it. Haha now to install philz touch recovery and theme it to mimic stock recovery.
Sent from my HTC One X using xda premium