[Root][JB 4.2] Root your Nexus 7 without unlocking bootloader. (djrbliss motochopper)

Search This thread

GedBlake

Senior Member
Jan 5, 2013
889
604
Ashton-under-Lyne, Manchester, UK
Hi guys,

Thanx for the info.
I hadn't read those posts in xda but did read others enough to know I have some options.
I have been in and out of safe mode-didn't help.
I haven't gone to Recovery yet as I didn't want to wipe.
There looks like there may be a couple other things I didn't try, (fastboot and wipe cache) but not much hope.

Sorry if this is in the wrong thread but I just need to rant a second.
I did not steal my nexus.
I DID set a storage password.
I even set a second password to unlock the screen but I can't get to that.
My Nexus was fully charged, I use it every day, plug it in at night and unplug in a.m.

To hell with Google/Asus/Android- my warranty has been over for 2 months and they are not acknowledging the problem, indeed after the 4.3 update my Nexus started doing strange things also. I don't have the time to sit on the phone with tech support, I wish others luck who do:(

I can't believe I may have a "brick" after 14 months of use.
Think I got that tech word right.
Thanx for the 2 answers and I will update ya' if you want.

Jean

Hi, again jdny...

You should calm down a little... it's not good for the heart... apparently (I should talk! you should hear some of the language I come out with, when tech isn't DOING AS IT'S DAMN WELL TOLD:):) and far more colorful expletives that I dare not use on this forum:)).

Sometimes a good rant is good for the soul... but you should never let your emotions cloud your analytical faculties... particularly when dealing with computers. You a need clear, almost dispassionate head on your shoulders, no matter how annoying or intractable the problem appears to be.

First off, I certainly don't think you stole your Nexus 7. This encryption problem has been documented well enough, both here on XDA and on other forums, sufficiently such that it's a known issue.

Secondly, if you can access the bootloader, you're not hardbricked. You can fastboot flash back to factory stock. Relatively straightforward to do, but I understand your irritation at having to do it.

I guess this whole 'encrypt tablet' thing is still bug ridden and hasn't been thoroughly tested by Google, given the number of problems people seem to be having with it.

Anyway... try a factory reset first.. If that doesn't cure the problem, then fastboot flash back to factory stock. There's an excellent thread here on how to accomplish this.

Good luck.

Rgrds,
Ged.
 
  • Like
Reactions: derubm and jdny

derubm

New member
Oct 13, 2013
1
0
CMX Aquila / commax blade 70

I can confirm that rooting this Device worked like a charm with your Tool.
(needed root for disabling "Phone Device" as this tableet has no Phone module, and Android 4.1.1 was using loads of energy to find a network with a non existing Phone module.

Thanks a lot :)
 

nhshah7

Senior Member
Feb 14, 2009
2,069
568
Boston
I can confirm that rooting this Device worked like a charm with your Tool.
(needed root for disabling "Phone Device" as this tableet has no Phone module, and Android 4.1.1 was using loads of energy to find a network with a non existing Phone module.

Thanks a lot :)

I'm surprised you're still on 4.2. Most people already upgraded. Glad it worked though :).

Sent from my HTC One XL using Tapatalk 4
 

clandestino123

Senior Member
Dec 20, 2010
477
107
Brisbane
Since using this method on my nexus 7, I have been unable to update via OTA (error during install).

I am also unable to update via ADB as my device is not recognised. Tried everything I can think of re: driver updates, but nothing is working. Very frustrating.
 

nhshah7

Senior Member
Feb 14, 2009
2,069
568
Boston
Since using this method on my nexus 7, I have been unable to update via OTA (error during install).

I am also unable to update via ADB as my device is not recognised. Tried everything I can think of re: driver updates, but nothing is working. Very frustrating.

Did you change, move, or replace any system files?

Also try a different cable, different PC, different USB ports. For drivers, did you install the latest android SDK?

Sent from my Transformer Prime TF201 using Tapatalk 4
 

shashwatblack

Member
Jan 18, 2014
5
0
Failure to root on Nexus 7 2013 running kitkat 4.4.2

I get the following error message upon running the script run.bat (trying to root nexus 7 2013)

Code:
[*] Press enter to root your phone...
Press any key to continue . . .
[*]
[*] Waiting for device...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[*] Device found.
[*] Pushing exploit...
2596 KB/s (1283460 bytes in 0.482s)
[*] Pushing root tools...
2510 KB/s (91980 bytes in 0.035s)
2424 KB/s (1867568 bytes in 0.752s)
2335 KB/s (1966976 bytes in 0.822s)
        pkg: /data/local/tmp/Superuser.apk
Success
[*] Rooting phone...
[+] This may take a few minutes.
[COLOR="Red"][B][-] Failure.[/B][/COLOR]
[*] Cleaning up...
[*] Exploit complete. Press enter to reboot and exit.
Press any key to continue . . .

Is it because i'm running 4.4.2 and this was written a while back? In that case what files should I be using? Thanks
 

nhshah7

