yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Android Development] NLBeev:
You are not using OTA.

In the first place you need the latest version of Wug''s toolkit. http://www.wugfresh.com/

The first action with the toolkit is to set your model type and the current Android build. (Button 'Change')

When needed the toolkit will download the latest Android 4.4 build for your model type.
[Nexus 7 Android Development] tpinkfloyd:
Thank You SO much for this. My phone refused to let me update my recovery and didn't like the 4.4 I was trying to push and this made it all work so MANY MANY Thanks. Keep it up. If I had extra cash would be donating to you right now.
[Nexus 7 Android Development] Siddy1200:
Is it safe to use this to updaste from 4.3 to 4.4?
[Nexus 7 Android Development] devra1:
Problem re-rooting after 4.4 OTA

I have a Nexus 7 (v2) and Toolkit 1.78.

I did OTA update to 4.4 (KRT16S) which ran without problems.

This update removed TWRP and root so I used the toolkit to re-root and install TWRP and this is where things seemed to get weird.

SuperSU was no longer installed and Apps which needed root were not okay (Root Checker, Stick Mount).

I downloaded SuperSU again from Play Store and after installation everything seems okay and I am now rooted.

Any idea what the problem might have been?
[Nexus 7 Android Development] WugFresh:
Chainfire - the developer of SuperSU has noted that what you experienced can occur, and that the solution is exactly what you did (reinstall from playstore). Why it occurs, I personally don't know - but don't worry about it, you're good.
[Nexus 7 Android Development] CBers:
I have KitKat 4.4 installed on my Nexus 10, along with TWRP and SuperSU, and I'm trying to flash the 4.4 update OTA via the tookit, using the ADB SIDELOAD method but it's failing with:

E:failed to verify whole-file signature

E:signature verification failed

I have KitKat 4.4 installed, along with TWRP and SuperSU.

Anyone know how to get rounf this "failed to verify whole-file" message please ??

I have adb sideload the KitKat update OTA on my Nexus 4 successfully.

TIA.
[Nexus 7 Android Development] WugFresh:
Maybe it's just a bad download of the OTA zip. Try again with a freshly downloaded one.
[Nexus 7 Android Development] CBers:
OK, thanks Wug - I'll give that a go.
[Nexus 7 Android Development] devra1:
Thanks Wug, I thought it was something I might have done.

BTW, the version of SuperSU it loaded from Playstore was 1.80.
[Nexus 7 Android Development] CBers:
Thanks Wug - downloading of the ZIP file again cured the issue :good: :good: :good:

Now running build KRT16S on my Nexus 10.

:D :D :D
[Nexus 7 Android Development] WugFresh:
Cool. I will get that updated today along with a few other things.
[Nexus 7 Android Development] niav:
Everything that I previously mentioned had been done with the 1.7.8 version of the toolkit. Anyway I have since flashed stock using the toolkit and then rooted again and all seems well now. Thanks for your input.
[Nexus 7 Android Development] bobd2754:
Last night I saw that the OTA was ready on my N7 v1, I installed it. All went well and even though I lost root, I saw that TWRP was still there. I plugged in the NRT and, after a couple of hiccups with superSU (Andy lying on his back with the red triangle) it rooted and was fine.

Thanks WUG!

donation forth coming (payday is friday)
[Nexus 7 Android Development] CBers:
I've just got my KitKat update (4.4) on my Nexus 7 2012.

What's the best way of installing this without bricking the device please?

Can I do it via adb sideload or is that just for OTA updates?

TIA.
[Nexus 7 Android Development] Siddy1200:
I tried to use this to return my grouper to stock, followed the instructions, NRT said it worked, but left my device in bootloader. Now it is stuck in bootloader and fails to boot recovery and fails to start.

I tried to temp run TWRP which works but when I try and wipe it just says failed.

I went to advnaced and installed TWRP recovery, but it asks for a password. I never made a password so I press cancel. Wipe still fails.

I tried Adb sideload but it just TWRP just says Failed, unable to mount system.

I tried to push a rom to /sdcard/, NRT says process finished but when I go to install the rom is is not there.

What should I do?
[Nexus 7 Android Development] Siddy1200:
FIXED

I went back to TWRP, went to wipe, in the wipe options I unchecked everything and then only had "system" checked, so wiped system only, now I can mount system and pushed a rom and installed.
[Nexus 7 Android Development] cammel:
[MENTION=3110798]WugFresh[/MENTION] just one silly question, I'm using my Nexus 5 completely stock, no root, no unlocked bootloader, no nothing... But I want to flash stock Google image on my phone just to try something out, so the question is, can I flash stock nexus 5 image from Google servers on my phone without unlocking my bootloader?

