Ok, so over on the Shift forums, they stumbled upon a way to downgrade your device to allow nand unlocking. *All credit goes to ScaryGhoul, and Otaking71*
Basically by using a temproot method (which the 3D has), and using a misc.img partition from another phone (The Tbolt for this instance), they were able to trick the Hboot security check into allowing older RUU's to be run against the device.
According to Scary, and Otaking the dev work behind this should work for other devices, as long as you are able to identify which BLK houses the hidden partition that Hboot uses to check everything it flashes. As they outlined it is usually "misc", or hboot -1, in the case of the Evo shift, their Hboot partition is mmcblk0p18, so since the hidden partition is hboot -1, it would be mmcblk0p17.
Following their theory, If someone is willing to try this we would need to know which partition the Evo 3D uses for Hboot, we would also need to know if the 3D uses emmc or mtd blocks. If it is emmc the same commands with the proper mmc blocks will work, if it is mtd, we would need to reference the original EVO 4G root method to figure out how to force the hboot to bypass the security checks.
Here is the full post laying out the ground work necessary, including reference to the original Evo 4G root method. http://forum.xda-developers.com/showthread.php?t=1255474
If this works, then it will allow us to run the original RUU for the Evo 3D, essentially downgrading the device from Hboot 1.5 to Hboot 1.30, which then allows the device to be rooted with Revolutionary instead of being forced to use HTC's Unlock method.
Is there anyone out there willing to help dig into this, to see if we can roll back the Hboot of the Evo 3D to allow revolutionary to root it?
---------- Post added at 05:46 PM ---------- Previous post was at 05:29 PM ----------
The direction I am going with this is, If we can force the Hboot to allow downgrades, then that should mean that we should technically be able to force the hboot to downgrade itself, theoretically taking the hboot from 1.50 to 1.30 or 1.40 depending on whichever one you can get your hands on. Also here is some more info added to the whole wrack your brain process this is becoming. Also please ignore my odd way of thinking, I'm trying to think whether or not this is possible, while at the same time gathering data and trying to formulate a process to make it work. I could be entirely wrong about the whole thing, but you never know until you have it looked into and reviewed.
So first step to digging, It looks like the Evo 3D does indeed have emmc partitions http://forum.xda-developers.com/showthread.php?t=1197315
Which makes using their method easier to accomplish.
otaking71 said:
I accidentally figured this out.
You'll need temp root on the phone. Use any temp rooting method.
Push the extracted misc.img file to the sdcard.
Once you have root, dd the misc.img to the partition just above hboot.
In the case of the shift and the thunderbolt this is /dev/block/mmcblk0p17
Once this is done..you can proceed to use any ruu (the full executable) or any properly signed AND named zip from hboot.
This has only been tested on the shift...but the theory is sound. If you are doing this on anything other than a shift/tb....please check the size of the partition just above hboot.
Click to expand...
Click to collapse
We should also be able to use the misc.img file from the Tbolt that they used, as long as the size doesnt conflict with the 3D, the version is lower than that of the 3D, so it is still staying true to their groundwork.
So now knowing all of this, we just need someone willing to perform this to try and see if the HBoot can be downgraded accordingly since sofar everything is appearing to line up nicely.
The other question I would then propose is, If this is possible, could it work for 3D's that were unlocked using HTC's method. ie. Unlock with HTC's method, flash a rooted ROM, perform the hboot security bypass using the misc.img file. Then run an RUU that is from the 1.30 or 1.40 HBoot to return the device back to stock, after re-root using revolutionary.
One final thing, The only reason I am bringing this straight to the community without diving into it myself, is that I presently don't have a 3D to work with, but at the same time was tasked by several people that Have 3D's that took the OTA to HBoot 1.50, to see if there was a way to revert the process. That and I have no idea which mmcblk is the hboot partition for the 3D.
Sorry but this was one of the first things that was tried and multiple people have confirmed it's a no go. A little searching should be able to pull up some of the older threads that have more info about it in them.
Sent from my PG86100 using xda premium
xHausx said:
Sorry but this was one of the first things that was tried and multiple people have confirmed it's a no go. A little searching should be able to pull up some of the older threads that have more info about it in them.
Sent from my PG86100 using xda premium
Click to expand...
Click to collapse
Thanks, yeah I searched but didn't will admit didn't look as hard as I should have.
Sent from my PC36100 using Tapatalk
xHausx said:
Sorry but this was one of the first things that was tried and multiple people have confirmed it's a no go. A little searching should be able to pull up some of the older threads that have more info about it in them.
Sent from my PG86100 using xda premium
Click to expand...
Click to collapse
I just looked into what you posted xHausx, and I can only find threads where people tried to just flash a new Hboot ontop of the 1.50 HBoot, however this is known not to work because HTC does not fully unlock the HBoot, What I am proposing is forcing the HBoot to act like it is 100% unlocked to allow downgrading by using the misc.img file from the TBolt, like they did with the Evo Shift, I searched and searched, and cannot find anyone even attempting to modify the security of the HBoot -1 partition by using an unlocked bootloader from another device. So I am bringing this theory back up for testing, and for someone to show me where this method was tried and failed. Since as mentioned, I can only locate attempts to flash a bootloader ontop of a still locked bootloader.
If this is viable then it should also be useful for GSM E3D right?
Actually there is no temp root for updated Evo 3D's with 1.50 HBOOT and 2.3.4...HTC patched the exploit that was used to gain temp root. The only way this will work is if you already used HTC's unlocking method and use a rooted ROM. I am still on 1.40 and can't help(I probably wouldn't be much use anyway), but I would get into contact with Treve from the Synergy Rom. He has done all kinds of stuff with download mode and messing with the partitions before full root was available. He may not know of this hidden partition and may be able to help you out.
housry23 said:
Actually there is no temp root for updated Evo 3D's with 1.50 HBOOT and 2.3.4...HTC patched the exploit that was used to gain temp root. The only way this will work is if you already used HTC's unlocking method and use a rooted ROM. I am still on 1.40 and can't help(I probably wouldn't be much use anyway), but I would get into contact with Treve from the Synergy Rom. He has done all kinds of stuff with download mode and messing with the partitions before full root was available. He may not know of this hidden partition and may be able to help you out.
Click to expand...
Click to collapse
As suggested I contacted TrevE regarding this, and he didn't outright say that it wasn't possible, but without a temproot for the latest version, it basically came down to this. Obtain root via HTC's unlock, then attempt the patch, and then attempt the downgrade.
Any luck with this Khilbron?
Evo3Duzer said:
Any luck with this Khilbron?
Click to expand...
Click to collapse
its been 3 months...... not trolling but god damn way to rise a dead thread
nate420 said:
its been 3 months...... not trolling but god damn way to rise a dead thread
Click to expand...
Click to collapse
I am relatively new to this forum. Is there a time limit on threads? Is there a point where a user is no longer permitted to post a question in a thread?
Maybe an Admin can let me know if I have done something wrong?
I guess I could have IMd him.
Thanks for your useful input nate420
Evo3Duzer said:
I am relatively new to this forum. Is there a time limit on threads? Is there a point where a user is no longer permitted to post a question in a thread?
Maybe an Admin can let me know if I have done something wrong?
I guess I could have IMd him.
Thanks for your useful input nate420
Click to expand...
Click to collapse
Nope dude there is no problem with asking questions and raising "dead" threads. It shows that you are searching. If you had not searched then you would have been flamed for not searching. Unfortunately, on this forum, you are damned if you do and damned if you don't. Some people get their panties in a bunch for no reason at all.
animal7296 said:
Nope dude there is no problem with asking questions and raising "dead" threads. It shows that you are searching. If you had not searched then you would have been flamed for not searching. Unfortunately, on this forum, you are damned if you do and damned if you don't. Some people get their panties in a bunch for no reason at all.
Click to expand...
Click to collapse
chill dude i said i wasnt trolling
but if you see that their hasnt been an update in 3 months... by OP or ANYONE is there a point to ask for a update on the status?
sorry if my logic seems back asswards
but yes good job for searching before cheating a new thread ill give you both a thanks since im gonna be out of this forum soon
Searching this out is kind of depressing. no S Off on 1.5 and no downgrading off 1.5.... man atleast i have Flash GUI
Related
so I'm thinking about the 1.5 issue and had a thought. On the shift it was possible to temp root to gain access to the partition where the hboot resides, using the process in this thread (not my work)
http://forum.xda-developers.com/showthread.php?t=1255474
we're able to gain access, find the address, and then flash a new hboot. after that using the rooting method you can gain perm normal root.
any thoughts on if this would work?
ekz13 said:
so I'm thinking about the 1.5 issue and had a thought. On the shift it was possible to temp root to gain access to the partition where the hboot resides, using the process in this thread (not my work)
http://forum.xda-developers.com/showthread.php?t=1255474
we're able to gain access, find the address, and then flash a new hboot. after that using the rooting method you can gain perm normal root.
any thoughts on if this would work?
Click to expand...
Click to collapse
the shift didn't have all the partitions nand write locked like the EVO 3D does.
1st time around: shift didnt 'have nand write lock on the hboot partition, hence being able to temp root and directly flash eng hboot to the hboot partition.
2nd time around: shift didn't have the nand write lock on the misc partition, hence being able to temp root and flash a lower version to the misc partition then hboot would allow a downgraded version of software to be loaded.
esseentially it seems as if htc was doing the bare minimum to protect the shift from being unlocked/rooted as all these methods were known and some were used on the HTC EVO prior to the shift software releases.
this has been covered a few times on the forums, but i hope rehashing old ideas/attempts might spark new ones! sometimes it only takes a slight tweak to an old method for it to bypass a patch and work! hope that helps!
ah ok, gotcha, I had seen the threads on the downgrading thing, but they were a bit old and wasn't sure if the shift downgrade method was looked at as a viable option, but that makes sense as you explained it. I understand the process and methodology however, not the commands required to try it so I had the thought bouncing around and had to put it down to see if the "smart folks" might see something I missed. well, we'll see how it plays out.. it's interesting in the big picture to see how the devs always manage to find some loophole or crack in big businesses coding to develop the workaround, then they close, they find, round and round we go..
So I just got the EVO 3D and am running HBOOT 1.5 and the most recent update I believe. Nothing I could do about that, it was preloaded on there.
I'm wondering if it is even worth it for me to root my phone at this point. I've seen a few people hboot 1.5 **** up their phones and i'd rather not do that. I'm no stranger to custom roms at all (I installed countless ones on my Hero) so it's not that I'm not familiar. Were the people who messed up their phones just doing stuff they shouldn't have/being stupid in general?
DjNawo said:
So I just got the EVO 3D and am running HBOOT 1.5 and the most recent update I believe. Nothing I could do about that, it was preloaded on there.
I'm wondering if it is even worth it for me to root my phone at this point. I've seen a few people hboot 1.5 **** up their phones and i'd rather not do that. I'm no stranger to custom roms at all (I installed countless ones on my Hero) so it's not that I'm not familiar. Were the people who messed up their phones just doing stuff they shouldn't have/being stupid in general?
Click to expand...
Click to collapse
Yes, it worths at least for myself. I have hboot 1.50 too and i rooted fast with no problems.
DjNawo said:
So I just got the EVO 3D and am running HBOOT 1.5 and the most recent update I believe. Nothing I could do about that, it was preloaded on there.
I'm wondering if it is even worth it for me to root my phone at this point. I've seen a few people hboot 1.5 **** up their phones and i'd rather not do that. I'm no stranger to custom roms at all (I installed countless ones on my Hero) so it's not that I'm not familiar. Were the people who messed up their phones just doing stuff they shouldn't have/being stupid in general?
Click to expand...
Click to collapse
More than likely, yes. Most users who follow the guides don't seem to have issues.
The HTC unlock method changes the dynamics a bit from previous common and accepted methods. Many "new" users become between old and current guides.
As far as I've seen, there are only three limitations to hboot 1.5, compared with early "compromised" versions using the AlphaRevX revolutionary method.
1) Kernel is not able to be flashed from recovery mode. Work arounds include: flashing from normal Android mode, my app is great for that, Flash Image GUI. Loading the custom recovery from fastboot. Flashing the kernel from fastboot. Using the "dumlock" method with TWRP.
2) Unable to selectively flash radio images
3) Unable to selectively flash intial splash screens
If I'm missing anything, I'm sure somebody else can post up.
None of those seem like deal breakers to me. Thanks for the fast replies.
It's kind of a ***** just because you have to do a few extra steps but if you know what your doing you won't screw it up.
Yarr. I think I'm going to keep stock for probably just a bit longer. Maybe 1.5 S-Off wont be a problem then. Not bored of it yet, and coming from HTC Hero the thing is a dream.
Root is the way to go Get rid of bloat Also adb isn't hard I always fastboot boot recovery.img and wipe flash no issues
Should I start a new thread on this? I tried to root my HBoot1.5 with 2.17.651.5. When I have went through the HTC unlock process it stays locked. I tried to install the 2.08 version through the original RUU, but it keeps failing. Not sure where I should go from there.
ls3mach said:
Should I start a new thread on this? I tried to root my HBoot1.5 with 2.17.651.5. When I have went through the HTC unlock process it stays locked. I tried to install the 2.08 version through the original RUU, but it keeps failing. Not sure where I should go from there.
Click to expand...
Click to collapse
I used the 2.17 from http://www.filefactory.com/f/4ef0ef536face67a/ and mine unlocked. I ran the ruu while in hboot so it didnt check my current version. When i tried the same ruu from within android it failed every time.
What did it say when you flashed the unlock token? Did you get the message on the phone screen asking if you want to unlock?
xcpefrmreality said:
I used the 2.17 from http://www.filefactory.com/f/4ef0ef536face67a/ and mine unlocked. I ran the ruu while in hboot so it didnt check my current version. When i tried the same ruu from within android it failed every time.
What did it say when you flashed the unlock token? Did you get the message on the phone screen asking if you want to unlock?
Click to expand...
Click to collapse
That is what he needs to do to fix .
Sent from my PG86100 using xda premium
DjNawo said:
Yarr. I think I'm going to keep stock for probably just a bit longer. Maybe 1.5 S-Off wont be a problem then. Not bored of it yet, and coming from HTC Hero the thing is a dream.
Click to expand...
Click to collapse
You have Hboot 1.5 with S-off?
G.Newton said:
You have Hboot 1.5 with S-off?
Click to expand...
Click to collapse
No he doesn't from what he said he is stock and asking if he should root
xcpefrmreality said:
I used the 2.17 from http://www.filefactory.com/f/4ef0ef536face67a/ and mine unlocked. I ran the ruu while in hboot so it didnt check my current version. When i tried the same ruu from within android it failed every time.
What did it say when you flashed the unlock token? Did you get the message on the phone screen asking if you want to unlock?
Click to expand...
Click to collapse
Much obliged!
DjNawo said:
So I just got the EVO 3D and am running HBOOT 1.5 and the most recent update I believe. Nothing I could do about that, it was preloaded on there.
I'm wondering if it is even worth it for me to root my phone at this point. I've seen a few people hboot 1.5 **** up their phones and i'd rather not do that. I'm no stranger to custom roms at all (I installed countless ones on my Hero) so it's not that I'm not familiar. Were the people who messed up their phones just doing stuff they shouldn't have/being stupid in general?
Click to expand...
Click to collapse
I think some people just got ahead of themselves flashing wrong files. I got a bit worried too first go round after coming from a.Transform.
In my signature I've got a guide/flashing notes that are a bit more updated than some of the stickied threads that may help clear some things up.
Sent from my PG86100 using Tapatalk
What root did you use
Sent from my EVO 3D using XDA Premium
[/COLOR]
Yoyodude1124 said:
What root did you use
Click to expand...
Click to collapse
I used the HTC Unlock (zedomax's video), CWM Recovery, Su 3.07 zip, BusyBox (market), all layed out here:
[Guide] My Hboot 1.50 HTC Unlock/recovery/rom/kernel flashing notes http://forum.xda-developers.com/show....php?t=1495358
Hey thanks again. Yeah I have the newest update, so i would need to get the 2.17 that xcp mentioned. Also, thanks for the guide above.
Lately I have read many posts with wrong assumptions about S-OFF. I am writing this post in General to clear up to many of you what S-OFF is and isn't.
To start off, S-OFF has nothing to do with your phone being rooted. I've seen people post that S-OFF means a "full" root, or "permanent" root. Those terms aren't even correct, root is just another user on the linux system, and you either have access to it or you don't. Rooting your phone and what that entails is out of the scope of this writeup.
When your device is shipped, your bootloader will show the flag S-ON. This stands for Security-On. What this security does is protect the NAND partitions (ie: the boot partition, the recovery partition, the radio, the system partition...) from being permanently modified at all. Basically, all changes made to these partitions while the phone is running is not permanent, and will be reset upon a reboot. Also, while your phone is S-ON, all firmware zips (ie: PJ75IMG.zip) must be digitally signed by HTC in order to be flashed through the bootloader.
When your device is set to S-OFF, the security is turned off. This allows you to modify any partition on the device, and changes will not be reset upon a reboot. Also, the signature checking of the firmware zips (ie: PJ75IMG.zip) is disabled, allowing users to flash unsigned firmware zips containing the separate images of the partitions. S-OFF gives the user great power over the device, but also comes with much responsibility to be careful.
I have seen many posts stating the term "S-OFF root". As I stated earlier, S-OFF and root are completely different things. When you have S-OFF in the bootloader, you then can flash a package containing Superuser.apk and the su binary, which in turn will give you root in the file system when the device is booted. Again, S-OFF does not mean you have root. You can have S-OFF set (if there was an S-OFF exploit released) on the stock phone running the stock unchanged ROM, and not have root in the file system because you haven't pushed/flashed the Superuser.apk and su binaries on your phone yet.
I have also seen many posts about people not "trusting" the bootloader unlock at HTCdev. Yes, we all know that it does not set the bootloader to S-OFF, but it does unlock the partitions that are needed to flash a custom recovery, and through that flash a custom ROM. This is probably the most trustworthy way to "unlock" the bootloader. Any S-OFF method released here in the future will most likely be a hack to make it work. Imagine if HTC gave out the radio S-OFF unlock. That would mean ANYONE (specifically people who are very flash happy) could find a random radio firmware zip which.. oops.. isn't for the correct device, flash it through the S-OFF bootloader, and brick their device. Releasing the limited unlocking was very smart by HTC, and will definitely save many phones from ending up in the graveyard.
Now I am not saying I do not want S-OFF haha. As a developer, S-OFF is well needed and is extremely useful. It's definitely being worked on. But for the average flasher, (of ROMs, not human parts ) radio S-OFF is not needed.
Hope this clears up confusion about what S-ON and S-OFF is. I will add to this as I feel necessary, and to clear up some of my sentences (Sometimes I start typing before I finish thinking of what I'm going to type).
Thank you.
Thank you soooo much haha so many people were confused about it...
A good example is my moms phone. She has an evo 3d and I made it s-off with eng hboot in case I sell it at a later time. Currently it's not rooted at all, but if I want to considering my bootloader's unlocked I could easily flash a recovery and then flash superuser which in turn gives me root
make the subject a bit more clearer
cuz when i saw it i thought that you had s-off for us lol
please sticky this!
If I may add to this discussion ...
If you do not already know these terms and what they mean you should probably not be attempting to root your phone yet
You should instead invest some time reading and learning first.
Unreasnbl said:
If I may add to this discussion ...
If you do not already know these terms and what they mean you should probably not be attempting to root your phone yet
You should instead invest some time reading and learning first.
Click to expand...
Click to collapse
Or, rather, you should not be attempting to gain access to the root user / superuser account and privileges on your phone.
Updated the title just for clarity. If there's anything someone disagrees with or would like to add to the OP, let me know here and I'll see what I can do. And I definitely agree with Unreasnbl. It may be a pain in the a$$ to read before jumping into things, but seriously, it will help so much when it comes understanding.
Unreasnbl said:
If I may add to this discussion ...
If you do not already know these terms and what they mean you should probably not be attempting to root your phone yet
You should instead invest some time reading and learning first.
Click to expand...
Click to collapse
I rooted, with S-off, and flashed my phone before I understood any of these terms lol. Just by following instructions clearly.
But then later I learned all of these things.
But yes, you are absolutely correct.
edit: this is a good, valuable post op. Thank you.
arozer said:
I rooted, with S-off, and flashed my phone before I understood any of these terms lol. Just by following instructions clearly.
But then later I learned all of these things.
But yes, you are absolutely correct.
edit: this is a good, valuable post op. Thank you.
Click to expand...
Click to collapse
I think you just prooved the OP correct, you shouldn't have S-OFF, because it doesn't exist yet and you don't need it and that's probably good for person that thinks they rooted with S-off.
Thank you
Thank you for the great info! While not a noob(have had rooted, s-off OG 4G, and 3D, just rooted EVO LTE), I don't understand, nor want to, at an advanced level, Linux, ADB,FASTBOOT, etc. I like making my phone my own, and like flashing ROM's. I tried to use the HTC method of unlocking, but am just not comfortable with my skills to try and use SDK/ADB/FASTBOOT. Perhaps I can find someone in San Antonio to show me, but unless/until, I'll wait for someone such as yourself to provide a "dumbed-down" method. Again, thanks for sharing your knowledge and expertise.
Update: Couldn't stand it..went ahead, carefully reading and following instructions, and did HTC unlock. Had a few issues with TWRP, and flashing ViperROM, due to internal/sd configuration, but moved things to their proper place with ROM toolbox. Everything in it's place, and my phone running like I like it for almost 24 hours with no issues, other than the hilarious HTC warning at boot screen.
Thanks regaw for taking your time with this. If you don't end up with 500 thanks ill be shocked lol
I personally want S-Off.
Mainly because I prefer not notify HTC that I'm unlocked.
Occasionally it's fun to dabble in trying newer radios and is sometimes required for later releases of the OS. Radio firmware can add or take away some functionality as well (like VPN).
Yes, we know it's dangerous, it's pretty rare folks dork their phones because they had s-off. But one of the worst examples is the flash happy folks on the EVO 3D that flashed Virgin Mobile firmware and should not have (myself included).
---------- Post added at 10:00 PM ---------- Previous post was at 09:56 PM ----------
dongarritas said:
Thank you for the great info! While not a noob(have had rooted, s-off OG 4G, and 3D, just rooted EVO LTE), I don't understand, nor want to, at an advanced level, Linux, ADB,FASTBOOT, etc. I like making my phone my own, and like flashing ROM's. I tried to use the HTC method of unlocking, but am just not comfortable with my skills to try and use SDK/ADB/FASTBOOT. Perhaps I can find someone in San Antonio to show me, but unless/until, I'll wait for someone such as yourself to provide a "dumbed-down" method. Again, thanks for sharing your knowledge and expertise.
Click to expand...
Click to collapse
It's really not that hard. No harder than figuring out how to use recovery, bootloader etc.. The current root procedure you just did on the LTE used ADB !! Just follow procedures.
Unreasnbl said:
If I may add to this discussion ...
If you do not already know these terms and what they mean you should probably not be attempting to root your phone yet
You should instead invest some time reading and learning first.
Click to expand...
Click to collapse
Maybe you could direct them to some good reading material -- like the first post.
Sent from my EVO using Tapatalk 2
Great thread, Daniel.
Sent from my EVO using Tapatalk 2
mswlogo said:
I think you just prooved the OP correct, you shouldn't have S-OFF, because it doesn't exist yet and you don't need it and that's probably good for person that thinks they rooted with S-off.
Click to expand...
Click to collapse
Nice try at being a smart ass bro, but I was talking about when I first started, on the htc Evo 4G.
Before that I had the incredible and droid 1 and I just used the one click roots.
Great post. I don't like it when people use the incorrect terms either, and have made similar posts on other forums, specifically relating to the OG. I usually recommend that noobs that "want to root" use the HTC unlocker because, as you pointed out, it's a safer solution for those that don't really know what they're doing.
Unfortunately, because that process is somewhat involved, many users new to Android or just not technically inclined prefer to use what this community has to offer. That's good, I suppose, as that's one of the reasons this community exists, but I strongly feel like it takes away some user responsibility to get to know their device. If people would take the time to learn about adb and fastboot and find out what an RUU is and what the /misc partition is, I feel like there would a lot more contributors on this forum than whining leechers.
I've personally never been one to follow instructions without first at least trying to understand what I'm doing, but I guess not everyone is like that.
At any rate, thanks for the post, and I'm sure I'll see everyone around a bit more once Amazon finally delivers my phone.
Very informational.But just to clarify:
If I were to have S-OFF, I can repartition the onboard storage so that instead of having 2gb of app storage, I can have say 6 or 10gb? That's what I really want to do.
Thanks for clarifying this OP. I personally knew what S-OFF meant but alot of folks on this phone are obviously new to roooting and had no idea about any of this.
Sent from my EVO using xda premium
Thank you for the clarification
<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
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