Greetings! I hope you are having a fine day!
I am writing this to try to alleviate future issues for some of you.
Sunday night, I posted instructions for installing a certain update manually. Now, I am S-Off, and just assumed when I wrote it that anybody else flashing stuff like that would be too. This was apparently my mistake.
So in an effort to try to prevent future problems I am writing this, and hoping many of you will read it, and pay attention. Although I know that usually doesn't happen.
So, here we go:
If you are planning to manually flash anything other than a ROM, you should be S-Off. There is no excuse not to be, and no reason you shouldn't do it.
First, it's completely reversible. Second, it removes the "Unlocked" message from your phone.
It prevents the mainver older issue.
It lets you pretty much flash anything you want, whenever you want, as long as the phone is physically able. This means, if you flash something and it goes wrong, you can flash backwards to what you had before.
After S-Off, you DO NOT HAVE TO UNLOCK!!!!!! I cannot say this enough. S-Off is a step beyond unlocking. This is why we do it!
Reverting to S-On is as simple as flashing a full, released, OTA RUU and issuing a fastboot command to change the flag. Although the only reason I could see to do that is to return the phone.
If you aren't sure that a set of directions apply to you, ask first!
If you are following the directions, and something goes wrong, STOP!!!!!! Do not guess what to do, or try to go backwards unless you know for a fact it will work. Go online and ask for help. If you ask properly, somebody will help you. Some people live for the chance to help others.
When asking for help, say what you had before you started, what you were trying to do (with a link), what step you were on, and what the unexpected result was. POST THE EXACT MESSAGES!!!! Not an abbreviated version.
If a post does not specify that you need to be S-Off, read through the instructions before you start. If you see anything to do with a PH98IMG.zip file, or going into HBOOT, assume you should S-Off first. Simply to be safe.
I know this was all disjointed, but I was simply posting my responses to issues I see all too often that could easily have been avoided, or resolved much easier.
So, to sum up.
S-Off Your Phone!
Thank you!
D
.
dsb9938 said:
So, to sum up.
S-Off Your Phone!
Thank you!
D
.
Click to expand...
Click to collapse
Exactly. Plus educate yourself.
Sent from my ADR6425LVW using Tapatalk 2
also, to add on, if you want to revert to s-on, RUN AN RUU FIRST!!!!!! it will brick your phone if you s-on on a modified/unsigned hboot!! although it is reversible (as i did tonight...derp) it was annoying. also if you want a guide on how to unbrick a rezound bricked by writing security flag 3 with an unsigned hboot, or caused by a damaged hboot via interrupted OTA update/RUU flash on a S-ON device, i will gladly do it, all props to meadows btw
Thanks for the write up.
To be honest I am not sure what to do to update my firmware from that 100mb ota after reading that thread several times. Or if I even need to if I don't have a use for the gsm stuff. I am s-off though.
Edit: I forgot to mention, I am running ics firmware on the viper rom.
If I were a dev, I wouldn't include any options for s-on. It's simple to do, safe enough, and not scary at all.... It makes everyone's life much easier.
Nice thread, dsb9938, and right on point. Problem is, nobody reads. Nobody looks at the threads above and nobody searches. Alright, not nobody, but not enough people. The way I see it, if you are going to take the responsibility for manipulating the innards of your $200 handset, the least you could do is poke around for the right way to do things before just messing around and thinking Dad will buy you a new handset when you bork it. This Dad won't.
XDA is for people who take responsibility. If you can't handle that, please go play in someone else's sandbox.
If I had a dollar for every post in another current thread here that reflects users not reading posts only a page above, not checking stickies first, not using the search function, or just plain trolling, I could buy several Rezounds just to mess with and still have money left over for a Nexus 7.
/end rant
Sent into the innertubes from my Arnova 10 G2.
hgoldner said:
Nice thread, dsb9938, and right on point. Problem is, nobody reads. Nobody looks at the threads above and nobody searches. Alright, not nobody, but not enough people. The way I see it, if you are going to take the responsibility for manipulating the innards of your $200 handset, the least you could do is poke around for the right way to do things before just messing around and thinking Dad will buy you a new handset when you bork it. This Dad won't.
XDA is for people who take responsibility. If you can't handle that, please go play in someone else's sandbox.
If I had a dollar for every post in another current thread here that reflects users not reading posts only a page above, not checking stickies first, not using the search function, or just plain trolling, I could buy several Rezounds just to mess with and still have money left over for a Nexus 7.
/end rant
Sent into the innertubes from my Arnova 10 G2.
Click to expand...
Click to collapse
While everything you said is true, people just need to be nicer to each other. We are all here to help each other, no need to be mean about it. :highfive:
antp121 said:
also, to add on, if you want to revert to s-on, RUN AN RUU FIRST!!!!!! it will brick your phone if you s-on on a modified/unsigned hboot!! although it is reversible (as i did tonight...derp) it was annoying. also if you want a guide on how to unbrick a rezound bricked by writing security flag 3 with an unsigned hboot, or caused by a damaged hboot via interrupted OTA update/RUU flash on a S-ON device, i will gladly do it, all props to meadows btw
Click to expand...
Click to collapse
Lol that's in giant font on the s-off tutorial.
Yet you still failed.
Sent from my NeoMax Rezound
wlmeng11 said:
Lol that's in giant font on the s-off tutorial.
Yet you still failed.
Sent from my NeoMax Rezound
Click to expand...
Click to collapse
I ruu'd that morning. I was playing mw3 and I completely spaced. It's all good now so does it matter?
Sent from my ADR6425LVW using Tapatalk 2
OK so im s-off do i need to "fastboot oem lock" before updating to the latest RUU????
synisterwolf said:
OK so im s-off do i need to "fastboot oem lock" before updating to the latest RUU????
Click to expand...
Click to collapse
It kills me when people actually have no idea about things like that. I mean that's just common knowledge and could be found with a 5 minute Google search
AshtonTS said:
It kills me when people actually have no idea about things like that. I mean that's just common knowledge and could be found with a 5 minute Google search
Click to expand...
Click to collapse
Google?
Sent from my iPhone...
86shelby said:
If I were a dev, I wouldn't include any options for s-on. It's simple to do, safe enough, and not scary at all.... It makes everyone's life much easier.
Click to expand...
Click to collapse
With all due respect alienating any portion of your user base is generally not good. I'm not s-off but it's only because I haven't been around a pc that's got an internet connection. I appreciate how easy it is but there are still those of us that have life situations that haven't allowed for the whole process yet.
Sent from my ADR6425LVW using xda premium
Geoi1006 said:
With all due respect alienating any portion of your user base is generally not good. I'm not s-off but it's only because I haven't been around a pc that's got an internet connection. I appreciate how easy it is but there are still those of us that have life situations that haven't allowed for the whole process yet.
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
You could download the stuff to your phone and transfer it via USB to your computer, or you could use tethering.
It's called being resourceful
I see you talking but all I'm seeing is talking down to people. Trying to decide where the constructive portion of this thread is.
Sent from my ADR6425LVW using xda premium
I agree more people need to read and remember the rules and posts like this as well. Thank you for posting this, however i do disagree with one thing. I recently upgraded my firmware to the ICS update OTA(not the ICS update itself but the update that was pushed shortly after) which updated my hboot to 2.27, Locked. All is fine until I needed to flash a boot.img because of boot manager. No big deal until I get a "remote not allowed" return on a fastboot flash boot boot.img command. For some reason I can not for the life of me create a flashable zip to be flashed in recovery, and I'm too lazy to take my sdcard out to put a PH98IMG.ZIP file on there to flash boot.img in bootloader. So I had to unlock my bootloader to perform the fastboot command needed to get my phone back. Until there is a patched hboot 2.27, you will need to unlock your bootloader, or downgrade to jb_hboot. Just my 2 cents...
Great post. Thanks for writing it up.
I tried numerous times to get s off, and it just didnt work for me. I dont have a land line or a spare phone so I am very dependant on my phone. I can't have it in non working phone.
I appreciate all the work the drvs do and all the people who help us out to make our phones top notch. However, I do like how the devs have s on and s off roms
I don't S-Off because brickings are always possible when S-Off, and S-On hasn't really inconvenienced me.
AshtonTS said:
You could download the stuff to your phone and transfer it via USB to your computer, or you could use tethering.
It's called being resourceful
Click to expand...
Click to collapse
Geoi1006 said:
I see you talking but all I'm seeing is talking down to people. Trying to decide where the constructive portion of this thread is.
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
That's definitely talking down to people. It's a big wave of arrogance emitting from this thread. Keep in mind a lot of these dudes are young Btw.
Sent from my ADR6425LVW using xda premium
scy1192 said:
I don't S-Off because brickings are always possible when S-Off, and S-On hasn't really inconvenienced me.
Click to expand...
Click to collapse
Actually, bricking your phone, as unlikely as that is, is less likely when s-off since there are more options to recovery if you mess up.
D
.
Related
So I kind of thought that once any temp root was established, that one could write a recovery which would in turn, enable the ability to flash a rooted ROM... thus giving a semi-perm root....
Why can we not do this?
Are we unable to flash a recovery with our temp root?
Or does flashing a recovery require S-OFF? Which, pardon me if I am mistaken, but I thought we DIDN'T have S-OFF in the beginning when we were doing the 4Gs yet we were still able to flash rooted ROMs.
And if it is an eng bootloader we need, don't we have one for the 3D?
From what I understand, the partition where we can write the eng hboot is encrypted, so we need to get around that before we can do anything major.
Dont complain atleast you guys have some form of root
Sent from my htc evo 4g gingerscrewd
edufur said:
So I kind of thought that once any temp root was established, that one could write a recovery which would in turn, enable the ability to flash a rooted ROM... thus giving a semi-perm root....
Why can we not do this?
Are we unable to flash a recovery with our temp root?
Or does flashing a recovery require S-OFF? Which, pardon me if I am mistaken, but I thought we DIDN'T have S-OFF in the beginning when we were doing the 4Gs yet we were still able to flash rooted ROMs.
And if it is an eng bootloader we need, don't we have one for the 3D?
Click to expand...
Click to collapse
I thought the same thing. But its a different hboot, needing different things. Idk the mechanics of it all, but obviously we would have done that by now if tht were true..
Just a heads up, prepare to get possibly flammed
the problem is that we dont have enough arrogant, ignorant, impatient ass holes making posts implying that the devs are incompetent. so for that, i thank you for doing your part to help
you obviously have no idea what is involved in cracking this phone open. threads like this do nothing but discourage people who are doing this for FUN. so do us all a favor and do some research before making a new thread. you know, maybe get a clue about what you are talking about first?
My post wasnt ment to insult ot was ment to inply that you sould be thankfull for what the devs have been able to acheve for you if you want it faster try it yourself
Sent from my PC36100 using XDA App
Omgadroid said:
My post wasnt ment to insult ot was ment to inply that you sould be thankfull for what the devs have been able to acheve for you if you want it faster try it yourself
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
my post was aimed at no one other than the op
Easy fellas, I think he was just genuinly curious, not condecsendingly asking why.
ill break it down the best i can, this phone is very well secured. all previously know exploits have been patched. additionally s-on seems to be controlled by the radio and checks its integrity in the hboot on boot up. this means not only will the hboot need to be modified but also this checking at boot. anything trying to be flashed is also checked against a private signature which cannot be "hacked" of duplicated or tricked etc etc. also, the s-on prevents any writing to system partitions without passing the signature check.
so to sum it up,
cannot crack signature
cannot write to system
cannot replace hboot/radio/kernal/recovery without signature
cannot modify radio since cannot write to system partitions
basically up **** creek as the saying goes. the above reasons are why we only have temp root as any changes to system areas of the phone are wiped with a reboot since you never actually wrote those values due to system partitions being locked.
older phones, ie og evo did not have the level of protections that this phone/sensation have. this is a whole new beast and will take time. follow the root thread and read before making stupid assumptions.
I kno u wernt targeting me i just didnt want to offend
Btw have u herd anything about the
Evo 4g
Sent from my PC36100 using XDA App
Omgadroid said:
I kno u wernt targeting me i just didnt want to offend
Btw have u herd anything about the
Evo 4g
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Bout what? its latest update?
Omgadroid said:
I kno u wernt targeting me i just didnt want to offend
Btw have u herd anything about the
Evo 4g
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
nope, in the same boat. new gingerbread update and hboot closed all known holes.
Oh ok im not much of a tec on android i just know my servers lol thanks
Sent from my PC36100 using XDA App
DomSim said:
ill break it down the best i can, this phone is very well secured. all previously know exploits have been patched. additionally s-on seems to be controlled by the radio and checks its integrity in the hboot on boot up. this means not only will the hboot need to be modified but also this checking at boot. anything trying to be flashed is also checked against a private signature which cannot be "hacked" of duplicated or tricked etc etc. also, the s-on prevents any writing to system partitions without passing the signature check.
so to sum it up,
cannot crack signature
cannot write to system
cannot replace hboot/radio/kernal/recovery without signature
cannot modify radio since cannot write to system partitions
basically up **** creek as the saying goes. the above reasons are why we only have temp root as any changes to system areas of the phone are wiped with a reboot since you never actually wrote those values due to system partitions being locked.
older phones, ie og evo did not have the level of protections that this phone/sensation have. this is a whole new beast and will take time. follow the root thread and read before making stupid assumptions.
Click to expand...
Click to collapse
I thought the @secu flag has always been set by the radio config. Hence the difference between eng s-off and radio s-off. Meaning an eng h-boot doesn't actually change the flag, it is just made so the radio thinks its off allowing for manufacturer testing and development. No offense intended to anyone. Just curious if I'm wrong or if that had changed.
Sent from my HTC Thunderbolt
DomSim said:
the problem is that we dont have enough arrogant, ignorant, impatient ass holes making posts implying that the devs are incompetent. so for that, i thank you for doing your part to help
you obviously have no idea what is involved in cracking this phone open. threads like this do nothing but discourage people who are doing this for FUN. so do us all a favor and do some research before making a new thread. you know, maybe get a clue about what you are talking about first?
Click to expand...
Click to collapse
The OP isnt the one being an arrogant ass hole here.
How could anyone be discouraged by an honest question? really?
This is the Q&A section, is it not?
He is not the only person with this question and unless you fully understand whats involved, searching isnt going to make things any easier.
If you want to police this thread then maybe you should become a moderator.
Until then keep it to youself, the devs can speak for themselves,
DomSim said:
the problem is that we dont have enough arrogant, ignorant, impatient ass holes making posts implying that the devs are incompetent. so for that, i thank you for doing your part to help
you obviously have no idea what is involved in cracking this phone open. threads like this do nothing but discourage people who are doing this for FUN. so do us all a favor and do some research before making a new thread. you know, maybe get a clue about what you are talking about first?
Click to expand...
Click to collapse
So i keep coming on here looking for updated info on whats going on with perm root. When temp root was first established it sounded like perm root was right around the corner. I have not found a solid thread or place to find updated info, without those things questions like this in the Q AND A section are going to come up.
So how about instead of being a arrogant, ignorant, impatient ass hole(copy and pasted if you couldn't tell), you kindly direct people to a place where this info is available and answer the question.
Drewmungus said:
So i keep coming on here looking for updated info on whats going on with perm root. When temp root was first established it sounded like perm root was right around the corner. I have not found a solid thread or place to find updated info, without those things questions like this in the Q AND A section are going to come up.
So how about instead of being a arrogant, ignorant, impatient ass hole(copy and pasted if you couldn't tell), you kindly direct people to a place where this info is available and answer the question.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1140578
Here you go
Sent from my PG86100 using XDA App
DomSim said:
the problem is that we dont have enough arrogant, ignorant, impatient ass holes making posts implying that the devs are incompetent. so for that, i thank you for doing your part to help
you obviously have no idea what is involved in cracking this phone open. threads like this do nothing but discourage people who are doing this for FUN. so do us all a favor and do some research before making a new thread. you know, maybe get a clue about what you are talking about first?
Click to expand...
Click to collapse
whether or not there exist posts like this will definitely not discourage someone, sometime, from cracking this thing open. In other words, it will happen no matter how much one nags or not. Posts like yours are just as discouraging to those who have the potential to donate to developers. Kettle meet pot.
A.Priori said:
whether or not there exist posts like this will definitely not discourage someone, sometime, from cracking this thing open. In other words, it will happen no matter how much one nags or not. Posts like yours are just as discouraging to those who have the potential to donate to developers. Kettle meet pot.
Click to expand...
Click to collapse
oh i know im an ass hole. but i do my research before making making posts or asking questions. seriously, everything the op needed to know is in the sticky threads. is it really that hard to find? he could have also used the search function. point is, making threads like, "whats taking you so long?" is insulting. a tiny bit of reading could have save him from it.
JBO1018 said:
I thought the @secu flag has always been set by the radio config. Hence the difference between eng s-off and radio s-off. Meaning an eng h-boot doesn't actually change the flag, it is just made so the radio thinks its off allowing for manufacturer testing and development. No offense intended to anyone. Just curious if I'm wrong or if that had changed.
Sent from my HTC Thunderbolt
Click to expand...
Click to collapse
i believe you are 100% right here.
anyone know an easier way? -.-
i unlocked the bootloaders with HTC.
can someone please move this to the right section? sorry.
Post in the q&a and you'll find out. Plus revolution really is not hard if you follow the video.
Sent from my PG86100 using XDA Premium App
jordan23945bulls said:
anyone know an easier way? -.-
Click to expand...
Click to collapse
Wrong section, please pay attention to where you are posting next time.
In regards to your question, there really isn't an "easier way". The AlphaRev tool is one of the easiest I have ever seen. I suppose if that is too hard you could void your warranty and go the HTC route(Not Recommended).
i already did it with HTC. i want clockwork or something.
*sigh*
10chars
Your fellow posters are correct. If you have a question, ask it in... wait for it... Q&A!
In the future, please do your best to help keep the site nice and tidy. You will gain a greater sense of self-worth and everyone will appreciate you and write poems about you and your progeny. Thanks!
ugh i want CWM installed
jordan23945bulls said:
anyone know an easier way? -.-
i unlocked the bootloaders with HTC.
can someone please move this to the right section? sorry.
Click to expand...
Click to collapse
Since you followed HTC's method you are stuck as of right now. Their method unlocks your bootloader, but still has a NAND lock keeping you from flashing to different partitions. This situation is similar to the OG Evo if I'm not mistaken. Just wait around and a root method should appear.
Sent from my HTC Hero making C.R.E.A.M.
dastin1015 said:
Since you followed HTC's method you are stuck as of right now. Their method unlocks your bootloader, but still has a NAND lock keeping you from flashing to different partitions. This situation is similar to the OG Evo if I'm not mistaken. Just wait around and a root method should appear.
Sent from my HTC Hero making C.R.E.A.M.
Click to expand...
Click to collapse
thank you! ugh i really hope it does, i hate not being rooted.
Shoulda used Alpharevs revolutionary. Sorry. Not bein a ass. But you may have to wait awhile. Give it some time someone will fix it for ya.
Sent from 3D A.W.E.S.O.M-O
You will see claims from people in these forums that they were able to root and install recovery using HTC's unlocking, but those are false claims. All of those posters had been previously rooted using revolutionary.io. No one that took the OTA on a phone that hadn't previously been unlocked have been successful installing a custom recovery.
Basically you have an unlocked bootloader, now you will have to wait for someone to come up with an exploit like "rage against the cage" from the Evo to unlock the nand and attain s-off. If you had the original Evo 4g you will remember that in order to root you had to use unrevoked or Toast's method. Something similar to that will now be needed.
For those reading this your best option is to hold off using HTC's unlocker and if you haven't taken the 2.08 update use revolutionary.io to unlock your phone and if you did take the update or have a phone that came with the update, wait for an update to revolutionary.io.
fools
10char
SayWhat10 said:
fools
10char
Click to expand...
Click to collapse
Say what? If you're not contributing in a positive way, please leave the insults at home... for your cat. Thanks!
JDAWS said:
(So what 10) Oh I can root my phone I'm so cool now! Really son? You probably wear your star trek costume at the same as worshipping your phone! Get a life
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
Please look up.
TaurusBullba said:
Say what? If you're not contributing in a positive way, please leave the insults at home... for your cat. Thanks!
Click to expand...
Click to collapse
lol im saying man
not sure why people rush to htc unlock and THEN wonder how to do things...
but ok, i'll just refer to the other guy for the correct answer to this thread:
Since you followed HTC's method you are stuck as of right now. Their method unlocks your bootloader, but still has a NAND lock keeping you from flashing to different partitions. This situation is similar to the OG Evo if I'm not mistaken. Just wait around and a root method should appear.
better?
SayWhat10 said:
lol im saying man
not sure why people rush to htc unlock and THEN wonder how to do things...
but ok, i'll just refer to the other guy for the correct answer to this thread:
Since you followed HTC's method you are stuck as of right now. Their method unlocks your bootloader, but still has a NAND lock keeping you from flashing to different partitions. This situation is similar to the OG Evo if I'm not mistaken. Just wait around and a root method should appear.
better?
Click to expand...
Click to collapse
I completely agree that many of the new users do often get a bit excited and "rush" to root or unlock their devices (without fully understanding or reading directions) and end up in a lurch. But not a single person on this forum should log in to make a person feel bad or incompetent. If you see someone that jumped the gun and is lost, please help them. If you can't, then just let someone who can do it. We are all here to learn and help each other out. Let's stick to that and everyone will be happy.
TaurusBullba said:
I completely agree that many of the new users do often get a bit excited and "rush" to root or unlock their devices (without fully understanding or reading directions) and end up in a lurch. But not a single person on this forum should log in to make a person feel bad or incompetent. If you see someone that jumped the gun and is lost, please help them. If you can't, then just let someone who can do it. We are all here to learn and help each other out. Let's stick to that and everyone will be happy.
Click to expand...
Click to collapse
Amen! I totally agree.
Furthermore, vBulletin, phpBB, Wiki* and most technologies used to share and publish information and content are just terribly inefficient in regards to topics like these (Android, rooting, development, tech, etc.). Newcomers simply can not come into forums like these and find the info or content they want consistently. You can tag, break stuff up into sub-forums and make stickies like 3M 'til your blue in the face but until you fully understand a noob's thought process and behavior and have the software reflect that we forever will have these problems.
One temporary resolution is to try to change the one variable we can change in this equation. That is to try to cease the negative comments since we already know noobs and their questions are a constant.
Do not use the HTC root method, just use the Revolutionary method and before doing so download and copy TWRP and a ROM and flash in HBOOT\Recovery
root with s-on
Like an idiot, I unlocked my bootloader via official HTC way. I have not rooted my phone with revolutionary, my phone was completely stock. I was able to flash CWM via fastboot and install superuser via CWM.
ok,weve had s-off for a couple days now,and ive see quite a few questions on various threads that make me wonder why the posters even wanted s- off int he first place,other than following the crowd like lemmings. lots of "what do i do now,why is my hboot this or that..."
i feel all the new rooters need to see this:
please be careful!
you can now have complete control of your phone. you can chage whatever you want since its not doing ANY security checks at all. as such you have a much greater responsibility to know what your flashing and why,and that your files are 100% unmolested and uncorrupt.
please be aware that a bad bootloader or radio flash can and will brick your phone,possibly beyond recovery.
you do not any longer have the s-on safety net of htcdev.
im seeing alot of flip-flopping bootloaders around,and most folks dont even know why they want the eng hboot.please think about this.its risky-flashing a a new bootloader is prolly THE biggest risk you can take on your devices,as without a bootloader NOTHING will load. i.e.,you have a brick. if your current bootloader suits your needs(ie boots youre phone and supports the fastboot commands you regularly use) then why are you changing it?
s-off is awsome,i know but again,i just want all the noobs that have been asking various question to realize the the seriousness of having this privelege is. have fun flashing roms and slpash screens,but be extremely cautious/careful with the important parts of your device.
-make sure you know what your flashing,and why
-make sure you have an md5 summer and use it.
-if you just asked "whats an md5??" then learn it
-make sure you are comepletely comfortable with all procedures for things you do.
last and not least,please ask any questions BEFORE your phone makes a short lil buzz,shuts off,and wont come back on
A nice friendly reminder. I appreciate it Scotty and I think this should be stickied to avoid people bricking phones.
Sent from my ADR6425LVW
Someone had to say it.
I am of the opinion that if you cannot fully support your device on your own and do more than basic troubleshooting, you should not take the risks associated with modifying your firmware. I see posts from people who obviously can't handle basic troubleshooting and I am sure after the S-OFF announcement and instructions there are definitely some bricked phones out there, which Verizon is going to replace on their dime.
So I echo the OP ... Please be careful, and accept the consequences of your actions.
Great post Scotty. I'm glad you took the time to write that. Hopefully people will read it.
Checking md5 is super important.
Sent from my ADR6425LVW using XDA
Scotty, excellent info for everyone, not just the noobs, as some people don't realize they are still noobs.
Mods, this should be stickied when you get a chance.
Thank you for writing up this excellent post.
Something else that I think should be mentioned is that Verizon/HTC should not be eating the costs of these phones. If you decide to jump voltage on your phone and get stuck in a boot loop and then screw it up trying to fix it, then you need to step up and take responsibility, as the poster above mentioned. You don't have to tell Verizon you were s offing your phone, just tell them you tore it up. They will help you save some money one way or another if you talk to them, and if there's not an option for that hit up craigslist.
For those of you who may be reading this considering the pros and cons, I would wait until you actually need s off to do the process. And when and if you do it, don't do it when you are in a hurry. It's a short process but if you hit a snag and need to start over you do not want to be rushing or not paying attention.
Sent from my ADR6425LVW using xda premium
thanks for the posts,guys. i agree 100% if you screw up your own device trying to s-off it,or doing something stupid after,man up and pay for it. its not vzw or htcs fault.
CharliesTheMan,i espeically like your firmware download,i was planning to do something similar folks are so used to slapping on a new set of radios,they dont realize how important the rest of the firmware can be. the sensation guys have been using similar downloads for quite some time.
great guide,its exactly what we needed
A great way to check MD5 checksums is with AFV Android File Verifier. It works great and you do not have to check each file with a PC. I always download all of the files I flash from my phone, so using AFV make things much simpler.
Clay333 said:
A great way to check MD5 checksums is with AFV Android File Verifier. It works great and you do not have to check each file with a PC. I always download all of the files I flash from my phone, so using AFV make things much simpler.
Click to expand...
Click to collapse
I agree completely. If you download right to your phone,AFV is a great app. I also very highly recommend it.
Sent from my ADR6425LVW using XDA
Very helpful thank you. I'm one of those people who don't know what eng boot is lol
Sent from my ADR6425LVW using Tapatalk 2 Beta-5
It is unfortunate that the stock hboot blocks fastboot commands unless you htcdev.com unlock again. That is the reason for the patched hboots. The S-OFF team I believe is working on a patched 2.11 hboot so the engineering hboot won't need to be used. So it will basically be the same as the 2.21 patched hboot they have for ICS.
Alright, so I am on gingerbread hboot, and have all of the files I need to s–off. After I get s-off, what steps do I need to take? I know this has been discussed, I and I am confident in my abilities, just want to do it right. Any help would appreciated. Thanks....
Sent from my ADR6425LVW using Tapatalk
Great info as always Scotty. People should know exactly what their getting into with S-Off and the consequences along with it. Going to add this to my FAQ.
Sent from my Htc Rezound
Follow me on twitter @lmrtech
I'm just curious. How could flashing wrong Radio brick the Phone ? Is there a technical reason for it ?
I've been flashing Radio on the Samsung Vibrant like crazy with all the radio even from AT&T without a hitch.
Thank you
Thanks Scotty, the main reason I did it was because I jammed something up and needed to do a fresh install anyway. I then assumed all of the upcoming roms will be prepared with s-off assumption. (not the best reason but I got through okay) I need to do my research on MD5 so I will take your advice. Best of luck to everyone else trying to get where they want to be, even if they don't need to be.
nbhnohome said:
I'm just curious. How could flashing wrong Radio brick the Phone ? Is there a technical reason for it ?
I've been flashing Radio on the Samsung Vibrant like crazy with all the radio even from AT&T without a hitch.
Thank you
Click to expand...
Click to collapse
Think of the radio like the bios on a main board. We've turned off the security check that makes sure the file is good. I beleive there is no signature check at all, so a corrupted download will still flash. A bad radio will leave you with a paper weight.
Sent from my ADR6425LVW using XDA
I am S-On with the GB firmware. If I don't S-Off, will I have problems down the road flashing new ROMs? I can I still flash the ROM, then fast boot the kernal?
k_flan said:
Think of the radio like the bios on a main board. We've turned off the security check that makes sure the file is good. I beleive there is no signature check at all, so a corrupted download will still flash. A bad radio will leave you with a paper weight.
Sent from my ADR6425LVW using XDA
Click to expand...
Click to collapse
I though that Hboot (Bootloader???) acts as Bios. Anyway, be safe better than feeling regret
Thanks
k_flan said:
Think of the radio like the bios on a main board. We've turned off the security check that makes sure the file is good. I beleive there is no signature check at all, so a corrupted download will still flash. A bad radio will leave you with a paper weight.
Sent from my ADR6425LVW using XDA
Click to expand...
Click to collapse
Being technical here maybe, but a bad radio would technically just make you not have reception or data correct ? As long as your HBoot wasn't corrupted, you could flash the radios back. Big danger is if your flashing a different or corrupted Hboot right ? I am just trying to understand myself so not being argumentative just trying to get it straight with the way I understood it .
Long story short, kind of a newb, but flashed roms on my original evo years ago, so not completely dumb to all of this. I'm on hour 6 trying to get this fixed on my 4g LTE, while watching two little kids, and cannot get it, so I am asking for help from the community. I'm stuck at the splash screen and will not go any further.
My phone was updated to latest OTA (HBOOT 1.19), and S-ON. Thought I had the correct tutorial, and use the workaround, but it screwed me. I first did the HTCdev unlock method, and downloaded the latest nightly cyanogenmod 10 build. I used abd to flash boot.img. After restart, it just stays on the splash screen. I then flashed TWRP, backed up, and this is where I'm stuck. From what I read, I'm supposed to install dumlock, but my phone gets stuck on splash screen.... so .... now what? Please help, either going back to OEM, or to fix and continue cyanogenmod 10 flash.
-Mike
You need to do some reading.
Literally 10 people post this same exact issue every day. Its probably why this hasn't been answered until now.
KNOW YOUR HBOOT LIMITATIONS
http://androidforums.com/evo-4g-lte-all-things-root/606748-how-install-kernels-h-boot-1-15-a.html
Rxpert said:
You need to do some reading.
Literally 10 people post this same exact issue every day. Its probably why this hasn't been answered until now.
KNOW YOUR HBOOT LIMITATIONS
http://androidforums.com/evo-4g-lte-all-things-root/606748-how-install-kernels-h-boot-1-15-a.html
Click to expand...
Click to collapse
Rxpert me and you are def working overtime on these threads lol anyways back too problem...your issue you need to use fastboot to flash the boot.img then flash the rom since your on a hboot higher than 1.15 and your s-on
Sent from the depths of hell
wileout said:
Rxpert me and you are def working overtime on these threads lol anyways back too problem...your issue you need to use fastboot to flash the boot.img then flash the rom since your on a hboot higher than 1.15 and your s-on
Sent from the depths of hell
Click to expand...
Click to collapse
I dont know what it is... but nobody knows what they're doing.
Each time I come to XDA I facepalm and post that same link 4 or 5 times
Rxpert said:
I dont know what it is... but nobody knows what they're doing.
Each time I come to XDA I facepalm and post that same link 4 or 5 times
Click to expand...
Click to collapse
I hear ya man...i think imma do a write up somewhat dumbing down/explaining how to do it to try and eleviate issues
Sent from the depths of hell
wileout said:
I hear ya man...i think imma do a write up somewhat dumbing down/explaining how to do it to try and eleviate issues
Sent from the depths of hell
Click to expand...
Click to collapse
I did a write up that I've been posting over here.
http://androidforums.com/evo-4g-lte-all-things-root/606748-how-install-kernels-h-boot-1-15-a.html
Notice we don't have any of these threads over on android forums . People actually know what they are doing.
Rxpert said:
I did a write up that I've been posting over here.
http://androidforums.com/evo-4g-lte-all-things-root/606748-how-install-kernels-h-boot-1-15-a.html
Notice we don't have any of these threads over on android forums . People actually know what they are doing.
Click to expand...
Click to collapse
Lmao....anyways can u do me a favor check mine out in the general section and give some constructive insight if i forgot something please i just did it quick cuz im on my phone plus life is still going on here lol
Sent from the depths of hell
I have started to try and help but I already feel defeated, and you guys do this on the daily....
Figured I was going to get **** for this, but thanks for the replies, guess we all cannot be uber android giniuses.. Google searches for some reason did not come up with results from xda. I did know I needed a workaround for boot 1.15 and 1.19, my probl em was with the ROM file itself... for some reason it would not install, even though it all seemed to be there. I re downloaded and tried 3 times, each gave me multiple errors accessing directories. The 4th worked and all is good.
d1scopotato said:
Figured I was going to get **** for this, but thanks for the replies, guess we all cannot be uber android giniuses.. Google searches for some reason did not come up with results from xda. I did know I needed a workaround for boot 1.15 and 1.19, my probl em was with the ROM file itself... for some reason it would not install, even though it all seemed to be there. I re downloaded and tried 3 times, each gave me multiple errors accessing directories. The 4th worked and all is good.
Click to expand...
Click to collapse
the problem is that it doesnt take a genius, these threads are popping up like crazy even by people who have rooted other devices but the problem is that all these devices are different, even the same make/model will not produce the same results across multiple devices, people just need to take the time to sit down and learn the basics for android customization, one guy had s-off and decided to fastboot the kernel, somehow he managed to obliterate his recovery as well, another guy kept trying lazy panda to s-off his hboot 1.15, there are some kind and helpful people on xda but this is ridiculous, ive even taken to pm'ing users as a way to lessen the threads popping up, if you take the time to read the guides posted then take extra time to read about the failures, they help the most, it sounds horrible to me but reading about their failure and seeing possible solutions will help you avoid them
d1scopotato said:
Figured I was going to get **** for this, but thanks for the replies, guess we all cannot be uber android giniuses.. Google searches for some reason did not come up with results from xda. I did know I needed a workaround for boot 1.15 and 1.19, my probl em was with the ROM file itself... for some reason it would not install, even though it all seemed to be there. I re downloaded and tried 3 times, each gave me multiple errors accessing directories. The 4th worked and all is good.
Click to expand...
Click to collapse
These off topic replies were not directed specifically at you. Its more frustration with those of us trying to help because we see so many of these threads everyday.
its simply mind boggling and frustrating to know that the majority of these problems are the exact same problem, you and wile do way way more damage control then i do and i just dont see how you guys keep on, i decided to start helping if i can and im already burned out, if i had a steady job id have probably given enough donations to warrant a tech support salary to you guys
om4 said:
its simply mind boggling and frustrating to know that the majority of these problems are the exact same problem, you and wile do way way more damage control then i do and i just dont see how you guys keep on, i decided to start helping if i can and im already burned out, if i had a steady job id have probably given enough donations to warrant a tech support salary to you guys
Click to expand...
Click to collapse
Like i said in i think my thread so many posts i dont know lol anyways i find it relaxing and helps me deal with myself and issues i have thank you iraq for that appreciate it so i dont mind but when users ask for help then get smart or act arrogant towards me for trying to troubleshoot for them i.e. dude in thw thread evo lte wont turn on rhats when i get pissed off and start contimplating whether i should help out or just say f*ck them but then i think of when i need or needed help and dirt off my shoulder and move to the next
Sent from the depths of hell
om4 said:
its simply mind boggling and frustrating to know that the majority of these problems are the exact same problem, you and wile do way way more damage control then i do and i just dont see how you guys keep on, i decided to start helping if i can and im already burned out, if i had a steady job id have probably given enough donations to warrant a tech support salary to you guys
Click to expand...
Click to collapse
Lol maybe I do need to put a donate button up. :silly:
I'm just a poor PhD student after all
I should but i doubt it wiuld get used
Sent from the depths of hell
PhD?? You're better off then I am, I have an associates in electrical engineering and computer science from ITT. Nobody from my graduating class with the exception of 2 people were able to directly benefit and now we owe a lot of money to an institution that isn't even accredited by the state I live in
Good job guys, these people need help, thanks for what you are doing
Sent from my EVO using xda premium
Is it not possible to get S-OFF on 1.15 or are we just waiting for the devs to do their magic?
Noxzoul said:
Is it not possible to get S-OFF on 1.15 or are we just waiting for the devs to do their magic?
Click to expand...
Click to collapse
Not possible yet
Sent from the depths of hell
Ok some of you may know me and i probably yried to help some of you so here is a guide for the new/inexperienced rooter.
welcome to xda youve probably found yourself here because youve rooted your shiny new LTE. Congrats. Now you wanna install and mod it. Follow these rules and you *shouldnt* have issue.if s-on anf hboot 1.12 flash as normal or use lazypanda to get soff while you still can!
1. Read read read
2. Unless s-off use fastboot to flash boot.img
3. Make sure boot.img is compatible with your rom/firmware i.e 1.13 1.22 2.13 *boot.img is kerne*
4. Dont post new thread for the same question asked already use search function
5. Enjoy your new rom
Side note use sense kernels with sense roms aosp kernels with aosp roms
Follow this link for fastboot instructions (thanks rxpert)
http://androidforums.com/evo-4g-lte-all-things-root/606748-how-install-kernels-h-boot-1-15-a.html
Any questions pm me oh and if i helped hit thanks lol
If anyone wants to add to this please do as ill be maintaining this
Sent from the depths of hell
Its a decent start. The problem is most people having the kernel flashing issues dont know what most of that means.
You have to give them the directions step by step as I have done here
http://androidforums.com/evo-4g-lte-all-things-root/606748-how-install-kernels-h-boot-1-15-a.html
Also, S-ON users with 1.12 do not have any of these problems and can flash normally
Rxpert said:
The problem is most people having the kernel flashing issues dont know what most of that means.
You have to give them the directions step by step as I have done here
http://androidforums.com/evo-4g-lte-all-things-root/606748-how-install-kernels-h-boot-1-15-a.html
Also, S-ON users with 1.12 do not have any of these problems and can flash normally
Click to expand...
Click to collapse
Ive never used fastboot because never had s-on with any of my devices thank god lol but ill research and add the steps or if you dont mind ill post your link in OP plus imma add yhat 1.12 thing in there just because someone will ask lol thanks bro for the help
Sent from the depths of hell
Feel free to post the link wherever lol.
More it gets posted more people get helped haha
Rxpert said:
Feel free to post the link wherever lol.
More it gets posted more people get helped haha
Click to expand...
Click to collapse
Already in op before you answered i figured you didnt care lol
Sent from the depths of hell
so many "bricked" threads I completely misread the title and assumed it would be someone admitting they're too high to have even tried the entire process and needed help. Was looking forward to reading about what happened, now im a bit disapointed, great write up though
om4 said:
so many "bricked" threads I completely misread the title and assumed it would be someone admitting they're too high to have even tried the entire process and needed help. Was looking forward to reading about what happened, now im a bit disapointed, great write up though
Click to expand...
Click to collapse
Sorry for disappointing lol
Sent from the depths of hell
theres always the hope that someone will come totally baked out of their minds
om4 said:
theres always the hope that someone will come totally baked out of their minds
Click to expand...
Click to collapse
Thats y we have all the bricked threads lol
Sent from the depths of hell
im waiting for the day that someone writes the most anti-rooting, blatantly hostile disclaimer like dont do this you will void warranty, you will damage the health of your phones nand memory, you will corrupt the file structure cache and dalvik you will destroy recovery, do not under any circumstances assume that rooting, installing recovery or flashing any rom through the action or inaction there of the developer is at all safe at any time. do not ever do this under any circumstances. without further ado this is how to root and s-off your htc evo 4g lte
That would be epic lol
Sent from the depths of hell
you know, today i was actually thinking about starting a google hangout specifically to trouble shoot for these people but my clear reception totally sucks and it kept kicking me off the net before i could even try. im really likeing the idea of starting hangouts specifically to help troubleshoot and educate, though it could be because i volunteer to teach kids on the weekends and i quite enjoy the job
om4 said:
you know, today i was actually thinking about starting a google hangout specifically to trouble shoot for these people but my clear reception totally sucks and it kept kicking me off the net before i could even try. im really likeing the idea of starting hangouts specifically to help troubleshoot and educate, though it could be because i volunteer to teach kids on the weekends and i quite enjoy the job
Click to expand...
Click to collapse
That would be a good idea actually
Sent from the depths of hell
Of course it is, I thought of it and I only make stupid decisions when Im tanked or Im trying to impress the gf. Really the only reason I thought it would make such a good idea is because I run a small business on the side, I repair and upgrade computers and most of my customers are small business owners so as a sort of bonus I will look at their business and migrate them to linux. I very often use some form of desktop sharing to help ease them into the new software when im on a tight schedule but they need help.
Bump
Sent from the depths of hell
bump this *extends arm fist forward* sorry you're not the only one bored...I have nothing to look forward to right now