yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Android Development] williamlaw:
just tried to flash 4.3, failed.....bricked.....

but same method to flash back 4.2, succeeded....

why ??
[Nexus 7 Android Development] cammel:
Used this toolkit (1.6.4) to flash 4.3 factory image with no problems. Then root it using cf-auto-root (updated yesterday) from Chainfire and you're done! Piece of cake!

Enviado desde mi GT-I9300 usando Tapatalk 4 Beta
[Nexus 7 Android Development] jdagreek:
Nexus 7 (2013)

will you be creating a tool for the New Nexus 7 (2013)
[Nexus 7 Android Development] major payne:
I have recently gotten a new laptop (samsung) with USB 3.0 port only on it. I have tried using method #1 as it was the one suggested. It was not able to see the phone. I did want through all the steps. I did not try to other drivers though.

Anyone else using this on USB 3.0 and it works fine? Any help is appericated as I need to install the recovery as i forgot to install twrp or cwm the first time around. This of course prevents me from backing up and installing 4.3 any help is appericated
[Nexus 7 Android Development] danvee:
Once installed, I can move between 3.0 and 2.0 with no issues.

On another install, again, no issue with either port. On one, method #4 was the best way.

If you're rooted, GooManager will install TWRP, and ROM Manager will install CWM.
[Nexus 7 Android Development] WugFresh:
This tool will always be updated to support all nexus devices and I will continue to streamline my code to make the updating process more fluid.

I am working right now in a lab, when I get back later I will code through the night to finish v1.6.6. I got most of it done yesterday, there are just a few more things I would like to clean up and code.

{{ WugFresh }}
[Nexus 7 Android Development] tu3218:
So is it best to just restore to stock, accept the 4.3 ota, then be ready for your update of the toolkit to root 4.3 again? Also does the bootloader relock when we go back to completely stock to accept the ota?
[Nexus 7 Android Development] cammel:
No, your bootloader will not relock unless you manually do it.

