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

[deadcatsrule]

Yes, but the download does not have a folder called android-sdk-windows or platform-tools, unlike the one mentioned in the op, so when trying to set up adb I'm not sure what to put in command prompt

https://developer.android.com/studio/releases/platform-tools.html
Its about half way down
Sent from my Nexus 6 using XDA Labs

 

[ktmom]

Yes, but the download does not have a folder called android-sdk-windows or platform-tools, unlike the one mentioned in the op, so when trying to set up adb I'm not sure what to put in command prompt

Unless you need/want the full studio, google released stand alone versions of fastboot and ADB

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

 

[fueled]

first post gave me these links for cf root and twrp
are these latest ?
https://download.chainfire.eu/628/CF...amu-nexus6.zip

http://techerrata.com/browse/twrp2/shamu

 

[ktmom]

first post gave me these links for cf root and twrp
are these latest ?
https://download.chainfire.eu/628/CF...amu-nexus6.zip

http://techerrata.com/browse/twrp2/shamu

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

 

[HACK3DANDR0ID]

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]

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

 

[HACK3DANDR0ID]

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?

 

[ktmom]

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

 

[HACK3DANDR0ID]

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...

 

[ktmom]

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

 

[fueled]

@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]

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

 

[fueled]

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]

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

That's fine

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

 

[fueled]

That's fine

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

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

 

[ktmom]

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]

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

 

[phr0zen]

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?

 

[briandanforth1]

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.

 

[phr0zen]

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