When a root isn't a root!?!

[cheggerspop]

Folks,

I've recently rooted my Hero, but I'm not sure it's actually worked!?!

When I start the unit by pressing Power and Home, the Android Recovery System (root) menu appears and that makes me a happy-type-chap.

But........and there's always a but........when I try and use any root app they either say the unit isn't rooted or just don't do what they're suppose to

I know that apps are generic and growing/learning on a day to day basis (which I think is why I'm so happy that I went with the Hero/Android) and I'm thinking that maybe due to the recent Hero upgrade and the root build I have, the current root apps aren't compatible?

Here's a breakdown of my current set-up:

Firmware - 1.5
Software - 1.0.0.A6288
Root - RA-HERO-v1.2.2

Any help would be really appreciated.


Chegs.

 

[G8D]

I have MoDaCo and a similar issue.
Seems to me like the apps are not updated to work with Hero/MoDaCo..

 

[Slug]

When I start the unit by pressing Power and Home, the Android Recovery System (root) menu appears and that makes me a happy-type-chap.

Right, you've flashed the modified recovery image successfully....

But........and there's always a but........when I try and use any root app they either say the unit isn't rooted or just don't do what they're suppose to

Did you push su and superuser.apk to the device as per the instructions? It's su (superuser) that gives root access, and superuser.apk lets you 'whitelist' trusted apps.

I'm thinking that maybe due to the recent Hero upgrade and the root build I have, the current root apps aren't compatible?

I haven't found one yet. Root Explorer, Root Booter, Backup for Root Users, Autostarts and Swapper all work with MCR2.3.

 

[cheggerspop]

Did you push su and superuser.apk to the device as per the instructions? It's su (superuser) that gives root access, and superuser.apk lets you 'whitelist' trusted apps.

Okey dokey, as I've seen so may lists of instructions over the past few days I've got myself even more confused that you'd realise!?!

I've not pushed the su and superuser.apk, as using the Command Prompt hasn't been possible, seemingly due to the upgrade on my handset, which is why I had to go with the SD root option.

Oh what to do


Chegs.

 

[Slug]

I've not pushed the su and superuser.apk, as using the Command Prompt hasn't been possible, seemingly due to the upgrade on my handset, which is why I had to go with the SD root option.

Oh what to do

You should be able to do from the prompt when in the recovery image, I think. Actually, I think you may have to fastboot into it to get access.... haven't got time to check at the mo but I'll try to confirm later.

 

[cheggerspop]

You should be able to do from the prompt when in the recovery image, I think.

Slug-Meister, how do I get "in the recovery image" and can I assume the prompt would be via the PC?

Actually, I think you may have to fastboot into it to get access

Ah, something else I don't understand!?!

Bloody computers/data/binary code!?!

.... haven't got time to check at the mo but I'll try to confirm later.

No worries fella. One day we'll get this sort and I can stop bothering you


Chegs.

 

[Slug]

how do I get "in the recovery image" and can I assume the prompt would be via the PC?

Correct, you'll use the command line via a Windows prompt.

I assume you have a folder on your PC from your earlier flashing containing Recovery-RA-HERO-v1.2.2.img? Next, download modacopatchedrecovery-1.0.zip and extract the contents of the /Hero folder to there. You need adb.exe, fastboot.exe, superuser.apk and su.

Now comes the fun part....

1) restart into bootloader (switch on holding the back button)

3) Connect handset via USB

4) open CMD prompt from the above folder and type the following command: fastboot boot Recovery-RA-HERO-v1.2.2.img
(your handset should now enter the recovery console)

5)Now type the following commands exactly as they are here, hitting enter for a new line:

adb shell mount /system
adb push su /system/bin/
adb shell chmod 4755 /system/bin/su
adb push Superuser.apk /system/app/
adb shell reboot

Congratulations you now have root access!

As a quick check, connect handset via USB and at the command prompt (as above) type: adb shell
If you then see the $ prompt, type su. A black window will pop-up on the handset and (eventually) ask you to allow/deny root access. This is Superuser Permissions (superuser.apk) doing its thing - select 'always allow' so that you can run as su without hinderence in the future. You'll then see the # root prompt as visual proof of your rootedness.

 

[cheggerspop]

I am now fully rooted and booted

YEAAHHHH!?! (< This isn't shouting, it's me being very excited!)

Slug, you're a diamond and thanks for sticking with me on this


Chegs.

 

[Slug]

I am now fully rooted and booted

It worked? Phew! Glad you're fixed up, Chegs.

 

[cheggerspop]

It worked? Phew! Glad you're fixed up, Chegs.

I almost threw the computer out of the window and it wouldn't mount the img via Fastboot USB, but as I already had it installed (via the SD card), decided to risk bricking my Hero and try the abd commands via the recovery screen and it work..........well it's certainly now letting me use the root software from the Market etc.

I tried the adb shell thingy, but a #, rather than $ came up, so when I grab root software, I'm clicking the grant permission always button at this point, which I again expect (well hope) is normal?


Chegs.

 

[Slug]

II tried the adb shell thingy, but a #, rather than $ came up, so when I grab root software, I'm clicking the grant permission always button at this point, which I again expect (well hope) is normal?

Yup, it's good. I go straight to # prompt also but I couldn't remember if it had always been that way.

 

[justjimjpc]

Yup, it's good. I go straight to # prompt also but I couldn't remember if it had always been that way.

A $ prompt is the prompt for normal terminal ...

whereas:

a # prompt is the prompt for root (super user)