[GUIDE][TREBLE] How to erase ghost fingerprints - Huawei P9 Questions & Answers

Surely, some Huawei P9 owners are flashaholics like me. I've rebranded, danced left and right with OTAs in order to install EMUI 8.0 and the B540 firmware, juggled recoveries up and down and played with numerous Treble ROMs. If you're like me, you have soft bricked your device numerous times, or you did factory resets from AOSP without erasing the fingerprints first. The issue is, when you forget to wipe your fingerprints and factory reset, they are gone from AOSP ROMs, but not from the sensor hardware, which leads to the issue of ghost fingerprints.
What are ghost fingerprints? Fingerprints that occupy a space in the fingerprint sensor's memory without being registered as existing in pure Android. This causes issues at the moment of registering a new fingerprint since the sensor won't register an already occupied fingerprint which leads to the enrollment not being completed on that fingerprint, reducing the available number of registerable fingerprints and being a security issue as the ghost fingerprints are recognized by an active sensor as valid even if they are not the fingerprint registered in Android.
But there is a (painful) solution, fortunately. Your fingerprint sensor is not crippled for life. This guide involves flashing several times so be careful when following it and investigate every step. I am not responsible for soft or hard (OOF, my wallet hurts) bricked devices. Also this guide is intended for rebranded P9s running a Project Treble compatible firmware stack.
I DO NOT support people running EMUI 5.0 B3xx pre-Treble firmwares or older on their phones. You need a modern B5xx firmware with the new bootloader and partition layout of EMUI 8.0 to follow this guide.
NOTE: This tutorial involves formatting the internal storage. There WILL be data loss.
First, you need the following:
* The update.zip file of the EXACT SAME EMUI firmware image that you are using
* A computer with ADB drivers and an ADB and Fastboot stack.
* Any keyboard APK (I'll explain later)
* The Huawei Update Extractor
* The ROM image of your AOSP Treble OS.
* A Huawei P9 with an unlocked bootloader, an EMUI 8 firmware installed, and/or running any AOSP Treble ROM.
PART 1: Preparations
1. Open your firmware's update.zip in any ZIP file manager.
2. Extract the 'update.app' file to the location of your ADB and Fastboot stack.
3. Open the Huawei Update Extractor in your computer.
4. Disable the signature verification checks.
5. Right click and extract the following images: SYSTEM.img, and if you use a custom kernel, KERNEL.img. After that you can close HUE.
4. Enable developer options, and turn on USB debugging.
PART 2: Going back to EMUI
1. If you have Magisk, uninstall Magisk and everything that depends on Magisk.
2. Open a command prompt or terminal, depending on your computer's OS.
3. Connect your device to USB, and confirm that it can interface with ADB using 'adb devices'.
4. 'adb reboot bootloader': This will reset our device into Fastboot mode.
5. Confirm that communication with Fastboot is possible by using 'fastboot devices'.
6. If you were using a custom kernel, do...
'fastboot flash kernel KERNEL.img'
This will reflash the original kernel image that came with your firmware update.
7. Verify that your device has at least 20% battery, just to make sure that it will work if your battery is old or faulty.
8. The actual procedure.
'fastboot flash system SYSTEM.img'
Have patience. We're flashing the stock ROM through Fastboot now.
9. 'fastboot reboot'
Self explanatory. You can disconnect your phone now.
10. Keep Volume Up to boot to your recovery image, whatever are you using.
11. Do a factory reset, then reboot. This is required to switch between AOSP and EMUI ROMS, and recommended when switching any ROMs in general.
PART 3: Making the ROM usable
1. Skip through the first time wizard.
2. Enable developer options.
3. Go to developer options, enable USB debugging.
4. Connect your device, enable file transfer.
5. Accept the RSA key of your computer, and do 'adb devices' to make sure you can communicate with ADB.
6. 'adb install keyboard.apk'
This will install a virtual keyboard, as our barebones EMUI 8 lacks one. This ROM is not usable in this state, so don't keep it.
PART 4: Killing the ghosts and leaving the battlefield
1. Configure your lock screen, put a short PIN, then go to the fingerprint settings. Your ghost fingerprints will be there, exposed to the light thanks to EMUI's dark magic.
2. Delete each fingerprint. You cannot leave any fingerprint.
3. 'adb reboot bootloader'
4. 'fastboot flash system my-aosp-treble-rom.img'
Be patient. We're returning to AOSP once more.
5. 'fastboot reboot'
6. Boot into recovery
7. Do a factory reset.
8. Disconnect your phone and reboot to system for the last time.
Your ghost fingerprints are gone. Now you can enjoy your clean fingerprint sensor once more.
And remember, make sure to flash responsibly the next time!
If I helped you, please hit thanks and comment

Related

MiX Pack for the simple user (TWRP AdAway SuperSU)

Hi all,
Here you may find a zip containing some very basic resources which can be found elsewhere without too much effort however I figured I would make things that slightest bit easier for some who use any of the MIUI 9+ builds.
The following zip file includes the latest custom SuperSU for MIUI Oreo, the latest release of TWRP, the latest release of AdAway.apk and for the hell of it, the stock MIX boot animation if you wish to use it on any other ROM. 20/5/18
https://www.dropbox.com/s/29u1z721blc1mdy/MIX Package.zip?dl=0
You can find guides elsewhere which go much more in-depth but I'll make a quick one for those who have unlocked bootloaders and are wanting to use any of the builds located on the official MIUI site: http://en.miui.com/download-334.html
The following are the steps I take for my usual installation;
1. Download chosen Official Developer or Stable ROM from the site above in FASTBOOT version. (Click "flashing guide", then "fastboot update" on the left menu where you will find all Xiaomi models, select either "latest global stable" or "latest global developer")
2. Extract ROM folder from download (example: chiron_global_images_8.4.19_20180419.0000.00_8.0_global) to C drive root.
3. Make sure fastboot drivers are installed and device can be seen by PC then download: https://xiaomiflashtool.com/
4. Connect your phone, load up the tool and click "select" on the top left. Here you will locate the ROM folder on C drive.
5. Click "refresh", if your phone is discovered then click "CLEAN ALL" at the bottom to prevent re-locking your bootloader followed by "flash" on the top right hand side which will initiate a full wipe of your phone followed by the installation of your ROM.
When complete allow phone to boot completely and then power it off. Continue below for root instructions.
6. Extract contents of MIX Package to your desktop and open CMD: Hold shift and right click your desktop, click "open powershell window here". Once powershell is loaded, type "cmd" and hit enter. When ready for step 7, boot your phone to fastboot mode.
7. You can either install TWRP or single-boot to it which will allow you to use it one time before reverting to stock recovery upon next reboot. For install, type "fastboot flash recovery recovery.img" and hit enter, then type "fastboot boot recovery.img" to boot to recovery. For single-boot TWRP type "fastboot boot recovery.img" which will boot into the img and allow any desired flashing without installing TWRP to your phone.
8. You are now in TWRP and should have storage access to your phone via your PC, copy SuperSU (and AdAway if desired) to your phone storage.
9. Hit "Install" in TWRP and select SuperSU zip file then flash. Once complete you may now boot your phone and progress through the first time setup.
10. Congratulations, you now have a completely fresh, clean rooted version of your desired MIUI. If you wish to enable full-system ad blocking, proceed to your file manager and install the AdAway.apk then follow instructions in-app.
As mentioned, this is not particularly a replacement for any other guide already published for the Mi Mix 2, it is the guide which I follow for all of my installations which gives me the cleanest possible MIUI. If you are using a stable release ROM and need to pass safety net then I suggest you use substitute SuperSU for Magisk however all the developer ROMs are unable to pass safety net anyway and I much prefer using SuperSU as it has never failed me and has the ability to hide the icon completely from launcher.
Kaji.
Link doesnt work
masterismos said:
Link doesnt work
Click to expand...
Click to collapse
Will upload dropbox version.
Edit: Done.
Nice guide. Quite simple enough. Thank you for this
namasteji1 said:
Nice guide. Quite simple enough. Thank you for this
Click to expand...
Click to collapse
Thanks man, first ever guide...I thought I'd give it a go.
New stable release V9.5.8.0 available now everyone! Download here today: http://en.miui.com/download-334.html
Changelog:
System
· Fix - Errors occurred when the device connected to a saved Wi-Fi hotspot (05-10)
· Fix - Device rebooted automatically in some cases (05-10)
· Fix - Caller ID errors (05-10)
· Fix - Notification settings weren't applied for dual apps (05-10)
· Fix - Search bar in the Notification shade didn't respond (05-10)
· Fix - The problem of abnormal charging needs to be restarted once it is upgraded to the corresponding version. (05-11)
Mi Drop
· Fix - Couldn't open Mi Drop in some cases (05-10)

[RECOVERY][TB-X505F][UNOFFICIAL] TWRP 3.6.x for Lenovo Tab M10 HD

This version of TWRP works on the Lenovo TB-X505F (wifi).
For the TB-X505X, see this thread. For the TB-X605F/L, see this thread.
For the TB-X606F/L, see this thread. The X606F/L is the second gen M10 and it uses a Mediatek SOC.
Code:
#include <std_disclaimer.h>
/*
* We are 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 us for messing up your device, we will laugh at you.
*/
Working:
AFAIK, everything is working including:
data decryption
MTP
Known issues:
time not adjusting for Daylight Saving
OTA (for a workaround see this post)
Before installing TWRP
Before you install TWRP, upgrade your tablet to the Android 9 (Pie) or Android 10 (Q) stock ROM.
This tablet shipped with Android 8 (Oreo), in which the bootloader did not allow unlocking. When you tried to unlock the bootloader, it gave this error message:
Code:
fastboot oem unlock-go
FAILED (remote: 'unknown command')
fastboot: error: Command failed
Installation
It is recommended that you also install Magisk. This will ensure TWRP remains your default recovery.
Step-by-step guide
download TWRP to your PC (see the Download section below)
download magisk.apk to your MicroSD or OTG device. Get the latest Magisk apk file here. Rename the filetype from apk to zip (for example Magisk-v22.0.zip)
if your bootloader is already unlocked, go to step 4. To unlock bootloader:
on tablet: go to Settings->System->About and press "Build number" 7 times to enable Developer Options.
on tablet: go to Settings->System->DeveloperOptions. Turn on: "OEM unlocking" and "USB debugging".
connect tablet to your computer. Tablet will ask for permission to "Allow USB debugging". Tick "always allow" and select "OK".
backup any files you want to keep to an external device (MicroSD/OTG/computer), because the next step will wipe all your photos, files, google account etc on the tablet.
Now unlock the bootloader:
Code:
adb reboot bootloader
fastboot oem unlock-go
fastboot reboot
flash the twrp image:
Code:
adb reboot bootloader
fastboot flash recovery twrp.img
if you haven't loaded Magisk yet, go to step 6. If you have already loaded Magisk, you can just reboot and you're finished:
Code:
fastboot reboot
adb reboot recovery
load Magisk (step one): reboot to recovery. Do not reboot into the system, because it will over-write TWRP with stock recovery. If that happens, go back to step 4 and start again. When you issue the reboot command (below), you have to immediately press the button combination to reboot to recovery (TWRP). Here are the steps:
issue the reboot command:
Code:
fastboot reboot
immediately press and hold all three buttons (Pwr+VolUp+VolDown). The tablet might reboot twice. Release all the buttons when you see the TWRP screen, or hear your PC acknowledge that ADB is connected.
load Magisk (step two): flash Magisk. In TWRP:
select "Install"
use "select storage" to locate device you stored magisk.zip on.
press the OK button
select the Magisk zip file
swipe to confirm Flash
when Magisk is finished, hit the "Reboot System" button
finished!
If you prefer to use button combos, rather than fastboot/ADB commands:
Vol Down + Power = fastboot mode
Vol Up + Vol Down + Power = recovery mode
Changelog
Code:
01/03/2023 - bug fix: data partition again backs up and restores correctly
20/01/2023 - add TW_EXTRA_LANGUAGES and TB_X505F_S001149_221115_ROW kernel (credit to @Tonyha7 )
30/12/2022 - add system partition to AdvancedWipe (TB_X505F_S001147_220830_ROW firmware only)
15/11/2022 - TWRP 3.7.0-0 update
- support for TB_X505F_S001147_220830_ROW
18/12/2021 - TWRP 3.6.0-0 update
- support for A12 decryption (keymaster)
27/03/2021 - TWRP 3.5.1-0 update
- change to landscape mode for tablets
01/01/2021 - TWRP 3.5.0-0: initial release
Downloads
TWRP 3.7.0-0 for X505F: twrp-X505F_11.img (for TB_X505F_S001147_220830_ROW and above)
TWRP 3.6.0-0 for X505F: twrp-X505F_11_2021.img (for earlier stock ROMs)
Source code
https://github.com/minimal-manifest-twrp/platform_manifest_twrp_aosp/tree/twrp-11
https://github.com/Yahoo-Mike/recovery_device_lenovo_X505F/tree/android-11.0
Credits
The guys at TeamWin Recovery Project.
Everyone whose device trees I plagiarised from GitHub.
Contributors
Yahoo Mike
Tonyha7
Last Updated 2023-03-01 (fix /data backup/restore)
Created 2021-01-01
reserved
Thanks for useful post,
Possible to reboot into recovery from fastboot?
zubair1836 said:
Thanks for useful post,
Possible to reboot into recovery from fastboot?
Click to expand...
Click to collapse
Not that I know of. The bootloader accepts the command fastboot reboot recovery, but boots to system anyway.
Hello there, I've been looking how to install this on my slow tablet for almost like an hour. Could there be some tutorial or extended explanation to the process and installation, I'm such a noob, sorry.
This worked for me. Thank you for your effort and the TWRP!
Worked for me too - many thanks!
Can't wait for a custom ROM!
TWRP Recovery Installation Steps
1. Download android platform tools
2. Unlock developer mode on the M10
3. Enable USB debugging on the M10
3. OEM unlock enable on the M10
4. XDA download TWRP copy to sd
5. Download Magisk app (from Github!!! johnwu), change extension to .zip
6. Adb to fastboot
7. fastboot flash recovery [filename.img]
8. Turn off device
9. Turn on device holding all 3 buttons, release when see Lenovo splash screen
10. In TWRP find Magisk zip
11. Install Magisk
Stock ROM Recovery
1. Download qualcomm drivers 64 bit install
2. Download Lenovo recovery and image tool windows app from Lenovo support website
3. Fastboot oem edl
4. Turn off M10
5. Start recovery windows app, wait till instructions
6. Hold volume up (up is the side of the button closest to the front camera) and insert cable
7. Release button after windows app detects device
8. Troubleshoot by checking windows device manager for the M10 appears as a Qualcomm device
I'm thinking about getting one of these tablets, but before I do so I'd like to know that the screen lock still works after installing TWRP.
This might sound like a crazy question, but my Samsung Tab A won't set a screen lock - pattern, PIN or password - once TWRP has been installed, and I'd rather not run into the same issue again.
Heeni said:
I'm thinking about getting one of these tablets, but before I do so I'd like to know that the screen lock still works after installing TWRP.
This might sound like a crazy question, but my Samsung Tab A won't set a screen lock - pattern, PIN or password - once TWRP has been installed, and I'd rather not run into the same issue again.
Click to expand...
Click to collapse
Confirmed working normally.
zubair1836 said:
Confirmed working normally.
Click to expand...
Click to collapse
Many thanks.
Thank you! TWRP is working fine!
Stupid me flashed before I installed the Android 10 OTA, so I had to temporarily go back to stock recovery. Unfortunately beamingbadger's method didn't work for me.
This is how it worked for me:
Download the OTA via Lenovo's "Rescue And Smart Assistant"
The stock recovery image will be in the Download folder (default path: C:\ProgramData\LMSA\Download\RomFiles) called "recovery.img"
Flash the recovery.img the same way as you would with the twrp img (adb reboot bootloader -> fastboot flash recovery recovery.img)
fastboot reboot
Install OTA
Flash TWRP recovery + Magisk again (follow the steps from the first post, skip bootloader unlock)
The method I use to install OTAs is:
open Magisk App
select "Uninstall Magisk", then the "Restore Images" option
reboot to Android (you will have no root access and stock recovery is restored)
apply OTA
re-flash twrp and install Magisk
NOTE 1: if you've unencrypted your data partition, it will be re-encrypted by this process.
NOTE 2: the new Magisk App (v22) can be installed in TWRP by renaming the *.apk to *.zip. See the new install instructions.
What's involved with running gsi ROMs on this device? It's got the same SoC as my Samsung Tab, which runs them well, so I'm assuming that this tab will also, but I'd like to know if there are any traps that I need to be aware of.
I can partly answer my own question. It all went more smoothly than I expected: installing TWRP, Magisk and then LineageOS R Mod //LiR, followed by Disable_Dm-Verity_enfec.zip.
If I want to try other GSI ROMs, do I need to flash stock before trying another one? I've had some trouble doing that (won't boot) and it's possibly to do with encryption.
Heeni said:
I can partly answer my own question. It all went more smoothly than I expected: installing TWRP, Magisk and then LineageOS R Mod //LiR, followed by Disable_Dm-Verity_enfec.zip.
Click to expand...
Click to collapse
That's great news. Well done.
Heeni said:
If I want to try other GSI ROMs, do I need to flash stock before trying another one? I've had some trouble doing that (won't boot) and it's possibly to do with encryption.
Click to expand...
Click to collapse
On my X605F I do this in twrp for a new GSI install:
format (not wipe) data partition. This is the option where you have to confirm by swiping.
factory reset. This clears the caches.
restore the stock boot and vendor partitions (from a backup I made). This is because Magisk can touch these partitions.
install the GSI system image
install anything else I need like disable_Dm-Verity, Magisk, gapps etc
I don't know what LOS R Mod //LiR does to your system. If it touches any other partitions, you should restore those to stock too.
Thanks for that. It gives me something to go on with. I've downloaded the stock ROM from lolinet, so I can grab the boot and vendor images from that.
I was able to try a couple of other GSI ROMs and I've settled on AndyYan's LineageOS 17.1 for now. The only serious installation issue I had - which I can laugh about in hindsight - was thinking I'd got myself into a very bad bootloop, when all I needed to do was let go of the power button after the Lenovo logo appeared.
On this tablet, there is no navigation capability at all (no navbar, no gestures, no setting to configure them) on installation, and I have to set it using adb. I suspect it goes back to PHH basic ROMs, but I don't feel like doing yet another install and testing right at this moment. Is this happening on the other tablets that you're testing, or is it unique to this one?
I just posted the v3.5.1 update to twrp.
It's also changed to landscape mode, as many of you requested.
Quick question, how do i apply new system updates with twrp installed? Should i not bother? Also, i forgot how to block check for updates!
will this allow flashing of stock roms download from lenovo recovery? ive been stuck on an ancient android 9 version because the ota updater fails.

