[HOW-TO] The Nexus 6 All-In-One Beginner's Guide

Search This thread

deadcatsrule

Senior Member
Jan 3, 2014
415
202
Rochester,in
Last edited:
  • Like
Reactions: iosmonster

ktmom

Retired Forum Moderator
Apr 22, 2015
5,179
3,384
Deep Space Station K7

ktmom

Retired Forum Moderator
Apr 22, 2015
5,179
3,384
Deep Space Station K7

No, and this was answered in the other post you made. I did request you read the OP then go to page 84 in this thread and read through. It's as simple as flashing supersu or Magisk to root since lollipop.

Any one looking for cf-auto root is seriously out of date as to how root works currently. I strongly suggest reading either the SuperSu or Magisk threads to understand the modern systemless root method that modifies the kernel not system.

"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
 
Last edited:

HACK3DANDR0ID

Senior Member
May 25, 2017
1,157
323
42
New Jersey
Yea, i just ordered a brand new Google Nexus 6. I first had one when they came out. But they were on sale on Amazon for $219, so i ordered it as a Dev device, because my S9+ is LOCKED DOWN and wont be ever seeing root, anyway...

Should i OTA update all they way and then do everything in the 1st post. Not sure if Oreo made it too the N6 officially or not. My plans are too run Custom 8.1.0 ROMs. How would i make it that far, too Android 8.1.0, and do i need to upgrade the radio? A lot of the last flashing i did, you were required to be on a certain build to be able to run the Custom version of that Build...

Device should be here tomorrow or Sunday, just trying to set my bookmarks and download everything so i'm ready when it gets here.
 

ktmom

Retired Forum Moderator
Apr 22, 2015
5,179
3,384
Deep Space Station K7
Yea, i just ordered a brand new Google Nexus 6. I first had one when they came out. But they were on sale on Amazon for $219, so i ordered it as a Dev device, because my S9+ is LOCKED DOWN and wont be ever seeing root, anyway...

Should i OTA update all they way and then do everything in the 1st post. Not sure if Oreo made it too the N6 officially or not. My plans are too run Custom 8.1.0 ROMs. How would i make it that far, too Android 8.1.0, and do i need to upgrade the radio? A lot of the last flashing i did, you were required to be on a certain build to be able to run the Custom version of that Build...

Device should be here tomorrow or Sunday, just trying to set my bookmarks and download everything so i'm ready when it gets here.

Yes, update to the last (Oct 2017) release. For a oreo rom, you'll need the latest bootloader. I'm sure that radio will be fine as well. If not, you can search for the flashable radio zip thread for the N6.

In general terms, the first post will get you started for through recovery. Cf-auto root is no longer used (since 5.x). Rooting is as easy as flashing the root zip file in recovery. Go to page 84 in this thread and read forward.

If you are not familiar with systemless root , there are threads on xda explaining why it's now the boot img that gets modified and not system.

"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
 
  • Like
Reactions: HACK3DANDR0ID

HACK3DANDR0ID

Senior Member
May 25, 2017
1,157
323
42
New Jersey
Yes, update to the last (Oct 2017) release. For a oreo rom, you'll need the latest bootloader. I'm sure that radio will be fine as well. If not, you can search for the flashable radio zip thread for the N6.

In general terms, the first post will get you started for through recovery. Cf-auto root is no longer used (since 5.x). Rooting is as easy as flashing the root zip file in recovery. Go to page 84 in this thread and read forward.

If you are not familiar with systemless root , there are threads on xda explaining why it's now the boot img that gets modified and not system.

"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers

I usually use Magisk for ROOT, i see on page 84, it is recommended to use suhide. Is Magisk working with this device?

*edit*

Also, in Post 1, he is rooting before he flashes TWRP. But beings we are not using CF Auto Root anymore, am i fastboot flashing TWRP first and then TWRP flashing Magisk or the latest SU?
 
Last edited:

ktmom

Retired Forum Moderator
Apr 22, 2015
5,179
3,384
Deep Space Station K7
I usually use Magisk for ROOT, i see on page 84, it is recommended to use suhide. Is Magisk working with this device?

*edit*

Also, in Post 1, he is rooting before he flashes TWRP. But beings we are not using CF Auto Root anymore, am i fastboot flashing TWRP first and then TWRP flashing Magisk or the latest SU?
It wasn't recommended to use supersu. That was the direction the person asking for help wanted to go. In that same post was written:
As a side note, this process is the same for Magisk. Just flash the Magisk zip in the fastboot loaded twrp recovery. I use Magisk primarily because the are some Magisk plug-ins that I like and it's brainless [emoji3]

