[ROM][UNOFFICIAL] LineageOS 17.1 for Xperia 10 II [Stock-based] - Sony Xperia 10 II ROMs, Kernels, Recoveries, & Oth

[ROM][UNOFFICIAL] LineageOS 17.1 for Xperia 10 II [Stock-based] - Sony Xperia 10 II ROMs, Kernels, Recoveries, & Oth

Code:
#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.
*/
About LineageOS
LineageOS is a free, community built, aftermarket firmware distribution of Android 10.x (Q),
which is designed to increase performance and reliability over stock Android for your device.
All the source code for LineageOS is available in the LineageOS GitHub repo.
And if you would like to contribute to LineageOS, please visit our Gerrit Code Review.
Official LineageOS website : http://lineageos.org
About LineageOS Legal : http://lineageos.org/legal/
Important Information
1. This ROM has nothing related to ODM images! So you don't need to ask/install anything like that, just follow the instructions.
2. This ROM will never work with any versions of Google Camera (GCam)!
3. You need to flash Stock Android 10 before flashing this ROM.
4. For VoLTE, you need to boot into stock firmware and enable it before flashing this ROM!
5.If you cam from SODP ROMs, you need to go back to official Android 10 firmware, and boot into launcher.
6.This ROM works fo both dual and single models.
Downloads Links
LineageOS 17.1:
Unofficial-build: Link
Google Applications (optional):
OpenGapps: http://opengapps.org/ (ARM64->Android 10.0->Pico, Nano or Micro)
Information: Flash the GApps before the first boot. If not, a clean flash is recommended.
Flashing and updating
How to flash
Make sure you upgraded to Official Android 10.0 from Sony
Unlock bootloader is necessary.
Download latest platform-tools from google
1. Install fastbootd drivers, guidance
2. Download Lineage Recovery: AFH
3. Put your device into fastboot by volume up key.
4. Type the following command to flash the recovery:
Code:
fastboot flash recovery recovery.img
5. Enter fastbootd:
Code:
fastboot reboot fastboot
6. Flash LineageOS:
Code:
fastboot flash:raw boot boot.img
fastboot flash dtbo dtbo.img
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot --disable-verity --disable-verification flash vbmeta_system vbmeta_system.img
fastboot erase metadata
fastboot flash system system.img
fastboot flash product product.img
7. If you are first time to flash LineageOS, Wipe the old userdata:
Code:
fastboot erase userdata
Gapps:
After flashed images in fastbootd, choose Enter recovery - Apply update - Apply from ADB, then sideload the gapps package on your PC with adb tool:
Code:
adb sideload <PATH OF GAPPS>
Dolby Atmos:
Install magisk
1. Install Q-10__Dolby_Digital_Plus_v.7.3-_MMT-Ex_-20200519 from repey6.
2. Install Audio_Modification_Library-v4.0 from Magisk repo
3. Install sepolicy to permissive
4. Turn off AudioFX and reboot
Enjoy Dolby! All files I provide a mirror on AFH, you could downlaod from here.
Never flash oem from SODP!!
If you flashed oem and meet any issues, I could only say you are a hanhan.
Root access:
Flash Magisk in recovery.
Twrp:
See this: Link
Issues and reports
Report issues only if you are using the ROM kernel
If an additional mod is installed, make sure it's unrelated, and mention it
Make sure the issue wasn't discussed earlier in the threads
Share a log of the error with CatLog for example
Also thanks to:
Luk1337
The LineageOS Team
The CyanogenMod Team
XDA:DevDB Information
Lineage-17.1 for Xperia 10 II, ROM for the Sony Xperia 10 II
Contributors
Sjll
Source Code:
GitHub - sjllls/android_kernel_sony_sm6125
Contribute to sjllls/android_kernel_sony_sm6125 development by creating an account on GitHub.
github.com
GitHub - sjllls/android_device_sony_pdx201
Contribute to sjllls/android_device_sony_pdx201 development by creating an account on GitHub.
github.com
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
Version Information
Status: Stable
Created 2020-11-26
Last Updated 2020-11-30

FEATURES AND ISSUES
Code:
- Boot: Ok
- Bluetooth: Ok
- WiFi: Ok
- WiFi Hotspot: Ok
- Wireless display: Not tested
- RIL - Phone - Data: Ok
- VoLTE: Ok
- GPS: Ok
- Camera: Ok
- Camcorder: Ok
- Lights: Ok
- MicroSD: Ok
- Accelerometer: Ok
- Compass: Ok
- Gyroscope: Ok
- QTI sensors: Ok
- Touchscreen: Ok
- FM Radio: NA
- Fingerprint: Ok
- Vibrator: Ok
- Microphone: Ok
- Audio & music: Ok
- Bluetooth audio: Ok
- NFC: Ok
- Kernel: Ok
- Graphics: Ok
- 3D Rendering: Ok
- Clock: Ok
- DRM: Widewine L3
- Offline Charging: Ok
- USB: Ok
- USB Tethering: Ok
- USB OTG: Ok
- Encryption: Ok
- SEPolicies: Enforce

Res

hi, this might be a stupid question, but what part of this is from the stock firmware? i mean lineage OS is a complete ROM with its own kernel system etc. what is the benefit of combining it with stock? better HW compatibility? and does this affect OTA updates?

