yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Android Development] chairshot215:
I had the same problem but after a few minutes it eventually finished. Not sure what was going on but once in fastboot mode I noticed Windows trying to install a new device. After I received the windows message that the device is installed and ready to use it found my device device completed. Odd thing is that I ran the driver test before doing anything and had device manager open why performing unlock and root and when in bootloader or sorry fastboot device manager will now list my Nexus 5 as a Galaxy Nexus not that it stopped anything from working without any issue.

Anyhow have used this tool to unlock, root and install TWRP on both my Nexus 5 & 7. Was also able to restore both back to stock when I was one of the first to see the 4.4.3 update so reverted took the updates and then decided to Root again as I was not sure I was going too. Have been very happy with both devices but eventually did because after nearly a year sabbatical from developing decided I would jump back on the horse with Starship Nexus Class.
[Nexus 7 Android Development] ichigo_kurosaki:
Kitkat 4.4.4 Update (Factory Image) Available

Hey Mr. [MENTION=3110798]WugFresh[/MENTION],

Again there's another update to the KitKat lineup..KitKat 4.4.4 KTU84P just released..factory images for all Variants of the Nexus except the LTE ones. will you be again updating the toolkit? here's the thread of the update: http://www.xda-developers.com/android/android-4-4-4-ktu84p-factory-images-and-driver-binaries-available-for-nexus-devices-source-code-now-live/.

and i would like to ask. I am unlocked, and obviously rooted at 4.4.3. so if i flash this factory image, i will have to wipe data again and unroot?
[Nexus 7 Android Development] keneth_c:
Yes u will have to flash the update as stock and hence it will wipe all ur data.

It would be better to find an OTA zip to upgrade.

Wonder what this update is all about... Gonna do some reading!

--

Sent from my Samsung S3 (GT-i9300) on OmniROM 4.4.3 (official nightly) powered by Boeffla kernel via Tapatalk
[Nexus 7 Android Development] ichigo_kurosaki:
Update

just security fixes bro. no ota yet for the N7s..only the N5s first.:D it's said to finally implement the ART Runtime and get rid of the Dalvik. Do read the thread on my first post..:)

anyway, on the Wugs NRT there's an option to do the flashing without wipe ("enable flash without wipe") for flashing factory images.

EDIT: anyway, i read it somewhere that once you are unlocked, you can flash factory images without wiping data.
[Nexus 7 Android Development] keneth_c:
You can but it's not recommended. Check out WugFresh's FAQ section on the website.

--

Sent from my Samsung S3 (GT-i9300) on OmniROM 4.4.3 (official nightly) powered by Boeffla kernel via Tapatalk
[Nexus 7 Android Development] ichigo_kurosaki:
warning

yes i know it's not recommended as stated on the warning dialog box on the toolkit..but itwas also stated there that we can use that flash without wipe feature for minor updates..and i think this kitkat 4.4.4 is just a minor update..somebody on the FB nexus 7 group i also am a member of confirmed it to work for him..no lost data and he is now updated from 4.4.3-4.

