yashsingh1/xdaforums huggingface dataset:
[Nexus 6P General] Heisenberg:
Cool, glad to see you're all good now.
[Nexus 6P General] iJekyll:
Does anybody know

WHY

the Nexus 6P requires a different unlock bootloader command than the rest of the Nexuses?
[Nexus 6P General] slavandar:
Hi, I'm new to the SuperSU method of rooting. How often should I update SuperSU after rooting my device? Should I just leave it as is and never worry about it once I've rooted? If it does need to be updated after the fact, how would I go about doing that? Sorry for the first post questions, couldn't find the answer to this after a couple hours of looking around.

Starting my foray into Android programming and other related stuff, been lurking here for awhile. Great source of knowledge and information so far!
[Nexus 6P General] u89taper:
Stupid questions...

-Have you tried installing SuperSU 2.61 or are you intent on 2.62?

-Did you go back to stock system, boot and recovery before installing twrp and SuperSU 2.62? SuperSU 2.60+ requires stock system and will patch stock boot.img automatically (no need for modified boot.img any longer).

-Did you actually run twrp after flashing without installing SuperSU? By this I mean, did you run twrp, select "keep system read only" then reboot twrp before installing SuperSU (also without allowing twrp to automatically install SuperSU)?

-Are you able to boot into Android and download SuperSU 2.62 (rather than pushing via adb)? Tried installing through twrp via this method?
[Nexus 6P General] Heisenberg:
Wouldn't have the faintest idea, I'm sure there's probably information about it online somewhere. I never bothered looking for it because in the end does it really matter?

Well we're using SuperSU beta so the only way to update is by flashing a newer version with your custom recovery. As for how often, it's really up to you. If everything is working the way you need it to then you probably don't need to update. Keep an eye out in the SuperSU Beta thread here on XDA, and if you see anything that's introduced in newer builds that you want then it's time to update.
[Nexus 6P General] slavandar:
Sounds good, that's what I figured. I guess the only other question I have is will rooting the 6P cause a loss of camera quality at any point in the listed steps? When I put Cyanogenmod on my Nexus 5 awhile back when I was first starting out with this android stuff, my camera quality took a huge hit. I haven't seen any reports or posts about this when rooting the 6P and I'm pretty sure it's the ROM that did it, but I figured it can't hurt to ask.
[Nexus 6P General] Heisenberg:
Nah, the camera quality doesn't change at all.
[Nexus 6P General] adamo86:
Can I update ota after using systemless root or do I need to flash original recovery back? Also does layers work with systemless root.
[Nexus 6P General] Heisenberg:
You need to be stock to take an OTA, that includes recovery. Layers works with systemless root.
[Nexus 6P General] adamo86:
Are there any auto tool kits available to go back to stock recovery etc.
[Nexus 6P General] Heisenberg:
I'm a pretty vocal opponent of those things so you'll never see me recommend for anyone to use them. Nothing but trouble. Why would you need a toolkit anyway? It takes me like two minutes to go back to stock work fastboot. And it only takes that long because it takes the system image about 1:30 to flash lol.

Sent from my Nexus 6P
[Nexus 6P General] efrant:
Well, I guess that would depend on where you live and from where you purchased your device.

While a little dated now, and not specifically for the N6P, I can give you an example:

Based on posts here on XDA, some previous devices (e.g., the Nexus One), warranty was denied for certain users that purchased their devices through carriers, rather than through Google's website. Recall that the bootloader on the Nexus One was not relockable (without S-OFF, but very few users had S-OFF on the device back then). So, warranty work was denied because the bootloader was unlocked, despite the information on Google's website which you linked to (which existed as well since the days of the N1).

So, while you may be correct about not affecting warranty for N6P devices purchased through the Google store, a blanked statement like "It can't affect warranty" may not be true for all N6P purchases, as it may not necessarily be the case for N6P devices purchased through carriers (for which we have evidence from past devices).
[Nexus 6P General] Stephen:
Ahh sorry yes I was meaning for this device only. I should have been clearer than that. You are quite right. I can think of other phones as well that it would affect warranty eg some HTC devices.

I had an online chat session with Google support. They said that while the device is unlocked the warranty is void, but all you have to do is lock the bootloader again and your warranty is re-instated.
[Nexus 6P General] midas69:
I will copy this over from another thread here.

