yashsingh1/xdaforums huggingface dataset:
[Nexus 6P General] grimpow:
Android SDK Tools 24.4.1

Android SDK Platform-tools 21.1

Android SDK Build-tools 23.0.2

SDK Platform (API 23, Rev. 2)

Sources for Android SDK (API 23, Rev. 1)

Android Support Library 23.1.1
[Nexus 6P General] Heisenberg:
Minimal fixed your issues with

this device

? It's known to do the opposite with this phone.
[Nexus 6P General] azsl1326:
No, not with this device. I have had issues where running 'adb' + command simply returned a list of acceptable commands. This fixed it . Apologize if I steered him in the wrong direction.
[Nexus 6P General] grimpow:
Things like minimal aren't an option anyway (Linux user)
[Nexus 6P General] techbeck:
Ok, been a long day so bear with me....

I am looking at the OP and steps 10 and 11. I want to apply the 6.0.1 update but the steps in 10 and 11 look to be the same. Last time I flashed the following, I lost all my apps, settings, and had to go through the setup again.

My SD card remained in tact tho but curious if I flash what is in the code box on #10 in the app, will all my apps be gone? If so, there a way I can get the 6.0.1 update and keep my installed apps and settings?
[Nexus 6P General] Heisenberg:
As long as you don't flash/format userdata your apps, settings, and data will remain intact.
[Nexus 6P General] hapticxchaos:
Hello,

When I run "fastboot flashing unlock" I just get a list of commands, I never get the unlock screen on the phone. I am doing from Linux on a Chromebook. I tried updating ADB and fastboot, and no luck. Any suggestions?
[Nexus 6P General] Heisenberg:
What's your adb version? How did you install adb/fastboot?
[Nexus 6P General] hapticxchaos:
THanks for your quick reply

I also suspected by ADB version, so I made sure to update. It is now 1.0.32. I hope thats the latest. I installed with standard apt-get install, I think it was off webupd8s repository.

Regards
[Nexus 6P General] Heisenberg:
That is the latest, but you really need the other components of the SDK for it to work properly. Visit the prerequisites section at the beginning of the guide to install it via the SDK. Please note that on Linux you won't find SDK Manager, it's called Android once you extract the archive.
[Nexus 6P General] techbeck:
Worked great....thanks!
[Nexus 6P General] ridobe:
Did you get this sorted out? I saw you were a Linux user. I struggled mightily with this. All you have to do is precede the command with ./ from the folder of course.

For some reason $PATH isn't recognized with this.

---------- Post added at 05:59 PM ---------- Previous post was at 05:52 PM ----------

See my post above. See if that helps.
[Nexus 6P General] Mesmurized:
Can I take an OTA with just an unlocked bootloader, everything else stock? IE: Is an unlocked bootloader considered a system modification?
[Nexus 6P General] grimpow:
I did get it sorted, $PATH eventually worked for me. I found that I did actually have to reboot after modifying .bashrc, which I didn't do at first. I really should have though of that sooner, but these things happen haha. It's odd to me though, that I could use some commands before reboot, but not all. Just glad it got sorted.

Like Heisenberg said, even if that seems to be the latest, you are much better off to install via the SDK. I myself have tried the platform-tools available in the AUR, and even though they seemed to be latest versions, they do not work. You must open the file called Android inside that SDK zip (inside tools folder), and be sure to install platform-tools and build-tools from there. After that, open up .bashrc inside your home folder. At the end of the file, add these two lines.

export PATH="$HOME/Android/tools:$PATH"
export PATH="$HOME/Android/platform-tools:$PATH"

And then reboot. Hopefully that helps, since it seems you're running into the same problem I was.
[Nexus 6P General] shmeeks:
Android Debug Bridge version 1.0.31

Edit:

& this worked for me, thanks! Weird I didn't have to do ./ when unlocking.
[Nexus 6P General] pcoiner:
Systemless root reduced disk space to 24G

Hi

I hope it is ok to post this here (If not I apologize profusely) I want to document my travails in the hopes of saving someone else grief.

When I followed the instructions "6. How To Root – Systemless" and tried the systemless root example.

It would work, I was rooted, but my new phone I ordered with 128G would only show 24G in the Settings->Storage & USB tab.

