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

Search This thread

Maxr1998

Recognized Developer
Apr 15, 2013
2,148
3,209
22
Augsburg
maxr1998.de
my nexus 7 3g got OTA update.....after downloading the device restarted..... while installing it showed me Error.....am still on 4.2.2........pls help me....is this because I didn't unroot the device.....if so help me to do so

I think you just changed something in the system (or an app) and now Google won't allow this...the problem is it's not easy to restore the system...either you stay on 4.2.2 or you restore original system via fastboot, therefore you have to unlock the bootloader and then you can flash 4.3 with fastboot and you're done, you can then root this with the original method...

P.S.: unrooting won't help, sorry...

Sent from my Nexus 7 using Tapatalk 4 beta
 

itsirfandude

Senior Member
Oct 2, 2012
71
2
28
Coimbatore
Nexus 7
Google Pixel 2
I think you just changed something in the system (or an app) and now Google won't allow this...the problem is it's not easy to restore the system...either you stay on 4.2.2 or you restore original system via fastboot, therefore you have to unlock the bootloader and then you can flash 4.3 with fastboot and you're done, you can then root this with the original method...

P.S.: unrooting won't help, sorry...

Sent from my Nexus 7 using Tapatalk 4 beta

I didn't change anything......still can u pls elaborate on how to unroot.....won't I get ota update again.....will the already downloaded data for 4.3 update be present in the device
 

Maxr1998

Recognized Developer
Apr 15, 2013
2,148
3,209
22
Augsburg
maxr1998.de
I didn't change anything......still can u pls elaborate on how to unroot.....won't I get ota update again.....will the already downloaded data for 4.3 update be present in the device

I think any root app changed asomething...before updating, google checks if all system files are original and available, if, it blocks the update...unrooting can be done in the options of SuperSu, but i think it won't help, sorry :(

Sent from my Nexus 7 using Tapatalk 4 beta
 

nhshah7

Senior Member
Feb 14, 2009
2,069
568
Boston
Usually rooting alone will NOT affect ability to take and install an ota update. You should be able to do a factory reset and update that way. Worst case you take the original system file, and at least on other Asus tablets, place the file on your sdcard and you can reinstall it. Ask in q and a and you could probably get more detailed help. I don't think you need to unlock but you'll probably need to wipe your data one way or another. Also see if you an find an update log to see what went wrong. This is usually found somewhere through a file explorer.

Sent from my One X using Tapatalk HD
 

cevad

Member
Apr 7, 2012
8
0
Perth, WA
Usually rooting alone will NOT affect ability to take and install an ota update.

I can confirm that this is correct, I rooted 4.2.2 using this method and successfully updated to 4.3 OTA just over 1/2hr ago with no apparent issues.

It did not keep root (which is what I was expecting), but hopefully someone will have this sorted at some point - I would like to root again without unlocking my bootloader :)
 

nhshah7

Senior Member
Feb 14, 2009
2,069
568
Boston
I can confirm that this is correct, I rooted 4.2.2 using this method and successfully updated to 4.3 OTA just over 1/2hr ago with no apparent issues.

It did not keep root (which is what I was expecting), but hopefully someone will have this sorted at some point - I would like to root again without unlocking my bootloader :)

Did you try voodoo ota root keeper?

Sent from my One X using Tapatalk HD
 

clandestino123

Senior Member
Dec 20, 2010
477
107
Brisbane
I can confirm that this is correct, I rooted 4.2.2 using this method and successfully updated to 4.3 OTA just over 1/2hr ago with no apparent issues.

It did not keep root (which is what I was expecting), but hopefully someone will have this sorted at some point - I would like to root again without unlocking my bootloader :)

Just read your post. I also rooted 4.2.2 using the method described in this thread, three or four days ago. After rooting, I installed ad-aware.

I just tried to install the OTA update, but received an "error" message during install. I have just rebooted and I'm still on 4.2.2.

I've just tried disabling ad-aware. I want to attempt OTA again, how do I do that? any ideas?
 

Corvidd

Senior Member
Jun 28, 2010
93
23
Just read your post. I also rooted 4.2.2 using the method described in this thread, three or four days ago. After rooting, I installed ad-aware.

I just tried to install the OTA update, but received an "error" message during install. I have just rebooted and I'm still on 4.2.2.

