yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Android Development] kindofabuzz:
Question of the day, will this work with Marshmallow?
[Nexus 7 (2013) Android Development] madbat99:
Why wouldn't it? It has worked since jellybean, up through KitKat and lollipop so...
[Nexus 7 (2013) Android Development] gotshores:
i was able to. Just downloaded the 6.0 files from google's factory image site for my device, and then pointed the toolkit to use those instead of the standard ones that are listed. It flashed it just fine. Haven't tried rooting yet though because of the Red Notice on wug's page that rooting is not supported via the tool. I can wait for the goods. Thx Wug
[Nexus 7 (2013) Android Development] paztine:
THANKS...

THANKS again dev for this wonderful piece of your creation it never fail my NEXUS devices running the latest and greatest M 6.0 official build. Will stay stock for now. Good luck guys/gal
[Nexus 7 (2013) Android Development] idCyber:
Flashing elementalx 5.00 in twrp makes the device boot and root work ofc after flashing supersu and busybox
[Nexus 7 (2013) Android Development] Spudsicles:
Well just rooted my tablet... and now it's stuck on a boot loop. I tried rebooting into recovery and wiped both cache files, but it's still stuck... what should I reflash?
[Nexus 7 (2013) Android Development] k3lcior:
If you are on Android 6.0 you need custom kernel for root to work. (like ElementalX 5.0)

Otherwise you'll end up in bootloop.
[Nexus 7 (2013) Android Development] Spudsicles:
Is this something new to Android 6.0?... seems rather stupid.
[Nexus 7 (2013) Android Development] k3lcior:
Yes kinda, if you dont want ElementalX you can use modified Stock kernel from here:

http://xdaforums.com/showpost.php?p=63158038&postcount=210
[Nexus 7 (2013) Android Development] kindofabuzz:
So EX can be installed without root first?
[Nexus 7 (2013) Android Development] mdamaged:
Of course, using twrp.
[Nexus 7 (2013) Android Development] goinovr:
Same issue after root. I just ran the Flash Stock+Unroot (soft bricked) and used the 6.0 files and was back up an running in a couple minutes. Also used the No User wipe.
[Nexus 7 (2013) Android Development] mdamaged:
FWIW, Chainfire released modified boot images which allow root to be taken without the use of a 3rd party nonstock kernel.

Associated links:

http://xdaforums.com/apps/supersu/wip-android-6-0-marshmellow-t3219344

http://xdaforums.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
[Nexus 7 (2013) Android Development] mrdunn:
Wug's now has 6.0 MRA58K as an option. First try bootlooped, not rooted. Work quickly on second try.
[Nexus 7 (2013) Android Development] fendee1:
Just a FYI I was on 4.4.4 wiped system, installed 6.0 its listed, flashed, like above it works. Make sure on the tablet its unlocked. Didn't know if you you had to be on a older version but it works. I'm sure soon twrp will be included.
[Nexus 7 (2013) Android Development] mrdunn:
Ahh! That is why I bootlooped the first flash with Wug's, I unlocked it the second time and it worked. Thanks.
[Nexus 7 (2013) Android Development] sLpFhaWK:
Hi guys I'm trying to root my nexus 7 2013 lte version but wugs isn't working. It's saying it pushes the files over but i never see any progress bar or anything like I thought I saw before on other tablets. It's running official 5.1.1 and i can't even install recovery so I am at a total loss right now =(

Edit: NEvermind I forgot you have to use a USB port on the back of the computer for it to work right, I was using a USB extension that I use when I'm lazy. Its working now.
[Nexus 7 (2013) Android Development] el56:
Hi all.

Been using phones and ROMS for years but haven't see this before.

I was able to use NRT to install Marshmallow on my tablet, seems to work without problems.

Then I went to root it.

The NRT rooting process involves booting into TWRP and then installing some zip files from /sdcard/!ReadyToFlash/

However, TWRP it shows /sdcard as empty.

Looks like TWRP cannot mount most of the directories, when I reboot it even warns about no OS present.

Under a normal boot I can see the files fine.

