Database Info

[Q] Can't access root and Google apps

I recently rooted my phone (T-Mobile US Nexus S) and installed the 4.0.3 OTA update from this thread, but now I cannot access any Google apps or get root access on any of the apps that require it.

SounderBruce said:
I recently rooted my phone (T-Mobile US Nexus S) and installed the 4.0.3 OTA update from this thread, but now I cannot access any Google apps or get root access on any of the apps that require it.
Click to expand...
Click to collapse
Ok! first download : http://www.4shared.com/zip/XG506hyV/icsroot-fastboot-recovey.html
just unpack, connect your device and click run.bat.....Good luck!

I ran the .bat, but I get an error saying "Device already rooted", but it is still not recognized as rooted by SuperUser.
Alternatively, is it possible to completely wipe the phone of everything (including root) so I can start over with a fresh phone?

Of course you can, and might be the best idea if you don't mind doing it.
Make sure you have the latest CWM recovery on your phone, download the FULL ROM from this thread (i'm not american so i don't know exactly, but from what i know yours is the I9020T, so get that ROM) and copy it to the SDCard. Now go into recovery, wipe system/data and dalvik cache, then flash the ROM.
Do make sure you have the right ROM though. This will get you 100% fresh and untouched 4.0.3. You can probably clear out any non-personal folders on the sdcard too, but that shouldn't do any harm anyway.
After this, use the attached file from this thread to root, and feel free to update root/superuser.

Actually, that's what I did...I can't use CWM recovery because its displaying an error of no root. So how do I wipe this or fix CWM?

Is your boot loader unlocked? And are you trying to flash cwm through fastboot?
Note to backup your sdcard if unlocking the bootloader.

Harbb said:
Is your boot loader unlocked? And are you trying to flash cwm through fastboot?
Note to backup your sdcard if unlocking the bootloader.
Click to expand...
Click to collapse
My bootloader is apparently unlocked and I'm trying to flash through fastboot.

Are you sure the following is satisfied:
-open padlock and google logo on boot
-fastboot (on phone) says "bootloader status: unlocked" or something of the like
-you are using: "fastboot flash recovery "C:\path\to\recovery.img""
-you are using the above command while connected to the PC via USB (with working drivers) and that you are in fastboot mode on the phone (turn off phone --> hold Vol. Up then hold Power TOGETHER for about 2 seconds, should give you reboot and recovery options)
It is necessary to be in the bootloader/fastboot interface on the phone when you run the command. Hopefully it was something simple that i said above, otherwise i'm completely lost.

1. Yes
2. Yes
3. I didn't use that method to root...
4. I'll try that.

3 is just flashing recovery, that is the code u type into cmd/terminal to reflash the recovery img. It isn't rooting the phone. 4 is how to get into the mode on the phone to use the command.
Its a bit confusing at first but makes much more sense once you do it one or two times.

Where do I go to get the recovery image?

The latest ClockWorkMod Recovery can be found on this page. Just scroll down to Nexus S and download 5.0.2.0 crespo .img. Then just direct fastboot to the folder you have it saved in while using the "fastboot flash recovery C:\path\to\recovery.img" command.

Ok. I've tried this, but in command prompt, I get the following error:
C:\Users\Bruce>fastboot flash recovery C:\Users\Bruce\Downloads\recovery.img
'fastboot' is not recognized as an internal or external command,
operable program or batch file.

Check out this rooting guide, however only go up to step 5 (and do NOT type "fastboot oem unlock", do everything up until that point). This will setup fastboot for you, and setup drivers for your computer. Once this is done, do what you did above and it should work successfully.
Remember to cd (change directory) in cmd to where you unzipped that folder.

There isn't a link...

Sorry, stuffed that up. I fixed the link in my previous post pointing to NexusSHacks - How to Root Nexus S.

It's worked, but when I try to go to the recovery menu, the Google/unlocked padlock screen freezes or it displays an Android with its chest compartment open and a red triangular ! symbol.

I just had a really long reply and managed to lose it by closing the page..
That's the stock bootloader you see there, it probably didnt flash or you rebooted your phone. And make sure that you are flashing the latest CWM you downloaded before.