Yes, flash root in TWRP.

Don't just read one post. You'll glean more understanding if you read through the rest of the thread.

"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
 
  • Like
Reactions: HACK3DANDR0ID

HACK3DANDR0ID

Senior Member
May 25, 2017
1,157
323
42
New Jersey
It wasn't recommended to use supersu. That was the direction the person asking for help wanted to go. In that same post was written:


Yes, flash root in TWRP.

Don't just read one post. You'll glean more understanding if you read through the rest of the thread.

"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers

After Reading since page 84 and doing some searching, i havent found anything on changing the Boot Loader, only changing the Radio. But if i update to the latest 7.1.1 (Oct 2017), wouldnt i already be on the latest BL to get myself to Oreo? BTW, i DLed the M Preview 2 radio, which im guessing you were referring too?

*edit*
Found BLs on Lineage 15.1 page, my bad...
 
Last edited:

ktmom

Retired Forum Moderator
Apr 22, 2015
5,179
3,384
Deep Space Station K7
After Reading since page 84 and doing some searching, i havent found anything on changing the Boot Loader, only changing the Radio. But if i update to the latest 7.1.1 (Oct 2017), wouldnt i already be on the latest BL to get myself to Oreo? BTW, i DLed the M Preview 2 radio, which im guessing you were referring too?

*edit*
Found BLs on Lineage 15.1 page, my bad...
You don't need to do anything more than fully upgrade to the latest release. That will give the latest bootloader, radio and OS. Once that is done you're good to go to an Oreo ROM.

Don't make this hard on yourself [emoji6]

"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
 
  • Like
Reactions: HACK3DANDR0ID

fueled

Senior Member
Aug 20, 2010
642
151
@ktmom since you have helped me alot in my journey from unlocking bootloader to rooting to custom 8.1 rom

so i thought its better to ask you this question which is confusing me.
actually i have read somewhere that magisk must be flashed after the kernel ... so i want to update my kernel and iam already rooted, what will be better procedure. and do we need to wipe cache and dalvik cache in updating the kernel ?

Sent from my Nexus 6 using Tapatalk
 

ktmom

Retired Forum Moderator
Apr 22, 2015
5,179
3,384
Deep Space Station K7
I am very old school and always flash root (Magisk) again after flashing a different kernel.

I'm sure you have figured this out, but for anyone else who finds this post, the kernel is the boot.img that systemless root modifies. When flashing Magisk in recovery, the original boot.img is backed up and saved before being modified.

The worst that happens is on reboot, the device is not rooted and you then go back to recovery and flash root again.

It does get confusing. There is a script in the system/addon.d directory that reinstalls Magisk (open gapps tends to put scripts there also as well as others). So it's possible b to get away with not flashing Magisk and have everything be fine on boot. This is why you'll see confusing posts.

"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
 
Last edited:
  • Like
Reactions: fueled

fueled

Senior Member
Aug 20, 2010
642
151
I am very old school and always flash root (Magisk) again after flashing a different kernel.

I'm sure you have figured this out, but for anyone else who finds this post, the kernel is the boot.img that systemless root modifies. When flashing Magisk in recovery, the original boot.img is backed up and saved before being modified.

The worst that happens is on reboot, the device is not rooted and you then go back to recovery and flash root again.

It does get confusing. There is a script in the su.d directory that reinstalls Magisk (open gapps tends to put scripts there also as well as others). So it's possible b to get away with not flashing Magisk and have everything be fine on boot. This is why you'll see confusing posts.

"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
so its gonna be like this ?
1. flash new kernel
2. flash magisk
3. wipe cache wipe dalvik
4. reboot

Sent from my Nexus 6 using Tapatalk
 

ktmom

Retired Forum Moderator
Apr 22, 2015
5,179
3,384
Deep Space Station K7
cool guide . i have updated my kernel.
thanks alot

now this coming sunday iam gonna disturb you again to guide me how to disable encryption :)
That ones easy.

Do a backup of the user data partition.

Make sure your using a kernel that does not force encrypt.

Then boot to fastboot and wipe the user data partition:
fastboot erase userdata

On the next boot, the partition will be decrypted. You can restore the backed up data and it will still be decrypted.