EDIT; tried the "no wipe mode" and now i am updated to kitkat 4.4.4 without issues. the only thing i noticed was when i rerooted my nexus 7 (i let the NRT autodetect device+nbuild and it's now on "any build since 4.4.4 is not yet supported)..and thefunny thing is when i rerooted my N7, there was no SuperSU on my app drawer but root apps like TBand root checker says i have root. and during the rooting process, i was surprised that NRT only performed the operation halfway. it let me manually flash the root files pprovided by the toolkit.
[Nexus 7 Android Development] keneth_c:
Well NRT is now updated to 1.8.4 so you should be able to select the new 4.4.4 build on there.

Did you flash SuperSU v2.0 or an version...? Flash the latest SuperSU which is v2.0.

And yes... 4.4.4 is a minor update. It's a security fix more like it.

Thanks for the tip... About using "no wipe without data loss" when upgrading to minor update. Completely forgot about "minor update"...!

--

Sent from my Samsung S3 (GT-i9300) on OmniROM 4.4.3 (official nightly) powered by Boeffla kernel via Tapatalk
[Nexus 7 Android Development] ichigo_kurosaki:
no problem.:D

heheh..no problem bro.:D i didn't disregard your tip for me back then..i was just choosing not to follow what you said "at my own risk"..well..nothing bad happened to my tab now..i just reread and reread that dialog box of the toolkit before proceeding..but was still scared of the possibility that something could go wrong..luckily nothing did. and btw thanks for the headsup about the toolkit update.:D
[Nexus 7 Android Development] keneth_c:
No worries...

It's all about reading, sharing and helping :D

--

Sent from my Samsung S3 (GT-i9300) on OmniROM 4.4.3 (official nightly) powered by Boeffla kernel via Tapatalk
[Nexus 7 Android Development] ichigo_kurosaki:
Yeah right. That's the power of the sharing community. Anyway, when i updated to 4.4.4 via factory image and "no wipe" mode, what happened during boot was just like when actually recieving or flashing an OTA, you should see an "android is upgrading..optimizing apps x / x" on first boot..

EDIT: i rerooted my tab last night and also updated my TWRP as the new toolkit also brought along with it the new version of TWRP (2.7.0.0-2.7.1.1)..just for the sake of ensuring nothing goes wrong since when i rootd afer updating to 4.4.4, superSU didn't get flashed along and even when the toolkit did let me flash root files manually when it was still blind about the 4.4.4, i still didn't see the superSU app on my app drawer..BUT i was already rooted when i check with root checker and Titanium backup..but no one there to hold off permission granting..and now that 4.4.4 exploits (or whatever you call that) are included on the toolkit, the 2nd time i rooted, it went like how it did on 4.4.3-everything automated..i didn't need to lift a finger to operate the tablet.:D except on the time where NRT tells you to open the SuperSU to see if the binaries are updated, and to install the busybox applets.:D
[Nexus 7 Android Development] ~wolverine~:
Where do you find this 'no wipe' mode?
[Nexus 7 Android Development] ichigo_kurosaki:
it's in Options > Flash Stock > Enable "No Wipe Mode". :D
[Nexus 7 Android Development] ~wolverine~:
@ ichigo_kurosaki

Thanks
[Nexus 7 Android Development] tamanaco:
About to take the 4.4.4 No Wipe plunge from 4.4.3... Has anyone here used the new version of TWRP 2.7.1.1 to successfully backup and restore a N7 2012? I have been using TWRP 2.6.3.1 to backup and successfully restore my N7 for the past couple ROM releases. I tried using TWRP 2.7.0.0 to backup + restored my N7, but this specific version did not work for me.
[Nexus 7 Android Development] WugFresh:
Yeah. This is actually the perfect example where "no wipe mode" is a good option.

And yeah, I designed the "Any Build" mode to support the root process even when the toolkit has yet to be updated. The difference is exactly what you experienced, it requires the user to manually flash the zips in custom recovery.

Once the kit is updated, and the build is added to the list, you get the benefit of a fully automated root.

The cool thing is the kit will let you update and root new builds without me updating it right away. Just requires a few extra steps, like manually downloading the new factory pack and doing those steps in TWRP.

{{ WugFresh }}
[Nexus 7 Android Development] madLyfe:
when the tool looks for and downloads the most updated TWRP for both of my nexus devices(7 2013 and 5) it failed the first time. then a restart of the app and download again got the correct hash for both devices. not sure if bug, but ended up working either way. just an fyi
[Nexus 7 Android Development] WugFresh:
Just the servers getting hit hard all at once.

{{ WugFresh }}
[Nexus 7 Android Development] ichigo_kurosaki:
Heheh..thanks for the.reply..but i would like to clarify something. Like you said, when the new android build.isn't supported yet on the toolkit, when users root, it's not completely automated (no issues here since i know how to flash zips), so we flash the root files manually, and so i did. But why was it that even when i manually flashed superSu, when i booted after rooting, there was no supersu on my apps (but i am already.rooted as confirmed by.root apps i am using. only difference was no governor to "grant" or "deny" permission)..so i had to the supersu at the market.:)
[Nexus 7 Android Development] WugFresh:
It's a known SuperSU specific issue. Chainfire has stated before that on rare circumstances sometimes the app may not appear in the app drawer and you have to redownload from the playstore. Not sure why this happens exactly, but my guess is that if you were just to try doing it again through TWRP it would have worked. One of those weird computer anomalies where "try-again" magically fixes it.

{{ WugFresh }}
[Nexus 7 Android Development] ichigo_kurosaki:
hmmmm..ok..

ok..i have trid reflashing it about 3 times that time but still didn't appear on my app drawer after rerooting my newly updated 4.4.4..and the playstore allowed installation of SuperSU. so it means i already had root access.

