yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Android Development] ThurstonX:
Yeah, that's how it works. Windows Explorer will only show you /sdcard (which itself is just a symbolic link). You can't see /data/media/0 unless you use adb shell to connect, or using ES File Explorer. But I'm pretty sure TWRP under both is a hard link to the same actual data (inode; nevermind if you don't know). So basically /sdcard/TWRP and /data/media/0/TWRP point to the same "place" in the internal storage. Otherwise there would have to be two sets of the same data, and that's simple not practical. So theoretically you should see exactly the same files under /sdcard/TWRP and /data/media/0/TWRP

The big problem with using Windows Explorer to view the contents of the Nexus is that it doesn't always show all the files. I've been through this, and the best advice I can give is to...

kill the adb shell, as needed

safely eject the Nexus

unplug the USB cable

reboot the Nexus

plug it back in

navigate back to Nexus 7\Internal storage\TWRP\BACKUPS\<Unique Device ID> in Windows Explorer.

If the files still aren't visible, you can try the adb pull command. Something like

adb pull /sdcard/TWRP/BACKUPS/<Unique Device ID>/<backup folder name> SOME_NEW_FOLDER\

That'll create the folder SOME_NEW_FOLDER on your PC in the same place where adb.exe lives, so name it appropriately (try not to use spaces), and then pull all the files into it. Just run it from wherever adb.exe lives. Not sure if you'll need to change the permissions to make it work.

re: SuperSU, you said:

"Also when i run the adb shell SuperSu on the nexus asked for root permission (adb shell) which i granted"

I've never seen that when executing adb shell from the PC, but in SuperSU's settings I have the default action set to GRANT, so I never get prompted.