Enviado desde mi GT-I9300 usando Tapatalk 4 Beta
[Nexus 7 Android Development] Toronadian:
Exactly what I wanted to ask. Wondering the same thing.
[Nexus 7 Android Development] dragxdk:
hi i search the zip ota 4.3...i find nothing about that... :(

tapatalk
[Nexus 7 Android Development] Tipkaros:
If you have the 1.6.5 version of the toolkit (which I got from having 1.6.4 from before and just running the in-built application updater) there is no reason to do that. You can just pick the "flash stock+unroot" option and choose android version 4.3 when presented with the question. It will download the factory 4.3 image and flash it onto your device. Bootloader will remain unlocked, though you will lose all user data and internal storage so be sure to back that up. After that you can try the rooting, it worked for me but not right away, check a few pages back for my post about the issue.
[Nexus 7 Android Development] Anderson2:
Will it really provide root in 4.3? I read elsewhere that root is broken in 4.3. Would forcing it create other problems? Won't upgrade till I know root is possible.
[Nexus 7 Android Development] danvee:
Wugfresh says that, as I'd posted, 1.6.6 will provide root capability.

He said it. I'll take his word for it.
[Nexus 7 Android Development] bsoplinger:
Don't kill yourself on our account, what you've done already is appreciated. Sleep in and fix it tomorrow. Enjoy your weekend.

Either you misunderstood what you read or what was there was misleading or unclear. The changes made to 4.3 for better security broke the way root used to work. However Chainfire, the developer of SuperSU, has created a new way to handle root operations for 4.3 that works. You can get all the info in the SuperSU thread here at XDA in the application forum. He even provides links to more technical explanations of what was done and how he developed the method to get it to work for 4.3.

Sent from my Nexus 7 using Xparent Purple Tapatalk 2
[Nexus 7 Android Development] jdagreek:
Will 1.6.6 work for Nexus 7 (2013) ?
[Nexus 7 Android Development] danvee:
Only one person knows the answer, and he's coding that version right now.
[Nexus 7 Android Development] dragxdk:
i have flashed the new update but each time on cw, i have the same question, disable recovery yes or no fix ?

how to do for to fix that please?

tapatalk
[Nexus 7 Android Development] thereal_bigjake:
If you did or are planning on rooting with SuperSu then choose no or it will break root...
[Nexus 7 Android Development] dragxdk:
Yep, i loose my root access and my cw, i would like to flash them again but i can t with the ntk 1.6.3 because i m on android 4.3 now... :(

please help
[Nexus 7 Android Development] thereal_bigjake:
Just use fastboot to flash TWRP it's pretty easy.
[Nexus 7 Android Development] TahrirSquare:
I believe it actually downloads it from the official google link , places it in a folder and flashes it for you if you chose to restore back to stock.
[Nexus 7 Android Development] FiveOhFour:
Check it out yourself! That shouldnt sound negative, its a ringing endorsement of one of IMO the best features of this tool, everything you may click comes up with a little info bulletin further outline the process that lies ahead, its safe to explore to a satisfying degree without having a device plugged in, and if you need it plugged in you can almost always just unplug while its rebooting before any processes have completed though thats unadvisable. Normally we have to worry about knowing what the next step is before we even click to be sure we are prepared for all the possibilities but this tool remains powerful yet simple enough with clarification at each step, the little clarifications are my favorite feature. Anyway when you click and then click ok to start another window comes up asking you if you have your own source locally or if you want to downlaod the stock 4.1 for the asus tablet.

Capture
[Nexus 7 Android Development] nicksoph:
Point taken and I can see why we might think of them as fickle but I think the vagaries are discoverable here. If tjose with a working 64bit windows system that used the pdanet or 0.7 drivers is showing the same drivers then the field of that doubt just gets bigger so it would be nice to know.

If ANYBODY is running win64bit and has this working on a nexus 7 would they have a look at their drivers using USBDeview and compare them to thses

18d1	USB Composite Device	Google Inc.	Microsoft USB Generic Parent Driver	6.1.7601.17586	usbccgp.sys

18d1	Nexus 7	Google Inc.	6.1.7600.16385	WUDFRd.sys

18d1	Google Nexus 7 ADB Interface	Google Inc.	Android USB Driver	4.0.0.0	WinUsb.sys

Thanks again

nick
[Nexus 7 Android Development] Jiggavolt:
64 BIT WINDOWS 7 USERS:

I was able to make it work. Until a fix is implemented, this is how you do it. I'm on an i7 machine with Win7 Pro x64. Here's what I did:

1. Use USBDeview as instructed to remove all drivers.

2. Use the Universal Naked Driver to install the Nexus ADB interface.

3. Unplug device, restart computer.

4. Once restarted, plug device in.

5. Open the toolkit.

Now, go through the "Unlock" and "Root" scripts. The problem is, the scripts don't know when to "move on" during each ADB event. So, every time a status box pops up, wait for 60 seconds. If it disappears by itself, great (this should happen during fastboot checks). If it doesn't disappear after 60 seconds, it's finished that script and is "hung up". Press Ctrl+Shift+Esc to open Task Manager. On the Processes tab, sort alphabetically and kill the "adb.exe" process. The toolkit status box should disappear and move on; if it doesn't after another 30 seconds, kill the process again. Eventually the script will move on.

Do this throughout the entire process, and eventually the scripts will complete and your device will be rooted!
[Nexus 7 Android Development] nicksoph:
Agreed. It is a lovely toolset and well explained from the first step.
[Nexus 7 Android Development] FiveOhFour:
Sorry i thought you were in this conversation at that point as well, yes its been confirmed by many to work in 64 bit, surely you have read posts of people with success in 64 bit even on the previous page. I posted early on when wug initially posted the PDANet drivers that was the only way to get the tool to work on 64 bit machines. All i had to do for my setup at least was to uninstall the drivers that were auto installed, open the PDANET folder wug linked to ( i didnt use the naked driver link i used the pdanet) and installed the 64 bit installation .exe and at that point i had a functioning tool. You may have to go in device manager and click update driver and do a restart to let windows update do its thing but those drivers do work

---I am not quite sure what you mean when you say if those with x64 are using the same drivers then the field of doubt gets that much bigger so im not sure how to or if i have a response. they are and arent the same, they are 64 bit versions obviously, i had to run the 64 bit .exe to have success, ill grab my 64 bit machine in a moment and verify what the drivers show up as for you but for now i can verify they are the drivers from the wug added a couple pages into the thread
[Nexus 7 Android Development] nicksoph:
Please be aware this is the same thing as has been discussed as two adb.exe's and because we dont really know where the two threads are coming from it might be making the process more risky.

ta

nick
[Nexus 7 Android Development] danny8:
I want to root my new Nexus 7 using this software. I have a choice of using two Windows computers; an older version running 32-bit Windows XP Pro, or a newer computer running 64-bit Windows 7 Pro.

Should I choose the older machine just to make life easier?
[Nexus 7 Android Development] zedorda:
No one knows? Anyone even try with this build?
[Nexus 7 Android Development] WugFresh:
Just a hunch. For all of you who are saying that the toolkit is spawning two instances of adb for you; do you have the SDK installed on your machine?

My guess is that adb is added to your systems path variable and although my program is pointing to the local file, the globally accessible adb gets spawned as well causing the problem.

This is just a guess by the way, but if it were true, the solution would be for me to rename adb and fastboot to adb-wug.exe, and fastboot-wug.exe.

To confirm whether or not my theory is correct, temporarily rename adb.exe in your sdk folder.

This makes way more sense than drivers. Why would drivers have anything to do with the toolkit spawning two processes. My guess is that the they are fixing it because it allows the first instance to get resolved more quickly, before you get hung up.

{{ WugFresh }}
[Nexus 7 Android Development] FiveOhFour:
Yes, it works fine sorry i thought i saw a reply to that, many including myself have used it succesfuly with 3D, just keep 3C selected

---------- Post added at 01:14 PM ---------- Previous post was at 01:10 PM ----------

Either way, whatever is more convenient, either way it seems best to download the drivers that is pointed to under "drivers tip" in the OP, its pointed out as for 64 bit but just download it anyway and in that folder is a 64 bit installer and a 32 bit as well, for most ppl regardless of architecture this manual driver install is the way to go, you can try the auto install included in the tool first, but whichever machine you pick its likely to need the manual install

---------- Post added at 01:18 PM ---------- Previous post was at 01:14 PM ----------

Wug just to clarify, its not actually opening two windows showing the ADB check, its just in task manager it shows two ADB.exes open up while one at least for me closes in a few seconds and one stays open. I at the moment fail to see what it matters, its displaying this behavior for all it seems regardless of success or failure. Is there something im missing in re: to that that necessitates throwing up multiple "disclaimers" and warnings because it shows two running.

---------- Post added at 01:21 PM ---------- Previous post was at 01:18 PM ----------

I cant understand this and you seem to be vague about it while implying that there is some risk that you have knowledge of. Is there any merit to what you are implying here, if so it deserves elaboration or are you simply saying that its been unsuccesful for you and you think the reason has something to do with it showing two adb.exe's and you feel that this poses some risk that hasnt been adressed? Im trying to understand which is why i was talking to you about it and then you threw me off when you just reposted this sentance again by itself
[Nexus 7 Android Development] nicksoph:
ah - what i was trying to ask was - Are the drivers that I am reporting, the drivers that they have installed and working - the right drivers? Just trying to
[Nexus 7 Android Development] WugFresh:
I understand that. But if it's running two instances in task manager that means something is wonky. It should only take one instance.

I just had another idea.

In the toolkit open the manual input and type adb start-server

Now don't plug your device in and run the Unlock script. Tell me if it still stalls on you.

{{ WugFresh }}
[Nexus 7 Android Development] FiveOhFour:
Nope, when run that way it throws up a notification similar to the fastboot one like we discussed yesterday
[Nexus 7 Android Development] cwc3:
Worked perfect here. Windows 7 x64. Be sure to select JRO03C if your on JRO03D. Followed Guide, manually updated driver, no problems.

Thanks for your awesome tool.
[Nexus 7 Android Development] nicksoph:
Firstly sorry for the double quote.

In an earlier post I explained that I had used the toolset to unlock,root and flash a nexus 7 although each time I ran the program it seemed to hang. I reported that I noticed each time adb.exe was called, two instances would appear in the Task manager window and that once one of them ended if you killed the other process, the toolset would carry on and all the functions seemed to work. You have reported something similar.

In mentioning this method I thought it important to add that I was not sure what was going on here - it wasnt simply adb.exe hanging - there were two processes being spawned, one of which we know nothing about so I think a word of caution in ignorance wasn't too amiss.

nick
[Nexus 7 Android Development] FiveOhFour:
Ok i thought thats what you were asking just couldnt tell if there was something you were trying to imply as well sorry, took me a minute cuz i had to grab the other computer and all but here is a screenshot of all my drivers on the 64bit laptop that unlocks and roots fine for me.

drivers screen
[Nexus 7 Android Development] WugFresh:
Haha. Then that is the solution. Wow. It is always the little things.

Ok. Let me explain.

So, when you start adb for the first time, it goes through all of that starting daemon blah blah...

Well my toolkit is running string checks on the output, but its looking for patterns it doesn't recognize because the first time your run it, it outputting that daemon stuff. That is why its getting stalled.

The solution: Simple. To run adb start-server in the background when you start the toolkit. That's it.

For now. Everyone who is having stalling problems. Please restart the toolkit. Open manual input, and type adb start-server

Then proceed to use the tools. I bet it works with the autodrivers that weren't working before for some people.

{{ WugFresh }}
[Nexus 7 Android Development] FiveOhFour:
Ok i understand, thats what i thought you were saying but im not proficient in programming at all, so i wanted to be sure that was indeed what you were implying because its not just common knowledge for me.
[Nexus 7 Android Development] nicksoph:
I just tried :-

pluged in nexus

In the toolkit opened the manual input and type adb start-server

then went to Step 4 Tab- List All ADB devices

And it worked!

Upuntil now listing the adb devices always threw up two adb.exe's

Progress Im sure - I wish I knew what it meant
[Nexus 7 Android Development] CBers:
Just did my Nexus 10 using Wug's toolkit (v1.63).

Manually downloaded TWRP (v2.6.0.0) & SuperSU v1.43 zip.

Changed Recovery Image to v2.6.0.0.

Installed TWRP via toolkit (ROOT button) then flashed SuperSU zip when TWRP started up.

All rooted again :cool:
[Nexus 7 Android Development] dragxdk:
tx cbers

it works :D:thumbup:

tapatalk
[Nexus 7 Android Development] coradux:
With Nexus Root Toolkit 1.6.4 you choose your tablet and Android Version (including 4.3) and Root.
[Nexus 7 Android Development] dragxdk:
yep

:thumbup:

tapatalk
[Nexus 7 Android Development] WugFresh:
Question for you and any other N10 users running 4.3. Are you able to successfully temporarily boot into TWRP?

You can use the toolkits boot temporary "Custom Recovery" button in advanced utilities to test it.

{{ WugFresh }}
[Nexus 7 Android Development] ThurstonX:
4.3 with custom kernel goodness :)

Ditto. Thanks for the ideas. 1.63 set to "any" version of Android worked like a charm. I first used it to flash the stock recovery, after I restored the stock kernel (using this one so I have access to CIFs mounts). Then I used it to flash TWRP, and finally the latest SuperSU Pro. After that I could unplug and flash the kernel and modules to get back in business.

I should mention that I wanted to do the OTA, since it was already downloaded to my Nexus 7, and the little icon was bugging me :p

Cheers.
[Nexus 7 Android Development] CBers:
No, I don't believe it worked.

I chose Nexus 10 and any build.

I manually downloaded TWRP 2.6 and SuperSU v1.43.

Installed TWRP via root button, rebooted to TWRP and flashed SuperSU.
[Nexus 7 Android Development] ThurstonX:
No, I didn't mean 1.63 automated the process, just that it was usable after applying the 4.3 OTA. I downloaded the flashable zips of TWRP and SuperSU. I copied TWRP zip into the NRT's folder for that, then used the Advanced options to flash it.

Sorry for any confusion.
[Nexus 7 Android Development] ryfly65:
I have the Nexus 4 and I have used this Toolkit to root my phone in 4.2.2. After 4,3 was released, I sideloaded it to my phone, and reset my phone to factory, and cleared the cache in recovery mode. When I try to root my phone again, using the root tool in your toolkit, my phone stays on a blank screen and eventually I receive a message telling my that my phone has timed out. It always switches to the blank screen when the toolkit says, "Booting TWRP temporarily" ... "Rooting" ... "Waiting for your device." At this stage, my computer says it is connected just fine, but your toolkit stays at "waiting for your device." and then eventually pops up with "Waiting for device operation timed out." Am I doing something wrong?
[Nexus 7 Android Development] CBers:
Sorry, I was replying to wug - looks like out posts crossed :)

