[ROM][UNOFFICIAL][RAMDISK][11] LineageOS 18.1 for Galaxy S10e/S10/S10+/S10 5G Exynos - Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve

[ROM][UNOFFICIAL][RAMDISK][11] LineageOS 18.1 for Galaxy S10e/S10/S10+/S10 5G Exynos - Samsung Galaxy S10/S10+/S10 5G/E Cross Device Deve

Requirements:
Any Q or R based firmware installed on your device.
Pre-Install Instructions
Warning: The following instructions will unlock the bootloader and wipe all userdata on the device.
Connect the device to a Wi-Fi network.
Enable Developer Options by pressing the “Build Number” option in the “Settings” app within the “About” menu
From within the Developer options menu, enable OEM unlock.
Power off the device, and boot it into download mode:
With the device powered off, hold Volume Down + Bixby and connect USB cable to PC.
Now, click the button that the onscren instructions coorelate to “Continue” and/or “Unlock Bootloader”.
Your device will reboot, you may now unplug the USB cable from your device.
The device will demand you format userdata, please follow the onscreen instructions to do so.
Run through Android Setup skipping everything you can, then connect the device to a Wi-Fi network.
Re-enable Development settings by clicking the “Build Number” option 10 times, in the “Settings” app within the “About” menu, and verify that “OEM Unlock” is still enabled in the “Developer options” menu.
Installing LineageOS for the first time
Flash lineage recovery
Only the provided lineage recovery will be supported,
using TWRP might result in a possible data loss!!
If using Odin rename the lineage recovery image for your model to recovery.img and add it to a .tar archive using e.g 7zip.
If using Heimdall use: heimdall flash --RECOVERY recovery.img --no-reboot
Boot lineage recovery
IMPORTANT: Do not boot into system again before booting recovery, or system will restore stock recovery!
If using Odin untick auto-reboot before flashing.
After flashing reboot by pressing Volume Down and Power for approximately 7 seconds,
immediately hold Volume Up, Bixby and Power to boot recovery
IMPORTANT: As of OneUI 3 your device needs to be connected to a PC via USB cable in order to be able to
boot recovery via Volume Up, Bixby and Power.
Factory reset using Factory reset -> Format data/factory reset
Warning: Unlike TWRP this will also erase internal storage!
Sideload LineageOS by enabling sideload via Apply Update -> Apply from ADB
Then run adb sideload <path to your lineage.zip> on your PC
Optional:
Sideload GApps and magisk by repeating above step
with their zip/apk
Magisk
As this ROM has a working ramdisk sideloading the magisk apk is enough, just as it is
on every other device, no bootimage with magisk included or installing to recovery is needed!

Features
SELinux enforcing
AES-256-XTS FBE encryption
Latest Linux 4.14.x kernel
All cameras are working
Ramdisk is working
Dolby atmos is working
Known issues
VoLTE/VoWiFi
You tell me

Thanks for providing sources and the doing the hardwork to bring up the device, could you also provide what firmware version is required?
Also a simple guide for flashing firmware, would be helpful.

mcgi5sr2 said:
Thanks for providing sources and the doing the hardwork to bring up the device, could you also provide what firmware version is required?
Also a simple guide for flashing firmware, would be helpful.
Click to expand...
Click to collapse
Both Q and R firmwares should work
I'll add that and a guide for updating firmware later

Thank you so much for your work!
Can you provide a little more information about what's working and what bugs people might expect? I believe many are wondering about SELinux status and camera (quality and if all are usable).

DerSteppo said:
Thank you so much for your work!
Can you provide a little more information about what's working and what bugs people might expect? I believe many are wondering about SELinux status and camera (quality and if all are usable).
Click to expand...
Click to collapse
Sure I can add that too, SELinux is enforcing and all cameras are working (on beyond1lte at least)

Is this the new version of Modpunk's Lineage OS 17.1, so with selinux enforced and encrypted?

counti said:
Is this the new version of Modpunk's Lineage OS 17.1, so with selinux enforced and encrypted?
Click to expand...
Click to collapse
This is based on new trees but indeed reuses some stuff from old whatawurst trees.
But yes it's also FBE encrypted and enforcing.

Linux4 said:
Sure I can add that too, SELinux is enforcing and all cameras are working (on beyond1lte at least)
Click to expand...
Click to collapse
Thank you so much and keep up the great work!

Linux4 said:
This is based on new trees but indeed reuses some stuff from old whatawurst trees.
But yes it's also FBE encrypted and enforcing.
Click to expand...
Click to collapse
Is it possible to upgrade from Modpunk's Lineage OS 17.1? With TWRP from Modpunk?

counti said:
Is it possible to upgrade from Modpunk's Lineage OS 17.1? With TWRP from Modpunk?
Click to expand...
Click to collapse
No, sorry
And TWRP won't be supported at all here, see Post #2

Linux4 said:
No, sorry
And TWRP won't be supported at all here, see Post #2
Click to expand...
Click to collapse
But Lineage Recovery has no backup function right? that's a pity, How do you make backups?

counti said:
But Lineage Recovery has no backup function right? that's a pity, How do you make backups?
Click to expand...
Click to collapse
Do it with some app like https://f-droid.org/en/packages/dk.jens.backup/ ?
Or disable FBE encryption if you are fine with that and use TWRP ...
As long as FBE is enabled you'll eventually corrupt your /data partition by using TWRP.