Google (or any manufacturer) can tell you that rooting etc. voids your warranty.But that doesn't make it so. If it's sold in the U.S. it is their responsibility to prove that what you did had an effect on what you are use the warranty for. As an example, if you get into a boot loop they have a pretty good argument. But if the power button falls off there is no way they can use software modifications to try to deny your claim.
[Nexus 6P General] Ritchiejoe:
https://www.reddit.com/r/Android/comments/3phaw6/nexus_6p_has_a_hardware_fuse_that_blows/cw6k68e
[Nexus 6P General] zee24:
Guys will this activate an unfixable switch that we wont be able to undo? I need to know that this time around LOL every device ive had i never cared but then again i never bought a full out phone before spent 768$ on it so im gonna keep it stock or try to for a bit atleast and make sure theres no manufacturers defects before trying this. But if theres no such switch then ill go ahead and flash twrp asap so SOMEONE PLEASE LET US ALL KNOW ONCE YOU FIND OUT THANKSS
[Nexus 6P General] Heisenberg:
Are you referring to a Qfuse? If so there's a discussion taking place about this. Go to the Nexus 6P index thread (link in my signature) and in the general interest section you'll find a link to the Qfuse discussion thread.
[Nexus 6P General] Stephen:
[MENTION=4153349]Heisenberg[/MENTION],

Hey just thinking. It might be worth making a recommendation, not to lock the bootloader unless you are 100% stock factory image, bootloader, recovery etc. I have been looking at the nexus 5x forums and one guy bricked his phone after installing twrp and locking it. It was sheer luck he was able to get it sorted again.
[Nexus 6P General] Heisenberg:
Thankyou, a warning has been added to section 1 of the guide, a full return to stock section will be added once factory images have been released.
[Nexus 6P General] Stephen:
They are released very quickly after the official release of the 5x so I think it wont be too long before they release for the 6p
[Nexus 6P General] efrant:
This happens because starting with the Nexus 6, re-locking the bootloader forces a wipe of userdata. This is done by the bootloader telling the stock recovery to wipe. If you don't have the stock recovery (and you have a custom recovery) your device won't boot because the bootloader is looking for the stock recovery to complete the wipe before it loads the kernel.

[MENTION=5302753]The_Merovingian[/MENTION] wrote up a thread on how to safely re-lock the bootloader for the Nexus 6: http://xdaforums.com/showthread.php?t=3067302 and for the most part, should be applicable to the N9, N5X, and N6P.
[Nexus 6P General] Born<ICs:
:fingers-crossed:

Based on what I'm reading on 5X development it may be wise for even experienced folks to use caution before Decrypting, UnLocking Bootloader, Custom Recovery, Rooting. etc.

:confused:
[Nexus 6P General] sabbotage:
Looks like the command for unlocking/relocking the bootloader on the Nexus 6P is now "fastboot flashing [unlock | lock]" now instead of the former "fastboot oem [unlock | lock]".
[Nexus 6P General] hutzdani:
Seems not - using my ADB terminal window "FASTBOOT FLASHING UNLOCK" comes back as an unknown command seems we need some new ADB drivers
[Nexus 6P General] airmark:
It worked for me. Just unlocked it with this new command. Qfuse status remained enabled btw.
[Nexus 6P General] Heisenberg:
This guide has been updated to include the proper unlock command:

fastboot flashing unlock

I find it pretty odd that Huawei decide to alter this command, fastboot oem unlock has always been the universal command for this task.
[Nexus 6P General] Heisenberg:
Can you elaborate please?
[Nexus 6P General] nusclyss:
This is a superb tutorial, thanks for the writing up
[Nexus 6P General] airmark:
Any news on custom recovery and root?
[Nexus 6P General] Heisenberg:
Not yet. I'd expect TWRP to be available pretty soon though, and it shouldn't take too long for chainfire to release a modified boot.img (required for root on Marshmallow) now that the factory images are available.
[Nexus 6P General] Born<ICs:
.

Well I'm a nervous old dude (Born before IC's lol) only know enough to be dangerous but try to be prepared for things to go south.

So for this device so far we have no TWRP Custom Recovery, Factory Images up yesterday, No Modifed Images.

Personally I'm doing nothing with my device until the TWRP guys and Chainfire etc release their work...

Even then will ease into things while dust and bugs settle.

Drilling through 5X posts some seem to have issues with unlock, recovery, lock.

