• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

[Guide] Root/ROM FAQ/Tutorial (for 1.5)

Is anyone using a mac with the hero? I can boot into windows, but I'd rather just stay on the mac os... I searched the forums and it returned nothing.
 
First post! Read through all this forum and love the idea of rooting. Got all the way to step 7 with the autorooter and I get stuck in the constant loop "out of memory error" My question:

Does that loop stop at some point? I mounted my SD card and saw that the recovery-RA-heroc-v1.5.2.img is there on the root of the SD card. But the loop was still going on in the cmd prompt window.

Can I simply unmount and then reboot into recovery at this time with out the cmd line steps (14-end manual instructions) or do I need to stop that "out of memory error" in the cmd prompt window somehow?
 
First post! Read through all this forum and love the idea of rooting. Got all the way to step 7 with the autorooter and I get stuck in the constant loop "out of memory error" My question:

Does that loop stop at some point? I mounted my SD card and saw that the recovery-RA-heroc-v1.5.2.img is there on the root of the SD card. But the loop was still going on in the cmd prompt window.

Can I simply unmount and then reboot into recovery at this time with out the cmd line steps (14-end manual instructions) or do I need to stop that "out of memory error" in the cmd prompt window somehow?


Taken from this tutorial:

ccapasso said:
Step 7: If all goes well, you phone should reboot (if you were watching what it was doing, and read the manual steps, you will know when this should happen) and you should be rooted. *Note*I was unable to complete this as I had an Out of Memory Error (see below) so I cannot tell you if this will continue after rebooting and boot the recovery image. If someone who has successfully done it can let me know, I will edit this to reflect that.*Note*

If you get an Out of Memory Error, do not worry. I had this happen to me and it has happened to others as well. It seems to be something with Windows 7, but who knows. Anyways, if you get that error please check to see if the recovery image is actually on your phone. An easy way to do this, is to go ahead and mount your SD card and check the root directory of it (the main directory, top level, etc) to see if the recovery image exists there.

After checking to see if the recovery image is there, please unmount your SD card.

If it does exist, great, you should be able to continue around step 14 of the Manual Root Section and continue through all of it from there.

If the recovery image doesn
 
@ ccapasso

saw that. So it is of to start a new cmd prompt window? The out of memory data just kept looping for 10 minutes or so before I just bailed.

Is it OK to just close that looping cmd window and open a new one? Opening a new cmd window takes me to c:\ducuments and settings\NAME

I type "adb shell reboot" (step 14 as instructed) and get a 'adb' is not recognized as an internal or exteranl command, operable program or batch file.

Will typing C:\android-sdk-windows\tools get me back on track?

Sorry, I am a gadget user not a moder. Getting into the software guts is new to me! But exciting.
 
Yes you can close the window and open a new one. You then need to do as it says and go back to the C:\android-sdk-windows\tools

(type cd C:\android-sdk-windows\tools to do this) cd means change directory


which is where you would then do the adb commands
 
@ ccapasso

saw that. So it is of to start a new cmd prompt window? The out of memory data just kept looping for 10 minutes or so before I just bailed.

Is it OK to just close that looping cmd window and open a new one? Opening a new cmd window takes me to c:\ducuments and settings\NAME

I type "adb shell reboot" (step 14 as instructed) and get a 'adb' is not recognized as an internal or exteranl command, operable program or batch file.

Will typing C:\android-sdk-windows\tools get me back on track?

Sorry, I am a gadget user not a moder. Getting into the software guts is new to me! But exciting.

yes it's ok to close the window...
type cd\ android-sdk-windows\tools only if you have downloaded and unzipped the android sdk to that location.

make sure you follow the steps in the manual root section to get to a shell prompt
 
Dang...I wasn't doing the "cd" part. There is my one get out of stupid card used!

If I may, Is the asroot2 exploit files needed if you do the autorooter? I tried to go that link and it is behind a register page on XDA. I have the SDK and the recovery image as instructed but could not find the asroot2 file
 
I got my phone through all the cmd prompts but when i open the pre-kitchen i get this: get the error messages failed to push files and failed to find phone(i have done everything it says to do). says i need driver, and when i run the diagnostics it says i am missing java but it says its fine and i can still load the kitchen:confused::confused::confused::confused::confused::confused:
 
Dang...I wasn't doing the "cd" part. There is my one get out of stupid card used!

If I may, Is the asroot2 exploit files needed if you do the autorooter? I tried to go that link and it is behind a register page on XDA. I have the SDK and the recovery image as instructed but could not find the asroot2 file


I am not at home to verify, but I believe the asroot2 exploit should be included in the pre-kitchen. Check the folders in there, it should be there.
 
I got my phone through all the cmd prompts but when i open the pre-kitchen i get this: get the error messages failed to push files and failed to find phone(i have done everything it says to do). says i need driver, and when i run the diagnostics it says i am missing java but it says its fine and i can still load the kitchen:confused::confused::confused::confused::confused::confused:

Not sure I understand what you are saying. You say you got it through all of the command prompts, but then you say it doesn't work with pre-kitchen. Did you do the root manually? If so was it successful? Did you install the drivers as I mentioned earlier to you (either HTC Sync or PDAnet drivers)?

Java will fail if you don't have jre installed, which is no big deal as it is only used for signing. (This was discussed earlier in this thread as to what signing is, please search it for reference).
 
I got through all the cmd prompts did my nandroid backup. Then in the kitchen I ran diagnostics and it all checked but java ( I am not to concerned about that atm) and the problem occurs when I open the prekitchen and try to auto root my phone. It says "failed to push files" then "device not found" (my phone is unmounted at this time). And I am not sure do I get the required drivers out of my HTC sync folder or do I need to get them offline.

Should my phone be mounted during the rooting process ??
 
If you did your nandroid backup, you are already rooted. Why are you trying to auto-root if you have already rooted manually?

Yes you need the drivers, they are referenced in the tutorial. Please re-read it.

Your phone itself should not be mounted, nor should the SD card. Your computer needs to recognize your phone though as a device, which if you have the proper drivers installed (if you have HTC Sync installed and you are still getting that error, then install the PDAnet to get the correct drivers), it would recognize it.
 
That is where I got confused so since my phone is rooted and backed up I can install a custom Rom now my only question is the pre kitchen says its for FRESH ROM. Where do I get that from or will the pre kitchen do that from me? And thanks for all the help you guys have previously given me
 
as far as the kitchen being only for Fresh... not really... once rooted, you can use it to add themes or lock screens and things like that to other ROMS.. it is only for Fresh to add/remove Sprint apps
 
You are confused :). Pre-kitchen is not part of fresh rom or anything like that. Get it from the link above. Follow the insturctions after pre-kitchen portion to install Fresh 1.1
 
UPDATE:

My phone is rooted and running Fresh ROM 1.1 like a champ with no issues and it only took about 2 hours of work over 2 days to do including the mess up's. I want to thank ccapasso for this awesome step by step thread and I also want to thank tatonk_Hero, ccapasso, and mysticmead for helping me out when i got stuck since i have only had my hero for 3 days i did not know much about it but with the help and this thread it was cake. Thanks Alot!
 
UPDATE:

My phone is rooted and running Fresh ROM 1.1 like a champ with no issues and it only took about 2 hours of work over 2 days to do including the mess up's. I want to thank ccapasso for this awesome step by step thread and I also want to thank tatonk_Hero, ccapasso, and mysticmead for helping me out when i got stuck since i have only had my hero for 3 days i did not know much about it but with the help and this thread it was cake. Thanks Alot!


Glad you got Fresh 1.1 running and glad you like the guide. I will be writing more, I have one in the works now, and will be writing more soon. Happy modding :)
 
UPDATE:

My phone is rooted and running Fresh ROM 1.1 like a champ with no issues and it only took about 2 hours of work over 2 days to do including the mess up's. I want to thank ccapasso for this awesome step by step thread and I also want to thank tatonk_Hero, ccapasso, and mysticmead for helping me out when i got stuck since i have only had my hero for 3 days i did not know much about it but with the help and this thread it was cake. Thanks Alot!


always happy to help... you're gonna LOVE this phone
 
that was seriously so damn easy.

I was intimidated by the manual, but when the one click wouldn't work I tried it (I really wanted to experiment with rooting).

So easy, you should put that in the faq:::SOMETIMES MANUAL ROOTING IS EASIER.

It took less time to root, flash gumbo and fresh, WITH the fresh flash fix than it did to troubleshoot the kitchen.
 
that was seriously so damn easy.

I was intimidated by the manual, but when the one click wouldn't work I tried it (I really wanted to experiment with rooting).

So easy, you should put that in the faq:::SOMETIMES MANUAL ROOTING IS EASIER.

It took less time to root, flash gumbo and fresh, WITH the fresh flash fix than it did to troubleshoot the kitchen.

Glad that worked for you.

For me, it was the other way around. I should have went with the auto-rooter to begin with. Manual mode was not working for me at all.

Downloaded the pre-kitchen, got the fix, opened it up, and bam, rooted in no time.

Got teh Fresh 1.1, gumbo, setCPU and good to go man.

But yeah, auto-rooter gets a +1, and manual gets a +0 :)
 
Thanks for the guide!

I've had this phone since the beginning of the month, but found this site last month. Really only registered to give my thanks, and to stop mooching the info. Hopefully I can contribute:)

I'm rooted with Fresh, Gumbo, and setcpu. This thing is faster than my wifes! Haven't done hers...yet.

I had a problem manually at first. Then I tried to auto-root. I have a "with google" phone, and had to push the RA 1.2.3, then do the 1.5.2. It worked after that, but I started getting anxious after it would hang on the htc loading screen.

All's well that ends well.:D
 
I updated the FAQ section just now with a How to Mount/UnMount as there have been people having issues with that.
 
Back
Top Bottom