yashsingh1/xdaforums huggingface dataset:
[Nexus 5X Original Android Development] srnoth:
You have to format (wipe) the entire data partition (including internal SD) to start afresh with no encryption. Everything that is currently on your phone is already encrypted.
[Nexus 5X Original Android Development] jackdubl:
Is this true even of I'm already on the stock rom? I never flashed a custom.
[Nexus 5X Original Android Development] jackdubl:
Hey, when they optimize at boot, does it have the "updating app 10 of 70" screen that takes a long time, or does it just say "starting apps" for a few seconds and then start up? I do get that second, short screen after I wipe cache and davlik.
[Nexus 5X Original Android Development] mechapathy:
I'm having an odd issue with TWRP on my 5X. I boot into TWRP without flashing it, it asks for my encryption PIN, I enter it, and decryption fails. Any ideas?
[Nexus 5X Original Android Development] jackdubl:
Try changing your pin to a pattern and see if it works?
[Nexus 5X Original Android Development] skulldreamz:
Whenever you wipe dalvik cache is when you see the x number of apps out of x. The virtual machine is optimizing new dalvik cache cuz u just wiped it and the phone needs dalvik cache to run properly. That's why sometimes you will hear people or a dev say wioe dalvik cache. If you only wipe cache the phone just says starting apps and boots in a couple seconds.
[Nexus 5X Original Android Development] jackdubl:
So I never get that screen with the x out of x when wiping cache and davlik. Just the shorter one. Guess I should try to reformat the whole dang phone to fix it? Little bit of a bummer there.

---------- Post added at 03:36 PM ---------- Previous post was at 03:30 PM ----------

So I just wiped davlik only, and I just got the "starting apps" screen for a second and a half then phone started. No x of x screen.
[Nexus 5X Original Android Development] skulldreamz:
So your on stock rom. Only custom roms wipe x of x
[Nexus 5X Original Android Development] jackdubl:
Yes, I'm on stock m build. So then, this is how it SHOULD be? Nothing is wrong with my wipes?

---------- Post added at 03:40 PM ---------- Previous post was at 03:39 PM ----------

Is this due to odex?
[Nexus 5X Original Android Development] skulldreamz:
No, nothing is wrong with your wipes. Optimization has to do with dalvik and art runtimes.
[Nexus 5X Original Android Development] ourfear:
I got below red line message when I do Format data with TWRP 2.8.7.2

E: flash_image /dev/block/platform/soc.0/f9824900.sdhci/by-name/metadata /dev/zero precess ended with ERROR=255

then I reflashed chroma , it's decrypted already...

i just want to know what is the red error msg means?
[Nexus 5X Original Android Development] buru898:
I can't wait for F2FS support. I hope it happens with our phone.
[Nexus 5X Original Android Development] harcheng:
Oops nevermind :p
[Nexus 5X Original Android Development] kurt.gomez:
You're getting that cos you've rooted with systemless root and not the conventional SuperSU... TWRP devs are currently debating on removing that warning either on Marshmallow devices or universally once they reach a decision
[Nexus 5X Original Android Development] SlimSnoopOS:
Does anyone know if I need to have everything stock to backup my EFS? I am stock rooted with systemless SuperSU and EX kernel installed. Am I ok to backup my EFS via TWRP with my current setup or do I need to be stock rooted with no changes? Calls, texts, and data work fine right now. Just preparing for the future.
[Nexus 5X Original Android Development] add12364:
So I was on 6.0.0 decrypted by twrp. I tried to fastboot flash system image but my phone bootlooped. I completely wiped my phone entirely and reflashed everything. I'm on 6.0.1 now. I get the red corruption message on boot. I flashed twrp did the format and decryption but once I boot up my device i still get red corruption message and my phone is still encrypted. whats going on
[Nexus 5X Original Android Development] Gandalf:
At this point I would recommend backing up your userdata (pictures, files, etc.) and just doing a "flash-all" of factory images. Let it boot up, reboot to bootloader, flash TWRP again, and then format data from this clean slate.

Also, keep in mind that stock has a forceful "forceencrypt" in it's fstab, so unless you can grab a modified stock bootimage, you'll be stuck with 1) verity checks for system 2) forceencrypt for the data partition

It is very proactive to backup your EFS partitions and put them up on Google Drive or somewhere that you know for a fact they will not be lost. EFS partitions contain your phone's unique identifiers and therefore are not in the factory images. If you lose EFS, you are screwed.
[Nexus 5X Original Android Development] add12364:
Crap I totally forgot about the boot thing. Where can u find a modified boot image for 6.0.1 or can I use the old one?
[Nexus 5X Original Android Development] SlimSnoopOS:
Yea, I am aware. I was just unsure if I could backup my EFS while stock rooted with a custom kernel. I decided to go stock everything and back up. Thanks for your response!

