NRT rooting issues with MRA58K

anon(301129)

Well-known member
May 1, 2011
172
2
0
Has anybody else had issues with rooting the N7 running on MRA58K using Wugfresh NRT?
Mine goes all the way through to the Teamwin Recovery, then when it tells me to browse to the Beta SU and install it, the files do not show.
I know the files are there as I can see them in explorer.

Something interesting happens when I reboot my device; it always goes back to Connected as USB Charging only, even though I have set it to MTP in Developer Options. This might be what is causing it?
 
Looks like maybe there is no modified boot image available for this device yet. I guess I will wait and see. I have tried all I know and some I didn't know.
 
...no modified boot image available for this device...
There are two methods I've seen to root the 2013 N7 under MRA58K. The one using the modified kernel (ElementalX) did not work for me.
Chainfire did, in fact, make a modified boot image for the N7, and it worked fine. It's easy to find.

To root:
- Use NRT to flash stock and un-root. You can 'No Wipe' if you want.
- Put the SuperSU binary on your device somewhere you can find it later (2.52, as of this writing).
- Use fastboot to install the modified boot image.
- Use fastboot to install the proper TWRP recovery.
- Boot to Recovery Mode and install SuperSU.
- Reboot to System.
Done :)

For some reason, installing TWRP before sending the modified boot image didn't work (to root). It only worked when I installed TWRP afterward.
 
I used wugfresh.

You can use WugFresh' NRT to root, I just saw ... It's not how I did it, but the NRT website says its latest version is able to recognize that it needs the modified kernel for Marshmallow rooting and install it for you, then uses Chainfire's SuperSU Beta 2.52 to root.

These guys are wonderful....
 
Last edited:
You can use WugFresh' NRT to root, I just saw ... It's not how I did it, but the NRT website says its latest version is able to recognize that it needs the modified kernel for Marshmallow rooting and install it for you, then uses Chainfire's SuperSU Beta 2.52 to root.

These guys are wonderful....

This worked just fine on my N5 but not on the N7. When I run it on the N7 it prompts me to install SuperSU when it runs the Team Win recovery however it will not browse the drive on the N7 and I get error messages saying it can not mount the sdcard partition. A strange clue is maybe that I can not make the N7 automatically stay on USB/MTP or USB/camera. It always defaults back to USB/Charging. It seems there is some security issue getting in the way. My N5 is just fine and works just like it supposed to.
Anybody have ideas on that?
 
... it will not browse the drive on the N7 and I get error messages saying it can not mount the sdcard partition...
I don't have a clue, but maybe head over to XDA-Developers and look for this thread:
<< **UPDATE** Mounting Errors in Custom Recovery >>
People seem to have some success fixing this problem using TWRP's multirom recovery.

Oh, yeah - MRA58V is up for the N7, both WiFi and Mobile.
 
This worked just fine on my N5 but not on the N7. When I run it on the N7 it prompts me to install SuperSU when it runs the Team Win recovery however it will not browse the drive on the N7 and I get error messages saying it can not mount the sdcard partition. A strange clue is maybe that I can not make the N7 automatically stay on USB/MTP or USB/camera. It always defaults back to USB/Charging. It seems there is some security issue getting in the way. My N5 is just fine and works just like it supposed to.
Anybody have ideas on that?

I’m having the same problem as everyone else. I’m using 6.0.1 MMB29K. It goes through the motions but when TWRP launches the /sdcard directory is empty. However, when I reboot and look at the files using an app called File Manager, I see them in /storage/emulated/0/!ReadyToFlash/Root_Files/. However, if I use a app called Root Browser I see a directory called sdcard and in there is !ReadyToFlash/Root_Files/ so they are being copied to the tablet but when you go into TWRP to install them they can’t be found. I tried to use the app Root Browser and make a directory called kiledl, this failed, probably because I do not have root access. Kind of a catch 22 here. I was just going to copy the files in sdcard to my directory and then try again. NO go!!! Anyone else have any ideas? It seems like this is some sort of permissions issue with the files but only from TWRP. I sure hope someone comes up with an answer. If you find an answer please post the resolve here. One last note I have managed to use this same process on both the Nexus N5 and the Nexus 6P with no problems.
 
Found a solution the version of TWRP that WugFresh NRT is using is not compatible with this version of the N7 seems as though these were made with a different MMC memory. Check you this link and download this modified version of TWRP. You can use the NRT Advance Utilities > fastboot flash > recovery > other and then point to this modified version of TWRP and install it. Then you can proceed with the install of SuperSU and BusyBox. They will show up in the !ReadyToFlash/Root_Files/ folder to install.

Check this link **UPDATE** Mounting Errors in Custom Recovery

**UPDATE** Mounting Errors in Custom Recover… | Nexus 7 (2013)
 

Forum statistics

Threads
955,135
Messages
6,963,866
Members
3,163,206
Latest member
ZOMBIE