Thanks in advance!
[Nexus 7 Android Development] WugFresh:
Unfortunately no. Google doesn't allow flashing their stock packs without an unlocked bootloader.
[Nexus 7 Android Development] cammel:
Thanks a lot for to your fast answer!

[MENTION=3110798]WugFresh[/MENTION], is there any chance that I have a little private conversation with you about a problem on my Nexus 5 that's driving me nuts? Maybe on hangouts or somewhere else?

Thanks in advance!
[Nexus 7 Android Development] CBers:
[MENTION=3110798]WugFresh[/MENTION] - would this work do you think?

TIA.
[Nexus 7 Android Development] itzallgood707:
Can I use Odin to recover my N7 Grouper?
[Nexus 7 Android Development] SkOrPn:
Lmao no not unless your grouper was built by Samsung.
[Nexus 7 Android Development] Messerschmitt262:
Is it possible to use this tool to return to stock android together with all other components?

At the moment I have PA and a custom radio.
[Nexus 7 Android Development] SkOrPn:
Yes, this tool will bring you back to stock if you use it correctly.
[Nexus 7 Android Development] armz_bey:
Got my nexus 7 rooted now.... Thanks for toolkit sir wug... I flashed to stock/unroot and then root again this time it worked perfect....
[Nexus 7 Android Development] Spannaa:
Managed to deodex stock KRT16S for my Nexus 7 and your toolkit rooted it :good:

Thanks [MENTION=3110798]WugFresh[/MENTION]
[Nexus 7 Android Development] paulo_cv:
Jjhyj v
[Nexus 7 Android Development] itzallgood707:
The only reason I asked was because the toolkit said to try Odin if other stuff didn't work.

I'm well aware Odin is for Samsung, all my devices are Samsung besides my N7.

I just thought it was strange so I'd figured I'd ask
[Nexus 7 Android Development] WugFresh:
Yeah my bad. I should put some logic into that message box and only say that if you have selected a Samsung device.

It would be nice if there was an ODIN equivalent on the N7.. But I don't think there is (to my knowledge).
[Nexus 7 Android Development] WugFresh:
Yeah sure. Feel free to send me a message on hangouts. I too have some issues with my N5.. I am thinking about requesting a replacement.
[Nexus 7 Android Development] cammel:
Awesome, thanks! I'm contacting you right now on hangouts! I really Hope you are available :D
[Nexus 7 Android Development] itzallgood707:
Thanks for the reply Wug.
[Nexus 7 Android Development] WugFresh:
Note to everyone, I have been really busy these past few days with other projects but I should have some free time tomorrow.

I am aiming to roll out v1.7.9 within two days with some fixes and enhancements. Most notably - fixing the restore nandroid button (turned out to be something really small I overlooked), adding the ability to flash stock without wiping (not recommended.. But useful in some circumstances), including an alternate update info site to work around ISP's who block pastebin, and some other optimizations. Stay tuned.

{{ WugFresh }}
[Nexus 7 Android Development] SkOrPn:
As Wug said it would be nice if Odin worked with the N7. I loved using Odin ever since its discovery but since it is a engineering level piece of software built specifically for the Samsung techs, I suspect it would only work with devices who have Download Mode built into their bootloaders. It had such a nice clearly understandable user interface but could easily brick a device if you were not paying attention (I know from extreme experience lol). Bricking devices with Odin back in the day is what got me started debricking professionally with a JTAG Riff box, and building/selling JIG's on ebay (which I no longer do after about 5 years in the biz).

Besides, personally I think NRT is much more robust with many more features than Odin ever had.
[Nexus 7 Android Development] itzallgood707:
Wug already answered my question look up a few posts.

---------- Post added at 01:07 AM ---------- Previous post was at 01:06 AM ----------

I built my own JIG as well.
[Nexus 7 Android Development] hazwheel:
The nexus 4 has a download mode, which would suggest there is an LG version of Odin somewhere

Pushed from me to thee
[Nexus 7 Android Development] WugFresh:
Probably proprietary to LG.. And its what they use in-house to fix borked devices.
[Nexus 7 Android Development] FreyrNjord:
Hello

After waking up Windows from its sleep mode this morning, Device Manager no longers loads the ADB driver and my Galaxy Nexus is shown as "Unknown device", although I synced Outlook OK last night before going to bed :-/

