Database Develop

[BOOTLOADER][SAFEBOOT] Ouya Bootmenu (mlq)

{
"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"
}
Ouya Bootmenu development/release thread​
This is based on the awesome work by Hal9k.
Because of the fact that the Ouya doesn't have recovery accessibility via hardware buttons we need to play safe and utilise chainbooting.
This bootmenu resides in the kernel partition and is loaded on every normal bootup.
In-depth info in Hal9k's thread here: http://forum.xda-developers.com/showthread.php?t=2499673.
It presents various choices on every boot:
Normal boot - (default) loads bootimage from system partition (/system/boot.img)
Alternate boot - loads bootimage from sdcard (/sdcard/altboot.img)
Recovery - reboots into recovery (recovery partition)
Failsafe - loads built-in failsafe mode
Bootloader - Reboots into stock bootloader (for fastboot access - USE WITH CARE)
Notes about the failsafe
the failsafe mode (which has the bootmenu built-in) will pop up in the following cases:
the bootmenu could not find a valid bootimage (read: /system/boot.img for "normal boot"; /sdcard/altboot.img for "alternate boot")
the user selects "failsafe" from the menu
the failsafe mode resides in the bootmenu image itself and should ONLY be used (as its name suggests) as failsafe.
for regular flashing you need to use a newer cwm version which resides in the recovery partition and is accessible via the "recovery" entry in the bootmenu (see below).
And remember: After flashing this you DON'T NEED TO EVER touch your boot/LNX partition again
Reminder: Failsafe mode is ONLY to be used in case you can't boot into your recovery partition. For regular rom flashing the respective CWM recovery (see below) is required.
Installation
You need to have a newer CWM recovery installed in order to flash the bootmenu.
READ AND UNDERSTAND what you are doing!
This bootmenu is flashed over your current bootimage - newer cyanogenmod builds will place their bootimage to /system/boot.img automatically. if you are not using a custom rom you will need to relocate your bootimage (read: kernel) to /system/boot.img manually.
You need to have a newer CWM recovery installed in order to flash the bootmenu (otherwise you'll get a build.product mismatch while installing).
1a) If you already have an older custom recovery installed:
Boot into recovery and flash https://download.milaq.net/public/android/ouya/misc/recovery-clockwork-6.0.4.8-ouya.zip. This will update your recovery to a newer version allowing you to flash the bootmenu regularly.
1b) If you don't have a custom recovery installed:
You can either use the one-click installer from http://forum.xda-developers.com/showthread.php?t=2295645 and continue with step 1a).
Or you can flash a newer recovery via fastboot (if you know what you are doing): https://download.milaq.net/public/android/ouya/misc/recovery-clockwork-6.0.4.8-ouya.img
2.) Flash the bootmenu via (the new) recovery by installing the latest updatezip (download below). Make sure that the installation procedure was successful.
If you get a "MD5 mismatch" your download is probably broken. Just redownload and try again. The installscript checks the md5's mutliple times while installing and reflashes your old bootimage in case something goes wrong.
So if you are not doing something REALLY stupid this is safe to go.
Download
Download latest version (v2.0.4)
Changelog
Code:
2.0.4
* reduce menu timeout for faster regular boot
* ui improvements in failsafe mode
2.0.3
* bootmenu: increase maximum number of input devices to 5 - e.g. the gpio
keys (the ouya power button - 1 node), a mutlimedia keyboard (2 nodes), a mouse (1 nodes)
and a controller (1 node).
2.0.2
* add in additional alternate boot image folder handling to fix compatibility with kitkat
* update failsafe recovery to differ more from regular recovery
* minor ui and ux tweaks in both bootmenu and failsafe
2.0.1
* initial reworked version
And as always: we take no responsibility whatsoever for raging, screaming, crying, frustration, failing, confusion, dead kittens, etc.
Source
https://github.com/milaq/ouya_bootmenu

Thanks/Credits
Click to expand...
Click to collapse
Hal9k - for the inital ouya bootmenu and many great ideas
Dan Pasanen (invisiblek) - for great work on the recovery and initial porting efforts
Let me know if i omitted you and i will add you here asap
IRC channel
Click to expand...
Click to collapse
Visit us in #cyanogenmod (general) or #cyanogenmod-dev (only dev related talk) on freenode

alright so i installed it, and normal boot boots back into recovery

