So I tried rooting the phone and it wouldn't do it. After a restart its just getting stuck at the "MY" logo
Did i brick it?
Edit: its working now but I can't get it rooted. I got the root.rar file unzipped into the sdcard/root but it says its not permited, what am I doing wrong?
That gives us nothing to go on. There are several rooting methods out there. Which are you using?
http://forum.xda-developers.com/showthread.php?t=858021&highlight=operation
That one
When i get to c. Type "sh root.sh" + enter.
it gives me an error and it tells me to restart and check if s=off but when i reboot and hold down the volume button nothing happens. It just reboots normally
That's the best guide out there and the one that I used.
Before attempting to run the script, did you successfully gain temp root using Visionary and set system to R/W?
Try the method here: http://forum.xda-developers.com/showthread.php?t=858996
It is newer and better in my opinion. Try it from the beginning step-by-step and see if it works.
TeeJay3800 said:
That's the best guide out there and the one that I used.
Before attempting to run the script, did you successfully gain temp root using Visionary and set system to R/W?
Click to expand...
Click to collapse
It asked me for super user permission so i'm pretty sure I got temp root.
I finally got something it rebooted and I checked but it still says s-on.
I'll try the script again and post what I get but this is very weird, I had no problems with my G2.
Edit:
my terminal output is
Inserting kernel module
ismod: init_module '/sdcard/root/wpx.ok' failed (Function not implemeneted)
Duplicatiing hboot
2048+0 records in
2048+0 records out
1048576 bites transferred in 0.721 secs (1454335 bytes/sec)
Synchronizing
Powerdown and reboot into hboot to check if s+off
when I reboot i get
GLACIER PVT SHIP S-ON
HBOOT-0.86.0000
MICROP-0429
RADIO-26.03.02.26_M
eMMC-boot
OK Last edit:
It seems my Hboot being 0.86.0000 had something to do with it, I tried the other method with adb and it worked I finally got S-off. This was harder to do than on my G2 that's for sure.
Thanks to those who tried helping and thanks to kmdub for suggesting the alternate method.
For some reason, you are not writing the proper hboot image. Try to re-download or find another source, because the one you are writing, according to your output, is not the right one.
OR...you could try the method I posted above, which does not require a new hboot and actually turns the radio S=OFF. Seriously though, why not use a different (read newer and better) method if the one you are using is not working?
Evofusion said:
It seems my Hboot being 0.86.0000 had something to do with it, I tried the other method with adb and it worked I finally got S-off. This was harder to do than on my G2 that's for sure.
Thanks to those who tried helping and thanks to kmdub for suggesting the alternate method.
Click to expand...
Click to collapse
While there are other rooting methods out there, there is nothing wrong with the guide you are following. Like I said, it worked great for me. The only thing I can think of is the version of Visionary you are using. r11 is supposed to work better than r14 on the MT4G. The script you run in the beginning flashes the engineering bootloader (0.85.2007), so that's way to tell if the script was successfully run. Just make sure you actually get root access after typing 'su' (so make sure Visionary gets temp root and system is set to R/W first).
Glad you finally got it working.
It seems my Hboot being 0.86.0000 had something to do with it, I tried the other method with adb and it worked I finally got S-off.
Click to expand...
Click to collapse
That's because the method you were trying first requires the ENG hboot as an essential part of the rooting process. It would have worked, but for some reason it seemed like the one you were writing was the same as what you already had. I don't know if you used the other method I posted or another "other" method, but the one I linked to actually turns the radio's security off (S=OFF) among other things, if you so choose. The older method replaces the stock bootloader with one that does not enforce/ignores the radio's set security. Whereas the newer method actually turns that security flag off, so you can use either bootloader. Both can use Visionary and effectively allow you to "root" the device, but the newer method is more permanent, so to speak.
kmdub said:
I don't know if you used the other method I posted or another "other" method, but the one I linked to actually turns the radio's security off (S=OFF) among other things, if you so choose. The older method replaces the stock bootloader with one that does not enforce/ignores the radio's set security. Whereas the newer method actually turns that security flag off, so you can use either bootloader. Both can use Visionary and effectively allow you to "root" the device, but the newer method is more permanent, so to speak.
Click to expand...
Click to collapse
So even though I have the engineering bootloader and my S status is "OFF", the radio security is still on? Does that only matter if for some reason I switch back to the stock bootloader, and as long as I keep the eng SPL the difference in methods is inconsequential?
Evofusion said:
http://forum.xda-developers.com/showthread.php?t=858021&highlight=operation
That one
When i get to c. Type "sh root.sh" + enter.
it gives me an error and it tells me to restart and check if s=off but when i reboot and hold down the volume button nothing happens. It just reboots normally
Click to expand...
Click to collapse
Just a quick FYI on this, did you uncheck Fast Boot in the settings?
So even though I have the engineering bootloader and my S status is "OFF", the radio security is still on? Does that only matter if for some reason I switch back to the stock bootloader, and as long as I keep the eng SPL the difference in methods is inconsequential?
Click to expand...
Click to collapse
That is the impression I got from reading grankin01's method at the link I posted earlier; that yes, the security flag controlling the security is still set to on. Flashing the ENG bootloader is what actually gives you a label that says S=OFF on the older methods, since that bootloader either ignores the security flag or overrides it somehow. I am not certain about exactly how this takes place. What we do know however, is that security is not enforced regardless since it does allow you to effectively root the device, and you obviously have it working with the older method. The benefit of the newer method is outlined in his post. It allows you to retain the original bootloader and truly be S=OFF. I guess one could say that the older method provides an easier return to complete stock (warranty, return, etc.), since all one would have to do is use the PD15IMG to return to a completely stock state, bootloader and all. However, with the newer method, one would have to reverse the steps done with gfree in order to return to S=ON. So I would think that as long as you have the ENG bootloader you are ok, and it may make no difference. I do not know that from experience however, since I have only ever used the newer method with stellar results.
kmdub said:
The benefit of the newer method is outlined in his post. It allows you to retain the original bootloader and truly be S=OFF. I guess one could say that the older method provides an easier return to complete stock (warranty, return, etc.), since all one would have to do is use the PD15IMG to return to a completely stock state, bootloader and all. However, with the newer method, one would have to reverse the steps done with gfree in order to return to S=ON. So I would think that as long as you have the ENG bootloader you are ok, and it may make no difference. I do not know that from experience however, since I have only ever used the newer method with stellar results.
Click to expand...
Click to collapse
Thanks for the info. My understanding of one method versus the other was pretty much what you explained, but it's good to have it clarified.
I used fastboot way back in my G1 days.....first with the original EngSPL, then HardSPL, and finally when haykuro released DangerSPL. Since I would want the engineering bootloader anyway, I suppose there's no disadvantage to using the method I used. For those that want the stock bootloader, I can see why the newer method is advantageous to them.
Related
UPDATE: With all of the newer rooting and S-Off methods, and new hardware and firmware revisions, this thread may or may not help with your specific case if trying to unroot and go back to unrooted stock. I originally wrote this based of of the very first root methods known for the Launch EVO. There is a good chance that this method will still work, but there could definitely be something unaccounted for in your own specific case, so tread with caution. It is very doubtful that anything in this tutorial will result in your EVO becoming a fancy-schmancy paperweight, but if something goes afoul, you could have a nice headache to deal with...
Ok guys. There is a lot of partial and mis-information floating around out there about how to UN ROOT if you have to send your phone back for replacement, or you want the official unrooted OTA 2.2.
OLD NEWS!!!---> NEWER METHODS AVAILABLE TO ACTUALLY FIX PRI DOWNGRADE> SEARCH!!!! EDIT your PRI to show 1.40, thanks to sturmen for the pointer, and Calkulin for the method: http://forum.xda-developers.com/showpost.php?p=7267559&postcount=66
This assumes you are full root, S-Off. Note, this is not tested with simple root but should work (EDIT, Simple Root is basically Toastcfh's method, so you simple root users should be set), only with Toastchf's root method and nand unlock.
After reading every thread on the forum here, I think I finally found a fool proof way to do it. All the info was out there, but in several places and each one was missing something.
1) Before you start clicking and flashing and running RUUs, Check your HBoot build. You need to have the 0.76.2000 from Toastcfh's method #2. If you have 0.79.0000 (whatever) go to step 2 below. If you're getting Bootloader errors when running an RUU, I can almost guarantee that you don't have the correct HBOOT. If you somehow still have 0.76.2000 from previous modding, proceed to step 3.
2) Toast's Nand Unlock method. Found here: http://forum.xda-developers.com/showthread.php?t=701835
EDIT: The more I think about it, I think you can just run Simple Root to re-attain the .76 HBOOT and engineering build. It would eliminate the need for any adb, and SHOULD produce the same results. Just run the RUU after you run and complete simple root. See notes in BLUE below too!
THIS STEP IS 100% NECESSARY IF YOU HAVE THE .79 HBOOT version!!!...Do step #2 in Toast's thread, just like you did when you originally unlocked NAND (OR YOU SHOULD BE ABLE TO JUST RUN SIMPLE ROOT AGAIN...UNconfirmed, but should work methinks...). Not 100% sure which steps are necessary, but I do know you need to do steps #1 (Well, #1 is Nandroid Backup, so proceed at own risk if you skip) and #2 again. Make sure after you flash the Flash_Image, and the mtd-eng through adb, that you then load the PC36IMG.zip (Engineering Build), onto the root of your SD card, and boot into HBOOT, and let it install (just like you did when rooting). I didn't bother to flash the Recovery image at the end of step 3, but I don't think it would hurt if you're nervous about losing a custom recovery image in case this method for some reason does not work. It has come to my attention that flashing the engineering build (the PC36IMG from Toast's thread)through fastboot, might be as crucial as simply having the .76 HBOOT version. It at least is a surefire way to make sure you can run an RUU on top of it. There are probably other builds/roms that will work and allow you to run the RUU, but this one is confirmed, so don't skip that step!
3) If you have the 0.76.2000 HBOOT (can be checked by powering down, and booting by holding VOL down and Power), then you can go ahead and boot into the rom, and proceed with downloading the RUUs found here: http://shipped-roms.com/shipped/Supersonic/
Go ahead and download the first one (at least). I think the others are optional to "upgrade" but why should we care. We just want to go back to unrooted stock.
4) Make sure you have the latest version of HTC Sync installed, found here: http://www.htc.com/uk/SupportViewNews.aspx?dl_id=933&news_id=627
Install, and let it do it's thing. Will probably have to restart your PC when complete. Not even 100% sure this is necessary, but it won't hurt. It's basically for the HTC drivers from what I understand.
5) Run the RUU from your pc while your evo is in the phone loaded state of the Rom, (not the bootloader) with the phone connected through USB and have HTC sync selected. Even if it doesn't connect to HTC sync on your PC, you should be ok.
If you get a USB error after the screen goes black with the HTC LOGO, don't touch the phone. Exit the RUU via the EXIT button when given the option.
6) Run the RUU again and see what happens. The Error could happen 1 more time, but just exit again, and run RUU one last time.
7) Thank everyone here at XDA that our EVOs are so badass...I'm certinly not a dev, but these devs work hard for us to have the baddest ass phone there is right now.
Any problems, let me know. I assume your errors are the same ones I was getting, and it's all because of the wrong HBOOT.
I really take no credit for this, as I'm just compiling information in a tut....
Thanks op.
Or you can flash the new FroYo update release. =D
But thanks OP. Your hard work is much appreciated.
arozer said:
Or you can flash the new FroYo update release. =D
But thanks OP. Your hard work is much appreciated.
Click to expand...
Click to collapse
You might be correct, but I couldn't get the FROYO OTA to show up in any of the roms I was using.
Question: what's the deal with the PRI? Has anyone been able to properly fix that yet?
sturmen said:
Question: what's the deal with the PRI? Has anyone been able to properly fix that yet?
Click to expand...
Click to collapse
From my research, NO...Unfortunately, but this should get you as good as possible with what's out there now..
EDIT: Yess! See below and in OP!
Bang3r said:
From my research, NO...Unfortunately, but this should get you as good as possible with what's out there now..
Click to expand...
Click to collapse
Hm. I think I remember someone made a hex-edited PRI that people can flash in case they have to return it. I'll find it...
sturmen said:
Hm. I think I remember someone made a hex-edited PRI that people can flash in case they have to return it. I'll find it...
Click to expand...
Click to collapse
That would be cool, but I'm not too worried about that part. Phone is going back tomorrow!
Well, worry even less! Special thanks to Calkulin!
thankssssss
Thanks a lot for this. I have searched for a un root that worked and you were right the bootloader was the problem. Followed directions here and I am back to stock Froyo un rooted.
Thanks
topcop
I followed your guide and ran into a few issues. From my experiences, you can only run the RUU from your software version or higher (Can't use a 1.32 RUU on a Evo with software version 1.47). Therefore, I think everyone should always flash the engineering build so they can use the earliest RUU. Just my 2 cents though...
I'm getting error 155 running Ava Froyo and trying to go back.
blix1337 said:
I followed your guide and ran into a few issues. From my experiences, you can only run the RUU from your software version or higher (Can't use a 1.32 RUU on a Evo with software version 1.47). Therefore, I think everyone should always flash the engineering build so they can use the earliest RUU. Just my 2 cents though...
Click to expand...
Click to collapse
Yes, you are correct, but so am I. This is exactly what step 2 in the OP does (which is a link to Toastcfh's thread about the engineering build).
tonyk__78 said:
I'm getting error 155 running Ava Froyo and trying to go back.
Click to expand...
Click to collapse
Ok. RE-read the OP. Everything is there. Check your HBOOT version by booting to the bootloader. If you have .79, you need to re-flash the engineering build before the RUU will work (Step 2 in the OP to get HBOOT to .76). You cannot run the RUU on top of AVA froyo or any froyo, or any rooted custom 2.1 for that matter if you don't have the proper HBOOT (Which I believe you cannot have if you are running any custom rom). Flash to the engineering build, then the RUU.
How far "unrooted" does this get you? Can you still re-root using toast's method or SimpleRoot?
joypunk said:
How far "unrooted" does this get you? Can you still re-root using toast's method or SimpleRoot?
Click to expand...
Click to collapse
Yes you can still REroot VIA those methods. As long as you don't do a FROYO OTA or manually flash the UNROOTED Froyo...there is no ROOT method for FROYO yet.
It returns completely to UNROOTED stock, except for the PRI, which there is a fix for on the 1st page.
And incidentally (and I just figured this out last night) Simple Root is Toast's method, just automated...
EDIT: I think that you could even UNROOT and RUU to 1.3x (whatever it is), then use the ROOTING methods that were in place before the official 1.47 OTA rooting methods. But, I just did simpleroot last night on top of 1.47, and it is freaking SIMPLE....1 click for root...1 click to flash recovery.
tpdtopcop said:
Thanks a lot for this. I have searched for a un root that worked and you were right the bootloader was the problem. Followed directions here and I am back to stock Froyo un rooted.
Thanks
topcop
Click to expand...
Click to collapse
This is what were trying to show you on Androidcentral as well. Glad you are set!
tonyk__78 said:
I'm getting error 155 running Ava Froyo and trying to go back.
Click to expand...
Click to collapse
As long as you have .76 HBOOT flash back to an earlier rom...one that has a 1.32 base. Then use the 1.32 RUU or 1.47 RUU. You should be set. Make sure you have completed step 2 in OP.
Yes. I have .79, thanks!
Sent from my PC36100 using XDA App
Hello! I'm a long-time lurk and this is my first post. Why? Because you folks at XDA are extremely knowledgeable and very helpful! I actually enjoy reading the forums and usually can find my answer using search. Call me a masochist, I guess. I just wish I had the chops to develop and not just be a continuous noobish sponge. I have successfully rooted my own Inspire with Bubby’s method and have flashed several radios and ROMs, no problem (knock on wood).
Anywho, I have searched and have seen similar issues to mine, but I have what I consider a more unique problem (which, if I’m wrong, I’m sure you fine folks will let me know). I attempted to root my brother’s Inspire over the weekend and it is currently showing a black screen with three vibrations and amber light (If I try to go to Hboot manually, I get five whole vibrations with a green light). I can, though, pull the battery for 5 minutes or so, then the phone will boot normally. Although I think it’s on the downgraded ROM, because it shows the funky AT&T splashscreen instead of HTC. What I did was attempt root with Bubby’s and got stuck at the boot screen when the phone was trying to flash the PD98IMG.zip (downgrade I believe) after making the goldcard. It would show that it was trying to read the zip, however I never would get the “volume up to upgrade” option. I tried this three times. When that failed, I tried rooting with the Ace Hack Kit and after creating the goldcard image, when the script tried to reboot the phone to install the downgrade, I got the black screen, amber light with the 3 vibrations. My problem is that I don’t have root, can’t get to recovery from the Hboot screen (shows red exclamation with triangle) and was unable to install Clockworks Mod thru ROM manager because I’m not rooted, so no SuperUser privileges.
What can I do at this point? Maybe off base, but I believe I have somehow corrupted the boot partition or the like, including screwing up Hboot. Is it possible to fix this if I am not able to reboot without pulling the battery? I have tried going thru Bubby’s and the Ace kit again, but always fail when the phone reboots.
Thanks for your help!
I am far from an expert, or even a novice, but to me it sounds like you have a corrupted download for the bubbys one click.... Have you checked the Md5 on the downloaded file?
Sent from my Inspire 4G using XDA App
I could lie and say yes, but no I didn't check md5 the first go around (although I did the 2nd time I reinstalled, after it screwed up). I did have all antivirus programs uninstalled and firewall turned off.
It does sound like you got the downgrade rom without root. Go back to the hack kit. With the gold card in the phone, turn on usb debugging and connect to the pc in the charge only mode. Run menu number 3 in the hack kit.
Sent from my Desire HD using Tapatalk
@OP:
Follow the files and instructions in this post to get back to stock so u can start fresh. I followed these to get back to stock only today evening, and it worked.
--------------------
TO RETURN TO STOCK:
Make sure you S-ON (if able) BEFORE you Unroot. The S-On tool needs root permissions to function.
--------------------
Turn the phone on, connect to computer, and perform step 1. Make sure USB debugging is enabled.
Step 1 (S-On):
Run Bubby323's S-On tool: S-On Tool
Step 2 (STOCK ROM in ZIP FORMAT):
Place this .zip file on the root of your SD card. Disable fast boot in settings > applications. Turn off your phone. Hold down the volume down button and the power button at the same time. The phone will reboot into hboot. It will load the ROM automatically. Follow the steps to flash the ROM.
http://www.multiupload.com/JELMZNSKDF
I did this like a couple hours back, and mine's back to stock.
Note: I consolidated the links here from various posts on this forum.
Diablo: Was posting the reply below, when I saw your message. Would you still recommend I follow your steps to unroot, return to stock and run hack again?
Update: Well, I went thru Bubby’s root process again and was able to get the phone rooted (had to pull battery and wait 4 minutes when it needed to reboot). And I have confirmed root was successful. I also used Bubby’s fix to Eng S-Off (couldn’t hurt, right?). The phone now has the latest Android Revolution with Sense and the radio has been flashed (including full wipe and EXT4 wipe). However, it STILL won’t reboot correctly. I can boot directly into Clockwork from ROM Manager, but if I try to reboot normally (hold down power button and select restart), I get the black screen, amber light and 3 vibrations. Again, pull battery and wait 4 minutes and either power button to boot normally or power and volume down to get to Hboot works fine and goes to Clockwork from Hboot fine also. I guess I can keep up with the batter pull only when I have to manually restart, but WTH? There has got to be a fix for the reboot issue. Any ideas?
fernandezhjr said:
It does sound like you got the downgrade rom without root. Go back to the hack kit. With the gold card in the phone, turn on usb debugging and connect to the pc in the charge only mode. Run menu number 3 in the hack kit.
Sent from my Desire HD using Tapatalk
Click to expand...
Click to collapse
Thanks, but tried that earlier on and couldn't continue on with steps in hack kit.
ogarlen said:
...I also used Bubby's fix to Eng S-Off (couldn't hurt, right?)...
Click to expand...
Click to collapse
Well, actually, wrong, it could hurt. I'm not saying that's the cause of your problems, but you really should've read up a little more before clicking on stuff so nonchalantly.
Eng s-Off means the engineering bootloader. If that process were to fail while in the midst of performing it on your phone, it would most likely hard-brick it.
Not to mention it's unnecessary. It was only included in that rooting method at the time for flashing radios, I believe, and since then a safer method for doing so has come into standard usage that doesn't require eng s-Off.
It's also one method of resolving the cwr blackscreen people were having, where you're actually in cwr, but the screen is black so you can't see what your doing. Not the same black screen your seeing, I don't think, because you're able to at least get into cwr.
ogarlen said:
Thanks, but tried that earlier on and couldn't continue on with steps in hack kit.
Click to expand...
Click to collapse
The vibrations with the blinking led, I have seen a few posts with this. Sadly, I haven't seen anyone post a fix yet.
Sent from my Desire HD using Tapatalk
Fernandezhjir: I understand your sentiment, however my situation does seem to be a little different than the other posts, so there may be hope yet.
Scott: You're absolutely right (as if you need me to confirm that) that it could hurt. My sarcasm didn't come over very well without a wink-smiley or the like. As I mentioned before, I have read the forums and the other posts on the difference between radio s-off and eng s-off and how dangerous it can be. Actually Bubby's program fairly adequately describes that taking that step can possibly brick your phone and when you should consider taking the risk. I was desperate and dumb and poking fun at myself in my post.
Any advice with my current situation? Everything on the phone is working fine unless I try to normal restart, then I get the amber light with 3 vibrations. Again, battery pull for 4+ minutes then resinsert and power works and I can get to Hboot and Clockwork okay.
ogarlen said:
Fernandezhjir: I understand your sentiment, however my situation does seem to be a little different than the other posts, so there may be hope yet.
Scott: You're absolutely right (as if you need me to confirm that) that it could hurt. My sarcasm didn't come over very well without a wink-smiley or the like. As I mentioned before, I have read the forums and the other posts on the difference between radio s-off and eng s-off and how dangerous it can be. Actually Bubby's program fairly adequately describes that taking that step can possibly brick your phone and when you should consider taking the risk. I was desperate and dumb and poking fun at myself in my post.
Any advice with my current situation? Everything on the phone is working fine unless I try to normal restart, then I get the amber light with 3 vibrations. Again, battery pull for 4+ minutes then resinsert and power works and I can get to Hboot and Clockwork okay.
Click to expand...
Click to collapse
Heh. Now that you explain it, I can see the sarcasm. I'm usually good a picking up on it, but you know how these internet textual posts go....smilies are crucial...
As to your problem, there seem to be a few posts in recent days describing the led/vibrations type of symptom.
I don't know if they're interrelated or not. I don't have an answer, but I'm curious and will drop in if I manage to come across any pertinent information.
Thanks for the replies! I will continue to research and update this thread if I find a solution. I really believe that it has something to do with the startup processes or boot cache or some other $10 phrase related to what happens when the phone is attempting to startup normally. I appreciate all help.
Sent from my Inspire 4G using XDA App
Just wanted to add a quick update for anyone searching that comes across this post: The phone in question is now working flawlessly (knock on wood). Restarting, power down and battery pulls work with no problems (no vibrations or flashes). I am honestly unsure what I did to cause this error or what the resolution was and can only speculate. Since my last post, I have made a Nandroid backup and flashed a couple ROMs (namely AR with Sense, then Virtuous Unity with full wipes in between), so I assume that somewhere in there the corrupted boot files (or whatever) were corrected. All's well that ends well...
Here is just something to add to everyone's good advice that you received. Search for the RUU in the development section. It can fully restore your phone back to stock out of the box condition. In situations such as this it is worth having saved on your computer.
Wolf_2 said:
Here is just something to add to everyone's good advice that you received. Search for the RUU in the development section. It can fully restore your phone back to stock out of the box condition. In situations such as this it is worth having saved on your computer.
Click to expand...
Click to collapse
Not quite true. If you've rooted and have S-OFF, that will survive a complete RUU update. You have to S-ON your device before applying the RUU if you want true "out-of-the-box" restoration.
seems like you got yourself a good taste of rom flashing issues. that's a good thing. i know that you have everything working flawlessly now, BUT i would still HIGHLY recommend that you download the Super Wipe script from the Android revolution thread and use that to completely wipe and format your partitions, then do a FULL wipe through clockwork and then install whatever ROM you would like. but i cant stress enough, MAKE SURE that the Md5 sums match always. this can be the difference between a working rom and a bricked phone. also i would like to add that through my experience i usually find that the first time you root the inspire, the very first rom you install on it almost always has issues. that's how it is for me atleast. Ive rooted plenty of Inspire's and all of them have had some sort of issue on the first flash. and as always, follow the directions per rom to the T or else it might not work.
P.S. Some roms run better with matching Radio and RIL. flashing these is AWLAYS good practice to get your phone to tunr the best possible.
Wolf_2 said:
Here is just something to add to everyone's good advice that you received. Search for the RUU in the development section. It can fully restore your phone back to stock out of the box condition. In situations such as this it is worth having saved on your computer.
Click to expand...
Click to collapse
Gene Poole said:
Not quite true. If you've rooted and have S-OFF, that will survive a complete RUU update. You have to S-ON your device before applying the RUU if you want true "out-of-the-box" restoration.
Click to expand...
Click to collapse
Thats why I posted the full steps in the guide , to s-on and ruu back to stock. On a side note bubbies s-on tool does not always work.
On another side note, Genepoole would be interested in wrighting a script for the s-on/return t stock process to make it a little more automated? The steps right now are flashing back to stock then re rooting, then entering gfree s-off on then re running the ruu.
mudknot2005 said:
On another side note, Genepoole would be interested in wrighting a script for the s-on/return t stock process to make it a little more automated? The steps right now are flashing back to stock then re rooting, then entering gfree s-off on then re running the ruu.
Click to expand...
Click to collapse
I have actually considered this. The current methods require a complete downgrade just like rooting when all you really need for gfree to work is the radio and kernel from the downgrade ROM.
Gene Poole said:
Not quite true. If you've rooted and have S-OFF, that will survive a complete RUU update. You have to S-ON your device before applying the RUU if you want true "out-of-the-box" restoration.
Click to expand...
Click to collapse
You are correct. I should have re phrased that differently. I know that S-Off would survive the RUU procedure so I should have said "almost out of the box". The RUU is still a very handy thing to have.
Gene Poole said:
I have actually considered this. The current methods require a complete downgrade just like rooting when all you really need for gfree to work is the radio and kernel from the downgrade ROM.
Click to expand...
Click to collapse
Please, sir.
Seriously, this would be, imo, a profound contribution to this phone.
<Collaboration><Dev><Ideas> HTC Evo 2.3.3 Gingerbread Root Collaboration.
* I love the color orange.HTC Evo 2.3.3 Gingerbread Root Collaboration
The Lowdown on Everything
FASTBOOT
HTC's RUU releases basically run the adb reboot bootloader code, reconnect to the phone, verify the version and run a series of fastboot commands to install the contents of the PC36IMG (detailed below). In the same way it may be possible to run fastboot commands from command prompt with the SDK installed if you can time it just right in the flashing process, or not. The bootloader can be quite picky when it comes to letting anyone or anything flash anything lower than the version on the phone, or unsigned.
Click to expand...
Click to collapse
PC36IMG
The PC36IMG is what is flashed in the bootloader. The contents of the zip include the radio, system, and more. As long as S-ON is present the bootloader won't flash any PC36IMG that isn't signed by HTC themeselves, however with S-OFF you can flash custom PC36IMGs as well as downgrade, because the bootloader doesn't check the firmware version to see if it's newer or not. If someone was however to be a sneaky awesome ninja and steal HTC's secret sauce then we could simply sign any PC36IMG we wanted to and fake a newer version in the android info txt.
Click to expand...
Click to collapse
RECOVERY
From my understanding the stock recovery references alot with the bootloader to check for most of the same checks it looks for in the PC36IMG, but in the update.zip HTC includes for updates. The stock recovery won't flash anything but signed HTC update.zips either, which again you need the special sauce to sign. Custom recoveries like Amon RA or Clockwork remove the security and don't reference with the bootloader (since your phone has to be S-OFF anyways to flash a custom recovery.) A custom recovery is the key in flashing customs roms and kernels, if you can achieve it with the security on (S-ON) the you won't even have to worry about achieving S-OFF. However, that's near impossible due to the security in the bootloader HTC implements with updates. Which is why the bootloader has to be cracked to install anything.
Click to expand...
Click to collapse
RUU
The RUU is an official tool HTC puts out so people can reflash there phone with a stock firmware just like if it is brand new and your turning it on for the first time. The files included inside of the RUU frontend include the PC36IMG which is essentially what is flashed in the process, but in a fancy way I guess you could put it. The same security applies to the RUU, you can't downgrade versions without S-OFF because the bootloader still checks the version on the phone currently to see if it can flash the PC36IMG or not (when security is on [S-ON] )
Click to expand...
Click to collapse
APKS
I'm sure alot of you know of applications such as Visionary or Z4Root, they both use common exploits to root your phone in a simple application, first temp root then permanent root. They push the approiate resources, Superuser, su, busybox, set the permissions for everything to run, and clean up everything in the blink of an eye thanks to simple scripts. The same thing is still quite possible with any exploit, the exploit just has to be found in the software. You find the exploit you gain root. You have root you can do almost anything to your phone, but S-OFF still plays a role in everything with what you can and cannot flash. Sigh. I know right..
Click to expand...
Click to collapse
Our Mission
The whole purpose of this thread is to collaborate on possible ways to obtain S-OFF and/or root on 2.3.3, either update. We are community, thus we must act like one, and not bash each other for trying. If you have a truthful idea or any questions feel free to post them. You never know, you could very well help with rooting the latest update. This has gone on far to long it's been almost 2 months and no root. This is our time to free each other from the chains of security because we all like to be dangerous sometimes.
Click to expand...
Click to collapse
Possible Rooting Ideas
What Works What Doesn't
I encourage everyone to try previous rooting methods, and methods to obtain S-OFF and experiment as much as they feel comfortable with, you never know what you might find. We could be overlooking something.
Click to expand...
Click to collapse
There is no right or wrong answer only better ones than others. Please do not bash users, or slander them for there ideas, everyone has a right to post, but please stay on topic. /end
Am I missing something?
Sent from my PC36100 using XDA Premium App
lil_bono said:
Am I missing something?
Sent from my PC36100 using XDA Premium App
Click to expand...
Click to collapse
Just give me a few, I'm still typing.
<done></done>
<words>I'll be back on tomorrow, I'm going to go lay down and talk to my friend. Feel free to comment with any ideas. I, myself, am looking into and working very hard to achieve S-OFF and root for the 2.3.3 update, it will come in time. That's just the key; time.</words>
What other phones have you developed, alone or with a group, a rooting and/or s-off type process for? And I don't mean an app that uses an already known exploit such as rageagainstthecage.
I guess at least we have a fancy thread now. Best of luck to everyone.
ill jsut post a small snippet of thanks for thaking this initiative, i dont know about android os myself one bit, so i can hardly contribute, but would there be a way to "fool" the hboot or Ruu version number ?
either fooling the hboot into thinking the ruu one is trying to flash ( to downgrade of course) is a higher version one, or to somehow change the RUU itself to report a different version number? i realize this may sound incredibly stupid as my programming knowledge is very limited, but jst throwing it out there...
once again, thanks for taking this initiative for the evo 4g community
I was wondering if you could force the RUU update. We know it verifies the version on the phone, but surely to could still flash if it was forced. Sort of like doing an nvflash on the tablets. You'd just need to hack the RUU updater to skip the version check and flash anyway. Unfortunately, I'm not a cracker, so...
This should take off
There's a whole thread in Evo General full of ideas due to some kind of "bounty" to whomever achieves root on 2.3.3. At least we could get a start on what does/doesn't work. (This is not meant to deter traffic from this brainstorming thread)
http://forum.xda-developers.com/showthread.php?t=1162671
skatrwannabe3 said:
There's a whole thread in Evo General full of ideas due to some kind of "bounty" to whomever achieves root on 2.3.3. At least we could get a start on what does/doesn't work. (This is not meant to deter traffic from this brainstorming thread)
http://forum.xda-developers.com/showthread.php?t=1162671
Click to expand...
Click to collapse
Hey, great idea. Just so you know, there is no "bounty" on rooting the ota. I dont even know where that term came from. I just started a thread to say that I am desperate for root, I will pay for someone to figure it out. I never asked anyone or expected anyone else to throw money in on it too. It has since grown into a 600+ dollar pot, and I think that its a good thing. The people that take the time to root it should get a pat on the back.
On topic: I see a bunch of people saying to downgrade, isnt temp root gonna come before that? Shouldnt temp root be the thing to focus on first?
I'm not much of a programmer but ill brick my phone as many times as needed lol
Sent from my PC36100 using XDA App
github said:
What other phones have you developed, alone or with a group, a rooting and/or s-off type process for? And I don't mean an app that uses an already known exploit such as rageagainstthecage.
I guess at least we have a fancy thread now. Best of luck to everyone.
Click to expand...
Click to collapse
I've personally never been the leader of a rooting or S-OFF project before, but my knowledge of Android on a whole is pretty vast. I do develop roms and kernels as well as themes and apps for Android in general, so I guess I'm pretty qualified?
fldash said:
I was wondering if you could force the RUU update. We know it verifies the version on the phone, but surely to could still flash if it was forced. Sort of like doing an nvflash on the tablets. You'd just need to hack the RUU updater to skip the version check and flash anyway. Unfortunately, I'm not a cracker, so...
Click to expand...
Click to collapse
I'm not sure that the RUU is anything but a front end user interface for the process, the actual flashing and everything involves the bootloader, which is why it still pushes the PC36IMG temp. to the sdcard. It might however be in the RUU itself and using fastboot flashes? I'll look into it. Good idea, thanks.
Who rated the thread bad?
bubby323 said:
I'm not sure that the RUU is anything but a front end user interface for the process, the actual flashing and everything involves the bootloader, which is why it still pushes the PC36IMG temp. to the sdcard. It might however be in the RUU itself and using fastboot flashes? I'll look into it. Good idea, thanks.
Click to expand...
Click to collapse
but does the RUU update the hboot itself?
the point is , older hboots and android software are already rooted, if we can get back to those , the end result is the same, we get root, then upgrade using a stock rooted rom, problem solved
bubby323 said:
What Works What Doesn't
Click to expand...
Click to collapse
My recent failures attempts while on 4.24 S-On:
Amon_Ra Recovery PC36IMG.zip flashed from Hboot
Signed 3.70 PC36IMG.zip flashed from Hboot
Signed 4.24 PC36IMG.zip flashed from Hboot (it loads/updates, but is basically a factory reset)
3.70 RUU exe
UnrEVOked3
some chucklehead
bubby323 said:
Who rated the thread bad?
Click to expand...
Click to collapse
Eh, I put in a 5 star vote to make it up, also to show the uselessness of voting.
Has anyone looked at the contents of a PC36IMG.zip? I am still decompliling one, but its a fun task to decipher all of the code. Another thing I need is for someone to tell me which files I should be looking for as far as HTC signing. What I would like to do is maybe strip it from the stock one, and insert it into a custom image.
Sent from the land of motorcycles!
I guess I will start by saying that I have been a long time 'lurker.' I started coming around XDA back when the original Dash was new and have used all the information pumping out since then.
I tried looking around as best as I could to see if there were any other threads regarding a full root with the HTCdev bootloader but could only find discussion and debates around it.
I mostly am just confirming that it can be done. Not sure if I am a lucky one or if it was even a very risky process, but it took me all of about 15 minutes so I'm not complaining.
All I did was follow the instructions from HTCdev to unlock my sensation. After that I followed this guide from Step 2.
I currently have S-OFF, superuser access, installed a new rom, and reverted to my original rom. Everything seems to be properly working without a hitch.
Also, for clarity on this part in HTCdev FAQ:
What does this mean for me?
Unlocking the bootloader means that you now have the ability to customize software on your device. Please note that changing your bootloader can cause significant issues with your device and once you have unlocked your device, you have agreed to the disclaimer that states a change in warranty status such that in the event you render your device unusable, you are responsible for the recovery of your device, whether by repair or by other means.
Click to expand...
Click to collapse
All that means is that if you brick your device through unlocking or flashing new roms that HTC will not warranty your device. If everything works properly but you end up with other issues, i.e. touch screen no longer is responsive, then you are covered. I actually spoke to an HTC rep about it and that is what I got. Now they may try to say that unlocking may have caused it, but that isn't anything new.
Hmmm -_-
Sent from my HTC Sensation 4G using XDA App
hmmmm hmmmm cough choke cough
kleanblade said:
I guess I will start by saying that I have been a long time 'lurker.' I started coming around XDA back when the original Dash was new and have used all the information pumping out since then.
I tried looking around as best as I could to see if there were any other threads regarding a full root with the HTCdev bootloader but could only find discussion and debates around it.
I mostly am just confirming that it can be done. Not sure if I am a lucky one or if it was even a very risky process, but it took me all of about 15 minutes so I'm not complaining.
All I did was follow the instructions from HTCdev to unlock my sensation. After that I followed this guide from Step 2.
I currently have S-OFF, superuser access, installed a new rom, and reverted to my original rom. Everything seems to be properly working without a hitch.
Also, for clarity on this part in HTCdev FAQ:
All that means is that if you brick your device through unlocking or flashing new roms that HTC will not warranty your device. If everything works properly but you end up with other issues, i.e. touch screen no longer is responsive, then you are covered. I actually spoke to an HTC rep about it and that is what I got. Now they may try to say that unlocking may have caused it, but that isn't anything new.
Click to expand...
Click to collapse
Not trying to antagonize here but can you supply us with some screen shots of your "About" section and kernel and ROM part...??? No disrespect meant but if you say this is true then I would like to visualize the outcome. Thanks!
I understand anyone's skepticism. So I will provide, as best I can, whatever information I can. Have a couple screens attached. Soon as I can find a camera or get my hands on someone's phone I will take a picture of the HBOOT screen.
I'm not trying to do anything other than a "Hey, this actually worked for me." HTC's method just gave me the unlock and S-OFF. I understand it hasn't been the case for everyone. In fact I even had issues with HTC's method once I got the prompt to actually unlock the device. It wouldn't accept my input the first few tries (choosing yes or no yielded nothing).
Very legitimate. You should do a tutorial video on youtube and post it here.
kleanblade said:
I understand anyone's skepticism. So I will provide, as best I can, whatever information I can. Have a couple screens attached. Soon as I can find a camera or get my hands on someone's phone I will take a picture of the HBOOT screen.
I'm not trying to do anything other than a "Hey, this actually worked for me." HTC's method just gave me the unlock and S-OFF. I understand it hasn't been the case for everyone. In fact I even had issues with HTC's method once I got the prompt to actually unlock the device. It wouldn't accept my input the first few tries (choosing yes or no yielded nothing).
Click to expand...
Click to collapse
Sent from my HTC Sensation 4G using XDA App
hmmm
why use this and not the alpharev solution?
my question exactly...
reddoni said:
why use this and not the alpharev solution?
Click to expand...
Click to collapse
What is the difference between the two unlocking methods? Does one let you go back to S-on should you want to revert back? Are more internals accessible with one over the other (like radio's)? Just curious. When I do root I want to make sure I am using the best one with optimal features. Thanks in advance.
I personally have not seen a distinct advantage with using either method. If the phone bricks with either method you are out in the cold no matter what. Both are relatively easy to do. With HTC's method your warranty will at least be intact for any issues they deem not responsible from being rooted w/o having to 'hide' that you rooted your device. HTC's method may be easier to 'relock' your device as well. After I locked my device and rebooted, I locked it again and it was as simple as a short command. Any deeper than that I will say it's beyond my ability to know.
I feel like its as simple as an apples and oranges approach or an OEM vs after market. HTC has tested and checked their method and put their stamp of approval on it. For some 'consumers' it gives them a better sense of security. AlphaRev method works just as well but will never have the clout a large corporation, such as HTC, has.
If there is an interest for Snipes' request I could try to put a guide together. I know I don't command much credibility yet. So I don't want to do something know one would trust. However, it really isn't much different then the current guide available.
Also, HBOOT picture attached. As far as locking up your device again, with the HTC method it puts **** RELOCKED **** as the header and S-ON. I believe (not sure since I haven't done it) with the revolutionary method it simply replaces the hboot screen to the original.
How did you S-OFF? Using the same adb command as those with the Nexus One did?
I simply followed HTC's method to unlock the boot loader and it gave me S-OFF.
This gist of HTC's process is that you use go through fastboot, get your device token code, submit your token code to HTC, they email you an unlock_code.bin file, and you finish up with flashing your device with the unlock code. It is not difficult and took me about 3 minutes, maybe. The only extra thing that I am not even sure you need, is to have htcsync installed (it was listed as a requirement by htc).
Also,
The only two commands you use in the process are:
fastboot oem get_identifier_token (to get the token you need to submit)
fastboot flash unlocktoken Unlock_code.bin (flash your unlock code on the device)
If you want to relock your device you simply use:
fastboot oem lock
I just tried the HTCdev way, and I did get unlock, but did not get S-OFF
Billyvnilly said:
I just tried the HTCdev way, and I did get unlock, but did not get S-OFF
Click to expand...
Click to collapse
same here, it says unlocked but still s-on... and i get an error when trying to flash recovery (step 2) what to do?
I'll get my hands on another Sensation and see what results I get.
Odd that I would be the only one with a sensation that has s-off.
miroxlava said:
same here, it says unlocked but still s-on... and i get an error when trying to flash recovery (step 2) what to do?
Click to expand...
Click to collapse
Just start with step one then. I was able to follow all steps (except i dont need supercid) after doing htcdev. took maybe 45 minutes from start to finish, including downloads, restarts, and getting new ROM installed. Which btw, the CM7 alpha is out... trying it out soon.
Ok the HTCdev site says this. Not to mention they know you S-offed cause you did it via their website and tools.
Please understand that you will not be able to return your device to the original state
Click to expand...
Click to collapse
And in the [Guide] to Installing S-off, ClockWork, Root, SuperCID & S-on [03/AUG/11](noobproof) thread it says.
For Warranty Purposes/Returns:Follow Step 4 below for removing Clockwork and Root FOLLOW STEP 5 TO CHANGE BACK TO S-ON - CONFIRMED TO BE WORKING- USE WITH CAUTION
Click to expand...
Click to collapse
Now my question is this, if you S-off your Sensation via the HTCdev site and then S-on your Sensation via the method mentioned in the guide. Does your Unlit go back like it was originally, and not say " **** RELOCKED ****" at the top of the screen. Or is the to methods of S-offing your Sensation compatible with one another. I mean will combining the two brick the device. I would like some feed back from some devs that know more about what is actually going on when you switch from S-on to S-off, or from S-off to S-on.
Edit: Also the HTCdev site says this.
going forward your device may not be held covered under the warranty for all claims resulting from the unlocking of the bootloader. HTC bears no responsibility if your device is no longer usable afterwards.
Click to expand...
Click to collapse
So this is at the OP, just cause you use the HTCdev site to S-off your bootloader. It does not mean it does not void your warranty. And it does not mean HTC will fix your device if things go wrong and your device is rendered usless. You have to remember it is HTCdev, key word being dev not HTC.
Background:
My wife migrated from the (US AT&T) One X to the One on day one. Her One X has been sitting in her bedside drawer for almost a year. (She wanted to keep it as a backup.) Her One recently suffered irreparable physical damage; need to get her up and running on the One X.
Before the One X's temporary retirement, we:
Gained SuperCID
Unlocked Bootloader
Flashed custom recovery
Flashed a (Android 4.1 based) AOKP nightly
Did not achieve S-OFF
When the One X came back out of retirement, it had some major stability issues. Coming from the Nexus world, and (admittedly) not doing thorough enough research, I thought I could quickly re-ROM her phone and have her up and running.
Long-story short, I've somehow seemed to corrupt the recovery partition and the boot partition. And I'm not sure where to go next...
I can access the bootloader and fastboot. In fact, the bootloader is immediately loaded on boot.
I cannot achieve S-OFF. Every method I've seen requires some combination of fastboot and adb commands. I can do the fastboot portion, but without a working Android partition, I cannot perform the adb commands.
Every attempt to flash a custom recover via fastboot fails:
FAILED (remote: 12 signature verify fail)
From the research I've done, it seems like I need S-OFF to flash a recovery and ROM, but I need a ROM to achieve S-OFF.
Is that the case? Is there anything else I can try?
Run the 2.20 RUU, it's the only option you have, it should fix your partitions. Do not run the 3.18 RUU while s-on though or you'll brick.
How did the phone end up with borked partitions?
Sent from my Evita<br>
timmaaa said:
Run the 2.20 RUU, it's the only option you have, it should fix your partitions.
Click to expand...
Click to collapse
Found and downloaded 2.20 RUU; was nervous as hell running this with S-ON. The process never errored out, and the application never hung, I never saw a progress bar on the HOX either. (RUU quoted ~10 minutes. I waited 40.) I hard-bounced the phone and tried again... Success!
Thanks for the recommendation!
timmaaa said:
How did the phone end up with borked partitions?
Click to expand...
Click to collapse
I pushed the stock T-Mobile ROM to the phone from the older recovery that was already on the HOX, then rebooted. It hung at boot; was never able to boot back into Android. I was still able to access the bootloader and fastboot, so I tried pushing TWRP to the HOX using the WinDroid Toolkit. After that, I wasn't able to access Android or TWRP, and the phone booted directly to the bootloader.
The biggest mistakes: cockiness and lack of research. (Statement of frustration: this S-ON/S-OFF nonsense is for the birds!)
I'd strongly suggest you get s-off now, and discontinue your use of toolkits in favour of manual fastboot commands.
Sent from my Evita
timmaaa said:
I'd strongly suggest you get s-off now, and discontinue your use of toolkits in favour of manual fastboot commands.
Click to expand...
Click to collapse
Noted. Thanks...
The whole situation was frustrating because it was self-inflicted and I knew better than rush into trying to re-ROMing on hardware I wasn't familiar with.
I usually don't use toolkits; was just on a system that hadn't been prepped with adb yet. I re-learned a valuable lesson: take the time to set that up!
What's most frustrating is that I did try to use adb (after hosing the filesystem). I just kept running into issues with S-ON while trying to push boot.img's and recoverys. Coming from my Nexus world, I'm not accustomed to that.
Cool cool. It might be worth taking a quick look at my Evita FAQ and How-To Guide For Beginners threads in my signature. I'm not insinuating that you're a beginner, but they contain some vital information specific to this device which you might find useful.
Sent from my Evita
timmaaa said:
It might be worth taking a quick look at my Evita FAQ and How-To Guide For Beginners threads in my signature. I'm not insinuating that you're a beginner, but they contain some vital information specific to this device which you might find useful.
Click to expand...
Click to collapse
Yeah... that -- among many, many others threads -- was one of the threads I checked out after killing it.
I was so convinced that S-ON was my problem that I spent most of my time trying to get S-OFF and repair my recovery via fastboot. Had I been able to let go of that notion, I might have gotten somewhere without having to ask for help.
I only-ever mess with the wife's hardware when there's a problem, so I'm not incredibly familiar with it. I'll definitely re-review your guide before I take on any other tasks!
Thanks again!