I flashed the latest CWM, but when I try to go to recovery, my phone freezes at the Google logo with the unlocked padlock.

Have you tried flashing it again, or maybe redownloading the file? And of course making sure it is the NEXUS S version which you are downloading.
Alternatively, try just "fastboot boot recovery.img", replacing recovery.img with the full name and path of cwm.
edit: btw, i'll be gone for an hour or two Bruce so i can answer any more questions/issues when i get back

[Q] Having trouble installing custom recovery - Unlocked and rooted TF700

Hello,
I am a new user, but I will do my best at providing as much information as possible to help the experts out here.
My TF700 device is currently rooted, and unlocked. I am on JB 4.2.1 using build 10.6.1.14.8 (US). I have also installed the newest available TWRP from the play store. USB debugging is enabled on my tablet.
I am attempting to follow the steps in sbdags fantastic guide to installing CROMi-Xenogenesis 5.3 DEODEX: http://forum.xda-developers.com/showthread.php?t=2425383
I would have posted to that thread with my question, but I am not allowed as I am a new user.
I have had no problem following the steps up until I reached the part where I needed to download Scott's Custom Recovery Tool. The instructions are quite unclear. I have downloaded the recovery tool, put the folder on my desktop. I did some digging around and realized I have to rename a .blob file to recovery.blob and put it in the file. I believe that I downloaded the correct version and renamed it to recovery.blob. The version I downloaded was openrecovery-twrp-2.6.3.2-tf700t.blob
I renamed the file to recovery.blob and ran "Scott's TF700T Recovery Install Tool.bat". The following appeared:
Here we go! Rebooting to bootloader now! (this didn't actually do anything on my tablet)
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
There is an adb that came with the recovery tool I downloaded from the thread I linked, but I'm not sure what I am missing. Other threads mention it was straightforward so I am not sure what I am missing.
Any help would be greatly appreciated! Thank you!

Deetrixx said:
Hello,
I am a new user, but I will do my best at providing as much information as possible to help the experts out here.
My TF700 device is currently rooted, and unlocked. I am on JB 4.2.1 using build 10.6.1.14.8 (US). I have also installed the newest available TWRP from the play store. USB debugging is enabled on my tablet.
I am attempting to follow the steps in sbdags fantastic guide to installing CROMi-Xenogenesis 5.3 DEODEX: http://forum.xda-developers.com/showthread.php?t=2425383
I would have posted to that thread with my question, but I am not allowed as I am a new user.
I have had no problem following the steps up until I reached the part where I needed to download Scott's Custom Recovery Tool. The instructions are quite unclear. I have downloaded the recovery tool, put the folder on my desktop. I did some digging around and realized I have to rename a .blob file to recovery.blob and put it in the file. I believe that I downloaded the correct version and renamed it to recovery.blob. The version I downloaded was openrecovery-twrp-2.6.3.2-tf700t.blob
I renamed the file to recovery.blob and ran "Scott's TF700T Recovery Install Tool.bat". The following appeared:
Here we go! Rebooting to bootloader now! (this didn't actually do anything on my tablet)
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
There is an adb that came with the recovery tool I downloaded from the thread I linked, but I'm not sure what I am missing. Other threads mention it was straightforward so I am not sure what I am missing.
Any help would be greatly appreciated! Thank you!
Click to expand...
Click to collapse
Try my recovery guide here
http://forum.xda-developers.com/showthread.php?t=2646279

sbdags said:
Try my recovery guide here
http://forum.xda-developers.com/showthread.php?t=2646279
Click to expand...
Click to collapse
Thanks so much! This is much more detailed than what I've been able to dig up anywhere else.
I will give this a try when I get home.

sbdags said:
Try my recovery guide here
http://forum.xda-developers.com/showthread.php?t=2646279
Click to expand...
Click to collapse
Thanks so much for the guide, was very easy to follow and appeared to work well, one question though.
I was able to follow the steps, the device seemed to have flashed ok (at least the .bat file didn't give me any errors, nor did anything appear out of the ordinary on the tab when it was going through the steps.
However, when I hold down vol down + power following happens:
"Key driver not found.. Booting OS" appears at the top left of the screen, along with 2 other lines regarding bootloader and firmware version info, and "starting fastboot USB download protocol" on another line.
Then I hit vol up on the RCK icon
"Booting recovery kernal image" appears on the top left of the screen.
The android appears and it says "installing system update" below it.
Within about 3 seconds the android changes to lying on his back with the red warning symbol above him with "Error!" below.
Any ideas what this is, or how to fix it? I know my tab still works okay because I can still load my old OS fine, but wondering how to get this working properly.
Thanks again for your help!

Deetrixx said:
TI was able to follow the steps, the device seemed to have flashed ok (at least the .bat file didn't give me any errors, nor did anything appear out of the ordinary on the tab when it was going through the steps.
However, when I hold down vol down + power following happens:
"Key driver not found.. Booting OS" appears at the top left of the screen, along with 2 other lines regarding bootloader and firmware version info, and "starting fastboot USB download protocol" on another line.
Then I hit vol up on the RCK icon
"Booting recovery kernal image" appears on the top left of the screen.
The android appears and it says "installing system update" below it.
Within about 3 seconds the android changes to lying on his back with the red warning symbol above him with "Error!" below.
Any ideas what this is, or how to fix it?
Click to expand...
Click to collapse
This is the stock recovery. Are you sure you followed step 6? (you must not hold volume-down at the *first* reboot directly after flashing the new recovery)

_that said:
This is the stock recovery. Are you sure you followed step 6? (you must not hold volume-down at the *first* reboot directly after flashing the new recovery)
Click to expand...
Click to collapse
I have it working now, I just followed all the steps again and this time it seemed to work fine. That must have been what I missed.
Thanks for your help! Let the fun begin!!!!

TF300T 4.2 TWRP Error

Hi XDA,
I am a complete noob, and this is my first time posting, so bear with me.
Some time ago I rooted and unlocked my TF300 with SuperSu. Recently I wanted to upgrade to 4.4 kitkat. However, my Tablet was stuck at Andriod 4.1 because of the the unlock.
I went to manually update my TF via the Asus website. I installed the 10.6.1.8 using my TWRP 2.5, and Oem 4.1 OS. Installation worked just fine. After install, I booted up and I had 4.2 with everything working correctly.
Next step was to install TWRP 2.7.0.1. I reset my TF and went into RCK to see something went wrong when updating.
My TWRP will not load, and I get the Android on his back with the red triangle when I try to enter RCK.
Thanks in advance!!

I managed to install 10.6.1.27, but it did not change anything with my boot loader.
I downloaded motochopper, but that didn't seem to work, just told me my abt was out of date. SuperSu isn't working now either, "No Binary, There is a problem."
How do I install TWRP 2.7 with no boot loader? Please help.

TallMilk said:
I managed to install 10.6.1.27, but it did not change anything with my boot loader.
I downloaded motochopper, but that didn't seem to work, just told me my abt was out of date. SuperSu isn't working now either, "No Binary, There is a problem."
How do I install TWRP 2.7 with no boot loader? Please help.
Click to expand...
Click to collapse
Most people just install TWRP via fastboot like
Code:
fastboot -i 0x0B05 flash recovery twrp.blob
You could try using other root methods, like Framaroot or Kingo. I think Kingo was reported to work on the latest stock version.

cmendonc2 said:
Most people just install TWRP via fastboot like
Code:
fastboot -i 0x0B05 flash recovery twrp.blob
You could try using other root methods, like Framaroot or Kingo. I think Kingo was reported to work on the latest stock version.
Click to expand...
Click to collapse
I will look into that, but I am pretty sure I was already rooted, unless losing my boot loader means I am no longer rooted.
Another thing, I can't find a twrp.blob for 2.7, just a zip. I have one for 2.5, but that is useless because I already have 4.2. I also have not been able to find a working link to fastboot.
If anyone could give me a link to the fastboot or a link to a tutorial, that would be amazing. I have done my research, but all the lingo and different methods can be mind bending.
Thanks

TallMilk said:
I will look into that, but I am pretty sure I was already rooted, unless losing my boot loader means I am no longer rooted.
Another thing, I can't find a twrp.blob for 2.7, just a zip. I have one for 2.5, but that is useless because I already have 4.2. I also have not been able to find a working link to fastboot.
If anyone could give me a link to the fastboot or a link to a tutorial, that would be amazing. I have done my research, but all the lingo and different methods can be mind bending.
Thanks
Click to expand...
Click to collapse
You can get the img (which substitutes as a blob) from extracting it from the TWRP 2.7 zip file.
1) You will need ADB and fastboot for this: http://forum.xda-developers.com/showthread.php?p=42407269. I would suggest keeping the tablet at least at 50% battery.
2) Install Naked Drivers. This may be optional for you. If you can proceed to the next step without, you won't need it.
3) Enter fastboot by rebooting and holding down the power button. TF300 enters fastboot automatically since this is 4.2 BL.
4) Next we need to enter a command. In side the ADB folder, hold shift and right click. Then select Open command window here.
first check to make sure the device is connected:
Code:
fastboot devices
The device serial number should be listed.
enter command:
Code:
fastboot flash recovery twrp.img -i 0x0b05
Blue bar on device will fill. Be patient.
5) Reboot the Device back into Android. This is an important step.
6.) Go back into TWRP and install what you want.

