[HD] How to download and install Samsung USB drivers for Samsung Galaxy phones [Win 10/8.1/7]

Unlocking, rooting, relocking and unrooting simplified!
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.
Check out the updated for a more comprehensive breakdown of the feature set and changes in this release.
Help and support is greatly appreciated.
I will say tho, i trashed my first N7 v2 2013 wifi tablet the first round after 4.
Now 2nd round new N7 v2.
Only seen one other post about this problem, and answer was corrupt,incomplete download.
Can you msg me in google chat.
I pulled out old back-up comp.
It never moves beyond that point.
Any idea what the problem is?
The toolkit can flash and root it, but no full automation of other procedures yet.
Lawreys problem, but in my case im using 32bit w7, and i already have downloaded the ktu84l factory file.
If downloading manually is the answer could someone please send me a link and a clue where to put the files!
Any ideas on how to help?
Did you ever resolve this?
Make sure you select the right Neuxs7 device in the toolkit.
I waited a half an hour after that press any key and exited.
However, no matter which of the three download links I try I get a 72.
Now I can get around to backing up my phone so I can update CyanogenMod!
I will look into setting up doge as well.
I will let you know.
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.
If an android device ever freezes on you, just force powerdown with the power button.
Unlock is required to root.
Unlocking wipes, so backup first.
The driver solutions are much simpler now.
Just go with solution 1.
Thank you for bringing this to my attention.
That said, it has worked on this page in the past.
Swapped out the androidfilehost direct download link in favor of Major Geeks as the primary link.
Thanks for developing your toolkit.
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.
The only fix is to flash stock and start over.
I have previously successfully unlocked and rooted my Nexus4 with your toolkit.
But is it still unlocked, can I skip unlocking this time?
Will I loose app data etc.
And keep the project going!
What kind of back up.
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!
Thanks a lot for a possible input and thank you once more!
Thank you WugFresh for your Toolkit.
Near the end of rooting processus for my Nexus 4 KitKat 4.
Thank you WugFresh for your Toolkit.
Near the end of rooting processus for my Nexus 4 KitKat 4.
What options did you have selected when rooting your Nexus?
When exactly does this message show up?
Do you see the rooting complete message?
I am still stuck up with this error while installing.
Make sure you typed the name correctly, and then try again.
Also if youre getting mismatch errors on the updates just manually add the program exe as an exception to your firewall.
Thanks for the help mate!
Restarted, and so now he caught the screen with the Google logo.
How long was the process?
You may need to perform a manual factory reset.
Does the mother board is the problem?
That picture looks like everything went correctly.
Then try flashing the old Jelly Bean 4.
It is saying it is unlocked, as I have rooted it from 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 did however notice a bug that I can reproduce 100% of the time.
I will check it out and fix in the next release.
Also thank you for actually describing what you did to produce the error.
Thanks again for reporting this.
I have figured out the problem for that and made the fix, will be included in v1.
Thanks again for reporting this.
I am quite new to all this.
You really got me out of a pickle.
I desided that was too much.
My phone was in great condition because it was always in a case to protect it.
The phone I just brought had some weard Rom on it Android 4.
Tried to backup a single app from the backup section on the main screen.
I will see if I can figure out what caused that.
Thank you for the info.
It set Bluestacks as the default device when the nexus was connected.
Once I shut down Bluestacks, it all worked fine.
Do you know offhand if there will be any problems with doing it this way?
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.
Added a fix in this 1.
It worked smoothly on my Nexus 7 2013 Wi Fi with Kit Kat 4.
However I got a minor bug: After rooting process, the Cast Screen option on the quick configuration menu just disappeared.
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.
But want to unroot first.
I rooted and unlocked with toolkit v1.
You must follow these steps in the exact order: 1.
Grant that app Superuser permissions, use it to reset the tamper flag if applicable to your device and also to re-lock your device.
You would need a usb connection working then.
My device is not rooted, but unlocked.
Any ideas how I can modify the directions to do this?
I rooted and then mistakenly updated to 4.
Thanks for this great tool.
I need to ask, the Nandroid backup feature, where does it store the back up?
I asked because I have no idea how much space it would use.
I have a Nexus 5 with 3.
Can you please help me.
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?
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.
It works for my Nexus 7!
I love you, this is unique work!
This is the best software, saved my data and my digital life!
Yes, I probably should fork the backup stuff into another app — those adb backup features should work for any kitkat device, same deal with the screen recording all 4.
Do I have to make a manual backup for every user?
How would this best be done?
Does nobody else have this problem?
A quick Google search is telling me that adb backup only works on the primary user.
Looks like you would need root so you could use Titanium backup pro with multiple profiles option, or just make full nandroids.
I guess multi-user is still relatively new.
Hopefully Google will improve adb backup in the future.
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.
I messed up my phone so i decided to unroot it completely back so…it works!
I tried some of the others out there but none of them can do what this tool does.
I put some jingle in your pocket in appreciation to your hard work.
Even what appears to be a small change can take hours samsung usb driver win 8 64 bit hours of blood, sweat and tears.
Yes, this program has come a long way from when I started it.
Happy to hear that you are utilizing all the features!
I personally run Win 8.
You need to explain what occurs.
I have done several Flash Stocks but the problem persists.
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.
Unlocking is a prerequisite for flashing stock.
If you have unlocked, please post a screenshot of the failed flash.
How can I change that without my tablet turning on?
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.
Or try removing the usb cable when you see that screen before pressing the Yes via the power button.
Otherwise my situation is exactly the same as the original post from ronjcar.
Just stay in bootloader mode, and use the toolkits unlock button.
Chose the option to do it manually.
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.
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 did reinstall the program but still having the same problem.
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.
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.
I had used ccleaner cuople of weeks back.
I tried uninstalling and re installing the app again!
I am trying not to ruin my phone.
Or proceed to the driver test.
Just attempt to configure your drivers, run the driver test.
Does this mean not on lock screen or the type of unlocked that wipes everything?
Create an androidbackup with neither shared nor system apps checked.
Also backup any folders on your sdcard that appear to be auto-created by games on your device.
If you want to be super safe, you could just backup your entire sdcard and then restore stuff back selectively.
You could also backup contacts however they more likely auto-synced with your gmail account.
Unlock and root your device.
Sign into your primary gmail during initial setup and let google play automatically restore your samsung usb driver win 8 64 bit />Reconfigure your system settings manually like email accounts, stock home launcher layout, etc 8.
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.
Can I use the toolkit for this?
Hopefully this will allow you to boot up.
Unfortunately, though, the phone would not boot up after that.
When I hold down the power button, it just goes back into the loop with the Google circles going in and out.
To get your device working, try doing a factory reset from stock recovery.
Have no idea how it got into that state!
Thanks for helping me get it back!
My computer is running in win 7 64 bits.
Re-installed the software and same… Reboot pc, reboot nexus 7 and still nothing.
I was running Android L on my Nexus 5 and wanted to take it back to 4.
I will be donating to you.
If I got my hands on one, I would probably try and support it for nostalgia sake.
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.
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?
I made the driver installation as simple as humanly possible.
I hope you get it resolved.
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.
When you hit the flash stock + unroot button, there is a pull down menu where you can select which build you want to flash.
Combination of, hold volume button down then insert charger, the nexus 4 will boot to fastboot mode.
The nexus 4 is on!
I was rooting Nexus 4 running on KitKat 4.
This update requires bootloader 4.
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?
The unlock script asks if you want to start in bootloader mode.
Then flash stock + unroot with softbrick bootloop mode.
I am unsure if usb debugging is enabled or not.
Does this process normally take longer, and I am just being impatient?
Also try rebooting your computer.
To answer your first question; No — erasing boot should like like 1 second.
Let me know if you get everything resolved.
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??
Some sections says that the bootloader is locked.
It should be unlocked to perform the Flash Stock + Unroot I believe.
Looks something like this: And when you say, it gets stuck on waiting for device.
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.
Had Android L Developer review installed.
Was a bit buggy and was interfering with other apps.
This made reverting back to stock 4.
Well done and thank you!
Please keep up the great work!!!
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.
You really need your bootloader to unlock to do anything.
Try issuing a factory reset first: Then try unlocking again.
Id installed Clockwork mod recovery.
Then I found your script.
Boy am I glad that I found you.
Getting back to stock was simple.
Took a few tries to get the phone locked again.
You will be seeing a donation for your hard work and simplifying the process so drastically!
Anyways, I downloaded the stock factory image from Google and attempted to flash it through the toolkit.
Thanks for this program btw, have never had any issues with it.
Eagerly waiting for the update.
Same thing happened to me.
By the way, as always, love you WugFresh!
Anyways, I downloaded the stock factory image from Google and attempted to flash it through the toolkit.
Are you out on the Nexus 5?
Anyways, I downloaded the stock factory image from Google and attempted to flash it through the toolkit.
Does the download happen really quickly?
Now I want to lock the bootloader while keeping root.
That said, if you have problems in the future, it will make it more of a hassle to deal with.
If you understand these limitations of relocking the bootloader, and still want to I am guessing for security reasons?
Thanks for the quick response.
So if you are not unlocked yet, then you must backup stuff first.
If you are running KitKat and trying to flash Lollipop — the procedure will wipe data unless you disable that in the settings menu.
Now i must come back to stock 4.
I unistalled old drivers, instaled new drivers, used Google drivers and also Universal Drivers or Pdna Drivers.
If your computer can see your device when its in bootloader, then you should have no problems flashing stock and returning to 4.
Let me know if there is a preferred way to notify you.
Or if you just use changedetection, or something.
Tried the original cable that comes with it still no luck.
Am i doing something wrong?
I had a friend root it and I have no use for it and I would like to get rid of it.
The toolkit walks you through everything.
And I installed them and it still did not work.
My original N7 soft bricked.
Thanks for the great tool man.
Its fine that your device is messed up.
Simple power on does nothing.
Maybe the device is a goner?
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.
Thanks for the help, and thanks for the amazing tool.
I just noticed this false flag as well, as I use Avast on one of my machines.
I am submitting a false flag report right now.
I can assure you, this package is safe.
The programming language its coded in is known the cause false flags.
Have also submitted a report.
Avast has been pretty quick to whitelist it in the past, hopefully this case is no different.
Thank you for reporting it.
When im fail to ota update to 4.
But the weird things happen.
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.
Have you tried rebooting your comp.
What does device manager show when you are in fastboot?
I want to bring my phone back to stock and do a hard reset.
Just chose the latest official jellybean for that gnex.
Would you please help me?
Worked like a champ and a donation of thanks was sent.
So my father has a nexus 7 2012 edition.
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.
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.
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.
You can relock afterwards if you like.
Also try factory resetting again: You really need to get this thing unlocked, so try again if needed.
When i try to unlock manually with fastboot oem unlock it fails with an unknown error.
Im convinced its a hardware issue.
I appreciate the help but i dont think we are getting this unlocked.
Definitely fits the criteria of a hardware issue.
Hopefully you can get a replacement.
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.
But i get some trouble while rooting….
It gives you a link.
I manually installed the v.
Nothing change with the new version.
It seems that everything is successful prior to rooting — drivers, and unlock.
Verizon Galaxy Nexus Android 4.
Please update toolkit soon so I can root my N7.
I want to keep using the 5.
And I want to be able to use those apps.
Please keep adding all 5.
I want to be able to backup and restore data etc.
And also for Nexus 7 2013 Wi-Fi.
So, I want to use 5.
I understood that you loathe Android m.
It was just an example.
Maybe something is wrong with the new bat file?
Kudos to wugfresh to putting in all that effort btw!
I deleted everything, reinstalled v2.
Also manually unlocked and locked.
Guess I will go to the manual flashing….
In order for the kit to proceed with the root, it needed to download Dependencies but one of the links to the mda89d.
Waiting anxiously on the update.
Hade the same problem with my nexus 6, but then I did as you said, flashed everything manually and boom it works again.
I even got it rooted.
It just hangs at the google logo.
LuckilyI still had the 2.
Just that I have trouble downloading openrecovery twrp image as the link is broken.
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.
The Nexus 5 is still great though, im still holding on to my bloated battery-burnt in-faulty home button Galaxy S2.
Install the Nexus Root Tool Kit Version 2.
Open the location where the nrt is installed.
Run the Nexus Root Tool Kit Version 2.
Run the Nexus Root Tool Kit Version 2.
Factory Data Reset the phone.
I went back to 5.
Where can I download v2.
Bootloader is way unlocked but script detects otherwise.
It does say its unlocked however so its slightly different than the people with the 2013 model.
Is there a reason why?
I recommend others do too.
I have been guilty of not supporting the developers as much as I should.
All i can find appears to be malware when searching google.
Specs: Nexus 7 2013 wifi Android 5.
More to the point, I am unable to download root kernel for this phone.
Upgraded to the latest version and there are some problems.
How do i now apply the recent november security patch that was just released?
Then I re-rooted using advanced settings with super user beta.
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?
Thanks for this awesome tool btw!
Will try suggestions and await an update to the software.
Great tool and keep up the good work.
But, I have some concerns with the latest update.
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.
Shows up in notification drawer.
Those were the ones that helped me with my 5X.
Any idea what is going on?
Tried Android 6 and 4.
I have tons of free space on the phone.
Does anyone know how to solve this?
There appears to be some problems with the Nexus 7 rooting after Marshmellow.
I just wish to update my system image.
Up a creek, trying to remain calm.
I hope folks will join me in making a donation!
Starting now and will keep grinding until its done.
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.
Power down, select recovery… Everything leads right back to the fastboot screen.
Goes impossibly fast, sticks at fastboot.
Have rolled back to 2.
The unlock status is apparently different for that device.
Testing now and will fix asap in v2.
But I get a report that my N7 is locked.
If i remember correctly, the.
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.
Hopefully this helps and thanks again!
Following logfile was created: Nexus Root Toolkit v2.
Only after rooting I got stuck in a bootloop.
My phone was not wiped or unlocked.
Log: Checking Fastboot Connectivity fastboot devices 00c96daa83e23bcc fastboot Connectivity Status: Fastboot Device Connected + Bootloader Status: Locked.
Does anyone know a quick fix for it?
Credit goes to Wug for letting me know.
I am stuck in a bootloop and it is closing and cancelling the operation.
I hope this is fixed in 2.
Thank you to the developer s for being so responsive in the comment section.
If you still need it I could upload it to Dropbox for you tomorrow and leave a link here.
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 feel like I did something wrong.
Sorry for Wall of text.
But we might need to do a complete wipe first.
The script bombs with a remote table update fail error.
If this interest anyone let me know and I share what I did.
With Xposed being updated to 6.
Then window informed my device is corrupted, cant be recognized.
Please find the bug soon and realise 2.
I can easyly start it, but the update did not work.
But i tried it on Windows 7 and 8.
WugFresh is testing it currently and should be out soonish.
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.
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.
Do you have any more suggestions?
Thank you for your help.
You can do that if you are in bootloader mode.
Sorry for the noobish questions, normally rooting is a 10 minute process for me.
I am in bootloader mode.
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.
Really sorry for all the questions man.
I did a full wipe of the phone.
After displaying that message, the phone booted, and ran, fine.
So as soon as I saw 2.
This surprised me because I thought that a true stock install would avoid that message.
Again I chose no wipe.
Should I redo the stock flash using 2.
Would that get rid of the corrupt message at least until I successfully rooted?
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.
Only way to fix it is to flash stock.
Once I restart root works but busybox will not install.
All went good till it wanted to flash system.
There was an error and now my nexus 5 can only boot the bootloader.
However, it become boot loop after use 2.
Also for my Nexus 5x root is not working.
Tool is pretty much useless at the moment.
Try it manuallylook at forum for commands.
What the fudge is with this system?!
It will be the same.
Now all files should be available.
Now How do I root!!!!???
Is there also a bug in nrt v2.
These monthly Android security updates are a pain.
Just update the masterlist and all is well.
Thanks Wug, you are magic.
Did you manage to somehow solve this?
I have the same problem with BusyBox.
Long story short, I just tried using 2.
Then rooted — again, perfect.
Thanks for the tool, Wug!
I now have a rooted Nexus 6 running R.
Always be patient after flash stock.
If you ever truly bootloop, the first troubleshooting option is a factory reset from recovery i.
One of those two will help you fix.
Either way, glad it sorted itself.
Mine is showing I have 3092.
But: the script Flash stock + unroot in NexusRootToolkit.
Can you shoot me a message in google hangouts.
I will be happy to try and figure out why you are getting that error.
It pushes recovery fine, but gets hung up on pushing the root.
Ive reverted to 3 builds including 5.
Connection is fine, chord is stock, and usb debugging is set and checked and unchecked mtp.
Now stuck at the google logo.
Has anybody got an idea?
And Wugfresh is the number one!
Rooted and installed Custom recovery.
WugFresh, you did it again!
I want to get back to completely stock and rooted if possible.
Without wiping everything again, if possible.
Yesterday, I installed K, then rooted.
I have a few odd things happening that make me wonder if they are kernel related.
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?
Beside that, a log window opens.
And the masterlist numbers are shown in that window.
This leaves me to have to flash twrp manually to get it back.
Is this supposed to happen?
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.
I rebooted the phone manually and then it was preparing the apps for android 6.
I have a nexus 5 running Android 5.
I plan to install Marshmallow on my device.
What is the procedure I must be following to install Android 6.
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.
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?
Thankou you WugFresh for all your great work.
Can I ask you guys for help?
There, in general you can not create any directory or file.
Did you get the error the same way?
When trying to unlock bootloader?
I definitely want to get this bug figured out asap.
Current have root but not fully functional without busybox.
I used System App Remover from the Play store, you need around 130mb free.
I flashed Xposed and everything seems to be fine.
Unlocked and rooted my brandnew Nexus 6p.
Looks like I just overlooked some builds.
Will update you within the hour when its supported.
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.
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.
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.
Any thoughts of what the issue can be and how to fix it.
Try flashing a different build.
If your problems persist it could be a hardware issue.
I was attempting to flash the latest marshmallow 6.
How can I help debug?
I will be updating the kit with this shortly.
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 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.
Would be appreciated if you found a work around.
Thanks for your great work!
Some have suggested even using System App Remover from the Play Store to solve this.
So updated to R and rooted again successfully.
I manually installed BusyBox just in case.
There is currently no modified boot.
It is recommended to upgrade to the latest build available first.
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.
Is any one else having issues rooting the Nexus Player using this Marshmallow image?
I have a Nexus Player myself, so I will see if I can reproduce and try to figure out why.
Will this issue be fixed in the next release?
Maybe it got lost somewhere.
I will put the rom and gapps on my smartphone, will it work?
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.
Next to work on the nexus 6 root….
When do you plan to support those new builds?
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.
Never had this issues before.
Never had this issue before, but this is the first time I am rooting since Marshmallow came out.
I changed the partition 2 months ago because that message and blew up the problem.
Just wanted to bring it to your attention.
Did something change in Marshmallow that I am not aware of.
I have a Nexus 6P and am rooting and upgrading the Android build.
Thank you for all of your hard, dedicated work.
I want to use this to root my nexus 6p.
But I want to keep android pay.
Is there a way I can unlock the bootloader with this and then install twrp and then flash supersu manually with the beta.
I noticed this in Android Police artical.
Attempting to use it with the Nexus 6P fails with a message that it is an unknown instruction.
Google had Huawei replace the oem command in the Nexus 6P bootloader with the new flashing command.
Also how do we fix this.
Marshmallow took at least a couple of weeks and the last minor update took a week.
Due to it i am unable to upgrade to latest build.
Trying to root nexus 7v2.
Goes fine until temporarily opens twrp.
There are no zip files in sdcard to flash.
Any ideas on how to get it to work.
When it boots into twrp every folder is empty.
I would appreciate some advice how to problem solve this issue.
I got around the issue by manually booting Custom Recovery in the advanced Utilities.
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.
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.
Busybox install issue with the playstore app is a known problem at this point — still investigating the best fix.
I try rooting my Nexus 5 having installed the 6.
Edit : After a retry, it worked nicely.
About 2 weeks ago, the latest update left us in a bootloop when rooting.
Can you please fix it?
I know the fix — I have just been super busy, will get fixed this weekened.
Any chance you had time to get this fixed yet?
I have the same problem with my Google Samsung Nexus S 4G running 4.
Who died and made you Moderator?
Yes, yes he will he has done for the last however long!
Lets keep this to troubleshooting and what not and not just a means to bug Wugs.
Having issues with Nexus 5X and AdAway.
I also have a Nexus 9 that works fine with 6.
Worked fine on my old Nexus 5 too.
The only issue is on the 5X.
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!
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?
Some apps look for some minimum amount of space left in that partition in order to execute.
Nothing seems to be working.
I only want root to block ads.
I have used it previously to root and unlock the same phone.
Unfortunately, i am getting the same error reported by other users.
I am using Samsung Galaxy Nexus Verizon sch-i515.
I just noticed that 5.
Why, as you might know, there are many visually impaired Android users who like to root their Nexus devices independently without asking a sighted assistance for help.
This was possible in Android 5.
Note that I am not talking about bootloader unlocking, since I already did that and did not relock my bootloader.
I am talking about the stage that we need to add the zip packages and install them.
So again, any chance of having an automated root like before?
Franko kernel release 77 for Android 6.
My question is, will rooting again with this toolkit wipe all my data?
Now kit is using 2.
I will try on the 5X and 9 this afternoon and report back.
What if you factory reset, flash stock, and unroot first?
AdAway successfully wrote the hosts file, no more ads!
Thank you so much Wug, donation incoming!!
I had the same problems as Ted before.
I am running Android 6.
I have been reading through below and it seems that I can now use the tool to move to the new Android 6.
However, I am a bit confused on the steps.
Would it be possible to spell it out?
Should I Flash Stock and Unroot first?
Keep up the great work.
Make sure check no-wipe mode if u want to keep your files.
However, I cant root after updated to 6.
I soft bricked my nexus 5……now by the help of this toolkit….
So I reflashed it and saved all the zip files to the sd card.
I told it not to, and everything thing is working perfectly now.
Only issue that I have now is that the Home button of the Nexus Player remote does not bring me back the the Home Screen Leanback Launcher.
I re-flashed the image several times with and without root, but still the Home button does not function.
Both these Home keys worked with previous versions of Marshmallow.
I apologize for the off topic question, but my understanding is that you also have a Nexus Player.
Are you running Android 6.
Both of these Home keys worked fine before flashing 6.
The problem now is when editing the build.
I tried two root file managers, root explorer and fx manager.
Really the phone is not rooted properly until you can edit system files.
Go and delete some system packages like asian input methods etc.
Rooting with su ver 2.
I want to port youre toollbox over to linux so you can make it work for both platforms.
The all in one Nexus toolkit!
All I got is systemless root.
On the other hand, it seems that Chainfire stopped making Nexus boot images for traditional rooting.
Would you patch boot images for Nexus devices?
I hope there are people who still prefer the traditional nonsystemless root, just like me.
I will buy you a beer again.
Please reboot and try again.
Tried to root afterwards and got the never ending marshmallow logo loop similar to some of the comment bellow mentioned.
I was able to recover from that by flashing back to 6.
Any suggestion on how I can root my device.
Happy holidays and thank you for the wonderful job you are doing.
It worked fine before windows 10.
I can download it manually by fallowing the link in the pop up, but just want to know if there is anything I can do to solve my problem.
Any help would be much appreciated.
After that Super User was installed in my tab.
Everything was fine, but last week I unfortunately tried to update the android version to 4.
I tried almost everything as I can surfing internet.
Now please help me to get back my tab.
And thanks a lot in advance.
I am trying to Flash Stock + Unroot my 2012 Nexus 7.
What might I try next?
Previously before system less root it was xbin.
I respect ya very much!
Keep up the great work!
I think Google Wallet can do the trick.
I currently have a Nexus 5 which is rooted and running android version 4.
Much love and thank you for your help!
I currently have a Nexus 5 which is rooted and running android version 4.
Much love and thank you for your help!
I think that maybe automating the process or not using a modified boot image might have caused it to miss an important step on the N9.
On a positive note, I no longer see the yellow warning message on boot about not being able to check for corruption.
The process worked without error.
However, I do still see the yellow warning about not being able to check for corruption.
Not a big deal though.
But oddly enough as of this morning on 2.
I rooted the N9 again with 2.
Same as my 2nd post above, it worked that way.
ReadyToFlash folder on my N9.
It has always worked for my N5, N9, and N5X until now.
Does anyone else have this problem?
Once I flash root, my phone booted up.
Upon another reboot, I got stuck at the Google logo and had to flash again and wipe my phone.
It never does finish booting.
Left it for 45 minutes, then powered off and tried to boot again and get the same thing, shows the boot animation and goes no further.
I believe you need to update your toolkit to take this into account.
Can i tell me why?
Keep up the great work man.
By using Xender u can send all the apps to another phone and than take them back after root from that phone.
I would like to suggest a new feature.
Thanks for fixing the getvar unlocked problem.
Now my Nexus 7 2013 WiFi was able to flash stock, and afterwards successfully re-rooted.
The errors your received indicate a bad connection.
Please, can you tell me : does it work on a Nexus 4 running 5.
How would I go about updating without losing root?
Android Pay fails at checkout.
Reverted AdAway to original hosts, removed AdAway and cflumen.
I then used Flash Stock + Unroot with NoWipe mode and everything appears to run successfully.
And can I get back to clean booting N6 with working Android Pay without doing a full wipe?
Device is a nexus 5.
When I double click the exe it does not open.
I tried right clicking and to run as administrator but that did not open it either.
I double clicked and nothing happened.
In Device Manager there is no yellow exclamation point, so what do I do?
You can even try reinstalling drivers.
I had this issue, went to step 3, updated and that fixed it like the other users below.
Unlock worked fine, all drivers were successfully installed.
Problem is when i try to root it.
Any help or idea would be great.
I now have a working device thats currently upgrading and ticking along very nicely.
I get the screen with your phone is running corrupt software press power to pause boot and that is as far as it gets.
After a new bootup, it appears to be normal but without encryption.
Can someone help me please to fix this?
Any idea as to what might be causing this issue?
I pay for my lunch using Android Pay.
Open that folder and do these two things.
On the popup, tap properties.
Change that to 751, and tap Apply.
That should be you rooted, with Android Pay working.
Did I do something wrong?
I pressed FlashStock + Unroot and everything worked fine.
It says the xu binary is missing.
Shall I redo the update or will it not un-root anymore at all due to the new android?
Each attempt now to re-root the device results in a boot-loop.
Is there a solution to this problem?
Manually reboot Nexus to bootloader mode, then try to do the procedure.
All works and device is rooted correctly.
Then everything worked fine :.
Since I was less concerned to find exactly what was going wrong than just to get things working, I made a bunch of changes, and something in all that worked.
I did hit upon the same trick as did you smuggling twrp-3.
Be sure to rename it to twrp-2.
Then do a root + customer recovery.
When I try to update to 6.
Ive done it many times over the past couple of years on n7 2012 3g devices.
However, on both rooting failed.
No matter what I did I could not fix this.
In the end I used Advanced Utilities… Custom Recovery.
Got root successfully doing that on both devices.
Your goal was to make this entire process as smooth and simple as possible…….
Download it yourself from the main factory image site.
I did it yesterday on my Nexus 6, using no-wipe mode.
Did you just say that you managed it to have working root with working Android Pay?
Typically devs will wait until official release before working on a root solution — but I may be able to support new preview builds in some capacity like flashing it, etc.
I will try to be more vigilant about updating the masterlists quicker.
Honestly not sure how to proceed.
Honestly not sure how to proceed.
It would hang on the boot screen until I force rebooted it.
I had to flash my phone back to stock, enable encryption, encrypt phone.
Prior I was rooting phone, then trying to encrypt it would just hang for 10 hours.
Hope the info helps others.
Root check says that the phone is not properly rooted.
Had to unroot it and that feature still worked for me in this program.
Running the latest version of Android 6.
I started of from 6.
For me it fails when trying to unlock the bootloader.
This program is a lifesaver and has saved my bricked phone like 5 times.
I feel like a hacker but you do all the work and I just click a button.
This toolkit is so awesome.
When it will be updated then you will see a message saying the same.
After that your build will get listed in the tool kit.
Then you can update your Nexus 5X.
As of the time of writing this post, the master list has not been updated yet.
The toolkit goes through the motions, but at the end of it all, nothing works.
I believe it is just a software malfunction and I think a factory reset will fix it.
Is there a possibility to backup my data at least my sms?
Is this because I am running 6.
Such an awesome programme, thank you!
It said it was successful, but I just get a forever-stuck white Google logo.
You provided free software that many of us could not use our devices without.
You are awesome and very much appreciated!
Was sitting on the donate button if Pixel C support arrived, too.
With that said, I hope the dude is ok.
These past few months have just been incredibly busy despite my best efforts to set aside dev time.
I forced myself to sit down and really grind it out bender style, and now 2.
I wanted to get it out asap, so I am waiting to finalize pixcel C support for the next release — which I will tackle this upcoming weekend.
I spent a great deal of time automating more things on my end, so I should be much faster with future updates.
Apologies, regardless that I made it literally hours before 2.
Looking forward to continuing to update this, including new features and extended device support.
I just got swamped these past few months.
Not sure if posting this in right place.
It acted as though I hit confirm though and continued forward and thankfully successfully flashed anyways.
I testing it out when flashing some other items and confirmed the repro steps.
It is now fixed in my private dev build, will be fixed publicly in v2.
Or will this not be done til the full N comes out for everyone?
Within the next few days.
So far all of my testing has been successful.
No matter what I do, the root process get interrupted with the same notification.
The process goes through un hindered until I get.
As a quick fix — in the flashstock.
Does anyone know how I will be able to reinstall the os as I think it wont have any os on it?
Will I be able to use the toolkit for such thing?
Feel free to reach out to me if you have any problems.
How can I fix this?
WugFresh After that I tried the option Flash Stock+Unroot and I succeeded to reach the set up, then it ask me to connect with wifi.
Someone wrote that it can be done by connect to free wifi.
Do you how to through this?
Pls help just like you always have.
It does a quick load-animation, but then it goes away and nothing ever happens.
I am running Windows Vista—yeah, I know…stop it!.
Any help would be greatly appreciated!
Its not done via touch screen.
Not rushing just having issues with my phone not being updated for a few months.
Would it be safe to select one of the other builds or am I missing something?
As i understand it should modify the bootloader only, but not touch system.?
The troubleshooting says to go into Device Manager and find yellow exclamation point.
There is not an unconfigured device listed.
I reran the test and it came back the same way.
Line 18980 File C:Program Files x86 WugFresh Developmentnexus Root ToolkitNexusRootToolkit.
It went thru the motion of rooting as if it was successful but it was not when I checked.
I tried rooting again after a few minutes and everything was fine, it rooted properly.
I thought that this was simply a bug with the toolkit and wugfresh needed to release a patch for it.
My phone rebooted and its not stucked at the Google animation screen.
I waited for like 30 minutes because and its stucked.
It seems to be working on all the other devices, but something is going on with 6P.
I setup the Android N 3 beta last week.
No worries — the toolkit worked fine — I did the no-wipe rooting — that went fine also.
Tonight I decided to get the Android N 4 beta and get it going.
Then decided to go and again re-root it and it says something about encrypted device detected — must wipe all data to root blah, blah — because — it said — due to Android N…….
I did it though because I thought that for sure it would double check and ask if I was sure I wanted to wipe all — it did not — I know, I know — backup blah blah.
But really wugfresh:disqus why did it and actually why does it have to wipe to get root now?
I am confused as to how I will get root.
I decided to go back to marshmallow and rooted again.
The only problem with going back that far is that it appears that Google will not remember your profile to reinstall all of your apps, so mine asked to install the backup profile from my nexus 7.
Did they work with Android N Preview 4?
I have factory reset my tablet and re-flashed the factory image but the problem still persists.
Can someone please help me fix this?
When it rebooted after flashing the latest update it said there was a problem with the encryption and I had to do a factory reset.
It worked fine with my Nexus 6P with the June Marshmallow update.
You ought to put a warning for the sideload function that it It will cause a factory Reset.
All else aside I do appreciate the program!
Repeated every step one more time just to make sure, same result.
Nexus 6 users beware, 2.
Thanks for the great work!
Never has any problems before.
Then tried to fall back to latest M build, also with no forced encryption, same issue.
Finally flashed preview 4 again and allowed encryption, went off fine.
Or is that just to big of a jump.
Or is that just to big of a jump.
Would it be best do do each one in turn?
I would really rather not do a clean flash.
Worse case scenario is that you have to revert back.
I personally have had success with bigger jumps.
Than would be 6 updates.
Thank you for a great program and you advice!
I went from angler-mmb29m December 2015 release to the angler-mtc19x July 2016 release without do any of the other releases.
That made it a total of 7 updates.
Everything went just fine, thank you again for your assistance.
Is there any way to find these files?
Thank you for suggestion, I slack when it comes to Web Dev.
Is there any way I can get the backup of my data?
If so, using the buttons, boot it up to the bootloader and boot into recovery.
When I unenrolled my device and reinstalled the previous version I am not able to get past the boot animation…as if stuckin bootloop.
So when I am using fastboot for unlocking I am getting an error message that the device is locked.
How can I unlock my device now?
Followed all the prompts, and tried the fixes I found in the forums, to no avail.
Google has not, thus far, been fruitful.
Then you manually update but have it search your computer for a driver.
I ran into the same problem.
No option for that when using 2.
To continue, sign in with a Google Account that was previously synced on this device.
I am not knowledgeable in software coding etc, just a guy trying to get his Nexus 7 Wi-fi to work properly again.
Hoping this will be resolved with next update?
Nexus Root toolkit always send an error message : adb.
I wish N was for Nutella, Nougat sounds so weird.
I sent you some PayPal motivation for v 2.
Under the root button there is a check mark to also install custom recovery.
It will take care of both.
The official update for Android 7.
Great job with the software, thanks!
Root support will be extended as soon as possible.
Waiting for google to release the factory images to start working on it.
Will it work to root my Nexus 5X successfully?
If you were to replace the adb and fastboot with the old ones linked in that thread it would work.
I will integrate these old binaries into v2.
Thanks again for the report.
I will see if I can add in some better handling of that scenario, so that it just auto force-kills the hanged operation and retries it.
You will also have to wait for me to extend official support for those new 7.
I will do so asap — just waiting for google to release the factory images so I can get started working on it.
Strangely google decided to name the last preview build version 7.
You are correct, the latest official 7.
Root support will be extended as soon as possible.
Waiting for google to release the factory images to start working on it.
Since installing 90G have been unable to root and now getting same error for sideloading 90M.
When they release, I will start working on adding it.
When I received the next security update I lost root but kept the unlocked tethering.
Now I updated to Android N which I figure would erase the the tethering.
Well I guess I was wrong because I can still tether and receive updates with no problem on my 6p.
It is good to hear that this should not be the case.
What carrier are you on?
At this time google has only released factory images for pixel c, nexus player and nexus 9 wifi.
I just saw the build number on the screen shot and missed lookin at the model number.
Actually Android N not support Xposed.
I need uninstall Xposed from recovery with uninstall before the update to Android N.
Should I reflash the factory image or is this a change in Android 7.