Glad you're all sorted though.
[Nexus 7 Android Development] WugFresh:
No, you are not doing something wrong. It appears that the neuxs4(mako) TWRP 2.6.0.0 doesn't fastboot boot properly on 4.3. In v1.6.6 this will be avoided by just flashing TWRP and booting into it, and if the user doesn't have custom recovery checked, then after the root procedure, the stock recovery will get automatically re-flashed.

When Team Win updates the recovery to allow for fastboot booting on the N4, the toolkit will revert to the old method.

Stay tuned for v1.6.6 or just flash TWRP, and use the quick tools, reboot recovery to get into TWRP and flash the zips. Cheers.

{{ WugFresh }}
[Nexus 7 Android Development] ryfly65:
Okay gotcha! So just wait for 1.6.6? --Which will force flashing and booting into TWRP and reflash stock?
[Nexus 7 Android Development] ALD3:
Updated to 4.3 using Toolkit 1.6.4 and rooted with no problem. Copied SuperSU to tablet before and then flashed with TWRP 2.5.0.0, then flashed IMG of TWRP 2.6.0.0 with Toolkit 1.6.4. All went well but as always for some reason the toolkit has never restarted my Nexus 7 32g into fastboot or from fastboot to restart. Always had to do it manually when toolkit says waiting for device.
[Nexus 7 Android Development] starfighter1948:
i tried flashing several supposed superSU.zip solutions from the web for my Nexus 7 running Android 4.3 using an existing CWM recovery image, but most failed with bad package, and the one that did run to completion didn't work. However using the toolkit to install the latest version of TWRP which it downloaded for me, and downloading Chainfire's superSU.zip from his site (http://download.chainfire.eu/204) directly to the tablet everything works fine.

starfighter1948
[Nexus 7 Android Development] r00t4rd3d:
You should be getting SuperSU from this thread, currently on version 1.45:

http://xdaforums.com/showthread.php?t=1538053
[Nexus 7 Android Development] doncaruana:
site down?

Anyone else having trouble getting to wugfresh's site? I get an error that the site is on the cloudfare network and can't be resolved...
[Nexus 7 Android Development] r00t4rd3d:
It comes up for me, just really slow.

He posted this in the comments:
[Nexus 7 Android Development] markwebb:
New Build: JWR66N

New Build: JWR66N????j Just got my new Nexus today.

Never mind, I see that IS the current new build. Odd. As soon as I booted up Nexus, it downloaded that build. I am confused. :) I thought it was already pre-loaded.