Senior Member
Feb 14, 2009
2,069
568
Boston
I get the following error message upon running the script run.bat (trying to root nexus 7 2013)

Code:
[*] Press enter to root your phone...
Press any key to continue . . .
[*]
[*] Waiting for device...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[*] Device found.
[*] Pushing exploit...
2596 KB/s (1283460 bytes in 0.482s)
[*] Pushing root tools...
2510 KB/s (91980 bytes in 0.035s)
2424 KB/s (1867568 bytes in 0.752s)
2335 KB/s (1966976 bytes in 0.822s)
        pkg: /data/local/tmp/Superuser.apk
Success
[*] Rooting phone...
[+] This may take a few minutes.
[COLOR="Red"][B][-] Failure.[/B][/COLOR]
[*] Cleaning up...
[*] Exploit complete. Press enter to reboot and exit.
Press any key to continue . . .

Is it because i'm running 4.4.2 and this was written a while back? In that case what files should I be using? Thanks

Does not work on 4.3 or above as Google patched the exploit this uses. Thus thread should be closed lol. The only way to root now is to unlock your boot loader and manually install root, etc.

Sent from my HTC One X using Tapatalk
 
  • Like
Reactions: shashwatblack

shashwatblack

Member
Jan 18, 2014
5
0
One more question

Does not work on 4.3 or above as Google patched the exploit this uses. Thus thread should be closed lol. The only way to root now is to unlock your boot loader and manually install root, etc.

Sent from my HTC One X using Tapatalk