Edit: Several hours later, I realize I COMPLETELY misinterpreted your post. Thank you [MENTION=3878813]Gandalf[/MENTION] for in fact answering my question.

Go to post #265 for MMB29K boot.img in Heisenberg's guide here:

http://xdaforums.com/showthread.php?t=3206930
[Nexus 5X Original Android Development] gpvecchi:
Reboot with corrupted partitions after restoring a backup (of all partitions).
[Nexus 5X Original Android Development] jl154:
When installing twrp should you check the box for read only or swipe to modify system . Hope I said that right
[Nexus 5X Original Android Development] gpvecchi:
No, I did it, it seems a problem with vendor and system partitions...
[Nexus 5X Original Android Development] maxmax0:
Did anyone manage to get USB OTG running? I'd love to mount a usb-stick for backup, and cannot get it recognized.
[Nexus 5X Original Android Development] maxmax0:
In case anyone is interested: got it working, the problem was the "old" OTG cable I had and was using with a type c adapter, bought a single piece OTG type C plug and it works flawlessly now.
[Nexus 5X Original Android Development] Ashwa:
No luck here. Working fine when device running. But not in recovery. Unable to mount the otg.

Pls do help.
[Nexus 5X Original Android Development] gorilla p:
I purchased a cheap $3 type-c rUSB 3.1 otg cable on eBay and its working fine for me.
[Nexus 5X Original Android Development] Ashwa:
Mine also working when phone is in normal.

Not working in recovery. Could you pls confirm the same.
[Nexus 5X Original Android Development] gorilla p:
Im not sure what kernel youre using or if it even matters in recovery, but Im using ElementalX kernel.
[Nexus 5X Original Android Development] aschere:
TWRP 3.0.0

So, TWRP 3.0.0 just came. I don't see bullhead at Jenkins though.
[Nexus 5X Original Android Development] skulldreamz:
Yeah just read the new updates on 3.0.0-x but i think it's just taking [MENTION=912474]Dees_Troy[/MENTION] some time to push it out for all devices, that's all. Hopefully it will show up anytime ?
[Nexus 5X Original Android Development] th3g1z:
Looks like it's live now :) https://dl.twrp.me/bullhead/ thank you Dees_Troy
[Nexus 5X Original Android Development] bobby janow:
It's out now. https://dl.twrp.me/bullhead/twrp-3.0.0-0-bullhead.img.html
[Nexus 5X Original Android Development] SlimSnoopOS:
Using TWRP 3.0, I am able to restore my backup with secure lockscreen (pin and fingerprints) made in TWRP 3.0 and re-enter my pin successfully on every boot. This is with Chroma rom, ElementalX kernel and system root 2.66. Works for compression and not compressed backup.

Anyone else able to do so as well?
[Nexus 5X Original Android Development] illcat2000:
Praise jebus it was such a pain restoring a back up just to realize I forgot to remove the lockscreen pin and print [emoji36] great news.
[Nexus 5X Original Android Development] peltus:
Nog sure if I'm right to post this question here but is anyone using the twrp manager app?

I manually flashed 3.0.0 and its working fine. I then thought the app would make my life easier and installed it.

It won't recognize my custom recovery though. I also don't seem to be able to flash the recovery again from the app. It will download the recovery.
[Nexus 5X Original Android Development] VerneVerne:
I just flashed the new recovery with the app and didn't have any issues.
[Nexus 5X Original Android Development] peltus:
Nexus 5x I presume? It runs into an error whichever version I try.

Unsuccessful it says.

I've got supersu 252 and busybox running perfectly as far as I know.

Anyone else got any suggestions?
[Nexus 5X Original Android Development] buru898:
Does this support f2fs?
[Nexus 5X Original Android Development] SlimSnoopOS:
Only changelog we have is on the official TWRP website:

https://twrp.me/site/update/2016/02/05/twrp-3.0.0-0-released.html

