yashsingh1/xdaforums huggingface dataset:
[Nexus 5X Original Android Development] peltus:
Is there any kernel support required for FBE support? My data is FBE formatted. The new TWRP flashes fine, Supersu 2.82 SR4 flashes fine, thermal and audio mods flash fine. On stock oreo OPR4 kernel it boots fine, but if i try flashing ElementalX the phone won't boot. Did you get it to work with franko kernel?
[Nexus 5X Original Android Development] osm0sis:
Yes, I definitely have FK working great. No idea whether any special commits are necessary.

Maybe EX does something bad and replaces the fstab? FK used to do that, which broke FBE, but I fixed it for Franco using AK2 to make his fstab changes more surgically.

Edit: Found the likely cause. EX's editramdisk.sh in the install zip has the following:

if grep -qr forcefdeorfbe /tmp/ramdisk/fstab.bullhead; then
sed -i "s/forcefdeorfbe/encryptable/" /tmp/ramdisk/fstab.bullhead
fi

Which will replace the fstab's data option of forcefdeorfbe with encryptable, but FBE doesn't work with encryptable. I think SuperSU detects encryption now and only makes it encryptable is it's not encrypted (or maybe just not encrypted with FBE)?

FK just doesn't alter that stuff since it's better left up to a rooting zip, and custom kernels work fine without that stuff anyway.
[Nexus 5X Original Android Development] peltus:
That actually explains a lot of the troubles I've been experiencing.

Unfortunately my FBE adventure ended with me softbricking my 5x after flashing the stock boot, recovery and system partitions, silly me, resulting in having to flash the entire stock image and starting from scratch again. Thus I'm once again on the standard encryption. I think I'll stay away from fbe for the time being, but thanks for taking the time to investigate and explain.

Maybe I'll give it a try when I'm feeling more adventurous again.
[Nexus 5X Original Android Development] youxiaojie:
why this error?FAILED (remote: image is not a boot image)

I run fastboot flash recovery twrp under android 8.but got error : image is not a boot image

D:\TDDOWNLOAD>fastboot flash recovery twrp-3.1.1-0-bullhead.img

target reported max download size of 536870912 bytes

sending 'recovery' (7 KB)...

OKAY [ 0.079s]

writing 'recovery'...

FAILED (remote: image is not a boot image)

finished. total time: 0.099s

what can I do for flash recovery and root my android 8?
[Nexus 5X Original Android Development] CLPose:
Try to download the recovery image again and make sure the file is not currupted. It seems to be a problem with the file. :eek: Good luck! :fingers-crossed:
[Nexus 5X Original Android Development] suku_patel_22:
I am using 3.1.1.0, and fastbot booting it to flash kernels only.

I am facing an issue with FBE on stock 8.0. Wverytime i boot TWRP, i am getting the below error

"FBE support not found in TWRP"
[Nexus 5X Original Android Development] osm0sis:
Use the one I posted 2 pages back. It's called 3.1.1-0-FBE.
[Nexus 5X Original Android Development] AadilSid:
MTP is not working in this recovery.. :/
[Nexus 5X Original Android Development] axiel7:
Use jolla TWRP recovery instead ┐( ˘_˘)┌
[Nexus 5X Original Android Development] Captain_Hungary:
It does, you just have to disable and reenable it first most of the times
[Nexus 5X Original Android Development] g90814:
Anyone have a .zip format of twrp-3.1.1-0-bullhead for 5X?

I'm having issues with adb (computer won't see device in fastboot mode), but can get into stock recovery and run adb sideload and computer can see it.

Thanks
[Nexus 5X Original Android Development] osm0sis:
Stock recovery can only flash things signed by Google. Are you rooted? Use FlashFire.
[Nexus 5X Original Android Development] g90814:
Right now I'm totally stock Oreo. Can't get any computer (I have several Win10 devices) to recognize device in fastboot mode. I was able to access a few weeks ago, not sure what may have changed, all signs point to the phone.