I have tried re-installing TWRP from with NRT with no change.

Any suggestions?
[Nexus 7 (2013) Android Development] madbat99:
Root on marshmallow is a little complex right now. Wugs toolkit can't do it yet. Twrp can't read encrypted storage right now, so to see files you need to format data.

To root you need SuperSU beta 2.51 and chainfire's modified stock kernel. Instructions here

Sent from my Nexus 9
[Nexus 7 (2013) Android Development] brenty108:
Hi. Your website is apparently down right now. Great work on this amazing program BTW
[Nexus 7 (2013) Android Development] Spudsicles:
Any word on the root for 6.0.0 (MRA58U)? :good:
[Nexus 7 (2013) Android Development] BanziBaby:
+1 for this. Chainfire has released the modified boot img for this build so hopefully wug will add it soon :)
[Nexus 7 (2013) Android Development] mrdunn:
After unchecking both MTP and camera options, finally was able to get WUG to recognize my drivers, and unlock and root just fine. But no option has allowed me to have my win7 recognize the Nexus 7 except in camera mode. With MTP on or off, debug on or off, etc. Would flashing a custom ROM help, or is there something else I need to do. I see others have this problem, but the solutions I have seen so far haven't work for me. However, USB OTG Helper app does allow me to download to the Nexus 7. Hooray this finally worked: http://xdaforums.com/showpost.php?p=32728485&postcount=1
[Nexus 7 (2013) Android Development] maximus20895:
Don't know how to delete a post...
[Nexus 7 (2013) Android Development] wokka00:
Disabling MTP was key. I never had that issue with the original Nexus 7 or VZW Galaxy Nexus, but based on some more searching, apparently that's now a thing with ADB. Until I disabled MTP, adb commands wouldn't work. Bootloader/fastboot commands would go through, but ADB-based scripts failed.

Perhaps it would be a good idea to include a reminder in the pop-up to disable MTP/PTP?
[Nexus 7 (2013) Android Development] WugFresh:
Yeah, that info is already scripted in the soon to be released v1.7.0. I never had that issue myself so I didn't know about it. Adb has always worked for me with mtp enabled as well. Glad you got it resolved. :)

{{ WugFresh }}
[Nexus 7 (2013) Android Development] BFirebird101:
Your website seems to be down

Sent from my AOSP'd Droid DNA

ROM: Pio's PAC-Man HALO 7.13.13

Kernel: CRPalmer 3.0.2: Interactive, deadline
[Nexus 7 (2013) Android Development] WugFresh:
Yeah, the host admins are trying to resolve it now. I am very sorry for the downtime. Here is a mirror to the file: http://d-h.st/F7N

Thank you for notifying me. Hopefully this will get resolved quickly.

{{ WugFresh }}
[Nexus 7 (2013) Android Development] BFirebird101:
Should I just wait for 1.7?

Sent from my AOSP'd Droid DNA

ROM: Pio's PAC-Man HALO 7.13.13

Kernel: CRPalmer 3.0.2: Interactive, deadline
[Nexus 7 (2013) Android Development] Gunthermic:
Everytime I go to update 1.6.8and tell it I am on JWR66V it wants to get an update and downoads 1% and says complete...

I cant seem to get the stock r66V img so i can root this puppy...
[Nexus 7 (2013) Android Development] quickstang:
Looks like 1.7.0 is up on Wugs website. From his site....

News:

v.1.7.0 is released!

Code fixes and optimizations.

Updated changelog coming shortly.

Enjoy! ^_^
[Nexus 7 (2013) Android Development] vicw:
Same for me. I've been through a very rough couple of days, including a very scary boot loop in my new N7 (2013) in the mix, due to this problem, but the procedure that Tech posted which you you linked, worked beautifully for me. It's interesting that his post was made way back in October 2012, but it's really relevant today. I can now get MTP to work, and ADB is now working, as long as I disable MTP in Settings/Storage/Menu(USB Storage Connnection).

