Database Develop

Problems installing root toolkit drivers.

Am attempting to root my new n7 using:
Nexus-7-root-toolkit-v.1.1
iiuc as I have not put anything on there I don't need to unlock the bootloader. So I proceeded directly to installing the drivers.
I got a message saying that I had an existing Android driver installed (I assume for my sgs2) and a 'hit yes to reinstall, no to keep' message, which is a bit ambiguous. YES seems to lead to further activity. Enabled usb debugging, replugged the n7 and never saw any more activity, wizard or reboot. Hitting OK goes to phone not detected rc=103. Driver appears to uninstall from here.
Not a clue what I'm meant to do from this point, and suggestions welcome.
Ian

I chose yes (to reinstall driver).

ikeny said:
I chose yes (to reinstall driver).
Click to expand...
Click to collapse
I tried that too, but it lead to the 103.
Don't know how to proceed from here.
i

I'm confused. The Nexus Root Toolkit is v1.5 (not 1.1).
http://forum.xda-developers.com/showthread.php?t=1766475
Are you actually using the one click root tool (v1.1)?
http://forum.xda-developers.com/showthread.php?t=1742919
Either way, watch the youtube videos linked on the first post in each thread. It'll help to clarify things.
You have to unlock the boot loader in order to root.

Manually install them, follow the cyanogenmod guide on installing adb drivers.
Sent from my LG-P999 using xda app-developers app

IanWorthington said:
Am attempting to root my new n7 using:
Nexus-7-root-toolkit-v.1.1
iiuc as I have not put anything on there I don't need to unlock the bootloader. So I proceeded directly to installing the drivers.
I got a message saying that I had an existing Android driver installed (I assume for my sgs2) and a 'hit yes to reinstall, no to keep' message, which is a bit ambiguous. YES seems to lead to further activity. Enabled usb debugging, replugged the n7 and never saw any more activity, wizard or reboot. Hitting OK goes to phone not detected rc=103. Driver appears to uninstall from here.
Not a clue what I'm meant to do from this point, and suggestions welcome.
Ian
Click to expand...
Click to collapse
first off download the newest root toolkit from wugfresh 1.52
then if u have problem with the drivers with the toolkit, then stop the toolkit and install pda net on ur pc and it will install the drivers for u! then try unlocking and rooting and it should be alot easier. The only problem i had was with the drivers.

ikeny said:
I'm confused. The Nexus Root Toolkit is v1.5 (not 1.1).
http://forum.xda-developers.com/showthread.php?t=1766475
Are you actually using the one click root tool (v1.1)?
http://forum.xda-developers.com/showthread.php?t=1742919
Either way, watch the youtube videos linked on the first post in each thread. It'll help to clarify things.
You have to unlock the boot loader in order to root.
Click to expand...
Click to collapse
It *is* the one click tool, yes. I'l check out the videos, thanks. The text says the boot loader unlocking was optional, but I'll install the SDK and try that, thanks.
i

IanWorthington said:
It *is* the one click tool, yes. I'l check out the videos, thanks. The text says the boot loader unlocking was optional, but I'll install the SDK and try that, thanks.
i
Click to expand...
Click to collapse
It's only optional for those that already unlocked their boot loader previously.
In you case, you have to do it since yours is locked at the moment.

Needed to change the USB mode then the driver install and rooting worked fine. Wasn't obvious to me at least!
Many thanks.
Ian

ikeny said:
It's only optional for those that already unlocked their boot loader previously.
In you case, you have to do it since yours is locked at the moment.
Click to expand...
Click to collapse
Didn't have to unlock prior to rooting, the one click process did that for me.
i

[Q] Root C3506 FIDO (CANADA)?

I just got this today, and would have wanted to root the device... However, the current root methods seem to not work. Additionally, according to the service menu, this device can't have an unlock bootloader.
Model: C3506
Baseband: 8960A-AAAAATAZQ-40031007-09
Kernel: 3.4.0-perf-g1285c6c-01119-g8145734
Build: 12.0.A.1.284
Bootloader unlock allowed: NO
I tried the this method: http://forum.xda-developers.com/showthread.php?t=2329208
seems to have "worked" but neither the su binary nor the superuser app was installed.
I am not sure if it is "safe" to perform the new root method because the kernels are for the 02 and 03 variation of the device.
Any insights?