Edit: Ahh, it appears we have an updated OP so my link is pointless :/
[Nexus 5X Original Android Development] allard1997:
Can I flash 3.0.0 in TWRP 2.8.7.2 with just flashing the img in TWRP > Install > Images
[Nexus 5X Original Android Development] TJSteveMX:
Yes of course
[Nexus 5X Original Android Development] wpbear:
Still need ability to flash radio img files in twrp to complete all updates without needing a pc or flashify.
[Nexus 5X Original Android Development] SlimSnoopOS:
If it is not presently available, I am sure the TWRP team will work on it at some point.
[Nexus 5X Original Android Development] Travisdroidx2:
It seems like 3.0.0 does not restore older version of backups?
[Nexus 5X Original Android Development] toma62:
Forgive me when I install TWRP image 3.000

You get to select partition flash images

boot

recovery

Which one should I highlight?
[Nexus 5X Original Android Development] peltus:
Well, since you are flashing a recovery let's go with that.
[Nexus 5X Original Android Development] Midomad:
No.
[Nexus 5X Original Android Development] sognoone:
Is it correct that 3.0.0 doesn't restore backups from older version. It will effect the order I flash updates I need to make...
[Nexus 5X Original Android Development] rbt2008:
Just restored 2.7.x backup on 3.0 without any issues so far.
[Nexus 5X Original Android Development] skulldreamz:
[MENTION=5996255]jollaman999[/MENTION] kernel supports f2fs and inside his latest 5.2 kernel zip also has the new 3.0.0-0 twrp with f2fs support added. I've been using his twrp and running his kernel and can vouch everything works great
[Nexus 5X Original Android Development] bland.life:
Does the slow flashing problem occur with the 5X version?
[Nexus 5X Original Android Development] rekids:
May have been answered, but I can not find an answer yet but OTG is not working with 3.0.0 on the 5X, same thumb drive works on my N6(not 6p) but not on the N5x. Or is there a solution?
[Nexus 5X Original Android Development] peltus:
Is not that OTG doesn't work with 3.0.0. I've personally made several backups to my thumb drive already. No idea if there are differences between adapters or drives that can explain the fact it's not working.
[Nexus 5X Original Android Development] rekids:
I used the same OTG cable and drive on my Nexus 6 that works only difference is the adapter which I checked compatibility by useing the adapter on a data cable used on my Nexus 6 and still able to flash the 5x. Unless that don't work
[Nexus 5X Original Android Development] peltus:
Did it work with an earlier version of TWRP on your N5X or not altogether?
[Nexus 5X Original Android Development] PiousInquisitor:
The adapters apparently don't work with OTG. I have two adapters and three micro USB OTG cables. Not one combination works. USB type C OTG cables work fine though.
[Nexus 5X Original Android Development] rekids:
Think your right 100%, my adapter does work for flashing the phone but not for the OTG cable. Thank you so much wouldn't beeline it if I didn't are it first hand.
[Nexus 5X Original Android Development] Argeddion:
I made a system, boot and data backup with twrp 3.0.0-0 of stock with systemless root.

After playing a little with CM13 I restoored it. But it wont recognice my code for the lock screen. Same with my only older Backup (same partitions)

Did I something wrong or did somebody else have the same probleme?

Sorry dont have log. Did not think before I hit factory reset (gf got already mad)
[Nexus 5X Original Android Development] peltus:
[MENTION=6876924]Argeddion[/MENTION] Here you go: http://xdaforums.com/nexus-5x/help/pattern-unlock-twrp-restore-t3285628
[Nexus 5X Original Android Development] qu4nd:
I'm getting asked for a password when entering TWRP although I haven't set one? What to do?
[Nexus 5X Original Android Development] SlimSnoopOS:
Type: default_password
[Nexus 5X Original Android Development] qu4nd:
Reflashed stock rom and TWRP and the need for a password was gone. Thx anyways!
[Nexus 5X Original Android Development] fire7777777:
i flash the last images , twrp ask me a password pin but i dont have any pin, how can i fix? i reflash the recovery
[Nexus 5X Original Android Development] ddrum2000:
Has anyone noticed that after this month's factory update that TWRP won't unlock the data partition at all: default_password, pin, or pattern?
[Nexus 5X Original Android Development] gleggie:
default_password did not work for me. I also tried to put my pattern as a password like this:

123

456

789

but that also did not work.

Is there a way to prevent TWRP from asking a password each time? Or is the only way to get rid of it to decrypt?

---------- Post added at 09:23 PM ---------- Previous post was at 09:11 PM ----------

I am having the same problem and still have not found an answer. I may just revert to the previous version of TWRP

Edit: Looks like its a problem with the latest Factory image, as I reverted to the previous version of TWRP and still have the same issue. Looks like google screwed up
[Nexus 5X Original Android Development] SlimSnoopOS:
Seems like this is occurring only on MHC19J factory image. MMB29V factory image works fine according to comments on Android Police or Reddit.