This works because wiping the partition removes the flag for encryption. On a stock rom/kernel (or custom kernel that still force encrypts), the next boot the flag is restored and you're encrypted again.

"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
 

fueled

Senior Member
Aug 20, 2010
642
151
That ones easy.

Do a backup of the user data partition.

Make sure your using a kernel that does not force encrypt.

Then boot to fastboot and wipe the user data partition:
fastboot erase userdata

On the next boot, the partition will be decrypted. You can restore the backed up data and it will still be decrypted.

This works because wiping the partition removes the flag for encryption. On a stock rom/kernel (or custom kernel that still force encrypts), the next boot the flag is restored and you're encrypted again.

"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers

i did as you said.
backed up my phone
then went into bootloader connected to pc and gave command fastboot erase userdata then rebooted
now my phone went into bootloop i think.
when booting its going into recovery but showing some errors with redlines and restarting itself again and again
what to do now


Edit. I reflashed twrp and then was able to boot into recovery and wipe cache and dalvik. Then rebooted successfully into OS and checked iam not encrypted anymore
 
Last edited:
  • Like
Reactions: ktmom

phr0zen

Senior Member
May 24, 2009
527
109
OnePlus 7 Pro
Ok... I'm going to preface this by apologizing and I'm on a Mac. First of all I am not familiar with Mac's, and secondly, I have never done ADB or Fastboot to my knowledge. Either that or its been years ago and I do not remember doing any of this.

Ok with that out of the way, I'm thoroughly confused as to what's going on here. heres a list of things I've tried:
made sure I was in debug mode
downloaded the command line SDK
tried to open the Android command prompt as instructed in a video to download platform tools - nothing
downloaded standalone platform tools
rebooted to bootloader, plugged in phone, ran ./adb devices - nothing
bootloader is already unlocked, when down that route again just to make sure (it did not delete anything)
dragged the files from the tools folder to the platform toold foler since they were supposed to have been installed anyway... same thing with ./adb devices. none listed.

Is there any way someone would direct me to the resources needed without having to say "well the OP is outdated, go here to page ###" then when I get there I'm redirected to another site that has different commands?
 
Feb 21, 2017
26
2
Ok... I'm going to preface this by apologizing and I'm on a Mac. First of all I am not familiar with Mac's, and secondly, I have never done ADB or Fastboot to my knowledge. Either that or its been years ago and I do not remember doing any of this.

Ok with that out of the way, I'm thoroughly confused as to what's going on here. heres a list of things I've tried:
made sure I was in debug mode
downloaded the command line SDK
tried to open the Android command prompt as instructed in a video to download platform tools - nothing
downloaded standalone platform tools
rebooted to bootloader, plugged in phone, ran ./adb devices - nothing
bootloader is already unlocked, when down that route again just to make sure (it did not delete anything)
dragged the files from the tools folder to the platform toold foler since they were supposed to have been installed anyway... same thing with ./adb devices. none listed.

Is there any way someone would direct me to the resources needed without having to say "well the OP is outdated, go here to page ###" then when I get there I'm redirected to another site that has different commands?

I know that a Nexus 6 program for Mac was floating around somewhere. I don't know about the quality or reliability of it though. I'll see if I can find it on here

EDIT: I'm using the XDA Labs app and don't know how I can link you to the thread. You can find it on your own though if you just go through the Nexus 6 Android Development forum here on XDA.
 
Last edited:

phr0zen

Senior Member
May 24, 2009
527
109
OnePlus 7 Pro
I know that a Nexus 6 program for Mac was floating around somewhere. I don't know about the quality or reliability of it though. I'll see if I can find it on here

EDIT: I'm using the XDA Labs app and don't know how I can link you to the thread. You can find it on your own though if you just go through the Nexus 6 Android Development forum here on XDA.

Ok thank you, I'll sift through and see what I can find. Basically if I can get TWRP back on it I'll be home free. As it stands now I can't boot to recovery or use the TWRP app to flash anything.

Edit: tried it at work on Windows with no success. Downloaded the stand alone ADB and Fastboot. Tried other options when the USB cord is plugged in (file transfer, PTP, etc). The command "adb devices" still shows nothing is plugged in.

