yashsingh1/xdaforums huggingface dataset:
[Nexus 6P General] runawaybayeh:
. When I boot my phone it doesn't get any further than an error message that states that it is corrupt and can't be trusted. Then it goes to the screen with white Google letters . If at that point I hold down the power button and the volume down then I can get into the reboot bootloader etc mode. I can get into TWRP recovery from there. I have in my attempts to rectify this tried using the recovery image that I had done with TWRP as per your instructions. That did not work I end up back at the error screen about corruption .

I eventually tried the format data through TWRP,that did not work. , so no longer have the recovery image.

I then tried to reinstall factory image through the SDK tools that you recommended downloading at the beginning of your instructions. I have downloaded the factory image angler 6.01 from the Nexus site. I am stuck there. I am not very familiar with command prompt commands I have not been successful in installing the factory image.

When I give the command ' fastboot devices' it comes back with my serial number .

I have unzipped the full Angler factory image and tried to follow commands as given on the Nexus factory image website as given below

'Connect your device to your computer over USB.

Start the device in fastboot mode with one of the following methods:

Using the adb tool: With the device powered on, execute:

adb reboot bootloader

-

If necessary, unlock the device's bootloader by running:

fastboot oem unlock

The target device will show you a confirmation screen. (This erases all data on the target device.)

Open a terminal and navigate to the unzipped system image directory.

Execute the flash-all script. This script installs the necessary bootloader, baseband firmware(s), and operating system '

when I give the command 'adb reboot bootloader' it comes back with the' error :more than one device\emulator'

when I give the command 'fastboot oem unlock'it comes back with the error 'failed:remote unknown command'

if I navigate, having started in the SDK platform tools window, with the command prompt as you suggested, to the folder on another drive ,where I have the full unzipped factory image and give the command 'flash all' it comes back

'flash' is not recognize as an internal or external command operable program or batch files'

Any help would be appreciated. Sorry for the bother.
[Nexus 6P General] ultyrunner:
This may not be quite the right place to ask this, but it's related and all the Mac tools forum threads are closed, so ... I've got ADB and Fastboot installed on my Mac via Nexus Tools 2.8 by [MENTION=4516295]corbin052198[/MENTION]. Just wondering if he or anyone using ADB/Fastboot from terminal on a Mac can tell me whether I need to put the files in /usr/local/bin or I can just flash them from anywhere with the full path in the command?

Thanks.
[Nexus 6P General] ^tyrant^:
this is for anyone that has SuperSU-v2.62-3 installed. if you open the app and goto settings what version does it show? i have flashed the zip twice and it says SuperSU-v2.62 is that right?
[Nexus 6P General] Badger50:
Apparently it is. No biggie though. As long as it works is fine with me.
[Nexus 6P General] ^tyrant^:
thanks, i just wanted to make sure the flash took
[Nexus 6P General] NPOA556:
I'm not the expert on this, but a few things come to mind.

Just power down the phone and then hold volume down and power until you see the bootloader screen.

The command is 'fastboot flashing unlock'.

Are you giving the actual command 'flash all'? That's not a recognized command. If you are trying to use the flash-all.bat batch file, just double-click the file while the phone is in the bootloader and connected to your computer.

---------- Post added at 03:18 PM ---------- Previous post was at 03:18 PM ----------

Yeah, mine is showing the same thing. I hadn't noticed it because everything seems to be working fine, so I didn't think to even check it.
[Nexus 6P General] Heisenberg:
Isn't your bootloader already unlocked? If so, you don't need to unlock it again, plus "fastboot OEM unlock" isn't the right command. Follow my instructions on how to flash the factory images in section 11 of this guide.
[Nexus 6P General] runawaybayeh:
heart rate

Thank you very much Mister Heisenberg,I now have a phone again. When my heart rate is back down i will revisit rooting it.
[Nexus 6P General] azsl1326:
I am stuck trying to make my first set of backups listed in this guide. I installed TWRP 2.8.7.2 and rebooted into recovery to create my first backups. Upon entering recovery, I get a message about decrypting data and entering a password. First time, I skipped this and just tried to make a backup and it failed - something about encryption/decryption. I did remove all security on the device before beginning this process.

Also, there was a message the first time I was in TWRP regarding keeping the system read-only. What choice am I supposed to make here?

Thanks, in advance.