YoshiFan501 said:
alright so i installed it, and normal boot boots back into recovery
Click to expand...
Click to collapse
This bootmenu is flashed over your current bootimage (you will need to relocate your kernel (to /system/boot.img) if you not using a custom rom)
Click to expand...
Click to collapse
most probably because /system/boot.img is not found. you need to install cyanogenmod afterwards or relocate your bootimage if still on stock.

Is it possible to easily revert the Ouya to a fully stock state after this? Any unninstall method?

Fyi everyone, if you scroll down through the options in cmw a couple times you'll activate rainbow mode! I'm not sure if this is an ouya specific cmw mod or not cuz all my other devices have twrp but anywho ENJOY!
Sent from my Galaxy Nexus using XDA Premium 4 mobile app

Is it possible to use this bootloader with the EternityProject Kernel 3.4.37 for OUYA and the OUYA-Enhanced Rom. I can flash the ROM from within Recovery, but how do I install their kernel for it to boot in ouya bootmenu? I just don't want to brick, thanks for your help!

Just wanted to be the first to tell you that it's working fine and I'm glad to finally give the ouya what it deserves: a custom ROM! Thanks dude!

Can someone post a step by step to move from ep bootlegger to this one?

So can this be dualbooted? If stock ouya boot image is put on /sdcard and named altboot.bin? Right now if I select Alternate Boot, it boots cwm 6.0.3.2. Same as Failsafe.

new version
new version is available in the first post

firmtech said:
So can this be dualbooted? If stock ouya boot image is put on /sdcard and named altboot.bin? Right now if I select Alternate Boot, it boots cwm 6.0.3.2. Same as Failsafe.
Click to expand...
Click to collapse
update the bootmenu to v2.0.2 and rename your alternate bootimage on /sdcard to "altboot.img" and you should be ready to go

milaq thanks for excellent work....
Can you add reboot recovery options in Ouya Failsafe menu to get the full recovery menu?
The power button(for choices) works only if ouya connected-hdmi to hdmi
If Ouya connected hdmi to dvi(Pc monitor) the power button does not respond!
So to go into recovery mode, you can use alt + printScn (SysRq) + i (if keyboard connected)
But now the Ouya goes into a Failsafe menu.

version bump again
krest said:
the power button does not respond!
Click to expand...
Click to collapse
i suspect that you have too many input devices connected during boot.
in version <=2.0.2 the maximum number of input devices that are recognised in the bootmenu was 3.
in case you have a keyboard (usually takes up 2 input nodes) and a mouse connected, the ouya power button (also an input device) was at the end of the list thus not taken into account.
i raised the number of recognised input devices to 5 in version 2.0.3 (see first post for download). that should allow most setups to work fine.
in case you still can't use the power button to select just briefly disconnect your usb devices at boot and reconnect them after making your choice in the bootmenu.

milaq said:
i suspect that you have too many input devices connected during boot.
in version <=2.0.2 the maximum number of input devices that are recognised in the bootmenu was 3.
in case you have a keyboard (usually takes up 2 input nodes) and a mouse connected, the ouya power button (also an input device) was at the end of the list thus not taken into account.
i raised the number of recognised input devices to 5 in version 2.0.3 (see first post for download). that should allow most setups to work fine.
in case you still can't use the power button to select just briefly disconnect your usb devices at boot and reconnect them after making your choice in the bootmenu.
Click to expand...
Click to collapse
Yes, you're right....
Now it's working perfectly
In any case, it would be great if you added the reboot recovery options in Ouya Failsafe menu.
Thanks

Dual Boot
Now that I have CWM with the newest boot menu and CM11 running super smooth how do I go about flashing the stock Ouya ROM to the SD card without wiping the whole thing again? Must restore balance in the household. The natives are demanding to have Amazing Frog back!

bootmenu v2.0.4
new version up.
see first post for details.
KJRob said:
Now that I have CWM with the newest boot menu and CM11 running super smooth how do I go about flashing the stock Ouya ROM to the SD card without wiping the whole thing again?
Click to expand...
Click to collapse
dual booting the stock rom is not as easy as it may seem.
with the boot menu you _have_ the ability to dual boot another boot image (read: kernel/ramdisk) but you still need to have a partition where all stock roms system files reside. the internal "sdcard" is out of the game here as it is just a fused filesystem. but i could imagine external usb storage or such. one needs to partition it and make the respective changes to the stock ramdisk for it to work.
nevertheless, i will not spend time working on stock rom dualboot compatibility. but anyone willing to invest time into it is very welcomed to do so.

