• 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)

One other thing I want to check is to see if I'm even mounting/unmounting properly. "Mounting" just means dragging down the notification bar, clicking "Enable USB file sharing" and then clicking "Mount," correct? Then when I need to unmount, I usually click Settings-->SD Card but "Unmount" is always grayed out. I need to turn off USB file sharing first, and then "Unmount" is available. Am I doing that correctly? I had always thought that enabling/disabling USB file sharing was synonymous with mounting/unmounting but figured I'd go into Settings-->SD Card just to be safe. I'm using Fusion/XP on my MacBook so my only option on the computer is to "Safely Remove Hardware" which doesn't seem to do anything... so I haven't even been messing with that.

Thanks again for the help. Really hoping we can all figure this out and get the latest ROM/kernel up and running.

When I mount/unmount I did the following:

To Mount, when prompted in Notification bar, click on enable file sharing then mount as you did. To unmount do the same, but choose unmount. Do not go into settings>sd card>unmount. There is no need to do that. Try that and see if it works for you.
 
Upvote 0
Are you still doing it via auto root? As I mentioned earlier, looking at your print screen, there are steps missing there. Look at your cmd prompt vs the manual procedure. There are steps missing. You are missing the entire process or pushing the RA to your SD card, rebooting, then continuing. Please read through the manual procedure and hopefully it will make more sense.
 
Upvote 0
@ccapasso: Can you think of a cause or scenario where manually flashing the recovery image generates a correct response at the command line, yet no flashing has actually taken place? I'm pretty sure that's where I'm at. The recovery img file was pushed to the sdcard. I can see it there, both with Astro and with Windows Explorer (Vista32) if I mount the card.
 
Upvote 0
When I mount/unmount I did the following:

To Mount, when prompted in Notification bar, click on enable file sharing then mount as you did. To unmount do the same, but choose unmount. Do not go into settings>sd card>unmount. There is no need to do that. Try that and see if it works for you.

Ok, that's what I had been doing up until the last time I tried this last night before giving up, and no luck. Maybe I just need to try this on another computer?
 
Upvote 0
When doing it from cmd line, once the RA has been pushed, it should say X transferred at X. Do you see that showing up? If so, then the RA has been successfully pushed to your SD Card.
Yes, it said "1804 KB/s (3356672 bytes in 1.816 seconds)", which matches the size of the file on the card exactly. So my next question is: If the file is there, what might cause it to respond correctly to the recovery flash entry without actually flashing it?
 
Upvote 0
Yes, it said "1804 KB/s (3356672 bytes in 1.816 seconds)", which matches the size of the file on the card exactly. So my next question is: If the file is there, what might cause it to respond correctly to the recovery flash entry without actually flashing it?

Same here. Pushed correctly and showed up in the folder when mounted or using ASTRO, but I'm not convinced the flash part worked. Recovery rebooting just locked up on the "htc" screen for me.
 
Upvote 0
With it there, it isn't flashed yet, the file just resides on your SD Card. Once pushed, you must reboot (adb shell reboot), wait for the phone to come fully, continue with #15.
I'm certain that I did that as instructed, and repeated the process twice when the flash failed. I"ll reboot the phone and try it again. Thanks again for your help and patience.
 
Upvote 0
I'm certain that I did that as instructed, and repeated the process twice when the flash failed. I"ll reboot the phone and try it again. Thanks again for your help and patience.

Yeah I did the first reboot as instructed, waited for the phone to fully boot, etc. How long should the flash process take? It says "a few seconds" in the tutorial, but mine is like 1-2 seconds tops. Is that normal or should it take longer?

I can't try this right now since I'm at work, but I read here that flipz walked a few people through rooting who had a similar issue and for some reason flashing the v1.2.3 img first, and THEN the v1.5.2 img seemed to work for them. I'll definitely give that a shot tonight.
 
Upvote 0
Yeah I did the first reboot as instructed, waited for the phone to fully boot, etc. How long should the flash process take? It says "a few seconds" in the tutorial, but mine is like 1-2 seconds tops. Is that normal or should it take longer?