Whilst in the boot-loader it would show that the phone did indeed have the 128G that I ordered from Google.

The way I fixed it got it back to the original state i.e. all my storage back was to run the fastboot -w update image-angler-mmb29m.zip.

I think the -w option was what did the trick

Here is what the fastboot help says "Erase userdata and cache (and format if supported by partition type). "

BTW i did the second part (Convert systemless root method into what (for all intents and purposes) is a traditional system root) but that didn't help

If anyone could explain how I got in this sorry state I would be very grateful to be a little less ignorant.

So next I did the ole step 7 "How To Root - Traditional"

But it is not obvious to the uninitiated and the stoopid (yeah we all know who was the stoopid one in this case) that the links that go to the stock images are not the modified images that match the BETA-SuperSU-v2.52.zip needs.

I took me a while to figure it out the difference.

If you do flash the stock boot.img instead of the modified boot.img and then install the BETA-SuperSU-v2.52.zip you will get the "your device is corrupt and can't be trusted to work properly" message.

Then the animation video will run forever without the system starting.

Once I found the actual modified image (angler-mmb29m-boot.img) provided by [MENTION=3355398]mrRobinson[/MENTION] (many many thanks) and applied it after installing TWRP things I had root and all my storage space.

Well 111G out of 128G which makes it (in my mind) a bad idea to order this phone with only 32G when the system cuts it down to 24G.