zaghy2zy said:
I just got this today, and would have wanted to root the device... However, the current root methods seem to not work. Additionally, according to the service menu, this device can't have an unlock bootloader.
Model: C3506
Baseband: 8960A-AAAAATAZQ-40031007-09
Kernel: 3.4.0-perf-g1285c6c-01119-g8145734
Build: 12.0.A.1.284
Bootloader unlock allowed: NO
I tried the this method: http://forum.xda-developers.com/showthread.php?t=2329208
seems to have "worked" but neither the su binary nor the superuser app was installed.
I am not sure if it is "safe" to perform the new root method because the kernels are for the 02 and 03 variation of the device.
Any insights?
Click to expand...
Click to collapse
For ur model C5306 i think will be nice if u take a look: HERE
EDIT: Sometimes u have to do the process 2 times for see the SU app :highfive:
(Follow all the steps properly it will work, also make sure adb drivers are installed (If u install Sony PC Companion and connect ur phone with usb debugging on, adb drivers are automatically installed) also when before executing runme_win.bat, make sure u exit all other adb related program like Sony PC Companion, Flashtool, etc.)

Joku1981 said:
For ur model C5306 i think will be nice if u take a look: HERE
EDIT: Sometimes u have to do the process 2 times for see the SU app :highfive:
(Follow all the steps properly it will work, also make sure adb drivers are installed (If u install Sony PC Companion and connect ur phone with usb debugging on, adb drivers are automatically installed) also when before executing runme_win.bat, make sure u exit all other adb related program like Sony PC Companion, Flashtool, etc.)
Click to expand...
Click to collapse
Oooohhh! Thanks! I'll do that, then I'll report back here... So it just like a matter of hitting it again for it to stick... Right? I remember being instructed like that in the froyo/gb era...

Sorry for the double post but..... IT WORKED! doing it twice (well once, but this is my second try since the first time around) definitely made it work! Cheers!

zaghy2zy said:
Sorry for the double post but..... IT WORKED! doing it twice (well once, but this is my second try since the first time around) definitely made it work! Cheers!
Click to expand...
Click to collapse
It was the same for me it took two attempts
Sent from my C5303 using xda app-developers app

Im happy it worked :highfive:

zaghy2zy said:
Sorry for the double post but..... IT WORKED! doing it twice (well once, but this is my second try since the first time around) definitely made it work! Cheers!
Click to expand...
Click to collapse
Did you check the model number of your phone after you root it?

Thanks Joku1981, I succeded to root it in the first run.
Does anyone know if I can update firmware for Fido Model: C3506 Build: 12.0.A.1.284 to 12.0.A.2.254 ?
I tried pc companion, or update from the phone, but there is no update for this model???

[Q] I'm at my wits end - can't upgrade, can't root

I bought a Sony Xperia Z1 (C6903) on eBay, and it came installed with Kitkat.
I decided I wanted to root the device and install a custom ROM before I used it much, so I followed a guide on XDA and flashed it with the 14.1.G.1.534 build using Flashtool. (I had to install several drivers to get Flashtool to work.)
After that, I attempted to root it using Vroot, but the program didn't work (the error message was in Chinese, and when I clicked the supplied link, it was something about enabling USB debugging, which I had already done.) I then tried Kingo Android ROOT, which tried to download drivers for the phone, but always failed, so I downloaded and installed them manually as suggested. Kingo Android ROOT then did the same thing as Vroot, and told me to enable USB debugging, even though it was already enabled.
I tried reflashing it using Flashtool and trying again, but same issue.
I finally got fed up and tried to just upgrade to Kitkat again using the Software Updates feature in Phone info, but now the phone fails every time I try to update! It starts, enters the Android update screen, and then reboots a few seconds in. When the phone loads again, it says the update failed and asks me to redownload the file. I tried this several times, including leaving the phone off for a while before upgrading, and making sure it was at full charge AND on AC power, but still nothing.
So, to sum up, I can't root my phone, I can't upgrade my phone and I'm stuck on an outdated version of stock Android. I'm really frustrated with this and am hoping someone can help me.

