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.

Screenshots:

Main Interface

 

Instructions:
  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

Download:

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

Need a simple way to validate checksums? I recommend: http://code.kliu.org/hashcheck/

 


Credits/Thanks:
Donate:

~ 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. 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

  2. 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

  3. 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….!!!!

  4. 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?

    Thanks.

  5. 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

  6. 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

  7. 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-2.7.1.0-mako.img. 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!!!!

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

    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

    rebooting…

    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…

  9. 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?

  10. Hi..
    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” !!
    Thanks.

  11. 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…

    =========================

  12. 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.

    • 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

  13. 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 🙁

  14. 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!

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

  16. 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

    • 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.

  17. 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?

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

    • I just checked and its not working. That is strange. Thank you for bringing this to my attention. That said, it has worked on this page in the past. AndroidFileHost gave me a developer API key specifically for this reason – so I could deliver direct downloads. That’s how all the files are served through the toolkit.

  19. 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?

  20. 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.

  21. 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?

  22. 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!

    • Thank you. Please provide more details. What kind of back up. What explicitly happens. Saying “it doesn’t work” makes it impossible for me to guess what went wrong for you. Cheers.

  23. 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?

  24. 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 !

  25. 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
    DevelopmentNexusRootToolkit.exe”):

    Error: Variable used without being delared.

    (take a look at screenshot)

    Please, help me Wug !!

  26. 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
    DevelopmentNexusRootToolkit.exe”):

    Error: Variable used without being delared.

    (take a look at screenshot)

    Please, help me Wug !!

    • 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.

      • 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 🙂

        Thanks

  27. 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.

    • Create a new folder on c: and copy the install file to that folder and right-click the install file and “run as admininstrator”. Also real-time security/av software can temp block exe files during an installation.

      Also if youre getting mismatch errors on the updates just manually add the program exe as an exception to your firewall.

  28. 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.

      • 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…

        • 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.

          • 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!!!!

  29. 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.

  30. 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.

  31. 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

  32. 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”

      • 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?

        • 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

      • 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.

    • @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.

  33. 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.

      • 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

        • Then you are in luck. You must follow these steps in the exact order:
          1. Download & Install: https://play.google.com/store/apps/details?id=net.segv11.bootunlocker

          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).

          Cheers.

          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.

          • 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?

            Thanks!

    • 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*

      • 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?

  34. 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.

  35. 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?

  36. 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!!!!!

    • 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.

  37. 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!
    Olivie

  38. 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!

    • 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.

  39. 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?

    • “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.

  40. 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!

  41. 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!

  42. 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?

    • 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.

  43. 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.

      • 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.

        • 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.

          • 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).

          • 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.

        • 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.

  44. 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

  45. 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

    • 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.

      • 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.

        • 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.

          • 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.

    • 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. https://code.google.com/p/gdipp/ <<- 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.

  46. 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.

    • 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.

  47. 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

    • 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.

  48. Hi
    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 …

  49. 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…..?

  50. 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

  51. 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?

    • There is a special SMS backup feature as well. That said, I believe sms gets stored in an sql database
      here: /data/data/com.android.providers/telephony/databases/mmssms.db, 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.

  52. 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

  53. 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.

    • 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: http://is.gd/wipecache_n4

      • 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).

        • 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.

          • 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!

  54. 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.

  55. 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…

  56. 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.

    • 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.

      • 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 😉 “

    • 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).

      • 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.

    • 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.

  57. 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.

  58. 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.

  59. 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!

  60. 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 😉

    Cheers,
    Markus

  61. 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

  62. 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?

    • 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.

  63. Hello,

    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
    “Downloading”
    “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-2.8.0.1-mako.img”
    ‘OK’ to continue, it says
    “Downloading”
    “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!

  64. 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…

    • 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.

      • 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??

        • Do you have an unlocked bootloader? Some sections says that the bootloader is locked. It should be unlocked to perform the Flash Stock + Unroot I believe.

  65. Hey,

    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 ?

    • 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: http://i.imgur.com/UrlAtYU.png

      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.

    • 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

  66. 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? 😀

  67. 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?

  68. 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?

  69. Wug,
    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!

  70. 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!

  71. 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.

  72. 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 🙁

  73. HELP I’VE BEEN WAITING A DAY NOW.. NO RESPONSE. PLEASE.
    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!

  74. 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)

  75. HELP I’VE BEEN WAITING 2 DAYS NOW.. NO RESPONSE. PLEASE.
    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!

  76. 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?

    • 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.

  77. 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 🙁

    • 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.

  78. 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

  79. 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
    thanks

  80. 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.

      • 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

  81. 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.

    • 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!

      • 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

        • You are going to want to try factory resetting and trying to unlock again (and flash stock again) https://support.google.com/nexus/answer/4596836?hl=en 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

          • 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.

    • 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.

  82. 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.

  83. 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.

  84. 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.

  85. 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,

  86. 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?

  87. 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.

    • 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.

    • Thank you!!

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

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

  88. 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.

    • 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.

      • 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?

          • 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.

          • 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.

          • 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.

  89. 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

  90. 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

  91. 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?

  92. Hi,

    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?

  93. 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.

  94. Hi!
    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.

  95. 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

  96. Hello,

    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.

      • 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”.

        • 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. 🙂

          • 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

          • 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.

          • 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

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

  97. 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!

  98. 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.

  99. 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

  100. 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?

  101. 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.

    • 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.

  102. 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.

    • 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.

      • 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.

        • 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 2.0.6.1 or 2.0.7 I recommend using adb to manually upgrade as the toolkit is borked at the moment.

  103. 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

  104. 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-2.8.7.1-shamu.img download status will be incomplete.
    3. The openrecovery-twrp-2.8.7.1-shamu.img import will be incomplete.
    4. Manually download the openrecovery-twrp-2.8.7.1-shamu.img.
    5. Open the location where the nrt is installed.
    6. Paste the openrecovery-twrp-2.8.7.1-shamu.img 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. 😀

    • 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…

  105. 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.

  106. 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 🙁

  107. Hello,
    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?

    • 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.

  108. Hi,

    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………

  109. 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.

  110. 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.

    Specs:
    Nexus 7 (2013 wifi)
    Android 5.1.1 LMY48T

  111. 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.

  112. 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??

  113. 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??

  114. 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.
    THANKS

    • why would you put kitkat on a nexus5… Just go for the latest… its like going to a car dealership and asking for a new 1970 car.. Common man.

  115. Hi,
    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?

    Thanks!

  116. 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?

    • Somebody correct me if I’m wrong but to accomplish that you have to “Flash+Unroot” without wipe then install the updates thru the OTA or side-load if you like.

  117. 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?

  118. 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.

  119. 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?

  120. 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!

  121. 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

  122. 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.

  123. 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?

  124. 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?

    • I already decided to download the last factory image, (MRA58N), and start over… If I can use the NRT 2.0.6 I will rollback to 2.0.5 and let you know…

  125. 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.

  126. 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…

    • 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.

      • 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.

  127. 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?

  128. 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?

  129. 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

    • 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.

      • 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.

      • 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:
        bootloader_img
        radio_img_regular
        image_zip

        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!

      • 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

        Masterlists:

        – 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

        Masterlists:

        – 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

  130. 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 ??

  131. 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

  132. 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.

  133. 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-2.8.7.0-flo.img the location shows 404 error when I check the site.

  134. 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.
    Log:
    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?

  135. 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.

    Thanks.

    • 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

      • 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.

  136. 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.

  137. 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

  138. 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.

    Thanks

    • 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

  139. 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.
    C:UsersUserDownloadsNRT_v2.0.6.sfxdata>

  140. 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 !!!

        • 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.

          • 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.

          • 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.

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

          • 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.

          • 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.

          • 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.

          • 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.

  141. 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?

  142. 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)?

    • 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.

    • 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.

  143. 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.

    • 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.

      • 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.

  144. 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!!

  145. 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?!

  146. 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???

  147. Hello,
    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!

  148. 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.

  149. 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!

    • 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.

  150. 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…

  151. 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?

    • I am not getting this error myself, would love to try and reproduce. Can you shoot me a message in google hangouts. Its my username @ gmail. I will be happy to try and figure out why you are getting that error.

  152. 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

  153. 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?

  154. 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!
    Thanks!

  155. 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
    MRA58R
    with
    3.10.40-franco Kernel
    Just want to get back to stock and rooted. Without wiping everything again, if possible.
    Thanks Wug

    • 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.

      • 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.

  156. 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?

  157. 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?

  158. 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.

  159. @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.

  160. 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 ?

  161. 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!

  162. 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!

  163. 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?

  164. Hi,
    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

  165. 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.

  166. 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

  167. 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

      • 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.

        • 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.

          • Your only recourse is trying to reflash stock again. Try flashing a different build. If your problems persist it could be a hardware issue.

  168. 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?

  169. 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 🙁

  170. 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!

  171. 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?

  172. 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?

  173. 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?

          • 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.

          • 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.

          • 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.

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

          • 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.

          • 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.

          • 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.

          • 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.

          • 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.

  174. 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

  175. 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.”?

    • 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.

  176. 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?

  177. 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
    tricky)

  178. 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….

  179. 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?

    • 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.

  180. 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.

  181. 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.

  182. 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.

  183. Hi,

    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?

  184. 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

  185. 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.

  186. 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.

    Thanks

    • 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?

  187. 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

  188. 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.

  189. 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.

  190. 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.

  191. 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.

  192. 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!

  193. 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..

  194. 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….

  195. 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….

    • 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.

  196. 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 🙂

      • For what it’s worth, I’m running into this same problem on an Asus Nexus 7 Wifi (running 5.0.2), and retrying and retrying results in the same error each time regardless whether I start with the device showing the boot loader already or if it’s booted into Android and is allowing the toolkit to boot it to the boot loader using USB debugging. Would love to know if there’s a trick to get past this step and unlock.

      • Have you had a chance to work on this? I have the same problem with my Google Samsung Nexus S 4G running 4.1.2. Will you post a message when it’s fixed or you have a workaround?

      • 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?

        • 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 you..it 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?

          • 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.

          • 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.

  197. 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.

    • 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! 🙂

      • 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?