---------- Post added at 10:04 PM ---------- Previous post was at 10:01 PM ----------

So it appears I did something (very) wrong as when I rebooted now I am getting a password message to decrypt. I am stuck!!! Any help is greatly appreciated.

UPDATE: So I went ahead and formatted the data partition despite the guide saying it was no longer necessary. That seemed to fix the issue. I elected to allow changes to the system (not keep it read-only). What's the downside of this choice?
[Nexus 6P General] corbindavenport:
For Nexus Tools, you don't have to type the full path to the ADB/fastboot commands or put the files in a special location. Just the full path to the file (or drag the file into the Terminal window).
[Nexus 6P General] runawaybayeh:
NPOA556 Thanks to you as well for pitching in, that's community. Thanks.
[Nexus 6P General] ultyrunner:
Awesome, that's exactly how I expected it to work. I'm play with both GUI toolsets and yours, but I'll admit to loving the simplicity and specificity of using the command line. Well, that and being able to flash individual images if, for example, I wanted to keep TWRP, root and stay pretty much stock Nexus.
[Nexus 6P General] BeerFuelledDude:
Just a warning/reminder to anyone who is similarly new to all this. I rooted on 6.0 using this guide and used the latest TWRP. Something messed up and de-crypted my phone. Anyway, I tried re-encrypting using the settings on Android (nothing fancy)...it didn't do anything other than show me the android logo after two hours. Gave up and thought I'd try again in the future. Just went through the whole flashing 6.0.1 and then booting up - stuck there for 20 minutes and I thought I should restart it because it was getting hot. After reboot it told me the encryption process had been interrupted and I have to reset again. Marvellous.

This experience would've been greatly improved if Android told me what it was doing during boot instead of looking like it had crashed. Lesson learned, though.
[Nexus 6P General] Kremata:
I want to return to factory, so I downloaded the factory file "angler-mmb29m-factory-8c31db3f.tar".

Inside there was no folder. Only a file with the same name "angler-mmb29m-factory-8c31db3f".

I took a chance and renamed it angler-mmb29m-factory-8c31db3f.zip.

Inside the zip there was

Boot.img

cache.img

recovery.img

system.img

userdata.img

vendor.img

android-info.txt

NO

bootloader-angler-angler-xx.xx.img

radio-angler-angler-xx.xx.img

I downloaded the file 3 times and it's always the same thing. I don't how to proceed?

Thanks in advance for anyone who can help.
[Nexus 6P General] Krunk83:
Getting my 6P today and I am going to unlock the bootloader and run stock with the Cataclysm ROM mod and a custom kernel. To get the unencypted data do I still need to flash the unencrypt datauser file? It says in the step that if I am running TWRP 2.8.7.1 or higher that the step is no longer needed. I will be running TWRP 2.8.7.2. Does TWRP do this for me already when I flash it? I am a bit confused by this, sorry.
[Nexus 6P General] ycats:
good question, wanting to know if any have decrypted using the latest TWRP and if it worked well or not
[Nexus 6P General] napes22:
Is there any benefit to flashing userdata? I'm going to try to return to stock to see if a video issue I have is my device or if something got corrupted.
[Nexus 6P General] Mesmurized:
The first file downloaded is a *.tgz file. Extract that yields one tar file.

Extracting that yields bootloader, radio, a *.zip file, and supporting files.

Extracting the *.zip file yields Boot, cache, recovery, system, userdata, vendor imgs

See Step 11 Post #1 for more info.
[Nexus 6P General] Kremata:
For some reason, the downloaded files were "tar", I renamed them "tgz" and all the images appeared. Thanks!
[Nexus 6P General] Mesmurized:
I don't see any. In fact, it could cause problems if your device memory is larger than the one from the userdata's img. IE: On my 5X 32GB, if I flash the userdata img it will set my user partition as if it's a 16GB phone.

If necessary, I've read many posts recommending a format of the userdata partition over flashing the image.
[Nexus 6P General] sparkster666:
I must be missing a step. I followed you instructions and installed twrp-2.8.7.2-angler.img but every time I reboot and try to re enter recovery I only get the android on his back. Is there a step I must do so the recovery survives a reboot? thanks in advance.
[Nexus 6P General] Heisenberg:
If you want to permanently decrypt you need to format the userdata (internal storage) partition:

fastboot format userdata