Other experienced folks could explain possible issues or pitfalls better than I, if there in fact are any.
[Nexus 6P General] adamo86:
If I flash back to stock recovery would I loose root. Also does the unlock sign on boot still show when the bootloader is relocked
[Nexus 6P General] Heisenberg:
No, why would you lose root from changing recovery? The only relationship the two have is that recovery flashes SuperSU, that's it. The unlock symbol on the boot logo will not be present if you lock your bootloader? But why would you do that? Firstly, it'll wipe your phone. More importantly though, it's best to leave it unlocked in case you need to flash the factory images in future. If you ever get into trouble and need to flash you'll be forced to unlock it again, possibly in a situation where you don't have access to your data to back it up first.

Sent from my Nexus 6P
[Nexus 6P General] adamo86:
Only for selling purposes because some anti root buyers don't like root
[Nexus 6P General] Heisenberg:
Fair enough, but the bootloader has nothing to do with root.
[Nexus 6P General] adamo86:
So does that mean you can root with out unlocking bootloader
[Nexus 6P General] Heisenberg:
No you can't. But that doesn't mean they're the same thing. Sure, to flash SuperSU you need a custom recovery, and in order to flash a custom recovery you must have an unlocked bootloader. But having an unlocked bootloader doesn't necessarily mean you have root, it just means you have the ability to flash images to partitions on the device. In short, you can't have root without an unlocked bootloader, but you can have an unlocked bootloader without root.
[Nexus 6P General] dboren:
Error on location

Hello, I really appreciate this thread. Atfter typing the commands, I am always getting errors on the location. When i put any of the flashing commands in, i always receive an error: cannot load C:\<location> and thats it. ive switched the folders location a few times to see if anything would change, but the error will only load the top folder under the local disk, so in my case it would be C:\nexus 6p root. any help is appreciated:good:
[Nexus 6P General] adamo86:
What's the deal with android pay do I have to be stock Rom for it to work
[Nexus 6P General] Heisenberg:
Try this. Instead of typing the location, type the first part of the command:

fastboot flash recovery

(with a space after the last character)

Then drag the file you want to flash into the terminal window, this will automatically enter the file location for you.
[Nexus 6P General] Heisenberg:
Don't know, don't use it. This isn't really related to this thread anyway, there are threads discussing this, I can only suggest you look there.
[Nexus 6P General] jesssiii:
With phone on, plug into computer then touch the charging notification and pick install files. Then under "this pc" double click the nexus folder and open internal storage. Drag and drop the zip in then flash it in twrp.
[Nexus 6P General] slavandar:
Hey thanks again for the quick responses and friendly help.

Successfully rooted the Nexus 6P by following the listed steps, have no issues. I used SuperSU 2.61 since it looked like 2.62 mentioned something about breaking OTA updates and I wanted to keep the device as close to stock as possible while rooting it for the first time. I'm going to learn a little bit more about custom Kernals and advanced system control before going further, but for now it's enough for me to have rooted control over the device with some extra functionality.

Appreciate the effort that went into this post, and the continued effort involved with maintaining the thread and answering questions. Thanks so much!
[Nexus 6P General] adamo86:
I wanted to know why I can't access the phones storage folders when I connect to Windows vista because I downloaded all the files to unlock the device and a Rom to flash. It shows the internal storage but only photos.
[Nexus 6P General] Ketawa:
So far, every method of rooting on Marshmallow has broken OTA updates. You need stock images for OTAs. However, Chainfire is working on functionality for SuperSU that will allow OTAs.
[Nexus 6P General] Alferboy:
For what I've seen in the scripts, even whitespace is validated. Very hard task unless with different scripts.
[Nexus 6P General] vobasf:
reflash system.img for OTA update?

Hi Heisenberg,

I have read some post on reflash system.img for OTA update on Nexus 6 Lollipop.

http://xdaforums.com/nexus-6/help/rooted-nexus-6-fails-to-update-5-1-1-t3126216

Is this method valid on Nexus 6P marshmallow?

Thanks.
[Nexus 6P General] Heisenberg:
I have instructions for updating in this guide, follow those and you'll be fine.
[Nexus 6P General] dboren:
Got "an internal problem with the device" after updating to a new build

