yashsingh1/xdaforums huggingface dataset:
[Nexus 10 Android Development] garnet&gold:
Thanks. I just tried it with both the firewall and AV turned off., unfortunately, I still cannot access the NRT updater. I have noticed one other program, Evernote, is also not connecting to its server even with the firewall and AV off, but it connects fine over the web and thru my other devices. All other programs seem to connect fine. and I can access the web through Chrome and Firefox without issue. I have re-booted, uninstalled and re-installed both programs without any luck in getting connections. So, I don't believe it is an NRT issue, but I cannot figure out what is affecting the two of them only.
[Nexus 10 Android Development] WugFresh:
Can you try reinstalling NRT with your AV off, or check its quarantined items and add an exception. Maybe it quarantined Wug_updater.exe during the install, so temp turning it off did nothing.
[Nexus 10 Android Development] abdel12345:
If my bootloader is already unlocked i can just use the root button without losing any data? I forget because I've been off my nexus 10 for a while now

Sent from my VS980 4G
[Nexus 10 Android Development] garnet&gold:
I reinstalled after tuning off the av & firewall. Still cannot access the update server.
[Nexus 10 Android Development] ICuaI:
Yes
[Nexus 10 Android Development] WugFresh:
Can you try going to this URL through your web browser; https://gist.github.com/WugFresh/ and tell me what happens. Does it work? Does it get blocked?

Shoot me a chat message on google hangouts > wugfresh at g mail.

{{ WugFresh }}
[Nexus 10 Android Development] garnet&gold:
message sent.
[Nexus 10 Android Development] dobrun.franjo:
cant download anything for nexus 10

always file mismatch
[Nexus 10 Android Development] WugFresh:
I think I know what might be causing some issues. I am pushing v1.9.2 later tonight.
[Nexus 10 Android Development] WugFresh:
Let me know if your issue is resolved in v1.9.2. I didn't have the issue myself, but I pushed a fix that may have fixed the issue for you. If you are still getting mismatches, its likely an internet connectivity issue.

{{ WugFresh }}
[Nexus 10 Android Development] dobrun.franjo:
internet issue?i dont think so

every other thing works 100%

just your toolkit has download troubles(can say only for nexus 10)

tried 1.9.2 and the problem remains. i cant even download recovery image and supersu it just starts on 1% and after a second jumps to 100% every single time file mismatch.
[Nexus 10 Android Development] WugFresh:
Ahh. Based on your description of the behavior, I think your AV or firewall might be getting in the way. Make sure its not blocking the activity of nexwug_downloader.exe, and make sure there are no web-shield type rules against androidfilehost.com. Also can you try using the "try again" a few times when it fails, and see if that has an effect.

All downloads are working great for me and many users, so I don't think its server side, and I am pretty certain its not the software itself.

{{ WugFresh }}
[Nexus 10 Android Development] dobrun.franjo:
iam trying to download 4.2.0 build and no luck 4.4.4 downloads fine

have no firewall and no antivirus
[Nexus 10 Android Development] tyraelasd:
Hi I need a little bit of help. I'm stucked in an endless bot animation because I couldnt do the factory reset after unlocking the boatloader. I can go back to fastboot mode pressing up down and power but I CANT acces the recovery menu option to factory reset it... It's volume up plus power but it does not happen
[Nexus 10 Android Development] abdel12345:
If you can get into fastboot then just connect your tablet to the computer in fastboot mode and extract the factory image so that you have each file as separate images. Place them inside the wugfresh toolkit folder and then just open a command window on your computer in that same folder and use the command 'fastboot flash system system.img' without quotes. But if system is named something else and not system.IMG them just type that In its place. You can then do the same for other images as well example:

fastboot flash boot boot.img and that will flash the kernel. So try this and see if you can get it back to stock that way though if you flash user data it'll delete everything on your tablet. So try flashing everything but user data first and if it doesn't work then do userdata as well
[Nexus 10 Android Development] tyraelasd:
Thanks for your response but luckily I read a post where it said just press repeated 3 times power plus volume up and magically the recovery menu appeared. so problem solved, running KK now...

I think I definitely need to know how to use those adb commands..
[Nexus 10 Android Development] WugFresh:
Just use "Flash Stock + Unroot" with "Softbrick", and follow the instructions.
[Nexus 10 Android Development] fredphoesh:
Stuck!

Hello guys

I was trying to load stock KitKat to my N10.

Root Toolkit updated, downloaded the right image files etc, got ADB, rebooted my tablet, all good, but then did not complete the process.