If you want to remain encrypted you don't need to do anything, as the latest TWRP can access the encrypted data.

As long as you format (not wipe) the internal storage it should work without any issues.

No benefit at all, in fact, it will cause problems on the 64gb and 128gb devices, that's why it isn't included in my instructions. If you want to completely wipe your internal storage you can just choose to do so in the advanced wipe menu in TWRP. Or you can format it with fastboot:

fastboot format userdata

Not sure why this is happening for you. A couple of people have reported this problem, I'm not sure if we ever got to the bottom of it.
[Nexus 6P General] sparkster666:
Thanks. I think I found a workaround I can enter twrp with the twrp manager app. Ill keep testing.
[Nexus 6P General] napes22:
This is likely a silly question - but I used section 11 to return the device to stock.

I was expecting the outcome to the a fresh out of the box device (at 6.0.1) with my SDCard partition intact and everything else at stock. However upon reboot, all my apps, contacts, texts, etc were still intact when I rebooted. Is this how the return to stock is supposed to work?

Will not wiping data and continuing to use my phone as if cause any issues? Additionally, after flashing the system update menus has disappeared from settings/about phone.
[Nexus 6P General] doumer:
Hi, I've just followed section 10 to update to 6.0.1 and ended in a bootloop at "starting apps". After that I reflashed TWRP and installed supersu 2.6.2-3 and also got a bootloop with the android-logo. Did anyone experience similar problems? did I do something wrong by flashing everything and then tried to reboot before installing TWRP and SuperSU again? Did then a factory reset, reflashed everything and restored my stuff with Titanium backup, now it's working fine but restoring all apps is quite a pain...
[Nexus 6P General] srqrob:
Upgrade to 6.0.1, installing TWRP and systemless root all went perfectly using your instructions. Really nice to still have all my apps and data. Sure a painless way to accept an upgrade. Thanks.
[Nexus 6P General] Heisenberg:
I've just edited the guide to include a factory reset in the beginning of the process. Following the guide the way you did, what you're experiencing is normal because no wipe of the user data was performed. You should have no issues using the phone as is, but the fact that the update menu has disappeared throws a warning flag up for me, that doesn't sound right. It might be an idea to undertake the process again, including the factory reset at the beginning, to ensure that everything is the way it should be. Make a backup of your data and transfer it to your PC first though, so you can copy it back to the phone afterwards.

The fact that you didn't flash TWRP and SuperSU before booting the phone won't be the reason for the phone locking up during the "starting apps" phase. It could be that there were some incompatible apps or settings or something that were causing a conflict. You were rooted before right? What root apps did you have installed?
[Nexus 6P General] doumer:
Right, did the systemless root. Root apps are Titanium Backup, AdAway, Greenify, Terminal Emulator, Simple Reboot and Tasker (sort of – using it to grab some appdata and sync it between my devices).
[Nexus 6P General] Heisenberg:
My guess is that the retention of one or more of those apps (and its/their data) caused a conflict. If that is the case, flashing SuperSU again before the first boot probably would have helped. It's hard to say definitely though.
[Nexus 6P General] doumer:
Thanks, gonna try that the next time ;)
[Nexus 6P General] higgins290:
so i go to verify fastboot works..... i boot phone into boot loader via power button and down key. then through the same console i used to do the ADB checks etc. i use the [fastboot devices] command but it does nothing and starts a new line in the console. it doesnt show me the serial number etc like it should if its working. ADB checks came back good. usb drivers are all good. i do notice the device will say to plug in a USB cord even when one is plugged in when in bootloader and dowload mode in bootloader is disabled if that matters. usb debugging has been enabled of course. idk what to do and i dont want to go further of course with fastboot not communicating.
[Nexus 6P General] Krunk83:
Do you have USB debugging on in developer settings?

Sent from my Nexus 6P
[Nexus 6P General] higgins290:
yes USB debugging is enabled via developer settings. i feel like im just a magnet for stupid complex (yet probably simple) problems. i uninstalled and reinstalled USB drivers and no luck either.
[Nexus 6P General] Krunk83:
Make sure that you've installed the SDK toolkit like it says in the intro of the guide. That's what I did because mine was out of date and not working, then it worked.
[Nexus 6P General] higgins290:
Yeah I did it as per the instructions but I'll just try deleting and reinstalling maybe.
[Nexus 6P General] Krunk83:
If it's not even detecting the device that's the only thing I can think of. Gotta get that installed properly before anything.

