yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Android Development] mykimouse:
I have a unrooted Nexus 7 2012 wifi 32 gb.

1. Bootloader is unlocked using this tool.

2. Then i tried the Flash Stock + Unroot and selected the 4.4 (KRT16O) nakasi-krt16o-factory-db4a1a8a.tgz file.

The bootloader is showing 'Signature Match.' at the top left on screen but currently the tool is stuck at the point shown below.

Its more than 20 mins now. Please advice.

Flash Stock + Unroot...

------------------------------------------------------------------

erasing 'boot'...

OKAY [ 0.036s]

finished. total time: 0.036s

******** Did you mean to fastboot format this partition?

erasing 'cache'...

OKAY [ 0.093s]

finished. total time: 0.093s

erasing 'recovery'...

OKAY [ 0.034s]

finished. total time: 0.035s

******** Did you mean to fastboot format this partition?

erasing 'system'...

OKAY [ 0.484s]

finished. total time: 0.485s

******** Did you mean to fastboot format this partition?

erasing 'userdata'...

OKAY [ 4.965s]

finished. total time: 4.965s

sending 'bootloader' (2100 KB)...

OKAY [ 0.303s]

writing 'bootloader'...

FAILED (status read failed (Too many links))

finished. total time: 195.568s

< waiting for device >
[Nexus 7 Android Development] bittersound:
You Sir, are effin' brilliant. Thank you so much for your time and help, I am now KitKat'd up! Time to send a donation your way I think!
[Nexus 7 Android Development] sherlock5545:
Just updated to 4.4, working great so far but it doesn't seem to improve the performance of the Nexus 7 that much.

Sent from my GT-I9300
[Nexus 7 Android Development] fullmetal509:
I notice scroll lag on certain apps,, and takes longer to charge.

Via HTC Uno!
[Nexus 7 Android Development] Droidnoobi:
Wug,

Would this file work for the issues I am having trying to find files and such?? I am at a stuck point and am unsure what step I should proceed to next with the error message I am experiencing.
[Nexus 7 Android Development] cammel:
Hi [MENTION=3110798]WugFresh[/MENTION] thanks for taking the time of checking this! :D

So the only thing they changed is the values to match the ones you have already posted yesterday on G+ for the nexus 7, right?

And the values for the nexus 4 haven't changed at all?

I don't know why, but yesterday night I thought they also changed that values... but I can't check them because I delete the tar file from my PC after the toolkit unzipped it :rolleyes:

Enviado desde mi Nexus 4 mediante Tapatalk
[Nexus 7 Android Development] WugFresh:
No.. You are missing a core file of the toolkit. I am guessing your antivirus quarantined it or something. You need to reinstall the toolkit and let it install all its files.