bamdadkhan said:
hi, this might be a stupid question, but what part of this is from the stock firmware? i mean lineage OS is a complete ROM with its own kernel system etc. what is the benefit of combining it with stock? better HW compatibility? and does this affect OTA updates?
Click to expand...
Click to collapse
this might be a stupid question
Click to expand...
Click to collapse
Not at all, good question.
what is the benefit of combining it with stock?...
Click to expand...
Click to collapse
Better user experience and better battery time than SODP lineageOS. Test it yourself please.
does this affect OTA updates?
Click to expand...
Click to collapse
If you mean stock FW update. This is LIneageOS, not stock FW, we will provide OTA once we get LineageOS official support.
what part of this is from the stock firmware?
Click to expand...
Click to collapse
Some stock blobs and some kernel drivers, but System is LineageOS. There is no difference with other phones.
i mean lineage OS is a complete ROM with its own kernel system etc
Click to expand...
Click to collapse
As above, system is LineageOS, blobs and kernel drivers are provided by Sony. This is the same as other phones supported by LineageOS.

thanks for the detailed answer. sounds really awesome. too bad i'm on mac os and it's really hard to flash the stock FW here. i'm going to try tomorrow, though. : )

Sjll said:
If you mean stock FW update. This is LIneageOS, not stock FW, we will provide OTA once we get LineageOS official support.
Click to expand...
Click to collapse
You're planning official certification by LineageOS down the line?
Any reason not to flash the OEM binaries, by the way? What's the recourse for fixing that and installing this if one's already flashed the SODP firmware?

You're planning official certification by LineageOS down the line?
Click to expand...
Click to collapse
Yup.
Any reason not to flash the OEM binaries, by the way? What's the recourse for fixing that and installing this if one's already flashed the SODP firmware?
Click to expand...
Click to collapse
Go back to official Android 10 firmware, and boot it.

is there any way to do this without installing the whole stock firmware? i understand that you cannot distribute parts of it due to some legal crap, but if i have the extracted files from the .ftf can i just use fastboot to flash those?
i'm asking because after 2 hours of headaches (installing mono for xperifirm, flashtool not recognising my firmware files, doing the whole thing again in a VM in virtualbox but failing on the USB being constantly disconnected etc.) it's obvious that doing this on OS X is damn near impossible - and i don't have access to a windows machine currently.

bamdadkhan said:
is there any way to do this without installing the whole stock firmware? i understand that you cannot distribute parts of it due to some legal crap, but if i have the extracted files from the .ftf can i just use fastboot to flash those?
i'm asking because after 2 hours of headaches (installing mono for xperifirm, flashtool not recognising my firmware files, doing the whole thing again in a VM in virtualbox but failing on the USB being constantly disconnected etc.) it's obvious that doing this on OS X is damn near impossible - and i don't have access to a windows machine currently.
Click to expand...
Click to collapse
Newflasher:
1. Download firmware with XperiaFirm.
2. Flash it with newflasher.
https://forum.xda-developers.com/cr...gress-newflasher-xperia-command-line-t3619426
Or fastboot:
1. 1. Download firmware with XperiaFirm.
2. Convert two sin files should named super_XXXXX.sin and oem_XXXX.sin with unsin.
https://forum.xda-developers.com/crossdevice-dev/sony/tool-unsin-sin-v3-unpacker-t3128106
3. After you get two .ext4 files, flash them via fastboot.
Code:
fastboot flash super super_xxxxxx.ext4
fastboot flash oem oem_xxxxxxxx.ext4

well i tried everything..
- spun up a VM with vagrant and copied over the .sin files, did an unsin but the super one only produced an .img not a .ext4. tried flashing that but it want't happy.
- so i tried flashtool's sin editor but that complained about this version of sin being too new.
- then i found some (bad) info in the net about using an *older* version of flashtool for this. of course that didn't work either.
even though i'm really interested in this (especially since the other lineage ROM has major bugs), i had to give up.

You didn't mention it in your description but in the download link it says this is for XQ-AU51 (single SIM). Will it still work on the dual SIM version XQ-AU52?

bmo2718 said:
You didn't mention it in your description but in the download link it says this is for XQ-AU51 (single SIM). Will it still work on the dual SIM version XQ-AU52?
Click to expand...
Click to collapse
I've got the XQ-AU52 and can confirm this runs fine on it. I don't use two sims though, so can't confirm whether or not that happens to work.

dreDREb13 said:
I've got the XQ-AU52 and can confirm this runs fine on it. I don't use two sims though, so can't confirm whether or not that happens to work.
Click to expand...
Click to collapse
Don't plan on using two SIMS either, but in the thread for the other rom it was specifically stated that it only works for one variant.
Anyway, thanks for the reply, I will try it.

Hi @Sjll, do you think that this commit will help activating L1 for Xperia 10 II and possible another mark II devices?
Luk added that on Xperia XA2 and enabled widevine L1 for it

I have some questions
1)Will you add suport of Google Camera?
2) Does Google Pay work? and will it work in future? A heard something like that Google want start check Safenet with hardware solutions
Stock ROM doesn't has Level3 and RAW Capture

1) Read first post, there is the answer
2) If Safetynet pass CTS, will work Google Pay. About the future, if Google decides to check hardware, there is no way to pass CTS, so no Google Pay. The developer of Magisk has a twit about that explaining.

Hmm, I got this:
Code:
erasing 'metadata'...
FAILED (remote: Erasing is not allowed for partition)
...
sending sparse 'system' 1/2 (773764 KB)...
OKAY [ 21.700s]
writing 'system' 1/2...
FAILED (remote: No such partition.)
Edit:
All good now, I didnt boot correctly in fastbootd mode.

