ozzeh is teasing for an exploit that removes security on the shipping SPL, allowing you to flash unsigned images. It is expected to release tomorrow.
As Matt clarified in this thread, it will require a rooted phone. Though they expect users to be able to take OTAs without locking themselves out of the phone after applying unrEVOked forever, the exploit cannot yet be applied to the 2.2 OTA.
wow fingers cross lol
theillustratedlife said:
ozzeh is teasing for an exploit that removes security on the shipping SPL, allowing you to flash unsigned images. It is expected to release tomorrow.
Click to expand...
Click to collapse
Nice find can't wait to see this.
Here's to hoping
Sent from my PC36100 using XDA App
So that means root and nand unlock?
Sent from my PC36100 using XDA App
meinstein1987 said:
So that means root and nand unlock?
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Forever lmao
rjmjr69 said:
Forever lmao
Click to expand...
Click to collapse
Just forever or forever and ever?
is tonight now? its 4:41am in NY, lol... to sleep or not to sleep
spunks3 said:
is tonight now? its 4:41am in NY, lol... to sleep or not to sleep
Click to expand...
Click to collapse
It's technically morning so I would assume tonight as in the night of the 10th
063_XOBX said:
It's technically morning so I would assume tonight as in the night of the 10th
Click to expand...
Click to collapse
kiiinda what i figured... maybe their out of Cali and its 2am (still kind of tonight lol) on a side note. i have never rooted but have paid attention to the progress of rooting the Evo since i got mine (Google I/O Evo). I have updated to the OTA 2.2... is this gunna work for me?
spunks3 said:
kiiinda what i figured... maybe their out of Cali and its 2am (still kind of tonight lol) on a side note. i have never rooted but have paid attention to the progress of rooting the Evo since i got mine (Google I/O Evo). I have updated to the OTA 2.2... is this gunna work for me?
Click to expand...
Click to collapse
2.2 is the latest OTA so why bother making a new unrevoked if not for that
reserved... I will donate to that..
theillustratedlife said:
ozzeh is teasing for an exploit that removes security on the shipping SPL, allowing you to flash unsigned images. It is expected to release tomorrow.
Click to expand...
Click to collapse
good questions.
looks like its not an eng spl, so no fastboot.
it does turn security off, so no signature check on PC36IMG.zip files for us meaning we could create our own PC36IMG.zip files to flash any partition we've seen previous PC36IMG.zip files flash, which is quite a few more than flash_image gives us access to but NOT as many as fastboot allows.
fastboot > PC36IMG.zip > flash_image - in order of access to partitions on the phone
it is definitely a step in the right direction!
joeykrim said:
good questions.
looks like its not an eng spl, so no fastboot.
it does turn security off, so no signature check on PC36IMG.zip files for us meaning we could create our own PC36IMG.zip files to flash any partition we've seen previous PC36IMG.zip files flash, which is quite a few more than flash_image gives us access to but NOT as many as fastboot allows.
fastboot > PC36IMG.zip > flash_image - in order of access to partitions on the phone
it is definitely a step in the right direction!
Click to expand...
Click to collapse
But if you can turn off security, and flash any PC36IMG.zip, you can theoretically just use this spl to flash the PC36IMG.zip from Toasts original root method. Then work from there to get to a fully rooted 2.1 with fastboot then.
Then flash a 2.2, and you could be back where you were with full root.
Or am I missing something?
Dougie2187 said:
But if you can turn off security, and flash any PC36IMG.zip, you can theoretically just use this spl to flash the PC36IMG.zip from Toasts original root method. Then work from there to get to a fully rooted 2.1 with fastboot then.
Then flash a 2.2, and you could be back where you were with full root.
Or am I missing something?
Click to expand...
Click to collapse
**********
I think this would be the way to go to get out of the hboot .93 block. Good suggestion...
Dougie2187 said:
But if you can turn off security, and flash any PC36IMG.zip, you can theoretically just use this spl to flash the PC36IMG.zip from Toasts original root method. Then work from there to get to a fully rooted 2.1 with fastboot then.
Then flash a 2.2, and you could be back where you were with full root.
Or am I missing something?
Click to expand...
Click to collapse
sounds about right lol. it's a good way to get full root though for those who did the 2.2 ota update.
this looks promising.
subscribed
Interested to see what comes of this.
interested
Related
Hello
THIS THREAD IS OBSOLETE. PLEASE CLOSE.
YOU SHOULD BE ABLE TO ROOT DIRECTLY FROM 1.32.651.6 WITHOUT DOWNGRADING.
EDIT:
This is only confirmed to work with 1.32.651.6.
Refer to toast's reply below to understand why it might not work with other versions.
STEPS IF YOU WANT TO DOWNGRADE FROM STOCK .6 to STOCK .1 (NO ROOT)
1. I installed the latest RUU 1.32.651.6 found in this thread:
http://forum.xda-developers.com/showthread.php?t=695604
2. And I was able to downgrade back to the original one found here:
http://forum.xda-developers.com/showthread.php?t=685835
IF YOU WANT TO ROOT YOUR STOCK .6, JUST DO THE FOLLOWING:
3. Then did toast's root tutorial and got to the recovery and everything:
http://forum.xda-developers.com/showthread.php?t=690762
4. And am back to the rooted 1.32.651.1 with the ability to get to recovery and flash roms:
http://forum.xda-developers.com/showthread.php?t=693980
On step 2, the RUU was not able to reboot my device into the bootloader. So I booted into the bootloader myself (hold vol down + power on) then plug in the usb, select fastboot and then start the RUU from the PC. It installed like a champ and brought me back to 1.32.651.1.
Hope this helps everyone who decided to upgrade.
perfect!!! thanks for doing all this, testing and documenting your process. i was concerned with being limited between which versions, root process, recovery versions, etc.
this is great to know and should remove any doubts/concerns anybody has about jumping into the fray of flashing/experimenting/developing!
Yeah I had the ota RUU 1.32.651.6 installed, then found a method close to toasts method, rooted, flashes flipz stock rom, flash radio update, back to 1.32.651.1 with the radio update, still rooted!!! I even tried the froyo rom and thought it was cool, but waiting on more functionality version, so flashed back to stock rom, still rooted! Even thing works great (no 4g in my area so dont know about that.)
It's not that the current ruus won't allow u to downgrade. It's that every time u flash a newer ruu, u are gambling with root. Go look at the Eris and hero forums and u will see. I'm not gonna promote the flashing of ruus because I know what can happen. I have a eng ruu that is older and it can not be flashed because the mainversion is lower then the current mainversion. My goal is to inform everyone of the risks involve in flashing the newer ruus. The fact of not being able to downgrade isn't something I made up. U are just lucky that the newest ruus don't set the mainversion past the bootloader limit for downgrading.
Re: [howto] downgrade from OTA 1.32.651.6
I remember we were told excessives flashes can cause problems but with my htc diamond for the past year i was ruu updating weekly using different roms with their latest releases on my diamond is still going strong.. i like to say its user specific but i could be wrong
-------------------------------------
Sent via the XDA Tapatalk App
toastcfh said:
U are just lucky that the newest ruus don't set the mainversion past the bootloader limit for downgrading.
Click to expand...
Click to collapse
appreciate your feedback, knowledge and experience toast.
seems like the most accurate way to state this is flashing a newer RUU puts the EVO at risk of not being able to downgrade (or use root, wifi tether, custom ROMs, etc)
hopefully we will be able to detect when this change takes place, by md5sum on hboot.img and compare to previous versions. it didnt seem to change between .1 and .6 . hopefully it wont change in the future! once the md5sum changes, i'd say the risk of not being able to downgrade increases significantly!
although, ive only had an HTC phone with android for 3 days now, i could def be wrong in my analysis ...
I mean it could be the .1 and .6 doesn't matter. But idk
joeykrim said:
appreciate your feedback, knowledge and experience toast.
seems like the most accurate way to state this is flashing a newer RUU puts the EVO at risk of not being able to downgrade (or use root, wifi tether, custom ROMs, etc)
hopefully we will be able to detect when this change takes place, by md5sum on hboot.img and compare to previous versions. it didnt seem to change between .1 and .6 . hopefully it wont change in the future! once the md5sum changes, i'd say the risk of not being able to downgrade increases significantly!
although, ive only had an HTC phone with android for 3 days now, i could def be wrong in my analysis ...
Click to expand...
Click to collapse
I flashed the .6 through running ruu .exe,I havn't root my phone yet,can I run the unrevoke.apk to root then install wifi tether pre14 ?will this work?thanks.
So, semi-floating off topic. It turns out that ultimately the unrevoked root doesn't really do much, and apparently isn't enough for custom roms... if I was going to want to flash something custom, would I need to FIRST follow this guide to downgrade, THEN perform toasts root?
tl;dr - does toasts root work on .6?
2kmy477 said:
I flashed the .6 through running ruu .exe,I havn't root my phone yet,can I run the unrevoke.apk to root then install wifi tether pre14 ?will this work?thanks.
Click to expand...
Click to collapse
yes, it work for me.
tkhan02 said:
yes, it work for me.
Click to expand...
Click to collapse
Thank you.Will try when I get hone from work tonite.
Re: [howto] downgrade from OTA 1.32.651.6
FuManChuu said:
So, semi-floating off topic. It turns out that ultimately the unrevoked root doesn't really do much, and apparently isn't enough for custom roms... if I was going to want to flash something custom, would I need to FIRST follow this guide to downgrade, THEN perform toasts root?
tl;dr - does toasts root work on .6?
Click to expand...
Click to collapse
Yeah - if you are on .6, just do steps 2 and 3 then flash whatever rom u want using toast's recovery
Sent from my PC36100 using Tapatalk
I installed Sprint's official .6 by mistake, but was able to do steps 1 and 2 of your guide. I can see I'm in version .1 in my phone settings. However, when trying to follow toast's instructions from your step 3, I can't even do "adb push". When I do "adb devices", it doesn't see the phone. So I manually copied the PC36IMG.zip to the SD by mounting the USB and went into Fastboot. It did see the ZIP file and scanned (blue progress bar on the right). It actually looked like it scanned it twice, but, at the end, I didn't get an option to flash it. It just went back to the original 4-option fastboot menu. What am I doing wrong?
Re: [howto] downgrade from OTA 1.32.651.6
Sounds like it fails when it checks the rom. Make sure htc sync is installed on your pc then boot the phone, connect it and instead of charge only, select htc sync. Then, do the adb push stuff and try again.
And dont go to fastboot this time, just boot and wait and it should ask you whether to flash or not
Sent from my PC36100 using Tapatalk
Ok so I haven't rooted yet, but installed the OTA .6 update...can I still back up and get my root abilities back?
Can I ?
I have a stock Sprint Evo no root no nothing. Ive notice horrible battery life with .6 OTA.. Can I do step 2 without being rooted? I just want the original sprint before OTA.. Sorry for the ignorant question
xavier1022 said:
I have a stock Sprint Evo no root no nothing. Ive notice horrible battery life with .6 OTA.. Can I do step 2 without being rooted? I just want the original sprint before OTA.. Sorry for the ignorant question
Click to expand...
Click to collapse
Yes you can -- the 4 steps are independent of each other.
I am having issues with applying the RUUs, when I connect it via USB, do I choose USB or Charge only? Sorry.
engagedtosmile said:
I am having issues with applying the RUUs, when I connect it via USB, do I choose USB or Charge only? Sorry.
Click to expand...
Click to collapse
Choose HTC Sync
Re: [howto] downgrade from OTA 1.32.651.6
I have a stock Sprint Evo no root no nothing. Ive notice horrible battery life with .6 OTA.. Can I do step 2 without being rooted? I just want the ori
Click to expand...
Click to collapse
Yes you can -- the 4 steps are independent of each other.
Click to expand...
Click to collapse
Thanks will give it a go.. I was a windows mobile flash aholic...still scared to jump to flashing on android..
-------------------------------------
Sent via the XDA Tapatalk App
This is meant for 1.47.651.1 ROMs ONLY!
This is not the full radio but this will update the WiMax, recovery & kernel(same as in the OTA 1.47.651.1 zip).
Flash this through the bootloader like you would Toast's PC36IMG.zip(Power off, then Vol Down & Power button).
This will overwrite what ever recovery console you have, so once it's booted, replace the recovery console to what you were using before.
Also, this will not change the baseband version but it will update WiMax, so that's a start
EDIT: Full radio has been released, so removing this update
On a roll, dude. Donation is imminent.
I'm still not able to connect to 4g after appyling this update.
Looks promising.
I don't have 4G coverage here, but I flashed this radio upgrade against your rooted OTA Update ROM as a test.
I can confirm that nothing breaks =)
I was able to, without any problem, reflash the recovery I was using.
I can't wait for a full release that completely upgrades the radio!
and we will keep current rom settings and root with this?
Yes, your data & ROM are untouched as this only updates WiMax, recovery console & kernel
So, i understand this is not the full radio update..
But it WAS a full update with the OTA's that were sent out today right? I dont quit know what a radio.diff is (i think thats what they called it)
Excuse me for being a noob but does this mean that I will have do redo nand protection after I use this radio update? I did your update to OTA 1.47.651.1 without any problems. Thanks
mayfly82 said:
Excuse me for being a noob but does this mean that I will have do redo nand protection after I use this radio update? I did your update to OTA 1.47.651.1 without any problems. Thanks
Click to expand...
Click to collapse
no, you'll be fine doing this.
A 'diff' would be an update that only contains lines of code that changed from the original. This gives us a smaller payload making it less burdensome on the network for OverTheAir updates.
Touch censors are non responsive when flashing over Avalaunch's Froyo ROM via bootloader. Gonna have to flash Amon Ra's recovery via ADB. Also, the radio still shows up as version 1.39.00.05.31 is this expected? Thanks in advance.
c0mputerp0et said:
A 'diff' would be an update that only contains lines of code that changed from the original. This gives us a smaller payload making it less burdensome on the network for OverTheAir updates.
Click to expand...
Click to collapse
Nice! Thanks!!!
neckface said:
Touch censors are non responsive when flashing over Avalaunch's Froyo ROM via bootloader. Gonna have to flash Amon Ra's recovery via ADB. Also, the radio still shows up as version 1.39.00.05.31 is this expected? Thanks in advance.
Click to expand...
Click to collapse
"This is meant for 1.47.651.1 ROMs ONLY!" from the OP. Could be the issue. not sure if Avalaunch's has been updated yet.??
What exactly is meant by this line in the op?
"This will overwrite what ever recovery console you have, so once it's booted, replace the recovery console to what you were using before."
Details for a noob?
Really hope this update helps my 4G connection, otherwise I gotta return this phone ina few days
frettfreak said:
Nice! Thanks!!!
"This is meant for 1.47.651.1 ROMs ONLY!" from the OP. Could be the issue. not sure if Avalaunch's has been updated yet.??
Click to expand...
Click to collapse
Lawl Guess I neglected to notice that in my haste. I'll switch ROM's in a bit and give her a whirl again. Thanks.
EDIT: Got everything working again, flashed your OTA ROM and followed through with the radio. Sweet deal, man. Kudos again!
neckface said:
Lawl Guess I neglected to notice that in my haste. I'll switch ROM's in a bit and give her a whirl again. Thanks.
Click to expand...
Click to collapse
Coulda been an edit after the OP.. who knows.. and no prob man!! good luck!
frettfreak said:
Coulda been an edit after the OP.. who knows.. and no prob man!! good luck!
Click to expand...
Click to collapse
Nah, I saw what I wanted to see, or didn't, rather. Lol Everything's workin' now.
I know that this does not work... I tested it but maybe someone smarter can build off of it... In theory it should work but it doesn't on my phone... The file that it complains about is there maybe I just have the syntax wrong. Calkulin Please get this working.
Is there a reason we can't stick the radio diff into a PC36IMG.ZIP and upgrade via the bootloader as well?
I flashed this update over your release of today's update and 4G will start but will not connect. Any ideas of what I may have done wrong?
holob said:
Is there a reason we can't stick the radio diff into a PC36IMG.ZIP and upgrade via the bootloader as well?
Click to expand...
Click to collapse
we could try it... (you first) not saying that it will do anything bad but I have no idea.
WARNING!!!!YOUR RESULTS DEPEND ON LOCATION ...RE-CONFRIMED WORKING BY TESTERS IF YOU HAVE TROUBLE ITS FROM THE SPRINT SYSTEM ACTIVATION PROCESS WHICH WAS ALSO A ISSUE ON LAUNCH DAY OF EVO....TOO MANY ACTIVATION CODES FOR THE SYSTEM TO HANDLE..KEEP TRYING.
*********** PM ME IF THIS WORKED FOR YOU OR HAVE TROUBLE IAM HERE TO HELP **************
I PAVED THE WAY FOR OTHERS AND THEY MAY HAVE FOUND A "BETTER" WAY OF UPDATING..WHICH WAS WITHIN MY METHOD, NO ONE WAS POSTING A FIX OR WORK AROUND UNTIL AFTER I POSTED TODAY..THERE WAS 4 OTHER THREADS AFTER MINE WAS UP. I RISKED MY PHONE TO HELP OTHERS...IF YOU "FOUND" THIS FIX BEFORE ME ....SORRY I HAVE MORE THAN 143 AND COUNTING CONFIRMING MY WAY . CAN THE OTHERS SAY THAT? I DONT WANT YOUR $445 BOUNTY BTW ..YOU CAN SUCK IT... ITS ABOUT RESPECT FOR OTHERS WORK AND EFFORT.. ((HOT POCKET LINK BELLOW))
https://www.paypal.com/cgi-bin/webs...=PP-DonationsBF:btn_donateCC_LG.gif:NonHosted
UPDATE Option 1
Dial ##786#
Hit Menu
Press Reset
Enter MSL (if you dont have it call sprint and ask for it they just gave it to me I told them I was having issues)
Phone will reboot into recovery mode (can not confirm that this will work for clockwork mod)
Wipe everything 2x
Reboot
UPDATE Option 2 WITH UNREVOKED & STOCK 2.2
IAM USING RA_RECOVERY DURING THIS WHOLE PROCESS,PLEASE FLASH THE RA_RECOVERY PC36.IMG FIRST THEN BACK UP.THEN FLASH .6 THEN AFTERWARDS U CAN REVERT BACK TO CLOCKWORK...WHICH IS ALSO FOUND ON UNREVOKEDS SITE. -THANK YOU
1. Flash UNREVOKED Forever zip and download the ra-recovery on the unrevoked site .. its signed as pc36.img -SO PUT IT IN A FOLDER NOT ON THE
ROOT OF YOUR SD- NOTE:: U CAN USE ANY STOCK 2.2 ROM INSTEAD OF THE ONE PROVIDED.
2. In recovery make nandroid backup.
3 .Reboot
4. Download the official update that ends in .6 its pc36.img for 2.2 -PUT THIS IMG ON THE ROOT OF SD- THE OTHER ONE IS AFTER U ARE RUNNING STOCK.
5.Factory reset press ##786# on the dialer app and press menu to Wipe (ENTER YOUR MSL CODE TO CONFRIM, WILL REBOOT YOU INTO RECOVERY AND WHILE THERE ----WIPE YOUR BUTT TWICE.(WIPE CACHE AND DALVIK TWO TIMES!!!!!!!!)
6. Flash PC36.IMG UNDER HBOOT NOT RECOVERY--WILL AUTO CHECK FILE AND ASK YOU TO UPDATE...PRESS YES((LINK BELOW))
7. Reboot , auto activate and let it run and update **** for you,then check your version its 1.4.0 (( holy shiz)) - we did it! -dora
8. Now sign in gmail so you can download astro in market and delete the PC36.IMG on the root of your SD.
9.Now grab the RA_ Recovery thats signed as PC36.IMG in that folder( from step one kids.) and PUT ON ROOT OF SD. IF NOT SURE CHECK FILE SIZE ,SHOULD BE UNDER 5 MEGS.
10. Now power down and then press and hold power button + volume down. in the white screen with Andy the Android on a skateboard flash the recovery PC36.IMG and when asked to reboot select no and go into recovery and bam it back and remember to wipe your butt twice ,then restore.
BTW I BELIEVE WHEN U ACTIVATE YOUR PHONE YOU GET THE NEW PRI.WORKS FOR ME!!!
Use this as your 2.2 PC36.IMG When using Option 2 http://www.megaupload.com/?d=YVHC5NY2
PLEASE PM ME IF THIS WORKS FOR YOU OR TO TROUBLESHOOT
I thought it was confirmed no update had the new PRI...
Is this hex edited to look like it or is it legit ... how to tell?
Dude, I'm, on this... I was up with the guys last night on the unrevoked thread debating this. Going to do so, right now. You said the one ending in .6, of course, but the ruu, or custom made..
Links to what's what and where you got them would help.
Thanks.
This Was Composed With Swype Via Evo 4G
The question that needs to be asked is;
What PRI did you start the above process with?
if you already started with 1.40, then you did nothing new.
if you started with 1.34, well then you may have done something worth while.
TeknoJnky said:
The question that needs to be asked is;
What PRI did you start the above process with?
if you already started with 1.40, then you did nothing new.
if you started with 1.34, well then you may have done something worth while.
Click to expand...
Click to collapse
He started with .34 I know cause I was with him in the thread last night. When un revoked was released, this was our question.
This Was Composed With Swype Via Evo 4G
TeknoJnky said:
The question that needs to be asked is;
What PRI did you start the above process with?
if you already started with 1.40, then you did nothing new.
if you started with 1.34, well then you may have done something worth while.
Click to expand...
Click to collapse
Also... is it really an update or does it just look like it
PlankLongBeard said:
He started with .34 I know cause I was with him in the thread last night. When un revoked was released, this was our question.
This Was Composed With Swype Via Evo 4G
Click to expand...
Click to collapse
Yeah!! Sup bro? Any how hes right i did have .34 last night .. It doesnt matter which .6 PC36.IMG you use . After you ROOT with Unrevoked Forever you have root forever! does not matter which ****in hboot or any thing signed or unsigned u flash u got root. Also noted-- The speeds are the same but my ping was 350-450 and now they are 90 to 150.. the pri doesnt increase speeds but does in delivery (how fast data is sent to your phone from towers) follow the step and dont be gay----love GOONZ
Goonzy said:
Yeah!! Sup bro? Any how hes right i did have .34 last night .. It doesnt matter which .6 PC36.IMG you use . After you ROOT with Unrevoked Forever you have root forever! does not matter which ****in hboot or any thing signed or unsigned u flash u got root. Also noted-- The speeds are the same but my ping was 350-450 and now they are 90 to 150.. the pri doesnt increase speeds but does in delivery (how fast data is sent to your phone from towers) follow the step and dont be gay----love GOONZ
Click to expand...
Click to collapse
Goonz, Do me a solid.. Drop the PC36IMG You used.. I am hunting, but I can't find a "Official" Img, Besides going to sprint.com..
Thanks Dude.. I got the other one from Unrevoked.. The one for the recovery.
Im set, just need the official update.
PlankLongBeard said:
Goonz, Do me a solid.. Drop the PC36IMG You used.. I am hunting, but I can't find a "Official" Img, Besides going to sprint.com..
Thanks Dude.. I got the other one from Unrevoked.. The one for the recovery.
Im set, just need the official update.
Click to expand...
Click to collapse
Same here... thanks OP!
So if this really does work. Does goonz get the bounty?
Sent from my HTC EVO using Tapatalk
anyway you can post the files you used either as a link or uploaded somewhere so we know exactly which files to use
thanks OP
well since the 1.40 pri is not included in any official updates, I am confused.
BigRick10 said:
So if this really does work. Does goonz get the bounty?
Sent from my HTC EVO using Tapatalk
Click to expand...
Click to collapse
Yes. He should get the bounty. There is no disclaimer on how big or small the find may be. IMOH...
This Was Composed With Swype Via Evo 4G
PlankLongBeard said:
Yes. He should get the bounty. There is no disclaimer on how big or small the find may be. IMOH...
This Was Composed With Swype Via Evo 4G
Click to expand...
Click to collapse
Agreed
Sent from my HTC EVO using Tapatalk
If he wants the bounty, he needs to post which IMG he used to flash... Just telling us 'any' isn't going to cut it.
fldash said:
If he wants the bounty, he needs to post which IMG he used to flash... Just telling us 'any' isn't going to cut it.
Click to expand...
Click to collapse
Yeah I am also waiting on the files he used.
Sent from my HTC EVO using Tapatalk
Also.. for those of us not wanting to use unrevoked forever, being me, I would rather wait for a compiled update.zip to correct my PRI.
PlankLongBeard said:
Yes. He should get the bounty. There is no disclaimer on how big or small the find may be. IMOH...
This Was Composed With Swype Via Evo 4G
Click to expand...
Click to collapse
If it does work, I think unrevoked should get at least some of it because they are the ones that made it so you can flash the recovery after doing the stock update.
fldash said:
If he wants the bounty, he needs to post which IMG he used to flash... Just telling us 'any' isn't going to cut it.
Click to expand...
Click to collapse
And Thats what we're waiting for.. Once he does this.. We could test, then in all honesty give him what he rightfully deserves.!
He just listed this.. I will post screen shots..
Right now I am on, Calkulin Fully F**ing loaded.. Once I backup restore this, or just see it in the update, I will post, and assure we know this works..
You Must Be Rooted With S-OFF To Do This!
Seeing how there is no way to root 4.24 yet, I thought I would throw a little something together in case anyone needs to unroot before taking their phone into Sprint. This will return your phone to stock with S-ON while leaving a backdoor to reroot with. I have tested this as best I can without actually upgrading my hBoot (I want to keep the eng hboot), but there are no guarantees you won't run into issues. You also must flash the modified PC36IMG before setting S-ON in order for this to work.
While it would be trivial to create a script to automate this process, I wanted to make sure you know exactly what this does so it is easier to re-root. Plus there's no fun in having a script do all the work.
I've included all the files needed to use ADB and Fastboot on Windows, Linux and Macs. They have been renamed to match the operating system (eg. ADB for Windows is adbw, fastboot for Linux is fastbootl) and you may need to set the correct permissions in order to use them.
You will need:
Unrevoked Forever - The latest version of Unrevoked's S-OFF and S-ON tools
E4GUnroot.zip - The modified 4.24.651.1 PC36IMG zip and an unpacked copy of Amon RA's 1.8 recovery
Basic knowledge about ADB and Fastboot
Plenty of Battery Life
A little common sense
Click to expand...
Click to collapse
How To Unroot:
Make a Nandroid with the Boot, System and Data partitions along with your .android folder.
Make sure you have Radio S-OFF and not S-OFF from the ENG hBoot. If your bootloader shows SHIP S-OFF you should be good, if it shows ENG S-OFF then you will want to run Unrevoked Forever to make sure S-OFF is set from the radio.
Use ADB to reboot into RUU mode.
Code:
adb reboot oem-78
Once in RUU mode flash the PC36IMG. Be very careful that you do not interrupt it, doing so can easily result in the permanent bricking of your phone.
Code:
fastboot flash zip PC36IMG_4.24.651.1_Rootable.zip
Watch the output and make sure it completes correctly. If you get an error saying something about "remote 90: hboot pre-update" flash it again.
When it's finished flashing reboot and make your way into the Recovery.
Code:
fastboot reboot
--or--
fastboot reboot-bootloader
The recovery may show a green arrow for a few moments, wait for it to turn into the Red Triangle with an Exclamation Mark inside of it. Then push Amon RA's recovery to the phone and bring up the UI.
Code:
adb push amon_ra_1.8-mod /
adb shell "busybox --install /sbin"
adb shell "nohup /sbin/recovery &"
Now that the Recovery is up, use it to flash Unrevoked's S-ON tool.
You are now fully unrooted with S-ON! After you remove your SD card there will be nothing on your phone to show it was rooted.
Click to expand...
Click to collapse
How To Root Again:
Reboot into the Recovery and bring up Amon RA's recovery.
Run Unrevoked's S-OFF tool to unlock the NAND.
Flash your Recovery of choice and use it to restore your Nandroid
And that's it! You should be good to go again.
Click to expand...
Click to collapse
As always, you and you alone are responsible for everything you do to your phone. This is for informational purposes only; neither XDA nor I can be held responsible for anything that happens as a result of doing this.
Click to expand...
Click to collapse
Reserved...
I won't have to use this method, being rooted already, but will definitely help a lot of people. Also VERY clear, do good job man.
Agreed, great and useful guide.
Sent from my PC36100 using XDA Premium App
Good job and very educated post.
Just figured it may come in handy to someone, I had to unroot mine a few times to take it in to Sprint and I always did something similar to this to make it easier to reroot. If you wanted too you could even restore your data partition from a nandroid and remove all the root apps, that way your phone is still how you like it just unrooted for the time being.
Thank you sir. Very informative and useful post..
I have a question about this since it seems what your describing may help me. Since I got my E3d I have been playing around with my e4g and I upgraded mt hboot not realizing it would turn s-on. I know I'm still rooted since i have flashed at least 3 custom roms since then. I am on cm7.3 currently. For my case would using the unrevoked s-on/s-off tool to turn s-off work?
Great job here, hope I never have to use this though but should help many that need to take in their phone for service.
XpAcErX said:
I have a question about this since it seems what your describing may help me. Since I got my E3d I have been playing around with my e4g and I upgraded mt hboot not realizing it would turn s-on. I know I'm still rooted since i have flashed at least 3 custom roms since then. I am on cm7.3 currently. For my case would using the unrevoked s-on/s-off tool to turn s-off work?
Click to expand...
Click to collapse
Try using unrevoked forever from the recovery. If your radio is updated it may not let you do it but it's worth a try
Sent from my PG86100 using XDA Premium App
xHausx said:
Try using unrevoked forever from the recovery. If your radio is updated it may not let you do it but it's worth a try
Sent from my PG86100 using XDA Premium App
Click to expand...
Click to collapse
Thanks for the reply but i see from their site that 2.15.00.05.02 is not on the supported list.
XpAcErX said:
Thanks for the reply but i see from their site that 2.15.00.05.02 is not on the supported list.
Click to expand...
Click to collapse
Yeah, you'll most likely need to downgrade it first. I won't be getting home till late tonight or early in the morning but when I do I'll try to put some stuff together for you to downgrade with
Do you use a pc or linux?
Sent from my PG86100 using XDA Premium App
xHausx said:
Yeah, you'll most likely need to downgrade it first. I won't be getting home till late tonight or early in the morning but when I do I'll try to put some stuff together for you to downgrade with
Do you use a pc or linux?
Sent from my PG86100 using XDA Premium App
Click to expand...
Click to collapse
Thanks for your help, I have a pc.
Okay Haus. Now root my evo. Lol.
You can do it
Ill give you a hug from far away.
Sent from my PC36100 using Tapatalk
XpAcErX said:
Thanks for your help, I have a pc.
Click to expand...
Click to collapse
Sent a pm
tommytomatoe said:
Okay Haus. Now root my evo. Lol.
You can do it
Ill give you a hug from far away.
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
You mean you lost root too? I'm working it but unfortunately I haven't had that much free time to do it. I get the feeling it won't be too much longer now though.
xHausx said:
Sent a pm
Click to expand...
Click to collapse
Thanks, I'll dl and try it tonight.
hey xHausx
I've been with my Evo since the beginning so I have no issues, but a friend of mine just bought the Evo. Unfortunately, his came with gingerbread with 4.24.651. Since his is not rooted to begin with, we can't unroot and reroot, so is it safe to assume that this method will not work? If so, are there any known methods to root? thanks in advance....
heyman123 said:
so is it safe to assume that this method will not work? If so, are there any known methods to root? thanks in advance....
Click to expand...
Click to collapse
Correct assumption and nope. Join the masses over in Q&A and General posting about this daily.
github said:
Correct assumption and nope. Join the masses over in Q&A and General posting about this daily.
Click to expand...
Click to collapse
thanks for the response.
hmmm... well, all I can say is...... bummer! to my friend
aaaaaaand I'm back to s-off, thanks haus!
i was wondering if there is a way to do this. ??
im tired of my MTS4G, i want to install a good rom!
Amen to that
Sent from my myTouch_4G_Slide using Tapatalk
As of right now no, were all basically stuck. Htc say they'll release a update at the end of the month to allow unlocking but that will void your warranty. Im just waiting for a crack for this version. Shouldn't Be too long i hope.
Sent from my myTouch_4G_Slide using Tapatalk
I did not realize that this phone still had an unlocked bootloader when I purchased it a few days ago. It's unfortunate how the HTC Unlocker was glitchy with the MT4GS; it might be why there's such a lack of development right now, haha.
ac3theone said:
As of right now no, were all basically stuck. Htc say they'll release a update at the end of the month to allow unlocking but that will void your warranty. Im just waiting for a crack for this version. Shouldn't Be too long i hope.
Sent from my myTouch_4G_Slide using Tapatalk
Click to expand...
Click to collapse
i hope!! i dont care about the warranty, i hate the stock the sence , is so slow and i hate the interface, im comming from a vibrant runing ics passion v12, you can only imagine my frustration .
Limewirelord said:
I did not realize that this phone still had an unlocked bootloader when I purchased it a few days ago. It's unfortunate how the HTC Unlocker was glitchy with the MT4GS; it might be why there's such a lack of development right now, haha.
Click to expand...
Click to collapse
I think we can start shelving the idea that there's a lack of dev for the device - some definite strides being made in that direction now.
We could always use more people helping make stuff, though.
----
I need a copy of an S-ON bootloader that has not been unlocked.
I need both S-ON 1.44.0007 and S-ON 1.45.0013 - if anyone can get either to me that would be great.
They are only 1MB in size and can be attached to a post in the forum.
If you can get it - attach it as a reply to this post:
http://forum.xda-developers.com/showthread.php?t=1254518
The terminal command to back up a copy of it is:
Code:
dd if=/dev/block/mmcblk0p12 of=/sdcard/hboot.img
That will place a copy of your hboot on your sdcard, called hboot.img, if run from a terminal.
Nlarge got his unlocked S-ON bootloader added to that thread, now we need some regular S-ON ones to compare them to. If anyone can figure out how to get one to us it would be helpful.
We are trying to work the S-ON issue, but it's not exactly an easy nut to crack and we've mostly just started.
Thanks for any help that can be provided. This may not be all we need, but it's a start.
Hasn't anyone been able to flash the original PG59IMG.zip via the OTAbootloader patch?
Delivered via candygram for Mr. Mongo.
Blue6IX said:
I need a copy of an S-ON bootloader that has not been unlocked.
I need both S-ON 1.44.0007 and S-ON 1.45.0013 - if anyone can get either to me that would be great.
They are only 1MB in size and can be attached to a post in the forum.
If you can get it - attach it as a reply to this post:
http://forum.xda-developers.com/showthread.php?t=1254518
The terminal command to back up a copy of it is:
Code:
dd if=/dev/block/mmcblk0p12 of=/sdcard/hboot.img
That will place a copy of your hboot on your sdcard, called hboot.img, if run from a terminal.
Click to expand...
Click to collapse
I'll see if I can figure out how to get that to you. If I can't code, at least I can help with other things.
Cool, we'll look it over and see what we come up with. No promises, just gonna look and see what we see and hope it leads to something.
The hboot may or (more likely) may not be the whole problem for s-off/s-on, but the more we have to play with the more we are learning.
Blue6IX said:
Cool, we'll look it over and see what we come up with. No promises, just gonna look and see what we see and hope it leads to something.
The hboot may or (more likely) may not be the whole problem for s-off/s-on, but the more we have to play with the more we are learning.
Click to expand...
Click to collapse
I tried to copy it with (adb shell <command>) but it says I have permission denied.
Limewirelord said:
I tried to copy it with (adb shell ) but it says I have permission denied.
Click to expand...
Click to collapse
Okay, we are working on that, etn4off is leading the charge on adb through stock recovery, so hold that thought.
Meantime, i've whipped up a new version of the stock restore .zip file, that should work on the new OTA.
( Make sure you have a full battery first!)
Edit - didn't work
What you have to do is rename the file to:
PG59IMG.zip
...then place on the main directory of your sdcard.
Make sure fastboot is turned off in settings on the phone, and then power off.
Hold Volume Down and press Power to turn it on, booting into hboot. The installer will take over from there and guide you through it.
It will load itself, then ask you to press Volume UP to install - then does it's thing and will tell you to press power to reboot when it is done.
This is basically the same restore file you get from here: Thread Link updated for the new OTA.
This should solve the version mismatch problem people were having, but won't know until someone tries to install it.
Afterwards you can run Revolutionary to S-OFF your 1.44.0007 hboot.
You will no longer be on the newest OTA, but then you can apply it if you want and go back - as long as you run the Revolutionary process on the 1.44.0007 hboot before you do.
I'm going to try this asap
Sent from my myTouch_4G_Slide using Tapatalk
Blue6IX said:
Okay, we are working on that, etn4off is leading the charge on adb through stock recovery, so hold that thought.
Meantime, i've whipped up a new version of the stock restore .zip file, that should work on the new OTA.
( Make sure you have a full battery first!)
Stock_Retail_OTA_1-55-531-3_downgrade_PG59IMG.zip
Download link
MD5: c7ea224be738b14824a003fd9c9b4b19
What you have to do is rename the file to:
PG59IMG.zip
...then place on the main directory of your sdcard.
Make sure fastboot is turned off in settings on the phone, and then power off.
Hold Volume Down and press Power to turn it on, booting into hboot. The installer will take over from there and guide you through it.
It will load itself, then ask you to press Volume UP to install - then does it's thing and will tell you to press power to reboot when it is done.
This is basically the same restore file you get from here: Thread Link updated for the new OTA.
This should solve the version mismatch problem people were having, but won't know until someone tries to install it.
Afterwards you can run Revolutionary to S-OFF your 1.44.0007 hboot.
You will no longer be on the newest OTA, but then you can apply it if you want and go back - as long as you run the Revolutionary process on the 1.44.0007 hboot before you do.
Click to expand...
Click to collapse
Has anyone tried this? Not that im saying its bad i just dont want to mess up my newest toy...lol
Sent from my myTouch_4G_Slide using Tapatalk
izzy001 said:
Has anyone tried this? Not that im saying its bad i just dont want to mess up my newest toy...lol
Sent from my myTouch_4G_Slide using Tapatalk
Click to expand...
Click to collapse
No. That's why I said we won't know until someone tries.
I've run the package on both of my devices, so can attest to it working - but they are both s-off.
I've run it from the device in the newest OTA form, and it brought me back, but the old package did too - seems no version check on my devices (probably any s-off devices)
I've run from all versions of the hboot - 1.44.0006, 1.44.0007, 1.44.1107, and 1.45.0013, but they were all s-off.
As for what happens with an s-on device... ...? I updated the version because in another thread that was pinpointed as the problem for it not installing on the newest OTA.
Blue6IX said:
No. That's why I said we won't know until someone tries.
I've run the package on both of my devices, so can attest to it working - but they are both s-off.
I've run it from the device in the newest OTA form, and it brought me back, but the old package did too - seems no version check on my devices (probably any s-off devices)
I've run from all versions of the hboot - 1.44.0006, 1.44.0007, 1.44.1107, and 1.45.0013, but they were all s-off.
As for what happens with an s-on device... ...? I updated the version because in another thread that was pinpointed as the problem for it not installing on the newest OTA.
Click to expand...
Click to collapse
Well i tried it... But it didnt even see it as an update... It just checked it and went straight to the hboot menu
Sent from my myTouch_4G_Slide using Tapatalk
izzy001 said:
Well i tried it... But it didnt even see it as an update... It just checked it and went straight to the hboot menu
Sent from my myTouch_4G_Slide using Tapatalk
Click to expand...
Click to collapse
Okay thanks, it was pretty much an 'it will do it or it won't' situation, so we'll have to try something else.
I wish I could get an s-on device in my hands that I could try stuff on - for now it's test and test and test on the s-off, then try on the s-on ...
Sorry it didn't work, we'll have to try another way.
I'll give this a try as well, even though it supposedly doesn't work. Better try than not.
Is what you're trying to do make the older ROM (with the 1.44.0007 HBOOT) appear as an update to the newer update so we can, in a way, downflash to the older HBOOT that's compatible with the Revolutionary tool?
I'm kind of new to the whole Android scene and am just curious as to how things work.
Limewirelord said:
I'll give this a try as well, even though it supposedly doesn't work. Better try than not.
Is what you're trying to do make the older ROM (with the 1.44.0007 HBOOT) appear as an update to the newer update so we can, in a way, downflash to the older HBOOT that's compatible with the Revolutionary tool?
I'm kind of new to the whole Android scene and am just curious as to how things work.
Click to expand...
Click to collapse
If this flashes it should revert the phone back to retail launch - but it's probably not going to. Finding a way to force it could have a less then desirable outcome.
If it doesn't take, don't try to force the issue with it unless you know what you're doing and why.
Well I tried it as well and it got a check, but it didn't install anything. I wish I had the know-how to mess around with this stuff.
Limewirelord said:
Well I tried it as well and it got a check, but it didn't install anything. I wish I had the know-how to mess around with this stuff.
Click to expand...
Click to collapse
When it checks and oks it go to recovery in hboot menu
Sent from my myTouch_4G_Slide using Tapatalk