{{ WugFresh }}
[Nexus 7 Android Development] makbil:
Got myself in a mess, no thanks to Google :(

I downloaded the earlier image for nakasig and naturally had issues flashing it. Finally sorted everything, got the new file and managed to flash 4.4 successfully - kind of. After booting and setting up, it would only show about 6GB of memory from the 32GB it actually has. So, this morning decided to do a full wipe and reinstall 4.4. First went to twrp recovery that was flashed and deleted system, data and cache after which twrp showed the correct amount of memory as 32GB then started the tool kit to reflash 4.4. Things went sour for some reason, at the stage it was flashing the bootloader, while waiting for a reboot the screen just went dark and has been that way since. The PC can detect some device that is connected but there is no way to use adb or fastboot and it looks like the bootloader is wiped or corrupt. I've done some research on this issue and it seems to be more common than I would have thought. Apparently the only way out is if the bootloader can be flashed in apx mode.

Looks like it's going in for service using the warranty.

If anyone has any suggestions, I'd be glad to hear them otherwise looks like a drive to the shop for me.
[Nexus 7 Android Development] limpet:
If you do get it back to this state, try a factory data reset from settings. This

worked for me once with 4.3.
[Nexus 7 Android Development] FreyrNjord:
NRT 1.7.6 has been running for over an hour after hitting the "Create Android Backup File" with the default options. There's not much disk activity on the PC side, and no activity whatsoever on the Nexus side.

The PC application just displays "Backing up; please be patient".

Is the application just stuck and should I start again from scratch?

FWIW, it seems stuck while backing up "org.ebookdroid".
[Nexus 7 Android Development] kwbr:
Thanks for the update WugFresh!
[Nexus 7 Android Development] iifuzz:
I am having issues installing the drivers for fastboot.

I am on windows 8. Booted using the restrict driver enforcement thing.

I am have tried all of the driver options... The driver test will reboot me into the bootloader, then it will stop saying it cant find the fastboot device. I have tried clicking OK to try again several times..

I have uninstalled the drivers from the device manager and usbdeview or whatever and reinstalled using all of the options in the program as well as other drivers i have found online.

I have tried switching usb ports..

Nothing gets me past the bootloader. It comes up in windows as unknown device.
[Nexus 7 Android Development] WugFresh:
When in fastboot mode.. In device manager right click that unknown device and install the raw drivers.
[Nexus 7 Android Development] iifuzz:
I tried that already.. doesnt work. still shows an exclamation mark and doesnt work.
[Nexus 7 Android Development] GoldenLucifer:
'download links' on wug's page are none existent ;/
[Nexus 7 Android Development] geokilla:
I'm having a problem with the drivers. I followed the manual word for word, and even uninstalled the LG and Samsung drivers, as well as the VendorID drivers just in case they would cause a problem. Then once I got the new drivers installed and tried to get ADB working, it didn't. Windows Explorer wasn't detecting my Nexus 7 in MTP mode either, despite it showing in the Safely Remove Program icon. However, if I put it in PTP mode, Windows Explorer would detect it just fine. The toolkit couldn't find ADB either, despite having USB Debugging enabled.

Edit: Fixed MTP. Which fixed ADB... I did it by following this link.
[Nexus 7 Android Development] datt-bo:
:good::good: Thank you very very much :good::good:
[Nexus 7 Android Development] outlawmodzz:
memory problems

Tried to factory reset didn't work please help. N7 (12) mobile.

Memory down to 8gb from 32 GB.
[Nexus 7 Android Development] WugFresh:
Tried a factory reset to do what? Please quote what you are referring too or provide more details.

{{ WugFresh }}
[Nexus 7 Android Development] limpet:
Incorrect partition size is discussed here:

http://xdaforums.com/showthread.php?t=2518083

not sure it's completely diagnosed.

It happened to me installing 4.3 after swapping in a 32gb motherboard.

A data reset from settings after reflashing stock fixed the partitioning

for me.
[Nexus 7 Android Development] greeneyez15o:
BiG thAnX to the CreAtor !!!
[Nexus 7 Android Development] makbil:
Had exactly the same problem on 2 different N7's (nakasig) trying to flash 4.4. Go into recovery and format the data partition and you'll get back the missing memory.
[Nexus 7 Android Development] tamanaco:
Arrrggg!... last night I finished putting the final touches to my Wug's updated N7 now running KRT16O rooted and with Custom Recovery. Feeling lucky, I integrated some of the Google Apps into the ROM as I did not expect a new factory image for a few months. This morning I get a Software Update message telling me that OTA KRT16S is downloaded and ready to be installed. Given that I have Custom Recovery and have modified the ROM integrating the Google Apps I believe that can not just install OTA. Do I need to wait until the Toolkit gets updated with the KRT16S image or can I just expand the factory image in the Factory_Images folder of the toolkit and do a Flash Stock + Unroot?... Or is there ANY possible way to apply this OTA using TWRP having modified the ROM by integrating some apps? Why... Oh! why must I always be running the latest and greatest.
[Nexus 7 Android Development] Stransky:
Hi

Just got the same update OTA and installed OK on previously updated 4.3 to 4.4 using NRT 1.7.6. Only thing is have now lost root but am going to re-root later using the toolkit.

Installation went without problems and everything working sans apps which require root access.

Stransky
[Nexus 7 Android Development] fabulosospucas:
Do tell if it's safe to root KRT16S on Nexus 7 (2012) with the toolkit. I had problems with the KRT16S OTA and now that the device is booting again I don't want to go down that hell again.
[Nexus 7 Android Development] Spannaa:
Yes, it's safe - I've just re-rooted mine.

Select "Android *.*.* - Any Build" and follow the instructions exactly ;)
[Nexus 7 Android Development] fabulosospucas:
I just did so too. All good, KitKat KRT16S rooted! Wug rules!
[Nexus 7 Android Development] porkovich:
I am on stock 4.4 KRT16 , with twrp - recovery , and rooted. Do you think that i can take the OTA .... or will i loose the recovery / make a mess with my device. I have no intentions to reflash all stock again ... ? :confused:
[Nexus 7 Android Development] Spannaa:
If the OTA doesn't fail, you'll lose root and recovery but can use Wug's toolkit to re-root and put TWRP back ;)
[Nexus 7 Android Development] porkovich:
Hm i lost root, but not TWRP, that is great. I will reroot now.
[Nexus 7 Android Development] BobbaLouie:
Did the 4.4 OTA on a sideloaded 4.4

- Navigate to '/sdcard/!ReadyToFlash/Root_Files'

