[Toolkit] Wug's Nexus Root Toolkit v2.1.4 [Updated 01/16/16]: Nexus 10 Thread

Search This thread

dyrosto

New member
May 23, 2011
3
0
I'm having the same issue, when I list fastboot devices in the advanced utilities, it show this "R32CA..." fastboot.
Any help?
 

koei7

Member
Jul 7, 2012
6
0
Same problem here. Drivers are installed and working, but for some reason it's not seeing the device in bootloader mode even though with utilities, it's listing the device.

EDIT: Looks like the script which should be trying to look for the device in fastboot bootloader mode is trying to do so in ADB mode.
 
Last edited:

WugFresh

Inactive Recognized Developer
Oct 28, 2010
2,199
7,932
I'm having the same issue, when I list fastboot devices in the advanced utilities, it show this "R32CA..." fastboot.
Any help?

That means it sees your device. What is the issue? Can you please describe it in full details. Like what exactly are trying to do and when specifically do you encounter a problem?

Sent from my Nexus 7 using Tapatalk 2
 
  • Like
Reactions: griffinj

dyrosto

New member
May 23, 2011
3
0
That means it sees your device. What is the issue? Can you please describe it in full details. Like what exactly are trying to do and when specifically do you encounter a problem?

Sent from my Nexus 7 using Tapatalk 2

I am trying to unlock my device. I went through the procedures in step one. Had no luck the first time, checked and made sure anything that had to do with samsung, google and android were uninstalled from my system. Rebooted multiple times and re did the setup. It still gives me the same error after rebooting the nexus 10 into the bootloader. But, when I go to advanced utils and list the fastboot devices, it sees it.
 

WugFresh

Inactive Recognized Developer
Oct 28, 2010
2,199
7,932
I am trying to unlock my device. I went through the procedures in step one. Had no luck the first time, checked and made sure anything that had to do with samsung, google and android were uninstalled from my system. Rebooted multiple times and re did the setup. It still gives me the same error after rebooting the nexus 10 into the bootloader. But, when I go to advanced utils and list the fastboot devices, it sees it.

That's very odd. Can you add me on gchat? I would like to trouble shoot a solution so I can get to the bottom of what's causing this issue.

{{ WugFresh }}
 

WugFresh

Inactive Recognized Developer
Oct 28, 2010
2,199
7,932
I thought about it some more and I am like 99% sure why some of you are experiencing that problem, but I need to confirm it. Can someone with an N10 please hit me up on gchat, it should only take a few minutes.

{{ WugFresh }}
 
  • Like
Reactions: workerantDroid

Johan1976

Senior Member
Jul 12, 2011
354
47
Great work. I assume you got someone to test your theory then :)

Skickat från min HTC Desire via Tapatalk 2
 

WugFresh

Inactive Recognized Developer
Oct 28, 2010
2,199
7,932
Wug, can I replace the CWM-SuperSU-v0.97.zip with CWM-SuperSU-v0.98.zip in the root_files folder?

You can, but if you just run the root script, the toolkit will automatically recognize that you have an outdated cwm, and prompt you with a message then it will automatically download .98 for you and replace it. No need to do it yourself. But yes, the toolkit scans the local directory, so you can put any CWM SuperSU zip in there as long as its a non modified one, straight from Chainfire.

{{ WugFresh }}
 

Kael

Senior Member
Jan 6, 2007
112
7
42
Chicago
Strangely enough, I'm not allowed to install the drivers per the toolkit method, even when starting Device Manager in Admin mode...
Always the same error: The third-party INF does not contain digital signature information.
 

xda6969

Senior Member
Jan 20, 2012
321
35
The same with the CWM? I notice that recovery-clockwork-touch-6.0.1.8-manta.img is not in my CWM folder.
 

WugFresh

Inactive Recognized Developer
Oct 28, 2010
2,199
7,932
  • Like
Reactions: Kael

WugFresh

Inactive Recognized Developer
Oct 28, 2010
2,199
7,932
The same with the CWM? I notice that recovery-clockwork-touch-6.0.1.8-manta.img is not in my CWM folder.

Yes, the toolkit downloads everything it needs. This way when new CWM or TWRP or SuperSU comes out, the toolkit will grab the latest version. It scans the local directories first, if the file exists then it proceeds, if it does not it prompts the user to download it, and the toolkit does everything automatically.

