Root DETAILED Leak Root Tutorial

akillys · Aug 7, 2010

Yeah I was going to white windows too but i couldn't get past the rebooting with out getting stuck. Well I wasn't really stuck I just got impatient and yanked the battery and threw on tazz again once you and scary alien helped me get the marker running. So I'm new to the root thing what are relativly safe buy fast over clock settings? I'm using set pcu.

scary alien · Aug 7, 2010

akillys said:
Yeah I was going to white windows too but i couldn't get past the rebooting with out getting stuck. Well I wasn't really stuck I just got impatient and yanked the battery and threw on tazz again once you and scary alien helped me get the marker running. So I'm new to the root thing what are relativly safe buy fast over clock settings? I'm using set pcu.

Lots of good info. in this thread: http://androidforums.com/all-things-root-eris/98457-overclocking-hmm.html?highlight=overclocking+hmm

Basics:

1. 710MHz is a good safe speed
2. Keep the differences between min. and max. speeds no higher than 256MHz
3. Don't enable "set-on-boot" until you've run safely and stable for a "while"
4. Use "on-demand" ("performance" is always overclocking)
5. Don't forget to set a failsafe profile

Here are erisuser1's settings as of the date of this post: http://androidforums.com/all-things-root-eris/142217-possible-bad-root.html#post1311305

Good luck.

driverx125 · Aug 7, 2010

akillys said:
Yeah I was going to white windows too but i couldn't get past the rebooting with out getting stuck. Well I wasn't really stuck I just got impatient and yanked the battery and threw on tazz again once you and scary alien helped me get the marker running. So I'm new to the root thing what are relativly safe buy fast over clock settings? I'm using set pcu.

I was stuck at a blank screen for a little to but it got past there and is awsome.

Stygian · Aug 10, 2010

Just so I know, is there anyway to go back to the stock 2.1 (or 1.5) after rooting? If there is, some directions would be appreciated! :thinking:

scary alien · Aug 10, 2010

Stygian said:
Just so I know, is there anyway to go back to the stock 2.1 (or 1.5) after rooting? If there is, some directions would be appreciated!

Yep, no problem. Just use the RUU tool http://androidforums.com/htc-droid-eris/92096-verizons-ruu-official-2-1-droid-eris.html to take you back to stock 2.1.

Stygian · Aug 10, 2010

Hmm, that link is only for a Windows .exe and I'm running on a Mac

scary alien · Aug 10, 2010

Stygian said:
Hmm, that link is only for a Windows .exe and I'm running on a Mac

Oops! Sorry, didn't know you were a Mac...not sure If I've read about an easy un-root method for Mac users...can you get access to a Windows box (or just cross that bridge when/if you come to it)?

I'll have to search-around for Mac unrooting options...

Stygian · Aug 10, 2010

Thanks anyways!

I have no access to Windows. Only reason I'm concerned about going back to the stock version is that I may receive a new phone as a gift. If I sell this Eris I'd like to post it as being factory reset with the standard 2.1 (or 1.5)

richarddd · Aug 16, 2010

i followed all the steps but once the phone reboots the second time, it just freezes and get stuck showing the HTC logo. i don't seem to get into recovery mode

can anyone help me?

driverx125 · Aug 17, 2010

did you keep holding the volume up

vannman17 · Aug 17, 2010

richarddd said:
i followed all the steps but once the phone reboots the second time, it just freezes and get stuck showing the HTC logo. i don't seem to get into recovery mode

can anyone help me?

Same thing here and nothing works. Tried the one click method and the version for dummies and i always freeze at the 3 skaters when trying to boot into recovery.

boblobla · Aug 17, 2010

Followed instructions and flashed with Froyo v29 ROM. Although, what's the catch? When I install an app that requires root, it states I am still NOT rooted and the app cannot continue. And/or I require BusyBox...Any step I missed? thanks!

erisuser1 · Aug 17, 2010

Stygian said:
Hmm, that link is only for a Windows .exe and I'm running on a Mac

Using the Leak-V3 PB00IMG.ZIP produces the identical result as the "Official 2.1 RUU", and does not require a PC/Mac for anything. So, you can get back to "stock" that way if you need to.

eu1

erisuser1 · Aug 17, 2010

vannman17 said:
Same thing here and nothing works. Tried the one click method and the version for dummies and i always freeze at the 3 skaters when trying to boot into recovery.

I think in prior conversations you had said you have the 1.46 Bootloader, yes?

That might be the cause of the difficulty, but I am not completely sure - I was only able to test with the 1.47 and 1.49.0000 and 1.49.2000 bootloaders.

As I pointed out before, flashing either the "Official 2.1 RUU" or the Leak-V3 PB00IMG.ZIP ROM file would give you a (stock) phone with the 1.49.0000 bootloader, which might behave differently and get around your trouble. Lots of folks have had success with that bootloader with either of the new "easy" rooting methods.

I can't guarantee that though, and - as I previously pointed out - it would mean that you wouldn't be able to do a Nandroid backup of your current ROM with either of these "easy" rooting methods. Worst case though, you would end up with a stock phone that went through a Factory Reset.