You are amazing. I will give it a try tonight and report back!

cmendonc2 said:
You can get the img (which substitutes as a blob) from extracting it from the TWRP 2.7 zip file.
1) You will need ADB and fastboot for this: http://forum.xda-developers.com/showthread.php?p=42407269. I would suggest keeping the tablet at least at 50% battery.
2) Install Naked Drivers. This may be optional for you. If you can proceed to the next step without, you won't need it.
3) Enter fastboot by rebooting and holding down the power button. TF300 enters fastboot automatically since this is 4.2 BL.
4) Next we need to enter a command. In side the ADB folder, hold shift and right click. Then select Open command window here.
first check to make sure the device is connected:
Code:
fastboot devices
The device serial number should be listed.
enter command:
Code:
fastboot flash recovery twrp.img -i 0x0b05
Blue bar on device will fill. Be patient.
5) Reboot the Device back into Android. This is an important step.
6.) Go back into TWRP and install what you want.
Click to expand...
Click to collapse
Installed adb fastboot. However, my device does not automatically go into fastboot, I still have to hold down the volume key.
Once I am in fastboot usb (with the 3 icons), I fastboot successfully and get the serial number, then when I type the 'fastboot flash recovery twrp.img -i 0x0b05' command I get this error: cannot load 'twrp.img' : No error
I am attemping to use the 2.7.0.1 twrp from the 4.4.2 page. I have extracted the recovery.img (tried renaming to twrp and left it the same) and placed it in the root of both my external and internal sd.
I have now tried it with .zips .img .blob and I receive the same error everytime. Not sure what I am doing wrong now.

