yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Android Development] steviemch:
There's a backup and restore function in the toolkit itself, just use that.

---------- Post added at 10:03 AM ---------- Previous post was at 09:57 AM ----------

Yeah go through the process as normal for the second device, obviously don't uninstall drivers you've set up for the first device but check there's no sign of any drivers installed for the second one, if there is, remove and configure with the toolkit. I opted for installing the universal drivers, it took a few tries but eventually everything set up great.

---------- Post added at 10:09 AM ---------- Previous post was at 10:03 AM ----------

In the options menu you can change default recovery to cwm.

Sent by carrier pigeon
[Nexus 7 Android Development] dbgeek:
I'm guessing that you could properly MTP connect your 2nd device (e.g., could see it in windows explorer) before you installed the 2nd set of drivers. I've tried usb different ports for each device. I've tried the RAW install (#4) and the device reboots when I click on the button in the toolkit instructions (I.e., so I know that there's some sort of connection). And I've done each multiple times. I've even tried doing the in different orders. In each case, the 1st device connects fine, the 2nd can be seen in device manager, but the connect attempt in step 3 fails.
[Nexus 7 Android Development] tevil:
just updated to 4.4.2

keeps getting stuck when temporarily booting to TWRP.

Any ideas?

says waiting for your device then times out. reboots back to unrooted OS manually

thanks

UPDATE:

Disable your lock screen
[Nexus 7 Android Development] dbgeek:
Managed to get things working. I apologize if this is WAY more detail that people want, but I thought being thorough would help others.

First I had to edit the wpdmtp.inf per the following comment. I actually had to go into Wug's tool, to open the USBDeview (page 1 on the the driver install tool) to find the VID, PID and MI settings for the device that WON'T connect properly (toggle between PTP and MTP connect while connected will highlight the "device" that's active when the device that won't work properly is connected). Make the edit: add the bolded lines with the proper VID, PID and MI (my N4 didn't have MI settings, so I didn't include and MI parameter).

http://xdaforums.com/showpost.php?p=37054750&postcount=3

Then doing the driver installs per this comment:

http://xdaforums.com/showpost.php?p=35854664&postcount=7

Now both devices will connect via MTP and work properly with Wug's toolkit, even using the same USB port.
[Nexus 7 Android Development] WugFresh:
Look in the toolkits options menu.

{{ WugFresh }}
[Nexus 7 Android Development] thenbt:
ive been trying to flash stock 4.4.2 on my nexus devices and when i get to hashcheck verification it has a black space for the md5 hash, after i click ok nothing happens, also when i choose my model type android 4.4.2 doesnt show up, anyone else experience this problem?
[Nexus 7 Android Development] bobd2754:
I've noticed after the 4.4.2 update on my Nexus 7, the USB debugging pull down doesn't have the MTP, camera choice. How can we do the driver MTP install thingy?
[Nexus 7 Android Development] WugFresh:
There's actually another way to get to it if you need. Buried in settings:

Settings > Storage > Menu item in upper right

{{ WugFresh }}
[Nexus 7 Android Development] WugFresh:
Well.. the blank space is an input box.. To input the md5 - as it states on that interface. This would not be necessary if you updated the toolkit. You are lacking the latest masterlists. Just initiate a toolkit update.

{{ WugFresh }}
[Nexus 7 Android Development] thenbt:
ive tried to update it but it still stays the same, also i have enabled force flash mode and still the same
[Nexus 7 Android Development] keneth_c:
WugFresh...

On the KRT16O update for Nexus 7 (2012 GSM) via your toolkit, there was a MD5 mismatch for some reason. I had to input the MD5 checksum in myself and it worked then. This is inspite of having the masterlist updated then. Not sure why that happened or how it happened... But just thought I'd let u know. This was probably 3 weeks ago.

--
[Nexus 7 Android Development] doncaruana:
FWIW, I did a fresh update to the toolkit last night and then rooted my Nexus 7 Wifi (original) with KRT160 with zero problems whatsoever - no MD5 issues or anything. Plugged it in, let it go, and watched it go through the whole sequence, rebooting the N7 several times in the process. Painless, Pretty, and Perfect.

Thanks again WugFresh!!
[Nexus 7 Android Development] keneth_c:
Not sure how that happened in my case. Nevertheless like I mentioned earlier, after entering the md5 checksum in the input box (in NRT), NRT verified the md5 with the image and all went well after that. Hassle free flashing.

Since then I've flashed KRT16S and the recent / latest (KK 4.4.2/KOT49H) ...hassle free once again. Such a pleasure using NRT. Thanks WugFresh!