Having said that, because you have the 1.46 bootloader, you should also be able to use the old-fashioned "ROOT ROM (PB00IMG.ZIP)" rooting method with the battery pull trick.

eu1

erisuser1 · Aug 17, 2010

boblobla said:
Followed instructions and flashed with Froyo v29 ROM. Although, what's the catch? When I install an app that requires root, it states I am still NOT rooted and the app cannot continue. And/or I require BusyBox...Any step I missed? thanks!

This is speculation, so take it for what it is worth.

There was some recent squawking about versions of busybox having to do with support of metamorph themes, so it is possible that you are testing with an app that is sensitive to a detailed behavior of busybox (there are different versions, and they are not 100% compatible). Not completely sure - try and see if a different root app squawks at you the same way.

I can tell you that I briefly installed V29, and I was definitely able to use SetCPU (a root app) - moreover, inspecting the contents of the V29 installation files reveals that busybox is present in /system/xbin/busybox, and the META-INF/com/google/android/update-script creates a tremendous number of symlinks to it, so it should be present on your phone.

If this fails, try wiping and reflashing V29 - or try TazzPatriots V8 Froyo ROM (very similar, except that you need to flash the Gapps .zip file immediately after the V8 ROM, but before you boot it for the first time).

eu1

vannman17 · Aug 18, 2010

erisuser1 said:
I think in prior conversations you had said you have the 1.46 Bootloader, yes?

That might be the cause of the difficulty, but I am not completely sure - I was only able to test with the 1.47 and 1.49.0000 and 1.49.2000 bootloaders.

As I pointed out before, flashing either the "Official 2.1 RUU" or the Leak-V3 PB00IMG.ZIP ROM file would give you a (stock) phone with the 1.49.0000 bootloader, which might behave differently and get around your trouble. Lots of folks have had success with that bootloader with either of the new "easy" rooting methods.

I can't guarantee that though, and - as I previously pointed out - it would mean that you wouldn't be able to do a Nandroid backup of your current ROM with either of these "easy" rooting methods. Worst case though, you would end up with a stock phone that went through a Factory Reset.

Having said that, because you have the 1.46 bootloader, you should also be able to use the old-fashioned "ROOT ROM (PB00IMG.ZIP)" rooting method with the battery pull trick.

eu1

Yes i was on 1.46. Ok i ran thru the PB00IMG.ZIP ROM and i now have a stock version of 2.1 with bootloader of 1.49 and s=off. I guess that is good?

Which way should i go now? dummies version or 1 click or something else?

erisuser1 · Aug 18, 2010

vannman17 said:
Yes i was on 1.46. Ok i ran thru the PB00IMG.ZIP ROM and i now have a stock version of 2.1 with bootloader of 1.49 and s=off. I guess that is good?

Which way should i go now? dummies version or 1 click or something else?

Try the one-click, that will be faster.

After that, follow the instructions in the fourth post of the dummies thread to make an initial Nandroid backup and ROM install - the pictures are helpful.

eu1

[ Edit ] PS: The ROM that you just flashed is obviously the HTC Root-ROM, because you ended up with the 1.49.2000 S-OFF bootloader. The OS that shipped with it is chock full of bugs, so the Nand backup you make of it is mostly for the practice of making backups - they are really important.

vannman17 · Aug 18, 2010

erisuser1 said:
Try the one-click, that will be faster.

After that, follow the instructions in the fourth post of the dummies thread to make an initial Nandroid backup and ROM install - the pictures are helpful.

eu1

[ Edit ] PS: The ROM that you just flashed is obviously the HTC Root-ROM, because you ended up with the 1.49.2000 S-OFF bootloader. The OS that shipped with it is chock full of bugs, so the Nand backup you make of it is mostly for the practice of making backups - they are really important.

AWESOME we have success and i am now rooted with XTRRom 3.0.3

Big thanks out to erisuser1 for all the help. Its play time now.

boblobla · Aug 18, 2010

erisuser1 said:
I think in prior conversations you had said you have the 1.46 Bootloader, yes?

That might be the cause of the difficulty, but I am not completely sure - I was only able to test with the 1.47 and 1.49.0000 and 1.49.2000 bootloaders.

As I pointed out before, flashing either the "Official 2.1 RUU" or the Leak-V3 PB00IMG.ZIP ROM file would give you a (stock) phone with the 1.49.0000 bootloader, which might behave differently and get around your trouble. Lots of folks have had success with that bootloader with either of the new "easy" rooting methods.

I can't guarantee that though, and - as I previously pointed out - it would mean that you wouldn't be able to do a Nandroid backup of your current ROM with either of these "easy" rooting methods. Worst case though, you would end up with a stock phone that went through a Factory Reset.

Having said that, because you have the 1.46 bootloader, you should also be able to use the old-fashioned "ROOT ROM (PB00IMG.ZIP)" rooting method with the battery pull trick.

eu1

