yashsingh1/xdaforums huggingface dataset:
[Nexus 6P General] BankZZ:
So, I have flashed the system image from google before I read that the userdata.img would cause problems. I have the 64GB version. Under "Storage & USB" it says Internal storage is 53.67GB. Do I have a problem? How do I fix?
[Nexus 6P General] a1exus:
I do too have 64GB version, and also same 53.67GB, bare in mind that there is some overhead for Android system on your flash and file system as well have some overhead, in other words that's normal)
[Nexus 6P General] BankZZ:
I get that and it seems OK. The only reason why I am worried is because of the guide and it says not to flash the userdata.img on the 64 and 128GB models.
[Nexus 6P General] SlimSnoopOS:
It would change the default storage to 32 GB if your were to flash the userdata.img. That's essentially what the bullet point is referring to.
[Nexus 6P General] BankZZ:
How can I tell if I have the problem? My system storage says it's 64GB even those I did flash userdata.img.
[Nexus 6P General] khapp:
Boot time after dalvik cache

Hello,

I unlocked and flash the official android images, started up, then flashed again TWRP, then in TWRP flashed SuperSU and chose to wide data, cache and dalvik (to get a fresh new install with a rooted phone).

The phone is starting since a while now (about 10-15min). I don't know if it hangs or if a clean startup takes time ?

Phone: Nexus 6P.

Thank you!
[Nexus 6P General] mobileman88:
It's encrypting your data partition. Do not interrupt the process. I repeat again "DO NOT INTERRUPT THE PROCESS". I have done so and it resulted in a full factory reset and I lost all my data in virtual SDcard.

According to [MENTION=4684315]flar2[/MENTION] , this process could take an hour or more. Give it up to 2 hours if you have a 128GB model.
[Nexus 6P General] Johnhnhn#1:
"vendor image may be out of date"

Using your guide I rooted my Nexus 6P to Pure Nexus Angler 6.0.1 20151219. Thanks, everything worked fine. Today, I attempted to upgrade to Pure Nexus Angler 6.0.1 20160109. Since then, I have to pop up when booting "vendor image may be out of date" So far everything seems to work except for this pop up. Do I need to worry about this? And if so, what do I do to fix it?

Thanks
[Nexus 6P General] SlimSnoopOS:
You can "fastboot format userdata" if you are worried. Your first boot may take awhile after doing this of course. Like the other user stated, they have 53GB as well on theirs.

Fastboot flash the vendor.img that matches your rom base. In your case, that would be the January OTA MMB29P. There may be a TWRP flashable zip in your rom threads first post. If not, use fastboot.
[Nexus 6P General] asj0422:
After I used 7zip to extract the file, it then still says it doesn't know how to read the file. the extracted one. What gives?
[Nexus 6P General] Badger50:
After you extract the file, then extract the new file that was made. You actually have to do it twice so you can read what's inside :)
[Nexus 6P General] Jazz__75:
Hii,

I have Nexus 6p 32gb, root and unlock bootloader and TWRP:

this evening N6p give me a notification about it have downloaded the January 2016 security pach:

ready to install:

after install the file of the notication, TWRP auto opened and restart the phone:

The security pach is not the January 2016 but december 2015:

How to resolve?

Please help me, thxthx
[Nexus 6P General] Heisenberg:
If you read the FAQ in the second post you'll find the answers you need. It is there for a reason.
[Nexus 6P General] biggolfer:
How do I know if I need to factory reset and start all over based on instructions in Guide #10?

I followed the instructions in guide #10 and saw no issues. I completed the reboot and the phone restarted without any issues. I proceeded to flash twrp recovery in guide #2 and it completed successfully and booted into twrp. Twrp prompted and I kept the system read-only. I want to install SuperSU to root the phone. I had previously downloaded the SuperSU v2.66 to the download folder within my phone. However within twrp recovery, I cannot navigate/locate the download folder from install menu. I appear to be in the root level and cannot get to the internal storage. In the twrp install menu, select file from internal storage has (0 mb). If I click "select storage", both options Internal Storage and USB-OTG have 0mg. Also, I have attempted to use the file manager and go to sdcard folder and every other folder available. Twrp has never asked to install SuperSU on its own. I am following instructions in guide #6. When I restarted into android, I can see all of my files through the file manager. If I then boot back to recovery, twrp is not present and I get the red exclamation triangle with android figure.

What am I missing?

