Develop Bugs

[G800F][ROM][5.0.2][LRX22G] CyanogenMod 12.0 for G800F [Alpha 23/03/2015]

This is a CyanogenMod 12 ROM for the Exynos3470 based Samsung Galaxy S5 mini (G800F).
DO NOT USE IT FOR G800H/M/... OR YOU WILL BRICK YOUR DEVICE
Although G800F and G800H share the same name they are not related in terms of hardware due to the different SoCs used (Exynos vs. Snapdragon).
Hence please do not ask for support or ROMs for the G800H or G800M here.
Working features
Receiving and making calls
Hardware sensors (Light, Orientation, Compass, Proximity, Acceleration)
Audio
Bluetooth
Wifi
HW accelerated GUI
USB-OTG (Keyboard, Mouse, USB-Audio, Mass-Storage)
Camera (pictures+video: Back+Front)
MTP storage
IR
GPS
NFC
Known-issues:
Capacitive lights are blinking in standby mode
Touchscreen unresponsive for some seconds after resume from standby mode
Non-working features:
Fingerprint scanner (no app for tests found)
Pulse sensor + Step counter (no app for tests found)
SELinux
Disclaimer:
You flash this image at your own responsibility. I am not responsible for any damage that might be caused by flashing this image (bricked device, lost data, ...)
Flashing this kernel image will trigger the KNOX counter, so your warranty will be void.
The image is only for S5 Mini SM-G800F (Exynos)
It might be instable, crash your device, drain your battery, or even might damage your smartphone (e.g. if an USB-OTG device drains too much power)
Backup your data before flashing and check if the original firmware is present (e.g. at SamMobile)
Click to expand...
Click to collapse
Before you start:
Backup your data, like call history, contacts, sms, WhatsApp messages, favourite app settings that are on internal and external sd (by using Titanium Backup or other apps available on PlayStore). At least all internal data will be lost in any case. If you have bad luck you might also loose data from your external sd card.
!!! Development of this ROM is discontinued in favor of the CM 5.1 ROM !!!
This means that known issues will not be fixed. It is not recommended to use this ROM anymore.
The downloads have been removed and fully replaced by the 5.1 version. You can find the new CM 5.1 ROM here
Download:
Odin3-v3.07 (it is contained in CF-Auto-Root)
TWRP 2.8.5.0 recovery image [Updated 23/03/2015] (MediaFire Mirror)
CM12 rom for G800F (MediaFire Mirror)
Google Apps from here (for Google Play, ...). Select the package that suits you best. If you do not need all of the Google services the Micro edition is enough (BasketBuild Mirror for Micro edition).
Install recovery:
Reboot your device into Odin mode: turn off your device, then press Volume-Down + Home + Power button at the same time and release them.
Confirm the following warning message with the Volume-Up button.
Connect your device to your PC via USB
Make sure the device driver's are installed on your PC
Start Odin
In Odin select PDA and select the recovery image (recovery.tar.md5)
Check that only "Auto Reboot" and "F. Reset Time" is set
Click on "Start": the kernel image should be flashed now and the device should reboot afterwards. By flashing the recovery, your warranty will be void.
After the recovery flashing process was successful, power of your device. If not restart into Download mode and flash again or flash the stock rom.
Before you flash:
You need the latest TWRP recovery [Updated 23/03/2015]. Otherwise TWRP might not be able to flash the ROM. This is because TWRP checks now if the device is "supported".
G800M/G800Y are not supported but are not blocked as the ROM might work on these (Exynos3470 based) devices. Only flash the ROM on a G800M/Y if you know what you do. Do not expect help if something went wrong.
Wipe the device to avoid problems with remaining files from the old installation (see instructions below). This also applies if you already installed an older version of CM12.
Flash CM12:
Reboot into recovery mode (Press Volume-Up + Home + Power button)
If you come from a stock rom, this is your opportunity to make a Backup of your phone(Backup, then select Boot, System, Data, then swipe to backup). Note that the recovery might fail to restore the backup when you want to go back to the stock ROM (for me it got stuck after a restore during boot. But the backup was made with a different version of TWRP, so it might work in general) - simply do not expect too much of it at the moment.
If you haven't copied the installation files yet, you can now copy the GApps and CM12 zip to your internal sd or external sd (be careful not to put the files into the data directory of the internal sd card as this will be deleted in the next step). Be sure that MTP is enabled (inside Mounts, click on Enable MTP), then, from your pc, copy the files. If MTP does not work from recovery, try it directly from Android or remove the external sd card from the phone and put it into your PC.
Wipe Dalvik Cache, Cache, System and Data (inside Wipe -> Advanced Wipe). Do not report problems if you did not wipe those partitions as the problems are most probably related to this!
Install the CM12 rom zip-package
Install the GApps zip-package
Reboot the system and enjoy a Lollipop
How to root:
No SuperSu is needed as CM12 already comes with integrated root support. Root access is disabled by default.
You normally do not need root access. If you want to activate root access for apps, do the following:
Open the Settings menu, select "About Phone"
Tap on the "Build number" entry seven times. You should be notified, that the developer settings are now active.
Open the Settings menu, select "Developer options". Enable root access by selecting "Apps" in the "Root-Access" setting.
In case you want to go back to the stock ROM:
lf you do not have the latest ROM for the G800F you can download it from SamMobile
Reboot your phone into Odin mode
Open Odin on your PC and connect your smartphone with your PC via USB
If you have a zip-file unzip it so that you have a .tar.md5 file
In Odin click on the PDA button and select the .tar.md5 file. Then press "Start".
Normally the stock rom fails to boot as the data from CM12 is still on the data partition. So after flashing the stock rom, reboot into recovery mode (it looks a bit different now). First wipe the data partition, then wipe the cache.
Reboot
Changelog
Code:
23-03-2015:
* Fixed non-working mic on incoming call issue
* Fixed non-working menu-button
* Synchronized with latest CM12 sources
This section is for developers:
A script to setup the build environment can be found here:
Code:
https://github.com/tobigun/kminilte-patcher
Sources:
Code:
https://github.com/cm-3470/android_device_samsung_kminilte
https://github.com/cm-3470/android_vendor_samsung_kminilte
https://github.com/cm-3470/android_kernel_samsung_kminilte
https://github.com/cm-3470/android_device_samsung_smdk3470-common
Thanks to Unjustified Dev from Team Regular. As the S5 mini (G800F) and the Galaxy Light are quite similar we worked on this together.
XDA:DevDB Information
[G800F][ROM][5.0.2][LRX22G] CyanogenMod 12.0 for G800F [Alpha 23/03/2015], ROM for the Samsung Galaxy S5 Mini
Contributors
hennymcc, Unjustified Dev
Source Code: https://github.com/cm-3470
ROM OS Version: 5.0.x Lollipop
ROM Kernel: Linux 3.4.x
ROM Firmware Required: TWRP Recovery [version from 2015-03-23]
Based On: CyanogenMod
Version Information
Status: Alpha
Created 2015-03-03
Last Updated 2015-04-15

FAQ
Question:
I'm trying to flash this rom but it says to me: "This package is for kmniltexx, kminiltedv, kminilteub; this device is kminilte. E:Error executing updater binary zip ...."
Answer:
The device names were changed with the newest CM12 build to be able to distinguish between G800F (kmniltexx), G800Y (kminiltedv) and G800M (kminilteub) as all of them are kminilte devices. The new builds of TWRP and CM12 detect the correct device at runtime.
Older TWRP releases (for example that of RVR in another XDA thread) still detect the device as kminilte (instead of kmniltexx,...) and hence are not able to install the new CM 12 releases so please do not install RVR's TWRP if you want to install CM 12. Always use the TWRP image linked in the first post of this thread.

For future use

Thanks for great job. Looking forward to testing it soon!!

I also want to say BIG THANX!
My Phone now makes a backup and than i flash your rom
stiff

I just noticed that the mic is muted on incoming calls. If you want to use the phone for daily use you should not the flash the ROM.

I flashed it already and can confirm, that the mic is off.
But it looks good so far. :good:
stiff

stiffmeister75 said:
I flashed it already and can confirm, that the mic is off.
But it looks good so far. :good:
stiff
Click to expand...
Click to collapse
It works for outgoing calls so I did not notice it before.

Do you know a workaroud?
btw. can you provide a patch with a fix?
or is it necessary to build a new rom?
stiff

sorry my noob question: is this ROM going to be listed in the CM12 nightlies or how will it work? is it an unofficial one yet or... thanks

wabre said:
sorry my noob question: is this ROM going to be listed in the CM12 nightlies or how will it work? is it an unofficial one yet or... thanks
Click to expand...
Click to collapse
It is not official and there won't be nightlies. At the moment there are no plans to get it into the official repo.

stiffmeister75 said:
Do you know a workaroud?
btw. can you provide a patch with a fix?
or is it necessary to build a new rom?
stiff
Click to expand...
Click to collapse
There is some work on this at the moment but no fix yet. Seems as if the audio implementation has to be adjusted a bit. I don't know how much work there is left. As this is a spare time project, this might take some time.
When it works there will be a new ROM for download.

Hey there, been using the rom for a couple hours and I must say, you've done a great job ! The interface is faster than stock touchwiz, and everything runs really smoothly ! I've only encountered two small issues (apart from the incoming call muted mic) :
-when waking up the device, the lockscreen seems to freeze itself (touch doesnt respond), so to fix it, you have to press power button and wake it up again (happened sometimes)
-noticed something strange: while the phone is asleep, the capacitative buttons would blink (they turn on for like 1sec and then turn itself off like a notification light). I'm pretty sure you'll be able to fix it, as it might be kernel related.
-(edit) and I've just realised that the left menu capacitive button doesn't work (but you probably already know this)
other than that, this rom is flawless for an Alpha ! Great job buddy
I was able to score 23 000 pts on Antutu vs 20 000 pts with stock 4.4.2 lol

I have found an issue with the capacitive buttons on the bottom. I was not able to deactivate the lightning and some other settings does not work aswell..
But all in all great alpha, I really enjoyed it ?
Sent from my SM-T530 using XDA Free mobile app

Omg! For my phone!
How cool! I will wait for beta i think...but keep up the good work, i will use it someday
And ill try to help to get ppl to know this thread

basic086 said:
-(edit) and I've just realised that the left menu capacitive button doesn't work (but you probably already know this)
Click to expand...
Click to collapse
Will be fixed with the next build.

i can confirm, that somethimes the capacitive buttons doent work/react.
and the bigger problem is that the micro doent work. (worst problem for me)
and one more problem... the sound on my alarm somethimes got some glitches/sound stops too.
i'll backup the new CM12 and than restore my old backup back... until these errors are fixed.
but, most important, very good work! respect. can i give you a donation ?

E:signature verification failed
what to do?

Hi,
great work!
I also can confirm that the mic for incoming calls does not work and it also doesn't work for either incoming or outgoing calls when using a headset. Haven't used a bluetooth headset yet but will test it later that day.
Many thanks so far for this built and I hope the mic bugs won't be a big deal.
Cheers,
lotherk

bebe.fier said:
E:signature verification failed
what to do?
Click to expand...
Click to collapse
You have a G800F and not a G800H or another variant?
If it is a G800F try to reflash it, maybe somethin went wrong. What is the stock ROM you currently have installed? Is it the newest one - can you give me the version number?

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

LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review.
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
* Submitting bug reports on nightly builds is the leading
* cause of male impotence.
*/
WHAT WORKS
Boot
WiFi
Hotspot
Audio
RIL
Bluetooth
Sensors
FM
Camera
SDCard
GPS
KNOWN ISSUES
Video recording
VoLTE [Don't expect it to be working anytime soon]
SELinux Enforcing
!!! BUG REPORTS WITHOUT LOGS WILL BE IGNORED !!!
Android: adb logcat
Radio: adb logcat -b radio
Kernel: adb shell dmesg
Full Bugreport: Developer Menu -> Bugreport
HOW TO INSTALL LINEAGEOS
- Download the LineageOS zip(s). (see Downloads)
- Download the TWRP Image. (see Downloads)
- Copy the LineageOS zip to internal sdcard.
- Unlock bootloader and install TWRP from downloads.
- Boot into TWRP.
- Perform a backup of your current ROM. (Optional)
- IMPORTANT: Do a Factory Reset. (Wipe data & cache)
- Flash LineageOS.
- Optional: Install the Google Apps addon package. (see Downloads)
- Reboot
DOWNLOADS
LineageOS:
https://www.androidfilehost.com/?w=files&flid=203899
TWRP:
https://www.androidfilehost.com/?w=files&flid=203904
Google Apps:
OpenGApps (recommended: arm, 7.1.1, nano)
SOURCECODE
Device tree: https://github.com/ashwinr64/android_device_motorola_taido
Kernel: https://github.com/ashwinr64/android_kernel_motorola_mt6735
Vendor: https://github.com/ashwinr64/android_vendor_motorola_taido
HOW TO CONTRIBUTE
Use our code review system to send patches: https://review.lineageos.org
SUPPORT ME
Do you like my work? Consider donating me some beer!
​
XDA:DevDB Information
LineageOS for taido, ROM for the Moto E3
Contributors
ashwin007
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.x
Version Information
Status: Testing
Created 2017-08-03
Last Updated 2017-08-03

Changelogs
-> Build 1 [04-08-2017]
* Initial Public Release
* Merged upstream 3.18.63 kernel.
* Switched to XZ kernel compression and enabled -O2 flag.
* Widevine has been fixed, so DRM contents are playable.
-> Build 2 [16-08-2017]
* Synced with Lineage
* Merged upstream 3.18.65 kernel
* Hotspot fixed
* Added support for F2FS

Thanks a lot!

And the development starts again

Dear @ashwin007,
I'm so glad [emoji1] to see that you are working on taido.
I appreciate your brilliant work.
All the best

A fresh install of this ROM shows 14 GB used up by the system partition and negligible space in the data partition. Any solutions?

Not installing.
Code 7 error

bubba1601 said:
Not installing.
Code 7 error
Click to expand...
Click to collapse
use TWRP given by Ashwin, also check weather u did factory reset....
also follow the instructions....

spykarzzz said:
use TWRP given by Ashwin, also check weather u did factory reset....
also follow the instructions....
Click to expand...
Click to collapse
My Friend, I've been flashing Roms on various devices for more than three years.......
So I have done a factory reset, as I'm using another lineage OS version on my E3.
I followed all instructions.
So the TWRP version I'm using must be the issue, its the Dr framazone version 3.0.0.2, I can't flash the new twrp image in the twrp I'm using.
I'll have to try in fast boot mode through the PC.

U need deckers TWRP to flash dis particular Rom....Try this only!!!

One request, can you please add double tap 2 wake feature in the kernel?

spykarzzz said:
U need deckers TWRP to flash dis particular Rom....Try this only!!!
Click to expand...
Click to collapse
Yes, I know and understand that.
As I said in my previous comment, I cannot flash the newer twrp image through the version of twrp I'm using.
I've have now managed to flash the twrp image via fast boot and have this ROM up and running.
Unfortunately I've ran into many problems not seen in the other lineage OS ROM that I've been using for the last week.
1. Guest user was activated after initial set up, meaning I could not change any settings.
2. I cannot access my external SD card.
So important files to me are inaccessible?
3. No photographs taken using the camera are being saved, they just disappear from the gallery into thin air.
4. My service provider doesn't list in networks or the signal indicator (O2 UK) instead my device shows "23410"
Its at this point I confess to running this rom on my XT1700 and NOT a XT1706 (My device is in fact a European spec standard Motorola E3, but running E3 power firmware and renamed in system to a E3 power XT1706 - this was flashed by Motorola themselves during a repair as they claimed I had to pay for XT1700 firmwares, so E3 Power firmware was flashed by them.
Although I appreciate Ashwins efforts and i appreciate this is a testing version, I cannot use this ROM as I'm now also in trouble with my employer for not having photographic evidence of my work today (My E3 is used as my work device, and taking photos of my finished work is a requirement of my employment)
I have to now move to another ROM for this reason until these issues can be fixed and photos taken with the camera will be saved and stay saved.
Sorry.

Is there any issue with this rom
Pls let me know friends
I am waiting for a stable rom
Camera is working or not
Or any kind of bugs pls tell me

aman4512 said:
A fresh install of this ROM shows 14 GB used up by the system partition and negligible space in the data partition. Any solutions?
Click to expand...
Click to collapse
Bro do this....
U have to go to fastboot mode....
Then enter fastboot format userdata....
Then fastboot flash recovery.img
Then dont go to recovery let ur phone start....
Then enable usb debug & oem unlock in phone after rebooting...
Again switch of ur phone...
Now goto fastboot mode....
Type fastboot flash recovery .img
Now go to recovery and flash the rom file
It ll work 100%

solkarsalman said:
Bro do this....
U have to go to fastboot mode....
Then enter fastboot format userdata....
Then fastboot flash recovery.img
Then dont go to recovery let ur phone start....
Then enable usb debug & oem unlock in phone after rebooting...
Again switch of ur phone...
Now goto fastboot mode....
Type fastboot flash recovery .img
Now go to recovery and flash the rom file
It ll work 100%
Click to expand...
Click to collapse
Thanks, but I had solved the problem. The thing is my phone wasn't booting at all after flashing TWRP. Tried many version. It was some issue with the phone's boot.img (some Lenovo phone has a similar issue, K4 power I think). I flashed a stock ROM and after flashing TWRP, I flashed SuperSU, since it patches boot.img. That worked, after which I wiped /system, /data, /cache and flashed Lineage.

bjyadav4 said:
Is there any issue with this rom
Pls let me know friends
I am waiting for a stable rom
Camera is working or not
Or any kind of bugs pls tell me
Click to expand...
Click to collapse
Read the comments above you own
Don't install it, I had major issues.
Read previous comments before posting.

bubba1601 said:
Yes, I know and understand that.
As I said in my previous comment, I cannot flash the newer twrp image through the version of twrp I'm using.
I've have now managed to flash the twrp image via fast boot and have this ROM up and running.
Unfortunately I've ran into many problems not seen in the other lineage OS ROM that I've been using for the last week.
1. Guest user was activated after initial set up, meaning I could not change any settings.
2. I cannot access my external SD card.
So important files to me are inaccessible?
3. No photographs taken using the camera are being saved, they just disappear from the gallery into thin air.
4. My service provider doesn't list in networks or the signal indicator (O2 UK) instead my device shows "23410"
Its at this point I confess to running this rom on my XT1700 and NOT a XT1706 (My device is in fact a European spec standard Motorola E3, but running E3 power firmware and renamed in system to a E3 power XT1706 - this was flashed by Motorola themselves during a repair as they claimed I had to pay for XT1700 firmwares, so E3 Power firmware was flashed by them.
Although I appreciate Ashwins efforts and i appreciate this is a testing version, I cannot use this ROM as I'm now also in trouble with my employer for not having photographic evidence of my work today (My E3 is used as my work device, and taking photos of my finished work is a requirement of my employment)
I have to now move to another ROM for this reason until these issues can be fixed and photos taken with the camera will be saved and stay saved.
Sorry.
Click to expand...
Click to collapse
I didn't face any of the above issues on my Moto E3 Power. Camera is working fine and photos are also saving.
SD card is also accessible.
---------- Post added at 07:34 AM ---------- Previous post was at 07:30 AM ----------
bjyadav4 said:
Is there any issue with this rom
Pls let me know friends
I am waiting for a stable rom
Camera is working or not
Or any kind of bugs pls tell me
Click to expand...
Click to collapse
Camera is working properly.
If you do this
Thanks, but I had solved the problem. The thing is my phone wasn't booting at all after flashing TWRP. Tried many version. It was some issue with the phone's boot.img (some Lenovo phone has a similar issue, K4 power I think). I flashed a stock ROM and after flashing TWRP, I flashed SuperSU, since it patches boot.img. That worked, after which I wiped /system, /data, /cache and flashed Lineage.
Click to expand...
Click to collapse
then storage problem will also be solved.

aman4512 said:
A fresh install of this ROM shows 14 GB used up by the system partition and negligible space in the data partition. Any solutions?
Click to expand...
Click to collapse
Is this the actual screenshot? Because the developer has mentioned that LTE is not working but the screenshot shows LTE in the notification bar.

ranjithgn said:
Is this the actual screenshot? Because the developer has mentioned that LTE is not working but the screenshot shows LTE in the notification bar.
Click to expand...
Click to collapse
LTE works, VoLTE doesn't.

precedentbrute said:
I didn't face any of the above issues on my Moto E3 Power. Camera is working fine and photos are also saving.
SD card is also accessible.
---------- Post added at 07:34 AM ---------- Previous post was at 07:30 AM ----------
Camera is working properly.
If you do this
then storage problem will also be solved.
Click to expand...
Click to collapse
Thank you for your feedback, although I can't share your optimism or your confidence.
I've now reflashed this rom three times.
I cannot access external storage.
Photos disappear from the gallery, and now all my Google apps keep force closing - I'm using the recommendation of Google apps, open gapps nano arm.
Remember just because it's all good for you doesn't necessarily mean it's good for others, as I've seen so many times in these forums.
Regards.

[TWRP|ROM] C8/SM-C7100/jadeltechn C7100ZHU1ARB1 [Apr/20/2018]

Test twrp build for this mediatek device (SM-C7100). Post logs etc so I can help solve issues when I am available to do so.
TWRP download: https://www.androidfilehost.com/?fid=673956719939834043
SM-C7100_C7100ZHU1ARB1.zip: https://www.androidfilehost.com/?fid=673956719939834050
Kernel download: https://www.androidfilehost.com/?fid=746010030569970527 April, 23rd, 2018
Sources
Kernel source: https://github.com/travismills82/android_kernel_samsung_mt6757
TWRP device tree: https://github.com/travismills82/twrp_android_device_samsung_jadeltechn
Kernel Features
Knox Disabled
DM-Verity Disabled
Tima Disabled
More TCP congestion control algorithms
Remove verifiedbootstate flag from /proc/cmdline (for safety net)
Conservative gov enabled
Always enforce selinux disabled
Fsync on/off Toggle
Ninendo Wiimote support
+ More not listed check git changes for a full list
Regards,
Travis82

Hi it didn't work... I think this is for J7 plus only and please Help after flashing the custom recovery my boot logo of C8 is gone.... Please help

I have tried to install using odin and it says on the phone a chinese message,which i translated with google, that read your phone needs to be unlocked to install a custom operating system, even though i enabled oem unlock and usb debugging. I used viper4android on my old phone and its annoying that im not able to install it on my new one.
Please help me when you get time:good:

the twrp cannot mount data partition unless format it first. and my device is sm c7100.

I can't install twrp in the first place.
How did you guys install it.

I managed to install twrp with odin after unlocking bootloader with crom service and disabling frp lock but when i try to boot into it there's nothing. It just boots into android. Tried installing it again. I tried adb reboot recovery but that booted to the official samsung recoveryb even though i installed twrp. How to fix this??

How to use the TWRP with Android Oreo?

Gautam488 said:
I managed to install twrp with odin after unlocking bootloader with crom service and disabling frp lock but when i try to boot into it there's nothing. It just boots into android. Tried installing it again. I tried adb reboot recovery but that booted to the official samsung recoveryb even though i installed twrp. How to fix this??
Click to expand...
Click to collapse
Brother how do you manged to unlock bootloader...? Please share with us

google play gives an error, the installation screen is not constantly installing

Hi everyone,
For those who have tried, could you please confirm whether the files are working or not.
Since there is no steps and instructions, can someone post the the procedure/code used for flashing kernel and TWRP?
Thanks

I finally tested everything out. Please feel free to take the command for reference.
Disclaimer:
1. Warranty would be voided and I am not responsible for any:
- Bricked device
- Data loss. So PLEASE BACKUP and you will definitely lose all your data during the rooting process.
2. I am not the one who build the files such as Kernel and TWRP img
Donation:
- BUT I am the one spending the time to test the files out. So, if you are happy with my work, please donate. I am happy for whatever (I mean the amount) support you give me.
- Bitcoin address: bc1qzvv3wrfj0furpzhdfxvzp07gy7whan907045gn
Aim:
1. Since Samsung Galaxy C8 has only 64GB of internal storage, 1000% sure it is not enough for using in 2021 onwards -> We need data and obb to SD card
2. MediaTek Hellio P20 is not powerful enough for using in 2021 onwards -> Need some CPU tweak
-> So, IT CAN’T BE USED WITHOUT ROOT
3. Makes Android great again
Summary:
- Both TWRP and Kernel, posted by Travis82 are definitely working for Samsung Galaxy C8 since I have tested them out and using them but they are only for Android 7.1.1 and not for stock Android 8.1.
- The files are NOT tested with Custom Rom.
- The reason why I said the Kernel is also for Android 7.1.1 because you need TWRP for flashing.
Procedure (For Android 8.1 user) NOT RECOMMENDED:
- First of all, Android 8.1 is SERIOUSLY NOT RECOMMENED for Samsung Galaxy C8 as nothing much you can do even though you are rooted. (i.e. XInternalSD causes bootloop)
- As mentioned above, both TWRP and Kernel posted by Travis82 are not compactable with Android 8.1
- For Android 8.1 user, it is recommended to downgrade to Android 7.1.1 with Odin.
- If you still want to use Android 8.1 and root, follow the guide in the link below using Magisk. Just follow the section for Samsung is good enough:
https://www.xda-developers.com/root/amp/
Procedure (For Android 7.1.1 user) RECOMMENDED:
Unlock bootloader + Enable developer mode -> USB debug + Prepare a SD card and put both Kernel and Magisk zip to the SD card
Applying TWRP recovery
Compress the recovery image to a .tar archive using 7-Zip
Install 7-zip
Right-click on recovery.img
“7-zip”
“Add to archive”
Select “tar” for “Archive format”
Flashing the recovery tar archive in Odin
Download, install and open Odin (I use Odin3 v3.13)
Unclick/Deselect “Auto Reboot” and “F. Reset Time” under “Options”
Enter Download mode
Power off, Power button + Volume Down + Home button, connect your PC
Flash the recovery tar archive in AP slot
When done flashing, unplug the device and enter recovery mode.
Power button + Volume Up + Home button, when the screen goes blank quickly, Power button + Volume Down + Home button.
If you can’t boot to recovery in this way, use ADB. “adb reboot recovery”
Applying new Kernel and Magisk
If storage can’t be mounted in TWRP (i.e. 0MB), consider changing the SD card or see this post: https://forum.xda-developers.com/t/...rnal-storage-0mb-in-twrp-permanently.3830897/ To be honest, there are lots of ways to fix this problem. Find the one best fit for you.
Flash Kernel zip in TWRP as usual
Flash Magisk zip in TWRP as usual
Reboot and wait, it takes quite a long time to boot
NOT DONE yet. You will probably face a serious problems in this stage:
Wifi passwords and Bluetooth connections can’t be saved
To solve this problem -> Install “Libsecure_Storage” in Magisk
DONE
Want Xposed? -> Search for the one for Android 7.1.1
Want app data to SD card? -> ExSDCard Access Enabler (Magisk) + XInternalSD (Xposed)
Want app obb to SD card? -> ExSDCard Access Enabler (Magisk) + Obb on SD (Xposed)
Want ram (swap), CPU tweak? -> App2SD
Want to reward me for my hard work? -> Donate
Bitcoin address: bc1qzvv3wrfj0furpzhdfxvzp07gy7whan907045gn
If you found anything on top of these things, please share.

toto4c19 said:
I finally tested everything out. Please feel free to take the command for reference.
Disclaimer:
1. Warranty would be voided and I am not responsible for any:
- Bricked device
- Data loss. So PLEASE BACKUP and you will definitely lose all your data during the rooting process.
2. I am not the one who build the files such as Kernel and TWRP img
Donation:
- BUT I am the one spending the time to test the files out. So, if you are happy with my work, please donate. I am happy for whatever (I mean the amount) support you give me.
- Bitcoin address: bc1qzvv3wrfj0furpzhdfxvzp07gy7whan907045gn
Aim:
1. Since Samsung Galaxy C8 has only 64GB of internal storage, 1000% sure it is not enough for using in 2021 onwards -> We need data and obb to SD card
2. MediaTek Hellio P20 is not powerful enough for using in 2021 onwards -> Need some CPU tweak
-> So, IT CAN’T BE USED WITHOUT ROOT
3. Makes Android great again
Summary:
- Both TWRP and Kernel, posted by Travis82 are definitely working for Samsung Galaxy C8 since I have tested them out and using them but they are only for Android 7.1.1 and not for stock Android 8.1.
- The files are NOT tested with Custom Rom.
- The reason why I said the Kernel is also for Android 7.1.1 because you need TWRP for flashing.
Procedure (For Android 8.1 user) NOT RECOMMENDED:
- First of all, Android 8.1 is SERIOUSLY NOT RECOMMENED for Samsung Galaxy C8 as nothing much you can do even though you are rooted. (i.e. XInternalSD causes bootloop)
- As mentioned above, both TWRP and Kernel posted by Travis82 are not compactable with Android 8.1
- For Android 8.1 user, it is recommended to downgrade to Android 7.1.1 with Odin.
- If you still want to use Android 8.1 and root, follow the guide in the link below using Magisk. Just follow the section for Samsung is good enough:
https://www.xda-developers.com/root/amp/
Procedure (For Android 7.1.1 user) RECOMMENDED:
Unlock bootloader + Enable developer mode -> USB debug + Prepare a SD card and put both Kernel and Magisk zip to the SD card
Applying TWRP recovery
Compress the recovery image to a .tar archive using 7-Zip
Install 7-zip
Right-click on recovery.img
“7-zip”
“Add to archive”
Select “tar” for “Archive format”
Flashing the recovery tar archive in Odin
Download, install and open Odin (I use Odin3 v3.13)
Unclick/Deselect “Auto Reboot” and “F. Reset Time” under “Options”
Enter Download mode
Power off, Power button + Volume Down + Home button, connect your PC
Flash the recovery tar archive in AP slot
When done flashing, unplug the device and enter recovery mode.
Power button + Volume Up + Home button, when the screen goes blank quickly, Power button + Volume Down + Home button.
If you can’t boot to recovery in this way, use ADB. “adb reboot recovery”
Applying new Kernel and Magisk
If storage can’t be mounted in TWRP (i.e. 0MB), consider changing the SD card or see this post: https://forum.xda-developers.com/t/...rnal-storage-0mb-in-twrp-permanently.3830897/ To be honest, there are lots of ways to fix this problem. Find the one best fit for you.
Flash Kernel zip in TWRP as usual
Flash Magisk zip in TWRP as usual
Reboot and wait, it takes quite a long time to boot
NOT DONE yet. You will probably face a serious problems in this stage:
Wifi passwords and Bluetooth connections can’t be saved
To solve this problem -> Install “Libsecure_Storage” in Magisk
DONE
Want Xposed? -> Search for the one for Android 7.1.1
Want app data to SD card? -> ExSDCard Access Enabler (Magisk) + XInternalSD (Xposed)
Want app obb to SD card? -> ExSDCard Access Enabler (Magisk) + Obb on SD (Xposed)
Want ram (swap), CPU tweak? -> App2SD
Want to reward me for my hard work? -> Donate
Bitcoin address: bc1qzvv3wrfj0furpzhdfxvzp07gy7whan907045gn
If you found anything on top of these things, please share.
Click to expand...
Click to collapse
Libsecure storage cannot be downloaded from anywhere could you please provide me link for the module

toto4c19 said:
For Android 8.1 user, it is recommended to downgrade to Android 7.1.1 with Odin.
Hello, thx for all your hard work.
Click to expand...
Click to collapse
My C8 is 8.1 tried resetting back to factory, still 8.1
Noted your comment re ODIN, but I use Linux, Odin seems Win only.
Have successful rooted and installed Lineage on an old Note 3, but I didn't have to downgrade that!
Can you give me please, some guidance how I can return this wretched thing back to 7.1?
Actually, I am suspecting return is the wrong word as it may have come with 8.1 installed.
I'm a bit lost at this point.
Cheers
p

[ZE620KL/Android 9][TREBLE] COMPLETE GUIDE: Unlocking, Rooting & Flash GSI + Fixes

[ZE620KL/Android 9][TREBLE] COMPLETE GUIDE: Unlocking, Rooting & Flash GSI + Fixes
Unlocking bootloader to Flashing GSI (Asus Zenfone 5 [ZE620KL] / Android 9.0)
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
About :
The last guide could leads to soft brick, as the instructions were not clear nor the files not supported for Android 9.0.
Here is a complete guide with TWRP 3.3.0 for Android 9.0, clear instructions and multiple fixes for GSI.
It has been tested on stock version v16.0615.1903.92.​
Requirements :
- A stock version V16.0610.XXXX.XX or higher
- A phone on Android 9.0 (not 8.0!)
- A fully working USB cable
- Latest ADB / Fastboot drivers
- Bootloader unlocker (download latest from Asus website or from here)
- TWRP 3.3.0 image
- Android9EncryptionDisablerZE620KL.zip
- Magisk v19.3​
Instructions :
Unlocking Bootloader
1. Backup all your important data.
2. Install the bootloader unlocker APK, and follow the steps. You will loss your warranty here, and it will factory reset your data
3. If there is any issue here, go into your stock recovery (volume down + power button) and factory reset.​
Installing TWRP
4. Shutdown your device & boot in fastboot mode using volume up + power button.
5. Check that the connection between your device and your computer by typing this in your command line :
Code:
fastboot devices
6. Flash TWRP recovery using :
Code:
fastboot flash recovery <twrp_name>.img
7. Now reboot in recovery mode using :
Code:
fastboot oem reboot-recovery
8. In TWRP, select Wipe > Format Data > enter "yes" and confirm
9. Return to the main menu, select Reboot > Recovery
10. Do 8. & 9. and again
11. Using TWRP or ADB, install Android9EncryptionDisablerZE620KL.zip (on TWRP, go into Install > find Android9EncryptionDisablerZE620KL.zip > Install zip)
If everything has gone successfully, you now have a custom recovery.
As for some GSIs, a patched boot partition may cause bootloop, you should try installing Magisk after installing the GSI. If you want to keep your stock ROM, go directly to "Magisk Installation" section.​Installing a GSI
This step may vary depending on the different GSIs distribution. I assume you install Havoc OS v2.7 GSI which actually works on this device.
1. Backup all your important data using TWRP backup.
2. Select the arm64-aonly GSI image you want, and move it on your external SD.
3. Wipe Data, Dalvik, and Cache.
4. Go back in the main menu of TWRP, and reboot to recovery.
5. Remove Magisk if it was previously installed, by using its uninstaller script.
6. Flash the GSI to system partition.
7. Boot and perform a factory reset.​
Installing Magisk
1. Add the Magisk zip archive to your external storage.
2. Boot into TWRP recovery, and install the zip.
3. Enjoy!​
Bug fixes:
Insufficient storage in the system partition to flash GApps : Download your OpenGApps archive on your external SD, and use MagicGApps 2018.9.23 to install GApps.
Auto-Brightness doesn't work: Download framework-res__auto_generated_rro.apk from here.
Using a root explorer or command-line, push the APK to /vendor/overlay.
Then run the following command in a rooted terminal or ADB shell:
Code:
chcon u:object_r:vendor_overlay_file:s0 /vendor/overlay;chcon u:object_r:vendor_overlay_file:s0 /vendor/overlay/framework-res__auto_generated_rro.apk
My camera doesn't work well (green tint on face camera) and/or the app doesn't boot: If Asus Camera doesn't launch on your GSI, you should probably edit your /system/build.prob file.
You need to edit ro.product.model, ro.product.brand, ro.product.name, ro.product.device, ro.product.manufacturer & ro.build.product properties to be:
Code:
ro.product.model=ASUS_X00QD
ro.product.brand=asus
ro.product.name=WW_Phone
ro.product.device=ASUS_X00QD
ro.product.manufacturer=asus
ro.build.product=ZE620KL
You can instead use Google Camera mod (port from Arnova8G2 & modded by 5Z community, thanks to them!), which works well (edit: there is a bug on HavocOS, we can't access settings).​Bonus:
- You can reinstall DTS Headphone:X here.
- For booting your kernel in Permissive mode, check here
Sources:
TWRP 3.3.0 : On GitHub
If you need help or if you want to help on ZE620KL development go here:
https://t.me/Zenfone5Dev
(We will continue to update & help here though.)
Many thanks to all of the Zenfone 5 community (particularly Emincan, Pandolfi and Lmajkej),
Phhusson & Erfan for their works on GSI, and Shakalaca for its work on TWRP 3.3.0!​

On HavocOS v2.8 GSI (13-08-2019):
It works:
- Almost anything
- Adaptive Brightness (after manual fix)
- Notch overlay
- DTS Headphone X (after manual installation)
- NFC
- Face unlock
- Stock camera (after manual fix)
- Magisk
- SDcard access
It doesn't works:
- VoLTE / VoWifi
- Google Camera settings
- External speaker amplifier (NXP amp)
- APT-X / APT-X HD bluetooth
- Low microphone in normal use
- No microphone in calls (only headphone microphone works)

GCam settings
But my google camera keep crashing when I want to go into camera settings

Hi thanks for this tutorial, this is my first time rooting my phone. I'm encountering a problem with my sd card after installing havoc os, everytime i try to move, save or any write functionality i do to my sd card, it always says the android version isn't compatible. I could still see my files from my sd, but everytime it asks permission it always say this

bentley0928 said:
But my google camera keep crashing when I want to go into camera settings
Click to expand...
Click to collapse
Same issue here. I will update the thread when I will find a more working GCam port (perhaps, this GCam port works well on ZenUI)
Jolo110 said:
Hi thanks for this tutorial, this is my first time rooting my phone. I'm encountering a problem with my sd card after installing havoc os, everytime i try to move, save or any write functionality i do to my sd card, it always says the android version isn't compatible. I could still see my files from my sd, but every time it asks permission it always say this
Click to expand...
Click to collapse
It's a known issue, the GSI maintainer @vince31fr is working on it. I don't have it, but I can advice you to use Solid File Manager, which works like a charm on my device.

"- No microphone in calls (only headphone microphone works)"
Funny... I'm on stock latest firmware and I have this issue, so I thought I try something new, and this has that issue. It can't be a coincidence. Something is ****ed up with this device.

Wonder if this will work for the Zenfone 5 Lite (or 5Q)? I wanna root my 5Q so bad haha

Thanks for the great instructions! Steps 1 through 11 worked perfectly for me, then I installed LineageOS (lineage-17.0-20191231-UNOFFICIAL-treble_arm64_avN.img) and it works properly. Then when I go back to TWRP and install Magisk v20.1 it reboots into an endless Lineage bootup logo animation (not boot loop). I can get an adb shell, but now also the external SD card has become invisible. Any suggestions?
UPDATE: I switched over to the patched Magisk version from PHH (https://forum.xda-developers.com/zenfone-5/general/ze620kl-add-support-to-evey-android-9-t3966918) and everything works perfectly now!

Hi!! I thanks for these instructions you gave. I know this post is a bit older. But is the only one I think could help me.
I got an ZE620KL and I'm trying to root this device. I have some experience in unlocking bootloader and rooting devices. But this one... Is giving me a lot of work. Researching in a lot of forums and websites I tried a lot of things with no success. In theory, is just install the official apk provided by ASUS and run the application. But the app doesn't work for a long time as I researched (error accusing network problem). I tried unlock via fastboot commands but I always got stucked by "remote: permission denied" even with latest drivers and ADB Fastboot installed. And yes... I let my device with no one security feature enabled and didn't worked. I tried everything even after wiped data / cache and factory reset and no progress.
In my researches, I realized something about 'oem unlock'. It appears to be the key to solve this. And I guess the tool to work with this is the damn unlock tool from ASUS which don't work! Also, I've heard about workaround with Magisk by flashing a custom recovery to achieve the root. Magisk no longer supports zip files to flash. Only '.img' and '.tar' files. I'd like to find some light here... I don't know what to do. I appreciate any help!

Hello do I need to flash Android9EncryptionDisablerZE620KL.zip if Im gonna flash a non-GSI custom ROM? Or its only for GSI Treble ROM?

[email protected] said:
Hi!! I thanks for these instructions you gave. I know this post is a bit older. But is the only one I think could help me.
I got an ZE620KL and I'm trying to root this device. I have some experience in unlocking bootloader and rooting devices. But this one... Is giving me a lot of work. Researching in a lot of forums and websites I tried a lot of things with no success. In theory, is just install the official apk provided by ASUS and run the application. But the app doesn't work for a long time as I researched (error accusing network problem). I tried unlock via fastboot commands but I always got stucked by "remote: permission denied" even with latest drivers and ADB Fastboot installed. And yes... I let my device with no one security feature enabled and didn't worked. I tried everything even after wiped data / cache and factory reset and no progress.
In my researches, I realized something about 'oem unlock'. It appears to be the key to solve this. And I guess the tool to work with this is the damn unlock tool from ASUS which don't work! Also, I've heard about workaround with Magisk by flashing a custom recovery to achieve the root. Magisk no longer supports zip files to flash. Only '.img' and '.tar' files. I'd like to find some light here... I don't know what to do. I appreciate any help!
Click to expand...
Click to collapse
Im not sure if you still have your phone or you have successfully unlocked bl. but I found an updated version of their tool which works.
*tried unlocking from android 10 not working, it says device model not supported*
Zenfone 5 Unlock BL

cf100clunk said:
Thanks for the great instructions! Steps 1 through 11 worked perfectly for me, then I installed LineageOS (lineage-17.0-20191231-UNOFFICIAL-treble_arm64_avN.img) and it works properly. Then when I go back to TWRP and install Magisk v20.1 it reboots into an endless Lineage bootup logo animation (not boot loop). I can get an adb shell, but now also the external SD card has become invisible. Any suggestions?
UPDATE: I switched over to the patched Magisk version from PHH (https://forum.xda-developers.com/zenfone-5/general/ze620kl-add-support-to-evey-android-9-t3966918) and everything works perfectly now!
Click to expand...
Click to collapse
Do you still have the patched Magisk zip file, the original link in the post seems not working

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

AOSP for OnePlus 5/5T - Android 12
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it!
*/
Most of the information from here can be applied for this ROM.
Introduction
This projects aims to create an upgradable AOSP build system for the Oneplus 5 (Cheeseburger).
No repository from AOSP is changed: no commit over AOSP is at the moment present on the sources for this ROM.
All the changes are provided in separate repositories (HALs, kernel): this allows to upgrade Android with minimal effort, potentially also for future major versions.
Most of the added repositories is provided by LineageOS or CAF, so thanks to them for those repos.
Screenshots are attached.
This ROM is based on the work on Android 11 from here: https://forum.xda-developers.com/t/...-19-september-2021-locked-bootloader.4183691/
As usual, only builds with enforcing SELinux, no root access and 'user Android build flavor' will be posted here.
Known issues
- None that I'm aware of.
Changelog
See second post.
Download
Releases can be found on AndroidFileHost.
OnePlus 5 (Cheeseburger): https://androidfilehost.com/?w=files&flid=328726
OnePlus 5T (Dumpling): https://androidfilehost.com/?w=files&flid=328820
Installation
Backup everything.
The provided zip can be installed using the TWRP recovery: clear data while doing that.
The ROM expects the firmware from OOS 10.0.1: different firmwares are not tested.
The provided recovery allows only flashing signed images: use TWRP if you need to flash GApps or different packages.
Sources
Kernel on github: https://github.com/robertoglandroid/kernel_oneplus_msm8998
ROM sources: https://github.com/roberto-sartori-gl/local_manifests/tree/a12/gl
Telegram discussion group here!
XDA:DevDB Information
AOSP for OnePlus 5/5T, ROM for the OnePlus 5/5T
Contributors
robertogl
Thank you to @T1mb3 and @Maitreya29!
ROM OS Version: Android 12
ROM Kernel: Linux 4.x
Version Information
Status: Beta
Created 2021-10-05
Last Updated 2022-07-07

Changelog
[07/07/2022] aosp12_cheeseburger/dumpling-ota-user-20220707.zip
July2022 Security patches (synced with AOSP android-12.1.0_r10)
[08/06/2022] aosp12_cheeseburger/dumpling-ota-user-20220608.zip
June 2022 Security patches (synced with AOSP android-12.1.0_r8)
[21/05/2022] aosp12_cheeseburger/dumpling-ota-user-20220521.zip
Support f2fs formatted /cache partition
Synced with Lineage 19.1 sources
Minor fixes
Code cleanup
[15/05/2022] aosp12_cheeseburger/dumpling-ota-user-20220515.zip
Add option to apply OTA updates from SettingsExtra
4 files can be installed:
the ROM OTA - put the zip in /sdcard/update.zip
magisk - put the zip in /sdcard/magisk.zip
gapps - put the zip in /sdcard/gapps.zip
decryption zip - put the zip in /sdcard/decrypt.zip
The device will reboot automatically in recovery and apply the updates. Only TWRP can install magisk, gapps or the decryption zip.
Fix crash of the Settings app while configuring fingerprint or PIN lock (during the first setup, or from the Settings page)
Add possibility to enable location indicator in the Development Options
Location indicator is disabled for the Phone Services
[03/05/2022] aosp12_cheeseburger/dumpling-ota-user-20220503.zip
May 2022 Security patches (synced with AOSP android-12.1.0_r5)
Fix issue with Led Manager (SettingsExtra)
[04/04/2022] aosp12_cheeseburger/dumpling-ota-user-20220404.zip
April 2022 Security patches (synced with AOSP android-12.1.0_r4)
Fix slow unlock when fingerprint is used
[13/03/2022] aosp12_dumpling-ota-user-20220313.zip
Fix Settings app crash when opening fingerprint settings
[08/03/2022] aosp12_cheeseburger/dumpling-ota-user-20220308.zip
Android 12L
March 2022 Security patches (synced with AOSP android-12.1.0_r1)
Fix time and date not persisted after a reboot/factory reset
Fix vibration level setting on SettingsExtra
[01/03/2022] aosp12_cheeseburger/dumpling-ota-user-20220301.zip
Sync with Lineage 19 source
Fix issue with sim2 (data works also on sim2 now)
Fix Pocket Mode
Fix 'issue' that was causing some apps to detect root without Magisk
[08/02/2022] aosp12_cheeseburger/dumpling-ota-user-20220208.zip
February 2022 Security patches (synced with AOSP android-12.0.0_r29)
Fix Jio issues with VoLTE calls
[04/01/2022] aosp12_cheeseburger/dumpling-ota-user-20220104.zip
January 2022 Security patches (synced with AOSP android-12.0.0_r26)
Fix alarms not working with default Clock app
[07/12/2021] aosp12_cheeseburger/dumpling-ota-user-20211207-beta.zip
December Security patches (synced with AOSP android-12.0.0_r16)
[02/11/2021] aosp12_cheeseburger/dumpling-ota-user-20211102-beta.zip
November Security patches (synced with AOSP android-12.0.0_r13)
Add separate wifi and cellular data quick settings tiles (as Android 11)
Unified Android 12 tile is still present
[25/10/2021] aosp12_cheeseburger/dumpling-ota-user-20211025-beta.zip
Add f2fs support on /data partition
[20/10/2021] aosp12_cheeseburger/dumpling-ota-user-20211020-experimental.zip
Add support for OnePlus 5T (Dumpling)
Fix data on SIM1 (SIM2 is not working for data in this release)
Enable switch for default mobile data between SIM1 and SIM2 directly in the Android Settings (removed tile: less code to mantain)
Grant permissions to Play Store (and some Google apps) automatically - allow to setup the device and restore a backup at first boot
Fix TWRP not booting after flashing Android 12
Now recovery is not updated/overwritten anymore (no need for the persist_twrp mod or anything - installed recovery is persisted)
Vibration and alarm icons are back in the status bar
[09/10/2021] aosp12_cheeseburger-ota-user-20211009.zip
Fix encryption - Now File Based Encryption is enabled by default
Fix SIM1 sometimes not being recognized at boot
Fix an issue that caused Android to being stuck at boot sometimes (e.g. after flashing it the first time)
Add 'SIM Data Switch' tile to allow switching the default SIM used for mobile data
[06/10/2021] aosp12_cheeseburger-ota-user-20211006-alpha.zip
First release: October 2021 Security Patch (synced with AOSP android-12.0.0_2)
Only known issue is encryption not working

Booting with locked bootloader
This ROM can be booted with locked bootloader.
Not supported at the moment.
For more info, refer to the A11 thread (the information are the same):
[ROM][11.0][OnePlus 5] AOSP for OnePlus 5 [06 OCTOBER 2021][Locked bootloader]
New build in the first post: aosp_cheeseburger-ota-user-20201205.zip Changelog: Add option to enable Call Recording - available in the Settings Extra app Add battery level on the bluetooth icon on status bar (when a bluetooth device reports a...
forum.xda-developers.com

Reserved3

Gapps android 12 here

Added to the OnePlus 5 Index Thread here.

Sources are now available here: https://github.com/roberto-sartori-gl/local_manifests/tree/a12/gl

New release: aosp12_cheeseburger-ota-user-20211009.zip
Changelog:
Fix encryption - Now File Based Encryption is enabled by default
Fix SIM1 sometimes not being recognized at boot
Fix an issue that caused Android to being stuck at boot sometimes (e.g. after flashing it the first time)
Add 'SIM Data Switch' tile to allow switching the default SIM used for mobile data
So, this release fixes encryption: I only plan to support builds with encryption enabled, so if you flashed the first A12 release (without encryption), you'll need to format /data or disable encryption somehow (I don't provide support for this, sorry, but there should be some flashable zips).
This is the last time that formatting /data will be require, I promise!
This also means that if you have my A11 ROM (linked in the first post) you can actually update to A12 without losing any data (app included). But this is still a beta release, so at your risk!

Roms works fine for the most part. I'm not sure if i'm even supposed to test different browsers but chrome and kiwi browser end up crashing when downloading heavy files (> 100Mb)

work on device decrypted and twrp?

hello, there's some problem with the rom and the phone. i accidentaly rebooted in recovery and it stays stuck on logo screen and wont go over, also force rebooting it will always go into twrp and wont boot anyway. tried also to update to lastest recovery verison, but result it'S also the same. any solution or fix for this? p.s.: at the first flash, the rom booted fine.

kitamurt said:
hello, there's some problem with the rom and the phone. i accidentaly rebooted in recovery and it stays stuck on logo screen and wont go over, also force rebooting it will always go into twrp and wont boot anyway. tried also to update to lastest recovery verison, but result it'S also the same. any solution or fix for this? p.s.: at the first flash, the rom booted fine.
Click to expand...
Click to collapse
What logo? Android animation, oneplus logo, or Android recovery logo?
morfances said:
work on device decrypted and twrp?
Click to expand...
Click to collapse
The ROM only supports encrypted /data, but there should be some zip on XDA to manage decryption (I never tested that though).

robertogl said:
What logo? Android animation, oneplus logo, or Android recovery logo?
The ROM only supports encrypted /data, but there should be some zip on XDA to manage decryption (I never tested that though).
Click to expand...
Click to collapse
it stays stuck on twrp logo, but i can go to fastboot mode also and reboot, but the system wont boot anyway. it will only boot automatically into twrp, but i cant make anything since it stays stuck on twrp logo. i followed the steps above, bootlaoder already unlocked, formatted data, then flashed rom and gapps, eventually rebooted.

kitamurt said:
it stays stuck on twrp logo, but i can go to fastboot mode also and reboot, but the system wont boot anyway. it will only boot automatically into twrp, but i cant make anything since it stays stuck on twrp logo. i followed the steps above, bootlaoder already unlocked, formatted data, then flashed rom and gapps, eventually rebooted.
Click to expand...
Click to collapse
What TWRP are you using? TWRP should boot as it should not depend on the OS.

robertogl said:
What TWRP are you using? TWRP should boot as it should not depend on the OS.
Click to expand...
Click to collapse
i'm using the official twrp downloaded from the website, version 3.5.2. what doesn't add up is the reason why the recovery boots and stays stuck on the logo. so it's really weird. i also tried to boot the twrp from adb, giving the command "fastboot boot twrp.img", but the result it's the same.

kitamurt said:
i'm using the official twrp downloaded from the website, version 3.5.2. what doesn't add up is the reason why the recovery boots and stays stuck on the logo. so it's really weird. i also tried to boot the twrp from adb, giving the command "fastboot boot twrp.img", but the result it's the same.
Click to expand...
Click to collapse
Try booting this: https://androidfilehost.com/?fid=10763459528675599801

robertogl said:
Try booting this: https://androidfilehost.com/?fid=10763459528675599801
Click to expand...
Click to collapse
that worked, thx. but seems that the "signed twrp" can't recognize encrypted data, indeed when asking for pattern/pin, even entering it correctly, will say that isn't recognized and therefore data is not recognized. so normal twrp can't be used for flash this kind of rom and gapps?

kitamurt said:
that worked, thx. but seems that the "signed twrp" can't recognize encrypted data, indeed when asking for pattern/pin, even entering it correctly, will say that isn't recognized and therefore data is not recognized. so normal twrp can't be used for flash this kind of rom and gapps?
Click to expand...
Click to collapse
For sure current TWRP cannot decrypt data as they need to be updated to support A12.
But at least you can flash/format things now.
I'm not sure why your TWRP didn't work, the signature should not be important (I shared that because it was already uploaded).

well, thanks for the advice! that said, the bugs i've encountered so far are:
-wifi very buggy, it disconnects after a while and the signal it's very poor, after it's disconnected it can't reconnect to any network. this is solved by rebooting the device
-random crash of systemui, especially when pressing the settings button
-twrp 3.5.2 not booting after flash the rom, only the signed_twrp will work (but not decrypt data) and allow to flash other things

kitamurt said:
well, thanks for the advice! that said, the bugs i've encountered so far are:
-wifi very buggy, it disconnects after a while and the signal it's very poor, after it's disconnected it can't reconnect to any network. this is solved by rebooting the device
-random crash of systemui, especially when pressing the settings button
-twrp 3.5.2 not booting after flash the rom, only the signed_twrp will work (but not decrypt data) and allow to flash other things
Click to expand...
Click to collapse
- The networking is a bit broken apparently, I already had different report of this. We are working on fixing this.
- This happens when you open the settings button from the Quick Settings view, right? It is broken also on A11, it should work only if you have a PIN/fingerprint configured (for some reason).
- TWRP will need to be updated to support A12 encrypted, yes
Of course, thanks for reporting these issues! Always appreciated, as I cannot test everything by myself