[JB ROOT] motochopper works! (Root JB 4.1.1 & 4.2.1 with locked bootloader!)

Morlok8k

Senior Member
Aug 28, 2012
140
265
0
Pacific Northwest
I did backup my root but I lost my superuser data after i rushed into something without reading and uninstalled super user because someone said they had success after uninstalling super user on their phone.and im afraid to do a factory reset because I have some apps frozen from before I lost root.


I am a n00b do I just open a command prompt and type those lines exactly? If I do that will i be able to just go to rootkeeper and restore?

If all you did was uninstall superuser, then:

install superuser or supersu form the market.

did it work?
yes: :)
no:
restore root using Voodoo OTA Rootkeeper

did it work?
yes: :)
no:
then get terminal emulator from the market, and follow the commands above

did it work?
yes: :)
no:
tell us which commands you used (exactly), and we will get back to you.
 

Bogart's Falcon

New member
Apr 27, 2011
3
3
0
I Need Some Help Please

First I need to let you know I have not rooted anything before. Now let me get to the questions.

I have a TF201 with Android 4.0.3. I have to assume that is the reason tapping 7 times on the build number doesn't work. Please tell me what I have to do.

My tablet is in a dock. Do I have to remove it before I root?

If there is anything else you feel I should know please post it here.

I want to thank all of you, in advance, for any help you give me.
 

sheep348

Senior Member
Sep 9, 2012
61
7
0
If all you did was uninstall superuser, then:

install superuser or supersu form the market.

did it work?
yes: :)
no:
restore root using Voodoo OTA Rootkeeper

did it work?
yes: :)
no:
then get terminal emulator from the market, and follow the commands above

did it work?
yes: :)
no:
tell us which commands you used (exactly), and we will get back to you.

cd /system/usr/we-need-root
./su-backup
mount -o rw,remount /system
cp su-backup /system/xbin/su

I followed the steps above and after the first line i got "permission denied"
after the second I got operation not permitted.
What can I try now? Thanks for your help and responding so quickly.
 
Last edited:

Morlok8k

Senior Member
Aug 28, 2012
140
265
0
Pacific Northwest
First I need to let you know I have not rooted anything before. Now let me get to the questions.

I have a TF201 with Android 4.0.3. I have to assume that is the reason tapping 7 times on the build number doesn't work. Please tell me what I have to do.

My tablet is in a dock. Do I have to remove it before I root?

If there is anything else you feel I should know please post it here.

I want to thank all of you, in advance, for any help you give me.
You have Ice Cream Sandwich.
This root method is made for Jelly Bean (android 4.1 and 4.2).

It might work with ICS - you can try it. but ICS has its own method for root.


the tapping 7 times is ONLY for JB 4.2. Your Developer Options menu isn't hidden, but you still need to enable USB debugging.

Using the dock doesn't matter. I rooted mine in the dock.
 
  • Like
Reactions: Bogart's Falcon

forivadel

New member
Apr 12, 2013
3
1
0
bummer, i'm getting the same daemon message as well. unfortunately, i have never unlocked bootloader or had root access. i'm on 4.1.1, any suggestions?
 

Morlok8k

Senior Member
Aug 28, 2012
140
265
0
Pacific Northwest
cd /system/usr/we-need-root
./su-backup
mount -o rw,remount /system
cp su-backup /system/xbin/su

I followed the steps above and after the first line i got "permission denied"
after the second I got operation not permitted.
ok. do this:

Code:
cd /system/xbin
ls -l su
(that last command is LS -L but in lowercase)

then tell us if su is listed, and what the line says (it looks something like: "-rwsr-sr-x root root 96260 2013-04-11 11:34 su")

then do this:
Code:
cd /system/usr
ls
is the "we-need-root" folder there?

if so, do this:
Code:
cd we-need-root
ls -l
and again tell what the line says.
 
  • Like
Reactions: krinkster

sheep348

Senior Member
Sep 9, 2012
61
7
0
ok. do this:

Code:
cd /system/xbin
ls -l su
(that last command is LS -L but in lowercase)

then tell us if su is listed, and what the line says (it looks something like: "-rwsr-sr-x root root 96260 2013-04-11 11:34 su")

then do this:
Code:
cd /system/usr
ls
is the "we-need-root" folder there?

if so, do this:
Code:
cd we-need-root
ls -l
and again tell what the line says.
I must not have had a good back up because it says no such file or directory. Does having a titanium backup of superuser and root keeper from before I lost root help?
 

forivadel

New member
Apr 12, 2013
3
1
0
what message? that it is outdated?

it should still work...
this is the message:
[*] Waiting for device...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *

doesn't do anything after that. i left at that point for more than 5 minutes several times. have tried rebooting both my computer and tablet. made sure i turned USB debugging on. ran the batch file as admin. i think i'll try with my laptop with xp. i'm on win 7.
 

sheep348

Senior Member
Sep 9, 2012
61
7
0
this is the message:
[*] Waiting for device...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *

doesn't do anything after that. i left at that point for more than 5 minutes several times. have tried rebooting both my computer and tablet. made sure i turned USB debugging on. ran the batch file as admin. i think i'll try with my laptop with xp. i'm on win 7.
Bump. I have the exact same problem except I dont have an xp computer to use.
 
Last edited:

forivadel

New member
Apr 12, 2013
3
1
0
Bump. I have the exact same problem except I dont have an xp computer to use.
Ok. So, i got this sh-t to work on my trusty ol' decrepit thinkpad t41 with xp. i had to install drivers for the tablet because it was not recognized. i suspect that was the issue on my win 7 machine, as i did not install any drivers and let win 7 install ones for MTP.
Couldn't get the drivers from ASUS (wouldn't display any OS to choose) but was able to find them on XDA. here: http://d-h.st/A9h
Source thread: http://forum.xda-developers.com/showthread.php?t=1697227
 
  • Like