What I meant by the rest of it was, first run the chmod -R 777 /data/media/0/TWRP command from adb shell (make sure you're running it AFTER typing su Then run ls -al /data/media/0/TWRP That will list the contents of the TWRP directory, and its immediate contents. You should see something like

1|root@grouper:/ # ls -al /data/media/0/TWRP
ls -al /data/media/0/TWRP
-rwxrwxrwx media_rw media_rw 1359 2013-08-04 12:48 .twrps
-rwxrwxrwx media_rw media_rw 7 2013-02-15 12:14 .version
drwxrwxrwx media_rw media_rw 2013-02-01 11:23 BACKUPS

rwxrwxrwx = 777

That'll tell you the chmod command worked. You could always check the permissions before running the chmod command. Again, use ls -al /data/media/0/TWRP and note the permissions. If they're not already rwxrwxrwx, then you need to use the chmod command.

The last thing I can think of, if none of the above helps, is to download and install the latest Android SDK. I'm using adb.exe from it, not from the toolkit.
[Nexus 7 Android Development] WugFresh:
Just to clarify the adb.exe and fastboot.exe in the toolkit are the same as the sdk.

{{ WugFresh }}
[Nexus 7 Android Development] ThurstonX:
Great! I assumed as much, but didn't want to state that assumption :)
[Nexus 7 Android Development] twinkyz1979:
ClockworkMod just updated superuser to version 1.0.2.1 just so you know
[Nexus 7 Android Development] WugFresh:
Cool, I will get that uploaded asap.

{{ WugFresh }}
[Nexus 7 Android Development] nemesi54:
I really really dont know what to say........

All the laws of android are no use at my Gnex....:eek:

Another thing is that when i highlight the file with Es Explorer and choose -properties- i get:

Readable: Yes

Writable: Yes

Hidden: No

C:\Program Files\WugFresh Development\data>adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
shell@maguro:/ $ su
su
root@maguro:/ # chmod -R 777 /data/media/0/TWRP
chmod -R 777 /data/media/0/TWRP
Bad mode
10|root@maguro:/ # ls -al /data/media/0/TWRP
ls -al /data/media/0/TWRP
-al: No such file or directory
BACKUPS
1|root@maguro:/ #

I also tried the WHOLE path.....

C:\Program Files\WugFresh Development\data>adb shell
shell@maguro:/ $ su
su
root@maguro:/ # chmod -R 777 /data/media/0/TWRP/*
chmod -R 777 /data/media/0/TWRP/*
Bad mode
10|root@maguro:/ # ls -al/data/media/0/TWRP/BACKUPS/014*****************B/2013-08-11-
-01-44-37/
PS/014***********************B/2013-08-11--01-44-37/ <
-al/data/media/0/TWRP/BACKUPS/014**************B/2013-08-11--01-44-37/: No such fi
le or directory
1|root@maguro:/ #

FINAL EDIT: Eventually i managed to get the file to my PC ONLY through Wugs Toolkit and the -Pull- file Feature !!!!

I dunno how or what..I just pressed the button gave the path and the process started!!

After this and in the case that maybe one of the previous commands worked without me knowing it i tried the toolkit -Pull- feature to my Nexus 7 where i had the exact same issues....(without trying the adb shell commands)

Guess what...It worked there also..!!
[Nexus 7 Android Development] CodemasterRob:
Just download 1.6.8 so I could root my N4 after foolishly upgrading to 4.3 without looking for a root solution. The root option isn't working for some reason, despite my bootloader showing that the phone is unlocked. Root checkers are showing that the root didn't go through either.

Also, when I enter recovery mode I'm greeted by the Android with an exclamation mark in it's chest and "No command" written below it, which I never got before.
[Nexus 7 Android Development] ThurstonX:
Glad to hear you figured it out :)
[Nexus 7 Android Development] bricker1:
I had to run it twice but it worked

Sent from my Nexus 7 using Xparent BlueTapatalk 2
[Nexus 7 Android Development] john306:
Run it 3 times now for rooting 4.3 , it says its done but rootchecker says no root.
[Nexus 7 Android Development] nakedtruthishere:
Same here... No root after upgrading to 4.3 and no backup possible from any backup file made under 4.2.2. Stuck at animated X. Think, I´ll go back to 4.2.2 and wait for a working tool. Hope, the backup will work again with 4.2.2.
[Nexus 7 Android Development] hazwheel:
The tool IS working, the majority do not have the problems you are having. It must be something at your end.
[Nexus 7 Android Development] nakedtruthishere:
I'm not that sure, because I read a lot of complaints describing exactly the same issue: Rooted Nexus under 4.2.2 stuck when trying to upgrade to 4.3

Going from 4.2.1 to 4.2.2 was no problem at all, only root got lost and could be restored with the tool.

Now, trying to get 4.3, the ota update failed and it took several attempts to flash the stock ROM (with the tool) and although the tool says, the device is rooted, it isn't.
[Nexus 7 Android Development] evilgenx:
I came from 4.2.2 straight to 4.3 using this tool a couple of days ago. No problems, rooted just fine as well. Everything fired off and worked first try. I ran on my Nexus 7 (v1).
[Nexus 7 Android Development] Anderson2:
I'm one having no luck getting past the adb not found error when trying to root my nexus 7.2 (2013) with Wugfresh.

I suspect the problem may be with the windows 7 security settings. No matter which drivers I install through Wugfresh (universal, etc.) when I connect my new nexus 7.2 the Wugfresh toolkit says adb not found.

While waiting for skipsoft's toolkit to be ready,

1. I've gone through the Wugfresh toolkit process several times with no luck

2. (As recommended by some) I've disabled windows 7 setting to automatically update device drivers with no difference (so I restored that back to the default)

So, the Wugfresh drivers just don't install correctly on my windows 7 64 bit system possibly because a setting in windows 7 is interfering. I wish there was a log file to show where the problem is.

Is there a simple way to root manually for someone who doesn't know adb and Linux commands?

Thank you
[Nexus 7 Android Development] LordLugard:
Not to rub it in on folks having issues with Wug's toolkit, but I used it easily on Windows 7 running in VMWare Fusion on my Mac Mini, 2012 32gb WiFi 4.3.
[Nexus 7 Android Development] nakedtruthishere:
That´s a point, I have to think about, as I used a Win 7 this time, too. All previous root work has been done under XP.

To be more precisely in regards to my last post I suspect the SU app in the ROM to be responsible for my trouble with root, as when changing the root settings in ES File Explorer, it prompts the SU permission to come next, but it never appears. In consequence, the file explorer test for root rights fails - thus I don´t have access to the system folder.
[Nexus 7 Android Development] WugFresh:
v1.7.0 update package is now live. Updating my website with the new links and info shortly. Enjoy! ^_^

{{ WugFresh }}
[Nexus 7 Android Development] Anderson2:
I've not yet tried the new version but here is a thought that might explain why some of us are having trouble when testing for adb.

I noticed that when I usb connect my nexus 7 and 7.2 device to my windows 7 64 bit pc, that although the pc shows the usb as connected the nexus does not appear as a drive in the "My Computer" folder. That means the pc cannot access the nexus file system. They used to but that disappeared after deleting all earlier nexus drivers and installing those from Wugfresh.

Yes, usb debug is selected in the nexus device. I even unselected and reselected with no difference. So, maybe the Wugfresh drivers cannot access the nexus if some setting is incorrect or another driver is missing.

I'm not a programmer so this is just a thought for those who know more.
[Nexus 7 Android Development] xhepera:
Have those of you having trouble getting the device adb-recognized, have you tried switching USB mode from MTP to PTP? You'll have to uninstall the drivers under camera (or whatever it's called in win 7. I use XP). illogical but it worked for me
[Nexus 7 Android Development] txmanx:
Wug's NRT 1.7 on a new Nexus 7 FLO

Nexus 7 - FLO-32

Build JSS15J

Turned it on - let the Google Updates install (twice).

Started the toolkit - all ADB driver and Fastboot tests seem to work.

Unlocked without a problem.

I start to Root w/Custom Recovery - and find I have to press/hold the power button when it's "waiting on your device". Have to do this twice during the procedure.

Everything seems to complete... but no icon for SuperSU when I'm done... or BusyBox.

Any ideas where to go from here except the old method?
[Nexus 7 Android Development] WugFresh:
Please try an alternate USB port and repeat the process.

{{ WugFresh }}
[Nexus 7 Android Development] txmanx:
I read that suggestion on your website and tried that before posting here; it was the same. I ran all the USB driver tests; only thing I have not done is uninstall/re-install USB drivers for the device.

Thanks for the quick reply!
[Nexus 7 Android Development] theboywonder:
guys, having some MAJOR issues. this is the 3rd time ive tried this toolkit to lock/flash to stock

followed every step flawlessly (i think) and each time i get to the end of the process and i just end up at the recovery mode screen with nothing happening.

i can boot back into the phone manually but im still unlocked/rooted and still have the custom ROM on there. like it didn't do anything at all.

please help, i need to get the device back to stock as soon as possible.

thank you.
[Nexus 7 Android Development] danvee:
This forum is for the first Generation Nexus 7.

Is that what you have, or do you have, as you stated, a phone?
[Nexus 7 Android Development] theboywonder:
ah, no i have a gnex. i apologize.
[Nexus 7 Android Development] WugFresh:
No worries. Are you certain that you selected the correct gnex device and build in the toolkit.

{{ WugFresh }}
[Nexus 7 Android Development] thehavock18:
website down? Have an alternate location to download the toolkit?
[Nexus 7 Android Development] WugFresh:
Yeah.. I am literally going to pull my hair out dealing with my host. :mad:

Here is a download link: http://goo.gl/R8cauh

{{ WugFresh }}
[Nexus 7 Android Development] thehavock18:
Thanks!! Sorry about your host :(
[Nexus 7 Android Development] WugFresh:
:) Looks like I am back up and running again. And the updated changelog is now posted as well: http://www.wugfresh.com/nrt/changelog/

Cheers.

{{ WugFresh }}
[Nexus 7 Android Development] luonchinguoc:
Try to change USB connection from MTP to PTP. It works with me. And also install ADB Installer independently after runing Step 1 with NRT.
[Nexus 7 Android Development] ronf1011:
file teansdwr

All I want is to move files not pix, from my PC to my N7 2013. Is there a solution? Other than using the cloud, like the Google "tech" told me. My older N7 was so much less complicated.
[Nexus 7 Android Development] melfunn:
I got my use MTP by using the suggestion on this post from a different thread on xda.

http://xdaforums.com/showthread.php?t=
[Nexus 7 Android Development] barbo:
You might like this app (get at the play store):

"WiFi File Transfer"

You run it on your tablet then open a browser and move anything you want back and forth. It works great.
[Nexus 7 Android Development] Anderson2:
Have you tried es file explorer? If your pc and tablet are on the same wifi you can use it to move files through your home wlan.
[Nexus 7 Android Development] eliboy:
Hi!

Can i use this tool to backup my data, unlock bootloader + root, then install any ROM i want, then restore my data without loosing anything?
[Nexus 7 Android Development] MDCWLK:
Yes you can :)

Verstuurd van mijn Nexus 7 met Tapatalk
[Nexus 7 Android Development] mentallo:
Please delete
[Nexus 7 Android Development] d4c:
Hi All,

I am having issues reverting back to stock. I have TWRP as recovery and CM 10.2 nightly installed. I have downloaded the Google factory image and have successful adb connection, my only issue is that the NRT does not extract the file google file to allow for flashing? Can anyone provide any help?

*EDIT* Seems as though downloading automatically and flashing has worked. Still unsure as to why the program would not let me download the image first and then flash? Maybe you can look in to this Wug? At least then we can rule out if its my end or yours that has the issue?

Thanks
[Nexus 7 Android Development] MDCWLK:
I've had the same problem. In NRT there are two options you can choose from --> (1) My nexus is normal/on (2) softbrick

Ive ticked the "bricked" option and the ROM flashed without any problems. Hope it helps for you too :)
[Nexus 7 Android Development] d4c:
I seem to have fixed it by allowing NRT to download the file for me. I tried downloading both JDQ39 and JWR66V and tried to flash via NRT but to no avail. Maybe Wug will find a fix for this soon?
[Nexus 7 Android Development] WugFresh:
You can certainly download it on your own. In the flash stock interface you just have to select "other/browse" and then select the tgz factory pack you downloaded. The factory packs are here:

Google Code - Factory Image Packages

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

I did do that but when it gets to the part of un packing the file it sort of skips the process goes to the black screen where it should go through the process of flashing but skips directly to the end where it tells you about it boot looping etc.

Hope that helps...
[Nexus 7 Android Development] CBers:
Looks like there's a new JB 4.3 update that's been released in the last 24 hours.

The build is JWR66Y - seems to be security fixes only.

Just received it on my Nexus 10.

For reference:

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

http://www.androidcentral.com/android-43-jwr66y-security-update-landing-some-nexus-phones

http://www.androidpolice.com/2013/0...date-may-also-be-rolling-out-to-the-nexus-10/
[Nexus 7 Android Development] ThurstonX:
Just wanted to note:

the JWR66Y update became available for my Nexus 7 OG today, so I went ahead and installed it, after restoring the stock kernel (boot.img). Forgot to restore stock recovery, but it seems that wasn't needed, as TWRP went away.

In the Toolkit I identified my device as running JWR66V, then flashed TWRP 2.6.0.0, rebooted just to be sure, then booted back into TWRP to flash SuperSU (1.45, cuz I needs me some CIFS support ;) ... and SuperSU complained it needed the binary). Finally I flashed vorcers' kernel to get CIFS support back.

I've been doing more stuff via the Android SDK, as I like to understand the nuts and bolts of what I'm actually doing, but since I donated to Wug's awesome efforts, I like to use the NRT, too :D

So, if anyone has any doubts about taking JWR66Y (assuming you're on JWR66V, I reckon), it worked fine for me.

Cheers (and beers for Wug) :highfive:
[Nexus 7 Android Development] WugFresh:
I will try to reproduce the problem.. But I have never had that happen. Can you tell me exactly which factory img you used.

{{ WugFresh }}
[Nexus 7 Android Development] d4c:
Yeah sure I tried it with both JDQ39 and JWR66V both downloaded via the links provided in the NRT. I was also using the latest edition of the NRT program 1.71.
[Nexus 7 Android Development] r00t4rd3d:
Whats up with 4.3 JWR66Y? Does the toolkit still work on this version?
[Nexus 7 Android Development] ThurstonX:
Read a few posts back. I updated to 'Y' then used the toolkit (set to 'V') and was able to do all the things I describe.
[Nexus 7 Android Development] fairxda:
Yes. I can confirm. Thanks for your successfull try ...
[Nexus 7 Android Development] WugFresh:
Its now officially added. I uploaded everything last night and updated the masterlists. :)

{{ WugFresh }}
[Nexus 7 Android Development] d_phekt:
Tried this toolkit to flash stock JWR66Y. It failed to flash and now all I have is bootloader mode since it wiped everything. Boot failed.

Edit: Got it figured out.
[Nexus 7 Android Development] crisvillani:
same for me how did you fix this?
[Nexus 7 Android Development] mssam:
Man, you move fast! Just updated to JSS15Q with no problems. Everything still working as expected - smooth! :good: Thanks again Wug!
[Nexus 7 Android Development] porkovich:
Hi i also "blicked" the device using the latest tool - after unlock , i wanted to flash stock - using the latest image, now i hang at erasing userdata , and that's all. Is there a way to restore the device, fastboot is working fine but ...

So i manage to fix it , i am not sure where the problem is , it's ether in the 1.7.1 version or in my USB cable/port, but after changing ports i managed to install the Y update. After that root was a problem too, but restarting the app did the work ... so ?? .
[Nexus 7 Android Development] nirco68:
N00b question: i have the JWR66V. Did root only without custom recovery, just as the root process ended, got the ota notification for JWR66Y, the update failed, got the little Android with Exclamation mark, needed to press the power for ten seconds for restart, mobile showed message upgrading android and updating applications however it went back to JWR66V.

Now i don't get the ota again :(

Do the tool make any modifications in stock file system that might prevent the OTA? , or i should wait for it?, i prefer to upgrade via OTA

Thanks for your support!
[Nexus 7 Android Development] hazwheel:
Funnily enough, I'm rooted with twrp, got the update notification, thought to hell with it and clicked on it and it actually updated to 66Y, but lost root and installed stock recovery! Obviously I have rerooted and installed twrp again. It ran the open recovery thingy and worked, which I never expected, I expected it to fail

EDIT: this was on my N4 BTW
[Nexus 7 Android Development] Locutus5382:
Site for downloading 1.7.1 is down.
[Nexus 7 Android Development] ed33:
Have same problem, did anyone find a answer to this?
[Nexus 7 Android Development] theguru1974:
Alternate location to download:

http://www.afterdawn.com/software/system_tools/manage_external_devices/nexus_root_toolkit.cfm

Nevermind. This is a crappy download manager thing - don't use this. I'll keep looking.

---------- Post added at 09:04 AM ---------- Previous post was at 08:43 AM ----------

Use this, worked like a charm:

http://www.softpedia.com/progDownload/Galaxy-Nexus-Root-Toolkit-Download-213077.html
[Nexus 7 Android Development] MicheleFrost:
Done and got it but it cannot download custom recovery -

neither CWM nor openRecovery.... any hints on where to find the images directly so I will not have to find it out by myself? :D

UPDATE: nevermind, found cwm images download page at: http://clockworkmod.com/rommanager
[Nexus 7 Android Development] ZombieUsr:
So I have update to 1.7.1 of the toolkit. I have looked over the past few posts of this thread and have read several different threads on the "How"...If anyone can PM me that would be great. What are the steps I need to update to 4.3? What are the files?

For my N4, I flashed the bootloader, radio, rom and gapps...

For the N7 (2012) what are the steps. I have found nothing as of yet. Thank you
[Nexus 7 Android Development] Christian72D:
I unlocked and rooted my N7 3G with this tool and all looked good.

But SOME apps tell my my phone is not rooted.

ClockSync works, SystemAppRemover tells me my device is not rooted.

What can i do?
[Nexus 7 Android Development] porkovich:
After going here and there with different roms i returned to the stock 4.3 , but the process failed (because of a usb port) so i reflashed. The bootloader is 4.23, it's the one i got with the first install of 4.3. If the bootloader is the same as the one coming with the Stock Rom, does the script override it ? or no. I ask because i see e message during the install (looking at the Command Promt) that after pushing the bootloader version it fails to install because of some state ? Is this normal behavior ? the process finished and all is working ? but i am curious.
[Nexus 7 Android Development] tamanaco:
I just updated my ROM using the Back to Stock + Unroot function of the toolkit which actually flashes the JWR66Y factory images and wipes the phone. I tried Unrooting the phone using the Full unroot function of SuperSU 1.51 and reinstalling the Stock Recovery using the Toolkit. But I have not been successful re-installing the Stock Recovery with the past couple ROM releases. No matter what, I always end up with a dead Android with a red triangle. So, I backed up everything, saved my Titanium backup folder to the PC and used the Back Stock option of the toolkit. Not complaining... all is fine and dandy, but this full wipe process and restore takes a long time. Is there a possibility a Non-Wipe option to flash back to stock will be available with this toolkit in the future? With other Android devices, some time after the Factory Images are available Non-Wipe back-to-stock with root injected are made available. Just wondering why this is not doable on the N7. I'm probably missing something obvious and feel like I asked this question before, but forgot the answer.
[Nexus 7 Android Development] jolaviska:
Can't access the update server from the tool. Is it going to be fixed?
[Nexus 7 Android Development] Sloth:
I used it yesterday :confused:
[Nexus 7 Android Development] jolaviska:
I currently have Nexus 4, 4.2.2 JDQ39, root with TWRP 2.42

Updating the OTA 4.3 through phone did not work and stuck on TWRP screen.

What is the best way of upgrading to 4.3 and still keeping the custom recovery and root?

(I tried manually flashing the 4.3 update from here: http://xdaforums.com/showthread.php?t=2145848 but TWRP failed to flash it..)
[Nexus 7 Android Development] WugFresh:
Read FAQs on my site.

{{ WugFresh }}
[Nexus 7 Android Development] nweaver11:
I did, but I am still kinda confused. I'm running Purity. But when I run your program, my tablet is not recognized. Any ideas?
[Nexus 7 Android Development] JackMetal:
OK, I have a dumb question. My Nexus 7 (2013) is at build JSS15J. I've seen other builds (JWR66Y for example). Is there a list of all these builds and what the differences are, etc..?? I'm guessing some of it has to do with country, and other things?

Also - I just saw a notice pop up on mine for another update (still 2.3.0, so I'm not sure what it is).. I attempted the update and it just booted to recovery (TWRP), so I rebooted and from what I can tell it didn't apply the update. So....my plan was to move back to the stock recovery and see if the update pops up again. If it doesn't, what options do I have to get the latest?

Thanks!!!