Nexus Root Toolkit v2.1.9

Unlocking, rooting, relocking and unrooting simplified! (and much more!)

VERSION 2.1.9 – 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, utility set for merging custom build.prop tweaks, 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 official support for the new ZIP style factory packages.   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 ~

Supported Nexus devices:
· Galaxy Nexus: GSM Models (both yakju and non-yakju builds)
· Galaxy Nexus: CDMA/LTE Verizon Models
· Galaxy Nexus: CDMA/LTE Sprint Models
· Nexus S: Worldwide, i9020t and i9023 Models
· Nexus S: 850MHz, i9020a Models
· Nexus S: Korea, m200 Models
· Nexus S 4G: d720 Models
· Nexus 7: Asus Tablet
· Nexus 7 3G: Asus Tablet
· Nexus 7 v2 (2013): Asus Tablet
· Nexus 7 v2 (2013) LTE: Asus Tablet
· Nexus 10: Samsung Tablet
· Nexus 4: LG Phone
· Nexus 5: LG Phone
· Nexus 5X: LG Phone
· Nexus 9: HTC Wifi Tablet
· Nexus 9: HTC LTE Tablet
· Nexus 6: Motorola Phone
· Nexus 6P: Huawei Phone
· Nexus Player: Google Device
· Nexus Pixel C: Google Tablet
Feature List:
· Install correct ADB/Fastboot Drivers.
· Auto-detect device and build.
· Auto-download all required files with hashcheck verification.
· Automatically root any build on all Nexus devices.
· Flash Custom Recovery (TWRP/CWM/Philz/Other).
· Unlock Bootloader.
· Re-lock Bootloader.
· Restore/Upgrade/Downgrade to any android build.
· Recover device from softbrick/bootlooped state.
· Intelligent device/bootlaoder variable checking to prevent flashing incompatible firmware.
· Dual-mode ADB/Fastboot intelligent connectivity checking.
· Create Android Backup files for individual or all apps.
· Backup & Restore Virtual SDcard.
· Backup & Restore SMS, Call Logs, APN.
· Create Full Nandroid Backup with Custom Recovery.
· Fastboot Flash IMG files to any device partition.
· Flash No-forced Encryption Boot.img.
· Restore Stock Kernel.
· Fastboot Boot IMG files (Boot.img/Recovery.img).
· Fastboot Boot Custom or Stock Recovery.
· Fastboot Erase/Format partitions.
· Grab Screenshot.
· Screen Record.
· Set/Check File Permissions.
· Sideload OTA Update zips.
· Flash zip files (Roms/Gapps/Etc).
· Tweak Display Density.
· Install APK’s.
· Push/Pull files to any device partition.
· Push/Pull on-device hashcheck verification system to ensure complete operations.
· Generate Logcat/Bugreport.
· Enter manual ADB/Fastboot commands.
· [NEW] Merge and manage custom build.prop tweaks.


Main Interface


  1. Select the correct device and build (what you are currently running)
  2. Configure your drivers if you haven’t already using the driver guide (If you aren’t sure use Step 3 of the driver guide to test your drivers).
  3. If you need to, backup your important data.
  4. Unlock your device
  5. Root your device
  6. Enjoy! ^_^
  • Learn more about each option by mousing over the control, dynamic tooltips will provide you more information, also each button displays a message about what it does first.
  • So the best way to get familiar with the toolkit is simply to press the buttons and read what it says.
Looking for more information? First please read the Frequently Asked Questions
Need a visual walk through? Check out these great how-to Video Guides + Tutorials
Still need help? Search and participate in the Nexus Root Toolkit Forums


File size: 44.8 MB
MD5: 53c4072f15343fd545b4676aa5bfd099
SHA256: 61dc26a304a3835aedfc3a1e7bd67f76bee6673f5e22e43729a1a706d3ef8820

Need a simple way to validate checksums? I recommend:



~ If you like my work please consider making a small donation. Help and support is greatly appreciated. Thank you! ~


{{ WugFresh }}