Hello, so i was able to update to a new build using the guide "How To Update To A New Build Of The Stock ROM" . Everything went smoothly, and when i was done, i flashed TWRP and SuperSu as the guide says. After i had flashed supersu as well as xposed, my 6p went into a bootloop. Not knowing what had caused the bootloop, because i was under the impression xposed was compatible with 6.0.1, i went back into recovery and restored the backup i made before the whole process of updating. After i had restored and rebooted the phone, i now get a pop up when i turn the phone on saying "There is an internal problem with your device. Contact your manufacturer for details." The phone works perfectly fine, except neither cameras will work. i only get a black screen in apps that use the camera, including the stock app. So i guess i am looking for some guidance, not really knowing where to go or look from here. all help is appreciated:good::good:
[Nexus 6P General] Heisenberg:
Xposed does work, but you need to make sure you flash the right version. I probably would have booted the phone at least once before flashing it too. When you restored your backup which partitions did you restore? It sounds to me like you have an incompatible boot.img possibly.
[Nexus 6P General] dboren:
youve been extremely good with replys and i really appreciate it:good:. i will remember to boot the phone to see if the update goes well before eagerly flashing in the future. the partitions i restored were boot, system, data, recovery, and efs.
[Nexus 6P General] Heisenberg:
Just an idea, but it could be because you still have the 6.0.1 vendor partition present on the phone while running an earlier build now. I'd suggest flashing the vendor image for the build that you restored, that's if you want to remain on the older build. Otherwise just flash the latest MMB29M build to update again.
[Nexus 6P General] dboren:
so to update to the 6.0.1, i am unclear what i am flashing. do you mean the modified boot.img? or can you link me to that build
[Nexus 6P General] Heisenberg:
Didn't you do it already by following my instructions in section 10?
[Nexus 6P General] dboren:
yes, yes i did:rolleyes:. i used my head since that last reply and redid section 10. so now i reboot, check that everythings ok, then flash twrp and supersu? followed by xposed?
[Nexus 6P General] Heisenberg:
Yep, looks good to me.
[Nexus 6P General] dboren:
you sir, are a gentleman and a scholar. thank you for holding my hand.
[Nexus 6P General] Heisenberg:
Shh, don't tell anyone, I have a reputation to uphold!

:silly:
[Nexus 6P General] Fauert:
HO-ho , really .. :laugh:
[Nexus 6P General] cturbos:
go to device manager on your PC,and update your drivers...
[Nexus 6P General] adamo86:
Didn't work it says already has best drivers. So it gave option to uninstall tried didn't work it gave option to delete driver from device so I did then it worked .windows vista
[Nexus 6P General] jesssiii:
Moved to question thread.
[Nexus 6P General] GCbard:
i am trying to unlock bootloader after updating to 6.0.1. Fastboot recgonizes the device but the command

fastboot flashing unlock

returns the just a list of possible commands for fastboot. See below. The returned portion from the fastboot devices command was edited for privacy sake.

Any suggestions?????

C:\adb>fastboot devices

ertyugg(this edited for privacy) fastboot

C:\adb>fastboot flashing unlock

usage: fastboot [ <option> ] <command>

commands:

update <filename> reflash device from update.zip

flashall flash boot + recovery + system

flash <partition> [ <filename> ] write a file to a flash partition

erase <partition> erase a flash partition

format <partition> format a flash partition

getvar <variable> display a bootloader variable

boot <kernel> [ <ramdisk> ] download and boot kernel

flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it

devices list all connected devices

continue continue with autoboot

reboot reboot device normally

reboot-bootloader reboot device into bootloader

help show this help message

options:

-w erase userdata and cache (and format

if supported by partition type)

-u do not first erase partition before

formatting

-s <specific device> specify device serial number

or path to device port

-l with "devices", lists device paths

-p <product> specify product name

-c <cmdline> override kernel commandline

-i <vendor id> specify a custom USB vendor id

-b <base_addr> specify a custom kernel base address.

default: 0x10000000

-n <page size> specify the nand page size. default:

2048

-S <size>[K|M|G] automatically sparse files greater th

an

size. 0 to disable
[Nexus 6P General] MrMundy:
i hope im not wrong but the guide on how to take an OTA is gone right?

anyway main question is, im on 6.0 rooted and running xposed with gravitybox.

to update to 6.0.1 while keeping all my apps and data intact all i have to do is follow part 10: How To Update To A New Build Of The Stock ROM, after updating, flash twrp and do a systemless root again and bam, enjoy the phone AGAIN

