[ROM][8.1.0][OFFICIAL] LineageOS 15.1 for Wileyfox Storm - Wileyfox Storm

[ROM][8.1.0][OFFICIAL] LineageOS 15.1 for Wileyfox Storm
Code:
[COLOR="Purple"]#include <std_disclaimer.h>[/COLOR]
[COLOR="Navy"]/*
* 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.
*/[/COLOR]
Installation:
If you are on stock OS, you need a custom recovery first. You can get the recommended TWRP recovery in the official installation instructions link below.
If you are coming from stock or other ROMs, you need to make a factory reset.
As always, make sure to backup before installing this ROM.
More detailed instructions at:
Install LineageOS on kipper
Official Download link:
LineageOS Downloads
Recommended Google Apps package:
Open GApps (choose the variant you want)
Changelog:
Changes for kipper
Bug reports:
How to submit a bug report
LineageOS JIRA
Donate to support development:
Donate via PayPal to jrior001
Donate via PayPal to LineageOS
XDA:DevDB Information
LineageOS, ROM for the Wileyfox Storm
Contributors
jrior001, jrior001, mikeioannina
Source Code: https://github.com/LineageOS
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.10.x
Version Information
Status: Beta
Created 2018-05-20
Last Updated 2018-09-10

Reserved
Updated recovery required
http://www.theflamingskull.com/downloads/kipper/TWRP-kipper-3.2.3.img
Test Build #1
* permissive selinux for debugging purposes
Test build #2 5/30/18
camera/flashlight and UI lag resolved

the last build works well
lineage-15.1-20180902-UNOFFICIAL-kipper

i cant instal instagram app

nightly 2018-09-10
1. I installed Instagram , but it doesn't play video
2. please fix the widgets
3. when I use dark theme ( dark mod theme)
the icons of "turn on/off" in "privacy guard" don't change the color

Can't install gapps (tried pico (stuck on logo) and stock (error 70 in TWRP)).
OK, let's go w/o gapps. Can't install .apk files.

Monate said:
Can't install gapps (tried pico (stuck on logo) and stock (error 70 in TWRP)).
OK, let's go w/o gapps. Can't install .apk files.
Click to expand...
Click to collapse
From opengapps, pico and nano should fit. I'm not sure what error 70 is but if you grab the entire recovery log from a failed flash I'll be glad to look it over.
With device in recovery, after your failed flash hook up to PC, and run "adb pull /tmp/recovery.log"
Sent from my PH-1 using Tapatalk

jrior001 said:
From opengapps, pico and nano should fit. I'm not sure what error 70 is but if you grab the entire recovery log from a failed flash I'll be glad to look it over.
With device in recovery, after your failed flash hook up to PC, and run "adb pull /tmp/recovery.log"
Click to expand...
Click to collapse
Both gapps were taken from opengappsorg.
Pls, help me with 1 more thing: I want to format /data from ext4 to f2fs but I got an error. Log contains both errors.
Aaaand... I didn't find how to attach a file ;(
UPD: https://drive.google.com/open?id=1ecgkLr7jRasryLgmKvPTaxsqdNcfHGPC

Monate said:
Both gapps were taken from opengappsorg.
Pls, help me with 1 more thing: I want to format /data from ext4 to f2fs but I got an error. Log contains both errors.
Aaaand... I didn't find how to attach a file ;(
UPD: https://drive.google.com/open?id=1ecgkLr7jRasryLgmKvPTaxsqdNcfHGPC
Click to expand...
Click to collapse
The only gapps attempt in that log was opengapps "STOCK" version which has everything. That won't fit, stick with PICO or NANO, I believe both of those will fit on 15.1, anything else you want you can get from Play Store.
Also I updated the link in post #2 to a newer TWRP version. I was able to convert /cache to f2fs just fine with that one.

Whatsapp video player is not working.

iN4sser said:
Whatsapp video player is not working.
Click to expand...
Click to collapse
Whatsapp and Instagram videos are both wonky. I'm aware. The only fix I have found breaks more than it fixes so for now we're stuck like this.
Sent from my PH-1 using Tapatalk

Hey. After the appearance of this error, I decided to try again to install LOS 15.1 (installed on f2fs, so the gapps did not fit). I downloaded Apkpure.apk through a standard browser, found it through a standard file manager, clicked, but nothing happened. Rebooting the device did not help. I tried to find in the settings the item "installation from unknown sources" (somehow it is called so), but it is not there. What to do?) The same problem was before on ext4.
build lineage-15.1-20181106-nightly-kipper-signed
UPD found solution: open file from internal storage

When the official image for kipper moved from LineageOS 14 to LineageOS 15, I destroyed my telephone by not noticing that the new OS wouldn't fit in the partitions and rebooting. I then wiped the phone, restored an older LO 13 (cm-13.1.2-ZNH2KAS3NA-kipper-signed-fastboot-1eb4b5e94b.zip) via fastboot flash and was back in business.
Since TWRP won't recognize SD card and/or USB memory device, I used adb sideload to install LineageOS 15 (lineage-15.1-20181230-nightly-kipper-signed.zip). The TWRP output ends with "script succeeded: result was [1.0000]", the adb process on the (Linux) desktop counts up to 47 % and then terminates with exit code 0 and without an error message.
The installed image boots, shows the usual LineageOS boot screen (the circles moving on a line from right to left) for a few minutes, and then reboots into recovery.
How do I find out what's going wrong here? How do I fix this behavior?
Is there any way to obtain a Lineage OS 14 image to try? The official download media seem only to have the latest six snapshots, which are all LineageOS 15 images.
Greetings
Marc

everything works well
everything works well on my phone
instagram doesn't have problem anymore ( since last month)

Related

[UNOFFICIAL][ROM][4.4] CyanogenMod 11 for Samsung Captivate