[Android 12] [EXPERIMENTAL] [RE-UPLOADED] AOSP Android 12 for A21s

WARNING + DISCLAIMER:
By installing this custom ROM, you are VOIDING your warranty. Also, installation of this ROM WILL TRIP KNOX PERMANENTLY, and render apps such as Samsung Health, Private Folder, (+ any apps that depend on KNOX) useless until you get the phone's motherboard replaced at the Samsung C/S center.
Although this software is released in the hope that it will be useful, there is NO GUARANTEE that installing this will not cause any harm to your device. I TAKE NO RESPONSIBILITY FOR ANY BRICKED DEVICES, DAMAGED HARDWARE, OR ANY OTHER PROBLEMS CAUSED BY THIS ROM. You are using this ROM at YOUR OWN RISK. I strongly recommend that you DO NOT continue to the steps below UNLESS YOU FULLY UNDERSTAND WHAT YOU ARE DOING.
While this ROM has been tested with South Korean variant of Galaxy A21s (SM-A217N, CSC changed from LUC->SKC), please keep in mind that it hasn't been tested on any other variant (such as A217F, A217M.)
Click to expand...
Click to collapse
I would like to express special thanks to all the developers who contributed to the LineageOS port for Galaxy Tab S6 Lite + all the other developers who contributed to sepolicy & hardware parts for Samsung SLSI (Exynos) devices. Porting LineageOS to A21s would have been much harder without them.
Click to expand...
Click to collapse
This is Android 12 ROM built from Google's AOSP sources released on October 4, 2021. The sources are based on the Lineage OS for A21s, with some modifications for Android 12.
NOT WORKING:
Samsung Proprietary Apps (Samsung Health, etc.)
VoLTE & VoWifi (Due to Samsung's twisted & wicked IMS service)
Auto Brightness (The phone doesn't have the sensors for it anyway)
ExFAT-formatted SD Card & OTG (there are legal problems associated with it.)
Working but buggy or not tested:
Audio volume is smaller than usual (WIP)
RIL starting up late on very rare occasions. If telephony doesn't work after reboot, please allow up to a minute.
Cell broadcast (emergency messages) is working in South Korea, but not tested in other countries
Working, but needs installation of additional apps:
NFC, Screen Sharing, Wi-FI Direct works, but needs installation of additional apps to work
Browser app is not installed by default. Installing Firefox or Chrome from Google Play is recommended
GPS & Location services don't work when GApps are not installed.
This ROM is not compatible with TWRP due to File-based encryption.
The ROM is NOT ROOTED by default. In order to root it, install Magisk from official source.
WORKING:
Everything else not mentioned above
p.s. ADVANTAGES WHEN COMPARED TO GSI Android 12:
Based on official release, whereas GSI is based on Beta 5
Working MTP
Working NFC
Working Cell Broadcast
Fixed Fingerprint removal bug
Camera works up to 48MP (GSI camera is fixed @ 12MP)
Double-tap-to-wake is working
Model number correctly matches with the actual device (shows SM-A217N instead of AOSP on ARM64)
Updated kernel graphics driver to the latest from ARM
1. BEFORE INSTALLING, make sure that you have UNLOCKED the bootloader of your device. This is a great guide that show how to do it. Also, the phone must be on the Stock ANDROID 11. If you are on binary U6/U7, please use the recovery tar for U6/U7.
2. Download the Lineage Recovery, ROM, Google Apps, ADB, and Odin. Unzip ADB and Odin to somewhere appropriate. Save the ROM images to the folder where you unzip ADB/Fastboot
- ROM: super.img. boot.img, dtbo.img, recovery(U5), recovery(U6), recovery(U7)
- ADB and Fastboot
- Odin
- Kernel Source
- Google Apps(Flame)
WARNING: A BUG WHICH CAN POTENTIALLY LEAD TO BOOT LOOP ON U7 WAS FOUND. IF YOU ARE ON U7, PLEASE DO NOT FLASH THIS ROM UNTIL THIS IS FIXED.
3. Enable USB Debugging on the device. Go to settings->About phone->Software information, and tap the build number several times until you see the notification that the devloper settings have been enabled. After enabling developer settings, go to settings->developer settings and check USB debugging.
4. Open Command Prompt, and type "cd <the path where you saved ADB to>".
5. On the phone, start holding down the Volume Up and Down keys. KEEP THE KEYS PRESSED UNTIL THE PHONE REBOOTS AFTER YOU TYPE THE COMMAND IN THE NEXT STEP.
6. While holding the keys down. type in the command "adb reboot recovery" on the command line.
7. After the phone reboots into download mode, press volume up to continue. Make sure that you see the "OEM LOCK: OFF" before continuing.
8. Open Odin. After opening Odin, click on AP, and select the Lineage Recovery Tar file that you downloaded in the step 2. After that, click on Start.
9. After a few seconds, if everything goes well, Odin should show "PASS" and the device should reboot into Lineage Recovery. After the device enters recovery, tap on Advanced->Enter fastboot. In some cases, touchscreen may be unresponsive or slow. If that happens, use Volume Keys to navigate and Power key to select. KEEP THE DEVICE CONNECTED TO THE COMPUTER.
10. After choosing Enter fastboot, type the following lines in the Command Prompt and press enter:
10-1. "fastboot flash boot boot.img" ---> this takes around 5~10 seconds.
10-2. "fastboot flash dtbo dtbo.img" ---> this takes around 5~10 seconds.
10-3. "fastboot flash super super.img" ---> this takes several minutes.
11. After the steps above are complete, choose Enter recovery. After the phone enters recovery, choose Apply update->Apply from ADB
12. After choosing Apply from ADB, type "adb sideload <the path where you saved Google apps to>" on the Command Prompt and press enter.
13. After about 1-2 minutes, installation should be complete. Again, ADB might show "Failed to read command" errors. As long as the phone says that it was success, this is no problem. After installing, click on the "back" icon on the top of the phone.
14. Choose Factory reset->Format data/factory reset, and reboot the device.
15. If everything went well, the phone should reboot into Android 12 AOSP. Set up the device and Enjoy!
Changelogs:
2021-10-19: Initial Release (AOSP 12.0.0_r2)
2021-10-21: Updated to AOSP 12.0.0_r3
2021-11-03: Updated to AOSP 12.0.0_r13 & added U7 support
2021-11-22: Fixed graphics issue, fixed battery issue (when battery level sometimes dropped by more than 2-3% on reboot), and fixed force crash when choosing Battery Manager in Settings
2021-11-25: Updated to AOSP 12.0.0_r15, changed battery mechanism to make it more accurate
2021-11-27: Kernel GPU driver update (R33P0 -> R34P0), LTE is now enabled by default
2021-12-10: Updated to AOSP 12.0.0_r16, removed the annoying search box widget on the home screen
2022-01-01: EGL graphics driver update to improve performance, minor bug fixes related to some apps.
SCREENSHOTS:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
EDIT: the boot issue has been fixed, and you can now download the ROM.
This is great!
Do you working on this ROM for A21s, or you working on LineageOS 18 A11, paralel with this ROM?
grccorps said:
EDIT: the boot issue has been fixed, and you can now download the ROM.
Click to expand...
Click to collapse
instead of fastboot can we sideload super,boot etc?
Zdivan said:
This is great!
Do you working on this ROM for A21s, or you working on LineageOS 18 A11, paralel with this ROM?
Click to expand...
Click to collapse
Yes. I am also working on Lineage 18. Actually, the source code for this ROM is based on the source code for the Lineage 18. (of course, along with some modifications)
NuzzaimStark said:
instead of fastboot can we sideload super,boot etc?
Click to expand...
Click to collapse
I'm really sorry, but it is not possible to adb sideload images.
i got this when type and enter "fastboot flash boot boot.img"
C:\Users\nussa\Downloads\platform-tools>fastboot flash boot boot.img
< waiting for any device >
nothing showing in phone log
grccorps said:
I'm really sorry, but it is not possible to adb sideload images.
Click to expand...
Click to collapse
I am a bit sad because gaming time screen is flickering... Grrcorps pls check in your phone
grccorps said:
This is Android 12 ROM built from Google's AOSP sources released on October 4, 2021. The sources are based on the Lineage OS for A21s, with some modifications for Android 12.
It has been only 2 weeks since Android 12 came out, so there may be some instability / bugs. I will try to work it out as time goes by. Also, when Lineage 19 is released, I will try to port it too. (Shouldn't be too hard though, as Lineage is quite similar to AOSP)
NOT WORKING:
Samsung Proprietary Apps (Samsung Health, etc.)
VoLTE & VoWifi (Due to Samsung's twisted & wicked IMS service)
Auto Brightness (The phone doesn't have the sensors for it anyway)
ExFAT-formatted SD Card & OTG (there are legal problems associated with it.)
Working but buggy or not tested:
Audio volume is smaller than usual (WIP)
RIL starting up late on very rare occasions. If telephony doesn't work after reboot, please allow up to a minute.
Cell broadcast (emergency messages) is working in South Korea, but not tested in other countries
The network is set to 3G by default, so in order to use LTE, you should go to Settings->Network and Internet->Internet and change the default network setting from 3G to LTE.
Working, but needs installation of additional apps:
NFC, Screen Sharing, Wi-FI Direct works, but needs installation of additional apps to work
Browser and Music/Video Player apps are not installed by default. Installing Chrome and YouTube music from Google Pay is recommended
The search bar on the home launcher is useless until "Google" app or "Google Go" app is installed.
GPS & Location services don't work when GApps are not installed.
This ROM is not compatible with TWRP due to File-based encryption.
The ROM is NOT ROOTED by default. In order to root it, install Magisk from official source.
WORKING:
Everything else not mentioned above
p.s. ADVANTAGES WHEN COMPARED TO GSI Android 12:
Based on official release, whereas GSI is based on Beta 5
Working MTP
Working NFC
Working Cell Broadcast
Fixed Fingerprint removal bug
Camera works up to 48MP (GSI camera is fixed @ 12MP)
Double-tap-to-wake is working
Model number correctly matches with the actual device (shows SM-A217N instead of AOSP on ARM64)
Updated kernel graphics driver to the latest from ARM
1. BEFORE INSTALLING, make sure that you have UNLOCKED the bootloader of your device. This is a great guide that show how to do it. Also, the phone must be on the Stock ANDROID 11. If you are on binary U6, please use the recovery tar for U6.
2. Download the Lineage Recovery, ROM, Google Apps, ADB, and Odin. Unzip ADB and Odin to somewhere appropriate. Save the ROM images to the folder where you unzip ADB/Fastboot
- ROM: super.img, boot.img, dtbo.img (Download all three)
- Recovery(for U5) / Recovery(for U6) / Recovery(for U7: coming soon)
- Google Apps
- ADB and Fastboot
- Odin
3. Enable USB Debugging on the device. Go to settings->About phone->Software information, and tap the build number several times until you see the notification that the devloper settings have been enabled. After enabling developer settings, go to settings->developer settings and check USB debugging.
4. Open Command Prompt, and type "cd <the path where you saved ADB to>".
5. On the phone, start holding down the Volume Up and Down keys. KEEP THE KEYS PRESSED UNTIL THE PHONE REBOOTS AFTER YOU TYPE THE COMMAND IN THE NEXT STEP.
6. While holding the keys down. type in the command "adb reboot recovery" on the command line.
7. After the phone reboots into download mode, press volume up to continue. Make sure that you see the "OEM LOCK: OFF" before continuing.
8. Open Odin. After opening Odin, click on AP, and select the Lineage Recovery Tar file that you downloaded in the step 2. After that, click on Start.
9. After a few seconds, if everything goes well, Odin should show "PASS" and the device should reboot into Lineage Recovery. After the device enters recovery, tap on Advanced->Enter fastboot. In some cases, touchscreen may be unresponsive or slow. If that happens, use Volume Keys to navigate and Power key to select. KEEP THE DEVICE CONNECTED TO THE COMPUTER.
10. After choosing Enter fastboot, type the following lines in the Command Prompt and press enter:
10-1. "fastboot flash boot boot.img" ---> this takes around 5~10 seconds.
10-2. "fastboot flash dtbo dtbo.img" ---> this takes around 5~10 seconds.
10-3. "fastboot flash super super.img" ---> this takes several minutes.
11. After the steps above are complete, choose Enter recovery. After the phone enters recovery, choose Apply update->Apply from ADB
12. After choosing Apply from ADB, type "adb sideload <the path where you saved Google apps to>" on the Command Prompt and press enter.
13. After about 1-2 minutes, installation should be complete. Again, ADB might show "Failed to read command" errors. As long as the phone says that it was success, this is no problem. After installing, click on the "back" icon on the top of the phone.
14. Choose Factory reset->Format data/factory reset, and reboot the device.
15. If everything went well, the phone should reboot into Android 12 AOSP. Set up the device and Enjoy!
SCREENSHOTS:
View attachment 5436707View attachment 5436709View attachment 5436711View attachment 5436713View attachment 5436731
Click to expand...
Click to collapse
only 1 sim card is work or 2 sim cards is working ?
( A217F ) , EGY
NuzzaimStark said:
I am a bit sad because gaming time screen is flickering... Grrcorps pls check in your phone
Click to expand...
Click to collapse
I'm really sorry, but could you please tell me which game it is?
ayman9321 said:
only 1 sim card is work or 2 sim cards is working ?
( A217F ) , EGY
Click to expand...
Click to collapse
As of now, this ROM is for single sim variant...
grccorps said:
As of now, this ROM is for single sim variant...
Click to expand...
Click to collapse
how can i fix it or can you help me to make 2 sim cards work ?
i install pit file for my country from the csc.tar from the android 11 firmware but not work after i install the stock android 11 firmware that is says your sim cards is changed restart to apply the changes .
grccorps said:
I'm really sorry, but could you please tell me which game it is?
Click to expand...
Click to collapse
Watch my gameplay I screen recorded it
NuzzaimStark said:
Watch my gameplay I screen recorded it
Click to expand...
Click to collapse
It said EXPERIMENTAL.
This ROM is not good enough for daily driver.
Wait for new version or install Lineage 18, or continue use this rom for testing.
Can anyone guide me how to root this rom?
Is this the s
grccorps said:
This is Android 12 ROM built from Google's AOSP sources released on October 4, 2021. The sources are based on the Lineage OS for A21s, with some modifications for Android 12.
It has been only 2 weeks since Android 12 came out, so there may be some instability / bugs. I will try to work it out as time goes by. Also, when Lineage 19 is released, I will try to port it too. (Shouldn't be too hard though, as Lineage is quite similar to AOSP)
NOT WORKING:
Samsung Proprietary Apps (Samsung Health, etc.)
VoLTE & VoWifi (Due to Samsung's twisted & wicked IMS service)
Auto Brightness (The phone doesn't have the sensors for it anyway)
ExFAT-formatted SD Card & OTG (there are legal problems associated with it.)
Working but buggy or not tested:
Audio volume is smaller than usual (WIP)
RIL starting up late on very rare occasions. If telephony doesn't work after reboot, please allow up to a minute.
Cell broadcast (emergency messages) is working in South Korea, but not tested in other countries
The network is set to 3G by default, so in order to use LTE, you should go to Settings->Network and Internet->Internet and change the default network setting from 3G to LTE.
Working, but needs installation of additional apps:
NFC, Screen Sharing, Wi-FI Direct works, but needs installation of additional apps to work
Browser and Music/Video Player apps are not installed by default. Installing Chrome and YouTube music from Google Pay is recommended
The search bar on the home launcher is useless until "Google" app or "Google Go" app is installed.
GPS & Location services don't work when GApps are not installed.
This ROM is not compatible with TWRP due to File-based encryption.
The ROM is NOT ROOTED by default. In order to root it, install Magisk from official source.
WORKING:
Everything else not mentioned above
p.s. ADVANTAGES WHEN COMPARED TO GSI Android 12:
Based on official release, whereas GSI is based on Beta 5
Working MTP
Working NFC
Working Cell Broadcast
Fixed Fingerprint removal bug
Camera works up to 48MP (GSI camera is fixed @ 12MP)
Double-tap-to-wake is working
Model number correctly matches with the actual device (shows SM-A217N instead of AOSP on ARM64)
Updated kernel graphics driver to the latest from ARM
1. BEFORE INSTALLING, make sure that you have UNLOCKED the bootloader of your device. This is a great guide that show how to do it. Also, the phone must be on the Stock ANDROID 11. If you are on binary U6, please use the recovery tar for U6.
2. Download the Lineage Recovery, ROM, Google Apps, ADB, and Odin. Unzip ADB and Odin to somewhere appropriate. Save the ROM images to the folder where you unzip ADB/Fastboot
- ROM: super.img, boot.img, dtbo.img (Download all three)
- Recovery(for U5) / Recovery(for U6) / Recovery(for U7: coming soon)
- Google Apps
- ADB and Fastboot
- Odin
3. Enable USB Debugging on the device. Go to settings->About phone->Software information, and tap the build number several times until you see the notification that the devloper settings have been enabled. After enabling developer settings, go to settings->developer settings and check USB debugging.
4. Open Command Prompt, and type "cd <the path where you saved ADB to>".
5. On the phone, start holding down the Volume Up and Down keys. KEEP THE KEYS PRESSED UNTIL THE PHONE REBOOTS AFTER YOU TYPE THE COMMAND IN THE NEXT STEP.
6. While holding the keys down. type in the command "adb reboot recovery" on the command line.
7. After the phone reboots into download mode, press volume up to continue. Make sure that you see the "OEM LOCK: OFF" before continuing.
8. Open Odin. After opening Odin, click on AP, and select the Lineage Recovery Tar file that you downloaded in the step 2. After that, click on Start.
9. After a few seconds, if everything goes well, Odin should show "PASS" and the device should reboot into Lineage Recovery. After the device enters recovery, tap on Advanced->Enter fastboot. In some cases, touchscreen may be unresponsive or slow. If that happens, use Volume Keys to navigate and Power key to select. KEEP THE DEVICE CONNECTED TO THE COMPUTER.
10. After choosing Enter fastboot, type the following lines in the Command Prompt and press enter:
10-1. "fastboot flash boot boot.img" ---> this takes around 5~10 seconds.
10-2. "fastboot flash dtbo dtbo.img" ---> this takes around 5~10 seconds.
10-3. "fastboot flash super super.img" ---> this takes several minutes.
11. After the steps above are complete, choose Enter recovery. After the phone enters recovery, choose Apply update->Apply from ADB
12. After choosing Apply from ADB, type "adb sideload <the path where you saved Google apps to>" on the Command Prompt and press enter.
13. After about 1-2 minutes, installation should be complete. Again, ADB might show "Failed to read command" errors. As long as the phone says that it was success, this is no problem. After installing, click on the "back" icon on the top of the phone.
14. Choose Factory reset->Format data/factory reset, and reboot the device.
15. If everything went well, the phone should reboot into Android 12 AOSP. Set up the device and Enjoy!
SCREENSHOTS:
View attachment 5436707View attachment 5436709View attachment 5436711View attachment 5436713View attachment 5436731
Click to expand...
Click to collapse
Is this the stock Samsung Android 12 ROM?
NuzzaimStark said:
Can anyone guide me how to root this rom?
Click to expand...
Click to collapse
Patch the boot.img with magisk, same as how you root any other ROM
Maxis89 said:
Is this the s
Is this the stock Samsung Android 12 ROM?
Click to expand...
Click to collapse
No it is AOSP, it is written in the OP and also the screenshots are quite clearly AOSP
Do you need any logs or bug reports? If so, how to get them? Will the Lineage OS method work?
Add.: Gapps installation error: !Wrong android version detected. This package is for android 10.0 only. Your ROM is Android: 12. Blame, blind.
I tried rooting. There is no option ( root permission for usb debugging ) developer setting.
And I get these
NuzzaimStark said:
I tried rooting. There is no option ( root permission for usb debugging ) developer setting.
And I get these
Click to expand...
Click to collapse
Patch the boot.img with magisk app. Then reboot fastboot and flash the patched.img with fastboot.
This is, and will always be, the recommended way of installing magisk and getting root.

[GUIDE][SM-T290/SM-T290N] Samsung Galaxy Tab A 8.0 (2019) - How to Install LineageOS 18.1 (GSI) + Gapps

Hello!
So recently I was able to install LineageOS 18.1 (GSI) + GApps on my Samsung Galaxy Tab A 8 (SM-T290) tablet and wanted to share how I did it. I noticed a lack of decent step-by-step guides to modding this tablet so I figure I'd share what I learned through scouring multiple threads and through multiple headaches. Fun fact: I also got this working with LineageOS 19 (GSI), however it ran pretty poorly and Android 12 is ugly as hell so why bother anyway? ALSO interestingly enough, you'll see I wrote [SM-T290N] in the title as well. That is the model of the Kid's Edition of this phone, which happens to be the one I had. So I can confirm this process works for the Kid's Edition of this tablet as well as the original.
Some Things To Note
Below I'll list the software/firmware I used in this process. You don't necessarily need to follow this exactly but I don't see any reason not to. The end result is a working install of LineageOS with GApps so if that's what you want I would just follow along step-by-step. ALSO I'm writing this from memory so if I make a mistake please let me know and I'll try and correct it.
Click to expand...
Click to collapse
What You'll Need
Your tablet
A USB Cable to connect your tablet to your PC
A 4GB+ MicroSD card
A Windows PC
Some patience
Instructions
Preparing Your MicroSD Card
1. Place the LineageOS 18.1 .img file from this thread (On SourceForge, there is a section below the files about the naming conventions and how they relate to the hardware of your device and configuration of your ROM. I used the lineage-18.1-20220315-UNOFFICIAL-arm64_bvS-vndklite.img.xz image for my device. If your device is slightly different, you can use Treble Info to determine what ROM you should use. Just make sure to use the VNDKLITE rom if your device supports it.
2. Place the multidisabler .zip folder on there as well. This will preserve encryption provided by TWRP after rebooting.
3. Finally, place the MindTheGapps .zip folder on your SD card (make sure to get the correct version. In my case this was the 11.00-arm64 version).
4. Insert your MicroSD card into your device.
Unlocking the Bootloader
So the first thing you're gonna want to do is unlock your OEM bootloader on your Samsung device.
1. Go to Settings->About Phone->Software Information and look for a field called "Build Number". Tap this Five Times until you see a notification saying developer settings were enabled.
2. Go to Settings->Developer Settings and look for the setting labeled OEM Unlock and turn it on.
If you don't see this setting try connecting to wifi, changing your date and time to around two months prior (I set mine to back to May 2021 since the firmware I was using was set in July 2021), then go back to your developer settings and switch them off and back on again. You should now see the OEM Unlock option.
Click to expand...
Click to collapse
3. From here, you can reboot your device into Recovery Mode by holding the Vol+ and Vol- buttons when the device begins to boot again.
4. You should see a blue screen with some options. Press the Vol+ button to enter Download Mode. This is where you'll use Odin to flash the firmware you need as well as TWRP.
Flashing Firmware
So when I attempted this process I used Magendanz's Unofficial TWRP 3.6.0 as it is the only version of TWRP I found for this device. I also used Odin v3.14.1_3B Patched from this XDA thread. Magendanz's TWRP requires you to have the T290XXU3CUG4 Firmware (I used the XAR region) in order to flash TWRP to your device (you can check wether or not you already have this firmware on your phone by looking the About Phone section again). It takes a while to download though make sure you have some time.
1. Download Odin and run the program. Unzip your firmware folder and use the relevant files when selecting the BL, AP, CP, CSC fields in Odin. I didn't use the HOME_CSC just leave it blank.
2. Connect your device via USB and Flash this firmware to your device.
3. Once your device restarts, go through the setup process and then repeat the Unlocking the Bootloader instructions above in order to make sure it is unlocked again.
4. Reboot your device the same way as stated above.
Flashing TWRP
Before starting, be aware that after you flash TWRP to your device, your device will restart and attempt to open the stock system again. You're going to want to hold the Power and Vol+ buttons simultaneously. You will likely get a warning screen saying that the bootloader is unlocked and may ask you to do a factory reset, this (I believe) is fine. The key here is that once you press the Power Button to continue (as instructed on the warning screen) you'll want to immediately press and hold the Power and Vol+ keys for around 6 Seconds before letting go again (you should be seeing the Samsung Galaxy Tab A logo screen). After letting go, wait around 3-4 seconds, if nothing changes, restart the device by holding all three buttons (Power, Vol+,Vol-) and attempt the process again. It's a pain in the ass but you'll get it eventually. Just make sure not to let the device boot into the system again as that can cause problems in TWRP and you'll likely have to start the process over (from flashing the firmware).
1. Once your tablet is once again in Download Mode, open Odin again and flash the TWRP (tar.md5 file) to the AP (recovery) partition. Do not use any of the other partitions.
2. If this is successful, your phone will begin to reboot. Quickly press and hold the combination of buttons Power and Vol+ until you see the warning dialog pop up. Once you do, release all buttons and be ready to quickly press and release the Power button continue, and then immediately after press and hold the Power and Vol+ buttons again for 6 seconds. After around 6 seconds, release all buttons. Wait around 3-4 seconds and, if the screen does not change to the TWRP logo, restart the device by pressing and holding all buttons simultaneously and try this step again.
3. If you have entered into TWRP, congrats!
Installing Custom ROM + Software in TWRP
1. The first thing you'll want to do is select the Wipe->Format Data. Type 'yes' and hit enter (or swipe I forget which).
2. Next, select Install, and then select your MicroSD card as your storage device. You should see your zip files (if not switch from the install image option).
3. Install the multidisabler, do not reboot
4. Go back into Install and select Install Image (might not be the exact naming) option. Select your MicroSD card as the storage device again and install the LineageOS 18.1 rom. Do not reboot.
5. Go back into Install and select your MindTheGapps zip file and install it.
Now, a lot of people run into a problem when trying to install Gapps which is your device complaining about no more available space in the system partition. If this is the case, go back to Wipe and select Advanced Wipe. Select your system partition and then select Change or Repair Partition. Once you're here you should see the size and available space of your partition. You'll want to hit Resize Partition and let it do it's thing. To confirm it worked, go back to Wipe->Advanced Wipe->Select System->Change or Repair Partition and your available space should be much larger now. Now just attempt to install MindTheGapps again.
Click to expand...
Click to collapse
Final Steps
Once you reboot you should be able to successfully reach the setup screen for Lineage. Go through the steps of setting up your device as usual and be sure that Gapps are installed. Go ahead and re-enable developer settings and enable USB-Debugging and Root Debugging. The reason for this is that, when I first installed Gapps, Google Play Protect would keep throwing warnings at me about my device not being Google Play Certified. This means I couldn't actually use any of the google play services. If you run into the same issue, here are the steps you can take to fix it:
1. First, go into Settings->Apps and find your Google Play Services app. Clear the cache and delete the app data, then reboot your device. If you try and sign into the Google Play store and you are able to without getting any play protect warnings, then you're good you can disregard the following steps.
2. If you are still receiving these warnings, you'll want to head over to this site and follow the instructions (I'm not gonna tell you how to use ADB here). Once you submit your framework ID, reboot your device. Everything should be working fine now.
And that's it! If I am forgetting any steps please let me know, again I am writing this from memory of the process so it may be missing some minor details. I hope this helps!!!
How's the stability, speed and the responsiveness on Lineage with a t290? I have mine rooted debloated and twrp installed but it is slow on stock OS
kkdamion said:
How's the stability, speed and the responsiveness on Lineage with a t290? I have mine rooted debloated and twrp installed but it is slow on stock OS
Click to expand...
Click to collapse
It runs surprisingly well! Much better than stock. There’s virtually no input lag and the battery life is also very solid on lineage.
Where i run into some lag is when trying to use apps that have embedded video in them. For whatever reason the T290 cannot handle video very well at all.
So yeah I would definitely recommend trying it, it’ll really breathe new life into that tablet
i cant get google play services to work and i cant fetch device_id to register the device
i get "no closing qoute" message
adb shell 'sqlite3 /data/data/com.google.android.gsf/databases/gservices.db \
/system/bin/sh: no closing quote
EDIT: downloaded "android device id" APK from the internet and gathered the framework id information from the app
kkdamion said:
i cant get google play services to work and i cant fetch device_id to register the device
i get "no closing qoute" message
adb shell 'sqlite3 /data/data/com.google.android.gsf/databases/gservices.db \
/system/bin/sh: no closing quote
EDIT: downloaded "android device id" APK from the internet and gathered the framework id information from the app
Click to expand...
Click to collapse
Glad it worked out for you! Let me know if you have any more questions and I'd be happy to help.
Hi! is this applicable also for SM-T295?
for those trying to figure out the Google Play Certified page with the adb command
Code:
adb shell 'sqlite3 /data/data/com.google.android.gsf/databases/gservices.db \
"select * from main where name = \"android_id\";"'
do : adb shell
first then paste in :
sqlite3 /data/data/com.google.android.gsf/databases/gservices.db \
"select * from main where name = \"android_id\";"
and it shouldn't give you the error
i must say. linageos on my sm-t290 is really nice
its fast and smooth way much better then stock fw
i would reccomend anyone with a t290/t295 to install this GSI
Im into a bootloop right now after a few fails with installing Lineage on my SM-T290..
Seems like i cant install any rom? not sure how to fix this issue, can anyone point me in the right direction?
Im able to get into TWRP and download mode. but cant install any rom?
thepalek1ng said:
Hello!
So recently I was able to install LineageOS 18.1 (GSI) + GApps on my Samsung Galaxy Tab A 8 (SM-T290) tablet and wanted to share how I did it. I noticed a lack of decent step-by-step guides to modding this tablet so I figure I'd share what I learned through scouring multiple threads and through multiple headaches. Fun fact: I also got this working with LineageOS 19 (GSI), however it ran pretty poorly and Android 12 is ugly as hell so why bother anyway? ALSO interestingly enough, you'll see I wrote [SM-T290N] in the title as well. That is the model of the Kid's Edition of this phone, which happens to be the one I had. So I can confirm this process works for the Kid's Edition of this tablet as well as the original.
What You'll Need
Your tablet
A USB Cable to connect your tablet to your PC
A 4GB+ MicroSD card
A Windows PC
Some patience
Instructions
Preparing Your MicroSD Card
1. Place the LineageOS 18.1 .img file from this thread (On SourceForge, there is a section below the files about the naming conventions and how they relate to the hardware of your device and configuration of your ROM. I used the lineage-18.1-20220315-UNOFFICIAL-arm64_bvS-vndklite.img.xz image for my device. If your device is slightly different, you can use Treble Info to determine what ROM you should use. Just make sure to use the VNDKLITE rom if your device supports it.
2. Place the multidisabler .zip folder on there as well. This will preserve encryption provided by TWRP after rebooting.
3. Finally, place the MindTheGapps .zip folder on your SD card (make sure to get the correct version. In my case this was the 11.00-arm64 version).
4. Insert your MicroSD card into your device.
Unlocking the Bootloader
So the first thing you're gonna want to do is unlock your OEM bootloader on your Samsung device.
1. Go to Settings->About Phone->Software Information and look for a field called "Build Number". Tap this Five Times until you see a notification saying developer settings were enabled.
2. Go to Settings->Developer Settings and look for the setting labeled OEM Unlock and turn it on.
3. From here, you can reboot your device into Recovery Mode by holding the Vol+ and Vol- buttons when the device begins to boot again.
4. You should see a blue screen with some options. Press the Vol+ button to enter Download Mode. This is where you'll use Odin to flash the firmware you need as well as TWRP.
Flashing Firmware
So when I attempted this process I used Magendanz's Unofficial TWRP 3.6.0 as it is the only version of TWRP I found for this device. I also used Odin v3.14.1_3B Patched from this XDA thread. Magendanz's TWRP requires you to have the T290XXU3CUG4 Firmware (I used the XAR region) in order to flash TWRP to your device (you can check wether or not you already have this firmware on your phone by looking the About Phone section again). It takes a while to download though make sure you have some time.
1. Download Odin and run the program. Unzip your firmware folder and use the relevant files when selecting the BL, AP, CP, CSC fields in Odin. I didn't use the HOME_CSC just leave it blank.
2. Connect your device via USB and Flash this firmware to your device.
3. Once your device restarts, go through the setup process and then repeat the Unlocking the Bootloader instructions above in order to make sure it is unlocked again.
4. Reboot your device the same way as stated above.
Flashing TWRP
Before starting, be aware that after you flash TWRP to your device, your device will restart and attempt to open the stock system again. You're going to want to hold the Power and Vol+ buttons simultaneously. You will likely get a warning screen saying that the bootloader is unlocked and may ask you to do a factory reset, this (I believe) is fine. The key here is that once you press the Power Button to continue (as instructed on the warning screen) you'll want to immediately press and hold the Power and Vol+ keys for around 6 Seconds before letting go again (you should be seeing the Samsung Galaxy Tab A logo screen). After letting go, wait around 3-4 seconds, if nothing changes, restart the device by holding all three buttons (Power, Vol+,Vol-) and attempt the process again. It's a pain in the ass but you'll get it eventually. Just make sure not to let the device boot into the system again as that can cause problems in TWRP and you'll likely have to start the process over (from flashing the firmware).
1. Once your tablet is once again in Download Mode, open Odin again and flash the TWRP (tar.md5 file) to the AP (recovery) partition. Do not use any of the other partitions.
2. If this is successful, your phone will begin to reboot. Quickly press and hold the combination of buttons Power and Vol+ until you see the warning dialog pop up. Once you do, release all buttons and be ready to quickly press and release the Power button continue, and then immediately after press and hold the Power and Vol+ buttons again for 6 seconds. After around 6 seconds, release all buttons. Wait around 3-4 seconds and, if the screen does not change to the TWRP logo, restart the device by pressing and holding all buttons simultaneously and try this step again.
3. If you have entered into TWRP, congrats!
Installing Custom ROM + Software in TWRP
1. The first thing you'll want to do is select the Wipe->Format Data. Type 'yes' and hit enter (or swipe I forget which).
2. Next, select Install, and then select your MicroSD card as your storage device. You should see your zip files (if not switch from the install image option).
3. Install the multidisabler, do not reboot
4. Go back into Install and select Install Image (might not be the exact naming) option. Select your MicroSD card as the storage device again and install the LineageOS 18.1 rom. Do not reboot.
5. Go back into Install and select your MindTheGapps zip file and install it.
Final Steps
Once you reboot you should be able to successfully reach the setup screen for Lineage. Go through the steps of setting up your device as usual and be sure that Gapps are installed. Go ahead and re-enable developer settings and enable USB-Debugging and Root Debugging. The reason for this is that, when I first installed Gapps, Google Play Protect would keep throwing warnings at me about my device not being Google Play Certified. This means I couldn't actually use any of the google play services. If you run into the same issue, here are the steps you can take to fix it:
1. First, go into Settings->Apps and find your Google Play Services app. Clear the cache and delete the app data, then reboot your device. If you try and sign into the Google Play store and you are able to without getting any play protect warnings, then you're good you can disregard the following steps.
2. If you are still receiving these warnings, you'll want to head over to this site and follow the instructions (I'm not gonna tell you how to use ADB here). Once you submit your framework ID, reboot your device. Everything should be working fine now.
And that's it! If I am forgetting any steps please let me know, again I am writing this from memory of the process so it may be missing some minor details. I hope this helps!!!
Click to expand...
Click to collapse
bro, I have a problem, my tablet is in a bootloop and I don't know what to do, try with other custom roms but it's the same, what do I have to do so that when I install a custom room it doesn't give me that error?
Flashing the Gapps package resulted in an error: Failure to mount '/system_root' (Invalid argument)
V0latyle said:
Flashing the Gapps package resulted in an error: Failure to mount '/system_root' (Invalid argument)
Click to expand...
Click to collapse
Sorry for the bother, new to Android modding scene.
I went into the recovery menu (oem unlock on) and tried to flash TWRP as written on this guide, but I get a secure check fail : aboot on my device and fail on Odin. What do I do here?
Edit: Aparently my device is SM-T295, basically the LTE version of the same device, which is why it isn't recognising it. My bad.
Do you have any video to teach better ???
HyruleanKnight said:
Sorry for the bother, new to Android modding scene.
I went into the recovery menu (oem unlock on) and tried to flash TWRP as written on this guide, but I get a secure check fail : aboot on my device and fail on Odin. What do I do here?
Edit: Aparently my device is SM-T295, basically the LTE version of the same device, which is why it isn't recognising it. My bad.
Click to expand...
Click to collapse
Shouldn't matter, TWRP is the same for both variants.
There's two ways to get around the secure check fail problem:
After updating via Odin, make sure you immediately interrupt the boot and force reboot into Download Mode. Then, flash TWRP.
Or, after updating, allow your device to boot to Android, skip through the setup wizard (make sure you connect to the internet), and enable Developer Options. Ensure OEM Unlocking is there and grayed out. If not, leave it for a bit until it is. This disables Vaultkeeper on the bootloader. Then, reboot to download mode and flash TWRP.
In both cases, after flashing TWRP, DO NOT let the device boot into Android. Force boot into recovery, then install the Multidisabler from here.
Now to my own problem...
I don't know what I did differently (or wrong) but I cannot get LineageOS to boot correctly on my T290. I was running 18.1 before. I recently updated to CVG3 and followed the same process as I did before - flashed TWRP, then installed the LineageOS GSI to /system.
18.1 continuously bootloops without even loading LineageOS.
19.1 gets to the LineageOS splash screen, and occasionally the setup screen, but continuously reboots also.
After flashing TWRP, I'm installing the multidisabler, then wiping /system, /data, /cache.
Any idea what I'm doing wrong?
@J.Michael any thoughts? You're more familiar with Samsung than I am
V0latyle said:
Shouldn't matter, TWRP is the same for both variants.
There's two ways to get around the secure check fail problem:
After updating via Odin, make sure you immediately interrupt the boot and force reboot into Download Mode. Then, flash TWRP.
Or, after updating, allow your device to boot to Android, skip through the setup wizard (make sure you connect to the internet), and enable Developer Options. Ensure OEM Unlocking is there and grayed out. If not, leave it for a bit until it is. This disables Vaultkeeper on the bootloader. Then, reboot to download mode and flash TWRP.
In both cases, after flashing TWRP, DO NOT let the device boot into Android. Force boot into recovery, then install the Multidisabler from here.
Now to my own problem...
I don't know what I did differently (or wrong) but I cannot get LineageOS to boot correctly on my T290. I was running 18.1 before. I recently updated to CVG3 and followed the same process as I did before - flashed TWRP, then installed the LineageOS GSI to /system.
18.1 continuously bootloops without even loading LineageOS.
19.1 gets to the LineageOS splash screen, and occasionally the setup screen, but continuously reboots also.
After flashing TWRP, I'm installing the multidisabler, then wiping /system, /data, /cache.
Any idea what I'm doing wrong?
@J.Michael any thoughts? You're more familiar with Samsung than I am
Click to expand...
Click to collapse
I think I have a solution.
I see that you are installing the multidisabler after you booted TWRP and by wiping the partitions, however, what you are supposed to do is this:
After you have booted into TWRP and have swiped to allow modifications, go to Wipe> Format Data and type yes. Don't reboot, and don't wipe any other partitions.
After that, go to install and then install the multidisabler, don't reboot.
Then install the latest LineageOS gsi to the system partition, and finally install gapps, then reboot.
Make sure you are choosing the arm64_bvS_vndklite variant, otherwise it will bootloop.
Hope this helps!
Just Mike said:
I think I have a solution.
I see that you are installing the multidisabler after you booted TWRP and by wiping the partitions, however, what you are supposed to do is this:
After you have booted into TWRP and have swiped to allow modifications, go to Wipe> Format Data and type yes. Don't reboot, and don't wipe any other partitions.
After that, go to install and then install the multidisabler, don't reboot.
Then install the latest LineageOS gsi to the system partition, and finally install gapps, then reboot.
Make sure you are choosing the arm64_bvS_vndklite variant, otherwise it will bootloop.
Hope this helps!
Click to expand...
Click to collapse
Okay, so install Multidisabler AFTER wiping data. I'll try that.
I'm using the bgS image so it's already got Google apps. I didn't have any success flashing any of the Gapps packages on the vanilla images.
Is Multidisabler still necessary on Android 11 on this device, or do we just need a patched vbmeta.img?
V0latyle said:
Okay, so install Multidisabler AFTER wiping data. I'll try that.
I'm using the bgS image so it's already got Google apps. I didn't have any success flashing any of the Gapps packages on the vanilla images.
Is Multidisabler still necessary on Android 11 on this device, or do we just need a patched vbmeta.img?
Click to expand...
Click to collapse
Yes, Multidisabler is necessary, otherwise it'll bootloop. I haven't tried anything with a patched vbmeta and frankly don't want to.
The bgS version will work just fine for Android 11.
Currently running Android 13 with LineageOS 20.0, the bvS version. Gotta say it works great. MindtheGapps 13 will work, I haven't encountered any "This device is not certified" issues.
Just Mike said:
Yes, Multidisabler is necessary, otherwise it'll bootloop. I haven't tried anything with a patched vbmeta and frankly don't want to.
The bgS version will work just fine for Android 11.
Currently running Android 13 with LineageOS 20.0, the bvS version. Gotta say it works great. MindtheGapps 13 will work, I haven't encountered any "This device is not certified" issues.
Click to expand...
Click to collapse
Do I need to wipe /system or /boot or anything before installing? I did exactly as you said - rebooted to recovery (was running Samsung stock), formatted data, installed multidisabler, then installed a LineageOS 19 image to /system. It begins to boot (LineageOS animation) then reboots.
Are you using Andy Yan's builds?
V0latyle said:
Do I need to wipe /system or /boot or anything before installing? I did exactly as you said - rebooted to recovery (was running Samsung stock), formatted data, installed multidisabler, then installed a LineageOS 19 image to /system. It begins to boot (LineageOS animation) then reboots.
Are you using Andy Yan's builds?
Click to expand...
Click to collapse
Nope, you don't have to wipe any other partitions, only format data
Yes, I'm using Andy Yan's builds. I'll link the thread here: https://forum.xda-developers.com/t/gsi-13-lineageos-20-trebledroid-based.4517345/
If I may ask, which type GSI from Andy Yan did you use?
Just Mike said:
Nope, you don't have to wipe any other partitions, only format data
Yes, I'm using Andy Yan's builds. I'll link the thread here: https://forum.xda-developers.com/t/gsi-13-lineageos-20-trebledroid-based.4517345/
If I may ask, which type GSI from Andy Yan did you use?
Click to expand...
Click to collapse
Trying to get back into TWRP, just a sec...
-arm64_bgS.img
Flashing the vndklite one now to see if it works
If I can get this working, I plan on using a bgN flavor so I can just install Magisk, since I don't use SuperSU
Edit: vndklite is bootlooping too

Development [ROM][13][barbet] PixelExperience [AOSP][OFFICIAL]&[UNOFFICIAL]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
PixelExperience for Pixel 5a Barbet
​
What is this?
PixelExperience is an AOSP based ROM, with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts, boot animation)
Our mission is to offer the maximum possible stability and security, along with essential and useful features for the proper functioning of the device
Based on Android 13
Whats working?
Wi-Fi
RIL
Mobile data
GPS
Camera
Flashlight
Camcorder
Bluetooth
FM radio
Fingerprint reader
Face unlock
NFC
Lights
Sound/vibration
Known issues
Nothing yet
You tell me
DON'T FLASH GAPPS, THEY'RE ALREADY INCLUDED
Downloads:
OFFICIAL:
https://download.pixelexperience.org/barbet
UNOFFICIAL:
Standard
PixelExperience_barbet-13.0-20230109-0542-UNOFFICIAL.zip
drive.google.com
Plus ver.
PixelExperience_Plus_barbet-13.0-20230109-0353-UNOFFICIAL.zip
drive.google.com
Stay tuned
Our Official Telegram channel
Our blog
Install PixelExperience on barbet​WARNING: I copy and pasted thes instuctions. Please go to the offical guide for your device Barbet https://wiki.pixelexperience.org/devices/barbet/install/
WARNING: These instructions only work if you follow every section and step precisely.
Do not continue after something fails!
Basic requirements​
Read through the instructions at least once before actually following them, so as to avoid any problems due to any missed steps!
Make sure your computer has adb and fastboot. Setup instructions can be found here.
Enable USB debugging on your device.
warning
WARNING: Before following these instructions please ensure that the device is on the latest Android 13 firmware.
This is not necessarily the newest available version! Please up- or downgrade to the required version before proceeding (guides can be found on the internet!).
Flashing the vendor boot partition​warning
WARNING: This platform requires the vendor boot partition to be flashed for recovery to work properly, the process to do so is described below.
Download this vendor_boot.img file.
Power off the device, and boot it into bootloader mode:
With the device powered off, hold Volume Down + Power.
Flash a the downloaded images to your device by typing (replace <vendor_boot> with the actual filename!):
fastboot flash vendor_boot <vendor_boot>.img
Unlocking the bootloader​info_outline
NOTE: The steps below only need to be run once per device.
warning
WARNING: Unlocking the bootloader will erase all data on your device! Before proceeding, ensure the data you would like to retain is backed up to your PC and/or your Google account, or equivalent. Please note that OEM backup solutions like Samsung and Motorola backup may not be accessible from PixelExperience once installed.
Enable OEM unlock in the Developer options under device Settings, if present.
Connect the device to your PC via USB.
On the computer, open a command prompt (on Windows) or terminal (on Linux or macOS) window, and type:
adb reboot bootloader
You can also boot into fastboot mode via a key combination:
With the device powered off, hold Volume Down + Power.
Once the device is in fastboot mode, verify your PC finds it by typing:
fastboot devices
If you don’t get any output or an error:
on Windows: make sure the device appears in the device manager without a triangle. Try other drivers until the command above works!
on Linux or macOS: If you see no permissions fastboot try running fastboot as root. When the output is empty, check your USB cable and port!
Now type the following command to unlock the bootloader:
fastboot flashing unlock
info_outline
NOTE: At this point the device may display on-screen prompts which will require interaction to continue the process of unlocking the bootloader. Please take whatever actions the device asks you to to proceed.
If the device doesn’t automatically reboot, reboot it. It should now be unlocked.
Since the device resets completely, you will need to re-enable USB debugging to continue.
Flashing the vendor boot partition​warning
WARNING: This platform requires the vendor boot partition to be flashed for recovery to work properly, the process to do so is described below.
Download this vendor_boot.img file.
Power off the device, and boot it into bootloader mode:
With the device powered off, hold Volume Down + Power.
Flash a the downloaded images to your device by typing (replace <vendor_boot> with the actual filename!):
fastboot flash vendor_boot <vendor_boot>.img
Temporarily booting a custom recovery using fastboot​
Download the PixelExperience Recovery. Simply download the latest recovery file.
Connect your device to your PC via USB.
On the computer, open a command prompt (on Windows) or terminal (on Linux or macOS) window, and type:
adb reboot bootloader
You can also boot into fastboot mode via a key combination:
With the device powered off, hold Volume Down + Power.
Once the device is in fastboot mode, verify your PC finds it by typing:
fastboot devices
If you don’t get any output or an error:
on Windows: make sure the device appears in the device manager without a triangle. Try other drivers until the command above works!
on Linux or macOS: If you see no permissions fastboot try running fastboot as root. When the output is empty, check your USB cable (preferably use a USB Type-A 2.0 one or a USB hub) and port!
check
TIP: Some devices have buggy USB support while in bootloader mode, if you see fastboot hanging with no output when using commands such as fastboot getvar ... , fastboot boot ..., fastboot flash ... you may want to try a different USB port (preferably a USB Type-A 2.0 one) or a USB hub.
Temporarily flash a recovery on your device by typing (replace <recovery_filename> with the actual filename!):
fastboot flash boot <recovery_filename>.img
info_outline
NOTE: Outdated fastboot releases dropped legacy A/B support, so it might attempt to flash to boot__a / boot__b rather than boot_a / boot_b if you try to flash boot. In this case, you must update fastboot to a release newer than or equal to 31.0.2. Alternatively, you can manually specify which slot to flash to based on what slot fastboot failed to flash to. For example, if fastboot fails to flash to boot__a, you must flash to boot_a.
Installing PixelExperience from recovery​
Download the PixelExperience installation package that you would like to install or build the package yourself.
If you are not in recovery, reboot into recovery:
With the device powered off, hold Volume Down + Power. Then use the menu to select Recovery Mode.
Now tap Factory Reset, then Format data / factory reset and continue with the formatting process. This will remove encryption and delete all files stored in the internal storage, as well as format your cache partition (if you have one).
Return to the main menu.
Sideload the PixelExperience .zip package:
On the device, select “Apply Update”, then “Apply from ADB” to begin sideload.
On the host machine, sideload the package using: adb sideload filename.zip.
check
TIP: Normally, adb will report Total xfer: 1.00x, but in some cases, even if adb: failed to read command: Success/No error. In some cases it will report adb: failed to read command: No error or adb: failed to read command: Undefined error: 0 which is also fine.
Once you have installed everything successfully, click the back arrow in the top left of the screen, then “Reboot system now”.
info_outline
NOTE: The first boot usually takes no longer than 15 minutes, depending on the device. If it takes longer, you may have missed a step, otherwise feel free to get assistance
check
TIP: If the installation process reports the message "(~47%) adb: failed to read the command: No error", do not worry, the process was completed successfully and you can restart the device.
I am not connected to Pixel Experience rom in any way.
Just posting to share.
I am not providing help and am not responsible for anything that happens.
Help each other!
If a P.E. maintainer wants this down. Please do so.
RESERVED:
Jan. Changelog:
January and December (2022) security patch
Google Apps updated
Fixed battery drain and lag spike caused by Pixel Launcher (Need to uninstall previous updates of Android System Intelligence or do a clean flash if the issue persists)
Minor issues fixed
Plus Version:
13 Plus version is here!​First of all we hope you all are doing well. After the last two months of delayed updates it feels good to push an update in the perfect time period!
As the title says we are here with the PixelExperience Plus version.
Clean flash is not required if coming from normal version
Click to expand...
Click to collapse
Now coming to the feature list for the Plus version:-
LiveDisplay (color profile, display mode, reading mode, color calibration)
Hide Notch support.
StatusBar shortcuts
Rotation settings
Lock screen display (media cover, music visualizer, power menu)
Per-app volume settings
Increasing ring volume
Different gestures
Power and Volume button customisations
Network traffic monitor
Brightness (brightness slider, auto brightness, brightness control)
Quick settings (quick pulldown, title visibility, vibrate on touch, rows, columns)
There is more stuff one can unearth – this list was just a start off for the long feature list we have.
Just to be clear. Not a maintainer. Not affiliated with PixelExperience. Not Responsible for your choices!
Just creating a thread to spread the word my friends
Thanks for this, exactly what I've been looking for (stock ROM with volume button playback control, let's go!)
Flashed using instructions (factory reset, sideload). No issues, things seem to be working smoothly. Will observe battery life over the next few days but not expecting much difference either way.
Thanks for the nice Rom
Is there a version of PixelExperience for Pixel 5a Barbet but Android 11 (Plus edition)?
ALWA7SH6 said:
Thanks for the nice Rom
Is there a version of PixelExperience for Pixel 5a Barbet but Android 11 (Plus edition)?
Click to expand...
Click to collapse
No. Not that i know of. Give thanks to the PE team.
rhewins2268 said:
No. Not that i know of. Give thanks to the PE team.
Click to expand...
Click to collapse
Who is know?
ALWA7SH6 said:
Who is know?
Click to expand...
Click to collapse
I am just saying that i don't know of any Official PixelExperience Android 11 (Plus edition)
rhewins2268 said:
I am just saying that i don't know of any Official PixelExperience Android 11 (Plus edition)
Click to expand...
Click to collapse
TY
ALWA7SH6 said:
Thanks for the nice Rom
Is there a version of PixelExperience for Pixel 5a Barbet but Android 11 (Plus edition)?
Click to expand...
Click to collapse
there is none, pixel experience crew stopped with support for android 11, all projects moved to android 12
ALWA7SH6 said:
Thanks for the nice Rom
Is there a version of PixelExperience for Pixel 5a Barbet but Android 11 (Plus edition)?
Click to expand...
Click to collapse
you might be able to build your own rom and switch to the branch eleven-plus, but not sure if it would actually work or not. also i am sure it would be outdated for kernel security patches and other updates. build time on my dual cpu e5-2667v2 (32 cores total), 160gb of mem, WD SN750 1tb nvme and 1gbp internet running debian bookwork with tkg kernel is about 2hrs from start to finish. i just build a twelve-plus yesterday and i was surprised that everything worked out of the box using adb sideload on the unoffical twrp. the experience recovery actually installed and worked this time. rom is very smooth or i should say smoother than it was. a few new features were added. some were moved to a different spots. magisk install was easy with the working experience recovery allowing adb sideload to flash magisk. i might actually stick with this rom for a while.
rchris494 said:
you might be able to build your own rom and switch to the branch eleven-plus, but not sure if it would actually work or not. also i am sure it would be outdated for kernel security patches and other updates. build time on my dual cpu e5-2667v2 (32 cores total), 160gb of mem, WD SN750 1tb nvme and 1gbp internet running debian bookwork with tkg kernel is about 2hrs from start to finish. i just build a twelve-plus yesterday and i was surprised that everything worked out of the box using adb sideload on the unoffical twrp. the experience recovery actually installed and worked this time. rom is very smooth or i should say smoother than it was. a few new features were added. some were moved to a different spots. magisk install was easy with the working experience recovery allowing adb sideload to flash magisk. i might actually stick with this rom for a while.
Click to expand...
Click to collapse
Can you share it ty?
ALWA7SH6 said:
Can you share it ty?
Click to expand...
Click to collapse
yeah.
steps
1. unlocked bootloader
2. flashed fresh factory image (12.1.0 (SP2A.220405.003, Apr 2022)) from google dev site (check marked full wipe & force flash all partitions)
3. waited for phone to fully boot up. did offline setup skipping everything until i hit home screen
4. went to settings enabled developer mode & usb debugging
5. rebooted to bootloader (adb reboot bootloder)
6. toggled bootloader until i seen recovery then booted into stock reocovery
7. power + vol up for 3 sec then release you should get the stock recovery menu. do a factory reset / wipe data
8. reboot back to bootloader in the menu options of stock recovery
9. boot unoffical trwp from nijel8 (fastboot boot twrp-3.6.0_11-0-barbet.img)
10. in twrp go to advanced and adb sideload. set twrp to adb sideload
11. download https://drive.google.com/file/d/1yJdmMDap95-vYVZEhUUrZ2m3E45Y6ARg/view?usp=sharing (sha-256 checksum) or https://drive.google.com/file/d/1yJdmMDap95-vYVZEhUUrZ2m3E45Y6ARg/view?usp=sharing (untouched rom direct from pixel experience) if you don't care about checksum you can skip it.
12. adb sideload the rom (PixelExperience_Plus_barbet-12.1-20220423-2211-UNOFFICIAL.zip) note it fails at 47% and you might see a bunch of red warning on twrp. just ignore them and reboot the phone. pixel experience is now loaded on the phone. i had to do the whole process twice because twrp messed up the first time due to it not being officially up to 12 and sideload sometimes being flaky.
13. after setup was done i enabled debugging again and booted to bootloader, then recovery mode. pixel experience recovery should now be loaded. its touch screen or volume controlled. select adb sideload and side load magisk 24.3.apk or you can rename it to zip. doesnt matter. reboot phone. check app drawer. magisk will be there. if not give it a second it will pop up. tap the app to download full version. enjoy rooted & pixel experience
the rom is compiled directly from pixel experience source. i do not mod or edit anything. i just let my computer sweat at 100% usage for 2hrs and hope like hell the rom works.
i can try an eleven-plus build if you want but i doubt it will work and would probably end up bricking your phone.
this is the process i used. i take not responsibility if you brick your phone.
usually your brick is a soft brick holding power + vol up + vol down for 30sec will force restart your phone. then power off then power + vol dow to get back to bootloader so you can work with it again (factory flash or whatever)
android base is 12.1.0_r4
rchris494 said:
yeah.
steps
1. unlocked bootloader
2. flashed fresh factory image (12.1.0 (SP2A.220405.003, Apr 2022)) from google dev site (check marked full wipe & force flash all partitions)
3. waited for phone to fully boot up. did offline setup skipping everything until i hit home screen
4. went to settings enabled developer mode & usb debugging
5. rebooted to bootloader (adb reboot bootloder)
6. toggled bootloader until i seen recovery then booted into stock reocovery
7. power + vol up for 3 sec then release you should get the stock recovery menu. do a factory reset / wipe data
8. reboot back to bootloader in the menu options of stock recovery
9. boot unoffical trwp from nijel8 (fastboot boot twrp-3.6.0_11-0-barbet.img)
10. in twrp go to advanced and adb sideload. set twrp to adb sideload
11. download https://drive.google.com/file/d/1yJdmMDap95-vYVZEhUUrZ2m3E45Y6ARg/view?usp=sharing (sha-256 checksum) or https://drive.google.com/file/d/1yJdmMDap95-vYVZEhUUrZ2m3E45Y6ARg/view?usp=sharing (untouched rom direct from pixel experience) if you don't care about checksum you can skip it.
12. adb sideload the rom (PixelExperience_Plus_barbet-12.1-20220423-2211-UNOFFICIAL.zip) note it fails at 47% and you might see a bunch of red warning on twrp. just ignore them and reboot the phone. pixel experience is now loaded on the phone. i had to do the whole process twice because twrp messed up the first time due to it not being officially up to 12 and sideload sometimes being flaky.
13. after setup was done i enabled debugging again and booted to bootloader, then recovery mode. pixel experience recovery should now be loaded. its touch screen or volume controlled. select adb sideload and side load magisk 24.3.apk or you can rename it to zip. doesnt matter. reboot phone. check app drawer. magisk will be there. if not give it a second it will pop up. tap the app to download full version. enjoy rooted & pixel experience
the rom is compiled directly from pixel experience source. i do not mod or edit anything. i just let my computer sweat at 100% usage for 2hrs and hope like hell the rom works.
i can try an eleven-plus build if you want but i doubt it will work and would probably end up bricking your phone.
this is the process i used. i take not responsibility if you brick your phone.
usually your brick is a soft brick holding power + vol up + vol down for 30sec will force restart your phone. then power off then power + vol dow to get back to bootloader so you can work with it again (factory flash or whatever)
android base is 12.1.0_r4
View attachment 5597359
Click to expand...
Click to collapse
(a few new features were added)
Like what?
ALWA7SH6 said:
(a few new features were added)
Like what?
Click to expand...
Click to collapse
rhewins2268 said:
Plus Version:
April Update: 12 Plus version is here!​First of all we hope you all are doing well. After the last two months of delayed updates it feels good to push an update in the perfect time period!
As the title says we are here with the PixelExperience Plus version.
Now coming to the feature list for the Plus version:-
LiveDisplay (color profile, display mode, reading mode, color calibration)
Hide Notch support.
StatusBar shortcuts
Rotation settings
Lock screen display (media cover, music visualizer, power menu)
Per-app volume settings
Increasing ring volume
Different gestures
Power and Volume button customisations
Network traffic monitor
Brightness (brightness slider, auto brightness, brightness control)
Quick settings (quick pulldown, title visibility, vibrate on touch, rows, columns)
There are more stuff one can unearth – this list was just a start off for the long feature list we have.
Click to expand...
Click to collapse
How is fingerprint sensor working, does it also have lag if AOD is not enabled? March update introduced 2 seconds delay after FP sensor registers your finger before it shows you your home screen. If you use AOD that issue is not present.
rhewins2268 said:
Plus Version:
April Update: 12 Plus version is here!​First of all we hope you all are doing well. After the last two months of delayed updates it feels good to push an update in the perfect time period!
As the title says we are here with the PixelExperience Plus version.
Now coming to the feature list for the Plus version:-
LiveDisplay (color profile, display mode, reading mode, color calibration)
Hide Notch support.
StatusBar shortcuts
Rotation settings
Lock screen display (media cover, music visualizer, power menu)
Per-app volume settings
Increasing ring volume
Different gestures
Power and Volume button customisations
Network traffic monitor
Brightness (brightness slider, auto brightness, brightness control)
Quick settings (quick pulldown, title visibility, vibrate on touch, rows, columns)
There are more stuff one can unearth – this list was just a start off for the long feature list we have.
Click to expand...
Click to collapse
I noticed that sometimes the scanner simply refuses to understand the finger, I also noticed that when AOD is on, if you put the phone with the screen down, it does not go out, but if you turn up the screen and close the proximity sensor, it goes out
fackstrot said:
I noticed that sometimes the scanner simply refuses to understand the finger, I also noticed that when AOD is on, if you put the phone with the screen down, it does not go out, but if you turn up the screen and close the proximity sensor, it goes out
Click to expand...
Click to collapse
Please open bug on pixel experience GitHub, since main developer is not following this thread and PE community usually only fixes issues reported on official page.
Issues · PixelExperience/android-issues
Issue tracker. Contribute to PixelExperience/android-issues development by creating an account on GitHub.
github.com

Categories

Resources