& thanks for your input mate.

--
[Nexus 7 Android Development] tagari:
Great toolkit,been using it for over a year now...But for the first time i've been having difficulties flashing stock..I'm trying to flash 4.4.2 coming from purity rom but it seems to be stuck at "writing system".Any workarounds?
[Nexus 7 Android Development] scupetta:
sorry but working fine with usb 3.0 and windows 8.1?
[Nexus 7 Android Development] keneth_c:
Would recommend USB 2.0 depending on the device I guess.

Definitely working on Windows 8.1 ;)

--
[Nexus 7 Android Development] scupetta:
ok tnx, but if i have a notebook with only usb 3.0? :'(

Inviato dal mio Nexus 5 con Tapatalk 4
[Nexus 7 Android Development] WugFresh:
It works fine on my comp with 3.0 ports.
[Nexus 7 Android Development] scupetta:
i so happyyyy thanks Bosssss ;) great job

Inviato dal mio Nexus 5 con Tapatalk 4
[Nexus 7 Android Development] cvhovey:
Previously used NRT when I updated my Nexus 7 Wifi (2012) to KRT16S (4.4) without a hitch. Was doing the same thing for KOT49H (4.4.2) but get an AutoIt Error as follows"

Line 14368 (File 'C:\....\NexusRootToolkit.exe'):

Error: Variable used without being declared.

I reloaded NRT making sure everything up to date. Retried doing same thing for KRT16S (instead of KOT49H) but end up with same error. So basically can't flash anything at this point because of this AutoIt error.

Both of the above factory image files are on my computer, MD5's checkout okay via NRT, and the KRT16S factory image is the

same

downloaded file on my computer that I'd flashed previously about 3-1/2 weeks ago ... likely with NRT v1.7.8. Not seeing a way to roll-back to an earlier version to see if that would resolve this error.
[Nexus 7 Android Development] WugFresh:
Maybe try reinstalling NRT.
[Nexus 7 Android Development] ecossais:
The same thing happened to me going from Purity to Stock 4.4.2. My solution was to stop the script and start over, it ran to completion the second time with no errors. Good luck.
[Nexus 7 Android Development] tagari:
Thanks for your feedback,but the only solution i found was to stop the script and just boot the device,which booted up perfectly..i tried going to stock because i had wierd android OS drain the last week with a lot of custom roms/kernels even with playstore app installed but they still occur to stock,so i'm kinda frustrated on this now :P
[Nexus 7 Android Development] cvhovey:
Uninstalled NRT, downloaded and re-installed NRT. Same error. HOWEVER, this error popping up may be due to one NRT change I made ... enabling "No Wipe Mode"?

I don't have time at the moment to re-try without "No Wipe Mode" enabled, but will do so later when I have enough time to restore data.
[Nexus 7 Android Development] WugFresh:
Ok.. I will look into it. I tested that feature without problems so I am wondering what's causing that error for you. I will see if I can figure it out.
[Nexus 7 Android Development] SITH16:
If I can't get the OTA 4.4.2 to install, can I use this to upgrate to 4.4.2 by using flash stock + unroot?
[Nexus 7 Android Development] melfunn:
Took the OTA 4.4.2(while rooted with TWRP) , updated NRT & rerooted. Cake. I am using N7 wifi 2013.
[Nexus 7 Android Development] keneth_c:
Instead of doing that... Why not find the custom recovery OTA zip on XDA and install via recovery?

If you really wanna go through all the hassle of backing up ur app + data... Then flash stock + unroot... And then upgrading using Google stock image... You can certainly use this toolkit. It's a no-brainer hassle-free toolkit for sure.

--
[Nexus 7 Android Development] WugFresh:
FAQs - I am unlocked/rooted and OTA is not working – how do I update to the latest android version (without loosing all my data and/or root)?

Gotta love FAQs. ;)
[Nexus 7 Android Development] cvhovey:
I'll second the FAQs. In my case, option 1 of the above FAQ (No Wipe Mode) hit an AutoIt Error, option 2 (side load) hit some kind of Korean IME mismatch error ... ended up with an option 3 solution that took all of a couple minutes.
[Nexus 7 Android Development] WugFresh:
I am looking into the autoit error you got with option 1. As for sideloading, I know that script is built correctly - so I am guessing the specific error you encountered when sideloading would explain the problem. Either way, glad you got it resolved.
[Nexus 7 Android Development] MrMiami81:
The kit is asking me for a modified boot razor 4.4.2 kot49h image. Can I use the factory razor image or do I need a certain one? Sorry for the question but I'm stuck and can't find this anywhere.
[Nexus 7 Android Development] hazwheel:
Backing up is a given dude, a hassle maybe, but anyone who flashes stuff and doesn't have a backup is a fool.... Its tedious, but necessary.
[Nexus 7 Android Development] keneth_c:
Nandroid is mandatory. Totally agree.

