yashsingh1/xdaforums huggingface dataset:
[Nexus 6P General] sidhaarthm:
Hi OP,

Do you plan on releasing a similar guide for the Pixel 2 / Pixel 2 XL devices? I know most of the steps might be common so at least you wouldn't have to start from scratch :)
[Nexus 6P General] 18yusuf:
check this out: https://xdaforums.com/showpost.php?p=73355557&postcount=174
[Nexus 6P General] danwil77:
Hey, I've been running the PureNexus rom on my 6p for a long time. Today I tried following the instructions in this thread "10. How To Flash The Factory Images (And Return To Stock)" using the latest factory image. Now my 6p won't boot, just stays at the 4 animated circle icons for 20+ minutes so far.

What's the best way to approach fixing this? I saw another site said to use the flash-all.bat that came with the factory image but I didn't know if that works with my bootloader unlocked...

help please!
[Nexus 6P General] Badger50:
The flash-all.bat will work fine with your bootloader unlocked. Be advised, using that script..WILL wipe your phone! :eek:
[Nexus 6P General] danwil77:
Thanks for the quick response... I wasn't crazy about the idea of wiping my phone but I tried a few other things this morning before posting here and I was just frustrated enough.. ha... It's up and running now, like a brand new phone
[Nexus 6P General] drone991:
Will this guide work on Oreo 8.1 DP 1 ?
[Nexus 6P General] ffejy462:
Yes.
[Nexus 6P General] Einwod:
You need to update your signature link: This domain name expired on 2017-10-25 23:59:59
[Nexus 6P General] mkmathers:
I'm gonna be complete noob here just to be on the safe side. I'm on the stock 7.1.2 build, rooted of course!

Now I got this OTA for the 8.0 build, so do I just do the steps in section 9, or is there something else I should de beforehand?

And also, I've installed an APK as a system file, so do I delete that before upgrading or is it okay?

And thank you for bearing with me
[Nexus 6P General] ffejy462:
Since you've modified system, ota will fail. Your best option is to manually flash factory image with fastboot.
[Nexus 6P General] W@r10ck:
Or you can update through flashfire
[Nexus 6P General] ffejy462:
That's what I generally do, but I consider it the second best option and only suggest it for those that I know are familiar with fastboot/adb already. In a thread meant as a guide, flashfire could become obsolete or abandoned by the developer (considering that chainfire no longer develops supersu, it's a potential possibility).
[Nexus 6P General] W@r10ck:
Great timing for magisk to come in
[Nexus 6P General] mkmathers:
So I need to download the new factory image, and just simply flash it via fastboot?

Like there's no need for me to use TWRP and all that

Sorry, used to play with other phones, but a nexus was new to me, so I'm just getting used to it..

Thank you and sorry for being an annoyance..
[Nexus 6P General] ffejy462:
Yes.

If you want custom recovery, flash twrp. If you want root, flash SuperSU or magisk. I don't know what your goal is.
[Nexus 6P General] cor_mann:
Verizon Version

Hi,

Noob question. I used the tutorial to return to stock. I originally purchased the Verizon version and unlocked/rooted using the exploit (I believe). Now that I've used the this tutorial, is there any remnants of the Verizon bootloader (or anything else), or is the phone now unlocked like from Google directly? I ask because I'm planning to sell it and I want to make sure I list it correctly. Thanks in advance.
[Nexus 6P General] mulhiny:
Verizon version of the 6p?
[Nexus 6P General] cor_mann:
^

Yep.
[Nexus 6P General] SlimSnoopOS:
This phone was never released through Verizon. Just flash the factory image, sign out of your Google account (or the buyer will be locked out of the device), and lock the bootloader prior to selling it.

The MotoNexus 6 and the Pixels have Verizon variants.