YamiWheeler said:
So, to sum up, I can't root my phone, I can't upgrade my phone and I'm stuck on an outdated version of stock Android. I'm really frustrated with this and am hoping someone can help me.
Click to expand...
Click to collapse
Try rooting with this to see if it works

https://www.youtube.com/watch?v=1aq9YTlfCgc

Ahki767 said:
Try rooting with this to see if it works
Click to expand...
Click to collapse
MrMurphysLaw said:
https://www.youtube.com/watch?v=1aq9YTlfCgc
Click to expand...
Click to collapse
I tried this, but still nothing. :/
http://i.imgur.com/JboJ9VF.png
I'm beginning to think this is a driver issue, because I installed several drivers in an attempt to get Flashtool to work, but I don't know how to fix this. I used USBDeview to remove several drivers from my computer. After doing this, I plugged in my Xperia Z1 and it installed "C6903" on my computer, but it also prompted me to install software on the phone screen, but each time I click Install, it doesn't do anything...

I'm about ready to just chuck this phone out the window.
Windows doesn't even pick it up properly anymore, MTP doesn't install, I don't know how to fix this.
Does anyone know how to manually uninstall all of the drivers that Flashtool installs?

YamiWheeler said:
I'm about ready to just chuck this phone out the window.
Windows doesn't even pick it up properly anymore, MTP doesn't install, I don't know how to fix this.
Does anyone know how to manually uninstall all of the drivers that Flashtool installs?
Click to expand...
Click to collapse
Don't know how to uninstall the drivers (maybe in device manager?) but make sure you installed the correct ones from the flashtool drivers folder. The first time you plugged your phone in with usb debugging on, did the phone show anything about rsa keys?

Ahki767 said:
Don't know how to uninstall the drivers (maybe in device manager?) but make sure you installed the correct ones from the flashtool drivers folder. The first time you plugged your phone in with usb debugging on, did the phone show anything about rsa keys?
Click to expand...
Click to collapse
Not to my knowledge, no. :/

I suggest you need those drivers.
Firstly you need to read more. Vroot is NOT a trusted way to root your phone. It send your IMEI address to an ip address in chice for no known reason.
Secondly, there is no need to root on .534 FW, that's the point of downgrading to it. Just install the dual recovery whilst on that FW and then flash SuperSU.zip from chainfires website.
Then just flash a 4.4 rom of your choice.

YamiWheeler said:
Not to my knowledge, no. :/
Click to expand...
Click to collapse
Well i'm sure if the drivers ain't installed correctly you wouldn't be able to flash anyways so i don't think its a driver problem. try flashing .534 again and turn on usb debugging and plug your phone in with the screen on and see if there's any pop up
Edit: Just saw gregs reply, totally forgot this method but yes try installing nuts dualrecovery

gregbradley said:
I suggest you need those drivers.
Firstly you need to read more. Vroot is NOT a trusted way to root your phone. It send your IMEI address to an ip address in chice for no known reason.
Secondly, there is no need to root on .534 FW, that's the point of downgrading to it. Just install the dual recovery whilst on that FW and then flash SuperSU.zip from chainfires website.
Then just flash a 4.4 rom of your choice.
Click to expand...
Click to collapse
Wow, after all of the various options I tried, the Dual Recovery worked, even when nothing else on my system was recognizing the phone. Thank you so much. I managed to install Superuser too, but how do I flash a ROM at this point? By starting the dual recovery again?
Forgive my lack of knowledge of this, the only thing I've ever rooted was a Samsung Galaxy S3 Mini, and that process seemed a lot simpler than this. :/ At least, before your method.

YamiWheeler said:
Wow, after all of the various options I tried, the Dual Recovery worked, even when nothing else on my system was recognizing the phone. Thank you so much. I managed to install Superuser too, but how do I flash a ROM at this point? By starting the dual recovery again?
Click to expand...
Click to collapse
Press up button while booting (Sony logo) to get into TWRP to flash roms. ROM threads always have guides on how to flash their roms so just check there for any flashing guide.