Will keep trying.
[Nexus 5X Original Android Development] SlimSnoopOS:
Just ruling out simple mistakes. ADB only works while the phone is fully booted in Android or in recovery. While in the bootloader, only fastboot commands will work.

Also, try updating your platform tools if you have not done so since upgrading to Oreo. Each major OS updates brings with it a new level of APIs, libraries, etc. The ADB platform tools often need to be updated so that it functions properly on the new OS.
[Nexus 5X Original Android Development] g90814:
I'm just using the Minimal ADB and Fastboot tool... I'll see if there's an update for it.

It's funny, it worked once this morning that allowed me to get fully stock Oreo, so at least I have a functioning phone until I figure this out.
[Nexus 5X Original Android Development] derkleinebroicher:
Did you try the commands "adb kill-server" then "adb start-server", while your phone is connected to your pc? This often helped me, when I had the same issue.
[Nexus 5X Original Android Development] g90814:
Yes have tried that also... no dice.
[Nexus 5X Original Android Development] derkleinebroicher:
? Then hopefully updating adb and Fastboot tools will help. ?
[Nexus 5X Original Android Development] g90814:
Nope no change.

Device is seen with 'adb devices' when fully booted and debugging enabled, but when you reboot into fastboot it's not available as a device.

Even the adb reboot fastboot command just reboots the device normally, not into fastboot :confused:

Oh well!
[Nexus 5X Original Android Development] SlimSnoopOS:
Could you post a screenshot? "Fastboot devices" should not be causing consistent issues when booted into the bootloader. Might be an issue with the Google driver or maybe you could try a different USB port. Might even need to unplug then replug the USB cable after rebooting into the bootloader.

Edit: Also, the proper adb command is: adb reboot bootloader
[Nexus 5X Original Android Development] g90814:
Ok something I did got it to work. I think it was using the updated tools from the SDK, and that I was typing 'adb devices' and seeing nothing, rather than 'fastboot devices' which showed my device.

Thanks all :)
[Nexus 5X Original Android Development] derkleinebroicher:
As adb sideload works, you could get root access by flashing a corresponding Supersu.zip or magisk.zip. With root you can use flashify from playstore to flash a TWRP.img.
[Nexus 5X Original Android Development] g90814:
You can't flash the root solutions with adb sideload (I tried). As someone mentioned previously, it only works with google signed files.

I'm up and running now, however :)
[Nexus 5X Original Android Development] derkleinebroicher:
OK, good to know for the future :good:

And nice to see, you have been successful finally!
[Nexus 5X Original Android Development] SlimSnoopOS:
I have yet to try it but TWRP 3.2 is live and available for download:

http://www.androidpolice.com/2017/1...g-better-support-oreo-roms-pixel-2-bug-fixes/

Edit: read this G+ post for an added warning about some builds but maybe not Bullhead:

https://plus.google.com/+DeesTroy/posts/PhAUQHMXnJK
[Nexus 5X Original Android Development] zurik:
On my bullhead device, it works.
[Nexus 5X Original Android Development] jcmm11:
FBE support?
[Nexus 5X Original Android Development] SlimSnoopOS:
Same. I've flashed a custom kernel and it worked fine on 7.1.2. I'll try 8.0 next week.

FBE is mentioned in the notes but idk firsthand. I'm using default encryption only.
[Nexus 5X Original Android Development] osm0sis:
Nope. I pinged the dev who got FBE working for us on GitHub and he's going to see about submitting his changes officially now that the Oreo/Pixel FBE bringup is all done. So hopefully for 3.2.1 or [MENTION=912474]Dees_Troy[/MENTION] can do 3.2.0-1 for us or something.
[Nexus 5X Original Android Development] tuhinxp04:
Who get FBE working...? Are you please mension the name please...!!
[Nexus 5X Original Android Development] osm0sis:
https://xdaforums.com/nexus-5x/orig...h-recovery-t3230471/post73649646#post73649646
[Nexus 5X Original Android Development] jugoslavpetrovic:
Any material themes for the new 3.2.0.0 somewhere?
[Nexus 5X Original Android Development] eurochild:
TWRP 3.2.0-X

