Fingerprint sensor reset - Xiaomi Mi 6 Questions & Answers

Hello,
Now I'm on LineageOS 16 from @NeoArian.
I've builded a kernel based on the source of LineageOS 16 provided by @NeoArian and flashed it via AnyKernel2 script.
After rebooting I've realized that my fingerprint scanner does not work. It was nothing in "Fingerprint" section of settings and when I tried to add a fingerprint, I've got the error (on screenshot).
I've tried to rollback the kernel (reflashed the LineageOS zip) but it wasn't helped.
I've tried to flash MIUI 9 and on this ROM fingerprint sensor works correctly.
After that I've tried to flash LineageOS 16 again but I still got the error.
Logcat (attached) says that the fingerprint could not be written to memory. Is it possible to reset this memory?
Thank you.

Related

[ROM+TWRP][taido][7.1.x][UNOFFICIAL] Lineage Android Distribution for Moto E3

LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review.
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
* Submitting bug reports on nightly builds is the leading
* cause of male impotence.
*/
WHAT WORKS
Boot
WiFi
Hotspot
Audio
RIL
Bluetooth
Sensors
FM
Camera
SDCard
GPS
KNOWN ISSUES
Video recording
VoLTE [Don't expect it to be working anytime soon]
SELinux Enforcing
!!! BUG REPORTS WITHOUT LOGS WILL BE IGNORED !!!
Android: adb logcat
Radio: adb logcat -b radio
Kernel: adb shell dmesg
Full Bugreport: Developer Menu -> Bugreport
HOW TO INSTALL LINEAGEOS
- Download the LineageOS zip(s). (see Downloads)
- Download the TWRP Image. (see Downloads)
- Copy the LineageOS zip to internal sdcard.
- Unlock bootloader and install TWRP from downloads.
- Boot into TWRP.
- Perform a backup of your current ROM. (Optional)
- IMPORTANT: Do a Factory Reset. (Wipe data & cache)
- Flash LineageOS.
- Optional: Install the Google Apps addon package. (see Downloads)
- Reboot
DOWNLOADS
LineageOS:
https://www.androidfilehost.com/?w=files&flid=203899
TWRP:
https://www.androidfilehost.com/?w=files&flid=203904
Google Apps:
OpenGApps (recommended: arm, 7.1.1, nano)
SOURCECODE
Device tree: https://github.com/ashwinr64/android_device_motorola_taido
Kernel: https://github.com/ashwinr64/android_kernel_motorola_mt6735
Vendor: https://github.com/ashwinr64/android_vendor_motorola_taido
HOW TO CONTRIBUTE
Use our code review system to send patches: https://review.lineageos.org
SUPPORT ME
Do you like my work? Consider donating me some beer!
​
XDA:DevDB Information
LineageOS for taido, ROM for the Moto E3
Contributors
ashwin007
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.x
Version Information
Status: Testing
Created 2017-08-03
Last Updated 2017-08-03
Changelogs
-> Build 1 [04-08-2017]
* Initial Public Release
* Merged upstream 3.18.63 kernel.
* Switched to XZ kernel compression and enabled -O2 flag.
* Widevine has been fixed, so DRM contents are playable.
-> Build 2 [16-08-2017]
* Synced with Lineage
* Merged upstream 3.18.65 kernel
* Hotspot fixed
* Added support for F2FS
Thanks a lot!
And the development starts again
Dear @ashwin007,
I'm so glad [emoji1] to see that you are working on taido.
I appreciate your brilliant work.
All the best
A fresh install of this ROM shows 14 GB used up by the system partition and negligible space in the data partition. Any solutions?
Not installing.
Code 7 error
bubba1601 said:
Not installing.
Code 7 error
Click to expand...
Click to collapse
use TWRP given by Ashwin, also check weather u did factory reset....
also follow the instructions....
spykarzzz said:
use TWRP given by Ashwin, also check weather u did factory reset....
also follow the instructions....
Click to expand...
Click to collapse
My Friend, I've been flashing Roms on various devices for more than three years.......
So I have done a factory reset, as I'm using another lineage OS version on my E3.
I followed all instructions.
So the TWRP version I'm using must be the issue, its the Dr framazone version 3.0.0.2, I can't flash the new twrp image in the twrp I'm using.
I'll have to try in fast boot mode through the PC.
U need deckers TWRP to flash dis particular Rom....Try this only!!!
One request, can you please add double tap 2 wake feature in the kernel?
spykarzzz said:
U need deckers TWRP to flash dis particular Rom....Try this only!!!
Click to expand...
Click to collapse
Yes, I know and understand that.
As I said in my previous comment, I cannot flash the newer twrp image through the version of twrp I'm using.
I've have now managed to flash the twrp image via fast boot and have this ROM up and running.
Unfortunately I've ran into many problems not seen in the other lineage OS ROM that I've been using for the last week.
1. Guest user was activated after initial set up, meaning I could not change any settings.
2. I cannot access my external SD card.
So important files to me are inaccessible?
3. No photographs taken using the camera are being saved, they just disappear from the gallery into thin air.
4. My service provider doesn't list in networks or the signal indicator (O2 UK) instead my device shows "23410"
Its at this point I confess to running this rom on my XT1700 and NOT a XT1706 (My device is in fact a European spec standard Motorola E3, but running E3 power firmware and renamed in system to a E3 power XT1706 - this was flashed by Motorola themselves during a repair as they claimed I had to pay for XT1700 firmwares, so E3 Power firmware was flashed by them.
Although I appreciate Ashwins efforts and i appreciate this is a testing version, I cannot use this ROM as I'm now also in trouble with my employer for not having photographic evidence of my work today (My E3 is used as my work device, and taking photos of my finished work is a requirement of my employment)
I have to now move to another ROM for this reason until these issues can be fixed and photos taken with the camera will be saved and stay saved.
Sorry.
Is there any issue with this rom
Pls let me know friends
I am waiting for a stable rom
Camera is working or not
Or any kind of bugs pls tell me
aman4512 said:
A fresh install of this ROM shows 14 GB used up by the system partition and negligible space in the data partition. Any solutions?
Click to expand...
Click to collapse
Bro do this....
U have to go to fastboot mode....
Then enter fastboot format userdata....
Then fastboot flash recovery.img
Then dont go to recovery let ur phone start....
Then enable usb debug & oem unlock in phone after rebooting...
Again switch of ur phone...
Now goto fastboot mode....
Type fastboot flash recovery .img
Now go to recovery and flash the rom file
It ll work 100%
solkarsalman said:
Bro do this....
U have to go to fastboot mode....
Then enter fastboot format userdata....
Then fastboot flash recovery.img
Then dont go to recovery let ur phone start....
Then enable usb debug & oem unlock in phone after rebooting...
Again switch of ur phone...
Now goto fastboot mode....
Type fastboot flash recovery .img
Now go to recovery and flash the rom file
It ll work 100%
Click to expand...
Click to collapse
Thanks, but I had solved the problem. The thing is my phone wasn't booting at all after flashing TWRP. Tried many version. It was some issue with the phone's boot.img (some Lenovo phone has a similar issue, K4 power I think). I flashed a stock ROM and after flashing TWRP, I flashed SuperSU, since it patches boot.img. That worked, after which I wiped /system, /data, /cache and flashed Lineage.
bjyadav4 said:
Is there any issue with this rom
Pls let me know friends
I am waiting for a stable rom
Camera is working or not
Or any kind of bugs pls tell me
Click to expand...
Click to collapse
Read the comments above you own
Don't install it, I had major issues.
Read previous comments before posting.
bubba1601 said:
Yes, I know and understand that.
As I said in my previous comment, I cannot flash the newer twrp image through the version of twrp I'm using.
I've have now managed to flash the twrp image via fast boot and have this ROM up and running.
Unfortunately I've ran into many problems not seen in the other lineage OS ROM that I've been using for the last week.
1. Guest user was activated after initial set up, meaning I could not change any settings.
2. I cannot access my external SD card.
So important files to me are inaccessible?
3. No photographs taken using the camera are being saved, they just disappear from the gallery into thin air.
4. My service provider doesn't list in networks or the signal indicator (O2 UK) instead my device shows "23410"
Its at this point I confess to running this rom on my XT1700 and NOT a XT1706 (My device is in fact a European spec standard Motorola E3, but running E3 power firmware and renamed in system to a E3 power XT1706 - this was flashed by Motorola themselves during a repair as they claimed I had to pay for XT1700 firmwares, so E3 Power firmware was flashed by them.
Although I appreciate Ashwins efforts and i appreciate this is a testing version, I cannot use this ROM as I'm now also in trouble with my employer for not having photographic evidence of my work today (My E3 is used as my work device, and taking photos of my finished work is a requirement of my employment)
I have to now move to another ROM for this reason until these issues can be fixed and photos taken with the camera will be saved and stay saved.
Sorry.
Click to expand...
Click to collapse
I didn't face any of the above issues on my Moto E3 Power. Camera is working fine and photos are also saving.
SD card is also accessible.
---------- Post added at 07:34 AM ---------- Previous post was at 07:30 AM ----------
bjyadav4 said:
Is there any issue with this rom
Pls let me know friends
I am waiting for a stable rom
Camera is working or not
Or any kind of bugs pls tell me
Click to expand...
Click to collapse
Camera is working properly.
If you do this
Thanks, but I had solved the problem. The thing is my phone wasn't booting at all after flashing TWRP. Tried many version. It was some issue with the phone's boot.img (some Lenovo phone has a similar issue, K4 power I think). I flashed a stock ROM and after flashing TWRP, I flashed SuperSU, since it patches boot.img. That worked, after which I wiped /system, /data, /cache and flashed Lineage.
Click to expand...
Click to collapse
then storage problem will also be solved.
aman4512 said:
A fresh install of this ROM shows 14 GB used up by the system partition and negligible space in the data partition. Any solutions?
Click to expand...
Click to collapse
Is this the actual screenshot? Because the developer has mentioned that LTE is not working but the screenshot shows LTE in the notification bar.
ranjithgn said:
Is this the actual screenshot? Because the developer has mentioned that LTE is not working but the screenshot shows LTE in the notification bar.
Click to expand...
Click to collapse
LTE works, VoLTE doesn't.
precedentbrute said:
I didn't face any of the above issues on my Moto E3 Power. Camera is working fine and photos are also saving.
SD card is also accessible.
---------- Post added at 07:34 AM ---------- Previous post was at 07:30 AM ----------
Camera is working properly.
If you do this
then storage problem will also be solved.
Click to expand...
Click to collapse
Thank you for your feedback, although I can't share your optimism or your confidence.
I've now reflashed this rom three times.
I cannot access external storage.
Photos disappear from the gallery, and now all my Google apps keep force closing - I'm using the recommendation of Google apps, open gapps nano arm.
Remember just because it's all good for you doesn't necessarily mean it's good for others, as I've seen so many times in these forums.
Regards.

[G800F/M/Y][ROM][8.1.0][OPM2] LineageOS 15.1 for G800F/M/Y [Alpha]

This is a LineageOS 15.1 ROM for the Exynos3470 based Samsung Galaxy S5 mini (G800F/G800M/G800Y).
DO NOT USE IT FOR G800H OR YOU WILL BRICK YOUR DEVICE
Please do not ask for support or ROMs for the G800H. G800F and G800H have nothing in common.
Working features
HW accelerated GUI
Initiate and receive calls
Camera (only photos)
Flash Light
Sound
Fingerprint scanner
Hardware sensors (Orientation, Compass, Proximity, Acceleration, Hall sensor, Step counter)
Light sensor (needed for auto-brightness)
Pulse sensor (preliminary and very inaccurate. Works with Apps like Kardiograph)
Wifi
GPS
Bluetooth (A2DP, HFP, HID)
Mobile Data
SMS
MTP storage
USB-OTG (Keyboard, Mouse, USB-Audio)
IR
NFC
Video reproduction is still sometimes a bit buggy on browser (Youtube works fine)
Untested features:
SD-Card as internal storage
Known issues:
USB-OTG (Mass-Storage): detected but the file-system is not usable and will be corrupted afterwards (--> do not connect your USB-stick at the moment)
SELinux not enforcing
Video recording is still buggy/not working (crashes)
Fingerprint scanner can only records 3 fingers and sometimes it could be unresponsive
Disclaimer:
You flash this image at your own responsibility. I am not responsible for any damage that might be caused by flashing this image (bricked device, lost data, ...)
Flashing this kernel image will trigger the KNOX counter, so your warranty will be void.
Applications that use KNOX (e.g. "Private Mode") might not work anymore when returning to the stock ROM, as the device is regarded as compromised. Do not flash this ROM if you need those applications.
The image is only for Exynos3470 based S5 Mini variants SM-G800F/M/Y.
It might be instable, crash your device, drain your battery, or even might damage your smartphone (e.g. if an USB-OTG device drains too much power)
Click to expand...
Click to collapse
Before you start:
Backup your data, like call history, contacts, sms, WhatsApp messages, favourite app settings that are on internal and external sd (by using Titanium Backup or other apps available on PlayStore). At least all internal data will be lost in any case. If you have bad luck you might also loose data from your external sd card.
Important note: It is possible that flashing this ROM can cause efs partition issues. Therefore it is strongly recommended to make a backup of your efs partition before flashing this ROM. This can be done via TWRP.
Download:
Odin3-v3.07 (it is contained in CF-Auto-Root)
TWRP 3.1.1-0 (.tar.md5 file)
Latest TWRP (.img/.tar file)
LineageOS 15.0 ROM for G800F/M/Y: Android File Host
LineageOS 15.1 Monthly/Weekly updates (@Andrea224): Google Drive
Open GApps (select the variant you prefer, e.g. mini)
Install recovery:
Reboot your device into Download mode: turn off your device, then press Volume-Down + Home + Power button at the same time and release them.
Confirm the following warning message with the Volume-Up button.
Connect your device to your PC via USB
Make sure the device driver's are installed on your PC
Start Odin
In Odin select "PDA" (in newer versions: "AP") and select the recovery image (recovery.tar.md5)
Check that only "F. Reset Time" is set. "Auto Reboot" should be disabled to avoid a reboot into stock ROM.
Click on "Start": the recovery image should be flashed now. By flashing the recovery, your warranty will be void.
After the recovery flashing process was successful, reboot into recovery mode (see instructions below).
Important: make sure not to boot into stock ROM, otherwise the stock ROM might remove the custom recovery again. If this happens, flash the recovery image again.
Flash ROM:
Reboot into recovery mode (Press Volume-Up + Home + Power button)
Make a Backup of your phone (Backup, then select Boot, System, Data, then swipe to backup). Note that the recovery might fail to restore the backup when you want to go back to the stock ROM.
Copy GApps and LineageOS ROM zip to your device's internal or external SD card
Connect your device via USB to a PC. You should see the device in the Windows File Explorer now.
If you do not see the device in File Explorer, make sure that MTP is enabled (inside Mounts, click on Enable MTP).
If MTP does not work from recovery, try to copy via MTP by booting your old Android ROM or just remove the external SD card and copy to it directly.
Select one of the two drives (internal or external SD) and copy the files to it.
Do not put the files into the data directory of the internal sd card, otherwise they will be wiped in the next step.
Wipe Dalvik Cache, Cache, System and Data (inside Wipe -> Advanced Wipe).
Do not report problems if you did not wipe those partitions as the problems are most probably related to this!
Install the LineageOS ROM zip package
Install the GApps zip package
How to root:
LineageOS does not have root support integrated by default. You have to download addonsu-arm-signed.zip for 14.1 from the Lineageos Extras download page and install it with TWRP.
After that root access is still disabled by default. If you want to activate root access for apps, do the following:
Open the Settings menu, select "About Phone"
Tap on the "Build number" entry seven times. You should be notified, that the developer settings are now active.
Open the Settings menu, select "Developer options". Enable root access by selecting "Apps" in the "Root-Access" setting.
In case you want to go back to the stock ROM:
lf you do not have the latest ROM for the G800F you can download it from SamMobile
Reboot your phone into Odin mode
Open Odin on your PC and connect your smartphone with your PC via USB
If you have a zip-file unzip it so that you have a .tar.md5 file
In Odin click on the PDA button and select the .tar.md5 file. Then press "Start".
Normally the stock rom fails to boot as the data from CM is still on the data partition. So after flashing the stock rom, reboot into recovery mode (it looks a bit different now). First wipe the data partition, then wipe the cache.
Reboot
Changelog
Code:
24/10/2017:
* Wake on Home button press
* Model string fixed ("G800F" instead of "G800")
* GPS fixed
* Bluetooth fixed
* Update to newest LineageOS sources
* Note: Android 8.0 requires a new TWRP recovery (build from 22/10/2017). otherwise you will not be able to flash the image ("E3004: This package is for device: kminiltexx,kminiltedv,kminilteub,kminilte; this device is .")
10/10/2017:
* telephone calls working
* Camera works (recording videos might still not work)
* LineageOS sources updated
24/09/2017:
* Initial test build
Source:
https://github.com/cm-3470/android_device_samsung_kminilte (Check README.md for build instructions)
Help from other developers is always welcome. Just ask in this thread or PM if you want to help.
Thanks to spookcity138, ayke, mirhciulica, Psyafter and CTXz for working on this ROM.
XDA:DevDB Information
[G800F/M/Y][ROM][8.1.0][OPM2] LineageOS 15.1 for G800F/M/Y [Alpha], ROM for the Samsung Galaxy S5 Mini
Contributors
hennymcc, ayke, Andrea224, spookcity138, mirhciulica, CTXz
Source Code: https://github.com/cm-3470
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.4.x
ROM Firmware Required: TWRP Recovery [version >= 22/10/2015]
Based On: LineageOS
Version Information
Status: Alpha
Created 2017-09-24
Last Updated 2018-07-05
Wow thanks for your amazing work!
I am experiencing random reboots when I lock my device.
oh nice, im testing right now
tibor8 said:
I am experiencing random reboots when I lock my device.
Click to expand...
Click to collapse
Thanks for the info. I was able to reproduce it now. Will be fixed in next build.
RIL will be fixed too.
phone when it locks up in a reset, it does not turn on a constant download, and the wi-fi is on and off after every 5 seconds. Also, there's no way to turn off the backlight of the buttons. Also, I noticed that the connection only lights up H on the seven I'm on H +
wasya78 said:
phone when it locks up in a reset, it does not turn on a constant download, and the wi-fi is on and off after every 5 seconds. Also, there's no way to turn off the backlight of the buttons. Also, I noticed that the connection only lights up H on the seven I'm on H +
Click to expand...
Click to collapse
That means you see the SIM-card now?
yes sim card is seen
---------- Post added at 09:20 AM ---------- Previous post was at 09:17 AM ----------
still noticed that the android 8.0 does not work camera
amazing
wasya78 said:
yes sim card is seen
Click to expand...
Click to collapse
Hallelujah, I'm gonna go get drunk *vodka*
ty best news since your lineage 14 release +++
Hello, is it possible to deactivate this new Slide Menu on Home Screen? To have the old Catapult menu Button back? Or will it be possible in future releases?
There is root inbuild again?
Thanks for development!!
MikeT. said:
There is root inbuild again?
Thanks for development!!
Click to expand...
Click to collapse
No
Sorry my mistake, its the rootmanagment for addonsu in develooer options, now i see it.
Thanks for fast reply
Great! Thanks. Looking forward to next build.
Will these non-working features be updated soon? Because I am using version 14.1 at the moment, and I can't even start the camera... I hope you will either update the previous version or get the camera working in version 15 so I can use that version.
just wanna stop by and tell you that you're awesome, keep up the amazing work!
Jelsie said:
Will these non-working features be updated soon? Because I am using version 14.1 at the moment, and I can't even start the camera... I hope you will either update the previous version or get the camera working in version 15 so I can use that version.
Click to expand...
Click to collapse
At least camera and calls work now. I was abroad for a week so I could not work on it or release a new build.
Maybe there will be a new build next week.
I uploaded a new build with RIL and camera fixed. See opening post for more details.

Failed To Install Magisk to Zenfone 2 ZE500CL with LineageOS 14.1

Hello. This is my first post in this forum, so forgive me if i post this in a wrong category.
I have Zenfone 2 ZE500CL, flashed with LineageOS 14.1 20180127 Nightly Build from this.
I've tried to install the latest Magisk from here : https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445, also the one from here : https://forum.xda-developers.com/zenfone2/development/magisk-14-0-root-universal-zenfone-2-t3669137. None of them working. Both of them prints output that says : "Unable to Detect Boot Image".
I've tried to extract the boot.img from my device build of LineageOS, and then use Magisk Manager to patch the boot image manually, and failed miserably. I've even tried to extract the boot.img to test if it's even readable with Android Kitchen, and sure it is it can't read the file while outputting : "Unsupported Format".
Can anyone help me at this?
same here tried everything i know but still unsupported for our device, i'm using mokee rom for asus zen2 500cl
i found that we need a boot image signature just like the others try to look at this https://forum.xda-developers.com/zenfone2/development/script-boot-recovery-image-signature-t3690522

Stuck installing ROM on Mi A2 Lite (daisy) - ERROR 1, ERROR 7

Hi,
I am "building" (first had to fix the LCD etc.) a de-googled DAISY. I managed to unlock the bootloader, install TWRP, and root the original OS (Android One 10).
The problems started when I tried to install a custom ROM (at first Havoc, but other gave the same results). Just as instructed (YT, other pages, here...) I:
- formatted via TWRP
- REBOOT to TWRP
- wipe all except SD
- install ROM from zip
...and at this point I came across an error message
Error applying update: 7 (Error code: : kInstallDeviceOpenError)
Updater process ended with ERROR: 1
Many solutions suggest flashing boot.img from the ROM package, but (WHY?!?) all ROM's ((Havos, crDroid etc.) for daisy have no such file, although other devices have boot.img in their package.
I'm pretty much clueless... :/
Help, and thanks in advance...
mothzart said:
Hi,
I am "building" (first had to fix the LCD etc.) a de-googled DAISY. I managed to unlock the bootloader, install TWRP, and root the original OS (Android One 10).
The problems started when I tried to install a custom ROM (at first Havoc, but other gave the same results). Just as instructed (YT, other pages, here...) I:
- formatted via TWRP
- REBOOT to TWRP
- wipe all except SD
- install ROM from zip
...and at this point I came across an error message
Error applying update: 7 (Error code: : kInstallDeviceOpenError)
Updater process ended with ERROR: 1
Many solutions suggest flashing boot.img from the ROM package, but (WHY?!?) all ROM's ((Havos, crDroid etc.) for daisy have no such file, although other devices have boot.img in their package.
I'm pretty much clueless... :/
Help, and thanks in advance...
Click to expand...
Click to collapse
Error 1 usually means wrong install package or wrong TWRP.
Are you using TWRP by offain?
[SOLVED]
The whole problem was that TWRP was wrong (not even offain as far as I remember). But I got a HUUUUGE amount of help (MANY THANX!!!!) from opal06 (main maintainer for crDroid on daisy) on Telegram channel dedicated to crDroid on daisy.
So If anyone hase similar problems - go to Telegram group - they will help you!
After flashing right (modified) TWRP versions, evrthng went fine, although I got to admit it was pretty complicated for [unlock + TWRP + custom rom + root] combo. On lavender it was much easier
cya all, good luck!

[ROM][12.1][OnePlus 5/5T] AOSP for OnePlus 5 [07 JULY 2022]

AOSP for OnePlus 5/5T - Android 12
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it!
*/
Most of the information from here can be applied for this ROM.
Introduction
This projects aims to create an upgradable AOSP build system for the Oneplus 5 (Cheeseburger).
No repository from AOSP is changed: no commit over AOSP is at the moment present on the sources for this ROM.
All the changes are provided in separate repositories (HALs, kernel): this allows to upgrade Android with minimal effort, potentially also for future major versions.
Most of the added repositories is provided by LineageOS or CAF, so thanks to them for those repos.
Screenshots are attached.
This ROM is based on the work on Android 11 from here: https://forum.xda-developers.com/t/...-19-september-2021-locked-bootloader.4183691/
As usual, only builds with enforcing SELinux, no root access and 'user Android build flavor' will be posted here.
Known issues
- None that I'm aware of.
Changelog
See second post.
Download
Releases can be found on AndroidFileHost.
OnePlus 5 (Cheeseburger): https://androidfilehost.com/?w=files&flid=328726
OnePlus 5T (Dumpling): https://androidfilehost.com/?w=files&flid=328820
Installation
Backup everything.
The provided zip can be installed using the TWRP recovery: clear data while doing that.
The ROM expects the firmware from OOS 10.0.1: different firmwares are not tested.
The provided recovery allows only flashing signed images: use TWRP if you need to flash GApps or different packages.
Sources
Kernel on github: https://github.com/robertoglandroid/kernel_oneplus_msm8998
ROM sources: https://github.com/roberto-sartori-gl/local_manifests/tree/a12/gl
Telegram discussion group here!
XDA:DevDB Information
AOSP for OnePlus 5/5T, ROM for the OnePlus 5/5T
Contributors
robertogl
Thank you to @T1mb3 and @Maitreya29!
ROM OS Version: Android 12
ROM Kernel: Linux 4.x
Version Information
Status: Beta
Created 2021-10-05
Last Updated 2022-07-07
Changelog
[07/07/2022] aosp12_cheeseburger/dumpling-ota-user-20220707.zip
July2022 Security patches (synced with AOSP android-12.1.0_r10)
[08/06/2022] aosp12_cheeseburger/dumpling-ota-user-20220608.zip
June 2022 Security patches (synced with AOSP android-12.1.0_r8)
[21/05/2022] aosp12_cheeseburger/dumpling-ota-user-20220521.zip
Support f2fs formatted /cache partition
Synced with Lineage 19.1 sources
Minor fixes
Code cleanup
[15/05/2022] aosp12_cheeseburger/dumpling-ota-user-20220515.zip
Add option to apply OTA updates from SettingsExtra
4 files can be installed:
the ROM OTA - put the zip in /sdcard/update.zip
magisk - put the zip in /sdcard/magisk.zip
gapps - put the zip in /sdcard/gapps.zip
decryption zip - put the zip in /sdcard/decrypt.zip
The device will reboot automatically in recovery and apply the updates. Only TWRP can install magisk, gapps or the decryption zip.
Fix crash of the Settings app while configuring fingerprint or PIN lock (during the first setup, or from the Settings page)
Add possibility to enable location indicator in the Development Options
Location indicator is disabled for the Phone Services
[03/05/2022] aosp12_cheeseburger/dumpling-ota-user-20220503.zip
May 2022 Security patches (synced with AOSP android-12.1.0_r5)
Fix issue with Led Manager (SettingsExtra)
[04/04/2022] aosp12_cheeseburger/dumpling-ota-user-20220404.zip
April 2022 Security patches (synced with AOSP android-12.1.0_r4)
Fix slow unlock when fingerprint is used
[13/03/2022] aosp12_dumpling-ota-user-20220313.zip
Fix Settings app crash when opening fingerprint settings
[08/03/2022] aosp12_cheeseburger/dumpling-ota-user-20220308.zip
Android 12L
March 2022 Security patches (synced with AOSP android-12.1.0_r1)
Fix time and date not persisted after a reboot/factory reset
Fix vibration level setting on SettingsExtra
[01/03/2022] aosp12_cheeseburger/dumpling-ota-user-20220301.zip
Sync with Lineage 19 source
Fix issue with sim2 (data works also on sim2 now)
Fix Pocket Mode
Fix 'issue' that was causing some apps to detect root without Magisk
[08/02/2022] aosp12_cheeseburger/dumpling-ota-user-20220208.zip
February 2022 Security patches (synced with AOSP android-12.0.0_r29)
Fix Jio issues with VoLTE calls
[04/01/2022] aosp12_cheeseburger/dumpling-ota-user-20220104.zip
January 2022 Security patches (synced with AOSP android-12.0.0_r26)
Fix alarms not working with default Clock app
[07/12/2021] aosp12_cheeseburger/dumpling-ota-user-20211207-beta.zip
December Security patches (synced with AOSP android-12.0.0_r16)
[02/11/2021] aosp12_cheeseburger/dumpling-ota-user-20211102-beta.zip
November Security patches (synced with AOSP android-12.0.0_r13)
Add separate wifi and cellular data quick settings tiles (as Android 11)
Unified Android 12 tile is still present
[25/10/2021] aosp12_cheeseburger/dumpling-ota-user-20211025-beta.zip
Add f2fs support on /data partition
[20/10/2021] aosp12_cheeseburger/dumpling-ota-user-20211020-experimental.zip
Add support for OnePlus 5T (Dumpling)
Fix data on SIM1 (SIM2 is not working for data in this release)
Enable switch for default mobile data between SIM1 and SIM2 directly in the Android Settings (removed tile: less code to mantain)
Grant permissions to Play Store (and some Google apps) automatically - allow to setup the device and restore a backup at first boot
Fix TWRP not booting after flashing Android 12
Now recovery is not updated/overwritten anymore (no need for the persist_twrp mod or anything - installed recovery is persisted)
Vibration and alarm icons are back in the status bar
[09/10/2021] aosp12_cheeseburger-ota-user-20211009.zip
Fix encryption - Now File Based Encryption is enabled by default
Fix SIM1 sometimes not being recognized at boot
Fix an issue that caused Android to being stuck at boot sometimes (e.g. after flashing it the first time)
Add 'SIM Data Switch' tile to allow switching the default SIM used for mobile data
[06/10/2021] aosp12_cheeseburger-ota-user-20211006-alpha.zip
First release: October 2021 Security Patch (synced with AOSP android-12.0.0_2)
Only known issue is encryption not working
Booting with locked bootloader
This ROM can be booted with locked bootloader.
Not supported at the moment.
For more info, refer to the A11 thread (the information are the same):
[ROM][11.0][OnePlus 5] AOSP for OnePlus 5 [06 OCTOBER 2021][Locked bootloader]
New build in the first post: aosp_cheeseburger-ota-user-20201205.zip Changelog: Add option to enable Call Recording - available in the Settings Extra app Add battery level on the bluetooth icon on status bar (when a bluetooth device reports a...
forum.xda-developers.com
Reserved3
Gapps android 12 here
Added to the OnePlus 5 Index Thread here.
Sources are now available here: https://github.com/roberto-sartori-gl/local_manifests/tree/a12/gl
New release: aosp12_cheeseburger-ota-user-20211009.zip
Changelog:
Fix encryption - Now File Based Encryption is enabled by default
Fix SIM1 sometimes not being recognized at boot
Fix an issue that caused Android to being stuck at boot sometimes (e.g. after flashing it the first time)
Add 'SIM Data Switch' tile to allow switching the default SIM used for mobile data
So, this release fixes encryption: I only plan to support builds with encryption enabled, so if you flashed the first A12 release (without encryption), you'll need to format /data or disable encryption somehow (I don't provide support for this, sorry, but there should be some flashable zips).
This is the last time that formatting /data will be require, I promise!
This also means that if you have my A11 ROM (linked in the first post) you can actually update to A12 without losing any data (app included). But this is still a beta release, so at your risk!
Roms works fine for the most part. I'm not sure if i'm even supposed to test different browsers but chrome and kiwi browser end up crashing when downloading heavy files (> 100Mb)
work on device decrypted and twrp?
hello, there's some problem with the rom and the phone. i accidentaly rebooted in recovery and it stays stuck on logo screen and wont go over, also force rebooting it will always go into twrp and wont boot anyway. tried also to update to lastest recovery verison, but result it'S also the same. any solution or fix for this? p.s.: at the first flash, the rom booted fine.
kitamurt said:
hello, there's some problem with the rom and the phone. i accidentaly rebooted in recovery and it stays stuck on logo screen and wont go over, also force rebooting it will always go into twrp and wont boot anyway. tried also to update to lastest recovery verison, but result it'S also the same. any solution or fix for this? p.s.: at the first flash, the rom booted fine.
Click to expand...
Click to collapse
What logo? Android animation, oneplus logo, or Android recovery logo?
morfances said:
work on device decrypted and twrp?
Click to expand...
Click to collapse
The ROM only supports encrypted /data, but there should be some zip on XDA to manage decryption (I never tested that though).
robertogl said:
What logo? Android animation, oneplus logo, or Android recovery logo?
The ROM only supports encrypted /data, but there should be some zip on XDA to manage decryption (I never tested that though).
Click to expand...
Click to collapse
it stays stuck on twrp logo, but i can go to fastboot mode also and reboot, but the system wont boot anyway. it will only boot automatically into twrp, but i cant make anything since it stays stuck on twrp logo. i followed the steps above, bootlaoder already unlocked, formatted data, then flashed rom and gapps, eventually rebooted.
kitamurt said:
it stays stuck on twrp logo, but i can go to fastboot mode also and reboot, but the system wont boot anyway. it will only boot automatically into twrp, but i cant make anything since it stays stuck on twrp logo. i followed the steps above, bootlaoder already unlocked, formatted data, then flashed rom and gapps, eventually rebooted.
Click to expand...
Click to collapse
What TWRP are you using? TWRP should boot as it should not depend on the OS.
robertogl said:
What TWRP are you using? TWRP should boot as it should not depend on the OS.
Click to expand...
Click to collapse
i'm using the official twrp downloaded from the website, version 3.5.2. what doesn't add up is the reason why the recovery boots and stays stuck on the logo. so it's really weird. i also tried to boot the twrp from adb, giving the command "fastboot boot twrp.img", but the result it's the same.
kitamurt said:
i'm using the official twrp downloaded from the website, version 3.5.2. what doesn't add up is the reason why the recovery boots and stays stuck on the logo. so it's really weird. i also tried to boot the twrp from adb, giving the command "fastboot boot twrp.img", but the result it's the same.
Click to expand...
Click to collapse
Try booting this: https://androidfilehost.com/?fid=10763459528675599801
robertogl said:
Try booting this: https://androidfilehost.com/?fid=10763459528675599801
Click to expand...
Click to collapse
that worked, thx. but seems that the "signed twrp" can't recognize encrypted data, indeed when asking for pattern/pin, even entering it correctly, will say that isn't recognized and therefore data is not recognized. so normal twrp can't be used for flash this kind of rom and gapps?
kitamurt said:
that worked, thx. but seems that the "signed twrp" can't recognize encrypted data, indeed when asking for pattern/pin, even entering it correctly, will say that isn't recognized and therefore data is not recognized. so normal twrp can't be used for flash this kind of rom and gapps?
Click to expand...
Click to collapse
For sure current TWRP cannot decrypt data as they need to be updated to support A12.
But at least you can flash/format things now.
I'm not sure why your TWRP didn't work, the signature should not be important (I shared that because it was already uploaded).
well, thanks for the advice! that said, the bugs i've encountered so far are:
-wifi very buggy, it disconnects after a while and the signal it's very poor, after it's disconnected it can't reconnect to any network. this is solved by rebooting the device
-random crash of systemui, especially when pressing the settings button
-twrp 3.5.2 not booting after flash the rom, only the signed_twrp will work (but not decrypt data) and allow to flash other things
kitamurt said:
well, thanks for the advice! that said, the bugs i've encountered so far are:
-wifi very buggy, it disconnects after a while and the signal it's very poor, after it's disconnected it can't reconnect to any network. this is solved by rebooting the device
-random crash of systemui, especially when pressing the settings button
-twrp 3.5.2 not booting after flash the rom, only the signed_twrp will work (but not decrypt data) and allow to flash other things
Click to expand...
Click to collapse
- The networking is a bit broken apparently, I already had different report of this. We are working on fixing this.
- This happens when you open the settings button from the Quick Settings view, right? It is broken also on A11, it should work only if you have a PIN/fingerprint configured (for some reason).
- TWRP will need to be updated to support A12 encrypted, yes
Of course, thanks for reporting these issues! Always appreciated, as I cannot test everything by myself

Categories

Resources