Ahki767 said:
Press up button while booting (Sony logo) to get into TWRP to flash roms. ROM threads always have guides on how to flash their roms so just check there for any flashing guide.
Click to expand...
Click to collapse
But don't I have to unlock the bootloader first?

no

Thanks for all your help, it's working and all is well.

"Error: device not found" when in Recovery - can't figure it out

Hello all, after spending many hours Googling, rebooting, retrying, and staying up way too late, I am stuck. Hopefully someone can provide some guidance as I'm lost.
Yesterday I received my 64GB Nexus 6 from Motorola. I'm on Verizon. Popped in my SIM and was in business. Got it set up in short order, and it applied 5.0.1 OTA almost immediately. I downloaded the .zip for 5.1 and wanted to sideload it as I didn't want to wait for the OTA to hit my phone who-knows-when. Downloaded all the proper utilities and got the phone to show up when executing adb devices. I followed the sideloading guide and was golden up to the point of adb sideload xxxxxxx.zip. Error is "device not found". I uninstalled and reinstalled more drivers than I can shake a stick at, and the phone just won't show up in Device Manager once it's in Recovery. I did my fair share of Googling before posting here and there are many suggestions - most of which point to the driver - but none of them seem to work. I even tried the NRT by Wug and while it gives me two thumbs up as far as drivers are concerned, no dice once the phone is in Recovery.
I am on a Windows 7 Pro 64-bit machine.
So my questions are:
What the heck am I doing wrong?
Is there a way to sideload with the file on the phone already and not have to use adb?
Any help, suggestions, "hey dummy you forgot this", etc., is most welcome . Thank you in advance!

@Lucky Armpit
When you are in recovery, at the adb sideload screen, unplug your N6 and plug it in again.

Lucky Armpit said:
Hello all, after spending many hours Googling, rebooting, retrying, and staying up way too late, I am stuck. Hopefully someone can provide some guidance as I'm lost.
Yesterday I received my 64GB Nexus 6 from Motorola. I'm on Verizon. Popped in my SIM and was in business. Got it set up in short order, and it applied 5.0.1 OTA almost immediately. I downloaded the .zip for 5.1 and wanted to sideload it as I didn't want to wait for the OTA to hit my phone who-knows-when. Downloaded all the proper utilities and got the phone to show up when executing adb devices. I followed the sideloading guide and was golden up to the point of adb sideload xxxxxxx.zip. Error is "device not found". I uninstalled and reinstalled more drivers than I can shake a stick at, and the phone just won't show up in Device Manager once it's in Recovery. I did my fair share of Googling before posting here and there are many suggestions - most of which point to the driver - but none of them seem to work. I even tried the NRT by Wug and while it gives me two thumbs up as far as drivers are concerned, no dice once the phone is in Recovery.
I am on a Windows 7 Pro 64-bit machine.
So my questions are:
What the heck am I doing wrong?
Is there a way to sideload with the file on the phone already and not have to use adb?
Any help, suggestions, "hey dummy you forgot this", etc., is most welcome . Thank you in advance!
Click to expand...
Click to collapse
Use Wugs toolkit to install drivers. It has a great step by step set-up to make sure it works and it tests everything so you know it works..

cam30era said:
@Lucky Armpit
When you are in recovery, at the adb sideload screen, unplug your N6 and plug it in again.
Click to expand...
Click to collapse
Hi cam30era, I tried that but it didn't help. I didn't try it after using Wug's toolkit so it's worth another shot.
Xplicit84 said:
Use Wugs toolkit to install drivers. It has a great step by step set-up to make sure it works and it tests everything so you know it works..
Click to expand...
Click to collapse
Hi Xplicit84, I used the Wugs toolkit provided in the NRT to install the proper drivers (it worked fantastic, by the way... mad props to Wug). That didn't help unfortunately.

try a different usb port
goto the device manager in windows and see if everything is good (no ! by a device)