TallMilk said:
Installed adb fastboot. However, my device does not automatically go into fastboot, I still have to hold down the volume key.
Once I am in fastboot usb (with the 3 icons), I fastboot successfully and get the serial number, then when I type the 'fastboot flash recovery twrp.img -i 0x0b05' command I get this error: cannot load 'twrp.img' : No error
I am attemping to use the 2.7.0.1 twrp from the 4.4.2 page. I have extracted the recovery.img (tried renaming to twrp and left it the same) and placed it in the root of both my external and internal sd.
I have now tried it with .zips .img .blob and I receive the same error everytime. Not sure what I am doing wrong now.
Click to expand...
Click to collapse
Put the twrp.img into your ADB folder, where you installed it. Then run the next command.

cmendonc2 said:
Put the twrp.img into your ADB folder, where you installed it. Then run the next command.
Click to expand...
Click to collapse
Awesome! Worked like a charm. twrp 2.7.0.1 installed perfectly.
Then I tried to flash the cyanogenmod. Said it installed fine, but it just gets stuck on the loading screen...

I am trying to do exactly what TallMilk is doing...put Cyanogenmod on my tablet. It is my understanding that I have to unlock my bootloader though? Which I have tried doing a million different ways with the Asus Unlock tool which always gives me an error.
If I follow the instructions posted above I will be able to flash Cyanogenmod without unlocking my bootloader?

