Database Develop

ROM: Sony AOSP 8.1 (H3113) (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"
}
Sony AOSP project​
Disclaimer
I'm not liable for anything YOU do to YOUR device, YOU are doing it and it's YOUR device.
What is it?
It's a project developed and maintained by Sony Xperia Developers team.
You can get more informations here: https://developer.sony.com/develop/open-devices/
Can I build it by myself?
Sure, just follow these instructions and have patience!
What works and what doesn't?
According to this official page, almost everything seems to be fine.
How can I flash it?
Follow these steps:
Unlock the bootloader (this will erase your data and will void warranty): https://developer.sony.com/develop/open-devices/get-started/unlock-bootloader/
Setup fastboot on your PC (there are many guides for this step)
Download and unpack the zip archive
Open a shell into the folder containing unpacked files
Run these commands:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash userdata userdata.img (it’s not necessary to flash userdata every time)
Download and unpack the corresponding vendor image from here: https://developer.sony.com/develop/open-devices/downloads/software-binaries
Open a shell into the folder containing unpacked image
Run this command:
fastboot flash oem SW_binaries_for_Xperia_xxxxx.img (where "xxxxx" varies depending on the file)
(optional) In case you want to flash GApps, Magisk or other mods, you can use TWRP: https://forum.xda-developers.com/xa2-ultra/development/recovery-twrp-3-2-1-0-touch-recovery-t3774193
Reboot the device and enjoy!
Download link
You can get the builds from my AFH folder: https://androidfilehost.com/?w=files&flid=269497.
I haven't done any change to Sony's source code, these are vanilla builds.
Credits
All credits go to Sony and Google.
XDA:DevDB Information
Sony AOSP, ROM for the Sony XA2 Ultra
Contributors
axxx007xxxz
Source Code: https://github.com/sonyxperiadev
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 4.x
Based On: AOSP
Version Information
Status: Testing
Created 2018-05-08
Last Updated 2018-05-08

Reserved
NOTE: I'm in no way associated with Sony, these are unofficial builds and are made for pesonal usage.
Also, these builds are untested so I can't assure they're going to work!

Reserved 2
Post reserved for future usage.

Reserved 3
Post reserved for future usage.

Reserved 4
Post reserved for future usage.

New build
Build informations:
Build type: userdebug
Android revision: android-8.1.0_r20
CAF revision: LA.UM.6.4.r1
Last commit of sonyxperiadev/local_manifests: 81032020581dd636ab9d7f8414609bad07332288
Last commit of sonyxperiadev/kernel: 1df958f2943c6c5cae31018e42d2f42e8a55c4b3
Last commit of sonyxperiadev/device-sony-nile: c775da101d57377979cdcb79b1ba1b5bbd3739a4
Last commit of sonyxperiadev/device-sony-pioneer: 5b804c4aa86ca13653d2d692120437fa76f61ae9.
Download link: https://androidfilehost.com/?fid=818222786056029296.

It always says "There's an internal problem with your device" after booting up. It's kinda annoying.
And it also does not accept my Samsung microSD card formatted on stock ROM and wants me to format it. I'm backing it up, and will try to format it later.
Fingerprint aslo does not work, but I'm fine with that at the moment.
If someone needs to know, I have H4113 (dual-sim variant of regular XA2).

Casserole said:
It always says "There's an internal problem with your device" after booting up. It's kinda annoying. And it also does not accept my Samsung microSD card formatted on stock ROM and wants me to format it.
Click to expand...
Click to collapse
Just information: I have the H3223 not H3213, and haven't tried to flash this, but on the Google Pixel (8.1) with at least some custom kernels and some versions of Magisk, the same "There's an internal problem with your device" when you boot up, but other than possibly having your phone screen on longer than it should, there are no actual problems on the Pixel. Could be for the same reason(s), whatever those reasons are. I'm not positive but I think that more recent versions of Magisk might not cause that message anymore. I use an old version of Magisk, but in my case the Pixel custom kernel I use causes that, too.

roirraW "edor" ehT said:
I'm not positive but I think that more recent versions of Magisk might not cause that message anymore. I use an old version of Magisk, but in my case the Pixel custom kernel I use causes that, too.
Click to expand...
Click to collapse
I haven't flashed any magisks at the moment, so I don't think the problem are caused by it. But thanks anyway for the reply.

Casserole said:
I haven't flashed any magisks at the moment, so I don't think the problem are caused by it. But thanks anyway for the reply.
Click to expand...
Click to collapse
You're welcome! I'm not suggesting that you flashing Magisk or anything is the cause of this on this ROM, it's just related to changes in Android 8.1 and that it doesn't really necessarily mean there's something wrong. I'm sure there are ways around it, but since I'm not a developer and I don't know what triggers it, I don't know.

Is fingerprint scanner not working for everyone or it is not working only for those with a fingerprint scanner made by a a different hardware maker?

