yashsingh1/xdaforums huggingface dataset:
[Nexus 5X General] qtipbailey:
FWIW, here's my experience coming from a bone-stock phone fresh out of the box (almost, I did let it do an OTA update to MMB29K first):

I unlocked the bootloader exactly as in the OP.

Flashed TWRP 2.8.7.2 as in the OP.

I did NOT decrypt data partition.

Flashed SuperSU 2.64 which modifies the bootloader automatically.

That's it! No problems at all. At every step I followed instructions to the letter, rebooting after every step. Several days later SuperSU 2.65 came out and I flashed it over 2.64 after someone else reported doing so successfully. It went off without a hitch and updated itself. It gave a warning that the phone may reboot several times. Indeed it rebooted 3 times I think, and then all was fine. Apparently this is normal.

If you don't decrypt your data, TWRP will ask you for a password. If you hit cancel, it will let you continue and perform backups but it will SKIP the data partition even if you have it selected. The password is your PIN (backup PIN if using fingerprint unlock), or if you set up a pattern unlock you have to figure out your "PIN" like this:

1 2 3

4 5 6

7 8 9

edit: even though it's in the OP instructions, some people still missed this important instruction so I'll reiterate it here: Do not answer yes to flash the version of SuperSU that TWRP offers to flash for you in order to give you root. Manually flash the newer SuperSU zip file yourself from within TWRP.
[Nexus 5X General] 2x4:
Correct me if I'm wrong having read that, but does this mean each time we need to update we need to use the ADB environment?
[Nexus 5X General] joetheshmo:
Yes
[Nexus 5X General] rosen.grayfox.ch:
"I will give anything or pay any price" as a prince once said
[Nexus 5X General] briant1234:
Hey im having some trouble decrypting. i formated user data like the post said but after booting it says that I'm still encrypted in android settings? is there something else i need to do to decrypt?
[Nexus 5X General] joetheshmo:
If you don't have a modified boot.img it will auto encrypt on boot
[Nexus 5X General] 2x4:
I apologize if this is obvious, but it is there any way around that?

Custom roms don't have this requirement tight?
[Nexus 5X General] joetheshmo:
The only way around it is to unroot and flash stock recovery to receive the ota update AFAIK. Custom ROMs usually include a flashable zip to flash updated radio, bootloader, etc as well as the updated ROM for system and boot.img. I personally have been on pure nexus rom and updates are very painless.
[Nexus 5X General] 2x4:
Makes sense. I've only ever been on stock, modified stock, and CM roms, but now that you mention it I went and read up on it a bit on the thread and watched the XDA review video and it looks like a great option. So in this case I would just be able to download and flash updates directly via TWRP (similar to updating CM), correct? Nothing else to flash each time I update? (except Gapps, I presume)

On that topic, have you run into any issues using this rom? I presume Android pay doesn't work, which is to be expected, but does nexus imprint still work for google play purchases and apps like lastpass? Any other issues?

thanks again for all your detailed help btw, really appreciate the community sense here
[Nexus 5X General] brennerj:
Hey guys quick question took a brand new out of the box nexus 5x and unlocked it. Then flashed recovery twrp 2.8.7.2 and then flashed systemless root 2.65. I am rooted but my android pay does not work. I get a big white pop up that says android pay cannot be used. Google is unable to verify that your android device or the software running on it is android compatible. Look forward to hearing from all the experts on this!

Thanks
[Nexus 5X General] syintiphic:
I'm running supersu 2.60 and Android Pay works on my Nexus 6P. Give this version a try instead. I think I also saw posts mentioning that Android Pay works with supersu 2.61 too.
[Nexus 5X General] Travisdroidx2:
For those that are trying to decrypt this is what I did. I was rooted with twrp and phone was encrypted.

1. Flashed the stock images back to stock.

2. Flashed the modified boot.IMG, before rebooting also typed fastboot format data.

3. Booted up and an encryption was off.

4. Booted back into download mode and flashed twrp. As soon as I was in twrp I hit format data again. Booted back up and verified with twrp encrypt was still off.

5. Booted back to twrp and flashed the SuperSU zip and rebooted.

Now my phone is not encrypted anymore like it was before. I might done extra steps but followed a guide on YouTube and it worked for me.
[Nexus 5X General] brennerj:
What is the proper way to flash over. Just download and flash over in Recovery?