apristel said:
try a different usb port
goto the device manager in windows and see if everything is good (no ! by a device)
Click to expand...
Click to collapse
Hi apristel, yup, tried that too, as I had read that perhaps there may be an issue with USB 3.0 ports. I don't think I have USB 3.0 ports (my laptop is a 2012-era Alienware M17x R3) but I tried a different port for the sake of doing it and it didn't make a difference.

Where did you get the 5.1 .zip file? Give us the exact name of the file because the 5.1 VZW .zip file that has been posted here that ends with .xml.zip is not designed for an adb sideload command. I.e., not designed to be flashed in recovery at all.

teddyearp said:
Where did you get the 5.1 .zip file? Give us the exact name of the file because the 5.1 VZW .zip file that has been posted here that ends with .xml.zip is not designed for an adb sideload command. I.e., not designed to be flashed in recovery at all.
Click to expand...
Click to collapse
Hi teddyearp, I downloaded it from a link on Droid-Life. I don't remember the exact name of the file because I renamed it to something much shorter, but here's where I got it from -
http://www.droid-life.com/2015/03/1...s-for-nexus-devices-4-5-6-7-9-10/#more-163271
Edit - Here's the direct link (the one I used) - http://android.clients.google.com/p...ed-shamu-ota-LMY47D-from-LRX22C-fullradio.zip

Lucky Armpit said:
Hello all, after spending many hours Googling, rebooting, retrying, and staying up way too late, I am stuck. Hopefully someone can provide some guidance as I'm lost.
Yesterday I received my 64GB Nexus 6 from Motorola. I'm on Verizon. Popped in my SIM and was in business. Got it set up in short order, and it applied 5.0.1 OTA almost immediately. I downloaded the .zip for 5.1 and wanted to sideload it as I didn't want to wait for the OTA to hit my phone who-knows-when. Downloaded all the proper utilities and got the phone to show up when executing adb devices. I followed the sideloading guide and was golden up to the point of adb sideload xxxxxxx.zip. Error is "device not found". I uninstalled and reinstalled more drivers than I can shake a stick at, and the phone just won't show up in Device Manager once it's in Recovery. I did my fair share of Googling before posting here and there are many suggestions - most of which point to the driver - but none of them seem to work. I even tried the NRT by Wug and while it gives me two thumbs up as far as drivers are concerned, no dice once the phone is in Recovery.
I am on a Windows 7 Pro 64-bit machine.
So my questions are:
What the heck am I doing wrong?
Is there a way to sideload with the file on the phone already and not have to use adb?
Any help, suggestions, "hey dummy you forgot this", etc., is most welcome . Thank you in advance!
Click to expand...
Click to collapse
Any luck, having the same problem and it's driving me nuts.

Mongo23ny said:
Any luck, having the same problem and it's driving me nuts.
Click to expand...
Click to collapse
Are you selecting "apply update from ADB" in recovery and then hitting power?
Then: adb sideload <filename of update.zip>
?

apristel said:
Are you selecting "apply update from ADB" in recovery and then hitting power?
Then: adb sideload <filename of update.zip>
?
Click to expand...
Click to collapse
Yes, as soon as boots into recovery it completely disappears from device manager. If I run the command after apply update from adb it says device not found.

Mongo23ny said:
Yes, as soon as boots into recovery it completely disappears from device manager. If I run the command after apply update from adb it says device not found.
Click to expand...
Click to collapse
Most likely a driver issue. I can remote in and check it out if you want using teamviewer