(I still haven't done a NANDROID backup and I expect the 111G to drop some more.

It apparently stores it somewhere where it doesn't count or it is small enough not to make a big difference I did a nandroid backup and still have the 111G on the Settings->Storage & USB.)

I hope this helps some other poor stoopid noob
[Nexus 6P General] Heisenberg:
It's fine to take the update with an unlocked bootloader, your bootloader has nothing to do with /system.
[Nexus 6P General] Mesmurized:
When the userdata partition is preserved, are any system settings (the changes made in Settings / ... / ... / ... ) lost when performing Step 10 or 11? (I would assume some are lost, but maybe not, I hope!)

Even though I started long ago with the Nexus 4, this noob is still a bit confused :confused:
[Nexus 6P General] Heisenberg:
No you shouldn't lose any settings.
[Nexus 6P General] zer0se7en:
I really hope the easiest method to root would arrive. I badly want a USB fast charge for my 6p which can be achieved by installing ElementalX custom kernel.

Rooting my old Nexus 5 is as easy as pie.
[Nexus 6P General] Heisenberg:
What's so difficult about it? Nothing is going to change. You don't need root to flash a kernel, you need an unlock bootloader and a custom recovery. So just unlock your bootloader, install TWRP, flash the kernel. Easy as pie.
[Nexus 6P General] zer0se7en:
Not really that hard. I'm just being paranoid because of some user experiences having trouble. Might try to root all the way before xmas. Busy at work for now. Already unlocked the bootloader.
[Nexus 6P General] Heisenberg:
Generally the only reason to have problems is not following the instructions properly, as long as you do everything by the book it should be smooth sailing.
[Nexus 6P General] veliksam:
Please HELP! Phone bricked ( I think?)

I beg anyone to please please assist me, I would really appreciate it!

Here's the story: I'm using my phone ( 100% stock, unrooted, locked) the other day and all of the sudden my phone reboots, however it won't get past the white "google" logo and it keeps rebooting.

Before all this happened I did

NOT

enable Developer options, usb debugging, or oem unlock.

I can get into recovery, I can adb sideload an update, however on fastboot it won't let me flash anything because it keeps saying that my device is locked, I tried unlocking but it won't let me. I have pasted my results from CMD below. Any assistance or advice would be welcome.

C:\SDK\android-sdk-windows\platform-tools>adb version

Android Debug Bridge version 1.0.32

Revision 09a0d98bebce-android

C:\SDK\android-sdk-windows\platform-tools>fastboot devices

84B5T15A04002575 fastboot

C:\SDK\android-sdk-windows\platform-tools>fastboot flashing unlock

...

FAILED (remote: oem unlock is not allowed)

finished. total time: 0.016s

C:\SDK\android-sdk-windows\platform-tools>adb devices

List of devices attached

* daemon not running. starting it now on port 5037 *

* daemon started successfully *

C:\SDK\android-sdk-windows\platform-tools>fastboot devices

84B5T15A04002575 fastboot

C:\SDK\android-sdk-windows\platform-tools>fastboot flash recovery twrp-2.8.7.2-angler.img

target reported max download size of 494927872 bytes

sending 'recovery' (16880 KB)...

OKAY [ 0.388s]

writing 'recovery'...

FAILED (remote: device is locked. Cannot flash images)

finished. total time: 0.411s

C:\SDK\android-sdk-windows\platform-tools>fastboot flash bootloader C:\angler\images\bootloader-angler-angler-02.45.img

error: cannot load 'C:\angler\images\bootloader-angler-angler-02.45.img'

C:\SDK\android-sdk-windows\platform-tools>fastboot reboot-bootloader

rebooting into bootloader...

OKAY [ 0.011s]

finished. total time: 0.012s

C:\SDK\android-sdk-windows\platform-tools>fastboot flash boot C:\angler\images\boot.img

error: cannot load 'C:\angler\images\boot.img'

C:\SDK\android-sdk-windows\platform-tools>fastboot devices

84B5T15A04002575 fastboot
[Nexus 6P General] syintiphic:
[MENTION=4153349]Heisenberg[/MENTION] thank you very much for putting together a well thought through and comprehensive guide. I have never used the adb commands before and your guide was straightforward and easy to follow. I received my Nexus 6P yesterday and during the evening I was able to unlock the bootloader, flash TWRP and root the device in about 15-20 minutes with no issues.

I ordered my device late last week and while I waited for it to be delivered I went through your guide multiple times and checked out some YouTube videos on how to perform the steps that you described. I guess you can say I did little homework while I waiting for my device to be delivered.

Again, thanks a lot for your guide. It is much appreciated.

Cheers.
[Nexus 6P General] hapticxchaos:
I'm sorry, maybe I don't understand... I tried "./ fastboot flashing unlock" and even as someone who really doesn't know much about command line, that doesn't seem right lol. Clearly I don't understand where you mean for me to put the "./"

I have installed the SDK and updated everything possible, and I still get the same message. I've been reading about this "fastboot flashing unlock critical". Would it be possible to flash a custom bootloader to then install TWRP? Or are there no available custom bootloaders? Any other suggestions as to how I might fix this?

One strange clue that probably means nothing...when I stay unplugged and excecute the command, it will say "waiting for device" and the moment I plug in booted into bootloader, it immediately gives me the same message about acceptable commands to try.

Gah! Wish I had Windows, feel like thisd be easier haha

Kindest regards
[Nexus 6P General] Heisenberg:
No amount of attempting to flash anything with fastboot is going to work if you never enabled OEM unlocking in Developer Options and unlocked the bootloader. Essentially, you're screwed unfortunately, you'll have to contact Google and request an RMA.

Awesome, glad to have helped. Especially someone who hadn't used adb or fastboot before. Nice work.

You need to navigate to where you have the SDK installed, open the "platform-tools" folder, right click, and select open in command prompt (or open in terminal, it differs from distro to distro). Once in the terminal you just enter the commands, but prefixed with the "./" (no space between the "./" and the beginning of the command). Here's an example:

./fastboot flashing unlock

All the "./" does is instruct that the command be carried out within the current location that the terminal is pointing to.
[Nexus 6P General] zer0se7en:
Oh... Seen the features of ElementalX 1.02 for Marshmallow 6.0.1, there is no USB fast charge??? What custom kernel did you flash on yours? Or is there another way to USB fast charge?
[Nexus 6P General] Heisenberg:
I haven't flashed any custom kernel so I'm not much help in that department, sorry.
[Nexus 6P General] zer0se7en:
All good. My Nexus 6p is now fully rooted. Cheers to this post!
[Nexus 6P General] JoKe_42:
Currently I'm running an unrooted stock phone.

I definitely want root it, but it seems you have to decide between security or root. Most of the custom roms add a ton of (for me) unneeded features, seem to be a lot buggier than stock roms and disable SELinux and/or the forced encryption.

My plan would be to stick with the stock rom and just root it. If I got this right, you can lock the bootloader after this, to get rid of the annoying boot message and enable the verification of the bootloader? If I want to flash an update, I would need to unlock it again and would loose /data again?

I know some of my points may seem weird, but security (against malware and government agencies) is very important for me. The reasons to root are for example AdAway or be able to fix minor bugs myself (like the buggy nc which makes you sound mumble sometimes).

Regards,
[Nexus 6P General] yass090:
How would I do all this on a mac? not sure how to use terminal very well either...I wish to unroot
[Nexus 6P General] Heisenberg:
Having a locked bootloader doesn't guard you against malware, government agencies, or anything like that. It simply means nothing can be flashed to the device with fastboot. You could lock it again if you really want to but I'd strongly advise against it. Firstly, each time you lock or unlock it, it'll wipe your device. But most importantly, if you ever run into issues you'll need it unlocked in order to flash the factory images. You may not have access to your data at this time to back it up first. You really get no benefit from keeping it locked. Your security concerns are tied to root, not the bootloader, and even then they're pretty minimal. As long as you're not installing dodgy apps and the like you're perfectly safe.

The commands are essentially the same on a Mac, but usually need to be prefixed with something before each command. There are guides on setting up and using adb/fastboot on a Mac online. You just need to make sure you install adb/fastboot via the Android SDK so you get the latest version which will recognise the "fastboot flashing unlock" command.
[Nexus 6P General] mongonexus:
hey guys,just a small issue i had unlocking bootloader, it would not unlock for me until i put the animation settings in developer options back to on 1.0 or at least to the on position,for me,,same thing with the hidden menu for the system ui tuner,,any thoughts,,steve
[Nexus 6P General] yass090:
I rooted the long way, using this here: http://nexus6proot.com/nexus-6p-root/how-to-root-nexus-6p-winmaclinux/2/ which appears to be the long way to root.

The only problem is I didn't back up my phone before rooting it, did I make a mistake?
[Nexus 6P General] Heisenberg:
No idea, sorry.

Yeah you probably should have made a backup first, can't do anything about that now though. What exactly do you want to do? Go back to a fully stock setup?
[Nexus 6P General] yass090:
Yes sir, I want to unroot it.
[Nexus 6P General] Heisenberg:
Just flash the factory images with fastboot, you'll be stock again.
[Nexus 6P General] yass090:
It worked! thanks
[Nexus 6P General] Heisenberg:
There might be some previous settings conflicting. Flash TWRP recovery again, boot into it, select wipe from the main menu, then select advanced wipe, check only the data box and swipe to wipe, then reboot the phone.
[Nexus 6P General] yass090:
I edited my post literally at the same time as you replied...I re-did the steps and it works just fine now! thanks for helping me
[Nexus 6P General] efrant:
Although not directly on-topic, I just wanted to expand on the above posts because I feel the issue is important.

Security can mean many things, but let's assume that in this case, we are talking about security of the data on the device in the event that the device is lost or stolen. Having a locked bootloader

is

certainly part of the chain of keeping your data secure, but it is only one link in that chain. A locked bootloader by itself is not sufficient to keep your data secure.

The best way is to have ALL of the following:

1) encryption enabled;