Also does it matter if you are using titatnium backup, cf lumen, call recorder and modified build.prop for tethering??? Would that have any effects on not being able to use android pay?
[Nexus 5X General] syintiphic:
Yes, I just downloaded and flashed SuperSU 2.60 in recovery. You probably know this already but don't select to install SuperSU in TWRP when you are ready to reboot your system, just reboot even though the message states TWRP can't detect that the device is rooted.

I don't think it would matter if you are using any of the above. I'm using TiBu and I don't have any issues. I can't say if the modified build.prop impacts Android Pay. Maybe try to use Android Pay with your unmodified build.prop first and see if it works.
[Nexus 5X General] :
Another question on this:

Originally Posted by 2x4

"Correct me if I'm wrong having read that, but does this mean each time we need to update we need to use the ADB environment?"

My N5X only has the bootloader unlocked after the troubles I had with TWRP. Does this mean I can only update my device this way, or were you referring to decrypted devices? My build is so messy right now, I'm not sure how much I want to interfere with flashing new ROMs before I get it under control.
[Nexus 5X General] berndblb:
OTAs don't care about encryption or the bootloader. They do fail if you made any changes to the system partition.

OTAs work incrementally. They change/patch an existing installation. If you made changes - and Google cannot know wth you did - it would be foolish to flash an incremental update.

But if your build is messed up I'd think it would be high time to flash back to pure stock and start fresh anyway. And yes, you have to do it in fastboot.
[Nexus 5X General] Sandmannet:
Nice guide!!Thanks man!!
[Nexus 5X General] dimoochka:
Just a question about the above statement. You meant soft brick, right? Even if all partitions (except bootloader) are trashed, it's always possible to unlock bootloader and reflash everything back to stock through fastboot (?).

Alternatively, if the bootloader partition is trashed, it's a hard brick :)

Thanks a bunch!
[Nexus 5X General] Heisenberg:
Yes, soft brick. As long as you keep your bootloader unlocked you should have no problems, accessing the OEM unlock option in Developer Options isn't always possible, so if you lock your bootloader and can't access that you're screwed.
[Nexus 5X General] dimoochka:
Yikes. That sounds like a disaster. To be clear, it sounds like in this scenario both the system AND recovery partitions would have to be corrupted, leaving the bootloader as the only method of access into the phone.