The toolkit is defaulted to use TWRP by the way. If you wan't it to use CWM then go in the toolkits options menu and switch it to CWM. The toolkit wil still utilize TWRP for performing other procedures by uzing it temporarily, however it will flash CWM if you want. I personally prefer TWRP because of its openess and improved selective backup options.

{{ WugFresh }}
 

ShadowVlican

Senior Member
Feb 27, 2007
576
96
Toronto
stupid computer doesn't detect the device in bootloader mode... need the drivers for bootloader mode

---------- Post added at 03:16 PM ---------- Previous post was at 02:58 PM ----------

driver installation didn't work... ADB mode detected, but once it restarts into bootloader, it no longer recognizes the device.. so i can't do crap to it

[ADB/FB/APX Driver] Universal Naked Driver 0.72 and Superboot - Nexus 10 root solution worked like a charm... no need to unlock either
 

WugFresh

Inactive Recognized Developer
Oct 28, 2010
2,199
7,932
stupid computer doesn't detect the device in bootloader mode... need the drivers for bootloader mode

---------- Post added at 03:16 PM ---------- Previous post was at 02:58 PM ----------

driver installation didn't work... ADB mode detected, but once it restarts into bootloader, it no longer recognizes the device.. so i can't do crap to it

[ADB/FB/APX Driver] Universal Naked Driver 0.72 and Superboot - Nexus 10 root solution worked like a charm... no need to unlock either

The drivers included need to be updated to those newer naked drivers by 1wayjonny. I am pushing an update later today (v1.6.1), so that users don't encounter the driver problems you experienced. Either way, glad to hear you got your device rooted.

{{ WugFresh }}
 

WugFresh

Inactive Recognized Developer
Oct 28, 2010
2,199
7,932
Ok guys. v1.6.1 is officially out now which will fix the issues some of you were having with device recognition. Now everything should work properly for this device. :)

Enjoy ^_^

{{ WugFresh }}
 

curly9

