Not officially.What are you talking about? There is already twrp with android 12/12.1 decryption fully working.
Not officially.What are you talking about? There is already twrp with android 12/12.1 decryption fully working.
I don't think there is, or if there is then it's not very easy to find which is why that question was asked. The official build can't decrypt /data fully without deleting all lockscreen passwords and fingerprints. Neither can the unofficial one posted above. Which leads me to the question as politely as you're clearly capable of asking, what are YOU talking about?
So why then one from here decrypt my data using pattern without a problem? Man it is decrypting data and it is confirmed by manyyyy people around xda and telegram![]()
[RECOVERY] [12] [OFFICIAL] TeamWin Recovery Project
Introduction: Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added...forum.xda-developers.com
If you are not using LOS on your main phone or don't mind to be a beta tester, that's ok. Thanks for the contribution to the community. Some of us don't have that time/luxury/opportunity.
It would be helpful if you could link to exactly which build you're talking about (there are multiple official and unofficial ones posted in that thread). All the ones I'm trying can't decrypt /data/media/0. Also do I need to reformat /data again in order to get this decryption to work, as some people seem to be suggesting?So why then one from here decrypt my data using pattern without a problem? Man it is decrypting data and it is confirmed by manyyyy people around xda and telegram![]()
[RECOVERY] [12] [OFFICIAL] TeamWin Recovery Project
Introduction: Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added...forum.xda-developers.com
Thank you so much, man. I'm using precisely the LOS recovery.WARNING: I soft bricked my phone trying this the first time and had to format /data to get it working again. Back everything up if you're going to try it.
The answer is yes, but with a lot of hassle in my experience. The reason it doesn't work at the moment is linked to the fact that TWRP (and other custom recoveries) can't decrypt /data on Android 12.
The solution is this fork of Magisk made for the very purpose of getting Magisk to survive OTA updates when recovery can't decrypt /data:
https://github.com/programminghoch10/Lygisk
WARNING 2: That fork only supports LineageOS Recovery. When I tried it with TWRP that's when I got the soft brick. I then wiped and reinstalled everything, including LineageOS Recovery, Lygisk and an older version of LineageOS 19.1. When I then updated LineageOS using the OTA updater, the update went fine and Lygisk survived the update OK too.
It would be helpful if you could link to exactly which build you're talking about (there are multiple official and unofficial ones posted in that thread). All the ones I'm trying can't decrypt /data/media/0. Also do I need to reformat /data again in order to get this decryption to work, as some people seem to be suggesting?
Edit: I got it working with this build:
https://www.pling.com/p/1833617/
I had to format /data first though (again), decryption wouldn't work otherwise. And thanks but at the same time a little less ego flexing / attitude wouldn't go amiss next time.
I think so yes. That may have been it then as obviously formatting /data removes the passcode/pattern.Did you had a password/pattern when you flashed the new twrp 12. I had the decryption issue. Booting system, removing and adding pattern again, fixed my decryption issue.
I have followed this steps, everything worked ok.Not sure why you want/need to rename the package file name. But from memory this worked fine for me:
1. Upgrade TWRP to latest official version
2. Flash Xiaomi firmware update (link posted above somewhere) with TWRP
3. Flash Lineage update with TWRP
4. Flash Magisk with TWRP
5. Personally I then flashed GApps.
6. Wipe cache / dalvik cache
7. Reboot
Just be aware that once you reboot TWRP will no longer be able to decrypt /data due to TWRP bug with Android 12 firmware. Although personally it works for me if I delete fingerprints and pass code.
Is anybody using chrome browser ?...mine seems to freeze for a few seconds while browsing....anyone any ideas ?
Please, tell on Telegram: https://t.me/SebaUbuntuChatYesterday I did not receive a cell broadcast (emergency message) running lineageos 19. This worked fine under lineageos 18.1
Using Chrome here. No issues. 103.0.5060.71I have the same issue with Brave, so it's something related to Chrome. In 18.1 it was working well.
I've got LSPosed installed via Zygisk and it seems to work fine, athough I've only used one module so far (SIM number setter).Has anybody installed any Xposed framework under lineageOS 19.1? Any particular issues found?
I'm planning to upgrade from LineageOS 18.1 to 19.1 but wouldn't like to loose some (currently EdXposed) modules.
Just updated from 11 to 12 today via dirty flash and so far so good.
Here's what I did;
1. Downloaded latest version of MindTheGapps for 12L.
2. Downloaded TWRP-3.6.2-vayu-Nebrassy-03-07-22.img
3. Downloaded latest 19.1 LinageOS daily.
4. Extracted boot.img and created MagiscBoot image.
5. Removed lock from existing 18 linage. The nebrassy twrp can't decode android 11 for some reason (works on 12).
6. Reboot to Recovery
7. Flash nebrassy twrp and reboot to recovery
8. Flash LinageOS 19.1
9. Flash nebrassy twrp recovery
10. Flash magisc boot image
11. Flash MindTheGapps
12. Clear cache/dalvik
13. Reboot
After adding fingerprint and lock, twrp can decode.
And that's it. All my apps and data remained
Pass safety net, gpay working. Happy days
Someone asked?Thanks for finally releasing LineageOS, but you devs are 3 months too late... ArrowOS has inadvertently stolen my heart in your absence, lol.