I also just encountered the update to 1.7.0, which failed to complete on the first pass, but did work on the second attempt.
[Nexus 7 (2013) Android Development] quickstang:
I'm about to that point. This is really ticking me off. I don't blame the program at all, but i'm on like my 8th computer reboot after installing & uninstalling & what not. Went through Driver 1, 2, 3, & now on RAW. It shows up as ADB, when I did the PDAnet drivers it showed as Nexus 7, & then Original Android ADB when I did the 3rd one. Every time I clicked the test the drivers deal, ADB wasn't found. Has yet to find it & I have yet to get a green light saying everything is installed correctly. Using a Win 7 computer, & I have MTP unchecked as well.

Now i'll spend another 30min going through Driver 4 to see if that works. If not, i'm not sure what to do besides resorting to another method.
[Nexus 7 (2013) Android Development] WugFresh:
Since you actually tried everything to no avail I would be willing to help you next time I am free. Send me a hangout request on Google+, or email me an im.

{{ WugFresh }}
[Nexus 7 (2013) Android Development] quickstang:
Thanks for the help man. I actually got the RAW drivers to work. One thing I did get hung up on was the bootloader deal. I found out once I turned the tablet on it had the RSA key popped up on the screen, clicked it, got it in to bootloader mode, then unlocked & now rooted.

The only question however for anyone...

Wasn't it mentioned NOT to install TWRP when it asks, but to click cancel then boot, THEN go back & install TWRP after the device has actually booted?