2) the stock recovery flashed;

3) USB Debugging disabled;

4) no apps (root or otherwise) installed that are not from verified sources;

5) no ROMs flashed that don't have sources available and are not verified by you;

6) Android Device Manager (or a similar app) installed;

7) a locked bootloader.

If any one of these items is missing, it weakens the chain, and may possibly make it easier to access the data on the device. It's up to each individual to determine how sensitive his/her data is, what the consequences of compromise are, and how far to go to and to what level to secure that data.

To address the bootloader issue directly, here's an example: You misplace your bootloader-unlocked device and someone picks it up. He/she is tech-savy, modifies the system partition (and he/she is able to because the bootloader is unlocked) to add a remote administration app/server to send all your data off your device when you boot it up. He then returns the device and you find it, and start using it as per normal. Your data is compromised strictly due to having an unlocked bootloader.
[Nexus 6P General] Jleech330:
Does the systemless root trip the "fuse" that is built into the nexus 6p?
[Nexus 6P General] jimmyjohnIII:
Not to sound rude, but why does it matter? That fuse does not have any impact to usability of the device.
[Nexus 6P General] Jleech330:
Due to warranty concerns, so that is why i am asking
[Nexus 6P General] jesssiii:
Google trips the fuse before it comes to you. No worries about warranty in that area.
[Nexus 6P General] Jleech330:
I did not know that. Thanks
[Nexus 6P General] Golf c:
Then why does it say "Qfuse enabled" in the bootloader?
[Nexus 6P General] efrant:
Read that as: "Qfuse tripped". This is done at the factory.
[Nexus 6P General] runawaybayeh:
hey thanks for the root Heisenberg!