Could it be my cord? I've tried 7 different ones lol
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 213
    2d1of9s.jpg


    Welcome to the Nexus 6 All-In-One Guide. If you are a new user that is looking for the opportunity to take advantage of your device and do it right the first time, this guide is here to point the way. This thread exists to keep all the necessary methods and material in one common place just for you. As always: Do your homework first.

    If followed correctly, this guide can be a useful tool. These steps are listed in the order in which they should be completed. The intent is to seamlessly unlock, root, backup and/or flash, leaving as little room for error as possible. This process will erase and/or reset everything on your device. All steps are assuming you have backed up your contacts, texts, pictures, videos, etc. I do not take credit for any of this material or information.
    This guide is a compilation of work from across XDA, most specifically users like @Chainfire and @Chromium, that I have simply brought together.


    icon-checkmark-small.png
    Step 1: Read. Read. Succeed.


    Your journey down the Android path of rooting and modifying can be smooth, fun and educational, based on your attempt at learning everything you can before you begin. This is entirely up to you, the user. There is some excellent material here on XDA that I highly recommend reading over as part of step 1. Even though these 2 informational links were written for the Nexus 5, the knowledge still applies so don't skip this information!

    A message from the moderators - All users please read
    Yep, read it. It's for your own good. Included with some very useful general forum information, it also contains the forum rules which should also be read and understood.

    [FAQ][REF]★All you need to know about Android | Read this before you post/root★
    This awesome thread by @abaaaabbbb63 is a *noob friendly* collection of information every user that wants to root their phone should know. Many people blindly follow guides without even knowing what "Rooting" means. Hopefully, this will help new users (and old ones, why not?) understand what is happening with their phone, and what they will put up with. Get on over there and read it.

    Be sure to checkout Post #2 below for additional information regarding your Nexus 6


    icon-checkmark-small.png
    Step 2: Installing The Necessary Desktop Tools


    ADB and Fastboot Installation
    1. Download the full Android SDK here (scroll to the bottom of the page>DOWNLOAD FOR OTHER PLATFORMS>SDK Tools Only).
    2. Extract the zip and place the android-sdk-windows folder on your desktop.
      **If you chose to download the slimmed sdk skip to step 5**
    3. Only if you downloaded the full sdk: Go into the android-sdk-windows folder and run SDK Manager.exe. Install the following packages (there are a total of 4 packages):
      - Tools > Android SDK Tools, Android SDK Platform-tools
      - Extras > Android Support Library, Google USB Driver

    4. Only if you downloaded the full sdk: Go back into the android-sdk-windows directory, and you should see a new folder named platform-tools. If you don't see this new folder, repeat the step above.
    5. To confirm that it is indeed working, open a command prompt window and enter the following commands:
      Code:
      cd Desktop/android-sdk-windows/platform-tools
      adb version
      If it displays "Android Debug Bridge version x.x.xx" it is working. If it is gives an error saying that adb is not a recognized command, it has not been successful. Carefully repeat the steps above if this is the case. Close the command prompt window when you are done.

    icon-checkmark-small.png
    Step 3: Unlock, Root & Custom Recovery


    For those of you who want to get most out of your Nexus 6, you will certainly want to root it. Rooting your device provides you as the user many, many benefits. That's why you're here right now reading this. You want it all. Please note that there is always the chance of error during these processes. Bad or faulty USB cables, USB ports, bad/old device drivers on the computer, an active virus scanner. These are a few of the issues that can cause your device to fail to connect or prohibit a successful root/flash. Use good and original OEM USB cables. Uninstall any drivers you may have installed for previous mobile devices and disable your virus scanner.

    >>>>>>Before you begin, make sure your N6 has USB Debugging Mode switched on<<<<<<
    Before continuing, users must enable Developer Options in the devices settings and select the OEM Unlock option. To do so:

    - Go into Settings
    - Under About Phone, you'll be able to locate your Build Number
    - Tap Build Number until you are notified that you have activated Developer options
    - Go into Developer Options, ensure it is enabled and check the Enable OEM Unlock box
    - While in Developer Options, ensure the USB Debugging box is checked

    Unlock The Bootloader
    • Turn the phone off. Then boot it into the bootloader/fastboot mode by holding volume down + power.

    • Plug the phone into your PC, then open a command prompt window window and type:
      Code:
      cd Desktop/android-sdk-windows/platform-tools
      Code:
      fastboot devices
      This command will list the connected devices. If your phones serial number shows up you are good to go and may continue. If the phone is NOT listed this indicates that your drivers are not installed correctly. In order for you to continue you must fix your drivers so that your phone is listed under fastboot devices.

    • If the phone has been recognized by the command above, proceed to unlocking the bootloader with the following command:
      Remember that this step will wipe EVERYTHING off the phone
      Code:
      fastboot oem unlock
      On the phone a screen should pop up asking whether or not you would like to unlock the bootloader. Use the volume rockers to highlight "Yes" then press power to confirm the action.

    • After the above command has finished executing, run the following (DO NOT skip this step, it is more important than you think):
      Code:
      fastboot reboot
      The phone will reboot. Next you will be presented with a screen containing an android logo and a progress bar (this may take up to ten minutes to complete). Wait until the phone has fully booted up into android, then proceed onto the next section of the guide.

    • Close the command prompt window.

    Obtain Root
    The instructions below and the zip file are the work of our beloved @Chainfire. CF-Root is the root for "rooting beginners" and those who want to keep as close to stock as possible. CF-Root is meant to be used in combination with stock firmware and be the quickest and easiest way for your first root.

    - Download the ZIP file
    - Extract the ZIP file
    - Boot your device in bootloader/fastboot mode. Usually this can be done by turning your device off, then holding VolUp+VolDown+Power to turn it on.
    - Connect your device to your computer using USB

    - Windows:
    --- Run root-windows.bat

    - Linux
    --- chmod +x root-linux.sh
    --- Run root-linux.sh

    - Mac OS X
    --- chmod +x root-mac.sh
    --- Run root-mac.sh

    Follow the on-screen instructions - watch both the computer and the device!

    **If you want to have root access only you can stop here.**​


    A word on custom recoveries: A recovery image is the system level software for your Android that lets you perform several maintenance and recovery tasks. The stock recovery image is quite limited in what it allows you to do and therefore, flashing a custom recovery image is required to gain full control of your device’s administration. A custom recovery image allows you to perform the following tasks:

    - Wipe your phone’s data (Factory reset) and cache
    - Make, restore and manage backups of your phone’s operating system and software
    - Mount, unmount and format your phone’s internal as well as external storage partitions
    - Install a custom ROM or application from a zip file to your phone
    - Wipe Dalvik cache and battery statistics
    - Make logs for error reporting and debugging


    Additionally, you can download the Goo Manager app to install TWRP updates.
    *NOTE: I do not recommend Rom Manager as a tool to do anything but just install and/or update your recovery Do not flash ROMs from this application.

    Installing A Custom Recovery

    Go HERE to download the latest TWRP recovery for the Nexus 6.

    • Turn the phone off. Then boot it into the bootloader/fastboot mode by holding volume down + power.

    • Rename the recovery file that you downloaded above to recovery.img. *Make sure that you rename it to recovery.img NOT recovery.img.img* Remember that you should place the file in the platform-tools folder inside of the android-sdk-windows folder on your desktop.

    • Open command prompt and run the following commands:
      Code:
      cd Desktop/android-sdk-windows/platform-tools
      Code:
      fastboot flash recovery recovery.img

    • On the phone, use the volume buttons to scroll onto "Restart Bootloader" and hit power to select it. After the bootloader reloads, use the volume buttons to scroll onto "Recovery Mode" and power to select it. You should then be greeted with your newly installed custom recovery.
    • Close the command prompt window.


    icon-checkmark-small.png
    STEP 4: Making A Backup

    Making a Nandroid will allow you to try out new ROMs while still keeping a safe backup in the event you experience issues during or after a custom OS or kernel installation. Be sure your device is fully charged before proceeding to the backup and flashing procedures.

    If you are not already booted into recovery then do so now.

    1. Boot into fastboot mode (Volume Down + Power)
    2. Browse with the volume keys to Recovery Mode and press the power button
    3. You are now in custom recovery.
    4. In CWM go to Backup and Restore and select Backup. In TWRP select Backup. Name and select the options you want. Swipe to backup.
    5. In TWRP, go to Backup and proceed to the next step(s).
    6. After backup is finished, select reboot system now or stay in recovery to continue with this guide.


    *NOTE: Be sure to save a copy of these backups to your computer and/or micro sd card. Having a recent backup saved to your computer and micro SD card can be useful if something happens to your phones internal memory.


    icon-checkmark-small.png
    Step 5A: Wiping Your Device


    When flashing any ROM, it is always important to follow the proper wipe procedures in order for everything to function properly. There are various levels of wiping based on what sort of transition you may be making. In this guide, I will list the procedures for a full wipe, presuming that you are coming from the stock firmware and changing your OS completely. This is all assuming you have made the appropriate backups. ALWAYS perform the appropriate wipe before flashing a new ROM or update!

    1. If you are not already in recovery, boot in now.

    In CWM:
    2. Select Wipe data/factory reset
    3. Select Wipe Cache
    4. Select Advanced and Wipe Dalvik Cache
    5. Select Mounts and Storage and format /system
    6. If you are transitioning from Android versions (4.4 to 4.x, etc) you must also format /data. You will lose all personal data so back it up first.

    In TWRP:
    2. Select Wipe
    3. Select Factory Reset and wipe
    4. Select System and wipe
    5. If you are transitioning from Android versions (5.0 to 5.x, etc) you must also select Wipe Data and wipe. You will lose all personal data so back it up first.


    icon-checkmark-small.png
    Step 5B: Flashing a Custom ROM


    Once you have selected a ROM for your Nexus 6:

    1. Download the ROM. Be sure to download the appropriate Gapps as well.
    2. From your PC, place the ROM/Gapps on your internal storage. Remember where they are.
    3. Boot into custom recovery.
    4. Perform the wipe listed above if you have not already.
    5. From the main recovery screen:
    >>CWM - Choose the "install .zip from SD Card" and confirm.
    >>TWRP - Choose Install and locate the desired ROM on your internal storage.
    6. Repeat step 5 and select the Gapps package.
    7. Reboot system. It will take several minutes to load so be patient and don't worry. Once the phone is booted, let it sit for 5 minutes, reboot and enjoy!
    40
    >>Additional Information

    Want the performance boost available with disabling forced encryption? Check out @bbedward's guide linked below for more information and instructions.
    [How-To] Disable Forced Encryption

    Running Windows 8.x and having device detection issues? Be sure to grab the Google USB drivers and follow the instructions from the link below.
    Nexus 6 Driver (ADB, Fastboot and MTP) for Windows and MAC

    Need to return your Nexus 6 to stock for resale, OTA or warranty purposes?
    Checkout @Mr hOaX's excellent guide. The procedures require the use of the fastboot tool from the Android SDK. See post #1 above for information on installing this if you have not done so already. In his guide, you have the option of returning completely to stock or select specific portions to flash (radio, recovery, etc).
    [Guide][How To] Flash Factory Images For Nexus 6

    Looking for stock recovery? If you need to revert to stock to receive an OTA, here's the LRX22C Android recovery:
    Unzip the image and flash per the norm in fastboot.
    View attachment recovery.zip
    7
    Great guide for noobs and people who are rusty with adb because they've had Samsung Galaxy devices for the last 4 years. Lol

    Thanks xBeerdroiDx. :highfive:
    5
    No need for toolkit or drivers on Mac/Linux

    Here's Mac/Linux way.

    First create a file on your home folder named something like nexus 6. (This is where your going to save your files.)

    Download su(I'll let op point to zip)

    Download recovery (same as above from op)

    Put them both in that file you created. (Make sure it is in home or you'll have to cd to wherever you put it)

    OK make sure you back up your data(this will wipe everything.)

    Boot into fastboot.
    (Hold power and up/down button)
    (Ensure you have adb and fastboot installed on your comp)

    cd RootNexus (or whatever you named that folder you created)

    *First things first...

    ./fastboot devices

    Should see your device.(if not double check adb and fastboot are installed properly. Follow link. http://forum.xda-developers.com/showthread.php?t=1917237(make sure to click thanks button over there for easy setup.)

    .



    ./fastboot oem unlock

    (Follow on screen instructions, this will wipe data. )

    ./Fastboot restart bootloader.

    (Linux users remove ./ in front of fastboot.)

    Start up phone and sign in and let it completely boot. Then put SuperSU on device.

    On your Mac/Linux
    (Ensure you are still in root nexus folder)

    ./fastboot flash recovery recovery.img where recovery.img is the name of your recovery image file

    Once that is done on your phone press the volume up (twice) until you see "Recovery". Then press the power button.*

    Once inside recovery go to back up and back up your device.

    Flash SuperSU after. Then restart and applaud yourself. Your now rooted. I've been doing it this way since forever
    5
    Added. Thanks for catching that, @Kusanagi Fire :good: