yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Android Development] WugFresh:
Sorry, not sure what you can do. Maybe just run it through a windows vm instead.

I am only able to work on this project in my limited free time so I have not made much progress on a multiplatform version of NRT.

I have grown to like Linux myself, but for now NRT remains Windows only.

{{ WugFresh }}
[Nexus 7 (2013) Android Development] mookdawg7:
Yeah, unfortunately I cannot even get to stock recovery. From the bootloader screen both start and recovery mode just boot to that darn google logo with unlocked bootloader symbol. I've been out of town since yesterday morn so am going to get back to messing around with it. Think I'm going to try to factory image 4.3 or something with the toolkit. Thats about the only other thing I can think of trying. Other than maybe trying to relock the bootloader as well???
[Nexus 7 (2013) Android Development] daddlefan:
Hello mookdawg7, try flashing a complete factory-image in fastboot=bootloader-mode manually. Actually it is almost the same as flashing with Wug´s ForceFlash-method, but sometimes it helps. If it doesn´t work, you probably have a hardware error.

Download the appropriate factory-image from here: http://www.randomphantasmagoria.com/firmware/

Try to flash all partitions singularly using this guide section D, and read section C for understanding what I suggest here afterwards..

Make a new directory called maybe C:\Nexus7, and copy into this directory out of wugfresh´s directory \wugfresh\data\ four files: Fastboot.exe, Adb.exe, AdbWinApi.dll and AdbWinUsbApi.dll; these will work without problems with your by Wug´s toolkit preinstalled drivers for ADB- and Fastbootmode!

After this is done copy into the same directory, C:\Nexus7, all six images (or seven if you have GSM / LTE) with 7z extracted images from the downloaded factory.tgz-file (including the five out of the zip-file unzipped image-files!)..

Open a command prompt within this directory or otherwise navigate in a command-prompt-window to the path of your newly created directory C:\Nexus7; (path in the command prompt header must then be the same as your directory´s path!). Now follow Section D in the guide and change the given image-names to your Nexus7-image-names.Skip flashing radio.img if you have no GSM / LTE! Add one fastboot command:after you flashed the other five (or with radio six) images:

fastboot flash cache cache.img

Do not lock the bootloader, its a nuisance. As soon as you want to flash a custom-recovery or a custom-rom, you would have to unlock and again loosing your personal data! Except you have to return the device for guarantee

PS: If you skip flashing userdata.img you might keep your personal data, but as you said in your earlier posts you did already use Wugfreshs softbricked and forceflash method, so all your data most probably have been wiped already. Much success daddlefan.
[Nexus 7 (2013) Android Development] WugFresh:
Just an FYI, this is just an extended routine to accomplish what force flash mode already does. If force flash mode already failed, attempting to perform these steps manually is redundant.

{{ WugFresh }}
[Nexus 7 (2013) Android Development] mookdawg7:
Thank you, thank you daddlefan for giving me another way of trying. I'm at the point of having the directory set up with required files, I wonder if you would mind giving input on whether everything appears to be correct before I proceed. Created Nexus7 directory with following files:

The four you instructed from the toolkits data file, and then I have six IMG files: userdata, boot, recovery, cache, system, and a bootloader-flo-flo-04.02 file. In addition there is a flash-all BAT file, flash-all.sh file, and flash-base.sh file. Does this sound correct? Forgive me if this is redundant and slow, I am not quite the whiz! But your instructions are very simple and straightforward. I am just desperate for this to work and want to make sure I am doing it absolutely correct!

---------- Post added at 09:05 PM ---------- Previous post was at 09:00 PM ----------

I am willing to try anything...

BTW, I apologize if I have cluttered up your thread too much with my problem WugFresh. I only initially posted here since I was using the RootKit in attempting to resolve my issue. It is clear, I believe, that your tool was not in any way part of the problem, but has been nothing but helpful to me with my previous Nexus 7 and this one! You have not suggested otherwise, but I want to make sure that is clear! Thanks again!
[Nexus 7 (2013) Android Development] WugFresh:
Fair enough, it was just an FYI so you didn't get your hopes up too much . You are obviously free to try anything you want :)

Cheers.
[Nexus 7 (2013) Android Development] mookdawg7:
Bummer, you were right Wug. Didn't work. Thanks again to you and thanks Daddlefan. Guess I'm SOL for now.
[Nexus 7 (2013) Android Development] daddlefan:
That´s what I said initially in my post! Sorry for interfering, but he sounded so hopeless," But never give up hope" ( We say in Germany)! ;)

For this you don`t need to copy the flash-all.bat, flash-all.sh and flash-base.sh. .Only your six images. Just make sure to flash the bootloader first and then "

fastboot reboot-bootloader

", before proceeding with the other images. Just follow strictly the guide in section D, and flash cache.img at the end as said in my post. Now I have to go to sleep It´s five thirty am here... daddlefan

---------- Post added at 05:55 AM ---------- Previous post was at 05:33 AM ----------

Sorry to hear this. Where did it fail? There was no error-message? But you should still have guarantee, the tab is brandnew!, At least this appllies in Germany.. daddlefan
[Nexus 7 (2013) Android Development] daddlefan:
Yes off course. But there are a lot of people here in XDA and in the german Nexus-threads reporting after reflashing twice or more often suddenly the tab or phone lives up again.

On the other hand you yourself made a suggestion to use the original Nexus7 factory-reset, which is after force-flashing the device the same redundant and also based on "Hope" ! ;)

This realiving after repeated flashing and the reported sudden bricks and bootloops "out of the blue" most probably are originated in some "inconsistencies" in the nand-chips or nand-controller. Getting a guarantee-exchange might postpone consecutive bricks by such "hardware-bugs" into the future only , forfeiting possible (follow-up?) guarantee by Google, Asus or LG!

So what is the best to do?
[Nexus 7 (2013) Android Development] Toronadian:
Hey, I know this post was over a month ago now and you might have found the answer but I just wanted to report back on this; found the answer purely by accident weeks ago as to why the restore part of the Backup SMS app you push in the toolkit wasn't working.

So I accidentally stumbled upon the Backup SMS app on the PlayStore and saw that it had an update of some sort. Turns out with KitKat, in order to be able to restore SMS, the app needs new permissions of some sort to be able to do that action (your toolkit appears to push an earlier version of the app that does not need as many app permissions).

For those that are running the restore function with the app after updating it, you then need to change the default SMS app in settings to the "Backup SMS" app (or whatever the name of the app is), and then run the restore. Afterwards, your messages should be restored, then you can change your default messaging app back to whatever it is you use. The app itself should explain to you what you need to do as you run it for the first time after the update.

However, I am not sure if it restores only to certain messaging apps. I know it for sure restores back to the Nexus 4's default messaging app but did not try out with Google Hangouts.

You probably don't care lol, but just thought I follow up on this. Sorry if my explanation isn't good, I'm not the best with the technical stuff.
[Nexus 7 (2013) Android Development] ariehle:
Stuck trying to stock

using the "Flash Stock + Unroot" function I am left w/this error:

main issue seems to be:

checking product...

FAILED

background:

I've rooted many devices all the way back to the first g1 - this was my first time trying a toolkit and I had great hopes - followed everything to the t and at this time am lost as to the next steps. I used the toolkit but it never completed - always stuck where it was sending new boot.img to the device, but it would revert back to the os after a reboot, now I'm in a boot loop. Looking for live assistance (join.me) to fix it.

Thanks in advance.
[Nexus 7 (2013) Android Development] mdamaged:
It looks like you tried to flash the grouper rom to a flo device, you should only flash roms that are made for your device.
[Nexus 7 (2013) Android Development] ariehle:
and we have a winner! thank you - could this have been the error (my error in choosing the wrong image from the beginning of the process) that made the root process hang and not work properly via wugfresh's toolkit?
[Nexus 7 (2013) Android Development] mdamaged:
That indeed is it. Select the proper image (FLO which is "Nexus 7 v2 WiFi tablet") from Wugs and Flash to stock, i.e. select "Soft-brick/bootloop" from "Flash Stock + Unroot" and you should be ok, then you can reroot once it's back up.
[Nexus 7 (2013) Android Development] Ned_Flanders:
Hi, new nexus 7 2013 owner here :)

I have updated via OTA to 4.4.2 so right now everything is stock and always has been. Coming from Xperia S I have some idea of what is needed to root and unlock the bootloader, but as this is a different device I just need to check what I am doing is correct.

I am thinking this root toolkit by Wug is what I need, will this root OK for 4.4.2 android?

Also right now I just want to keep stock ROM with root, but was thinking may as well unlock bootloader now ready for future, is it possible to re-lock bootloader though and unroot in such a way as no one would ever know? I am sure Xperia S unlocking bootloader left a flag saying it had been changed. Was wondering if unrooting and re-locking bootloader would keep the warranty if ever needed.

I just had to reinstall Windows 8 so need to setup adb and fastboot etc.

Thanks all :)
[Nexus 7 (2013) Android Development] mdamaged:
Welcome.

Yes, just make sure you select the correct ROM from the dropdown in Wugs toolkit, i.e. select Nexus * v2 for 2013 models.

Yes, you can unroot and relock within Wugs toolkit as well as manually. There is no flag to worry about.

No problem.
[Nexus 7 (2013) Android Development] Ned_Flanders:
So it took me forever to setup everything (adb, fastboot and Android SDK Manager).

Anyway I run the Full Driver Installation Guide in NRT and it rebooted the device and everything until I got the success! message.

I missed something though I think, the NRT prompted me about 3 times to download some things (maybe bootimg or something) and I cancelled one of them as I don't know how big those downloads were (limited data plan). Do I need to make sure NRT has everything it needs now or can I just go ahead and press the unlock and root buttons? I am a bit worried it could need one those downloads I cancelled (I had about 3 prompts).

EDIT: Just Ran NRT and it attempted to download the file: "modified_boot_razor_4.4.2_KOT49H.img"

NRT now all up to date.

Might be useful if the developer could include the size of the downloads before updating so users like myself who only get so much data per month can see the size before downloading :)

Also How can I backup my stock rom first (doesnt matter about the apps just the rom)?

Thanks again! :)
[Nexus 7 (2013) Android Development] Ned_Flanders:
All unlocked and rooted :D :good:
[Nexus 7 (2013) Android Development] paradiselost28:
Congrats for this GREAT tool : unlock, root and recovery installed very easily :good:

5$ Paypal from me !

One question : in what is it usefull to install Busybox (from Stericson) ?
[Nexus 7 (2013) Android Development] Ned_Flanders:
From this link: http://chislonchow.wordpress.com/2013/03/29/what-is-busybox-for-an-android-user/

And good job on the unlock and root, this is a great tool :cool:
[Nexus 7 (2013) Android Development] paradiselost28:
Thanks, I know a BusyBox can be dangerous (it's the same with root's rights) but I really wanted to know if this busybox could be usefull for something on my Nexus 7 ?

For example, I can use Titanium Backup without any problems (as far as I am root)
[Nexus 7 (2013) Android Development] Deksloc:
I'm another person having issues with the driver installation. I think it's something to do with my computer or Nexus, as the issue doesn't seem directly a result of the toolkit, but there is an issue with it later on during the driver installation, and I figured you guys might be able to help anyway.

First of all, in Step 2 of the driver installation guide, after re-enabling USB debugging, I plug in my Nexus, and the windows driver installer window pops up, but results in "No driver found" for one of the two ambiguous "Nexus 7" devices. I've tried to proceed with the driver installation, and I can install all 4 of the methods in the toolkit (on separate occasions), but when it comes time to test out if they've been installed correctly, it fails. The toolkit can't reboot the tablet itself, or confirm the bootloader status. I have to reboot it manually.

I should mention that I'm only trying to use this toolkit because I want to root my Nexus to use certain apps. It's currently on stock 4.4.2. I've used the toolkit before to unlock it after I updated it OTA from a rooted, stock 4.3 (rookie mistake, I know, but I've been out of the loop for a while and it was like 5am when I saw the OTA notification and I wasn't really paying attention). Unlocking it gave it a factory reset, of course, but when I was in the process of doing that I had the same issue getting the toolkit to reboot the tablet automatically.

Here's the info from the bootloader screen. The recovery is stock. I can include any other information that might be pertinent, but I'm not entirely sure what would be, so I'll just give this for now.

Product Name - flo

Variant - flo 32G

HW version - rev_e

Bootloader version- FLO-04.02

Signing - yes

Secure Boot - Enabled

Lock State - Unlocked

Has anyone else experienced this issue?
[Nexus 7 (2013) Android Development] detr0yt:
hey bud..... i had major problems last week getting all my drivers to work.... i spent HOURS trying to get it all set up using the NRT... dont get me wrong.... this thing is awesome.... but i had lots of issues using it to get my 32 bit windows 7 laptop to work... till i found this other exellent tool from here.... use this tool... and you will be flying in no time!! these two tools are hands down some of the most elite tools ive ever used in my droid days! thanks WUG and SKIP!

http://xdaforums.com/showthread.php?t=2525026
[Nexus 7 (2013) Android Development] mdamaged:
Download and install this, it will install a universal adb driver, so far it has yet to fail me.

Source: https://plus.google.com/103583939320326217147/posts/BQ5iYJEaaEH
[Nexus 7 (2013) Android Development] Jgm3590:
not recognizing my nexus in adb

so now i have tried 2 computers and usb debugging is on but no matter what i cannot get adb to recognize my new nexus 7 wifi some one please help
[Nexus 7 (2013) Android Development] Gareee:
I had the same thing. I had to go through each driver install in the toolkit, uninstalling each and trying the next until I could get a greenlight. it took me an hour and a half, FAR longer then actually unlocking and rooting did.

Just go through each driver installation instructions in the toolkit till it works.
[Nexus 7 (2013) Android Development] mickrg123:
I had to manually install raw drivers went through and checked OK. My problem is Nexus 7 (2013) won't show on c drive so I can access internal storage. When I check camera (ptp) it shows as a folder on laptop, but when I check media device (mtp) it does not show! Any help?
[Nexus 7 (2013) Android Development] banshee28:
I had this same problem...For me the solution was to disable MTP!! I found it under storage and the 3 "dots" and disabled it there. Then ADB worked perfect and I completed the steps to unlock and root :cowboy:
[Nexus 7 (2013) Android Development] dragonboydbboy:
This is great! Used 1.6.4 to unlock my device the first day I got it, but was having problems rooting and installing twrp. Was waiting for this to come out, it works great THANK YOU!
[Nexus 7 (2013) Android Development] Gareee:
Yeah.. my reply on the previous page about the exact same issue.

"connect nexus to usb

open device manager

uninstall the adb driver

unplug the nexus, wait a few seconds, and plug it back in

It should reinstall a driver and you should now see it as nexus 7, not google adb device

The Caveat of course, is now that the nexus works properly again with the usb port, the wug driver checker now fails, and wug no longer works because the drivers no longer pass.

"
[Nexus 7 (2013) Android Development] Roland Deschain:
I am sick and ****ing tired of Android driver issues. I've had driver issues with the Droid X, Rezound, Galaxy Note II, Nexus 7 original, and Nexus 7 refresh across three different ****ing computers. Whose fault is this? Google's for a crappy driver? Microsoft's? I honestly want to know where to mentally direct my rage.

I can't get my computer to show as a device in Windows Explorer or be recognized by the toolkit. Windows sees it as an ADB device in device manager just fine. Did all the steps in the driver configuration guide, there are no leftover USB devices related to phones/tablets/etc. in the USBDeview tool, I've rebooted, tried USB port on back of computer and front, etc.

This is a ****ing joke. I hate it. I seriously want to punch whoever it is in the face that is the cause of all these problems I've had off and on for YEARS across a bunch of devices, computers, and different versions of Windows. It's pathetic that I need to install Linux on a machine just to access a damned modern Android device half the time. Ugh.
[Nexus 7 (2013) Android Development] mickrg123:
That still does not get my nexus to show as folder on C drive. Very frustrating!
[Nexus 7 (2013) Android Development] Gareee:
It shouldn't show in windows on your c drive.. it should show in system as a separate device, just like hd partitions, and external hard drives.

Then you just browse the device and drag n drop normally.
[Nexus 7 (2013) Android Development] mickrg123:
Correct, it doesn't show as separate device so I can not access any internal storage!
[Nexus 7 (2013) Android Development] Gareee:
and you followed the instructions I posted? Did it install as a nexus 7?
[Nexus 7 (2013) Android Development] partylikeaninjastar:
Used your toolkit for my Nexus 4. Will update it and unlock my Nexus 7 after picking it up today. Thanks!
[Nexus 7 (2013) Android Development] DenDries:
Thanks, worked perfectly! Forgot to unlock the bootloader first though :p
[Nexus 7 (2013) Android Development] mickrg123:
Yes it goes through the update installation. but only shows as Nexus 7 if I check camera PTP, when I check media device mtp it doesn't show up!
[Nexus 7 (2013) Android Development] bbgt2:
Tried another Tool Kit with no luck, went back to Wug Tool as it worked flawlessly as expected. Thank you for your work.
[Nexus 7 (2013) Android Development] mickrg123:
When do you think we can restore back to factory with this?
[Nexus 7 (2013) Android Development] danvee:
As soon as Google makes the image available....
[Nexus 7 (2013) Android Development] fstbusa:
If adb is working the drivers are likely installed correctly. Try going into settings/storage, click the button in the upper right/usb connection

Make sure the mtp is checked.
[Nexus 7 (2013) Android Development] Lens Pirate:
Downloaded and installed today. Worked slicked rooted a TWRP 2.6 all working fine.
[Nexus 7 (2013) Android Development] MariozPOC:
Many thanks

Really many many thanks. I was trying with the other Toolking but no way to make Win 8 to see my device. With your step by step driver installation guide and the different types of options I found the light :)))))

Paypal

Confirmation number: 21R79847LE1726350
[Nexus 7 (2013) Android Development] Pandae:
There's only one driver you need, and it's straight from Google. It works with both N7 generations and most other Nexus devices.

http://developer.android.com/sdk/win-usb.html

First, with your Nexus 7 disconnected, go into Device Manager. Click View at the top, then set it to show hidden devices. Delete anything that might be an Android device, even drivers you may have just installed.

Then plug in your N7, and you can cleanly install the drivers I linked to.
[Nexus 7 (2013) Android Development] Deksloc:
Thanks guys, but none of these work for me. I first tried the Skip toolkit detr0yt linked to, but it couldn't connect via ADB while Wug's NRT could. So then I uninstalled all of the drivers and USB devices as per Step 1 in the driver installation guide in NRT, and tried the Universal ADB driver mdamaged linked to. I tried the full driver test in the NRT, but it didn't reboot the tablet into the bootloader. So then I uninstalled everything again as per Step 1, and then plugged my Nexus back in and updated the drivers to the Google drivers Pandae linked to. I've also tried all of the permutations of USB-Debugging on/off and MTP/PTP in order to get the drivers installed and the devices shown in USBDeview, but the toolkit still can't reboot my tablet.

Perhaps I have some conflicting driver that I'm not aware of? I tried what Pandae said about deleting anything that could be an Android device, but I didn't notice anything that referenced Android besides these two things. I can post the full list of drivers in case anyone knows of specific ones that cause issues that I might have installed.

Since neither the universal ADB driver nor the Google driver worked (and of course the options 2, 3, and 4 in NRT), I think I might just need to root my Nexus 7 the clunky old school way. Since I can reboot into the bootloader manually, I can probably find some other way to do it. The only thing that has stopped me from doing this yet, and might be worth mentioning, is that even when I put it into the bootloader manually, let the drivers install, and then try to run the Root + install custom recovery function in the toolkit, the toolkit just hangs as if it doesn't recognize the bootloader. It gets as far as "Pushing boot.img files" or something, and then just does nothing. I left it for 10 minutes, but when I came back nothing had happened, so I just closed the toolkit and rebooted my tablet.

Could that be the source of the issue? Thank you all for your help and your time thus far.
[Nexus 7 (2013) Android Development] detr0yt:
I would most definitely say that you still are not deleting all your drivers bud... In wug freshs "NRT" under tab 1 #3 and launch USBDeview it tells you to delete any devices or drivers..... In particular any device with a Vendor ID of "18d1" or "04e8" I had to delete EVERYTHING that had that.... Then i used skips to to download the right driver...
[Nexus 7 (2013) Android Development] Pandae:
I agree, there's probably still something, somewhere.

Deksloc, make sure to click any suspicious driver to highlight, then hit Del and choose to uninstall it, not just remove the device. Otherwise when you plug your N7 back in, Windows could be going back to the old driver. I know the drivers from Google work great, because I didn't have to change a thing when I upgraded my first-gen N7 to the second-gen.

How about this: when you plug your N7 back in, Windows should start trying to install it, and what new item appears in Device Manager? Something should appear.