Senior Member
Sep 29, 2011
399
43
RC failed in data\MD5check_Depot\libiconv2.dll
CRC failed in data\MD5check_Depot\libintl3.dll
CRC failed in data\Drivers\RAW_Drivers\PDAnet_RAW\i386\WdfCoInstaller01007.dll
CRC failed in data\Drivers\RAW_Drivers\PDAnet_RAW\amd64\WdfCoInstaller01007.dll
CRC failed in data\Drivers\RAW_Drivers\Google_Drivers\i386\WdfCoInstaller01009.dll
CRC failed in data\Drivers\RAW_Drivers\NAKED_Drivers\i386\WdfCoInstaller01009.dll
CRC failed in data\Drivers\RAW_Drivers\Google_Drivers\amd64\WdfCoInstaller01009.dll
CRC failed in data\Drivers\RAW_Drivers\NAKED_Drivers\amd64\WdfCoInstaller01009.dll
CRC failed in data\Drivers\RAW_Drivers\PDAnet_RAW\i386\WinUSBCoInstaller.dll
CRC failed in data\Drivers\RAW_Drivers\PDAnet_RAW\amd64\WinUSBCoInstaller.dll
CRC failed in data\Drivers\RAW_Drivers\Google_Drivers\i386\winusbcoinstaller2.dll
CRC failed in data\Drivers\RAW_Drivers\NAKED_Drivers\i386\winusbcoinstaller2.dll
CRC failed in data\Drivers\RAW_Drivers\Google_Drivers\amd64\winusbcoinstaller2.dll
CRC failed in data\Drivers\RAW_Drivers\NAKED_Drivers\amd64\winusbcoinstaller2.dll
CRC failed in data\Drivers\RAW_Drivers\Google_Drivers\i386\WUDFUpdate_01009.dll
CRC failed in data\Drivers\RAW_Drivers\NAKED_Drivers\i386\WUDFUpdate_01009.dll
CRC failed in data\Drivers\RAW_Drivers\Google_Drivers\amd64\WUDFUpdate_01009.dll
CRC failed in data\Drivers\RAW_Drivers\NAKED_Drivers\amd64\WUDFUpdate_01009.dll
CRC failed in data\Drivers\RAW_Drivers\PDAnet_RAW\i386\androidusb.sys
CRC failed in data\Drivers\RAW_Drivers\PDAnet_RAW\amd64\androidusb.sys
CRC failed in data\Drivers\RAW_Drivers\PDAnet_RAW\lg\lgandbus.sys
CRC failed in data\Drivers\RAW_Drivers\PDAnet_RAW\lg\lgandbus64.sys
CRC failed in data\Drivers\RAW_Drivers\PDAnet_RAW\i386\ssadbus.sys
CRC failed in data\Drivers\RAW_Drivers\PDAnet_RAW\amd64\ssadbus.sys
CRC failed in data\Drivers\RAW_Drivers\PDAnet_RAW\i386\ssadwhnt.sys
CRC failed in data\Drivers\RAW_Drivers\PDAnet_RAW\amd64\ssadwhnt.sys
CRC failed in data\RS_BackupRestoreApps\com.riteshsahu.APNBackupRestore-1.7.apk
CRC failed in data\RS_BackupRestoreApps\com.riteshsahu.CallLogBackupRestore-2.3.apk
CRC failed in data\RS_BackupRestoreApps\com.riteshsahu.SMSBackupRestore-4.8.apk
CRC failed in data\Drivers\RAW_Drivers\NAKED_Drivers\androidwinusb86.cat
CRC failed in data\Drivers\RAW_Drivers\Google_Drivers\androidwinusb86.cat
CRC failed in data\Drivers\RAW_Drivers\NAKED_Drivers\androidwinusba64.cat
CRC failed in data\Drivers\RAW_Drivers\Google_Drivers\androidwinusba64.cat
CRC failed in data\Drivers\RAW_Drivers\PDAnet_RAW\lg\lganddriver32.cat
CRC failed in data\Drivers\RAW_Drivers\PDAnet_RAW\lg\lganddriver64.cat
CRC failed in data\Icons\Actions-go-next.ico
CRC failed in data\Icons\Actions-go-previous.ico
CRC failed in data\Icons\backup_single.ico
CRC failed in data\Icons\backup_utils.ico
CRC failed in data\Icons\download.ico
CRC failed in data\Drivers\Driver_Pics\driverconfig.ico
CRC failed in data\Icons\driverconfig.ico
CRC failed in data\Icons\File_Permissions.ico
CRC failed in data\Icons\hashcheck.ico
CRC failed in data\Icons\options.ico
CRC failed in data\Icons\pull.ico
CRC failed in data\Icons\push.ico
CRC failed in data\Icons\Toolbox.ico
CRC failed in data\Icons\Uninstall.ico
CRC failed in data\Icons\whickstok.ico
CRC failed in data\Icons\Wug_Updater.ico
CRC failed in data\Drivers\Driver_Utilities\DeviceManager.lnk
CRC failed in data\Drivers\Driver_Pics\Raw\Scenario3_1.png
CRC failed in data\Drivers\Driver_Pics\PdaNet\01.jpg
CRC failed in data\Drivers\Driver_Pics\Samsung\01.jpg
CRC failed in data\Drivers\Driver_Pics\Raw\01.jpg
CRC failed in data\Drivers\Driver_Pics\Samsung\02.jpg
CRC failed in data\Drivers\Driver_Pics\Raw\02.jpg
CRC failed in data\Drivers\Driver_Pics\PdaNet\02.jpg
CRC failed in data\Drivers\Driver_Pics\PdaNet\03.jpg
CRC failed in data\Drivers\Driver_Pics\Samsung\03.jpg
CRC failed in data\Drivers\Driver_Pics\Raw\03.jpg
CRC failed in data\Drivers\Driver_Pics\PdaNet\03a.jpg
CRC failed in data\Drivers\Driver_Pics\Raw\04.jpg
CRC failed in data\Drivers\Driver_Pics\Samsung\04.jpg
CRC failed in data\Drivers\Driver_Pics\PdaNet\04.jpg
CRC failed in data\Drivers\Driver_Pics\PdaNet\05.jpg
CRC failed in data\Drivers\Driver_Pics\Raw\05.jpg
CRC failed in data\Drivers\Driver_Pics\Samsung\05.jpg
CRC failed in data\Drivers\Driver_Pics\PdaNet\06.jpg
CRC failed in data\Drivers\Driver_Pics\Raw\06.jpg
CRC failed in data\Drivers\Driver_Pics\Samsung\06.jpg
CRC failed in data\Drivers\Driver_Pics\PdaNet\07.jpg
CRC failed in data\Drivers\Driver_Pics\Samsung\07.jpg
CRC failed in data\Drivers\Driver_Pics\Samsung\08.jpg
CRC failed in data\Drivers\Driver_Pics\Samsung\09.jpg
CRC failed in data\Drivers\Driver_Pics\Samsung\10.jpg
CRC failed in data\Drivers\Driver_Pics\Samsung\11.jpg
CRC failed in data\Drivers\Driver_Pics\Samsung\12.jpg
CRC failed in data\Drivers\Driver_Pics\Samsung\13.jpg
CRC failed in data\Drivers\Driver_Pics\Samsung\14.jpg
CRC failed in data\Icons\about.jpg

