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

Sprint Hero HAS BEEN ROOTED@!

bray424 said:
I was having similar problems but I noticed that even when PdaNet didn't finish installing, it did still successfully install the drivers.

If that doesn't work, after choosing the install directory and hitting next, all the drivers will be extracted to a sub folder in that directory, so if you should be able to go there and copy that folder before you progress any further with the pdanet installation.
Click to expand...

thanx, none of those drivers worked though. looks like im screwed.
 
I have rooted my phone. I did the flash_image recovery. Everything is fine, I think.

It's just that I can't get to the recovery screen.

When I type in "reboot recovery" as superuser, my Hero reboots, shows the HTC logo then goes blank. Unresponsive to anything. I have to take the battery out and reboot it.

Turning the phone off and booting it with VOL Down Key + Power and then pressing home just gets me stuck on the HTC logo, unable to do anything.

Anyone have/had similar issues that can help me out?

I've also deleted the Recovery img off my SD card, and pushed it back and flashed again twice. > <
 
Did you use Recovery Flasher to backup a recovery image? If you did, try flashing that recovery image back to your phone and starting over.
 
cypherus said:
Did you use Recovery Flasher to backup a recovery image? If you did, try flashing that recovery image back to your phone and starting over.
Click to expand...

Recovery flasher? Probably not then cause I don't know what that is.

Here is what I did:
Code: 
adb push recovery-RA-heroc-v1.2.3.img /sdcard/

I got a response.

Then I did:
Code: 
adb shell
cd /sdcard/
su
flash_image recovery reocvery-RA-heroc-v1.2.3.img /sdcard/

I got this in response:
Code: 
flash_image recovery -RA-heroc-v1.2.3.img /sdcard/
usage: flash_image partition file.img

Then I was like, ALRIGHT COOL IM DONE JUST NEED TO BACK UP NOW.
Code: 
reboot recovery

HTC logo, screen goes blank. Unresponsive. Gotta take out battery to boot back up.
 
Sorry, I thought you were using the Recovery Flasher. So you are sure you went through the rooting process and it was successful right? If not, make sure you follow the steps here http://theunlockr.com/2009/11/07/how-to-root-your-cdma-htc-hero-sprint-verizon/

Next follow these steps:

Flash a New Recovery Image

1. Find the recovery image you want and MAKE SURE IT IS FOR YOUR PHONE (should say in where you download it what phone it is for).​
2. Write down the filename of the recovery image EXACTLY as it is written (i.e. RA-Hero-Recovery-v1.2.2.img).​
3. Put the recovery image file on the SD card (not in any folders).​
4. Download Terminal from the Market if you don​
Click to expand...
 
Yeah, I'm definitely rooted.

I just tried your suggestion, downloading your copy of the .img and flashing it on the phone directly instead of the command prompt on my comp.

