Related
I rootrd my Thunderbolt using Jcase's manual method shortly after the phone was released. I have the following (unimportant or matching info omitted):
MECHA XD ENG S-OFF
HBOOT 1.04.2000
A friend just rooted using Revolutionary and he has the following:
MECHA XD SHIP S-OFF
HBOOT 6.04.1002
I've been reading some info about Revolutionary and it looks like the program essentially turns off security so you can install SuperUser and flash CWM Recovery. I assume it does not replace the stock (SHIP) bootloader. Does this limit the phone at all? Can he still flash radios through bootloader? What's the easiest/safest way to install the engineering bootloader, or is it even needed?
I noticed that bootloader and CWM both say Revolutionary as well now. Any modifications going on behind the scenes that I may need to know? I ask all of this because his phone has been force closing a lot and "messing up" so I'm going to be fixing it. I've onpy had my hands on the device for about 5 minutes so that's really all of the info I know about it.
Any/all feedback is appreciated!
Sent from my ADR6400L using Tapatalk
joshw0000 said:
I rootrd my Thunderbolt using Jcase's manual method shortly after the phone was released. I have the following (unimportant or matching info omitted):
MECHA XD ENG S-OFF
HBOOT 1.04.2000
A friend just rooted using Revolutionary and he has the following:
MECHA XD SHIP S-OFF
HBOOT 6.04.1002
I've been reading some info about Revolutionary and it looks like the program essentially turns off security so you can install SuperUser and flash CWM Recovery. I assume it does not replace the stock (SHIP) bootloader. Does this limit the phone at all? Can he still flash radios through bootloader? What's the easiest/safest way to install the engineering bootloader, or is it even needed?
I noticed that bootloader and CWM both say Revolutionary as well now. Any modifications going on behind the scenes that I may need to know? I ask all of this because his phone has been force closing a lot and "messing up" so I'm going to be fixing it. I've onpy had my hands on the device for about 5 minutes so that's really all of the info I know about it.
Any/all feedback is appreciated!
Sent from my ADR6400L using Tapatalk
Click to expand...
Click to collapse
Actually, Revolutionary does replace the bootloader. The difference between the ADB method and Revolutionary is that ADB uses a soft-patched engineering bootloader, whereas Revolutionary uses a hard-patched release version of the bootloader.
So basically what you're saying is I can flash another hboot over my hboot and it would take (i.e. I could act stupid and brick the phone) but if you use Revolutionary you can flash whatever in hboot but the actual hboot will not be replaced? Or is there a different meaning implied?
Sent from my ADR6400L using Tapatalk
joshw0000 said:
So basically what you're saying is I can flash another hboot over my hboot and it would take (i.e. I could act stupid and brick the phone) but if you use Revolutionary you can flash whatever in hboot but the actual hboot will not be replaced? Or is there a different meaning implied?
Sent from my ADR6400L using Tapatalk
Click to expand...
Click to collapse
As far as I know, the Revolutionary hboot is patched to prevent flashing over. I don't know all the ins and outs. Never used the newer hboot because... if it's not broke, I don't fix it.
Alright, thanks for sending your thoughts. I don't think anything with the rooting method is causing his problem. I'll reflash the official MR2, do a full wipe, and install a fresh rom. He'll be good as new.
Sent from my ADR6400L using Tapatalk
joshw0000 said:
Alright, thanks for sending your thoughts. I don't think anything with the rooting method is causing his problem. I'll reflash the official MR2, do a full wipe, and install a fresh rom. He'll be good as new.
Sent from my ADR6400L using Tapatalk
Click to expand...
Click to collapse
I hope you're not saying you're going to flash the MR2 RUU.... If you do you'll loose your recovery.
joshw0000 said:
So basically what you're saying is I can flash another hboot over my hboot and it would take (i.e. I could act stupid and brick the phone) but if you use Revolutionary you can flash whatever in hboot but the actual hboot will not be replaced? Or is there a different meaning implied?
Sent from my ADR6400L using Tapatalk
Click to expand...
Click to collapse
Correct. The only way to overwrite revolutionary hboot (that i know of) is to flash a new one with adb.
Sent from my HTC ThunderBolt using Tapatalk
loonatik78 said:
I hope you're not saying you're going to flash the MR2 RUU.... If you do you'll loose your recovery.
Click to expand...
Click to collapse
No I flashed the MR2 radio only. I'm pretty sure he already had that radio but I did it just to make sure.
Sent from my ADR6400L using Tapatalk
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.
ok, so i went through the s-off process and completed it successfully. It asked me if I wanted to flash the jb-hboot.zip which I said yes. Now, when I boot into hboot it has this ugly pink bar accross the top that says "juno..." (the name of the team). I am currently on the new firmware running BAMF Evita sense 4. Is there a stock ics hboot or something i can put back in its place that will leave s-off, be compatible with new firmware and not give custom labels accross the top?
Please help....
jbeitel said:
ok, so i went through the s-off process and completed it successfully. It asked me if I wanted to flash the jb-hboot.zip which I said yes. Now, when I boot into hboot it has this ugly pink bar accross the top that says "juno..." (the name of the team). I am currently on the new firmware running BAMF Evita sense 4. Is there a stock ics hboot or something i can put back in its place that will leave s-off, be compatible with new firmware and not give custom labels accross the top?
Please help....
Click to expand...
Click to collapse
Technically, you could just reflash the leaked RUU then and you will still have S-off. Changing Hboots , won't affect S-off, Numerous threads have popped up with just radio's and Hboots to flash. Just be careful and don't mix and match Radios and Hboots to avoid trouble.
mjh68 said:
Technically, you could just reflash the leaked RUU then and you will still have S-off. Changing Hboots , won't affect S-off, Numerous threads have popped up with just radio's and Hboots to flash. Just be careful and don't mix and match Radios and Hboots to avoid trouble.
Click to expand...
Click to collapse
do I have to relock anything like when I upgraded to the new ics firmware? I was hoping for a straight forware ph98img.zip flash. i know, thats lazy but easy.
IMO, leave it. Put up with eye sore. If the flash to the stock one goes belly up, you will brick the phone. Leave it til you need to go back to an S-On device.
Snuzzo said:
IMO, leave it. Put up with eye sore. If the flash to the stock one goes belly up, you will brick the phone. Leave it til you need to go back to an S-On device.
Click to expand...
Click to collapse
Technically true, but really as long as he doesn't pull the plug while its loading the Hboot its not a great danger.
---------- Post added at 12:03 PM ---------- Previous post was at 12:00 PM ----------
jbeitel said:
do I have to relock anything like when I upgraded to the new ics firmware? I was hoping for a straight forware ph98img.zip flash. i know, thats lazy but easy.
Click to expand...
Click to collapse
I am pretty sure , their hboot is already relocked . So shouldn't have to relock , I went all the way back to GB and used the full exe RUU and relocked since I didn't know that it was locked initially and it ran just fine.
I would try without relocking , it will either run or fail before it starts doing anything.
Thank you mjh. Yes it is relocked & again leave it as is. Trust me you will thank me later. No need for unlock codes anymore and just waiting for roms to be rebased and official OTA(not for the actual OTA but for kernel source if released).
you guys know how to frustrate a guy, geez. What a great world that everyone can have their own opinion. Now, who's do I want to have?
I know exactly how you feel. Cant make up my mind what I want to do either. Currently on ICS S-OFF displaying Tampered/Locked
Do I RUU back to GB and flash the ENG Hboot?
Do I go ahead and flash jb_hboot? And which one is it actually. There have been way to many threads and posts on S-OFF and a bunch of different answers.
Do I leave it alone and wait to see what happens with the next release?
In some ways it would be nice to be back on Hboot 2.11 and have ENG S-off but is it worth it? Wont really know until the next official release comes out.
jbeitel said:
you guys know how to frustrate a guy, geez. What a great world that everyone can have their own opinion. Now, who's do I want to have?
Click to expand...
Click to collapse
I am not telling not to flash, just telling you after S-off and using their Hboot it is already locked, but you can still flash the stock RUU. I did and haven't had any issues , but I didn't realize it was already locked so relocked and unlocked by HTC dev without knowing it . I am still tempted to flash the eng hboot , but not sure if I really have a need to.
mjh68 said:
I am not telling not to flash, just telling you after S-off and using their Hboot it is already locked, but you can still flash the stock RUU. I did and haven't had any issues , but I didn't realize it was already locked so relocked and unlocked by HTC dev without knowing it . I am still tempted to flash the eng hboot , but not sure if I really have a need to.
Click to expand...
Click to collapse
whats the big deal with the engineering hboot? is it different or is that the standard one in the ruu?
Snuzzo said:
No need for unlock codes anymore
Click to expand...
Click to collapse
There is more difference than this(allows more commands to be ran in prompts) but with an ENG hboot, you can keep it locked and s-off, along with still being able to flash anything your heart desires. ALTHOUGH if you wish to go back to s-on, flash an RUU of your choice first. As when you do write secureflag and a few reboots on an ENG hboot, you could brick.
Leave the hboot they give you. The tag might be annoying but it is better than having to re-unlock to use fastboot commands.
Why is un- re locking not ideal? It takes 2 minutes.
Sent from my v6 supercharged Rezound.
AJMetal87 said:
Why is un- re locking not ideal? It takes 2 minutes.
Sent from my v6 supercharged Rezound.
Click to expand...
Click to collapse
Scotty posted earlier if your S-OFF then unlock and relock again it will alway show relocked again unless you RUU then S-ON and then S-OFF again. If you S-OFF and don't unlock it and RUU it will say locked but its best to use the patched hboots supplied to be able to use certain fastboot commands that way you don't have to unlock and not have a problem with it saying relocked.
Sent from my ICS Rezound
LakerStar25 said:
Scotty posted earlier if your S-OFF then unlock and relock again it will alway show relocked again unless you RUU then S-ON and then S-OFF again. If you S-OFF and don't unlock it and RUU it will say locked but its best to use the patched hboots supplied to be able to use certain fastboot commands that way you don't have to unlock and not have a problem with it saying relocked.
Sent from my ICS Rezound
Click to expand...
Click to collapse
Aside of the text difference on the bootloader and potential warranty comprimising, is there any other downfall?
No downfall. But again, nor needed to unlock if s-off.
Sent from my ADR6425LVW using XDA
I'm not trolling or trying to start a argument, but if that's a big deal to you to have the pink junabear banner across your hboot screen then you should have never s-off. I mean really. Who sits there and stares at the hboot screen and decides that it doesn't look good. Lmao.
Sent from my ADR6425LVW using XDA
Especially when the stock hboot uses the same color banner but says locked instead?
Via Rezound using XDA Premium
GB
Anyone who was on Gingerbread when the did S-Off does *NOT* have the Juououuoouououpnutbear logo; just standard Eng HBoot.
This would be me.
Bump. I need the stock Hboot to send back to Verizon. The GB hboot if anyone has it please.
I'm on 3.14 stock ruu, unlocked bootloader, amonra in the recovery
do I need to flash something like the "3.14 stock deodexxed root"
or can I just finally try to s-off?
thanks <3
Watercycle said:
I'm on 3.14 stock ruu, unlocked bootloader, amonra in the recovery
do I need to flash something like the "3.14 stock deodexxed root"
or can I just finally try to s-off?
thanks <3
Click to expand...
Click to collapse
the su binary MUST be present in the system for the S-OFF process to work correctly, so yes, you must root.
Since you have Amon ra installed, just boot into that, go to the developer menu and install the su binary, then do S-OFF
a.mcdear said:
the su binary MUST be present in the system for the S-OFF process to work correctly, so yes, you must root.
Since you have Amon ra installed, just boot into that, go to the developer menu and install the su binary, then do S-OFF
Click to expand...
Click to collapse
unguarded or super user? and thank you i didn't know about that =)
Watercycle said:
unguarded or super user? and thank you i didn't know about that =)
Click to expand...
Click to collapse
Sueperuser not unguarded
this is the most rediculous process ever! (currently trying to wire trick) I'VE USED 2 DARN TYPES OF WIRE AND A PAPERCLIP AND NONE OF THEM DO ANYTHING
oh god, whew... i was running around the house making a wire out of everything...
but after trying the paperclip for like the 8th time (which took a half hour to find) it seems to have worked
S-off is the most stressful android activity ever >XO
thanks you two <3
You did use the ics jb hboot right? Make sure you can see the sd card? And don't unlock your phone again. You would need to s-on then s-off again for it to say locked. I just woke up and saw your new posts, its been a long day but I see you got help. Welcome to the club, glad it finally worked.
sent from my Clean Rezound
I used the Hboot that came with 3.14 Ruu, if S-off took the "relocked" away then i'm happy, if it didn't, oh well, but I was unlocked when I started the process =o
As long as you don't unlock it after s-off, it will be locked again ( although it says "juopunutbear" instead of "locked" if you're using their modified boot. Just flash a stock one and it will say locked)
I'm still not to sure why people keep bringing up the Hboot, is it because if you flash S-off's it will break it?
I declined the modified version and everything appears to be working
Watercycle said:
I'm still not to sure why people keep bringing up the Hboot, is it because if you flash S-off's it will break it?
I declined the modified version and everything appears to be working
Click to expand...
Click to collapse
The patched hboot adds some advanced fast boot commands. However everything will work without the patched hboot. You don't need it its just nice to have
Watercycle said:
I'm still not to sure why people keep bringing up the Hboot, is it because if you flash S-off's it will break it?
I declined the modified version and everything appears to be working
Click to expand...
Click to collapse
The juoponut bear hboot is an eng hboot that allows for adb commands and other options most people will not need.
The h boot issue is thus......in the event you want your phone returned to stock (s on and locked in downloader), after gaining s off do NOT HTC unlock the phone.
If you don't unlock it and want to return to stock you basically run a ruu, and then write the secure flag back to s on (scotty123 has a thread how to do this). After which point you phone will be on stock Rom, recovery and h boot will say locked and s on. Just like the day you first got the phone.
If you unlock after s off (as an early adopter I did) your bootloader will only say unlocked or relocked. You can run ruus, and write secure flag to s on.....BUT your hboot will say relocked or unlocked. And to a trained eye, someone can tell you tampered with it (running Roma,etc)
In my case, I had to follow scottys thread, s on, and do the s off process all over again. Early on we thought flashing a ruu would change the hboot status from relocked to locked. However we were mistaken.
So, don't unlock after s off.
If you can't run adb commands with your h boot and don't want to flash an eng hboot, use the ph98img.zip method to flash things (ex recovery, hboots, radios).
Sent from my Rezound
ericsignals said:
The juoponut bear hboot is an eng hboot that allows for adb commands and other options most people will not need.
The h boot issue is thus......in the event you want your phone returned to stock (s on and locked in downloader), after gaining s off do NOT HTC unlock the phone.
If you don't unlock it and want to return to stock you basically run a ruu, and then write the secure flag back to s on (scotty123 has a thread how to do this). After which point you phone will be on stock Rom, recovery and h boot will say locked and s on. Just like the day you first got the phone.
If you unlock after s off (as an early adopter I did) your bootloader will only say unlocked or relocked. You can run ruus, and write secure flag to s on.....BUT your hboot will say relocked or unlocked. And to a trained eye, someone can tell you tampered with it (running Roma,etc)
In my case, I had to follow scottys thread, s on, and do the s off process all over again. Early on we thought flashing a ruu would change the hboot status from relocked to locked. However we were mistaken.
So, don't unlock after s off.
If you can't run adb commands with your h boot and don't want to flash an eng hboot, use the ph98img.zip method to flash things (ex recovery, hboots, radios).
Sent from my Rezound
Click to expand...
Click to collapse
Well everything is right but the first part, the modified hboot allows you to perform fastboot commands that would otherwise require you to unlock the bootloader
Fastboot flash, fastboot boot... Etc.
Sent from my ADR6425LVW using Tapatalk 2
superchilpil said:
Well everything is right but the first part, the modified hboot allows you to perform fastboot commands that would otherwise require you to unlock the bootloader
Fastboot flash, fastboot boot... Etc.
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
Forgot to add that part when I typed the adb part ....thanks for correcting me.:thumbup:
Sent from my Rezound
oh dear, so without that Hboot command prompt won't be able to fastboot into recovery and whatnot?
Watercycle said:
oh dear, so without that Hboot command prompt won't be able to fastboot into recovery and whatnot?
Click to expand...
Click to collapse
Yes, but there are ways around that
I personally just package my own ph98img.zips if I need to flash a kernel or recovery after doing something dumb
Sent from my ADR6425LVW using Tapatalk 2
If you want to add the JB Hboot, it is very simple. You can go to their site and just download the most recent hboot. You must know if you are ICS or GB. But go here: http://unlimited.io/hboot-downloads/ and download the right one, either vigor ics or vigor gb. Put that in the folder where you had put the original controlbear program and follow these instructions:
To flash the JuopunutBear hboots
Put the phone in fastboot mode, connected to the pc and enter the following commands
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip jb_hboot.zip
Thats all there is to it and you can now benefit from the JB Hboot.
I thought you needed to be unlocked with htc dev to gain s-off? Now I'm hearing that I should not unlock my phone before I s-off?
Yes you need to be unlocked. It's part of the prerequisites. Please read then reread the thread in general "s-off with instructions...it's official". Understand how to avoid problems and fix them if they arise. It's very easy but it's like people half ass reading the instructions recently. Don't be that person.
sent from my Clean Rezound
th3rapist said:
I thought you needed to be unlocked with htc dev to gain s-off? Now I'm hearing that I should not unlock my phone before I s-off?
Click to expand...
Click to collapse
You have to unlock befor you s off, afterwards it's redundant to do so. But some people have
Sent from my ADR6425LVW using Tapatalk 2
doubleshot, ruby ICS, vigor ICS, holiday ICS, pyramid ICS?
which one? haha
I don't mind don't 1 more small flash that will probably be necessary in the future as long as it doesn't screw my current rom up
<MOD EDIT>
THIS IS NOT SAFE FOR REGAINING S-OFF
DO NOT PERFORM THIS METHOD IF YOU WISH TO KEEP S-OFF
</MOD EDIT>
So i didnt want to wait for the devs to update thier roms, and i wanted the radio updates as well. for all those ppl say not to do the OTA you will losew root until a new method is found are not correct. Yes you will lose root, but you can get it back. and its easy. Here are the steps
1. Relock boot loader
2. apply RUU for the same rom version you are running http://forum.xda-developers.com/showthread.php?t=1645890
3. rerun RegawMOD EVO 4G LTE Rooter
3a. It will sucessfully unlock and flash the recovery on your phone, but it will fail to root it.
3b. Download the rooting files http://downloadandroidrom.com/file/HTCEvo4GLTE/rooting/Evo4GLTERoot2.zip
4. Extract the contents of the zip file
5. Copy the file CWM-SuperSU-v0.87.zip to your SD card
6. Reboot to recovery
7. Flash CWM-SuperSU-v0.87.zip
8. Reboot to system and Viola you have have a rooted install
But can you still unlock with Lazy Panda?
EDIT: I realize you can unlock with the RegawMod unlock, but I have no doubt HTC's unlock tool will work.
Try to lazy panda your new hboot
{ParanoiA} said:
Try to lazy panda your new hboot
Click to expand...
Click to collapse
This is really the main(only?) concern.
Sent from my LTEvo
You are not correct. People are not saying "Don't do the OTA because you'll lose root", they're saying "Don't do the OTA because you'll lose the ability to S-OFF".
This happened with the Evo 3D. We had S-OFF for HBOOT 1.4, and then an OTA comes that upgrades to HBOOT 1.5. The S-OFF exploit was patched with 1.5, making it damn near impossible to S-OFF.
Seriously. If you're even remotely considering S-OFF, don't bother with applying the OTA. Wait for ROM devs to incorporate the OTA into their custom ROMs, because they will do it in a way that doesn't change your HBOOT or any other sensitive partition.
LiquidSolstice said:
You are not correct. People are not saying "Don't do the OTA because you'll lose root", they're saying "Don't do the OTA because you'll lose the ability to S-OFF".
This happened with the Evo 3D. We had S-OFF for HBOOT 1.4, and then an OTA comes that upgrades to HBOOT 1.5. The S-OFF exploit was patched with 1.5, making it damn near impossible to S-OFF.
Seriously. If you're even remotely considering S-OFF, don't bother with applying the OTA. Wait for ROM devs to incorporate the OTA into their custom ROMs, because they will do it in a way that doesn't change your HBOOT or any other sensitive partition.
Click to expand...
Click to collapse
Sure you may lose the ability to "S-OFF" but in all honesty, with these phones I can do every thing with S-ON, that you can do with S-OFF, except i have a couple of extra steps. Honestly the only reason i would S-OFF is to flash the radios easier. but how many times do you acutually flash a different radio to your phone? I do about every time there is a new update.
This is really for the people the HTC and RegawMod Unlock. Lazy Panda ppl continue to heed the disclaimer. I have no desire to completly S-OFF, unless someone can come with with a compelling reason to do so.
HseloMein said:
Sure you may lose the ability to "S-OFF" but in all honesty, with these phones I can do every thing with S-ON, that you can do with S-OFF, except i have a couple of extra steps. Honestly the only reason i would S-OFF is to flash the radios easier. but how many times do you acutually flash a different radio to your phone? I do about every time there is a new update.
This is really for the people the HTC and RegawMod Unlock. Lazy Panda ppl continue to heed the disclaimer. I have no desire to completly S-OFF, unless someone can come with with a compelling reason to do so.
Click to expand...
Click to collapse
Dude, just listen to LiquidSolstice on this one. DO NOT OTA an already S-OFF PHONE! Literally in a few hours we will probably have a stock / rooted ROM posted. Just have patience.
HseloMein said:
Sure you may lose the ability to "S-OFF" but in all honesty, with these phones I can do every thing with S-ON, that you can do with S-OFF, except i have a couple of extra steps. Honestly the only reason i would S-OFF is to flash the radios easier. but how many times do you acutually flash a different radio to your phone? I do about every time there is a new update.
This is really for the people the HTC and RegawMod Unlock. Lazy Panda ppl continue to heed the disclaimer. I have no desire to completly S-OFF, unless someone can come with with a compelling reason to do so.
Click to expand...
Click to collapse
The compelling reason to S-OFF is the fact that HTC and Sprint are never made aware in the slightest that you have done anything to your phone. The Dev unlock runs and tells HTC and Sprint that you are messing with your device. If done correctly, S-OFF gives you complete unfettered access to your phone, and with the proper tools, you can ensure you don't have to deal with the warning text on the screen that almost criminalizes you for having the audacity to unlock your phone.
People who are S-ON and HTC Dev unlocked ultimately run into strange issues down the road. You just wait until full AOSP comes around. On the Evo 3D, it was a nightmare. Even on the One-X, they're having issues because their boot partition is still locked and they can't use custom kernels (though I don't think that's as much of an issue with our phones).
S-OFF is so easy to perform, and the ONLY type of soft-brick that sometimes happens when performing it can be easily fixed with a dedicated tool. There is literally no downside to being S-OFF.
HseloMein said:
with these phones I can do every thing with S-ON, that you can do with S-OFF
Click to expand...
Click to collapse
I'd love to see you have the H-boot say S-ON and ***locked*** while still rooted
While your at it, go ahead try to remove the red HTC text as well.
HseloMein said:
Sure you may lose the ability to "S-OFF" but in all honesty, with these phones I can do every thing with S-ON, that you can do with S-OFF, except i have a couple of extra steps. Honestly the only reason i would S-OFF is to flash the radios easier. but how many times do you acutually flash a different radio to your phone? I do about every time there is a new update.
This is really for the people the HTC and RegawMod Unlock. Lazy Panda ppl continue to heed the disclaimer. I have no desire to completly S-OFF, unless someone can come with with a compelling reason to do so.
Click to expand...
Click to collapse
Lol so much fail. Good luck with that bro. I'm keeping my s-off
No one should follow this guy. You better hope it doesn't come back to bite you in the ass.
And you sir are in denial.
Sent from my EVO using xda premium
Rxpert said:
I'd love to see you have the H-boot say S-ON and ***locked*** while still rooted
While your at it, go ahead try to remove the red HTC text as well.
Click to expand...
Click to collapse
And although this may seem like just a visual thing, I have a friend who sent his phone in Dev unlocked and they denied his Google Wallet claim to replace the phone.
He then got his phone S-OFF'd through LazyPanda, changed the bootloader text, and sent it in again, and granted, I didn't think it would go through, but they accepted it that time.
LiquidSolstice said:
And although this may seem like just a visual thing, I have a friend who sent his phone in Dev unlocked and they denied his Google Wallet claim to replace the phone.
He then got his phone S-OFF'd through LazyPanda, changed the bootloader text, and sent it in again, and granted, I didn't think it would go through, but they accepted it that time.
Click to expand...
Click to collapse
Well that is a compelling reason for me, but i still think the 1st post is good for ppl that do not want to S-OFF after doing an HTC unlock. Im sure there are other users out there like me. The disclaimers and watermarks dont bother me in the slightest.
HseloMein said:
Well that is a compelling reason for me, but i still think the 1st post is good for ppl that do not want to S-OFF after doing an HTC unlock. Im sure there are other users out there like me. The disclaimers and watermarks dont bother me in the slightest.
Click to expand...
Click to collapse
While I respect your choice, I must also respectfully disagree with it. Regardless of what I think, you did take the time to explain how to re-root, and for that, I can't fault you. Thanks for your contribution.
HseloMein said:
Well that is a compelling reason for me, but i still think the 1st post is good for ppl that do not want to S-OFF after doing an HTC unlock. Im sure there are other users out there like me. The disclaimers and watermarks dont bother me in the slightest.
Click to expand...
Click to collapse
A recognized developer warning us should be enough reason.
OMG pbedard thanking my post? The world has just ended, lol.
Nice to see you again pbedard
Forgive me if this is a stupid question, but if you do accept the new update and lose S-OFF can you not just run the original RUU to get back to the release image which allows you to S-OFF again?
Once you apply the ota it installs a new hboot that blocks the current s-off method so keep that in mind. I don't know if running a ruu reverts the hboot.
Sent from my EVO 4G LTE
RoidPusher said:
Forgive me if this is a stupid question, but if you do accept the new update and lose S-OFF can you not just run the original RUU to get back to the release image which allows you to S-OFF again?
Click to expand...
Click to collapse
Nope. Keep your hboot. It can be difficult if not impossible to downgrade hboot.
Sent from an EVO 4G LTE using Tapatalk 2.
HseloMein, would you mind editing the title of this thread (maybe add [S-ON] at the beginning) to indicate that it may affect the ability to get S-OFF in the future.
david279 said:
Once you apply the ota it installs a new hboot that blocks the current s-off method so keep that in mind. I don't know if running a ruu reverts the hboot.
Sent from my EVO 4G LTE
Click to expand...
Click to collapse
Is this fact or assumption on the HBOOT Update? I'm S-off and no damn way am I taking the update BUT I thought I'd ask just for general knowledge. Back on the 3D, while we did get the HBOOT update, at least if you were S-off before the HBOOT update you held on to that and weren't stuck like chuck with HBOOT 1.50.000, what a nightmare. We were able to downgrade the HBOOT as long as you were S-off but why go through all that pain. I guess the saving grace here is that we really do have a pretty good "official" Dev unlock that doensn't totally screw you like the half baked unlock we got from HTC for the EVO 3D.
I need to get the word out to any and all LTE owners I know to not take it before I can S-off their phones.... might be a busy rest of the week! :laugh:
Thanks