bamdadkhan said:
well i tried everything..
- spun up a VM with vagrant and copied over the .sin files, did an unsin but the super one only produced an .img not a .ext4. tried flashing that but it want't happy.
- so i tried flashtool's sin editor but that complained about this version of sin being too new.
- then i found some (bad) info in the net about using an *older* version of flashtool for this. of course that didn't work either.
even though i'm really interested in this (especially since the other lineage ROM has major bugs), i had to give up.
Click to expand...
Click to collapse
usin is enough for you to unpack these sin file, you could flash these files unpacked by it. .ext4 is only an example,.
If you want to go back to stock, you need to reloack your device, then repair it with Xperia Companion.
bmo2718 said:
You didn't mention it in your description but in the download link it says this is for XQ-AU51 (single SIM). Will it still work on the dual SIM version XQ-AU52?
Click to expand...
Click to collapse
SS/DSDS configs stored in vendor partition. So it's depend on your stock FW version.
Meloferz said:
Hi @Sjll, do you think that this commit will help activating L1 for Xperia 10 II and possible another mark II devices?
Luk added that on Xperia XA2 and enabled widevine L1 for it
Click to expand...
Click to collapse
We are using stock vendor blobs, so these files are never missing, you could only get L3 level on unlocked status.
adem_blackv said:
I have some questions
1)Will you add suport of Google Camera?
2) Does Google Pay work? and will it work in future? A heard something like that Google want start check Safenet with hardware solutions
Stock ROM doesn't has Level3 and RAW Capture
Click to expand...
Click to collapse
Gcam is really nice, but as you said, Xperia 10 II doesn't support RAW support, if I have time, I will try to port camera hal from SODP, which support RAW.
Meloferz said:
1) Read first post, there is the answer
2) If Safetynet pass CTS, will work Google Pay. About the future, if Google decides to check hardware, there is no way to pass CTS, so no Google Pay. The developer of Magisk has a twit about that explaining.
Click to expand...
Click to collapse
Sorry, GMS is not avaliable in China. You could try to pass Saftynet with some Magisk modules. I don't know much about it.

Sjll said:
We are using stock vendor blobs, so these files are never missing, you could only get L3 level on unlocked status.
Click to expand...
Click to collapse
I know that we get L3 for widevine after unlocking bootloader, I just point you with that commit if could help to activate L1 for the Xperia 10 II with LOS, because Luk (Xperia XA2 series maintainer for LOS) could activate L1 for it with bootloader unlocked and using Lineage OS

After everyth
Meloferz said:
I know that we get L3 for widevine after unlocking bootloader, I just point you with that commit if could help to activate L1 for the Xperia 10 II with LOS, because Luk (Xperia XA2 series maintainer for LOS) could activate L1 for it with bootloader unlocked and using Lineage OS
Click to expand...
Click to collapse
I guess this is because nile platform has L1 after unlocked on Pie on stock. But we only have L3 on stock.
https://review.lineageos.org/c/LineageOS/android_device_sony_nile-common/+/269526

Related

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?

[OFFICIAL] [NIGHTLIES] LineageOS 16.0

Reserved

Reserved

Thank you， ota ：）

How to get root on LOS 16?
There's no official root binary for LOS 16: https://download.lineageos.org/extras

7bob said:
How to get root on LOS 16?
There's no official root binary for LOS 16: https://download.lineageos.org/extras
Click to expand...
Click to collapse
Check again.

Just finished installing Lineage 16 on my moto z2 force, I cannot find the option for locking the screen by using the fingerprint that came originally with the phone. Is this feature available on lineage 16?

zidemizar said:
Just finished installing Lineage 16 on my moto z2 force, I cannot find the option for locking the screen by using the fingerprint that came originally with the phone. Is this feature available on lineage 16?
Click to expand...
Click to collapse
Yes. If you aren't seeing it, I'd suspect you're using an unsupported addon, or your hardware is failing.
It shows up/works fine here.

npjohnson said:
Check again.
Click to expand...
Click to collapse
Thanks, now I see it.
Is there something I have to consider when updating a Z2 Force from 15.1 to 16? Or can I just follow the general update guidelines?

7bob said:
Thanks, now I see it.
Is there something I have to consider when updating a Z2 Force from 15.1 to 16? Or can I just follow the general update guidelines?
Click to expand...
Click to collapse
Just follow general guidelines. We already had testers and upgrading from 15.1 to 16.0 didn't cause any issues. Obviously, if you do run into an issue, it is suggested to clean flash first to see if it was a borked update

npjohnson said:
Yes. If you aren't seeing it, I'd suspect you're using an unsupported addon, or your hardware is failing.
It shows up/works fine here.
Click to expand...
Click to collapse
Do you have a screenshot showing that it shows under screenlock settings?
Also what gaaps did you use when installing, I used the reccomended mindthegaaps and it kept giving me errors related to pixel apks.

link if image does not work
https://imgur.com/a/1eoVcgk
This is what shows under my screenlock setting, I do not have the setting that allows me to lock the phone using the fingerprint reader, this is from a fresh Lineage 15.1 installation with mindthegaaps, nothing else is installed on it. Had the same issue with lineage 16

Am I able to install Lineage 16 on Sprint Moto Z2 Force? I will get the phone next week, so I don't know if it's nash or what? Thanks.

Now I have installed los 16 and it was instructive for me. Learning by doing. After I have get working TWPR on both slots, data area of los 16 was suddenly encoded and requires a passwort for it on TWRP start to use it. So backup of intern data fails. Ok so far, we have two slots and that's anyway the backup. But how will work the update process? Just over the updater-function in settings/system or over TWRP? I'm on slot b now and on system_a is nothing. If I want update later, I have to do just flash the zip over TWRP and then reboot it and then maybe flash gapps again, because it's the first update on slot_a? Hope that's works because the encoding problem. Don't have the key.

AmazerG said:
Am I able to install Lineage 16 on Sprint Moto Z2 Force? I will get the phone next week, so I don't know if it's nash or what? Thanks.
Click to expand...
Click to collapse
Sure. It works on TMO and SPR, just no VZ and ATT for obvious reasons. Nash is the internal name for the Z2.
allrightlite said:
After I have get working TWPR on both slots, data area of los 16 was suddenly encoded and requires a passwort for it on TWRP start to use it. So backup of intern data fails. Ok so far, we have two slots and that's anyway the backup. But how will work the update process? Just over the updater-function in settings/system or over TWRP?.
Click to expand...
Click to collapse
Remove your fingerprint and screen lock method prior to entering TWRP. If you came from a stock ROM you must format data before flashing LOS. Updates can be done automatically with the updater, or manually thru recovery. The latter requires more time with no added benefits. Also encryption is enabled with custom ROMs.