Samsung_USB_Driver_for_Mobile_Phones_v1.5.14.0.exe, PDAnet (Samsung USB Driver for Mobile Phones 1.3.1900.0), and Universal Naked Driver 0.72 all trigger Windows to say: The best driver software for your device is already installed. Windows has determined the driver software for your device is up to date."

So next, I ran Nexus Root Toolkit v1.7.6, but after I okayed the upgrade to 1.7.8, but it's been sitting for over 15mn at "Download Status: Complete! 100%". What should I do?

Thank you.

---------- Post added at 02:25 PM ---------- Previous post was at 01:44 PM ----------

I just had to click on the X button to close the window and proceed.

Next step, uninstalling the driver and installing a new one:

Driver Solution #1: Universal Drivers

Windows says "USB Device Not Recognized"

Device Manager shows "Unknown Device"

Driver Solution #2: PDANet

Has someone else experienced this? FWIW, I'm using Windows7.

Thank you.

---

Edit: Problem solved.

I noticed the phone wouldn't even charge when plugged into an AC charger. So I rebooted the phone... and the phone showed that it was charging OK. Then I plugged it into my Windows 7 host, and voilà: The driver installed automatically and I'm back in business.

Lesson learned: Before worrying about drivers or cables, make sure the phone is at least charging when plugged into the mains.
[Nexus 7 Android Development] Mystikalx:
Hi Wug,

Able to assist on this?

Can't get my Nexus 7 back on stock, recovery and ROM is gone.

Tried force flashing but still can't get it back up.

Appreciate your assistance, thanks!
[Nexus 7 Android Development] WugFresh:
Looks like a connectivity issue.. Try again on an alternate USB port (preferably USB 2.0 if available).
[Nexus 7 Android Development] Mystikalx:
Solved it by changing USB ports, thanks Wug!
[Nexus 7 Android Development] tevil:
Having a bit of issue seems with drivers. It does not pass the driver test but will still run through the process.

Can I ask do you have to unlock prior to root or can you just root.

I went through the process but upon reboot it was not rooted.

Running the new KitKat

Thanks

update:

Got it

Dont know why but this morning when I tried it went to 1.7.9 and ran unlock and root fine...... I feel dirty. I have a new Galaxy S4 which I could wait to root but having my Nexus S so long on stock I feel a bit guilty I just devirginized it
[Nexus 7 Android Development] ProNewb:
virus detected?

https://mediacru.sh/Sc1-C-lhMd56.png

while updatig from 1.7.8 to 1.7.9

false alarm?
[Nexus 7 Android Development] tele_jas:
THANK YOU, THANK YOU, THANK YOU!!!

My stock N7 was soft bricked from trying to do a stock, factory update. You saved me!
[Nexus 7 Android Development] finneginsfast:
Thanks for a great tool!

Confirmation number: 51E817898D987691X
[Nexus 7 Android Development] Anderson2:
Hi WugFresh

Again thanks for your great toolkit. I'm hitting the problem many others have stumbled on.

After using the toolkit - and deleting Windows installed drivers in the process - I can no longer connect to my windows 7 as MTP.

My rooted nexus 7 2013 running stock android 4.3 connects correctly as PTP to my windows 7 laptop but will not as mtp.

I am using the Asus oem usb cable with the same usb port that worked before using the toolkit.

My windows 7 device manager says the "android phone" is connected as a "Google Nexus ADB interface" and the driver listed is ClockworkMod 7.0.0.4

When I tell Windows to update the driver it tells me I have the latest driver even when I tell it to search in c:\Windows.

I've switched between MTP and PTP and back many times both with debug on and off, with no help. Connected and reconnected.

I've rooted 3 times and this happens every time after using the toolkit. Either the correct windows driver for a MTP connection is deleted in the rooting process or Windows is now made to think that the ClockworkMod driver is the best correct one and will not install the driver needed to connect the nexus 7 as a mtp so I can transfer files.

How do I find and install the correct Windows driver to connect as mtp *after* using the toolkit which causes the problem. What is the name of that driver? How can I install it manually or make Windows change to it.

Thank you.

(this is a reproducible problem that many have encountered).

---------- Post added at 03:23 PM ---------- Previous post was at 03:16 PM ----------

Forgot to mention that I also uninstalled the Google nexus ADB interface driver, disconnected and reconnected the usb. Windows recognized the nexus but installed again the same ClockworkMod driver.
[Nexus 7 Android Development] WugFresh:
Yes. Please report it to your AV provider so they can review it, deem it safe and whitelist it.