Thank you for the info.
So basically I now have to unlock the bootloader (which will wipe my data), install twrp, then install root. Please correct me if i'm wrong.
I have just one more question, after root, will I still get OEM updates? (I don't plan to install other custom ROMs.)
 

adex9

Member
Jul 31, 2013
21
2
working on kit kat ?

hey, this may be a stupid question but i cant find any info on this root anywhere but this page, will this work on 4.4.2 kitkat? please dont say "it may work give it a shot" i need to know for sure. but yeah anyone tried this on kit kat ? keen to root this thing but not going through the whole bootloader unlocking nightmare
 

efrant

Senior Moderator / Developers Relations
Staff member
Feb 12, 2009
11,468
10,981
Montreal
hey, this may be a stupid question but i cant find any info on this root anywhere but this page, will this work on 4.4.2 kitkat? please dont say "it may work give it a shot" i need to know for sure. but yeah anyone tried this on kit kat ? keen to root this thing but not going through the whole bootloader unlocking nightmare
As AndDiSa mentioned, it won't work. This vulnerability has already been patch in KitKat.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 88
    Hi all,
    I just rooted a nexus 7 using the motochopper toolkit made by djrbliss. He gets full credit for the method, I just modified it to work for the N7 by updating the adb files within it (tested on Win7 64-bit, N7 wifi). Oh, and if something breaks, it's not my fault :)

    (original thread: http://www.droidrzr.com/index.php/t...id-root-exploit/page__pid__244281#entry244281)


    Here's what you'll need:

    Nexus 7 Drivers installed (try the universal naked drivers if you have issues with this. Search google if ADB/motochopper cannot see your device)
    (Android SDK is recommended if you need to troubleshoot the nexus connecting, but not necessary.)
    Developer options enabled, USB debugging enabled.
    The attached zip.

    Steps:
    1. Download and unzip the folder within the attached file.
    2. Make sure USB debugging is enabled. When you plug the tablet into the computer, the status bar of the tablet should say "USB debugging connected". If it doesn't, see below.
    3. WITH YOUR SCREEN TURNED ON, run the appropriate script from the motochopper folder. (Run.bat for windows, I think run.sh for Mac and Linux).
    4. You may be prompted by the tablet to approve a connection by the computer (RSA key, etc.). Accept this!
    5. If all is fine and dandy here, it will see your device and start to push files to it. When it tries to push the SuperSU.apk, your tablet will ask you to Approve something for tracking apk's/apps installed over ADB. Click yes or accept.
    6. The script (on your computer) should prompt you to reboot. Hit any key and you should be rooted when it starts up!
    Note: if your computer isn't able to see the device, try setting the device to PTP from MTP. This seems to work for some.


    Need to enable USB Debugging?
    1. Make sure you are in the main account.
    2. Go to settings, about, and scroll to the bottom.
    3. Tap on the "build number" entry 7 times.
    4. Exit out of the 'about' and go to Developer options.
    5. Check "USB debugging".

    Since I do NOT have a nexus 7 of my own, I can't fully support this but I'll do my best. I thought it would be great to share this with the nexus community for anyone (like me) that doesn't want to unlock their device in order to root. Like I mentioned before, all credit goes to djrbliss.

    Enjoy!

    Edit: some people are asking why this is useful. If you want root, unlocking the bootloader to gain root erases your device. This method does not.

    Edit 2: users report that it does not work on nexus 10 but does work on nexus 4.


    Indeed it would be amazing... and very useful... but as I've indicated in a previous post, 4.3 implements a new security model designed to protect itself from exploits (ostensibly of the malicious kind), so it's very unlikely this (motochopper) or any other exploit in the future will work.

    If you want root on 4.3, you're going to have to do it the old fashioned way...

    1) Unlock the bootloader with fastboot.
    2) Fastboot flash a Custom Recovery (CWM or TWRP).
    3) Using that recovery, flash Chainfire's modified SuperSU root updater.

    Rgrds,
    Ged.


    Update 3/2014. This method is outdated and no longer works for any current version of android (4.3+)
    6
    Thank you so much for your replies still run windows xp will that still be ok to root with please.

    Thank You
    :)

    As a lowly user, I'm the wrong one to ask. As a Windows admin, I've got a bit more experience. The tools used here on the Windows side look pretty basic to me. If you can find the right USB driver and establish communications, I can't see why XP wouldn't be just fine. The USB driver has been the thing that has tripped me and several other users up. Get the right one for the right device. Just because Windows sees your device doesn't mean the root process will work. There's some other API involved.

    ---------- Post added at 11:48 AM ---------- Previous post was at 11:08 AM ----------

    Now that I've hit my 10 post count legitimately and no one can complain, I wanted to re-share some sources for USB drivers. Myself and several other users have been bitten using nhshah7's awesome modification when it hangs, apparently unable to communicate with our Nexus 7. In every case the problem has been a bad USB driver.

    Myself and at least one other have solved this by installing PDANET+ which includes it's own USB drivers. Follow the instructions here:

    How To Install Drivers For Any Android Device

    And get PDANET here:

    http://junefabrics.com/android/downloadold.php

    But the drivers included didn't work for my older Galaxy Nexus. nhshah7 recommends using the USB drivers included in the full Android SDK. But if you hunt around, you can find lists of manufacturer USB drivers. A couple I found are:

    http://www.teamandroid.com/download-android-usb-drivers


    http://dottech.org/26188/usb-adb-and-fastboot-drivers-for-windows-for-all-android-phones/

    Hope this helps the next person to get a hung batch file.
    3
    Just had another tinker with this exploit...
    (I fastboot flashed back to stock, and relocked the bootloader beforehand).

    ...and I can confirm (again) that not only does it work... but you can reverse it really easily...

    ...by going to the app, SuperSU... and then SETTINGS>>FULL UNROOT.

    Upon reboot, the device is fully unrooted.

    --------

    And as with the normal method of ROOTING, you can also backup your root (SU binary) using Voodoo OTA Rootkeeper...

    http://play.google.com/store/apps/details?id=org.projectvoodoo.otarootkeeper&hl=en

    Upon (deliberate) loss of ROOT, I was able to restore ROOT, using this app.

    Further, and with relative ease, I was also able to change over from Chainfire's ROOT to Koush's (the CWM guy) ROOT...

    http://play.google.com/store/apps/details?id=com.koushikdutta.superuser&hl=en.

    -------

    I have thrown every ROOT app I can think of at it... and it just works.

    (And unrooting works, as described earlier.)

    And the beauty of it is... if you do loose ROOT (either by accident or design)... you can easily acquire it again, just by re-running the script.... and WITH NO LOSS OF DATA.

    -------

    Rooting doesn't get any easier than this...

    I 'tip my hat' in appreciation and respect... in the general direction of nhshah7 for making this exploit available.

    Rgrds,
    Ged.
    2
    I have rooted Nexus with this method (very easy, THANKS!), but the idea (at least for me) for rooting was to use an external SDCARD or pen disk with an OTG cable connected to Nexus 7.

    But this I can't do, I have used OI File Manager and Root Browser to explore pen disk but I can't see external SDCard with these apps.

    Can someone explain me what I am doing wrong? Thanks

    It could be a million and one things!
    Where are you looking for the external card? You know it's mounted under /sdcard yeah?
    Could be the cable you're using. Some don't work.
    Have you tried using StickMount?
    2
    Hello, I am having trouble with this on my Nexus 7. I get the following in CMD and it seems to just be on a loop of trying.

    [*] Pushing root tools...
    error: more than one device and emulator
    ...
    ...
    snip
    ...
    ...
    EDIT******* seems to be working now but oddly enough I just tried doing it with usb debugging disabled......yes with it off lol
    now it shows pushing exploit so stay tuned ill let you know how it goes.

    UPDATE:
    [*] Waiting for device...
    * daemon not running. starting it now on port 5037 *
    * daemon started successfully *
    [*] Device found.
    [*] Pushing exploit...
    576 KB/s (1283460 bytes in 2.175s)
    [*] Pushing root tools...
    402 KB/s (91980 bytes in 0.223s)
    483 KB/s (1867568 bytes in 3.770s)
    535 KB/s (969701 bytes in 1.770s)

    and im now left with a blinking cursor under that last line and waiting for something else to happen


    Are you sure you didn't start an emulator when you installed the Android SDK? You might be trying to root an emulator! (That might explain why you apparently saw things happening with ADB turned off).

    Anyway, you certainly should not be seeing messages such as this:

    error: more than one device and emulator

    manually running the command "adb devices" from a command window should show you only a single device listed - your N7.
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone