[Recovery] j_r0dd-mb200-v2.0 FINAL (2/6/11)

[tonymy01]

As I said, your superuser app is wrong, so you will never get that to work, but if you only want to flash a recovery, then run the rageagainstthecage binary again to get a hash# prompt and then you can do anything that su can do.

edit:
Bingo, I mucked about with "superoneclick" on my DEXT a bit more, and it turns out that not all su/superuser.apk are made the same. The versions included in with the folder for superoneclick (the automated rooting tool that does everything for you that previously you manually had to do) are for Eclair & Froyo, (2.1&2.2) and won't work for Cupcake/Donut (1.5&1.6). You need to download the PROPER su & superuser package for your operating system. If you use the *wrong* ones, you will get the "linker" error messages when you (or an app asking for root privs) tries to run "su". Get either version cd=cupcake/donut ef=eclair/froyo HERE: http://forum.xda-developers.com/showthread.php?t=682828

Get the superuser.apk & su files from the zip (they are in separate folders in the zip as it is in a flashable update.zip format, but this update.zip WILL NOT WORK for the Moto recovery), put the resepctive files into the superoneclick directory, and run superoneclick (ensure USB debugging is enabled under settings, applications, development).... job done!

[GuanhaoMOTO]

1) I would like to ask how to boot into the custom recovery?

2) How do i boot into the ROM?

[bloodyshyt]

if you had already flashed the recovery image, shut off the phone and reboot, while rebooting, keeping pressing the camera key until there is a message asking u to release. Press the down volume button to go into recovery.
if u are on 1.5, u make want to do an nandroid backup
wipe an flash the rom of your choice.
for more info, check out theunlockr and look for how to flash a custom rom. hope this helps.
sent from opera mini

[j_r0dd]

was doing adb while in recovery yes. i can flash this? thought i had to extract and rename recovery.img

still dont see what im doing wrong. i followed all the instruction and im stuck with some terrible basic version of 1.5

The system isn't mounted in recovery therefore it will fail. You can do it while the phone is booting though. Thinking about adding the mounts options to the recovery

Sent from my SGH-T959 using Tapatalk

[Buck Shot]

The system isn't mounted in recovery therefore it will fail. You can do it while the phone is booting though. Thinking about adding the mounts options to the recovery

Sent from my SGH-T959 using Tapatalk

did it on boot with handlers method and still not found. I then tried it on boot with ur commands and it stated su not found. Im guessing handlers update.zip does not have SU permissions? I nned root?

[j_r0dd]

did it on boot with handlers method and still not found. I then tried it on boot with ur commands and it stated su not found. Im guessing handlers update.zip does not have SU permissions? I nned root?

Google superuser 2.3.6.1. Extract the zip. Then do the following.

adb remount
adb push Superuser.apk /system/app
adb push su /system/bin
adb shell
chmod 06755 /system/bin/su

You will have root after

Sent from my SGH-T959 using Tapatalk

[GuanhaoMOTO]

Ok... Now i am following every steps given. And redo several times and still the same result...
But i still can't root and got the following result...
And i am still unable to get that freaking idiot # sign out of the CMD while $ is still coming out...


Anyone wants to use Teamviewer to help me?

[tonymy01]

You Are not rooted, you only have a $ prompt. If you can type su, do it.

[GuanhaoMOTO]

You Are not rooted, you only have a $ prompt. If you can type su, do it.

i got the 3 errors after typing SU.

Ok i have tried the method
If you end up with "#" prompt, do the following. Otherwise reboot the phone and try opening the "Terminal Emulator" again. If even that doesn't give "#" prompt, go back to step "./rageagainstthecage-arm5.bin". There are mixed results atm., but some succeeded. See this post for possible way:


Here are two results by screenshots (Windows XP and Windows 7) which i still can't get $ to #...

[tonymy01]

As I said before, get superoneclick1.5.5, swap out the su and superuser.apk files with the ' cd' ones (cupcake and donut) from the su-2.3.1-bin-signed.zip file you can download, run the exe and your phone will be rooted in about 15 seconds.

[nusz]

Hi need to ask something...

I have installed this recovery image...if I'm flashing with custom ROM...will it unlock the SIM lock? Or it is still remain locked?

[j_r0dd]

Hi need to ask something...

I have installed this recovery image...if I'm flashing with custom ROM...will it unlock the SIM lock? Or it is still remain locked?

No

Sent from my SGH-T959 using Tapatalk

[tonymy01]

I just tried this recovery for the first time (have been mucking about with my little dext lots to build up a stock Aussie system for people to roll back) and I have to say "thankyou thankyou thankyou" hehehe.
I was using handlers one, and he didn't even have shell in /system/bin, so you couldn't run adb to do anything. With yours I can do plenty from your recovery from adb on the PC, which is a necessity when I am experimenting and pushing different files, moving other files etc to the sdcard for flashing or nandroid backup/restores (and with the adb shell allowed, I can get in there and do what I want, rather than what the few menu options in most recoveries generally let you).
(I flashed it on a stock 1.4.8sbf.... wow that f/w was a pain for superoneclick to root!! Took about 25mins of looping and rebooting phone and disabling/re-enabling USB debugging before it would take, where as running the Aussie 1.5.10 f/w it takes nearly the first loop! Once rooted of course can #flash_image recovery /sdcard/JRoddsRecoveryIsTheBest.img ).

(edit: the reason I was using Handlers was his nandroid restore option gave a menu for which directories to restore, which other recoveries have not in the past, only offering to restore more recent... but yours thankfully does!!)
Cheers, and thanks!

[th_black_joker]

I had the "su" problem so i did
adb shell flash_image recovery /sdcard/recovery.img
and it still pushed it to work, when i booted the recovery, just wanted to ask if I have to watch out for anything just in case that was the wrong thing to do or am i just fine and dandy?

[j_r0dd]

I had the "su" problem so i did
adb shell flash_image recovery /sdcard/recovery.img
and it still pushed it to work, when i booted the recovery, just wanted to ask if I have to watch out for anything just in case that was the wrong thing to do or am i just fine and dandy?

you're good if you a recovery that looks like the pix in the 1st post

I just tried this recovery for the first time (have been mucking about with my little dext lots to build up a stock Aussie system for people to roll back) and I have to say "thankyou thankyou thankyou" hehehe.
I was using handlers one, and he didn't even have shell in /system/bin, so you couldn't run adb to do anything. With yours I can do plenty from your recovery from adb on the PC, which is a necessity when I am experimenting and pushing different files, moving other files etc to the sdcard for flashing or nandroid backup/restores (and with the adb shell allowed, I can get in there and do what I want, rather than what the few menu options in most recoveries generally let you).
(I flashed it on a stock 1.4.8sbf.... wow that f/w was a pain for superoneclick to root!! Took about 25mins of looping and rebooting phone and disabling/re-enabling USB debugging before it would take, where as running the Aussie 1.5.10 f/w it takes nearly the first loop! Once rooted of course can #flash_image recovery /sdcard/JRoddsRecoveryIsTheBest.img ).

(edit: the reason I was using Handlers was his nandroid restore option gave a menu for which directories to restore, which other recoveries have not in the past, only offering to restore more recent... but yours thankfully does!!)
Cheers, and thanks!

haha. i thought you were using it all along!