2,184 comments on “Nexus Root Toolkit v2.1.9
  1. Ricardo Serrano says:

    I’m running Android L on a Nexus 5 and I want to root it. Is it possible?

  2. Sebastian Brochocki says:

    when NRT upgrade to android L install?

  3. Penis says:

    No, you can go straight to 4.4.4.

  4. Penis says:

    See if either Media drive (MTP) or Camera (PTP) is checked under Settings -> Storage -> USB computer connection.

  5. Eric Strom says:

    Google Chrome is also flagging it as malicious.

  6. M.F. Lawrey says:

    HI Wugfresh, let me say great work with NRT. I will say tho, i trashed my first N7 v2 2013 wifi tablet the first round after 4.4.3 OTA. prolly my ignorance. Now 2nd round new N7 v2. updated 4.4.3. unlocked and rooted, flawless. Now next OTA is out, not wanting to do trash another, dint accept OTA yet, Trying to “flash+unroot” keep getting same “no system, boot,recovery,img” It appears to me NRT isnt reading the the files inside the included zip file. Only seen one other post about this problem, and answer was corrupt,incomplete download. I have used NRT to d/l both the 4.4.3 and 4.4.4 file multiple (9-10) times and d/led direct from google, all say matched and complete. Never used and not opposed to using ADB method just alittle gun shy ATM. Thanks and sorry for being long winded

  7. Justin Deain says:

    hey i need help i unrooted and flashed the stock rom on my nexus 4 and it said it is finished and its booting up now and its booting now for 2 hours and its still booting at the color changing screen

  8. Nexus 5. 16 GB. kk says:

    thanks guys for everything you do I just had a quick question I want to know if there’s a way you can take T Mobile throttle iand just totally just get rid of it is there a way to do that and thanks for everything….!!!!

  9. fingrlakes says:

    Is there a way to flash my nexus without turning on debugging?

  10. BDPSU says:

    After upgrading to Android 4.4.4, NRT will not re-root my unlocked Nexus 4. It boots the phone into the bootloader, but then the phone sits on “downloading”, and NRT says that it’s “Booting modified boot.img to enable privileged commands”. It never moves beyond that point.

    I’ve tried running this several times and letting it run for 10 minutes or more – it never works.

    Any idea what the problem is?


  11. GigaCode says:

    Are you going to add “L” support anytime soon ?

  12. Maku Suchinben says:

    Sir WugFresh, I encountered M.F. Lawreys problem, but in my case im using 32bit w7, and i already have downloaded the ktu84l factory file.. NRT cant find system.img… Help me please

  13. BA14 says:

    complete noob to this but seeing the same: both downloads proposed on starting NRT fail having shown 1% downloaded and then a hash-check fail. Using NortonIS – no pop ups or log entries to suggest that’s the problem. If downloading manually is the answer could someone please send me a link and a clue where to put the files ! Thanks

  14. Peter Gutierrez says:

    WugFresh. first of all thank you for the toolkit. it gave me a bit of trouble(because of my dumbness), but overall, smooth. Here is a solution I found: I am using windows 7/64 and was rooting a nexus 4(4.4.4). there are two files that were not pulling automatically 1.modified_boot_occam_4.4.4_KTU84P.img and 2.openrecovery-twrp- since it is not doing so, when attempting to root with or without custom img., you hang mid process. what I did was pull them manually(as instructed by your toolkit), had nrt browse locally after download, then merged them. once that was done, I reattempted, and pow!!! im in. I don’t know if this issue was resolved already, but I hope I could help someone who needs it. Thank you again!!!!

  15. Michael Kramer says:

    Following is what I have been after a day of trying to fix my boot-looped nexus 7 (2012) any ideas?
    Thank you

    Flash Stock + Unroot…


    erasing ‘boot’…

    OKAY [ 0.018s]

    finished. total time: 0.018s

    ******** Did you mean to fastboot format this partition?

    erasing ‘cache’…

    OKAY [ 0.015s]

    finished. total time: 0.016s

    erasing ‘recovery’…

    OKAY [ 0.015s]

    finished. total time: 0.015s

    ******** Did you mean to fastboot format this partition?

    erasing ‘system’…

    OKAY [ 0.016s]

    finished. total time: 0.016s

    ******** Did you mean to fastboot format this partition?

    erasing ‘userdata’…

    OKAY [ 0.022s]

    finished. total time: 0.022s

    sending ‘bootloader’ (2100 KB)…

    OKAY [ 0.304s]

    writing ‘bootloader’…

    FAILED (remote: (InvalidState))

    finished. total time: 0.438s

    rebooting into bootloader…

    OKAY [ 0.020s]

    finished. total time: 0.021s

    sending ‘boot’ (4994 KB)…

    OKAY [ 0.706s]

    writing ‘boot’…

    OKAY [ 0.020s]

    finished. total time: 0.726s

    rebooting into bootloader…

    OKAY [ 0.020s]

    finished. total time: 0.020s

    sending ‘recovery’ (5534 KB)…

    OKAY [ 0.775s]

    writing ‘recovery’…

    OKAY [ 0.026s]

    finished. total time: 0.801s

    rebooting into bootloader…

    OKAY [ 0.020s]

    finished. total time: 0.020s

    erasing ‘system’…

    OKAY [ 0.020s]

    sending ‘system’ (644062 KB)…

    OKAY [ 89.639s]

    writing ‘system’…

    OKAY [ 10.705s]

    finished. total time: 100.364s

    rebooting into bootloader…

    OKAY [ 0.019s]

    finished. total time: 0.020s

    erasing ‘userdata’…

    OKAY [ 0.027s]

    sending ‘userdata’ (104289 KB)…

    OKAY [ 14.518s]

    writing ‘userdata’…

    OKAY [ 1.592s]

    finished. total time: 16.138s

    rebooting into bootloader…

    OKAY [ 0.140s]

    finished. total time: 0.143s


    finished. total time: 0.082s

    Booting up your freshly flashed stock device…


    Wait for your device to finish booting up…

    – It may appear to be boot looping; just wait…

    – It could take 5-10 minutes; please be patient…

    When its finally booted back up, please remember

    to re-enable USB debugging if you plan on using

    the toolkit to perform other operations.

    Press any key to exit…

  16. Enrique Llanos says:

    Hi mate, any plan to update NRT to fit root Android L for the N5?

  17. Wayne Rumble says:

    My nexus 7 running 4.4.4 has been backed up and unlocked succesfully but fails during the rooting procedure because the nexus keeps stalling when it says booting downloaded img. Any ideas on how to help?

  18. Austen Evans says:

    Awesome work, long time supporter / donater (since you fixed my bricked N7 🙂 )
    Have upgraded my WiFi+Cell Nexus 7 to 4.4.4 and can no longer root.
    Upgrading didn’t “re-lock” the device of tamper with the ADB drivers, all that continues to work fine.
    Toolkit seems to think that it’s pushing the Root files OK and boots into Bootloader but it just sits there.
    After Toolkit times out selecting “Recovery Mode” on the N7 gives me the Android Dude with an ” ! “.
    I have tried with both TWRP and CWM to no avail.
    Haven’t had this issue before, previous Roots have been “as advertised” !!

  19. MorcCrafak says:

    I Bricked my phone and testing the stock help 😀

  20. Vladimir Fomin says:

    What does that mean? I waited a half an hour after that press any key and exited. Nexus 7 Wifi tablet.
    Flash Stock + Unroot…


    Length is zd — too small

    error: failed to access zipdata in ‘(null)’

    Booting up your freshly flashed stock device…


    Wait for your device to finish booting up…

    – It may appear to be boot looping; just wait…

    – It could take 5-10 minutes; please be patient…

    When its finally booted back up, please remember

    to re-enable USB debugging if you plan on using

    the toolkit to perform other operations.

    NOTE: If this process was too quick and your device

    is still in bootloader mode, then flashing stock may

    have failed or been incomplete. Simply check the

    log above: if you notice it skipped steps because it

    didn’t meet certain requirements, like the bootloader

    or baseband version, then consider enabling ‘Force Flash’

    mode in the toolkits options menu and trying the

    ‘Flash Stock + Unroot’ processs again. Cheers.

    Press any key to exit…


  21. The auto-updater downloads 1% and then says complete but obviously fails the hash check, so I came here to download directly. However, no matter which of the three download links I try I get a 72.3MB file instead of 72.2MB and the MD5 never matches. Any idea what’s going on?

    I would be fine without upgrading seeing as I’m still using a Nexus 4 which 1.7.9 handles just fine, except that there’s apparently an update to CWMR which 1.7.9 refuses to download or recognise if I download manually – and it won’t let me do a NANDroid without first updating CWMR. Very frustrating.

  22. Giorgi Bregvadze says:

    Please add Android L support

    • Dying_in_this_Crap_World says:

      they will when a version comes out. They stated already that it’s not worth the effort to do it for a developers build when it might change

  23. Jon Colón says:

    Can we donate Doge to you? Awesome work!

  24. Lumir2 says:

    Hi wugfresh, i updated and rooted my nexus 7 2012 to android 4.4.3 and i cant see icon when USB debugging is enabled and pc absolutly no detect nexus as device… have u some idea, what problem is it? I cant connect absolutly to pc now 🙁

  25. Cuddly Nutter says:

    My Windows 8.1 laptop won’t instal V1.8.4 …………………………Just another reason to hate Windows 8.1 🙁

  26. Gianni Metitieri says:

    Hi wugfresh can you add a torrent for next version? devhost download very slow today!!

  27. Wugfresh, please, please add fresh version of NRT to any torrent-tracker. It’s impossible to download it from that damn file-exchangers. Please.

  28. Fatin Daiman says:

    hi wugfresh, stuck at logo google/android logo.. went i take recovery mode/ others mode, its say Booting Failed. so howto fix ;(

  29. Steve Phan says:

    Need help, my phone has no OS and there is no way to start my phone. I tried flashing stock but same error pops up. (Failed – remote: flash write failure). If anyone can tell me how to fix this, your help is appreciated. I have a Nexus 5 and I was running Slimkat 4.4.4. Thanks!

  30. jckckckck says:


  31. ЛЕОНИД БЕЛИКОВ says:

    Спасибо за простую программу. Не совсем понял зачем мне навязали кастомное рекавери…

  32. Soykan says:

    Someone help ı unlocked my devıce then ı pressed root then ıt loaded bootloader then ıt saıd ın the corner bootıng ımage fıle ıt frezeez there help me please

    • WugFresh says:

      Make sure you have selected the correct device and build in the toolkit. Make use of the “Auto-detect” if you are not sure. If an android device ever freezes on you, just force powerdown with the power button.

  33. Marius says:

    If i want to root Nexus 7 2012, with android 4.4.4, with locked bootloader, i need to press the unlock button first, or can i press directly root?

  34. Marius says:

    Too root a Nexus 7 2012, with android 4.4.4 and locked bootloader, i need to click the unlock button first, or i can click directly root?

  35. Saugat says:

    i am having a problem on installing… says samsung driver not found or not installing…so try reinstalling the program…
    it also says that the file is corrupted…Any suggestion?

  36. none says:

    Direct linking does NOT work on AndroidFileHost. It’s advised by them not to, so CDN can determine the best mirror location to serve the file.

  37. WugFresh says:

    Added some more mirrors. Swapped out the androidfilehost direct download link in favor of Major Geeks as the primary link.

  38. jata says:

    Wugfresh. Thanks for developing your toolkit. I’ve been using it for a year – I have a nexus 7 2013.

    For 2 weeks I have many problems with twrp backups not restoring and boot loop. Im not sure what is going wrong as it is usually works fine. Its not an issue with your toolkit but I hoped you could help.

    I have kk 444 stock not rooted as primary ROM

    I have android l not rooted as secondary

    When I switch between these ROM using twrp backup/restore it gets stuck during boot at the coloured circles stage. The only fix is to flash stock and start over.

    Any advice?

  39. Jayanta Chakravorty says:

    I am gettinng this error on trying to install 1.8.5 “windows cannot find nexusroottoolkit.exe”….solutions???

  40. ddonuts4 says:

    For some reason, using the ‘OEM Lock’ script doesn’t seem to check if TWRP has been downloaded, and the entire script will run ‘successfully’ without actually doing anything.

  41. gladvold says:

    Hi! I have previously successfully unlocked and rooted my Nexus4 with your toolkit. Kept stock, no custom ROM. Since then I have received Google OTA system updates, and because of that the phone is no longer rooted. But is it still unlocked, can I skip unlocking this time? Will I loose app data etc. if I root again?

  42. Luqman NH says:

    Nexus 4 user here! I love this toolkit. Making flashing ROMs and stuff more easy without having to use adb whatever command ;D
    Though sometimes there is this problem where I want to restore backup that I made using this toolkit and it doesn’t seem to work. I’d be glad if you fix this 🙂

    Donated 😉
    You deserve it.
    And keep the project going!

  43. none says:

    Auto update doesn’t work when upgrading from 1.8.5 to 1.8.6. Had to manually download and install.

  44. CARPDM says:

    nexus 7 v2 stuck on Google boot up screen (stock & unlocked) been trying to flash stock from soft-bricked/bootloop option. It’s not working. I tried unlock bootloader, but it freezes after pressing power button for “yes”. any suggestions?

  45. zdenek faltus says:

    Hello, for the first time here .. First of all, let me to thank you for this wonderful guide and programme ! I got a bit angry with Google for storing all my photos somewhere in the cloud and started to look up the info abvout rooting my Nexus 5. I got a bit angry with the feeble ringing as well.
    Today I have performed my first root with the help of your programme – everything went on smoothly, but after the rooting I had no camera app ! So, I had to flash back the stock ROM and I do hope that the cam will be back:
    So, in the meantime the flash went Ok, the camera is back … What could be the problem ? An secondly,
    what king of custom ROM could I flash after the eventual new rooting?
    Thanks a lot for a possible input and thank you once more !

  46. Freewer39 says:

    Hi everybody !
    Thank you WugFresh for your Toolkit. He’s amazing 😀 (excuse my english, I’m french)

    But I’ve got a problem.
    Near the end of rooting processus for my Nexus 4 (KitKat 4.4.4), there’s a error message :

    Autolt Error

    Line 19423 (File “C:Program Files (x86)WugFresh

    Error: Variable used without being delared.

    (take a look at screenshot)

    Please, help me Wug !!

  47. Guest says:

    Hi everybody !
    Thank you WugFresh for your Toolkit. He’s amazing 😀 (excuse my english, I’m french)

    But I’ve got a problem.
    Near the end of rooting processus for my Nexus 4 (KitKat 4.4.4), there’s a error message :

    Autolt Error

    Line 19423 (File “C:Program Files (x86)WugFresh

    Error: Variable used without being delared.

    (take a look at screenshot)

    Please, help me Wug !!

    • WugFresh says:

      Are you running 1.8.6? What options did you have selected when rooting your Nexus? Flash recovery? Busybox free? When exactly does this message show up? Do you see the rooting complete message? Is your device rooted.

      • Freewer39 says:

        Yes, I’m running the 1.8.6 version.

        I choose TWRP Recovery when I’m rooting my phone.

        I don’t know when exactly he his showing up and the rooting complete message didn’t appear but I solved the problem by checking the “Busy Box Free” installation (I unchecked it before) and my device is now roote 🙂


  48. Michael says:

    used it to unlock nexus7 and install Android L.

    Worked great!

  49. AJ1993 says:

    Hi! I am still stuck up with this error while installing. Can you help?
    Windows cannot find ‘NexusRootToolkit.exe’. Make sure you typed the name correctly, and then try again.

  50. kulvinder singh says:

    hi wugfresh…i m new here and i appreciate you for this awesome project……..

  51. zdenek faltus says:

    Thanks, Wug, you program is brilliant !

  52. Leonardo Floresta Nascimento says:

    firstly congratulations on application
    already used it to root and everything went well
    today after almost two months, but today the touch became unresponsive.
    Restarted, and so now he caught the screen with the Google logo.
    He goes into fastboot, but does not go into recovey mode … used your app in “back to stock” and then the second application all went well … but after all process is finished, it remains on the screen with the google logo.

    sorry for bad english.

    • WugFresh says:

      Are you sure the flash stock completes? How long was the process? You may need to perform a manual factory reset. Check out the instructions under ‘Reset Device in Recovery Mode’ –

      • Leonardo Floresta Nascimento says:

        lasted about 2 minutes … I will add a print to see you …
        the tablet I can not get into recovery, because when I select “recovery mode” in the “fastboot” and press power button, the tablet restarts but returns to the screen from google.
        I’ve tried with 4.4.3 and 4.4.4 and still not getting into the android.
        I’m already more than seven hours in this sad joke … xD
        The strangest thing was that this afternoon after more than three hours attempted, he entered the android, but remained unresponsive to touch … so I rebooted again … and so far failed to do more android back.
        Does the mother board is the problem?

        sorry for bad english again…

        • WugFresh says:

          Strange. That picture looks like everything went correctly. Try opening the toolkit options menu, then go the ‘Flash Stock’ tab > and Check ‘Enable Force Flash Mode’. Then try flashing the old Jelly Bean 4.3.0 (JSS15J). Also, can you try using a different USB cable and USB port if you have one. It could be the motherboard, but I wouldn’t give up yet.

          • Leonardo Floresta Nascimento says:

            And now,Like magic,the tablet as working great….after many hours im turn in on….and after his start Android and for are working… Yep…this is realy crazy

            For now…tks for the suporte!!!!

  53. Guest says:

    I have 4.4.4 using a nexus 7 (2014). I just finally updated and I can’t get it to root. It is saying it is unlocked, as I have rooted it from 4.4.2 to 4.4.3 and on a friends nexus but using an earlier version of the program, 4.4.3 to 4.4.4. I have tried unlocking it again in case and it basically resets the tablet but does nothing else. It does go through bootloader sequence before it reloads my old home page. I have tried to root and it goes through the motions but doesn’t add SU to my tablet and no root.

  54. Been using the NRT heavily ever since I got into Nexus Devices and more recently ROMS, I’m a huge fan and I tell all my Nexus toting friends to use your software. I did however notice a bug that I can reproduce 100% of the time. Launch Advanced Utilities -> Push/Pull Files, then select the “Push Files” radio button, then click the “Push Files/Folder” button and select 2 files and then click “Open”. You will get the error that I’ve attached to this post. If you need/want more info or whatever I can be reached through G+ or Hangouts.

    Edit: It didn’t allow me to upload an image, so the error is:

    AutoIt Error

    “Line 21075 (File “path to NexusRootToolkit.exe”):

    Error: Subscript used on non-accessible variable.

  55. zdenek faltus says:

    Could somebody point me to the site with the custom ROMS , please ? I am quite new to all this.. Thanks

  56. nirwaiz says:

    Worked on Nexus 5, 4.4.4 KTU84Q, Thanks!

  57. Dallas Dorrington says:

    Hey Wugfresh, Thanks heaps eh buddy. You really got me out of a pickle. My Samsung Google Nexus S GT-I9023 died in a big way. The GSM chip fried itself leaving me with no phone. I took the phone to Samsung and they said it needed a new mainboard and this would set me back $200.00 Australian. The phone cost me $300.00 back in 9/2011 brand new. I desided that was too much. So here’s how I fixed the phone. We have a website in Aust’ called “GUMTREE” (www[dot]gumtree[dot]com[dot]au) where people can sell/buy things. So I put up a WANTED ad for a Nexus S GT-I9023 with a broken screen. I got a reply 8days later with a guy wanting to sell his Nexus S for $50.00 and it had a broken screen but otherwise it worked great. My phone was in great condition because it was always in a case to protect it. (Might of been why it overheated and burnt out the GSM chip) So i stripped both phones down and swapped out mainboards which was very easy to do. The phone I just brought had some weard Rom on it (Android 4.2.2 custom) and I hated it so i used your little program and wiped the phone and put the stock Google rom on it Android 4.0.4 ICS I then let the phone do a F.O.T.A. update to 4.1.3 Jellybean and this fixed all the things wrong with the phone and besides I was used to 4.1.3JB because my own phone had it on it. I fixed my phone for $50.00 and 2 hours work I’m now a happy little camper.
    Thanks again

  58. Leonardo Diego says:

    your tool is awesome will donate!

  59. Jim Penny says:

    Hello. Love the program, but I have a possible bug report:

    Galaxy Nexus GSM. Tried to backup a single app from the backup section on the main screen. I get the error:

    “AutoIt Error

    Line 18387 (file “c:program files (x86)WugFresh DevelopmentNexusRootToolkit.exe”):

    Error: Subscript used on non-accessible variable.

    ADB was working, and the device was connected, according to the popup message. This happens right after the message shows up that says “Populating App List”

    • WugFresh says:

      Interesting, that hasn’t happened to me. I will see if I can figure out what caused that. Thank you for the info.

      • Jim Penny says:

        Yeah. It set Bluestacks as the default device when the nexus was connected. Once I shut down Bluestacks, it all worked fine. I intend to convert the device to F2FS soon, and am going to be using NRT to do the flashing once the file system is changed. Do you know offhand if there will be any problems with doing it this way?

        • WugFresh says:

          Thanks for letting me what caused it. I just added a quick line of code so that if it fails populating the app list, it will just give a blank pull-down menu, rather than crashing on you with that error.

          Regarding your question, as long as the files you are flashing are designed for f2fs, it should be fine. The toolkit performs the standard “fastboot flash” cmd’s, so changing the file system first shouldn’t be a problem. Cheers

      • Jim Penny says:

        It was Bluestacks android emulator. NRT wasn’t able to differentiate between the two devices, and kept trying to take information from it instead of the GNex.

    • WugFresh says:

      @jimpenny:disqus thanks again for reporting this. Added a fix in this 1.8.7 release so this behavior wont occur if something is interfering with it like bluestacks – it just populates a blank pull down instead.

  60. linuxbaby03 says:

    Shutup and take my money, you just fixed my tablet.

  61. Jack says:

    If it were any smoother and simpler, it wouldn’t have needed me.

  62. simkeyur says:

    I bought you a beer! Enjoy!

  63. Fernando Romero says:

    Your app is really good. It worked smoothly on my Nexus 7 (2013) Wi Fi with Kit Kat 4.4.4. However I got a minor bug: After rooting process, the Cast Screen option on the quick configuration menu just disappeared. The cast screen option on the Chromecast app is there but it can’t recognize my chromecast device.
    The fun thing here is that I am able to cast fine through the regular enabled Chromecast apps like Netflix or Youtube, so it is not a Chormecast config issue.

    Hope you can help with this.

  64. Matt says:

    Can I unroot without a PC? My mini USB is fried and I need to send it in for warranty.. But want to unroot first. Any ideas?

    • WugFresh says:

      Are you running a custom ROM or stock? Are you running a custom recovery or stock?

      • Matt says:

        Should be stock ROM and recovery. I rooted and unlocked with toolkit v1.8.6 on version 4.4.2 and then mistakenly updated the OS to 4.4.4 and never re-rooted again

        I would run the toolkit again but can’t get the Nexus to be recognized by any PC.. Always allows up as unknown device

        • WugFresh says:

          Then you are in luck. You must follow these steps in the exact order:
          1. Download & Install:

          2. Grant that app Superuser permissions, use it to reset the tamper flag (if applicable to your device) and also to re-lock your device.
          3. Reboot your device to make SURE that the little unlock icon on the ‘Google’ screen is no longer there (it will just say ‘Google’ with a black background)

          4. Now once you are certain that your are relocked, open Busybox (if you have it), and hit Uninstall
          5. Now open SuperSU > Settings > Full Unroot
          6. Then perform a factory reset (this will wipe everything): Settings > Backup & reset > ‘Factory data reset’
          7. That’s it. Your device will be wiped, unrooted, relocked, and stock (assuming you still have stock recovery and are running the stock ROM).


          Edit…. Wait, you aren’t rooted? If you aren’t rooted, you can’t relock, or do anything I described above. You would need a usb connection working then.

          • Matt says:

            It took me awhile to get all the data backed up and I’m ready to do this now

            When I download the boot unlocker it says I need to have a rooted device to use. My device is not rooted, but unlocked.

            Any ideas how I can modify the directions to do this?


      • Matt says:

        Should be stock for both. I rooted and then mistakenly updated to 4.4.4 a few days later… and have not rerooted since

  65. Daryle Edmond Dakis says:

    Hello. Thanks for this great tool. I need to ask, the Nandroid backup feature, where does it store the back up? Thanks again.

    • WugFresh says:

      On the device sdcard, afterwards it uses adb pull to store it on your computer wherever you specify. The default directory is: PROGRAM_FILESWugFresh Developmentnexusbackupcustom-recovery-backups*

      • Daryle Edmond Dakis says:

        So it stores the backup on the sdcard temporarily only, correct? I asked because I have no idea how much space it would use. I have a Nexus 5 with 3.3GB free space. Would that suffice?

  66. Sakif says:

    I’ve installed the drivers for my nexus 5
    onto my PC running on windows 7 including the drivers for adb debugging . However, the RSA fingerprint that is suppose to show up on my phone when connected in adb debugging mode does not show up when the NRT is opened. Can you please help me.

  67. kopfarzt says:

    Hello, does NRT handle backup/restore of multiple user accounts?

  68. Dave McAdams says:

    Thanks for the great tool and the steady enhancements. I have been thinking of updating to KitKat with the new CyanogenMod installer. If I choose to go back to a stock build is it as easy ass using the Nexus Root Toolkit to install a Google image?

  69. Prakash Chowdary says:

    file size greatly reduced

    thanks alot for that
    works flawless for my nexus 4

  70. Francisco Pleitez says:

    I got this:
    fastboot flash bootloader bootloader-mako-makoz20i.img
    sending ‘bootloader’ (2201 KB)…
    OKAY [ 0.073s]
    writing ‘bootloader’…
    FAILED (remote: flash write failure)
    finished. total time: 0.077s

    fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1700.84.img
    sending ‘radio’ (54321 KB)…
    OKAY [ 1.944s]
    writing ‘radio’…
    FAILED (remote: flash write failure)
    finished. total time: 1.947s

    Nothing seems to work, just bootloader and TWRP but when I start TWRP it takes too long to start and Internal storage has 0mb u.u I can’t install a custom rom and can’t install stock rom 🙁 I’ve tried Force Flash but it didn’t work 🙁
    Help please!!!!!

  71. Hannah Stern says:


    • Hannah Stern says:

      Please answer me!
      Will there be ANY DATA LOSS or what?
      Answer quickkly Please!

    • WugFresh says:

      It won’t let you unless your bootloader is unlocked. Full nandroid are one of the benefits of being unlocked. Your only backup options before hand are android backup files, and just copy pasting anything from your sdcard on to your computer. Easy on the caps lock, its the equivalent of screaming at someone.

  72. Hannah Stern says:

    In Bootloader 4.23, What happens when you Press „Start” „UP-arrow” „DowN-arrow”

  73. PeteA says:

    Thanks for the program and updates, it’s been very useful, have donated a beer or two.

  74. Pete A says:

    Thanks for the program and updates, it’s been very useful, have donated a beer or two.


  75. ahmad says:

    how do i run this in ubuntu , iguess this program deal with usb connection differently ! ie no wine support

  76. Roberto Huang says:

    thank very much.. works fine.

  77. olivie says:

    Thank you very much for NRT!

    It works for my Nexus 7! BUT works too for backup and restore of HTC Desire X !!!

    I love you, this is unique work!

    This is the best software, saved my data and my digital life!

    I sent you all my BTC and real money too 🙂

    Best regards and have a nice day!

  78. kopfarzt says:

    Before rooting I need to know what would happen on a tablet with multiple user accounts (multi-user feature)… Does NRT support backing up multiple users? Do I have to make a manual backup for every user? How would this best be done? Is there an FAQ somewhere that I did not find? Does nobody else have this problem? 🙂
    Thank you!

    • WugFresh says:

      I never did the multi user thing myself, so I didn’t run into this. A quick Google search is telling me that adb backup only works on the primary user. I found a thread where someone said they tried to use my kit on the secondary users with adb backup and it just returned a 0KB file.

      Looks like you would need root so you could use Titanium backup pro with multiple profiles option, or just make full nandroids. I know that doesn’t help you if you aren’t unlocked yet, but this seems to be be case.

      I haven’t seen any dev/app address this issue. I guess multi-user is still relatively new. Hopefully Google will improve adb backup in the future.

  79. marty says:

    hey guys, i need help. ive had my nexus 4 formatted and all data and every single thing that can be wiped has been wiped all i have is the bootloader and when i try booting my phone it just stays on the google screen. i have no operating system on it or no back up data and when i plug my usb in to my pc it doesnt find the driver 🙁 c am i tottaly screwed or is there a way back for me?

    • WugFresh says:

      “Flash Stock + Unroot” ‘softbrick’ mode. Follow the instructions. You will have to boot your device into bootloader mode and configure the fastboot driver, which you should be able to do – then you can get everything back up and working.

  80. Brian Arisius says:

    Thanks NRT! I messed up my phone so i decided to unroot it completely back so…it works! thanks once again for saving my phone and keep up the good work!

  81. zdenek faltus says:

    Hi,Wug !

    LG Nexus 5 here, your toolkit saved my phone, thanks !!

  82. Lucas Parrish says:

    I’ll join the chorus, this tool is fantastic! I tried some of the others out there but none of them can do what this tool does. I’m a total novice to Android, got into this for a CarPuter project on my electric car. Then I got the added bonus after rooting to also help me with installing a custom ROM and GAPPS. Dang! I put some jingle in your pocket in appreciation to your hard work. I’m a software developer and know the hard work it takes to bring these projects to life. Even what appears to be a small change can take hours and hours of blood, sweat and tears. Again, thank you!

  83. eliran says:

    Great tool! thank you!!!

  84. Zsolt Zombori Jr says:

    can’t install on win 8.1 64 bit 🙁

  85. sainokawara says:

    I have used NRT since 1.7.8 or so to Flash Stock many times. When I first got my Nexus 7 2013, I could access it as an MTP Device. However, I slowly lost the ability to connect as an MTP Device and by about 1.8.3 or so, I could only connect as CAMERA in USB Debug Mode. I really didn’t pursue this problem because I had no real need to connect as an MTP device, UNTIL NOW! It is not a USB driver issue. It appears that some “device identifier” stored on the Nexus 7 has been “corrupted” which results in a “WUDFHostProblem” (Time-out) during MTP driver update/install. I have done several Flash Stocks but the problem persists. Is there some kind of “Super” Flash Stock that is guaranteed to update every conceivable “device identifier” stored anywhere so that I can again access my Nexus 7 as an MTP Device using Windows Explorer or other programs?

    • WugFresh says:

      Flashing stock does wipe everything. You could go to ‘advanced utilities’ > launch cmd prompt > and with your device in bootloader mode, type the cmd’s:

      fastboot erase system
      fastboot format system

      Then reflash stock. If that doesn’t work, its either a hardware issue, or related to something (configuration) with your comp.

  86. Raja Sekhar says:

    Thanks for the Application. it saves me a lot of time. works on win 8.1 64 bit flawlessly.

  87. ronjcar says:

    I am trying to get my Nexus 7 v2 back up and running. I can’t get it past the screen that says “Google”. I can’t get my computer to allow me to use any of the ADB connections. The only one that seems to work is the Flash Stock + Unroot (Soft-Bricked/Bootloop). It brings up the cmd screen and runs some things, but they all say FAILED. It tells me to press any key to exit and nothing on my tablet has changed. I have tried everything the instructions have told me to, but nothing. It seems nothing can talk to my tablet. Anyway to force my tablet to except this stuff. My N7 goes up on the Device Manager list of windows, so it is being recognized. I can get to the bootloader screen also. Not sure what my next step is. Please help. Thanks.

    • WugFresh says:

      Have you unlocked your device yet? Unlocking is a prerequisite for flashing stock. If you have unlocked, please post a screenshot of the failed flash. Cheers.

      • ronjcar says:

        It says on the bootloader screen that my locked state is locked. How can I change that without my tablet turning on? I can only get to the startup screen that says “Google” and this bootloader screen.

        • ronjcar says:

          I see now the unlock section of the Toolkit. I was hitting the OK button I think each time and it would not do anything. I now have the Unlock bootloader screen on my tablet and have clicked yes. Pressed the power button and nothing. Seems to just stay highlighted on Yes and does not change from there.

          • WugFresh says:

            Try alternate USB cord, and/or port. Or try removing the usb cable when you see that screen before pressing the Yes (via the power button).

          • zeut99 says:

            I am having the same problem with it getting stuck on the “unlock bootloader” screen after trying to run the unlock tool. Also tried removing USB cable when I see the screen, does not change anything. Otherwise my situation is exactly the same as the original post from ronjcar.

        • WugFresh says:

          You don’t need your device to be on to unlock. Just stay in bootloader mode, and use the toolkits unlock button. It will ask you if you want to ‘automatically boot into bootloader’, or if your want to do it manually. Chose the option to do it manually. Cheers.

  88. mikelor says:

    I have the same issue as @ronjcar. However when I use the Fastboot and Flash Stock & Unroot, it fails, with a “Flash Write Failure”.

    Flash Stock + Unroot…
    sending ‘bootloader’ (3911 KB)…
    OKAY [ 0.141s]
    writing ‘bootloader’…
    FAILED (remote: flash write failure)
    finished. total time: 90.760s

    rebooting into bootloader…
    OKAY [ 0.008s]
    finished. total time: 0.010s
    sending ‘radio’ (76038 KB)…
    OKAY [ 2.401s]
    writing ‘radio’…
    FAILED (remote: flash write failure)
    finished. total time: 92.640s

    Created filesystem with 11/35840 inodes and 4616/143360 blocks

    checking product…
    OKAY [ 0.004s]
    checking version-bootloader…
    OKAY [ 0.005s]
    checking version-baseband…
    OKAY [ 0.005s]
    sending ‘boot’ (7018 KB)…
    OKAY [ 0.229s]
    writing ‘boot’…
    FAILED (remote: flash write failure)
    finished. total time: 90.195s

  89. Rocky says:

    i have used this toolkit for as long as i have gotten my nexus 4. never had any problems. until latest update. as soon as app says “rooting” after phone reboots, i get this error message “line 19433 (file “C:program files (x86)wugfresh developmentnexusroottoolkit.exe”):

    error: variable used without being declared

    • WugFresh says:

      Please try again. I have never received any errors when rooting. And looking at my code, I am really unsure how that error could even be present at that point. Please confirm you are running v1.8.7. Also, during the root procedure don’t press other toolkit buttons.

      • Rocky says:

        i never press any buttons. i let the process complete fully before doing anything else. anyways i did a manual root as i did a clean install and didn’t work. thanks for the program anyways. always was useful since day 1 i got it.

        • WugFresh says:

          I am a bit confused. I would to try and reproduce the error if I can, but I don’t understand what you are describing. “i did a manual root as i did a clean install and didn’t work” .. I don’t know what this means.

          • Dan Yargici says:

            I just experienced the exact same error. Nexus 4. Seemed to happen right at the end after the final reboot, just after it said device detected…

            Anyways, it seems to have rooted fine, regardless.

  90. Nirjhar Mistry says:

    Hi! I’m getting this error message all time. I did reinstall the program but still having the same problem. I’m on windows 8.1 64bit Pro.

    • WugFresh says:

      I run win 8.1 64bit, and I have tested this program extensively on every supported windows OS (xp–>8.1, 32/64bit); so this error you are getting is not related to my program, but rather, windows specific. Have you tried basic windows clean-up, and maintenance trouble-shooting, like running ccleaner for registry errors. I have never even heard of gdipp until you posted that. But here is the official page for it. <<- did you install this? Maybe you made a bad install. Sorry man, but this program is totally not related to my program. That is the most I can help.

  91. Moris Vnucec says:


  92. gautam behal says:

    after updating the app to the latest version 1.8.7 whenever I click on push files and folder, after entering the location when clicked on Ok the program gives a popup saying Done! and when i click on ok the app closes.

    I tried uninstalling and re installing the app again! no go.

  93. CVB says:

    I have a Nexus 4.4.4 and everytime I go to do the pda net drivers and click ok some downlad and others do not. I am trying not to ruin my phone. help please.

    • WugFresh says:

      Maybe try solution #1 instead. Or proceed to the driver test. Just an FYI – if you configure your drivers incorrectly, its not going to ruin your phone.. the program simply won’t work, and you will get a message that it can’t find your device. So need to worry. Just attempt to configure your drivers, run the driver test.. and if it works, proceed – if it doesn’t try again with another solution.

  94. CVB says:

    Hey I have nexus 4.4.4 and every time i go to do the pda net drivers some download and others do not. i really dont want to mess my phone up please help.

  95. jjfabbsy says:

    Hi – when attempting to backup SD card on android 4.4.4 – the toolkit says the device needs to be UNLOCKED first. Does this mean not on lock screen or the type of unlocked that wipes everything? Also what is the best backup option to backup EVERYTHING including virtual SD – so that I can restore a complete mirror of my pre-rooted device? Thanks for the software and will of course donate post-root 🙂 p.s using Nexus 10

    • WugFresh says:

      Hey, I really need to add a detailed response to this in the FAQ, and my apologies for the late response.
      – Toolkit unlocks the bootloader, which factory resets; Nexus devices don’t have an ext-sdcard partition so factory reseting wipes EVERYTHING including virtual sd.
      – The best backup solutions are available post-unlock+root such as full nandroids, and powerful root apps like Titanium Backup
      – The most complete (and recommended) backup solution and procedure with a locked device is as follows:

      1.) Create an androidbackup with neither shared nor system apps checked. The reason being (not to check them), is because ‘shared data’ attempts to backup things like your pictures and some sdcard data but from testing seems to do an incomplete job – resulting in a much larger backup file, but a false sense that you have everything backed up. Checking ‘system’ data is not recommended because restoring system data is known to potentially cause issues (better to re-configure system settings manually), and will definitely cause problems if you attempt to restore the system data on a different ROM or version of android. If you are currently running the same version of android that you plan on running post-unlocking, then backing up and restoring system data might actually work for you (and save you some time), but it is recommended to also make another androidbackupfile without system data, incase the one where its included doesn’t work so well for you.

      2.) Manually backup your important non-app data like pictures/videos/music/documents that are on your sdcard via copy+paste with windows explorer or with cloud storage. Also backup any folders on your sdcard that appear to be auto-created by games on your device. Some game apps download a lot of extra content and don’t save that stuff in the standard app/data dir but rather store it in some sdcard dir. If you want to be super safe, you could just backup your entire sdcard and then restore stuff back selectively.

      3.) Backup SMS and call logs if you care to keep that. You could also backup contacts however they more likely auto-synced with your gmail account.

      4.) Unlock and root your device.

      5.) Sign into your primary gmail during initial setup and let google play automatically restore your apps. Androidbackupfiles do not backup your PAID apps, they do however backup your FREE apps + app data for BOTH your free and paid apps – so you must let google auto-restore your apps first.

      6.) Restore your androidbackupfile.

      7.) Reconfigure your system settings manually (like email accounts, stock home launcher layout, etc)

      8.) Copy+paste back any sdcard stuff you want

      That’s it.

      This will give you the most complete and cleanest restore possible. The main annoyance will be re-setting up your email accounts and homescreen layout (if you use the stock android home launcher); other than that, you will have everything back and be back to where you started.

      Like I mentioned, once unlocked+rooted you have all the best backup options available; that is why, in the future it is recommended (in my opinion) to unlock a Nexus device right away when you get it, so you can avoid the hassle of backing up without full system access.

      Hope that helps. I will clean this post response up and move it to the FAQs asap. Cheers.

  96. Jay says:

    Thanks for your gr8 work
    I am planning to buy nexus 7 lte. does still these are having issues …
    and after unlocking > root>
    does the warranty is going to void….
    or after relocking and using unroot option. …I would again get warranty back……
    plz rply…thanks …

  97. Emiliano Parizzi says:

    It’s not clear if unlocking the device wipes media data (pictures, videos, songs)… Most recovery full wipes doesn’t wipe media. Anyway, if it does wipe media, how to back it up if the backup data/media needs the device to be unlocked…..?

  98. FuMiYu says:

    hello, im using the modified rom cataclysm 4.4.2 for my nexus 5, i’d like to install TWRP for it using Nexus tool kit, but i got stuck in download modified_boot_img_4.4.2, it completed downloading but has a mismatch check, pls help !!! tks in advance

  99. Bob F says:

    I successfully did a “Create Android Backup File” and after “Restore” all my SMS data is missing. Was I mistaken in assuming the Tool Tip saying “…backup file with all your user apps+data, system apps+data and shared data” would include SMS data?

    • WugFresh says:

      There is a special SMS backup feature as well. That said, I believe sms gets stored in an sql database
      here: /data/data/, which would be considered system data. You could try using the paid app Titanium Backup which can unpack ab files, and try to selectively restore the phone/messaging app data and see if that works. Please report back. Cheers.

  100. andrei312 says:

    hello i have a problem: every time i try to root or unlock,it tells me that “ADB device was not found” and i did all the driver installation/configuration guide

  101. Lisa says:

    I am trying to recover data from my soft-bricked Nexus 4. Can I use the toolkit for this? I can’t seem to make it work because the phone is stuck in fastboot, locked.

    • WugFresh says:

      If the bootloader is locked, there is very little you can do. Your best option is to try and wipe cache (JUST cache, NOT data & cache – aka ‘factory reset’) with the stock recovery. Without the toolkit, in bootloader mode;

      – Switch the big green START to the red RECOVERY via volume keys, then press power to select; you’ll see an image of an Android robot with a red exclamation mark and the words “No command.”
      – While holding down the Power button, press the Volume Up button.
      – Use the volume buttons to scroll to “wipe cache partition” and press the Power button to select it.

      Hopefully this will allow you to boot up. If so, backup your data, and consider unlocking your bootloader and performing a full factory flash via “Flash Stock + Unroot”. Cheers.

      Edit, here I found a youtube video:

      • Lisa says:

        Thanks for this, I was able to wipe the cache using your directions. Unfortunately, though, the phone would not boot up after that. I tried a couple times and now something extra-weird is happening: the phone won’t power down. When I hold down the power button, it just goes back into the loop (with the Google circles going in and out).

        • WugFresh says:

          Unfortunately if your bootloader is locked, and that’s happening – recovering any data is not going to be possible.

          To get your device working, try doing a factory reset from stock recovery. If that doesn’t work, use the toolkit to unlock.. And then use “Flash stock + unroot” with “softbrick/bootloop” checked, and follow the instructions.

          • Lisa says:

            Okay, thanks, I lost the data but at least I have my phone back. Have no idea how it got into that state! Thanks for helping me get it back!

  102. Figgy says:

    Hi, I’m having a problem, I can’t access the options in nexus root toolkit. My computer is running in win 7 64 bits. What can I do?

  103. Scott says:

    You are a genius! I was running Android L on my Nexus 5 and wanted to take it back to 4.4.4 After flash, phone would not boot past Google screen. Refreshing did nothing. Your program fixed EVERYTHING with a couple of clicks. I will be donating to you.

  104. SXK says:

    Can Nexus Root Toolkit be used to root Android One too?

  105. Joe knows who I am. says:

    First, thank you for an amazing Toolkit! While I’m fairly new to rooting, I’ve successfully jailbroken Apple products previously and this Toolkit is a welcome, well thought out, versatile one.

    I’m in the process of rooting my Samsung Google Nexus S, which I purchased as an unlocked device direct from Google and run on T-Mobile. I successfully installed the drivers and proceeded through the unlock process. For all intents and purposes it appears to have been at least partially successful. I received the “Success” message, went through the ADB Bootloader/Fastboot process, reverted to stock, and it’s unlocked.

    However, I’ve been using QBking77’s video, which is not exactly the same model, but appears to be as close as I could find to mine which uses the Toolkit. When I attempt to Root the phone while also Flashing a Custom Recovery, I receive the script message that the ADB Device was not found. In addition to being unlocked, I’ve unlocked Developer mode, activated USB debugging, and switched off MTP. Should I proceed through the Full Driver Installation process again? Is there something that I might have missed in the steps? Prior to the Unlock, I did do a Backup, admittedly against your direction, of my System Apps +Data, though I am pretty sure that I relocated everything off of my phone. Could this have an effect?

    Any next steps or suggestions would be most helpful at this point as I’m stuck at the moment.

    Thanks again.

    Marc AKA: Joe knows…

  106. Sean William Robertson says:

    Does not work on Nexus 7 (2012) I keep getting the “Fastboot device was not found” even though I am in bootloader as I do it, tried every single “solution” that is given and it will not work.

    • jason says:

      i used this and was able to root my n7 2012. go to the advanced tab and follow the instructions for deleting the drivers, that’s what i had to do.

      • Sean William Robertson says:

        Yea I managed to delete ALL my drivers for all my android devices then reboot then had to go through about 40 more steps to get it to work… not as simple as many people say. Basically “If your device is bricked, then the best thing to do is to not have it bricked… your welcome 😉 “

    • WugFresh says:

      Sorry you are having difficulties. I made the driver installation as simple as humanly possible. Its not related to me software, its a windows/comp specific issue. My best recommendation would be to try an alternate usb port and/or cord and/or computer and try Solution#1 (automated) or Solution#4 (manual). I have tested and confirmed the driver installation on every single version and architecture of windows (xp to win10 tech-preview/enterprise), as well as many other users. I hope you get it resolved. (Also try disabling MTP on your device; settings > storage > menu item in upper right > mtp > uncheck).

      • Sean William Robertson says:

        There was nothing wrong with the software. The device I was trying to fix was just in the worst possible state, it was bricked at the boot animation, developer options were never enabled, it was bricked so obviously couldn’t enable or disable any MTP options, and the bootloader was locked and the PC wouldn’t recognize it, it would show up for a second and try to install the drivers but would always fail so the software kept saying “fastboot device not detected”. After a couple of hours using every bit of advice I could find I finally managed to unlock the bootloader and I just kept hitting retry on the softbrick +unroot option till it eventually worked.

  107. jason says:

    i have 4.4.4 on my 2012 and i want to go back to 4.3, is this possible?

    • WugFresh says:

      Yes, you can flash any available android version to your device easily with the toolkit. When you hit the flash stock + unroot button, there is a pull down menu where you can select which build you want to flash. Cheers.

  108. This is a lifesaver. Due to some irresponsible rooting/experimenting, I’d got my phone stuck in a bootloop. I was able to flash back to stock and OEM Lock it to prevent me from ever bricking it again. WugFresh, many thanks.

  109. Ali says:

    It broke my nexus 5 I am so mad

  110. irsan ehc says:

    how to on my nexus 4 without power button ? help me pls.

  111. Connor says:

    Quick question, I’m a flashing/rooting noob and I used CM installer to put CM on my Nexus 7, and now it is stuck on the CM boot animation, it’s rooted, unlocked and I am able to access the boot-loader, will this work for me? I need to use it on a different computer to normal, so it won’t have any drivers for it.

  112. Irsan Ehc says:

    I can on/boot my nexus despite having broken power button.

    Combination of, hold volume button (down) then insert charger, the nexus 4 will boot to fastboot mode.

    Then using NRT just reboot the nexus 4. And now! The nexus 4 is on!

    Thanks a lot to WF!

  113. Markus Baumstamm says:

    Great work!!

    I was rooting Nexus 4 running on KitKat 4.4.4 and it ran smoothly and all my data is still there without using any recovery.

    How is that possible? You wrote, that everything gets wiped…Root works, so it ran through perfectly 😉


  114. Dwight Spade says:

    my nexus 7 2012 gsm crashed and i could not get it to master reset I am trying to flash back to factory but I keep getting a bootloader not supported message. This update requires bootloader 4.23 mine is 4.13, I was wondering if you could give me some help to get past this problem

  115. Timothy Smith says:

    Hi WugFresh,

    My nexus 4 is suffering from softbricked/ boot loop problem. To make matters worse my usb debugging is NOT enabled.

    I am not able to unlock bootloader and “ADB device not found” error is coming which I believe is because my usb debugging is not enabled.

    I tried Flash Stock + unroot option but as I said before bootloader is locked and since usb debugging cannot be enabled (bootloop issue) I am confused. Can you guide me or point me to the steps that can help me recover my phone?

    • WugFresh says:

      You can unlock and flash stock purely in bootloader mode. No USB debug required. The unlock script asks if you want to start in bootloader mode. Do that. Then flash stock + unroot with softbrick bootloop mode.

  116. jewishjew says:

    hey man running 4.4.4 wifi model cant find a adb thingo factory wiped changed cable used all the diffrent drivers help?

  117. JohnnyDroid says:

    Hi Wug :), is it needed to have installed Java Runtime (JRE) to run properly your Nexus Root Toolkit?
    Thanks 🙂

  118. Allison says:


    My Nexus 4 is stuck on a boot loop. I am unsure if usb debugging is enabled or not. When I run the tool kit I get the message

    “Tool Kit would like to download this: modified_boot_occam_4.4.4_KTU84P.img”
    ‘OK’ to continue, it says
    “Status: Complete!”
    “Hashcheck: Mismatch”

    “NRT File Download incomplete / hashcheck – mismatch”
    ‘Cancel’ to end operation
    ‘Try Again’ to retry autodownload
    ‘Continue’ to manually download

    Followed by:
    “You currently have no TWRP recovery for your build in the local directory

    “Tool Kit would like to download this: openrecovert-twrp-”
    ‘OK’ to continue, it says
    “Status: Complete!”
    “Hashcheck: Mismatch”

    “NRT File Download incomplete / hashcheck – mismatch”
    ‘Cancel’ to end operation
    ‘Try Again’ to retry autodownload
    ‘Continue’ to manually download

    I do not know what to do and am asking if you could help with instructions. Please and thank you!

  119. ayush shahi says:

    can i install Android L on Nexus 7C 4G by NRT 1.8.8?

  120. Chad Thornley says:

    Hello all,

    So my Nexus 7 (2013) is stuck on a boot loop where it only displays the Google screen – endlessly. I have the “Force Flash” enabled and when I attempt to run the ‘Flash Stock + Unroot’ option for a soft-bricked/Bootloop unit it just pulls up and shows:

    Flash Stock + Unroot…

    erasing ‘boot’…

    It will sit here like this for hours, not doing anything. Does this process normally take longer, and I am just being impatient? If I press the power button on my tablet in the midst of this it finally pulls up the following text…

    FAILED (status read failed (Too many links))
    finished. total time: 1830.262s
    erasing ‘cache’…

    erasing ‘recovery’…
    FAILED (status read failed (Too many links))
    finished. total time: 277.391s
    erasing ‘system’…
    FAILED (command write failed (Invalid argument))
    finished. total time: 0.048s
    erasing ‘userdata’…
    FAILED (command write failed (Invalid argument))
    finished. total time: 0.003s

    sending ‘bootloader’ (2100 KB)…
    FAILED (remote: Bootloader is locked.)
    finished. total time: 0.009s
    rebooting into bootloader…
    OKAY [ 0.007s]
    finished. total time: 0.008s

    sending ‘boot’ (4994 KB)…
    FAILED (remote: Bootloader is locked.)
    finished. total time: 0.008s
    rebooting into bootloader…
    OKAY [ 0.007s]
    finished. total time: 0.008s

    sending ‘recovery’ (5534 KB)…
    FAILED (remote: Bootloader is locked.)
    finished. total time: 0.009s
    rebooting into bootloader…
    OKAY [ 0.007s]
    finished. total time: 0.008s

    erasing ‘system’…
    FAILED (status read failed (Too many links))
    finished. total time: 680.988s

    rebooting into bootloader…
    OKAY [ 0.017s]
    finished. total time: 0.018s

    erasing ‘userdata’…
    FAILED (status read failed (Too many links))
    finished. total time: 234.669s

    Any help would be so greatly appreciated! Would hate to lose my Nexus…

    • WugFresh says:

      First thing to try would be an alternate USB port and/or cable. Also try rebooting your computer. Those errors are indicative of a wonky USB connection. To answer your first question; No – erasing boot should like like 1 second. Let me know if you get everything resolved. Cheers.

      • Chad Thornley says:

        I appreciate the suggestion… but it seems to still be an issue. I have restarted my computer multiple times, and tried at least two other cables. Seems that it is still an issue though as it will just sit here for ages not changing at all. Attempting to unlock the bootloader freezes, as does anything else I seem to try… Any other thoughts??

  121. nexus 7 says:

    My nexus 7 2012 doesn’t rotate the screen after update to kitkat using the tool what can i do ?

  122. Helder says:


    Im stuck on “Waiting for your device…” each time i try to root my Nexus 7: Asus 2012 Tablet :/

    The drivers test runs perfect, i’ve already reinstalled my drivers and still having the same problem, after a few minutes stuck on “Waiting for your device..” I get “Waiting for device operation timed out.” Plus alot of troubleshooting options that I have already tryed..

    Any opinions ?

    • WugFresh says:

      Have you accepted the RSA security prompt, and checked ‘Always allow from this computer’ when you were setting up usb debugging? Looks something like this:

      And when you say, it gets stuck on waiting for device.. at that stage, what state is your device in? Is it on? Or is stuck in bootloader mode? Are you 100% certain you selected the correct Nexus7 device in the kit? There are four available options to choose from.

    • Sirbubbz1990 says:

      exact same issue

    • SirBubbz says:

      hey just got mine to work i believe u didnt actually unlock it while fiddling with mine the nexus popped a screen that asked if i wanted to unlock then pug said that would happen if it is unlocked it would say so at the bottom of ur bootloader screen and well as a lock symbol at the bottom of ur “Google”
      loading screen when turning on the device

  123. Ty says:

    Hey there, Wug! Had Android L Developer review installed. Was a bit buggy and was interfering with other apps. This made reverting back to stock 4.4.4 an absolute breeze. Well done and thank you! BTW, will you have the new 5.0 Lollipop Images on here when Google officially releases them later on this week? 😀

  124. Adi says:

    Hi there,

    I am having a problem with unlocking the device. I run the toolkit and it sucessfully unlocks the device and shows up as unlocked at the bootloader screen. But when I need to restart in bootloader to do the flash stock + unroot, the device locks back up again. Any workaround to this?

  125. Gaige says:

    Hey Wug, this program is extremely useful but I’m having a real hard time getting this to work with my nexus 7 2012 tablet. I’ve got Windows 8.1 64-bit to pick it up as an ADB device, but when it gets into fastboot it doesn’t recognise the device and windows pops up saying “USB device not recognised”. Device manager also says that the nexus is “Unknown USB Device (Device Descriptor Request Failed)” and I have no clue what I’m doing wrong. I’ve gone through the driver install tutorial and tried all four of the solutions but it’s still doing the exact same. Any clue as to what’s wrong?

  126. markyfromars says:

    Instead Lollipop they will give us another new version of Android L
    Preview codename lpx13d. In a few minutes

  127. Frank Bostick says:

    You guys are awesome. I’d banged my head against the wall trying to unroot and relock my Nexus 5 to receive the OTA for “L” in a few weeks. Id installed Clockwork mod recovery. Following the LONG way around using command prompts, etc got me no where. XDA suggested that you not use an automated script. Then I found your script. Boy am I glad that I found you. Getting back to stock was simple. Just a few clicks…. Took a few tries to get the phone locked again. But its all stock now and ready for the OTA.
    Thanks again! You will be seeing a donation for your hard work and simplifying the process so drastically!

  128. SnakePlisskin77 says:

    This is tempting, but I’m just going to wait for Android L to make its way to my Nexus 7 2013 tablet.

  129. Ardy says:

    Hi. Long story short, my N5 has no OS installed (does have TWRP).
    Anyways, I downloaded the stock factory image from Google and attempted to flash it through the toolkit..
    It successfully imported, but whenever I type the md5 hash in the “Hashcheck Verification” screen, it is a mismatch (BUT I am typing the correct md5 checksum!).
    help… pls… Thanks!

  130. Fabio Cannas aka sna says:

    I’ve just uploaded the toolkit to the latest version but the hashcheck continues to fail…! this happens from a long time 🙁

  131. Rick says:

    I flashed Android5.0.09 LPX13D onto my N7 (2013) today… unlocked fine, but when I go to Root it, I get a message “SuperSU v2.13 is no capable of rooting this build. Wait for SuperSU update to try again.” I checked out the lasted SuperSU.. guess there is a v2.14.. will this one (once you add it to the root toolkit, allow rooting of Lollipop I have?

    Thanks for this program btw, have never had any issues with it. works GREAT.

  132. Ajith Simha says:

    Hi there,
    With nexus 4, I tried to FLASH STOCK+UNROOT, it says – “AutoIt Error – Line 15664, Array variable has incorrect number of subscripts or subscript dimension range exceeded.” With v1.8.9. Please help me, my phone is needs it 🙁

  133. Ardy says:

    Hi. Long story short, my N5 has no OS installed (does have TWRP).
    Anyways, I downloaded the stock factory image from Google and attempted to flash it through the toolkit..
    It successfully imported, but whenever I type the md5 hash in the “Hashcheck Verification” screen, it is a mismatch (BUT I am typing the correct md5 checksum!).
    help… pls… Thanks!

  134. Jay says:

    I have a AutoIt Error – Line 15664 error??

  135. mikelor says:

    Getting Flash Write Failures on my Nexus 7. I’ve been able to use NRT successfully in the past, any clue on where to look next?

    FAILED (remote: flash write failure)

  136. Ardy says:

    Hi. Long story short, my N5 has no OS installed (does have TWRP).
    Anyways, I downloaded the stock factory image from Google and attempted to flash it through the toolkit..
    It successfully imported, but whenever I type the md5 hash in the “Hashcheck Verification” screen, it is a mismatch (BUT I am typing the correct md5 checksum!).
    help… pls… Thanks!

  137. none says:

    SuperSU 2.14 released

  138. sonofjon says:

    Can you relock without unrooting (the hover info box for OEM Unlock says to “use the ‘Flash Stock + Unroot’ before running this”)? I have used NRT to successfully unlock and root my Nexus 7 (2012). Now I want to lock the bootloader while keeping root. Can it be done with NRT?

    • WugFresh says:

      Yes, relocking the bootlader will work without flashing stock first. That said, if you have problems in the future, it will make it more of a hassle to deal with. In particular, you will have to unlock the bootloader again (which wipes) if you needed to flash stock (or fastboot boot/flash any img file for that matter). If you understand these limitations of relocking the bootloader, and still want to (I am guessing for security reasons?), then for sure – go for it, you can disregard that info.

  139. SockMafia says:

    Flashed my Nexus 7 2013 WiFi with no issues. Thanks.

  140. Paolo Raymondi says:

    And for mac? When? 🙁

  141. nicknickhoho says:

    Is it possible to root Android L now? Thanks.

  142. Samuele Trotto says:

    I have installed factory image of Android 5.0 on my Nexus 5 with NRT. Now i must come back to stock 4.4.2 but the Full Driver Test doesn’t work! T.T I try it a lot of times, but it doesn’t work yet. I unistalled old drivers, instaled new drivers, used Google drivers and also Universal Drivers or Pdna Drivers..but it doesen’t work! Help me 🙁

    • WugFresh says:

      Have you tried alternate usb ports and/or cables (also rebooting your computer?). You actually only need your fastboot drivers configured to flash stock – so you could use flash stock + unroot (softbrick/bootloop mode) and follow the instructions from there. If your computer can see your device when its in bootloader, then you should have no problems flashing stock and returning to 4.4.2.

  143. jerby nicdao says:

    sending ‘bootloader’ (3911 KB)… OKAY [ 0.135s]
    writing ‘bootloader’…
    FAILED (remote: flash write failure) finished. total time: 90.787s
    rebooting into bootloader…
    OKAY [ 0.009s]
    finished. total time: 0.010s

    sending ‘boot’ (7050 KB)…
    OKAY [ 0.242s]
    writing ‘boot’…
    FAILED (remote: flash write failure)
    finished. total time: 90.185s
    rebooting into bootloader…
    OKAY [ 0.008s]
    finished. total time: 0.009s

    erasing ‘cache’…

    need help please this is all i get…
    i believe i bricked my nexus 7 2013 no recovery and no os installed
    bootloader version FLO-03.14
    lock state – unlock

  144. Guest says:

    sending ‘bootloader’ (3911 KB)…
    OKAY [ 0.135s] writing ‘bootloader’…
    FAILED (remote: flash write failure)
    finished. total time: 90.787s
    rebooting into bootloader…
    OKAY [ 0.009s] finished.
    total time: 0.010s

    sending ‘boot’ (7050 KB)…

    OKAY [ 0.242s] writing ‘boot’…
    FAILED (remote: flash write failure)
    finished. total time: 90.185s
    rebooting into bootloader… OKAY [ 0.008s]
    finished. total time: 0.009s

    erasing ‘cache’…

    need helps please
    bootloader version flo 03.14

  145. monstrousmoran says:

    Hi im very much new to doing this type of thing and I kind need some help walking me through the process of unrooting my nexus 5. I had a friend root it and I have no use for it and I would like to get rid of it.I don’t have anything installed on my computer right now. Help please.

    • WugFresh says:

      Check out one of the many videos on youtube. The toolkit walks you through everything. Backup anything you want to keep, then use “flash stock + unroot”, and then relock it – and you will be back to stock.

      • monstrousmoran says:

        I looked at Babbling Booleans video and I followed it all the way through and when I tried to flash the stock ROM it said that I did not have the proper driver packages. And I installed them and it still did not work. I had USB debbuging on and I switched the USB ports as well to see of a different one would work. I lost the original charger for my nexus 5 and I’m using a Samsung tablet cord and that could be the issue please help

  146. prince says:

    sir not download nexus root toolkit plz help

  147. Kishore says:

    Will this work in Windows 7 32 bit system.

  148. Andrea says:

    con questa procedura perdo i dati o no
    se root lollipop perdo qualche dato ??

  149. Carey Parks says:

    Hey Wug, small problem. My original N7 soft bricked. Trying your “Flash Stock & unroot” to get it going again. Seems to work until near the end it hits this:

    checking product…
    OKAY [ 0.030s]
    checking version-bootloader…
    OKAY [ 0.025s]
    sending ‘boot’ (4994 KB)…
    FAILED (remote: Bootloader is locked.)
    finished. total time: 0.269s

    I tried manually starting the device with normal power on, restart bootloader and recovery mode but nothing goes anywhere.

    I did some searching found I could unlock the bootloader via ADB, but ADB doesn’t find the bricked device, even tho your thing seems to be able to. The USB connect sound plays, but I guess I can’t put the device in the debug mode since it’s bricked. Ideas?

    Thanks for the great tool man.

    • WugFresh says:

      You don’t need to be connected via ADB (on with usb-debug enabled) to unlock. You just be connected via FASTBOOT (bootloader mode). Just use the “Unlock” button, and follow the instructions it gives you to MANUALLY boot your device into bootloader mode, then proceed from there. Its fine that your device is messed up.. you just have to get the bootloader unlocked. Once its unlocked you can use “Flash Stock + Unroot” with softbrick/bootloop mode to get your device back to normal. Cheers!

      • Carey Parks says:

        Thanks for the quick reply! Sadly, the unlock runs, the device says “Unlocking bootloader” or something similar, and then goes dark. The USB is still connected, but sitting for 30 mins – nothing happens. Manually starting in bootloader (pwr & vol down) gives USB off sound and USB on sound. Running “Flash Stock & Reboot” goes like this:

        Flash Stock + Unroot…


        erasing ‘boot’…

        OKAY [ 1.160s]

        finished. total time: 1.165s

        ******** Did you mean to fastboot format this partition?

        erasing ‘cache’…

        OKAY [ 3.056s]

        finished. total time: 3.061s

        erasing ‘recovery’…

        OKAY [ 0.176s]

        finished. total time: 0.176s

        ******** Did you mean to fastboot format this partition?

        erasing ‘system’…

        OKAY [ 0.005s]

        finished. total time: 0.010s

        ******** Did you mean to fastboot format this partition?

        erasing ‘userdata’…

        OKAY [ 0.005s]

        finished. total time: 0.010s

        sending ‘bootloader’ (2100 KB)…

        FAILED (remote: Bootloader is locked.)

        finished. total time: 0.030s

        rebooting into bootloader…

        OKAY [ 0.020s]

        finished. total time: 0.020s

        And then nothing happens. Simple power on does nothing. Boot to bootloader and I’m back where I started. Rinse and repeat. No change. Maybe the device is a goner? In which case I’d like to be sure any personal data isn’t accessible to the folks I return the device to. Thoughts on that? Thanks much. C

        • WugFresh says:

          You are going to want to try factory resetting and trying to unlock again (and flash stock again) The factory reset will take care of your user data, so if your device is actually fried, then at least you wont have to worry about that. Actually, looking at the above text you posted. It looks like it already erased your data partition – so your device is already wiped. I would keep trying to get that bootloader unlocked… if you can, you will be all set. Try a different computer, a different usb port… etc. You could also try to issue the comamnds (NRT advanced utilities > launch cmd prompt):
          fastboot format system
          fastboot format data
          fastboot format cache

          • Carey Parks says:

            Thanks Wug, I’ll have a go this evening. Good to hear it’s wiped.

          • Carey Parks says:

            No joy getting past the lock, but as it seems any personal data has been wiped I’ll just do the warranty return and enjoy my 2013 N7. Thanks for the help, and thanks for the amazing tool.

  150. Agam Oberoi says:

    im getting an error nexwug_downloader.exe cannot be found be windows while flashing stock. Please help

    • WugFresh says:

      Check your antivirus, it probably falsely flagged that exe and quarantined it. Add an exception to your AV for that file or the install location of this program, and either restore the file from your virus-chest/quarantine folder or re install the toolkit. Also, please tell me which AV provider you use so I can report it to them. Cheers.

  151. Agam Oberoi says:

    I have this error when I’m trying to flash stock or unroot.
    It says that “Windows cannot find nexwug_downloader.exe”
    Please help as soon as possible.

  152. Jumbles says:

    Avast is currently reporting all download links as having Win32:Dropper-gen [Drp]

  153. putt he says:

    Please give me a hand.
    I just use your great NRT to restock my old nexus 7(2012) to 4.2.
    When im fail to ota update to 4.3, i use NRT to do the oem lock again. But the OTA is still failed.
    So i want use your NRT to upgrade to 4.4.2 directly.
    But the weird things happen. I can’t make Windows 7 recognize my nexus in fastboot, but i just use NRT to flash a stock rom in Fastboot!
    And then i try all the method i could found to find a fastboot driver but with no lucky.
    Is there sth wrong in my bootloader? How can i fix it?

    Here is my progress in brief:
    – a nexus 7(2012) with oem unlocked.
    – use NRT to flash stock “nakasi-jdq39-factory-c317339e” (fastboot driver is good)
    – ota update failed in stock 4.2
    – use NRT to do oem lock
    – oem lock is ok, but fastboot driver is not good anymore.

  154. Sam says:

    What’s the latest Version for Wug’s Toolkit for the Galaxy Nexus? I’m running KitKat, so once I bring my phone back to stock, would it pick up ICS or KitKat? I’m on Verizon. Thanks.

  155. Brockalicous Merkwan says:

    is there a linux client?

  156. edward jinks says:

    When in recovery after pushing root files to my Nexus 4 running android lollipop preview, the perm recovery flashes however UPDATE – SuperSU – V2.14 always fails with the error (E: Unable to open zip file.). Any advice? Thanks,

  157. Maximus says:

    Whenever I try to flash a rom. It imports the image but always hashcheck mismatch and then cancels

  158. Scipizoa says:

    quick q, in the option of nexus took kit i noticed the root options installs twrp, supersu and quickboot, do i really need quickboot if i can get the same exact options in the power menu when i hold the power button?

  159. Sam says:

    Hey Wug, I’m running KitKat, so once I bring my Verizon Galaxy Nexus back to STOCK, would it automatically pick up JellyBean or do I need to like flash those extra? I want to bring my phone back to stock and do a hard reset. I need to do this by today as I’m selling it today.

    • WugFresh says:

      The toolkit lets you flash any official version of android available for your device, so when you press “Flash Stock + Unroot” there is a pull down menu to chose which version. Just chose the latest official jellybean for that gnex.

  160. Sam says:

    I’m running Windows 8.1 and I see no success when installing the “google drivers” for my Galaxy Nexus Verizon.

  161. Fatih Özaltun says:

    Can i use it on nexus 4 – android 4.4.4 ?

  162. Meraz Bin Mizan says:

    Bro, today suddenly my Nexus 5 turned off and after that it stuck on google logo. I tried but can’t recover. Would you please help me? Please!

  163. OAR_John says:

    Just did this on my new Nexus 5. Worked like a champ (and a donation of thanks was sent). Thank you!

    • WugFresh says:

      Thank you!!

      You’re receiving this message because you’re signed up to receive notifications about activity on WugFresh.

      < img src =” https :// /proxy/ ChqEwCm-JLMQkexL0RmS-1dpFKCu3zBKU-p-rV3b0 _ Qo2u5nidOoIcDdLpFDIT3OnnqY8JhcrRScDboSceUhFF9SbpOeShm-6o5RrSFCUwaOHg =s0-d-e1-ft#http:// /1413230218/images/email/ logo-gray.gif “>

  164. nicholas says:

    my nexus 5 is stuck in the android logo, how can i get out of this?

  165. Markus Maal says:

    I have rooted my Nexus 7 using this

  166. David Dupre says:

    Hey Wug. So my father has a nexus 7 2012 edition. It was never rooted. It updated to 4.4.4 recently as he is slow to getting around to updating it. Since he updated it started freezing up and restarting all the time. So he did a factory reset. It rebooted into recovery to factory reset and i guess it was wiping and suddenly went to a screen with the android guy with a red triangle and exclamation point. He so he let it sit for a bit and it did nothing. so he rebooted. it finally loaded into android, seemed to be fine all the sudden, but it rebooted itself again and now it doesnt go past the google screen. He can get into recovery but the problem is, its not unlocked and he cant enable usb debugging because he can’t get into the OS to enable it. Where should he go from here? He lives a couple hours away so i can mess with it myself. Just looking for the simplest way to get him back up and running. Even if we can install customer recovery and a ROM. Thats fine too. Thanks in advance.

    • WugFresh says:

      You don’t need USB debug to unlock. Just get it into bootloader mode, and run the unlock script. There is a message where you can say your are manually starting in bootloader mode.

      Once unlocked, “flash stock + unroot” the latest android. You can relock afterwards if you like. Cheers.

      • David Dupre says:

        So he gets the to screen that says unlocking now. the screen goes back. the computer is waiting for it to reboot. but it never reboots. he has left it for almost an hour. still doesnt come back. Any ideas?

        • WugFresh says:

          Force reboot the device.. check to see if the little unlocked padlock icon exits, if it does, then its unlocked, and you are good to proceed. If not, force restart NRT if its hung – then try again with an alternate usb port and/or cable. Also try factory resetting again:

          You really need to get this thing unlocked, so try again if needed.

          • David Dupre says:

            We reboot manually. No unlock icon. When i try to unlock manually with fastboot oem unlock it fails with an unknown error. Tablet goes dark. Every single time. Im convinced its a hardware issue. Emmc chip i think. Idk. I appreciate the help but i dont think we are getting this unlocked.

          • WugFresh says:

            Sorry to say it, but based on your description I agree with your diagnosis. Definitely fits the criteria of a hardware issue. Hopefully you can get a replacement.

          • David Dupre says:

            Thanks man. He has had it for 2 years. I dont think there is a warranty anymore. Probably cant replace the chip im guessing. Thanks for all your help. And thanks for your amazing tool. Keep up the good work buddy.

  167. Arik says:

    Nexus 4
    Line 20805 (File “C:Program Files (x86)WugFresh DevelopmentNexusRootToolkit.exe”):

    Error: Variable used without being declared.

  168. giovanni says:

    1.9.1 dopo lo sblocco ed il root, non visualizza le cartelle, e di conseguenza non fa usare ne la fotocamera e non apre la galleria

  169. Pankaj says:

    Special thanks to you man, i just install Android L Dev Pre. in nexus 5. But i get some trouble while rooting…. pls looks for this

  170. Jim says:

    Have a nexus 7 that is stuck on 4.1.1. It fails to update. Will rooting help me with this?

  171. baba says:

    cant able to download it

  172. bhav says:

    hi i tried flash stock and unroot but it gave me an error something like failed to access null in the command prompt thing when it says waiting for phone to reboot. it tells me to do force flash so i do that and when that finishes my phone doesnt even reboot. it just stays on the bootloader screen. pleeaassee help

  173. baba says:

    always saying hashcheck mismatch

  174. bhav says:

    hi thanks for replying. i updated to 1.9.3 and now it says hashcheck mismatch.please tell me how to fix this im crying right now. i have the right device, build and im in softbrick mode. this is my only hope as by usb debugging is disabled. if this doesnt work, ill be dead. do you know any other softwares or programs that do the exact same thing without usb debugging? pleeaase help

  175. Try says:

    Why I get hashcheck mismatch for any update I try to do? I manually installed the v.1.9.3 cause with the former one the update didn’t work. Nothing change with the new version. Can you help me?

  176. Mak59 says:


    I’m trying to root my Galaxy Nexus. It seems that everything is successful prior to rooting — drivers, and unlock. When I hit the root button, it goes through the root process and once it’s complete I have SuperSU installed. When I click on SuperSu it can’t download the binaries. Root Check says that my device isn’t properly rooted. Any advice?

    Verizon Galaxy Nexus Android 4.2.2, build JDQ39

    I payed close attention to the prompt on the phone, when it was pushing. After prompting “downloading SuperSU” it says “Checking for MD5 file, then no MD5 file found, followed by “skipping check for MD5 file” — could this be why?

  177. bhav says:

    did that and still mismatch. is there a problem with this version because this started happening when i updated. please help. is there any other way of getting my phone out of bootloop? i cant enable usb debugging so i cant use adb. im a noob at this. please help. i beg you.

  178. Unfortunately, this can’t help me with my Nexus 9, bricked from Marshmallow. It just won’t unlock the device. Without unlocking, I can’t do anything.

  179. Dovid Shimon Baars says:

    how do i know if i have twrp on my nexus 6, i succesfuly rooted with nrt

  180. Rizwan Ayub says:

    I am using Nexus 7 2013 wifi and my android build number MRA58U and MRA58V still not showing in build list.Please update toolkit soon so I can root my N7.

  181. Ibrahim Ead says:

    I’m using nexus7 2013 Android 5.1.1 – Build: LMY48T and when I tried to root it, it stopped after showing teamwin recovery screen and don’t compleat and when I click on console icon I see some red messages like that:
    E : unable to mount /data/media/TWRP/.twrp when trying to read settings file

  182. passerby says:


    Why haven’t you added all the latest LMY48* builds?

    I want to keep using the 5.1.1 version, not the crappy 6.0.0 because the crappy 6.0.0 messes up the icons in older apps. And I want to be able to use those apps. Please keep adding all 5.1.1 builds as well.

    • Princess Kobe says:

      You can download those manually, and then point the installer to your download.

      • passerby says:

        Yes, you can, but if you have “Any build” then you have a lot of functionality disabled. I want to be able to backup and restore data etc. I want to be able to root and I don’t know, if it uses the most relevant binaries for rooting. And, of course I want to be able to backup and restore and it doesn’t allow it for “Any build”.

        • passerby says:

          That’s why I want to have all builds for Nexus 4 and 6, don’t care about 5. And also for Nexus 7 2013 Wi-Fi. I need all 5.1.1 builds for those 3 devices please. 🙂

          • MiniMe says:

            dont cry. nrt is great!

            use the latest listed build and do what ever you want. i just rooted my n5 on mra58n with the settings for mra58k

          • passerby says:

            Instead of giving orders on the internet, learn some English. And don’t reply to messages you don’t even understand… Notification icons in 6.0.0 are messed up. If you want to use an older app, that’s never going to be updated, you will see white squares and circles instead of its notification icons. So, I want to use 5.1.1, not 6.0.0, thank you.

          • MiniMe says:

            Instead of compaining on my english, use your brain for some reflection. I understood that you loathe Android m. It was just an example.

            If the new build isnt listed you can chose the latest listed of YOUR lmy48 !!! Its works well

          • passerby says:

            And you can choose version 4.4.4 It works well too… If we’re competing, who writes the most stupid comment here. LOL.

  183. HomeX says:

    Woohoo!!! v2.0.6!!! Thanks @WugFresh !

  184. Dalairen says:

    So after 2.0.6 my Nexus 10 LMY48T is still not on the list. =(

  185. boo says:

    Root kernel link broken for nexus 6p mda69d

  186. Jef says:

    Trying to flash 6.0 stock on my N5 that is currently running latest 5.1.1. Device is in fastboot mode and live log stops at ‘launching flashstock.bat’. Maybe something is wrong with the new bat file? Kudos to wugfresh to putting in all that effort btw!

  187. Max says:

    please, add MM custom rom for N4 in the build list. thanks

  188. Gregory says:

    My Nexus fastboot mode says “LOCK STATE – unlocked”, but when I run NRT I keep getting “Notice – Bootloader is Locked!” and no matter what I do – try unlocking it again, locking and unlocking again, etc. I can’t get past that notice. I have Nexus 7 2013 Edition Wi-Fi and trying to go from MRA58K to MRA58U.

  189. jacob oyola says:

    Trying to flash 6.0 stock on my N6 that is currently running latest 5.1.1. Device is in fastboot mode and live log stops at ‘launching flashstock.bat’. need help

  190. JohnN says:

    Unfortunately, 2.0.6 will not root my Nexus 6 running Android 6.0 (Build number MRA58N – Security patch level: November 1, 2015), unless I just plain don’t know how to do it.
    When I try, it “sift-bricks” my phone.
    Help, anyone?

    • Same thing happened to me. I guess it’s because this build hasn’t yet been added to NRT.

      I also got soft bricked so I did a Flash Stock + Unroot with the MRA58N image I got from Google and selected No Wipe Mode. I had some trouble with this so I had to try it a few times before it worked with NRT 2.0.5. I guess 2.0.6 is bugged?

  191. Masih says:

    Tried rooting with 2.0.6 earlier and face a problem from the get-go. In order for the kit to proceed with the root, it needed to download Dependencies but one of the links to the mda89d.img is broken, it couldn’t download that. Waiting anxiously on the update.

  192. VAVA Mk2 says:

    My Nexus 6P now no longer boots beyond the Google lgoo. FUCK!

    • VAVA Mk2 says:

      Oh God that was scary. I fixed it. Had to use adb to manually flash the bootloader, radio, recovery, boot, and system, but I got back to stock MDB08K on my 6P. Guys until WugFresh fixes bugs in this build of the NRT, I highly recommend using adb to manually flash/upgrade factory images as this has some bugs in it.

  193. Tyler Gaps says:

    Updated and tried to restore nexus 7 to stock but it does not work. It just hangs at the google logo. Luckily , I still had the 2.0.5 setup, deinstalled 2.0.6 and installed 2.0.5 and bam. Everything works fine now. Just that I have trouble downloading openrecovery twrp image as the link is broken.

    • Tyler Gaps says:

      Update : Unable to root nexus 7 grouper with 2.0.5. recoveryimage link broken. Tried 2.0.6 but unable to push root files.

    • VAVA Mk2 says:

      Same problem here…unfortunately 2.0.5 has no support for a Nexus 6P. UGGG I may have to go a day or so with my Nexus 5 until this gets fixed. My 6P is stuck with the Google logo and manually trying to flash factory images through adb is not working (says problem with sig on system file despite it coming straight from Google). Effing nightmare.

      • Tyler Gaps says:

        That’s a bummer , just hope that this gets sorted out soon. Can’t really do without root.
        The Nexus 5 is still great though, im still holding on to my bloated battery-burnt in-faulty home button Galaxy S2. Now that’s a real nightmare.

        • VAVA Mk2 says:

          See my post below. I fixed it and got back to MDB08K on my 6P without loosing data (can reroot easily), but until WugFresh does a bughunt on this and releases or 2.0.7 I recommend using adb to manually upgrade as the toolkit is borked at the moment.

  194. Nick says:

    Seems like 2.0.6 is having issues downloading the modified boot.img or it’s not seeing it when I try to ADB Pull a file.

  195. martin levy says:

    N7 2013 lte – is it possible to flash from kitkat (also was flashed via NRT, rooted) to lolipop or marshmallow and preserve all apps and configs ? I am too tired to install and config everething again from the sctratch … and Is any advantage N7 2013 LTE with lolipop or marshmallow against kitkat as I have now ? thank you for advice

  196. enke ledio says:


  197. tzermat says:

    Nexus 6 5.1.1 Fi specific builds – LVY48H missing from list, LVY48I cannot be rooted (boot loop)

  198. SimulatorOne says:

    If flashing stops when flashing MRA58R then run this procedure –

    1. Install the Nexus Root Tool Kit Version 2.0.5.
    2. The openrecovery-twrp- download status will be incomplete.
    3. The openrecovery-twrp- import will be incomplete.
    4. Manually download the openrecovery-twrp-
    5. Open the location where the nrt is installed.
    6. Paste the openrecovery-twrp- to Nexus Root ToolkitdataRecovery_CustomTWRP.
    7. Run the Nexus Root Tool Kit Version 2.0.5 -> Flash Stock + Unroot -> Recommended Settings.
    8. Import the factory image.
    9. Flash the factory image.
    10. To decrypt, go to http:// forum. xda-developers. com/nexus-6/development/mod-disable-force-encryption-rom-kernel-t3000788
    11. Download – NO_FORCE_ENCRYPT_shamu_v1. 0-signed. zip. Copy it to phone.

    12. Run the Nexus Root Tool Kit Version 2.0.5. Launch Advanced Utilities. Boot Custom Recovery. Install the NO_FORCE_ENCRYPT_shamu_v1. 0-signed. zip. Factory Data Reset the phone.

    You are welcome. 😀

    • Gregory says:

      Thanks for the tip about openrecovery file! I went back to 5.1.1 firmware until everything is fixed with Marshmallow. Some rooted apps don’t work like they should…

  199. Jon Peterson says:

    v2.0.6 keeps saying that the tablet bootloader is locked. the screen on the table says: “LOCK STATE – unlocked”. Where can I download v2.0.5? because I am stuck.

  200. minioninnc says:

    Can you now root N6 Moto without getting the corruption message and without having to do special things with 2.0.6?

  201. Christoph.G. says:

    It’s not running with Google Nexus 5 Build MRA58N. after root the device (Bootloop)

    factory image alone with Nexus Root Tool Kit Version 2.0.5 not with 2.0.6 🙁

  202. nilbud says:

    Thank fuck it’s busted the only other alternative was an embolism.

  203. Anonymous says:

    Nexus 5 Android 6.0.0 (MRA58N) not in list dude.

  204. Bassdj says:

    My 6P is now stuck on the google splashscreen. Can anyone help?

  205. Jeremy Jackson says:

    LMY48W isnt listed as a build, is it safe to load ?

  206. passerby says:

    I have a Nexus 7 2013 Wi-fi device, that has build LMY48M on it. When, I am trying to do ‘Flack Stock + Unroot’ to flash version LMY48T, it for some reason thinks that my bootloader it locked, although it’s unlocked and the device also says that on the screen that opens… Is this a bug in the NRT or something is messed up in my device? What’s the fix?

    • Ian Goodwin says:

      I have exactly same problem with exact same nexus model/android version. NRT detecting device (nexus 7 2013 wifi) bootloader as locked

      So hopefully it’s not our devices. Looking for solution now.

  207. passerby says:


    I have a Nexus 6 device, and I see that it’s not possible to flash versions LMY48T/W/X/Y. Is there a reason why? I want to be able to flash those and root, and backup, and restore, and many other things………

  208. paulo says:

    What with all the issues people are reporting with the new 2.0.6….it seemed like a good time to spread a little love and make a quick donation to wugfresh, to support all the effort. I recommend others do too.

  209. paulo says:

    And I’m happy to report that I just used 2.0.6 to (re) root my nexus 6, which would not root under 2.0.5, and mra58k. Smooth as silk. thanks, wugfresh!

  210. Ian Goodwin says:

    Having problem where bootloader is being detected by NRT as locked even though it’s unlocked (also reported by other users). Could anyone help direct me to older versions of NRT? All i can find appears to be malware when searching google.

    Nexus 7 (2013 wifi)
    Android 5.1.1 LMY48T

  211. Lucky says:

    2.0.6 does not work with my Nexus 6P Huawei MDA89D. Bootloader unlock does not work:

    >Connectivity Status: ADB Device Connected
    >Rebooting your device into bootloader mode…
    >adb reboot bootloader
    >Checking Fastboot Connectivity
    >fastboot devices
    >CVH7N15A17001856 fastboot
    >Connectivity Status: Fastboot Device Connected
    > + Bootloader Status: Locked.
    >fastboot flashing unlock
    >Rebooting your device…

    But after that it is still locked. More to the point, I am unable to download root kernel for this phone.

  212. Where can I download the downgrade to v. 2.0.5? Upgraded to the latest version and there are some problems.

  213. Felipe Fuentealba says:

    used the nrt 2.0.6 to update firmware, fails, I have manually unlocked the bootloader on day one when I got phone (6P) to prevent my data deleted in the future after unlock. Early today tried to update firmware using toolkit, as I see in google websites has up to MDB..M, NRT only shows me can update to MDB…K, comming from MDB…D, it started the batch flashing something and then stopped, to my luck phone still boots, Am I going to have trouble now WugFresh when you fix the toolkit and I try to update again since your script looks like partially flashed something already??

  214. Felipe Fuentealba says:

    used the nrt 2.0.6 to update firmware, fails, I have manually unlocked the bootloader on day one when I got phone (6P) to prevent my data deleted in the future after unlock. Early today tried to update firmware using toolkit, as I see in google websites has up to MDB..M, NRT only shows me can update to MDB…K, comming from MDB…D, it started the batch flashing something and then stopped, to my luck phone still boots, Am I going to have trouble now WugFresh when you fix the toolkit and I try to update again since your script looks like partially flashed something already??

  215. samuel Joshi says:

    NRT 2.0.6 for NExus 7 2013 wifi version
    the unroot+Stock command keeps(again n again) on unlocking my bootloader .

  216. NORSE says:

    I have Nexus 5,i unlocked it using nrt 2.0.6 and tried downgrading to kitkat but it doesn’t does the job.
    It stops on ‘running flash.bat’.
    Any help is appreciated.

  217. Brian M says:

    Same here for a Nexus 10 latest 5.1.1 update. Stops and “launching flashstock.bat”…

  218. Rémi Platini says:

    Tried to unroot my Nexus 5 to get an OTA but it’s not working.
    It stops at “launching flashstock.bat”…

  219. Fredrol says:

    I also have some issues with the latest NRT verson..
    Was going to flash the latest factory image on my Nexus 5, but as many others im stuckc at “starting flashstock.bat”.

    Tried to download the previous version of NRT; and had to download a new file, but when following the link i get a 404 not found..

    Someone has a working link to get the previous version of NRT to work?


  220. Alex France says:

    Rooted my nexus 5 again using 2.0.6 all went buttery smooth. Thanks WugFresh. How do i now apply the recent november security patch that was just released?

  221. art says:

    anybody have tried these on their N5 using the NRT 2.0.6?

    1. “Flast+Unroot” without wipe
    2. then do an OTA of Android Marshmallow 6.0.0 (MRA58N)

    any issues?

  222. Dave says:

    I had to download the November update manually, then I had to go back to NRT 2.0.5 to flash the November update with flash stock and unroot, then I had to download and update the masterlist to the latest version to get TWRP. Then I re-rooted using advanced settings with super user beta. This works until the bugs are fixed in NRT 2.0.6. Thanks WugFresh.

  223. Stefan Weißhampel says:

    Hi WugFresh
    the noforce-encryption-shamu-kernel cannot be found atm. If I follow the link to load it manually, I get a 404. I also had a look for it n other places, to no avail. Is there a chance that it will be back soon?

  224. Ryan says:

    Hey Wug, the link to the Nexus 6P Huawei MDA89D build’s root kernel is either broken or being used as a placeholder. Any idea whne this will be fixed/available? Thanks for this awesome tool btw!

  225. Tim Nixon says:

    Good to hear that I’m not the only one having issues (nexus 2013 wi-fi) with unlocking the boot-loader. Will try suggestions and await an update to the software. Great job wugfresh!! Great tool and keep up the good work..

    The Nov update fixes the stuttering issue with video on netflix and other video playback issues

  226. Byron says:

    Good morning WugFresh. Thank you for the NRT. But, I have some concerns with the latest update. I am constantly getting a “ADB connection error messages” I took four attempts to root my phone (Nexus 6 Lollipop) due to these constant errors messages. I did not have this problem with the previous version. Once the phone was finally rooted, the errors return while trying to install Viper4android. Your feedback was be greatly appreciated. Peace.

  227. alexus says:

    Is there any plans of adding Linux and/or Mac to NRT?

  228. Victor Siefen says:

    Got no connection with Nexus 5x – tried different usb ports and usb-debugging is turned on. Doesn’t auto-detect model and build either. Maybe it’s because i’ve got the german version?

  229. Daniel Tobon says:

    Hello Guys, I have the same problem with flashing stock and unroot… I have a Nexus5, with marshmallow, then I received the last security update and I read some post about the new superSU, I was trying to get a clean rom, them root, them the new superSU and finally lock the OEM to receive the OTA but the NRT 2.0.6 closed the CMD window runingt the “Launching flashstock.bat”. Any idea what is going on?

  230. Mark Goertzen says:

    I have Nexus 5, currently kitkat rooted & unlocked. NRT keeps failing to perform Flash Stock + Unroot. Tried Android 6 and 4.4.4 KTU84P which is what is currently installed. It runs the flashstock.bat – cmd prompt displays success for copying over the files (which it does INSTANTLY (far too fast considering the size) then closes cmd prompt. I have tons of free space on the phone. I don’t know what the issue is.

  231. Daniel Tobon says:

    At this point I already installed the MRA58N manually…. with ADB and Flash-all command… the device is unlocked, I will try to root it and later lock it…

  232. Joseph Wellman says:

    my nexus 7 has the bootloader unlocked and 2.0.6 keeps telling me to unlock the bootloader …. were can I find a NRT 2.0.5

    • David Miller says:

      I ran into the same problem. There appears to be some problems with the Nexus 7 rooting after Marshmellow. I found a d/l for NRT 2.0.5, but then I couldn’t update the recovery flash tool. I’m just going to wait for the NRT 2.0.7 that should probably fix this issue.

      • Kennon Wong Chun Cheung says:

        I have this issue +1. My Nexus 7-2013 (razor, Flo WIFI) have unlocked bootloader, but the tool is asking me UNLOCK bootloader and told me will wipe my device, I stopped flashing the new image. I just wish to update my system image.

  233. Eric Hawkins says:

    Nexus 6P boot loops, and refuses to go past launching flashstock.bat. Up a creek, trying to remain calm.

  234. Chandri MacLeod says:

    Does this update fix the root failure after update that the Nexus 5 encountered after MRA58K? That update required a TWRP workaround using a custom kernel… will we need to do that again if updating to the latest build?

  235. Chandri MacLeod says:

    Has there been a fix for root failure after update that the Nexus 5 encountered after MRA58K? That update required a TWRP workaround using a custom kernel… will we need to do that again if updating to MRA58N?

  236. WugFresh says:

    For those who experienced bugs in 2.0.6 – I will fix in v.2.0.7

  237. daps says:

    thanks WugFresh, we will always love you, anyway !

  238. Leo Kwok says:

    Bugs in 2.0.6. Fail on Nexus 7 2013 rom MRA58V, cannot root.

  239. WARMgiannes says:

    Hi, i am stuck in loading screen after rooting my phone. Can help please?

  240. Kennon Wong Chun Cheung says:

    One more issue, the flash stock +Unroot mode issue:
    Inside have the option of no wipe mode and “force flash mode”

    the “force flash mode” is grey out. cannot tick. please fix

    • WugFresh says:

      Force flash is permanently enabled and checked. I decided not to remove it all together because then people would see old posts which said to enable it and wonder where the option went. With this new version, the flash stock is revised to always function in this more reliable mode.

  241. Jack Miehoff says:

    Is there some way to get 2.0.5 so I can fix my Nexus 10 until you get 2.0.7 out? Right now, I can’t escape the bootloader screen.

  242. nvog says:

    Impossible to ” flash stock +Unroot” !!!!

    The kit keeps saying to unlock my bootloader, even if IT’S ALREADY UNLOCKED !!!!!

    Please, fix this.

  243. MC HD says:

    Impossible to “flash stock + unroot” my Nexus 5 with NRT 2.0.6!!!! Is there any possibility to go back to NRT2.0.5?

    • WugFresh says:

      Can you explain what happens. I don’t have this issue on my Nexus 5.

      • arc S says:

        please fix the problem with the N5!

      • SKerr says:

        Hello WugFresh, I experienced this problem a few days ago as well. If i remember correctly, the .bat file would just stop executing after flashing the radios and the CMD window just closes. I didn’t see any errors listed right before it closed, but since it is so fast I’m not totally certain there weren’t any. To get around the issue, I just copied all of the ADB and FASTBOOD executables and DLLs to the folder where NRT saved the image file and ran the flash-all.bat script manually. Thanks for all your hard work on this tool, and let me know if I can do anything to help provide you any more info on this issue.

      • SKerr says:

        I think I see what might be the issue when flashing mra58k to the N5. When the WhatToFlash.bat was created, it’s not setting all of the path parameters used in flashstock.bat. It only sets:

        But the Flash_image_zip flag is never referenced in the flashstock.bat, and the image_zip parameter is not used.

        Hopefully this helps and thanks again!

      • daps says:

        same problem on my N5: process stops abruptuly after running flashstock.bat (Thanks forever WugFresh )

      • VAVA Mk2 says:

        Can we expect 2.0.7 anytime soon? 2.0.6 has a LOT of bugs. I guess they changed a lot in 6.0…

      • MC HD says:

        I have a Nexus 5 Build Number LMY48I and before updating to to Marchmallow I wanted to do the next step update to LMY48M. But after running flahstock.bat the process stops and the device remains in bootloader modus.

        Following logfile was created:

        Nexus Root Toolkit v2.0.6


        – LatestToolkitFiles.ini 3085

        – AndroidDeviceListFull.ini 3085

        – AndroidDeviceListFlash.ini 3085

        HAMMERHEAD-HAMMERHEAD: Android 5.1.1 – Build: LMY48I

        Live log initiated [2015-11-15]:

        Information: Getting Device Properties…

        Nexus Root Toolkit v2.0.6


        – LatestToolkitFiles.ini 3085

        – AndroidDeviceListFull.ini 3085

        – AndroidDeviceListFlash.ini 3085

        HAMMERHEAD-HAMMERHEAD: Android 5.1.1 – Build: LMY48I

        Live log initiated [2015-11-15]:

        Checking ADB/FASTBOOT Connectivity

        adb devices

        0342aed0251dcf82 device

        fastboot devices

        Connectivity Status: ADB Device Connected

        Rebooting your device into bootloader mode…

        adb reboot bootloader

        Checking Fastboot Connectivity

        fastboot devices

        0342aed0251dcf82 fastboot

        Connectivity Status: Fastboot Device Connected

        + Confirmed: Bootloader Unlocked.

        fastboot getvar product

        product: hammerhead

        finished. total time: 0.001s

        Launching flashstock.bat

  244. Twml says:

    Please include the new google security patch updates for the Nexus 6P in V2.0.7
    Cant update OTA with rooted /system

  245. Hamza Sbai says:

    Hi, tried to root my nexus 5 build MRA58N using NRT 2.0.6, now it’s in bootloop. Tried to flash stock/unroot using softbricked-bootloop mode (no wipe) using build MRA58N again but it doesn’t work.
    What is wrong ??

  246. Piter says:

    My nexus 7 is soft bricked/ can only access fastboot, when I use “flash stock + unroot” the cmd window crash suddenly after writing radio. How can I do? thx

  247. Wolfgang says:

    I had no problem to update my Nexus 5 from MRA58K to MRA58N using the NRT 2.0.6.
    Only after rooting I got stuck in a bootloop. So I flashed MRA58N again and now I wait for the NRT 2.0.7 before I root again.

  248. Joseph Wellman says:

    since i was having problems in 2.0.6 I went back to 2.0.5 but now I cant download the file openrecovery-twrp- the location shows 404 error when I check the site.

  249. Nelson Robles says:

    2.0.6 can`t download the file openrecovery-twrp- fix please error 404

  250. 123XYZ says:

    I can’t flash stock my Nexus 5! All time exit “flashstock.bat” after writing ‘radio’!

  251. Matt says:

    I have a Nexus 5x, Build: MDB08L. When I attempt to Unlock Bootloader, there is no error but it doesn’t work. NRT boots my phone into bootloader (works), checks Fastboot Connectivity (works), then a box from NRT flashes on my computer screen for only a brief second, my phone reboots, and nothing has changed. My phone was not wiped or unlocked.
    Checking Fastboot Connectivity
    fastboot devices
    00c96daa83e23bcc fastboot
    Connectivity Status: Fastboot Device Connected
    + Bootloader Status: Locked.
    fastboot oem unlock
    Rebooting your device…

    Is anyone else experiencing this problem? Does anyone know a quick fix for it?

  252. Nik says:

    Also having the flashstock.bat issue.. I am stuck in a bootloop and it is closing and cancelling the operation. Really need my phone.

  253. Matt Kelly says:

    Not sure if the issue I’m having is with my device, or with 2.0.6.

    Nexus 6, MRA58K, unlocked, twrp, rooted. – Achieved all of this with NRT last month. Zero issues.

    The latest nexus 6 ota is available as MRA58R, so naturally I’d like to update.

    This is what I did:

    -Flash stock + unroot (device is normal)

    -MRA58R is selected to download

    -Force flash is greyed out, but the box is checked.
    -No wipe mode is checked
    -No force encrypt is NOT checked as I never removed the encryption from my device when I originally unlocked the bootloader.
    -clicked Ok

    NRT downloaded the latest Image, installed it. No issues. Got back into OS, a few settings had changed (dpi, kernel settings, etc) because I was no longer rooted.

    No problem, back to NRT, click “Root”, phone does it’s thing…finally get to the pop up that tells me what files to flash in TWRP, in the !readytoflash folder. I picked all three files (including SU 2.52 beta..), swiped to confirm, they install.
    Reboot system.

    Here’s the problem, the phone boots up, then gets and error saying that my device is corrupt, then shuts off.
    I googled it, and people have had success with flashing a different kernel, so I tried flashing Hells Core. It gets me past the corrupt warning, but then bootloops (waited 20 mins).

    I got back into recovery, flashed my nandroid, and I’m back to where I was an hour ago. No real big deal.

    So. Any ideas? I feel like I did something wrong.

    Sorry for Wall of text.


    • Daniel Cardozo says:

      I had the exact same problem than you had.
      Same Nexus 6, same rooted MRA58K to startup, all the same process, got the same result.
      So, it’s not your device, it’s something between Nexus 6 and NRT 2.0.6

      • Matt Kelly says:

        Ya. I think it might have something to do with not doing a complete wipe when we update to “R”. I didn’t select full wipe, thinking I could just flash the latest image, then re-root. But we might need to do a complete wipe first.

  254. .. says:

    Can you add Custom ROM – M (Marshmallow) for Nexus 4 and 5, Galaxy Nexus, Nexus S option for selection of android build?

  255. Dharam Intwala says:

    We love you WugFresh hope you release a better version of this toolkit supporting the nexus 6P

  256. Jon Bradley says:

    2.0.6 Issue. – As other are finding the latest release is failing to complete a flash and unroot routine. The script bombs with a remote table update fail error.

  257. James Ulrich says:

    Root/TWRP install on Nexus 6 with MRA58R results in “Your device is corrupt.”… and cannot be trusted, then device powers off.

  258. JM says:

    openrecovery-twrp- not found with link. Anyone else having this problem?

  259. Captain says:

    I tried to root my Nexus 7 2012 yesterday. It failed while trying to push files with adb :
    I had a ADB operation timed out error.

  260. Joseph Wellman says:

    WugFresh knows all the problems we just need to wait till he has time to release his 2.0.7 update. witch he already said he was testing it. I cant wait so I can finally root my Nexus 6P

  261. Tung Quang Mai says:

    I’ve Nexus 7 flo, tried to unroot+flashstock and same process as everyone else.

    NRT shows my device is locked, then it hangs on bootloader screen, cannot do anything, press power + volume no use.
    Then window informed my device is corrupted, cant be recognized.
    I’ll wait for it to run out of juice and try again.
    Please find the bug soon and realise 2.0.7.


  262. leontrg says:

    I rooted my nexus 7 2013 and tried to install the update and now it says “no command” on startup screen WHAT CAN I DO TO BYPASS THIS?

  263. Sam Samy says:

    I thought wugfresh said he was about to release 2.0.7 like 2 days ago?

    • Joseph Wellman says:

      he did says he was working on it 2 days ago. but with the issues 2.0.6 had I think a few days of testing is ok. he will have it out when he thinks its passed the testing. so I say soonish

  264. Kleinhirn says:

    Hi, I want to update my rooted Nexus 4. But on update with “no wipe” it switch into fastboot wrote “Radio” and exit. The NRT shows no message and my Nexus 4 is in Fastboot mode. I can easyly start it, but the update did not work.
    Is there a bug?
    Here is my protokoll:

    Flash Stock + Unroot [WugFresh Development]

    sending ‘bootloader’ (2264 KB)…
    OKAY [ 0.086s]
    writing ‘bootloader’…
    OKAY [ 0.492s]
    finished. total time: 0.580s

    sending ‘radio’ (45537 KB)…
    OKAY [ 1.689s]
    writing ‘radio’…
    OKAY [ 2.999s]
    finished. total time: 4.690s
    “(” kann syntaktisch an dieser Stelle nicht verarbeitet werden.

  265. Nigel Almada says:

    can’t someone post the NRT 2.0.5 ? I need it ASAP . 2.0.6 do not works well

  266. Nigel Almada says:

    i can’t root my nexus 6 in 6.0
    the phone say that it’s corrupted
    i know that i need to flask a custom kernel before rooting but there is nothing to do it in the toolkit nor any warning before rooting !!!

    • Joseph Wellman says:

      just wait for 2.0.7 to come out. WugFresh is testing it currently and should be out soonish. that’s what I am doing as well

    • Diego Stilman says:

      There is a way to recover the phone with all your data, download the EX kernel and flash it. Problem solved.

      • Marc Perrusquia says:

        My 6p appears to be in a bootloop.

        • Diego Stilman says:

          Yes becouse incompatibilities between the new kernel and supersu. You have to turn it off and press all the buttons at the same time until the phone enter to recovery mode. The you can flash it.

          • Marc Perrusquia says:

            Can you give me a more detailed explanation? I’ve already unlocked the bootloader and flashed a custom recovery, and when I try to flash back to stock fastboot stops working. Thanks for the response.

          • Diego Stilman says:

            try to enter to bootloader mode and flash pressing all buttons at the same time, when you are ther you can wach a little robot, plug in the usb cable. Download external x kernel and copy to the folder where the fastboot program is. Enter to cmd and go to the folder, write fastboot flash boot (and the name of the external x file) and afer flashing restart the phone. Hope you can solve the problem.

          • Marc Perrusquia says:

            It fails and tells me the remote image is not a boot image. Do you have any more suggestions? Thank you for your help.

          • Diego Stilman says:

            Have you tried to use the new version of the root toolkit?, reflash your current version without erasing data. You can do that if you are in bootloader mode.

          • Marc Perrusquia says:

            Yes I actually got the update after the failed root. How would I reflash? Sorry for the noobish questions, normally rooting is a 10 minute process for me. I am in bootloader mode.

          • Diego Stilman says:

            No problem!, you have to select your android version first, do it manually. Then, press flash stok+unroot. And then select the bootloop mode. Afert that choose to download the firmware, no wipe mode, and force flash. Take into account that the software is going to download the firmware first and then flash it. Make shure that you have enough battery, if not shutdown the phone from bootloader option and charge it first.

          • Marc Perrusquia says:

            Thanks for all your help man. I’ve tried flashing to stock this way multiple times now and I keep getting the message Error:Array Variable has incorrect number of subscripts or subscript dimension range exceeded. Really sorry for all the questions man. I’ll also try and look around XDA, thank you for all the responses you’ve given me.

  267. Joseph Harding says:

    Nexus 7 2013 wifi tablet running android 6.0, MRA58V. Using NRT 2.0.7, still cannot root, after initiating TWRP to flash the 3 files and rebooting system. The tablet bootloops. Any suggestions?

  268. Kennon Wong Chun Cheung says:

    Thanks new version. Root work for latest build for nexus 7 2013 WiFi?

  269. Scotty York says:

    I’d tried, a few days ago, using NRT 2.0.6 to upgrade my Nexus 6 from 5.1.1 to 6.0 (R). I did a full wipe of the phone. In common with others, I couldn’t get root – and before I even tried to root, the (so-called stock) upgrade gave me the infamous “your device is corrupt” message when I rebooted the phone. After displaying that message, the phone booted, and ran, fine. All the apps re-installed. But I couldn’t get root. After I flashed the 3 files under TWRP, I saw the corrupt message but this time the phone would NOT boot – it just powered off. Long hold of the power button just repeated that cycle of “corrupt – power off”. I tried to reflash the stock using the “softbrick” setting but NRT couldn’t see the phone (no surprise – it kept powering off). So I had to (i) enter bootloader mode by power+volup+voldown; then (ii) use NRT to reflash the softbricked phone. Now it ran OK.

    So as soon as I saw 2.0.7 on here, I installed it, and repeated the process. Selected “flash & unroot”, and re-applied the R release, this time choosing no wipe (because I didn’t want to wait for them all to re-download, then set them up, etc.). Seemed to go OK BUT, when phone booted, it still showed the corrupt warning. This surprised me because I thought that a true stock install would avoid that message. Anyway, I pressed ahead & tried to root. Same as with 2.0.6. So once again I had to (i) enter bootloader mode by power+volup+voldown; then (ii) use NRT to reflash the softbricked phone. Again I chose no wipe. Went OK. So right now, my phone is running 6(R), and seems fine EXCEPT (i) if I have to reboot, I’m told it’s corrupted and (ii) I still don’t have root.

    Should I redo the stock flash using 2.0.7, this time using “wipe mode”? Would that get rid of the corrupt message (at least until I successfully rooted)?

    • todini says:

      Same here. Nexus 6. Black screen-soft brick when I tried to root on MRA58R. I used NRT to revert to 5.1.1; locked the BL, then let it OTA to 6.0. After that I unlocked and did not have the “Corrupt” warning, until I tried to root again.

    • Daniel Cardozo says:

      Exactly the same for me.
      I did the whole process 3 times, just in case, so it’s reproducible.
      Nexus 6 (R)
      I can flash stock+unroot, it works (but I do get the ‘corrupt’ message at startup.
      If I root, after the ‘corrupt’ message, the screen goes blank and nothing else happens.

  270. roydukkey says:

    Humm… I’m still getting stuck at android spinning logo boot screen after TWRP reboot.

  271. P.L. says:

    I unlocked my 5x with no issue. When I go to root and flash custom recovery, I end up with the android with red exclamation mark (no recovery) but still able to boot up normally. Only way I can flash recovery by the advanced utilities. After I get the latest TWRP flashed, I go root with custom recovery unchecked, flash beta SU and busybox, then get stuck at the boot logo. Only way to fix it is to flash stock. Using NRT 2.0.7 stock android 6.0 MDB08L.

    • Jay Zimmer says:

      I’m in the same boat. It will boot TWRP temporarily fine and flash all the the files but after that it goes and flashes the stock recovery through fastboot and if i try to boot to recovery I get mr. android on his back with !. Once I restart root works but busybox will not install.

      • P.L. says:

        Only way I could get BusyBox to install was to flash it manually.
        1)Install BusyBox app from the playstore but don’t install from the app. 2)Found a flashable zip for a October version of Stericon and flashed it in TWRP and reboot.
        3)Checked it installed properly and then you can update to latest version in the BusyBox app.

  272. James says:

    Nexus 6 patch 5.1.1
    I don’t see: LYZ28N

  273. Marcin Obała says:

    NRT 2.0.7. Trying to flash MRA58N. Only bootloader sending and writing OK. All other Sending OK, writing failed. Probably bootloop.

  274. Marcin Obała says:

    After changing usb cable, no errors, everything works like a charm. Don’t buy usb cables on aliexpress…

  275. Marius Merchiers says:

    I tried the no wipe method to flash MRA85N to my nexus 5. All went good till it wanted to flash system. There was an error and now my nexus 5 can only boot the bootloader. Now what? I made a nandroid backup but I don’t have twrp anymore!!

  276. Артур Валеев says:

    Nexus 7 bootloop after rooting. (2.0.7)
    did it like 100 times before, never had any problem..
    is it just me or i should wait for fix ?

  277. Thomas Au says:

    Just use 2.07 to flash my nexus 5 to v6(58n), it seems ok for the stock rom. However, it become boot loop after use 2.07 to root it. Pls help to fix it

  278. Mish says:

    Bootloop after rooting my Nexus 5 (hammerhead) MRA58N. What the fudge is with this system?! Maybe it’s the Superuser that doesn’t work with the latest stock?!

  279. LeNon says:

    boot loop after trying to root NEXUS5 MRA58N with v.2.0.7

  280. Marius Merchiers says:

    I was stuck in bootloop when trying to root Nexus 5 with MRA58N android 6.0.
    I reinstalled MRA58N with nrt 2.05 but it failed to send system. I tried the MRA58K and this sends and writes the system ok.

    Now How do I root!!!!??? And install twrp???

  281. Harald says:

    with nrt v2.0.7 i am able to flash stock rom.
    If i flash stock rom MRA58V it works fine.
    But if if try coustom recovery (TWRP) and root the nexus 7 2013 LTE hangs in bootloop after flashing.
    Is there also a bug in nrt v2.0.7?
    Please Help!

  282. F4LL0U7 says:

    Is there any way to root an encrypted device without having to wipe it first to remove the encryption? TWRP can never take the password I enter when trying to root. I’m using a Nexus 5X and Nexus 9. These monthly Android security updates are a pain. I don’t have time to wipe my devices every month in order to install them.

  283. Joseph Harding says:

    Nexus 7 2013 running MRA58V can now be rooted using NRT 2.0.7. Just update the masterlist and all is well.
    Thanks Wug, you are magic.

  284. P.L. says:

    I cant get Busybox to install to either xbin or bin.

  285. Scotty York says:

    I posted a couple of hours ago (below) about problems using 2.0.7. I was trying to flash MRA58R – worked OK, in so far as the phone ran fine, but (i) every reboot, I got a “corrupt” warning (but the boot completed OK) and (ii) I couldn’t get root (after trying, it bootlooped). Long story short, I just tried using 2.0.7 to downgrade to MRA58K (using no wipe). Worked perfectly. No “corrupt” warning. Then rooted – again, perfect. So right now my phone is rooted & running nicely on K; and I’m not sure that I really need the N or R release. Thanks for the tool, Wug!

    • Scotty York says:

      Replying to myself. After the above, I saw Wug’s post that he had re-uploaded some of the NRT files. He did this AFTER I failed with R, but BEFORE my success with K (above). So, I thought I’d try again with R, this time using the “correct” files from Wug. Worked perfectly. I now have a rooted Nexus 6 running R.

  286. Rudolph says:

    I’m gonna update my nexus 7 2013 from 5.0.2 to 6.0 , I hope this works, last time I updated was 1 year ago…

  287. Antonio says:

    are the bugs fixed now? I’m still waiting to root an unlocked Nexus 5 and a locked Nexus 6

    BTW, MRA58N is missing in Nexus 6 list

  288. Rutjan says:

    I went through the flash stock with no wipe MRA58N version, went smoothly, with NRT 2.0.7 masterlists 3090.

    Rooting process appears to achieve, but when I lauch BusyBox (which I had to install via PlayStore as it didn’t get flashed by TWRP), there is no root access prompt…

  289. James Robinson says:

    Rooted my Nexus 5 with no issues. Thanks WugFresh!

  290. noelito says:

    i have a nexus 6 that i want marshmallow on. i did the flash stock + unroot and i’m stuck on bootloop. what gives?!

  291. Chuck T says:

    Please update to the latest Masterlists (3090)? Mine is showing I have 3092. are we missing things in 3090/91?

  292. HarryM says:

    I’m now running CM 12.1 because it’s impossible to flash any factory image at this moment without getting errors while flashing system.img — manual as well as with NRT 2.0.5. and 2.0.6. Hoped 2.0.7. would resolve this.

    But: the script Flash stock + unroot in NexusRootToolkit.exe (on Windows 10) produces the next error:
    AutoIt error Line 27232 of : “Array variable has incorrect number of subscripts or subscript dimension range has exceeded”

    What options do I have?

  293. vicks says:

    The screen freezes at “Unlock Bootloader” when I try to select Yes via the power button.

  294. Josh Billingsley says:

    I was on 6.0 and tried to go backwards and it didn’t go well. Ive restored stock, but now I’m getting no sdcard location. It pushes recovery fine, but gets hung up on pushing the root. An ideas? Ive reverted to 3 builds including 5.0 to try to get it to root. Connection is fine, chord is stock, and usb debugging is set and checked and unchecked mtp. Ive done all I know to do

  295. Bar T says:

    Wanted to downgrade my Nexus 7 2012 Wifi (nakasi/grouper) to 4.4.4. Now stuck at the google logo. And yes, I’ve waited… For about 40 minutes. Has anybody got an idea?

  296. daps says:

    A rooted Marshmallow has landed on my Nexus 5 and it was smooth as the sea of tranquility is ! And Wugfresh is the number one ! Thank you so much !

  297. Marco De Rosa says:

    After a series of failures with previous NRT and masterlists version (I had to reset and reflash my Nexus 6 a couple of times), finally I have been able to root my nexus 6 MRA58R.
    Nexus 6, MRA58R, NRT 2.0.7, Masterlist 3092. Rooted and installed Custom recovery. Works like a charm!

  298. Cobra_dk says:

    Just upgraded my Nexus 5 from MRA58K to MRA58N (nowipe), then rooted.
    No issues. Smoooooth as a baby.
    WugFresh, you did it again! 🙂

  299. rushter says:

    So is 2.07 now using the Stock Kernel instead of having to interrupt NRT and installing the Franco kernel to work? I want to get back to completely stock and rooted if possible.
    I am on
    3.10.40-franco Kernel
    Just want to get back to stock and rooted. Without wiping everything again, if possible.
    Thanks Wug

    • Scotty York says:

      Should work fine. Yesterday, I installed K, then rooted. Then installed R (which meant fully-stock & unrooted) using no wipe mode. Again, it worked fine. After doing this, I chose to re-root (which you don’t want to do). But bottom line is, I think you’re good to go, just installing stock R & unrooting using no wipe mode.

      • rushter says:

        I want to keep root. Just wanted to know if the stock kernel is working now as it wasn’t before.
        I have a few odd things happening that make me wonder if they are kernel related.

  300. Marius Merchiers says:

    Ok I want to try again to update my nexus5 android 5.11 to 6.0 and root it and install twrp. I will try with the latest masterlist.
    But first, what is a masterlist actually? And how do I check if i have the latest? I know how to update but where can I check if I have in fact the latest?

  301. P.L. says:

    So I’ve managed to get everything done on my 5x (root/twrp/busybox) after a bit of fiddling and help from nrt.
    But when I use root and flash custom recovery in nrt it goes through every thing but near the end it does a final reboot and flashes stock recovery leaving me with the no recovery “dead” Android screen. This leaves me to have to flash twrp manually to get it back. Is this supposed to happen?

  302. Mark Goertzen says:

    I just tried to Root + Custom recovery on Nexus 5 with Android 6 MRA58N – FAILED. NRT seemed to flash TWRP but when I tried to get into Recovery Mode to continue the root install, it simply booted me into full Android. I guess TWRP didn’t get installed! Now I don’t even have any recovery! I used NRT 2.0.7 for this.

  303. Brian M says:

    Worked like a charm on my Nexus 5 (MRA58N) and my Nexus 10 (LMY48X)… Updated and rooted both with no problems.

  304. Tony Montana says:

    Nexus 5 flawless install + root. Thanks again for all the work.

  305. Marius Merchiers says:

    @Wugfresh. Now it worked for me. I removed 7zip programm from my computer (when I choose my own nexus5 image it gave errors with nrt) and now nrt works. What I noticed when it was flashing bootloader, recovery, and such my nexus 5 didn’t reboot everytime! And when it comes to flashing “system” it was a failure, I think this is because my phone didn’t reboot between the flashes.
    It’s weird but when I removed 7zip, my phone rebooted between flashes…

    Another remark, when flashing system of MRA58N was done my phone just stayed in bootloader. Is this normal? I rebooted the phone manually and then it was preparing the apps for android 6.0.

  306. goutham kumar says:

    Hi! I have a nexus 5 running Android 5.1.1 on blu spark kernel and xposed framework installed .obviously, the bootloader is unlocked.
    I plan to install Marshmallow on my device. What is the procedure I must be following to install Android 6.0 using this toolkit . I have been waiting for xposed for marshmallow and since it is created and running fine for marshmallow I plan to upgrade my device .Please guide me with the steps I need to follow Android 6.0 using Wugs nexus root toolkit. I also wish to root the nexus 5 after installing marshmallow .So lease tell me how to do that also .
    Do I have to follow any special procedure as I have xposed framework installed ?

  307. Murmand says:

    Thank you! Nexus 5 with build MRA58N and everything works like a charm! Thankou you WugFresh for all your great work. I just had to pass the “Full Driver Installation Guide” because otherwise “Fastboot Connectivity” didn’t work, but now I have rooted device again!

  308. 叶希杰 says:

    hi, i have a nexus 6p and i have used NRT v2.0.7 to flash angler-mdb08m-factory-dbc17940.tgz. however it stunk at the google logo and cant get into the system.please check the tools and solve the problem, thanks alot!

  309. Neal Palmer says:

    Awesome! Took about 1 hour total to get through rooting my Nexus 6P! Thankyou.

  310. Andy says:

    Why I can not install BusyBox? No matter what path I choose “/system/xbin” or “/system/bin” I always have an error (installation was not successful)
    Nexus 5X with Marshmallow is unlocked and rooted.
    Can I ask you guys for help?

  311. Jmylk says:

    line 27232 problem? Anything I’m doing wrong?

  312. Kvin says:

    While trying to unlock the bootloader, I received the error:

    “Line 27242 (File “C:Program Files(x86)WugFresh DevelopmentNexus Root ToolkitNexusRootToolkit.exe”);
    Error array variable has incorrect number of subscripts or subscript dimension range exceeded.”

    Please help

  313. Jay Zimmer says:

    Nexus 5x (MDB08L) unable to install busybox using NRT 2.1.0. Unable to flash TWRP as part of root & flash custom recovery. Was able to flash TWRP separately in advanced utilities. Current have root but not fully functional without busybox.

  314. .. says:

    Can you add Custom ROM – M (Marshmallow) for Nexus 4 and 5, Galaxy Nexus, Nexus S option for the Selection of Android Build? New ROMs supporting those devices is on XDA

  315. Brian M says:

    If I wanted to enable full disk encryption on my Nexus 5 would I run into any problems updating and re-rooting?

  316. bentc says:

    Upgraded Nexus 5 from mra58k to n. And rooted the phone. No problems. Unlocked and rooted my brandnew Nexus 6p. No problems. Thank you Wug!

  317. Mizraim Carrasco says:

    busybox won’t install

  318. Victor Qu says:

    Why are there still no support for all of the Lollipop builds (LMY48X, LMY48Y, LMY48W) for the nexus 6?

  319. busybox won’t install on Nexus 7 2013 WiFi, Build MRA58V

  320. Chris says:

    The Google page hasn’t updated yet, but there is a new Nexus 6 (Shamu) Factory Image for T-Mobile (MRA58X)

  321. Ant Joseph says:

    Doesn’t work when trying to update to 6.0.0 (MRA58N) on Nexus 5, stays on 6.0.0 (MRA58K)

  322. Fred says:

    Meu aparelho continua em Loop :/… fica apenas na tela de:
    waiting for your device

  323. Loeschi says:

    finished 😉 Thank you very much WugFresh 6.0.0 (MRA58N) on Nexus 5 is rooted

  324. nirbhai chadha says:

    Hi Wugfresh… Thank you for the brilliant application. I was successfully able to fix (partially) my nexus 5 which had this weird issue with impromptu reboots.

    The device worked fine for some time but now I am getting the issue again intermittently. Any word of advise from yourself or some one more experienced.

    I love my nexus 5 and really dont want to part with it

    • WugFresh says:

      I would suggest backing up and reflashing stock with “Flash Stock + Unroot”

      • nirbhai chadha says:

        I did indeed do that with the “Soft Bricked/Bootloop” option selected. The device worked perfectly for a week / ten days and then was back to acting up again…

        Though I must add that it doesnt happen as frequently as it was happening earlier. As soon as the device was out of warranty at the end of last year this issue started happening and the frequency increased to a point when I had to install DTSO (Double Tap Screen On Off) and even the slightest touch to the power button would send send my phone down bootloop. When this would happen, I used to start my device by hammering away with multiple clicks on the start button…

        Atleast after using your tool to root and upgrade, there was no issue initially and when it did resurface, it is not that frequent. Hope that helps put things in a better perspective.

        • nirbhai chadha says:

          Hi Wugfresh,

          The restarts are becoming more frequent now. Another thing that I am noticing is that the date sometimes goes back to a random older date which makes no sense at all to me. For example after one of the restarts the date went back to 14 September and I had only used the NRT tool sometime in end October to install marshmallow.

          Any thoughts of what the issue can be and how to fix it.

  325. Byron says:

    Good afternoon. I was attempting to flash the latest marshmallow 6.0 through the NRT. But, for some reason, the NRT did not recognize the zip file for the mashmallow 6.0. Am I suppose to unzip the file first and then run it through NRT?

  326. Jsteef says:

    Hi Wugfresh… Many thanks you for the amazing application. In custom recovery my storage couldn’t mount and i found 0 MB (nexus 7 2013 Wi-Fi). Is there any chance to root my device 🙁

  327. hey Wugfresh. Using 2.1.0 and Nexus 6 (successfully got to Stock 6.0.0 MRA58R via NRT 2.1.0), I’m unable to do the following: Advanced->Restore Stock Recovery (gets stuck in TWRP saying “Waiting for Device” – after I reboot manually from within TWRP. Tried twice. Not sure if ADB Connect only working in PTP (vs MTP) mode has anything to do with it (I think pre-Marshmallow it had to be in MTP?). Also, the OEM Lock does not work. In both cases, NRT thinks it was successful, but neither are working for me. How can I help debug? Let me know!

  328. Steve Cabito says:

    Hi Wug, thanks for all the hard work. There are still some things I can’t do with 2.1.0/3097 because it says there’s no modified_boot.img for my Nexus 6P (MDB08L). Is this true? Should I just wait?

  329. K3Fen says:

    Used toolkit to succesfully root Nexus 5x. But seems like can’t write in /system or something. (Busybox app won’t install to system, AdAway can’t write hosts file in system, etc.)
    Also have a Nexus 5 just rooted and it doesn’t have this issue.
    Help? What do?

  330. K3Fen says:

    Successfully rooted Nexus 5x (using nrt 2.1.0.) but can’t write to /system or something. (Busybox won’t install in /system/… AdAway can’t write host file to system, etc.) Any solution to this?
    My Nexus 5 that I just rooted (using the toolkit as well) doesn’t have this problem.
    Help? What do?

    • K3Fen says:

      ..and i double posted this. My bad.

    • WugFresh says:

      According to many users, there is a newer version of busybox out now that works. I will be updating the kit with this shortly.

      • K3Fen says:

        I’ve already downloaded/updated busybox from the playstore. I don’t think this is the issue.

        • WugFresh says:

          Which build are you trying this on that is giving you difficulty?

          • K3Fen says:

            MDB08M on Nexus 5X. I’m definitely rooted now but anything that needs to write to system will not work like I said. Which defeats a lot of the purpose of rooting. Your toolkit worked perfect for my Nexus 5 and 7 though. Just something is off with 5x. Seems other are having this issue as well.
            Thanks, really appreciate the work you put in.

          • WugFresh says:

            I am able to reproduce this fail install behavior on my Nexus 5X. I am investigating the issue. Either the root kernel will need further modding, or some of the available root apps such as busybox installer will need further updating.

          • Brain_san says:

            For what it’s worth, I’m seeing the same problem on a Nexus 5X with BusyBox, and also AdAway and AdFree.
            AdAway complains its symlink can’t be created, and blames HTC’s S-On as a likely culprit.
            AdFree fails silently. It claims all is well, but doesn’t actually block anything.

          • Recko says:

            I am having the same issue. Would be appreciated if you found a work around. Thanks for your great work!

          • K3Fen says:

            I’m using Xposed Framework now with modules like Adblock that are working perfectly fine so I think it’s just that a lot of the root apps (like busybox) need updating.
            So yeah I don’t think it’s an issue with the toolkit/root but what do I know.

          • Nick R. says:

            It seems with Marshmallow, there is a *lot* less space in /system to install Busybox. I’ve seen it listed as 19mb free or even less, which necessitates removing some System APKs to gain enough free space. Some have suggested even using System App Remover from the Play Store to solve this.

          • CoolHwip says:

            I’m having the same issue with my 5x. Also, on nrt 2.1.0 when I do “root and also flash custom recovery” after installing and booting up the phone the toolkit restarts my phone again and flashes the stock recovery automatically for some reason.

          • nicki says:

            do you have any update on this? my phone is successfully rooted but the system directory is read only. as well as meaning busybox fails to install, it also means AdAway is unable to edit the hosts file. I’ve tried a number of methods to remount system to give read/write access but have been unable to.

          • WugFresh says:

            Hey, yeah – spoke with Chainfire about this complication the other day, and we will have to await the next version of SuperSU for a working fix.

    • yaoppp says:

      Had the same issue, i thought wugfresh is using the wrong rooted boot image. I don’t use busybox.

  331. SoupDawgs says:

    Successfully rooted N6 MRA58K. Of course I realized MRA58R was available after. So updated to R and rooted again successfully.

  332. art says:

    Thanks, successfully upgraded my rooted N5 MRA58K to MRA58N then root

    One small thing though, when I rooted my N5 MRA58N, the Busybox did not install but the root was sucessfull, weird.

    I manually installed BusyBox just in case.

    Everything worked fine

    Thanks again Wugs

  333. Gary says:

    Thanks for the toolkit – donation just sent. I rooted a Nexus 5 on MRA58N, however when I tried to create nandroid backup w/ custom recovery I got this error message: “This feature will not work properly without a modified boot.IMG. There is currently no modified boot.IMG available for your MRA58N. You may have to wait for/ WugFresh to build and upload it. It is recommended to upgrade to the latest build available first.” What does that last sentence mean? should I have waited to root until after there was a “modified boot.IMG available for your MRA58N.”?

    • WugFresh says:

      Work still needs to be done for all the fully automated features in NRT to work on Marshmallow. You can make nandroid backups manually with TWRP for now. The features currently available are as much as I am able to do right now, but more will come soon once I can build similar modified boot.imgs for Marshmallow, like I was able to for lollipop.

  334. tamanaco says:

    Unable to root Nexus Player using NRT 2.1.0 – I’m able to flash the Marshmallow 6.0 MRA58N ROM, but after I follow the the steps to root and install TWRP recovery the Nexus Player gets stuck in the bootanimation. The only way to get it to boot is to re-flash the MRA58N. I had a similar issue with my Nexus 7 2013 when I rooted it with NRT 2.0.7, but was fixed with an updated boot image that was subsequently added to the toolkit. Is any one else having issues rooting the Nexus Player using this Marshmallow image?

  335. tamanaco says:

    Sorry if this is a duplicate post… but I can’t see the one I posted earlier. Maybe it got lost somewhere.

    I’m able to flash the Marshmallow 6.0.0 MRA58N image using the NRT
    2.1.0, but after flashing the 3 zips (perm-recover-signed, SuperSU-2.52
    and busybox-signed) in the root flash folder, the Nexus Player gets
    stuck in the bootanimation. If I flash the ROM back, the Nexus Player
    boots right away without any issues, of course, without root. I
    experienced a similar problem with my Nexus 7 2013 with the first
    release of the NRT 2.07 which was fixed with a subsequent 2.07 update that had an updated boot image for the Nexus 7.2013

    Btw, in order to flash the root files with TWRP you need a mouse (I’m using
    a Logitech wireless keyboard with an integrated trackpad) in order to
    select the options in TWRP recovery and to swipe the arrow to the right
    in order to flash the selected files. (The swiping can be a little

  336. Saitek says:

    Can i flash when there is no modified boot.img ? I will put the rom and gapps on my smartphone, will it work?

  337. Matt says:

    Nexus 5 running MRA58N with root thanks to you!
    There is still a little trial and error as far as getting it to boot after rooting and then factory reset to get back into the settings where I was able to clone from my other phone. I’m guessing there is a less round about way to get it done but it is finally done! Thanks Again! Next to work on the nexus 6 root….

  338. Victor Qu says:

    Hi WugFresh,
    As you know, the android monthly updates for December 2015 will roll out soon for both Lollipop and Marshmallow. When do you plan to support those new builds?

    • WugFresh says:

      I typically aim to support new builds within 48hours after they are released to Google’s factory image page. Ideally less than 24hours if I am notified immediately. The last few months I have just been extremely busy and there was a lot of work needed to be done to support marshmallow – which is why the project stalled a bit. Things are back on track and a lot of work has been done on my end go hopefully make supporting new releases quick again.

  339. Jack says:

    my anti virus software says this download is not safe

  340. jsz3us says:

    I updated my Nexus 6 to MRA58N and then decided to root it. After I did, I tried to install ad block on it and it gave me an error that “/data/data/xxxx” was full and to clear space. Never had this issues before. I don’t remember the exact file path but wondered what I am doing wrong. Never had this issue before, but this is the first time I am rooting since Marshmallow came out.

  341. jsz3us says:

    Nexus 6 here, when using the toolkit, under “flash stock + root” the Marshmallow images are out of order. MRA58N should be before MRA58R. This is confusing because under the “your model type” the images are listed correctly in there. Just wanted to bring it to your attention.

  342. Chad Kuchinski says:

    Tried the root option and I’m getting an AutoIt Error…Line 27242…Error: Array variable has incorrect number of subscripts or subscript dimension range exceeded.

  343. Jyotis says:

    you need to make an update to try find out how can we unlock the bootloarder on an bootloop device running marshmello

  344. Endi Piovesana says:

    will there be support for nexus 6 t-mobile build of marshmallow?

  345. Alex says:


    i am trying to root my Galaxy Nexus device but the unlooking is not working.
    I’ve tried it on several computers and i receive always the same error message

    “Line 27242 (File “C:Program Files (x86)WugFresh DevelopmentNexus Root ToolkitNexusRootToolkit.exe”):
    Error: Array variable has incorrect number of subscripts or subscript dimension range exceeded.”

    Could you please help me?

  346. Just updated my Nexus 5 to MRA58N which went fine but I am now unable to Root it, it gets to the point where it should temporarily boot into Recovery but instead it just reboots into Android, anyone else seeing this or know how to fix this?

    I’m Using NRT 2.1.0

  347. Faiaz says:

    Hi…thanks a lot……worked well for me but my Nexus 5 is 32 GB…after the downgrade my storage shows only 12 GB…can you please help me with this.

  348. Hudson Lofchie says:

    When I boot into TWRP none of the zips are in the /sdcard/ folder. What am I doing wrong?

  349. Muneeb Sohail Qureshi says:

    Hey, i downloaded the MRA58N Custom rom from XDA and was trying to flas it on my N5. but when i try to do it through NRT it gives me error that “there is no modified boot.img available for your build.” i am currently on MRA58K rom and cant upgrade because of this error. i tried updating and reinstalling NRT but the error still prevails.
    please help.

  350. Dn Bro says:

    Hi there, just got the Nexus 6p and noticed you just updated this to include the 6p. I’m really stuck though because I can not figure out MTP. Did something change in Marshmallow that I am not aware of. I am doing the initial setup and can’t seem to find a way to complete step 2 in the initial setup. I look for the menu in the upper right hand corner (step 3 of tab step 2) and I just can’t find it.


    • Dn Bro says:

      Replying to myself here. I just skipped over it and installed drivers using recommending settings and then ran the test and there was no issues so I’m assuming I’m good, even if MTP doesn’t seem to be working. Is that okay?

  351. Streamliner says:

    Just wanted to say that (for me at least) the current iteration of your toolkit, 2.1.0, is working flawlessly. I have a Nexus 6P and am rooting and upgrading the Android build. Thank you for all of your hard, dedicated work. It’s very much appreciated

  352. Jeffrey Hurtado says:

    donated some $$ for your troubles… thank you for this useful tool

  353. James Self says:

    I just have a question. I want to use this to root my nexus 6p. But I want to keep android pay. I know there’s a systemless root method out there. I know this doesn’t do that. I can’t get my computer to recognize adb. Is there a way I can unlock the bootloader with this and then install twrp and then flash supersu manually with the beta. Would that work? Can anyone help please.

  354. Chuck T says:

    Unlocking Bootloaders for 6P is giving a warning screen at boot up… what is going wrong here? I noticed this in Android Police artical..

    By now most orders for the Nexus 6P have been delivered, or at least
    getting close. If you haven’t tried unlocking the bootloader yet, it
    might come as a surprise that the ‘fastboot oem unlock’ command
    no longer works. Attempting to use it with the Nexus 6P fails with a
    message that it is an unknown instruction. Don’t worry, this doesn’t
    have anything to do with drivers, and it isn’t a fluke. Google had
    Huawei replace the oem command in the Nexus 6P bootloader with the new flashing command. Here’s what it will look like:

    fastboot flashing unlock

    fastboot flashing lock

    fastboot flashing unlock_critical

    fastboot flashing lock_critical

    fastboot flashing get_unlock_ability”

    Have these commands been put into NRT yet? Also how do we fix this.

  355. CoolHwip says:

    Any update on the /system read only issue with the nexus 5x? And thanks for the work you guys do, I’ve been using NRT with my Nexus 5 for long time and it’s a huge time saver for rooting/unlocking/re-rooting after updates.

  356. A shoutout and lots of love to Wugfresh for the great tool! Looking forward to installing and rooting MMB29K on my Hammerhead.

  357. HomeX says:

    v6.0.1 (MMB29K) and many more rolled out… o/ Waiting for update 🙂

  358. Brian says:

    How long does it generally take to upload and push new image files to the toolkit after Google releases them?

  359. Muneeb Sohail Qureshi says:

    Wugfresh please help with my error. Due to it i am unable to upgrade to latest build. i posted the error few days back.

  360. vinh says:

    can it root Nexus 7 2013 LTE android 6.0 yet?

  361. Dan B says:

    Sorry wug. Trying to root nexus 7v2. Goes fine until temporarily opens twrp. Waiting for device. There are no zip files in sdcard to flash. Any ideas on how to get it to work. I’m using version 2.1.0. I’m on stock ota LMY48I. When it boots into twrp every folder is empty.

  362. sonofjon says:

    Having some problems rooting a Nexus 5 with NRT 2.1.0. I have unlocked the device and the driver test was successful, however during the rooting process at the stage when the log says “Temporarily Booting TWRP…” and the rooting instructions for TWPR window pops up the phone simply reboots into Android. The phone does not enter into the TWRP menu as expected. I would appreciate some advice how to problem solve this issue. The device has been rooted before using an earlier version of NRT. Thanks!

  363. Dora Babu says:

    Hi, My Nexus 5 – 18 months old phone. suddenly turned off. Keeps restarting while connected to power. Left for couple days, didnt work out. Removed and packed back the battery, even though no-luck. I have taken to Mobile store, he said there is a problem with power section and it is now sorted out, tried switching it on but showing like Starting Android but its like on going process.. turned off and tried it again. Left full night to allow it itself staring the android but same screen in the morning also. Mobile store guy said to hard factory reset if it didnt work-out but i will loose the data. so, today morning I started doing to with youtube videos help. But again ended up “Recovery Mode” – “No Command” screen freezing and coming back to same story. At last tried with NRT V2.1.0, however i have a new screen using it today that is to chose “Yes” option while trying to unlock it. but again there after no further process…. “Notification window – Wait for your device for finishing up booting……..” Please help me out in giving any solution for this..

  364. Scotty York says:

    Wug – are you going to release a new NRT that supports rooting for the most recent builds? I just used NRT to install MMB29K on my Nexus 6. Worked fine, and I seem to be getting improved LTE. BUT, NRT 2.1.0 won’t let me root because this build isn’t listed….

  365. Scotty York says:

    Posted earlier, didn’t seem to work: when will NRT support the latest builds (including 6.0.1)? I’ve flashed MMB29K, and it worked well – but NRT (2.1.0, masterlists 3099) won’t let me root it because the build isn’t officially included….

  366. Victor Qu says:

    When will you add support for build MMB29K?

  367. Tol Dark says:

    Wug, thank you for such an incredible i would say piece of art) and question: will you add root support for the latest android build (MMB29K)?

    • Ry says:

      Of course he will as he said below it’s usually done within 48 hours but might sometimes take longer depending on how much free time he has.. You really didn’t need to ask.

  368. HomeX says:

    Chill guys, I’m sure WugFresh working on it, please be patient…

  369. WugFresh says:

    6.0.1 added – root working properly on my devices. Busybox install issue with the playstore app is a known problem at this point – still investigating the best fix.

  370. miki beneti says:

    Is there any chance how to install busybox some other way?

  371. Mirco says:

    Great work, Wug, alays used your fantastic tool! But with this version I am not more able to root my Galaxy Nexus, this is the error:
    “Line 27242 (File “C:Program Files (x86)WugFresh DevelopmentNexus Root ToolkitNexusRootToolkit.exe”):
    Error: Array variable has incorrect number of subscripts or subscript dimension range exceeded”

    I see (few comments down and also in the official discussion on XDA) that also other people are having the same issue with this version and this device. Can you please fix it? Thanks 🙂

  372. Nick R. says:

    Hey Wug, thanks so much for this. I was wondering if you were going to add MRA58X now that Google posted it?

    • Ry says:

      Think you could read the posts below before asking a question with a obvious answer?

      • Nick R. says:

        Think you could read the posts below too? Searching for ‘MRA58X’ only shows two hits, one of them mine. I was asking if he was going to add it to NRT, since Google *just* posted it a few days ago. Who died and made you Moderator?

        • Ry says:

          It’s the Nexus Toolkit. Wug has added support for everything that’s come out since it’s development.
          Don’t you think he get’s tired of multiple questions asking “Wug are you gonna add support for ABC123” within 24 hours of it having been released? The answer is obvious. If someone did die I’ll would’ve been someone who knew what thew answer was.. along with about oh..99.9% of just about everyone else who actually uses this tool. If I was a moderator I’d have a rule against asking that and would auto delete any posts and warn anyone who asked. Don’t kids came off spoon feeding after a couple of years?

          • Anthony Pettit says:

            Will wug be adding Android 7 when it gets released? Yes, yes he will he has done for the last however long! I’d Like to reiterate what Ry has said the NRT gets updated soon after release so pointless asking its not going to make it go any quicker! Lets keep this to troubleshooting and what not and not just a means to bug Wugs.

          • Nick R. says:

            As far as I know, and what I’ve seen, MRA58X is not available in NRT as an option. I’m not *begging* for Wug to add it, I was merely curious if he *was*, since Google posted it about a week ago after the other versions.

          • Ry says:

            Yeah I know that it’s not supported right now but it can’t be too far off.

  373. Ted Voltolina says:

    Wug, thank you for all your work. Having issues with Nexus 5X and AdAway. I’m able to root with no problems, on 6.0 and just now on 6.0.1. But when trying to set up AdAway, I get an error: “Copying of hosts file failed.” It seems I don’t have permission to write to the hosts file, even though I have root access. I also have a Nexus 9 that works fine with 6.0.1 root + AdAway. Worked fine on my old Nexus 5 too. The only issue is on the 5X.

    • miki beneti says:

      I had the same problem, gmail was notifying me that I have problem with play services. So uninstall updates of play services, update them again and after that you will be able to install busybox without problem! And after all, ad away is working like a charm!
      Cheers! 🙂

      • Ted Voltolina says:

        Thanks for the reply, but that didn’t work for me. I uninstalled the updates, reinstalled, and then tried AdAway, and I got the same error message. Also tried running AdAway before reinstalling Play Services update and received the same error.

        Has anyone else been able to use AdAway on a rooted 5X?

        • tamanaco says:

          You most likely need a little space in the system partition. I had this issue before and I used Titanium Backup to remove Google Korean Input and Google Pinyin Input from the system partition as I don’t use these.

          • Ted Voltolina says:

            I was able to permanently delete Docs/Sheets/Slides using the new 6.0 feature for uninstalling certain system apps (not just disabling them). Shouldn’t that be enough space?

          • tamanaco says:

            Use an app like Diskinfo to find out how much space is left on your system partition. Some apps look for some minimum amount of space left in that partition in order to execute.

          • _08/15_ says:

            there actually seems to be a problem with the 5X and root. while all root-apps are saying that access is there (and granted via SU), it’s read-only. not sure what causes this, and it does not seem to affect everyone. i noticed this by trying to install the newest busybox, deinstalling system apps with TiB, and ultimately using AdAway. every of those actions failed.

          • Ted Voltolina says:

            This is what I was thinking. Nothing seems to be working. Thankfully I’m able to flash MOAAB, but it’s not as good as AdAway. I only want root to block ads.

    • KatTara says:

      I’m having the exact issue as well. I’ve tried flashing busybox and then installed the latest busybox from the play store. This allowed busy box to install properly, but it still seems like I don’t have permission to write to the system partition. :'(

  374. livealoha says:

    Mahalo for your work on this awesome tool. I have used it previously to root and unlock the same phone. Unfortunately, i am getting the same error reported by other users. “Line 27242 (File “C:Program Files (x86)WugFresh DevelopmentNexus Root ToolkitNexusRootToolkit.exe”):Error: Array variable has incorrect number of subscripts or subscript dimension range exceeded”.

    I am using Samsung Galaxy Nexus Verizon sch-i515.

  375. Atma Darkwolf says:

    hi again, long time… back with the n7: Got one issue I came up to recently that I have to note – When your softbricked(bootlooped, etc) and have to use the toolkit to repair it, the popup instructs you to ‘hold power, volume up, and volume down’ at the same time. THIS does NOT work with nexus 7, you need to hold power ‘until it powers up’ (When u see google, and the locked/unlocked icon) then, while still holding down power, hold down volume down key(NOT up)

    Just a small note (Im unsure if the same is true of the n5 or n6, but I haven’t had issues with my n5 or 6)

  376. art says:

    MMB29K Flash+Unroot my N5, then root, no problem at all.

    Thank you very much, Wug!

  377. Jay Zimmer says:

    N5X just flashed latest MB29K and on boot get message “There’s an internal problem with your device. Contact your manufacturer for details”. I didn’t root just stock this is just 1st/2nd boot after flashing stock.

  378. Nigel Almada says:

    Just flashed 6.0.1 and rooted my N6
    everything works fine
    But when i try to access to recovery , i’ve the droid laying down with the belly open and the red sign. Why ?

  379. Loeschi says:

    Hey WugFresh you’re the greatest 😉 Update Nexus 5 to Android 6.0.1 MMB29K = Check !!! Root = Check !!!
    Thank you ver mutch for the great work everytime

  380. Deeco says:

    Nexus 7 (2013) – Android 6.0.1, root supported?

  381. Chandri MacLeod says:

    Does this update (2.1.0) support MMB29K root on the Nexus 5X?

  382. Hey WugFresh, keep up the awesome work. I just noticed that 5.1.1 (LMY48Z) isn’t recognized for my old Nexus 10 — any plans to sneak that in there so I can root? 🙂

  383. Jonathan Yeboah says:

    Wug for life!

  384. Edmond says:

    Hey… Thanks for this great thing!:)
    So, any chance of having a completely automated rooting also in Android 6.1? Why, as you might know, there are many visually impaired Android users who like to root their Nexus devices independently without asking a sighted assistance for help. This was possible in Android 5.1.1 but now I see I have to do something on the phone in the end of the rooting process. Note that I am not talking about bootloader unlocking, since I already did that and did not relock my bootloader. I am talking about the stage that we need to add the zip packages and install them.
    So again, any chance of having an automated root like before?
    Thanks so much!

  385. Marius Merchiers says:

    Hello Wugfresh. is there a reason why in NRT it is still SuperSU 2.52 and not the latest beta: 2.62??

  386. Johnny C says:

    I’m already rooted on my Nexus 6 with android 6.0 but I want to update to 6.0.1 with the ota but I understand it will take away root if I do. My question is, will rooting again with this toolkit wipe all my data?

    • Jay Zimmer says:

      Rooting should not wipe the data, only unlocking the bootloader does that. If you already unlocked your bootloader you won’t be able to take an OTA, you have to manually update. If you manually update using NRT make sure to use no wipe mode

  387. Ted Voltolina says:

    Hey Wug, any update on fixing root access on the 5X? I don’t think I’m the only one — I can root successfully, but it leaves me with read-only access. 6.0.1 / MMB29K

    • _08/15_ says:

      no news so far i’m afraid. in the meantime i opened a topic in the forums.

    • WugFresh says:

      Try updating, reflashing stock and rooting again. Now kit is using 2.62 supersu which autopatches the kernel and uses systemless root.

      • Ted Voltolina says:

        Awesome, I was debating on whether or not to manually use 2.62, but now I don’t have to! I will try on the 5X and 9 this afternoon and report back. Thank you!!

        • _08/15_ says:

          just tested it and i can confirm that root works now, you have to pay attention though. after you flash the zip files as instructed, TWRP on its own will ask you if it should install superSU. this you have to decline! also make sure, that before attempting to root you deinstalled any manual updates (playstore) of superSU and busybox.

          • Ted Voltolina says:

            Thanks for confirming! What if you factory reset, flash stock, and unroot first? After big adjustments like this, I generally like to even OEM lock so that I’m 100% back to factory state, and then I go through the NRT process from scratch. Hopefully that works.

          • _08/15_ says:

            i don’t see how that could be a problem. ofc the factory reset should already get rid of the playstore updates, so one step less for you. the important part really is to decline TWRPs request to flash superSU, since this to my understanding replaces the version you just flashed with the zip. (it even tells you during flashing to dismiss the request)

          • Ted Voltolina says:

            I didn’t have time to do the full unroot and relock on my 5X. So I just flashed stock, unrooted, then rooted again using SuperSU 2.62 and it worked. AdAway successfully wrote the hosts file, no more ads! Thank you so much Wug, donation incoming!!

      • sonofjon says:

        I can confirm that following these instructions works on my Nexus 5X. I had the same problems as Ted before. Thanks!

  388. Dave Crenshaw says:

    WugFresh, First of all Thank You!. I use this last month to unlock and root my Google Nexus 6P and got it running great on Verizon even though it isn’t white list yet. I am running Android 6.0 and Build MDB08L. I keep getting an OTA 6.01 message. I have been reading through below and it seems that I can now use the tool to move to the new Android 6.01. However, I am a bit confused on the steps. Would it be possible to spell it out? Should I Flash Stock and Unroot first?

    Keep up the great work.

    • wK says:

      I just updated from 6.0 MDB08L to 6.0.1 by doing flash stock + unroot and it works. Make sure check no-wipe mode if u want to keep your files. However, I cant root after updated to 6.0.1.

  389. shds86 says:

    hi. i updated my n5 hammerhead from 6.0.0 to 6.0.1 and tried to root that. first time tried to install su-2.62 but it failed. second time i root n5 with su-2.52 – was done. what is the problem?

  390. Danya says:

    Thanks for this work! I update my nexus 6 from 6.0.1, how I can install root to my device?

  391. Satyam Shukla says:

    Thanks Wugfresh…..
    I soft bricked my nexus 5……now by the help of this toolkit….I m back….
    I m a I can’t donate…..but I can say you thanks…..Thank-you So Much

  392. Mirco says:

    I can confirm (just tried) that the issue with Galaxy Nexus is still here.

  393. KARTIK KELA says:

    Thanks wugfresh, i followed all instruction to unlock and root my Nexus 4 ,BUT after rooting, when i try to reboot in recovery mode, i get android lying on its back with ” ! ” mark on it, Also i didnt get busybox fee app as well. what went wrong? please reply.
    thanks again.

  394. Den says:

    Wugfresh, When I set the root on your nexus 6, the first time using it I have it flies. What should I do?

  395. Chris Joyce says:

    rooted my 6p but cant update the supersu binary keeps failing. need help. have 2.62 on nexus root toolkit but the supersu on play store is 2.46 can someone please help

    • _08/15_ says:

      just guessing, but sounds like the same inconvenience the 5X suffers from at the moment. did by any chance after flashing the zip-files from the recovery twrp specifically ask you if it should flash superSU for you?

    • Eric says:

      This is exactly what is happening with me, was it fixed?

      • Chris Joyce says:

        So the first time I tried to root it I didn’t save the zip files to the sd card. So I reflashed it and saved all the zip files to the sd card. At the the end of rooting the phone twrp said your phone doesn’t seem to be rooted and wanted to download SuperSU again. I told it not to, and everything thing is working perfectly now.

  396. tamanaco says:

    After updating the Material list and updating the SuperSU zip to version 2.62 via the NRT 2.1.0 I was able to successfully flash Android 6.0.1 MMB29M and root my Nexus Player with the updated SuperSU. Only issue that I have now is that the Home button of the Nexus Player remote does not bring me back the the Home Screen (Leanback Launcher). I re-flashed the image several times with and without root, but still the Home button does not function. I wonder it this is a bug in MMB29M or if they change the behavior of the Home key. It’s not the remote key itself as the same thing happens when I use the Home key on my Logitech K700 keyboard. Both these Home keys worked with previous versions of Marshmallow.

    • WugFresh says:

      Not sure about your home screen issue – rooting wouldn’t affect that, maybe a hardware issue, or bug in that google release. Regarding recovery however, sounds like TWRP never flashed properly. Reflash it. See this FAQ:

      • tamanaco says:


        First of all thanks… re-flashing TWRP fixed the issue of not booting into recovery. I apologize for the off topic question, but my understanding is that you also have a Nexus Player. Are you running Android 6.0.1 and if so, does the Home button of your remote work as expected? Like I said, I doubt that it’s a hardware problem as it’s happening to my remote and my K700 keyboard simultaneously. Both of these Home keys worked fine before flashing 6.0.1.

        • tamanaco says:

          Factory reset fixed the issue with the Home button on both the remote and the keyboard. Wish I could’ve found exactly what was causing the problem. Reset the NP over 5 hours ago and I’m still re-installing and re-configuring the NP settings, Kodi and other apps.

  397. mari says:

    nexus 6 with android 6.0.1 successfully rooted using supersu 2.62. The problem now is when editing the build.prop system file, the file
    contents get deleted ie it has zero content in it. I tried two root file managers, root explorer and fx manager. Really the phone is not
    rooted properly until you can edit system files.

    • yurtesen says:

      You probably ran out of space in the /system partition. Go and delete some system packages like asian input methods etc. (unless you are using asian inputs, remove something you dont need) then try again.

  398. mari says:

    rooting with su ver 2.62 creates a problem when editing the build.prop file it deletes its contents

  399. mari says:

    Problem solved, now able to edit the build.prop file.
    Rooting with su ver 2.62 didn’t create the problem.
    android 6.01 filled the system partition, I deleted the
    YouTube apk from the system partition app folder
    and then was able to edit successfully.

  400. Jon says:

    I have a Nexus5x brand new out of the box. I did the OTA update to 6.0.1. I unlocked, rooted and installed TWRP, seemingly with no problems – I didn’t receive any errors. However, as of the time of this writing, my phone has been sitting at the “swirling dots” loading screen for about an hour. Any advice?

  401. Warren Udd says:

    Doesn’t have option for LMY48Z 🙁

  402. Joe Salazar says:

    “Hashcheck missmatch” I wasn’t able to go beyond that point. Nexus 6 Android 6.0.1

  403. DirtyDroidX says:

    Hew wuggie, hit me up on hangouts. I want to port youre toollbox over to linux so you can make it work for both platforms. The all in one Nexus toolkit!

  404. Shawn says:

    Hello Wug,
    As you know Chainfire is now working on some kind of systemless root… The newest Supersu install zip will detect whether if the phone’s boot image support traditional way of rooting. But I found that with Nexus 6 on MMB29K I cannot do it the old way. All I got is systemless root. On the other hand, it seems that Chainfire stopped making Nexus boot images for traditional rooting. Would you patch boot images for Nexus devices? I hope there are people who still prefer the traditional nonsystemless root, just like me.
    Thanks. I will buy you a beer again.

  405. Eric says:

    After loading up SuperSU on Nexus 5x 6.0.1, I’m getting a “Insallation failed ! Please reboot and try again.” error. I’ve rebooted 5 times already.

    • _08/15_ says:

      that’s because you overwrote superSU with another version. uninstall all updates you may have made to superSU via the playstore, flash stock+unroot with NRT again. after that try to root it again with the tool kit. after you flashed the zip-files and the recovery asks you to flash superSU decline and say *no* to that, since that flashes another version over the one you just put on your device with the zip-file.

  406. Mike says:

    I tried wugs toolkit. I have custom recovery installed and I’m unlocked ,but I’m stuck on the maeshmellow boot logo I can not get my device to boot up.

  407. Ronen says:

    Hey Wug,

    Got an error after flashing 6.0.1 (“nowipe” mode) on a N5. I keep getting the following error every time I try to update the “model type”:

    Line 19098 (File “/path-to-folder/NexusRootKit.exe”)

    Error: Subscript used on non-accessible variable.

    Tried to root afterwards and got the never ending marshmallow logo loop (similar to some of the comment bellow mentioned). I was able to recover from that by flashing back to 6.0.0 and then to 6.0.1 again.

    Any suggestion on how I can root my device.

    Happy holidays and thank you for the wonderful job you are doing.

  408. GenericName says:

    I recently updated from windows 7 to windows 10. I seem to be having troube with NRT Dependency Downloader. Every time i click the “Download+update all dependencies” it gives me an incomplete download and of course fails the hashcheck. It worked fine before windows 10.

    I can download it manually by fallowing the link in the pop up, but just want to know if there is anything I can do to solve my problem.

    Tried running as administrator, reinstalled and check my firewall/antivirus. Any help would be much appreciated.

  409. Shibli says:

    I’ve rooted my nexus 7(2012) with Nexus Root Toolkit at android 4.2.2 (JDQ39) “nakasi”. After that Super User was installed in my tab. Everything was fine, but last week I unfortunately tried to update the android version to 4.4. But the tab showed that update is failed and after that the tab is struck with “no command” and a dead android with red pyramid. As I can not start/boot tab so I can’t enable USB debugging, so I cant use the toolkit again to flash back. My windows 7 pc also don’t show the tab. I tried almost everything as I can surfing internet.
    Now please help me to get back my tab. It’s my daily companion actually. And thanks a lot in advance.

  410. John Luce says:

    as I have NRT 2.1.0 installed on Windows 10. I am trying to Flash Stock + Unroot my 2012 Nexus 7. It errors out with “Line 27242 (File “C:Program Files (x86)WugFresh DevelopmentNexus Root ToolkitNexusRootToolkit.exe”): Error: Array variable has incorrect number of subscripts or subscript dimension range exceeded.

  411. Coop says:

    Nexus 7 2013 LTE, latest Android update appears to have bricked it. NRT worked to the point of unlocking the bootloader; it shows “rebooting” but the device itself is still at the “Unlock bootloader?” screen. I’ve retried it:

    05f0afc3 fastboot

    Connectivity Status: Fastboot Device Connected

    + Bootloader Status: Locked.

    fastboot oem unlock

    Rebooting your device…

    However device does not reboot and continues to sit at the “unlock bootloader” screen.

    What might I try next?

  412. Kory Sheldahl says:

    I have a nexus 6. MotoXT1100, XT1103 Android 6.0.1 MMB29K
    I’m trying to OEM lock because I have to send it back for warranty. The NRT says it work, but it is still showing unlocked when it boots. I’m not sure where to start so I can fix this and I have to sent it back today 🙁 . hopefully someone can help me.

    NRT v2.1.0

  413. Jay Patel says:

    After the root process nexus5 will not start. it will display only booting process.Pleass give some help

  414. Richard Morris says:

    ok all, if you have upgraded to 2.1.0 and getting any errors, find nd use NRT 2.0.5 and reinstall, DO NOT update the program, I’m flashing my n7, after trying for a couple hours last night. thought this may work, and it is, no errors and fulling flashed 5.1.1 so far

  415. YuCMi says:

    Will the backup option also back up my Android device ID? I want to unlock and root, but I need to preserve my device ID because of Play Music.

  416. CustExperGuru says:

    Arrrgh! 2.10 worked on a Nexus 6, one Nexus 7 and then pulled the Windows error reported for the last few years “Error: Array variable has incorrect number of subscripts….”

    Need a link to roll back to 2.05. 2.06 was a complete abortion and doesn’t work for anyone that I can tell.

  417. Marius Merchiers says:

    Question about busy box. Do I install it to system/xbin or su/bin. Previously before system less root it was xbin. But now busy box fills in su/bin for me. Is that correct?

  418. Isam Diab says:

    You saved my gift to my son after some friend break it , now its new nexus 6 and he is very happy, all the best to your team, im in Jordan – Amman and I cant donate unfortunately due to restriction in my bank card, happy new year to all.

  419. HomeX says:

    v6.0.1 Nexus 7 / (MMB29O) and many more out! Waiting for update 🙂

  420. Philippe Boudreault says:

    THX a million time, save my new Nexus 6 , that i just receive today, and that i probally softbrick … lol and Root it at the same time. I sent you a donation 😉

  421. Christopher Smith says:

    I’ve been using this superb tool ever since I’ve had my Nexus 5.
    I tried to send you a donation but PayPal didn’t allow it because I live in Japan. Too bad!
    I respect ya very much! Keep up the great work!

    • WugFresh says:

      Thank you! Is there some other donation/pay service that most people in Japan use?

      • Christopher Smith says:

        Sorry for the late reply! I think Google Wallet can do the trick. It’s certainly available in Japan– I can tell that because I made a donation to the Japanese Red Cross through it when that earthquake hit us 5 years ago.

        I’ve got your latest update just now. Your work is awesome!!

  422. Adam says:

    Nexus 6 … This Build name is not there – “MMB29S”

  423. Ivan says:

    i root my nexus5 ang then my nexus 5 is stuck in 4 dots. can this toolkit can fix my phone?

  424. Craig says:

    Can i use this tool kit to root my Nexus 4, using windows 10? if not, does anyone have the link? thank you in advance!

  425. Conner Claybaugh says:

    Quick Question!!
    I currently have a Nexus 5 which is rooted and running android version 4.4.4 build KTU84Petio

    I want to update it to 6.01 marshmallow.
    My question is, can I use the flash Stock/Unroot tool from 4.4.4 to get to 6.01
    Do I need to flash the 4.4.4 stock rom first before updating to 6.01
    is it possible to just update it to 6.01 from 4.4.4 and not loose root access?

    Much love and thank you for your help!

  426. Conner Claybaugh says:

    Quick Question!!
    I currently have a Nexus 5 which is rooted and running android version 4.4.4 build KTU84Petio

    I want to update it to 6.01 marshmallow.
    My question is, can I use the flash Stock/Unroot tool from 4.4.4 to get to 6.01
    Do I need to flash the 4.4.4 stock rom first before updating to 6.01
    is it possible to just update it to 6.01 from 4.4.4 and not loose root access?

    Much love and thank you for your help!

    • _08/15_ says:

      short: yes, no, no. long: don’t forget to backup all your important data. consider not using the ‘no wipe’ mode, since an upadte of that scale can bring some incompatability issues. you can simply re-root after the update.

  427. Moose05 says:

    Any plans for a Linux Debian release? Will this work in WINE?

  428. Shortwave Pirate says:

    Trying to use NRT to flash CM to my Nexus 6. Continue to get an error that says “Dependency Not Available” and that a modified boot image is not available. Using Advanced Utilities >> Flash Rom. . .what to do?

  429. HomeX says:

    N7/2013 , NRT v2.1.1 : Stuck in “Retrying [Attempt #1 of 5]: fastboot getvar unlocked”. Prev versions working fine. Any solution?

  430. Warren Udd says:

    I just went straight to google and flashed factory 6.0.1 the long way.
    Works flawlessly BTW. ATT has no excuse.

  431. Wolfgang says:

    Nexus 5, NRT 2.1.1: Update to MMB29S was successfull but rooting ended in a bootloop.

  432. Ted Voltolina says:

    Trying to root Nexus 9 Wifi with 2.1.1. I get all the way to TWRP but it fails to load SuperSU.

    • Ted Voltolina says:

      Update: It worked when I downloaded SuperSU myself and put it into the root directory of the N9’s internal storage. I think that maybe automating the process or not using a modified boot image might have caused it to miss an important step on the N9. So it’s all working now. On a positive note, I no longer see the yellow warning message on boot about not being able to check for corruption. (MMB29S)

      Next I tried it on my 5X. I put the SuperSU zip onto the device’s internal storage just in case, but I don’t think that was necessary this time. The process worked without error. However, I do still see the yellow warning about not being able to check for corruption. Not a big deal though. (MMB29P)

      Everything seems to be working for me, thanks for another awesome release!

      • WugFresh says:

        I should add this to an info box – but the yellow warning you are describing is entirely normal (and unavoidable) behavior for an unlocked nexus 5X/6P device – this is just a security warning google decided to integrate.

        • Ted Voltolina says:

          Yeah the yellow one doesn’t bother me. But oddly enough (as of this morning on 2.1.3), when I Flash Stock + Unroot (no wipe mode) my N9, I get the red warning at boot, and SuperSU is still installed (and I did not install it from the Play Store). It’s unable to run since I no longer have root, but it’s there. Previously Flash Stock + Unroot would boot with no warning, and SuperSU was gone.

          I rooted the N9 again with 2.1.3 to see if I’d have a better experience than my OP, but I still got the same error. It looks like root files are getting pushed to the device while I’m still entering my password into TWRP. Then when it’s time to install SuperSU, it can’t find the file. It bumps me out to the TWRP home screen, and then I choose the reboot option. It prompts me to install SU before rebooting, which I decline.

          So then I boot back to Android, drop SuperSU 2.66 into the root directory of my N9, and go through the process again. Same as my 2nd post above, it worked that way. However, I’m no longer able to delete the !ReadyToFlash folder on my N9.

      • Matthew Shapiro says:

        NRT hasn’t pushed the zip for SuperSU to my Nexus 6 in ages, either. I just preload it manually onto the internal storage, then apply it from TWRP.

        • Ted Voltolina says:

          This was a first for me. It has always worked for my N5, N9, and N5X until now. Can’t confirm either way on the N5 right now, since I sold it when I got the 5X.

  433. Mark Ward says:

    . Thank you.Worked perfect updating to MMB29S and rooting on my Nexus 9.

  434. Emmanouil Peros says:

    Im trying to root my nexus 7 running android 6.0.1 everything is alright but when it boots into recovery there are no files anywhere, no possible to mount anything, just nothing all folders are empty. Does anyone else have this problem?

  435. armoredshoes says:

    Hitting unlock on 2.1.1 Nexus 6 it says test encrypted, and does nothing else. Ideas?

  436. mikeytusa says:

    When flashing/rooting my Nexus 6, my NRT settings are set to use the beta SU and also to install busybox. It never installed busybox. Once I flash root, my phone booted up. Upon another reboot, I got stuck at the Google logo and had to flash again and wipe my phone.

  437. Mark Ward says:

    On Nexus 6P after rooting it gets to the boot animation and then just stops. It never does finish booting. Left it for 45 minutes, then powered off and tried to boot again and get the same thing, shows the boot animation and goes no further.

  438. Andrew says:

    fastboot getvar unlocked? what this, as I was trying to upgrade to 6.01, I cannot even test the driver guide as it will not unlock?

  439. azukay says:

    The date on your changelog for the latest version is wrong, should be 2016 not 2015 🙂

  440. Dave Frischknecht says:

    WugFresh, for the Nexus 7 2013 at least, there is no fastboot variable called “unlocked”. When I do “fastboot getvar all” I see a variable called “lock_state” with a value of “unlocked”. I believe you need to update your toolkit to take this into account.

  441. Will Cox says:

    When i try flashing a ROM or backing up on my nexus 7 (2013), there is a error dialog box saying “rety Fastboot getvar operation” and so, i use the original USB cable and my ports are OK. Can i tell me why?

  442. brolly says:

    Thanks for your work on these great toolkits.

    I just used to NRT to root my N5 a few days ago, and now I’m prompted with a monthly update for my phone which I can’t apply as I’m rooted. What’s the best way to apply these monthly updates now?

    • WugFresh says:

      Actually with the systemless root, you should technically be able to take the OTA successfully (make a backup first), and then you will just re-root afterwards. The previous NRT release (2.1.0) still made some system modifications if you had it flash custom recovery, so you may want to re-flash stock and then re-root with this latest NRT release v2.1.2 – then, moving forward you can try just taking the OTA regularly and then using NRT to re-root afterwards.

      Or alternatively, you can use NRT’s “Flash Stock + Unroot” button then tick “no wipe mode” to upgrade your device to the latest android release without wiping your userdata (then root afterwards).

      • brolly says:

        Thanks for the fast response!

        I did use 2.1.0 to flash root, and tried to apply the security update which failed. But I’ll update the NRT as you say and reflash stock and re-root and try again. Would be amazing to get those OTA while rooted.

        I’ll post my experience. Keep up the great work man.

      • brolly says:

        Re-flashed stock & unroot with no wipe which worked great. I then rooted and I was all up to date and everything’s fine. I guess I can’t test the OTA until next month, but I’ll try to remember to post when I do.

      • brolly says:

        Hey, well I tried this months security update OTA and just got the android logo and a message saying error. I am not using a custom recovery so I’m not sure why it wouldn’t work.

  443. Jonas Forsberg says:

    Recently I soft bricked my Nexus 6P by messing with kernels too much, I fixed that, completely restored it to factory default. However now when I try to Unlock the bootloader I always get weird error messages (and yes I made sure I went through the full manual driver setup process and adb and fastboot all checked out) like “adb server outdated” or “encrypted” or ever just a blank small window labeled “test”. What’s wrong? (Build number 6.0.1 MMB29P by the way.)

  444. Aishwarya Jain says:

    I have Nexus 6P, hope it’s supported. I’ve read to unlock bootloader a full system swipe is required but I have more than 95 apps installed and I don’t wish to download them again can I create backup and restore all apps as they were before the root?

    • giriraj bhootra says:

      Yeah,you can do that by using apk extractor or xender .
      Apk extractor will create apk’s for all your installed apps.
      By using Xender u can send all the apps to another phone and than take them back after root from that phone.

    • Andrew Snyder says:

      also you can create a Android Backup File or a Nandroid backup file both are included in the Toolkit. Personally I use APKExtractor because its much faster than the back ups and in some cases more reliable.

  445. webmasterone says:

    I would like to suggest a new feature.
    As many of us (that have a rooted device) install also Xposed, why don’t you add this fetature in your tool (to install/remove Xposed Framework) ?

  446. Ray James says:

    Hi Wug. Thanks for fixing the getvar unlocked problem.

    Now my Nexus 7 2013 WiFi was able to flash stock, and afterwards successfully re-rooted.
    There was one hiccup – while flashing stock NRT reported that writing of system had failed, although it had actually completed successfully.

    Following was displayed:

    erasing ‘system’…
    OKAY [ 0.184s]
    sending ‘system’ (843393 KB)…
    OKAY [ 29.601s]
    writing ‘system’…
    FAILED (status read failed (Too many links))
    finished. total time: 46.825s

    FAILED (command write failed (No such device or address))


    • WugFresh says:

      You should repeat the process with an alternate USB port. The errors your received indicate a bad connection.

    • Juraj M. says:

      I just tested with Nexus 7 2013 32GB with version 2.1.3, flash was successful but after re-root I ended up in boot loop. After re-flashing I have at least working updated device but without root 🙁

      erasing ‘system’…
      OKAY [ 1.201s]
      sending ‘system’ (843393 KB)…
      OKAY [ 26.420s]
      writing ‘system’…
      OKAY [ 40.152s]
      finished. total time: 67.775s

  447. Lightrafale says:

    Hi !

    I’ve been looking for a way to root my phone for a while now and I ended up findind this.

    Please, can you tell me : does it work on a Nexus 4 running 5.1 ?

    Thanks !

    • Andrew Snyder says:

      it works on the Nexus 4 Running any version of android that is officially put out by google, rooted phones work as well.

      • Lightrafale says:

        Oh thanks !
        And, I don’t mean to bother you but I’ve red some comments talking about bricked phones.
        If it doesn’t go well, will it brick my phone ?

        • Andrew Snyder says:

          it shouldnt, i did it many times on my nexus 4 until i accidentally deleted my OS in TWRP and bricked it. but NRT had nothing to do with the bricking. NRT uses direct factory images from Google so it is safe.

  448. chobani says:

    I rooted my Nexus 7 (2013) maybe a week ago and now there’s a 2016 update available.
    How would I go about updating without losing root?

    • Andrew Snyder says:

      from Wugfresh: “Actually with the systemless root, you should technically be able to take the OTA successfully (make a backup first), and then you will just re-root afterwards. The previous NRT release (2.1.0) still made some system modifications if you had it flash custom recovery, so you may want to re-flash stock and then re-root with this latest NRT release v2.1.2 – then, moving forward you can try just taking the OTA regularly and then using NRT to re-root afterwards.
      Or alternatively, you can use NRT’s “Flash Stock + Unroot” button then tick “no wipe mode” to upgrade your device to the latest android release without wiping your userdata (then root afterwards).”

  449. Phssthpok says:

    Ok, I just used NRT 2.1.3 to root my Nexus 6 MMB29S to try systemless root, AdAway, cflumen and Android Pay. Android Pay fails at checkout. No big deal, I’ll just unroot. Reverted AdAway to original hosts, removed AdAway and cflumen.

    I then used Flash Stock + Unroot with NoWipe mode and everything appears to run successfully. However, I get the “Your device is corrupted” error at boot. I’ve tried running the flash stock + unroot a couple more times and use the advanced utilities to flash the kernel, recovery, and system individually but with the same result.

    Anything I’m missing? And can I get back to clean booting N6 with working Android Pay without doing a full wipe?

    • Andrew Snyder says:

      you are most likely going to need to do a full wipe because there could still be root files in your phone (even if it systemless idk) but id say you need to wipe data. if you can just backup everything and put it all back its not that hard.

  450. Scott586 says:

    Thanks for this awesome toolkit, very nice! I finally rooted my Nexus 10 tablet and installed Marshmallow [AICP]. Can you add build “[B]LNY48Z[/B]” to the presets? Thanks!

  451. LeNon says:

    trying to root nexus5 with v.2.1.4 … error message: ADB recovery device was not found
    with former versions(v.2.1.0) just worked fine

  452. LeNon says:

    trying to root nexus5 with v.2.1.4…error message: ADB recovery device was not found
    just worked fine with former versions(v.2.1.0)

  453. .. says:

    @wugfresh:disqus Can you add Custom ROM – M (Marshmallow) for Nexus 4 and 5, Galaxy
    Nexus, Nexus S option for the Selection of Android Build? New ROMs
    supporting those devices is on XDA.

  454. seal308 says:

    Hello, I can not open the toolkit. I am on Vista. Device is a nexus 5. When I double click the exe it does not open. I tried right clicking and to run as administrator but that did not open it either. please help!

  455. seal308 says:

    Hi, I cannot open the toolkit.
    I’m on Vista and the device is a nexus 5.
    I double clicked and nothing happened.
    I tried right clicking and to run as administrator, but that didn’t work.

  456. Juraj M. says:

    Nexus 5, all OK using v2.1.4. I had same problem with root as with Nexus 7 2013, ADB recovery not found, just open Device Manager and uninstall (and install again) the Android Device / …ADB…. It may NOT be marked with yellow triangle at all! THANKS A LOT!

  457. Chandri MacLeod says:

    There’s a note back in the 2.1.1 changelog that NRT has adopted the Chainfire systemless root method. Does this actually mean that, using NRT 2.1.1 and later, we can successfully accept the prompted OTA updates when they appear on our phones and simply re-root the phone afterwards?

  458. Johnny C says:

    Can this toolkit help me upgrade to the January 2016 security patch without losing root?

  459. Ed says:

    Download link isn’t working for me. Do you have any mirror links?

  460. John says:

    Download link isn’t working for me, do you have any mirror links but on a different website?

  461. Joseph Wellman says:

    Wug is it passable to gat a modded boot to remove or change the boot warning on the Nexus 6p

  462. Ed St John says:

    Error – ADB Recovery Device not found.In Device Manager there is no yellow exclamation point, so what do I do? Also, if in DM I go on android device and browse there, I do not get the same menus as described. Can anyone help?

  463. Ed St John says:

    And also to get around the error below can I flash zips without rooting? I.E I’ve unlocked so can I just flash cm13 now or not?

    • WugFresh says:

      Once unlocked, yes – you can use a custom recovery to flash zips. In advanced utilities there is a button for booting into custom recovery temporarily, which you can use – or you can flash it via the “fastboot flash > recovery” button.

  464. andreas ioannou says:

    Nexus 7 2013 WIFI stuck after update. Tried to unlock but freezes after I press YES with power button. Any suggestions are appreciated

  465. andreas ioannou says:

    Nexus 7 2013 bricked after update. Tried to unlock but freezes after I push YES with power button. Any suggestions?

  466. Mark says:

    Just wanted to say THANKS! Nexus 7 came back to live 🙂

  467. Max Lavoie says:

    Trying to root my Nexus 5x with your software. Ran into a problem i can’t find a fix for online. Unlock worked fine, all drivers were successfully installed. Problem is when i try to root it. When it reboots my device and attempt to boot into recovery, i get to a “no command” screen on my phone and toolkit tells me my drivers need updating. Any help or idea would be great.

  468. Diana says:

    I have my Nexus 7 (2013) rooted with NetHunter, however it will not “see” the USB wi-fi adapter I have plugged in via an OTG cable. It is the TP Link TL-WN722N adapter so I believe it should be working. What needs to be done to get the USB adapter working?

    • _08/15_ says:

      i don’t know what you are trying to accomplish with that otg setup, but it sounds intruiging. i do however own that very same wifi adapter. i don’t know how the situation with linux/android is, or how android manages drivers in general, but i do know that the driver situation for this particular adapter is terrible when it comes to windows. unreliable, unstable and way behind with releases.
      as for android OTG in my experience, it’s either plug’n’play or you’re most likely out of luck.

  469. PostHumus says:

    I can not download dependencies files automatically (it said can not access server), so where can I download the files directly?thanks

  470. Alastair says:

    i just wanted to say thank you, i was suffering on 4.1.2 with a nexus that wouldnt upgrade and also was stuck in a nfc service loop rendering the device unusuable. I now have a working device thats currently upgrading and ticking along very nicely.
    thank you so much for all your time and effort into going into this project

  471. creed says:

    Does the root feature work with MMB29S on the Nexus 6? Every time I run the root feature, when it’s finished, the phone will not boot. I get the screen with your phone is running corrupt software press power to pause boot and that is as far as it gets. Am I missing something?

  472. HomeX says:

    Nexus 7 / 2013 v6.0.1 (MMB29Q) and more february update is out, waiting for masterlist update 🙂

  473. DoC DefoC says:

    Are there known issues with the encryption after rooting a Nexus5? I’ll get in a ‘looping’ bootscreen after activating encryption. Waited over 3 hours. After a new bootup, it appears to be normal but without encryption.

  474. Thomas Au says:

    Does NRT 2.14 support 6.0.1 (MMB29Q) on Nexus5?

  475. Pals013 says:

    I tried to install the OTA update with the February security patch level with systemless root on Android 6.0.1 MMB29S on my Nexus 9 but it comes up with error 7 on twrp. Can someone help me please to fix this?

    Thank you

  476. TheInvisible says:

    Nexus 7 Wifi 2013, 6.0.1 / MMB29Q, Device encryption enabled: Rooting with NRT 2.1.4 ended up in a bootloop. With NRT 2.1.3 no problems at all…

    • Daniel Kian Mc Kiernan says:

      Are you saying that you successfully rooted a Nexus 7 2013 WiFi MMB29Q using NRT 2.1.3? Or are you simply saying that you did not have trouble rooting previous builds with NRT 2.1.3?

  477. tamanaco says:

    After updating my Nexus Player to MMB29U and rooting using NRT 2.1.4 the USB port of the Nexus Player does not work after a full boot into Android. The only way that I can get the USB port to be recognized is by booting the NP into bootloader mode. In bootloader mode my Windows computer Device Manager recognizes the NP as an Android Device->Android Bootloader Interface. From this mode I have re-flashed MMB29U and also gone back to MMB29T and rebooted the NP, but once Android boots the USB port does not work. Before the update when I connected my USB Hub to the NP after it booted, the LED of the USB Hub would come on… now it doesn’t. I suspect there’s an issue with the USB driver. I have flashed in full wipe mode and have factory reset the NP several times. Any idea as to what might be causing this issue?

  478. pgellen Anderson says:

    hey, im new at this but, frustrated. i had a samsung galaxy s3 that was a sph-L710. it got to the point that the on and off switchwas getting weak and the charging and usb plug disintegrated completely. i hooked up wireless charging however ive only got limited access to the computer and my phone was always hooked to the computer for music and i also did a lot of learning file systems. im very good on this phone after having to re odin it about 15 times. now, my new s3 is an sph-L710T. the only thing that i can see that the t applies to is the bootloader which is locked harder than i have been able to crack. can anyone help me with this problem before i take this phone vback.its a great phone but i wang to get rid of some never used apps and files.

  479. christian2001 says:

    Nexus 7 2013 Mobile, flash stock from MMB29O to MMB29Q. Flash w/No Wipe worked fine and boots normally. Rooted, and stuck at “Starting apps.” Reflashed to MMB29Q w/No Wipe and boots fine. Tried root again and stuck at “Starting apps.” Any ideas?

  480. NubCake says:

    Are we getting TWRP 3 support? 😛

    • Jeffrey Sherman says:

      It’s there now. Update File dependencies, etc. Any update on rooting Nexus 6P with MMB29Q? Wugfresh detects it, but given others’ troubles, I’m hesitant to try.

  481. Johnny Cage says:

    After flash stock + unroot my nexus 5 boots to green android with red exclamation. What do I do?

  482. Jam Spider says:

    Any way to use Android Pay with root enabled?

    • _08/15_ says:

      google just recently patched AP to even detect systemless root. the onlyway i know of atm is to go into superSU and disable root manually while AP is in use

      • Scotty York says:

        Not so – it’s still possible to get it working without having to disable sSU — see my post above

        • bigfire says:

          I can confirm Scotty York’s finding. I’m using the current March patch level Nexus 6P with systemless root. I use Root Browser to change permission on /su/bin to 751 and remove the /su/xbin_bind symbolic link. I pay for my lunch using Android Pay.

    • Scotty York says:

      Google has been patching to make this more & more difficult, and after installing MMB29Q + systemless root 2.67, I lost Android Pay. HOWEVER, if you do 3 things, it’ll work again (at least, it did for me, on Nexus 6). You’ll need a decent file explorer app (I use Total Commander for Android – give it root permission).

      Open TC, go to “File system root”. You’ll see a folder called su. Open that folder and do these two things.
      (1) delete the folder xbin_bind
      (2) long-press on the “bin” folder to open a popup. On the popup, tap properties. On the next popup, tap RWX (you’re going to change the folder permissions). At the bottom-left, it’ll show 755. Change that to 751, and tap Apply.

      Now (3) reboot. That should be you rooted, with Android Pay working.

  483. Zazzels says:

    After running the update it didn’t unroot the phone. The xu binary file isn’t there. Did I do something wrong? I pressed FlashStock + Unroot and everything worked fine. Nexus 5 from 4.4 to 6.0.1.

  484. Zazzels says:

    I just updated from 4.4.x to 6.0.1
    Somehow my phone is now not un-rooted anymore. It says the xu binary is missing. Shall I redo the update or will it not un-root anymore at all due to the new android? btw is paypal the only method to pay (donation)?

  485. Kennon Wong Chun Cheung says:

    Hi, is it the root work for latest build 6.0.1 (MMB29Q) nexus 7 2013 WIFI???

  486. Nick Chen says:

    Need support for Nexus 5’s 6.0.1 (MMB29Q). Thanks!

  487. Anandharaj Subramaniam says:

    What is the root method NRT is using? Systemless? or traditional root?

  488. Ry says:

    Hey Wug, could you make NRT use the system’s default browser to launch links (changelog, guides, threads) rather than launching IE? Cheers.

  489. Daniel Kian Mc Kiernan says:

    I run Android 6.01 on a 32 GB Nexus 7 2013 WiFi. After using NRT to unroot, I successfully installed the February update to MMB29Q, but each attempt now to re-root the device results in a boot-loop. Each time, I am able to use NRT to unroot, but re-rooting again results in a boot-loop.

  490. Borsa says:

    While I was flashing stock + unroot my nexus 5 turned down and now it doesn’t turn on anymore… I’m not able to do anything with the phone because the computer doesn’t recognize it and doesn’t turn on.
    Is there a solution to this problem?

  491. Ruben Perez says:

    My experience finally do root on MMB29Q: First flash and unroot Nexus 5 all OK. Trying to root and custom recovery doesn’t work but I finally could do it. Manually reboot Nexus to bootloader mode, then try to do the procedure. Temporary TWRP and push files correctly but fails the rooting procedure, so device boots without root. Then I go to Advanced Utilities and do a Temporary Custom Recovery (I put device on bootloader mode first manually), and go to Install, search the files on “Ready to Flash” and select SuperSU 2.67, perm recovery and busybox that before has been pushed, flash all three and reboot. All works and device is rooted correctly.

  492. Mahdi Khan says:

    is this systemless root

  493. Mahdi Khan says:

    is the root systemless

  494. Siebe says:

    Rooting no longer works for Nexus5 MMB29Q. I can do it manually, but then what’s the point of having this program? It seems it’s not flashing recovery correctly, so all the other steps fail as well (although the program doesn’t seem to pick up on that and just continues to the end).

  495. Desmond says:

    Guys, can anyone share how can i swap the menu and back softkey?

  496. Wolfgang says:

    I had the same problems with rooting my Nexus 5 and Nexus 7 that some others have: TWRP pushed the zips for SuperSU and busybox to the device but then failed to install them.
    Finally I followed the steps of the ‘Full Driver Installation Guide’ in NRT to completely remove all Android/Nexus drivers from my PC and reinstall them. Then everything worked fine :-).

  497. Joseph Wellman says:

    problem with Nexu 5x. when I try to unlock it using 2.1.4 everything is going right till the point were the script puts up the screen to make the phone display the Yes No option to unlock the phone all it does is make it reboot
    tried it 4 times on 2.1.4 and not asking for some help thanks

  498. Joseph Wellman says:

    I have a nexus 5x but I cant unlock the bootloader. in NRT 2.1.4 It get to the point of where it tells me to pick yes or no but just before it pops up NRT reboot the phone. so I tried in using the fastboot commands. I got the newest SDK files and I use the command fastboot oem unlock and I get error FAILED: (oem unlock is not allowed) so I tried the new command fastboot flashing unlock and still same error
    please any help thanks

  499. Johnson Lee says:

    When root Galaxy Nexus@Stock JWR66Y, reboot to TWRP then ADB find the divice, but toolkit can’t.

  500. slalomnut says:

    If you haven’t found a work-around here’s what I did for my N7 2013. Downloaded twrp-, replaced the twrp- in the “Program FilesWugFresh DevelopmentdataRecovery_CustomTWRP” with twrp- Be sure to rename it to twrp- Then do a root + customer recovery.

  501. darkz says:

    when I search and open the page,,ity shows “Posted on November 13, 2012 by WugFresh”,I don’t know if the version is the newest, so can change the “post time” to “update time” so every can know the version time clearly ??

  502. Ray J says:

    I have a Nexus 5, with 6.0.1 (MMB29S) installed. When I try to update to 6.0.1 (MMB29Q) it goes through all the motions, but it never actually updates. When it reboots, it’s still at 6.0.1 (MMB29S). I’ve tried multiple times, and even once wiping the device. It just can’t get to 6.0.1 (MMB29Q), what can I do?

  503. Deeco says:

    Systemless root supported?

  504. todd holzwarth says:

    What was once a painless operation, I am seemingly unable to backup an image or restore one. Ive done it many times over the past couple of years on n7 2012 3g devices. but im constantly getting checksum errors mismatch, adb push errors, etc. unlock, root, bootloop fix, etc all still work

  505. Sigh, Using 2.1.4 on a nexus 5 (soft-bricked/bootloop). The ‘force flash mode’ still gives dialog box saying bootloader is locked.. of course we cant unlock the bootloader if the phone wont boot. can someone help?

  506. Mayank says:

    when i try to install the toolkit,i am getting an error which says “nexus root toolkit.exe not found”. Any help please !!

  507. Brian M says:

    So, I updated a Nexus 5 and a Nexus 10 to the latest. However, on both rooting failed. I got “ADB Recovery Device Not found”. No matter what I did I could not fix this. In the end I used Advanced Utilities… Custom Recovery. Once on TWRP I went through the regular procedure; Install; “Ready to Flash” and select SuperSU,
    perm recovery and busybox; flash all and reboot. Got root successfully doing that on both devices. Just didn’t work using the NRT method.

  508. Aubrey Armorer says:

    i have a nexus 7 2012 that is in bootloop and when i try to (flash stock + unroot ) it says that the “ADB Device Not Found. what do i do ?

  509. Jackie says:

    Anyone having problems, I used windows 10, but couldn’t get it to work until I went to a windows 7 laptop.

  510. Dean Stratton says:

    Dear Mr WugFresh. Your goal was to make this entire process as smooth and simple as possible…….you’ve failed.

  511. Eldrin says:

    Using NRT (v2.1.4) for the very first time (with my Nexus 4), everything was going smoothly up to a point. I did the necessary driver configuration, unlocked the bootloader, and then chose to root the device and at the same time flash the Custom Recovery (TWRP). That seemed to work successfully, but afterwards a window popped up telling me to Open SuperSU and then after that Open BusyBox Installer. Well, where is BusyBox? I don’t see that anywhere. Now I’m stuck.

  512. Timmy Johnson says:

    Need help, nexus 6 rooted bootloader unlocked I was using the nrt and the advanced utility board and in where it says system I put a zip file twrp open recovery in that box, now my phone won’t come out of the load up screen that says google but if I put in bootloader mode I can make it go into twrp settings screen, I tried recovering it from the tool but says its not detecting adb fastboot any suggestions on how I can reverse this and get no phone back.

  513. HomeX says:

    v6.0.1 (MMB29V) March updates are rolled out 😀 Waiting for masterlists update 😉

    • Scotty York says:

      Why wait? Download it yourself from the main factory image site. Copy the MD5 hash. Then Use NRT to install it, pointing the program to the file you’ve just downloaded (you’ll be prompted to enter the hash). I did it yesterday on my Nexus 6, using no-wipe mode. Then rooted. Worked flawlessly. After doing the usual tricks, it’s now working with Android Pay…..

    • mickrussom says:

      The v build for March is bad. Switch to MHC19Q

  514. Origin says:

    @wugfresh:disqus Google rolls out security updates on the first Monday of each month.

    MMB29V and other factory images are available.

  515. XilehNori says:

    The new N preview is out, shamu-npc56p-preview-54b13c67, I assume Nexus Root Toolkit not ready yet

  516. Origin says:

    The last activity of Wug Fresh was a month ago. I hope that he is fine.

  517. jony says:

    wug make a patch nrt shortcut once uninstalled is necessary remove it manually

  518. Chandri MacLeod says:

    Sadly, even though MHC19J is showing up in the lists now and flashed fine to my Nexus 5X, rooting via the “Root” button in NRT was still a failure.

    It gets as far as booting temporarily into TWRP and then I get a request for a password, and when I can’t provide that (having no idea which password it could be) I get a “failed to decrypt” message informing me that I’m going to need to “format data” (I assume a wipe) in order to proceed. I’ve ended up just rebooting to get out of TWRP, but on boot I’m also now getting the red “corrupt” warning rather than the orange one from before, and I am not rooted. I’ve tried this twice without success. Really don’t want to regress to flashing custom kernels but running out of other ideas…

    • Chandri MacLeod says:

      Further research suggests this is a (new?) issue due to the 5X’s encryption. I’ve tried removing all security and TWRP, as part of the automatic Root process, is still demanding a password that doesn’t exist (I’ve also tried “default_password” but no dice). Honestly not sure how to proceed. Various manual/auto/combo methods have all gotten me back to the same place: in TWRP being asked for a password that doesn’t exist. Getting very frustrated.

  519. Chandri MacLeod says:

    Unfortunately it looks like there are still problems with the Root command for the Nexus 5x, even though the lists have been updated. MHC19J flashed fine, but then I go to Root in NRT: I can get as far as booting into TWRP, but then it requests a password to decrypt, and of course I don’t have one. Unable to root. Really don’t want to use adb sideload but not sure what else to try…

    • Chandri MacLeod says:

      Further research suggests this is a (new?) issue due to the 5X’s encryption. I’ve tried removing all security and TWRP, as part of the automatic Root process, is still demanding a password that doesn’t exist (I’ve also tried “default_password” but no dice). Honestly not sure how to proceed. Various manual/auto/combo methods have all gotten me back to the same place: in TWRP being asked for a password that doesn’t exist.

      • Nickaroo says:

        If you use a pin to unlock your phone, or have the pin set up (which is mandatory with fingerprint scanning), then input the pin using the numerical section of the keyboard in the password section. Let me know if you’ve any more questions.

        • Chandri MacLeod says:

          I use fingerprint unlock with a PIN backup, but TWRP doesn’t recognize it when entered. Even when I disable fingerprint in favour of PIN-only prior to attempting the root, it still doesn’t recognize the PIN.

          Unless you’re saying that it matters that I use the ordinary keyboard’s number row rather than hitting the number/symbol key and using the 10-key there? I’m honestly not certain which I’ve been doing, though it’s probably the latter.

  520. Tony Montana says:

    Anyone that cares, I figured out how to Encrypt the Nexus 5 (had issues with doing it) on MMB29V and previous version. It would hang on the boot screen until I force rebooted it. I had to flash my phone back to stock, enable encryption, encrypt phone. THEN root the phone. Prior I was rooting phone, then trying to encrypt (it would just hang for 10 hours). Hope the info helps others.

  521. Ace says:

    Just tried to root my Nexus 5 with new 2.1.4 version and it doesn’t do it completely. Basically I get no SuperSu, no BusyBox or TWRP installed even though it’s present in the phone’s memory and the program reported that it finished the process successfully .Root check says that the phone is not properly rooted.
    That didn’t happen before and I’m quite surprised.
    Had to unroot it and that feature still worked for me in this program.
    Running the latest version of Android 6.0.1 build number MMB29V.
    Any advice?

    • Andrea Borgia says:

      Same thing happened to me: I had to manually install 2.8.7, then flash the latest SuperSU and then the systemless mode kicked in and patched the boot image for me. I started of from 6.0.1 with January update installed.

    • tim says:

      can confirm, had to install twrp manually. now flashing SuperSU.

    • AySz88 says:

      Boot into TWRP (you can boot into it without installing it, via NRT -> Advanced Utilities -> Custom Recovery) and install the !ReadyToFlash/*.zip files manually. (Make sure you only flash the ones that NRT put there this latest go-around – I can’t remember the names unfortunately….)

  522. tamanaco says:

    NRT 2.1.4 can’t download twrp-

  523. tamanaco says:

    Unable to download the TWRP recovery for the Nexus Player via the update function of NRT 2.1.4 (Sorry if this is a duplicate post, but I can’t see my post on this issue from yesterday – Maybe it was lost on the way or or was deleted)

  524. Benjo says:

    I can not install superuser with the toolkit, with Android 6.0.1 and Windows 10
    you think it’s a problem with Windows 10?

  525. Eric Cotte says:

    Does the software work in case of “Failed to mount /cache” errors? For me it fails when trying to unlock the bootloader. The device does ask “unlock bootloader” and I select Yes + press power, but nothing happens.

  526. Dozer says:

    Did it work with latest update on Nexus 5x ? Im waiting for USB and SIM card to start rooting ! 😉

  527. Eldrin says:

    I wonder if we’ll see a new version of NRT sometime. A version that fixes the issues where BusyBox and SuperSU don’t get installed properly. There’s been no activity on this project for a long time.

  528. Artūrs Stīpnieks says:

    I cant thank you enough. This program is a lifesaver and has saved my bricked phone like 5 times. I rate 10/10

  529. scarfacez2007 says:

    Need add for Google Pixel C please and thanks

  530. Jr Smilez says:

    If I’m on a custom rom (dirty Unicorn weekly build). do I have to goto a specific build of stock?

  531. s427 says:

    Quick question: now that I have rooted my Nexus 6P, OTA updates don’t work anymore. Is it possible to easily get these updates via NRT? How? I can’t find any option for that.

  532. Arik J says:

    Million thanks!!!
    Works like a charm :p
    Model: Nexus 5X
    Build: MHC19J
    Thanks for everything!!!

  533. John Jae says:

    Well this root the Nexus 5

  534. John Jae says:

    Will this root the Nexus 5 6.0.1

  535. Jason B. says:

    you make it so easy to customize my new 6P! I feel like a hacker but you do all the work and I just click a button. This toolkit is so awesome.

  536. Lollolollo84 says:

    MHC19Q for 5x is not present…. Why?

    • Origin says:

      The master list has not been updated yet.

      • Lollolollo84 says:

        How i can update my nexus 5x (rooted) to MHC19Q using toolkit?

        • Origin says:

          All of us will have to waith for the master list to be updated. When it will be updated then you will see a message saying the same. After that your build will get listed in the tool kit. Then you can update your Nexus 5X.

          As of the time of writing this post, the master list has not been updated yet.

          • Lollolollo84 says:

            Ok… Tanks!
            Usually I use cyanogenmod and updates are differents, this is first time for me that I use NRT… but in this case for update I need to flash stok and unroot before? And after I can root again with new build… It’s correct?

          • Origin says:


          • Lollolollo84 says:

            Do you kmow where I can found the update masterlist?

          • Origin says:

            When the masterlist update will become available then your installation of the Nexus Root Tool Kit will automatically update itself.

  537. Lollolollo84 says:

    MHC19Q for 5x is not present on nexus root toolkit…. Why?

  538. Jeff80 says:

    how come my download status is always incomplete? i wanna update new stock rom but always came out with this error message.

  539. Curter says:

    then does nothing… 😐

  540. Rhanmar Azucena says:

    Can i use this on nexus 5x h798 variant?

  541. Curter says:

    can’t root MMB29V, MMB29X, MMB29O and can’t flash recovery

    • jabib says:

      Same thing here. The toolkit goes through the motions, but at the end of it all, nothing works. I can post a log of the toolkit if you need

      • Curter says:

        well after several trial and error, it worked on MMB29V, nrt doesn’t have configuration for X or O yet, but it acted weird on V too, kept me showing some recovery driver is missing craps although i re installed drivers 4-5 times restarting and torturing my machine several times; do that rooting thing couple of times on V version and you’ll get it works; don’t care bout the systemless rooting shit, just wanted to root the mofo to get rid of android’s fuken ads…

        • jabib says:

          I got it to work last night, I downloaded the latest MOB30D release instead of letting NRT pick the release. Flashed properly, and actually got the proper commands to TWRP to install root. If you don’t care about TWRP, you can likely unplug your phone with the temporarily loaded recovery and install the zips yourself.

          • Curter says:

            1. MOBxxx is not hammerhead; nrt doesn’t have selection for versions beyond MMB29V
            2. wanted to flash twrp manually through adb and i got the commands right, but nrt adb failed several times on manual attempts.
            3. after several attempts , it worked on MMB29V and was only able to flash twrp through rooting, hope this version of super su let the OTA in

  542. Cayden Hyde says:

    My Nexus 7 2012 is stuck in a boot loop. USB Debugging is not turned on, will that be a problem? I believe it is just a software malfunction and I think a factory reset will fix it.

    • Jakob says:

      I have the same bootloop-problem with my Galaxy Nexus. Does wugfresh’s backup-feature work for my not rooted device with USB-Debugging turned off and locked bootloader? Is there a possibility to backup my data (at least my sms)? Stucked in a bootloop I can’t turn on USB-Dubugging by using the normal phone settings. Is a turned on USB-Debugging necessary for wugfresh?

  543. mari says:

    April updates are out 6.0.1 (MOB30D), and still waiting
    for masterlists update.

  544. Gruuuvy says:

    Works great on 5X & 6P; Have used it over and over again without fail. Magical Stuff! “THANKS”

  545. Aaronmod says:

    Amazing toolkit, used it to root a Nexus 7 WiFi 2012 at the weekend, worked wonders! Just tried to Unlock and flash custom recovery to Nexus 7 2013, the unlock worked, but now I can’t load into recovery, I just get a dead android. Is this because I am running 6.0.1 (MOB30D)? Such an awesome programme, thank you!

  546. Hitesh Pande says:

    hello, i tried to revert back to stock and when i click flash stock +unroot, and try to download the 6.0.1 MMB29V, it says hascheck mismatch and it aborts. when check in google site, its 6.0.1 (MOB30D) .my kit is uptodate

  547. Mayank Pipara says:

    Root Nexus 5 (mmb29v) without Installing Custom Recovery It Worked For Me, It temporarily boot TWRP and Install ROOT,
    then install Custom Recovery.

  548. ARR says:

    hi, what about MHC19Q on nexus 5x??

  549. .. says:

    Latest SuperSU BETA is v2.71
    Latest SuperSU STABLE is v2.65

  550. tamanaco says:

    Hmm, no Masterlists update yet?… WugFresh must be very busy.

  551. F. Gabriel Olvera says:

    New factory images are up since last week, any ETA on when are they are going to be available in the NRT?

  552. Chandri MacLeod says:

    Just tried to update/root to MHC19J again, now that it’s supposedly supported for root, but the update itself wouldn’t even go through. It said it was successful, but I just get a forever-stuck white Google logo. The only error I’m seeing during the flashstock.bat segment of the process is “FAILED (remote: buffer overreads occured due to invalid sparse header),” but I’m not sure what that actually means. Will probably try again in a few days just in case it’s the machine I was using, but very puzzled as the update, at least, worked fine the last try (it was only root that wasn’t working).

  553. Veritas says:

    WugFresh isn’t fresh, he ist rotten.
    No posts on twitter and no new version of NRT !!!

  554. Ted Voltolina says:

    I’m definitely not complaining about the update frequency of software that is published based on donations (and I have gladly donated in the past and will continue to), but I was wondering if we could just get a status update on rooting the April security patches?

  555. I think WugFresh should make this a paid service/app – it is that good, should absolutely be a paid service without doubt. This way it would ensure prompt updates and it would put food on the table for WugFresh

  556. J Smith says:

    cant DL anything getting mismatch over and over..trash

  557. Ilan Berlinbluv says:

    Newest version (2.1.4) does not support the Nexus 6P’s latest build (MHC19Q).

  558. Andy says:

    I’m afraid that we can no longer expect the next update … Never before WugFresh not told us to wait so long 🙁

    • jtr165 says:

      yeah, worried. This solved so many annoying issues for me with preventing forced encryption and still getting monthly security updates installed before the OTA’s even arrive…Used to mess with this manually and was tired of it, this has been great for the past few months.

      Now sitting with an OTA prompt on my Nexus 6 for April’s for weeks, but don’t want to do it if I can flash without encryption through NRT. Was sitting on the donate button if Pixel C support arrived, too. Appreciate the the help since Feb…and would gladly pay a monthly fee for these services…would also have zero problem with delays as long as people are informed as to why…but the ‘all quiet’ approach is way too OEM’ish for my tastes.

      With that said, I hope the dude is ok. It’s true that this is uncommon.

      • WugFresh says:

        Sorry for all the delays, and lack of communication. These past few months have just been incredibly busy despite my best efforts to set aside dev time. I forced myself to sit down and really grind it out bender style, and now 2.15 is finally released! I wanted to get it out asap, so I am waiting to finalize pixcel C support for the next release – which I will tackle this upcoming weekend. I spent a great deal of time automating more things on my end, so I should be much faster with future updates.

        • jtr165 says:

          After re-reading my post from yesterday; I didn’t mean for that to come across as so bitchy haha. Apologies, regardless that I made it literally hours before 2.1.5 popped up.

          Thank you very much, and I’m very happy that you’re still at it. Can’t wait for the pixel C support as well

          • WugFresh says:

            It’s all good, I didn’t think you were. Looking forward to continuing to update this, including new features and extended device support.

    • WugFresh says:

      I am sorry, but this project is far from dead. I just got swamped these past few months. I won’t let it stall like this again. v2.1.5 is out.

      • Gustavo P says:

        Great job, Wug, thanks again

      • Andy says:

        Thank you very much WugFresh. I allowed myself to send you a little bit of my gratitude.

      • Portzblitz says:

        Hi, Wug. Not sure if posting this in right place..

        For a long time my build numbers haven’t been listed in your toolkit, and i don’t know which to pick instead; right now my 6p (cm13-n) is MOB30J..

        (automatic detect is failing for me)

        Don’t know if picking the right match is closer to arbitrary, or closer to CRUCIAL.

        Lost, please help!

  559. jazzy663 says:

    This application is nothing short of impressive.

  560. HomeX says:

    Updated/rooted MOB30J (N7/2013), thanks again WugFresh! 😉

  561. Chandri MacLeod says:

    Flashed & rooted Nexus 5X to MTC19T using automatic method. Still a little thrown by TWRP having to load twice and having to enter password twice (though at least now it’s taking the password!), and got v. worried when it made me enter the Start Android password twice, but in the end all was well. Thanks, Wug!

  562. tamanaco says:

    WugFresh, first of all many thanks for the update.. A couple things… 1. the Options menu in 2.15 is not closing for me on Windows 10. I have to use task manager to force close NRT. 2. Could you add an option so that one can select to use the current “stable” or latest “beta” release of SuperSU. There are some apps that have not yet been updated to handle the latest beta releases of SuperSU.

  563. Maik B says:

    Flash & Root – – Google Pixel C

  564. Clay Peña says:

    Can you add support to android one devices too

  565. narsil says:

    First tanks for you toolkit

    I’m trying to root ma Nexus 9 wifi with encryption
    but i can’t install twrp.
    I could temoraly boot on
    then i’ve got a screen whith open recovery scrip
    and nothing

  566. yourbuddypal says:

    Hello, I think I found a bug. In the Advanced Utlities section, When using the “Flash Zip…” option with the “File is on this computer option”, in the ensuing dialog I added my zip to the list. I then hit the “Confirm Operation…” button, but got cold feet and hit Cancel on the next dialog. It acted as though I hit confirm though and continued forward and (thankfully) successfully flashed anyways. I am 90% sure I hit cancel there but… I am not going to try to repro my steps 🙂

  567. tamanaco says:

    SuperSU 2.72 beta released.

  568. Anshul Verma says:

    hey cant restore to stock firmware. i have a nexus 5x MHC19Q. Says hashcheck: missmatch. please help.

  569. Michael Doerner says:

    A lot smaller package than the full-blown Android Studio….does all the things needed to root, unlock, and factory restore any Nexus device. This is what Google should have come up with for DIY hobbyists that aren’t programmers!

  570. Fathod says:

    thanks a lot. It works perfect for my LG Nexus 5 D821(e) 16Gb model.

  571. minioninnc says:

    Have any idea if you can root Android N as of yet? Or will this not be done til the full N comes out for everyone?

  572. Dude says:

    During rooting I get a notification stating that there was no adb device found. I’ve followed every single step to uninstall and then reinstall the necessary drivers. No matter what I do, the root process get interrupted with the same notification. FYI, on previous builds, I’ve rooted and uprooted with no issues. I’m frustrated because I love your toolkit!

  573. fkinell says:

    Nexus 9 – Formatting is not supported for filesystem with type ‘f2fs’ – after N-Beta removal.

    Hi, In removing Beta N from my Nexus 9 using NRT (which has worked flawlessly everything b4) I am unable to Flash Stock + Unroot.

    The process goes through un hindered until I get ..

    Formatting is not supported for filesystem with type ‘f2fs’

    On Reboot I am stuck at the Google Screen and nothing happens!

    Either I or the solution to this is “Simple” I am sure.

    I appear to have full control over the N9, I can access TWRP I can wipe and format partitions …etc.

    Just can’t get the N9 to accept a stock ROM after the Beta N trail (which was becoming unusable anyway)

    Please help..

    • WugFresh says:

      Thank you for information about this, I will fix asap in the next release which is nearly complete and fully supports N. As a quick fix – in the flashstock.bat file, just edit the line under: “::Post-Flash Format Userdata” that says ‘fastboot format userdata’ and change it to ‘fastboot erase userdata’ Then try again.

  574. Greg Santiago says:

    My 2012 N7 has been bricked for a while now, nothing has been successful to get it back to a functional state. I think the board isn’t good anymore so I actually just ordered one as the final attempt at recovering it. Does anyone know how I will be able to reinstall the os as I think it wont have any os on it? Will I be able to use the toolkit for such thing? Thanks in advance.

    • WugFresh says:

      If you can get into the bootloader. IE boot into fastboot mode, then you can use “Flash Stock + Unroot” to install the OS. Simply use “Flash Stock + Unroot” with “Soft brick” mode, and it will walk you through how to manually boot into bootloader mode and automate flashing the OS. Feel free to reach out to me if you have any problems. Cheers.

  575. Ahpros Lee says:

    Hi, I tried this root toolkit on my nexus10 but the green, blue,yellow and red dots are cycling endlessly. It don’t proceed getting stuck. How can I fix this? Please help!

    • WugFresh says:

      Can you provide some more details, what were you doing exactly.

      • Ahpros Lee says:

        Hi, Mr. WugFresh
        After that I tried the option Flash Stock+Unroot and I succeeded to reach the set up, then it ask me to connect with wifi. I enter my PW to connect to my WIMAX router but I couldn’t connect to the router. Someone wrote that it can be done by connect to free wifi. I did it but getting stuck at ” checking connection”. Do you how to through this?

  576. bhav says:

    Hey Wug long time, so i was trying to flash stock + unroot on my friends phone but the driver configuration guide isnt working for fastboot… Its a Galaxy Nexus GSM… adb devices show the phone but fastboot devices is blank. In device manager, when phone is on, it shows “Android adb interface” but when phone is in bootloader, it shows “Android 1.0” under Other devices. Pls help just like you always have. Thx in advance…

  577. Jon Kincaid says:

    *NRT will not open when I click on it* For some reason–and I have downloaded it twice–the toolkit will not open. It does a quick load-animation, but then it goes away and nothing ever happens. I am running Windows Vista–yeah, I know…stop it!. Any help would be greatly appreciated! I ALWAY root my phones, and I love the Nexus, but this is killing me! FYI, I am using a Moto Nexus 6

    • Jon Kincaid says:

      AAAAAND a couple minutes later, I figured it out! QUICK TIP: DO THIS ON GOOD SLEEP *does crazy laugh* . Right clicked and had to go to properties and ‘unblock’ because it “came from an outside source”….NICE!

  578. Edwin Tan says:

    Hi, any chance you have this particular software in Mac?

  579. Jack says:

    I’m stuck on the ‘unlock bootloader’ section… It wont select ‘yes’ Any help?

  580. HomeX says:

    v6.0.1 (MOB30M) builds are out!

  581. Nick says:

    My build number for my Nexus 6p is nowhere to be found on the list of builds (MMB29U, running 6.0.1). Would it be safe to select one of the other builds or am I missing something?

  582. Bill Tsiftes says:

    bootloop in nexus 6. factory recovery says no command. what can i do? thanks!

  583. Jan Milants says:

    I’ve rooted my stock Nexus 6 through NRT (entirely stock, except for root) and was wondering if this method is leaving me with a modified system/ even though the systemless is supposed to leave it untouched..? As i understand it should modify the bootloader only, but not touch system..?
    The reason i’m asking is that normally flashing the stock boot partition should allow me to apply the OTA.update.. but it doesn’t, so i’m wondering if NRT might have made some changes to system/..

    Chainfire has an app ‘FlashFire’ which enables on device firmware flashing if you are rooted.. Now the best part is it has a feature where if it detects an OTA update downloaded by the OS it automatically generates the instructions needed to restore boot/, apply the OTA update and restore root afterwards… only thing left to do is reboot and you have the update applied and root restored.

    Thing is on my Nexus, which I rooted through NRT, applying the OTA update fails due to changes made to system/ … and except for rooting to be able to use some root only apps I ‘ve never really done any tinkering with it.

  584. Pharkas Gammer says:

    I unlocked my Nexus 7 2013. When I run the root script it stops and says “ADB recovery device was not found. The troubleshooting says to go into Device Manager and find yellow exclamation point. There is not an unconfigured device listed. I have an Android device with Google Nexus ADB Interface at top of screen, but it shows that it is working properly. I reran the test and it came back the same way. Please Help!

  585. DDSkier says:

    Since upgrading to 2.1.6 I am getting the following error message whenever I attempt to change the version of the firmware to use.

    Line 18980 (File C:Program Files (x86)WugFresh Developmentnexus Root ToolkitNexusRootToolkit.exe”): Error: Subscript used on non-accessible variable.


  586. art says:

    for some reason, my first attemp to root failed.

    It went thru the motion of rooting as if it was successful but it was not when I checked. I looked at the live log and it seems the SU and BusyBox wasn’t pushed to the device due to a checksum error.

    I tried rooting again after a few minutes and everything was fine, it rooted properly.


  587. Oleh says:

    Since upgrading to 2.1.6 and after clean full reinstallation I have problem with ADB and popular error of absent Wsapoll function in ws2_32.dll that is unsupported for WinXP. Reverted to version 2.1.5 – no problems.

  588. Ry says:

    Wug, change log version number needs fixing.

  589. Tyler Bang says:

    I’m currently on Android N Preview 3 (NPD35K) on the Nexus Player (fugu), just as I was about to root it, NRT prompted to update twrp, supersu, and download the noforce_encrypt_kernel. Just as I was about to download it, it wouldn’t download. I thought that this was simply a bug with the toolkit and wugfresh needed to release a patch for it. However, when I went to download the kernel from Android File Host from wugfresh, I noticed something…

    The kernel wasn’t uploaded…

    y tho

  590. coldheater says:

    I have a nexus 6p with android N Beta on it and I just did the root and install custom recovery. My phone rebooted and its not stucked at the Google animation screen. I waited for like 30 minutes because and its stucked. Any suggestioins?

  591. rushter says:

    What just happened? I setup the Android N 3 beta last week. No worries – the toolkit worked fine – I did the no-wipe rooting – that went fine also.
    Tonight I decided to get the Android N 4 beta and get it going. Went through everything – flash stock unroot – update with NPD56N, flashed no problem – everything went great. Then decided to go and again re-root it and it says something about encrypted device detected – must wipe all data to root blah, blah – because – it said – due to Android N…….TWRP……
    Anyways, why was I able to root with no issues or master wiping last time and this time – there is no choice.
    I did it though because I thought that for sure it would double check and ask if I was sure I wanted to wipe all – it did not – I know, I know – backup blah blah. But really @wugfresh:disqus why did it and actually why does it have to wipe to get root now? I am confused as to how I will get root.

    • Greg Brown says:

      Did you actually let it wipe to root? I backed my Nexus 6 up and let it wipe but the rooting process still fails with bootloop of “no command”. Same thing when I went back to Preview 3 – I can’t root that anymore or even flash stock when “force no encryption” is checked. It seems anything to do with “no force encryption” in NRT v2.1.6 isn’t working for me.
      I guess I’ll go back to Preview 4 and stay unrooted in hopes I can eventually get it rooted.

      • rushter says:

        I actually tried everything you said and had the same issues as you.
        I decided to go back to marshmallow and rooted again.
        The only problem with going back that far is that it appears that Google will not remember your profile to reinstall all of your apps, so mine asked to install the backup profile from my nexus 7. That was weird but I’m back up and rooted and since I flashed the phone, it’s quite speedy.

  592. Ayyylmao says:

    Hi, does this tool root my nexus 7 too?

  593. Pals013 says:

    I recently flashed the June security patch for my HTC Nexus 9 (WIFi only version) and whenever an app asks for permissions to specific capabilities or information such as access to my storage the “allow” option does not work once it is tapped. I have factory reset my tablet and re-flashed the factory image but the problem still persists. Can someone please help me fix this?

    Thank you

    • Mark Ward says:

      I had a problem with the Nexus 9 as well. When it rebooted after flashing the latest update it said there was a problem with the encryption and I had to do a factory reset. After the factory reset it seems to run fine but I’ve never run into that before with NRT until 2.1.6. It worked fine with my Nexus 6P with the June Marshmallow update.

      • WugFresh says:

        Did you flash android N? The toolkit removes forced encryption (for now) when rooting android N – and it should perform the factory reset for you during the root (and inform you of this in new message boxes)

        • Mark Ward says:

          No, I was just going from the M May to M June update. I did originally try to do it unencrypted but it couldn’t download the unencrypted boot image so I shut NRT down, rebooted computer and tried updating like normal with no wipe mode. I’m thinking that had something to do with it. After a factory reset it booted up running the June M update so all is well now but there was a problem trying to download the unencrypted boot image if that’s the proper term.

      • Roy Stevens says:

        I had the same problem. For the other updates I was able to side load them just fine without any need for a factory reset so having to reset was a huge surprise and I didn’t have a choice at that point. I’m glad I decided to backup before hand but having to reinstall all my apps and transfer files again is a major pain. You ought to put a warning for the sideload function that it It will cause a factory Reset. All else aside I do appreciate the program!

  594. Speedoo says:

    Hello, thank you that they have received the Google pixel C in the root toolkit . Thank you!! You are the best!! 🙂

  595. William Rittenberry (Billy) says:

    I just want to say that when someone searches how to root or unlock a nexus yours should be the first link to pop up,great work

  596. Nino says:

    I’m on v2.1.6. I was on Android Paranoid Marshmallow for my nexus 6, for some reason my phone kept blocking adb/fastboot access. I did a reset on the phone and uninstalled/reinstalled NRT (and drivers) and it still wouldn’t give access to it. I rebooted the phone into bootload mode and NRT finally recognized it, tried to do a clean installed of Preview 4 of Android N and the log said everything went fine…once I tried to turn the phone on I kept getting “no command”. Repeated every step one more time just to make sure, same result. Finally got tired and went on XDA and was able to flash Android N Preview 4 while on bootload, everything is running fine. Nexus 6 users beware, 2.1.6 may be misbehaving this time around. Before 2.1.6 tho, NRT has been the only toolkit I’ve ever used, never had any problems. Thanks for the great work!

    • WugFresh says:

      Can you clarify how you tried to “do a clean install” with NRT – because there is not fundamental difference with how it flashes N on N6 than any other build. I will check the files on my end to make sure the factory package is complete

      • Nuke says:

        I have same problems. Nexus 6 and installed Android N – first boot have green robot and error “No command”.
        Never has any problems before.

        • jtr165 says:

          Same for me. Tried the latest preview 4 of ‘N’ on a Nexus 6 w/ ‘no forced encryption’ and went into a bootloop with ‘no command’. Then tried to fall back to latest M build, also with no forced encryption, same issue. Finally flashed preview 4 again and allowed encryption, went off fine.

          I was a little worried because encryption back in the lollipop days SUCKED on the nexus 6, and I hadn’t been encrypted since (I used NRT specifically to get to M as my carrier had a weird OTA update path for it, and didn’t bother with encryption), but phone is doing great with preview 4, boots quickly and seems to be as smooth as it was without it. First time i’ve used google’s built in back up, too, and honestly kind of impressed…didn’t even bother with my manual back up from my PC.

      • rob sumptin' says:

        Same problem. Tried root. Ended up with “no Command”

  597. Mark says:

    just wanted to say thanks. I’ve rooted my Nexus 6P and everything is working smoothly. (except for Android Pay but who cares!)

  598. Alex says:

    how to lunch debug mode with a broken screen ? Nexus 6 Moto phone

  599. HomeX says:

    July updates are out! 😉

  600. Danny Kile says:

    New Builds are out 6.0.1 (MOB30P)

  601. Danny Kile says:

    Can I go from the angler-mmb29m December 2015 release to the angler-mtc19x July 2016 release without do any of the other releases? Or is that just to big of a jump.

    • WugFresh says:

      You can jump up or down as much or as little as you want – there is no restriction with the “Flash Stock” feature. But it would be advisable to do a clean flash rather than “no wipe mode”, meaning backup your data first and restore afterwards.

      • Danny Kile says:

        So what would be the biggest jump I could make when doing a “no wipe mode”? Would it be best do do each one in turn? I would really rather not do a clean flash.

        • WugFresh says:

          There is no true rule of thumb. Doing then incrementally won’t make a difference. Just do a full TWRP backup and try to just do the jump you want without a clean flash. Worse case scenario is that you have to revert back. I personally have had success with bigger jumps. As long as it’s not a full android version difference like Lollipop to Marshmallow, etc

      • Danny Kile says:

        I would really rather not do a clean flash. I prefer to do “no wipe mode”, should I do each monthly in turn? Than would be 6 updates. Thank you for a great program and you advice!

      • Danny Kile says:

        OK, I went ahead and took the plunge! I went from angler-mmb29m December 2015 release to the angler-mtc19x July 2016 release without do any of the other releases. That made it a total of 7 updates. I did this with the “no wipe mode”. Everything went just fine, thank you again for your assistance.

  602. el_lumianz says:

    Nexus 5X July Build is out MTC19Z. Need to root it soon with this amazing tools..

  603. Michi says:

    Awesome tool, thanks I am pretty sure that i will donate now