Now I get to bootloader and when I choose recovery mode, the tablet reboots, but instead of coming to recovery mode, it goes back to the START menu... So I cannot get back up to Android and cannot get to Recovery. Also, I cannot get Root Toolkit to connect with ADB.

What can I do to salvage my tablet?

Cheers,

Mark.
[Nexus 10 Android Development] WugFresh:
FAQs - Help!!! My Nexus device is totally messed up. It has ______ problem. What do I do??

Since you can get to that start menu, you are all good. Flash Stock + Unroot will get you going again (with Softbrick mode) - just follow the instructions.

You only need fastboot connectivity to restore a device, not adb.
[Nexus 10 Android Development] fredphoesh:
Hi mate, thanks... I just tried that but get

archive does not contain 'boot.sig'

archive does not contain 'recovery.sig'

archive does not contain 'system.sig'

archive does not contain 'tos.img'

and then when trying to send boot it fails (data transfer failure (unknown error))

I did download the image just before starting. BTW I was on Lollipop and was trying to flash back.

Thanks,

Mark.
[Nexus 10 Android Development] WugFresh:
Try again with an alternate USB port, and enable Force Flash mode in the toolkits option menu.
[Nexus 10 Android Development] fredphoesh:
I tried a second computer and it worked perfectly, thanks WugFresh...

Mark.
[Nexus 10 Android Development] Armeniandave:
Will the Root option work on 5.0?

Just used the toolkit to upgrade and it worked perfectly!

Thank you
[Nexus 10 Android Development] capitansky:
root and twrp work?
[Nexus 10 Android Development] Armeniandave:
I was asking if it did. I just updated to lollipop without root.

I haven't tried to install twrp or root it yet.
[Nexus 10 Android Development] xstahsie:
I'm going to download the Lollipop stock image and use this tool flash.

Could you tell me which option in this tool was I need to select to get my Nexus 10 upgraded to lollipop?

Sent from my LG G3
[Nexus 10 Android Development] WugFresh:
Redownload it now.

{{ WugFresh }}
[Nexus 10 Android Development] WugFresh:
Updater package is live now. Enjoy ^_^ Everything working properly on the Nexus10 now.

{{ WugFresh }}
[Nexus 10 Android Development] Gunthermic:
Seems to be working now with driver issues. Thank you for your hard work.

Only items i see that for me cause me to pause, if i select custom recovery and select CWM, all the continues to say TWRP.. if that can be changed to be more concise for users. then they know .. just a suggestion is all..
[Nexus 10 Android Development] WugFresh:
It still actually will flash CWM, but the toolkit NEEDs TWRP regardless, because that is the recovery is uses (temporarily) to root the device, via an automated zip flashing using open recovery script. When you select CWM as you recovery, when rooting it will ask you to download both CWM and TWRP if they aren't found in the local directories. Sorry if that wasn't clear. I could see that being confusing if you just selected CWM and the next prompt you see mentions TWRP. I will add a note about that somewhere, or maybe integrate that message into the toolkit somewhere.

The toolkit also utilizes TWRP for the automated zip flashing (file on this computer), regardless if you have CWM checked. Open recovery script allows for these advanced features, and unfortunately CWM restricts this type of third party integration in this manner.

Cheers. Glad its working for you.

{{ WugFresh }}
[Nexus 10 Android Development] jmtend:
It Works

I was one that had the identified problem. 1.6.1 solved the problem. Under " Portable Devices " it is recognized as a Nexus 10 however under "Android Phone " it is recognized as a Google Nexus 4 ADB Interface. I don't think the conflict in identity is relevant, but I thought I would make it known. Thanks for the fix.
[Nexus 10 Android Development] WugFresh:
Yeah, the drivers are a credit to 1wayjonny's magic. The incorrect name display is not an issue if you get that, if the toolkit can communicate with your device all is well. :)

{{ WugFresh }}
[Nexus 10 Android Development] jmtend:
New Problem

I posted to soon regarding the fix. In the process of doing a Nandroid backup it installed a new driver and switched the identity of " Android Phone " from a " Google Nexus 4 ADB Interface " to a " Google Galaxy Nexus ADB Interface. After that happened it now freezes on the TWRP screen during the backup. I then closed and reopened the toolKit and tried a " Full Driver Test " The test was successful however during the test it changed the " Android Phone " back to a " Google Nexus 4 ADB Interface. The ToolKit still does not work for me.
[Nexus 10 Android Development] WugFresh:
Please try initiating it again and report. I have had numerous user report success.