I know it is probably something dumb that I am missing. I have flashed updates on Samsung phones for years but this is only the second month for updates on Nexus phone. The Dec update worked for me without any issues and I rooted the phone with SuperSU v2.62-3. The phone is working fine other than being unable to get root. I have attempted to reflash from the beginning with the same result.
[Nexus 6P General] hjmrox:
Thanks for this wonderful guide [MENTION=4153349]Heisenberg[/MENTION] Looking at some of the recent questions and also myself having the same question, I was wondering whether you could have a section on the FAQ for those of us who are on Stock ROM, Stock Kernel, with unlocked bootloader, systemless root and TWRP wishing to update to the last Google OTAs.

If we are supposed to follow 10. How To Update To A New Build Of The Stock ROM, could you please include "systemless root and TWRP recovery" in the Prerequisites section of guide 10 so that it's much clearer. :confused:Many thanks for your consideration!
[Nexus 6P General] Gayos24:
Very good

good job but the post is a litel bit long

Sorry for my bad english
[Nexus 6P General] force70:
Likely keeping it read only is your problem.I had issues also at first keeping things read only

sent from my Nexus 6P, Note 5, Nexus 6 or Note 4
[Nexus 6P General] ^tyrant^:
yes, i have it installed
[Nexus 6P General] pablogsm:
Hi, I think that something is not OK with my root... I followed all steps, and everything was pretty fine, but then when I was trying to edit the build.prop to change the DPI (doing it via adb casuses problems with some apps). I cant manage to get root access from ES file explorer, so I downloaded root browser. Now I can access the build.prop, but not save the file after editing it... Any ideas?
[Nexus 6P General] limpexowns:
For the people who are running systemless root, is Viper4Android working for you guys? Ever since upgrading to MMB29P, the driver won't install for me. It used to work on previous build that ran traditional root.
[Nexus 6P General] badabing2003:
I had to do this to get rw access to system

From Chainfire's notes*here:*

If you have one of those devices that refuse to remount system r/w in Android such as the Nexus 6P, but you do want to do this, "echo FSTABSYSTEMRW=true>>/data/.supersu" in recovery root shell before a SuperSU ZIP flash will patch the boot image in such a way that remounting will work. This feature itself breaks OTA compatibility, regardless of if you end up writing to /system or not.

From Heisenberg's*notes*here:

You can convert this systemless root method into what (for all intents and purposes) is a traditional system root. Do the following:Download*Terminal Emulator*from the Play Store.Open the app and issue the following commands:Code:

su

(you'll need to grant Supersu access at this point)

mount -o remount,rw /system

touch /system/bin/su /system/xbin/su

mount -o remount,ro /systemThis should clear up any compatibility problems you may encounter with systemless root. It probably isn't necessary for all users though.

As you might have guessed, this practically makes it non-systemless root and breaks Android Pay.

Hope it helps.
[Nexus 6P General] Upstreammiami:
guys i have a problem after unlock anf flashing recovery the phone wont boot it just hangs on the boot animation ..i have sideloaded a rom and still the same issue with the rom it just hangs on the bootanimation .
[Nexus 6P General] pablogsm:
Thanks man, I already did this at the beginning. Maybe I did something wrong... Anyways I think I'll go back to stock because my phone if rebooting like crazy, so I want to star discarding things and hope that is a software more than a hardware problem!

Thanks to you now I know what they meant by systemless root;)
[Nexus 6P General] graybeard5:
Viper is working for me without any problems
[Nexus 6P General] Heisenberg:
I've hit the character limit in post #1, so the guide has been split into the second post, FAQ has been moved into the third post.
[Nexus 6P General] deusfaux:
this phone comes encrypted, correct? I recall that causing issues with some of the typical alterations made to the Nexus phones, but the opening posts don't mention it causing any issues. Thus, it's as easy to to unlock and root an encrypted 6P as it is an unencrypted 5? And it stays encrypted?
[Nexus 6P General] Heisenberg:
It does come encrypted. There was some early issues with TWRP not being able to decrypt, but it's all good now. Just follow the instructions and don't worry about encryption.
[Nexus 6P General] Pain-N-Panic:
Yes, just flash the latest (or your choice of) systemless root.
[Nexus 6P General] Heisenberg:
What do you mean by "any root"? Root is achievable regardless of what build you're on.

Sent from my Nexus 6P
[Nexus 6P General] Heisenberg:
Yes you do, you didn't specify that. No, there's no modified boot.img for the latest build. Why not just go with systemless? System root is no longer being developed or maintained by Chainfire.