I can't speak to it personally, as I have not flashed either image, but it sounds like MHC19J is the March OTA. Some changes are present in the OTA apparently.
[Nexus 5X Original Android Development] gleggie:
So i guess there's no way to flash MHC19J then? I', on MHC19J right now and I can't root or access my storage in TWRP because of the inability to decrypt. Gonna try reflashing MHC19J and try again. If anyone has a solution I would greatly appreciate it.
[Nexus 5X Original Android Development] SlimSnoopOS:
Idk, but I'm sure things will be researched in due time.

Don't do this cuz I have no idea if you can downgrade, but have you already installed the new bootloader along with boot, system, and vendor? Or did you install just the boot, system, and vendor IMGs?

If you installed just MHC19J boot/system/vendor then you can just flash the older MMB29Q files.
[Nexus 5X Original Android Development] gleggie:
I flashed everything, so idk if I can revert.

Edit: So I tried reflashing the factory image and still a no go in TWRP, so looks like i'm out of luck.
[Nexus 5X Original Android Development] SlimSnoopOS:
I just think you need additional input from someone with better grasp on this. This is only my first Nexus so I can't suggest too much in your case. If you can boot up, I'd say enjoy the phone for the time being until this gets situated.
[Nexus 5X Original Android Development] gleggie:
I think i'll give MMB29V a try until MHC19J gets figured out. Thanks for the help anyways
[Nexus 5X Original Android Development] bg1906:
Yeah if you are seeing enter password, you have to install MMB29V instead of MHC19J. I installed MHC19J first and couldn't get into TWRP but after reflashing MMB29V. I was able to get right in and install SuperSU 2.68. Google should mark these clearly with dates. I don't even look at the version to know there are differences. I just download the last one in the list as that is usually the latest version. So in a situation like this, they should clearly mark that these both are March 2016 Updates and then which one is which. I was directed to the right answer by this Reddit post.

https://www.reddit.com/r/nexus5x/comments/49e0ij/601_mhc19j/
[Nexus 5X Original Android Development] gleggie:
Are you saying that for some people, MHC19J won't work at all? I'm running fine on MMB29V after MHC19J didn't work for me.

It's really weird that google would make two versions like this....
[Nexus 5X Original Android Development] bg1906:
I think if you bought the initial batch of Nexus 5X you have one set of firmware where is if you purchased after January 2016 you may have a different version. I think the 2 version deal with how encryption is handled. If you bought between so anything between October 2015 and January 2016 uses MMB29V where is January 2016 and beyond use MHC19J. So if you flash MHC19J and once you flash TWRP if it queries you for a password, then you know you need to reflash your phone with MMB29V. It's all explained here: https://www.reddit.com/r/nexus5x/comments/49e0ij/601_mhc19j/
[Nexus 5X Original Android Development] gleggie:
Thanks for the info! I was wondering why i was having so many problems with MHC19J
[Nexus 5X Original Android Development] fire7777777:
For the flash if i have de version J, i flash with all the erase? Or i can flash all with the Last line of the flash batt less - w?