So I was able to successfully update from 15.1 to 16.0. Here's what I did:
Backup my data
Boot into bootloader
Code:
fastboot boot twrp-3.2.3-2-nash.img
In TWRP, wipe System partition, then start sideload
Code:
adb sideload lineage-16.0-20190305-nightly-nash-signed.zip
reboot into bootloader
Code:
fastboot boot twrp-3.2.3-2-nash.img
In TWRP, start sideload
Code:
adb sideload MindTheGapps-9.0.0-arm64-20190216_211116.zip
Code:
adb sideload addonsu-16.0-arm64-signed.zip
reboot
done

I have tries at this moment to update over the lineage updater in settings and it's stopping with installation error. After try to reboot to TWRP it's endet up in reboots. But LOS16 stats normally again after press power button a little bit. Now I try again to update. Presumably it isn't working again. I think I will reflash twrp first and try then over this to update. Good idea or what's going wrong on my phone?
I must do new install. All broken. Holy crap. Hope this time I get it working.

7bob said:
So I was able to successfully update from 15.1 to 16.0. Here's what I did:
Backup my data
Boot into bootloader
Code:
fastboot boot twrp-3.2.3-2-nash.img
In TWRP, wipe System partition, then start sideload
Code:
adb sideload lineage-16.0-20190305-nightly-nash-signed.zip
reboot into bootloader
Code:
fastboot boot twrp-3.2.3-2-nash.img
In TWRP, start sideload
Code:
adb sideload MindTheGapps-9.0.0-arm64-20190216_211116.zip
Code:
adb sideload addonsu-16.0-arm64-signed.zip
reboot
done
Click to expand...
Click to collapse
what are the steps to update from firmware 8.0 to LineageOS 15.1 or 16, please
unlock bootloader, twrp, magisk (no problem),
My phone locks the boot loader again when I try to install a custom ROM
my firmware (TWRP, magisk)
RETAIL/NASH_RETAIL_8.0.0_OPXS27.109-34-19_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
in any way I thank you :good:

Ok, I have found out how get it working. Updater app not working here, always installation error after end of update process. Don't know why. So now I have a way found out, which seems to be working every update. Go to TWRP, flash los16 new zip and, this is very important (understand it very late xD) don't forget to flash twrp installer zip directly after los 16, because otherwise on the other slot is the stock recovery again. So, after this boot to the other slot with twrp directly from your phone and flash gapps every time, every update. Here I forgot it and nothing of the play store and co. was working anymore. Android Framework ID was away, too. Is there an easier way to update over TWRP or do I have to do so? And what happend to, backup wasn't possible to restore, maybe cause thought encoding?
The new update process with A/B is not easy to understand directly But the rom is a beast, very very good. Why I update and switch to los16? That's easy, because the bluetooth bugs on stock oreo was terrible (and no 8.1-batterie icon ) and lags on few drm videos and here and there. Speed of the UFS-flash going slower and slower, no its 3 times faster again. This phone works really great with LOS16. Very good work! It's not easy to understand all, but I will get it in my brain
Edit: There is another point, which could be interesting. Netflix shows error on start up (15001) and this even though safety net is passed. Hm.. Have downloaded from play store. Maybe older version does do this job, don't know.

Ace42 said:
Sure. It works on TMO and SPR, just no VZ and ATT for obvious reasons. Nash is the internal name for the Z2.
Click to expand...
Click to collapse
Is there anything different between Sprint Z2 force and Tmo ones in terms of hardware such as lack some band or what?

[ROM] DivestOS 20.0 for mata