I'm in TWRP and I'm stuck here because there is no such folder. The dialogues said it was pushing the files, where are they?

[edit] Still on bootloader 4.18, is that a problem?
[Nexus 7 Android Development] thejmannnc:
i just purchased a nexus 7 lte from t mobile today (just came out today) will i be able to use this kit for it?

thankyou so much for any help you may be able to give!
[Nexus 7 Android Development] tamanaco:
Took the plunge and installed the KTR16S OTA over a Wug's Toolkit installed and rooted KTR16O stock ROM. As it has been mentioned here, it worked even with TWRP Custom Recovery installed and with a bunch of apps that I had integrated into the ROM with Titanium Backup. The process ran smoothly. I was surprised, but a bit concerned when the OTA process booted into Custom Recovery (TWRP) to patch the system... but all the commands ran without a hitch. A very friendly OTA I must say. Lost root, but quickly restored it using the the Toolkit by selecting the NAKASI-GROUPER Android *.*.* given that there is no KTR16S option in the toolkit... yet. After rooting I updated the SuperSU binaries with version 1.75 which was released today. I'm a happy camper.

EDIT: Spoke too soon. The TWRP Custom Recovery was actually clobbered by the OTA process. I just used the Root and selected to also flash Custom Recovery to fix it. Btw, I have been unable to flash the Stock Recovery for some time now. After I flash it I always end up with a dead Android when I try to boot Stock Recovery. Custom Recovery works just fine after I flash it.
[Nexus 7 Android Development] makbil:
Got the "new" 4.4 factory image and after checking a few things, I saw that only system.img needs to be flashed so that's what I did. Rooting using the toolkit was easy, all you need to do is select "Android .. Any build". The good thing with this process is that all data remained intact, so I didn't have to setup my N7 again.

One interesting thing is that "ART" doesn't seem to be available for the N7 2012 but it is there for N7 2013. Anyway, happy camper here and thanks for this very useful toolkit, really does make life easier.
[Nexus 7 Android Development] NLBeev:
The updates of SuperSU are mostly packed in a .zip file.

Would you be so kind to tell us how you updated SuperSU.

Tia.
[Nexus 7 Android Development] melfunn:
OTA as I chat
[Nexus 7 Android Development] tamanaco:
I updated SuperSU via the Google Play Store. Once installed I open it and it asks to update the SuperSU binaries.
[Nexus 7 Android Development] arunreturns:
Small hiccups

Just a small question. Forgive me if its asked before.

If i update via OTA from 4.3 to 4.4, And OTA is SUCCESS, I lose root and recovery.

But is my bootloader also locked?

And one more question, if i unlock bootloader again will it wipe the data on my device, is there anyway to get around this?
[Nexus 7 Android Development] suchavibrantthang:
Can't seem to reroot. Boots itself into bootloader and pushes modified boot.img.

Tablet says "Booting download image", pc stuck at "waiting for your device"

I've flashed stock 16S successfully, I've uninstalled/reinstalled drivers, Tried enabling/disabling MTP. ADB shows device attached. Tried downloading goomanager app and attempted to d/l and flash recovery, but it won't download from server. Am I missing something? :confused:

WinXP

Bootloader 4.23

Lock State: Unlocked

Bone Stock 4.4 16S

EDIT fixed: Using the permanent flash in advanced util did it. Whew.
[Nexus 7 Android Development] mattcooper:
Anyone keep getting stuck on 'Formatting Cache using make_ext4fs function' when flashing a zip? Stuck there for 5 mins now and not sure whether to quit...

Edit... Ooops, just noticed this is the N7 forum... Having the problem with N5
[Nexus 7 Android Development] dbgeek:
OTA worked fine. Had to reroot (which was expected), but other than that everything seems to work perfectly.
[Nexus 7 Android Development] thejmannnc:
Just wanted to say thank you, everything worked perfectly!
[Nexus 7 Android Development] limpet:
Check the size of: modified_boot_nakasi_4.4.0_KRT16S.img

if not 4994 KB delete it, restart toolkit, and select that build again. It should download the correct file. Worked for me.

(got this from Wug...some people may have gotten a bad version)
[Nexus 7 Android Development] imeem:
Trying to flash 4.4 image and my phone is on the android bootloader screen for a very long time. Also CMD on the computer ins't really doing anything. Am i suppose to keep waiting or am i suppose to do something?
[Nexus 7 Android Development] WugFresh:
Something is wrong. No need to wait. It should start flashing immediately so since its not.. Just start your device back up and exit the script. Are you running v1.7.8, which device and build are you flashing? Where did you install the toolkit (what directory)?
[Nexus 7 Android Development] imeem:
yes i'm running the latest version. I'm flashing on Nexus 4 running aokp 4.2.2 . I installed the toolkit in the default location (program files x86).