Now on your release of NRT v1.8.4, i tried "rerooting" my device..and now it was automated like how it was in 4.4.3. and now i had the updated SuperSU no problems.:D thanks for the kind response.:) i was very amazed at you when 4.4.3 got released..your toolkit got updated evern before most nexus devices received the update.:D
[Nexus 7 Android Development] WugFresh:
Ahh, interesting. That is really strange that the manual method didn't work, but the automated one did - because they literally do the same thing.

Thanks man. Actually thank my past-self like four or five releases ago. Somehow I had motivated myself and got in the zone to code for like an entire week straight - creating this whole crazy automated system for updating the toolkit when new builds get released. I wrote code that analyzes new factory packs, extracts the files it needs, renames things to the proper toolkit conventions, modifies certain files, and then even updates my other code. Code that writes code - my favorite, robots FTW! I actually spent more time on it this past release, and made it even better. I try whenever I can to automate as much as possible because this toolkit has become too massive to deal with all the files manually. Too many Nexus devices, too many builds - gotta keep my sanity. It will allow me to spend time adding new features and improving the main codebase instead. :)

Cheers.

{{ WugFresh }}
[Nexus 7 Android Development] Xeddicus:
Chrome is calling the file hosted on Mediafire malware. False positive I assume? Or has someone done something to the file...
[Nexus 7 Android Development] WugFresh:
False positive. AV protectors hate Autoit, the language I used to code this. You can always check the hash values I provide on my site, if you are unsure about integrity.

{{ WugFresh }}
[Nexus 7 Android Development] ichigo_kurosaki:
+1!

+1! i also get that on first try. download of new stuff fails due to hashcheck mismatch..ihave to try and try. otherwise i just download it manually via the link provided in the toolkit. no problem for me. IDM downloads it much faster than the tool does anyway.:D
[Nexus 7 Android Development] Xeddicus:
That's what I figured, yeah. Didn't even think about the hash values, though, duh. Thanks for the program/reply in any case!
[Nexus 7 Android Development] skeeterfood:
I'm getting the following error when I try to go to www.wugfresh.com/nrt. Anyone else?

Error 1001 Ray ID: 1405f348a434098e

DNS resolution error

What happened?

You've requested a page on a website (www.wugfresh.com) that is on the CloudFlare network. CloudFlare is currently unable to resolve your requested domain (www.wugfresh.com). There are two potential causes of this:

Most likely: if the owner just signed up for CloudFlare it can take a few minutes for the website's information to be distributed to our global network.

Less likely: something is wrong with this site's configuration. Usually this happens when accounts have been signed up with a partner organization (e.g., a hosting provider) and the provider's DNS fails.
[Nexus 7 Android Development] BoeingDude777:
Simple search of the thread for mirrors: http://www.softpedia.com/get/Mobile-Phone-Tools/Others/Galaxy-Nexus-Root-Toolkit.shtml ...
[Nexus 7 Android Development] ~wolverine~:
https://plus.google.com/113329792100896065459/posts/gDz982f9qsk
[Nexus 7 Android Development] WugFresh:
Yeah. My bad, here are mirrors:

1.)*http://goo.gl/LdUZp0

2.)*http://goo.gl/wbKZ4s

3.)*http://goo.gl/YStTih

MD5 Sum: b89b3317bc60dbef2954d05390704b67﻿
[Nexus 7 Android Development] eddicin:
my too help please
[Nexus 7 Android Development] kornklown69:
So how do u flash other images from this toolkit ive done it once before just dont remember im trying to flash android L
[Nexus 7 Android Development] gurpswu:
Hit the flash stock + unroot option..browse to the image you downloaded..and thats it pretty much.
[Nexus 7 Android Development] Nexus11:
How do i use this to install L?
[Nexus 7 Android Development] WugFresh:
https://plus.google.com/113329792100896065459/posts/BszDNPs1tXD
[Nexus 7 Android Development] Nexus11:
It didn't let me add the 2 at the end of the nexus 7 md5
[Nexus 7 Android Development] dragonboydbboy:
To all those trying to install L, I used this method, it worked.

On that note, I am now trying to install TWRP (also tried Phils for good measure) via the "advanced utilities" (on my nexus 7 running L dev prev) but it doesn't work. No errors, just when I try to boot recovery it goes to the stock one. I was too afraid to try rooting and then installing custom recovery, since L probably isn't rooted yet... Not sure if being rooted is necessary for flashing the custom recovery.

Luckily, you can still access the custom recovery via "boot temporary custom recovery" in order to make/restore backups, etc.