Sent from my Nexus 6P
[Nexus 6P General] brichardson1991:
I'm going to do the same thing.

How easy is it to go from system root to systemless?

I assume just upgrade the system as per your instructions then follow steps for systemless root as opposed to system root?
[Nexus 6P General] Heisenberg:
That'll do it.
[Nexus 6P General] cturbos:
Heisenberg

Thank you for being here....
[Nexus 6P General] Ravenryan:
Too bad this isn't an easy way to do this like the nexus 6 lol... the one click button!
[Nexus 6P General] im_on_fire:
I went thru step 10 to update to the Jan security patch (because of the persistent system update notification). everything went successfully with no issues, except the the security path is still showing as December and the persistent notification is still there. What could've gone wrong? Was it ill-advised on my part to flash the updated img, twrp and SU all in one go? Just want to know if there is anything I should look out for before I do it again, as I'm trying to avoid the same outcome. Thanks.
[Nexus 6P General] snovvman:
Systemless, going forward, is definitely the way to root. Be advised that you will need to re-grant root to your apps after you make the transition. I usually unlock the phone immediately during the first boot so that I can grant root when all the prompts come up (Greenify, Lightflow, etc.).
[Nexus 6P General] BeerFuelledDude:
[MENTION=4153349]Heisenberg[/MENTION] I followed step 10 - this is the 2nd time - and it has gone wrong. First time, can't remember in detail. This time, on first boot, it told me it was corrupt (in red writing) instead of the warning (in orange writing). Then just sits on the Android loading animation forever, I left it for 2.5 hours. Ended up having to wipe it all and start again. I must be missing something, otherwise, it would be happening to everyone! Do you recognise what it might be?

I do everything in the list (including the recovery.img). After flashing vendor.img, should I then

1. Flash TWRP

2. Install SuperSU.zip

3. Format userdata (I initially thought this would delete all my apps/data)

4. Reboot

Last time I didn't format userdata.

When I tried to recover from a nandroid - it messed up my PIN code and wouldn't let me use the phone.
[Nexus 6P General] snovvman:
Did you see the *stickied* thread in this same forum?

http://xdaforums.com/nexus-6p/general/psa-twrp-backups-lockscreen-security-t3245070
[Nexus 6P General] Vref:
So I followed this guide http://xdaforums.com/showthread.php?t=1917237to unlocking using Mac osX but when I type adb devices, it gives me the serial number of my Nexus 6p but also says it's offline. Is that normal or am I missing something?
[Nexus 6P General] SlimSnoopOS:
I just ran "adb devices" on my 5X and receive just the serial number. Are you receiving this while in the bootloader? When you run "./fastboot devices" is your output just the serial number?
[Nexus 6P General] pablogsm:
So as I mention it a couple posts ago. I'm having (a lot!) random reboots since I rooted the N6P and installed the Xposed framework... So just to check if it was a software problem I went back to stock using method 11. My question is: In case that this thing keep happening, could I send it to google for warranty for the reboots like this without risking it that they say it's my fault for rooting the device? What can I do so that it's 100% sure that is completely stock?
[Nexus 6P General] Vref:
The phone is in it's normal mode, screen on. I'm currently bootloader locked. I'll try booting to bootloader and running the adb devices command.
[Nexus 6P General] SlimSnoopOS:
Ok. I don't recall seeing "unknown" after my serial number was printed out when I was bootloader locked. Not after either ./ADB or ./fastboot devices. I am using OSX 10.10.5 if that helps.
[Nexus 6P General] Vref:
While the phone is in normal mode with screen unlocked this is what I get after typing "adb devices"

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

* daemon started successfully *

List of devices attached

"phones serial number" offline

except it get the actual serial number.

It's the "offline" bit that has me confused.

update:

went into bootloader and did the fastboot devices and got the serial number back with no "offline." Unfortunately my kids are almost home from school now so I'll have to wait until I get some time tonight to unlock, flash twrp, and Chroma.
[Nexus 6P General] SlimSnoopOS:
Yea, likewise. Ok, what version of the SDK and Platform-tools do you have installed? I have SDK 24.4.1 and Platform-Tools 23.1 (I had 23.01 installed previously though).
[Nexus 6P General] Vref:
I'm sure that's part of my problem. Still have the tools I downloaded when I tried to unlock (very unsuccessfully I might add) my M7 (verizon).

I'll grab fresh copies. Thanks for the help!
[Nexus 6P General] Shaftamle:
Could someone elaborate on this a little for me? Coming from Samsung, this is new for me, what is flash/boot? I feel dumb right now. :what:

There is a pitfall with keeping it read-only, however. TWRP isn't able t persist without modifying system, so you'll lose it after booting into Android, you'll need to flash/boot it to access it again.

Sent from a Shaftamle Galaxy S4

"Thanks Button" is always appreciated!

149ThemedGoogleKeyboards!!!!!!

Eclipse ROM fatness!

MyColorScreen
[Nexus 6P General] omametsnor:
Thankyou so much for this clear and really easy tutorial.

I have one question thou, I've used the systemless root method and obv i keep getting the messaged '' your device can't be checked on corruption please lock bootloader"

on my nexus 6 I rooted with the modified boot img but is there a way to hide the message while making use of the systemless root method

thanks in advance
[Nexus 6P General] SlimSnoopOS:
It is a temporary install. Some people may only want to temporarily install TWRP to perform a backup or simply check it out. If you want TWRP to remain permanently then flash SuperSU. Flash TWRP (using fastboot), install SuperSU, then you can successfully boot into TWRP any time you want.
[Nexus 6P General] Shaftamle:
So should I click modified system instead of read only when twrp boots in order to keep it? Would using the old non systemless root be better?

Sent from a Shaftamle Galaxy S4

"Thanks Button" is always appreciated!

149ThemedGoogleKeyboards!!!!!!

Eclipse ROM fatness!

MyColorScreen
[Nexus 6P General] im_on_fire:
Not sure what's going on. I went through step 10 again with a new image download and didn't flash TWRP or SU this time. Same issue. Still showing Dec patch level with persistent update notification. What am I missing? Do the current images for nexus not contain the Jan patch?
[Nexus 6P General] SlimSnoopOS:
Leave system R/O for systemless root. If you plan on using Android Pay then systemless root is the recommended way to go. I didn't fully know how system root compares vs systemless, I don't personally use many mods or root apps. I guess that depends on what you are looking to do? I believe most of the roms can be run systemless by flashing an unsu.zip then installing SuperSU 2.6x as systemless, but even still they may have a mod that is incompatible with Android Pay.

Are you flashing the MMB29P factory image (January OTA)? I do not see that explicitly stated in either of your posts.
[Nexus 6P General] Heisenberg:
When making a nandroid you must remove all security first, I'm pretty sure this is mentioned in my instructions, plus there's a sticky thread discussing it too. After flashing the update are you booting the phone straight away? Or are you flashing TWRP and SuperSU first?

Flash the factory images, format userdata, lock bootloader.

Flash: install.

Boot: live-boot.

When I say flash I just mean to install it again. When I say boot I'm talking about using fastboot to live-boot the recovery image instead of installing it permanently. You'd achieve that with this command:

fastboot boot <filename.img>

There's an FAQ in the second post. I link to it several times in the guide.

It's up to you. I select to to be able to modify system, which allows TWRP to persist. This will mean things like Android Pay won't work though.

You're flashing MMP29P?
[Nexus 6P General] omametsnor:
Thankyou my man, great effort ! I appreciate it soo much.
[Nexus 6P General] im_on_fire:
[MENTION=4153349]Heisenberg[/MENTION] [MENTION=3576831]SlimSnoopOS[/MENTION] nope. (swear). i knew it was something stupid i was doing. thanks.
[Nexus 6P General] SlimSnoopOS:
Ahh, wasn't aware that TWRP would persist just by making system R/W. Nice to know.

---------- Post added at 05:02 PM ---------- Previous post was at 04:55 PM ----------

No worries! The update list is in order from oldest at the top to newest at the bottom for the device you are looking for. They are also alphabetized if that makes it clearer.
[Nexus 6P General] Shaftamle:
Ahhhh, OK, that wasy main question. Thanks! Last question, is there anyway to use the read only method and be able to get back to twrp by installing via app or terminal on the phone itself, like mobile Odin or flashify? I doubt it but figured I'd throw it out there.

Sent from a Shaftamle Galaxy S4

"Thanks Button" is always appreciated!

149ThemedGoogleKeyboards!!!!!!

Eclipse ROM fatness!

MyColorScreen
[Nexus 6P General] im_on_fire:
Makes sense. I'm used to flashing zips with the same build number (or that's what I remember from my s3 anyway). So I downloaded 29M because that's what I saw in about phone. Thanks again.
[Nexus 6P General] Heisenberg:
Odin is a Samsung tool, so no to that. Flashify should work.