is it possible to use samsung camera on aosp roms? i have s10e unfortunately can't focus on zgcam and it has color shifts in some cases. i want to flash aosp but cant find a proper camera app

hi_s10e said:
is it possible to use samsung camera on aosp roms? i have s10e unfortunately can't focus on zgcam and it has color shifts in some cases. i want to flash aosp but cant find a proper camera app
Click to expand...
Click to collapse
Not possible to use Samsung camera on any AOSP ROMS unfortunately

@Linux4 Thanks for you nice work, really appreciate it.
I was waiting for an update on Modpunks 17.1 version. Now it seams it is dead and no official LineageOS builds exist to regularly update that version. It's a bit annoying to format and set up the OS all over again every half a year or so. So do you intend to push your work to become an official version?

wora92 said:
@Linux4 Thanks for you nice work, really appreciate it.
I was waiting for an update on Modpunks 17.1 version. Now it seams it is dead and no official LineageOS builds exist to regularly update that version. It's a bit annoying to format and set up the OS all over again every half a year or so. So do you intend to push your work to become an official version?
Click to expand...
Click to collapse
I'm thinking about doing it in the future, but can't promise anything

cgirerd said:
Not possible to use Samsung camera on any AOSP ROMS unfortunately
Click to expand...
Click to collapse
thank you

is there anyway to make volte work ?

Related

[OFFICIAL][7.1] LineageOS 14.1 - Xiaomi Mi3 [cancro]