Sent from my Nexus 6P
[Nexus 6P General] higgins290:
Well and that's the weird thing ADB works and passes checks just fine so to speak it's just like the computer and phone aren't communicating when the phone is in bootloader is all. Idk if the Google USB drivers are for that?
[Nexus 6P General] Heisenberg:
The Google drivers are for that. It isn't all that strange because adb and fastboot use separate drivers. Do you have any drivers installed on your PC pc for other phones?
[Nexus 6P General] higgins290:
ah i see. just as i had thought. no i dont have other drivers but it installed the generic MTP driver everytime i plug it in anywhere. i tried uninstalling the driver through device manager and reinstalling google driver and even tried manually installing it through device manager. still didnt seem to stick. i notice when my phone is in boot loader it comes up as "android" on my computer and has a yellow triangle next to it due to not having a driver. thats why it cant comunicate. so thats where i was trying to put the google driver of course. i just cant figure out why it didnt install in the first place.

---------- Post added at 05:30 AM ---------- Previous post was at 05:10 AM ----------

figured it out finally. redownloaded SDK completely and it worked flawlessly. file was slightly bigger then other one i downloaded therefore probably had a corrupted file for who knows what reason. same exact file etc. installed it the same way. it just simply worked. thank you for your time sir. :D
[Nexus 6P General] Sh0X31:
Hey Guys,

I rooted my Device, format userdata and flash SinLess Rom. After I start my N6P and see this (See Attachments). Is this normal if your unlock your Bootloader and anyway to skip this?
[Nexus 6P General] GCbard:
Normal.
[Nexus 6P General] TigerSoul925:
I rooted and got everything ready incl supersu and busybox in please. Then I wiped in twrp to get a fresh start before getting stuff installed. When rebooting after the wipe, I no longer have supersu or busybox however. I thought those were /system apps, how could they be gone? What do I do here, just redo the procedure to root+adding busybox?

EDIT: Excuse my ignorace, I managed to miss the piece of information that says system less rooting goes away after wiping. SORRY FOLKS. Keeping this here for other dumbnuts to find.
[Nexus 6P General] srqrob:
Not only Normal, but I believe impossible to banish short of returning to stock and locking the bootloader.
[Nexus 6P General] higgins290:
the only thing i wish this had or i wish i could find is a list of which ROM's are project-fi supported. i searched the forums and couldnt find anything. i mean obviously anything based on stock ROM should work but i do know a few AOSP ROMS do as well just dont know which ones past pure nexus.
[Nexus 6P General] Heisenberg:
That's normal for a phone with an unlocked bootloader. There's nothing you can do about it.

Surely the ROMs would have this noted in the feature list?
[Nexus 6P General] higgins290:
Some of the ROMs that specifically support it do like pure nexus for example but some others like chroma don't say anything and I see other users saying it's compatible after scrolling halfway through the thread. I can try to make a thread myself on what's compatable if I can figure things out.... I feel like such a noob
[Nexus 6P General] Heisenberg:
Have you tried entering what you're looking for into the search box? It's usually pretty reliable.
[Nexus 6P General] higgins290:
Yep searched on there for quite a while. Closest I got was a thread asking the same question with no viable answer. If someone else wants to look and make sure I'm not being blind.
[Nexus 6P General] Heisenberg:
Sorry, I meant searching within the ROM threads, of the question has been asked you'll find your answer that way.
[Nexus 6P General] OneManArmy:
Rom Error / Compatability (cyanogenmod)

Hello everyone,

I'd like to first say thank you to the thread creator for making such an awesome thread with so much pertinent and viable information. I'd also like to thank everyone who has contributed great info that helped me get to here.

I will try to summarize the issue I am having so hopefully anyone else having this issue can easily find it and solve it too.

[ Environment ]

Linux - Fedora derivative

Android SDK w/ Platform tools for adb and fastboot

Nexus 6P

cyanogenmod for angler

TWRP - recovery

I started with the fresh Nexus 6P and worked my way through these steps:

Prereqs

Step 1 <~~~ completed w/o errors

Step 2 <~~~ completed w/o errors

Step 4 <~~~ completed w/o errors

Step 5 <~~~ completed w/o errors

Step 6 <~~~ completed w/o errors