Flashing the same build number that you see in about phone will just reflash what you already have installed.
[Nexus 6P General] Vref:
[MENTION=4153349]Heisenberg[/MENTION]

When first flashing TWRP do we still need to rename the recovery to "recovery.img" or just use the file name it downloaded as?

Also, I don't see a modified boot.img for my build number MMB29P.

I haven't flashed anything since my days of the HTC Rezound and I'm trying hard NOT to F-up my new Nexus.
[Nexus 6P General] Shaftamle:
Edit,sorry:All of the info u need to install recovery is covered in the main post, section #2.

Not sure about mmb29p, possibly because its new. But don't quote me on that.

Sent from a Shaftamle Galaxy S4

"Thanks Button" is always appreciated!

149ThemedGoogleKeyboards!!!!!!

Eclipse ROM fatness!

MyColorScreen
[Nexus 6P General] Vref:
It doesn't explicitly say to change the file name or not...not big deal since if it's wrong I assume it just won't flash but the lack of compatible build # had me concerned about flashing the wrong boot.

I'm sorry if these are noob questions but I haven't flashed anything since I've been using an HTC M7 for the past two years.
[Nexus 6P General] Shaftamle:
I hear ya. I'm right with you. Better to be safe then sorry. I was going by this from sectiom2:

fastboot flash recovery .img

(The recovery filename in the command will change depending on which recovery you're flashing)

I would assume you would type the downloaded file name.

Sent from a Shaftamle Galaxy S4

"Thanks Button" is always appreciated!

149ThemedGoogleKeyboards!!!!!!

Eclipse ROM fatness!

MyColorScreen
[Nexus 6P General] Heisenberg:
It doesn't matter what it's named, as long as you enter the command correctly to suit the filename. If the filename is recovery.img then the command is:

fastboot flash recovery recovery.img

If the filename is twrp-2.8.7.2-angler.img then the command is:

fastboot flash recovery twrp-2.8.7.2-angler.img
[Nexus 6P General] Vref:
Thanks.

Question about the modified boot.img (using traditional root). I didn't see one for my build number MMB29P
[Nexus 6P General] Heisenberg:
There isn't one, only systemless root is possible.
[Nexus 6P General] user68734:
Does that mean build number MMB29P will never have traditional root? Or is a temporary thing because MMB29P is new? I also have a new Nexus 6P an mine is MMB29P.

You also mention in step #6: You can convert this systemless root method into what (for all intents and purposes) is a traditional system root. Does this also not apply to those running MMB29P?

One last question ... If I ever wanted to sell the Nexus 6P could I restore it back to unrooted stock such that Android pay would work again? Or is Android Pay gone forever? Doesn't matter to me but people buying the phone might.

Thanks for the guide by the way!
[Nexus 6P General] Heisenberg:
It might get traditional root, but that would require someone to make a modified boot.img to suit. There really isn't much point because systemless root is here now, it doesn't require anything other than flashing the zip. Plus, traditional root isn't being developed or maintained anymore, systemless is what's being focused on moving forward.

The method to convert systemless root to a more traditional style (modified system) root works regardless of what build you're on.

Android Pay will only not work for as long as the things preventing it from working are present. Rewritten the phone to stock and it'll work fine.
[Nexus 6P General] user68734:
Thank you for answering! Reason I ask is I have read that some root apps like Xposed might not work properly with the system-less root. Since I did not care about Android Pay I thought it would be better to use traditional root. In any case, from what you said, sounds like system-less is the future.
[Nexus 6P General] Heisenberg:
I'm pretty sure Xposed works just fine with systemless root, have a look back over the last few pages, I think someone confirmed that.
[Nexus 6P General] user68734:
When flashing the Rom, Nexus Gapps, FiDialer fix and Vendor img can they all be flashed from the same TWRP session or do you need to install th ed Rom first, reboot, then go back to recovery, flash Gapps, etc ...
[Nexus 6P General] Heisenberg:
They can all be flashed in the same session.
[Nexus 6P General] BeerFuelledDude:
Na, I didn't see it. I have since read about it after it happened ;)

---------- Post added at 08:21 AM ---------- Previous post was at 08:20 AM ----------

Yeah, I've read it now - but it seemed so simple to do a backup, I didn't read the instructions about disabling security. Rookies :rolleyes:

After flashing the update, I didn't write it down (I did it a couple of weeks ago and kept forgetting to come on the forums to ask), but think I flashed TWRP then booted (didn't do SuperSU). Also, definitely didn't format user data.

Appreciate the help man.