EDIT: Well, The unlocked portion worked, but when I went to unroot it, it did its thing, downloaded what it needed to, then booted in to fastboot, said waiting for device... Timed out 2x, so I powered it off, and now it won't come back on. I can't even get the device to power using the Volume keys along with the power keys, so I wonder if I just hosed my Nexus? :(

Edit:2 It's not hosed. I had to plug it in the wall charger then it kicked on. For some reason even though the battery is 100%, it wouldn't power no matter what until plugged in to an AC source.
[Nexus 7 (2013) Android Development] Gareee:
I see that announcement, but the link takes you to 1.6.8
[Nexus 7 (2013) Android Development] quickstang:
Just go to the website & you'll see the file. I downloaded with no issues. Hit the blue 1.7.0 box, scroll down to where it says download & you'll see the file.
[Nexus 7 (2013) Android Development] jakis39:
Hello,

I'm using this toolkit now, and I've run into a snag. I unlocked the tablet fine, but now when I click the root button, it reboots it into fastboot mode, then the program says "Waiting for your device...", and nothing happens.

Eventually the toolkit times out, and the tablet seems frozen in fastboot mode. I can only get out by holding the power button for a long time. Then I can boot back into Android, but the same thing happens every time I try to root.

Has anyone come across this? Any advice?

Thanks
[Nexus 7 (2013) Android Development] thor6577:
I'm also having this error. Any help with this? :(
[Nexus 7 (2013) Android Development] airicd22:
Yes, I am having that problem too. Ihave restarted the tablet when this happens and it appears to take the nexus to the next steps and finishes but root is not achieved.
[Nexus 7 (2013) Android Development] quickstang:
So for the two of you above, I had the same issue. Spent about an hour to no avail.

Decided to try the cmd stuff, same thing. Waiting for device...

Finally came across a fix.

http://xdaforums.com/showthread.php?p=44678265

[TUTO+VIDEO] AIO Unlock Bootloader-Flash Recovery (TWRP)-Root-Restore Back the N7 FLO

You need to download the platform tools from the first post, extract them to an area. Easiest for me was to use the default directory that shows up when you type cmd.

Following what was mentioned in the above thread allowed me to finally flash twrp then boot to twrp & install the SU zip & root.

Sent from my iphone killing Galaxy Nexus running ASKP kernel & AOKFP ROM. For the love of everyone on forums READ BEFORE YOU POST.
[Nexus 7 (2013) Android Development] airicd22:
I can even boot into recovery and twrp will ask to root device but it doesn't work. Question, Should secure boot be enabled?
[Nexus 7 (2013) Android Development] ksfno1:
I wonder when @WugFresh will add MRA58U and MRA58V along with root options :confused:
[Nexus 7 (2013) Android Development] efix_LT:
how to root latest MRA58V, link?
[Nexus 7 (2013) Android Development] dark0shark:
Would love to install OTA Update Nexus 7 2013 (Wi-Fi) MRA58V from MRA58U - Download at http://www.droidsec.org/news/2015/11/02/nexus-update-november-2015.html - , but Wug's Nexus Root Toolkit doesn't seem to be prepared for this yet. Anyway: Great tool!
[Nexus 7 (2013) Android Development] efix_LT:
Toolkit updated to v2.0.6 and now support MRA58U, but still missing latest MRA58V
[Nexus 7 (2013) Android Development] Spudsicles:
It seems that the new v2.0.6 update now shows that my bootloader is LOCKED... when it's clearly UNLOCKED. Now I can't flash anything... :crying:

Anyone else have this problem?
[Nexus 7 (2013) Android Development] rulla:
Temporary solution for MRA58V until next NRT fix arrives, via manual way:

flash-all script with no wipe mode,

install latest TWRP via adb,

from TWRP: install ElementalX-N7-5.04 and BETA-SuperSU-v2.52,

Reboot, check root and enjoy.
[Nexus 7 (2013) Android Development] willows:
I have same problem
[Nexus 7 (2013) Android Development] dark0shark:
Hi

WugFresh, thanks a lot for v2.0.6, it works great with that latest OTA Update:

Nexus Root Toolkit v2.0.6

Masterlists:

- LatestToolkitFiles.ini 3085

- AndroidDeviceListFull.ini 3085

- AndroidDeviceListFlash.ini 3085

RAZOR-FLO: Android 6.0.0 - Build: MRA58U

Live log initiated [2015-11-09]:

Checking ADB/FASTBOOT Connectivity

adb devices

0a36**** device

fastboot devices

Connectivity Status: ADB Device Connected

Rebooting your device into recovery mode...

adb reboot recovery

Checking ADB Sideload Connectivity

adb devices

0a36**** sideload

Connectivity Status: ADB Sideload Device Connected

Initiating Sideload of '4c6989a4542d37e23a121bf370bd748aa37df692.signed-razor-MRA58V-from-MRA58U.zip'; Please be patient...

adb sideload "4c6989a4542d37e23a121bf370bd748aa37df692.signed-razor-MRA58V-from-MRA58U.zip"

loading: ...
[Nexus 7 (2013) Android Development] Blackdragon77:
With 2.0.6 program says that my nexus 7 have a locked bootloader, even if it isn't
[Nexus 7 (2013) Android Development] _jis_:
Yes, it is a known problem, try to read a few last posts.
[Nexus 7 (2013) Android Development] daraldf:
Same here
[Nexus 7 (2013) Android Development] ddskier:
Since 2.0.6 is broken on the 7, does anyone know where I can grab 2.0.5?

Sent using Tapatalk 4
[Nexus 7 (2013) Android Development] Blackdragon77:
https://www.androidfilehost.com/?fid=95916177934547093
[Nexus 7 (2013) Android Development] jamesc760:
2.0.6 is broken, not just on the 7 but on ALL Nexus models. Learn to use native android commands like adb, fastboot, etc.. There's a thread somewhere on the xda. Search for it. Do not rely on a toolkit like the NRT, these tools usually don't work very well, 2.0.6 is a prime example of a tool/utility that doesn't work. Just because the previous version worked doesn't mean the newest and latest is the best. In fact, the newest and the greatest is a marketing ploy designed to separate you from your money/time/effort. Better to learn the commands and be done with these stupid toolkits.
[Nexus 7 (2013) Android Development] tamanaco:
I was about to flash MRA58U on my Nexus 7 with the 2.0.6 toolkit, but this image is no longer listed. I'm sure I saw it there a couple days ago.

EDIT: NEVER MIND - I selected the wrong N7... I needed to select the N7 (2013)

EDIT2: As others have reported, with 2.0.6 the bootloader of my N7 (2013) shows as locked, but it's actually unlocked.
[Nexus 7 (2013) Android Development] kschang:
I think the 2.06 flashing update problem may be a ROM bug returning the wrong bootloader lock state. I started a new topic on it.

http://xdaforums.com/nexus-7-2013/nexus-7-2013-qa/technical-fastboot-returns-wrong-t3250418
[Nexus 7 (2013) Android Development] Emalasto:
So since 2.06 isn't working for the latest update, whats the best alternative to root?
[Nexus 7 (2013) Android Development] _jis_:
You should use manual method: http://xdaforums.com/showthread.php?p=63727509
[Nexus 7 (2013) Android Development] Emalasto:
I followed another guide that didn't involve the flash-all script and it worked just fine. Whats that script do?

I pushed TWRP using adb, I flashed a modified kernel and su 2.52.
[Nexus 7 (2013) Android Development] _jis_:
Modified flash-all.bat script from original factory image *.tgz with no wipe mode for your user data:

@ECHO OFF
:: Copyright 2012 The Android Open Source Project
::
:: Licensed under the Apache License, Version 2.0 (the "License");
:: you may not use this file except in compliance with the License.
:: You may obtain a copy of the License at
::
:: http://www.apache.org/licenses/LICENSE-2.0
::
:: Unless required by applicable law or agreed to in writing, software
:: distributed under the License is distributed on an "AS IS" BASIS,
:: WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
:: See the License for the specific language governing permissions and
:: limitations under the License.

PATH=%PATH%;"%SYSTEMROOT%\System32"
fastboot flash bootloader bootloader-flo-flo-04.05.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot update image-razor-mra58v.zip

echo Press any key to exit...
pause >nul
exit

It flashed all these images:

boot.img

cache.img

recovery.img

system.img

So it is de facto the same procedure as is in recommended post from my previous post :)
[Nexus 7 (2013) Android Development] Emalasto:
Is it a big deal that I didn't do that first? I really wasn't worried about keeping my data.
[Nexus 7 (2013) Android Development] _jis_:
If you wasn't worried about keeping your data then I recommend to use original flash-all.bat script from original factory image *.tgz to be sure that you will have flash your new MM ROM in pristine form. I did the same when I was updating from 4.4.4 to 6.0.0. I didn't preserved my data to be sure that there won't be any residuum from previous ROM. I have my data in cloud and it is easy to setup all my apps to my liking.
[Nexus 7 (2013) Android Development] Emalasto:
Does it make a difference that I initially took the ota and started clean to begin with?
[Nexus 7 (2013) Android Development] _jis_:
It is totally up to you and your preferences. Your way is easy and without hassle. To flash factory image is more complicated way but you can be sure then that you will get everything in original pristine form.
[Nexus 7 (2013) Android Development] Emalasto:
Well I'll definitely keep that mind if I ever have to do this again and thanks for the response! :good::good:
[Nexus 7 (2013) Android Development] tamanaco:
After flashing 6.0.0 Build MRA58V using the new NRT version 2.0.7 I'm unable to root my N7 2013 using the toolkit. MRA58V boots fine after I flash the ROM with the No Wipe option selected. I then follow the instructions in the toolkit panels and use TWRP 2.8.7.0 to flash both perm-recovery-signed.zip and BETA-SuperSU=v2.52.zip, but after selecting to Reboot the System the N7 gets stuck in the boot animation. The only way I can get the N7 to boot... is to re-flash the ROM. Any suggestions as to how to root it without getting stuck in this bootloop? Thanks.
[Nexus 7 (2013) Android Development] madbat99:
http://xdaforums.com/showthread.php?p=63168310
[Nexus 7 (2013) Android Development] tamanaco:
Quick question... The modified razor-mra58k-boot.img in the first post of this thread is for the K release. I flashed MRA58V with NRT 2.0.7 on my N7 2013... does the MRA58K boot.img works with MRA58V?