{
"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"
}
DivestOS is a more private and more secure aftermarket system.
Essential Phone Notes:
- please install PH1-Images-QQ1A.200105.032.zip to both slots first!
edit 2022: firmware is included for a while now
- relocking does work, just take the steps slow and test before locking
- device must be relocked to enable verified boot
- phone call audio can be weird, toggling speaker phone usually fixes it
- phone call audio over bluetooth doesn't always work
- phone call speaker phone volume cannot be adjusted
- in-place upgrade from 17.1 to 18.1 has been tested working
- in-place upgrade from 18.1 to 19.1 has been tested working
Features:
- strong focus on FOSS
- various system hardening
- various privacy enhancements
- automated removal of unnecessary proprietary blobs
- automated kernel hardening and CVE patching
- ability to relock bootloader on supported devices
- verified boot on supported devices
- no root support
- SELinux always enforcing
- encrypted by default
- monthly updates
- OTA delta updates
- OTA updates over Tor (optional)
- F-Droid included
- hardened system WebView with rapid updates: https://divestos.org/misc/ch-dates.txt
Extra Features (not installed by default & also compatible with all systems):
- Mull, our hardened fork of Fenix with rapid updates: https://divestos.org/misc/ffa-dates.txt
- Hypatia, our real-time malware scanner
- Extirpater, our free space eraser
Links:
- Website: https://divestos.org
- Onion: http://divestoseb5nncsydt7zzf5hrfg44md4bxqjs5ifcv4t7gt7u6ohjyyd.onion
- Downloads: https://divestos.org/index.php?page=devices&base=LineageOS#device-mata
- Changelogs: https://divestos.org/index.php?page=news
- Project History: https://divestos.org/index.php?page=history
- Known Issues: https://divestos.org/index.php?page=broken#mata
- Screenshots: https://divestos.org/index.php?page=screenshots
- Security Patching Overview: https://divestos.org/index.php?page=patch_levels
- About + Credits + Notices: https://divestos.org/index.php?page=about
- Donate: https://divested.dev/donate
- Source Code: https://github.com/divested-mobile or https://gitlab.com/divested-mobile
- XMPP Chat Room: xmpp:[email protected]
Device Specific Links
- Device Tree: https://github.com/LineageOS/android_device_essential_mata
- Kernel: https://github.com/LineageOS/android_kernel_essential_msm8998
- Kernel CVE Patches Applied: https://github.com/Divested-Mobile/..._Patchers/android_kernel_essential_msm8998.sh
Other Bits:
- Good and bad feedback is welcomed. Else how can we improve?
- If you find a bug, please report it below or via GitHub/GitLab.
- Testing/Translations/Code contributions are gratefully appreciated.
Important Notes for New Users:
- Please make a backup of your device and copy it to another computer.
- You must wipe before installing this OS.
- This OS has userdata encrypted by default
- You are intended to relock your bootloader with this OS (if your device is marked supported for that).
DivestOS does *not* support the following:
- Google Apps (OpenGAPPS)
- DRM (Widevine)
- alternative recoveries (TWRP)
- root (Magisk)
- runtime modification frameworks (Xposed or theme engines)
All downloads are GPG signed with the following key:
Code:
#B874 4D67 F9F1 E14E 145D FD8E 7F62 7E92 0F31 6994
-----BEGIN PGP PUBLIC KEY BLOCK-----
mDMEXupIxBYJKwYBBAHaRw8BAQdAC1RiTvrqJaAQ4FIHsxX+gzEgdT4mspISS+p0
y847Nge0SERpdmVzdE9TIFJlbGVhc2UgU2lnbmluZyAoMjAyMCAjMSkgPHN1cHBv
cnQrcmVsZWFzZXNpZ25pbmdAZGl2ZXN0b3Mub3JnPoiQBBMWCAA4FiEEuHRNZ/nx
4U4UXf2Of2J+kg8xaZQFAl7qSMQCGwMFCwkIBwIGFQoJCAsCBBYCAwECHgECF4AA
CgkQf2J+kg8xaZR1BgEAwwLVVsG7kbp8M3GTV987XpVl5cZeTtDc/g+66briCHUB
APiuH/dk8eRnhFnq4Up2/j7uD/8FtSvxPbHiz6t1MdgB
=VzP2
-----END PGP PUBLIC KEY BLOCK-----

SkewedZeppelin said:
relocking does work, just take the steps slow and test before locking
Click to expand...
Click to collapse
I'm interested to try DivestOS on mata, especially because of the potential for relocking.
I'm fairly sure that when I first unlocked bootloader it was with fastboot flashing unlock followed by fastboot flashing unlock_critical.
If relocking is still possible would I have to fastboot flashing lock_critical first, followed by fastboot flashing lock?

chrisrg said:
I'm interested to try DivestOS on mata, especially because of the potential for relocking.
I'm fairly sure that when I first unlocked bootloader it was with fastboot flashing unlock followed by fastboot flashing unlock_critical.
If relocking is still possible would I have to fastboot flashing lock_critical first, followed by fastboot flashing lock?
Click to expand...
Click to collapse
Lock should cover critical.

Thanks for that.
Carefully following instructions here to prepare the phone and subsequent flashing of the DivestOS all went smoothly.
Post install I downloaded the latest OTA update and did a bit of testing before locking the bootloader with fastboot flashing lock command.
Very nice, thanks .

Want to give this a try on my PH-1. I am on LineageOS 18.1 latst build. Anything in specific I should take care of? Any pitfalls?
Edit: Took sometime to clean-up and go back to the mentioned stock firmware. The flash went through fine. Will test things out first and then dare to relock

Dear DivestOS maintainer.
I`m using a DivestOS for almost a year.
Recently i start facing an issue, that my camera cannot send information to the servers. I cannot use it for a face identification and QR codes approvals.
Is this a new feature? Or i mess with something and have to reflash the rom?

WillWire said:
Dear DivestOS maintainer.
I`m using a DivestOS for almost a year.
Recently i start facing an issue, that my camera cannot send information to the servers. I cannot use it for a face identification and QR codes approvals.
Is this a new feature? Or i mess with something and have to reflash the rom?
Click to expand...
Click to collapse
Can you elaborate?
mata is my daily driver, it is very stable.
If you mean no camera app works, do you have the 'sensors off' tile enabled? That disables the camera in addition to sensors.
If you mean the camera app works, but some apps that use the camera don't, can you say which app?

SkewedZeppelin said:
Can you elaborate?
mata is my daily driver, it is very stable.
If you mean no camera app works, do you have the 'sensors off' tile enabled? That disables the camera in addition to sensors.
If you mean the camera app works, but some apps that use the camera don't, can you say which app?
Click to expand...
Click to collapse
Sorry for a late reply. Forced to flash back to latest LOS.
Apps which are not working are Binance, Wirex, WhatsApp(I hate it, but have to use it)
Basically operations such as scan QR code or Face Id were not working.

SkewedZeppelin said:
Can you elaborate?
mata is my daily driver, it is very stable.
If you mean no camera app works, do you have the 'sensors off' tile enabled? That disables the camera in addition to sensors.
If you mean the camera app works, but some apps that use the camera don't, can you say which app?
Click to expand...
Click to collapse
It appears to be LOS or MicroG issue. Same here on latest LOS. i was thinking of Bromite, but problem persists on LOS WebView.

WillWire said:
Sorry for a late reply. Forced to flash back to latest LOS.
Apps which are not working are Binance, Wirex, WhatsApp(I hate it, but have to use it)
Basically operations such as scan QR code or Face Id were not working.
Click to expand...
Click to collapse
The first two sound SafetyNet related.
I don't use WhatsApp, but afaik it should fully work without Google Apps.