To be sure you are good, you need to start the driver configuration from step 1.. that means uninstalling all the drivers first completely. It sounds like you may have other drivers on your system. Then install the drivers with the guide. If you follow the full driver instructions everything should work no problems.

{{ WugFresh }}
[Nexus 10 Android Development] DagrXDA:
My device & drivers are now being correctly recognized as well & I pass the "step 3" verification test. That said, it's really wierd... no matter what I do to clean out the old drivers, my devices still comes up as "ASUS Android Device" and "Nexus 4 ADB Interface". I assume the Nexus 4 part is simply from the drivers you are using... but why the heck does device manager show "ASUS Android Device" for my Samsung tablet?? (I had an ASUS Infinity previously, so I'm worried the drivers are hanging around).

Thanks!
[Nexus 10 Android Development] WugFresh:
Use the including "USB deview" app by Nirsoft, in step one of the driver guide, to fully eliminate all traces of previous conflicting adb drivers. That will prevent what you are experiencing.

{{ WugFresh }}
[Nexus 10 Android Development] DagrXDA:
I've been doing that... killed everything, rebooted, etc. At this point the drivers are working, so its a minor thing... I just don't know where the device itself is being recognized as ASUS (the driver below it says Nexus 4 adb interface as you would expect for the naked drivers).

So it looks like this (to be clear)

- PC Name

- ASUS Android Devices​

- Google Nexus 4 ADB Interface​

.... other devices, then

- Portable Devices

- Nexus 10 (I assume this is the MTP interface of the N10)​

Also, in USBDeview, there is nothing there that has "ASUS" in it... just the google inc. vendor entries you would expect.
[Nexus 10 Android Development] curly9:
I was on 4.2.1 and now it is stuck at the nexus boot. I've searched every where. What do I need to do.
[Nexus 10 Android Development] WugFresh:
Hold the power button to turn it off. Then follow the "Flash Stock + Unroot" "soft brick" script to restore your device. You could also try a simple factory reset, by going into the stock recovery from bootloader mode.

{{ WugFresh }}
[Nexus 10 Android Development] curly9:
Hash check mismatch extraction cancel led flashing stock cancelled
[Nexus 10 Android Development] WugFresh:
That prevents you from flashing an incomplete factory image. It is an important fail safe I included. Update the toolkits master lists (Help > About...) to ensure you have the latest lists, then try again on a stable internet connection, or download it from google, and use the "other/browse" option in that flash stock interface: https://developers.google.com/android/nexus/images

I think if you just update your master lists and try again, all will be well.

{{ WugFresh }}
[Nexus 10 Android Development] DagrXDA:
Thanks for your work Wug... I'm now rooted with TWRP recovery (I had been using CWM, looking forward to giving TWRP a try).