{
"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 7.1 (Nougat), which is designed to increase performance and reliability over stock Android for your device.
Code:
All information and files — both in source and compiled form — are provided on an as is basis.
No guarantees or warranties are given or implied. The user assumes all risks of any damages
that may occur, including but not limited to loss of data, damages to hardware, or loss of
business profits. Please use at your own risk. Note that unless explicitly allowed by the warranty
covering your device, it should be assumed that any warranty accompanying your device will
be voided if you tamper with either the system software or the hardware.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit Gerrit Code Review.
Wiki
Official LineageOS Wiki: http://wiki.lineageos.org/cancro_info.html
Installation
First time LineageOS 14.1 installation on your Xiaomi Mi3:
Read the official Wiki page
Flash a custom recovery via Fastboot
Push GApps (arm) and the CM 14.1 zip to your device
Boot into Recovery
Perform factory reset
Flash the LineageOS 14.1 zip from SD card
Flash GApps from SD card
Reboot
Upgrading from CyanogenMod 14.1 :
Download the experimental migration build to your SD card
Download the latest lineageOS nightly build to your SD card
Boot into Recovery
Flash the experimental migration build
Reboot and wait until it's ready
Reboot into Recovery again
Flash the nightly build
Reboot
Supported devices
Mi3w
Mi4 (WCDMA)
These devices are supported, but the maintainer WILL NOT fix bugs that are reproduceable just in those devices
Mi4 LTE
Downloads
Download nightly : https://download.lineageos.org/cancro
-----------------------------------------------------------------------------
Google Apps (arm): http://opengapps.org/?api=7.1&variant=nano
Su addon (arm): https://mirrorbits.lineageos.org/su/addonsu-arm-signed.zip
Su remover (arm): https://mirrorbits.lineageos.org/su/addonsu-remove-arm-signed.zip
Reporting bugs
Model (Mi3 / Mi4 / Mi4 LTE)
DO NOT report bugs if you're running a custom kernel
DO NOT report bugs if you've modifies system files
DO NOT report bugs if you've installed xposed and/or other mods
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 or bugs reported in the lastest 5 pages of this thread. Any bug not reported in the bug report format below may be ignored.
Code:
Phone Informations
* Phone model (Mi3 / Mi4 / Mi4 LTE)
* LineageOS version
* Gapps version
What you did:
* Wipe data: y/n
* Upgrade from previous official LineageOS build: y/n
* Restore with titanium backup: y/n
You're using (if yes write which one) :
* Task killer
* Phone cleaner / Battery enhancer apps
* Non-stock kernel
* Modified kernel settings
* Other mods
Bug info:
* Last version it worked on
* Repro steps
F.A.Q.
I get error 7 while flashing this rom, what does it mean?
Read what the recovery says: "You're running on an unsupported (Kitkat) baseband". In order to flash the lastest CM builds you must have Miui MM baseband and partition layout installed. Visit http://bit.ly/cancroCMBaseband to learn how to update these
ROOT! ROOT! Give me root or i'll die!!! Where root is???
Root has been removed from LineageOS builds, to allow people who are not interested in root access to enjoy apps such as PokemonGo or banking apps. A zip to re-enable root will be provided next days. Other packages such as SuperSu, magisk or others are not supported and might cause problems
Why no nightly today?
Build failed. Check again tomorrow
When do I have to wipe data?
You must wipe data only when you're switching from another rom or migrating to Snapshot branch from Nightly and vice versa. You don't need to wipe data when you update in the same release channe (this applies to 13.0 -> 14.1 upgrades too)
Will you add <insert awesome feature here>?
I won't. If you write it, submit a commit to gerrit, where it will be reviewed.
The LineageOS team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!
XDA:DevDB Information
[OFFICIAL][7.1] LineageOS 14.1 - Xiaomi Mi3 [cancro], ROM for the Xiaomi Mi 3
Contributors
linuxxxx
Source Code: https://github.com/lineageos
ROM OS Version: 2.3.x Gingerbread
Version Information
Status: Testing
Created 2017-01-31
Last Updated 2017-01-31

nice

Oh...wow...Finally...!!

Finally , it's here ! [emoji14]

Great sir. Has anyone tried it? Is it stable to use as a daily driver?

ROM OS Version: 2.3.x Gingerbread

SwastikAcharya said:
ROM OS Version: 2.3.x Gingerbread
Click to expand...
Click to collapse
you know its nougat right

Sooo nice.
I'm testing on my Mi3 with a data-only SIM card. Having done experimental->23 nightly->30 nightly
Till now I haven't found bugs, just some lags.
No themes, but I can live without
I know I can't say anything about calls, BT issues and so on, but LineageOS just made my Mi3 "new" again

Found bug on audio fx, its so disturbing me -_- i want a pure lineage os, not custom equalizer

SwastikAcharya said:
ROM OS Version: 2.3.x Gingerbread
Click to expand...
Click to collapse
lol... Don't know how many days it will be there in the thread! @linuxxxx don't really look in the thread much.

Any chance this ROM suppory LTE mode switch preference in the setting?

help requested.
struck at
detected filesystem ext4 for /dev/block/bootdevice/by-name/system

sunil_defy said:
help requested.
struck at
detected filesystem ext4 for /dev/block/bootdevice/by-name/system
Click to expand...
Click to collapse
It took ~10 mins for me and then worked. Initially I also though it is stuck but finally loaded.

Yeah same here

sunil_defy said:
help requested.
struck at
detected filesystem ext4 for /dev/block/bootdevice/by-name/system
Click to expand...
Click to collapse
Yes, this happens to me as well. It's kinda misleading BUT behind the scene it is running alright. It took a while to finish (there is not even a success message being shown). Just continue to flash GApps or reboot to system when its done. Should be fine. It works for me.

sunil_defy said:
help requested.
struck at
detected filesystem ext4 for /dev/block/bootdevice/by-name/system
Click to expand...
Click to collapse
The Flashing time took a lot (about 20-25 min) because all lineage os builds are signed with a key. That's why
So please wait patiently and enjoy lineage os.

Excellent build. Good battery life
1. Wallpaper scroll doesn't work
2. Bluetooth telephony didn't work
3. Browser closes sudenly

is there a fix for battery counter dropping drastically after a reboot. Otherwise extremely happy with the ROM .

xdarkstar said:
It's there a fix for battery counter dropping drastically after a reboot. Otherwise extremely happy with the ROM .
Click to expand...
Click to collapse
As of now i don't think so ..I asked shivam sir and he was also unable to find the reason:crying:This problem is the reason I am not using any LOS Roms and using AOSP roms instead

reality1234 said:
As of now i don't think so ..I asked shivam sir and he was also unable to find the reason:crying:This problem is the reason I am not using any LOS Roms and using AOSP roms instead
Click to expand...
Click to collapse
Same reason here + ZX kernel

LineageOS 16.0 - Xiaomi Mi A2 Lite [ENFORCING]

# Reserved

# Reserved 2

Thanks!!!!!!

Thanks a lot!, I am already on january stock rom with twrp and rooted, with magisk modules.
Should i restart with fresh rom flash, or i can just wipe and flash?.

Does this rom have los updater working?

just wipe /data and /system and install
Txatxiquesi said:
Thanks a lot!, I am already on january stock rom with twrp and rooted, with magisk modules.
Should i restart with fresh rom flash, or i can just wipe and flash?.
Click to expand...
Click to collapse
---------- Post added at 02:53 PM ---------- Previous post was at 02:52 PM ----------
los updater is for official rom , this rom is unofficial so no... but is not a problem for update after flash new zip in twrp and reboot
Moemen Gaber said:
Does this rom have los updater working?
Click to expand...
Click to collapse

Moemen Gaber said:
Does this rom have los updater working?
Click to expand...
Click to collapse
Being it's still in a testing phase I doubt it.but not 100% sure

Will this ever support custom kernel?
I need color calibration to remove yellowish tint of my phone. And to some who will say im on reading mode or etc. NO, my default lcd is EBBG, its warm tone by default.

camera2 API works? are this tom can use oreo vendor?

leitseleac said:
Will this ever support custom kernel?
I need color calibration to remove yellowish tint of my phone. And to some who will say im on reading mode or etc. NO, my default lcd is EBBG, its warm tone by default.
Click to expand...
Click to collapse
1. Open the kernel ZIP file
2. Copy module/system/vendor/lib/modules/wlan.ko to module/system/lib/modules
3. Flash the kernel.
But you don't need a custom kernel to change the hue, there's an option for that in LOS settings.

davidrocher said:
1. Open the kernel ZIP file
2. Copy module/system/vendor/lib/modules/wlan.ko to module/system/lib/modules
3. Flash the kernel.
But you don't need a custom kernel to change the hue, there's an option for that in LOS settings.
Click to expand...
Click to collapse
Does it have RGB values adjuster

CreateYourDream said:
camera2 API works? are this tom can use oreo vendor?
Click to expand...
Click to collapse
Gcam does not work. LOS can only be installed on the vendor pie.

during flashing it appears: updater process ended with error 1. I think it's something at boot level if I'm not mistaken. I tried flashing the boot stock and then the rom, but it still gives me error 1. How do I solve it?

Could you explain how to correctly install the rom together with the gapps? he made me hard brick which I had to solve with test points after doing a clean installation together with the gapps "open_gapps-arm64-9.0-pico-20190406"

I'm having trouble decrypting my phone on TWRP, did anyone manage to do this?

Hakkinan said:
I'm having trouble decrypting my phone on TWRP, did anyone manage to do this?
Click to expand...
Click to collapse
You have to wipe system, data and cache

Pupo_28 said:
You have to wipe system, data and cache
Click to expand...
Click to collapse
Already did that, i'm having trouble decrypting after i've installed LOS (it was said that the rom supports HW encryption and the new TWRP was supposed to fix this problem).

Hakkinan said:
Already did that, i'm having trouble decrypting after i've installed LOS (it was said that the rom supports HW encryption and the new TWRP was supposed to fix this problem).
Click to expand...
Click to collapse
Owh, sorry then I thought you referred to the password asked to let it mount the storage

help error 1 in twrp, what do i do ?

[ROM][OFFICIAL][gts4lvwifi][10] LineageOS 17.1

-- bit more friendly stock -> lineage instructions --
1. Unlock the bootloader
- Connect to WiFi network
- Enable OEM Unlock in developer options
- Turn off the tablet
- Boot to download mode manually by plugging in USB and holding all the buttons for few seconds
- Follow instructions on the screen
2. Connect to WiFi network and make sure OEM Unlock in developer options is still checked
3. Flash custom VBMeta image ( https://dl.twrp.me/gts4lvwifi/vbmeta.tar.html ) in Odin ( use AP slot )
4. After flashing VBMeta, boot to stock. It'll likely ask you to wipe data, if so do that
5. Connect to WiFi network and make sure OEM Unlock in developer options is still checked
6. Now you can flash TWRP ( https://dl.twrp.me/gts4lvwifi ) in Odin ( use AP slot once again ), for convenience you can hold volume up while flashing it so that you boot to recovery right after it's flashed
7. Install Lineage × whatever else you need ( gapps, addon-su, ... )
8. Format data
9. Reboot ( make sure to not install TWRP app when TWRP asks you to )
---
Also Odin download for those who can't find it on their own https://build.nethunter.com/samsung-tools/Odin_3.13.1.zip
( sha1sum 1057496afa34bfdf7e77caf0b99207dca77fcb2d )

Builds 20200824+ depend on Android 10 firmware, and thus from now on the recovery will abort the installation if you're still on Android 9 one.
You can update the firmware by flashing following Odin package: https://github.com/luk1337/gts4lv-fw/releases/tag/T720XXS2CUA3.
After the firmware update you should be able to flash newer builds.

Well.. that was faster than expected. Thank you very much for your dedication.
Which gapps are you currently using or recommending? Opengapps doesn't seem to have gapps for 10 yet.
Also any special instructions for flashing when coming from your previous los16 rom?

LuK1337 said:
LineageOS is a free, community built, aftermarket firmware distribution of Android 10, 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.
Instructions :
Download the latest build and gapps
Reboot to recovery
Flash the latest build and gapps
Reboot
Downloads :
Builds :
https://www.androidfilehost.com/?w=files&flid=299579
http://downloads.codefi.re/jdcteam/luk/lineage-17_0/gts4lvwifi
https://sourceforge.net/projects/luk-lineageos/files/gts4lvwifi/lineage-17.0
Reporting Bugs
DO NOT Report bugs if you're running a custom kernel or you installed Xposed
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. Any bug not reported in the bug report format below may be ignored.
Code:
What is your--
LineageOS version:
LineageOS Download url:
Gapps version:
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
XDA:DevDB Information
[ROM][UNOFFICIAL][gts4lvwifi][10] LineageOS 17.0, ROM for the Samsung Galaxy Tab S5e
Contributors
LuK1337
Source Code: https://github.com/LineageOS
ROM OS Version: Windows 8 Mobile
Version Information
Status: Testing
Created 2019-09-24
Last Updated 2019-09-24
Click to expand...
Click to collapse
Wow!!!! Thanks op!

andre0005 said:
Well.. that was faster than expected. Thank you very much for your dedication.
Which gapps are you currently using or recommending? Opengapps doesn't seem to have gapps for 10 yet.
Also any special instructions for flashing when coming from your previous los16 rom?
Click to expand...
Click to collapse
Apparently https://sourceforge.net/projects/opengapps/files/arm64/beta/ works.

I had the opportunity to test the image yesterday as kind of a preview. After killing the setup wizzard, it worked really great. The switch from LOS 16 to 17 was easy.
Rooting had to be done with magisk (current stable was fine) as Luk told me that superSU probably won't work.
I eventually reverted to LOS 16 mainly because of personal discomfort. No Trebuchet, some settings dialogues not (yet) ported and Titanium Backup did not work (there were no buttons displayed - could not even press the problems? button as it was not there ). I personally decided to wait a bit until I will return to LOS 17 on that device.

That was fast. You got me

inka$$o said:
I had the opportunity to test the image yesterday as kind of a preview. After killing the setup wizzard, it worked really great. The switch from LOS 16 to 17 was easy.
Rooting had to be done with magisk (current stable was fine) as Luk told me that superSU probably won't work.
I eventually reverted to LOS 16 mainly because of personal discomfort. No Trebuchet, some settings dialogues not (yet) ported and Titanium Backup did not work (there were no buttons displayed - could not even press the problems? button as it was not there ). I personally decided to wait a bit until I will return to LOS 17 on that device.
Click to expand...
Click to collapse
Did you perform a full wipe before flashing?
Also how did you 'kill' the setup wizard?

There is an issue with twrp decrypting storage on Los 17. Is this more than likely a twrp issue?
I also can't install apps, probably because no access to SD card.

suzook said:
There is an issue with twrp decrypting storage on Los 17. Is this more than likely a twrp issue?
Click to expand...
Click to collapse
TWRP issue.

LuK1337 said:
TWRP issue.
Click to expand...
Click to collapse
Apps won't install from play store also
Unfortunately I can't download anything, since SD card is encrypted. Guess I will go back to Los 16. Thanks anyway op.

suzook said:
Apps won't install from play store also
Unfortunately I can't download anything, since SD card is encrypted. Guess I will go back to Los 16. Thanks anyway op.
Click to expand...
Click to collapse
>Apps won't install from play store also
Format data; reboot and they should install fine now.

LuK1337 said:
>Apps won't install from play store also
Format data; reboot and they should install fine now.
Click to expand...
Click to collapse
Will give it a shot.

andre0005 said:
Did you perform a full wipe before flashing?
Also how did you 'kill' the setup wizard?
Click to expand...
Click to collapse
I started with my device running LOS16 already. If you're coming from stock, you should stick to the instructions for the LOS16 installation in the other thread - just use instead of LOS16 image the LOS17 image.
If you have already LOS16 on the device:
-> Boot to Recovery
-> install LOS 17 image
-> if desired stable Magisk for rooting
-> if desired these openGAPPS (was told to use them - they worked fine)
-> FORMAT data (wipe doesn't do the trick, as it doesn't do it when installing LOS 16)
After facing the problem with the setup wizzard I was told to simply delete it.
Boot to Recovery, mount system partition and open the terminal.
The command is:
rm -rf /system/priv-app/SetupWizard
After that, the wizard is gone and you can boot to system. You'll have to manually go through the settings to set up everything though.

Are there any launchers other than the included that work with the new gesture navigation?

andre0005 said:
Are there any launchers other than the included that work with the new gesture navigation?
Click to expand...
Click to collapse
No.

OK, got it set up properly with the format data. Just a couple things. Black theme doesn't work, and immersive mode force crashes settings app when trying to access it. Not complaining, just letting you know.

suzook said:
OK, got it set up properly with the format data. Just a couple things. Black theme doesn't work, and immersive mode force crashes settings app when trying to access it. Not complaining, just letting you know.
Click to expand...
Click to collapse
Use a standalone dark theme toggle, not 'Style' one.

@LuK1337 Thanks a lot for the build. Time to buy the Tablet.
One Question:
 @LuK1337 or anyone, are the corners rounded like that of the stock ROM or are the corners sharp?

[ROM][UNOFFICIAL][alpha] LineageOS 17.1 for Redmi K30 5G (picasso) (20200419)

{
"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"
}
WARNING
DO NOT try to install this on the non-5G version of Redmi K30. This ROM is ONLY intended for Redmi K30 5G and they are NOT the same device. Their difference is more than just 5G or non-5G.
Introduction
This is an UNOFFICIAL port of LineageOS 17.1 (based on Android 10) for the device Redmi K30 5G, codenamed Picasso.
LineageOS is a free, community built, aftermarket firmware distribution of Android 10, 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 Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
What's working
- All basic mobile phone features (Wi-Fi, Bluetooth, Cellular Data, Phone Calls, SMS, etc., incl. 5G and VoLTE)
Known Issues
- (For Chinese Users) NO Alipay / WeChat Pay fingerprint support, and no plan to add support for them. Ask Alibaba / Tencent to support the standard Android biometrics API, not me to make my ROM support their API.
- 3.5mm jack does not work for some reason. (Will be fixed in the next release) Fixed since 20200311
- Wi-Fi display is not implemented since I have no device to test it on
- VoWiFi is not tested since I have no carrier support
- No 5G toggle. You cannot disable / enable 5G support. It's on by default and it goes to 5G if it can. (Note: there seems to be a dedicated network type option now in settings - mobile network for 5G NR, but I checked AOSP source code and that's only for 5G SA, and 5G NSA still falls under LTE, not the NR type)
- CTS does not pass because xiaomi's build fingerprint is not CTS-verified. You are on your own finding a solution to this. (Hint: Magisk modules)
- (For Developers) I cannot build a working DTB image from the sources provided by Xiaomi. I do not know the exact reason and for now I'm using prebuilt DTB and DTBO images, which you can extract from the official ROM and its boot.img.
- I'm not sure if there is any other issue, but at least nothing deal-breaking for me.
Instructions (Install / Upgrade) (IMPORTANT)
Side Note: I am fully aware that there is a TWRP port for this device, however it seems to be based on a modified version of TWRP whose source code I cannot find. The official TWRP repository (that I can see) does not even support Android 10 dynamic partitions yet, let alone porting it to this device. Of course it is possible that the author of that TWRP port has access to some internal testing version of TWRP, but since I cannot access the source code either way, I cannot do tests on the TWRP port. The LineageOS recovery I ported is adjusted specifically for this ROM and I have only tested the ROM on my LineageOS recovery port. If you choose to use the TWRP port, you are on your own, and do not ask me for problems you may encounter by using that port.
1. Install LineageOS 17.1 Recovery following my guide in the other thread (https://forum.xda-developers.com/re...covery-lineageos-recovery-17-1-redmi-t4059879), DO NOT use TWRP because it will NOT work for devices with dynamic partitions.
2. Reboot to LineageOS Recovery, wipe all data (skip if you are upgrading) (BACKUP ALL YOUR DATA TO A COMPUTER BEFORE FLASHING)
3. Flash required OFFICIAL MIUI version via adb sideload before flashing LineageOS 17.1. (consult the Downloads section for the corresponding MIUI version required for each LineageOS release)
- Flash OFFICIAL, not Xiaomi.eu or any other modified version.
- You can skip this step if you already have the required MIUI firmware + vendor version flashed before (e.g. if you upgrade from an older release of my LineageOS port and I did not change the required MIUI version)
- You can choose to try installing LOS on non-tested MIUI versions, though they are not tested so expect some hiccups or even disasters.
- DO NOT just flash the firmware of the required MIUI version. Always flash the full MIUI ROM (no additional wiping needed if you do not actually boot into MIUI). This ROM depends on the vendor partition provided by MIUI to work. You will need to flash at least the firmware PLUS the vendor and odm partition images of its required MIUI version for the ROM to actually work.
4. Flash LineageOS 17.1 zip via adb sideload
5. Reboot to Recovery (If you want to install Magisk or OpenGAPPS or both, else just reboot to system
6. Select "Mount /system" in the rebooted Recovery, ignore any error that may pop up on the screen
7. If you would like to, install Magisk (you MUST use a version later than or equal to 20.4)
8. If you would like to, install patched OpenGAPPS zip (available in Downloads section. You MUST use the patched OpenGAPPS for now.)
9. Reboot and enjoy. Magisk may cause your phone to double-boot (i.e. auto-reboot after the logo disappears) on first boot. If your phone boots up the second time then it will be fine.
Downloads
20200419: https://mega.nz/file/LAJjCYDT#L1Rd-WFJQ7SaU3vfAxU2y7AJsfH9qZ3fSAKMTQhgPWM
(MIUI firmware / vendor version tested on: miui_PICASSO_V11.0.11.0.QGICNXM_65ec88895f_10.0)
Changelog:
- Updated LOS source (April patch)
- You can now install the OFFICIAL version of Magisk >= 20.4 without modification
20200311: https://mega.nz/#!iB53SIKQ!ewdfMNFHmHjOemDDuYcgQO2t1KgrB9hx6YXYAdLKxU4
(MIUI firmware / vendor version tested on: miui_PICASSO_V11.0.11.0.QGICNXM_65ec88895f_10.0)
Changelog:
- Fixed 3.5mm jack support
- Lowered minimum allowable brightness to match the auto brightness curve
- Synchronized LineageOS 17.1 March Security Patch update
20200307: https://mega.nz/#!KQ5jkbAQ!dJspI92ls3BiVGk8FIGbVf4b4QBkwaaLUUr_NKX020A
(MIUI firmware / vendor version tested on: miui_PICASSO_V11.0.11.0.QGICNXM_65ec88895f_10.0)
Patched OpenGAPPS 20200306 (2): https://mega.nz/#!2EwVzAJR!NmBbO1_ao5ziyup6UVx64lZK06_VGNXSsFDA9T4sOO0
(Changelog: added `sync` after flashing to ensure everything is actually written to /system; also added a flag to `tar` to ignore creation times because that seems to break sometimes in our recovery)
Patched OpenGAPPS 20200306: https://mega.nz/#!2NgHXL6T!Z7J6AbJ7i4y9AuflIF0v_7KLbAO8XVV4ACsk13oz380
(What's patched: the `busybox` included in OpenGAPPS cannot mount the system partition as Read-Write in LineageOS Recovery for some reason. I edited the install script to use the `mount` command provided by the recovery instead of busybox. Also I removed the unmounting at the end of installation since it seem to stall the whole recovery, which means you will have to flash OpenGAPPS at the very last of your flashing process.)
XDA:DevDB Information
LineageOS 17.1 for Redmi K30 5G, ROM for the Redmi K30 5G
Contributors
PeterCxy
Source Code: https://github.com/PeterCxy/android_device_xiaomi_picasso
ROM OS Version: Android 10
Version Information
Status: Alpha
Created 2020-03-08
Last Updated 2020-03-08

I've been trying to compile the os from your device tree these days...now it's a waste of time
Anyway, I've followed you on GitHub. Thank you for doing so much!

zhufucdev said:
I've been trying to compile the os from your device tree these days...now it's a waste of time
Anyway, I've followed you on GitHub. Thank you for doing so much!
Click to expand...
Click to collapse
Sorry for that, you need some additional patches in LineageOS to actually build it successfully (you can search for patches by me on LOS gerrit: https://review.lineageos.org/q/owner:peter%40cxy.moe). Also I haven't uploaded the prebuilt DTB / DTBO image in my device tree. You will need to extract those on your own (or maybe you can help me figure out why the official open-source version does not work)

PeterCxy said:
Sorry for that, you need some additional patches in LineageOS to actually build it successfully (you can search for patches by me on LOS gerrit: https://review.lineageos.org/q/owner:peter%40cxy.moe). Also I haven't uploaded the prebuilt DTB / DTBO image in my device tree. You will need to extract those on your own (or maybe you can help me figure out why the official open-source version does not work)
Click to expand...
Click to collapse
I'm sorry but I am basically a noob on ROM porting. I'm only familiar with some basic linux commands and Android developing.

Hi, there! There is something I can't figure out:
Is there any checksums for ROM?
BTW, is there any force encryption feature in LineageOS?
However, thanks for your ROM.

RiverYKB said:
Hi, there! There is something I can't figure out:
Is there any checksums for ROM?
BTW, is there any force encryption feature in LineageOS?
However, thanks for your ROM.
Click to expand...
Click to collapse
No checksum, but since Mega.nz uses end-to-end-encryption it should do checksum on its own. Also you can verify the package against testkeys.
Force encryption is of course enabled by default.

PeterCxy said:
No checksum, but since Mega.nz uses end-to-end-encryption it should do checksum on its own. Also you can verify the package against testkeys.
Force encryption is of course enabled by default.
Click to expand...
Click to collapse
I'm just worrying about my downloaded ROM. Because you know some of E2EE file send platforms (such as Mega.nz) is being blocked by Chinese Gov. ?So I have to download with VPN.
But it's just fine.

Do not try it on the non 5G K30, oh ok means now I definitely have to try it.

Ya_SG said:
Do not try it on the non 5G K30, oh ok means now I definitely have to try it.
Click to expand...
Click to collapse
You may have better luck trying a K20 ROM on non-5G K30 than trying this one. The non-5G K30 shares the same kernel source tree with K20 instead of K30 5G. (of course, existing K20 kernels and thus ROMs do not even support dynamic partitions, so you would probably not be able to boot either way)

Hi!
I know I'm a really noob, but I ran into a problem.
So before I flash LineageOS, my /sdcard and /data is already encrypted.
And I backed my files to /sdcard, then I wiped /data and flashed LineageOS.
I can boot to LineageOS properly now, but I can't access my backup files in /sdcard, it's all garbled.
Is there any way to help?
Thank you very much.

RiverYKB said:
Hi!
I know I'm a really noob, but I ran into a problem.
So before I flash LineageOS, my /sdcard and /data is already encrypted.
And I backed my files to /sdcard, then I wiped /data and flashed LineageOS.
I can boot to LineageOS properly now, but I can't access my backup files in /sdcard, it's all garbled.
Is there any way to help?
Thank you very much.
Click to expand...
Click to collapse
looks like you have wiped the encryption keys for some reason. Unfortunately, there's nothing I can do to help in this case.

RiverYKB said:
Hi!
I know I'm a really noob, but I ran into a problem.
So before I flash LineageOS, my /sdcard and /data is already encrypted.
And I backed my files to /sdcard, then I wiped /data and flashed LineageOS.
I can boot to LineageOS properly now, but I can't access my backup files in /sdcard, it's all garbled.
Is there any way to help?
Thank you very much.
Click to expand...
Click to collapse
Hi RiverYKB
The point I guess is to decrypt the data partition, which can be easily done using a TWRP recovery. So I suggest flashing TWRP via fastboot with your computer. You should be able to decrypt your data with the password set before lineage os was flashed.

Updated 20200311

PeterCxy said:
Updated 20200311
Click to expand...
Click to collapse
it looks like bootloop after flash 0311 version, logcat file below
htdeletemetps://drive.google.com/file/d/1INO9nNnEyR_JxmJRvZzhNrOVfWrDIuwv/view?usp=sharing

Cedric1223 said:
it looks like bootloop after flash 0311 version, logcat file below
htdeletemetps://drive.google.com/file/d/1INO9nNnEyR_JxmJRvZzhNrOVfWrDIuwv/view?usp=sharing
Click to expand...
Click to collapse
Your issue seems gapps-related. Make sure you flash my patched version of gapps, not the official version. Did you upgrade to 0311 from 0307 or just flash 0311? If you upgraded, make sure you re-flash gapps after the upgrade.

I will try when next update comes, thank you for your great rom port
PeterCxy said:
Your issue seems gapps-related. Make sure you flash my patched version of gapps, not the official version. Did you upgrade to 0311 from 0307 or just flash 0311? If you upgraded, make sure you re-flash gapps after the upgrade.
Click to expand...
Click to collapse

This rom working on poco x2 4g?

fromjeet said:
This rom working on poco x2 4g?
Click to expand...
Click to collapse
of course not

It looks like if I set a password for Hotspot, other devices can not connect this hotspot
if no password for hotspot, it works perfectly

Thanks for your ROM since I have been using it for a couple of days with no critical problem found. However,
1. Since 5G NSA falls under LTE, is it possible to make it displaying "NR" or something else to indicate that the phone is on 5G network? If impossible, is there any other ways to know whether the phone is on 5G or not?
2. Is there a working root solution for it?
Thank you for your time and effort

[ROM][OFFICIAL][gts4lv|gts4lvwifi][12] LineageOS 19

LuK1337 said:
LineageOS is a free, community built, aftermarket firmware distribution of Android 12, 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 organization. And if you would like to contribute to LineageOS, please visit our Gerrit Code Review. You can also view the changelog for a full list of changes & features.
Instructions :
https://wiki.lineageos.org/devices/gts4lvwifi/install
Downloads :
https://www.androidfilehost.com/?w=files&flid=332252
http://downloads.codefi.re/jdcteam/luk/lineage-19_0/gts4lvwifi
https://sourceforge.net/projects/luk-lineageos/files/gts4lvwifi/lineage-19.0
Reporting Bugs
DO NOT Report bugs if you're running a custom kernel, or you installed Xposed
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 /sys/fs/pstore/console-ramoops and /sys/fs/pstore/dmesg-ramoops-0. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
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. Any bug not reported in the bug report format below may be ignored.
Code:
What is your--
LineageOS version:
LineageOS Download url:
Gapps version:
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
Click to expand...
Click to collapse
Omg, thank you!

Amazing! Thank you!

Yes!

Installed and runs just fine Just interestingly, after flashing nikgapps core there were no Gapps after booting... But flame gapps work ok
Thanks the Dev for bringing A12 for us! 🤝🏻

Lord Sithek said:
Installed and runs just fine Just interestingly, after flashing nikgapps core there were no Gapps after booting... But flame gapps work ok
Thanks the Dev for bringing A12 for us! 🤝🏻
Click to expand...
Click to collapse
Do i need to format data of only with factory reset i can flash

apokit said:
Do i need to format data of only with factory reset i can flash
Click to expand...
Click to collapse
I wiped and formatted everything except MicroSD card, then flahsed latest firmware available in Odin (https://github.com/luk1337/gts4lv-fw/releases/tag/T720XXU2DUL1), then flashed all necessary stuff in TWRP

Brightness slider not showing on notification center even set to show always
LineageOS version: 19.0
LineageOS Download url: https://www.androidfilehost.com/?w=files&flid=332252
Gapps version: MindTheGapps 12 arm64 http://downloads.codefi.re/jdcteam/javelinanddart/gapps
Did you--
wipe: yes, cache system data
restore with titanium backup: no
reboot after having the issue: yes
Are you using--
a task killer: no
a non-stock kernel: no
other modifications: Lineage Recovery

whiteyaksa said:
Brightness slider not showing on notification center even set to show always
LineageOS version: 19.0
LineageOS Download url: https://www.androidfilehost.com/?w=files&flid=332252
Gapps version: MindTheGapps 12 arm64 http://downloads.codefi.re/jdcteam/javelinanddart/gapps
Did you--
wipe: yes, cache system data
restore with titanium backup: no
reboot after having the issue: yes
Are you using--
a task killer: no
a non-stock kernel: no
other modifications: Lineage Recovery
View attachment 5526051View attachment 5526049
Click to expand...
Click to collapse
Don't report missing features, I'm well aware they're missing.

whiteyaksa said:
Brightness slider not showing on notification center even set to show always
Click to expand...
Click to collapse
Brightness slider is available on mine.
Edit:
I dont have wifi available though. I click wifi button and it switches off immediately. Im going to install via odin rather than twrp and if that doesnt work, Ill post a bug report with logcat.
Fixed the broken wifi by flashing https://github.com/luk1337/gts4lv-fw/releases/tag/T720XXU2DUD7 this vb meta data in AP slot of ODIN.
@LuK1337 : los19, EXCELLENT!! WHOOHOO!! Thanks buddy!!!
If you want any testing, let me know...

Can you please release Lineage Recovery 19.0? Thank you

whiteyaksa said:
Can you please release Lineage Recovery 19.0? Thank you
Click to expand...
Click to collapse
Not sure if it makes sense to release recovery images separately, but if you want up-to-date recovery (that also passes signature check for these builds), then simply toggle "Update recovery" in system updater preferences, and it should automatically flash it.

LuK1337 said:
Not sure if it makes sense to release recovery images separately, but if you want up-to-date recovery (that also passes signature check for these builds), then simply toggle "Update recovery" in system updater preferences, and it should automatically flash it.
Click to expand...
Click to collapse
the updater crashes when i save this option

whiteyaksa said:
the updater crashes when i save this option
Click to expand...
Click to collapse
Oh? Can you take a logcat?
EDIT: Actually nvm, it's probably just SELinux anyway. You can set do adb root + adb shell setprop persist.vendor.recovery_update true instead.

LuK1337 said:
Oh? Can you take a logcat?
EDIT: Actually nvm, it's probably just SELinux anyway. You can set do adb root + adb shell setprop persist.vendor.recovery_update true instead.
Click to expand...
Click to collapse
I did this and reflashed the LOS 19.0 image, restart to the recovery and it's still 18.1

Hi, thank you for amazing work. In portrait mode quick settings looks like this. Any suggestions.
Your browser is not able to display this video.

Forgive me the stupid question but can I do a dirty flash from the official lineage 18?

XRed_CubeX said:
Forgive me the stupid question but can I do a dirty flash from the official lineage 18?
Click to expand...
Click to collapse
You should be able to. Flash L-OS and gapps straight afterward. Optionally magisk if you need so

Ok thanks for the tip

XRed_CubeX said:
Ok thanks for the tip
Click to expand...
Click to collapse
Remember to take a backup first and update your firmware

Develop Bugs

welcome