HDPI Themes Folder @ AFH
[Nexus 5X Original Android Development] jugoslavpetrovic:
Works great. Thanks a lot
[Nexus 5X Original Android Development] r3act:
I have had no luck wth 3.2.0.0 so far. I can make a backup but when trying to restore it it just hangs and the phone get very hot. Reverted back to 3.1.1.0 for now. Anyone?
[Nexus 5X Original Android Development] Tortel:
Exactly the same for me.
[Nexus 5X Original Android Development] derkleinebroicher:
+1
[Nexus 5X Original Android Development] rp158:
Cannot confirm this: works fine here, so not a general bug. But I saved 3.1-img for the case ;)

...and had to go back to 3.1. today (sorry, didn't find a reason)
[Nexus 5X Original Android Development] DashWooDeveloper:
TWRP problem

Hi, I flash twrp 3.2.0 on nexus 5x android 8.1 final but nothing to show just show some folder name like this "@szxvr432sfdfz"
[Nexus 5X Original Android Development] TKruzze:
Sounds like you're using FBE. You'll need a version of TWRP that supports FBE. Unfortunately, the previous unofficial version that supported FBE in 8.0 does not work in 8.1 (for me, anyway). Looks like we'll have to wait until it gets fixed / updated.
[Nexus 5X Original Android Development] CazeW:
Same here too.
[Nexus 5X Original Android Development] AquilaDroid:
Add one more to the list. Going back to 3.1.1-0.
[Nexus 5X Original Android Development] Josh:
+1
[Nexus 5X Original Android Development] tuhinxp04:
New version 3.2.1.0 available in official website....!!
[Nexus 5X Original Android Development] jugoslavpetrovic:
Interesting, 3.2.1.0 when I whipe system it seems to be leaving my script file in su.d, that means that it might not wipe at all.
[Nexus 5X Original Android Development] rp158:
[MENTION=6478047]jugoslavpetrovic[/MENTION]: wipe, then mount system and look for script with TWRP-filemanager...
[Nexus 5X Original Android Development] c3k:
you can also:
[Nexus 5X Original Android Development] c3k:
I got an error while formatting my data partition (brand new device, only flashed chainfire kernel mdb08i on system mdb08m)

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

tried to unmount all / disable mtp too

above error is incomplete because I take a screenshot but wasn't saved correctly (maybe because I unmount data?):

root@bullhead:/ # cd /sdcard
root@bullhead:/sdcard # ls
0
Alarms
Android
DCIM
Download
Movies
Music
Notifications
Pictures
Podcasts
Ringtones
TitaniumBackup
data
root@bullhead:/sdcard # cd 0
root@bullhead:/sdcard/0 # cd Pictures/
root@bullhead:/sdcard/0/Pictures # ls
Screenshots
root@bullhead:/sdcard/0/Pictures # cd Screenshots
tmp-mksh: cd: /sdcard/0/Pictures/Screenshots: Permission denied
2|root@bullhead:/sdcard/0/Pictures # ls -al
lstat './Screenshots' failed: Permission denied

everething seems ok anyway: data is decrypted and I can take screenshots after reboot

edit: I can access the screenshots via mtp in recovery (above adb log is from system)

View attachment 3540599
[Nexus 5X Original Android Development] inffy:
So with the newest .2 release we can backup and restore normally? Or will we need to disable all screen securities from SEttings before doing a backup?
[Nexus 5X Original Android Development] Gandalf:
Use the following process, under the following conditions, to have full stock backups with your security code intact:

The point here is to ensure to make a System Image backup BEFORE system is mounted rw. If it has ever been mounted rw prior to the backup being made, verity integrity is lost and the device will not boot unless you flash the stock system image.

Once the System Image backup is made before system is EVER mounted rw, you may then flash other ROMs or whatever you want. To restore the System Image to working order, ensure that system is mounted ro before starting the restoration, as this will preserve the "ro" state that the backup was created in. If you are rw when you restore, you can remount system ro and perform the restoration again. I have not had any issues with lost security codes or boot halts following the above procedure. This should apply to the Nexus 6p (angler) and Nexus 6 (shamu) that is on the new bootloaders that house verity.
[Nexus 5X Original Android Development] inffy:
Thanks for the instructions.

So if I have my stock firmware on the device (not rooted, no TWRP installed), just bootloader unlocked. I can just flash TWRP and boot it and make sure that i mount it RO in the first recovery boot, right? And after that follow the backup instructions from your post so I can backup my current stock rom configuration.

After that I can flash any rom etc and if I want to restore to my stock rom, i just boot to TWRP, make sure the system is mounted RO and then just do a restore of /system, /data and /boot?
[Nexus 5X Original Android Development] westernmg:
Sorry to sound like a noob, but what exactly do i have to select in the backup section to get a complete backup of the rom and my apps ?

When i select everything, the backup is very large, about 6Gb, so i guess some of the data must be backed up twice or so.

What does the system_image.emmc contain?

Gesendet von meinem Nexus 5X mit Tapatalk
[Nexus 5X Original Android Development] sms2000:
I installed TWRP .2 and PureNexus. Everything seems OK but every time I turn the phone on I have a warning like:

"Your device software cannot be checked for corruption .... " with a yellow rectangle. After few seconds the phone boots OK.

I understand it's because I have the bootloader unlocked. But it was stated it's impossible to lock it back when TWRP installed because of brick.

Should I continue as is or there is a fix for the warning without a brick?

Thanks
[Nexus 5X Original Android Development] rustybathtub:
The only fix is to return to full stock and relock bootloader. You can instead opt to mask the warning message. There is a flashable zip available at the themes and apps section.
[Nexus 5X Original Android Development] peikojose:
Something very strange happened, I wanted to try another ROM, so I wiped data, system and cache, before that I made a nandroid of course.

Flashed new rom, new gapps... booted... didn't like the rom... I said no problem because I have a nandroid.

Reboot into recovery, wipe system, data and cache... restore... selected nandroid... error..." cannot restore system -- mounted read only", went to mount, disabled "read only system partition", went to restored, this time it worked flawlessly... rom boots... and the problem begins, i didn't reconizes my PIN, of course I am sure which is my pin.. tried everyhthing... nothing... do I have to clean flash? Why did this happen???
[Nexus 5X Original Android Development] srnoth:
Posted this earlier in the thread:

Also you should "rm /data/system/locksettings.db"

Basically delete any files from /data/system/ which end in ".key" or start with "locksettings".
[Nexus 5X Original Android Development] sms2000:
Neat trick, so they just masked the Yellow/Red triangles as those are stored in image file. Should work as I understand but I'd prefer to see warnings when needed and not to see when not needed.

I did accidentally lock the BL with TWRP installed and had read the article afterward. No brick happened but I decided to make it safe and unlocked again.
[Nexus 5X Original Android Development] TheBurgh:
I make sure not to have any device security settings set prior to nandroid backup and all has been good on restoring.
[Nexus 5X Original Android Development] peikojose:
Thanks. Did I that and worked fine. Yesterday that happened at night, I was like... Wow I have to clean flash now? So I better wrote my question here knowing that in the morning I would have it fixed somehow.. And voila..

---------- Post added at 08:13 AM ---------- Previous post was at 08:12 AM ----------

Sorry I didn't know it was a issue with Android M? I have never done that when using twrp (galaxy nexus, n4 and n5). Do I have to start doing so?
[Nexus 5X Original Android Development] TheBurgh:
Not sure where the problem is. I read a post a few weeks back about people having the same problem when trying to restore backup. Easy enough to set device security up after it boots so it works for me.
[Nexus 5X Original Android Development] Blacknighter:
TWRP latest version working like a charm on my Nexus 5x.

View attachment 3555288View attachment 3555289View attachment 3555290
[Nexus 5X Original Android Development] therealmarv:
Hm, I can confirm TWRP 2.8.7.2 cannot delete cache/dalvik correctly. It will not rebuild cache on boot. I wonder what is deleted though when executed. Having fear I've corrupted anything
[Nexus 5X Original Android Development] jackdubl:
Oops.

---------- Post added at 08:31 PM ---------- Previous post was at 08:22 PM ----------

I noticed nothing rebuilt either. I was hoping it was Marshmallow. Haven't had a problem with the one mod I flashed. So what are you doing, going to the previous version?
[Nexus 5X Original Android Development] skulldreamz:
Twrp rebuilds every time i clear cache/dalvik
[Nexus 5X Original Android Development] jackdubl:
Do apps still update when you boot up, or does it just start up? Mine just starts up, no more "Android is updating apps". I was thinking this was how Marshmallow worked, but maybe twrp isn't wiping correctly.
[Nexus 5X Original Android Development] skulldreamz:
Yeah they still optimize for me every boot after i wipe dalvik cache. If i were you i would format data/media and reinstall stock and then reflash your custom rom and see if that helps. Formatting data/media fixes 9/10 problems every time
[Nexus 5X Original Android Development] jcmm11:
Which su.d? There's 2 of them.

One is in /system/su.d - that one should get wiped.

The other is either /su/su.d or /data/adb/supersu/su.d (normally accessed via sbin path, but via TWRP the sbin path isn't available. For the /su path you need to mount su.img)

Neither of those will get wiped.

Easy way to check - wipe system, mount system, see what's there. Should be nothing
[Nexus 5X Original Android Development] jugoslavpetrovic:
The other one sbin/supersu/su.d. Thanks
[Nexus 5X Original Android Development] rp158:
Version 3.2.1.0 doesn't hang, when restoring a backup ?
[Nexus 5X Original Android Development] tuhinxp04:
Wow...!! That's great...!! Thanks for confirm..!
[Nexus 5X Original Android Development] fvisagie:
Thanks! That's with Android 8.1?
[Nexus 5X Original Android Development] rp158:
[MENTION=6159169]fvisagie[/MENTION]: 'still' 8.0.0.

Edit: I'm on 8.1.0 now and backup&restore work flawless, too.
[Nexus 5X Original Android Development] chris5s:
I have twrp 3.1.1-0 installed on my 5x running rooted Oreo 8.1, whenever I try to install latest twrp 3.2.1-0 I get a bootloop. Tried flashing via fastboot and flashfire and twrp app but same result. Any suggestions? Thanks...
[Nexus 5X Original Android Development] jugoslavpetrovic:
I flashed it via twrp as image and then reboot to recovery, all fine.
[Nexus 5X Original Android Development] CazeW:
[MENTION=4544860]osm0sis[/MENTION] Any update on the FBE support for 8.1?
[Nexus 5X Original Android Development] osm0sis:
You know what I know: https://github.com/TeamWin/Team-Win-Recovery-Project/issues/854#issuecomment-351584348
[Nexus 5X Original Android Development] tom0769:
I'm running stock oreo 8.1, twrp 3.2.1.

Each time i flash stock kernel (boot.img), twrp is gone and I have to reflash recovery..

What am I missing?
[Nexus 5X Original Android Development] peltus:
You're missing that your stock boot.img has a feature that tries to keep the phone completely stock. :D

Either run a modified stock image (there is a thread for that) that has the feature disabled, install a custom kernel or install SuperSU.
[Nexus 5X Original Android Development] osm0sis:
chetgurevitch posted a new test build with FBE support, seems to take a while for "Updating partition details..." but otherwise working well.

https://github.com/TeamWin/Team-Win-Recovery-Project/issues/854#issuecomment-356162635
[Nexus 5X Original Android Development] provolinoo:
Sorry for the stupid question but what is FBE?
[Nexus 5X Original Android Development] Argeddion:
File Based Enycryption.

Every file gets encrypted seperatly, while with its counterpart the whole storage is encrypted as one unit.

With FBE the phone is able to boot without you entering the passcode. And it has some other advantages over Full Disk Enycryption. Google will help you ;)
[Nexus 5X Original Android Development] CazeW:
Like I mentioned in the git thread, I'm having some issues with it. Could be related to though not having the RPMB partition. What I basicly had to do was flash TWRP (had lost it thanks to all my flashing and wiping), flash Magisk (to get root), boot, flash stock recovery with the official TWRP app and convert. Thanks to MagiskSU sticking even after a data wipe, I could reinstall Magisk through the manager and flash the TWRP image again with the TWRP app. The problem I'm now having with TWRP is that none of the settings are sticking and to me it looks like it isn't recognizing that /data is encrypted. It never asks for the password to decrypt and all the file and folder names are scrambled. This wouldn't be that big of a problem if Flashfire had not stopped working with the newest Magisk as well...
[Nexus 5X Original Android Development] TKruzze:
I just took the OTA with the February Security Updates and FBE support seems to be broken again with the fixes made in January. Anyone else confirm?
[Nexus 5X Original Android Development] razorloves:
yep, the feb security update broke fbe decrypt in twrp on all devices.

it was caused by the CVE-2017-13240 security patch

twrp needs to be updated. probably need new keymaster and gatekeeper blobs. not sure yet... haven't looked into too deeply
[Nexus 5X Original Android Development] sirxdroid:
Are there any unofficial builds with working FBE and March security update?
[Nexus 5X Original Android Development] sirxdroid:
From watching the github issue, looks like there are new builds now:

https://github.com/TeamWin/Team-Win-Recovery-Project/issues/854#issuecomment-372503905
[Nexus 5X Original Android Development] Plonkyplonk:
I updated TWRP to the latest 3.2.2. As the OTA update without decryption of the data partition seems really interesting, I updated first TWRP before testing it with the pending update I had of LineageOS (microG version), dated 20180702.

Unfortunately, it doesn't seem to work, as I land on the TWRP screen wanting to know if I want to keep my system partition untouched or permit modification of it. I tried with both answers and the two times I landed on the TWRP homescreen without decryption of the data partition as per design (so the settings were not applied and so on).

But as the LineageOS updater downloads the ZIPs to /data/lineageos_updates, TWRP is not able to see the file as the partition is left encrypted, thus the latest version of TWRP breaks the ability to update LineageOS from the in-system updater.
[Nexus 5X Original Android Development] marcocsh:
I subscripted through 1 year donation but still the app said I'm not subscripted. Any clue?
[Nexus 5X Original Android Development] jcmm11:
Update play store, clear play store data. Try again.

https://www.androidpolice.com/2018/...censing-bug-putting-developers-horrible-spot/

https://www.apkmirror.com/apk/google-inc/google-play-store/google-play-store-10-8-21-release/
[Nexus 5X Original Android Development] marcocsh:
Thanks! It works like a charm!
[Nexus 5X Original Android Development] parthabhatta:
On 5x build MDB08L and systemless root. Everytime I come out from TWRP (2.8.7.2), I am given the warning that "System is unrooted" I ignore and press "Do not Install" and boot to system. No problem otherwise and root is working fine. Not getting the reasons for the warning message.
[Nexus 5X Original Android Development] add12364:
can't decrypt my nexus 5x. Still says encrypted in settings. I flashed the modifed boot with fastboot then also flashed the latest twrp. Twrp works flawlessly but idk why it still says encryped in settings.