this is what i get when i download and try it and it wont do anything. what do i need to do?
 

Top Liked Posts

  • There are no posts matching your filters.
  • 183
    Unlocking, rooting, relocking and unrooting simplified! (and much more!)

    VERSION 2.1.4 - This program will automatically bring together all the files you need to unlock and root your device in a few clicks, or flash it back to stock and re-lock it. You can also use this program to backup/restore all your important data, flash zips, set file permissions, push and pull files, install apps, generate logcats/bugreports, and much more! With the included file association options, you can perform tasks like flashing zips, installing apps, restoring android backup files, and flashing/booting img files with just a double click! The program includes a full featured interface for automating tasks in TWRP, enhanced restore features, an in-built auto-updater/notification system, ‘any build’ mode, advanced restore features,’NRT- Live Log’ for viewing the adb/fastboot cmds that are run in the background, quick tools utilities, and tools for taking screenshots/screen-recordings. All the latest official Android builds and Nexus devices are supported. The program intelligently and selectively downloads the files it needs for your device and makes sure you are using the latest files available. The program can even auto-detect your device and build. This release brings full Marshmallow root support plus all automated features by utilizing a new system that no longer requires modified boot.imgs. Check out the updated changelog for a more comprehensive breakdown of the feature set and changes in this release.

    ~ my goal for this project is make the entire process as smooth and simple as possible ~

    GDhJYE8.jpg


    q1o1kav.jpg


    Please read the FAQs before posting questions: http://www.wugfresh.com/nrt/faqs/

    Looking for a walk-through? >> Excellent Instructional/How-To Videos: http://www.wugfresh.com/videos/

    More information & Download Links: http://www.wugfresh.com/nrt/

    Changelog: http://www.wugfresh.com/nrt/changelog/

    Enjoy! ^_^

    {{ WugFresh }}
    12
    If anyone starts bootlooping for longer than 5 minutes after an unlock than you need to factory reset.

    1. Hold down the power button to shut the device off
    2. Restart the device holding all three buttons (vol up and down + power button)
    3. In bootloader mode, switch the big green START to the red RECOVERY using the volume buttons
    4. Enter stock recovery by pressing the power button
    5. You will see an android on its back
    6. Press Vol up + power button at the same time to enter the stock recovery menu
    7. Select "Factory Reset" with the volume buttons and press the power button to initiate it.
    8. After the factory reset your device should boot up normally.

    {{ WugFresh }}
    6
    Version 1.6.3 is up now and the updater package is also live via the in-built updater. Enjoy!
    (Updated changelog coming shortly)

    {{ WugFresh }}
    5
    TWRP fails here too. What did you do to fix the problem? I cant seem to get anything to work!

    This is what I have to do after the first twrp factory reset fails:

    1. Properly and completely turn off your device.
    2. Press and hold Volume Up + Volume Down + Power keys until the device powers on. You should see an image of an Android icon lying on its back.
    3. Press Volume Down twice until the screen says “Recovery mode.”
    4. Press Power to restart into “Recovery mode.” You should see an image of an Android with a Red triangle after a few minutes.
    5. Tap Volume Up key while hold and press Power button.
    6. Use the volume keys to scroll to “wipe data/factory reset” and press Power to comfirm.
    7. Use the volume keys to scroll to “Yes – erase all user data” and press Power to confirm.
    8. Your device will reboot itself after the data wipe completed.
    5
    Are you going to update "[Toolkit] Wug's Nexus Root Toolkit" to install Root and Recovery with version 4.3?

    Yes, by tomorrow.

    {{ WugFresh }}