Was talking about Titanium backup for apps + app data earlier.

--
[Nexus 7 Android Development] SITH16:
Actually, the tablet is brand new and doesn't have anything on it I"m not willing to lose. It also isn't rooted...It actually took the OTA after I OEM locked it today so its a moot point but just letting you know...
[Nexus 7 Android Development] bazabaza:
I have flashed my 2012(16g) version back to stock (4.4.2) from a custom ROM. Everything seemed to go OK. noticed a message about a fix if the nexus reporting low storage, but didn't read it properly...of course the nexus is reporting only 6g storage. Where can I find the advice to read again please. Don't seem to be able to see it in the Wiki or FAQ?

Solved = flashed 4.4 storge as should be
[Nexus 7 Android Development] Berrydroidcafe:
I was trying to find the exact issue you are/were having, no luck so far. The question I have is, was the Nexus 7 stock when you were trying to upgrade? I'm just trying to clear things up in my head because when I bought mine, it first updated to 4.3, then it updated to 4.4.1

It didn't matter because I was going to root and flash a custom rom, but the ota did work without a hitch. So are you saying that the ota to 4.4.2 isn't working?

Edited: Never mind. :) If I could have found a way to delete this, I would have. :confused::what:

Sent from my Nexus 7 (2013)
[Nexus 7 Android Development] SITH16:
Its cool, thanks for the effort dude. I now know it wouldn't take the OTA because it wasn't locked properly...Once I OEM locked it setting it back to full factory, it went fine. Now I am backing up my stock set up and I am going to unlock it and re root it.
[Nexus 7 Android Development] hoopas:
Just used this great toolkit on my new N7. Couldn't ask for anything simpler:good:Everything went without one hiccup. Thanks Wug!!!!:good:
[Nexus 7 Android Development] wmccombs:
Need the 1.7.8 toolkit badly

I have searched everywhere and cannot find this version of the tool kit. 1.7.9 will not work for me. I get mismatches everywhere on the hash and the manual download does not find the path. Somehow I lost TWRP recovery and no way to flash it now. I need to get 1.7.8 because it worked fine for me but I cannot find it. I wish legacy versions of the toolkit were available for situations like this. I've spent almost an hour searching for it. Even the 1.7.5 link is there but broken but not sure it would work. Thanks anyone and everyone
[Nexus 7 Android Development] WugFresh:
Check to see if your AV is blocking androidfilehost. Another user discovered malwarebytes pro was.

Running legacy versions of my software is not going to fix what you are experiencing. No changes were made to the download system between 1.7.8 and 1.7.9.
[Nexus 7 Android Development] wmccombs:
Thank you soooo much!!! Wugfresh....it was my Malwarebytes as well. Funny, I have been using it for a few years and your kit for several months now and no problems till now. Thank you I had not thought of that. Great toolkit. Merry Christmas to you and yours. Bill
[Nexus 7 Android Development] Berrydroidcafe:
Slightly off topic but I tend to stay away from those apps. Fine and dandy on a computer, but as long as you are not installing stuff from shady places, Android devices/OS is pretty much secure. Not infallible, but the prevention (malware apps) can be a pain, especially with apps like this one (NRT)! Just my opinion.

Sent from my Nexus 7 (2013)
[Nexus 7 Android Development] wmccombs:
Actually I have Malwarebytes on both my tablet and my PC. I disabled it on my PC then it worked fine. I'm having issues with 4.4.2 not flashing now so I will try disabling on the tablet as well. I'll let you know how it goes. Thanks for the input.
[Nexus 7 Android Development] WugFresh:
Cool. I reported the issue to Androidfilehost admins - they are reaching out to malwarebytes. Cheers.

{{ WugFresh }}
[Nexus 7 Android Development] wmccombs:
Thanks for reporting that. My last issue seemed related to the fact that I actually had 4.4.1 on and not 4.4. So I flashed it anyway and everything seems fine...no more problems with your toolkit. LOL, it never fails the one thing I don't think to check is the problem....I always wrongly assume since it always worked in the past no reason it shouldn't work now. Burned again. Thanks for your help
[Nexus 7 Android Development] Berrydroidcafe:
Wasn't until after the fact that I had the DUH moment! Of course it was the computer. Have to stay away from the liquid refreshments. Are you dirty flashing 4.4.2 btw?

