After successfully rooting my Nexus 4 with the equivalent toolkit, I took the plunge and tried the same with my Nexus 10.
I'm completely stuck at the moment though. I'm using the latest version after donating. I started unlocking the bootloader and it rebooted into the red exclamation Android screen. The instructions said to hold the power button and press the right-most ('third from the left') button to get into stock recovery. It didn't. It rebooted and got into the boot loop on the Nexus 'X' screen.
Now I don't seem to be able to get into the recovery screen at all. I can get back to the fastboot screen, but it has the 'Downloading... Do not turn off target!' screen and the toolkit doesn't seem to detect the device anymore (no serial number is displayed in fastboot devices).
Oh, one more thing: the Toolbox did say it couldn't find the Busybox file? Not sure if that has anything to do with it.
EDIT: Crisis averted. No surprises, I was doing it wrong. Anyone with the same;
Hold down ALL THREE BUTTONS to get into Fastboot. This'll let you use the volume keys to find the recovery option. Select that. When the red exclamation with Android screen appears, hold the power button, press the right-most volume key... AND THEN RELEASE BOTH (this, I think, was the bit I failed to do, causing it to reboot). This will only the menu, from which you can do the wipe.
Hope it helps someone.
GOOGLE NEXUS 10 TOOLKIT AUTO UPDATE V1.7.3 [28TH FEB 2013] AVAILABLE!!
+Updated SuperSu [root] files to V1.20 for all root procedures
+Updated TWRP Touch Recovery to 188.8.131.52
+Fixed all bugs that have been reported and that I could find
+Added more text to root and unlock procedures for newb friendliness
For people who do not want or cannot get the Auto Update versions you can download TWRP 184.108.40.206 from http://goo.im/devs/mskip/recovery/go....2.0-manta.img and flash it via the Toolkit. You can also update from adb files for 4.2.2 by downloading http://goo.im/devs/mskip/toolkit/adb..._for_4.2.2.zip and overwriting the files. SuperSU can be updated to the latest version from the app.
[Auto Updates (beta versions) are only accessible if you have donated to the Toolkit project, received an activation code and unlocked the professional features. Auto Updates are a much faster and easier way of pushing small updates that would otherwise not be worth doing. I can push a single textual change or add support for a new build without having to go through the whole process of building a full version and uploading a large file. IF you are not able to or do not want to donate to unlock the Auto Update feature (and other professional features) then all the smaller updates are collated and a full build made when I have time or if there are enough updates to warrant it. This is the easiest way to make sure all the Toolkits are as up to date as possible. IF you have any views about this please pm me about them and do not post in the open thread]
Hi Mark, I'm currently trying to update my Nexus 10 Toolkit from 1.7.1 to 1.7.3 as soon as the change log for the update is displayed the toolkit closes. I've never had any issues previously on both my nexus 4 or 10 toolkit during the update process.
I'm running Windows 8 Pro x64 same as previously but I've only just started having the issue.
Can you shed any light?
The 1st post only has 1.3 links and after reading about donating, is that the only way to get an updated version? If not are there links because I'm not seeing them. I used this successfully on my GF Nexus 10 and after the update SU is not working so I'm hoping to fix it with this as well...
|Thread Tools||Search this Thread|