CyanogenMod is a free, community built, aftermarket firmware distribution of Android 4.4 (KitKat), which is designed to increase performance and reliability over stock Android for your device.
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.
*/
CyanogenMod 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. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
What are UNOFFICIAL builds? A version of CyanogenMod not compiled by CyanogenMod's build servers and may contain code not yet committed to the repository. If you find bugs/issues you can/must discuss here (do not submit nightlies bug on CyanogenMod issue tracker).
Downloads
ROM:http://d-h.st/myfiles?fld_id=28773#files (just look for the one with the newest date on it
Gapps:http://forum.xda-developers.com/showthread.php?t=2012857
use what ever gapps you want but i personally use these ones since its just the basic stuff and its art compatible
Installation
- First time flashing CM11 to your Galaxy S (or coming from another ROM)?
Root your device and install ClockworkMod Recovery.
Reboot into Recovery using 3-button-combo
Do a Nandroid backup!
WIPE (wipe data/factory reset + wipe cache partition)
Install the ROM from internal sdcard using ClockworkMod Recovery
Optionally install the Google Addon
- Upgrading from CM7/CM9?
Do a Nandroid Backup!
WIPE (wipe data/factory reset + wipe cache partition)
Install the ROM from internal sdcard using ClockworkMod Recovery
Optionally install the Google Addon
- Upgrading from CM10/10.1?
Do a Nandroid Backup!
Install the ROM from internal sdcard using ClockworkMod Recovery
You will finally see a "set_metadata_recursive" status 7 error. That is normal.
Reboot back into recovery (the reboot is required)
Install the ROM again from internal sdcard using ClockworkMod Recovery
Optionally restore /data from Nandroid Backup (the update will wipe your /data)
Optionally install the Google Addon
- Upgrading from CM10.2?
Do a Nandroid Backup!
Install the ROM from internal sdcard using ClockworkMod Recovery
Optionally install the Google Addon
- Upgrading from another build of CM11?
Do a Nandroid Backup!
Install the ROM from internal sdcard using ClockworkMod Recovery
Warning: You may get set_metadata_recursive related-errors during install if you're using a custom kernel without SELinux support. In that case, revert to the stock kernel before continuing or follow the instruction for upgrading from CM10.1.
Note: The partition layout of CM11 is the same as CM10.2.
Known Issues
Please do not report bugs if it is already listen in the list of known issues
No access to TV-Out menu
Layout issues in lockscreen
Menu soft-buttons appearing where they shouldn't
Some CyanogenMod features a missing - please do not file bug reports for those.
Privacy guard icon not disappearing when exited app
Broken layout of quick message popup (SMS)
Cannot set value via custom brightness "Edit" menu
If back button is pressed during incoming call, you can't answer the call.
FC when changing image sharpness
Pressing "menu" unlocks swipe lockscreen
Browser: FC in incognito mode and Advanced -> Website settings)
Quick Access Ribbon gone when switching from Quick Settings
2G/3G toggle does not work
Cannot flash CM10.2 from recovery (workaround: restore a 10.2 backup or flash a 10.2 kernel before flashing)
Reporting Bugs
You are allowed to report bugs only in this thread. Before reporting a bug, please make sure you are running as stock as possible. This means no custom kernel, no custom framework modification, etc. If you are using any of the above modifications, please flash the rom again to get rid of the modifications before reporting.
REPORT BUGS IN THIS THREAD ONLY
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. The following is a useful format to follow. Note: If you can provide the latest night/build that the bug didn't exist, it would greatly help in tracking down what caused it.
Code:
What is your--
Phone model:
Radio (baseband):
CM version:
CM 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:
CMSettings/Performance settings (other than stock):
ART Runtime:
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
FAQ
Why is there no transparent status bar/lockscreen widget/"OK Google"?
Those features have been disabled by Google for low RAM device in order to save RAM. You can try enabling it by removing "ro.config.low_ram=true" from /system/build.prop, however, it is not an officially supported setup.
Is there a changelog for gapps?
I did not create the packages and do not know. (Please don't annoy the original developer of the packages by asking him either.)
Does this ROM support FM radio?
I've checked and the new FM API in CM is not really compatible with our device without heavy modification. Applications using the new API expect to be able to read the FM input as it if were another stream, but FM on our device only does pass-through from FM receiver to speaker/headset, which causes certain functionalities to not work such as volume control. Maybe one can modify the audio routing table in the kernel to have it behave like the API expected, but I'm not really interested in investing time to do that.
TL;DR: No built-in FM radio except if someone else does it and submits a patch.
the above gapps are what i personally use you can use what ever ones you would like though
Thanks to
pawtip
CM team
FaultException
Kasper_h
anyone else who i forgot pm me and il add you
Is the problem with the phone speaker solved? On receiving calls, speaker didn't work..
is it fixed??
n205des said:
Is the problem with the phone speaker solved? On receiving calls, speaker didn't work..
is it fixed??
Click to expand...
Click to collapse
Deleted
Could you expain what you did to create this ROM? Did you do straight what was said in the Cyanogenmod building instructions for captivatemtd?
ankamar92 said:
Could you expain what you did to create this ROM? Did you do straight what was said in the Cyanogenmod building instructions for captivatemtd?
Click to expand...
Click to collapse
Basicly
New build soon with some kernel modifications to make it even smoother
All the post is C&P from Pawitp i9000 post lol (except links and credits)
But, whatever, I'll download the rom right now, and will try it later..
BTW, gapps links doesn't work.
And..
cannondaleV2000 said:
Deleted
Click to expand...
Click to collapse
What do you mean with "DELETED"? Fixed?
Thanks for your work ^^
When i installed this, all i got was the little cyanogen robot with the rotating arrow, that lasted for about an hour until i got frustrated with it and just went back to my old rom, any ideas on why this is happening?
Boots fine for me. Did you dirty flash or flash anything else with it?
And yeah it is a c&p from pawtip because it is completely stock cm for now at least
Sent from my SGH-I897 using xda app-developers app
Link gapp error ,file not found
cannondaleV2000 said:
Boots fine for me. Did you dirty flash or flash anything else with it?
And yeah it is a c&p from pawtip because it is completely stock cm for now at least
Sent from my SGH-I897 using xda app-developers app
Click to expand...
Click to collapse
Ok, ok, but that not answer my question, the problem with the speaker on receiving call, is fixed?
You answered that to another user --> "Deleted", Deleted == Fixed?
Thanks.
should be. i have not run into the isue so far been running since lastnight.
new build up. syncd with cm sources and tweeked kernel to give more usable available ram
cannondaleV2000 said:
new build up. syncd with cm sources and tweeked kernel to give more usable available ram
Click to expand...
Click to collapse
I think the link you posted, isn't for public, when entering, I can't see anything, only you can see the files on the folder.
OK will fix
Sent from my SGH-I897 using xda app-developers app
Sorry guys I just realized I uploaded the wrong file. Il fix it tomorrow and post a new link
ManaSV93 said:
I think the link you posted, isn't for public, when entering, I can't see anything, only you can see the files on the folder.
Click to expand...
Click to collapse
He linked the myfile link in d-h its goes to my own uploaded file when I logged on in dev- host
Make direct link bro
mohammad.afaneh said:
He linked the myfile link in d-h its goes to my own uploaded file when I logged on in dev- host
Make direct link bro
Click to expand...
Click to collapse
Yep noticed that will fix after school. Because I also uploaded the wrong file top
Downloaded first version, and, have to say that the performance is awesome.
Ram: constant 170 mb free, using BBM, and listening some music.
Web Browser performance was better on CM 10.1
And, with all the KK builds I have tried on the cappy, Every time I turn ON the phone, When OS is completely loaded, I get a message, of invalid IMEI, and that, I can have some problems..
How can I solve this? If I go back to stock rom, and then to CM 10.1, I don't have any problem with this, but when I update to CM 11, I have this error, and don't know wich errors can this give me on future.
Any screenshot ?

[GUIDE] Install Android 11 On J7 2016/J7 Nxt/J7 Prime

A simple guide to help you install Android 11 Beta on your Exynos7870 device.
Code:
[SIZE="4"]/*
* 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.
*/[/SIZE]
Devices Supported - J7 2016, J7 Nxt, J7 Prime and other Exynos7870 devices.
Installation -
1. Boot into custom recovery. (OrangeFox recommended)
2. Repartition system size. Check guide here - https://forum.xda-developers.com/sa...es/tool-universal-repartition-script-t4143541 (Note - Use at your own risk. If you want to restore stock size, flash PIT file in Odin) (Note - Repartitioning will erase your internal storage so backup your data before)
3. Format data and reboot into recovery.
4. Wipe system, data, dalvik cache, cache. (If you get any error related to mounting of /cache, resize FS for cache)
5. Flash Exynos7870_CreateVendor_V2.0 zip.
6. Reboot into recovery again.
7. Flash Android 11 GSI.
8. Flash H-Vendor V1.0 zip.
9. Reboot. It may bootloop once or twice so let it rest for a few minutes until it boots fine.
10. Open Files app and install GooglePlayServices apk.
11. Now you can setup your Google account.
12. For root access, flash Magisk canary zip.
Working -
WiFI
Bluetooth
GPS
Camera (OpenCamera tested)
Hardware keys
Flashlight
Not tested -
RIL (Can't test as I don't have a spare sim)
Mobile data
Bugs -
Hotspot
And more which I don't know + Android 11 Beta bugs
Downloads -
Android 11 GSI - https://mirrors.lolinet.com/firmware/gsi/Pixel/Pixel-AB-11-20200909-ErfanGSI.img-0125.7z
CreateVendor zip - https://drive.google.com/file/d/19_yXIWkfPicXtAA-iE2ngCl1StTUy7ek/view?usp=sharing
H-Vendor v1.0 - https://forum.xda-developers.com/ga...opment-and-mods/treble-h-vendor-v1-0-t4116281
GooglePlayServices apk - https://www.apkmirror.com/apk/googl...0400-320008519-android-apk-download/download/
Magisk canary - https://github.com/topjohnwu/magisk_files/blob/canary/magisk-debug.zip
Repartitioner tool - https://forum.xda-developers.com/sa...es/tool-universal-repartition-script-t4143541
PIT file - https://drive.google.com/drive/folders/1PyflE9X8uTUEw4x8HriT7rpeJgjHwK-s
Credits -
@Astrako for H-Vendor, repartitioner tool
@erfanoabdi for Android 11 GSI
@ananjaser1211 for Project Spaget X
Thanks to all Exynos7870 Devs for working hard!
on j7 2016 it restarts very often and nothing changed for 30 minutes that it was resting
d1r3 said:
on j7 2016 it restarts very often and nothing changed for 30 minutes that it was resting
Click to expand...
Click to collapse
Are you using a sim? Try switching to Airplane mode and see if it still restarts.
has how to disable the navbar?
Ruturaj Kadam said:
A simple guide to help you install Android 11 Beta on your Exynos7870 device.
​
Click to expand...
Click to collapse
Are you still making this rom? need fixes !
Hello, the link for the pit file is dead, can you update the link?
Thanks.
Is the hotspot bug still there?
Voice echo problem....
I keep getting the "invalid zip file format" when I try to flash the GSI file
I keep getting the "invalid zip file format" when I try to flash the GSI file
Çukur dosya bağlantısı çalışmıyor. linki yeniler misin
If my english disturbed you, forgive me...
And I don't know why but UI usually downs and system does fast restaring. (In restarting think like Samsung Galaxy J7 Prime logo isn't show itself but Google logo shows itself)