SkewedZeppelin said:
The first two sound SafetyNet related.
I don't use WhatsApp, but afaik it should fully work without Google Apps.
Click to expand...
Click to collapse
Nope, SafetyNet is passable using MicroG.
WhatsApp is .... , but it required to communicate with my employer.
Otherwise i'm using only Matrix/Telegram/Status/Briar.

SkewedZeppelin said:
The first two sound SafetyNet related.
I don't use WhatsApp, but afaik it should fully work without Google Apps.
Click to expand...
Click to collapse
Nope, SafetyNet is passable using MicroG.
WhatsApp is .... , but it required to communicate with my employer.
Otherwise i'm using only Matrix/Telegram/Status/Briar.
SkewedZeppelin said:
The first two sound SafetyNet related.
I don't use WhatsApp, but afaik it should fully work without Google Apps.
Click to expand...
Click to collapse
Just after couple another atempts, i may say that it is looks like a Zygisk issues. Whent i enable Denylist Binance is giving a WebView error.
I was thinkinh of Bromite WebView at first, but apparently it was not as issue.
Great Rom, will be comming back soon)).
Another anoyance for myself, why Mata camera360 and AptX drivers are disabled? As they are available in LOS.
Camera is heavilly GMS dependant, i understand. But AptX is not.
Is there any security concern regarding this thechnology?

very happy with this rom so far. I have been using it as a daily driver for 2 weeks now and I will continue to use it. i will be sure to post any issues i find here.... thanks!

Anyone had issues with the "adb sideload copy-partitions-mata.zip"? It fails for me on setup to install sideloaded zip with `permission denied` on unmount of /vendor/firmware_mnt.
This particular phone really doesn't like fastboot (any version) and/or my USB cables, but occasionally it will work. One lucky session I got DivestOS (system, vendor, and boot) onto slot a successfully.
Aside: I appear to have triggered the dm-verity corruption along the way with my flashing of various ASOP (GSI thread) and lineageOS. I don't think it is related to this error.

chaseadam said:
It fails for me on setup to install sideloaded zip with `permission denied` on unmount of /vendor/firmware_mnt.
Click to expand...
Click to collapse
This is a known issue with the DivestOS recovery for mata. I have no idea why it happens, spent hours trying to figure it out.
chaseadam said:
This particular phone really doesn't like fastboot (any version) and/or my USB cables, but occasionally it will work. One lucky session I got DivestOS (system, vendor, and boot) onto slot a successfully.
Click to expand...
Click to collapse
Mata was my daily driver, and is still actively tested. It does work well aside from the recovery quirk.
chaseadam said:
Aside: I appear to have triggered the dm-verity corruption along the way with my flashing of various ASOP (GSI thread) and lineageOS. I don't think it is related to this error.
Click to expand...
Click to collapse
Recommend flashing stock then DivestOS again.
The official mata stock is no longer available, but you can find mirrors of it.
Here is the sha512sum for you to verify against
a9d979fdde4b2b59ff9c0c1256f440b4d5250242179648494a9b641ca75b4911cae666b6197162b6a93009b94cdc07f9f04df2bd0a72e819db09f7392f60ddde PH1-Images-QQ1A.200105.032.zip

SkewedZeppelin said:
This is a known issue with the DivestOS recovery for mata. I have no idea why it happens, spent hours trying to figure it out.
Click to expand...
Click to collapse
So if you haven't run that copy-partitions-mata.zip, did you re-lock your bootloader? If so, what was your procedure? My understanding is both slots need to be the same for the re-lock to work (without bricking?)
SkewedZeppelin said:
Mata was my daily driver, and is still actively tested. It does work well aside from the recovery quirk.
Click to expand...
Click to collapse
That quirk is annoying, and just when I am about to give up, it starts a "working" fastboot session
SkewedZeppelin said:
Recommend flashing stock then DivestOS again.
The official mata stock is no longer available, but you can find mirrors of it.
Here is the sha512sum for you to verify against
a9d979fdde4b2b59ff9c0c1256f440b4d5250242179648494a9b641ca75b4911cae666b6197162b6a93009b94cdc07f9f04df2bd0a72e819db09f7392f60ddde PH1-Images-QQ1A.200105.032.zip
Click to expand...
Click to collapse
Had that stock already downloaded, so after a bunch of "banging" at it, the flashboot writes finally got through (lots of reboots and re-plugging).
This was my sequence to get past the "device is corrupt” dm-verity message and boot to DivestOS
slot A has latest Stock
slot B has DivestOS
Boot to slot A
adb reboot "dm-verity enforcing"
boot into Stock
switch to slot B
format userdata
boot DivestOS without dm-verity warning!

double post

double post

chaseadam said:
So if you haven't run that copy-partitions-mata.zip, did you re-lock your bootloader? If so, what was your procedure? My understanding is both slots need to be the same for the re-lock to work (without bricking?)
Click to expand...
Click to collapse
My bootloader has been locked for like 3 years, never unlocked except for testing.
In the case of mata, that isn't needed because firmware is included.
Also try cleaning out your usb port, and using a usb-2.0 port on your computer.

SkewedZeppelin said:
My bootloader has been locked for like 3 years, never unlocked except for testing.
In the case of mata, that isn't needed because firmware is included.
Click to expand...
Click to collapse
Great news! I hope to get to a locked state soon as well.
I see references to "firmware is included" (your comment) and "firmware-empty" and "A/B devices only without firmware enabled".
What is this "firmware" in relation to the boot, system, vendor and other images? Is the firmware related to AVB?
Is the PH-1 an AVB device? (does it require working with `avb_custom_key` in fastboot)
I am attempting to be thorough because of all the warnings about locking resulting in a brick.
Aside: There is mention of "full" and "yes, ue" in the firmware-empty status. What do "ue" and "full" mean?

