yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Android Development] cas0586:
I have not messed with it today. I am going to reflash stock first before I mess with it. Then I will copy the original twrp image back into the NRT TWRP directory. Since you that is not required to replace it with the multirom image and rename.

You lost me though. It is literally going to take a step by step since there is so much information floating around. I'll be glad to put it all together once finished for other newbs. Again my apologies. I usually pick things up very quickly!

---------- Post added at 05:33 PM ---------- Previous post was at 04:43 PM ----------

Alright. I just re-flashed stock and bootloader is unlocked. Let's do this...
[Nexus 7 (2013) Android Development] cas0586:
Nope, haha not me.
[Nexus 7 (2013) Android Development] cas0586:
I was able to get the multirom recovery installed properly. Comes up every time(when selected) and can see files. There is however no ready to flash folder. I could see the folder briefly after using NRT to root and selecting the 'custom recovery'(of course selecting the multirom image in NRT options). I can see the script running on the tablet and it says everything installed properly then just boot loops. No idea what I am doing wrong.
[Nexus 7 (2013) Android Development] dlkile:
Maybe, someone else will chime in with assistance, I have ran out of ideas.
[Nexus 7 (2013) Android Development] madbat99:
OK. If you have twrp installed, just install SuperSU. Done. If you are on marshmallow, you need SuperSU beta 2.66 or 2.67. Either one will work fine. I'll find you a link if you can't find it.

Update: Download the zip from this post. (SuperSU beta) Flash it in twrp. That's it. Rooted. Get busybox installer from the play store. The stericson one works well.
[Nexus 7 (2013) Android Development] cas0586:
Yes, this is 6.0.1/MMB29O.

Perhaps not using the BETA has been the problem. As in the NRT settings I have been using 'default' and BETA is not selected. I found SuperSu 2.67 BETA here: https://download.chainfire.eu/897/SuperSU/BETA-SuperSU-v2.67-20160121175247.zip
[Nexus 7 (2013) Android Development] dlkile:
Interesting I am on Marshmallow and I have SuperSU beta 2.65 installed.
[Nexus 7 (2013) Android Development] madbat99:
Nrt uses SuperSU beta by default. I linked it in my post above yours.

---------- Post added at 08:07 PM ---------- Previous post was at 08:06 PM ----------

2.65 works fine too. But 2.66 and 2.67 are out now. I just meant that beta is required, I linked 2.67 because its the latest.

I think wugs uses 2.65, or 2.52. Because 2.52 is the master beta branch right now.
[Nexus 7 (2013) Android Development] cas0586:
Thanks guys. Successfully rooted now. Used the 2.67 beta. Should have done it that way from the beginning and not rely on NRT to do it automatically. :p

Now I also downloaded busybox installer and installed. Is there any benefit of the pro version?
[Nexus 7 (2013) Android Development] wooddale:
Im rooted on 5.1.1. going to flash 6.0.1 bootloader do I need 2.6.7 if so did you just flash it in twrp. Thanks
[Nexus 7 (2013) Android Development] madbat99:
Why are you flashing 6.0.1 bootloader? You don't need it unless you are on 6.0.1.

You don't need 2.6.7 unless you are on marshmallow. If you are rooted, that's it, nothing needed.
[Nexus 7 (2013) Android Development] wooddale:
lol I want to get on 6.0.1. Im gonna flash the 6.0.1 bootloader and radio in fastboot. I just wanted to cover my bases and be up to date with twrp and SU because after I flash I want to be compatable with everything. Thanks
[Nexus 7 (2013) Android Development] madbat99:
Oh, lol. Got it. If you're on 6.0.1, SuperSU beta 2.65 - 2.67 all work perfectly for me. No extra boot image or anything to flash. The SuperSU beta zip does it all for you.
[Nexus 7 (2013) Android Development] wooddale:
Thanks I'm gonna give it a shot today both my phones and myself batteries were getting lo last night !o!.
[Nexus 7 (2013) Android Development] dlkile:
Eureka!!! Now that you are rooted you will not get OTA update. You will have to flash update yourself and then of course you will loose root, so you will have to reroot. Hopefully from this point on you will not have a problem.
[Nexus 7 (2013) Android Development] wooddale:
Or you can just flash the bootloader like I did that's all you really need.
[Nexus 7 (2013) Android Development] madbat99:
Huh? Flashing a bootloader does not update you. Where did you get that? To manually update, you need bootloader, system and boot images.

