great work thank youHere is test3, tested with the latest firmware: https://build.twrp.me/test/redfin/twrp-3.5.0-0-test3-redfin.img
Please let me know what issues you have. I will be working on integrating fscrypt v1 policies so I can port over crosshatch to the aosp11 tree. I will work on repacking afterwards.
Hey FYI the link still downloads test 3 instead of test 5. When I change the url to 5 it works. I'm going to test 5 now I'll edit this post with the results.I posted a link to a test4 image in OP. I enabled MTP and fixed bind mount to /sdcard from /data/media/0.
test 5 is working very well tho the link is pointing to test 3I posted a link to a test4 image in OP. I enabled MTP and fixed bind mount to /sdcard from /data/media/0.
Most of the decryption flags show up as unhandled on bramble. Any thoughts on a fix short of compiling from scratch? Thanks.Do you have logs for debugging? I cannot help without logcat and recovery.log.
Hey FYI the link still downloads test 3 instead of test 5. When I change the url to 5 it works. I'm going to test 5 now I'll edit this post with the results.
test 5 is working very well tho the link is pointing to test 3
this is the fixed link https://build.twrp.me/test/redfin/twrp-3.5.0-0-test5-redfin.img
anyway great work what's misc?
What is bramble? I am not sure what you are referring to? What are you wanting to compile from scratch?
Should I keep crypto disabled or should I try to resolve the fscrypt includes somehow? With crypto disabled to avoid that error, I've got the Google boot splash with the above ADB fix for proper shell access including dmesg and logcat, but it fails to start actual TWRP and the logcat is complaining about missing vintf manifest entries for android.hardware.boot and android.hardware.health
Edit: I also had to inject the Proton kernel for it to boot, I'm currently using the latest AOSP11 bramble/redbull with your commits cherry-picked like I did earlier with the lineage-18.1 attempt