Edit: Going to reiterate, sign out of your Google account and other email accounts prior to locking the bootloader. Factory Reset Protection will prevent any buyer from signing into the phone once the device has been factory reset if the email account was still signed in.
[Nexus 6P General] cor_mann:
Thanks. I bought the phone from BB and had it in my mind that it was a Verizon variant. I returned it to stock and locked the bootloader, but I can't remember if I specifically signed out of my accounts before doing that. I'll see if I can go through the initial set up again, disconnect any accounts, and then wipe one more time.
[Nexus 6P General] 21-Savage:
Although I enjoy my G3, I am going to buy a Nexus 6P next semester. The guy I arranged to buy the phone off of has it on 8.1. Could I still follow this guide to a T? I want to try CarbonROM.
[Nexus 6P General] badabing2003:
Just be aware that Nexus 6p has serious battery issues (defect), even some causing bootloops.

Google was replacing them with Pixel XL, even out of warranty, but it stopped doing that as it became overwhelming.

Just be aware what you're getting into.

Search the forums, there are threads about it.
[Nexus 6P General] W@r10ck:
Forget about buying N6P. Dont get me wrong this phone is one of the best phone i ever had but because of this issue i would never recommend it to anyone ever. Save yourself $$$ and get other phones.
[Nexus 6P General] 21-Savage:
Well that's no good. Alright, I'll look elsewhere. Thanks for the heads up.
[Nexus 6P General] rob219:
does this work on 8.1.0 build OPP6.171019.012?
[Nexus 6P General] teohguangli:
Guys do you all have problem rooting the latest stable release of android 8.1? I can't seem to get pass the Google logo on booting up after flashing SuperSU v2.82 through TWRP v3.2
[Nexus 6P General] ffejy462:
Either use 2.82 sr5 (from the beta thread) or magisk.

SuperSU isn't being actively developed, but magisk is. I'd recommend flashing magisk 14.5.
[Nexus 6P General] ebeeman:
I just went through root process yesterday no problem on my Nexus 6p. (Thanks xda forum!) Only issue I had was the fastboot version on my Ubuntu PC didn't allow flashing unlock command. Googled how to update fastboot and found a great guide from helpful guy named Bernaert at bernaerts.dyndns.org that quickly solved that issue.

Replaced the Nexus 6p battery last month with a $26 Amazon purchase. As long as you are getting a really good deal on phone. It will work fine for you. I chose magisk over SuperSU.
[Nexus 6P General] wolfman66:
I have the same problem. Flashed the latest factory image (8.1.0) from the developers website and ran through the process as usual.

After applying SuperSU 2.82 and re-booting device, it hangs on Google splash screen.

Someone suggested rooting with Magisk. Does this make any difference?

Any help will be good before I try this.

EDIT:

Re flashed and applies Magisk flashable zip file. Then installed Magisk Manager apk. All perfrect now.
[Nexus 6P General] Braakie:
Hey,

Where should the busybox binary be installed on Oreo 8.1 with supersu 2.82 R5.

I get to see the following paths:

/system/xbin

/system/bin

/sbin/supersu/xbin

custom path

Also the supersu app dit not install after flashing supersu
[Nexus 6P General] ffejy462:
/xbin

Or

/su/xbin

That is dependent in what order you flashed supersu and busybox.

I'd highly recommend the busybox from [MENTION=4544860]osm0sis[/MENTION]

https://xdaforums.com/showthread.php?t=2239421

Common issue using supersu on 8.1. Extract the apk from the zip. Flash SuperSU then install apk as an app after booting.

Considering the development status of supersu, I'd recommend magisk.
[Nexus 6P General] Braakie:
Okay thnx you, you mean I take the Busybox Installer (all devices) from osm0sis. And which version can I best use of magisk, the beta or the stable.
[Nexus 6P General] ffejy462:
14.5. I believe it's in the beta thread.
[Nexus 6P General] Braakie:
Oke thnx you.
[Nexus 6P General] ebeeman:
Nexus 6p with superSU

I had same issue with 2.82 sr5. Boot loop at Google logo. I next tried 2.79sr3 with fresh 8.1.0 build. Although it seemed to work and booted, apps did not recognize device as being rooted. My next step is test 2.79 sr2. I welcome any suggestions on proper SuperSU version.