{{ WugFresh }}
[Nexus 7 Android Development] Anderson2:
No solution?
[Nexus 7 Android Development] WugFresh:
I have never had this problem so I don't know what to say. I just toggle mtp off and windows configures it properly, then I turn it back on and mtp works.

My best suggestion would be to try an alternate driver solution like the RAW drivers. When you do this.. Make sure to start at step one and remove previous drivers.
[Nexus 7 Android Development] madLyfe:
is busy box supposed to be installed on when going from CM on my n7(2013) back to stock(kitkat)?
[Nexus 7 Android Development] Anderson2:
I was afraid of that. Thought you might have an idea. Ah well, it was worth a try

Just for the record, the forum and other nexus 7 forums have numerous messages about this problem. I own 2 nexus 7 tablets - 2012 and 2013. My own experience mirrors yours with the unrooted devices. I simply connect the tablet using the usb cable and it is automatically recognized and the nexus 7s appear in Windows Explorer and files are transferred with no problems.

However after using the toolkit, the ptp works fine but the mtp doesn't. Happened the 4 times I used the toolkit to root my devices. I would be able to have windows Explorer recognize the tablet in ptp mode only if I restored Windows to before using the toolkit. Unfortunately I would rather not do that this time. Maybe because the driver the toolkit installs is more recent than the original Windows driver Windows does not update back to that driver.

If I knew the name of the original Windows driver I would copy it back from a backup without needing to restore the os partition.
[Nexus 7 Android Development] cammel:
I can't sideload the ota update on my Nexus 5 with the toolkit, as soon as I select adb update on stock recovery, the phone is no longer recognized and I don't know what to do... Can anybody please help?

Thanks in advance!

Enviado desde mi Nexus 5 mediante Tapatalk
[Nexus 7 Android Development] Vyom:
I have the same problem as Anderson2. MTP stops working after using Toolkit the first time. I use adb to push or pull files on my pc. Or pen drives.

But thanks wugfresh for the tool. It made life a lot easier for a lot of tasks. :)
[Nexus 7 Android Development] WugFresh:
Maybe I can help one of you get this working remotely... then when I figure out what to do, I can post it here. Just because I have never had the problem - doesn't mean I shouldn't try and help you guys solve it. :)

Seems to be happening to more than one person.

People with this issue, please hit me up via chat on hangouts. I have some free time today. Cheers.

{{ WugFresh }}
[Nexus 7 Android Development] WugFresh:
sometimes adb sideload mode needs to be configured separately - even if you already configured adb before. Check your device manager and see if there is an entry with a question mark - then use 'Update driver' > 'Let me pick from a list of...' > adb interface (or something like that).

Cheers.

{{ WugFresh }}
[Nexus 7 Android Development] charon72:
WTF !!

http://postimg.org/image/83n6hw0ql/
[Nexus 7 Android Development] WugFresh:
Its a false positive, please report it to your AV provider so they can review it, deem it safe and whitelist it.

The programming language this is written in (Autoit) is known to get falsely flagged.

I am the sole developer and publisher of this application and if you downloaded it from my website and the hash value matches what I posted there then I guarantee its 100% clean and will always be.

I use to report it to AV providers myself but it is too time consuming, so I ask that users please report it themselves.

I hate malware and viruses - I would never publish something publicly with malicious intent.

If you don't believe me feel free to ask others in this thread or elsewhere.
[Nexus 7 Android Development] charon72:
I do believe you, and it happened when version 1,76 auto updated, that is why i was surprised.
[Nexus 7 Android Development] cdt82002:
Asus Nexus 7 New Rom install failing

So hey guys I have the new nexus 7 and Ive used Wug's program(great BTW) to unlock, root and install twrp. Before I did any of this I received and updated to the 4.4 software. Now every time I try to install any kind of Rom it fails within seconds. Ive tried purity rom/cm11 and no luck. Ive been doing this stuff for years and never encountered this problem.

I've been doing the usual steps

1. Backup current rom

2. Factory data reset

3. Wipe Dalvik and cache.

4. Install Rom --> then fails. Screenshot attached(sorry its sideways)

What am I missing? Please help!!
[Nexus 7 Android Development] keneth_c:
Uncheck both...

--
[Nexus 7 Android Development] Vyom:
Well, it's a lot coming from you, that you want to resolve this issue. Unfortunately, I don't have access to my pc, probably for the next 8 hours.

I would hope someone else can help you show the problem and you may able to resolve it.