Other than the thing about my device list showing ASUS, I'm good to go now. (I'm wondering if ASUS just changed a registry description for AndroidUsbDeviceclass items? (That's where the "ASUS Android Devices" string is located).
[Nexus 10 Android Development] DagrXDA:
One more questions for you (similar to the longer thread over in the N7 forum, but i was unable to find a solution in there).

I'm not having much luck making nandroid backups via the toolkit to TWRP. Basically all goes well, but when into the actual backup in TWRP I get a message similar to: "backup failed unable to locate android secure partition"...

I was checking all of the includes... should I not be doing this (including .android_secure).

I am unlocked / rooted / latest TWRP / 4.2.1 updated.

Thanks!
[Nexus 10 Android Development] WugFresh:
Yeah, I typically don't include that partition. I will investigate the issue though and see if I can reproduce the error.

{{ WugFresh }}
[Nexus 10 Android Development] WugFresh:
I am not entirely sure but that is possible. Which ASUS device did you have previously, can you PM me the drivers or installer you used for that device? Maybe I can hunt it down. Doesn't seem to matter though, but its always fun to figure things out. :)

{{ WugFresh }}
[Nexus 10 Android Development] DagrXDA:
I literally just deleted the file. It was from ASUS directly I believe (I had a TF700 infinity). No worries about it, but I appreciate the help!

I'm just not having luck with the nandroid backups... finally got it to complete then the tablet did a reboot right as the script was trying to transfer the files to the laptop.

I may just got back to using Titanium or see about using the UTG cable method of backing up in TWRP.
[Nexus 10 Android Development] alryder:
I was not able to get root to work on Lollipop. I ended up getting stuck in a boot loop. I was finally able to flash back to stock using the force option.
[Nexus 10 Android Development] Johan1976:
You need a modified kernel and beta supersu to get it to work (I did it on precompiled preview) however on factory image version TWRP doesn't seem to be able to create files on system. After install zip no files gets created. Trying to copy files in file manager only results in FAIL. :(

Skickat från min GT-I9505 via Tapatalk
[Nexus 10 Android Development] tigcf:
On the upper left corner of the program window, select your nexus 10 and Android Lollipop version. Save and then go to the option "flash stock + unroot". It will download and flash the android lollipop stock image.
[Nexus 10 Android Development] Echo_Platoon:
I also had the same issue of getting stuck in a bootloop on my Nexus 10 when trying to root it. I was able to flash it back to stock. Afterwards, I searched for and found the CF-Auto-Root for the Nexus 10 running Android 5.0. Chainfire's original CF-Auto-Root originally didn't work as well and people were getting stuck in a bootloop. Chainfire said that it was "a case of the OutOfSpacies on /system", fixed it, and released a working solution of rooting Android 5.0 on the Nexus 10; it's an updated version of the CF-Auto-Root for the Nexus 10. You could find it on Chainfire's CF-Auto-Root site (http://autoroot.chainfire.eu/).
[Nexus 10 Android Development] striker59:
Installed lollipop and it works. Problem is I have no recovery, I get into bootloader and select recovery, screen goes black, nothing. I know it should be in recovery. If I long press power it will restart. I tried installing stock recovery and it goes into bootloader then restarts and get a message waiting for device.
[Nexus 10 Android Development] b1g.p0ppa:
Yep, same thing here. Cannot boot to recovery and cannot enter stock recovery at all. What I've found works is to boot to bootloader, fastboot flash recovery from a TWRP image and without rebooting the bootloader tell it to boot to recovery. That's the only way I found to get into TWRP at all at the moment. No way that I can find to boot to stock recovery at all.
[Nexus 10 Android Development] noname580:
Nexus 10 root issue

I had no problem upgrading to 5.0. When I try and perform the root option, without flashing a custom recovery as I already have one flashed, the tablet will boot into the modified but upon restart the USB debugging will not be enabled and the program hangs at waiting for device. This also happens when using the Advanced Utilities and booting into the modified-boot.img. Boots into the regular bootloader with a green android then loads into the modified-bootloader with the teal android. After that my tablet boots into Android but again the program just hangs at waiting for device with my tablet loaded up to android but no USB debugging option showing in my notifications nor does it even say that the device is plugged in as a media device. When I go into the developer options USB Debugging is checked. When I uncheck it, the tablet reboots back into android with the program still hanging. I tried deleting the modified-boot from the folder a re-downloading it but still doesn't work. Any suggestion would be great. Any other info please just ask. Thanks in advanced.
[Nexus 10 Android Development] lilbigdude1:
Try and use the hold +volume and trap the power button when the screen is black....might work
[Nexus 10 Android Development] striker59:
Tried using the updated version 1.9.4 and did a fresh install, still no recovery. I could not root it either so I'm back on KitKat. With wugfresh its easy to change so I did.
[Nexus 10 Android Development] MDCWLK:
I flashed and rooted my device without any problems using NRT. Booting to TWRP is not a problem either.

Thanks Wug :)
[Nexus 10 Android Development] abdel12345:
On lollipop recovery takes a little longer to show up. It'll be a black screen for like a minute or two even. Just be patient. (Were talking stock recovery right? Because v that's how it is for me)
[Nexus 10 Android Development] Tourmans:
Used the 1.9.4 version and also the problem: no TWRP first just a black screen then the green android with te empty trunk :(
[Nexus 10 Android Development] forsaken82:
toolkit works perfect.. untill i try to sideload adb. it finds the nexus 10 all the way intill i select sideload. the quicktools finds it under adb and fastboot but not when i try to sideload. any ideas? debugging is on, tried uninstalling and reinstalling drives over and over but no luck.
[Nexus 10 Android Development] WugFresh:
Have you tried messing with drivers while you are in adb sideload mode? That's the trick.

You need to open device manager, and configure it while its in that mode.
[Nexus 10 Android Development] juicybuffy:
Super Brilliant. Good job!
[Nexus 10 Android Development] Johan1976:
Is TWRP in toolkit updated for 100% compatible with lollipop? As it is now folders created with TWRP (like sdcard/TWRP) are not readable or possible to delete from lollipop. They doesn't show up in lollipop mtp mode either. Needs to be deleted from TWRP manager or accessed from TWRP mtp mode.

Skickat från min GT-I9505 via Tapatalk
[Nexus 10 Android Development] WugFresh:
I wasn't aware of these complications. I will look into it, but I don't develop TWRP, so it would probably be better to direct those questions to them.
[Nexus 10 Android Development] Tourmans:
Hello;

Solved my problem with the latest 1.9.6 version back rooted and TWRP present many thanks ;)
[Nexus 10 Android Development] WugFresh:
Nice. On which device? N10?