[ROM][RAV/SOFIA][11][UNOFFICIAL] PixelExperience (Plus) [AOSP]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
PixelExperience for [RAV*/SOFIA*]
What is this?
PixelExperience is an AOSP based ROM, with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts, boot animation)
Our mission is to offer the maximum possible stability and security, along with essential and useful features for the proper functioning of the device
Based on Android 11
Whats working?
Wi-Fi
RIL
Mobile data
GPS
Camera
Flashlight
Camcorder
Bluetooth
Fingerprint reader
Face unlock
Lights
Sound/vibration
Known issues
FM Radio
You tell me
Downloads
Link to Post
Installation
Link to Post
Donate
Liked my work? Give me a beer
Translation
Help with project translation
Stay tuned
Our Telegram channel
Our blog
Android OS version: 11
Security patch level: November 2021
Build author/Device Maintainer: AbsoluteZeroEdge
Kernel Source: https://github.com/S4muel007/kernel_motorola_trinket
Device Source: https://github.com/ph4n70m-404/device_motorola_sofiar
Vendor Source: https://github.com/ph4n70m-404/vendor_motorola_sofiar
Source code: https://github.com/PixelExperience
ROM Developer: jhenrique09
Contributors
Vache for initial device and vendor sources + TWRP
ph4n70m & Beetle84 for tons of building help
S4muel007 for kernel
Thanks awesome peeps
ROM OS Version: Android 11
ROM Kernel: Linux 4.x
Based On: AOSP
Version Information
Status: Stable
Created 2021-11-20
Last Updated 2021-11-21

Download Links
TWRP
TWRP - Credit to Vache
https://drive.google.com/file/d/1SwiiptkODqLTnDF1GRknYrF2g2yPxdJY/view
Pixel Experience
11/20/2021 Build - Initial Build
https://drive.google.com/drive/folders/1pdStP6Rnph19wIu_plpDwjRa124yJvNK?usp=sharing
11/21/2021 Build - Added Moto Camera 2
https://drive.google.com/drive/folders/1dSnZUiuK5TlOEtZU8oQIbjjV-TxJgFyr?usp=sharing

Installation
DON'T FLASH GAPPS, THEY'RE ALREADY INCLUDED
FastbootD
1) Extract rom zip and open cmd prompt in the extracted folder
2) Reboot into fastbootd
Code:
fastboot reboot fastboot
3) Flash images
Code:
fastboot flash boot boot.img
fastboot flash vbmeta vbmeta.img
fastboot flash product product.img
fastboot flash system system.img
4) Format data
Code:
fastboot -w
5) Reboot, profit.
TWRP
1) Boot to bootloader
2) Flash TWRP (included download above)
Code:
fastboot flash recovery_a twrpfile.img
fastboot flash recovery_b twrpfile.img
3) Flash the rom
4) Format Data (not factory reset)
5) Reboot, Profit
5.1) (Optional) If magisk is desired flash it in TWRP after first boot

Reserved

I would like to try this but I have a question:
Is this rom for sofia or sofiar? The title of the post says sofia but the download link says sofiar.
which is it? I have the U.S. retail version of the Moto G Power, which is sofia.

classic757 said:
I would like to try this but I have a question:
Is this rom for sofia or sofiar? The title of the post says sofia but the download link says sofiar.
which is it? I have the U.S. retail version of the Moto G Power, which is sofia.
Click to expand...
Click to collapse
Yes it should work,
In the title it shows rav*/sofia* for wildcards meaning any rav*, or sofia* device

AbsoluteZeroEdge said:
Yes it should work,
In the title it shows rav*/sofia* for wildcards meaning any rav*, or sofia* device
Click to expand...
Click to collapse
Okay thank you. If I give it a try I will let you know how it goes.

I originally installed Beetle84's Havoc Rom, which he/she no longer supports, on my Moto G Power 2020 XT2041-4 using FlashbootD, but, soon, my battery life diminished until it barely lasted a day. So, I tried to flash the new Lineage 18.1, but it failed and I had to Rescue my device. It's now running the stock Android 11 (A!11) Rom. Other Cooks have suggested that I can't flash another Rom until I downgrade the device to A10, which I haven't been able to do. I wanted to try Vache's Moto Flash Tool, but I can't find instructions online. Do I have to downgrade to A10 to flash this Rom? If not, can I just follow the above instructions which are similar to Beetle84's instructions I successfully followed when I flashed his Havoc A11 Rom? Also, how does this Rom compare to Havoc?
Thanks

jhford said:
I originally installed Beetle84's Havoc Rom, which he/she no longer supports, on my Moto G Power 2020 XT2041-4 using FlashbootD, but, soon, my battery life diminished until it barely lasted a day. So, I tried to flash the new Lineage 18.1, but it failed and I had to Rescue my device. It's now running the stock Android 11 (A!11) Rom. Other Cooks have suggested that I can't flash another Rom until I downgrade the device to A10, which I haven't been able to do. I wanted to try Vache's Moto Flash Tool, but I can't find instructions online. Do I have to downgrade to A10 to flash this Rom? If not, can I just follow the above instructions which are similar to Beetle84's instructions I successfully followed when I flashed his Havoc A11 Rom? Also, how does this Rom compare to Havoc?
Thanks
Click to expand...
Click to collapse
unfortunately yes you have to downgrade to a10 for the rom to boot
for downgrade instructions it's rather self explanatory. just drop ur stock 10 firmware zip in the firmware folder and start the flash
after u downgraded just use the installation guide above
And for how it compares, Not sure. It's basically AOSP but with google apps, It's like havoc but more bare and made for pixel fans that want the pure pixel experience
if u want more features I would definitely point u towards ph4n70m's havoc build

AbsoluteZeroEdge said:
unfortunately yes you have to downgrade to a10 for the rom to boot
for downgrade instructions it's rather self explanatory. just drop ur stock 10 firmware zip in the firmware folder and start the flash
after u downgraded just use the installation guide above
And for how it compares, Not sure. It's basically AOSP but with google apps, It's like havoc but more bare and made for pixel fans that want the pure pixel experience
if u want more features I would definitely point u towards ph4n70m's havoc build
Click to expand...
Click to collapse
Thank you, but I don't understand this: "just drop ur stock 10 firmware zip in the firmware folder and start the flash." So, can you please give me specific downgrade instructions. I've tried and failed at least 6 times.

jhford said:
Thank you, but I don't understand this: "just drop ur stock 10 firmware zip in the firmware folder and start the flash." So, can you please give me specific downgrade instructions. I've tried and failed at least 6 times.
Click to expand...
Click to collapse
Well, in moto flash tool's root directory it has a firmware folder to place your device's stock firmware for it to flash, after that is done open up the tool and select the stock 10 package u placed

AbsoluteZeroEdge said:
Well, in moto flash tool's root directory it has a firmware folder to place your device's stock firmware for it to flash, after that is done open up the tool and select the stock 10 package u placed
Click to expand...
Click to collapse
I have done that both zipped and unzipped several times and it has always failed. Maybe I downloaded the wrong firmware. I got it from lolinet. Do you have a link for the correct A10 firmware for Moto G Power 2020 XT2041-4?
BTW, since I'm now stock A11, I used Nova Launcher v6.x - new.version 7.x is incompatible with many of my widgets - today.to make the UI look identical to my rooted and rommed Nexus 7 2013 deb tablets, and it's pretty livable. Plus, Android Auto now works perfectly and never did when the phone was rooted and rommed. Food for thought.
[Edit] I flashed Vache's TWRP. I'd be pretty happy if I could make a Nandroid backup of my current stock setup. Have you done that?
Thanks again

jhford said:
I have done that both zipped and unzipped several times and it has always failed. Maybe I downloaded the wrong firmware. I got it from lolinet. Do you have a link for the correct A10 firmware for Moto G Power 2020 XT2041-4?
BTW, since I'm now stock A11, I used Nova Launcher v6.x - new.version 7.x is incompatible with many of my widgets - today.to make the UI look identical to my rooted and rommed Nexus 7 2013 deb tablets, and it's pretty livable. Plus, Android Auto now works perfectly and never did when the phone was rooted and rommed. Food for thought.
[Edit] I flashed Vache's TWRP. I'd be pretty happy if I could make a Nandroid backup of my current stock setup. Have you done that?
Thanks again
Click to expand...
Click to collapse
What's Moto Flash Tool's output? And I can't really decide the correct firmware for you phone, u need to see what software channel your phone is and select it here: https://mirrors.lolinet.com/firmware/motorola/sofia/official/
for nandroid backup well I'm not really sure, haven't done one before. a quick google search should do something for you.

AbsoluteZeroEdge said:
What's Moto Flash Tool's output? And I can't really decide the correct firmware for you phone, u need to see what software channel your phone is and select it here: https://mirrors.lolinet.com/firmware/motorola/sofia/official/
for nandroid backup well I'm not really sure, haven't done one before. a quick google search should do something for you.
Click to expand...
Click to collapse
Here's how I used Moto Flash Tool (MFT). Pasted A10 firmware in firmware folder. Connected phone in bootloader mode. Double clicked the MFT exe. A blank DOS window popped up and disappeared. That's it.

jhford said:
Here's how I used Moto Flash Tool (MFT). Pasted A10 firmware in firmware folder. Connected phone in bootloader mode. Double clicked the MFT exe. A blank DOS window popped up and disappeared. That's it.
Click to expand...
Click to collapse
make sure it's in a path with no spaces, i recommend putting it in a folder with of course no spaces again on any drive's root

AbsoluteZeroEdge said:
make sure it's in a path with no spaces, i recommend putting it in a folder with of course no spaces again on any drive's root
Click to expand...
Click to collapse
I followed you suggestion and only moved the folder to the root of C:\ that hosts the exe and the firmware, etc. folders. I double clicked the exe and for the first time, a usable batch file DOS window opened. So, it appears that I have a working setup. However, I'm going to think about rooting/romming this phone again, because I don't want to lose Android Auto (AA) again. But AA only works with a USB wired connection in my car, and I ordered an AAWireless device which should obviate the wired connection and allow my rooted/rommed phone to connect. I'll test it, and, if so, I'll flash your Rom Immediately.
Thanks for putting up with me.

I flashed this rom to my retail Moto G Power (2020) that was purchased from Google Fi. I make it to the Google logo screen on boot and it just sits there with the progress bar perpetually scrolling. Any advice?

NobleX13 said:
I flashed this rom to my retail Moto G Power (2020) that was purchased from Google Fi. I make it to the Google logo screen on boot and it just sits there with the progress bar perpetually scrolling. Any advice?
Click to expand...
Click to collapse
First boot usually takes a while, if it hasn't booted within 10 minutes it's stuck. Make sure you did a Format and not only a Wipe as well

Thanks. Upon further inspection when I executed a fastboot -w it wiped the data partition but did not format it. I'll try this again as time permits.
AbsoluteZeroEdge said:
First boot usually takes a while, if it hasn't booted within 10 minutes it's stuck. Make sure you did a Format and not only a Wipe as well
Click to expand...
Click to collapse

NobleX13 said:
Thanks. Upon further inspection when I executed a fastboot -w it wiped the data partition but did not format it. I'll try this again as time permits.
Click to expand...
Click to collapse
Yeah, fastboot -w usually has problems. Good luck!

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

Database Develop

welcome