I kind of did it backwards to what you are saying. I ran the automated script (by accident) before going into recovery and flashing SU.zip. It flashed over fine, I backed out to the main menu and when I went to reboot the system it was not allowing me to click it. The power button was simply turning my screen off and on. Regardless, I tried it again just now and it worked haha. I rebooted, went into ROM manager and flashed CWM from there (as the instructions stated), so I suppose everything is good? Thanks for the reply!
DroidForums.net | Android Forum & News
This is a sample guest message. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!
[HACKS] [Toolkit] Nexus Root Toolkit v1.6.0 [Updated 11/26/12]
- Thread starter WugFresh
- Start date
I kind of did it backwards to what you are saying. I ran the automated script (by accident) before going into recovery and flashing SU.zip. It flashed over fine, I backed out to the main menu and when I went to reboot the system it was not allowing me to click it. The power button was simply turning my screen off and on. Regardless, I tried it again just now and it worked haha. I rebooted, went into ROM manager and flashed CWM from there (as the instructions stated), so I suppose everything is good? Thanks for the reply!
Glad it worked out...I know when things don't go exactly right when rooting, it can really freak a person out.
Nice! I often tell people that 85% of computer related problems can be solved by toggling things off/on or just starting over...lol. Never underestimate the power of 'round two'
{{ WugFresh }}
Didn't say this last night, but well done Wug! :hail:
I got my G Nexus unlocked and rooted last night! The hardest part for me was the installation of the drivers...I was having a "duh" moment not realizing I needed to plug in my device to get the drivers completely updated. Also, might of had problems because I was having "fake tea" with my 2 year old and trying to do this at the same time!
Anyway, well thought out tool with complete steps that don't seem to miss anything. I have seen many instructions over the years using Android where a dev will leave out some key steps just because the process is second nature to them. This is definitely a usable root method for any noobie!
I will get you a donation next week...short right now because I had to unexpectedly fix a broken furnace this weekend. :frown:
I got my G Nexus unlocked and rooted last night! The hardest part for me was the installation of the drivers...I was having a "duh" moment not realizing I needed to plug in my device to get the drivers completely updated. Also, might of had problems because I was having "fake tea" with my 2 year old and trying to do this at the same time!
Anyway, well thought out tool with complete steps that don't seem to miss anything. I have seen many instructions over the years using Android where a dev will leave out some key steps just because the process is second nature to them. This is definitely a usable root method for any noobie!
I will get you a donation next week...short right now because I had to unexpectedly fix a broken furnace this weekend. :frown:
Didn't say this last night, but well done Wug! :hail:
I got my G Nexus unlocked and rooted last night! The hardest part for me was the installation of the drivers...I was having a "duh" moment not realizing I needed to plug in my device to get the drivers completely updated. Also, might of had problems because I was having "fake tea" with my 2 year old and trying to do this at the same time!
Anyway, well thought out tool with complete steps that don't seem to miss anything. I have seen many instructions over the years using Android where a dev will leave out some key steps just because the process is second nature to them. This is definitely a usable root method for any noobie!
I will get you a donation next week...short right now because I had to unexpectedly fix a broken furnace this weekend. :frown:
Thank you! I am happy to hear it worked well for and that you found it to be user friendly. Haha, yes.. I forgot to include a warning about avoiding tea parties while rooting.. lol ;-)
Enjoy!
{{ WugFresh }}
I haven't installed the toolkit just yet (looks great!) but I noticed that Backup Apps + Data gives you the option to backup system apps. I didn't see from the doc where there was an option to restore system apps? Is there any granularity between what you choose to backup (Apps, Data, System Apps, System Data) and what you choose to subsequently restore (Apps, Data, System Apps, System Data)? Or is the mix you choose to backup the only mix that can be restored?
Also, is the backup/restore for files and data only intended between (same/different?) versions on the stock roms and (not?) for use with custom roms? Just wondering how far this would go before you had to use titanium?
Also, is the backup/restore for files and data only intended between (same/different?) versions on the stock roms and (not?) for use with custom roms? Just wondering how far this would go before you had to use titanium?
When you select the backup apps + data button, you are presented with a choice to backup just user apps + data, or user app + data and system apps + data. Its recommended to only backup user apps, because restoring system apps is known to potentially cause problems. Regarding selective restoring. No.. it's a batch process. It restores the whole restore file. Regarding a more selective backup... its not really possible for me to do it in a way that didn't just create a million backups.. Like I could make a way to have the end user selectively backup individual apps and data.. but I don't think I can make it do it all in one backup file. Plus.. there would have to be a cool way to list all the apps the user has on their phone currently... otherwise the user would have to type in the exact app name they wanted to restore.. and that would kind of defeat the point of it being automated. I will look into a more selective, user choice governed backup.
For now backing up user apps + data and restoring them on a custom ROM is entirely ok. Go for it. Enjoy!
{{ WugFresh }}
OK need some help. I downloaded 1.3 and ran it. Did the drivers part like the instructions said and then realized I hadn't backed up anything off my phone. No big deal I figured, closed the toolkit, backed up all my stuff and launched the toolkit again. Did the drivers option again since I closed it before I finished that section and now I get the following error after the part where you're supposed to get rid of any old drivers etc.
View attachment 46414
On top of that I've uninstalled the Samsung USB Drivers for mobile phones and removed the WUG directory from C: to try to start fresh. Always get the same thing and I'm afraid to go any further. It seemed to be working the first time I tried before I stopped it in the middle to back up all my files. How should I go about getting back there to start over or correct this error?
View attachment 46414
On top of that I've uninstalled the Samsung USB Drivers for mobile phones and removed the WUG directory from C: to try to start fresh. Always get the same thing and I'm afraid to go any further. It seemed to be working the first time I tried before I stopped it in the middle to back up all my files. How should I go about getting back there to start over or correct this error?
Yeah.. I put that in in case the auto driver configuration didn't work, the "Something went wrong..." just means that the auto configuration didn't work.. but then it goes right into manual driver instructions. No need to be scared to keep going, you just need to configure your drivers... that's all. If you want more detailed instructions on driver configuration, check out: Manual Driver Configuration | WugFresh
The same manual steps are included in the script though... in a slightly more abbreviated version.
{{ WugFresh }}
Cool man, whatever works for you. You easily flash cwm with my program using the flash to recovery button. Or just type in a simple fastboot cmd in terminal.
{{ WugFresh }}
+1 Successfully unlocked and rooted tonight.
HikenGruven
Member
I've gone through the instructions for Part 1 at least 20 times now. Instead of seeing "Mobile ADB Device" as mentioned, I'm seeing "Android ADB Interface". When I enter "adb devices" in the CMD prompt, this is the message it says ADB is not recognized. I'm running 32 Bit Windows 7.
Last edited:
Sounds like you might have some file/folder path issues as I did. Turns out that I had two different SDK folders (one on my SSD, Windows 7 operating system drive, C:, and one on my User Data/Files drive, X: ). Once I merged the contents into the C: path, tool worked great.