If you at least had a working stock recovery, I would imagine that this phone would still be salvageable (ie. factory reset & sideload a signed stock OTA rom)?
[Nexus 5X General] Heisenberg:
If you can't access /system it isn't guaranteed that adb will work as usb debugging may not be activated. I've seen at least a couple of cases like this in our Q&A section.
[Nexus 5X General] Mistic92:
I have simple question. Still forgetting how to do it:D I have root and unlocked bootloader. How to install new security updates? Download image, unpack and sideload system or something?
[Nexus 5X General] SlimSnoopOS:
Follow section #10. Flash the files using fastboot then root if you desire.
[Nexus 5X General] dimoochka:
Recoveries read that flag? I thought it was just for the system runtime. Is this just the stock recovery or custom recoveries as well? I just ordered this device so I'll have to play with it a little to learn it. I'm used to the boot structure of the samsung galaxy S2 which is basically unbrickable (unless you do something crazy like corrupt the partition table or overwrite the bootloader). Any other modifications are easily recoverable using Odin on a PC (Samsung's equivalent of what I think is LGUP).
[Nexus 5X General] Heisenberg:
I could be wrong, the fact that adb wasn't working in recovery could have been unrelated to the setting in Developer Options. You're right though, unless you corrupt the partition table or screw the bootloader it's very difficult to brick this phone.
[Nexus 5X General] briant1234:
How would update to a new build of the stock rom, after I've decrypted, and rooted? I have TWRP installed and don't want to lose any data
[Nexus 5X General] berndblb:
Literally 3 posts above yours.....:rolleyes:
[Nexus 5X General] briant1234:
My bad, I was more specifically wondering about how to prevent re-encryption. Is it the boot.img that re-encrypts, or the stock kernel? Should i not flash the recovery and then reinstall a custom kernel before i reboot to system?
[Nexus 5X General] berndblb:
Maybe not as screwed as I thought one might be in this situation just this morning. Just stumbled across this:

http://xdaforums.com/showthread.php?p=63889395

I have never owned an LG device so I am not familiar at all with the LG FlashTool, but it looks as if it could save your bacon if your bootloader locked and OEM unlock disabled in settings... You guys heard about this?

Instant hero status for [MENTION=4325732]bitdomo[/MENTION] in my book! :angel:
[Nexus 5X General] SlimSnoopOS:
I am not all that clear on how to maintain decrypt status while on stock boot.img. I just decrypted last night. I use a custom kernel which does not force encryption (EX kernel) and so I plan to update/fastboot flash all the .img files, boot to TWRP, re-install EX then flash SuperSU 2.6x to maintain decrypt status with custom kernel. Just waiting until the Pacers/Heat game ends before I begin.
[Nexus 5X General] berndblb:
Oh ok, I see what you're saying now. Yes either you'd have to wait updating until a modified boot.img (=kernel) is available, or you install the new firmware (including the stock boot.img) and then flash systemless root in recovery.

Chainfire's new root method modifies the stock boot.img on the fly and removes forced encryption.
[Nexus 5X General] dirtyrott3njb:
Still not clear on if I can just flash his kernel in my stock recovery like it says??
[Nexus 5X General] yooouuri:
When i flash twrp and i reboot to the recovery it shows twrp. But when i reboot to the phone and and boot to the recovery it gives me an android laying on his back with a warning sign. What am i doing wrong..
[Nexus 5X General] PiousInquisitor:
Andy replaces twrp with the stock recovery every reboot. Did you not read the prompt when you first boot twrp from the bootloader?
[Nexus 5X General] dirtyrott3njb:
I tried to flash elemental x kernal no root, it say error volume path to SD not something?? Recognized??

---------- Post added at 03:01 AM ---------- Previous post was at 02:55 AM ----------

Correction..it says "unknown volume for path( SD card)
[Nexus 5X General] SlimSnoopOS:
EX Kernel is flashed using TWRP recovery (a custom recovery). That is implied when you read instructions for a custom kernel or custom rom. Some advice, it must explicitly state somewhere that "this file can be installed/flashed using stock recovery" before you ever attempt to install using stock recovery.

How did you attempt to install Ex Kernel?
[Nexus 5X General] dirtyrott3njb:
I downloaded the zip to my SD card,I also have es file ex..then I booted into recovery and tried to apply update from SD card..I got amsg that it was aborted.. It said"unknown volume for path[SD card}
[Nexus 5X General] SlimSnoopOS:
I received confirmation from flar2 that you need to have unlocked your bootloader to install his custom kernel even if you do not want root access. So you'll have to enable Developer Options, then enable "OEM Unlocking" and "USB debugging." Your next steps would be:

-unlock bootloader using fastboot (this step will delete

EVERYTHING

from your 5X)

-fastboot flash TWRP recovery

-boot directly into TWRP and install Ex Kernel

-then boot into stock rom with no root access
[Nexus 5X General] agmtpd:
is encryption that much of a performance barrier? I just got my nexus, deciding whether to decrypt or not as I want to avoid backing up data, decrypting and re copy data once again in near future.
[Nexus 5X General] NameLessThugZero:
Convert from system to systemless

How do I (or where can I go to find out) how to convert from system to systemless root? I'm 6.0.1 (Dec. 1st) Stock ROM rooted w/ TRWP.

I think I can live without Xposed (though I'll miss Gravitybox and its features), and I want to be able to use Android Pay. I'm getting the impression that systemless is becoming more stable/reliable/supported now, and if it allows me to do (nearly all of) the same things I could before, I down to try it. Thank for any help!
[Nexus 5X General] berndblb:
For AP to work you cannot have any changes to the system partition and you need the stock kernel for systemless.

So best would be to flash system.img and boot.img of your current firmware in fastboot, reboot into TWRP and flash systemless root.

That's the short version, the thread is here: http://xdaforums.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133/post64711001#post64711001
[Nexus 5X General] Sytheii:
Please excuse me if this is a stupid question, i searched the thread, and googled a bit, but didn't find anything conclusive.

In the section on installing a custom recovery, the guide says to:

"Make sure you check the md5 to verify its integrity (where possible)."

Does TWRP supply md5 checksums for their images for bullhead? There are two versions available for download, 2.8.7.0 and 2.8.7.2, but no info on any checksums for those images. If you download the files using Firefox, is this process automated when I download them? I just want to make sure that what I am flashing isn't corrupted.

Or maybe this references generating a md5 of the image and then checking that with what I send over to the phone?

In any case, I just want to be careful and make sure I take all precautions to not mess anything up. I plan on reading this whole thread from front to back including comments, but I got hung up on this step first so figured I'd ask.

Thanks in advance.
[Nexus 5X General] berndblb:
If you go to the actual download page for the TWRP image you'll see the link for the md5 file on top right under the page header.

You can then use programs like Hashtab or similar to compare that md5 with the one you generate from the downloaded file
[Nexus 5X General] Sytheii:
Wow. I am blind. Sorry. And thank you. Do we know if one version is recommended over the other?
[Nexus 5X General] berndblb:
Happens to everyone... ;)

As for the version: Always go for the latest. There's usually a reason they released an update. Occasionally the latest comes with a new bug, but the early adapters find those pretty quick. Leading to the next release....
[Nexus 5X General] Sytheii:
Roger that! and Thanks again. Are you the thread creator? Heisenberg? Or just a fan? lol
[Nexus 5X General] berndblb:
Nope. Just a similar taste in avatars I guess. But Heisenberg rules!
[Nexus 5X General] NameLessThugZero:
Right, that too. I forgot to mention that I've no kernel mods either.

So all I would need to do is flash boot and system.img and flash systemless? Wouldn't I have to, say, 1)unroot 2)uninstall Xoposed/Gravitybox 3) then flash as per your suggestion?
[Nexus 5X General] berndblb:
Your current root is in /system. Flashing the image will take care of it anyway.

Uninstalling Xposed and Gravitybox may be a good idea. I have no idea how those install, but they wold not work anyway.

The same may be true for any app with root access you currently have. Not all apps work with systemless root yet. The best way to find out is probably to start with "clean" systemless root, then add root apps one by one and see if they work...

Matter of fact - I would start with a factory reset....
[Nexus 5X General] Stauf99:
Keep us updated, I'm dying to hear the results.

Especially if gravitybox works on systemless or not :fingers-crossed:
[Nexus 5X General] NameLessThugZero:
Ah i see. Well that was what I was trying to avoid lol. But factory resetting wouldn't be an unsafe idea though.

---------- Post added at 04:03 PM ---------- Previous post was at 03:58 PM ----------

Well, I'm not going to do it just yet. I have to see which of my other apps aren't compatible first(which I don't have a lot honestly). But whenever I can, I definitely will update.
[Nexus 5X General] nvertigo:
>If TWRP offers you to keep /system read-only, indeed keep it read-only.

If I already swiped the read write option, how can I change it back to read-only system?
[Nexus 5X General] dirtyrott3njb:
Ya but you need need to be rooted to install twrp recovery so I don't see how that would work?? Is fastboot an app or is it in my recovery?? Thx.
[Nexus 5X General] alfick3:
No you don't. You flag TWRP from fastboot even before you root.
[Nexus 5X General] dirtyrott3njb:
Flag? Fastboot, pls elaborate?
[Nexus 5X General] joetheshmo:
Pretty sure flag was meant to be flash. You flash twrp before you ever flash SuperSU, which gives you root. I.e. you can have twrp and not be rooted.
[Nexus 5X General] alfick3:
Yes, my applogies. I meant flash. The autocorrect on my phone changed it to flag and I didn't notice before I posted via Tapatalk. Like [MENTION=7037416]joetheshmo[/MENTION] said, you flash TWRP via fastboot (you can search this great forum or XDA or Google to find out how to do that). Then you flash SuperSU via TWRP to achieve root (or just the the built-in root in some ROMs such as CM13).
[Nexus 5X General] dirtyrott3njb:
How do I flash twrp?! My bootloader have to be unlocked,?? How do I do that ora??

---------- Post added at 09:39 PM ---------- Previous post was at 09:39 PM ----------

Typo, ota.
[Nexus 5X General] joetheshmo:
Read the guide in the first post of this thread ;)
[Nexus 5X General] dirtyrott3njb:
Do I need a oc??

---------- Post added at 09:40 PM ---------- Previous post was at 09:40 PM ----------

PC??
[Nexus 5X General] dirtyrott3njb:
Thx, I have rotted using kingroot before and flashed twrp on my nxs5 7 2013 before all ota, but that's why it was easy for me then.
[Nexus 5X General] queerquirks:
I have no need for android pay since its not supported in my country, can we flash xposed over systemless root? Currently on traditional root and plan to convert to systemless
[Nexus 5X General] bluey45:
If your already on traditional root and want to go system less root, do you just reflash your super su as per the instructions to make it system less?
[Nexus 5X General] SlimSnoopOS:
Nope, per post #2 here: http://xdaforums.com/showthread.php?t=3219344

You'll use fastboot to flash two system and vendor img's that match your rom base then boot into TWRP and flash SuperSU.
[Nexus 5X General] dave2775:
I think I read somewhere that you can just flash the unSu script, then flash systemless root zip? Don't quote me, um liking go convert as well.
[Nexus 5X General] Travisdroidx2:
I am unable the decryption on MMB29P build. I have tried to format userdata in fastboot and the device is still encrypted. Any ideas? On MMB29k I flash the modified boot then twrp. After twrp I format data and encryption is off. Any get it working on MMB29P? Is it because I do not have the modified boot.img for MMB29P?
[Nexus 5X General] SlimSnoopOS:
I think you're right, I gotta read up on that though

Fastboot flash the MMB29P boot.img and leave that alone. You need to install SuperSU via TWRP which will disable force encrypt within the stock kernel then it is safe to boot into your rom. You will be decrypted at this point and this can be checked in Settings/Security as it well say "Encrypt Phone" and present a button to start that process.

[MENTION=4153349]Heisenberg[/MENTION], could you edit Section 3? It should mention that in order to decrypt and stay decrypted with the stock boot.img, one must install SuperSU (or a custom kernel that does not force encryption) which will disable the "force encrypt" process that the stock boot.img will do.
[Nexus 5X General] Travisdroidx2:
So after I flash the factory images for MMB29P flash the boot.img again, then flash twrp and flash supersu before rebooting system?
[Nexus 5X General] bluey45:
Oh I see. Great thanks for that slimsnoop.

I must've missed that previous post!
[Nexus 5X General] SlimSnoopOS:
Download SuperSU into your computer.

*Flash the MMB29P factory image

*boot up to make sure it is fine and of course encrypted (not necessary though)

*fastboot format userdata (you are now tentatively decrypted)

*fastboot flash TWRP then boot into TWRP. Do not boot into your rom or you will encrypt.

*Move SuperSU over from computer to your phone

*flash SuperSU and boot. If you want systemless then read the link in my previous post on how to force systemless SuperSU.

*boot up and verify you are decrypted. Check Security and tap "Encrypt Phone." There will be a second screen that states how to encrypt. This means you are officially decrypted.

You should be set after that.

Not a problem, I'm here to help! Btw, that should have been "the system and vendor..." in my previous response to you. There is also a command line that you'll have to write out to force systemless with 2.66 SuperSU, all contained in that post. You can do that in TWRP before installing SuperSU.

Edit: just want to clarify, the link is from the Marshmallow SuperSU thread.
[Nexus 5X General] Travisdroidx2:
Thank you, let me try again. Don't think I ever transfered a file from comp to phone while in twrp before. This damn encrypt sucks! Appreciate the help!

Update: Thank you so much that worked!! Man I spent a few hours trying to get that damn thing off. Appreciate your help so much! Now since I did not flash a modified boot.img do I need to run the terminal commands to make it system root? I do not want systemless root.
[Nexus 5X General] SlimSnoopOS:
You are welcome! I used SuperSU 2.62_3 to root MMB29P as I didn't have a reason to test out 2.66 haha Either way, I put the SuperSU file in the same folder as ADB then used "ADB Push filename.zip /sdcard/filename.zip" and it worked for me.

You can do it haha I did so using OSX so no excuses!

Edit: just rewrote the proper ADB command

---------- Post added at 01:30 AM ---------- Previous post was at 01:19 AM ----------

The way I understand it, SuperSU 2.66 prioritizes installing to /system. You can check your status in SuperSU. I am unsure how to make it system root if it fails to do so on its own.

Edit #2: [MENTION=4251564]Travisdroidx2[/MENTION], I think I may have to call in help for SuperSU 2.66. Cuz in the Marshmallow SuperSU thread, 2.66 checks to install to system first and NOT modify the boot.img, which *I think* means you will boot up encrypted.

Edit #3: I may be overthinking this. However, if SuperSU 2.66 system install does not disable "forceencrypt" in the stock boot.img, then you would need a custom kernel (like Ex kernel) that turns off "forceencrypt," which would keep you decrypted.
[Nexus 5X General] Travisdroidx2:
With following your advise I installed 2.66 and it is not encrypted. Now when i check it gives me the option to encrypt so I know I am good. When I look in SuperSu where it shows system it is grayed out where it says Install SuperSu into/system Not currently available in systemless root mode. So not sure if since it is gray and not available to click on if I have systemless root. I am still updating my apps and will check my directory and maybe try those commands in the OP.
[Nexus 5X General] SlimSnoopOS:
Ok, hmm. Systemless may just be the default for SuperSU 2.66. I really don't know how to help you at this point. I think SuperSU 2.52 is for system root but I'm guessing at that point and I'm not one to do that.