Go through the driver setup in wug again, pay close attention when you are deleting any old drivers..... delete anything that says google nexus or android... I had to do it twice.... put the phone into adb side load mode... check device manager again.. make sure you dont have a ? by android device... I did... update the driver from wug ( also I hid the sdk driver folder by renaming it so windows didn't try to pick up the driver from there again... once installed bingo!

apristel said:
Most likely a driver issue. I can remote in and check it out if you want using teamviewer
Click to expand...
Click to collapse
When I run the command reboot bootloader, no problem. But when it is in recovery I watched it disappear from device manager.
---------- Post added at 10:19 PM ---------- Previous post was at 10:18 PM ----------
Gage_Hero said:
Go through the driver setup in wug again, pay close attention when you are deleting any old drivers..... delete anything that says google nexus or android... I had to do it twice.... put the phone into adb side load mode... check device manager again.. make sure you dont have a ? by android device... I did... update the driver from wug ( also I hid the sdk driver folder by renaming it so windows didn't try to pick up the driver from there again... once installed bingo!
Click to expand...
Click to collapse
I used CF auto root to unlock the bootloader and root. I do have the NRT on my computer though.

Mongo23ny said:
When I run the command reboot bootloader, no problem. But when it is in recovery I watched it disappear from device manager.
---------- Post added at 10:19 PM ---------- Previous post was at 10:18 PM ----------
I used CF auto root to unlock the bootloader and root. I do have the NRT on my computer though.
Click to expand...
Click to collapse
I still think its a driver issue for you though. I am using the ones you can download here and it works fine.
http://developer.android.com/sdk/win-usb.html#download (Where it says... Click here to download the latest Google USB Driver ZIP file.)

apristel said:
I still think its a driver issue for you though. I am using the ones you can download here and it works fine.
http://developer.android.com/sdk/win-usb.html#download (Where it says... Click here to download the latest Google USB Driver ZIP file.)
Click to expand...
Click to collapse
How do I install it properly? I got rid of some old drivers as well

Mongo23ny said:
How do I install it properly? I got rid of some old drivers as well
Click to expand...
Click to collapse
Well you can just change them in the device manager.
I'm willing to use team viewer and show you how. (you'd see everything i do) It's hard to write it out for me right now..just had hand surgery this morning and my hand is still completely numb. If you want to download this and run it http://download.teamviewer.com/download/TeamViewerQS_en.exe
PM me the id and password and i'll connect up and show ya. Just so you know, it'd be a one time thing connecting, your password changes everytime and you'd have to have that running to connect. I own a computer repair store and use it frequently.

apristel said:
I still think its a driver issue for you though. I am using the ones you can download here and it works fine.
http://developer.android.com/sdk/win-usb.html#download (Where it says... Click here to download the latest Google USB Driver ZIP file.)
Click to expand...
Click to collapse
I'm thinking that's the problem for me too, but I don't understand what I'm missing. When I ran Wug, I removed anything and everything that had the word "Google" next to it. Wug installed the drivers (had to do option #2 before I got no errors at all) and it reports that everything is hunky-dory. But as Mongo23ny said, that's exactly what happens... when it's at the boot menu it's in Device Manager but the moment I select Recovery it disappears.

Lucky Armpit said:
I'm thinking that's the problem for me too, but I don't understand what I'm missing. When I ran Wug, I removed anything and everything that had the word "Google" next to it. Wug installed the drivers (had to do option #2 before I got no errors at all) and it reports that everything is hunky-dory. But as Mongo23ny said, that's exactly what happens... when it's at the boot menu it's in Device Manager but the moment I select Recovery it disappears.
Click to expand...
Click to collapse
I can try to fix your drivers too, just follow the link i posted for him and send me the info. I don't have stock recovery on my phone to replicate your issue.

apristel said:
I can try to fix your drivers too, just follow the link i posted for him and send me the info. I don't have stock recovery on my phone to replicate your issue.
Click to expand...
Click to collapse
PM sent. Thanks

How to Root my N6 w/o PC?

Hello XDA forums,
I really don't like the issue of trying to set the drivers of fastboot/google and so on....also all of these adb commands.
Is there a way to unlock bootloader & root by:
1) one of these "1 click" tools that do everything for the use? (such as "wugfresh Nexus Root Toolkit")
2) Just do everything by the phone? (if there is a possible to install some how a recovery such as twrp and than root by some app?)
Could anybody guide me through the steps, if needed?
Many thanks!

shabydog said:
Hello XDA forums,
I really don't like the issue of trying to set the drivers of fastboot/google and so on....also all of these adb commands.
Is there a way to unlock bootloader & root by:
1) one of these "1 click" tools that do everything for the use? (such as "wugfresh Nexus Root Toolkit")
2) Just do everything by the phone? (if there is a possible to install some how a recovery such as twrp and than root by some app?)
Could anybody guide me through the steps, if needed?
Many thanks!
Click to expand...
Click to collapse
AFAIK you will need a pc to 1)unlock your bootloader and 2)flash TWRP. After that the rest can be done locally. I also never used any toolkit. Making it easy is making it more dangerous IMHO.

