i have looked through the threads and i did not see anything about this question or anything close enough to it. I need to go back to sprint to get my phone fixed (the microphone doesn't always work. sometimes it does, sometimes it does not. i have found that it is not software related, but definitely a hardware issue.) but i do not want to get my account noted or anything. right now i am s-off (NOT htc dev unlocked), running TWRP recovery v 2.2.0, and running meanrom with a custom kernel that was installed with meanrom. i know i can run an RUU and return to stock, but i will still be s-off. i did install a custom bootloader (thanks to regaw_leinad) that makes it look like i am s-on and not tampered, but i do not know if sprint can still see if i am s-off. sorry if this is a noob question, but i have never dealt with s-off before.
http://forum.xda-developers.com/showthread.php?t=1744700
Look harder next time.... Just joking. This is what you want to read.
metalfan78 said:
http://forum.xda-developers.com/showthread.php?t=1744700
Look harder next time.... Just joking. This is what you want to read.
Click to expand...
Click to collapse
thank you! that was exactly what i was looking for! i guess i didn't look hard enough sorry.
but just to clarify, i cannot just leave my phone s-off? if i take it to sprint with s-off, but the custom bootloader that makes it look stock from regaw_leinad, will they still be able to find out that i am s-off?
I have never returned my phone to s-on in two years. I've never had a problem with the Sprint stores. It's your call though. If you do s-on it, tell them you don't want it updated. If it was me I would just have the stock rom on it and call it good
metalfan78 said:
I have never returned my phone to s-on in two years. I've never had a problem with the Sprint stores. It's your call though. If you do s-on it, tell them you don't want it updated. If it was me I would just have the stock rom on it and call it good
Click to expand...
Click to collapse
that is probably what i will do then. again, thank you!
You're welcome
ok, last question. if i run the latest ruu, will it update my hboot? i am still on 1.12 and i do not want a newer one. i downloaded the 1.13.651.1 ruu. is this fine? i am running meanrom v 4.0 if that info is needed.
I'm about to go 100% back to stock as well to try and resolve many of the problems i'm having, this thread has been particularly helpful, thanks
I think it does update your hboot, but I don't know for sure.
i have confirmed that it does indeed update your hboot.
if you have hboot 1.12, then use this ruu:
http://bit.ly/VPl2wn
it is the 1.13.651.1 ruu. it has hboot 1.12 in it.
tim.d said:
I'm about to go 100% back to stock as well to try and resolve many of the problems i'm having, this thread has been particularly helpful, thanks
Click to expand...
Click to collapse
i am glad to posted a helpful thread. but we can thank metalfan78 for supplying the information that helped us
sorry to post a third time, but i ran the ruu that i previously posted a link to and went to the sprint store (i also had to re-flash the custom bootloader from the regaw_leinad tool). they had no clue i was s-off or i had done anything to my phone. but there is one problem. if they had tried to update it and it updated the bootloader as well, it would have removed the custom one and put HTCs back on it. that wouldnt be a problem as you would still be s-off, but instead of looking stock(s-on, locked), it would now say s-off in the bootloader. so if you want to be sure that the sprint employees will not be able to tell you modded your phone, you do have to return to s-on. chances are that they wont try to update it, but its better to be safe than sorry!
Yea, true. I'm glad everything worked out.
Related
So someone mentioned in a thread I read that they were on hboot 1.4 with s-off and they were having issues (that aren't important to the topic of this thread) so they used a 2.08 RUU to return to stock, which flashed hboot 1.5 onto their phone. This person said they checked their bootloader and saw that it was indeed hboot 1.5, then they RUU'd back to an older stock ROM and their bootloader was hboot 1.4.
So, was this workaround for being able to Revolutionary unlock an HTC Evo 3D common knowledge before and it's old news now, or had nobody thought of doing this earlier to get rid of hboot 1.5? I was one of the lucky ones who first got my 3vo less than a month ago, yet it came with hboot 1.3 (now it's on the eng bootloader of course ). so I'm too afraid of losing my revolutionary root to try this myself, but I figured I'd at least put this out there in its own thread so that all you adventurous types stuck with hboot 1.5 can try this out and report your findings.
NOTE: as stated before, I did not try this myself and the person who said they tried this did not prove it to me or anyone else, they merely stated it and since this is the internet, I go by "pics or it didn't happen" if information comes from an untrusted source. I'm not responsible for bricks and impregnation of your daughter(s), and all that other stuff devs usually claim no responsibility for in their disclaimers.
You can change the bootloader if you're s-off, you can't if you're s-on
Twolazyg said:
You can change the bootloader if you're s-off, you can't if you're s-on
Click to expand...
Click to collapse
Does that apply even if you're using an RUU? I knew you couldn't change the bootloader if you tried to flash using fastboot, but I didn't remember seeing anything about not being able to through RUU (though I guess I never saw anything that said you could through RUU either...)
w0rdOo said:
Does that apply even if you're using an RUU? I knew you couldn't change the bootloader if you tried to flash using fastboot, but I didn't remember seeing anything about not being able to through RUU (though I guess I never saw anything that said you could through RUU either...)
Click to expand...
Click to collapse
yes, you will remain s-off
t3project said:
yes, you will remain s-off
Click to expand...
Click to collapse
Well I should've known it was too good to be true, that you could get to an old bootloader through an RUU. Thanks to both of you for the quick and helpful responses.
w0rdOo said:
Well I should've known it was too good to be true, that you could get to an old bootloader through an RUU. Thanks to both of you for the quick and helpful responses.
Click to expand...
Click to collapse
sounded like a good idea. would love to get back to hboot 1.40
will it work how does it work and if so how do i do it im stuck with a hboot 1.5 im rooted but s on still
tashsru said:
will it work how does it work and if so how do i do it im stuck with a hboot 1.5 im rooted but s on still
Click to expand...
Click to collapse
You are stuck with 1.50 with no changes in sight. At present time you can only change hboot if you are S-off.
I am beyond feeling like a ReeeTard right now. As someone who beta tests for a lot of ROM builders and knows a great deal about Android, software development etc... please don't reply to this with a smart a** remark. It helps no one and makes you look like just a jerk.
We all have our days where we simply cannot think straight, I am dealing with a great deal of stress, in my life, so forgive me for somehow not finding the answer to this question.
I updated my phone, using an RUU...My phone WAS hboot 1.40, now however it's hboot 1.50, and it's UNLOCKED (the bootloader) as well as S-Off, Am I forgetting to do something to have ROOT access?
So I am hboot 1.50 UNLOCKED and S-off
With all of those things I thought, because I cant seem to think clearly right now, that I was rooted. I however ran root checker and I am not.
Please throw me a bone and fill me in on what I am missing here. It's been a rough couple weeks for me.
Much appreciated.
quickfixguru said:
I am beyond feeling like a ReeeTard right now. As someone who beta tests for a lot of ROM builders and knows a great deal about Android, software development etc... please don't reply to this with a smart a** remark. It helps no one and makes you look like just a jerk.
We all have our days where we simply cannot think straight, I am dealing with a great deal of stress, in my life, so forgive me for somehow not finding the answer to this question.
I updated my phone, using an RUU...My phone WAS hboot 1.40, now however it's hboot 1.50, and it's UNLOCKED (the bootloader) as well as S-Off, Am I forgetting to do something to have ROOT access?
So I am hboot 1.50 UNLOCKED and S-off
With all of those things I thought, because I cant seem to think clearly right now, that I was rooted. I however ran root checker and I am not.
Please throw me a bone and fill me in on what I am missing here. It's been a rough couple weeks for me.
Much appreciated.
Click to expand...
Click to collapse
Hey! No worries man. You're almost there. All you need to do is flash a recovery now. Choose a recovery, and flash it, either a pg86img.zip or a recovery.img, and flash it. Once you have recovery flashed, either just flash a rooted ROM, or flash a su.zip. Then you should be good to go.
Sent from my PG86100 using Tapatalk
Thanks a lot man, I appreciate it. I knew I needed to flash superuser I just wanted to be sure it was just flash a recovery then su.zip
quickfixguru said:
Thanks a lot man, I appreciate it. I knew I needed to flash superuser I just wanted to be sure it was just flash a recovery then su.zip
Click to expand...
Click to collapse
You're welcome. Glad to help. Let me know if you have further questions. if you just decide to flash a su.zip, as opposed to an entire custom rom, you'd probably have the best luck looking in the old original TWRP thread for one. I know that had a su.zip posted in it. I'll see if i can find it for you real quick.
EDIT: Here's a super user zip http://techerrata.com/toastcfh/Shooter/su-2.3.6.3-efgh-fixed-unsigned.zip that I found in the 3rd post of this old thread http://forum.xda-developers.com/showthread.php?t=1192077&highlight=twrp+recovery. That's not the newest super user app, but it should work just fine, and you should be able to update it from there once you get it installed.
buckley nailed it!
i was actually unaware that updating your bootloader would still leave you s-off if you were on 1.4. that is interesting... although i would still never update.
did you know that it would still leave you with your NAND unlocked when you updated?
cobraboy85 said:
buckley nailed it!
i was actually unaware that updating your bootloader would still leave you s-off if you were on 1.4. that is interesting... although i would still never update.
did you know that it would still leave you with your NAND unlocked when you updated?
Click to expand...
Click to collapse
Yea, updating will still leave you S-off. You won't have a custom recovery anymore, and you'll be on hboot 1.5, but you still have S-off. There is pretty much no way that I know of to turn it back to S-on without going into fastboot and doing that 'fastboot setsecureflag3' command or whatever it is. The revolutionary team gave us some pretty damn permanent S-off, lol. I've seen lots of people take OTA updates, and still have S-off. You can even downgrade the hboot back to 1.4 if you wanted to, even though there really isn't a reason to. Having hboot 1.5 with S-off is just the same as having 1.4 with s-off, you don't need to do any extra stuff to flash.
up-to-date instructions on downgrading to 1.4 for S-Off then upgrading to ICS? *that period was supposed to be a question mark. opps*
SPRINT CDMA!
I've read many of the threads and have been keeping myself up to date on everything. HOWEVER, there really aren't any good real step by step instructions on start to finish. I DID NOT take the OTA to 4.0. I NEVER take OTA's! It's just that I received the phone with 1.5 already installed and made a choice to wait until ICS.
I'm still on 2.3.4
2.17.651.5
1.5 bootloader.
I've read through http://forum.xda-developers.com/showthread.php?t=1563342
I'd like it if someone can just re-write the entire thing from start to finish to end up with the OTA rooted S-off. Do I need to be 1.58 for ICS? There is just so much useless information throughout the entire site, it is hard to get exacts. Sadly I'm ready to do all of this now but after reading ALL of the instructions... It's not clear on exact steps for ICS without having issues. All those youtube videos are also out of date.
So what I need are exact files to download, exact steps.
I've currently downloaded:
1.Superwipe.zip 144KBs
3d-ICS-Deodex.zip 465,310 KBs
PG86IMG_2.17.651.5.zip 409,064 KBs
revolutionary-0.4pre4.zip 1,583 KBs copied my key too
PG86IMG.zip *no idea what this one does because it wasn't labelled right so won't use it* 12,190KBs
RUU_Shooter_S_Sprint_WWE_1.13.651.7_Radio_0.97.10.0530_NV_NV_SPCS_1.16_release_198109_Signed.exe
Also downloaded the [TOOL] HBOOT Downgrade Toolkit Live 8.2 CD and tested it to insure it works correctly.
When I got my phone, I already had the 1.5 bootloader on it. Therefore, I just waited. I knew that ICS was coming out so I didn't root my phone just yet. I've rooted my other phones in the past before like my original Evo.
The biggest favor I need is just Good instructions on what I really need for getting ICS fully installed as stock and stable as I can while being S-off and rooted.
Of course I'll press your thanks button for anyone that helps me out. plz no smartass replies on here. I think I've at least made an attempt. I just don't want to make any mistakes. Mistakes cost time and money.. I don't have the time. I'm not a beginner. I believe that if this gets created in a simple set of instructions... It would HELP A LOT OF people from asking the same question or saying, "HELP, I BRICKED MY PHONE" or something else silly like that.
ps, I really hate putting this in this thread as I don't think it'll get the right viewers to help me and others out the best. But I DO THANK YOU FOR TRYING.
I'd like it if someone can just re-write the entire thing from start to finish to end up with the OTA rooted S-off.
Click to expand...
Click to collapse
Well there really isn't a need to re-write that. The process is still the same for getting s-off. I can't really help you with that, as I have hboot 1.4 and never had to do that. But I do know the process for getting s-off is still the same.
Do I need to be 1.58 for ICS?
Click to expand...
Click to collapse
It seems to be that if you want to run the new kernel, you must be on hboot 1.58. That may change in the coming weeks, I'm sure someone will find a way around that. But you can run the kernel from the 2.17 VM leak, and from what I've been reading, that should work fine with the new rom.
sitlet said:
Well there really isn't a need to re-write that. The process is still the same for getting s-off. I can't really help you with that, as I have hboot 1.4 and never had to do that. But I do know the process for getting s-off is still the same.
It seems to be that if you want to run the new kernel, you must be on hboot 1.58. That may change in the coming weeks, I'm sure someone will find a way around that. But you can run the kernel from the 2.17 VM leak, and from what I've been reading, that should work fine with the new rom.
Click to expand...
Click to collapse
So therefore, what's the point of going to 1.40 if it is going right back to 1.58?
In other words... Should I continue to wait? But those instructions really aren't that clear when trying to go ICS. like maybe just add a few more steps for ICS?
If you don't downgrade to hboot 1.4, then you cant run revolutionary to gain s off... Once you are s off, you are good to go, because if you decide to upgrade the bootloader to 1.58, you will retain your s off status
sent from my EVO 3D
So therefore, what's the point of going to 1.40 if it is going right back to 1.58?
Click to expand...
Click to collapse
So you can get s-off.
In other words... Should I continue to wait?
Click to expand...
Click to collapse
Personally, I would wait at least a week or so to see if someone comes up with a workaround for the new hboot. But that's up to you.
But those instructions really aren't that clear when trying to go ICS. like maybe just add a few more steps for ICS?
Click to expand...
Click to collapse
Again, there is no need to re-write those instructions. ICS is just another rom/update like any other rom/update. Do those instructions, then flash an ICS rom like normal.
sitlet said:
So you can get s-off.
Personally, I would wait at least a week or so to see if someone comes up with a workaround for the new hboot. But that's up to you.
Again, there is no need to re-write those instructions. ICS is just another rom/update like any other rom/update. Do those instructions, then flash an ICS rom like normal.
Click to expand...
Click to collapse
when we allow 1.58... can it be downgraded without issues? I remember with other phones, we had to rewrite it to allow that to occur.
but yeah, I'm just going to wait a little longer. I refuse to allow sprint to rip of off on a phone then say we can't use it. that's why I root. They don't have the right to do that. I don't care about their profits. If they would invest in a good network, they wouldn't need to rip us off. because everyone would want them instead. yeah, I know I did a 360 on my subject. lol. my 2.3.4 crashed again today. lol. wth.
Hey guys....
I feel really stupid about this entire thing but I've finally decided to post here because I'm getting desperate.
The guide in question (http://forum.xda-developers.com/showthread.php?t=1563342) is fairly striaghtforward. Except the links are really scattered, at least for me. I'm on HBOOT 1.58, and I've had numerous problems even getting to the point where my phone is relocked (it's currently HTC unlocked because I use an MIUI port ROM) successfully. I would bring my problems to that thread, but I don't have 10 posts, which is a questionable rule but w/e.
Anyway, here's my problem. First, I'll tell you what I've done so far, and the problem I've come across both times.
1. Place a "2.89 RUU" or whatever onto my SD card and call it PG86IMG. This is where most of my confusion is. OP of that thread hasn't yet covered what the difference between 2.17 and 2.89 is, but my understand is that 2.17 corresponds with HBOOT 1.5 and 2.89 to 1.58. Honestly, all these numbers piss me off when there's little to no documentation of what the hell they even mean. This file is about 448 MB and my understanding was that it was a stock RUU and would make it so I could access my phone while it was still locked, which you can't do with a 3rd party ROM like the one I usually use.
2. Lock my phone's bootloader. I just did fastboot oem lock in Windows and it rebooted to *** RELOCKED *** *** Security Warning ***. Apparently this is normal, and now I need to flash said RUU.
3. Flash the RUU. This took an EXTREMELY long time, and it went through Loading PG86IMG.zip.. then to some other stage that took much less time to complete. After that it just sits in the bootloader.
Here's my concern... I can't access my SD card. Why? Because I can't even get out of the bootloader or fastboot. All it does is sit here, and since I can't remove the update file PG86IMG.zip, if I try to enter recovery (which I'm sure won't work anyway) it will try to start loading that file again. I don't really know what step I missed here, but it's probably because I'm fairly clueless when it comes to this stuff, lol.
So, I did this once, and then I waited about 6 hours for HTCdev's site to stop crashing so I could unlock my phone again. Made it through a school day with my old ROM and stuff, deleted the update files so they wouldn't run again, etc. etc.
Now, I'm doing it again today with this new 2.89 RUU or whatever and the same exact problem is happening. So now I'm at a stage where my phone is entirely useless until HTCdev.com starts actually sending e-mails. I swear, these crashes on HTCdev's part could not be more untimely.
So basically, what am I doing wrong with relocking my phone? OP implies that I should be able to start my phone (not the bootloader, but actually start it) because they ask after you've supposedly re-locked the bootloader for you to move a new PG86IMG.zip file onto your SD card, which I'm unable to do because my phone can't get out of fastboot/bootloader screen. That's the next step, which is actually doing the downgrading.
And yes, I know that it's possible for HBOOT 1.58 because someone else already did it (last post in the thread).
At this point, I don't really care when I get it to work, man. This is proving to be such a gigantic pain in the ass just to install a new Jelly Bean ROM. I JUST WANT JELLY BEAN!
If anyone can send a noob in the right direction, that'd be great. I have all week and all weekend, but I've run out of time to waste on this for today. I guess most of what I need is to know what files I'm supposed to be downloading, because I have a feeling that's most of what I'm getting wrong.
I hope I've explained my problem well enough, and thanks a ton to anyone who just suffered through reading my essay and can offer help. I'll be sending this to OP of the guide as a PM so hopefully if none of you guys can help they can.
Thanks a ton everyone, I just want to get Jelly Bean on my phone and stop dealing with MIUI :laugh:
Update: Found this thread: http://forum.xda-developers.com/showthread.php?t=1495358. I believe this will probably help me out a lot! Wish I would've seen it sooner.
TL;DR: Need better explanation of how to relock 1.58 hboot bootloader with a stock rom, and where to find the rom.
Honestly, your post was tl;dr for me, but I think you would be best served to follow ramjet's guide to s-off. It's really the easiest and includes everything you need.
http://forum.xda-developers.com/showthread.php?t=1889438
coal686 said:
Honestly, your post was tl;dr for me, but I think you would be best served to follow ramjet's guide to s-off. It's really the easiest and includes everything you need.
http://forum.xda-developers.com/showthread.php?t=1889438
Click to expand...
Click to collapse
Lol. I'm not surprised. I tend to pour my heart out on forums when I get to the point of desperation.
Gonna be honest with you, zero interest in the wire tap method. Zero. Not trying it. Not even going to think about it. Sorry, I appreciate the idea but honestly screw that.
Logic33 said:
Lol. I'm not surprised. I tend to pour my heart out on forums when I get to the point of desperation.
Gonna be honest with you, zero interest in the wire tap method. Zero. Not trying it. Not even going to think about it. Sorry, I appreciate the idea but honestly screw that.
Click to expand...
Click to collapse
Then, honestly, you are EXTREMELY limited as to what you can do. S-Off is your best bet. Good Luck.
raptoro07 said:
Then, honestly, you are EXTREMELY limited as to what you can do. S-Off is your best bet. Good Luck.
Click to expand...
Click to collapse
I don't understand how that limits me at all. I just want to use the downgrade method to hboot 1.4 and s-off. I never had any intention of staying on hboot 1.5, and certainly not hboot 1.58.
Logic33 said:
I don't understand how that limits me at all. I just want to use the downgrade method to hboot 1.4 and s-off. I never had any intention of staying on hboot 1.5, and certainly not hboot 1.58.
Click to expand...
Click to collapse
From my understanding, the downgrade method works with hboot 1.58, but you have to brick your phone twice. But it really is the more challenging method so you may want to reconsider your stance on the wire trick. I've yet to hear of an unhappy customer who followed ramjet's guide.
coal686 said:
From my understanding, the downgrade method works with hboot 1.58, but you have to brick your phone twice. But it really is the more challenging method so you may want to reconsider your stance on the wire trick. I've yet to hear of an unhappy customer who followed ramjet's guide.
Click to expand...
Click to collapse
I'm not sure.
However, this thread can be closed because I *finally* got the RUU to work properly! I was doing things in the wrong order, and not using the .exe was a silly idea. It's much easier that way. Currently have stock ROM running on a locked 1.58 hboot. Now I can continue!
Logic33 said:
I'm not sure.
However, this thread can be closed because I *finally* got the RUU to work properly! I was doing things in the wrong order, and not using the .exe was a silly idea. It's much easier that way. Currently have stock ROM running on a locked 1.58 hboot. Now I can continue!
Click to expand...
Click to collapse
Good! :thumbup:
Keep posting questions, we'll do our best to help.
coal686 said:
Good! :thumbup:
Keep posting questions, we'll do our best to help.
Click to expand...
Click to collapse
LOLJK. I swear, at this point HTC must be trolling me. It's loaded up now. Thanks for trying to help everyone! I can't wait to get Jelly Bean on here soon!
Doubt this will help, but did you remove the PG86IMG.zip from your sd card? Also, did you run the ruu.exe while in bootloader (it will say fastboot usb in red). I'm sort of grasping at straws since the ruu usually works without issue when using the exe.
coal686 said:
Doubt this will help, but did you remove the PG86IMG.zip from your sd card? Also, did you run the ruu.exe while in bootloader (it will say fastboot usb in red). I'm sort of grasping at straws since the ruu usually works without issue when using the exe.
Click to expand...
Click to collapse
I have a feeling you didn't see my update It magically decided to work. Here comes double bricking action... this should be (un)fun D:
i am on hboot 1.58 and used HTC Unlock and wire trick to get s-off. i was about to flash a JB Rom but realized that it requires hboot to be lower than 1.58. so all i do is pick the first hboot 1.40 from Here, put it in the root of SD, boot up the phone in recovery and flash that PG86IMG.zip.
once its done ill swap the SD with another one which would have the ROM i want to install, then boot again in recovery and wipe Dalvik+cache, and then flash ROM?
am i doing it right?
thank you.
chubaan said:
i am on hboot 1.58 and used HTC Unlock and wire trick to get s-off. i was about to flash a JB Rom but realized that it requires hboot to be lower than 1.58. so all i do is pick the first hboot 1.40 from Here, put it in the root of SD, boot up the phone in recovery and flash that PG86IMG.zip.
once its done ill swap the SD with another one which would have the ROM i want to install, then boot again in recovery and wipe Dalvik+cache, and then flash ROM?
am i doing it right?
thank you.
Click to expand...
Click to collapse
No, do it from the bootloader
Sent from my skz_tenderloin using xda premium
fdavila17 said:
No, do it from the bootloader
Sent from my skz_tenderloin using xda premium
Click to expand...
Click to collapse
I have the exact situation with my wife's phone? I want to install Pacman on her phone which is still stock. Is all I have to do what chubaan said?
ruckstande said:
I have the exact situation with my wife's phone? I want to install Pacman on her phone which is still stock. Is all I have to do what chubaan said?
Click to expand...
Click to collapse
Just download the hboot you want, 1.50 or below to get PACMAN to.boot, rename it as PG86IMG.zip place it on the root of your sd card, go to.the bootloader and select yes to apply update , and your done
Sent from my PG86100 using xda premium
Thank you.. that's what I did. And after you're done make sure to wipe dalvik and cache from recovery, at least in my case I had to. And then flash the rom. And that's it..
Sent from my PG86100 using XDA Premium App
Hello all,
Just a quick question, I google'd around a bit with no solid answer. What's the deal with Hboots? Do you need a certain version to run a certain version of AOS? from what I could tell it sounds like toy need the 2.09 or above hboot to run JB. this true? I'm on 1.12 Hboot, stock rooted rom, S-on with TWRP recovery and going for s-off, but apparently need to update my hboot to do so. Is there an Hboot that is more desirable than another? are there still ENG bootloaders out there? Just dont wana bork my phone or myself with this last step.. sheesh, when did rooting get so complicated? Thanks in advance
9X
They have progressively become stricter. Each time a new hboot is released its due to changes made. Patching exploits, adding support for changes in hardware, little things like that. 1.12 was relatively open, 1.15 removed access to areas of the boot partition requiring kernels to be flashed differently, not too sure what 1.19 changed if anything, 2.09 removes r/w access to your system so any changes to system will revert upon reboot.
x9x0 said:
Hello all,
Just a quick question, I google'd around a bit with no solid answer. What's the deal with Hboots? Do you need a certain version to run a certain version of AOS? from what I could tell it sounds like toy need the 2.09 or above hboot to run JB. this true? I'm on 1.12 Hboot, stock rooted rom, S-on with TWRP recovery and going for s-off, but apparently need to update my hboot to do so. Is there an Hboot that is more desirable than another? are there still ENG bootloaders out there? Just dont wana bork my phone or myself with this last step.. sheesh, when did rooting get so complicated? Thanks in advance
9X
Click to expand...
Click to collapse
You only have to update your HBOOT to get S-OFF because the tool to S-OFF the 1.12 HBOOT is no longer supported. After that, there's no reason to touch your HBOOT.
is there a "best" hboot? as in enables the most hardware / most bug fixes / still exploitable?
x9x0 said:
is there a "best" hboot? as in enables the most hardware / most bug fixes / still exploitable?
Click to expand...
Click to collapse
No. They're all S-OFF-able at this point. Just stick with the DirtyRacun HBOOT you get after S-OFF is complete and you'll be fine.
And why is s-off for 1.12 no longer supported? If it's not detrimental anyone know how I can s-off it?
x9x0 said:
And why is s-off for 1.12 no longer supported? If it's not detrimental anyone know how I can s-off it?
Click to expand...
Click to collapse
Because Team Unlimited isn't supporting it anymore. Because it's a simple matter to RUU to a newer version and S-OFF it. There's no reason not to - I don't understand your hesitation.
Just dont want a newer more restrictive hboot period. but here goes 1.15
x9x0 said:
Just dont want a newer more restrictive hboot period. but here goes 1.15
Click to expand...
Click to collapse
Once you're S-OFF, it doesn't matter. Restrictions are all removed.
x9x0 said:
Just dont want a newer more restrictive hboot period. but here goes 1.15
Click to expand...
Click to collapse
The restrictions of Hboot are gone once you're S-off. It's just a number afterwards.
This is regardless of what Hboot you're on
Edit: Captain beat me to it. Hopefully you get the point now
The advice is free....the bandwidth, not so much
FinZ28 said:
The restrictions of Hboot are gone once you're S-off. It's just a number afterwards.
This is regardless of what Hboot you're on
Edit: Captain beat me to it. Hopefully you get the point now
The advice is free....the bandwidth, not so much
Click to expand...
Click to collapse
Not exactly - the stock HBOOTs don't have fastboot commands enabled unless they're unlocked. So while you have the freedom to flash whatever HBOOT you want, it's still best to have one of the DirtyRacun modded HBOOTs to get the full benefit.
Captain_Throwback said:
Not exactly - the stock HBOOTs don't have fastboot commands enabled unless they're unlocked. So while you have the freedom to flash whatever HBOOT you want, it's still best to have one of the DirtyRacun modded HBOOTs to get the full benefit.
Click to expand...
Click to collapse
Very true.
+1 for Captain Throwback.
The advice is free....the bandwidth, not so much
hboot 1.15 s-off completed, thanks guys... just didnt want to do something i was going to regret.
Who on earth would regret soff?
om4 said:
Who on earth would regret soff?
Click to expand...
Click to collapse
Someone who bricked their device because they flashed something they could, but shouldn't have . . . . I will say, there are probably some people that shouldn't S-OFF, just because they'll find a way to break stuff. But I would hope those people don't frequent this forum (though I'd probably be wrong . . . )
Captain_Throwback said:
Someone who bricked their device because they flashed something they could, but shouldn't have . . . . I will say, there are probably some people that shouldn't S-OFF, just because they'll find a way to break stuff. But I would hope those people don't frequent this forum (though I'd probably be wrong . . . )
Click to expand...
Click to collapse
You know better than that
The advice is free....the bandwidth, not so much
Well it seems everybody has had that sort of day even with s-on, at least in this forum. Most of the time it's hardly ever been device wrecking. There was a time when my inbox would flood lol
om4 said:
Well it seems everybody has had that sort of day even with s-on, at least in this forum. Most of the time it's hardly ever been device wrecking. There was a time when my inbox would flood lol
Click to expand...
Click to collapse
Thank God for devs
The advice is free....the bandwidth, not so much
Just didnt want to lockout or loose options. when I started doing this, it was easy to update to a version that sucked, in the process of trying to root or s-off and sometimes there was no way back, you were essentially stuck in limbo. That being said, I've rooted a LOT of phones for my self and other people, and never once bricked a phone. Not to say I havent been in no mans land where 90% of the people out there would call it bricked. Had more than a few looooong night undoing experiments gone bad. Although the victory of escaping brick-dom is super sweet, I Just dont have time right now to visit no mans land, reflow, jtag/reflash again. seems that now the devs have made this pretty much idiot proof, Incredible how far things have come.
x9x0 said:
Just didnt want to lockout or loose options. when I started doing this, it was easy to update to a version that sucked, in the process of trying to root or s-off and sometimes there was no way back, you were essentially stuck in limbo. That being said, I've rooted a LOT of phones for my self and other people, and never once bricked a phone. Not to say I havent been in no mans land where 90% of the people out there would call it bricked. Had more than a few looooong night undoing experiments gone bad. Although the victory of escaping brick-dom is super sweet, I Just dont have time right now to visit no mans land, reflow, jtag/reflash again. seems that now the devs have made this pretty much idiot proof, Incredible how far things have come.
Click to expand...
Click to collapse
Tell me about it. I took my son's OG EVO out last week and finally got S-off via Revolutionary. For $hits and giggles I even got my old Hero out and got it S-off, too. Probably the easiest phone I've done yet-just had to flash a zip file in recovery
The advice is free....the bandwidth, not so much