SilentSpartan said:
I am trying to do exactly what TallMilk is doing...put Cyanogenmod on my tablet. It is my understanding that I have to unlock my bootloader though? Which I have tried doing a million different ways with the Asus Unlock tool which always gives me an error.
If I follow the instructions posted above I will be able to flash Cyanogenmod without unlocking my bootloader?
Click to expand...
Click to collapse
Finally got it to work. I had to do a wipe first, read about old roms interfering with new installations.
SilentSpartan, I used SuperSU last year to root and unlock my tablet when it was still a 4.0 android to flash to 4.1. This recent update was from 2.5 TWRP on a rooted device running 4.2. When I installed 4.2, it blew away my TWRP, and I had to flash the new TWRP 2.7.0.1.
That flash from OEM fastboot to TWRP 2.7.0.1 is what I needed help with.

TallMilk said:
Finally got it to work. I had to do a wipe first, read about old roms interfering with new installations.
SilentSpartan, I used SuperSU last year to root and unlock my tablet when it was still a 4.0 android to flash to 4.1. This recent update was from 2.5 TWRP on a rooted device running 4.2. When I installed 4.2, it blew away my TWRP, and I had to flash the new TWRP 2.7.0.1.
That flash from OEM fastboot to TWRP 2.7.0.1 is what I needed help with.
Click to expand...
Click to collapse
Damn, so I'm screwed. Why does Asus have to such so much...? You can no longer unlock afaik.

SilentSpartan said:
I am trying to do exactly what TallMilk is doing...put Cyanogenmod on my tablet. It is my understanding that I have to unlock my bootloader though? Which I have tried doing a million different ways with the Asus Unlock tool which always gives me an error.
If I follow the instructions posted above I will be able to flash Cyanogenmod without unlocking my bootloader?
Click to expand...
Click to collapse
You're going to have to unlock no matter what. Did you try both v7 and v8 of the unlocker and calling Asus Support to tell them to put your serial number back into the database (get a manager)?

cmendonc2 said:
You're going to have to unlock no matter what. Did you try both v7 and v8 of the unlocker and calling Asus Support to tell them to put your serial number back into the database (get a manager)?
Click to expand...
Click to collapse
I've tried every firmware and unlock tool combination. Nothing works. I sent them an email a day ago. Depending on there response, maybe I'll try calling. I'm so fed up with this tablet, I'm about to throw it out my window. $400 POS. :good:

SilentSpartan said:
I've tried every firmware and unlock tool combination. Nothing works. I sent them an email a day ago. Depending on there response, maybe I'll try calling. I'm so fed up with this tablet, I'm about to throw it out my window. $400 POS. :good:
Click to expand...
Click to collapse
Did you ever get your tablet fixed? I am having some problems myself after a miserable m9 update.

[Q]Stuck in bootloop with deleted OS, abd not working.