Thought I'd let you know, and also wondering if this is something that will work/be fixed relatively soon, or is there something very different in L that would make it difficult?

Thanks for this super kickass tool!
[Nexus 7 Android Development] Nexus11:
Never mind
[Nexus 7 Android Development] kornklown69:
worked perfectly
[Nexus 7 Android Development] WugFresh:
I know why that's happening. Will fix it in the next release. You can just use the "root" button with "Custom recovery" check, it will work then. The root won't stick but that can be fixed in recovery once you have it. https://twitter.com/ChainfireXDA/status/482384834468126720

{{ WugFresh }}
[Nexus 7 Android Development] dummy1001:
Hi,

I am getting a little bit desperate as I softbricked mz Nexus 7 Grouper.

I tried to Flash Stock+Unroot (coming from unlocked bootloader with Mahdi Rom) and it failed at some point. So it is softbricked now (failed boot.img not enough memory ).

So I tried Flash Stock+Unroot with softbrick ticked with different images (4.4.3, 4.4.2, 4.1) but it always fails:

erasing boot,...

FAILED (command write failure (invalid argument))

...and everything afterwards is failing for the same reason.

Any help is welcome, I have no idea what I could do...

Hi,

It is solved now. I took some hurdles but finally it worked:

I installed the kit on an old Laptop running with Win7 and with "old USB 2.0" port. That solved the issue.

Second hurdle was that procedure failed with the message "Bootloader is 4.13 but 4.23 is required" - no problem I just installed 4.2.2 which runs with old bootloader.

Currently I am running the update in the background. Once more, USB port is critical!
[Nexus 7 Android Development] :
'virus'

I'm aware that this program doesnt have a virus, however this popped up.. I downloaded install file from the wugfresh website.. incase the screenshot doesnt post well, McAfee is ID'ing the virus as "Artemis!774D2B055DFD" & it blocks "wug_updater.exe". I'd love to remove McAfee, but this is my work computer issued by my company, so no dice..
[Nexus 7 Android Development] WugFresh:
I will report it to McAfee.

{{ WugFresh }}
[Nexus 7 Android Development] :
thanks, i wasnt sure if i should or if u wanted to take care of it... i atleast wanted u to know.
[Nexus 7 Android Development] WugFresh:
If there is a simple way to in McAfee then please do. Multiple submissions don't hurt.
[Nexus 7 Android Development] milski65:
Thanks big time wugs. Got me back to root on 4.4.4 Handy tool.

Edit Donation sent. Remember your stuff from Droid X days.
[Nexus 7 Android Development] b_hermon:
Possible bug in NRT 1.8.4???

1.8.4 isn't fully making copies of my virtual SD card, like it had in 1.8.3. When I created a backup in 1.8.3 (of 4.4.2) it created "0" "clockworkmod" and "obb". This time around (of 4.4.3) it only creates "0" and even then not all the contents are in "0". Anybody know where I can download NRT v1.8.3?

*EDITED* Found a link: http://d-h.st/nUv
[Nexus 7 Android Development] Serial_Noob:
I had an interesting experience with my N7 this morning. I got the OTA notification for 4.4.4 while I was away on business Thursday. I didn't have my laptop with me, therefore no adb, and no way to restore root, so I just ignored the notification until I got back home last night. So this morning I started the update for NRT and at the same time touched "install" on the OTA. I completely spaced off Xposed, which is installed on my N7. I didn't think about it until the OTA was installing. Everything I've read says that OTA won't work with Xposed installed, so I expected it to fail.

Surprise! It installed and rebooted. Everything came up normally, though of course I didn't have root anymore. I re-rooted with NRT, reset the Xposed framework and everything's working fine.

THAT's not supposed to happen.

What universe did I wake up in this morning?
[Nexus 7 Android Development] ichigo_kurosaki:
That's weird. But you're one lucky dude. :D
[Nexus 7 Android Development] Gloftking:
help me

Hi guys

I have a very annoying problem

my tablet is hard bricked and I don't know which options to select in this program to unbrick it. I CANNOT access fastboot as the tablet will not turn on

I am not sure how this happened but I think it was because of the command "fastboot erase bootloader" in the cmd or it was because I tried to use the temporary boot feature in the toolkit and booted with the wrong boot.img file