Flashed it, rebooted into Recovery. HTC logo for a second or so blank screen. :[

It's frustrating because I want to delete the stock apps and install the Modaco ROM, which I can do but if I did, I wouldn't have a backup to go back to when I need to.


EDIT: I'm gonna flash back to factory reset and re-root the phone and try again. Some people on XDA said they were able to get into the recovery screen after doing that.
 
I got this in response:
Code: 
flash_image recovery -RA-heroc-v1.2.3.img /sdcard/
usage: flash_image partition file.img
Click to expand...
TOKiMONSTA said:
I'm gonna flash back to factory reset and re-root the phone and try again. Some people on XDA said they were able to get into the recovery screen after doing that.
Click to expand...


I'm hoping you see this before you flash the RUU / factory reset.

When you tried the flash_image command and it came back with a 'usage: ... ' type statement, the command was trying to tell you how to use it, not that it worked.

Next time, try (without the $/# characters of course):
Code: 
$ cd /sdcard
$ su
# flash_image recovery recovery-RA-heroc-v1.2.3.img
What you should get in response is.. absolutely nothing. If you get an error, warning, or 'usage' statement, something went wrong.
 
pking said:
I'm hoping you see this before you flash the RUU / factory reset.

When you tried the flash_image command and it came back with a 'usage: ... ' type statement, the command was trying to tell you how to use it, not that it worked.

Next time, try (without the $/# characters of course):
Code: 
$ cd /sdcard
$ su
# flash_image recovery recovery-RA-heroc-v1.2.3.img
What you should get in response is.. absolutely nothing. If you get an error, warning, or 'usage' statement, something went wrong.
Click to expand...

Yeah, That wasn't the only command I tried. That was just he last one I did.

I've done,

adb shell flash_image recovery recovery-rA-heroc-v1.2.3.img

adb shell
su
flash_image recovery /sdcard/recovery-RA-heroc-v1.2.3.img

and all variations, including yours etc etc. I've read the whole thread on XDA, and tried every method they suggested to the two people having the same issue. One of them asked them to do RUU back to default and do the rooting process again and it worked.

EDIT: I'm having trouble using the RUU. It tells me there is a connection error but when I go into the androidsdk\tools\ command prompt and type adb devices it recognizes my phone. HTC sync recognizes it as well. Gonna try different USB port then I don't know...can't even get my phone back to factory. :/
 
What operating system are you using? Is the phone in Debug Mode? Are you certain that you installed the drivers properly for ADB?
 
Try this:

Reinstall Drivers (If they did not install properly in Section I)

1. Download USBDeview
USBDeview
2. While the phone is still plugged in, open USBDeview and sort by manufacturer. Find all the HTC drivers and delete them all.
3. Once all have been deleted, unplug the phone from the USB cable and plug it back in.
4. The correct drivers should reinstall automatically (check the drivers as they are installing, one should say ADB Device driver).
5. To check, goto Devices in your Start menu then click on the &#8220;Android Phone&#8221;. Click on the Hardware tab, and check the list of drivers for ADB Interface under Type.
5. Done! Now you can use ADB to alter your phone from your computer.
Click to expand...

Are you able to mount the phone as a drive? If the instructions above don't work...try downloading the drivers for ADB from here Debugging/Installing apps on the G1 (Windows Driver) :: anddev.org - Android Development Community | Android Tutorials

You can also hit me up on AIM if you want xxcypherusxx
 
Okay so I ran the RUU. Got back to exactly factory defaults.

Re did the rooting process and flashing. Immediately went into Recovery Mode. I'm actually loading up the new ROM right now. ^_^
 
cypherus said:
So you got it? What was the difference in what we tried?
Click to expand...

/shrug. All I know is, running the RUU program to go back to exactly factory defaults made the difference. Don't know why, but if anyone is having problem going to recovery screen then I would recommend doing it if you really want to flash to a different ROM. Of course, after exhausting all other options because it will delete everything from your phone and since you can't access the recovery screen you don't really have a nandroid backup lol.
 
^^This exact thing happened to me. It ended up being a corrupt img file. Just re-download and over-write your existing img file on the SDCard and re-flash it.

Worked for me after hours of incredibly frustrating tinkering.
 
It wasn't that for me at all. I downloaded like 6 img files from different sources. In fact the img I used was one that didn't give me a screen before I reflashed to stock.
 
So, I have been bouncing around between threads, and from my understanding, if your phone is rooted, but you haven't installed custom ROM, then your update should install just like an unrooted phone. Is that correct? I just tried mine, and the update downloaded just fine, it rebooted to reovery mode, where I chose the "reboot" option, and then it rebooted normally. However, when I checked the phone information, it was still showing the old version before update. I don't care if I unroot my phone, as the only thing I rooted it for was to take off the sprint apps. Any advice?
 
If you have rooted, this update will not install. You must unroot, update and reroot using the same methods you previously used.
 
nathanotis said:
If you have rooted, this update will not install. You must unroot, update and reroot using the same methods you previously used.
Click to expand...

This is inaccurate.

A phone that is just rooted, WITHOUT a custom ROM can be updated just fine. I know because I did it myself. I only rooted my phone to fix the crashing/downgrading apps issue (and just for the hell of it).

If you do have a custom ROM installed, the OTA update will not install. You will have to reflash back to a stock ROM image and then run the update. But if you're using custom ROMs and, still wish to keep using them, there's no sense in even getting this update. Just wait for your ROM provider to release an update.

Either method will unroot the phone and you will have to reroot the phone again using the same method mentioned on page 1 of this thread.
 
Should also clarify, without a custom ROM or custom recovery image.

I rooted my Hero only to remove some of the stock apps and I installed the heroc recovery image to gain the nandroid backup program. I did not install any custom ROMs.

With that scenario, the MR patch from Sprint will not install on my phone.
 
pdragon said:
A phone that is just rooted, WITHOUT a custom ROM can be updated just fine. I know because I did it myself.
Click to expand...

That's interesting. I don't doubt you, but I was NOT running a customer ROM, the phone was rooted and the install would NOT install. I tried several times.
 
You must log in or register to reply here.
Back
Top Bottom