27 replies to this topic

[SamuriHL]

WARNING: You assume all risk in following this guide.  Specifically it shows you how to unlock the bootloader and install root.  This MAY void your warranty.  Also these steps are potentially dangerous.  Know how to restore a factory image before starting.  As always....read, read again, read one more time™.

 

So you got yourself a new shiny Nexus 6, eh?  Congrats!  Now, how the hell do you get that thing setup properly?  Lollipop changes a few things.  

 

NOTE: http://www.droidrzr....-nexus-11-beta/

 

o) Install platform tools and make sure the directory with adb and fastboot are in your path

 

Process:

 

o) Take out of box

o) Charge

o) Boot up, skip through setup (don't bother with it)

o) Enable developer mode

o) Enable oem unlock command on developer mode menu

o) Boot to fastboot, connect to USB

o) fastboot oem unlock

o) Boot up, run through setup this time

o) Do whatever you need (restore apps, setup accounts, etc)

o) When ready, reboot to fastboot

o) ??

o) profit

 

TWRP:

 

You don't need to flash twrp.  If you need to use twrp, connect it to USB, drop it in fastboot mode, and:

 

fastboot boot openrecovery.img

 

(where openrecovery.img is the twrp image you downloaded)

 

When you reboot to system, TWRP will prompt you to install SuperSU if you're not rooted.  Slide the slider to install it and then install SuperSU from the play store.  Run it and allow it to update the su binary as needed.

 

Troubleshooting:

 

If you're having issues with ADB recognizing your new Nexus 6, see if this helps...

 

If you use Koush's universal ADB driver, the Nexus 6 may decide to use that as the ADB driver by default.  Ordinarily that's not a problem.  My guess, however, is that something has changed with 5.0 and the ADB interface as it most definitely does not work.  

 

o) Uninstall the universal ADB driver

o) Uninstall the Nexus 6 from device manager with the "delete driver" option checked

o) Toggle USB Debugging on the Nexus 6 (or unplug it, plug it back in...whichever)

o) Force it to use the Google USB driver from platform tools.  You may have to manually point it to the Google USB driver folder in the platform tools.

[rebretz000]

SOB..... can't believe I forgot unlocking will wipe all. Just to damn excited to get the Nexus 6, be able to port my Verizon number in, generate new number, and not have to pay Verizon a ETF.

[livinginkaos]

SOB..... can't believe I forgot unlocking will wipe all. Just to damn excited to get the Nexus 6, be able to port my Verizon number in, generate new number, and not have to pay Verizon a ETF.

You will always do it better and faster the second time around

Turbo Driven Comment

[soocold]

Not always true. I soft bricked mine on second power up

Sent from my Nexus 6 using Tapatalk

[livinginkaos]

Yeah and I was told it was my fault......

Turbo Driven Comment

[livinginkaos]

Heads up to anyone reading this.  Chainfire has a new root out that does not require patching the kernel.  It is best advised that you reflash the stock boot image before moving up to the 2.27 (or above since he is on a build a day recently) as it will conflict with the kernel mod.

[soocold]

Ahh. Well I gotta flash the update so that'll restore the og IMG

Sent from my Nexus 6 using Tapatalk

[SamuriHL]

Yes.

[rebretz000]

Has everyone restored original boot.img and flashed 2.27 beta? Cautious since he said high probability for boot loops.

[livinginkaos]

I haven't, but then I still don't have mine.....

It seems to be booting fine for most people.

Turbo Driven Comment

[SamuriHL]

I have.  No issues.

[soocold]

I will so hopefully no issues

Sent from my Nexus 6 using Tapatalk

[jayrod]

Gonna have to fastboot a few things so I'll know later. So far 2.7 is working fine.. Just gotta get rid of the phantom ota crap

Sent from a whale named Shamu

[matjmonk]

I haven't, but then I still don't have mine.....

It seems to be booting fine for most people.

Turbo Driven Comment

Neither do I and still showing the same Dec shipping dates .... snarl .... growl ...mutter ..

[matjmonk]

Has everyone restored original boot.img and flashed 2.27 beta? Cautious since he said high probability for boot loops.

I did this on the N7 (2013) and everything seems to be working quite well.

[JustAGuy]

Just remember to boot though to the system after oem unlock.

Don't flash TWRP until after you boot into the system, if you do, you will boot loop. The fix is to flash back the stock recovery.

[soocold]

Or! Leave a stock recovery and just boot into twrp from the PC akin to booting a PC from a USB jump drive. That's how Sam, jayrod, and I are using twrp

Sent from my Nexus 6 using Tapatalk

[SamuriHL]

Yup.  To me that's the better way as you don't have to screw around with your partitions at all.  Booting twrp in memory gives you all the access you need but leaves everything stock.  Love it.  Wished it worked properly on my S4.

[JustAGuy]

Or! Leave a stock recovery and just boot into twrp from the PC akin to booting a PC from a USB jump drive. That's how Sam, jayrod, and I are using twrp

Sent from my Nexus 6 using Tapatalk

I've got a couple of apps that want a custom recovery. From my understanding, they run scripts through TWRP.

I had to used TWRP more than a few times without a PC around. Its just more convenient for me to have it loaded.

Better have it and not need it than need it and not have it.

[SamuriHL]

Kids these days.    You keep both twrp and stock recovery img's on your internal memory.  Then use flashify to switch between them if you want to flash it for whatever reason.