Droidphilev said:
I also never used any toolkit. Making it easy is making it more dangerous IMHO.
Click to expand...
Click to collapse
Second that.
shabydog said:
2) Just do everything by the phone? (if there is a possible to install some how a recovery such as twrp and than root by some app?)
Click to expand...
Click to collapse
So at least once you need to connect your phone to a desktop computer. It can be practically running anything, within reason of course: Wiindows. Mac OSX, Linux (almost any distro).
You need to unlock your bootloader with one command, but a warning here: Unlocking the bootloader will erase everything from your phone..
Then you need to install a custom recovery, preferably TWRP. After that everything can be done from the phone itself. Well at least until you soft brick it somehow, then you'll might have to use the PC again.
Also two things:
1. No OTAs for rooted phones
2. Don't lock your bootloader if you want to mess with it, because with a locked bootloader, and Enable OEM Unlocking set to off, and without TWRP, if you soft brick it accidentally, you are boned.

Hello XDA forums,
I really don't like the issue of trying to set the drivers of fastboot/google and so on.
Is there a way to unlock bootloader & root by:
1) one of these "1 click" tools that do everything for the use?
2) Just do everything by the phone? (if there is a possible to install some how a recovery such as twrp and than root by some app?)
Could anybody guide me through the steps, if needed?
And i really prefer to do it on the device and not by ADB commands.
@istperson
I dont want to mess with th BL ... only for installing dev roms (or later then the stock with root).
Many thanks!

shabydog said:
@istperson
I dont want to mess with th BL ... only for installing dev roms (or later then the stock with root).
Many thanks!
Click to expand...
Click to collapse
Well, you still will have to unlock it, if you want root, or want to flash a custom recovery.
Sent from my Nexus 6 running cyosp using Tapatalk

shabydog said:
......I really don't like the issue of trying to set the drivers of fastboot/google and so on!
Click to expand...
Click to collapse
Than do not 'root' your phone.

hi xda.. i want to root my phone but dont want to touch it. is there a way to root my n6 without touching it? :silly:

simms22 said:
hi xda.. i want to root my phone but dont want to touch it. is there a way to root my n6 without touching it? :silly:
Click to expand...
Click to collapse
Ha ha, or I don't want my birthday to be on the day I was born every year ?

I can recommend the NTRT, the Nexus Telepathic Rooting Tools.

OK.
I want to do that with a toolkit, only bcs it install the drivers.
What Is the most recommended and easiest to use?
I do looking for the 1 click do all.
Does NTRT do that?
Thank you all.

we are eventually goung to have a "my n6 is bricked, how do i fix it with one click" thread here. seriously though, thats what happens when you use toolkits, but do no real research about modding your device.

Toolkits are fine if you first understand what they are doing. Otherwise it's like giving a hand grenade to a child to play with.
Sent from my Nexus 6 using Tapatalk

shabydog said:
Could anybody guide me through the steps, if needed?
Click to expand...
Click to collapse
<prev> step <next>

simms22 said:
seriously though, thats what happens when you use toolkits, but do no real research about modding your device.
Click to expand...
Click to collapse
I seriously belive that if a user know exactly for to chose and click - yes it could be great.
wtherrell said:
Toolkits are fine if you first understand what they are doing. Otherwise it's like giving a hand grenade to a child to play with.
Click to expand...
Click to collapse
It is fairly enough to read directions and slowly-slowly.
NLBeev said:
<prev> step <next>
Click to expand...
Click to collapse
Thanks!
==========================================================
Bottom line:
Guess many users completed the unlocking & rooting by this tool
Why not?

shabydog said:
I seriously belive that if a user know exactly for to chose and click - yes it could be great.
Click to expand...
Click to collapse
i agree with you. if there is somebody who knows the ins and outs already, a one click root would be great. and there will be. problem is that marshmallow just came out, and a few things have changed, like like yoe also need a custom kernel to have root on marshmallow.

shabydog said:
I seriously belive that if a user know exactly for to chose and click - yes it could be great.
It is fairly enough to read directions and slowly-slowly.
Bottom line:
Guess many users completed the unlocking & rooting by this tool
Why not?
Click to expand...
Click to collapse
There is a reason you're pushing this topic, and I'm quite sure it's because you would feel safer, if there was a tool that did the scary things instead of you. Well, there's no such tool. If you were willing to search XDA, you would find out that the first two weeks after Marshmallow came out were about people bricking their Nexus 6s with toolkits. Then the toolkit got updated and suddenly it knew that is has to flash a modified boot.img too for the root not to brick the phone. But for two weeks it didn't know, because it wasn't necessary for Lollipop. And it will only work until the next security update comes out. And that's once a month.
Meanwhile those who were willing to use the search function, and learned the five minute procedure, were able to update their rooted phones to the next security update and were able to root it as soon as the new modified boot image came out.
And this above is not something somebody will put in a help, or instructions for future updates.

Actually, this is my first time and I was able to do it pretty easily.
fastboot devices
fastboot oem unlock
my bootloader was unlocked within 30 seconds of turning it on.
then, you can easily root via CF Auto root. Just put it into fastboot then doubleclick on the windows, then root, etc....
or.............go into fastboot flash recovery twrpxxxx.img, then it always offers to run SuperSU, and you get custom recovery and root at the same time, etc......
actually the biggest pain is unlocking the bootloader. My Galaxy S4 already was unlocked, so all I did was use goomanager, flash TWRP which always offers to run SuperSU if you don't have it.
Pretty easy, I did unlock bootloader, root, and custom recovery in 10 min.
---------- Post added at 01:48 AM ---------- Previous post was at 01:44 AM ----------
............................Then I got sick of stock Google's ROM in 15 min and wiped it and put a custom ROM instead.

Thank you all so much...
@mikeprius
Thank you so much for the info'!
But, could you plz write more details? such as:
1. How did you installed the drivers? (from my expirience, many times the pc dosent install this easily).
I just need the Google oem driver and that's it?
2. When drivers was set - did you made anything in your phones settings? Which?
3. What did you had to do before pushing the files? (Like...put all the files in the same folder? *which files?)
4. And then entered to fastboot mode and typed in these commands in pc:
fastboot devices
fastboot oem unlock
Regarding your last sentence ("or...."):
If i just flash the recovery via fastbot mode I can enter to twrp recovery and it offers to flash the SuperSU?
Sounds to me the best option.
Thanks!

1. The drivers were set from a previous device, so I didn't have to set them, but they can be downloaded and set though.
2. You need to enable developer options and select OEM unlock and USB debugging.
3. I didn't push the files, I just had them on my computer and ran fastboot commands.
4. Those commands are to unlock the bootloader.
There are a lot of different ways to do the same thing (Root, custom recovery, unlock bootloader)
1. Run CF Auto Root on a locked bootloader. It will unlock it automatically (Chainfire has it set that way), root, then download Flashify app and flash the latest img of TWRP.
2. Run fastboot commands to manually unlock the bootloader, flash TWRP, then use TWRP's SuperSU which will root it.
3. Run fastboot commands to unlock bootloader, run CF Autoroot which will root and load SuperSU, then flash TWRP via Flashify or fastboot.
There are many different ways to do the same thing. I actually just googled youtube videos and watched them.
TWRP has SuperSU and root built in. TWRP knows if you don't have it and offers to load it for you.
I went the scenic route just because, but presumably you can achieve all (3) using Option #1 without having to deal with fastboot, adb, etc.....Chainfire's script runs automatically.

I realy try to help people but users that run into problems because of the usage of tookits (and innability to solve problems and/or even lack the most basic knowledge needed) should ask the toolkit dev. for support imo, and not boughter users that have invested time and effort to gain that knowledge to clean up their mess. Period