Sent from my Nexus 7 (2013)

---------- Post added at 12:49 PM ---------- Previous post was at 12:46 PM ----------

Guess that answered my question. :D Glad you got it figured out.

Sent from my Nexus 7 (2013)
[Nexus 7 Android Development] allendoc:
I have two Nexus 7 and this Tool has been priceless. Both are rooted fine, both running 4.4.2 but one shows all files when connected via USB and one shows just camera files. I did the same process on both Tablets, but I can not copy files to one of them... Anyone know if I missed something? Adfree, TWRP, BusyBox and ES File Explorer all have Root access on both Tablets, just one will not give me root access via USB. Is there a setting I am missing? Thank you in advance, Allen
[Nexus 7 Android Development] WugFresh:
Try plugging that device in and toggling USB mass storage (mtp) off via settings > storage > menu item in upper right.

See if windows configures a driver, then re-enable mtp.
[Nexus 7 Android Development] allendoc:
It worked, now one Nexus 7 works via MTP, and the one that works with Debug on gives me complete access to the phone. Just odd, but atleast I can transfer things to my Son's Christmas gift now before I rebox it. My daughter's behaves like my S4, just odd, but thank you for the tip.
[Nexus 7 Android Development] gogol:
...DELETED...
[Nexus 7 Android Development] tevil:
they both rooted????

Is your other nexus really set on MTP and not PTP?

drivers shoudlnt be an issue if they are both the same device.
[Nexus 7 Android Development] dbgeek:
I don't have 2 N7's, but have an N4 and N7. Initially, I couldn't even PTP connect the 2nd device (regardless of which was initially connected, MTP), but after the 3rd or 4th reinstall, got to the point that you describe. I eventually, went through the steps listed in the post, to get things working properly:

http://xdaforums.com/showpost.php?p=48417408&postcount=3803
[Nexus 7 Android Development] allendoc:
Yes, both are rooted and the second N7 is really set to MTP, not PTP to work. I completely agree that in theory that same model devices should not need different drivers or setups, but they did, reason I posted here. I have access to both devices now via windows explorer, just takes different setup on each N7 to do so.
[Nexus 7 Android Development] G-STAR01:
Thanks mate, great program.

Just rooted my N7 (2012-wifi) 4.4.2.
[Nexus 7 Android Development] hx4700 user:
"can't access update server. If this continues contact wugfresh"

Whenever I launch the toolkit, it now gives me the above message.

I also get "can't access update server. If this continues contact wugfresh" by clicking on "Update" . Is this pop up suppose to happen?

I notice it was an issue in 2012, but was fixed. It has not happened to me before. My version is 1.7.9

---------- Post added at 01:26 PM ---------- Previous post was at 01:23 PM ----------

Will the toolkit support updating the android version? I am stuck rooted on 4.4.0. Updating on the phone, even trrying to do so through CWMR appearsx to install teh files, but I am still on 4.4.0. It would be great if NRT could support upgrades to android, as once rooted, OTA updates do not work.
[Nexus 7 Android Development] keneth_c:
Yes NRT does support updating. I recently updated to 4.4.2 using NRT.

Not sure about OTA updates working or not. I think that has to do a lot with the bootloader.

But there's another thread where you can get the OTA update zip for flashing. Read the instructions carefully. Good luck.

--
[Nexus 7 Android Development] Berrydroidcafe:
Just because the program can't access the update server doesn't mean the program won't work. You should still be able to flash with it. Have you tried using TWRP?

If I understand you correctly, you want it to do upgrades such as ota's? If so, I don't think that would be feasible.

If you want stock 4.4.2, then the only way to do it is return to full stock 4.4 than do the upgrade via ota, or you can download the factory image from Google and flash it via the toolkit.

Sent from my Nexus 7 (2013)
[Nexus 7 Android Development] hx4700 user:
I have tried on both nexus 5 and 7-2013. I downloaded the update as a stand alone package, then went into TWRP to flash it, rebooted once into recovery and then normal reboot. This is the procedure recommended on several websites. However, I'm still on 4.4.0.

If I return to stock then OTA update, then use NRT to root, does that not remove all my personalisation?

I'd hoped that nrt would have an update section, where it would either use the android OTA update already on the device, or download the update file, then flash that to the unlocked and rooted device, leaving it rooted, with no data loss - updated as easily as if done OTA.
[Nexus 7 Android Development] Berrydroidcafe:
The only sure thing that I know is, if you flash stock, you will lose your personalization. In order to get the OTA, you have to be fully stock. I understand what you want to do, but I'm not sure if it can be done that way.