it might be a bad image file so i'll try redownloading

EDIT: retry again and it's working fine. and i just notice that this isn't the Nexus 4 forum...
[Nexus 7 Android Development] Zeusc4:
Point form

1 - Once rooted and We update to another OS version by OTA or image. Do we have to root again each time ?

2 - If Yes, Do we have to wait for the modified boot image release in order to root ?

Im new to these stuff.
[Nexus 7 Android Development] NLBeev:
Till now every update of my Android devices causes to lose root access.

Rooting again for Nexus x devices is easy with The Nexus Root Toolkit.

http://www.wugfresh.com/
[Nexus 7 Android Development] Zeusc4:
That means, we have to wait for the modified boot image also.

Considering even astronomical chance of getting my phone bricked eachtime rooting, Im considering cynogenmod now. :)

My device is Nexus 4.
[Nexus 7 Android Development] limpet:
I've lost root with every update, OTA or image.

I was able to root a Nexus 7 with KRT16S by selecting "Android *.*.* Any build" in the toolkit which, I believe, does not need a build specific modified boot image.
[Nexus 7 Android Development] NLBeev:
My device is Nexus 4 too.

Yesterday updated with the Nexus Root Toolkit.

Now using Android 4.4 Build: KRT16S.

I think rooting has a lower 'bricking' risk than flashing a new rom.
[Nexus 7 Android Development] WugFresh:
No you don't. You can root with "Any Build Mode" which forgoes using those modified boot.imgs.

Also.. the modifications are harmless... And they aren't flashed- they are booted, which means the worst that could happen is a bootloop and the end user has to power cycle (that's it). As far as I know, no user has ever had NRT brick their phone during rooting ever.

The ways to hard brick your phone are as follows:

+ You pull the USB plug mid stock flash

+ Your device isn't charged enough and dies mid ROM flash

+ Your device was faulty in the first place

+ You physically smash it with a brick :)

All that said.. If you want to try custom ROMs - go for it. I just wanted to make that clarification.
[Nexus 7 Android Development] HighlanderZA:
Hi All

Been on 4.3 since release and now on 4.4 on my Tilapia.

Had to flash each image manually with toolkit - OTA wouldn't work at all.

all is up and working fine on wifi and 3G.

I flashed Radio 18 from the toolkit when I went to 4.3 and it shows in bootloader mode as correct, BUT on the settings 'about Tablet'

screen it has always and still shows 17. Any idea why and is it even worth bothering about?
[Nexus 7 Android Development] makbil:
Agree 100% with this. I would say the only real danger of bricking is while flashing the bootloader, which unfortunately is what happened to me. I'm pretty confident there is a way out from any other situation.

Just as a footnote, if you're already on 4.4 and want to flash to the latest version, all you need to do is take the system.img from the factory image and flash that through fastboot (and boot.img as well if you want, though I don't think it's necessary) and you will have a dirty flash to the latest version.
[Nexus 7 Android Development] dbgeek:
I can verify that rooting with the JB boot image, after the OTA will not brick the device (yeah, I'm that guy who misses the obvious).

Wug, that's for this great tool. Google needs to pay your for this development. With the availability of this tool, the only device that I'll buy in the future, will be a Nexus.
[Nexus 7 Android Development] JackD3ath:
Great Work!

Just wanted to say great job! I was having trouble updating TWRP through goo manager, used this app to do it...easy peasy, lemon squeezy! :good:
[Nexus 7 Android Development] WooHooGuy:
Hey Wug, love the toolkit and recommend it to everyone I know.

There may be an issue with the current version of your toolkit, 1.7.8, I am running Windows XP.

Backup + Restore

Click "Restore" then under Restore full backups w/ custom recovery, clicking the Restore Nandroid Backup button does nothing.

No script launches.

If I go to backup and click the Create nandroid button, the script launches just fine.

I have been tossing back and forth between nandroids as I just flashed KitKat using your great toolkit, realized I didnt have my Titanium data folder saved so I had to roll back to the nandroid I made a few hours ago and noticed the bug.

No real issue as Ill just launch TWRP and flash my nandroid from a usb drive, just a heads up for you.

Thanks for your toolkit, after actually buying a nexus device your toolkit is the second must have for it.
[Nexus 7 Android Development] ardaalisahin:
This program is an perfect tool for nexus 4 all versions.I have used it to root my n4 krt16s build.Thank you very much for your help WugFresh.

Nexus 4 cihazımdan Tapatalk ile gönderildi
[Nexus 7 Android Development] skrewie:
great app !! Nexus 7 user flashed to latest 4,.4. is it possible to root 4,4 with this and flash twarp ?
[Nexus 7 Android Development] hazwheel:
Twarp? Hee Hee, yes it is, rooting and twarp

Pushed from me to thee
[Nexus 7 Android Development] armz_bey:
downloading update now.... superboot didnt work on my nexus 7 (wifi).... :)
[Nexus 7 Android Development] armz_bey:
just tried to root my n7 this morning.... did it twice... i didnt get superuser icon... so i tried to download and when i tried to choose update binaries it says "gaining root access Fail!... :( same thing with busybox... it say my device is improperly rooted im still trying to root now...any suggestions on what i could have been doing wrong im on 4.4 now bl unlocked tnx
[Nexus 7 Android Development] WugFresh:
I am guessing that you selected the Wrong N7 device or have a connectivity issue in which case you should try an alternate port.

