Related
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
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..
Hey guys i just got the 3d today and have it rooted. I installed 1 or 2 updates already but still had 1.4. But im curious as to what update exactly changes my hboot to 1.5. can any one help?
DO NOT OTA UPDATE YOUR PHONE! You do not want the HBOOT 1.5 it will make your life difficult. Stick with your bootloader and if you want to UG do it via a custom ROM.
jrockisme said:
Hey guys i just got the 3d today and have it rooted. I installed 1 or 2 updates already but still had 1.4. But im curious as to what update exactly changes my hboot to 1.5. can any one help?
Click to expand...
Click to collapse
The RUU for software verison 2.08 should also update hboot to version 1.5.
Probably best not to load this version unless you're up for an adventure! The
RUU software version 2.08 which also contains Hboot 1.5 patches all previously used exploits. Meaning, a new exploit will have to be developed and released in order to achieve the same unlocked access on Hboot 1.5 as was available for previous versions of Hboot.
Hope that helps answer your question!
divedr said:
DO NOT OTA UPDATE YOUR PHONE! You do not want the HBOOT 1.5 it will make your life difficult. Stick with your bootloader and if you want to UG do it via a custom ROM.
Click to expand...
Click to collapse
ahh, its not too bad. Granted i wish i had 1.30 or 1.40 but ADB & Fastboot aren't too bad.
joeykrim said:
The RUU for software verison 2.08 should also update hboot to version 1.5.
Probably best not to load this version unless you're up for an adventure! The
RUU software version 2.08 which also contains Hboot 1.5 patches all previously used exploits. Meaning, a new exploit will have to be developed and released in order to achieve the same unlocked access on Hboot 1.5 as was available for previous versions of Hboot.
Hope that helps answer your question!
Click to expand...
Click to collapse
That doesnt answer my question but it does answer which RUU i need to download for my Hboot version. But thanks for that one!
jrockisme said:
That doesnt answer my question but it does answer which RUU i need to download for my Hboot version. But thanks for that one!
Click to expand...
Click to collapse
Wait I am confused, do you want to have hboot 1.5? If so why?
Sent from my PG86100 using xda premium
jrockisme said:
Hey guys i just got the 3d today and have it rooted. I installed 1 or 2 updates already but still had 1.4. But im curious as to what update exactly changes my hboot to 1.5. can any one help?
Click to expand...
Click to collapse
joeykrim said:
The RUU for software verison 2.08 should also update hboot to version 1.5.
Probably best not to load this version unless you're up for an adventure! The
RUU software version 2.08 which also contains Hboot 1.5 patches all previously used exploits.
Click to expand...
Click to collapse
jrockisme said:
That doesnt answer my question but it does answer which RUU i need to download for my Hboot version. But thanks for that one!
Click to expand...
Click to collapse
If your question, as I read your post was, "what update exactly changes my hboot to 1.5" and you're on the Sprint version of the EVO 3D, then my answer above is correct. Software version 2.08.651.2 contains an update to bootloader version 1.5.
Perhaps I'm wrong in assuming you're on the Sprint device and perhaps you're using a GSM version. I'm not familar with the history of the GSM software versions, but I'm sure somebody else can post up to help clarify. Not sure where else the miscommunication could have occured.
Off the top of my head and to reiterate:
There have only been four updates for the EVO 3D from Sprint for their CDMA version of the EVO 3D.
1.11.651.2, 1.13.651.7, 2.08.651.2 an 2.08.651.3 (no leak RUU yet, only OTA, minor system software/kernel changes, no updated bootloader/radio).
If you're interested in gaining the ability to answer this question yourself, the hboot version is generally listed in the hboot file name of the image provided inside the firmware.zip of the RUU rom.zip (often renamed as PG86IMG.zip) included inside the RUU .exe. Hboot file name is generally, Hboot1.4_signed.img or something similar.
Also, if you feel adventurous, you could open the hboot img in a hex editor and search for the string containing the version number! Thats an adventure I don't take very often.
To obtain the extracted rom .zip files, renamed as PG86IMG.zip files or the original RUU .exe files for any of these software versions which have been leaked online, goo-inside.me keeps a reliable collection: http://www.goo-inside.me/shooter/ruu .
Allowing EVO 3D users to revert back to any previous software version or update to the recent versions.
Hope that helps answer your question with more detail/insight or help anybody coming across this post that might have the same/related questionand resolve any miscommunication! Money back guarantee!
SketchyStunts said:
ahh, its not too bad. Granted i wish i had 1.30 or 1.40 but ADB & Fastboot aren't too bad.
Click to expand...
Click to collapse
Agreed, a little more of a pain but also makes you learn things other people may not be savvy on! Great opinion man!
joeykrim said:
Off the top of my head and to reiterate:
There have only been four updates for the EVO 3D from Sprint for their CDMA version of the EVO 3D.
1.11.651.2, 1.13.651.7, 2.08.651.2 an 2.08.651.3 (no leak RUU yet, only OTA, minor system software/kernel changes, no updated bootloader/radio).
If you're interested in gaining the ability to answer this question yourself, the hboot version is generally listed in the hboot file name of the image provided inside the firmware.zip of the RUU rom.zip (often renamed as PG86IMG.zip) included inside the RUU .exe. Hboot file name is generally, Hboot1.4_signed.img or something similar.
Click to expand...
Click to collapse
I am sure I know the answer, cause if it were this easy we wouldn't have so many *****ing about 1.5, but if the RUU installs the bootloader, would it be possible to use an RUU of 1.11 or 1.13 to get the older bootloader?
Bob
ParrSt said:
I am sure I know the answer, cause if it were this easy we wouldn't have so many *****ing about 1.5, but if the RUU installs the bootloader, would it be possible to use an RUU of 1.11 or 1.13 to get the older bootloader?
Bob
Click to expand...
Click to collapse
No, it won't work. I believe the install will fail and cancel itself.
ParrSt said:
I am sure I know the answer, cause if it were this easy we wouldn't have so many *****ing about 1.5, but if the RUU installs the bootloader, would it be possible to use an RUU of 1.11 or 1.13 to get the older bootloader?
Bob
Click to expand...
Click to collapse
Short answer: No and I think the exact error people receive is "Main version is older". As far as I recall, main version information is stored in the misc partition.
We've had a few threads on this, usually the title or key phrase is "downgrading" the bootloader.
Essentially, the HTC EVO Shift was able to have the bootloader downgraded two different ways after two different releases, but neither method will work for hboot 1.5.
If you're interested in a longer semi technical explanation, I've quoted my previous posts below for convenience.
http://forum.xda-developers.com/show...88&postcount=2
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!
Click to expand...
Click to collapse
So instead of waiting for revolutionary, im going to temp root because I don't want to use HTC's method. So, by doing so:
1)if I temp root and then I reboot the device, will any problems occur or will I just lose my root but it'll be the same as stock?
2) Can I remove a bloatware that I can't remove completely (Qik Video for example) with temp root?
3) Can I install the Google Talk with Voice/Video Chat (Link:http://forum.xda-developers.com/showthread.php?t=1230795) and will it work?
THANK YOU ALL SO MUCH
TechnoHacker said:
So instead of waiting for revolutionary, im going to temp root because I don't want to use HTC's method. So, by doing so:
1)if I temp root and then I reboot the device, will any problems occur or will I just lose my root but it'll be the same as stock?
2) Can I remove a bloatware that I can't remove completely (Qik Video for example) with temp root?
3) Can I install the Google Talk with Voice/Video Chat (Link:http://forum.xda-developers.com/showthread.php?t=1230795) and will it work?
THANK YOU ALL SO MUCH
Click to expand...
Click to collapse
How do you plan on temp rooting? I am pretty sure that the fre3vo temp root method no longer works if you're on 1.5hboot. Also, if you were to somehow accomplish temp root, anything you remove from /system/ will be back after a reboot. I would just use HTC`s method. You can flash whatever your want, minus radios.
Sent from my PG86100 using Tapatalk
k2buckley said:
How do you plan on temp rooting? I am pretty sure that the fre3vo temp root method no longer works if you're on 1.5hboot. Also, if you were to somehow accomplish temp root, anything you remove from /system/ will be back after a reboot. I would just use HTC`s method. You can flash whatever your want, minus radios.
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
I want to use fre3vo.
Well I just switched from an intercept to my EVO3D (3VO haha). What's the point of flashing radios?
I want to perma root, but wont that destroy my battery life?
TechnoHacker said:
I want to use fre3vo.
Well I just switched from an intercept to my EVO3D (3VO haha). What's the point of flashing radios?
I want to perma root, but wont that destroy my battery life?
Click to expand...
Click to collapse
If you want to have any root at all, as of right now the only thing you can do is use the HTC unlock method. It should definitely not destroy your battery life, not sure what prompted you to think it will destroy your battery life, but it won't.
Also, the point of flashing a radio is just to stay up to date with whatever radios HTC releases. Sometimes it will give you better signal, but usually you will be just fine staying on whatever radio you're already on.
Sent from my PG86100 using Tapatalk
k2buckley said:
If you want to have any root at all, as of right now the only thing you can do is use the HTC unlock method. It should definitely not destroy your battery life, not sure what prompted you to think it will destroy your battery life, but it won't.
Also, the point of flashing a radio is just to stay up to date with whatever radios HTC releases. Sometimes it will give you better signal, but usually you will be just fine staying on whatever radio you're already on.
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
So HBOOT 1.50 has no temp root (fre3vo does not work?)
Well I could use a signal boost for the radio as I don't get to much coverage indoors. :/ I'm not sure what to do, can I un-root and turn s-on ( *** Locked***) again?
-Sent from my HTC EVO 3D using the XDA App.
TechnoHacker said:
So HBOOT 1.50 has no temp root (fre3vo does not work?)
Well I could use a signal boost for the radio as I don't get to much coverage indoors. :/ I'm not sure what to do, can I un-root and turn s-on ( *** Locked***) again?
-Sent from my HTC EVO 3D using the XDA App.
Click to expand...
Click to collapse
The temp-root exploit that fr3vo used has been patched. Since you are on HBOOT 1.5 you have the latest radio. You can't turn S-ON because you never get S-OFF with the HTC method.
私のEVO 3Dから送信される。
No I'm saying if i turn s-off, can i go completely stock and turn s-on?
Also, If i root using HTC's method, will I lose all my apps and data :O
-Sent from my HTC EVO 3D using the XDA App.
Also, how am I supposed to backup my apps without root?
As far as backing up your app's without root, try linda file manger. And what flash is saying is the htc method is not a true unlock. Therefore you can't get your Evo3d to be s-off because your on hboot 1.5 so the only way you can unlock your phone is threw htc's method. The methods of truly unlocking your Evo3d are not an option for Evo3d's with the 1.5 boot loader. So in short you don't have to worry about getting your phone s-off and going back to stock because you can't get s-off. You can still however flash roms,mods,kernels,etc. You do however have to flash kernels threw fast boot or threw Joey k's app. Hope this helps. If you need more info send me a pm.
Locked & Loaded
""shooter on Deck""
laie1472 said:
As far as backing up your app's without root, try linda file manger. And what flash is saying is the htc method is not a true unlock. Therefore you can't get your Evo3d to be s-off because your on hboot 1.5 so the only way you can unlock your phone is threw htc's method. The methods of truly unlocking your Evo3d are not an option for Evo3d's with the 1.5 boot loader. So in short you don't have to worry about getting your phone s-off and going back to stock because you can't get s-off. You can still however flash roms,mods,kernels,etc. You do however have to flash kernels threw fast boot or threw Joey k's app. Hope this helps. If you need more info send me a pm.
Locked & Loaded
""shooter on Deck""
Click to expand...
Click to collapse
Okay, I just want temp-root. How can I get it?
TechnoHacker said:
Okay, I just want temp-root. How can I get it?
Click to expand...
Click to collapse
I think the only publicly released exploit for root on EVO 3D works with software versions 1.11 and 1.13 but was patched by HTC in software version 2.08 and is called fre3vo developed and released by agrabren. This exploit was also integrated and used in the AlphaRevX revolutionary tool to gain temp root access before modifying the bootloader.
Original thread and guide by agrabren, I located by typing fre3vo into google.com: http://forum.xda-developers.com/showthread.php?t=1150006
Hope that helps!
You can not get temp root. Temp root methods for hboot 1.4 were patched with the release of hboot 1.5...
You have been told this already in this thread several times. You have two option. Hurry up and wait for revolutionary to do there thing or you can unlock VIA htcs onlick method.
HTC method will void your warranty. It registers your serial number with them and there's no way around that. Also it is not a true s-off root. It will allow you to write to system to root but will leave the s-on still. This is easily fixed by GUI flash image developed by joeykrim, or by learning to use fastboot commands. Which BTW are easy and fast. I can use fastboot to flash a system.img data.img and boot.img as well as a recovery image in about 4 seconds of typing. Your best bet is to get the sdk set up and get fastboot working. Use fastboot to flash a recovery. You do this by putting the recovery image of your choose into the platform-tools folder of the sdk & rename it to recovery.img . Navigate with windows explorer to the platform tools folder. Assuming you have win7 hold shift and right click an empty spot in the folder and choose open cmd window here. In your cmd window type the following with no quotes..
"Fastboot flash recovery recovery.img" and hit enter.
That flashes your recovery, now to use it you need to boot recovery with fastboot
" fastboot boot recovery recovery.img" then enter.
Something about fastboot booting the recovery completly negates the s-on flag allowing full access to all partions on the device.
Again no temp root at all. It's possible but your gonna have to develop your own exploit. Good luck.
Sent from my PG86100 using Tapatalk
Okay, I understand now.
So there is no temp root or perma-temp root for HBOOT 1.5 correct?
(I also don't think there is a way to downgrade your hboot).
I want to use HTC's method but it erases all of the phones data(factory reset).
-Sent from my HTC EVO 3D using the XDA App.
joeykrim said:
I think the only publicly released exploit for root on EVO 3D works with software versions 1.11 and 1.13 but was patched by HTC in software version 2.08 and is called fre3vo developed and released by agrabren. This exploit was also integrated and used in the AlphaRevX revolutionary tool to gain temp root access before modifying the bootloader.
Original thread and guide by agrabren, I located by typing fre3vo into google.com: http://forum.xda-developers.com/showthread.php?t=1150006
Hope that helps!
Click to expand...
Click to collapse
mikedavis120 said:
You can not get temp root. Temp root methods for hboot 1.4 were patched with the release of hboot 1.5...
This is easily fixed by GUI flash image developed by joeykrim...
Click to expand...
Click to collapse
To clarify on the technical details, in case anybody comes across this later, the fre3vo temp root exploir, I quoted here and linked to in my previous post in this thread, exploited an area inside the kernel.
The kernel was patched in software release 2.08*. the fre3vo exploit is not related to hboot or hboot version. The hboot version number 1.5 coincided with software release 2.08* but did not patch the temp root exploit itself.
The kernel update in software version 2.08* and assuming all future versions has/will be patched against the fre3vo exploit.
Also link for Flash Image GUI mentioned above, http://goo.gl/sNi7V . Thanks for the support! Works well when away from a computer but wanting to change kernels/ROMs!
Also, will echo the above post, should always use and become familar with custom recovery for backup proposes. There is not a very good way around this therefore it is strongly encouraged!
Hope the additional technical details help currently or in the future!
<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