I can't try this right now since I'm at work, but I read here that flipz walked a few people through rooting who had a similar issue and for some reason flashing the v1.2.3 img first, and THEN the v1.5.2 img seemed to work for them. I'll definitely give that a shot tonight.
Thanks for the confirmation, Drew. I've rebooted the phone, opened the cmd line, cd'd back to the SDK tools folder, and re-entered lines 15-18. I don't even get a 1-2 second delay; it simply echoes the entry syntax, then immediately returns the root prompt on the next line. I ran the reboot recovery entry, got the quick vibration and HTC logo, and the phone went dead a second later. It's been at least 5 or 6 minutes and the phone is still dead and unresponsive to any button input. No flaming Sprint logo animation, no Hero logo or animation. If I pull the battery, it will do a full reboot, but if I try to force a recovery reboot to run a Nandroid backup, it will rapidly scroll several error messages and freeze up on the HTC logo.
 
Upvote 0
So you pushed 1.2.3, flashed it, and all went well? From there, you can simply as you did push the 1.5.2 recover img and flash it. Even if it did the out of memory errors, which I have gotten, it should be ok. Once the 1.5.2 img is on your sd card, after already flashing 1.2.3, go ahead and continue manually but this time use the 1.5.2 image instead.
 
Upvote 0
Also, thanks for the notice about the typo in that step, it is fixed. My apologies about that.

You're welcome. :) Thank you for compiling all the data and your continued support to the thread! If it wasn't for your post I probably wouldn't have rooted. It just seemed so daunting before (and I consider myself a pretty tech savvy person). But within 1 hour (it would have been less had HTC Sync actually worked for me) I was rooted and loading up Fresh 1.1. HOLY SMOKES!!! What a big difference. Thank you, thank you, thank you. And especially thanks to the people who figured out the root and built the ROMS. Just further proving why Android is far superior.
 
Upvote 0
So you pushed 1.2.3, flashed it, and all went well? From there, you can simply as you did push the 1.5.2 recover img and flash it. Even if it did the out of memory errors, which I have gotten, it should be ok. Once the 1.5.2 img is on your sd card, after already flashing 1.2.3, go ahead and continue manually but this time use the 1.5.2 image instead.
Following the error addresses, the cmd line says "[1] Killed su", with the $ shell prompt on the next line. Have you seen that response, and do you still think that v1.5.2 is correctly flashed? Thanks.
 
Upvote 0
Yes, that is normal. I have seen that. To be sure, go ahead and using an app like astro and make sure that your 1.5.2 img is on your SD card. If it is (as stated in tutorial) you should be good to go on manually.


Also, as an FYI, I am currently at work (been here since 8am est) and can only check this every now and then. If I do not respond to a question, hopefully someone else can, or I will get back to you as I am able :)
 
Upvote 0
Yes, that is normal. I have seen that. To be sure, go ahead and using an app like astro and make sure that your 1.5.2 img is on your SD card. If it is (as stated in tutorial) you should be good to go on manually.


Also, as an FYI, I am currently at work (been here since 8am est) and can only check this every now and then. If I do not respond to a question, hopefully someone else can, or I will get back to you as I am able :)
Hey, no problem, I just appreciate that you're helping me at all. One thing I may not have communicated well though, is that the memory errors were not the result of pushing the file, they were a result of trying to flash it. Is that still ok to go on and try the back up and flash a rom?
 
Upvote 0
Ok good. So you are rooted and have a stable RA. That is good news :)

Where did you get your 1.5.2 img from? Are you using the one from pre-kitchen or the one in the link in step 3?

Whichever you are using, try the other. Just to be sure, after your phone is hooked up to your PC, double to check to make sure USB Debugging is still enabled. If so, push the 1.5.2 img. Are you able to push the img successfully?
 
Upvote 0
Ok good. So you are rooted and have a stable RA. That is good news :)

Where did you get your 1.5.2 img from? Are you using the one from pre-kitchen or the one in the link in step 3?

Whichever you are using, try the other. Just to be sure, after your phone is hooked up to your PC, double to check to make sure USB Debugging is still enabled. If so, push the 1.5.2 img. Are you able to push the img successfully?
I got it from step 3, so I will now try the one from pre-kitchen. Does it matter if I push a new img file on top of the file that's already there, or is it better to delete the current one and start over?
 
Upvote 0

BEST TECH IN 2023

We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.

Smartphones