Samsung Galaxy S1 S2 S3 S4 S5 USB Drivers Download for Windows XP Vista 7 8 8.1 10 [TUT]

Unlocking, rooting, relocking and unrooting simplified!
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.
Check out the updated for a more comprehensive breakdown of the feature set and changes in this release.
Help and support is greatly appreciated.
I will say tho, i trashed my first N7 v2 2013 wifi tablet the first round after 4.
Now 2nd round new N7 v2.
Only seen one other post about this problem, and answer was corrupt,incomplete download.
Can you msg me in google chat.
I pulled out old back-up comp.
It never moves beyond that point.
Any idea what the problem is?
The toolkit can flash and root it, but no full automation of other procedures yet.
Lawreys problem, but in my case im using 32bit w7, and i already have downloaded the ktu84l factory file..
If downloading manually is the answer could someone please send me a link and a clue where to put the files!
Any ideas on how to help?
Did you ever resolve this?
Make sure you select the right Neuxs7 device in the toolkit.
I waited a half an hour after that press any key and exited.
However, no matter which of the three download links I try I get a 72.
Now I can get around to backing up my phone so I can update CyanogenMod!
I will look into setting up doge as well.
I will let you know.
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.
If an android device ever freezes on you, just force powerdown with the power button.
Unlock is required to root.
Unlocking wipes, so backup first.
The driver solutions are much simpler now.
Just go with solution 1.
Thank you for bringing this to my attention.
That said, it has worked on this page in the past.
Swapped out the androidfilehost direct download link in favor of Major Geeks as the primary link.
Thanks for developing your toolkit.
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.
The only fix is to flash stock and start over.
I have previously successfully unlocked and rooted my Nexus4 with your toolkit.
But is it still unlocked, can I skip unlocking this time?
Will I loose app data etc.
And keep the project going!
What kind of back up.
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!
Thanks a lot for a possible input and thank you once more!
Thank you WugFresh for your Toolkit.
Near the end of rooting processus for my Nexus 4 KitKat 4.
Thank you WugFresh for your Toolkit.
Near the end of rooting processus for my Nexus 4 KitKat 4.
What options did you have selected when rooting your Nexus?
When exactly does this message show up?
Do you see the rooting complete message?
I am still stuck up with this error while installing.
Make sure you typed the name correctly, and then try again.
Also if youre getting mismatch errors on the updates just manually add the program exe as an exception to your firewall.
Thanks for the help mate!
Restarted, and so now he caught the screen with the Google logo.
How long was the process?
You may need to perform a manual factory reset.
Does the mother board is the problem?
That picture looks like everything went correctly.
Then try flashing the old Jelly Bean 4.
It is saying it is unlocked, as I have rooted it from 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 did however notice a bug that I can reproduce 100% of the time.
I will check it out and fix in the next release.
Also thank you for actually describing what you did to produce the error.
Thanks again for reporting this.
I have figured out the problem for that and made the fix, will be included in v1.
Thanks again for reporting this.
I am quite new to all this..
You really got me out of a pickle.
I desided that was too much.
My phone was in great condition because it was always in a case to protect it.
The phone I just brought had some weard Rom on it Android 4.
Tried to backup a single app from the backup section on the main screen.
I will see if I can figure out what caused that.
Thank you for the info.
It set Bluestacks as the default device when the nexus was connected.
Once I shut down Bluestacks, it all worked fine.
Do you know offhand if there will be any problems with doing it this way?
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.
Added a fix in this 1.
It worked smoothly on my Nexus 7 2013 Wi Fi with Kit Kat 4.
However I got a minor bug: After rooting process, the Cast Screen option on the quick configuration menu just disappeared.
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.
But want to unroot first.
I rooted and unlocked with toolkit v1.
You must follow these steps in the exact order: 1.
Grant that app Superuser permissions, use it to reset the tamper flag if applicable to your device and also to re-lock your device.
Now once you are certain that your are relocked, open Busybox if you have it , and hit Uninstall 5.
You would need a usb connection working then.
My device is not rooted, but unlocked.
Any ideas how I can modify the directions to do this?
I rooted and then mistakenly updated to 4.
Thanks for this great tool.
I need to ask, the Nandroid backup feature, where does it store the back up?
I asked because I have no idea how much space it would use.
I have a Nexus 5 with 3.
Can you please help me.
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?
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.
It works for my Nexus 7!
I love you, this is unique work!
This is the best software, saved my data and my digital life!
Yes, I probably should fork the backup stuff into another app — those adb backup features should work for any kitkat device, same deal with the screen recording all 4.
Do I have to make a manual backup for every user?
How would this best be done?
Does nobody else have this problem?
A quick Google search is telling me that adb backup only works on the primary user.
Looks like you would need root so you could use Titanium backup pro with multiple profiles option, or just make full nandroids.
I guess multi-user is still relatively new.
Hopefully Google will improve adb backup in the future.
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.
I messed up my phone so i decided to unroot it completely back so…it works!
I tried some of the others out there but none of them can do what this tool does.
I put some jingle in your pocket in appreciation to your hard work.
Even what appears to be a small change can take hours and hours of blood, sweat and tears.
Yes, this program has come a long way from when I started it.
Happy to hear that you are utilizing all the features!
I personally run Win 8.
You need to explain what occurs.
I have done several Flash Stocks but the problem persists.
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.
Unlocking is a prerequisite for flashing stock.
If you have unlocked, please post a screenshot of the failed flash.
How can I change that without my tablet turning on?
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.
Or try removing the usb cable when you see that screen before pressing the Yes via the power button.
Otherwise my situation is exactly the same as the original post from ronjcar.
Just stay in bootloader mode, and use the toolkits unlock button.
Chose the option to do it manually.
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.
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 did reinstall the program but still having the same problem.
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.
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.
I had used ccleaner cuople of weeks back.
I tried uninstalling and re installing the app again!
I am trying not to ruin my phone.
Or proceed to the driver test.
Just attempt to configure your drivers, run the driver test..
Does this mean not on lock screen or the type of unlocked that wipes everything?
Create an androidbackup with neither shared nor system apps checked.
Also backup any folders on your sdcard that appear to be auto-created by games on your device.
If you want to be super safe, you could just backup your entire sdcard and then restore stuff back selectively.
You could also backup contacts however they more likely auto-synced with your gmail account.
Unlock and root your device.
Sign into your primary gmail during initial setup and let google play automatically restore your apps.
Reconfigure your system settings manually like email accounts, stock home launcher layout, etc 8.
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.
Can I use the toolkit for this?
Hopefully this will allow you to boot up.
Unfortunately, though, the phone would not boot up after that.
When I hold down the power button, it just goes back into the loop with the Google circles going in and out.
To get your device working, try doing a factory reset from stock recovery.
Have no idea how it got into that state!
Thanks for helping me get it back!
My computer is running in win 7 64 bits.
Re-installed the software and same… Reboot pc, reboot nexus 7 and still nothing.
I was running Android L on my Nexus 5 and wanted to take it back to 4.
I will be donating to you.
If I got my hands on one, I would probably try and support it for nostalgia sake.
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.
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?
I made the driver installation as simple as humanly possible.
I hope you get it resolved.
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.
When you hit the flash stock + unroot button, there is a pull down menu where you can select which build you want to flash.
Combination of, hold volume button down then insert charger, the nexus 4 will boot to fastboot mode.
The nexus 4 is on!
I was rooting Nexus 4 running on KitKat 4.
This update requires bootloader 4.
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?
The unlock script asks if you want to start in bootloader mode.
Then flash stock + unroot with softbrick bootloop mode.
I am unsure if usb debugging is enabled or not.
Does this process normally take longer, and I am just being impatient?
Also try rebooting your computer.
To answer your first question; No — erasing boot should like like 1 second.
Let me know if you get everything resolved.
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??
Some sections says that the bootloader is locked.
It should be unlocked to perform the Flash Stock + Unroot I believe.
Looks something like this: And when you say, it gets stuck on waiting for device..
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.
Had Android L Developer review installed.
Was a bit buggy and was interfering with other apps.
This made reverting back to stock 4.
Well done and thank you!
Please keep up the great work!!!
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.
You really need your bootloader to unlock to do anything.
Try issuing a factory reset first: Then try unlocking again.
Id installed Clockwork mod recovery.
Then I found your script.
Boy am I glad that I found you.
Getting back to stock was simple.
Took a few tries to get the phone locked again.
You will be seeing a donation for your hard work and simplifying the process so drastically!
Anyways, I downloaded the stock factory image from Google and attempted to flash it through the toolkit..
Thanks for this program btw, have never had any issues with it.
Eagerly waiting for the update.
Same thing happened to me.
By the way, as always, love you WugFresh!
Anyways, I downloaded the stock factory image from Google and attempted to flash it through the toolkit..
Are you out on the Nexus 5?
Anyways, I downloaded the stock factory image from Google and attempted to flash it through the toolkit..
Does the download happen really quickly?
Now I want to lock the bootloader while keeping root.
That said, if you have problems in the future, it will make it more of a hassle to deal with.
If you understand these limitations of relocking the bootloader, and still want to I am guessing for security reasons?
Thanks for the quick response.
So if you are not unlocked yet, then you must backup stuff first.
If you are running KitKat and trying to flash Lollipop — the procedure will wipe data unless you disable that in the settings menu..
Now i must come back to stock 4.
I unistalled old drivers, instaled new drivers, used Google drivers and also Universal Drivers or Pdna Drivers..
If your computer can see your device when its in bootloader, then you should have no problems flashing stock and returning to 4.
Let me know if there is a preferred way to notify you.
Or if you just use changedetection, or something.
Tried the original cable that comes with it still no luck.
Am i doing something wrong?
I had a friend root it and I have no use for it and I would like to get rid of it.
The toolkit walks you through everything.
And I installed them and it still did not work.
My original N7 soft bricked.
Thanks for the great tool man.
Its fine that your device is messed up..
Simple power on does nothing.
Maybe the device is a goner?
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.
Thanks for the help, and thanks for the amazing tool.
I just noticed this false flag as well, as I use Avast on one of my machines.
I am submitting a false flag report right now.
I can assure you, this package is safe.
The programming language its coded in is known the cause false flags.
Have also submitted a report.
Avast has been pretty quick to whitelist it in the past, hopefully this case is no different.
Thank you for reporting it.
When im fail to ota update to 4.
But the weird things happen.
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.
Have you tried rebooting your comp.
What does device manager show when you are in fastboot?
I want to bring my phone back to stock and do a hard reset.
Just chose the latest official jellybean for that gnex.
Would you please help me?
Worked like a champ and a donation of thanks was sent.
So my father has a nexus 7 2012 edition.
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.
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.
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.
You can relock afterwards if you like.
Also try factory resetting again: You really need to get this thing unlocked, so try again if needed.
When i try to unlock manually with fastboot oem unlock it fails with an unknown error.
Im convinced its a hardware issue.
I appreciate the help but i dont think we are getting this unlocked.
Definitely fits the criteria of a hardware issue.
Hopefully you can get a replacement.
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.
But i get some trouble while rooting….
It gives you a link.
I manually installed the v.
Nothing change with the new version.
It seems that everything is successful prior to rooting — drivers, and unlock.
Verizon Galaxy Nexus Android 4.
Please update toolkit soon so I can root my N7.
I want to keep using the 5.
And I want to be able to use those apps.
Please keep adding all 5.
I want to be able to backup and restore data etc.
And also for Nexus 7 2013 Wi-Fi.
So, I want to use 5.
I understood that you loathe Android m.
It was just an example.
Maybe something is wrong with the new bat file?
Kudos to wugfresh to putting in all that effort btw!
I deleted everything, reinstalled v2.
Also manually unlocked and locked.
Guess I will go to the manual flashing….
In order for the kit to proceed with the root, it needed to download Dependencies but one of the links to the mda89d.
Waiting anxiously on the update.
Hade the same problem with my nexus 6, but then I did as you said, flashed everything manually and boom it works again.
I even got it rooted.
It just hangs at the google logo.
Luckily , I still had the 2.
Just that I have trouble downloading openrecovery twrp image as the link is broken.
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.
The Nexus 5 is still great though, im still holding on to my bloated battery-burnt in-faulty home button Galaxy S2.
Install the Nexus Root Tool Kit Version 2.
Open the location where the nrt is installed.
Run the Nexus Root Tool Kit Version 2.
Run the Nexus Root Tool Kit Version 2.
Factory Data Reset the phone.
I went back to 5.
Where can I download v2.
Bootloader is way unlocked but script detects otherwise.
It does say its unlocked however so its slightly different than the people with the 2013 model.
Is there a reason why?
I recommend others do too.
I have been guilty of not supporting the developers as much as I should.
All i can find appears to be malware when searching google.
Specs: Nexus 7 2013 wifi Android 5.
More to the point, I am unable to download root kernel for this phone.
Upgraded to the latest version and there are some problems.
How do i now apply the recent november security patch that was just released?
Then I re-rooted using advanced settings with super user beta.
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?
Thanks for this awesome tool btw!
Will try suggestions and await an update to the software.
Great tool and keep up the good work..
But, I have some concerns with the latest update.
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.
Shows up in notification drawer.
Those were the ones that helped me with my 5X.
Any idea what is going on?
Tried Android 6 and 4.
I have tons of free space on the phone.
Does anyone know how to solve this?
There appears to be some problems with the Nexus 7 rooting after Marshmellow.
I just wish to update my system image.
Up a creek, trying to remain calm.
I hope folks will join me in making a donation!
Starting now and will keep grinding until its done.
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.
Power down, select recovery… Everything leads right back to the fastboot screen.
Goes impossibly fast, sticks at fastboot.
Have rolled back to 2.
The unlock status is apparently different for that device.
Testing now and will fix asap in v2.
But I get a report that my N7 is locked.
If i remember correctly, the.
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.
Hopefully this helps and thanks again!
Following logfile was created: Nexus Root Toolkit v2.
Only after rooting I got stuck in a bootloop.
My phone was not wiped or unlocked.
Log: Checking Fastboot Connectivity fastboot devices 00c96daa83e23bcc fastboot Connectivity Status: Fastboot Device Connected + Bootloader Status: Locked.
Does anyone know a quick fix for it?
Credit goes to Wug for letting me know.
I am stuck in a bootloop and it is closing and cancelling the operation.
I hope this is fixed in 2.
Thank you to the developer s for being so responsive in the comment section.
If you still need it I could upload it to Dropbox for you tomorrow and leave a link here.
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 feel like I did something wrong.
Sorry for Wall of text.
But we might need to do a complete wipe first.
The script bombs with a remote table update fail error.
If this interest anyone let me know and I share what I did.
With Xposed being updated to 6.
Then window informed my device is corrupted, cant be recognized.
Please find the bug soon and realise 2.
I can easyly start it, but the update did not work.
But i tried it on Windows 7 and 8.
WugFresh is testing it currently and should be out soonish.
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.
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.
Do you have any more suggestions?
Thank you for your help.
You can do that if you are in bootloader mode.
Sorry for the noobish questions, normally rooting is a 10 minute process for me.
I am in bootloader mode.
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.
Really sorry for all the questions man.
I did a full wipe of the phone.
After displaying that message, the phone booted, and ran, fine.
So as soon as I saw 2.
This surprised me because I thought that a true stock install would avoid that message.
Again I chose no wipe.
Should I redo the stock flash using 2.
Would that get rid of the corrupt message at least until I successfully rooted?
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.
Only way to fix it is to flash stock.
Once I restart root works but busybox will not install.
All went good till it wanted to flash system.
There was an error and now my nexus 5 can only boot the bootloader.
However, it become boot loop after use 2.
Also for my Nexus 5x root is not working.
Tool is pretty much useless at the moment.
Try it manually , look at forum for commands.
What the fudge is with this system?!
It will be the same.
Now all files should be available.
Now How do I root!!!!???
Is there also a bug in nrt v2.
These monthly Android security updates are a pain.
Just update the masterlist and all is well.
Thanks Wug, you are magic.
Did you manage to somehow solve this?
I have the same problem with BusyBox.
Long story short, I just tried using 2.
Then rooted — again, perfect.
Thanks for the tool, Wug!
I now have a rooted Nexus 6 running R.
Always be patient after flash stock.
If you ever truly bootloop, the first troubleshooting option is a factory reset from recovery i.
One of those two will help you fix.
Either way, glad it sorted itself.
Mine is showing I have 3092.
But: the script Flash stock + unroot in NexusRootToolkit.
Can you shoot me a message in google hangouts.
I will be happy to try and figure out why you are getting that error.
It pushes recovery fine, but gets hung up on pushing the root.
Ive reverted to 3 builds including 5.
Connection is fine, chord is stock, and usb debugging is set and checked and unchecked mtp.
Now stuck at the google logo.
Has anybody got an idea?
And Wugfresh is the number one!
Rooted and installed Custom recovery.
WugFresh, you did it again!
I want to get back to completely stock and rooted if possible.
Without wiping everything again, if possible.
Yesterday, I installed K, then rooted.
I have a few odd things happening that make me wonder if they are kernel related.
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?
Beside that, a log window opens.
And the masterlist numbers are shown in that window.
This leaves me to have to flash twrp manually to get it back.
Is this supposed to happen?
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.
I rebooted the phone manually and then it was preparing the apps for android 6.
I have a nexus 5 running Android 5.
I plan to install Marshmallow on my device.
What is the procedure I must be following to install Android 6.
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.
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?
Thankou you WugFresh for all your great work.
Can I ask you guys for help?
There, in general you can not create any directory or file.
Did you get the error the same way?
When trying to unlock bootloader?
I definitely want to get this bug figured out asap.
Current have root but not fully functional without busybox.
I used System App Remover from the Play store, you need around 130mb free.
I flashed Xposed and everything seems to be fine.
Unlocked and rooted my brandnew Nexus 6p.
Looks like I just overlooked some builds.
Will update you within the hour when its supported.
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.
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.
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.
Any thoughts of what the issue can be and how to fix it.
Try flashing a different build.
If your problems persist it could be a hardware issue.
I was attempting to flash the latest marshmallow 6.
How can I help debug?
I will be updating the kit with this shortly.
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 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.
Would be appreciated if you found a work around.
Thanks for your great work!
Some have suggested even using System App Remover from the Play Store to solve this.
So updated to R and rooted again successfully.
I manually installed BusyBox just in case.
There is currently no modified boot.
It is recommended to upgrade to the latest build available first.
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.
Is any one else having issues rooting the Nexus Player using this Marshmallow image?
I have a Nexus Player myself, so I will see if I can reproduce and try to figure out why.
Will this issue be fixed in the next release?
Maybe it got lost somewhere.
I will put the rom and gapps on my smartphone, will it work?
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.
Next to work on the nexus 6 root….
When do you plan to support those new builds?
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.
Never had this issues before.
Never had this issue before, but this is the first time I am rooting since Marshmallow came out.
I changed the partition 2 months ago because that message and blew up the problem.
Just wanted to bring it to your attention.
Did something change in Marshmallow that I am not aware of.
I have a Nexus 6P and am rooting and upgrading the Android build.
Thank you for all of your hard, dedicated work.
I want to use this to root my nexus 6p.
But I want to keep android pay.
Is there a way I can unlock the bootloader with this and then install twrp and then flash supersu manually with the beta.
I noticed this in Android Police artical..
Attempting to use it with the Nexus 6P fails with a message that it is an unknown instruction.
Google had Huawei replace the oem command in the Nexus 6P bootloader with the new flashing command.
Also how do we fix this.
Marshmallow took at least a couple of weeks and the last minor update took a week.
Due to it i am unable to upgrade to latest build.
Trying to root nexus 7v2.
Goes fine until temporarily opens twrp.
There are no zip files in sdcard to flash.
Any ideas on how to get it to work.
When it boots into twrp every folder is empty.
I would appreciate some advice how to problem solve this issue.
I got around the issue by manually booting Custom Recovery in the advanced Utilities.
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..
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.
Busybox install issue with the playstore app is a known problem at this point — still investigating the best fix.
I try rooting my Nexus 5 having installed the 6.
Edit : After a retry, it worked nicely.
About 2 weeks ago, the latest update left us in a bootloop when rooting.
Can you please fix it?
I know the fix — I have just been super busy, will get fixed this weekened.
Any chance you had time to get this fixed yet?
I have the same problem with my Google Samsung Nexus S 4G running 4.
Who died and made you Moderator?
Yes, yes he will he has done for the last however long!
Lets keep this to troubleshooting and what not and not just a means to bug Wugs.
Having issues with Nexus 5X and AdAway.
I also have a Nexus 9 that works fine with 6.
Worked fine on my old Nexus 5 too.
The only issue is on the 5X.
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!
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?
Some apps look for some minimum amount of space left in that partition in order to execute.
Nothing seems to be working.
I only want root to block ads.
I have used it previously to root and unlock the same phone.
Unfortunately, i am getting the same error reported by other users.
I am using Samsung Galaxy Nexus Verizon sch-i515.
I just noticed that 5.
Why, as you might know, there are many visually impaired Android users who like to root their Nexus devices independently without asking a sighted assistance for help.
This was possible in Android 5.
Note that I am not talking about bootloader unlocking, since I already did that and did not relock my bootloader.
I am talking about the stage that we need to add the zip packages and install them.
So again, any chance of having an automated root like before?
Franko kernel release 77 for Android 6.
My question is, will rooting again with this toolkit wipe all my data?
Now kit is using 2.
I will try on the 5X and 9 this afternoon and report back.
What if you factory reset, flash stock, and unroot first?
AdAway successfully wrote the hosts file, no more ads!
Thank you so much Wug, donation incoming!!
I had the same problems as Ted before.
I am running Android 6.
I have been reading through below and it seems that I can now use the tool to move to the new Android 6.
However, I am a bit confused on the steps.
Would it be possible to spell it out?
Should I Flash Stock and Unroot first?
Keep up the great work.
Make sure check no-wipe mode if u want to keep your files.
However, I cant root after updated to 6.
I soft bricked my nexus 5……now by the help of this toolkit….
So I reflashed it and saved all the zip files to the sd card.
I told it not to, and everything thing is working perfectly now.
Only issue that I have now is that the Home button of the Nexus Player remote does not bring me back the the Home Screen Leanback Launcher.
I re-flashed the image several times with and without root, but still the Home button does not function.
Both these Home keys worked with previous versions of Marshmallow.
I apologize for the off topic question, but my understanding is that you also have a Nexus Player.
Are you running Android 6.
Both of these Home keys worked fine before flashing 6.
The problem now is when editing the build.
I tried two root file managers, root explorer and fx manager.
Really the phone is not rooted properly until you can edit system files.
Go and delete some system packages like asian input methods etc.
Rooting with su ver 2.
I want to port youre toollbox over to linux so you can make it work for both platforms.
The all in one Nexus toolkit!
All I got is systemless root.
On the other hand, it seems that Chainfire stopped making Nexus boot images for traditional rooting.
Would you patch boot images for Nexus devices?
I hope there are people who still prefer the traditional nonsystemless root, just like me.
I will buy you a beer again.
Please reboot and try again.
Tried to root afterwards and got the never ending marshmallow logo loop similar to some of the comment bellow mentioned.
I was able to recover from that by flashing back to 6.
Any suggestion on how I can root my device.
Happy holidays and thank you for the wonderful job you are doing.
It worked fine before windows 10.
I can download it manually by fallowing the link in the pop up, but just want to know if there is anything I can do to solve my problem.
Any help would be much appreciated.
After that Super User was installed in my tab.
Everything was fine, but last week I unfortunately tried to update the android version to 4.
I tried almost everything as I can surfing internet.
Now please help me to get back my tab.
And thanks a lot in advance.
I am trying to Flash Stock + Unroot my 2012 Nexus 7.
What might I try next?
Previously before system less root it was xbin.
I respect ya very much!
Keep up the great work!
I think Google Wallet can do the trick.
I currently have a Nexus 5 which is rooted and running android version 4.
Much love and thank you for your help!
I currently have a Nexus 5 which is rooted and running android version 4.
Much love and thank you for your help!
I think that maybe automating the process or not using a modified boot image might have caused it to miss an important step on the N9.
On a positive note, I no longer see the yellow warning message on boot about not being able to check for corruption.
The process worked without error.
However, I do still see the yellow warning about not being able to check for corruption.
Not a big deal though.
But oddly enough as of this morning on 2.
I rooted the N9 again with 2.
Same as my 2nd post above, it worked that way.
ReadyToFlash folder on my N9.
It has always worked for my N5, N9, and N5X until now.
Does anyone else have this problem?
Once I flash root, my phone booted up.
Upon another reboot, I got stuck at the Google logo and had to flash again and wipe my phone.
It never does finish booting.
Left it for 45 minutes, then powered off and tried to boot again and get the same thing, shows the boot animation and goes no further.
I believe you need to update your toolkit to take this into account.
Can i tell me why?
Keep up the great work man.
By using Xender u can send all the apps to another phone and than take them back after root from that phone.
I would like to suggest a new feature.
Thanks for fixing the getvar unlocked problem.
Now my Nexus 7 2013 WiFi was able to flash stock, and afterwards successfully re-rooted.
The errors your received indicate a bad connection.
Please, can you tell me : does it work on a Nexus 4 running 5.
How would I go about updating without losing root?
Android Pay fails at checkout.
Reverted AdAway to original hosts, removed AdAway and cflumen.
I then used Flash Stock + Unroot with NoWipe mode and everything appears to run successfully.
And can I get back to clean booting N6 with working Android Pay without doing a full wipe?
Device is a nexus 5.
When I double click the exe it does not open.
I tried right clicking and to run as administrator but that did not open it either.
I double clicked and nothing happened.
In Device Manager there is no yellow exclamation point, so what do I do?
You can even try reinstalling drivers.
I had this issue, went to step 3, updated and that fixed it like the other users below.
Unlock worked fine, all drivers were successfully installed.
Problem is when i try to root it.
Any help or idea would be great.
I now have a working device thats currently upgrading and ticking along very nicely.
I get the screen with your phone is running corrupt software press power to pause boot and that is as far as it gets.
After a new bootup, it appears to be normal but without encryption.
Can someone help me please to fix this?
Any idea as to what might be causing this issue?
I pay for my lunch using Android Pay.
Open that folder and do these two things.
On the popup, tap properties.
Change that to 751, and tap Apply.
That should be you rooted, with Android Pay working.
Did I do something wrong?
I pressed FlashStock + Unroot and everything worked fine.
It says the xu binary is missing.
Shall I redo the update or will it not un-root anymore at all due to the new android?
Each attempt now to re-root the device results in a boot-loop.
Is there a solution to this problem?
Manually reboot Nexus to bootloader mode, then try to do the procedure.
All works and device is rooted correctly.
Then everything worked fine :-.
Since I was less concerned to find exactly what was going wrong than just to get things working, I made a bunch of changes, and something in all that worked.
I did hit upon the same trick as did you smuggling twrp-3.
Be sure to rename it to twrp-2.
Then do a root + customer recovery.
When I try to update to 6.
Ive done it many times over the past couple of years on n7 2012 3g devices.
However, on both rooting failed.
No matter what I did I could not fix this.
In the end I used Advanced Utilities… Custom Recovery.
Got root successfully doing that on both devices.
Your goal was to make this entire process as smooth and simple as possible…….
Download it yourself from the main factory image site.
I did it yesterday on my Nexus 6, using no-wipe mode.
Did you just say that you managed it to have working root with working Android Pay?
Typically devs will wait until official release before working on a root solution — but I may be able to support new preview builds in some capacity like flashing it, etc.
I will try to be more vigilant about updating the masterlists quicker.
Honestly not sure how to proceed.
Honestly not sure how to proceed.
It would hang on the boot screen until I force rebooted it.
I had to flash my phone back to stock, enable encryption, encrypt phone.
Prior I was rooting phone, then trying to encrypt it would just hang for 10 hours.
Hope the info helps others.
Root check says that the phone is not properly rooted.
Had to unroot it and that feature still worked for me in this program.
Running the latest version of Android 6.
I started of from 6.
For me it fails when trying to unlock the bootloader.
This program is a lifesaver and has saved my bricked phone like 5 times.
I feel like a hacker but you do all the work and I just click a button.
This toolkit is so awesome.
When it will be updated then you will see a message saying the same.
After that your build will get listed in the tool kit.
Then you can update your Nexus 5X.
As of the time of writing this post, the master list has not been updated yet.
The toolkit goes through the motions, but at the end of it all, nothing works.
I believe it is just a software malfunction and I think a factory reset will fix it.
Is there a possibility to backup my data at least my sms?
Is this because I am running 6.
Such an awesome programme, thank you!
It said it was successful, but I just get a forever-stuck white Google logo.
You provided free software that many of us could not use our devices without.
You are awesome and very much appreciated!
Was sitting on the donate button if Pixel C support arrived, too.
With that said, I hope the dude is ok.
These past few months have just been incredibly busy despite my best efforts to set aside dev time.
I forced myself to sit down and really grind it out bender style, and now 2.
I wanted to get it out asap, so I am waiting to finalize pixcel C support for the next release — which I will tackle this upcoming weekend.
I spent a great deal of time automating more things on my end, so I should be much faster with future updates.
Apologies, regardless that I made it literally hours before 2.
Looking forward to continuing to update this, including new features and extended device support.
I just got swamped these past few months.
Not sure if posting this in right place..
It acted as though I hit confirm though and continued forward and thankfully successfully flashed anyways.
I testing it out when flashing some other items and confirmed the repro steps.
It is now fixed in my private dev build, will be fixed publicly in v2.
Or will this not be done til the full N comes out for everyone?
Within the next few days.
So far all of my testing has been successful.
No matter what I do, the root process get interrupted with the same notification.
The process goes through un hindered until I get..
As a quick fix — in the flashstock.
Does anyone know how I will be able to reinstall the os as I think it wont have any os on it?
Will I be able to use the toolkit for such thing?
Feel free to reach out to me if you have any problems.
How can I fix this?
WugFresh After that I tried the option Flash Stock+Unroot and I succeeded to reach the set up, then it ask me to connect with wifi.
Someone wrote that it can be done by connect to free wifi.
Do you how to through this?
Pls help just like you always have.
It does a quick load-animation, but then it goes away and nothing ever happens.
I am running Windows Vista—yeah, I know…stop it!.
Any help would be greatly appreciated!
Its not done via touch screen.
Not rushing just having issues with my phone not being updated for a few months.
Would it be safe to select one of the other builds or am I missing something?
As i understand it should modify the bootloader only, but not touch system..?
The troubleshooting says to go into Device Manager and find yellow exclamation point.
There is not an unconfigured device listed.
I reran the test and it came back the same way.
Line 18980 File C:Program Files x86 WugFresh Developmentnexus Root ToolkitNexusRootToolkit.
It went thru the motion of rooting as if it was successful but it was not when I checked.
I tried rooting again after a few minutes and everything was fine, it rooted properly.
I thought that this was simply a bug with the toolkit and wugfresh needed to release a patch for it.
My phone rebooted and its not stucked at the Google animation screen.
I waited for like 30 minutes because and its stucked.
It seems to be working on all the other devices, but something is going on with 6P.
I setup the Android N 3 beta last week.
No worries — the toolkit worked fine — I did the no-wipe rooting — that went fine also.
Tonight I decided to get the Android N 4 beta and get it going.
Then decided to go and again re-root it and it says something about encrypted device detected — must wipe all data to root blah, blah — because — it said — due to Android N…….
I did it though because I thought that for sure it would double check and ask if I was sure I wanted to wipe all — it did not — I know, I know — backup blah blah.
But really wugfresh:disqus why did it and actually why does it have to wipe to get root now?
I am confused as to how I will get root.
I decided to go back to marshmallow and rooted again.
The only problem with going back that far is that it appears that Google will not remember your profile to reinstall all of your apps, so mine asked to install the backup profile from my nexus 7.
Did they work with Android N Preview 4?
I have factory reset my tablet and re-flashed the factory image but the problem still persists.
Can someone please help me fix this?
When it rebooted after flashing the latest update it said there was a problem with the encryption and I had to do a factory reset.
It worked fine with my Nexus 6P with the June Marshmallow update.
You ought to put a warning for the sideload function that it It will cause a factory Reset.
All else aside I do appreciate the program!
Repeated every step one more time just to make sure, same result.
Nexus 6 users beware, 2.
Thanks for the great work!
Never has any problems before.
Then tried to fall back to latest M build, also with no forced encryption, same issue.
Finally flashed preview 4 again and allowed encryption, went off fine.
Or is that just to big of a jump.
Or is that just to big of a jump.
Would it be best do do each one in turn?
I would really rather not do a clean flash.
Worse case scenario is that you have to revert back.
I personally have had success with bigger jumps.
Than would be 6 updates.
Thank you for a great program and you advice!
I went from angler-mmb29m December 2015 release to the angler-mtc19x July 2016 release without do any of the other releases.
That made it a total of 7 updates.
Everything went just fine, thank you again for your assistance.
Is there any way to find these files?
Thank you for suggestion, I slack when it comes to Web Dev..
Is there any way I can get the backup of my data?
If so, using the buttons, boot it up to the bootloader and boot into recovery.
When I unenrolled my device and reinstalled the previous version I am not able to get past the boot animation…as if stuckin bootloop.
So when I am using fastboot for unlocking I am getting an error message that the device is locked.
How can I unlock my device now?
Followed all the prompts, and tried the fixes I found in the forums, to no avail.
Google has not, thus far, been fruitful.
Then you manually update but have it search your computer for a driver.
I ran into the same problem.
No option for that when using 2.
To continue, sign in with a Google Account that was previously synced on this device.
I am not knowledgeable in software coding etc, just a guy trying to get his Nexus 7 Wi-fi to work properly again.
Hoping this will be resolved with next update?
Nexus Root toolkit always send an error message : adb.
I wish N was for Nutella, Nougat sounds so weird.
I sent you some PayPal motivation for v 2.
Under the root button there is a check mark to also install custom recovery.
It will take care of both.
The official update for Android 7.
Great job with the software, thanks!
Root support will be extended as soon as possible.
Waiting for google to release the factory images to start working on it.
Will it work to root my Nexus 5X successfully?
If you were to replace the adb and fastboot with the old ones linked in that thread it would work.
I will integrate these old binaries into v2.
Thanks again for the report.
I will see if I can add in some better handling of that scenario, so that it just auto force-kills the hanged operation and retries it.
You will also have to wait for me to extend official support for those new 7.
I will do so asap — just waiting for google to release the factory images so I can get started working on it.
Strangely google decided to name the last preview build version 7.
You are correct, the latest official 7.
Root support will be extended as soon as possible.
Waiting for google to release the factory images to start working on it.
Since installing 90G have been unable to root and now getting same error for sideloading 90M.
When they release, I will start working on adding it.
When I received the next security update I lost root but kept the unlocked tethering.
Now I updated to Android N which I figure would erase the the tethering.
Well I guess I was wrong because I can still tether and receive updates with no problem on my 6p.
It is good to hear that this should not be the case.
What carrier are you on?
At this time google has only released factory images for pixel c, nexus player and nexus 9 wifi.
I just saw the build number on the screen shot and missed lookin at the model number.
Actually Android N not support Xposed.
I need uninstall Xposed from recovery with uninstall before the update to Android N.
Should I reflash the factory image or is this a change in Android 7.