Sent from my Nexus 7 (2013)
[Nexus 7 Android Development] WugFresh:
FAQs - I am unlocked/rooted and OTA is not working – how do I update to the latest android version (without loosing all my data and/or root)?

Please read FAQs.
[Nexus 7 Android Development] keneth_c:
I believe that has to do a lot with the locked/unlocked bootloader.

But if your bootloader is unlocked and remains unlocked, you can definitely update without wiping your data. There is an option for 'no wipe' update in one of the tabs in 'Options' in NRT.

Please read the FAQ mate. It's there for a reason :)

--
[Nexus 7 Android Development] hx4700 user:
Sorry, I had tried the FAQ, and searched for update, and not found this guide.:o Perhaps I should have looked using my PC rather than my tablet.

Thank you. This is exactly what i had been looking for.

The first option of enabling "no Wipe Mode" did nothing on my Nexus 7 2013; the second option of enabling "Force Flash Mode" did work. I then had to root again, and to install SuperSu again, and only then could I install busybox and TWRP. Finally, a rooted N7.2013 running 4.4.2. Tomorrow I can do the same on my Nexus 5.
[Nexus 7 Android Development] scotyard:
I have installed wug's toolkit and set up the drivers. The driver test was a success.

How do I make a complete system ROM of my device?

Earlier I created a system ROM backup of my phone using MTK droid tools and used SP Flash Tool to flash it back. It created a complete system/data backup of my phone. Whenever I had an issue, or a flash went bad, I could restore that backup and come back to an earlier state no matter how big the issue.

I would like to put such a banker backup in.

How do I go about doing a complete system backup? What options to use on the backup window?
[Nexus 7 Android Development] ruscik:
Toolkit works great however I had to do manual driver install. Now all works great bar mtp/ptp. When I connect in MTP it sees a device on USB but nothing shows up in my computer so unable to copy files. In PTP Nexus shows Up as camera but inside no folders, no photos, unable to copy anything. Any suggestions how to fix it?

Sent on the move from HTC One
[Nexus 7 Android Development] grunted:
does anyone know where I can get the latest update for the bootloader I'm on ver. 3.34.
[Nexus 7 Android Development] CBers:
File Browser

[MENTION=3110798]WugFresh[/MENTION] - any chance of adding a basic file browser in your toolkit please ??

It would be easier to see what folders/files there are on a device rather than blindly trying to remember what they're called.

I ask this, as my daughter has changed the PIN on her Nexus 7 and can't remember it, so I am trying to copy everything off of it before wiping it.

TIA.
[Nexus 7 Android Development] WugFresh:
Like a root file browser? It's something I have thought of, but it's not so basic to code :)

It's on the (potential) to do list but won't be a feature on the next release (v1.80).

{{ WugFresh}}
[Nexus 7 Android Development] CBers:
Something like that :good:

OK, no worries, just a thought seeing as I'm now about to wipe my daughter's Nexus 7.

Unless you have any other suggestions ??

TIA.
[Nexus 7 Android Development] Berrydroidcafe:
Since you're going to wipe it, why not try to wipe only the data partition? This is a wag, but maybe that will clear the pin?

Sent from my Nexus 7 (2013)
[Nexus 7 Android Development] CBers:
I tried that but it didn't work.

Thanks for the suggestion though :good:

Just re-flashed stock and unrooted again.

About to restore from Titanium Backup.
[Nexus 7 Android Development] ScusiXDA:
same issue, insecure boot img remote fail to download.

I have that same issue, I'm trying to figure it out now, because I cannot even do a virtual disk backup because it doesn't see the MTP and the toolkit im using( skipsoft ) theres something wrong/missing/ not working correctly with the insecure boot.img . So im looking for that insecure image to backup before i re-root the nexus 7 tablet ( i did like last year but went back to stock/locked bc of not knowing how to deal with the OTA's fast enough to keep it going smoothly.
[Nexus 7 Android Development] ruscik:
I do not think it is the boot image. I had my nexus 7 mtp on stock but could not do add with drivers installed. So I did manual driver removal, then I stalled drivers supplied with this root kit and rooted my nexus with custom recovery. After that I plugged in 2nd tablet I bought as gift just to root it and it was also not loading as Nexus 7 anymore And it was bog stock. I even skipped initial guided setup just to get mtp off and turn debugging on.

Sent on the move from Nexus 7