[ROM][11][UNOFFICIAL] LineageOS 18.1 for Lenovo P2

{
"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 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.
*
Installation:
If you are on stock OS, you need a custom recovery first. You can get the recommended LineageOS recovery in the official installation instructions link below.
You can use TWRP for installation, however it is no longer officially supported since we do not have full control of its update cycle and potential issues.
If you are coming from stock or other ROMs, you need to make a factory reset.
As always, make sure to backup before installing this ROM.
Installation Instructions:
Backup your data and see the next post below
Recommended TWRP Image:
twrp-3.7.0_9-0-kuntao.img
ROM Download Links:
Google Drive | MEGA.nz | SourceForge
Recommended Google Apps Package:
NikGapps-core & NikGapps-SetupWizard, or
MindTheGapps (choose ARM64 11.0 zip)
OpenGapps (choose ARM64 11.0 nano or pico) (not working anymore)
Root Access:
Magisk v26.1
Source Code:
https://github.com/LineageOS
ROM Firmware Required:
Any version of stock 6.0. Recommended P2a42_S251_171107_ROW
Latest Lineage OS 18.1 official (aka lineage-18.1-20221023-nightly-kuntao-signed)
Acknowledgements:
Thanks to @mikeioannina and all Lineage OS developers for the official builds
Special thanks to @Astridxx & @XiaoAk for helping me out
Important Notes:
As you can see from my profile, I'm not an experienced developer. I've made some builds after the official support drop and I'm sharing them here as a considerable amount of users showed interest in having their devices updated with latest LineageOS code. Therefore, my main objective here is to bring the latest Android security patches to kuntao making monthly builds.
To be clear, I'm more in a situation of "user became builder" than of "ROM developer". Please, understand this.
Long live to our beloved kuntao!
XDAevDB Information
[ROM][11][UNOFFICIAL] LineageOS 18.1 for Lenovo P2
Contributors
@Astridxx ,@XiaoAk ,@Sohit5s, @mikeioannina
ROM OS Version: 11
ROM Kernel: Linux 3.18.x
Based On: LineageOS
Version Information
Status: Stable
Created 2023-01-28
Last Updated 2023-06-12
Installation Instructions​
Remember, making a backup of your data before proceeding is recommended
If you are coming from Stock ROM, please refer to the instructions below:
Install LineageOS on kuntao
If you are coming from the latest official build, please follow these to a clean flash:
1- Wipe:
- Dalvik
- System
- Data
- Cache
- Internal Storage (optional)
2- Flash ROM ZIP, Gapps, Magisk addon, etc
3- Clean Cache
4- Reboot to system
5- Wait until it boots for the first time (may take some minutes)
Update Instructions​
For updating from one of my builds to another, please do the following:
1- Download ROM ZIP and copy to the phone
2- Reboot to recovery
3- Flash ROM ZIP
4- Reboot to system
Boot loop/Boot inside TWRP Fix Instructions​
1- Reboot to recovery
2- Wipe > Format data (careful, will erase everything and remove storage encryption)
3- Then repeat wipe from step 1 of Installation Instructions
4- Reboot to recovery again
5- Copy the ZIP files (ROM, Gapps...) to internal storage
6- Flash ZIP files again
7- Reboot to system
8- Wait for the boot and encryption process (may take some minutes)
9- Phone will reboot automatically and then start the system
10- Finish the setup wizard (Wifi, Google acc, etc)
10.1- Reboot the system in order to finish installing Magisk App (optional)
SafetyNet Status Fix Instructions​
1- Make sure Magisk was properly installed
2- Open the Magisk App
3- Open App settings (wheel on the top right side of the screen)
4- Enable "Zygisk"
5- Enable "DenyList"
6- Open "Configure DenyList"
6.1- Click the three dots on top right corner of the screen
6.2- Enable "Show system apps"
6.3- On "Google Play services": Enable "com.google.android.gms" & "com.google.android.gms.unstable"
6.4- On "Google Play Store": Enable "com.android.vending"
7- Click on the back arrow (on top left)
8- Reboot your system
9- Test again (now it should pass)
Note: For Magisk versions below 26.x, it might not be needed to follow steps 6.1 and 6.2 as the system apps should be already being displayed.
ROM Change log​
Code:
01/28/2023
- Initial release
01/31/2023
- Sync latest LOS source
02/20/2023
- Update LOS modules
-- packages/modules/NeuralNetworks
-- system/connectivity/wificond
- Sync latest LOS source
- Merge February security patch
03/28/2023
- Update LOS components
-- Manifest: Sync x86_64 webview prebuilts again
-- Update zlib source
- Sync latest LOS source
- Merge March security patch
04/21/2023
- Device Tree: Change proprietary blobs from official sources to themuppets' ones
- LOS: apn: update for T Star, Vibo and AURORA
- Sync latest LOS source
- Merge April security patch
05/10/2023
- Device Tree: Updates translations
- Sync latest LOS sources
-- Track vendor/crowdin
- Merge May security patch
06/12/2023
- Fetch latest Device Tree
-- Merge updated translations
- Sync latest LOS sources
- Merge June security patch
ROM Screenshots​Attached below
February 2023 Release​Changelog: Plz, read first post
Download URLs: GDrive | MEGA | SourceForge
Enjoy!
Thanks very much for keeping this alive.
Hi,
I have a stock ROM 7, but I would like to install a newer version of Android because some app doesn't install anymore on Android 7... So, I would like to try LineageOS 18.1. I have already unlocked and rooted my p2a42.
I've read for around 3h lots of posts and opinions on this forum. There is a huge information on it, you are awesome!!
However, I don't know where to find a "build" for my p2a42. When following the "instruction" link (https://wiki.lineageos.org/devices/kuntao/install) it's required to "build" an installation package. However, it seems that p2a42 is not anymore recognised (https://wiki.lineageos.org/devices/kuntao/build).
Furthermore, I've read that the proposed MEGA links are just for updating from previous LyneageOS versions. So, any advise on how to install LyneageOS in my stock ROM 7?
Thanks!
escombralls said:
Hi,
I have a stock ROM 7, but I would like to install a newer version of Android because some app doesn't install anymore on Android 7... So, I would like to try LineageOS 18.1. I have already unlocked and rooted my p2a42.
I've read for around 3h lots of posts and opinions on this forum. There is a huge information on it, you are awesome!!
However, I don't know where to find a "build" for my p2a42. When following the "instruction" link (https://wiki.lineageos.org/devices/kuntao/install) it's required to "build" an installation package. However, it seems that p2a42 is not anymore recognised (https://wiki.lineageos.org/devices/kuntao/build).
Furthermore, I've read that the proposed MEGA links are just for updating from previous LyneageOS versions. So, any advise on how to install LyneageOS in my stock ROM 7?
Thanks!
Click to expand...
Click to collapse
Hello,
To install LOS18.1 you should have a TWRP recovery already installed on your phone. Afterwards you have to download the ROM ZIP from any of the URLs on the first post (this will contain the OS, you can download the latest version, this is the build you are looking for). Then in order to have access to the Google Services (GMail, Play Store, etc) you must install GApps (URLs linked on the first post too).
Backup your data, perform step 1 of install instructions (wipe part) then copy the downloaded files to the phone's internal storage, then you can follow the other steps. This should give you the LineageOS custom OS based on android 11.
Note that the Stock ROM is Lenovo's android OS. LineageOS is another OS based on AOSP. So by installing LOS you will be switching the OS part of your phone.
I hope I could clarify the process to you, if you have any other questions please feel free to post them here
Thanks for the reply. It runs flawlessly.!!
March 2023 Release​Change log:
- Update LOS components
-- Manifest: Sync x86_64 webview prebuilts again
-- Update zlib source
- Sync latest LOS source
- Merge March security patch
Download URLs: GDrive | MEGA | SourceForge
Notes:
- Release was a bit delayed because of testing process (thanks @en666 for being our tester)
- Starting from next release, only the most updated build will be available on Google Drive (due to storage limitations). Mega & Source Forge will remain normal, so if you need a past build, refer to one of the URLs from first post, thanks for understanding.
Enjoy!
First time installing. No issues aside from looking up some instructions for twrp and adb and ignoring some that are on the lineageos page. Came from Android 7, so far it works great. Installed this on my dads P2, thinking I'll try your lineageos 20 on my own P2 and see how that goes. Thank you for keeping this phone alive.
April 2023 Release​
Change log:
- DT: Change proprietary blobs from official sources to TheMuppets' ones
- LOS: apn: update for T Star, Vibo and AURORA
- Sync latest LOS source
- Merge April security patch
Download URLs: GDrive | MEGA | SourceForge
Notes:
- If clean flashing, please use NikGapps because OpenGapps will cause system to not boot (URLs already updated on OP)
- Magisk v26.x can be flashed through TWRP as usual, and IFAIK it works even without the "additional setup", so you can ignore it (trying to install Magisk via its app doesn't work, it keeps flashing boot image indefinitely)
- As stated on previous release announcement, only the most updated build is available on Google Drive, the other ones were purged (reason: storage limitations)
Enjoy!
Regards,
some one have problem with dirty flashing/upgrade from March ?
So, uninstalled Magisk, decrypted and after upgrade which passed fine I can't get to Normal screen just returning to Recovery after some time. Every time. Made backups, earlier, so no warry.
THX
Hey guys!
For those who did a clean install with the latest April release, can you please check if the phone is using Galileo satellites now with the blobs from TheMuppets?
Thanks!
3volution3 said:
Hey guys!
For those who did a clean install with the latest April release, can you please check if the phone is using Galileo satellites now with the blobs from TheMuppets?
Thanks!
Click to expand...
Click to collapse
Hello,
I'm not currently on EU, so I couldn't test it out. I asked one of the testers and he said that unfortunately Galileo satellites weren't being used to GPS/GNSS.
Furthermore, according to GSM Arena and LineageOS wiki, our P2 doesn't support Galileo satellites.
Regards.
leo_97 said:
Hello,
I'm not currently on EU, so I couldn't test it out. I asked one of the testers and he said that unfortunately Galileo satellites weren't being used to GPS/GNSS.
Furthermore, according to GSM Arena and LineageOS wiki, our P2 doesn't support Galileo satellites.
Regards.
Click to expand...
Click to collapse
Alright, thanks. Galileo support just needs an update from the manufacturer. The hardware for GPS and Galileo is the same as long as the chipset supports it (which in the case of our P2 it does). A few devices from other manufacturers got the update, but unfortunately the P2 didn't. I was just wondering if the blobs from TheMuppets were updated with files from a more recent SD625 device with Galileo support, but apparently not. They are just the same'ol blobs.
May 2023 Release​
Change log:
- Device Tree: Updates translations
- Sync latest LOS sources
-- Track vendor/crowdin
- Merge May security patch
Download URLs: GDrive | MEGA | SF
Notes:
- If clean flashing, please use NikGapps because OpenGapps will cause system to not boot (URLs already updated on OP)
- Magisk v26.x can be flashed through TWRP as usual, and IFAIK it works even without the "additional setup", so you can ignore it (trying to install Magisk via its app doesn't work, it keeps flashing boot image indefinitely)
- If dirty flashing, flashing Magisk ZIP again may be needed
Enjoy!
June 2023 Release​
Change log:
- Fetch latest Device Tree
-- Merge updated translations
- Sync latest LOS sources
- Merge June security patch
Download URLs: GDrive | MEGA | SF
Notes:
- If clean flashing, please use NikGapps because OpenGapps will cause system to not boot
- Magisk v26.x can be flashed through TWRP as usual, and IFAIK it works even without the "additional setup", so you can ignore it (trying to install Magisk via its app doesn't work, it keeps flashing boot image indefinitely)
Enjoy!

[ROM][12.1][UNOFFICIAL] LineageOS 19.1 for Lenovo P2

{
"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 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.
*
LineageOS is a free, community built, aftermarket firmware distribution of Android 12L (Sv2), 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 Githup repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review.
Installation:
If you are on stock OS, you need a custom recovery first. You can get the recommended LineageOS recovery in the official installation instructions link below.
You can use TWRP for installation, however it is no longer officially supported since we do not have full control of its update cycle and potential issues.
If you are coming from stock or other ROMs, you need to make a factory reset.
As always, make sure to backup before installing this ROM.
Installation Instructions:
Backup your data and see the next post below
Recommended TWRP Image:
twrp-3.7.0_9-0-kuntao.img
ROM Download Links:
Google Drive | SourceForge
Recommended Google Apps Package:
NikGapps-core-12.1
NikGapps-SetupWizard
NikGapps-AndroidAuto
Or
MindTheGapps-12.1 (Google Drive mirror)
Root Access:
Magisk v25.2 (more stable experience)
Magisk v26.1 (more updated build)
Recommended Useful Add-on:
p2oggle-1.2
Source Code:
https://github.com/LineageOS
ROM Firmware Required:
Any version of stock 6.0. Recommended P2a42_S251_171107_ROW
Acknowledgements:
Thanks to @mikeioannina for his hard work regarding kuntao and to all other Lineage OS developers
Special thanks to @Astridxx for the device tree sources and for helping me out and to @en666 for early testing the initial build
Important Notes:
As you can see from my profile, I'm not an experienced developer. I've made some builds as a considerable amount of users showed interest in having their devices updated with latest LineageOS code. Therefore, my main objective here is to bring the latest Android security patches to kuntao making monthly builds.
To be clear, I'm more in a situation of "user became builder" than of "ROM developer". Please, understand this.
Long live to our beloved kuntao!
XDAevDB Information
[ROM][12.1][UNOFFICIAL] LineageOS 19.1 for Lenovo P2
Contributors
@Astridxx ,@XiaoAk ,@Sohit5s, @mikeioannina
ROM OS Version: 12.x
ROM Kernel: Linux 3.18.x
Based On: LineageOS
Version Information
Status: Stable
Created 2023-02-22
Last Updated 2023-06-11
Installation Instructions​
Remember, making a backup of your data before proceeding is recommended
If you are coming from Stock ROM, please refer first to the instructions below:
Install LineageOS on kuntao
If you are coming from astridxx previous build (aka lineage-19.1-20220822-UNOFFICIAL-kuntao) or my initial build (aka lineage-19.1-20230222-UNOFFICIAL-kuntao) or any version of LOS18.1 or below, you must perform a clean flash. Clean flash instructions:
0- Make a backup (optional, but recommended)
1- Reboot to recovery
2- Format data (will delete all your data!)
3- Reboot to recovery again
4- Wipe > Advanced Wipe:
- Dalvik
- System
- Vendor
- Data
- Cache
- Internal Storage (optional, but recommended)
5- Flash ROM ZIP, Gapps, Gapps add-ons, Magisk add-on, etc
6- Reboot to system
7- Wait until it boots for the first time (may take some minutes)
Update Instructions​
NOTE: Dirty flash from any of the aforementioned builds is not supported, device trees were changed. You have been warned!
For updating from one of my builds to another (aka dirty flashing), please do the following:
1- Download ROM ZIP and copy it to the phone
2- Reboot to recovery
3- Flash ROM ZIP
4- Clean cache
5- Reboot to system
Known Issues​- Storage encryption is partially broken (if your /data partition is unencrypted, trying to encrypt it using ROM menu will result in a dead OS; if already encrypted, storage encryption may or may not work. IFAIK, it's a kernel side issue)
- Device may not go to deep sleep
- Storage forceencrypt flag is disabled (to encrypt /data partition follow the instructions below)
- TWRP backups are broken (read notes below)
- You tell
Google Play Store Update Bug​
If Google Play Store app keeps failing to find updates for apps with message "Something went wrong. Try again.", just clear its data and then it should work again
SafetyNet Check Fails​
If your device is rooted, please, follow the instructions contained here
Magisk is Gone After First Boot​
Please, just reflash Magisk again (i.e. Reboot to recovery > Flash ZIP > Reboot back to system)
How to encrypt data partition​
0- Backup your files (this process will erase everything)
1- Boot to TWRP recovery
1.1- Wipe > Format data > Reboot to system
2- Settings menu > Security > Encryption & credentials > Encrypt phone
3- Reboot to system again
Error restoring TWRP system backups​
It looks like TWRP backups are broken for now, so please, if this is a must have for you, you can try to install OrangeFox recovey and follow these instructions (thanks @Zdeslav for that)
ROM Change logs​
Code:
02/22/2023
- Initial release
02/27/2023
- Sync latest LOS sources
- Device Tree change: Use old A12L dt instead of los
- Add Lenovo Parts menu (fp gestures, USB fast charge, in-call audio gain, screen kcal)
- Updates phone vibration strength
- Add fix to device deep sleep issue
- Many more changes
03/29/2023
- Fetch latest Device Tree sources
-- vendorsetup.sh: Add Trebuchet patch
-- AOSP WFD doesn't support protected Wi-Fi Display buffers
-- Overlays:
--- Enable voWIFI support
--- Disable IMS features for Turkiye networks
-- Don't warn user about FC in Vanced microG
-- DT rootdir:
--- Add cpuset for the camera daemon
--- Remove permission restrictions to the socket file
--- Restore iio sensor device6 on boot
-- Bump graphene camera version to 60
-- Don't force enable ims features
-- sepolicy: Address sensor hal denials
- Update LOS components
-- Manifest: Sync x86_64 webview prebuilts again
-- Update zlib source
- Sync latest LOS source
- Merge March security patch
04/09/2023
- Fetch latest Device Tree sources
-- Add navbar enable/disable support
-- fs: Revert sdfat update for OTG
-- block: Add zen io scheduler
-- dts: Decrease BCL low battery threshold to 5%
-- DeskClock:
--- Wallpaper based text coloring for digital
--- Adapt digital clocks to S style
--- Remove night mode
-- Trebuchet:
--- Kill haptics in recents
--- Make overview scrim transparent again
-- Nfc: Fix Mifare Classic reading
- Update LOS components:
-- lineage: Track the FMRadio App and dependencies
- Sync latest LOS source
04/19/2023
- Fetch latest Device Tree sources:
-- sepolicy: Silence tracingproxy_service neverallow denial
-- sepolicy: Allow system_app to access storaged via IPC
- Sync latest LOS source
- Merge April security patch
05/09/2023
- Fetch latest Device Tree sources:
-- Bump graphene camera version to 62
-- devicesettings: Protect broadcast to fingerprint gestures
-- rootdir: Remove permission restrictions to the socket file
- Sync latest LOS source
- Merge May security patch
06/11/2023
- Fetch latest Device Tree sources:
-- parts: Update few parts icon
-- vendorsetup.sh: Use depth=1
-- Remove pixel_2016_exclusive
-- Bump graphene camera version to 63
- Sync latest LOS sources:
-- Additional zstd cmdline tools
-- zstd compression support for rsync
-- 2023-06 ASB patching: packages/apps/Traceur
- Merge June security patch
ROM Screenshots​
Attached below. Others are available here.
February 27th 2023 Release​
Changelog:
- Sync latest LOS sources
- Device Tree change: Use old A12L dt instead of los
- Add Lenovo Parts menu (fp gestures, USB fast charge, in-call audio gain, screen kcal)
- Updates phone vibration strength
- Add fix to device deep sleep issue
- Many more changes
Download URLs: GDrive | SF
Dirty flash still not supported (tree changed), please make a clean flash
Thank you so much for keepng Lineage alive, its very much appreciated.
@leo_97 thank you for this new build! Installed it straight away and now the phone is running since then and also, I've flashed with battery at 67% and atm, after a quite hard usage to test out the new features, I'm on 13%. Basically, so far so good!
p2a42, twrp 3.7, rooted, unencrypted
Thank you @leo_97 !
I was frustrated that Lineageos 18.1 was no longer maintained when I saw this update!
It's amazing
To all users and developers who tested and created this ROM, is it time to switch on this version ?
Or is it better to wait ?
For example, automatic update is possible after install ?
bidulez said:
automatic update is possible after install ?
Click to expand...
Click to collapse
No
bidulez said:
Thank you @leo_97 !
I was frustrated that Lineageos 18.1 was no longer maintained when I saw this update!
It's amazing
To all users and developers who tested and created this ROM, is it time to switch on this version ?
Or is it better to wait ?
For example, automatic update is possible after install ?
Click to expand...
Click to collapse
You are welcome
If it's time to switch, I believe it's a matter of personal decision. Maybe you could wait the next build and then decide...
If with "automatic updates" you mean OTA updates, then the answer (as already pointed out by @utwer ) is no. But once the trees are stable enough, I hope every user will be able to just update to the newer versions flashing ROM ZIP through TWRP (just like it's done on LOS18.1)
BTW, IDK if you already saw it, but we are maintaining a monthly build of LOS18.1 which you can download from here. The source tree used there is far more tested (as it's older) than this one. Anyway, except by the encryption thing, you shouldn't have any problems using this LOS19.1 ROM as our amazing developers made an excellent job here.
Reg, Ive installed it and I may say it is quite good. Not tried to root it yet. Dont have direct problems with ROM and functionality, for me everything works. Camera, Location, GSM, Data, WiFi. With developer options I've turned off Animation scale on three options to OFF, and is good. Stable reliable.
MindTheGapps-12.1 works every app from Google, Phone, Contact, Gmail, maps...etc...
What I need root mostly is for Call recording (Skvalex) and Viper4Android.
Some words about twrp-3.7.0_9-0-kuntao.img,
With this I have only problems, so far I lost a few backups and I need to install it all over again a few times allready. Disappointed very. I can't rally on this when I make a nandroid ba.ckups.
Also lost backups for LOS18.1 and I am been very pis....ed off. Error 255 on System recovery, other Data, Boot, EFS, Vendor, etc.. recovery is good.
So I've installed OrageFox for Kuntao. Tried several backups to restore already and I may say I am very satisfied. Puh
What is on my mind, when I installed a Magisk 25.2, no matter of LOS 18.1 or 19.1 with very few modules, after 7-8 reboots I've got boot loops which is beyond repairable.. Try to remove modules in TWRP in file manager, uninstall whole magisk, no way, but what it is seems that DATA got corrupted some how, everytime.
There were also installed TWRP mentioned above.
Now I am with OrangeFox and I will try tomorrow to Root it and see is there any connection between Magisk and recovery software (OrangeFox or TWRP).
Reg
Tried quickly this ROM yesterday. In general all working, but didn't test much.
Few feedbacks:
-Scaler for brightness level is weird, very different from the original Lenovo roms. Anyway, not really important, but something that I noticed.
-Missing haptic feedback when using the fingerprint reader as a gesture button. Again, not critical, but I am really accustomed to it and thus I noticed immediately.
-Missing haptic feedback intensity regulation, or could not find it. It's there for general call/notification vibration, but if I remember correctly lineage could also change haptic.
Impressed that you could integrate also some lenovo features, even if of course not all of them
If you want me to test something more specific, please let me know. Ah, my model is the 4 GB/ 64 GB combination.
Cheers!
leo_97 said:
You are welcome
If it's time to switch, I believe it's a matter of personal decision. Maybe you could wait the next build and then decide...
If with "automatic updates" you mean OTA updates, then the answer (as already pointed out by @utwer ) is no. But once the trees are stable enough, I hope every user will be able to just update to the newer versions flashing ROM ZIP through TWRP (just like it's done on LOS18.1)
BTW, IDK if you already saw it, but we are maintaining a monthly build of LOS18.1 which you can download from here. The source tree used there is far more tested (as it's older) than this one. Anyway, except by the encryption thing, you shouldn't have any problems using this LOS19.1 ROM as our amazing developers made an excellent job here.
Click to expand...
Click to collapse
So for 18.1 we can just flash the newer versions via TWRP and do not have to reinstall the entire ROM?
Zdeslav said:
Reg, Ive installed it and I may say it is quite good. Not tried to root it yet. Dont have direct problems with ROM and functionality, for me everything works. Camera, Location, GSM, Data, WiFi. With developer options I've turned off Animation scale on three options to OFF, and is good. Stable reliable.
MindTheGapps-12.1 works every app from Google, Phone, Contact, Gmail, maps...etc...
What I need root mostly is for Call recording (Skvalex) and Viper4Android.
Some words about twrp-3.7.0_9-0-kuntao.img,
With this I have only problems, so far I lost a few backups and I need to install it all over again a few times allready. Disappointed very. I can't rally on this when I make a nandroid ba.ckups.
Also lost backups for LOS18.1 and I am been very pis....ed off. Error 255 on System recovery, other Data, Boot, EFS, Vendor, etc.. recovery is good.
So I've installed OrageFox for Kuntao. Tried several backups to restore already and I may say I am very satisfied. Puh
What is on my mind, when I installed a Magisk 25.2, no matter of LOS 18.1 or 19.1 with very few modules, after 7-8 reboots I've got boot loops which is beyond repairable.. Try to remove modules in TWRP in file manager, uninstall whole magisk, no way, but what it is seems that DATA got corrupted some how, everytime.
There were also installed TWRP mentioned above.
Now I am with OrangeFox and I will try tomorrow to Root it and see is there any connection between Magisk and recovery software (OrangeFox or TWRP).
Reg
Click to expand...
Click to collapse
So,
Resolved issue of bootloops:
after you install SU like Magisk, and wan to freeze apps by Titanium Backup or Neo-Backup, Apps which causes bootloops are ROM's Phone and Massages (In my case, for 16.1, 18.1, 19.1), I freeze Audio.apk who need to be shutdown for Viper4Android app who takes audio management and freezing is OK.
But Phone and Massages which are frozen cause bootloops, so you need to return from freeze state somehow in TWRP or OrangeFox with file management or revert backup. Revert backup is easier .
Camera; found issue when suddenly is out of work and cannot be connected to app. Also have problems with video cast Skype, Viber, Whatsapp, Telegram video is frozen. Hardly switch in Camera app from Camera mode to Video mode and vice-versa.
Clock & Info; missing dock icons and info, can't "capture" moment for reason when they disappear but after a while all is returned again.
P2oggle, left switch button work okey in form of 0.4 version.
Reg,
thanks on the development for this 19.1 ROM.
Zdeslav said:
Camera; found issue when suddenly is out of work and cannot be connected to app. Also have problems with video cast Skype, Viber, Whatsapp, Telegram video is frozen. Hardly switch in Camera app from Camera mode to Video mode and vice-versa.
Clock & Info; missing dock icons and info, can't "capture" moment for reason when they disappear but after a while all is returned again.
P2oggle, left switch button work okey in form of 0.4 version.
Reg,
thanks on the development for this 19.1 ROM.
Click to expand...
Click to collapse
Hello,
I've been using this ROM as my daily driver and couldn't confirm this camera bug, could you please give a few extra details? I tested on Telegram app. Which version are you using? The Play Store's one or the one from Telegram's official website? Did you give the app "While using app" permission or "Ask every time" permission for camera? Are you sure the QS Tile "Camera access" is activated (available) when the mentioned bug occurs?
Regarding the Clock widget, yes, there's a small glitch and I'm not sure on how to fix it, if it doesn't load at all, a system reboot should fix it.
P2oggle v1.2 is 100% working as far as I can tell, so you guys can try it too if you want.
MKbis said:
-Scaler for brightness level is weird, very different from the original Lenovo roms. Anyway, not really important, but something that I noticed.
-Missing haptic feedback when using the fingerprint reader as a gesture button. Again, not critical, but I am really accustomed to it and thus I noticed immediately.
-Missing haptic feedback intensity regulation, or could not find it. It's there for general call/notification vibration, but if I remember correctly lineage could also change haptic.
Click to expand...
Click to collapse
I'm not sure if it's possible to "fix" the brightness slider.
If with "haptic feedback" you mean the phone vibration, you can just adjust it to your liking in Settings > Lenovo parts > Vibration strength, it should affect fp reader too, dunno if it affects call vibration but IFAIK it should.
Regards
Leo_97
I've been using this ROM as my daily driver and couldn't confirm this camera bug, could you please give a few extra details? I tested on Telegram app. Which version are you using? The Play Store's one or the one from Telegram's official website? Did you give the app "While using app" permission or "Ask every time" permission for camera? Are you sure the QS Tile "Camera access" is activated (available) when the mentioned bug occurs?
Click to expand...
Click to collapse
Yes on latest Telegram app from web site, tried with Google Meet, Whatsapp, Viber.., always breaking connection with API/drivers. Yes I gave all permissions to Camera. If I am not giving permissions for camera, I have always noticed to confirm what I am giving, so I am excluded from this solution. And clean storage and cashe from app regular but not prevail.
But, in a while after installed a new ROM without giving SU/Root I noticed this behavior, right after I wrote earlier post up. My bad .
Choppy startup of camera, can't easily transfer from video 2 camera and vice-versa, so I tell to my self to test intensively.
Regarding the Clock widget, yes, there's a small glitch and I'm not sure on how to fix it, if it doesn't load at all, a system reboot should fix it.
Click to expand...
Click to collapse
Yes after a while it is returned back without reboot. weird.
P2oggle v1.2 is 100% working as far as I can tell, so you guys can try it too if you want.
Click to expand...
Click to collapse
Didn't know about P2oggle v1.2 app, thx
March 29th 2023 Release​
Changelog:
- Fetch latest Device Tree sources
- Update LOS components webview & zlib
- Sync latest LOS source
- Merge March security patch
- Many more changes
Full change log available on the bottom of this post
Download URLs: GDrive | SF
Note: Please, before flashing, carefully read the instructions from the 3rd post above to avoid breaking your system.
Enjoy!
Big Thank you for this release. Will try it. - test
Great job, dude.
Previous versions had some buggy charging driver that left a wakelock running after each charging, and u had to restart phone each time or leave it to slowly drain battery by not going to sleep.
Somehow this problems seems to be gone in your build and that is awesome.
I've been using the build for about 2 weeks now and so far everything seems to be working fine.
April 09th 2023 Release​
Change log:
- Fetch latest Device Tree sources (lots of changes)
- Update LOS components:
-- lineage: Track the FMRadio App and dependencies
- Sync latest LOS source
- Many more changes
Full change log available on the bottom of this post
Download URLs: GDrive | SF
Note: Dirty flash is unsupported for this build, please make a clean flash
Enjoy!

[ROM][13][UNOFFICIAL] LineageOS 20 for Lenovo P2

{
"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 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.
*
LineageOS is a free, community built, aftermarket firmware distribution of Android 13 (T), 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 Githup repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review.
Installation:
If you are on stock OS, you need a custom recovery first. You can get the recommended TWRP recovery in the installation instructions link below.
If you are coming from stock or other ROMs, you need to make a factory reset.
As always, make sure to backup before installing this ROM.
Installation Instructions:
Backup your data and see the next post below
Recommended TWRP Image:
twrp-3.7.0_9-0-kuntao.img
ROM Download Links:
Google Drive | SourceForge
Recommended Google Apps Package:
NikGapps-core-13
NikGapps-SetupWizard
NikGapps-AndroidAuto
Root Access:
Magisk v25.2
Source Code:
https://github.com/LineageOS
ROM Firmware Required:
Any version of stock 6.0. Recommended P2a42_S251_171107_ROW
Acknowledgements:
Thanks to all Lineage OS developers
Special thanks to @Astridxx & @XiaoAk for the device tree sources and to @Astridxx for (once again) helping me out
Important Notes:
As you can see from my profile, I'm not an experienced developer. I've made some builds as a considerable amount of users showed interest in having their devices updated with latest LineageOS code. Therefore, my main objective here is to bring the latest Android security patches to kuntao making monthly builds.
To be clear, I'm more in a situation of "user became builder" than of "ROM developer". Please, understand this.
Long live to our beloved kuntao!
XDAevDB Information
[ROM][13][UNOFFICIAL] LineageOS 20 for Lenovo P2
Contributors
@Astridxx ,@XiaoAk
ROM OS Version: 13.x
ROM Kernel: Linux 3.18.x
Based On: LineageOS
Version Information
Status: Stable
Created 2023-03-05
Last Updated 2023-04-20
Installation Instructions​
Remember, making a backup of your data before proceeding is recommended
If you are coming from Stock ROM, please refer first to the instructions below:
Install LineageOS on kuntao
If you are coming from any version of LOS18.1 or LOS19.1 or from any ROM that isn't android 13 based, you must perform a clean flash:
0- Make a backup (optional, but recommended)
1- Reboot to recovery
2- Format data (will delete all your data!)
3- Reboot to recovery again
4- Wipe > Advanced Wipe:
- Dalvik
- System
- Vendor
- Data
- Cache
- Internal Storage (optional, but recommended)
5- Flash ROM ZIP, Gapps, Gapps add-ons, Magisk add-on, etc
6- Reboot to system
7- Wait until it boots for the first time (may take some minutes)
8- If Magisk is missing after finishing the setup wizard, please reboot to system
Update Instructions​
For updating from one of my builds to another (aka dirty flashing), please do the following:
1- Download ROM ZIP and copy it to the phone
2- Reboot to recovery
3- Flash ROM ZIP
4- Clean cache
5- Reboot to system
Known Issues​
- Storage encryption is broken ( FDE was deprecated in a13 )
- Network traffic monitoring ( 4.9 kernel required for this )
- GPU monitoring ( 4.9 kernel required for this )
ROM Doesn't Boot After Flashing​
Make sure you formatted /data partition (see installation instructions step 2)
SafetyNet Status Fix Instructions​
1- Make sure Magisk was properly installed
2- Open the Magisk App
3- Open App settings (wheel on the top right side of the screen)
4- Enable "Zygisk"
5- Enable "DenyList"
6- Open "Configure DenyList"
6.1- On "Google Play services": Enable "com.google.android.gms" & "com.google.android.gms.unstable"
6.2- On "Google Play Store": Enable "com.android.vending"
7- Click on the back arrow (on top left)
8- Reboot your system
9- Test again (now it should pass)
ROM Change logs​
Code:
03/05/2023
- Initial release
03/30/2023
- Fetch latest Device Tree
-- Sepolicy:
--- Address sensor hal denials
--- Address launcher3 denials
--- Allow some apps to access debuggable prop
-- rootdir:
--- Create STSensorHAL folder on data
--- Restore iio sensor device6 on boot
--- Add cpuset for the camera daemon
-- overlays:
--- Disable IMS features for Turkiye networks
--- Enable voWIFI support
-- prop:
--- Disable Bluetooth APCF Extended features
--- Enable ro.hwui.render_ahead and set it to 20 frames
-- Enable selinux ignore never allow flag
-- Don't force enable ims features
-- Remove aptX(HD) encoder shared libs
-- vendorsetup.sh: Add Trebuchet patch
- Update LOS components
-- Manifest:
--- Sync x86_64 webview prebuilts again
--- March 2023 Quarterly Platform Release and Security update
--- gs101 March 2023 Quarterly Platform Release and Security update
-- Update zlib source
- Sync latest LOS sources
- Update platform to android-13.0.0_r35
- Merge March security patch
04/20/2023
- Fetch latest Device Tree:
-- Set default livedisplay mode to 0
-- vendorsetup.sh: Add DeskClock patch
-- trebuchet:
--- Make overview scrim transparent again
--- Kill haptics in recents
-- nfc: Fix Mifare Classic reading
-- sepolicy:
--- Silence suspend_control_service neverallow denial
--- Silence tracingproxy_service neverallow denial
--- Silence fsck_untrusted neverallow denial
--- Allow system_app to access storaged via IPC
-- overlay: Allow gms to access persistent data partition
-- props:
--- Silence ResourcesCompat spam
--- Remove hwui skia atrace properties
--- Disable virtual displays writeback
-- Revert "sepolicy: Allow some apps to access debuggable prop"
- Sync latest LOS sources:
-- lineage: Track the FMRadio App and dependencies
-- Move Trebuchet to default.xml
-- overlay:
--- Disable immersive mode confirmation
--- Move default status bar height to no-rro
-- soong: Bring bootloader_message_offset back
-- envsetup: aospremote: Take .gitupstream into account
- Update platform to android-13.0.0_r41
- Merge April security patch
ROM Screenshots​
Attached below.
Great work! Will test it when I have time, been waiting for this..
Hi all. I read these P2 forums for long time, but never participated. I love our P2 phone, riding a P2 since the release date and never changed. Now I got a message from my bank that the android version is too outdated to use their banking app, and they want me to switch to a newer OS. I could have ditched the P2, but couldn't. Therefore....easiest solution was to buy a second one xD I will test on the backup unit some of the roms available here, probably starting from the roms of @leo_97 . I need a stable daily driver, thus when I find something that works for me I will freeze it there for some time. But, in the meantime, I can help out with testing, starting from mid April onwards thus, feel free to contact me, and I will be a bit more active (and not passive) here in XDA for the coming months.
Cheers to all, and thanks @leo_97 , @Astridxx, @XiaoAk (and @mikeioannina for all the past efforts on P2!).
Hi
I just tested it on a P2 for a few hours and it works great! Thanks!
Is there any way to get full device encryption to work?
If I understand correctly, someone can access the phone's files even if you have a pin or password as it is now.
MKbis said:
But, in the meantime, I can help out with testing, starting from mid April onwards thus, feel free to contact me, and I will be a bit more active (and not passive) here in XDA for the coming months.
Click to expand...
Click to collapse
I'll PM you right away.
Draywen said:
Hi
I just tested it on a P2 for a few hours and it works great! Thanks!
Is there any way to get full device encryption to work?
If I understand correctly, someone can access the phone's files even if you have a pin or password as it is now.
Click to expand...
Click to collapse
You are welcome
So, IFAIK we don't have a way to make FDE work on A13 ROMs, A13 moved to FBE (File Based Encryption) which is not supported by 3.18.x kernel and we don't have rn a patch available that could enable it on our kernel version.
Regarding data access, I believe so. Without storage encryption, booting into recovery will already give access to the files. IIRC to this date encryption is fully working only on A11-based ROMs and maybe on some A12 ones.
Okay, so I'm stuck in a boot loop. I flashed the ROM from the link above but the phone won't start up. I just get the Lineage booting screen with the circle moving right to left. I've left it for 15 minutes just in case the first boot was slow but nothing else happens. I've tried to restore my original backup which was Lineage 17.1. It seemed to work, no errors from TWRP but now i just get the Lenovo screen and then it boots to fastboot mode. I flashed Lineage 20 for a second time but the same happened. I tried a different backup from August last year, again it just boots to fastboot.
Any ideas?
Cheers, Si.
EDIT: I've just noticed that I missed out step 3, reboot to recovery between Data wipe and flash ROM.
Now it boots no problem.
Cheers, Simon.
EDIT AGAIN: I still can't revert to either of my previous backups of Lineage 17.1. I would really like to be able to do this. Can anyone suggest why it will only boot to fastboot mode after a seemingly successful restore?
Thank you,
Simon.
@simes303
Don't know what the problem is, but I'd flash stock via fastboot. Then reinstall TWRP and restore LOS.
When things go wrong it's better to start from scratch rather than tinkering around and doing temporary fixes.
how is the battry life anyone?
eried1 said:
@simes303
Don't know what the problem is, but I'd flash stock via fastboot. Then reinstall TWRP and restore LOS.
When things go wrong it's better to start from scratch rather than tinkering around and doing temporary fixes.
Click to expand...
Click to collapse
Hi,
How is this different from flashing stock with TWRP?
Cheers, Si.
Used briefly but battery life seems worse, its like draining. Using 12L Lineage os and its way better.
mahmutpekkara said:
Used briefly but battery life seems worse, its like draining. Using 12L Lineage os and its way better.
Click to expand...
Click to collapse
how long does it last
laggy_boy said:
how long does it last
Click to expand...
Click to collapse
Didn't test much but its way waay noticable, you wouldn't want to use when you see the difference (didn't differ with or without gapps)
btw thx to all devs, using lineage os a12.1 and its good on battery
Battery life for me is considerably better than the Lineage 17.1 that I was using before, no question. I'd estimate almost twice the duration. I'm very happy with this ROM, thanks to all involved in developing it.
Simon.
I've actually just bought a brand new 64 Gb Lenovo P2 pretty cheap from eBay and I will definitely be flashing this Rom onto it.
Thanks again,
Simon.
Hi,
Does this ROM have USB OTG support? I can't get the phone to connect to either my external SSD drive or my bicycle helmet camera since I flashed this ROM. Both these things connected via OTG cable to my phone when I was running Lineage 17.1 and they also connect to the new P2 that I bought recently that still has stock OS. I've tried three OTG checker apps which all state that my phone is OTG compatible.
Thanks, Simon.
March 30th 2023 Release​
Changelog:
- Fetch latest Device Tree sources
- Update LOS components webview & zlib
- Sync latest LOS source
- Merge March security patch
- Many more changes
Full change log available on the bottom of this post
Download URLs: GDrive | SF
Enjoy!
simes303 said:
Hi,
Does this ROM have USB OTG support? I can't get the phone to connect to either my external SSD drive or my bicycle helmet camera since I flashed this ROM. Both these things connected via OTG cable to my phone when I was running Lineage 17.1 and they also connect to the new P2 that I bought recently that still has stock OS. I've tried three OTG checker apps which all state that my phone is OTG compatible.
Thanks, Simon.
Click to expand...
Click to collapse
Hello Simon,
Yes, it does have OTG support. IFAIK it should work correctly with both FAT32 and NTFS partition types on external storage devices.

Categories

Resources