{{ WugFresh }}
[Nexus 7 Android Development] WugFresh:
I will see if I can reproduce the problem or determine what is causing it for you. Thank you for reporting it.
[Nexus 7 Android Development] kywildcat:
nevermind
[Nexus 7 Android Development] koki1975:
Restore action

I have G Nexus and just made a nandroid backup thru GNRT. When I tried to restore it by clicking Restoring Nandroid Backup w/custom recovery, nothing is happening. I presume I should be offered to choose what I want to restore or something like that.

Any thoughts on this.

Beside the thing I explained the app is great and very useful.

Thanks and cheers.

EDIT: Just saw the same issue reported two posts back so I am sorry for repeating the same question. Hope to get some answer.
[Nexus 7 Android Development] niav:
Hi Wug, thanks for the great toolkit. I have a problem though.

Tonight I got a notification for the 4.4 OTA on my Nexus 7. I was running 4.3 JWR66Y rooted with stock recovery. Having had issues with previous OTAs I decided to use the "Cleanup for permanent unroot" in SuperSU before accepting the OTA. The OTA installed fine but now when I attempt to root SuperSU does not appear in my app list. The rooting process seems to execute without issue, there are no error messages, but at the end there is no SuperSU on my device. Busybox however does get installed.

I have tried flashing the SuperSU zip that is in !ReadyToFlash through the Advanced Utilities. I get a success message in TWRP but when I reboot there is no SuperSU app installed.

I have tried installing SuperSU from the Play Store. It installs but after a few minues I get an error saying "SuperSU has stopped"

I would be very grateful if you had any advice as to what I should do? Thanks.
[Nexus 7 Android Development] bamaredwingsfan:
Thanks again, just did the update of my bootloader and it was a piece of cake.
[Nexus 7 Android Development] longreach:
Thanks so much for the WugFresh I'm glad to be back to stock so I can start 'tweaking' again.

I was unable to get the drivers working again properly after following the instructions in NRT, I had Adb but not file access. This helped me for my Windows 7 64 bit drivers:

http://xdaforums.com/showthread.php?t=1934306

Simple, but I couldn't get it working till I did this. I hope it hasn't already been mentioned a bunch of times, search is not working for me right now.
[Nexus 7 Android Development] Stransky:
Hi Wug

Thanks for a great utility. Just re-rooted my N7(2012) after OTA update to KRT16S without problems. Donation sent.

Stransky
[Nexus 7 Android Development] PLmorpheuz:
Hello

On my N7 (2012)

I want root my N7 on 4.4 KRT16S - but proces freze on

"Booting modifief boot.img to enable running privilaged commands.."

what i can do ?
[Nexus 7 Android Development] armz_bey:
thnx for replying sir wug.... but i tried 2 different pc's.. :( i selected wifi model 16s build and i tried any build too... im thinking of flashing to stock.and then try to root again
[Nexus 7 Android Development] niav:
Slightly bizarre followup to the above. I started my tablet today and noticed that one of my apps that require root, ClockSync, is working. So I use Root Checker and it tells me the device is rooted yet SuperSU and Busybox are not in my app list. Does anybody have any ideas as to what has happened?
[Nexus 7 Android Development] NLBeev:
It seems to me that you have used the OTA - update.

After an (OTA) update root access is no longer there.

It is difficult to say what happened. But you must have done a 'reroot' after the OTA update.

The best thing you can do now is flashing the update again, but now with the Nexus Root Toolkit.

Before re-updating it is usefull to backup your data that is in the "internal storage".
[Nexus 7 Android Development] niav:
Thanks for the advice. Just to clarify should I flash the OTA zip using the toolkit or use the flash stock and unroot option?