---------- Post added at 12:56 PM ---------- Previous post was at 12:55 PM ----------

Actually, beta 2.67 is systemless root. So all you need to take ota is to flash the stock boot image and stock recovery. As long as you haven't modified the system in addition to root. If you want to keep ota ability, then don't flash twrp. Just boot twrp, and use it to flash SuperSU. Then you just need stock boot image to take ota when it comes.

---------- Post added at 12:57 PM ---------- Previous post was at 12:56 PM ----------
[Nexus 7 (2013) Android Development] dlkile:
I modify my build.prop file in addition to rooting
[Nexus 7 (2013) Android Development] madbat99:
---------- Post added at 12:57 PM ---------- Previous post was at 12:56 PM ----------[/QUOTE

No but if you flash the bootloader you can flash a stock rom and its the same or better[/QUOTE]

That makes more sense. Before you said " just flash a bootloader like I did".

Someone attempting to follow that suggestion would not be successful.

So actually it was "just flash bootloader and then flash a 6.0.1 rom like I did"
[Nexus 7 (2013) Android Development] wooddale:
That makes more sense. Before you said " just flash a bootloader like I did".

Someone attempting to follow that suggestion would not be successful.

So actually it was "just flash bootloader and then flash a 6.0.1 rom like I did"[/QUOTE]

OK you got me Ha ha.
[Nexus 7 (2013) Android Development] mikymro:
Hey there!

First i would like to say Thank you WUG for the excellent work and support!

Then i would like to complain :)

I have a Nexus 7 (2013) and i think i messed it up. I had 5.01 on it and it was the most horrible thing that could have happened to my tablet. Lagging, not responding, etc... The people who had it probably know what i am talking about.

Then one day, the table completely crashed. Black screen, no button response.

I entered in TWRP (i think i had ver. 2.8) and i decided to wipe everything i could get my hands on and then get back to 4.4 or something else. And i did. So now i had nothing on my tablet.

I installed NRT on my Win 10 PC, installed driver 1. I get to bootloader (ver 4.23) and i try the Flash Stock and Unroot option, with the Soft-bricked option checked.

fastboot devices

015d2a50a963fc17	fastboot

Connectivity Status: Fastboot Device Connected