Reactions: sheep348

CRACING

Inactive Recognized Developer
Jun 10, 2008
4,599
616
113
125 Miles From Sea
this is the message:
[*] Waiting for device...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *

doesn't do anything after that. i left at that point for more than 5 minutes several times. have tried rebooting both my computer and tablet. made sure i turned USB debugging on. ran the batch file as admin. i think i'll try with my laptop with xp. i'm on win 7.
Looks like ADB couldn't connect to or find your tablet. Make sure you have the correct drivers installed. I had asus sync already installed. Also make sure adb isn't running in the background. Force close the adb if its running already in the taskmanager and start the rooting process again.
 

sheep348

Senior Member
Sep 9, 2012
61
7
0
I got the root to run and say it was successful but it still did not work. I know I am almost there!

The exploit seems to be failing because I was previously rooted had had superuser installed. Is there a way to uninstall superuser? see the attached photo to better understand.
 
Last edited:

buhohitr

Senior Member
Nov 30, 2011
5,968
1,817
0
I got the root to run and say it was successful but it still did not work. I know I am almost there!

The exploit seems to be failing because I was previously rooted had had superuser installed. Is there a way to uninstall superuser? see the attached photo to better understand.
Open the superuser app and there is an option to remove root.

Sent from my ASUS Transformer Pad TF700T using xda premium
 
Aug 26, 2009
13
1
0
Woodstock
I have a tf300t with Android 4.2.1 and a locked bottloader. The motochopper rooted my tablet in seconds and my supersu and busybox appear to be operating properly. My problem is getting a recovery to install. Every other time I rooted a device there was always a recovery installed. Do I need to unlock the bootloader to install one, or use fastboot or what? I'm also having a hard time locating the proper version for the tablet. Is there a version of TWRP or CWM that works without crashing the tablet, and if so what is the best way to install it? Sorry for all the questions, I'm new to tablets, though I've never had a problem rooting any of my phones. Thanks in advance to anyone who can help.
 

l33ch0r

Senior Member
Apr 12, 2011
1,242
249
0
I have a tf300t with Android 4.2.1 and a locked bottloader. The motochopper rooted my tablet in seconds and my supersu and busybox appear to be operating properly. My problem is getting a recovery to install. Every other time I rooted a device there was always a recovery installed. Do I need to unlock the bootloader to install one, or use fastboot or what? I'm also having a hard time locating the proper version for the tablet. Is there a version of TWRP or CWM that works without crashing the tablet, and if so what is the best way to install it? Sorry for all the questions, I'm new to tablets, though I've never had a problem rooting any of my phones. Thanks in advance to anyone who can help.
In the section "general" pretty much at top is a thread that says something about "not flashing 4.1 recovery on 4.2 tablet". So I guess there it is said which recovery to flash.
As far as I know you have to unlock your device to flash a recovery. Which means if you planned to flash a recovery and a custom rom as well you wouldn't have needed to use motochopper :D
But anyways there are few guides on how to do it ;)
 
  • Like
Reactions: thursdayschild

Morlok8k

Senior Member
Aug 28, 2012
140
265
0
Pacific Northwest
I must not have had a good back up because it says no such file or directory. Does having a titanium backup of superuser and root keeper from before I lost root help?
no. titanium backs up the APP, not the BINARY.

this is the message:
[*] Waiting for device...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *

doesn't do anything after that. i left at that point for more than 5 minutes several times. have tried rebooting both my computer and tablet. made sure i turned USB debugging on. ran the batch file as admin. i think i'll try with my laptop with xp. i'm on win 7.
fix my problme need to run it as a "Run as Admin"
I use linux myself. If the "run as admin" doesnt work, get a linux live cd.

(or just ditch windows entirely, lol...)


I got the root to run and say it was successful but it still did not work. I know I am almost there!

The exploit seems to be failing because I was previously rooted had had superuser installed. Is there a way to uninstall superuser? see the attached photo to better understand.
Open the superuser app and there is an option to remove root.
Do you mean "temp unroot" ? Because super user crashes when I select it.
Sheep, are you using "Superuser" (the green android with the eyepatch), "Superuser" (a white # on a blue background), or "SuperSU" (a yellow sheild with a red #)?

Cause it sounds like the first one. and that one has issues with Jellybean 4.2. Thats why everyone is using SuperSU now.

did you try this: http://matthill.eu/mobile/root-transformer-prime-jellybean-update/ ?

So, SuperSU (install it from the market, if not already on the tablet) has a ton of options like "Full Unroot", "Switch superuser app", "Reinstall"...
Maybe you can try one of those...



I have a tf300t with Android 4.2.1 and a locked bottloader. The motochopper rooted my tablet in seconds and my supersu and busybox appear to be operating properly. My problem is getting a recovery to install. Every other time I rooted a device there was always a recovery installed. Do I need to unlock the bootloader to install one, or use fastboot or what? I'm also having a hard time locating the proper version for the tablet. Is there a version of TWRP or CWM that works without crashing the tablet, and if so what is the best way to install it? Sorry for all the questions, I'm new to tablets, though I've never had a problem rooting any of my phones. Thanks in advance to anyone who can help.
So far no luck with installing recovery. I tried myself, but the normal ways of installing the recovery dont work with the bootloader locked.
So, currently your only option for recovery is unlocking the bootloader.

anyways, the guy above explained it pretty well.