tombassi said:
cool down dude !! XDA is not the correct please for these bad words. if you don't know what you are doing that is not the Developer fault and if you need no bugs stay with the stock ROM.
Click to expand...
Click to collapse
Thanks! With "almost everything seems to be fine", I meant that most of the main parts (should) work.
Camera is a known problem on Sony devices due to DRM keys getting erased on bootloader unlock.
Casserole said:
It always says "There's an internal problem with your device" after booting up. It's kinda annoying.
And it also does not accept my Samsung microSD card formatted on stock ROM and wants me to format it. I'm backing it up, and will try to format it later.
Fingerprint aslo does not work, but I'm fine with that at the moment.
If someone needs to know, I have H4113 (dual-sim variant of regular XA2).
Click to expand...
Click to collapse
The SD card problem could be related to your phone being dual SIM: as the title says, these builds are for H3113 (single SIM variant).
You can try to set dual SIM properties in build.prop (you can do it with an app like this or a text editor if you have root access, otherwise I think it's doable through TWRP too):
Code:
persist.multisim.config=dsds
persist.radio.multisim.config=dsds
ro.telephony.default_network=9,1
then reboot the phone and test.
These come directly from H4113 makefile, I can't assure you everything will be fine after this, but you can give it a try.
As per the fingerprint, it's currently broken on all variants, I'm sorry.
mirco_pa said:
Is fingerprint scanner not working for everyone or it is not working only for those with a fingerprint scanner made by a a different hardware maker?
Click to expand...
Click to collapse
Sony website reports it as currently not working on AOSP, I'm sorry.

axxx007xxxz said:
The SD card problem could be related to your phone being dual SIM: as the title says, these builds are for H3113 (single SIM variant).
You can try to set dual SIM properties in build.prop (you can do it with an app like this or a text editor if you have root access, otherwise I think it's doable through TWRP too):
Click to expand...
Click to collapse
I think SD card problem was related to something else, because it started working after reformatting.
But there were also problems with SIM card, it worked on first boot, but after removing and inserting it again device shown that there were no signal, so your solution may be helpful in this situation. I can't test it due to limited amount of time, though.

New build
Build informations:
Build type: userdebug
Android revision: android-8.1.0_r26
CAF revision: LA.UM.6.4.r1
Last commit of sonyxperiadev/local_manifests: 1c992d7f3f2ef8d0b53397e23227e10489e40bec
Last commit of sonyxperiadev/kernel: ab6fd5b1a4126cfdd4391eefe8eba17eb6626781
Last commit of sonyxperiadev/device-sony-nile: 7d57c76da9ce47849429347e77e013781e63db2f
Last commit of sonyxperiadev/device-sony-pioneer: 5b804c4aa86ca13653d2d692120437fa76f61ae9.
Download link: https://androidfilehost.com/?fid=890278863836285554.

Can you build one for H4113? You shood have files for it too

Thanks axxx007xxxz for sharing these builds! They helped me recover Android on my completely wiped h3113 pioneer. Both the 8.0 and 8.1 build work for me. Downloading them to my PC was the hardest part, for some reason the download often fails.
I still have a couple of questions about these Sony AOSP builds that maybe you can answer:
1. Do you know what the Sony software binaries* do? I have flashed them on my device a couple of times, but I don't see anything added.
2. What is the difference between build type "userdebug" and "eng"?
3. If I use this build, how would you recommed I update it? Is the only way to flash in fastboot? (Like step 6 in Sony's guide**?)
Thank you!
roirraW "edor" ehT said:
Just information: I have the H3223 not H3213, and haven't tried to flash this, but on the Google Pixel (8.1) with at least some custom kernels and some versions of Magisk, the same "There's an internal problem with your device" when you boot up, but other than possibly having your phone screen on longer than it should, there are no actual problems on the Pixel. Could be for the same reason(s), whatever those reasons are. I'm not positive but I think that more recent versions of Magisk might not cause that message anymore. I use an old version of Magisk, but in my case the Pixel custom kernel I use causes that, too.
Click to expand...
Click to collapse
I get the same error message right after booting, also without root. It's annoying, but I guess I can live with it.
P.S. As I'm a new user, I cannot use links yet. Please use these footnotes instead:
*: https[colon]//developer[dot]sony[dot]com/develop/open-devices/downloads/software-binaries
**: https[colon]//developer[dot]sony[dot]com/develop/open-devices/guides/aosp-build-instructions/build-aosp-nougat-8-1-oreo-4-4/#tutorial-step-6

1. parts of android which are closed source, graphics driver for example. you won't see them.
2. eng should give you more debugging options, like working adb logcat without enabling developer options which is sometimes needed while you're porting android to new device and there's just black screen on the phone for example. correct me if i'm wrong.
3. flashing worked through twrp for me but i had to build unsingned zip.
regarding the internal problem message, just ignore it.

davidhozic said:
Can you build one for H4113? You shood have files for it too
Click to expand...
Click to collapse
Checking H4113 makefile, I don't see big differences except for a few properties: https://github.com/sonyxperiadev/device-sony-pioneer/blob/master/aosp_h4113.mk#L18-L22; you can try to set them (you can use an app like this) and check if you can get dual SIM to work.
I can make a H4113 build if you want to test it though.
Nonstop decay said:
Downloading them to my PC was the hardest part, for some reason the download often fails.
Click to expand...
Click to collapse
Unfortunately, Android File Host is problematic sometime.
Nonstop decay said:
I still have a couple of questions about these Sony AOSP builds that maybe you can answer:
1. Do you know what the Sony software binaries* do? I have flashed them on my device a couple of times, but I don't see anything added.
2. What is the difference between build type "userdebug" and "eng"?
3. If I use this build, how would you recommed I update it? Is the only way to flash in fastboot? (Like step 6 in Sony's guide**?)
Click to expand...
Click to collapse
Basically, what @frantisheq said.
I think you can flash IMG files through TWRP too if you extract the ZIP into your phone's memory.

axxx007xxxz said:
I can make a H4113 build if you want to test it though.
Click to expand...
Click to collapse
Just wondering aside from not being supported in Sony's open device program what exactly is needed to get the H3223 from getting AOSP 8.1 built for it? I can't imagine the kernel being much different on the H3223 from any of the other XA2 Ultra single sim models, right?

axxx007xxxz said:
Checking H4113 makefile, I don't see big differences except for a few properties: https://github.com/sonyxperiadev/device-sony-pioneer/blob/master/aosp_h4113.mk#L18-L22; you can try to set them (you can use an app like this) and check if you can get dual SIM to work.
I can make a H4113 build if you want to test it though.
Unfortunately, Android File Host is problematic sometime.
Basically, what @frantisheq said.
I think you can flash IMG files through TWRP too if you extract the ZIP into your phone's memory.
Click to expand...
Click to collapse
Yes plese make a build for H4413, i get so many random errors and every time i fix an error there appears another. And is the build for this model supposed to work with h4113? Aren't the boot images incompatible?

[ROM][EOL] Magma Moonshine - Android Q for Nexus 4 [mako]

{
"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"
}
HTML:
#include "std_disclaimer.h"
/*
* 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.
*/
IMPORTANT: You need to have a /system partition at least 1272 MB size to flash this ROM.
voron00 said:
A few options to repartition the device:
https://forum.xda-developers.com/nexus-4/general/guide-increase-nexus-4s-partition-space-t3800264
https://forum.xda-developers.com/nexus-4/orig-development/repartition-nexus-4-repartition-t3844383
Also quick and easy repartitioning script for flashing on stock partition table only: https://drive.google.com/file/d/1GNbxlqG78WYOeXBxgmfGgMmsf02KMVOX/view?usp=sharing
Use at your own risk.
Click to expand...
Click to collapse
Any repartitioning is done at your own risk.
Descritpion:
One of the first releases of Magma for any device. It's meant to be clean and stable that's why it's pretty bare for now. I'm using Nexus 4 for testing this so probably more updates will come.
Official release with OTA will be available soon :fingers-crossed:
Working/not working:
- everything should work like on LOS 16 by voron
Flashing Instruction:
1. Backup all your data (Important)
2. Wipe system, data and cache.
3. Flash the ROM.
4. Reboot.
Downloads:
ROM: https://mirror.codebucket.de/magma/mako/
Credits:
- LineageOS team.
- @voron00 for his work on LOS for mako
Sources:
Device: https://github.com/MagmaDevices/device_lge_mako
Kernel: https://github.com/voron00/android_kernel_lge_mako
Vendor: https://github.com/voron00/proprietary_vendor_lge
Source Code: https://github.com/MagmaProject

edi194 said:
Working/not working:
- everything should work like on LOS 16 by voron
Click to expand...
Click to collapse
Does this mean that the ROM is Android 9 that looks like Android 10?

ze7zez said:
Does this mean that the ROM is Android 9 that looks like Android 10?
Click to expand...
Click to collapse
This rom is Android 10 based

Looking pretty good. I had already repartitioned for PIE and Magma installed without any problem. I couldn't change my home wallpaper to the pure black I prefer, and I discovered that the smallest OpenGapps containing Wallpapers is Mini, which was too big for my system partition. I installed Pico (Micro also works) and got the Wallpapers apk from Apkpure. All working fine.
The only thing not working is Magisk 20.1, which refuses to stick. I get an "installed ok" message in TWRP, but Magisk Manager isn't installed when I boot, and when I install the apk Manager says that Manager is up to date but Magisk itself isn't installed. I'll keep trying and report if I get any more info.
Great job, @edi194. Amazing to have Android 10 running on such a very old device. Thank you.
Edit: I've installed Magma on my second N4, which is a good one (screen works fine), and Magisk doesn't stick on this one either.
This is absolutely not any sort of criticism, just reporting. As I said, I'm blown away by having Android 10 on my ancient N4s - a remarkable achievement for which I'm very grateful.

Why does it want gapps for 7.1.2 and not 10?
nvm silly me downloaded arm64 gapps
Rom is running super smooth!

Thanks for the ROM. Tried it out.
It's not smooth, stutters more than Pie ROMs. However, given that it's still early stage for 10 ROMs, it's very impressive. No huge bugs. Totally usable performance. Pie ROMs in early stages were way more slower than this.
Keep up the good work! It will be great to see some updates!

Hi, body, good job for this, it's very smooth on my nexus4. And I want to know which gapps I can flashed on it? I can't find it. Thanks~

https://www.cyanogenmods.org/downloads/pico-opengapps-for-android-10-arm32/
Pico works fine.

Testing, testing, testing...
New build is up!
Changelog:
- updated device tree
- updated source
- changed bootanimation
Nothing pretty big ¯\_(ツ)_/¯
December patch not added... yet.
Known bugs:
- inbuilt screen recording will crash your systemui constantly, don't use it
- too big advanced reboot icon
Download link: https://mirror.codebucket.de/cosp/test/Magma-Moonshine-OFFICIAL-mako-20191213.zip

Thanks for the new version. I like the new Marshmallow(?) boot animation.
A couple of things to report. Each time I've flashed after a total wipe (all partitions) & format.
1) Magisk still doesn't stick. Manual installation of Magisk Manager shows "Magisk not installed" although TWRP shows a successful installation. I mention this only because I don't think it's a Magisk problem, as Magisk works on my Nexus 5 with Android Q.
On my first two attempts I got a bootloop - it showed the SIM PIN screen for a second, and then the boot animation showed. This repeated for about 10 minutes.
On the third attempt I installed only the ROM & OpenGapps Pico (no Magisk), and the bootloop is still happening as I write this.
2) I set a security PIN, which was accepted, but then the security showed the unlock method as "Swipe", and no PIN is required to open the phone. When I try to change it again, it says "Wrong PIN".
I have two Nexus 4s. The other one still has the original Magma on it and it doesn't have the PIN or bootloop problems, though Magisk doesn't work on that device either.
It may be only this specific device. Can anyone confirm that these problems don't happen on their device?

dahawthorne said:
Thanks for the new version. I like the new Marshmallow(?) boot animation.
A couple of things to report. Each time I've flashed after a total wipe (all partitions) & format.
1) Magisk still doesn't stick. Manual installation of Magisk Manager shows "Magisk not installed" although TWRP shows a successful installation. I mention this only because I don't think it's a Magisk problem, as Magisk works on my Nexus 5 with Android Q.
On my first two attempts I got a bootloop - it showed the SIM PIN screen for a second, and then the boot animation showed. This repeated for about 10 minutes.
On the third attempt I installed only the ROM & OpenGapps Pico (no Magisk), and the bootloop is still happening as I write this.
2) I set a security PIN, which was accepted, but then the security showed the unlock method as "Swipe", and no PIN is required to open the phone. When I try to change it again, it says "Wrong PIN".
I have two Nexus 4s. The other one still has the original Magma on it and it doesn't have the PIN or bootloop problems, though Magisk doesn't work on that device either.
It may be only this specific device. Can anyone confirm that these problems don't happen on their device?
Click to expand...
Click to collapse
Flashing opengapps will break multiple things in android 10 on 32 bit arm devices at the moment, including security PIN settings.

Thanks, @voron00, but both problems persist.
Full wipe & format, install Magma only, no Gapps or Magisk, boot was fine. I chose Security/PIN, entered the PIN, which was accepted, and pressed the back button. It showed "Swipe". I locked the screen and unlocked it with a simple swipe, no PIN required. I tried changing it again and got "Wrong PIN".
And I'm afraid it's bootlooping again - a second of the SIM PIN screen and then the boot animation.

Looking into this, if I'll fix it I'll push new build today

Thanks, @edi194 - much appreciated.
I thought that reporting this without a log might not be too helpful, so I tried it on my second Nexus 4, which is in perfect condition. I'm afraid that both the PIN & bootlooping are happening on that device as well - just Magma, no Gapps or Magisk.
Thanks for your work on Nexus 4 Android 10.

Update... again
Changelog:
- hopefully fix keyguard (pin/password/pattern is now working, after reboot it takes some time to unlock)
- added (useless for now) MagmaSettings
- removed screenrecorder (not working on mako anyway)
- really small source updates
About Magisk...
To be honest, I don't know what's the problem. Tested several Q/10 roms and it wasn't working on any of them. Probably it's an kernel thing but i'm not experienced about these at all. We need to wait for proper fix by someone else.
Download link on first post

Wow, you're good...
PIN and reboot now work correctly.
Magisk still doesn't work despite claiming to be installed in TWRP. No problem - my Nexus 4s are my emergency phones.
I don't know if it's of any help (or interest ) but the Android 10 on my Nexus 5, on which Magisk does work, is the work of @z3DD3r - an experimental Hammerhead LineageOS 17 on the green banner at the top of this link:
https://sourceforge.net/projects/hammerhead-lineageos/files/16.0/

Unfortunately, recovery from backup twrp 3.3.1-1 UA does not work for me. The system does not stand up and hangs on flying balls. Adb works. I can do logcat if needed.
Has anyone obtained a working system from recovery?

When I read your post my first thought was that "hangs on flying balls" must be a traditional Polish way of saying "Not very stable". But then I got what you meant...
I can confirm that recovering an image doesn't seem to work, which rather defeats the purpose of a recovery. I've never seen a TWRP recovery failure before. I did a backup with 3.3.1-1 UA, wiped everything except Internal Storage, and recovered the image, but it "hung on flying balls" .
I flashed standard TWRP 3.3.1 Mako, but that's the same - although it did complain about vendor & EFS partitions not being found. When I get more time I'll reinstall Magma and try the same backup, wipe & recovery with standard TWRP.
Update: No, standard TWRP doesn't work either. Full wipe & format, flash Magma & OpenGapps only, took TWRP backup, system rebooted ok, back to TWRP, recovered this new backup apparently ok, but it's been on the flying dots boot screen for 10 minutes now.

edi194 said:
About Magisk...
To be honest, I don't know what's the problem. Tested several Q/10 roms and it wasn't working on any of them. Probably it's an kernel thing but i'm not experienced about these at all. We need to wait for proper fix by someone else.
Click to expand...
Click to collapse
Try the commits on Nov 19, 2019 here: https://github.com/Colt-Enigma/platform_system_extras/commits/c10
Nitin

edi194 said:
Changelog:
- hopefully fix keyguard (pin/password/pattern is now working, after reboot it takes some time to unlock)
- added (useless for now) MagmaSettings
- removed screenrecorder (not working on mako anyway)
- really small source updates
About Magisk...
To be honest, I don't know what's the problem. Tested several Q/10 roms and it wasn't working on any of them. Probably it's an kernel thing but i'm not experienced about these at all. We need to wait for proper fix by someone else.
Download link on first post
Click to expand...
Click to collapse
FYI recorder is also fixed in latest sources.

[ROM][UNOFFICIAL][jd2019][9 Pie] LineageOS 16.0 for the Lenovo Z5s L78071

{
"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"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 9 Pie, which is designed to increase performance and reliability over stock Android for your device.
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. You can also view the Changelog for a full list of changes & features.
Known issues: (as of May 19, 2020)
- FM Radio app doesn't work; It actually works, just once every two attempts: If it crashes the first time, select close app, clear apps from background and try again; I'll find a definite fix soon;
- Wi-Fi signal strength doesn't show on status bar, only in the wireless screen;
- Fingerprint reader doesn't work;
- SELinux is currently set to permissive;
Instructions:
- This is a FULL ROM build, meaning your BOOT, DTBO, SYSTEM and VENDOR partitions will be overwritten. Backup first!
- You need firmware version 11.x.y (preferably 11.3.169 - recovery encryption only tested with that version), any will do. 10.5 will not work
- Download TWRP from the files section, fastboot flash it (if you don't have custom recovery yet)
- Download patched vbmeta.img
- Download the latest build
- (Optional) Download Gapps (arm64 9.0, any flavor) and Magisk
- Boot to recovery (whichever you have), flash the new recovery
- Reboot to recovery, now your data is decrypted, flash vbmeta, latest build, magisk and gapps
- Format DATA completely to start from scratch since encryption is different
- Reboot
Downloads:
Builds: https://sourceforge.net/projects/lineageos-lenovo-z5s/files/
Source code:
LineageOS: https://github.com/LineageOS
Kernel and Device Tree: https://github.com/jacoghi
Reporting Bugs:
DO NOT Report bugs if you're not following the instructions!
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues.

Changelog:
May 19, 2020:
- Initital release, everything working except for FM and fingerprint reader;
- Kernel is completely overhauled and updated to LA.UM.7.8.r1-08500-SDM710.0;
- Audio drivers are stock 11.3.169 (we don't have the sources);
- Wifi is open-source, with MAC randomization currently being tested;
- Call recording already works;
- BT Audio works for calls and everything else, HD codecs being optimized;
- Wifi Display works perfectly on my cheap chinese Android TV Box. Please test with a Chromecast / Google Cast / SmartTVs, since I don't have any of those;
- Camera2API is active, RAW pictures are also enabled;
- Build will automatically encrypt your device, I had to fool Lenovo's BS keymaster to make it work, so it has to be enabled;
- As of now, I don't care if your apps work or not, that's not my problem, just let me know about hardware issues;

jacoghi said:
Please test with a Chromecast / Google Cast / SmartTVs, since I don't have any of those;
Click to expand...
Click to collapse
I can confirm that this works.
It's great to have a ROM that works and doesn't have audio problems or auto brightness issues compared to GSIs. I've been using this for two days without any problems aside from the bugs already mentioned. I am holding off on using Magisk like I normally do so as not to introduce complications.
Overall, a great first effort. Thank you very much!

carlshark said:
I can confirm that this works.
It's great to have a ROM that works and doesn't have audio problems or auto brightness issues compared to GSIs. I've been using this for two days without any problems aside from the bugs already mentioned. I am holding off on using Magisk like I normally do so as not to introduce complications.
Overall, a great first effort. Thank you very much!
Click to expand...
Click to collapse
Thanks for confirming that to me, great to know. Would you happen to have any of those fancy hi Def Bluetooth headphones so we can test aptx and aptxhd? And you can use magisk without any issues, I'm using it here right now, no problems.

jacoghi said:
Would you happen to have any of those fancy hi Def Bluetooth headphones so we can test aptx and aptxhd?
Click to expand...
Click to collapse
No, sorry. If that changes, I will let you know
I can imagine most of the users that are here are currently using a GSI. The stock 11.3.169 from here can actually be installed via TWRP. Flashing it would revert to stock recovery so users need to reinstall the TWRP recovery image during the same session. That's how I ensured that I was running an 11.x firmware after using all those GSIs from 4PDA. Hopefully this helps others to revert to stock so they can use your LOS build.

Some more good news, we now have a TWRP that decrypts data even from this updated Lineage 16 build. It actually should work for any ROM flashed atop firmware 11.3.169. That's the one I'm using and probably the majority of people who wanna stick to "the latest and greatest" speech, so here we go, now we can enable OTAs without any issues and flash anything. This recovery can decrypt any data regardless of password type, so you can use PATTERN, PIN, or whatever, it will work, I tested them all.
https://sourceforge.net/projects/lineageos-lenovo-z5s/files/twrp-3310-jd2019-recovery.img/download

And what is apparently massive news for us, our phone will get an Android 10 official update, meaning we'll be able to boot lineage 17.1 with the updated audio drivers (in theory). Anybody in China or who knows how to trick their system and able to get ahold of these files?
https://club.lenovo.com.cn/thread-5849244-1-1.html

jacoghi said:
Some more good news, we now have a TWRP that decrypts data even from this updated Lineage 16 build. It actually should work for any ROM flashed atop firmware 11.3.169. That's the one I'm using and probably the majority of people who wanna stick to "the latest and greatest" speech, so here we go, now we can enable OTAs without any issues and flash anything. This recovery can decrypt any data regardless of password type, so you can use PATTERN, PIN, or whatever, it will work, I tested them all.
https://sourceforge.net/projects/lineageos-lenovo-z5s/files/twrp-3310-jd2019-recovery.img/download
Click to expand...
Click to collapse
Hi, I used your recovery to try and create a full backup of your ROM before I go back to stock. I encounter an error when it tries to backup the system partition - the backup fails. When I tried to install the Full OTA ROM from Lenovo, it also fails. I flashed the other TWRP and both the backup and install worked.
I'm going back to stock to get the 11.5 update available only if the phone has a locked bootloader.

carlshark said:
Hi, I used your recovery to try and create a full backup of your ROM before I go back to stock. I encounter an error when it tries to backup the system partition - the backup fails. When I tried to install the Full OTA ROM from Lenovo, it also fails. I flashed the other TWRP and both the backup and install worked.
I'm going back to stock to get the 11.5 update available only if the phone has a locked bootloader.
Click to expand...
Click to collapse
Hey man, thanks for the report. I just rebooted to recovery and backed up the system partition without a hitch, so no clue what happened with you. Regarding the Lenovo Ota it probably doesn't work since they use different manifests from the ones I'm using with lineage. Nevertheless I'll make it universal now that I know about it. Let me know if you can get 11.5 and we can make a dump of all partitions. Thanks man

jacoghi said:
Hey man, thanks for the report. I just rebooted to recovery and backed up the system partition without a hitch, so no clue what happened with you. Regarding the Lenovo Ota it probably doesn't work since they use different manifests from the ones I'm using with lineage. Nevertheless I'll make it universal now that I know about it. Let me know if you can get 11.5 and we can make a dump of all partitions. Thanks man
Click to expand...
Click to collapse
The only thing I can think about was that I was trying to save to a microSD instead of internal storage.
Anyhow, I'm back on LOS. I went back to stock, relocked the bootloader, got the update notification but the downloaded update fails on install. I "read" in the Chinese forums that access to 11.5 is some sort of closed beta; some users also encounter failed updates.
@wzsx150 published a new TWRP based on Android 10, probably with the partition file info of 11.5. It doesn't work for me when I flashed it on top of 11.3 (Android 9). Thought it might help you further.

carlshark said:
The only thing I can think about was that I was trying to save to a microSD instead of internal storage.
Anyhow, I'm back on LOS. I went back to stock, relocked the bootloader, got the update notification but the downloaded update fails on install. I "read" in the Chinese forums that access to 11.5 is some sort of closed beta; some users also encounter failed updates.
@wzsx150 published a new TWRP based on Android 10, probably with the partition file info of 11.5. It doesn't work for me when I flashed it on top of 11.3 (Android 9). Thought it might help you further.
Click to expand...
Click to collapse
hey man could you please help out, was trying to revert to the stock rom but getting a blank screen after i'm done and it shows lenovo

carlshark said:
The only thing I can think about was that I was trying to save to a microSD instead of internal storage.
Anyhow, I'm back on LOS. I went back to stock, relocked the bootloader, got the update notification but the downloaded update fails on install. I "read" in the Chinese forums that access to 11.5 is some sort of closed beta; some users also encounter failed updates.
@wzsx150 published a new TWRP based on Android 10, probably with the partition file info of 11.5. It doesn't work for me when I flashed it on top of 11.3 (Android 9). Thought it might help you further.
Click to expand...
Click to collapse
That's why it failed, system partition is 5.1 GB, your sdcard is probably formatted in FAT32 which DOESN'T ALLOW files over 4GB, that's a filesystem limitation.
I'll wait for somebody getting us 11.5 firmware files and release a new twrp for Android 10, (partitions won't change and AFAIK, wsx's twrp doesn't decrypt and is full of extra non open source stuff) and Lineage 17.1, until then makes little sense to me update this knowing it won't last long anyways.

jacoghi said:
That's why it failed, system partition is 5.1 GB, your sdcard is probably formatted in FAT32 which DOESN'T ALLOW files over 4GB, that's a filesystem limitation.
Click to expand...
Click to collapse
Oh, right, I totally forgot all about that. Should have tried enabling compression or saving to internal storage.
I'll wait for somebody getting us 11.5 firmware files and release a new twrp for Android 10, (partitions won't change and AFAIK, wsx's twrp doesn't decrypt and is full of extra non open source stuff) and Lineage 17.1, until then makes little sense to me update this knowing it won't last long anyways.
Click to expand...
Click to collapse
I've found a 4PDA post regarding updating to 11.5 and reposted the good stuff here. Hope it helps. Thanks for your good work!
---------- Post added at 06:38 AM ---------- Previous post was at 06:35 AM ----------
seisa said:
hey man could you please help out, was trying to revert to the stock rom but getting a blank screen after i'm done and it shows lenovo
Click to expand...
Click to collapse
I know this is the wrong thread to answer this, but we can't really help you out without some more details. Were you trying to install through recovery? Through QFIL?
From the looks of it, sounds like you have a bootloop. Try doing QFIL again and unlocking bootloader, or the other way around - sometimes it works for me that way.

I have Z5s 6GB/128GB model, sold as Global Version & Global ROM.
It does have EU LTE bands, so it probably is somewhat "global".
The downside: I am at 10.5 version with no updates available. Seller also told that there are no updates.
Two questions:
1. Is it absolutely necessary to have 11.3+ to install this LineageOS ROM? What is blocking installation if I have 10.5? Can I brick it?
-- EDIT: I will answer myself: Yes it is needed. LineageOS did not flash over 10.5 and gave an error. That was validation error before flashing, so no harm done.
2. Is it safe to install Chinese ROM on this device? Is it possible to loose something in the process? Like LTE bands or something else important?
-- EDIT: Seems to be ok.
I really want to install LineageOS or some other google free AOSP ROM. But I do not want to loose important features or brick it in the process.
Thanks.
EDIT: I installed Arrow OS GSI at the moment over 10.5 and it seems to work. But still looking forward to get pure LineageOS installed.

I have one problem that is hardware related:
Microphone level is quite low compared to my previous phone and people are complaining about low volume when I call.
Is there any way to add more gain? I tried to search but did not find easy and straightforward answer. Most solutions refer to methods/files that do not exist on this ROM.
What I found was complaint that there is still no way to easily manage audio stuff in android...
Mic Test (lauresprojects.com.mictest) app confirms that recording levels are considerably lower in both direct sound and communication mode when comparing to my other phone.
Otherwise seems to working quite nicely. Thanks for your good work.

I can't use face unlock with this ROM.

Is there still some active development at this project?
Is there some active development at this project?

[ROM][OneUI 2.5][TWRP] NcX 2.5 for A71 [SM-A715F]

NcX 2.5 A71 ROM​Pretty straight forward, I took OneUI 2.5 firmware, debloated it and added a few features which can be found here: Link to MODs
My plan is to make this the best version of OneUI 2.5 with more features and fixed things (my mission is to fix Secure Folder in the near future) Fixed
Anyway, let's get started.
Code:
Your warranty is now void.
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about flashing this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you. HARD!
Features!​
TWRP Included
Full OneUI 2.5 features
Debloated
Added camera features
Dolby Atmos without earphones
Optimized
Edge Lighting fully enabled
Secure Folder fixed
Smart View fixed
Samsung Health fixed
Samsung OCR service
Bugs!​
Secure Folder broken (will try to fix later) Fixed on 2.5.1
Samsung Pass broken (because of knox 0x1, duh) Removed from ROM, it will never work.
Bug with AOD brightness when you use fingerprint unlock method. This bug happens when you have AOD to always show. If AOD is showing, then you turn the screen on to only show lockscreen clock and then turn the screen off for AOD to show, the brightness of AOD will reduce to the most minimal and it will be hard to see, regardless of what brightness you set up. There are 2 ways to getting rid of this bug:
Disable unlocking phone with fingerprint
Unlocking your phone and then locking it again. This will only fix it until you trigger the bug again
Fixed, clock animation removed.
You tell me
Changelog!​
25/Oct/2020 (NcX 2.5.2):
Added 60 fps recording on selfie cam
Added wide selfies. (a biiiiit buggy, but serviceable)
Added 24 fps recording modes on pro video mode
Fixed Samsung Health
Added Samsung OCR Service for better text extraction
12/Oct/2020 (NcX 2.5.1):
Secure Folder fixed
Smart View fixed
AOD bug fixed
Removed Samsung Pass
Removed Samsung Daily
Removed "Tips" app
Removed Bixby
Added camera features
08/Oct/2020: Release
Links!​
(V2.5.2)Google Drive
(V2.5.1)Google Drive
(V2.5)Google Drive
Prequisites​MANDATORY ALWAYS: SD Card. It IS possible to have it on internal storage but ONLY if you are not encrypted. If you are encrypted, then you will need to FORMAT DATA and that will delete everything in your internal storage and you won't be able to add it back to internal storage with TWRP because MTP is broken.​For installing 2.5.1/2.5.2:
Installing and following NcX 2.5 installation steps, as well as its prequesites
TWRP Installed (included in NcX 2.5)
Download multidisabler.zip (link: From Telegram Group (also attached on this thread) and add to SD Card or internal storage
Download Magisk zip installer to your SD Card or internal storage
For installing 2.5:
Update to bootloader U3 (either install OneUI 2.1 or OneUI 2.5 fully with Odin), otherwise you will have problems with camera
Fully unlock bootloader. I don't mean just turning OEM unlock on in developer settings , I mean FULLY unlock. If you didn't know, Samsung changed up how you unlock the bootloader on newer devices like this one. @topjohnwu gets a little more specific here: Explanation but I'm going to quote the important stuff to FULLY unlock bootloader:
Unlocking BL on modern Samsung devices have some caveats, so I figure this would be helpful.
Allow bootloader unlocking in Developer options → OEM unlocking
Reboot to download mode: reboot and press the download mode key combo for your device.
Long press volume up to unlock the bootloader. This will wipe your data and automatically reboot.
If you think the bootloader is fully unlocked, it is actually not! Samsung introduced VaultKeeper, meaning the bootloader will still reject any unofficial partitions before VaultKeeper explicitly allows it.
Go through the initial setup. Skip through all the steps since data will be wiped again later.
Connect the device to Internet during the setup.
Enable developer options, and confirm that the OEM unlocking option exists and is grayed out. This means the VaultKeeper service has unleashed the bootloader.
Your bootloader now accepts unofficial images in download mode.
Click to expand...
Click to collapse
Download Magisk zip installer to your SD Card or internal storage
Download multidisabler.zip (link: From Telegram Group and also attached in this thread) and add to SD Card or internal storage
Instructions!​For installing 2.5.1/2.5.2:
Reboot to TWRP
Flash NcX 2.5.1.img or NcX 2.5.2 as "super" image in TWRP
Reboot to Recovery
Format data if you are coming from Stock ROM. If you are coming from NcX 2.5 then you don't need to wipe or format, you can just skip this step.
Flash multidisabler (this is required always)
Flash Magisk zip (optional)
Reboot and wait patiently
For installing 2.5:
Reboot to download mode and add AP_NcX 2.5 A71 in AP on Odin
Uncheck the Auto reboot option in Odin
Flash
When it is finished, force a manual reboot (keep pressing VOL - and Power buttons together)
Immediately when phone reboots, boot to recovery mode (VOL + and Power button)
If your phone was unencrypted before, just do a normal wipe. If your phone was not unencrypted before, do a full data format (Go to WIPE option in TWRP, select FORMAT DATA button at the bottom and they type yes on the keyboard. This will completely wipe your internal storage so be sure to backup and photos, music, etc... you have in internal media.)
Flash multidisabler to ensure you do not get encrypted
Flash magisk (I don't know if this is mandatory, I would fully recommend it though)
Reboot and wait patiently
Credits!​ @ananjaser1211 for all your help and always willing to lend a helping hand
@SuperR. For his Super R's Kitchen which you can find here: https://forum.xda-developers.com/ap...dows-linux-superr-s-kitchen-v3-0-0-0-t3601702
@topjohnwu for Magisk
@sac23 for his tutorial on how to fix Secure Folder which you can find here: https://forum.xda-developers.com/showpost.php?p=82978861&postcount=1522
@Belco02 for the extra camera modes and features
@ianmacd in Telegram group TWRP/Root Samsung Android Devices for compiling TWRP for us
@ Samsung for the firmware
@ Team TWRP for their amazing recovery
@ To users like you!
If you feel I missed you, please give me a PM so I can add you
XDA:DevDB Information
NcX 2.5 for A71, ROM for the Samsung Galaxy A71
Contributors
ShaDisNX255, Ian Macdonald
Source Code: https://github.com/ianmacd/twrp_a71
Source Code: https://github.com/ianmacd/a71
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
Based On: OneUI 2.5
Version Information
Status: Stable
Current Stable Version: 2.5
Stable Release Date: 2020-10-08
Created 2020-10-08
Last Updated 2020-10-08

Join our Telegram group​
Code:
Check out the latest projects on our Telegram group, where we share our advancement on new things and try to help as best as we can.
For anything already released, please ask here in XDA
Link: Telegram Group
Join our Discord group​
Code:
Check out the latest projects on our Discord, where we share our advancement on new things and try to help as best as we can.
For anything already released, please ask here in XDA
Link: Discord
Android group in spanish
Link: Grupo Android​

FAQ
[Q] My phone is stuck in bootloop/infinite boot, what should I do?
[A] It is normal for first instalation to take aprox 10-20 minutes on first boot, let it sit for a little bit
[Q] Even after 20 minutes, my phone is still in a bootloop/infinite boot, what can I do?
[A] It is possible that your previoius Android setup is conflicting with this new setup. Please, do the following:
1. FORMAT DATA (not WIPE, FORMAT!)
2. Try the instalation of NcX again
[Q] I've found a bug, what should I do
[A] Please read the "Bugs" section of the thread to see if your bug has been reported, if it hasn't, please let me know exactly what the problem is so I can take a look
[Q] I flashed magisk on TWRP but no apps are asking for SU Permission
[A] Make sure you have the Magisk Manager app installed
[Q] I don't see Magisk Manager in my apps
[A] You need to download the manager from the official source: https://github.com/topjohnwu/Magisk
[Q] Something bothers me and I want it fixed/changed
[A] Please, kindly make a request and if it's within my grasp, I'll try to fix it. Just, don't be rude and demand something. Either that or return to stock, your choice

How to report a bug/Ask for a change​
Over the small amount of time I've been doing my edits and shared them with the community, I've noticed something that seems to irritate me. I can't speak for all the developers on this forum, but I do edits/ROMs/PORTs/etc... to what I like. I don't work for anybody else but me. I share my work because it may have something of value to other people and/or some people may share the same taste as me on regards to what they want on a ROM.
That being said, that doesn't mean I will completely ignore what the community has to say.
First and foremost, it must be said, I am merely a beginner. I do not claim to be a professional developer that knows how to add everything, I am nowhere close and I learn as I go.
There are ways to ask for something and/or report a bug when it comes to ROMs, and this post is my attempt to try to explain how to (and how not to) report a bug in order to help me out as much as possible to try to fix something
You can also ask for something to be added, but there are also ways to ask for something
So, here we go
Keep in mind:
I do not add stuff that can easily be downloaded from the Playstore
I, myself, don't do kernel edits
I COULD remove stuff if NOBODY uses it
---REPORTING BUGS---​
How NOT to report a bug:
"SystemUI (or any app)is crashing, please help!"
"Instagram doesn't allow me to edit my post, what could be wrong?"
"My bank account app is not letting me do such thing"
These posts are sort of pointless as they only state something but I have no context on what could be causing it. Also, I can't really control (for the most part) third-party apps, so if you're going to ask about them this way, don't even bother
A slightly better way to report a bug:
"I clean installed the ROM and was working fine, after I installed Facebook and logged in, I immediately uploaded a photo and SystemUI started to crash. Can you look in to it?"
"I tried to install Black Neon theme (a link to it would work as well) and it was working fine until I tried to activate AOD (or anything else for some reason) and SystemUI (or any other app) is crashing, could you look in to it?"
"My bank account app doesn't let me take a screenshot of my accounts. I get a toast notification saying "Can't take screenshot due to security policy"
As you can see, this provides a bit more context and explanation on your current situation. This gives me a little more detail on trying to replicate the problem and hopefully could fix it by replicating it. Well, except for point #3 which is out of my hands for the most part (I think). If you include what kernel you're using would make everything better! Also any significant change that would require root (like xposed and or anything that modifies /system also needs to be informed for better results)
The BEST way to report a bug:
LOGCAT!!!!!!!!!!!!!!!!!!
Please learn the ins and outs of a logcat, this really helps a lot on finding what the problem is. Also, please give a brief explanation as the above examples when providing a log cat
---ASKING FOR STUFF TO BE ADDED---​
How NOT to ask for stuff:
On your next update, add iris scanner
You should add (app) on your next update
Hey, please add (app or feature) on your next update
No, I do not work for you. Even if you say please like the third example, that doesn't mean you're being polite. It still sounds like an order lol so you should probably rephrase your request.
How to ask for stuff to be added to my work:
Would you be so kind to add (feature) to your ROM, if possible?
Would it be possible to add this app to your ROM?
Please, can you add (feature) to your ROM, if it isn't much to ask?
See how politeness makes everything better? You're not demanding it, you're just politely asking to see if maybe it is within my grasp to add something. And if all request would be like this, I can assure you I'd try my best to add said feature
I hope this is useful to you or I at least hope that some people read it.
If not, I can just tell you to return to stock ROM, probably better than any ROM I put out anyway

Enjoy guys, keep on the lookout for updates. I plan on adding more MODs and fixes

Attach the singletake .xml also here

sankhauaa said:
Attach the singletake .xml also here
Click to expand...
Click to collapse
I'll hold it off.
Plan on adding a future update with this and more stuff included

Good mod! Downloading...

well done mate, nice to see

New update hopefully tomorrow.
What's new?
-Fix Secure Folder, now working
-Fix Smart View mirroring, now working
-Adding CSC features, in progress

When i try to do the process of unlocking again It say after long press volume up. Lock Bootloader? Guess thats not what i want? My device is rooted stock with twrp installed..... Do you have an idea.?
I want to install your rom.

hans3103 said:
When i try to do the process of unlocking again It say after long press volume up. Lock Bootloader? Guess thats not what i want? My device is rooted stock with twrp installed..... Do you have an idea.?
I want to install your rom.
Click to expand...
Click to collapse
If you've already rooted, that means you have fully unlocked bootloader and it means that you can now freely install my ROM.

I installed it, it look very good. Its a big timesaver also. I used to root this device in a time comsuming way. This rom is very easy.... Very nice work!

hans3103 said:
I installed it, it look very good. Its a big timesaver also. I used to root this device in a time comsuming way. This rom is very easy.... Very nice work!
Click to expand...
Click to collapse
Thanks, next version will be easier to flash, just with super.img flash on TWRP.

ShaDisNX255 said:
Thanks, next version will be easier to flash, just with super.img flash on TWRP.
Click to expand...
Click to collapse
I will try it for sure, can I do an update or do I have to make a clean install?

hans3103 said:
I will try it for sure, can I do an update or do I have to make a clean install?
Click to expand...
Click to collapse
It can be installed with current version so no need to wipe data

ShaDisNX255 said:
It can be installed with current version so no need to wipe data
Click to expand...
Click to collapse
Very nice....many thanks!

nice business friend
Even if resizing in vendor, it will be nice because it will be very possible to make mod and custom kernel

No idea
my galaxy a71 its still in bootloop. bootloader fully unlocked with oem activated. data formated, installed decrypted data, and magisk zip installed, pls help..

zorexblade said:
my galaxy a71 its still in bootloop. bootloader fully unlocked with oem activated. data formated, installed decrypted data, and magisk zip installed, pls help..
Click to expand...
Click to collapse
Are you getting to boot animation?
Were there any red messages in TWRP when you were installing?

Development [CLOSED][ABANDONED] [OFFICIAL] [Rosemary/Secret/Maltose] Project Kasumi 1.x for Redmi Note 10S

{
"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"
}
Code:
#include <std_disclaimer.h>
/*
* Your warranty is... still valid?
*
* 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.
*/
Another weebified custom ROM aiming to be a home for weebs - Based on Project Materium, an optimized LineageOS-based Android aftermarket firmware with extra features, developed by people all over the world.
Quoting the LineageOS description:
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.
Click to expand...
Click to collapse
We offer vanilla, GApps and AuroraOSS variants. If you install a vanilla variant, the only supported GApps package is MindTheGapps (GApps/AuroraOSS builds are not available for a few devices due to space issues).
Download & instructions:
Install MIUI 12.5 if you have updated to anything Android 12.
Fully install custom recovery of your choice.
Flash the ROM. You can also sideload it with ADB if you want to.
!!! If you'll flash Magisk, you'll need to enable "Reflash (recovery) after installing a ROM" after choosing the ZIP as well !!!
After flashing, reboot to recovery.
Format data.
Flash Magisk if you want to.
Reboot to system and enjoy!
Download (Taken down due to discontinuation)
IMPORTANT: If you are coming from another ROM, you need to format data (TWRP > Wipe > Format Data > *type "yes"*).
IMPORTANT: If you want to keep Magisk after each OTA, you need to make it flash to inactive slot **right before rebooting** (Magisk > Install (In "Magisk" card) > Install to inactive slot)
About:
Features:
Latest security patches merged from LineageOS
SafetyNet passing unconditionally without Magisk/with kdrag0n's SafetyNet fix
Many optimizations coming from Stellar OS/Project Materium/droid-ng
New wallpapers & bootanimation
QS customization (tint, rows customizer, data usage)
Status bar customization (4G/LTE toggle, new NFC & VoLTE icons)
Kill app from notification
Notification pulse
KitKat-style notification ticker
Screenshot sound toggle
Per-app volume
WiFi & Bluetooth timeout
Smart Charging & Cutoff
Sensor, Wakelock and Alarm blocker
Battery info on lockscreen
Improved microG support (signature spoofing, location support)
...and more! (We accept suggestions!)
What's working:
Almost everything
Bugs:
Microphone doesn't work when speaker is enabled during calls.
You tell me.
Sources are available at https://github.com/ProjectKasumi and https://github.com/Kasumi-Devices
Full list of device sources used;
Device tree
Linux kernel tree used
Vendor tree for proprietary blobs
ROM Founded By: Yuki (AITEx64)
ROM Developed By: Beru Hinode
ROM Designed By: Ayuko, Qirkl and UsiF.
ROM OS Version: 1.3 "PoPiPa" R2
ROM Kernel: Customized Linux 4.14.186 from MiCode
ROM Firmware Required: MIUI 12.5.16.0.RKLMIXM (Global)
Based On: Project Materium 1.0 (LineageOS 18.1)
Version Information
Status: Discontinued
Last Stable Version: 1.4 "PoPiPa"
SELinux Status: Permissive
Initial Release Date: July 20, 2022

poggers! atleast some buildbot didn't post it this time

J6idot said:
poggers! atleast some buildbot didn't post it this time
Click to expand...
Click to collapse
It wasn't even their build, they just took my build and posted it away! XD

Let's goo. Very awesome work here

Amazing work!! Im a little disapointed with the note 10s
Hope to get the most out of it with a costum rom!
Miui on the 10s is a complete disaster... What the hell happened...

solidamage said:
Amazing work!! Im a little disapointed with the note 10s
Hope to get the most out of it with a costum rom!
Miui on the 10s is a complete disaster... What the hell happened...
Click to expand...
Click to collapse
I could never get used to MIUI myself so I feel you. For custom ROMs, there are quite a lot built (buildbotted) with practically the same bugs as well; you can check them out in respective Telegram groups/channels!

Hey there,
First of all, thx for bringing this
what about fast charging in these?
Would it work as expected?
Or as in every other GSI custom build i tested it doesn't work, and was kinda disappointing :/
Will the fix module be merged in the rom, making possible the avoid of magisk installing? Actually don't Care bout su and want m'y banking app to work
Hope to get your opinion soon

i followed the instructions to flash it down to the letter but cannot get it to boot. the phone will show the kasumi logo for a couple of minutes then just boots to fastboot. i am using orangefox recovery if that helps.

nintendobuster420 said:
i followed the instructions to flash it down to the letter but cannot get it to boot. the phone will show the kasumi logo for a couple of minutes then just boots to fastboot. i am using orangefox recovery if that helps.
Click to expand...
Click to collapse
It happens to me too ... Any advice?

Is this available on Android 12?

nintendobuster420 said:
i followed the instructions to flash it down to the letter but cannot get it to boot. the phone will show the kasumi logo for a couple of minutes then just boots to fastboot. i am using orangefox recovery if that helps.
Click to expand...
Click to collapse
Are you coming from 12.5.16 GLOBAL?
Do you format data before restarting?

Oxydeme said:
Are you coming from 12.5.16 GLOBAL?
Do you format data before restarting?
Click to expand...
Click to collapse
yup did all the steps in the thread

nintendobuster420 said:
yup did all the steps in the thread
Click to expand...
Click to collapse
Please, could you describe exactly the step you did?
As I didn't yet reinstalled all my apps, gonna try it out,
So i'll do as OP said to flash, probably tonight.
Are you really sure to come from Global version?
Have you tried with TWRP from Woomy?
All my previous tests were made with TWRP and appart i sometimes forget to format data After flash, once i did, it worked

Oxydeme said:
Please, could you describe exactly the step you did?
As I didn't yet reinstalled all my apps, gonna try it out,
So i'll do as OP said to flash, probably tonight.
Are you really sure to come from Global version?
Have you tried with TWRP from Woomy?
All my previous tests were made with TWRP and appart i sometimes forget to format data After flash, once i did, it worked
Click to expand...
Click to collapse
first I installed MIUI 12.5.16 global and completely erased the phone it had MIUI 13 before
then I installed orangefox by woomy
then I switched to slot B and installed the rom (gapps variant) also enabled reflash orangefox after installing rom
after installing I formatted data and installed magisk
then i rebooted and it bootlooped
i have a rosemary 10s with nfc

nintendobuster420 said:
first I installed MIUI 12.5.16 global and completely erased the phone it had MIUI 13 before
then I installed orangefox by woomy
then I switched to slot B and installed the rom (gapps variant) also enabled reflash orangefox after installing rom
after installing I formatted data and installed magisk
then i rebooted and it bootlooped
i have a rosemary 10s with nfc
Click to expand...
Click to collapse
Did you installed Magisk into the right slot?
@windowz414 is there any kind of vbmeta file to flash in order to be sure it would boot? An alternative boot IMG maybe? Or even a check disabler?
@nintendobuster420 finally gonna try flash tomorrow,
Did smtg else this evening, worked on a project, that isn't related at all to Android flashing x)
I also got a RN10S with NFC, maybe something related to variants?
Edit1: gonna try flashing Kasumi 1.3 PoPiPa Auroraoos 20220721; will update the post soon
Edit2: Kasumi auroraoos bootloop actually, reflashed auroraoos boot.img still bootlooping;
Gonna try with Kasumi classic, latest build to see
Edit3: Kasumi official 20220721 boolooping as well
Edit4: Will do a last attempt with Kasumi 20220716
Last attempt worked, I successfully booted up Kasumi, but with several differences
1- Backed up Pics and other important things for me;
2- Unlocked BL - Mi Unlock BL Tool latest version;
3- Switched Rom from 12.5.18EU to 12.5.16G with Mi Flash version 2018.5.28.0 (select fastboot rom, refresh, clean all, flash);
4- Booted once to get system settled
5- Installed TWRP from Womymy, booted on it
6- Switched Slot to B, Reflashed current recovery and rebooted from inside TWRP
NO I didn't, I switched to Slot B, reflashed recovery, got plenty errors, didn't rebooted in the end.
7- MTP mounted Storage and passed the zip rom
8- Flashed Kasumi, flashed again TWRP with the toggler while flashing rom, then directly formated format data,
9- Booted rom successfully!
still no fast charge, will keep it tough
@windowz414
Well done porting LOS dude!
Completely debloated
But still 13Go system
Little problem on CPU info
Battery seems good, phone is responsive, all the things that can be tweaked my god , bushido! Notification makes me smile
One word, net!
@HistoriaXV @nintendobuster420 hope you could success flash in the next days

Oxydeme said:
Hey there,
First of all, thx for bringing this
what about fast charging in these?
Would it work as expected?
Or as in every other GSI custom build i tested it doesn't work, and was kinda disappointing :/
Will the fix module be merged in the rom, making possible the avoid of magisk installing? Actually don't Care bout su and want m'y banking app to work
Hope to get your opinion soon
Click to expand...
Click to collapse
System reports "Charging slowly" but my battery fully charges from ~10% in just 1.5~2 hours.

nintendobuster420 said:
i followed the instructions to flash it down to the letter but cannot get it to boot. the phone will show the kasumi logo for a couple of minutes then just boots to fastboot. i am using orangefox recovery if that helps.
Click to expand...
Click to collapse
I have recently pushed a boot fix about this, you can flash it and format data to get it fixed.

Oxydeme said:
Please, could you describe exactly the step you did?
As I didn't yet reinstalled all my apps, gonna try it out,
So i'll do as OP said to flash, probably tonight.
Are you really sure to come from Global version?
Have you tried with TWRP from Woomy?
All my previous tests were made with TWRP and appart i sometimes forget to format data After flash, once i did, it worked
Click to expand...
Click to collapse
I use the OFOX from Woomy and it works with it too, so it's not recovery fault.
You mentioned firmware requirement there, good shot! Glad to see someone that's not from the development team finally noticing it!

Oxydeme said:
Did you installed Magisk into the right slot?
@windowz414 is there any kind of vbmeta file to flash in order to be sure it would boot? An alternative boot IMG maybe? Or even a check disabler?
Click to expand...
Click to collapse
The vbmeta required is shipped along with the ZIP itself, so whether if you disable it or not, you can always keep verity enabled AS LONG AS YOU DON'T MODIFY ANYTHING INCLUDING INSTALLATION OF TWRP. The boot problem was due to some missing permissions required with Lawnchair 12.0, which was platform-specific issue. I have mitigated it as the lead developer of Kasumi and now just waiting for LineageOS to merge August '22 ASB on their Lineage 18.1 branches to ship newer builds. Until then, I have placed a little flashable that you can slap in on the recovery. It's global (means will work on all devices with latest Kasumi build installed). In fact, all it does is just putting the new permission XML file.
Oxydeme said:
@nintendobuster420 finally gonna try flash tomorrow,
Did smtg else this evening, worked on a project, that isn't related at all to Android flashing x)
I also got a RN10S with NFC, maybe something related to variants?
Click to expand...
Click to collapse
Not at all. Even though I have Secret, everything should be around the same across all variants, given that Woomy also tested it only for NFC during initial bringup before.
Oxydeme said:
Edit1: gonna try flashing Kasumi 1.3 PoPiPa Auroraoos 20220721; will update the post soon
Edit2: Kasumi auroraoos bootloop actually, reflashed auroraoos boot.img still bootlooping;
Gonna try with Kasumi classic, latest build to see
Edit3: Kasumi official 20220721 boolooping as well
Edit4: Will do a last attempt with Kasumi 20220716
Last attempt worked, I successfully booted up Kasumi, but with several differences
1- Backed up Pics and other important things for me;
2- Unlocked BL - Mi Unlock BL Tool latest version;
3- Switched Rom from 12.5.18EU to 12.5.16G with Mi Flash version 2018.5.28.0 (select fastboot rom, refresh, clean all, flash);
4- Booted once to get system settled
5- Installed TWRP from Womymy, booted on it
6- Switched Slot to B, Reflashed current recovery and rebooted from inside TWRP
NO I didn't, I switched to Slot B, reflashed recovery, got plenty errors, didn't rebooted in the end.
7- MTP mounted Storage and passed the zip rom
8- Flashed Kasumi, flashed again TWRP with the toggler while flashing rom, then directly formated format data,
9- Booted rom successfully!
Click to expand...
Click to collapse
The dedication and the hassle... My God, it's just pure inspiration to me. XD
Oxydeme said:
still no fast charge, will keep it tough
Click to expand...
Click to collapse
As I said previously, it's what system reports presumably due to some SEL denials. I tried to get as many as possible sorted out, still no luck. But just as a fact, it actually is fast charging.
Oxydeme said:
@windowz414
Well done porting LOS dude!
Completely debloated
But still 13Go system
Little problem on CPU info
Battery seems good, phone is responsive, all the things that can be tweaked my god , bushido! Notification makes me smile
One word, net!
Click to expand...
Click to collapse
Well, thank you I guess. ^^;
Before I begin with replies to these, just referring to "dude", I'm a girl so I would prefer you calling me with "dudess" or "dudette" instead. Again, all up to you. No forces here.
The debloat is rather Lineage talent, I really just based on Materium and added things on top.
That 13 GB system partition is something that's coming from partition values from source, so whatever you do unless you flash GSI, it will always be 13 GB. See GitHub:Kasumi-Devices/[email protected]/BoardConfig.mk (Partitions section, BOARD_SYSTEMIMAGE_PARTITION_SIZE flag) for more info.
Eh, I still can't find a way to get CPU info properly, I guess it's related to kernel? Unsure though.
And some more tweaks will come as well, just stay tight! I'm working hard on another update! ;3

Sambit0789 said:
Is this available on Android 12?
Click to expand...
Click to collapse
Unfortunately no. Kasumi 1.x.x are all Android 11. Android 12 Kasumi will be possible only once our internal tests will be done and I finally finish working on Kasumi v2. Hundreds hyped, gradually widening audience, looking into the release of it. xD