{{ WugFresh }}
[Nexus 10 Android Development] a_netanel:
I was not able to get root to work on my Lollipop N10.

Did a "Flash Stock + Unroot", followed by factory reset, and then tried to root.

I tried with and without "Custom Recovery" checked, and also both SuperSU and superuser.

The process seems to go alright, and busybox is installed, but no SuperSU app. Tried installing it from the Play Store, but it said that su binaries are not installed.

I eventually tried CF-Auto-Root which did the trick, but I wonder what is wrong with the tool.

I'm now flashing the stock image again, so I'll be happy to provide logs or whatever.
[Nexus 10 Android Development] WugFresh:
Hit me up on google hangouts chat, wugfresh @ gmai...
[Nexus 10 Android Development] Tourmans:
Yes nexus 10 wifi tablet.

My problem was an issue with the adb settings reinstalled the new toolkitversion and it worked.

Thank you again :good:
[Nexus 10 Android Development] ColinB63:
Updated my Nexus 10 to Lollipop yesterday. Everything went well including root and TWRP.

Used 1.9.6.

The only problems I had were getting my PC to recognise my Nexus 10 when I plugged it in!

Thanks WugFresh:good:
[Nexus 10 Android Development] WugFresh:
Can you both root checker confirm root. Because another user said no good on N10.
[Nexus 10 Android Development] ColinB63:
Root checker confirms root.

SuperSU is granting root access to apps that need it.

I used Busybox free to install binaries to /system/xbin if that helps.
[Nexus 10 Android Development] Tourmans:
Rootchekker confirmes the root access at my Nexus 10 device
[Nexus 10 Android Development] MDCWLK:
[IMG="Confirmed :)"]http://i.imgur.com/2boxarv.jpg[/IMG]

No problems what so ever.
[Nexus 10 Android Development] Izeltokatl:
I couldn't get root to work, but I was able to flash everything to 5.0 just fine. I moved on to CF auto root. Might have been user error as I only tried once.
[Nexus 10 Android Development] striker59:
Latest update for Toolkit 1.9.7 wouldn't run, didn't download the files, will try again later.
[Nexus 10 Android Development] CoolRaoul:
Initially tried to root with NRT and "custom recovery" option checked and it ended in a bootloop: unable to even boot in recovery mode.

Fixed the issue using flash-all.bat in fastboot mode.

Rooted using CF-Auto-Root then.

Note that, after having flashed lollipop factory image, there is very little space remaining in "/system" partition.

I had to remove some packages to have busybox installation succeed.
[Nexus 10 Android Development] WugFresh:
You should factory reset from recovery. It should fix your storage issues. How To Factory Reset Nexus Devices
[Nexus 10 Android Development] WugFresh:
Thank you.
[Nexus 10 Android Development] CoolRaoul:
I've installed from scratch the factory image in fastboot mode, doesn't this reset the device even more "radically"?

Note that other people with the same device (Nexus 10) have the exact *same* storage issues: http://xdaforums.com/nexus-10/help/5-0-lack-free-space-install-busybox-t2939729
[Nexus 10 Android Development] cnow:
sideload OTA -> root-> missing SU-file

Hello,

I used version nrt 1.9.7 and had problems with getting root. I sideloaded OTA and it aborted with "no space left" in system partition. So I deleted SU.apk in system/app and tried the update again. Then everything was fine and OTA finished.

After that I wanted to root the tablet. I choosed the options "Utilize latest beta..." and "no custom recovery" as TWRP was already in place. But when the script finished no SU app was installed. So I downloaded it from PlayStore. When I started it, the message "no SU file" appears and the app closed. I tried it several times and ended up with CF-auto-root. Now everything is beautiful and I got root finally! (Even my N5 has now root as encryption means no longer a data wipe with CF-auto-root!!)

Besides NRT is a great tool and it's very easy to use. My fullest respect to Wug!

BR cnow
[Nexus 10 Android Development] forsaken82:
still cant get it to see the n10 in fastboot mode :( i did see where we can flash to stock 5.0 now though from nrt. im guessing that would work to upgrade?