Inviato dal mio Nexus 5X utilizzando Tapatalk
[Nexus 5X Original Android Development] lexcyn:
If you are getting a password prompt in recovery, you can still use ADB sideload. I've use that to root and install kernels... it just sucks you can't use any automatic flashing tools from within Android until this password bug has been fixed (if it even can be fixed).
[Nexus 5X Original Android Development] dimoochka:
The decryption bug in MHC19J is related to vendor.img. Flashing an older version of vendor.img restores this functionality (although obviously you don't want to use an old vendor.img with a newer ROM).
[Nexus 5X Original Android Development] fire7777777:
you tell me , if i flash J version , but the vendor of version V all si right? isnt there the but password of twrp? why you say that i woul a new vendor?! which is vendor file?
[Nexus 5X Original Android Development] SlimSnoopOS:
For decrypted users, all is good with TWRP 3.0. I guess the TWRP problem is only for folks using encryption.

From decrypted MMB29Q custom rom, factory reset then fastboot flashed all of MHC19J. I booted into TWRP 3.0 and was able to use the install tab to flash SuperSU. I can see all of my internal storage. Verified I am still decrypted as Settings/Security still lists "Encrypt Phone."
[Nexus 5X Original Android Development] Rekoil:
Already posted on the IRC channel, but here's my recovery.log from trying TWRP 3.0.0-0 on MHC19J.

http://hastebin.com/caradequhi.vhdl
[Nexus 5X Original Android Development] Mr0czny:
same here flashed MCH19J and can't enter internal storage
[Nexus 5X Original Android Development] SlimSnoopOS:
Try this:
[Nexus 5X Original Android Development] Shyciii:
I bought Nexus 5X, and update the newer rom ( MMB29U) with OTA. How can decrypted? I try unlock bootloader, flash TWRP 3.0.0 and flash AOiSP custom rom (With thuglife kernel), but the mobile still encrypted.
[Nexus 5X Original Android Development] SlimSnoopOS:
Both methods will delete all of your data (pics/video/everything) from internal storage. In TWRP, wipe internal storage then boot since you are already on a custom rom. Alternatively, with fastboot type: fastboot format userdata
[Nexus 5X Original Android Development] dmudd:
This is the first time I've upgraded before reading people's reviews first. And it will be the last time. I flashed MHC129J and I bought my phone back in October. I couldn't get past the password part in TWRP, thought it was because I needed to upgrade because I was still on TWRP 2.8 so I upgrade. Then I read here that it's the problem with the version build. I tried just flashing MMB29V over MHC129J and I'm getting some funky things happening. First, my home button wouldn't work. Rebooted, and now my app switching button doesn't work. Flashed back to MHC129J and things are still messed up. Guess I need to back up and factory reset... But I'm at work and it's going to kill me to sit here all day knowing something is up with my phone. And now I'm not getting any notifications.
[Nexus 5X Original Android Development] bobby janow:
You'll get it fixed, don't sweat it. You'll need the Google image and a computer for bootloader commands. Keep the J version and either use an OTG stick or google ADB sideload to install flashables if you really need. You can skip it all if you don't want to root, but I have a feeling you do. Once you flash via Heisenberg's guide all the image files other than userdata.img, I'd first reboot and log in and get it all set up. Then to install stuff with OTG if you have one you simply mount the storage after you cancel the password prompt and select "don't modify system" (or something like that). From your post I'm not sure how you flashed the J build though. Alternatively you can install any flashable to the cache partition and mount that since that is not encrypted. Another alternative I heard is to flash the vendor partition from the V build, boot to recovery from bootloader, flash your stuff regularly, then boot back to bootloader and flash the J vendor partition. I wouldn't do that but if you're totally stuck then you might want to give it a shot. Either way it's going to take some time so relax, and methodically do it step by step. Just don't flash a wrong bootloader from a diff device. That is the only way I've seen to brick the device.
[Nexus 5X Original Android Development] ddrum2000:
Have you tried flashing supersu without access to /data? When I tried it, it broke android pay.
[Nexus 5X Original Android Development] bobby janow:
Yes I did and I have it working just fine. Which SuperSU version did you flash?

edit: The way I did it was to twrp 3.0 factory reset (everything but internal data) then reboot to bootloader. Flash every .img from the google J image release other than userdata, and then reboot. Configure to make sure it booted and got data then went back to bootloader and flashed twrp.img. Booted from BL to recovery and got the password warning. Hit cancel, swipe don't modify system and there was the twrp screen although I had no access to internal data. Mounted my OTG drive and flashed SuperSU 2.68 and Osmosis busybox installer and rebooted. Had root installed Titanium. Checked Android Pay and it worked. Left it for the night and booted into recovery again this morning to flash Franco kernel r-6 and Viper systemless. Android pay still works. That's all I did.
[Nexus 5X Original Android Development] ddrum2000:
I sideloaded 2.68.
[Nexus 5X Original Android Development] Smultie:
This might fix the issue for the N5X on the latest update:

There's a test version of TWRP for the Nexus 5X.

https://www.androidfilehost.com/?fid=24438995911975437

Worked for me!
[Nexus 5X Original Android Development] bobby janow:
Lol good short answer to a long winded post. But I didn't do anything else so I'm not sure.
[Nexus 5X Original Android Development] ddrum2000:
That works great. Thanks.
[Nexus 5X Original Android Development] qtipbailey:
Cool, maybe now I'll give MCH19J a try. Where did you find the link to this test version?

I know some folks have installed the MCH19J update and rooted using USB OTG but I've held off from doing the same because I assume without being able to decrypt the data partition TWRP also would not be able to backup the data partition. I usually use USB OTG for flashing anyway but for the sake of discussion, without USB OTG the procedure would be...?

Install the test build of TWRP from TWRP or via Fastboot?

Fastboot flash boot, system, vendor and radio

Reboot into newly updated TWRP and install SuperSU from your now accessible internal storage

?