one question,I bought supersu a few years ago,what about pro version,should i download and install?
[Nexus 6P General] Heisenberg:
You must flash the beta version that I link to in the guide, you can enable the pro features from within the app once it's flashed though.
[Nexus 6P General] runawaybayeh:
its offering to install with an installer,when i tap on it,it offers either play or twrp,if i choose play it looks like old 4.3 version to update to...what?
[Nexus 6P General] Heisenberg:
Is this after flashing the beta zip?
[Nexus 6P General] runawaybayeh:
i installed with the zip pointed me to.when i rebooted there was a notification saying it wasnt rooted yet and to complete by installing GUI.thats the confusion.sorry for typing,im currently one handed.
[Nexus 6P General] Heisenberg:
Ok, which version did you flash?
[Nexus 6P General] runawaybayeh:
the most recent one. i ve tried restoring and it's come up with a message that my devices corrupt and can't be used. It just hangs at the Google white logo.

i can get into recovery, should I go to factory and just select that,do need to restore the factory image another way.please provide link if youre able. Sorry for the trouble
[Nexus 6P General] Heisenberg:
I asked which version for a reason, exactly which version did you flash?
[Nexus 6P General] runawaybayeh:
SuperSU-v2.62-3-20151211162651.zip
[Nexus 6P General] Heisenberg:
OK, what build are you on? Had you previously flashed the traditional root? Have you flagged any modified boot.img?
[Nexus 6P General] runawaybayeh:
no.6.01.i am able to get into android guy on his back with hood open. im able to get into twrp. I hadn't flashed traditional root. Can I use "adb reboot bootloader"? To restart with a factory image.
[Nexus 6P General] Heisenberg:
Yeah I really don't know what's happened. Just power the phone off, then hold power + volume down to boot into the bootloader and flash the factory images to start fresh.
[Nexus 6P General] runawaybayeh:
it says "reboot bootloader" and when I select that it goes back to start and when I try to flash the factory image using the SDK\platform-tools it comes back: "error closed".
[Nexus 6P General] srqrob:
Not clear on which SuperSU beta to install. Spent time looking at Chainfire's thread and I can't determine whether I want 2.62 or 2.62-3 for Systemless root on Nexus 6p with 6.01.
[Nexus 6P General] Heisenberg:
Your posts are pretty vague, it's really hard for me to determine what's going on. Please be more specific and provide as much information as possible.

1. What says reboot bootloader?

2. What do you mean by it goes back to the start? Start of what? While doing what?

3. It comes back "error closed" after doing what exactly? Issuing which command?

Well 2.62-3 is the latest version so I assume that's the best one to flash.
[Nexus 6P General] NPOA556:
I went through this all last night with my new Nexus 6P. I first took the OTA to 6.0.1, then I unlocked the bootloader, flashed TWRP, and flashed SuperSU-v2.62-3. Everything went exactly as expected. The only root app I have tested so far is TiBu, and it was able to get root access.
[Nexus 6P General] BeerFuelledDude:
Out of interest, what would happen to a systemless rooted device if you tried to update OTA from 6.0 to 6.0.1?
[Nexus 6P General] srqrob:
That's my path too tomorrow. I just did not understand why the change in the numbering scheme. 2.60, 2.61, 2.62 and then 2.62-3. Xposed and Gravity Box is all I want and it might be nice to use Android Pay if it works with this root method.
[Nexus 6P General] jimmyjohnIII:
If you're installing xposed, it's going to modify /system which means you're going to lose android pay. There's always Google wallet though.
[Nexus 6P General] NPOA556:
The numbering scheme is explained in this post by Chainfire.

http://xdaforums.com/showpost.php?p=64262580&postcount=3688

I have not installed Xposed yet, but that is my primary reason for rooting as well.
[Nexus 6P General] srqrob:
On my 6p, Google Wallet upgraded automatically to Android Pay,