milaq said:
new version up.
see first post for details.
dual booting the stock rom is not as easy as it may seem.
with the boot menu you _have_ the ability to dual boot another boot image (read: kernel/ramdisk) but you still need to have a partition where all stock roms system files reside. the internal "sdcard" is out of the game here as it is just a fused filesystem. but i could imagine external usb storage or such. one needs to partition it and make the respective changes to the stock ramdisk for it to work.
nevertheless, i will not spend time working on stock rom dualboot compatibility. but anyone willing to invest time into it is very welcomed to do so.
Click to expand...
Click to collapse
I appreciate the reply. I would love to have the know how to do the work but that is out of my knowledge base. Maybe one day I will. I can wait for the official Ouya store to hit android. The kids will have to wait as well. I love my KK device just the way it is.

milaq said:
dual booting the stock rom is not as easy as it may seem.
with the boot menu you _have_ the ability to dual boot another boot image (read: kernel/ramdisk) but you still need to have a partition where all stock roms system files reside. the internal "sdcard" is out of the game here as it is just a fused filesystem. but i could imagine external usb storage or such. one needs to partition it and make the respective changes to the stock ramdisk for it to work.
nevertheless, i will not spend time working on stock rom dualboot compatibility. but anyone willing to invest time into it is very welcomed to do so.
Click to expand...
Click to collapse
It's doable but once its done both sides of the roms would have significant storage reduction... on another note the method would be completely ( and easily ) reversible to the actual installed rom.
The other route is like you said with usb storage which would probably be the better of the 2 options.
Although with all this said we know that the ouya storefront is coming in the form of an app and I guess the other option would be to "portablize" the current framework ( I did it with 519... could try with the latest one... but I never tried it on anything higher than 4.3 )

How do you revert back to factory settings? Every time I flash stock, it boots to this. Thanks and sorry in advance

[GUIDE][SM-T510] Unlock/Root - Tab A 10.1 (Android 10)

This are exactly the steps I did to root this device.
Pre-requisites
. Odin 3.14.4
. Latest MagiskManager(Im using 8.0.2)
. bootloader unlocked
. Firmware that matches the version installed on your device.
. Lz4 extractor : https://github.com/lz4/lz4/releases
. TAR.MD5_PACKAGER
First at all, remember to unlock T510 bootloader
The firmware which is based is this : SM-T510_1_20200702122203_r4oibm2ll7_fac.zip
. Extract AP_T510XXU3BTFN_CL19000394_QB32592397_REV02_user_low_ship_meta_OS10.tar.md5
. Extract boot.img from .tar.md5
. lz4.exe -d boot.img.lz4
boot.img
. Copy MagiskManager-v8.0.2.apk to your tablet and Run it.
- Magisk > Install > Recovery Mode Selected > Next > Method > Select and Patch a File > boot.img > LET'S GO > "All done!"
File called : magisk_pached.img
. Copy to PC
- copy magisk_patched.img boot.img
copy boot.img to TAR_MD5_PACKAGER\parts\
. TAR.MD5_PACKAGER.bat > "1" > boot.img > "Y" > "2" > "1" > "Y" > "4"
in TAR_MD5_PACKAGER\packaged\ : boot.img.tar.md5
. Run Odin
Plug USB > should say "Added!!"
. Volume Up and Power until you get into recovery menu > reboot to bootloader
- Connect USB
- Run ODIN
. In Odin : AP > boot.img.tar.md5
Options > Delect "Auto Reboot"
Click Start . Make sure the operation succeeds.
Unplug your device and reboot.
. Ask for Factory data reset > Factory Reset
. Reboot System now
. Volume Up + Vol down + Power
. Setup WiFi
. Install and run MagiskManager-v8.0.2.apk
. Tablet will ask Reboot System now
Click to expand...
Click to collapse

Great! I somewhat did the same method for rooting/twrp installing. I was on latest Android 10 build(September patch perhaps). I download the latest firmware and unzipped it then I further extracted AP_T510XXX......... .tar.md5 using zarchiver which have me AP_T510XXX........ .tar. Instead of extracting boot image I patched the whole thing with megisk and flashed it from AP from ODIN. When tablet booted installed megisk manager apk and saw that tablet was rooted.
You can further flash TWRP image using flashify but then stock ROM may not boot. Anyway moving further if you want to flash GSI, first flash Lineage or Nexus Rom and then A64b GSIs can be flashed.

