As there are more and more firmware coming, people will be installing them more and more... Same thing about people that wants to go back to stock. This thread could be considered useless and will make people say "yeah man, I knew it I'm not so stupid" that's OK! You're right.
I just wanted to remember that you shouldn't ever ever ever S-ON your HBOOT if it is edited by someone else! This will immediately brick your device, if you want to check do it. You need first to replace your current HBOOT with a stock one and then you'll be good to go.
@Sneakyghost:
* Before resetting Security to ON (S-ON) you MUST flash a stock/unchanged HBOOT! Your device will brick instantly if you set Security ON and reboot on a modified HBOOT!
Click to expand...
Click to collapse
In all the hboot threads it clearly states this
And it's not locking your bootloader that bricks it, it's s-on that does it
Sent from my HTC One using Tapatalk
superchilpil said:
In all the hboot threads it clearly states this
And it's not locking your bootloader that bricks it, it's s-on that does it
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
I thought it was if you: fastboot oem writesecureflag -3 it will check if it's a modified hboot.
Sent from my HTC One using Tapatalk
I knew That simply locking the hboot would have bricked the device
Sent from my HTC One using XDA Premium 4 mobile app
@superchilpil you were right, I've edited the OP now and it should be ok now... :good:
matt95 said:
@superchilpil you were right, I've edited the OP now and it should be ok now... :good:
Click to expand...
Click to collapse
Wow, I think I've read about 20 threads so far about this, and this is the first time I've seen this corrected... Lots of threads always mentioned locking the bootloader as the issue if you don't have stock hboot.
I actually had a few questions about this,
1. Does the hboot version have to match that of the firmware ? ( 1.54 for 2.24.x.x for example ?) or does it simply have to be any stock hboot ?
2. Are there any differences between hboot for various carriers ?
3. I've read multiple times that running an RUU will not allow you to downgrade unless you have superCID, I don't understand this. I thought the RUU wouldn't run if the CID didn't match. From what I had understood previous to reading that is simply that an RUU cannot be used to downgrade the firmware or the hboot version, that can only be done manually with S-off
Thank you for your time and for the clarification!
ieldra said:
Wow, I think I've read about 20 threads so far about this, and this is the first time I've seen this corrected... Lots of threads always mentioned locking the bootloader as the issue if you don't have stock hboot.
I actually had a few questions about this,
1. Does the hboot version have to match that of the firmware ? ( 1.54 for 2.24.x.x for example ?) or does it simply have to be any stock hboot ?
2. Are there any differences between hboot for various carriers ?
3. I've read multiple times that running an RUU will not allow you to downgrade unless you have superCID, I don't understand this. I thought the RUU wouldn't run if the CID didn't match. From what I had understood previous to reading that is simply that an RUU cannot be used to downgrade the firmware or the hboot version, that can only be done manually with S-off
Thank you for your time and for the clarification!
Click to expand...
Click to collapse
1. Matching firmware/hboot is always the best route possible as it can minimize any issues that may arise, so I suggest it.
2.As far as compatibility issues there aren't any, the hardware on all these devices are almost exactly alike so running another hboot is quite possible. Although I suggest keeping to your carriers hboot to minimize issues. Or atleast keep a backup of yours
3.You can downgrade only if you are S-OFF, otherwise you can only upgrade or flash the corresponding firmware you're currently on. SuperCID only allows you to flash RUUs/firmware from other carriers or regions. CID stands for Carrier Identification. So even with supercid you can't downgrade, there are security measures in place to stop you from downgrading you hboot without s-off, it either won't write or you will end up with a brick.
Sent from my HTC One using Tapatalk
Related
Hey all. I've been unable to flash any kernels except for the stock one and Baconbits. All others but my phone in a perpetual bootloop. I'm using compatible kernels, but it seems any that write a boot.img makes this happen (though I may be wrong on that). Does this have anything to do with the fact I have HBOOT Version .82? I've noticed in most people's screenshots that after they did S-Off, they have .76. Could this be the issue and if so, ho can I downgrade it? Thanks!
Anyone? I've looked around but haven't heard anything with this specific problem.
Sent from my T-Mobile G2 using XDA App
0.76 is the engineering hboot for the G2, with S-OFF. I recommend though that you look at the new "gfree" method of getting S-OFF, which also gives you SIM unlock, SuperCID etc. It's much safer than the eng hboot, though the eng hboot does have some extra functionality.
I don't need the SIM unlock, so I didn't think the gfree method was needed. With that though, I'm on HBOOT .82, and have S-OFF. How can I get it to .76 and S-OFF?
You've got a G2, not a DZ, right ? I'm not sure how you can have the .82 HBOOT and have S-OFF unless you've run gfree ? I might be missing something though.
The gfree method is a much safer way of getting S-OFF, even if you don't need to SIM unlock.
steviewevie said:
You've got a G2, not a DZ, right ? I'm not sure how you can have the .82 HBOOT and have S-OFF unless you've run gfree ? I might be missing something though.
The gfree method is a much safer way of getting S-OFF, even if you don't need to SIM unlock.
Click to expand...
Click to collapse
Yes I have a G2, and I used this http://forum.xda-developers.com/showthread.php?t=833965 to get S-OFF. Am I supposed to have .82? The reason I doubted myself in the first place is that all the screenshots I've seen people have .76 and S-OFF.
phoenx06 said:
Yes I have a G2, and I used this http://forum.xda-developers.com/showthread.php?t=833965 to get S-OFF. Am I supposed to have .82? The reason I doubted myself in the first place is that all the screenshots I've seen people have .76 and S-OFF.
Click to expand...
Click to collapse
I can only assume there's another engineering hboot version, at 0.82 with S-OFF for the G2 ? Sorry, having a DZ myself I'm not so familiar with the exact HBOOT levels on the G2 (since that's one difference from the DZ), but I'm sure someone else can help you with that shortly.
I recommend using gfree though, because with a proper radio S-OFF (not a kind of "fake" S-OFF via HBOOT) it will be a lot easier to recover your phone if somehow you semi-brick it.
steviewevie said:
I can only assume there's another engineering hboot version, at 0.82 with S-OFF for the G2 ? Sorry, having a DZ myself I'm not so familiar with the exact HBOOT levels on the G2 (since that's one difference from the DZ), but I'm sure someone else can help you with that shortly.
I recommend using gfree though, because with a proper radio S-OFF (not a kind of "fake" S-OFF via HBOOT) it will be a lot easier to recover your phone if somehow you semi-brick it.
Click to expand...
Click to collapse
but what if i don't want to sim-unlock it? or do u have an option to opt-out the other unlocks?
If you use the gfree program its all automated for you. However you CAN do it manually by following the directions in the wiki. You would really need to understand what you are doing before you try to skip steps to only turn s off. Is there some reason you really dont want sim unlocked?
Sent from my HTC Vision using XDA App
shortlived said:
If you use the gfree program its all automated for you. However you CAN do it manually by following the directions in the wiki. You would really need to understand what you are doing before you try to skip steps to only turn s off. Is there some reason you really dont want sim unlocked?
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
well im rooted now with very detailed help from unlockr.com (w/o SIM unlock).. and i dont care for sim unlock at this time since im not leaving the county or switching carriers anytime soon.. so yea.
J-Hop2o6 said:
well im rooted now with very detailed help from unlockr.com (w/o SIM unlock).. and i dont care for sim unlock at this time since im not leaving the county or switching carriers anytime soon.. so yea.
Click to expand...
Click to collapse
So did you install the engineering hboot to get S-OFF ? Because if not, I highly recommend gfree. It's safe and it'll put your phone into a better state if anything bad does happen to it in the future (e.g. semi-brick), even if you don't want the SIM unlock. It gives you a proper radio S-OFF, the engineering hboot is kind of a fake S-OFF (because it reports S-OFF even though the radio is actually still S-ON).
Came to my attention today that many rooted Eris users do not have an eng bootloader. Likely due to use of our one click, or other root methods besides the original ENG RUU. I could of sworn I had posted this mid 2010, but was unable to find it today when I needed it.
Here you go, confirmed working with RA Amon's recovery. Not tested with clockwork. Please check the md5sum before flashing.
ENG hboot allows use of more fastboot commands (great for recovering ""bricks""), and removes signature checks on images flashed through fastboot/hboot.
If you are unsure how to figure out which bootloader you have, then you don't need this file.
For users with 1.49.x bootloaders you can flash this
8d69c3fd10238094f0c6d84385e7cff5 eris_eng_hboot.zip
http://www.multiupload.com/25XWSSWTCJ
For users with 1.46 or 1.47 bootloaders, you have more work to do
first follow this guide
http://forum.xda-developers.com/showthread.php?t=725047
then use bftb0's flashback to get the lastest radio
http://forum.xda-developers.com/showthread.php?t=792026
then fastboot the recovery back in and flash the rom of your choice.
With Love,
AndIRC
Thank you, I actually used the first one you had posted last yr, trackball went out and got a replacement Eris, just used one click this time and used your original one. It worked great, thanks for work, I'm sure alot of people will appreciate this
gracias.
10char
jcase said:
I could of sworn I had posted this mid 2010, but was unable to find it today when I needed it.
Click to expand...
Click to collapse
jcase,
Yep, you posted this on 13th July 2010, 11:09 PM:
How To Install Engineering bootloader FOR LEAK ROOTERS
Cheers!
Is this any different from the version that doesn't work on the 1.47.0000 S-ON bootloader, and may brick phones with 1.46.0000 S-ON? See http://forum.xda-developers.com/showpost.php?p=10711166&postcount=7
Just asking - I'd hate to see somebody brick their phone if they weren't aware.
doogald said:
Is this any different from the version that doesn't work on the 1.47.0000 S-ON bootloader, and may brick phones with 1.46.0000 S-ON? See http://forum.xda-developers.com/showpost.php?p=10711166&postcount=7
Just asking - I'd hate to see somebody brick their phone if they weren't aware.
Click to expand...
Click to collapse
Well, I unpacked the eris_eng_hboot.zip and it contains the hboot.img file that is identical to the spl.bin file that is in the erisengspl.zip file.
So, I do indeed think its the same thing...
Looks like this is safe for the 2.1 leakers to install since they have the 1.49.0000 S-ON bootloaders, and is harmless (but ineffective) for a 1.47.0000 S-ON phone but potentially sketchy (bricky ) on the aforementioned 1.46.0000 S-ON phones.
I'll leave the final word on this to bftb0 and jcase, though...
scary alien said:
Well, I unpacked the eris_eng_hboot.zip and it contains the hboot.img file that is identical to the spl.bin file that is in the erisengspl.zip file.
So, I do indeed think its the same thing...
Looks like this is safe for the 2.1 leakers to install since they have the 1.49.0000 S-ON bootloaders, and is harmless (but ineffective) for a 1.47.0000 S-ON phone but potentially sketchy (bricky ) on the aforementioned 1.46.0000 S-ON phones.
I'll leave the final word on this to bftb0 and jcase, though...
Click to expand...
Click to collapse
Apparently I did post this last year, in .zip format on another forum, and bftb0 posted it here. Sorry for the repost.
I was unaware of issue with the 1.46/1.47 bootloaders, but I had amended the post with a method that will work for them (as I used this method on my original 1.46 and 1.47 Eris-es).
Any chance at getting these files re-upped to a different file host since mltiupload is dead?
williams1978 said:
Any chance at getting these files re-upped to a different file host since mltiupload is dead?
Click to expand...
Click to collapse
Here you go: View attachment erisengspl.zip
MD5 checksum: df014009668389ef145fbb047b5ec56c *erisengspl.zip
All due cautions apply--wouldn't use this on a 1.46.0000 S-ON device (see doogald's post above).
jcase said:
Came to my attention today that many rooted Eris users do not have an eng bootloader. Likely due to use of our one click, or other root methods besides the original ENG RUU. I could of sworn I had posted this mid 2010, but was unable to find it today when I needed it.
Here you go, confirmed working with RA Amon's recovery. Not tested with clockwork. Please check the md5sum before flashing.
ENG hboot allows use of more fastboot commands (great for recovering ""bricks""), and removes signature checks on images flashed through fastboot/hboot.
If you are unsure how to figure out which bootloader you have, then you don't need this file.
For users with 1.49.x bootloaders you can flash this
8d69c3fd10238094f0c6d84385e7cff5 eris_eng_hboot.zip
http://www.multiupload.com/25XWSSWTCJ
For users with 1.46 or 1.47 bootloaders, you have more work to do
first follow this guide
http://forum.xda-developers.com/showthread.php?t=725047
then use bftb0's flashback to get the lastest radio
http://forum.xda-developers.com/showthread.php?t=792026
then fastboot the recovery back in and flash the rom of your choice.
With Love,
AndIRC
Click to expand...
Click to collapse
good job
could anyone re-upload the eris_eng_hboot.zip for the 1.49 hboot, please?
Swifty31703 said:
could anyone re-upload the eris_eng_hboot.zip for the 1.49 hboot, please?
Click to expand...
Click to collapse
Wow! Holy Eris resurrection, Batman!
I think I've got it on my home PC...I'll look for it and upload it then after I get home from work (won't be for several hours, though).
scary alien said:
Wow! Holy Eris resurrection, Batman!
I think I've got it on my home PC...I'll look for it and upload it then after I get home from work (won't be for several hours, though).
Click to expand...
Click to collapse
Actually, check post #9 above (first/previous page)...I've already got it uploaded in that post.
Cheers and best of luck!
scary alien said:
Actually, check post #9 above (first/previous page)...I've already got it uploaded in that post.
Cheers and best of luck!
Click to expand...
Click to collapse
Yeah, I got bored and pulled out the old eris to tinker with. Thank you.
jcase said:
Came to my attention today that many rooted Eris users do not have an eng bootloader. Likely due to use of our one click, or other root methods besides the original ENG RUU. I could of sworn I had posted this mid 2010, but was unable to find it today when I needed it.
Here you go, confirmed working with RA Amon's recovery. Not tested with clockwork. Please check the md5sum before flashing.
ENG hboot allows use of more fastboot commands (great for recovering ""bricks""), and removes signature checks on images flashed through fastboot/hboot.
If you are unsure how to figure out which bootloader you have, then you don't need this file.
For users with 1.49.x bootloaders you can flash this
8d69c3fd10238094f0c6d84385e7cff5 eris_eng_hboot.zip
http://www.multiupload.com/25XWSSWTCJ
For users with 1.46 or 1.47 bootloaders, you have more work to do
first follow this guide
http://forum.xda-developers.com/showthread.php?t=725047
then use bftb0's flashback to get the lastest radio
http://forum.xda-developers.com/showthread.php?t=792026
then fastboot the recovery back in and flash the rom of your choice.
With Love,
AndIRC
Click to expand...
Click to collapse
Haha.... Just looking back to my first android and rooting experience... My how things have changed [emoji2]
whojabacod said:
Haha.... Just looking back to my first android and rooting experience... My how things have changed [emoji2]
Click to expand...
Click to collapse
Yep! :good:
Those were the days! But many of the "root" p base) concepts remain the same, eh?
I still have my Eris (sitting right above my monitor on a shelf ) and boot it up occasionally.
True! Root concepts are the same .. I did it before the one click all commands .. I miss mine sometimes ... The little ball lighting. Up the original play store with only a hand full of apps... I could query "root" and count the apps my hand .. Now its just crazy and mostly phishing and ads
I'm trying to update my ROM before I run the HTC unlocking steps on the bootloader section. For the MyTouch 4G, it says I need to do it and my carrier is listed in the list (DAVE CA). It starts fine and then pops up with error 131 CID Error. The phone is stock and I haven't done anything to it yet.
Current version 2.09.1800.1
To: 2.32.531.1
Anyone know what is causing this CID error and how I can fix it?
Thx.
fruv said:
I'm trying to update my ROM before I run the HTC unlocking steps on the bootloader section. For the MyTouch 4G, it says I need to do it and my carrier is listed in the list (DAVE CA). It starts fine and then pops up with error 131 CID Error. The phone is stock and I haven't done anything to it yet.
Current version 2.09.1800.1
To: 2.32.531.1
Anyone know what is causing this CID error and how I can fix it?
Thx.
Click to expand...
Click to collapse
STOP!
Don't use HTC Dev. Are you on Froyo? If so, go to the development section of this forum and use the gfree thread (ultimate s-off) stickied there.
Everyone who goes through the htc-dev process comes back in here regretting it and goes ahead and roots the XDA way. Save yourself the trouble.
I assume you want to root your phone. Look up the "Mobilicity/Videotron Panache" thread.
If you don't want extra pain - don't use HTCDev unlock.
Jack_R1 said:
I assume you want to root your phone. Look up the "Mobilicity/Videotron Panache" thread.
If you don't want extra pain - don't use HTCDev unlock.
Click to expand...
Click to collapse
I'm still trying to figure out which one he has. He has using an RUU, so I can see now why you said that. Thanks Jack!
OP, clarify whether you have a myTouch 4g or Panache, please.
estallings15 said:
I'm still trying to figure out which one he has. He has using an RUU, so I can see now why you said that. Thanks Jack!
OP, clarify whether you have a myTouch 4g or Panache, please.
Click to expand...
Click to collapse
Panache. DAVE CA/Mobilicity version running stock Gingerbread. Was hoping that I wouldn't have to downgrade OSes but I guess I'll have to do that.
Thanks all.
You can avoid downgrading, but I strongly suggest you go that way instead of HTCDev-unlocking. It'll take very few ROM changes to get really annoyed by flashing boot.img manually.
Got it done following the dev guide.
Hi,
Just wanted to see how much interest is there in getting S-OFF for our HTC One phones. I personally could use this for testing Tmobile radios on the HTC Dev Edition phones. What are some of your interest and thoughts about S-Off. Most importantly, why is it important to you?
Interest? Sure. Able to do it? No idea. The HoX is still locked up tight. And for most people, S-Off would just mean easier to flash kernels, ability to flash radios and downgrade HBOOT so that it says LOCKED instead of RELOCKED for warranty purposes.
ArmedandDangerous said:
Interest? Sure. Able to do it? No idea. The HoX is still locked up tight. And for most people, S-Off would just mean easier to flash kernels, ability to flash radios and downgrade HBOOT so that it says LOCKED instead of RELOCKED for warranty purposes.
Click to expand...
Click to collapse
Could you please educate me more about the HoX? Thanks
Becool0130 said:
Could you please educate me more about the HoX? Thanks
Click to expand...
Click to collapse
Most HTC devices now are S-On (at least the recently released ones from 2011-2013). What they do have though is an unlocked bootloader. That means you can install a custom recovery like CWRM or TWRP, and you can flash kernels through Fastboot. S-Off gives the ability to flash kernels from within the recovery (Fastboot requires a USB cable and a computer) and also the ability to flash radios.
With the HoX (HTC One X, and all phones unlocked through HTCDEV), when you unlock your bootloader it will say UNLOCKED (as opposed to Locked when stock). Relocking the bootloader will say RE-LOCKED, but not LOCKED. This means HTC can see that you have unlocked the bootloader and they can, and depending on luck, wil reject your warranty claim.
With S-Off we can overwrite the HBOOT and downgrade to an older version where it still says LOCKED, send that back for warranty and all will be well
Not sure about the Tegra3 version of the HOX, but the S3 version of the HOX has achieved S-OFF for awhile now. There is definitely interest in ALL HTC devices to achieve S-OFF. Just a matter of time before devs crack the code.
getting the Tmobile AWS radio to work on the dev version would be my top interest
illestfob said:
getting the Tmobile AWS radio to work on the dev version would be my top interest
Click to expand...
Click to collapse
Don't hold your breath, I doubt this will work.
BenPope said:
Don't hold your breath, I doubt this will work.
Click to expand...
Click to collapse
its a slight crap shoot, but i live in a refarmed area so it should be liveable until LTE gets turned on.
I usually restrict my current phone (G2) to only edge anyway to conserve battery life
I think the problem with the HTC One X was the fact that it was Tegra and not Qualcomm - most of the major players in s-off work with Qualcomm chips. I remember when I had the One X about a year ago - rumour had it that the likes of revolutionary didn't want to work with Tegra hardware.
Things might be better for the One.
Out of interest did the One S get s-off?
Well with big devs getting it like Steve Kondik (CM) Koushik Dutta (CWM) etc I think the dev support will be strong on this one
ArmedandDangerous said:
Most HTC devices now are S-On (at least the recently released ones from 2011-2013). What they do have though is an unlocked bootloader. That means you can install a custom recovery like CWRM or TWRP, and you can flash kernels through Fastboot. S-Off gives the ability to flash kernels from within the recovery (Fastboot requires a USB cable and a computer) and also the ability to flash radios.
With the HoX (HTC One X, and all phones unlocked through HTCDEV), when you unlock your bootloader it will say UNLOCKED (as opposed to Locked when stock). Relocking the bootloader will say RE-LOCKED, but not LOCKED. This means HTC can see that you have unlocked the bootloader and they can, and depending on luck, wil reject your warranty claim.
With S-Off we can overwrite the HBOOT and downgrade to an older version where it still says LOCKED, send that back for warranty and all will be well
Click to expand...
Click to collapse
Thanks for the education man! I really think we can get this one done though because it's from Qualcomm as opposed to Tegra right?
Anyways, s-off is extremely important for warranty purposes I see Guess I should return my developer edition back right?
BenPope said:
Don't hold your breath, I doubt this will work.
Click to expand...
Click to collapse
Why is this? I actually bought the developer phone for the sole purpose of this working on TMobile network 1700 3G. I'm not refarmed to 1900 yet which means Edge speeds -_-. Gotta give us some hope! Lol
huwwatkins said:
I think the problem with the HTC One X was the fact that it was Tegra and not Qualcomm - most of the major players in s-off work with Qualcomm chips. I remember when I had the One X about a year ago - rumour had it that the likes of revolutionary didn't want to work with Tegra hardware.
Things might be better for the One.
Out of interest did the One S get s-off?
Click to expand...
Click to collapse
Good point! Qualcomm does seem fairly easy to hack with all the s3 and soon s4 out.
Sent from my SGH-T959 using xda app-developers app
ArmedandDangerous said:
Most HTC devices now are S-On (at least the recently released ones from 2011-2013). What they do have though is an unlocked bootloader. That means you can install a custom recovery like CWRM or TWRP, and you can flash kernels through Fastboot. S-Off gives the ability to flash kernels from within the recovery (Fastboot requires a USB cable and a computer) and also the ability to flash radios.
With the HoX (HTC One X, and all phones unlocked through HTCDEV), when you unlock your bootloader it will say UNLOCKED (as opposed to Locked when stock). Relocking the bootloader will say RE-LOCKED, but not LOCKED. This means HTC can see that you have unlocked the bootloader and they can, and depending on luck, wil reject your warranty claim.
With S-Off we can overwrite the HBOOT and downgrade to an older version where it still says LOCKED, send that back for warranty and all will be well
Click to expand...
Click to collapse
Dont need s-off for Radios or flashing kernels through recovery. There is a work around for all of that. We can change radios and flash kernels through recovery on this HTC One. The Renovate rom says the kernel is flashed with the rom install. You can install radios by installing radio to different partition then symlink to the new radio. Turge will be posting more about it soon. For now here is the thread where i tested this for him. http://forum.xda-developers.com/showthread.php?t=2243159 So we should be able to test the tmobile radio soon enough.
And yeah it's the tegra devices that are having the hardest time with s-off. The ATT One X (qualcom) THe DNA are both s-off. Since this is also qualcom, i have high hopes for s-off soon. Although it is not as important as it once was.
nugzo said:
Dont need s-off for Radios or flashing kernels through recovery. There is a work around for all of that. We can change radios and flash kernels through recovery on this HTC One. The Renovate rom says the kernel is flashed with the rom install. You can install radios by installing radio to different partition then symlink to the new radio. Turge will be posting more about it soon. For now here is the thread where i tested this for him. http://forum.xda-developers.com/showthread.php?t=2243159 So we should be able to test the tmobile radio soon enough.
And yeah it's the tegra devices that are having the hardest time with s-off. The ATT One X (qualcom) THe DNA are both s-off. Since this is also qualcom, i have high hopes for s-off soon. Although it is not as important as it once was.
Click to expand...
Click to collapse
I was mostly referring to the HoX, as mine is the Tegra one, and there is no workaround to flashing kernels or radios without ADB But yes I did read that on the One, it can be done through recovery although S-On. Would still love S-Off though for HBOOT downgrading
ArmedandDangerous said:
I was mostly referring to the HoX, as mine is the Tegra one, and there is no workaround to flashing kernels or radios without ADB But yes I did read that on the One, it can be done through recovery although S-On. Would still love S-Off though for HBOOT downgrading
Click to expand...
Click to collapse
Yes i totally agree. S-off is what we all want. Just not as important as it once was.. :fingers-crossed: we'll get it. I'd even make a bet that we have it in less than 60 days from now I did see somewhere that there is a suprcid method being worked on also.. That would be great as well :good:
nugzo said:
Yes i totally agree. S-off is what we all want. Just not as important as it once was.. :fingers-crossed: we'll get it. I'd even make a bet that we have it in less than 60 days from now I did see somewhere that there is a suprcid method being worked on also.. That would be great as well :good:
Click to expand...
Click to collapse
Just in time for me to wait out supply and batch issues from my telco, should start being available in early to mid May
First Android device I haven't rooted due to the Warranty issues with HTC ( How they are a right pain somtimes! ). Once S-OFF becomes available I will happily go ahead and unlock my boot loader etc. For now everything is fine without root
also would like super cid or S-off even better. to flash other region roms. INT RUUs etc . and we all know how ATT likes to software update HBOOT versions and no way to downgrade without S-OFF
nugzo said:
Dont need s-off for Radios or flashing kernels through recovery. There is a work around for all of that. We can change radios and flash kernels through recovery on this HTC One. The Renovate rom says the kernel is flashed with the rom install. You can install radios by installing radio to different partition then symlink to the new radio. Turge will be posting more about it soon. For now here is the thread where i tested this for him. http://forum.xda-developers.com/showthread.php?t=2243159 So we should be able to test the tmobile radio soon enough.
And yeah it's the tegra devices that are having the hardest time with s-off. The ATT One X (qualcom) THe DNA are both s-off. Since this is also qualcom, i have high hopes for s-off soon. Although it is not as important as it once was.
Click to expand...
Click to collapse
Ha! There is hope to flashing radios without S-OFF. I wonder if we can get a developer to try to get T-Mobile radios and flash them over to our Developer Edition phones. Meh, essentially they are ATT Htc Ones without restrictions
daddioj said:
also would like super cid or S-off even better. to flash other region roms. INT RUUs etc . and we all know how ATT likes to software update HBOOT versions and no way to downgrade without S-OFF
Click to expand...
Click to collapse
+1
BTW, I'm very curious what the cid is for the dev model.
Sent from my HTC One X+ using xda app-developers app
ArmedandDangerous said:
Interest? Sure. Able to do it? No idea. The HoX is still locked up tight. And for most people, S-Off would just mean easier to flash kernels, ability to flash radios and downgrade HBOOT so that it says LOCKED instead of RELOCKED for warranty purposes.
Click to expand...
Click to collapse
That's not exactly true. Downgrading hboot will still be relocked. There is a "lock status flag" that must be reset in order to become locked again.
S off does remove write protection on mmcblk0p3 where the lock flag lives,allowing the user to reset it and become locked again. User S_trace initially figured out what was going on and posted a flashable zip file. We have modded the zip(removed the device check) and i have threads in several forums,titled [how to]reset your lock status flag if you'd like a little more info/detail. The flag thus far has been the same in all s3 and all dual/quad core s4 devices.
The fact that the radio partition is currently writeable from recovery,is likely a fluke that will be "fixed" with newer hboots,so I'd advise those of you that like this feature to not update
Even tho the radio itself can be chanaged,other firmware cannot. Thus the newer radios may not be optimized with the older firmware remaining on the phone.(read: the new radios may not be working as good as you think they are)
My personal interest in s off is to change cid,and eliminate the security checks that prevent other carrier/regional ruus from flashing,and from going backwards in firmware. I also like to change the splash image
I cannot truly enjoy an s on device,and won't get one unless some means of s off becomes available.
Sent from my HTC PG09410 using xda app-developers app
Hey there!!!
So after a chat via pm with a fellow xda member, we found someone who did what most of us though was impossible, achieve an S-Off -able state after upgrading to the .11 firmware update. The user who achieved this has unfortunately been banned from the xda forums for reasons I don't know of, so you'll find a link to his page and tutorial in the bottom of the OP. I haven't personally tried this method all the way through yet, but it has been confirmed to work by a couple of the people over on his forum.
Apparently all you have to do is:
-Backup whatever data is on your phone
-Unlock your bootloader
-Flash a custom recovery(I prefer TWRP)
-Do a full system wipe(This WILL ERASE EVERYTHING on your phone, including your OS).
-Flash a "stock" 1.27.531.7 Rom (I know there's one floating somewhere in the dev forum section) OR restore a .7 Nandroid backup
-Wipe Cache and Dalvik
-Flash kernel
-Reboot
- Enable USB Debugging and make sure your battery is over 30%( I'd say 50% for good measure).
-Run the modified 1.27.531.8 RUU(Found in the link in the OP)
- Let it go through the motions (multiple reboots)
-BOOM. There you go. If all goes well you should be running the official(kind of) stock, S-Off capable, 1.27.531.8 Firmware, with the unmodified 1.44 hboot, meaning Revone AND Moonshine should both work, whichever you prefer.
If I forgot any steps I apologize, I'm typing this on the go, completely from memory. But if you're attempting this, I'm going to assume you've flashed a custom Rom before and know how to do it without bricking your phone. Good luck everyone!!! Feel free to post successes and failures for the rest of us!
Tutorial and Modified RUU:
link removed
Sent from my HTC One using xda app-developers app
ALL CRED FOR THIS DISCOVERY
GOES TO:
xboarder56 for the RUU :thumbup::thumbup::thumbup:
bloodbond3 For sharing this. :thumbup::thumbup:
MUCH THANKS MATES
Sent from my HTC One using xda app-developers app
1.54
But....this is not for 1.54 users, right?
Im on hboot 1.54 s-on ... Can s-off be axhieved following this tutorial
?
Nightf0x_007 said:
Im on hboot 1.54 s-on ... Can s-off be axhieved following this tutorial
Click to expand...
Click to collapse
I have now seen a post with this explanation:
No, this is for the US T-Mobile edition and WILL NOT assist in unlocking the 1.54 HBoot. Maybe the OP should add some backstory:
T-Mobile released an update about 2 months ago that changed the version incrementally. In doing so they updated the HBoot, but kept it on 1.44, and patched the hole used by Renovate and Moonshine. This mod tricks your US T-mobile phone into downgrading through RUU (since the HBoot version never changed it is working) and allowing S-Off... that being said dont be a dummy and RUU then take the update after the first boot lol.
This is a great tool, I am DL'ing it just in case, i already had mine done prior to the update and am running a GPE Converted phone now.
That being said I HIGHLY recommend doing this prior to taking the upcoming 4.2 or 4.3 update, They will be updating to the as-of now locked down 1.54 HBoot. At that time this mod should no longer work as downgrading your HBoot is only available while S-Off.
Maichel said:
I have now seen a post with this explanation:
No, this is for the US T-Mobile edition and WILL NOT assist in unlocking the 1.54 HBoot. Maybe the OP should add some backstory:
T-Mobile released an update about 2 months ago that changed the version incrementally. In doing so they updated the HBoot, but kept it on 1.44, and patched the hole used by Renovate and Moonshine. This mod tricks your US T-mobile phone into downgrading through RUU (since the HBoot version never changed it is working) and allowing S-Off... that being said dont be a dummy and RUU then take the update after the first boot lol.
This is a great tool, I am DL'ing it just in case, i already had mine done prior to the update and am running a GPE Converted phone now.
That being said I HIGHLY recommend doing this prior to taking the upcoming 4.2 or 4.3 update, They will be updating to the as-of now locked down 1.54 HBoot. At that time this mod should no longer work as downgrading your HBoot is only available while S-Off.
Click to expand...
Click to collapse
This is a post inception.... I made the post that was quoted that I am now quoting in my post......
Sent from my Nexus 10 using Tapatalk 4
This method has been floating around for s while now, since the update came out. But none the less, great guide op.
Sent from my HTC One using XDA Premium 4 mobile app
So wait I'm confused, lol did I not add enough backstory? Or was that from another thread?
Sent from my HTC One using xda app-developers app
EDIT: unconfused now. Mah bad
In simpler terms, a little less confusing, what Maichel is saying is that the RUU contains the unmodified 1.44 hboot, but still 1.44, so "technically" speaking, you're not downgrading your hboot at all.
Sent from my HTC One using xda app-developers app
Links to banned dev. Closed, link removed