Magisk does work but "wifi tether router" app Developer said it has problems with Magisk so he advised testing SuperSU.
[Nexus 6P General] azsl1326:
Attempting to lock the bootloader and when after typing, "fastboot flashing lock", terminal gives me a list of options to use with fastboot as it doesn't seem to recognize this command. Suggestions?

Thanks!

---------- Post added at 05:46 PM ---------- Previous post was at 05:32 PM ----------

Resolved - switched from Windows Powershell to CMD prompt in Windows 10 and was able to lock the bootlooder.
[Nexus 6P General] bibikleio2013:
I have a question.

I want to update the radio and the bootloader.

The command is, fastboot flash bootloader bootloader (name of the file).

And the same for the radio?
[Nexus 6P General] SlimSnoopOS:
Correct, just follow section 9. Just do not flash anything besides the bootloader and radio images.
[Nexus 6P General] bus36ta:
rooting build number 1.171019.011

could someone be so kind as to direct me to a root procedure tutorial for the latest 8.1 release on the 6p. i am having battery issues and think root and custom rom is worth a shot. anyone else experiencing horrible battery life after ota 8.1? also information about twrp and magisk
[Nexus 6P General] mobileman88:
Battery issues with the 6p usually is due to your battery going bad. Software can't fix it. You got to have it changed
[Nexus 6P General] baxxter106:
I did it today with this guide and it worked great in Debian. Nothing to change.
[Nexus 6P General] dwh2o13:
This guide is great, but you might also like this video as a guide to update. Hope it helps.
[Nexus 6P General] devmalla:
Getting error for file too large while flashing

hi. i did all of the steps but when i try to flash system.img or vendor.img , it gives an error

writing 'boot' 1/5...

FAILED (remote: size too large)

finished. total time: 11.146s

i tried using the format userdata command but after doing this, it still gives the same error
[Nexus 6P General] Einwod:
It should say writing system or vendor, not boot. Are you using the correct commands? Fastboot flash system system.img
[Nexus 6P General] devmalla:
Sorry I had been using the wrong commands (fastboot flash boot system.img instead of flash system)

Still I am having some problems.

I followed all the steps in the guide to unlocking the bootloader and then follwed the steps for 10. How to Flash The Factory Images (And return to stock). I got the following results

PS C:\Users\Dell\Desktop\platform-tools> fastboot flash boot D:\angler\images\boot.img

target reported max download size of 494927872 bytes

sending 'boot' (12065 KB)...

OKAY [ 0.286s]

writing 'boot'...

OKAY [ 1.288s]

finished. total time: 1.577s

PS C:\Users\Dell\Desktop\platform-tools> fastboot erase cache

******** Did you mean to fastboot format this ext4 partition?

erasing 'cache'...

OKAY [ 0.025s]

finished. total time: 0.026s

PS C:\Users\Dell\Desktop\platform-tools> fastboot flash cache D:\angler\images\cache.img

target reported max download size of 494927872 bytes

erasing 'cache'...

OKAY [ 0.024s]

sending 'cache' (5752 KB)...

OKAY [ 0.149s]

writing 'cache'...

OKAY [ 0.129s]

finished. total time: 0.307s

PS C:\Users\Dell\Desktop\platform-tools> fastboot flash recovery D:\angler\images\recovery.img

>>

target reported max download size of 494927872 bytes

sending 'recovery' (13001 KB)...

OKAY [ 0.306s]

writing 'recovery'...

OKAY [ 0.194s]

finished. total time: 0.503s

PS C:\Users\Dell\Desktop\platform-tools> fastboot flash system D:\angler\images\system.img

target reported max download size of 494927872 bytes

erasing 'system'...

OKAY [ 0.040s]

sending sparse 'system' 1/5 (480798 KB)...

OKAY [ 11.063s]

writing 'system' 1/5...

OKAY [ 6.880s]

sending sparse 'system' 2/5 (480321 KB)...

OKAY [ 11.140s]

writing 'system' 2/5...

OKAY [ 6.968s]

sending sparse 'system' 3/5 (479261 KB)...

OKAY [ 11.221s]

writing 'system' 3/5...

OKAY [ 7.347s]

sending sparse 'system' 4/5 (474278 KB)...

OKAY [ 10.902s]

writing 'system' 4/5...

OKAY [ 6.642s]

sending sparse 'system' 5/5 (43872 KB)...

OKAY [ 1.082s]

writing 'system' 5/5...

OKAY [ 0.640s]

finished. total time: 73.938s

PS C:\Users\Dell\Desktop\platform-tools> fastboot flash vendor D:\angler\images\vendor.img

target reported max download size of 494927872 bytes

sending 'vendor' (184537 KB)...

OKAY [ 6.145s]

writing 'vendor'...

OKAY [ 2.996s]

finished. total time: 9.144s

PS C:\Users\Dell\Desktop\platform-tools> fastboot flashing lock

...

(bootloader) Please select 'YES' on screen if you want to continue...

(bootloader) Locking bootloader...

(bootloader) Locked!

OKAY [ 5.468s]

finished. total time: 5.470s

then i locked the booloader and restarted the device. Now its stuck in the google logo loop and does not go further than that. Where did i go wrong? :confused:
[Nexus 6P General] Einwod:
You locked the bootloader before booting the device to make sure all was well. Unlock again, restart the device and then if it starts, (there's no need to set it up as locking will wipe everything again), then if and when it boots properly, you can relock the bootloader.
[Nexus 6P General] Heisenberg:
I'd be surprised if he could do this. He's flashed over the settings on the device so the OEM unlocking option will almost definitely no longer be enabled. No way to enable it either if the phone won't boot. Potentially looking at a brick here. I'd be trying the flash-all approach, it might work.
[Nexus 6P General] sunandoghosh:
Plep help for next update.

My current system status:

Attachment One

System prompts for 42 MB update.

Attachment two

Pls suggest how to update safely without data wipe and root thereafter Kindly
[Nexus 6P General] scrin378:
Just click download...it will download and install it..

Why do you think that you will lose data..?? You wont lose anything ;)
[Nexus 6P General] sunandoghosh:
sorry forgot to say i am rooted
[Nexus 6P General] mobileman88:
You won't lose data. However the ota installation will fail
[Nexus 6P General] TTA1326:
Sorry, for the newbie like question in advance! I left my Galaxy Nexus behind ages ago and forgot most everything I guess. I went Note 4 Developer Edition for years, and it's a different animal, then I bought the Pixel 2 XL 128 during the launch event. Mine was excessively blue, even at slight angles, and sorry, but for $1100+, I sent it back. So, I bought a black 64GB Nexus 6P two weeks ago off Swappa. It was refurbished by Google in Aug or Sept 2017, and it looks brand new. No marks anywhere on this one, and it runs just like my wife's white 64GB Nexus 6P that we bought new, and is stock, although it's been replaced once for the battery, duh. Her phone auto updates monthly as expected.

Anyway, I followed your instructions here, and that stimulated enough memories to get my new phone unlocked, rooted, setup with TWRP, Magisk, and a few apps I use (AdAway, Titanium, ES File Explorer, etc). This phone was locked, unrooted, and completely stock when I got it, and no problems with the work I did. It's on Android 8.1.0 Dec Patch (OPM1.171019.011). Here's the question, how do I install the monthly patches?

Is it just step "9 How To Update To A New Build Of The Stock ROM" and let Magisk repatch the boot image? I just don't want to mess up since the phone works so well right now.
[Nexus 6P General] Einwod:
That's all it should take. Don't format the userdata otherwise you'll start from scratch.
[Nexus 6P General] SlimSnoopOS:
Pretty much yes. Follow section 9 but exclude flashing the recovery.img. Boot back into TWRP and flash Magisk before booting up.

Edit: Ninja'd by a country mile lol
[Nexus 6P General] pdpatdwyer:
Okay to return to stock?

Hello all,

I have a couple questions regarding my phone and was wondering if someone could help me out or point me in the right direction.

What I want to do is return to a stock factory phone.

The phones status now is whats confusing me. Two years or so ago I followed Heisenburgs instructions to unlock bootloader and root the phone. But currently I do not have root access.

I did a couple things with root access when first obtained, but left it alone since then. Has never seen an upgrade since then either..

Android Version: 6.0.1

Security Patch: Jan 1 2016

Kernel: 3.10.73-g9741316

Build number: MMB29P

Initial modifications:

Unlock Bootloader

TWRP Recovery

Rooted

After root, kept factory image, installed apps:

AdAway

GravityBox [MM]

MinMinGuard

SuperSU

Terminal Emulator

Titanium Backup (Never used)

Youtube AdAway

Youtube Background Playback

Current Status:

When turning on, receive 'Your device software can't be checked for corruption. Please lock the bootloader' notification

SuperSU states 'There is no SU binary installed, and SuperSu cannot install it.'

Power+VolDown takes my to options page with open stomach android guy to load: Start, Reboot Bootloader, Revovery mode, Power off, Factory, BP Tools, Barcodes... Cant remember if this is factory

Boot into recover takes me to TWRP

I have three restore packages in twrp but I have no recall on what they are.

Also of note, OEM unlocking and USB debugging are unchecked in Developer Options, not sure how or when this happened

To me, this sounds like the bootloader is unlocked, but I lost root at some point.

So the question is, can I safely follow the instructions for #10 'How To Flash The Factory Images (And Return To Stock)'

Any help is appreciated, thank you
[Nexus 6P General] Einwod:
Switch back on the OEM unlocking and USB debugging before doing anything else. Then you can follow the instructions.
[Nexus 6P General] Scyzor:
Question regarding OP - are those steps for unlocking bootloader, custom recovery and root going to work on 8.1.0?
[Nexus 6P General] Badger50:
Sure. About the only thing different is your root method. Since SU is basically no more, you'll have to use magisk. Other than that, if you follow the directions, you'll be fine :good:
[Nexus 6P General] jimbomodder:
Vendor image size

OK so as late as it is I've now switched to 6p from the N6 and really loving it. Now having to get used to vendor imgs will come quick but the question I have is what size should they be? I was given one which was 190mb and if I google for it I find ABC site and its only 83.99mb. My intention is to flash I'm recovery but the smaller sized one failed. Any help appreciated
[Nexus 6P General] Badger50:
If memory serves, vendor images for the 6p were always around 190mb. I always extracted the monthly vendor from the factory images and used that when my custom rom was updated each month. Never had an issue with this method :good:
[Nexus 6P General] jimbomodder:
Ok well that's probably the one then, so one last thing... Do I only need to flash vendor image of I change between say 7.1.2/8.0/8.1?. And again thanks for the help, it's much appreciated:svetius:

P.s. any way to get rid of bootloader warning? I not no Biggie just one I'll need to get used to haha
[Nexus 6P General] Badger50:
Personally, every time there was a major OS update like you described, I always clean flashed the new factory image and wiped my phone. Then I would transfer all my data back from my pc, then flash my custom rom, gapps, and root. And, unfortunately, no, there is no way to remove the bootloader warning. Got the same thing on my P2XL..hahahahahaha :good:
[Nexus 6P General] jimbomodder:
Ah right ok I got it now:svetius: thanks for the help:fingers-crossed:
[Nexus 6P General] pdpatdwyer:
Thank you,

Unfortunately, ran into a problem. After reviewing options 9 and 10 I went with 9, trying to upgrade to the latest rom without wiping data. The only difference i saw was wiping data beforehand.

After following all instructions, i tried to boot into twrp recovery to wipe cache and dalvik, but it got a 'no command' error and never got into twrp.