Hey all,
I have a big problem with my TF700.
I wanted to root my device after unlocking the bootloader through the app, but by being dumb I managed to delete the OS in TWRP (thought it was factory reset) and now I'm in big trouble.
The only thing the tablet loads now is the TWRP 2.2.1 recovery. (TWRP came with a root-package, I didn't install it myself.)
Since I can't load an OS that is apparently deleted, I'm stuck with using the (latest) SDK to get the stock rom back on the tablet.
The problem is, it doesn't work, at all. The device is recognised by my (Win7) PC and the 'adb devices' command gives me the ID and 'recovery'.
If I try to push the ROM to the Sdcard folder (or any folder, for that matter) It gives me a "protocol error" with no other explanation.
If I try to sideload it it is stuck on "Waiting for device".
I tried the 'shell' command, just to see what that does, but it also gives me an error.
Other commands can also give the the "error: closed" message.
Since both of those commands don't work, I can't get anything on this tablet, since I can't get this version of TWRP to mount an external (micro) SDcard, the option simply isn't there.
Can anyone help me with this, of has my tablet been reduced to an expensive paperweight?

That's the problem with packages - you don't really know what's in it...
What root package did you use?
You have a very outdated recovery installed. I'm guessing here, since you didn't post your bootloader version and that's the first thing we need to know!
Can you still get into the bootloader?
Boot with Power and Volume Down buttons until you see the tiny script and post your bootloader version. Should be something like 10.6.1.....
Do NOT do anything else in recovery at this point!!!! If it is incompatible with your bootloader you could hard brick!
Once we know if you have fastboot access and what your bootloader version is, we can help you to flash the correct recovery in fastboot. With that installed it's a piece of cake to get you up and running.
But be patient! Don't do anything else you're not quite sure of!

*Update Below*
I believe the culprit was the 'Install recovery' method "Scott's Recovery install tool"
I tried a few but most didn't do anything. Every tool I tried comes from the xda forums and checked youtube videos explaining the steps.
If I boot using Volume down + power, nothing extra happens. I just see in the left hand corner "this device is unlocked", since I unlocked the bootloader using the ASUS app.
If I use the command adb reboot bootloader, it goes to TWRP 2.2.1.
Does this imply that I also deleted the bootloader?
Update: I deleted all drivers and software regarding the tablet from my PC and I installed the adb setup package from these forums and reinstalled the (universal?) driver package. This turned out to be a newer version of adb, and I actually managed to push a file to the tablet with no problems. I am reluctant to try anything else at the moment, since this whole ordeal had given me quite the scare (and the desire to learn more about this all)
Can anyone help me revive my tablet?

FooYoungHi said:
*Update Below*
I believe the culprit was the 'Install recovery' method "Scott's Recovery install tool"
I tried a few but most didn't do anything. Every tool I tried comes from the xda forums and checked youtube videos explaining the steps.
If I boot using Volume down + power, nothing extra happens. I just see in the left hand corner "this device is unlocked", since I unlocked the bootloader using the ASUS app.
If I use the command adb reboot bootloader, it goes to TWRP 2.2.1.
Does this imply that I also deleted the bootloader?
Update: I deleted all drivers and software regarding the tablet from my PC and I installed the adb setup package from these forums and reinstalled the (universal?) driver package. This turned out to be a newer version of adb, and I actually managed to push a file to the tablet with no problems. I am reluctant to try anything else at the moment, since this whole ordeal had given me quite the scare (and the desire to learn more about this all)
Can anyone help me revive my tablet?
Click to expand...
Click to collapse
Ok, good - you got adb working. The adb command to boot into the bootloader is
Code:
adb reboot-bootloader
Note the hyphen
Also I wonder if you pushed Power and Volume Down long enough. You should feel the tablet vibrate twice, then see some tiny script and 3 icons appear. That would be the bootloader menu and in it, you are in fastboot mode by default.
The next step would be to check if you have a fastboot connection.
The command for that is
Code:
fastboot devices
Read my guide on flashing a custom recovery and rom very carefully and follow the steps outlined to get TWRP 2.8.0.1 on your tablet.
Ask any questions you may have in that thread.
http://forum.xda-developers.com/showthread.php?t=2688891
Edit: Sorry, forgot that we have to determine your bootloader version first. So use the button combination or the adb command to boot into it and post it. Don't worry. I don't think you did anything to the bootloader - it's not that easy to mess it up...

Unfortunately, the adb code doesn't work, with or without the hyphen. The device will reboot, but will return to TWRP.
I've held down the Volume down+power button for more than a minute witout result. The device will just reboot after a while for as long as I'm holding it. I do see the screen flicker for a second.
I've also noticed, that after I push a file to the tablet, that after a reboot it loses the data I just moved.
After booting TWRP, when I look in the command line of TWRP, it tells me that it can't mount the 'system' , 'data' and 'cache' forders. (tw_mount)
And it specifically mentions (multiple times) that the /data folder failed to mount, giving the message "No such file or directory"
It seems I really managed to F'ed it up good...

My "force-boot-to-bootloader" kernel module might help you unbrick. Read this guide very carefully before you do anything:
http://forum.xda-developers.com/transformer-tf700/help/guide-t2853546

You people are my new heroes!
The last guide did the trick. The stock firmware is installed and I'm currently updating and installing all the apps.
Thank you all só much, you really saved me a ton of frustration.

Rooting new nexus 5 with 6.01

Android 6.0.1, build number MOB30H
I have a brand new nexus 5 that I want to root. Using ota, I accepted the system updates to 6.0.1 with the Android security patch of May 1, 2016. (not sure if that was a good idea or not but it's done now....). Now I want to root it with a twrp recovery.
Like most run of the mill users I've only rooted a device 2-3 times in my life, so my memory is rusty on how exactly to do it. I searched this forum and found many threads about this or that rooting problem which just confused me further. I know I need to unlock the bootloader and then flash a twrp recovery but I am not sure of the exact sequence of steps.
1. When I connect the nexus 5 to my windows pc using adb, it appears in Windows but the nexus 5 folder is empty. I have developer options available and usb debugging is on but I can't find where the mtp switch is.
2. Adb.
I have adb installed in Windows. The command "adb devices" returns the nexus 5 number unauthorized.
Don't know what "unauthorized" means or what to do about it.
I've done nothing further because I don't want to mess things up. Please help me resolve questions 1 and 2. Then, I presume I need to
A. unlock the bootloader
Fastboot command?
B. What's next?
Thanks for any help.

Two things, have you enabled developer options. Go to settings, about phone and tap build number 7 times. In developer options you can change USB configuration and you'll also need to enable OEM unlock. Then unlock and root your device per the guide in the general section.
Sent from my Nexus 9 using XDA Free mobile app

jd1639 said:
Two things, have you enabled developer options. Go to settings, about phone and tap build number 7 times. In developer options you can change USB configuration and you'll also need to enable OEM unlock. Then unlock and root your device per the guide in the general section.
Click to expand...
Click to collapse
Just to add,not to confuse him even more, there is no Oem unlock option for Nexus 5
Sent from my Alps Q10101 using XDA Labs

You need to connect the phone in fastboot mode, run the command "fastboot oem unlock:, accept the agreement using the volume and power buttons, reboot into fastboot mode, flash twrp, copy the latest version of supersu.zip to the phone's internal memory, and flash supersu.zip from twrp.
You can install TWRP and root without using ADB commands.

Yes I already had developer options working and also usb debug on.
Discovered that mtp is a problem in marshmallow. I finally got file transfer working.

audit13 said:
You need to connect the phone in fastboot mode, run the command "fastboot oem unlock:, accept the agreement using the volume and power buttons, reboot into fastboot mode, flash twrp, copy the latest version of supersu.zip to the phone's internal memory, and flash supersu.zip from twrp.
You can install TWRP and root without using ADB commands.
Click to expand...
Click to collapse
Thank you very much. That is very helpful.
I didn't know you could "install TWRP and root without using ADB commands". How do you do that?
BTW, I updated the new nexus 5 to marshmallow inadvertently. When I root I'll probably use a 5.1.1 image. Good idea?

Stevica Smederevac said:
Just to add,not to confuse him even more, there is no Oem unlock option for Nexus 5
Sent from my Alps Q10101 using XDA Labs
Click to expand...
Click to collapse
Yep, my bad. Sorry about that. My 5 crapped out and have the 5x now. Amazing how fast you forget things, lol.
Sent from my Nexus 9 using XDA Free mobile app

Download and flash twrp in fastboot mode: https://dl.twrp.me/hammerhead/twrp-3.0.2-0-hammerhead.img.html
Download supersu.zip and save it to the phone's internal memory: https://download.chainfire.eu/921/SuperSU/UPDATE-SuperSU-v2.65-20151226141550.zip
Boot the phone into fasboot mode, open a command prompt, type fastboot devices and press enter. If the device is recognized, you'll see the device's serial number. Unlock the bootloader by typing "fastboot oem unlock" and use the volume/power button to accept the agreement and unlock the bootloader. Unlocking the bootloader will wipe the phone's data and cache.
To install TWRP, boot the phone into fastboot mode, connect it to the computer, open a command prompt, and type "fastboot flash recovery name-of-TWRP-file,img" and press enter. After flashing, immediately boot into recovery using the power and volume buttons, and then flash supersu.zip.

Thank you so much audit13. I really appreciate your help.
One question if I may. Reading on the web about rooting the nexus 5 running marshmallow I came across a couple of sites that said I should download and flash "ElementalX kernel and SuperSU 2.52" in addition to supersu.
I've never had to install a separate kernel when I rooted in the past. I notice you don't add flashing a kernel either. Can I ignore flashing a special kernel?
Thank you so very much for your clear instructions.

Some root methods require a rootable kernel. The latest supersu should root mm.

Thank you. Ran into a problem. That's why people like me are afraid of rooting.
Bootloader is now unlocked. Thanks.
With the N5 in fastboot mode, I connected it again with the laptop.
From the laptop command prompt I ussued "fastboot devices" and it found the phone.
Problem:
1. Fastboot flash recovery.img
(I had renamed the twrp 3.0.2 img file to recovery. Img)
Result:
unknown partition 'recovery.img'
error: cannot determine image filename for' recovery.img'
Tried by downloading a fresh copy and using its original filename.
Same result.
What am I doing wrong?
Thank you.

Found my error. I forgot the word recovery.
I now flashed twrp successfully!
When I went to flash supersu I discovered that the supersu I had downloaded was no longer in download folder. Guess it got wiped. So I rebooted into system and will download it again. Hope that does not mess up things.
Edit:
All went well. Re-downloaded SuperSU, installed fine and I'm home free.
Thank you all, especially audit13. This is a nerve-wracking process for people who only do it rarely. Glad it is over. The rest is easy!

I spoke too soon. I believe I now have a boot loop? What I have is that the horizontal turning balls of marshmallow go around forever and never finish booting.
How do I exit from this?
So close, but not there!
Edit
I rebooted into twrp, deleted cache, davlik. Still in bootloop.
Deleted data. Still in bootloop.
Help.

Reflash the entire stock rom and start over.
Try the latest beta of supersu: http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133

Great you are still here.
Need more details.
You say reflash stock rom. Where do I get it? How do I get it into the phone? Do I flash it through twrp?

How to flash factory image: http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
Factory images are here: https://developers.google.com/android/nexus/ota#hammerhead

Thank you again. Will do.
I think I know what went wrong. After I flashed twrp the phone rebooted into system before I could stop it and I think I interrupted it somewhere to return to twrp to flash Supersu. Anyway, glad I didn't brick it. Thanks again for being there.
It's morning now and after a good night's sleep I'm less rattled. Will get breakfast and start again.

I'm going out with my wife for breakfast.
I haven't followed the marshmallow threads but I recall reading about lingering problems with marshmallow. I also like to use xprivacy and gravitybox. So I'm thinking of flashing the latest 5.1.1 instead of 6. Any thoughts?

I like both ROMs but my battery life seems a bit better on MM. I'm sticking with unrooted stock ROMs on all of my phones for now.
Being a "flashaholic" is tiring!

audit13, I know you know this but it was so simple to do (once you know how.....!). It took me the whole of 20 minutes, if that, to download the files, flash 5.1.1, flash twrp and install SuperSU. Makes you wonder why I had so much trouble before!
Well when you don't know the command syntax (forget to write which partition to flash to) and are frozen with fear that you will brick the phone, it is a scary process. Once I knew how, I breezed through it. Problem is that by the next time I need to do this, I will have forgotten how or will worry that the process has changed.
I just want to thank you more than I can say for helping and hanging in while I made my mistakes. I wish there was a way I could thank you with more than words. You were great!
P.S. This time I used the beta SuperSU. Don't know if it made any difference.