Another update: JSS15J So, am really confused. LOL
[Nexus 7 Android Development] ShaneAR:
That's normal. Updates were issued by google...

http://www.androidcentral.com/new-nexus-7-receives-two-updates-launch
[Nexus 7 Android Development] vicw:
The is cause to celebrate that you own a Nexus - updates will come rapidly, no more waiting for months for the manufacturer to finish testing and adding his own code.
[Nexus 7 Android Development] Toronadian:
So I'm trying to use the toolkit to flash stock and unroot to 4.3, but when I do that, it goes into fastboot mode and just stays there while on my computer in a window when the scripts are running it says that I should wait for it to run reboot by itself. I waited but nothing happened.

I just restart my phone for now, can't seem to get the 4.3 update to work for some reason.
[Nexus 7 Android Development] usmaak:
It's been a while since I've done anything with this. I used this to root my N7 back in January, and haven't touched it since. I have 1.62. When I launch it and select to update to 1.64, I get a Hashcheck: Mismatch message, and it won't update. I tried downloading from the link in the first post, and the page never came up. Any ideas on what I can try next?
[Nexus 7 Android Development] rickvnl:
Tried this? http://d-h.st/mUa
[Nexus 7 Android Development] ThurstonX:
Thanks for making it available.
[Nexus 7 Android Development] caanda45:
Is the toolkit good or will be good for rooting/unlocking the bootloaders for the N7 2013 edition?
[Nexus 7 Android Development] usmaak:
It was really slow, but it did finally complete downloading. Thanks!!
[Nexus 7 Android Development] doncaruana:
FWIW, I used 1.64 to reroot my stock 2012 N7 after I goofed and took the OTA. It was still unlocked so I had no issues. Also, as an aside, I finally got my Win7x64 machine to see the N7 by forcing the raw google drivers. Nothing else worked - and I tried all of them.