Is there any way I samsung usb driver win 8 64 bit get the backup of my data? I was rooting Nexus 4 running on KitKat 4. I think Google Wallet can do the trick. Had Android L Developer review samsung usb driver win 8 64 bit. I have a Nexus 5 and I was running Slimkat 4. Also for my Nexus 5x root is not working. Is there something that I might have missed in the steps? How can I unlock my device now? Repeated every step one more time just to make sure, same result. Please, can you tell me : does it work on a Nexus 4 running 5. Just stay in bootloader mode, and samsung usb driver win 8 64 bit the toolkits unlock button. Thank you to the developer s for being so responsive in the comment section. It is good to hear that this should not be the case. 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. Unlock worked fine, all drivers were successfully installed. Prior I was rooting phone, then trying to encrypt it would just hang for 10 hours. I have the same problem with BusyBox. I have figured out the problem for that and made the fix, will be included in v1. However, no matter which of the three download links I try I get a 72. I flashed Xposed and everything seems to be fine. All I got is systemless root. Ive done it many times over the past couple of years on n7 2012 3g devices. Thanks for helping me get it back! My device is not rooted, but unlocked. So I reflashed it and saved all the zip files to the sd card. He so he let it sit for a bit and it did nothing. Near the end of rooting processus for my Nexus 4 KitKat 4. Unlocking wipes, so backup first. When I double click the exe it does not open.