Thanks...
[Nexus 7 (2013) Android Development] madbat99:
You'd have to ask there. It should, but I would ask.
[Nexus 7 (2013) Android Development] WugFresh:
Hey guys/girls - I know I have been a bit MIA on XDA, but I am still around :)

If I missed any of your posts - my bad. I will try to back track through this thread.

NRT v2.0.7 is out now with support for all the new marshmallow builds, and a whole big script on my end to keep supporting new ones as they come out. NRT v2.0.6 had some bugs - so I am sorry if any of you were having complications with that release.

Make sure you update the kit to the latest masterlists via the update button, or letting it auto update on start (as of this post the latest are 3092). Cheers! Enjoy!

{{ WugFresh }}
[Nexus 7 (2013) Android Development] tamanaco:
The latest update to NRT 2.0.7 fixed the problem.

Thanks again
[Nexus 7 (2013) Android Development] Gitah.:
Just rooted on MRA58V and busybox doesn't show up.

Yes, I flashed it, I double-checked the log.
[Nexus 7 (2013) Android Development] dxy_c1:
Same here, I just install from play store and everything just fine.
[Nexus 7 (2013) Android Development] BanziBaby:
It installed on mine when I used the toolkit to root MRA58V & install TWRP but for some reason the quick reboot app didn't get installed despite being ticked to be installed, had to install the apk for it manually.
[Nexus 7 (2013) Android Development] Gitah.:
Oh yeah, quick reboot is missing too.
[Nexus 7 (2013) Android Development] meatfest1974:
...just curious. I bought a locked Nexus 7 off of Craigslist that is stuck on the Google screen upon boot up.