any ideas people!!!
[Nexus 7 Android Development] v1ncent:
I used the toolkit to unlock and root my Nexus 7 2013 Wifi only tablet running 4.2.2; I did not take any further update to my tablet. If I upgrade to 4.4.4 will I just need the toolkit to re-root? Will taking 4.4.4 relock the bootloader? (I don't want to have to erase my tablet if I don't have to.)
[Nexus 7 Android Development] marf28101995:
No it won't relock your bootloader.. But be sure you run stock kernel and recovery to install via ota after that you'll need to root it again

Cheers
[Nexus 7 Android Development] v1ncent:
OK, will do - will that option wipe my data? Just making sure.
[Nexus 7 Android Development] marf28101995:
If you update via ota no it won't wipe your data
[Nexus 7 Android Development] v1ncent:
Sorry, what I meant was when I rooted/unlocked I used the method that installed TWRP recovery as well. To accept the OTA, I have to go back to stock kernal and recovery. Does this mean I have to use the Back to Stock option (flash stock & unroot) and if so I was wondering if this will wipe my data.
[Nexus 7 Android Development] marf28101995:
If you use that.. It will wipe everything
[Nexus 7 Android Development] v1ncent:
OK, is there anything I can do to restore standard recovery, so I can accept the OTA without any step erasing my data? If there isn't a way, I'll just titanium backup it all and restore my apps later. Thanks.
[Nexus 7 Android Development] marf28101995:
I think you have the option in the toolkit to flash the stock recovery and kernel
[Nexus 7 Android Development] duckredbeard:
I used this kit to root my wife's N7 several months back. Went with TWRP and did a backup, but haven't done much since. She is complaining about the tablet being slow, so I thought I might clean it out and update the ROM. She is on KOT49H now, stock with a few OTA updates. Now that it is rooted, we are not getting the 4.4.3 update (hell, 4.4.4 is out already). We downloaded the update, but during the install, it reboots to TWRP and I'm not sure where to go from there - I just rebooted the device and nothing is changed. We keep getting the notification regarding the update, but not sure how to get past the TWRP recovery boot. Does this toolkit have a function to update to 4.4.3 or 4.4.4 where data can be retained? Not a big deal if she has to log into each app again, but it would be better if I could do it on the down-low. I need to do this where she doesn't have to do anything after the update.
[Nexus 7 Android Development] zohan99:
Of course it does! In the options menu, make sure you check NO WIPE. Then all you have to do is flash stock 4.4.4 without worrying about losing your data. Just don't forget to root after you are on 4.4.4.

Hope that helped!
[Nexus 7 Android Development] ichigo_kurosaki:
If you sideload otas from the toolkit it won't wipe data..however if you want to flash a factory image it will..but there is an option in the OPTIONS > FLASH STOCK+UNROOT>ENABLE NO WIPE MODE. Did that (and discovered) when i updated via factory image from 4.4.3-4.:D
[Nexus 7 Android Development] hazwheel:
Probably not relevant, but nexus tablets are a pain to switch on when the battery is completely dead, mine takes 15 minutes of charging before ANY sign of life on it. Have you left it plugged in to charge for a decent amount of time before trying?
[Nexus 7 Android Development] devra1:
I was running stock 4.4.3 but with TWRP 2.7.1.1 on my Nexus 7 2013.

I was able to do the 4.4.4 OTA despite the custom recovery.

Of course, I lost root and TWRP but I just got them back with the toolkit.

This way I did not loose my data.
[Nexus 7 Android Development] marf28101995:
But you had the stock kernel? I know that recovery is option but recommend..
[Nexus 7 Android Development] chavist:
Malicious file??

The androidhost file is not available for download and when I try to use the only other working link it says that software is malicious. Does anyone have another link for this program.
[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.

If you are talking about chrome flagging it, I really don't know how to report it to them. If anyone knows please tell me.
[Nexus 7 Android Development] devra1:
Yes I had stock 4.4.3 kernel.

The same thing happened when I did OTA update from stock kernel 4.3 -> 4.4.

Only thing not stock was having TWRP installed.

I did make Titanium Backup, just in case.
[Nexus 7 Android Development] v1ncent:
Thanks for all the help guys, I am now happily running 4.4.4 on my Nexus 7 without wiping any data and it's all looking good. I had to go through the install driver mess again, for some reason something had changed on my laptop and I had to work at getting the proper drivers loaded; even with instructions man did that take a looong time. Yeesh. (Would have took much longer if there were no instructions, thanks WUG! :p )

Re-rooted, still unlocked and have all my apps & data working fine. Stayed with the stock recovery, when and if I need custom, will use the toolkit to install. Again much thanks everyone, your help was deeply appreciated!!