[Toolkit] Wug's Nexus Root Toolkit v2.1.4 [Updated 01/16/16]: Nexus 7 (2013) Thread

[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"

 

[wooddale]

---------- 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

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.

 

[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:

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.

 

[madbat99]

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
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

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

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
015d2a50a963fc17fastboot
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.

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?

 

[mikymro]

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?

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!

 

[madbat99]

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!

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.

 

[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.

 

[madbat99]

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.

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

 

[papo08]

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

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

 

[madbat99]

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

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.

 

[mikymro]

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.

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!

 

[yanleites]

Hi.
What about Android N support ?

 

[quickdraw86]

Hi.
What about Android N support ?

The developer preview came out literally two days ago...

 

[yanleites]

The developer preview came out literally two days ago...

So?
I didn't ask for Twrp or something like this, just add an option to download it automatically...

 

[madbat99]

So?
I didn't ask for Twrp or something like this, just add an option to download it automatically...

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.

 

[dlkile]

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.

Yes, nicely said!

 

[quickdraw86]

So?
I didn't ask for Twrp or something like this, just add an option to download it automatically...

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.

 

[yanleites]

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.

I know, sorry...
That's why i don't write anymore

 

[madbat99]

I know, sorry...
That's why i don't write anymore

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!

 

[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