Aside from buying a replacement MoBo, is there a way I can use NRT to bypass this without activating USB debugging?

I mean, I'll try to wipe / factory restore it, but if I can't get into the OS to activate developer options, I may be SOL.

Thoughts, anyone?
[Nexus 7 (2013) Android Development] k4955:
Updated to to NRT 2.7.0 and I was able to update without wipe successfully. Thanks
[Nexus 7 (2013) Android Development] madbat99:
If the bootloader is unlocked, just pick the flash stock+unroot option. Boot it into bootloader and flash. No need for USB debugging in fastboot. But if it was one of the bricks that happened on 5.0.x, you may be s.o.l.
[Nexus 7 (2013) Android Development] meatfest1974:
...thanks again, madbat. I'll give that a go.

I appreciate your help with my S3 way back, too. It's still going strong, thanks to you!
[Nexus 7 (2013) Android Development] madbat99:
Also, make sure to choose the bricked option and not "device on normal". That way the kit knows you want to begin in fastboot not system.
[Nexus 7 (2013) Android Development] meatfest1974:
...yeah, tried that. NRT is pretty good at hand-holding you through the process. But yeah, you were right about the Lollipop update causing the Google screen-freeze; the bootloader won't unlock and freezes when I try.

Gathering from the consensus on Google, I broke down and bought a MoBo on eBay.

Considering the tablet was $45 and the MoBo was $28, we'll see in the end if this will still be worth my time.
[Nexus 7 (2013) Android Development] madbat99:
Mobo replacement seems to fix it for everyone that had that type of brick. Be sure and report back. Great price by the way.
[Nexus 7 (2013) Android Development] meatfest1974:
...Nexus 2012 > Nexus 2013.

...yeah, I kinda lucked out on the price, didn't I? Meh, timing is everything.

I Googled the heck outta this subject and I'm surprised at the overwhelming amount of bricked devices as a result of the Lollipop update. What's odd is that there are two main methods of solving the "stuck on Google screen": Physically hit the device on the back or replace the motherboard.

I pity the poor saps who defeatedly coughed up a $200 service fee to ASUS to fix a widespread problem.

That had to hurt, I'm sure.

That said, I bought a 2012 1st Gen Nexus 7 and used NRT to unlock the bootloader and root, successfully.

You could say that I got all cocky, thinking I could easily fix a "stuck on Google screen".

But yeah, the MoBo's shipped and because of the lack of follow-ups of motherboard replacement during my Google searches, I'll gladly report back.

Keep y'all posted.