yashsingh1/xdaforums huggingface dataset:
[Nexus 6P General] Badger50:
Scroll down when you get to the backup menu in twrp. EFS is there :good:
[Nexus 6P General] jc1266:
Pls help still can't find my efs partition

..thank in ady
[Nexus 6P General] scrin378:
Scroll down...it should be on the end of that list
[Nexus 6P General] jc1266:
I am so stupid .. finally found..it thank mate
[Nexus 6P General] McJesus15:
Just tried this method and everything went great until I tried to flash TWRP. It fails every time. I'm attaching a log of the command window. I've tried using other USB ports to no avail. I don't have another type C cord at the moment to try to eliminate that as a cause. I've been away from the rooting world for quite a while but I'm not a noob, that's for sure lol, so I can provide any additional logs if necessary
[Nexus 6P General] scrin378:
As i can tell, your first command is wrong...you cant flash recovery from recovery...it should be "adb reboot bootloader" from there you should be able to flash recovery image ;)
[Nexus 6P General] McJesus15:
I assure you that I'm not trying to push the recovery image while in recovery, haha. What you are seeing is my last attempt to see if twrp would boot if I rebooted that way. If I wasn't booted to the bootloader then it wouldn't list a device after the "fastboot devices" command.
[Nexus 6P General] scrin378:
Yes..i thought you did that...:) Well, i cant think any reason why it doesnt work...

Like you said..maybe to try change cable, but i doubt its cable...are you using latest platform tools??
[Nexus 6P General] erreterr:
How to ulnock bootloader when device hanging at Google logo?

Thanks
[Nexus 6P General] Badger50:
How did that happen?

Was it random, or did you do something?

Have you been in the OS to toggling OEM unlocking and USB debugging?
[Nexus 6P General] erreterr:
Just received in this condition from one friend. Wanted to help him to repair the problem
[Nexus 6P General] Badger50:
Well, since you don't know what the condition is of the system and OS. You'd likely be better off to go into stock recovery and do a factory reset, then see if the OS boots up. If it doesn't, then there's nothing much you can do since your pc probably doesn't recognize the device yet, and would make it impossible to unlock the bootloader.
[Nexus 6P General] sufy1000:
Hi, i've got the Pixel Experience ROM on my Nexus 6P, i want to put stock Oreo 8.1.0 on it, what's the procedure in doing so? i'm a newbie when it comes to this kind of stuff lol. My bootloader is unlocked.

Thanks
[Nexus 6P General] ffejy462:
Back up your internal storage off device. Download factory firmware from Google and follow it their instructions. You'll need working knowledge of adb and fastboot, but it's in this thread's op.

Factory firmware:

https://developers.google.com/android/images

Platform tools:

https://developer.android.com/studio/releases/platform-tools

In the future, it's best to know how to return to stock, have all necessary files to do so, and a working pc beforehand. You don't want to be in a position of a junk rom, mistake, etc etc and have no recourse.
[Nexus 6P General] Droid_Nut:
I am trying to flash my device with the latest 8.1.0 (OPM7.181205.001, Dec 2018). For the life of me, I can not connect to fastboot. Tried it in windows 10, Linux no go. I can connect in the Android recovery, but not in TWRP, I am also able to pull up the serial number with adb devices? Kind of at a loss here.

OTOH, any way to upgrade the image through TWRP with no PC, I can recover data if that's a problem.
[Nexus 6P General] Badger50:
Yes, you can flash the OTA zip in twrp. When done, then flash twrp and magisk again to maintain root and recovery before you boot to the OS. As far as fastboot goes, are you on the latest version, and/or tried another cable?
[Nexus 6P General] Droid_Nut:
I am on platform tools R28.01. I even moved the fastboot from the download to replace the default /usr/bin/fastboot with the new one. Also tried another cable.

Are the factory images the same as the OTA? So TWRP will be wiped out with the latest OTA? What about Gapps or radio, is that all in the OTA?

Thank you
[Nexus 6P General] Badger50:
Yes, the OTA's are the same as the factory images except for the fastboot stuff of course, and yes, twrp and root will get wiped since your flashing the stock recovery again. Gapps, and radio, are in there as well. I've done both OTA's, via twrp, and factory images with fastboot on my 6p and P2XL without issue :good:
[Nexus 6P General] Droid_Nut:
So you are saying, that TWRP will still be running in memory, after installing the factory image, before I reboot the phone?
[Nexus 6P General] Badger50:
Yes. However, if you don't flash the twrp installer zip before you boot up, then it will be gone. And since your having trouble with fastboot, you don't want to loose twrp :good:

---------- Post added at 12:26 AM ---------- Previous post was at 12:07 AM ----------

Also, on the 6p, I recommend that you disable screen lock, and any substratum themes you have installed before you flash :good::good:
[Nexus 6P General] Droid_Nut:
Great thanks, in what directory should I download the files to on my Nexus so they don't get wiped during the flash?
[Nexus 6P General] Badger50:
Nothing gets wiped during the flash, it's an OTA which doesn't wipe data. My procedure was.....

Download the OTA to wherever.

Set screen lock to swipe, disable substratum themes.

Reboot into twrp manually with the buttons.

Wipe dalvik/cache.

Flash the OTA. When done, flash twrp.zip, then magisk.zip.

Boot up, and you should be good to go :good:
[Nexus 6P General] Droid_Nut:
Thanks again, and again.

I guess the only reason Heisenberg said to use the fastboot method was to preserve root and TWRP.
[Nexus 6P General] Badger50:
If you read step #9, you'll see you would still have to flash root again anyway. The OTA trick is something I learned from another developer :cool:
[Nexus 6P General] Droid_Nut:
That worked out great badger, and a lot more pain free than ADB and Fastboot.

Can I pretty much do the same thing on my Moto G5 and any other android with TWRP for that matter?

I had my 6P on MM last OTA before rooting for 2 years because I did not want to bother with all the hassle of upgrading LOL. With this method I will be an upgrade whore. :p
[Nexus 6P General] Badger50:
Glad you like it my friend. I really couldn't tell you anything about the other phones. The premise makes sense, but the mechanics may be different from those manufactures. Best to look in those particular forums :good:
[Nexus 6P General] Droid_Nut:
Will do, thank you.
[Nexus 6P General] baxxter106:
i did a down/upgrade of my wifes moto g5s plus, but with fastboot in Linux. the phone was on lineage 15.1 inofficial. i downloaded the original images for n and o and did exactly all the steps that are written in the included XML file - with fastboot command. first downgrade to n and then upgrade to o. but i overwrote all the data area so it is like a new phone.

and also at my wifes "new" samsung s7 i did the twrp flash with fastboot and not Odin because of lack of a win system. rooting worked like charme and she is still able to use gpay aso...

fastboot and adb is always a good way to keep control of anything you do with your devices... ;)
[Nexus 6P General] Droid_Nut:
I just did this with TWRP on my G5 Plus, (non S)

https://xdaforums.com/g5-plus/development/oreo-twrp-flashable-stock-builds-coming-t3830482
[Nexus 6P General] Badger50:
Very nice! Now your the teacher :good::good:
[Nexus 6P General] raduvasile:
Ok
[Nexus 6P General] Badger50:
Glad you approve :confused:
[Nexus 6P General] pangas:
I was following this guide to root my Nexus 6P (ie. install TWRP and Magisk). I got everything installed alright, but after installation the Magisk SafetyNet check would fail on both ctsProfile and basicIntegrity. When I enabled Core-Only Mode and rebooted (as instructed in the Magisk tutorials) the check would pass, but that's where I'd get stuck because the tutorials went on to tell me to disable Magisk modules one by one to find the module that was causing the check to fail, but I wasn't running any modules.

Anyway, after some hurdles (including trying the latest Canary build of Magisk, which for whatever reason seemed to pass the SafetyNet checks... but I didn't want to use a debug version in daily use), I wound up reinstalling everything from scratch by factory resetting the device and reflashing the factory image (as instructed in the OP of this thread). This time when TWRP asked me if I want to do system modifications, I disallowed them — contrary to what is instructed in the guide in this thread's opening post. I then installed Magisk through TWRP as normal and booted into system... and lo and behold, the SafetyNet test was passing like it should.

I'm posting this in case someone in the future has the same problem I did. I guess the lesson here is: don't allow system modifications in TWRP unless you need to, and if you're having SafetyNet issues with Magisk, it might be because you allowed system modifications in TWRP.

If you've already allowed system modifications, you might have to do what I did and re-flash the factory image. Hopefully someone more knowledgeable can tell us if there's a better way.
[Nexus 6P General] scrin378:
What is the point of TWRP then if you dont allow modifications??
[Nexus 6P General] pangas:
I used it to install Magisk. Presumably you could also use it to install custom ROMs or whatever else you might want to do. It didn't seem to be actually necessary to enable them for this purpose.

All I know is that if I did allow /system/ modifications for TWRP, the SafetyNet check in Magisk would fail.

EDIT: I'll just reuse this post to provide the answer to another problem I was having that I had trouble finding the answer to on Google:

I wanted to disable developer mode (because some apps, such as my bank's payment app, check for it and refuse to work if it's enabled). However, flicking the switch at the top of the Developer Options screen to "Off" would also flick the switch for the Disable OEM Unlock option. Because it's unclear whether disabling this option locks your bootloader or not, and you must not lock your bootloader on a non-stock device or you'll risk a brick, I did not have the balls to turn off the developer options this way.

However, there's another way: long press on the Settings app in the app menu, drag it to "App Info", and delete the app's data through here. This hides the Developer Options menu, presumably without changing any actual settings, and was enough to satisfy my payment app. It also didn't lock the bootloader (as I confirmed by rebooting into bootloader).
[Nexus 6P General] x7aa1186:
Good Day, I have a problem with my nexus 6p

I have followed this guide to the T have used I had the latest version of android installed.

Unlocking the bootloader worked fine

Installed the Custom recovery with twrp-3.2.3-0-angler. that worked fine also

Created all recovery files.

and then tried to flash super SU v.282-201705271822

after flash with twrp the phone is now stuck in a boot loop. - Only the white google logo is displayed.

I have tried to restore the 2 different backups I made while installing custom recovery, and have tried to wipe system /factory reset etc.

still the system is stuck in the bootloop on the Google logo.

Any help?
[Nexus 6P General] x7aa1186:
Good Day, I have a problem with my nexus 6p

I have followed this guide to the T have used I had the latest version of Android installed.

Unlocking the bootloader worked fine

Installed the Custom recovery with twrp-3.2.3-0-angler. that worked fine also

Created all recovery files.

and then tried to flash super SU v.282-201705271822

after flash with twrp the phone is now stuck in a boot loop. - Only the white Google logo is displayed.

I have tried to restore the 2 different backups I made while installing custom recovery, and have tried to wipe system /factory reset etc.

still the system is stuck in the boot loop on the Google logo.

Any help?
[Nexus 6P General] ffejy462:
[MENTION=7384838]x7aa1186[/MENTION]

Please do not quote the entire op.

Your best bet would be to start over and flash factory firmware.

Then use magisk rather than SuperSU.
[Nexus 6P General] NatesLaw:
------------

Hello.

I've only recently purchased a brand new 6P (now on stock Oreo 8.1) since it was so cheap and my good ol' LG G3 finally died. I used to LOVE Resurrection Remix and see it's available for this phone (with Pie).

However, it's been so long since I've been in the root game and don't want to scan through 600+ pages (mostly outdated, more than likely) so any update as to whether the above worked with Magisk?

Thanks in advance for any help. It would be greatly appreciated.

Regards,

NatesLaw
[Nexus 6P General] ffejy462:
I don't see why it wouldn't...

SuperSU has been out of development for quite a while. Magisk is stable and works well. I'd be willing to bet RR development suggests using magisk, but read its op carefully and ask for clarification is it's not indicated.
[Nexus 6P General] NatesLaw:
Sounds good. Thanks for the reply :good:

Edit/Update (for anyone interested): I was a little rusty as it's been well over a year since I last rooted but this guide still works. Just make certain that when you flash TWRP you also flash Magisk before rebooting or TWRP won't stick. I'm now running Pie through Resurrection Remix on my Nexus 6P. ?
[Nexus 6P General] Kroniq:
I've owned every Nexus to date, even 2 pixel 2 xls, but this time ive ran into a problem trying to root my 6p. The phone is not being recognized in Windows 10 no matter what I try to do. Won't recognize mtp, ptp or ANYTHING, all it does is charge. It won't even give an option to change USB mode when I plug it in unless I go to dev options, and even then it does nothing. Also, fastboot and adb don't pick up the device.

This is what I've tried so far:

Turned on USB debug

Tried 3 different cables, and 5 different usb ports

Tried to update to latest Google drivers and nothing.

Done the Pnputil commands and deleted some .inf and reinstalled drivers

Updated windows to latest build

Tried wugfresh

Downloaded Android sdk

Still no go... this **** used to be easy, where did I go wrong? I have NEVER had a problem rooting Nexus devices until this one.
[Nexus 6P General] JLnyXDA:
Had the same problem, I just tried with another computer and Bam! It worked
[Nexus 6P General] Kroniq:
It was the USB cables :rolleyes:

Although they still worked for the pixel 2 xl, they wouldn't for the 6p. I feel like an idiot, but at least I'm now rooted :D
[Nexus 6P General] marianodelfino:
Great post! I was sweating like a mad man on every step
[Nexus 6P General] ambivalentSoul:
"If it returns a version number for Android Debug Bridge then you're good to go."

What if it doesn't return a version number? I followed the steps; turned on the bootloader on my Nexus 6p. Downloaded the angler files, then opened up the cmd prompt from the same folder. But when I send the command adb devices it doesn't list any devices. I'm very noob at this. Any help is appreciated. Thank you!
[Nexus 6P General] Warren_Orange:
Hi.

I am new to the Nexus 6p. I have stock Oreo with a password and fingerprint. I have just unlocked and installed TWRP 3.3.3-0. When I first loaded TWRP it asked me to decrypt data, but I just cancelled it as I thought it wasn't needed. I take it this is wrong?

I want to install Magisk and backup my ROM via TWRP.
[Nexus 6P General] Warren_Orange:
^^^^^

I have now tried to go back into twrp but I get the Android on its back saying 'no data'. So the twrp flash never stuck.

I am under some confusion whether I need to format userdata or not. I would prefer not to but if it needs doing it needs doing.

I am going to flash twrp again and use my passcode when it firsts boot. If that does not work I will have to wipe userdata.

Would removing my fingerprint before flashing twrp help?

Twrp is 3.3.1-0

OS is latest stock Oreo.
[Nexus 6P General] wedel219:
Hi, there.

I just tried to root my 6P and flash SuperSU 2.82, and I'm stuck on the Google screen.

I've looked through the thread, and even tried searching through it, and most of the remedies for this seem to be: use Magisk.

If that's what I have to try next, so be it, but I wanted to describe my scenario to see if anyone can help me simply resolve things.

I factory reset my phone, but the OS only went back to 8.1.0. I got the phone in August of 2016, so I don't know why the factory reset wouldn't restore me to Nougat.

However, I proceed, with perhaps reckless abandon. I flashed TWRP 3.4.0.0 and then tried to install SuperSU 2.820201705271822.zip.

And now I'm stuck. It bootloops unless I force it into the bootloader, and then I can access recovery and TWRP, but if I try to turn the phone off, it just starts bootlooping again.

How do I get out of this mess? I'm sorry if it's all laid out in here, somewhere. I did look through a good few hundred posts, but didn't find what I'm hoping is a simple solution to this. That, and I'd just like to know what actually went wrong, so I can learn something from this fiasco.

UPDATE: I can get into TWRP, but there are no directories on my sdcard except for TWRP. Did I blitz my OS altogether? That would explain why it's stuck on the Google screen.

Also, in cmd, my phone is only recognized by adb while in recovery. If I am in the bootloader itself, the "list of devices attached" is blank. Is that information at all helpful to someone wiser than I am?

NO ROOT: I ran 'adb shell su' from cmd, and it says "su: not found," so my attempt at root was clearly unsuccessful.

Thanks.
[Nexus 6P General] Einwod:
I suggest you download the last factory image and using the flash.all bat file, restore the device to the last available updates. Then try Magisk. I found Magisk much better for root than SuperSU which is now sadly way behind and no longer developed.
[Nexus 6P General] wedel219:
Unfortunately, ADB doesn't recognize my phone except in recovery. From what I understand, I need to run flash-all via ADB from the bootloader menu. That's not an option, since whatever I did has made my device unrecognizable from the cmd prompt, unless I'm in TWRP.

Should I just grab the latest OTA* and try flashing that normally via TWRP?

*Or should I grab an OTA older than July 2018, since I don't want to get hamstrung again by that Huawei has rescinded OEM unlocking?
[Nexus 6P General] Spannaa:
Connect your device to your pc via usb, boot into bootloader mode and then run flash-all.bat from a command window on your pc in the folder containing the files from the unzipped factory zip.

ADB only works when your device is booted to system or recovery. it doesn't work if you're booted to bootloader.

Likewise, fastboot only works when your device is booted to bootloader, it doesn't work if you're booted to system or recovery.

Then install magisk
[Nexus 6P General] wedel219:
Hi, there. Thanks for the advice.

What I wound up doing to bring it back to life was flashing the last Android 6 OTA via TWRP.

I'm getting the "your device is corrupt" message, but everything seems to be working.

The reason I went with 6.1.0 instead of a more recent (or the most recent) OTA is because most of the root guides are from when the phone was released. Now, this might elicit an eye roll, and I understand, and I'm sorry for doing so, but I was curious if I followed one of the old root guides since I'm on an old OS version:

Would it work?

Will it remain in effect if I were to flash a more recent OTA?

And should I even flash an OTA if I'm rooted (no, right?)

I realize this is probably obstinate of me that I'm not just updating to 8.1.0 and using Magisk, but part of me wants to understand how this whole process actually works and explore different methods of achieving root. If anyone would be willing to humor both my ignorance and my curiosity, I'd love to bend your ear.

Thanks.
[Nexus 6P General] Spannaa:
The "your device is corrupt" message is because your bootloader is unlocked.

The rest - it's up to you, but I don't really see the point of installing an ancient factory image and rooting it using an obsolete method (SuperSU) then updating to the last factory image and re-rooting using Magisk.

If you must do it your way, the necessary info (including the risks involved) is in the forums, so spend some time searching and reading before you proceed.
[Nexus 6P General] wedel219:
The reason I installed 6.1.0 is because my battery was tanking on 8.1.0 and I was curious if rolling back the version would make a difference.

Idling, it does. However the battery still tanks with regular app use, so it's clearly time to change the battery. I have a replacement.

As for rooting it through outdated means, there probably is no sense to it. After I replace the battery I'll flash an updated OTA and try rooting with Magisk.

Thanks again.
[Nexus 6P General] Spannaa:
Battery replacement is essential on the 6P.

Finding a good one and fitting it without breaking anything will give you another few years.

I still use mine as a backup and as a camera.
[Nexus 6P General] wedel219:
I bought what seems to be an OEM battery. Testing the voltage, it says it's 3.79V and it's rated for 3.82. So, I'm hoping that bodes well.

I just took the OTA that Google prompted me to download, so I'm running 8.0.0 as of now. I'm going to look at Magisk and try to root.
[Nexus 6P General] Spannaa:
Update to the last before Rooting - it's 8.1.0 (OPM7.181205.001, Dec 2018)

Careful not to break the top glass camera lens cover when you fit the battery - it's easy to do if you don't heat it enough for the glue to soften properly.
[Nexus 6P General] wedel219:
I'm on 8.1.0, but I'll double check to make sure I'm on the last available update.

I ordered two backup pieces of the camera glass. It was as cheap to buy two as to buy one, and my original is scratched up anyway from four years of use.

My screen is cracked, however, so I'm betting that opening the device is going to exacerbate that. As such, I bought a new screen that is on its way. Here's hoping it's the real deal. :)
[Nexus 6P General] Warren_Orange:
Hi.

I want to relock my bootloader. I am running stock Android but have twrp installed.

What is the easiest way?

edit - I managed to do it - Phew.
[Nexus 6P General] Warren_Orange:
This was very helpful in returning my Nexus 6P back to stock. At the end guide No. 10 - "fastboot flash recovery twrp". Boot into twrp and wipe dalvik and cache. Boot in OS. Then reboot to bootloader and "fastboot flashing lock". Reboot and it will then wipe the Nexus 6P, returning everything to stock.

Heisenberg mentioned "On 7.1.2 and above you'll also need to boot into TWRP recovery and wipe cache and dalvik cache." but I was not sure exactly what it meant being a bit of a newb. I was thinking "how can you boot into twrp when you have just restored stock recovery??". But you have to flash TWRP again to do the cache wipes.
[Nexus 6P General] Mr.Conkel:
I'm going to be purchasing this device very soon and was wondering if it mattered which Model of the Nexus 6P I received mattered. I'm getting the 128GB Gold version. Are all models bootloader unlockable? I'm trying to make sure before spending $170 on this device if I'm unable to unlock bootloader I don't want the device.

Thanks in advance for any replies hope to hear back soon, Cheers :)
[Nexus 6P General] Einwod:
First rule for using these forums is: DO NOT CROSS POST. You are posting the same question in multiple threads, STOP IT.

To answer your question, the bootloader for Nexus 6P is easy to unlock. Start from the beginning in this thread and read through the early posts to begin with. You'll find lots of information and most everything you need to get your new device the way you want it.
[Nexus 6P General] Mr.Conkel:
Thanks for your advice and sorry about that. I was just trying to make sure I didn't buy the wrong model because I know for other devices like this one unlock methods can vary