Thanks both! i will take a look when i am at home, i tried to patch AP_T510XXX......... .tar.md5 with magisk but i didnt extract it before and it hold on boot, i try to extract first like @Mrigendra10 then patch it and then odin...

i like the guide but the wording need some improvement newer members to understand it clearly just my 2 cents thanks for guide.

Help me out here, I did everything correctly and installed it with Odin, it was a success, but when I installed magisk on my tablet again, nothing new happened, didn't ask me to reboot and I tried an app that requires root but said I wasn't rooted. Help please.

Used a root checker, says a super user app was found, that being Magisk. says root unavailable and no su binary .

Hi, just to be sure
Odin > Options > Delect
means 'Deselect' and not 'Select'?
Thx!

cera33 said:
Hi, just to be sure
Odin > Options > Delect
means 'Deselect' and not 'Select'?
Thx!
Click to expand...
Click to collapse
Yes, it does

I was able to complete everything step by step and used a root checker and it states "Root access is not properly installed on this device. Any idea what may have gone wrong? Do I just start over and try again?

same here. can not root SM510. tried linegae, nexus and stock from. any video root with magisk with rambus on and saftety net passed?

Same..

Hey, just some notes to clear up any confusion about Magisk on the T510. The tablet doesn't have a ramdisk available for boot, so Magisk must be installed to the recovery partition. Below is a screenshot of Magisk Manager data from my own tablet:
{
"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"
}
And per the Magisk installation instructions:
Pay special attention to the Ramdisk info. If the result is Yes, congratulations, your device is perfect for installing Magisk! However, if the result is No this means your device’s boot partition does NOT include ramdisk. This means you will have to go through some extra steps to make Magisk work properly.
If your device does not have boot ramdisk, read the Magisk in Recovery section after installing. The information in that section is VERY important!
If you are using a Samsung device and the SAR result is Yes, please check its own section.
If you are using a Huawei device and the SAR result is Yes, please check its own section.
Click to expand...
Click to collapse
In order to boot into system with active Magisk, one has to essentially boot into recovery. From the Magisk in Recovery section (Bixby button references can be ignored):
If your device does not have ramdisk in boot images, Magisk has no choice but to be installed in the recovery partition. For these devices, you will have to reboot to recovery every time you want Magisk.
When Magisk is installed in your recovery, you CANNOT use custom recoveries to install/upgrade Magisk! The only way to install/upgrade Magisk is through the Magisk app. It will be aware of your device state and install to the correct partition and reboot into the correct mode.
Since Magisk now hijacks the recovery of the device, there is a mechanism to let you actually boot into recovery mode when needed: it is determined by how long you press the recovery key combo.
Each device has its own key combo to boot into recovery, as an example for Galaxy S10 it is (Power + Bixby + Volume Up). A quick Google search should easily get you this info of your device. As soon as you press the combo and the device vibrates with a splash screen, release all buttons to boot into Magisk. If you decide to boot into actual recovery mode, continue to press volume up until you see the recovery screen.
After installing Magisk in recovery (starting from power off):
(Power up normally) → (System with NO Magisk)
(Recovery Key Combo) → (Splash screen) → (Release all buttons) → (System with Magisk)
(Recovery Key Combo) → (Splash screen) → (Keep pressing volume up) → (Recovery Mode)
Click to expand...
Click to collapse
I can understand now why John Wu was spitting nails mad when Google switched to dynamic partitions with system-as-root: it completely effs up the architecture for rooting with Magisk.
I don't know why Google and manufacturers persist in making it messy to nigh-impossible for end users--who desire to do so--to have full control of their own devices. Stupid. Just stupid. Usunoro...
On the positive side, I hope this helps everyone trying to root their T510 tablets, and explains the weirdness people may have encountered.
(P.S. Since hardware attestation is used on the T510, SafetyNet won't pass, no matter what. There aren't any modules that can address this, given that hardware is being used for the evaluation. Another baka change! Also, I'm sticking with Pie since I can't stand Scoped Storage. Can't. Stand. It.)
Fur and Purrs --
--
King Cheetah

wolfyj1 said:
I was able to complete everything step by step and used a root checker and it states "Root access is not properly installed on this device. Any idea what may have gone wrong? Do I just start over and try again?
Click to expand...
Click to collapse

Development [ROM] BeyondROM v5.4 [15/06/2023]-[EWF1]-[EXYNOS]-[SM-G99xB]

{
"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"
}
​​Latest Version v5.4 [15/06/2023]​ROM Maintainer: Andrei @starbucks2010​
ROM Info:​
Click to expand...
Click to collapse
Supported devices:​[SM-G991B], [SM-G996B], [SM-G998B]
ROM Base:​G998BXXU8EWF1 (Android 13 OneUI 5.1) June 2023 Patch Level
ROM Features:​
Click to expand...
Click to collapse
Spoiler: View ROM features
Kernel:
Stock Samsung Kernel
CSC features:
Call Recording
Camera shutter sound menu
Real time network speed in statusbar
AppLock Enabled
ROM Disarm:
Knox partially removed
Light ROM debloat
Disabled Encryption
Disabled stock recovery-from-boot
Modded Settings/Services
Screenshots in secure apps allowed
Phone status: Official
Software Info ROM Details
BAck2Kill mod
Fixes:
Galaxy watch pairing
Bluetooth pairing after reboot
SafetyNet Patch (must enable Magisk hide and install kdrag0n's SN magisk module)
Secure Folder
Other Tweaks/Mods:
Warning boot screen removed, 2 custom boot animation
Automatic EFS backup
Various build prop tweaks
Pre-rooted with latest Magisk canary
Frame buffer increase to help gaming
Not working​
Click to expand...
Click to collapse
Knox related apps: Samsung Pay, Samsung AutoFill
For Safetynet use latest kdrag0n magisk module - link
Changelog​
Click to expand...
Click to collapse
v5.4
- Rebased to latest firmware EWF1 OneUI 5.1 **You must be on EWF1 firmware to flash the BR5.4 zip**
- Stock SHealth fix (tbc)
#######################################
PREVIOUS VERSION
#######################################
v5.3
- Rebased to latest firmware EWE1 OneUI 5.1 **You must be on EWE1 firmware to flash the BR5.3 zip**
Credits​
Click to expand...
Click to collapse
- Mr. Waehere for the extraordinary CRB kitchen
- afaneh92 for S21 TWRP
- John Wu for Magisk
- LeeXDA18 for help with some fixes and Object remover port from S23
- The elite team of ROM testers
- Nguyen for back2kkill mod
- dutchman89 for Beyond Boot Logo
If you like my work, consider buying me a coffee (PayPal link)
Download Links​
Click to expand...
Click to collapse
###############################
CURRENT VERSION
###############################
SM-G99xB ROM Link [EWF1] [BR5.4]
###############################
###############################
TWRP LINK
###############################
S21 TWRP [XDA]
S21+ TWRP [XDA]
S21U TWRP [XDA]
Installation:​
Click to expand...
Click to collapse
​Coming from full stock
Spoiler: How to go from Stock to BeyondROM
**Note: These steps will trip Knox and possibly void warranty on your phone**
**Note: Following these steps you will lose data on your phone, so back-up before continuing**
UNLOCK BOOTLOADER:
Enable Developer Options: Settings > About Phone > Software Information > Keep clicking 'Build Number'
Enable OEM Unlock: Settings > Developer Options > Click 'OEM Unlock' to enable it
Turn of phone
Hold Volume Up + Volume Down, plug in USB cable (PC to Phone)
Your now in download mode (Blue Screen)
Press and hold Volume up (bootloader unlock screen)
Pres Volume up to confirm
**Warning** This will now wipe your phone and restart and couple of times but this is normal
When the phone is booted, skip the initial setup, you don't need to sign in to anything.
Enable developer options again, go to developer options
OEM Unlock should be enabled and now greyed out
Congrats you've unlocked your bootloader
FLASH TWRP + PATCHED VBMETA:
Boot phone into download mode (from power off Volume Up + Volume Down and plugin USB cable)
Press Volume up to continue
Load up ODIN
Go to options and turn off auto reboot
Select USERDATA slot and select the TWRP+Patched VBMETA file (Device Specific)
Click Start
Odin should complete with a PASS
Now Keep USB cable plugged in, hold Volume Down and Power, as soon as the screen goes black hold Volume Up and Power
You should now be in TWRP
IN TWRP:
Do a full wipe (wipe > Format Data > type 'yes'
Reboot phone back to recovery (Reboot > Recovery)
Download ROM and copy either to the phone (PC to Phone) or to a USB OTG device (sorry no SD cards for S21 devices)
FLASH ROM:
In TWRP click 'Install'
If using OTG click 'select storage', select 'USB OTG'
Browse to the location of the ROM zip on the USB device, Select and wipe to confirm.
Follow on screen options
When flash is complete, click 'save logs' (in case you have any flashing issues)
Click finish
Reboot to System
After flash and setup download and install Magisk Canary app from Magisk github and install, when you run for the first time the magisk will need to do some setup and will then automatically reboot the phone
after reboot you're all set, congratulations
Coming from another custom ROM
Spoiler: How to move from another Custom ROM to BeyondROM
CLEAN FLASH (recommended)
Load into TWRP
Do a full wipe
Reboot back into TWRP
Flash Beyond ROM
DIRTY FLASH (warning)
Dirty flash may or may not work, we cannot guarantee that flashing a ROM over the top of another ROM will not give you any issues so it is therefore not our recommended choice, but obviously it's your device so feel free to do so but please do not ask for help with problems if this causes you issues.
Updating BeyondROM to latest version
Spoiler: How to update BeyondROM to latest version
This is obviously very dependent on which version you are running, I.E if your version 3.x jumping to 5.x, then there is a very high change that you will need to upgrade your phone to the latest FW before flashing latest BeyondROM.
Please take note of the changelog as it will say if you need to be on a certain FW version to flash this BR version or if dirty flash from previous version is ok (highly unlikely)
Where dirty flash is not possible and you do need to upgrade your FW to flash the latest these are the recommended steps.
It is assumed that you are already on BeyondROM.
Download the latest/required version of the firmware (Samfirm/Frija etc...)
Unzip the ROM
Rename the files and remove the .md5 from the end of the files
Boot phone into Download mode
Load up Odin, turn off auto-reboot
Insert the relevant files into their slots (BL = BL, AP=AP, CP=CP, CSC=HOME_CSC) **It's important to use HOME_CSC to keep your data intact**
In the USERDATA slot insert your TWRP+Patched VBMETA tar file (Device Specific)
Start Flash
When complete keep USB plugged in, hold Volume Down + Power, as soon as the screen goes black hold Volume Up + Power to enter TWRP
When in TWRP, flash latest BeyondROM (select Dirty flash option)
When complete, save logs, reboot to system
Enjoy!
Useful Links​
Click to expand...
Click to collapse
BeyondROM S21 Group [Telegram]
BeyondROM S21 Group [Discord]
S21 TWRP [XDA]
S21+ TWRP [XDA]
S21U TWRP [XDA]

Installation:
Coming from full stock
Spoiler: How to go from Stock to BeyondROM
**Note: These steps will trip Knox and possibly void warranty on your phone**
**Note: Following these steps you will lose data on your phone, so back-up before continuing**
UNLOCK BOOTLOADER:
Enable Developer Options: Settings > About Phone > Software Information > Keep clicking 'Build Number'
Enable OEM Unlock: settings > Developer Options > Click 'OEM Unlock' to enable it
Turn of phone
Hold Volume Up + Volume Down, plug in USB cable (PC to Phone)
Your now in download mode (Blue Screen)
Press and hold Volume up (bootloader unlock screen)
Pres Volume up to confirm
**Warning** This will now wipe your phone and restart and couple of times but this is normal
When the phone is booted, skip the initial setup, you don't need to sign in to anything.
Enable developer options again, go to developer options
OEM Unlock should be enabled and now greyed out
Congrats you've unlocked your bootloader
FLASH TWRP + PATCHED VBMETA:
Boot phone into download mode (from power off Volume Up + Volume Down and plugin USB cable)
Press Volume up to continue
Load up ODIN
Go to options and turn off auto reboot
Select USERDATA slot and select the TWRP+Patched VBMETA file (Device Specific)
Click Start
Odin should complete with a PASS
Now Keep USB cable plugged in, hold Volume Down and Power, as soon as the screen goes black hold Volume Up and Power
You should now be in TWRP
IN TWRP:
Do a full wipe (wipe > Format Data > type 'yes'
Reboot phone back to recovery (Reboot > Recovery)
Download ROM and copy either to the phone (PC to Phone) or to a USB OTG device (sorry no SD cards for S21 devices)
FLASH ROM:
In TWRP click 'Install'
If using OTG click 'select storage', select 'USB OTG'
Browse to the location of the ROM zip on the USB device, Select and wipe to confirm.
Follow on screen options
When flash is complete, click 'save logs' (in case you have any flashing issues)
Click finish
Reboot to System
After flash and setup, download and install Magisk Canary app from Magisk github; when you run for the first time the magisk will need to do some setup and will then automatically reboot the phone
after reboot you're all set, congratulations
Coming from another custom ROM
Spoiler: How to move from another Custom ROM to BeyondROM
CLEAN FLASH (recommended)
Load into TWRP
Do a full wipe
Reboot back into TWRP
Flash Beyond ROM
DIRTY FLASH (warning)
Dirty flash may or may not work, we cannot guarantee that flashing a ROM over the top of another rom will not give you any issues so it is therefore not our recommended choice, but obviously it's your device so feel free to do so if you like but please do not ask for help with problems if this causes you issues.
Updating BeyondROM to latest version
Spoiler: How to update BeyondROM to latest version
This is obviously very dependant on which version you are running, I.E if your version 1.0 jumping to 3.0, then there is a very high change that you will need to upgrade your phone FW to latest before flashing latest version of BeyondROM
Please take note of the changelog as i will note if you need to be on a certain version to flash this version or if dirty flash from previous version is ok
Where dirty flash is not possible and you do need to upgrade your FW to flash the latest these are the recommended steps.
It is assumed that you are already on BeyondROM.
Download the latest/required version of the firmware (Samfirm/Frija etc...)
Unzip the ROM
Rename the files and remove the .md5 from the end of the files
Boot phone into Download mode
Load up Odin, turn off auto-reboot
Insert the relevant files into their slots (BL = BL, AP=AP, CP=CP, CSC=HOME_CSC) **It's important to use HOME_CSC to keep your data intact**
In the USERDATA slot insert your TWRP+PatchedVBMETA tar file (Device Specific)
Start Flash
When complete keep USB plugged in, hold Volume Down + Power, as soon as the screen goes black hold Volume Up + Power to enter TWRP
When in TWRP, flash latest BeyondROM (select Dirty flash option)
When complete, save logs, reboot to system
Enjoy!
Andrei

reserved

Good to know. I will try this rom as soon as I buy the S21U

Nice! Pleasant to see the s21 Ultra exynos development is picking up more and more!!!

Hi thanks for the awesome ROM!! I loved beyond ROM on s10 plus!

nice, the secure flag disabled in screenshots. my favorite rom. thanks.

very nice rom. thanks

Wow nice features thanks hows battery life

Hello ZonalRipper
If I may some suggestions for next update:
-Long press back or recent buttons options like kill app
-Additional system fonts

Great to see roms emerging for S21. Wondering if Beyond will be supporting S21+ G996B?

CarbonX73 said:
Great to see roms emerging for S21. Wondering if Beyond will be supporting S21+ G996B?
Click to expand...
Click to collapse
You have just to test mate and you will see
There is a good chance that it works because this rom already supports s21 ultra and s21 models.
And Beyondrom on s20 models supported all 3 models.
Thank you to the original dev for his work !
You should create a new topic for your rom on S21 & (maybe S21+ ?) xda section too.

Chcolat-tiède said:
You have just to test mate and you will see
There is a good chance that it works because this rom already supports s21 ultra and s21 models.
And Beyondrom on s20 models supported all 3 models.
Thank you to the original dev for his work !
You should create a new topic for your rom on S21 & (maybe S21+ ?) xda section too.
Click to expand...
Click to collapse
ok thanks for the info

Hybrid Modpack for S20 & S21 Exynos Series with BeyondRom 14.09.2021​
Current Version: 1.6
Supported Devices: SM-G991B, SM-G996B, SM-G998B
Supported BeyondROM Version: 1.7
Supported Firmware Version: XXS3AUHD
Instructions:
Backup your System with TWRP. I'm not responsible for any damage.
Flash the Modpack via TWRP
Make sure you have selected the correct variant.
If you use Xposed and xposed modules, it might create some issues with the SystemUI Mods inside of the modpack. Be warned.
Please save the Aroma Log at the end of the Modpack installation. It might help for troubleshooting.
Let me know if something is abnormal or not working.
Spoiler: Content
Debloat:​- Debloat Google, Samsung and Misc Apps
Fixes:​
Samsung Dex Fix​
Mods:​- Audio:​
Viper4Android​
Stock​
- SystemUI:​
All SystemUi Mods incl. 3Minit Battery​
DisabledWarnings+MultiTile​
DisabledWarnings+MultiTile+CircularBattery​
Stock​
- Fonts:​
Modded Samsung Sans​
Google Product Sans​
Stock​
- Streaming:​
Streaming Mod for Amazone Prime and Netflix SD​
Stock​
- Multimedia:​
Youtube Vanced​
Stock​
- CSC_Change:​ You can change the CSC if you want to
CSCFeatures:​
Override Data Icon​
Enable Wifi Advanced Menu​
Disable AntiMalware​
Set Color of Days to XXXXXBR​
Enable Shutter Sound Menu in Camera​
Enable Camera during Calls​
Enable SMS Notification Popup in Camera​
Provider for unknown Number​
Enable LTEOnly in Network Menu​
Enable Realtime Networkspeed​
Quicksetting Toggles​
Enable Callrecording​
Enable Protection for Recent Apps​
Disable Knoxguard​
Enable eSIM Support​
Enable Applock​
Enable Data Usage on Quickpanel​
Spoiler: Additional Notes
For Viper4Android how will need to activate Legacy Mode in it
Streaming Fix doesnt activate Netflix HD on rooted devices
Some CSCFeatures aren't working anymore on Android 11
If you want to download additional Battery Icon then look here:
Here
Thanks for @gharrington for this
Spoiler: Credits
@starbucks2010
@ZonalRipper
@ianmacd
@gharrington
@afaneh92
@exocetdj
@zidane02 for some help
@Grouxho
S20 & S21 Testing Crew
Spoiler: Changelog
1.0: Initial Version
1.1: Added Support for SM-G996B
Some Script corrections
1.2: Removed BT and Safetynet Fix, not needed
Added Samsung Free to Debloat / Bloat List
Viper4Android works now with stock kernel too
1.3: Removed Option to Restore Bloatware (no one is using this)
Added 2 more Mods:
1. Disabled low Battery Warning
2. Possible to use camera flashlight on low battery level
1.4: Updated S21 SystemUI Mods to BeyondROM 1.3 based on XXU3AUF2 Firmware
Updated S20 SystemUI Mods to BeyondROM 3.4 based on XXS8DUE4 Firmware
Added MultiTile Mod
Updated Samsung Dex Fix
1.5: Updated S20 SystemUI Mods to BeyondROM 3.5 based on XXU8DUF9 Firmware
Updated S21 SystemUI Mods to BeyondROM 1.5 based on XXU3AUG4 Firmware
Removed 3Minit Clock
1.6: Updated S20 SystemUI Mods to BeyondROM 3.7 based on XXU9DUH5 Firmware
Updated S21 SystemUI Mods to BeyondROM 1.7 based on XXS3AUHD Firmware
Added Circular Battery
Added SystemUI-Mods + Stock for each variant of S20 & S21 series
Possible to Reinstall AR Apps
Spoiler: Download Links
GDrive
MEGA
MediaFire
Have Fun!

CarbonX73 said:
Great to see roms emerging for S21. Wondering if Beyond will be supporting S21+ G996B?
Click to expand...
Click to collapse
S21+ [G996B] is currently in testing

vegetaleb said:
Hello ZonalRipper
If I may some suggestions for next update:
-Long press back or recent buttons options like kill app
-Additional system fonts
Click to expand...
Click to collapse
The BACK button to kill app in it self if almost enough reason to switch to this ROM!!!!
And that MODPACK in the above post is also quite attractive!!

Can anyone give feedback for this rom? I want to try but hesitant for having to set up everything all over again.

vibrantliker said:
Can anyone give feedback for this rom? I want to try but hesitant for having to set up everything all over again.
Click to expand...
Click to collapse
Are you currently on KETAN?

babyboy3265 said:
Are you currently on KETAN?
Click to expand...
Click to collapse
no, stock

ZonalRipper said:
S21+ [G996B] is currently in testing
Click to expand...
Click to collapse

[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.

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