I've just tried disabling ad-aware. I want to attempt OTA again, how do I do that? any ideas?
Have you tried just going into Settings and checking for a system update there? Or type *#*#checkin#*#* into the dialer, see if either of those work for you.

Failing that, the update is easily available as a .zip, and installing it via adb is quite easy. I too only rooted for the first time a couple of days before 4.3 came along, and I was able to install 4.3 via adb quite easily. Let me know if you are doing this and I'll post the guide I used.
 
  • Like
Reactions: clandestino123

nhshah7

Senior Member
Feb 14, 2009
2,069
568
Boston
Just curious, is anyone working on fixing this root method, or is it completely a lost cause?

Fixing it for 4.3? Ask djrbliss lol

I think the appropriate question is, is anyone working on a root exploit for 4.3. I'm sure someone or some people are but you won't hear about it until it is achieved. Might take longer also because Google has patched up many of the holes with 4.3 and had a focus on security with this update.

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

Crazymmc

Member
Feb 4, 2013
14
0
Just read your post. I also rooted 4.2.2 using the method described in this thread, three or four days ago. After rooting, I installed ad-aware.

I just tried to install the OTA update, but received an "error" message during install. I have just rebooted and I'm still on 4.2.2.

I've just tried disabling ad-aware. I want to attempt OTA again, how do I do that? any ideas?

It has happened the same to me.
I got the message to update 4.3, when i accepted, n7 rebooted and... Error.
I booted again and still be 4.2.2.

Sent from Sony Xperia using Tapatalk.
 

Uzuki

Member
Jul 23, 2009
48
7
I rooted my N7 using this method, when i received OTA update, i just rebooted my N7 and now it's 4.3, no error. The root access is gone though
 

ilanad

Senior Member
Jun 28, 2008
115
4
Just a note here, I was having the OTA failure also, only rooted with this method. Did a factory wipe. Same problem. Then I remembered I had installed the AOSP Browser root app and had not uninstalled it. Wipe, reboot with this method, reloaded AOSP browser then uninstalled, uprooted, wipe, took the OTA without error.

Sent from my Nexus 7 using Tapatalk 4 Beta
 
  • Like
Reactions: clandestino123

AndDiSa

Senior Member
Dec 2, 2009
3,477
4,559
Heidelberg
No, but as soon as a system file or the kernel is modified / replaced / ... you will get problems with the OTA.

Sent from my Nexus 7 using xda app-developers app
 

dcatalyst

New member
Aug 4, 2013
3
0
Best way to root 4.3?

Fixing it for 4.3? Ask djrbliss lol

I think the appropriate question is, is anyone working on a root exploit for 4.3. I'm sure someone or some people are but you won't hear about it until it is achieved. Might take longer also because Google has patched up many of the holes with 4.3 and had a focus on security with this update.

Sent from my HTC One X using Tapatalk HD

I am in training for a tech support job that will require me to have root access for certain commands. In my effort to remain mobile, I was hoping to use my (1st gen) Nexus 7 for much of this work. Sadly, I didn't start trying to root my device until the day after it it updated OTA to 4.3. I love the idea of preserving the locked bootloader but still achieving root. However, given the enhanced security of 4.3 and the fact that I only have a couple of weeks before I am likely to need root, I have a choice: Give up on the Nexus 7 as a rooted Linux device for now and just use my laptop running Ubuntu, or find another way to achieve root on a device that has not previously been rooted.

Question: Is there a known way for me to achieve root on 4.3? If not, is there a simple way to revert back to 4.22 without losing my data and installed apps?
 

nhshah7

Senior Member
Feb 14, 2009
2,069
568
Boston
I am in training for a tech support job that will require me to have root access for certain commands. In my effort to remain mobile, I was hoping to use my (1st gen) Nexus 7 for much of this work. Sadly, I didn't start trying to root my device until the day after it it updated OTA to 4.3. I love the idea of preserving the locked bootloader but still achieving root. However, given the enhanced security of 4.3 and the fact that I only have a couple of weeks before I am likely to need root, I have a choice: Give up on the Nexus 7 as a rooted Linux device for now and just use my laptop running Ubuntu, or find another way to achieve root on a device that has not previously been rooted.

Question: Is there a known way for me to achieve root on 4.3? If not, is there a simple way to revert back to 4.22 without losing my data and installed apps?

No and no unfortunately. Why not just unlock your bootloader to get root?

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

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