Step 8 <~~~ completed, but errors after trying to boot into cyanogenmod

​

All of the steps worked well, seemingly, and I was able to install cyanogenmod along with gapps.

After wiping the dalvik/cache and then rebooting into the system. The phone booted normally until the cyanogenmod android face splash screen which hung there for a really long time. I want to say I let it sit there for about 20 mins before I decided to reboot into recovery and see if I did something erroneous. After that, I tried to do another full wipe and reinstall cyanogenmod. Same error. Next I tried to restore my backup. Same error except it hung on the Google boot screen. I was only able to get back to a working system by full wiping, restoring my backup, and then doing the systemless SU.zip which worked and gave me a functioning system.

I searched this thread quite thoroughly and the only thing that seems to have caused a problem is the encryption. When I reboot my phone, it will give me screen that says:

"Your device software can't be checked for corruption. Please lock the bootloader." - Ok, annoying but due to me unlocking the bootloader in step 1

There was another one, when I was trying to due the cyanogenmod about a corrupt encryption but I don't remember the exact verbiage. I think there was a post about this, but it was for someone doing a full flash.bat or something like that which I didn't do.
[Nexus 6P General] Heisenberg:
I can't really help with this as I don't run CM. There has been some talk of this problem with CM not booting in the Q&A section I believe, it might be worth checking there to find an answer.
[Nexus 6P General] OneManArmy:
Where is this Q&A?

I went to here and double checked to make sure it is the same as described here for installing the ROM.
[Nexus 6P General] Heisenberg:
I meant the Q&A sub-forum for this device here on XDA.

Nexus 6P

http://xdaforums.com/nexus-6p

Nexus 6P General

http://xdaforums.com/nexus-6p/general

Nexus 6P Q&A

http://xdaforums.com/nexus-6p/help

Nexus 6P Android Development

http://xdaforums.com/nexus-6p/development

Nexus 6P Original Android Development

http://xdaforums.com/nexus-6p/orig-development
[Nexus 6P General] runawaybayeh:
One debrief question:

everything went well, following your guide till I rebooted after having flashed SuperSu in twrp. When I rebooted there was a notification that SuperSu was being installed while also saying that I needed to install SuperSu,that I wasn't rooted yet,that I could install it with twrp or (Im afraid I can't remember the other option) this was where I should have let it continue to install SuperSu?... Rather than second guessing and stopping the process?
[Nexus 6P General] Heisenberg:
There's a note in the root section that addresses this:

You were right to ignore this.
[Nexus 6P General] goddammit:
So what folder should I put it on? The "/sdcard" folder that TWRP sees is always empty and if I boot Android I'm not allowed to put that file anywhere outside of Internal Storage because the phone is not rooted - this is a catch 22 situation.
[Nexus 6P General] goddammit:
Yes, I've tried all of that. The last step is not valid, because TWRP sees and empty "/sdcard" folder when it boots and if I boot Android I am not alowed to put the SuperSU zip anywhere outside of Internal Storage folder anyway, because the phone is not rooted - so this is a catch 22 situation.

Did anyone manage to systemless root 6.0.1 yet?
[Nexus 6P General] u89taper:
Yes. Did your read the steps I wrote on how to do the process further back in this thread? I've done this on a Nexus 6p, 6 and 5 successfully. Followed these steps and its worked every time.

http://xdaforums.com/showpost.php?p=64280720&postcount=1551

If I were you, I'd start fresh. I'd follow the steps I've listed but make a few modifications:

A) I'd hold off on downloading SuperSU (step 1) until the very end

B) I would format user data. This will totally erase and format the data on your phone. All of your songs, pictures, etc will be erased. To do this, at the end of step 4 but before step 5: fastboot format userdata

C) So again... This order. Steps 2-8. Step 10. At this point you'll have a fresh install of Android with TWRP installed. Set Android up then do Step 1 (download SuperSU 2.61). Reboot into TWRP/recovery and follow Step 9 (the SuperSU zip will be in /downloads folder by default if you downloaded using Chrome)

I've highlighted important things in bold. Systemless root is working on 6.0.1. Android Pay is working. AdAway is working. Root Explorer is working. Can't attest to anything else.
[Nexus 6P General] goddammit:
Will wiping the user data really make the difference? I was hoping to avoid that, because it will take me hours to get everything back. Did you do that when you were upgrading?