Retrying [Attempt #1 of 5]: fastboot getvar lock_state

Retrying [Attempt #2 of 5]: fastboot getvar lock_state

Retrying [Attempt #3 of 5]: fastboot getvar lock_state

Retrying [Attempt #4 of 5]: fastboot getvar lock_state

Retrying [Attempt #5 of 5]: fastboot getvar lock_state

When the device is in TWRP, it appears in device manager like this:

[IMG="when in twrp"]http://xdaforums.com/attachment.php?attachmentid=3644882&stc=1&d=1455374676[/IMG]

When the device is in bootloader, only the first device appears, Android Device > Android Bootloader Interface.

So, this means the drivers work, right?

By now, i have managed to install TWRP 3.0.0 somehow because in the old TWRP, i couldn't mount /system, apparently because of an Invalid argument.

I tried adb sideload...error....

What else can i mess up?

I downloaded an img file (i don't know how to install the tar file i got from google's official site) by going to Utilities > Flash Zips > File already on sdcard, i choose Rom/aio zip option:

Connectivity Status: ADB Device Connected

Rebooting your device into bootloader mode...

adb reboot bootloader

Checking Fastboot Connectivity

fastboot devices

015d2a50a963fc17	fastboot

Connectivity Status: Fastboot Device Connected

Temporarily Booting Custom Recovery...

fastboot boot "C:\Program Files (x86)\WugFresh Development\Nexus Root Toolkit\data\Recovery_Custom\TWRP\twrp-2.8.7.0-flo.img"

And then nothing on the tablet. It gets stuck in bootloader with a small text in the upper left corner: Booting downloaded image.

And that's it.

So next, i tried pushing an image to the device and installing it from TWRP 3.0.0, which i have managed to install somehow.

Could not find 'META-INF/com/google/android/update-binary' in the zip file

error installing image-razor-krt16s.zip

Well, i am guessing it might be the wrong image... or isn't it?

I know i am a noob/lame, i am tring to learn.... but this tablet is just killing my grey or brown brain cells. Please help.
[Nexus 7 (2013) Android Development] madbat99:
That all looks wrong, lol. What are you trying to do? You can't install a system image from twrp.

The tar you downloaded from Google is the entire firmware. You can't install it from twrp either.

If you are trying to install a fresh factory image with the toolkit, just pick the build you want, not the build you are on, and hit flash stock+unroot. The toolkit does the rest.

If your tablet came out of the box with lollipop, it cannot be flashed to KitKat.

What is your goal here?
[Nexus 7 (2013) Android Development] mikymro:
Well, see what i was talking about being a noob? I can't even explain myself right. But, i did mention that i tried the flash stock+unroot option and after it reboots from TRWP and enters booloader, i get this log entry in NRT:

fastboot devices

015d2a50a963fc17fastboot

Connectivity Status: Fastboot Device Connected

Retrying [Attempt #1 of 5]: fastboot getvar lock_state

Retrying [Attempt #2 of 5]: fastboot getvar lock_state

Retrying [Attempt #3 of 5]: fastboot getvar lock_state

Retrying [Attempt #4 of 5]: fastboot getvar lock_state

Retrying [Attempt #5 of 5]: fastboot getvar lock_state

The nexus had 4.4 when i got it. I installed 5.01. So after erasing and formatting everything on it now it has no OS on it (that's what trwp says and i can vouch for it)

What is my goal here? Do you mean on xda, in life or with this question? :)))) I am trying to load 4.4 back.

F1! F1!
[Nexus 7 (2013) Android Development] madbat99:
Lol, I just meant the goal of your flashing expedition. After you run flash stock + unroot, you shouldn't have twrp anymore. You shouldn't be in twrp for any part of that process.

Start in bootloader mode.

Also, are you sure your bootloader is unlocked?

I remember seeing that error for some on an older version of wugs kit. Has yours updated to the most recent?

Try a different cable, and try a different port on PC.

If you still have trouble after ensuring you're updated and trying different port and cable, try the driver install process again.

I see you want 4.4.4, just a suggestion but 6.0.1 is pretty smooth.

Also, if you do have twrp installed, you can always just flash a stock rooted rom.

I saw you attempt sideload. You can't sideload the entire factory image .tar. Sideload is only for ota zip files. And only if you have an OS installed. And it has to be the proper ota zip to go from the version you are on to the version you want, there are many. But ota zips are just patches, not full firmware.

If all else fails, you can always extract the .img files from the factory image (the .tar.gz file you download from Google) then in wugs advanced tools, flash each one separately. Select flash system image then select the system.img you extracted. Then the same with boot, and and any others from that package.
[Nexus 7 (2013) Android Development] papo08:
What was once a flawless tool kit to root, backup & restore my Nexus 7 3g (2012) model has gone completely haywire over the past few mos and I just cant seem to get around it easily. I have 2..1.4 but also have some laptops with the older 2.0.x versions. theyre all failing.

Tons of hash mismatch errors

md5sum errors

cannot find or access file errors

adb push pull errors.

one of my biggest issues has been with restoring nandroid backup. the process will begin as it always has, but with a new message on screen giving a time frame of completion. when this message 1st started to appear is when my problems began. the image push takes way longer than it used to and then fails at the end do to mismatch or adb push and starts itself over. it does fail the 2nd time as well, but the full backup has been pushed (if i wait long enough, ya gotta guess on this part) and you can restore manually from the TWRP app thats popped up. This is very hit or miss.

Alternatively, i can start the restore that will surely fail but while its going i can manually push my backup folder in to the twrp/backups/blahblah folder that restore creates, and then manually install the backup from there. that works...but seems silly. There must be a better way or a fix.

ive fully uninstalled, and reinstalled. tried installing older versions I have on file. installed on a fresh pc. grabbed the latest masterlist zip. nothings changing.

If anyones got a better way/suggestion for me to simply put my nandroid backup on to my nexus' please let me know. its a basic backup folder that was created by the NRT. not an image or a zip.
[Nexus 7 (2013) Android Development] madbat99:
Just put the nandroid on your device in the twrp backup folder. Then boot twrp and restore it. Why would you use the toolkit for that? That's just silly
[Nexus 7 (2013) Android Development] papo08:
doing this ( copying these 3 files, pushing my backup folder etc to the device ) over and over on a lot of devices, vs just pressing 3 buttons on toolkit and just selecting my image sitting on my desktop.... its a time thing.

However, because of the issues ill try this. Prob is, simply copying my backup into the TWRP folder is that its not recognized once I press restore while in TWRP. When I push a restore from the toolkit, it creates sub folders under twrp. Backups, and then in backups is a random 09864693something numbered folder. only if I have my backup placed in there will it show up
[Nexus 7 (2013) Android Development] madbat99:
The numbered folder is your device serial number. Make a backup of just cache or something small and the folders will be created. Or make them yourself. TWRP/backups/serial number/name of backup.

The toolkit uses adb push, which is soooo slow. Regular file transfer is much faster, just plug in and drag and drop.

You can also use a USB otg. Twrp can mount USB. Then you just plug, restore, done. No transfer at all. When I do backups, for example, I plug in my USB otg 64 GB, select USB in twrp and make backup straight to USB stick. Easy peasy.
[Nexus 7 (2013) Android Development] mikymro:
Hey there.

I have put this problem aside for a while and i thought i might give it another try a few days ago.

I managed to do it. Guess what the problem was... I selected the wrong freaking tablet . It wasn't a 2013, it was plain ol' nexus 7. So after figuring this out, everything went smoothly. Thanks! :)
[Nexus 7 (2013) Android Development] yanleites:
Hi.

What about Android N support ?
[Nexus 7 (2013) Android Development] quickdraw86:
The developer preview came out literally two days ago...
[Nexus 7 (2013) Android Development] yanleites:
So?

I didn't ask for Twrp or something like this, just add an option to download it automatically...
[Nexus 7 (2013) Android Development] madbat99:
Dude, you realize how many nexus devices there are? And how many precautions there are to take to allow it to be flashed? And the amount of code involved?

Wug has a life too, let the man work. It comes when it comes.

You can download it yourself and still use the kit to flash it.
[Nexus 7 (2013) Android Development] dlkile:
Yes, nicely said!
[Nexus 7 (2013) Android Development] quickdraw86:
It's rude and somewhat self-entitled to more or less ask someone else to invest his/her time and effort into doing something for you that you could easily do for yourself, and that the other party stands to gain nothing from, that's all.
[Nexus 7 (2013) Android Development] yanleites:
I know, sorry...

That's why i don't write anymore :o
[Nexus 7 (2013) Android Development] madbat99:
Don't be afraid to write. You're just asking for support for something that isn't quite there yet. Wug usually adds dev previews. No one has even confirmed a safe flashing process, no root yet, nothing. It makes no sense to jam it into a toolkit that is used by everyone, noobs included. And with so many noobs using wugs kit, adding a dev preview before everything has been tested and tested again, and confirmed, would just cause problems. A million noobs in here crying that nothing works, or x y z is broken.

Basically, a little patience goes a long way is all. You can download the preview and still use wugs advanced features to flash it. Flash away and report back, help the community.

And don't forget to have fun!
[Nexus 7 (2013) Android Development] miniblue:
Nexus 7 2013 old and new

Just used NRT to go through the upgrading and rooting process on both devices. Both were previously rooted and new one on MMB29V, but the old would not flash the OTA with FlashFire. Used the toolkit on the old one and it worked great through the whole process. TWRP latest version and SuperSU v2.67. Like I said it totally worked. I just went back to the new Nexus and used the toolkit from flash stock and unroot through rooting.

This is a super tool
[Nexus 7 (2013) Android Development] Spudsicles:
Anyone know if MOB30D has been released for NRT yet?
[Nexus 7 (2013) Android Development] Gruuuvy:
wrong thread
[Nexus 7 (2013) Android Development] dlkile:
Why do you think it is the wrong thread?
[Nexus 7 (2013) Android Development] Gruuuvy:
?

This is the N7 thread and not the 6P
[Nexus 7 (2013) Android Development] dlkile:
I must have missed where a 6P question was asked.
[Nexus 7 (2013) Android Development] quickdraw86:
He probably asked the 6p question himself, realized his mistake, and edited his own 6p post afterwards to reflect his mistake. No harm, no foul.
[Nexus 7 (2013) Android Development] jim_reich:
Safe for my Bluez-enhanced Lollipop?

Hi. So I've finally managed to build the Bluez for Android version of lollipop AOSP. It was supposed to be rooted, but somehow wasn't. Would it be safe to run NRT, i.e. would it leave the kernel and the contents of the filesystem alone? I think the FAQ implies this, but I don't want to leave that to chance, it was painful to get it set up.. Thanks! This looks like a great tool.
[Nexus 7 (2013) Android Development] k4955:
Auto Rotate

Is there any fix for failing auto rotate in My Nexus 2013 wifi Android 6.0.1 Build Number MOB30J- software or hardware ?

Thanks
[Nexus 7 (2013) Android Development] josephrm:
Fastboot getvar unlocked

Alright guys, I have a Nexus 7(2013). When I bought it was flashed with TWRP, and OmniRom running 4.4.1. I've been trying to flash an updated rom with no luck. I found this tool and still no luck. It sees my device. Reboots it into fastboot mode, sees it again. It fails with Fastboot getvar unlocked. After this it wont see my device at all and I have to reboot, toggle debug a couple times and eventually it comes back.

Now, when I try to just flash a new rom with my existing TWRP install it fails to install from zip. No specific error.

I installed the twrp application from the play store and it says I have to be root to run and crashes. (Not sure how I could possibly not be root)

I'd ask that you forgive my ignorance, but I'm honestly hoping you see something ignorant here that you can correct.

Bootloader: FLO-04.01

TWRP: v2.6.0.0

Build: omni_flo-userdug 4.4.1 KOT49E eng.hav0k.20131206.091004 test-keys
[Nexus 7 (2013) Android Development] madbat99:
Make sure your bootloader is unlocked. If it's not, unlocking it will wipe all your data.
[Nexus 7 (2013) Android Development] ArGyGG:
guys i have a nexus 7 2013 and i flashed a wrong factory image nexus 2012 tablet i think and now i get stuck in boot screen ...and the bad thing is that i cant get to bootloader as my vol down button is broken .Any recommendation on how to fix it
[Nexus 7 (2013) Android Development] wooddale:
If you have computer and adb hook up USB open command post and enter reboot bootliader
[Nexus 7 (2013) Android Development] ArGyGG:
---------- Post added at 09:26 PM ---------- Previous post was at 09:17 PM ----------

[/COLOR]

Not sure but my nexus 7 isnt recognised can u help me out with the drivers please i appreciate it :)
[Nexus 7 (2013) Android Development] wooddale:
Google moto drivers it will bring you to there site then download for your computer operating system.
[Nexus 7 (2013) Android Development] dlkile:
The first this I would try it using NRT is to flash the correct version using the Soft-Bricked/Bootloop Mode. If that does not get you then try going into advance utilities and use the Reboot Bootloader. See if either one of those get you where you want to be.
[Nexus 7 (2013) Android Development] consumer61:
I just downloaded the newest version - went from 2.1.4 to 2.1.6 under Windows XP pro.

Also updated all file dependencies. Now Wugfresh will load but generates all the same error, and can't talk to the tablet anymore.

Error is "the procedure entry point wsapoll could not be located in the dynamic library ws2_32.dll"

I restored my pc back to version .4 and everything works fine again - except it won't let me update the file dependencies.

How do I fix this please?
[Nexus 7 (2013) Android Development] Spudsicles:
Hey Wugs,

Google has changed their checksum when you bring your own factory image to flash... it's now a SHA-256 Checksum. So I can't flash the new security update because it will mismatch.

Thanks, keep up the good work!
[Nexus 7 (2013) Android Development] leecavturbo:
Any 2.1.7 progress ref WSApoll issue on xp
[Nexus 7 (2013) Android Development] dspPunk:
Hi,

I am on Linux Mint OS and I am using NRT 2.1.8 through WINE.

I am getting the "hashcheck mismatch" when trying to Flashing stock + unroot (my device is in bootloop). When researched a bit I found out that I will have to update the masterlist. However when I try to do so using "Update->Import update pack" NRT is not re-directing to the masterlist page (as in the browser is not opening). Any way I can directly go to the masterlist page and download the zip manually? Please help me with the link.

Thanks,

DSP
[Nexus 7 (2013) Android Development] Starphish:
I upgraded/rooted my N7 (2013) to the lastest MM with NRT. All went well, but SuperSU doesn't appear in my apps drawer. Root checker confirms root, and the Play Store confirms SuperSU is installed (my only option is uninstall). I killed the app and rebooted hoping that it might appear, but no change.

Any idea what is going on here? How can I get SuperSU to the app drawer?

FWIW, I once had a MM ROM where SuperSU appeared in Settings, but this time I flashed the Google ROM, so I figured NRT cleaned that up. So maybe there is a wipe still required? Hopefully a limited wipe? Or is this related to systemless root?
[Nexus 7 (2013) Android Development] dspPunk:
Anyone? I thought this is a active thread..
[Nexus 7 (2013) Android Development] jerethi:
Greetings.

I recently flashed the Nougat AOSP Rom for the Nexus 7 2013 available at this XDA thread. I used TWRP. When I install NTK though, it tells me that I don't have a custom recovery installed. Is this an error in NTK, or is it another reason? Not a big deal of course, just am curious.
[Nexus 7 (2013) Android Development] Zakud:
hi,

Im getting the same thing, im on windows 10, nexus 7 2013 wifi.

thought i was doing something wrong.
[Nexus 7 (2013) Android Development] Mochan:
Why do I need to Unlock before Rooting? I don't remember ever needing to Unlock the bootloader in the past when I wanted to Root, though this was on other device brands like Samsung.
[Nexus 7 (2013) Android Development] rsbuffalo:
I have TWRP v2.6.2.0 and I wiped the all the partitions. Now no devices show using both ADB or fastboot. PC can not recognize the USB device? How to recover so PC can see device? However, Nexus7 does post on This PC.
[Nexus 7 (2013) Android Development] vince2008:
coming from android 5.1 to [W.I.P] AOSP 7.0.0_r6 Nougat, TWRP 3.0.2.0 with NRT 2.1.9 installed successfully and rooted. thanks