Thanks for the enthusiasm nevertheless. ;)
[Nexus 7 Android Development] Skinpipe:
i have experienced the same error messages when trying to flash anything in twrp after 4.4 stock update on nexus 7 wifi. Your not alone im sure the twrp guys will figure it out.

running latest twrp also, flashed today
[Nexus 7 Android Development] Anderson2:
Thank you wugfresh. That's very kind of you. Unfortunately I'm traveling out of the country and won't be home for over a week. I still appreciate your very kind offer. I'll work on it on my own in the meanwhile. I'm sure it's a matter of restoring some legacy Windows 7 64 usb driver that was removed. If I find how to restore it I will certainly share it. Can't do it now.

Thanks again.

P. S. I use stickmount and a flash drive in the meanwhile to transfer files but it is less convenient.
[Nexus 7 Android Development] Hearnbiz:
Just wanna say thanks, this was one of the easier roots I've done. Incredible walk through! :good:
[Nexus 7 Android Development] Anderson2:
Maybe I should start a new thread but since I asked the question here I will provide an update that restored my windows 7 64 bit mtp driver functionality.

I've tried so many things that I'm not sure of all the details in the sequence that finally worked but here are the essentials.

As described above in this thread, after adding the adb driver to root the nexus I lost the ability for my windows 7 laptop from connecting in mtp mode. I tried all the recommended steps but nothing worked till now. Here is what worked.

My Windows device manager showed only one entry related to the nexus 7. It was an entry for "android phone" and within it an entry for "Google nexus ADB interface".

**there was NO entry for "portable devices" **

1. I clicked on the "Google nexus ADB interface" and selected to update the driver, /browse my computer for driver software, selected c:\Windows and this time

**let me pick.... **

2. Here is where I don't remember exactly which I chose. There was 2 choices but no mtp option and I think I selected ??

3. When it installed, suddenly portable devices appeared in the device manager with nexus 7 in it !! But with the yellow error symbol.

4. So I updated it and now mtp works fine.

I wish I could have been more accurate but at least this proves it is a wrong driver issue. Update does not solve it but selecting one of the 2 offered choices in

**let me pick.... **

Worked to recreate the entry for " portable devices" and when that was updated, mtp connection was restored!

Hope this helps someone else.
[Nexus 7 Android Development] fearstealth:
i'm new

i have a brand new laptop and all the usb ports are 3.0 and i wanted to root my New Nexus 5 ! and i was wondering if the toolkit will run smoothy if i use my 3.0 ports.:cool:

thanks :D
[Nexus 7 Android Development] Anderson2:
My laptop also has only usb 3.0 ports. Toolkit worked to root my 2013 and 2012 tablets. Be sure to use the usb cables that came with the Asus changer.
[Nexus 7 Android Development] keneth_c:
From .tgz file

After extracting .img files from .tgz (google factory images)...

I was wondering how do I manually flash my Nexus 7 (2012) aka nakasig device using WugFresh's Nexus Root Toolkit from "Advanced" section.

I tried it sometime back...

I believe you have to manually flash boot, system etc. one by one...

and you have to skip flashing data so as to not lose your app + app data...

Please correct me if i'm wrong...

2nd thing...

as soon as I flashed boot.img...

my device restarted & wouldn't boot...

and I could not go further & flash other .img files (like system etc.)...

I did have my nandroid backup.... but I couldn't get my device to reboot into recovery...

somehow with great difficulty I managed to reboot into recovery... and was able to restore my nandroid...

Can someone guide me on the steps using the WugFresh's NRT?

I'm a n00b with fastboot & adb commands...

and am not comfortable typing the commands manually...

your help will be greatly appreciated...
[Nexus 7 Android Development] WugFresh:
You don't have to use advanced utilities to flash factory packages although you could use each button follower by Quick Tools - fastboot: reboot bootloader.

To flash factory packages just use the "Flash Stock + Unroot" button - there are options in the toolkits main options menu for flashing stock without wiping data - however its not really recommended. Better off backing stuff up - doing a full flash then restore things. Cheers.

{{ WugFresh }}
[Nexus 7 Android Development] neok44:
I've been trying to unroot and return to stock my Nexus 7 but somehow this seemed to have bricked it.

It got stuck on sending 'bootloader' for over a half hour. Eventually gave up and closed the program. I now still have a bootloader, but no recovery and it can't boot. I can get to the bootloader and i tried to run it by the bricked setting, but same thing. I already downloaded the image, so what do i have to do now to get this thing restored?