Cool, i updated the titanium backup .exe file and now works. I also download a couple other apps that needed root and they work. Thanks! Now, is there any reason I would need to do that "engineering" thing to make S=ON show as S=OFF? Thanks.

erisuser1 · Aug 18, 2010

boblobla said:
Cool, i updated the titanium backup .exe file and now works. I also download a couple other apps that needed root and they work. Thanks! Now, is there any reason I would need to do that "engineering" thing to make S=ON show as S=OFF? Thanks.

There are good arguments for doing it and good arguments for not doing it.

For:

Having an S-OFF bootloader means that you can use the "fastboot" utilitity on the PC to flash the recovery partition, the radio firmware - even the bootloader itself. That means that if you ever did something to your phone where both the main OS and the recovery boot got hosed up, it would be quite simple to re-flash the recovery partition with Amon_RA, and then simply reload your ROM from a Nandroid backup - back in business in minutes!

Against:

Replacing the bootloader is the single most dangerous thing you can do to your phone. The reason for that is that no matter what you are booting - the main OS or the recovery boot - the bootloader must come alive and be working first. If you screw up the bootloader flashing somehow - you for sure will have a brick.

The current knowledge that we have suggests that even if the only thing which works on your phone is the 1.49.0000 S-ON bootloader, it is still possible to use either the Leak-V3 ROM or the "Official RUU" PC Utility to re-flash the entire phone. From there, root can be re-performed the same way you initially got it, and then (again) you just restore the Nand backup of your current ROM to get back to where you were. So, while this is a little bit more work, it allows you to completely avoid ever flashing the bootloader, except in case of a dire emergency.

eu1

midnight assassin · Aug 21, 2010

Surgeon, thanks you I used your walkthrough about a month ago and got root right awaaway. I am now becoming a flashing jujukie so thanks for that too. I was looking over the directions from jcase in order to get the s-off hboot, and am not quite as comfortable with trying this as I have become with flashing roms. Your excellent walkthrough was easy to understand and made me feel less paranoid. I am sure that others have said that too. I am wondering if you are willing to help out with the directions to get the hboot changed. I know that you have not done it yourself but if it's not too difficult (to you) could you please simplify the directions for me. (I mean the good of the community nity

) I forgot to mention that I am a Mac. Thanks for your help even if you don't want to do this request.

surgeon0214 · Aug 21, 2010

midnight assassin said:
Surgeon, thanks you I used your walkthrough about a month ago and got root right awaaway. I am now becoming a flashing jujukie so thanks for that too. I was looking over the directions from jcase in order to get the s-off hboot, and am not quite as comfortable with trying this as I have become with flashing roms. Your excellent walkthrough was easy to understand and made me feel less paranoid. I am sure that others have said that too. I am wondering if you are willing to help out with the directions to get the hboot changed. I know that you have not done it yourself but if it's not too difficult (to you) could you please simplify the directions for me. (I mean the good of the community nity ) I forgot to mention that I am a Mac. Thanks for your help even if you don't want to do this request.

I feel honored that you would come to me for help, but I have not done the Engineering boot-loader myself. You know why? 1. It's complicated. 2. The end result is NOT worth the effort. 3. For some magical reason you loose root, you can just follow this or one of the others and achieve root again. In other words, I did not include detailed instructions of the boot-loader change because of these 3 things. If you absolutely need the boot-loader directions I will be happy to type them up.

EricB · Aug 21, 2010

surgeon0214 said:
I feel honored that you would come to me for help, but I have not done the Engineering boot-loader myself. You know why? 1. It's complicated. 2. The end result is NOT worth the effort. 3. For some magical reason you loose root, you can just follow this or one of the others and achieve root again. In other words, I did not include detailed instructions of the boot-loader change because of these 3 things. If you absolutely need the boot-loader directions I will be happy to type them up.

I've also heard that doing this is a sure-fire way to brick your phone if you do it wrong.

surgeon0214 · Aug 21, 2010

EricB said:
I've also heard that doing this is a sure-fire way to brick your phone if you do it wrong.

Yes, also another reason haha I've seen too many good people get their phone bricked because of this

EricB · Aug 21, 2010

surgeon0214 said:
Yes, also another reason haha I've seen too many good people get their phone bricked because of this

Yup, which is why I haven't and will not do it.

Root DETAILED Leak Root Tutorial

Member

not really so scary

Well-Known Member

Newbie

not really so scary

Newbie

not really so scary

Newbie

Lurker

Well-Known Member

Lurker

Newbie

Android Expert

Android Expert

Android Expert

Lurker

Android Expert

Lurker

Newbie

Android Expert

Well-Known Member

Android Enthusiast

Android Enthusiast

Android Enthusiast

Android Enthusiast

BEST TECH IN 2023

Smartphones

Best Android Phones

Upcoming

Best iPhones

Upcoming

Tablets

Best Tablets

Upcoming

Laptops

Best Laptops

Upcoming

Televisions

Best TVs

Upcoming

Game Consoles

Best Game Consoles

Upcoming

Wearables

Best Wearables

Upcoming

Smart Home

Smart Home Tech

Upcoming

Similar threads