right?:fingers-crossed::fingers-crossed::fingers-crossed:
[Nexus 6P General] Chkeh:
I am currently rooted using traditional root running elementalx on 6.0. What do I have to do to update to 6.0.1 and then also reroot systemless rather than the traditional way? Is there a way to do this without losing my data?
[Nexus 6P General] osucowboy96:
That's what I did, same situation as you. Follow #10, reboot, them go back in to install TWRP and systemless root. Then I rebooted, then I went back into TWRP and reinstalled xposed. Worked like a charm.
[Nexus 6P General] LeftHandedWave:
I had the same problem. What I did was go to windows update and update all the needed security patches. Looks like I was missing some .NET stuff. After I restarted and then plugged in the phone, the drivers installed.
[Nexus 6P General] shag_on_e:
So this may have been mentioned already, but I noticed in fastboot mode a line that says Download Mode enabled- no. I'm wondering if anyone knows how to boot into and use download mode on this device. Coming from many Samsung devices, I know download mode and Odin can save some serious bricks. Anyone know anything about this?
[Nexus 6P General] zervic:
When I get to the vendor step, i'm receiving the following error:

C:\SDK\platform-tools>fastboot flash vender c:\angler\images\vendor.img

target reported max download size of 494927872 bytes

sending 'vender' (185129 KB)...

OKAY [ 7.764s]

writing 'vender'...

FAILED (remote: Permission denied!)

finished. total time: 7.793s

Any ideas? It gave me an error when I rebooted into my phone, but it looks like it's still working properly anyway (I'm at the optimizing apps screen right now).

Edit: Derp. "vendor" not "vender" -_-
[Nexus 6P General] shmeeks:
Same problem here except when relocking.
[Nexus 6P General] snovvman:
Thank you for this. I went with systemless when upgraded to 6.0.1 with 2.62-3. The trouble was that I would lose root after reboot. I tried a few things but no joy. There are several others with the same problem. This modified boot will allow me to use system root with 2.52 for now so all is well. Again, thanks.
[Nexus 6P General] Heisenberg:
This means your adb/fastboot is out of date. Open SDK Manager and update your platform-tools package. If you have no idea what I'm talking about then you probably didn't install adb/fastboot via the Android SDK, read the prerequisites section.

Yep, spot on.

Section 10, then flash TWRP and SuperSU again.

See above, your adb/fastboot is out of date.
[Nexus 6P General] MrMundy:
lmao, i just updated it before ur reply and the first thing that pop up on the first boot on 6.0.1 is the email notification of u quoting me in the reply

enjoying my phone yet again... thanks Heisenberg!!!

cheers!
[Nexus 6P General] shmeeks:
I updated my platform-tools before and restarted. Still doesn't work :(. Just opened it again to double check it took and it did. That's the only command not working for me.
[Nexus 6P General] StuartRothrock:
Be sure to download the latest SDK Tools in the beginning of this thread. I had the same issue. Oops I missed the other reply that answered your problem. Sorry. Admins - feel free to delete this reply....
[Nexus 6P General] Heisenberg:
Issue this command:

adb version

What does it return?
[Nexus 6P General] azsl1326:
Getting my Nexus 6P later this week. I plan on unlocking, rooting and flashing custom recovery. I am assuming that it won't have 6.0.1 loaded on it. What's the best way to get the latest update on the phone? Confused on if I should use the OTA or full version and if it needs to be sideloaded?

Thanks, in advance.
[Nexus 6P General] grimpow:
Cannot issue "fastboot flashing unlock"

Trying the guide exactly as described in the OP, and I cannot get "fastboot flashing unlock" to issue. The device is showing up properly when checking with "fastboot devices". I've seen others with this issue, and it's always been resolved by installing the latest SDK/platform tools directly from the SDK manager. I have the most recent build tools and platform tools all from the official SDK manager, and yet adb still will not recognize the command, and instead just returns a list of some recognize commands that I should try. What else could I be missing? And in case I'm somehow mistaken about my adb being current, the version is 1.0.32. I just installed earlier today though, so I have no idea how I could be outdated.
[Nexus 6P General] Heisenberg:
Boot the phone up, if you received the update notification then just take it. Otherwise flash the factory images to update it.

You definitely have the latest version installed. I can't think of why the correct command wouldn't be working. Exactly which packages do you have installed when you look in SDK Manager?
[Nexus 6P General] azsl1326:
I have had issues similar to yours in the past. I installed Minimal ADB and Fastboot and it fixed the issue. Not sure if it will in your case, but thought I would throw it out there.

http://xdaforums.com/showthread.php?t=2317790