Trying to boot normally looks like and endless boot cycle

The only thing i did wrong , was the fastboot erase cache, then realized i didn't have to .

Any recommendations?

Edit: I did turn back on unlocking and debugging beforehand
[Nexus 6P General] mobileman88:
Your twrp needs to be flashed in fastboot. No command means you are in stock bootloader
[Nexus 6P General] pdpatdwyer:
Worked, thank you very much

also found original? post here

has to flash new twrp, redo original process, then booted into oreo.

Thank you all,

cheers
[Nexus 6P General] Scyzor:
I have followed steps from the OP + flashed "bootloop" image fix but now I'm stuck on infinity Android logo (those spinning colorful dots). What part went wrong?

How can I check also if I have disabled those cluster cores?
[Nexus 6P General] TeahouseFox:
Hi - If anyone can figure out what I'm doing wrong, I could use a little help.

I was previously rooted on MMB29P and in December decided I really needed to update, so I followed the OP to reflash with the factory image, at the time OPM1. When I was done, my bootloader was still unlocked, but I wasn't rooted. I was in no rush, I figured I'd re-root after the holidays. Fast forward to last night, I went back to it by flashing TWRP 3.2.1 as the recovery, then booted into TWRP and flashed SuperSU 2.82, wiped the davlik/cache and rebooted.

It stuck on boot, with the word Google, and the unlocked symbol at the bottom for 30 mintues. I rebooted into the bootloader, reflashed the OPM1 files to at least get my phone back working for today, but I'm not rooted still. I probably reflashed TWRP/SuperSU like three times, and I don't know why it's not working.

I did notice that TWRP never offers to download SuperSU (even though you aren't supposed to accept that) and never asks about mounting the system read only. Any idea what I'm doing wrong? :confused: All I'm looking for is stock, but rooted, without losing my internal storage contents.

Thanks in advance,

Tea
[Nexus 6P General] Badger50:
I don't think SU works anymore on 8.1. Your going to need to use magisk 15.2. I just upgraded my 6p to 8.1 yesterday as well with the factory image. Fastbooted twrp, then flashed Ex kernel, then magisk 15.2 and all is working perfectly :good:
[Nexus 6P General] ffejy462:
SuperSU isn't actively being developed (2.82 sr5 was last release). Technically the last supersu works, but doesn't show up in app drawer (there's an easy workaround).

I'd recommend flashing the latest firmware (8.1 January) via fastboot, latest twrp (3.2.1), and latest magisk (15.2). You should be fine with that setup.

In case you didn't know, magisk is an actively developed superuser and root hide method (it does a few more things too).

If you'd rather use supersu, download the version I indicated from the beta thread. After flashing, extract the apk from the zip with a file explorer, and tap to install like an app.
[Nexus 6P General] TeahouseFox:
Thanks - I've seen Magisk mentioned here and there, and if SuperSU has ceased development, I'll look into it for my next root.

---------- Post added at 19:59 ---------- Previous post was at 19:50 ----------

Awesome! The beta did the trick. I was using Nova as my launcher, so my SuperSU icon never went away, it just said it couldn't detect root. After flashing the SR5 beta zip, my Nexus 6P rebooted properly and detected root when I launched SuperSU Pro.

I did want to still use SuperSU - It's a shame it's no longer developed. I will do some reading on Magisk before I feel comfortable trying a different root method and understand the app better.

Thank you for your help!
[Nexus 6P General] ffejy462:
I was hesitant on using Magisk too, but considering the falloff of supersu, I gave it a try, and so far, pleasantly satisfied with the results. The root hide was a bonus. No longer have to side load Netflix. (there is a suhide for supersu, but I haven't used it)
[Nexus 6P General] Az Biker:
While I can't speak for Magisk on the 6P (mine is still running last SU release), I can tell you Magisk works well on the new Pixel 2 XL.

There are a few different processes when using Magisk, but it is nothing difficult at all.

Check out the Magisk thread HERE.