LineageOS is a free, community built, aftermarket firmware distribution of Android 10 (Q), 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. You will need to provide your own Google Applications package (gapps). LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
DOWNLOAD ROM FROM HERE: https://sourceforge.net/projects/romz/files/lineage-17.1-20200416-UNOFFICIAL-kuntao.zip/download
WHAT'S WORKING?:
Fingerprint
Camera (and flashlight)
WiFi
Bluetooth
Telephony (Calls and Data)
Sensors
GPS
SElinux is enforcing
Issues:
Audio and video playback (will be fixed soon)
FLASHING INSTRUCTIONS:
Code:
[b]-Download the ROM and GApps of your choice
-Backup every partition from TWRP Recovery
-Make a full wipe (system, data, cache, dalvik)
-Flash LOS17.1
-Install GAPPS package
-Wipe cache!
-And at last Reboot!
[First boot will take a few minutes! Have patience]
Clean Flash is always recommended![/b]
SOURCES:
Device tree: https://github.com/LineageOS/android_device_lenovo_kuntao
Vendor: https://github.com/TheMuppets/proprietary_vendor_lenovo
Kernel: https://github.com/LineageOS/android_kernel_lenovo_msm8953
I would like to thank Priyesh anna for teaching and helping me in rom compiling. I would like to thank Swalih for testing my builds. cheers.
XDA:DevDB Information
LINEAGE OS 17.1, ROM for the Lenovo P2
Contributors
amrish7799, PriyeshP, SWALIH
ROM OS Version: Android 10
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Latest firmware
Version Information
Status: Beta
Created 2020-04-16
Last Updated 2020-04-16
Reserved
Is there screeshoot and sound panel in QS?
Andro8275 said:
Is there screeshoot and sound panel in QS?
Click to expand...
Click to collapse
There is screenshot tile and volume panel tile in quick settings. Sound tile is not present.
Does sound work, while playing YouTube, Spotify etc?
yajdintaydemir said:
Does sound work, while playing YouTube, Spotify etc?
Click to expand...
Click to collapse
Yes. Works fine.
Face unlock included ?
Does this Rom have all the extras that AICP Rom does?
Thanks.
Not booted bro format data and install not boot !
myjess said:
Does this Rom have all the extras that AICP Rom does?
Thanks.
Click to expand...
Click to collapse
Actually no. Lineage OS is pure vanilla ROM with almost no customisation other than just the basic ones
Bro rom not booted . Format data and install not booted.
Shades_of_death0 said:
Bro rom not booted . Format data and install not booted.
Click to expand...
Click to collapse
Booted fine for me. Didn't format data. Use compatible twrp. Check my screenshots. Provide logs, will look into it.
Bootloop for me too
Booted OK from TWRP wipe and adb push zips to /twrp/.
Data is f2fs.
1. Lineage 17.1 has its own recovery but how the heck do I install a magisk boot image with this lineage 17.1 recovery.
Going to try to put twrp3.3.1-1 back onto it.
2. I cannot see any device serial in adb devices or fastboot devices with the phone booted into OS. I can only see an adb device ID in Recovery. I can only see fastboot device ID in bootloader. This may be normal, I cannot remember.
I forgot to enable "Android debugging" in developer options. Now OK.
3. Why has the boot.img from this rom got a different MD5 sum from the AICP boot.img, and a different MD5 sum from the boot.img from Lineage 16.0?
L:\LenovoP2RomsEtcEtc\2020\Lineage17.1>certutil -hashfile ..\AICP\boot-20200415.img MD5
MD5 hash of ..\AICP\boot-20200415.img:
c9d965f1ecbd8496debc540f649e140c
CertUtil: -hashfile command completed successfully.
L:\LenovoP2RomsEtcEtc\2020\Lineage17.1>certutil -hashfile boot.img MD5
MD5 hash of boot.img:
c98e46c7c3d9118e78f458dce847b7a5
CertUtil: -hashfile command completed successfully.
L:\LenovoP2RomsEtcEtc\2020\Lineage17.1>certutil -hashfile ..\Lineage16.0\boot.img MD5
MD5 hash of ..\Lineage16.0\boot.img:
415ca883bc162e159ba00cc22b895d5c
CertUtil: -hashfile command completed successfully.
4. Facebook / Youtube / Whatsapp stuttering very badly.
Now working fine, only thing I did was turn on Android debuggin and do a full adb backup. Very strange.
Thanks.
Face unlock included ?
amrish7799 said:
Booted fine for me. Didn't format data. Use compatible twrp. Check my screenshots. Provide logs, will look into it.
Click to expand...
Click to collapse
will this ROM be maintaind time to time?
---------- Post added at 08:44 AM ---------- Previous post was at 08:39 AM ----------
siemens_marolikar said:
Face unlock included ?
Click to expand...
Click to collapse
no way
---------- Post added at 08:45 AM ---------- Previous post was at 08:44 AM ----------
siemens_marolikar said:
Face unlock included ?
Click to expand...
Click to collapse
even the official one havnt:silly:
myjess said:
Booted OK from TWRP wipe and adb push zips to /twrp/.
Data is f2fs.
1. Lineage 17.1 has its own recovery but how the heck do I install a magisk boot image with this lineage 17.1 recovery.
Going to try to put twrp3.3.1-1 back onto it.
2. I cannot see any device serial in adb devices or fastboot devices with the phone booted into OS. I can only see an adb device ID in Recovery. I can only see fastboot device ID in bootloader. This may be normal, I cannot remember.
I forgot to enable "Android debugging" in developer options. Now OK.
3. Why has the boot.img from this rom got a different MD5 sum from the AICP boot.img, and a different MD5 sum from the boot.img from Lineage 16.0?
L:\LenovoP2RomsEtcEtc\2020\Lineage17.1>certutil -hashfile ..\AICP\boot-20200415.img MD5
MD5 hash of ..\AICP\boot-20200415.img:
c9d965f1ecbd8496debc540f649e140c
CertUtil: -hashfile command completed successfully.
L:\LenovoP2RomsEtcEtc\2020\Lineage17.1>certutil -hashfile boot.img MD5
MD5 hash of boot.img:
c98e46c7c3d9118e78f458dce847b7a5
CertUtil: -hashfile command completed successfully.
L:\LenovoP2RomsEtcEtc\2020\Lineage17.1>certutil -hashfile ..\Lineage16.0\boot.img MD5
MD5 hash of ..\Lineage16.0\boot.img:
415ca883bc162e159ba00cc22b895d5c
CertUtil: -hashfile command completed successfully.
4. Facebook / Youtube / Whatsapp stuttering very badly.
Thanks.
Click to expand...
Click to collapse
Will try to fix video stuttering issues. Rest all good.
Media sound issue. Automatically got no audio output.
Mrinmay Medhi said:
Media sound issue. Automatically got no audio output.
Click to expand...
Click to collapse
+1
---------- Post added at 12:34 PM ---------- Previous post was at 12:33 PM ----------
amrish7799 said:
Will try to fix video stuttering issues. Rest all good.
Click to expand...
Click to collapse
+1
yt video plays at slow mo, audio not working.
markmywordz said:
+1
---------- Post added at 12:34 PM ---------- Previous post was at 12:33 PM ----------
+1
yt video plays at slow mo, audio not working.
Click to expand...
Click to collapse
+2
Related
MoKee OpenSource is based on the Google AOSP. We update our source code frequently to keep up with the latest development, and not forgetting to merge in special features of our own at the same time.
A small group of people from around the world who are interested in Android launched this project on the 12th of December 2012, and is committed to make this ROM better and better. Like most contributors of open source projects (Omni, CyanogenMod, Slim AOSPA etc), we are doing all these in our free time as our passion…
Since this project is open source, anyone interested can participate in the development (maintain new devices, contribute code etc). Newcomers are always welcomed!
Read here for developer application: http://www.mfunz.com/en/developer-application, you can host your unofficial MoKee builds on our server!
Forum:http://bbs.mfunz.com
Guide:http://bbs.mfunz.com/thread-754544-1-1.html
Statistics:http://stats.mokeedev.com
Review:http://review.mfunz.com
Download:http://download.mokeedev.com
Github:https://github.com/MoKee
Bug Tracker:http://issues.mokeedev.com/
Credits:
Google, Qualcomm, Motorola, Samsung, Lge, TI, Nvidia, Intel, Sony,
CyanogenMod, Omnirom, Slim Roms, Koush for open-sourced SuperUser
Code:
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
Found on Chinese MIUI forum.
->Download Link1<-
->Download Link2<-
LATEST VERSION 19-08-2015
Found on Chinese MIUI forum.
->Download Link<-
Not merged/Unmerged partition patch
->Download<-
Latest version 13-10-2015 can be found here:
http://www.miui.com/thread-3012343-1-1.html
Tested and works fine
for which layout type is this rom? I'm using the old one... with previous Mokee version...
New version found by the dev in Chinise Forum
I am installing this right now. Wait for Dropbox to Upload because baidu _____ and i want to help you download this faster
https://dl.dropboxusercontent.com/u/54386997/MK51.1-aries-201508181111-UNOFFICIAL.zip
NightHeron said:
New version found by the dev in Chinise Forum
I am installing this right now. Wait for Dropbox to Upload because baidu _____ and i want to help you download this faster
https://dl.dropboxusercontent.com/u/54386997/MK51.1-aries-201508181111-UNOFFICIAL.zip
Click to expand...
Click to collapse
Thanks but I already got a more recent version uploaded, see first post.
SWADED said:
Thanks but I already got a more recent version uploaded, see first post.
Click to expand...
Click to collapse
The patch is for merged partitions?Cause till now i think it was for not merged.
T3sla said:
The patch is for merged partitions?Cause till now i think it was for not merged.
Click to expand...
Click to collapse
It is for not merged, you are right.
already flash it on my mi 2s, awesome, thanks dude
Simple guide to update from not merged data-sdcard mokee official 4.4.4 to the last mokee unofficial 5.1.1 with merged partition 30/12/2015 update
1) optional - make a full nandroid backup in case anything went wrong
2)REPARTITION TO MERGED DATA
- download MIUI 5.9.2 fastboot package from official miui.com site or from here
- flash it via MiFlash, selecting "flash_all.bat" from advanced properties (the flash_all.bat is inside the miui 5.9.2 fastboot package)
-reboot from fastboot and wait (10 minutes more or less) until miui rom finally boot to the home screen
3)FLASH CUSTOM RECOVERY TWRP 2.8.7.0 FOR MERGED PARTITION
-use this guide (point 2) to flash TWRP via fastboot
4)FLASH MOKEE 5.1.1 ROM + GAPPS
-from twrp wipe data, system, caches -> flash MK51.1-aries-201511292011-UNOFFICIAL -> flash OTA-MK51.1-aries-201511292011-201512311830-UNOFFICIAL.zip -> flash gapps -> reboot
tested on MI2 32GB with mokee 4.4.4, use at your own risk
thanks to zipalign and swaded
I see the files is't same, i will try another file source, the dropbox files i got loss my imei
NightHeron said:
New version found by the dev in Chinise Forum
I am installing this right now. Wait for Dropbox to Upload because baidu _____ and i want to help you download this faster
https://dl.dropboxusercontent.com/u/54386997/MK51.1-aries-201508181111-UNOFFICIAL.zip
Click to expand...
Click to collapse
Hi, on my mi2s installed success, but imei is gone, how to fix this? i already restore EFS but if use mokee its still Unknow imei
gonewild87 said:
Simple guide to update from not merged data-sdcard mokee official 4.4.4 to the last mokee unofficial 5.1.1 with merged partition 30/12/2015 update
1) optional - make a full nandroid backup in case anything went wrong
2)REPARTITION TO MERGED DATA
- download MIUI 5.9.2 fastboot package from official miui.com site or from here
- flash it via MiFlash, selecting "flash_all.bat" from advanced properties (the flash_all.bat is inside the miui 5.9.2 fastboot package)
-reboot from fastboot and wait (10 minutes more or less) until miui rom finally boot to the home screen
3)FLASH CUSTOM RECOVERY TWRP 2.8.7.0 FOR MERGED PARTITION
-use this guide (point 2) to flash TWRP via fastboot
4)FLASH MOKEE 5.1.1 ROM + GAPPS
-from twrp wipe data, system, caches -> flash MK51.1-aries-201511292011-UNOFFICIAL -> flash OTA-MK51.1-aries-201511292011-201512311830-UNOFFICIAL.zip -> flash gapps -> reboot
tested on MI2 32GB with mokee 4.4.4, use at your own risk
thanks to zipalign and swaded
Click to expand...
Click to collapse
:fingers-crossed: it's work good for my aries, just one my problem, the diel USSD Code is Chines languange, how to fix this i already change the locale, change font, but still chines :crying:
https://dl.twrp.me/s2/
allrockedout said:
https://dl.twrp.me/s2/twrp-3.2.0-0-s2.img.html
Click to expand...
Click to collapse
What are the changes, oh wait, can read here https://twrp.me/site/update/2017/12/01/twrp-3.2.0-0-released.html :
What's new in 3.2.0-0:
Allow restoring adb backups in the TWRP GUI (bigbiff)
Fix gzip backup error in adb backups (bigbiff)
Fix a bug in TWRP's backup routines that occasionally corrupted backup files (nkk71)
Better support for installing Android 8.0 based zips due to legacy props (nkk71)
Support vold decrypt with keymaster 3.0 in 8.0 firmwares (nkk71)
Decrypt of synthetic passwords for Pixel 2 (Dees_Troy)
Support newer ext4 FBE policies for backup and restore in libtar (Dees_Troy)
v2 fstab support (Dees_Troy)
Bring TWRP forward to android 8.0 AOSP base (Dees_Troy)
Various other minor bugfixes and tweaks
Click to expand...
Click to collapse
Anyone tried yet?
Just try it after see this thread and notice that does not boot into recovery, stay in the screen with LeEco logo before it.
EDIT: Downloaded and flashed 3.1.1.1 and still does not boot into recovery... HELP!
EDIT2: Turn out the download from twrp app went bad and the files were corrupted, download it from PC and now its ok...
mdio said:
Just try it after see this thread and notice that does not boot into recovery, stay in the screen with LeEco logo before it.
EDIT: Downloaded and flashed 3.1.1.1 and still does not boot into recovery... HELP!
EDIT2: Turn out the download from twrp app went bad and the files were corrupted, download it from PC and now its ok...
Click to expand...
Click to collapse
So you confirm TWRP 3.2.1-0 works for LE S3 X522 ?
jithin6g said:
So you confirm TWRP 3.2.1-0 works for LE S3 X522 ?
Click to expand...
Click to collapse
I'm on le s3 working fine
There is a newer TWRP out now: https://dl.twrp.me/s2/twrp-3.2.1-0-s2.img.html
What's new in 3.2.1-0:
* minui fixes (cryptomilk)
* Better android-8.0 compatibility in ROM trees (Dees_Troy)
* Fix missing library in android-8.0 (nkk71)
* Fix inconsistent SDCard naming (DevUt)
* Default to TWRP restore instead of adb backup restore to fix restore on fresh TWRP boot (jlask)
Andy_04 said:
There is a newer TWRP out now: https://dl.twrp.me/s2/twrp-3.2.1-0-s2.img.html
What's new in 3.2.1-0:
* minui fixes (cryptomilk)
* Better android-8.0 compatibility in ROM trees (Dees_Troy)
* Fix missing library in android-8.0 (nkk71)
* Fix inconsistent SDCard naming (DevUt)
* Default to TWRP restore instead of adb backup restore to fix restore on fresh TWRP boot (jlask)
Click to expand...
Click to collapse
is only for snapdragon or mediatek also?
jithin6g said:
So you confirm TWRP 3.2.1-0 works for LE S3 X522 ?
Click to expand...
Click to collapse
Did not try 3.2.1.0 yet, but 3.2.0.0 is running ok.
---------- Post added at 08:41 PM ---------- Previous post was at 08:40 PM ----------
Andy_04 said:
There is a newer TWRP out now: https://dl.twrp.me/s2/twrp-3.2.1-0-s2.img.html
What's new in 3.2.1-0:
* minui fixes (cryptomilk)
* Better android-8.0 compatibility in ROM trees (Dees_Troy)
* Fix missing library in android-8.0 (nkk71)
* Fix inconsistent SDCard naming (DevUt)
* Default to TWRP restore instead of adb backup restore to fix restore on fresh TWRP boot (jlask)
Click to expand...
Click to collapse
That is nice... but is there any Android 8 rom for S2 already???
---------- Post added at 08:56 PM ---------- Previous post was at 08:41 PM ----------
EDIT: 3.2.1.0 Ok and running.
dziubson said:
is only for snapdragon or mediatek also?
Click to expand...
Click to collapse
This ist only for Snapdradon (the X52x Models)
---------- Post added at 06:16 AM ---------- Previous post was at 06:13 AM ----------
I installed it via TWRP app (RR-OS 5.8.5) on my X527 and it works very good
Does twrp 3.2.1 word on leeco le 2 x620 on eui 5.9.028s?
Andy_04 said:
This ist only for Snapdradon (the X52x Models)
Click to expand...
Click to collapse
Sukkel21 said:
Does twrp 3.2.1 word on leeco le 2 x620 on eui 5.9.028s?
Click to expand...
Click to collapse
If you can write, I assume you can read, can't you?
It doesn’t work on eui 5.9.028s I tried flashing no Luck, I tried booting without flashing didn’t work either. And when I try to boot into it it changes my oem unlocking from true to false so I don’t know how to install it.
What is this?
- sGSI of ZUI 10.0/ 5.0 from Lenovo Z5pro/Z5, based on Android 8.1.0, June 1,2018 security patch.
Since this was requested in some comments, I flashed it and found working for our device flawlessly, with some bugs.
Features?
-All features of ZUI 4 + Soft Charge, gestures, multi space ( dual apps ) etc. Split Screen is also available.
How to flash?
ZUI 10 :
1. Download the flashable zip from the links.
2. Boot to twrp, and wipe dalvik, cache, data, system and vendor.
3. Flash the zip.
4. Reboot.
ZUI 5:
Method 1 : (Recommended)
- 1. Download any treble based 8.1.x rom and ZUI5.0-sGSI.zip (link below).
[Please use MIUI 10 8.11.1 by Narshi Shukla as base ROM, as it seems it's Vendor is most compatible.]
2. Extract the zip in your storage. You will get three files ( two flashable zips and one folder "sGSI.....". [Folder name might differ, there will be only one folder, so no worries])
3. Boot into recovery and take a backup.
4. Clean flash treble based Oreo ROM that you downloaded.
5. From your twrp, use file manager to move " sGSI...." folder to backup folder of Twrp.
6. Mount system and vendor and wipe cache/delvik, data and system.
( Don't wipe firmware and Vendor )
7. Goto restore in your twrp and restore the system from "sGSI....." folder.
8. Flash the remaining two zips.
9. Flash magisk if needed.
10. Wipe cache/delvik and reboot. Done.
Method 2 : https://forum.xda-developers.com/showpost.php?p=78389810&postcount=320
(You need treble based twrp, search if you don't already have).
After following all these steps, if your phone is stuck in Lenovo powered by android screen for long, then force reboot the phone and it will boot up to system.
What works?
-Here:
Call,SMS, VOLTE, Data, play store, Utouch, Fingerprint , Navigation, Double touch to wake, GCAM, Face Unlock, Hotspot, Banking apps, nearly everything.
What doesn't work?
- ROM specific. Bugs depend upon the treble ROM that you used as base. In some ROM, system sounds does not work. In MiUI 10, video recording might not work. Game Mode has some issues with global apps.
*FOR VIDEO RECORDING - see this : https://forum.xda-developers.com/showpost.php?p=78219358&postcount=93 ****
*Update GPU drivers for VULKAN support. Link in the links section.***
Performance?
- Better than ZUI 4, smooth as butter, no stutter playing games like PUBG, notifications on time, decent SOT.
Can it be used as daily driver?
- Yes, if you can live with some Chinese texts in certain apps.
Any other thing?
- Because the ROM is ported from Z5 which has a notch, total area of the notification bar cannot be used. To see things like real time network speed and battery "percentage" you have to pull down the notification bar.
What should I do first after booting the device?
- Install play store from App center. Install magisk to remove bloat wares. Install any music app, since there is none. This will make the system optimal for us.
Also, Turn "True Full Screen Mode" ON in display settings for full screen in Apps.
Install Magisk and download and install "SafteyPatch V2" within Magisk to pass safetynet and hide banking apps in magisk hide to use them.
Open security app and give all important permissions to the apps you use, including system apps. Also include them in autorun/whitelist section.
Links?
-Here
ZUI 10
https://drive.google.com/open?id=17lyWnAl0Kjkv5S89wdtw7HglF2072zP5
ZUI 5
Mega link :
https://mega.nz/#!FyxSiI7Y!iZmmVufR6pipX3mwv_-I3HqI714YAMJN1a2zIysinmc
Gdrive link:
https://drive.google.com/open?id=1F_Ou6x2bj26hhdffw45uo4r9qlJuaDb5
MiUi 10 8.11.1 Narshi Shukla - Full Rom
https://androidfilehost.com/?fid=11410932744536996684
MIUI 10 8.11.1 Narshi Shukla - Vendor for twrp recovery: @(THIS VENDOR isnt compatible with all roms, if facing random reboots, use the complete MIUI 10 ROM for the Gsi)
https://drive.google.com/drive/u/0/folders/15QHEUfLMagMV9jZTmlUHa4hkhkNTF-RC
Working GCAM link :
https://www.celsoazevedo.com/files/android/google-camera/f/MGC_6.1.021_FINAL_V1a_A8.1+.apk
VULKAN enabled open GL 3.2 driver link :
https://drive.google.com/folderview?id=11_atz5CDK9bHG4K_ME2LSRFFnxxKqWw2
Credits:
Not my work, I am just sharing it since I found it working.
All credits goes to this Xiaomi thread and bugrevealingbme.
https://*************/threads/zui-5-0-a-only-treble-rom.226/
******************************** FLASHING ISSUE ******************
While flashing this ROM, try to follow the guide above as strictly as possible. Use the ROM that is recommended.
If you are facing bootloop, download the vendor that is provided and restore it in twrp and then flash patch 1 and 2.
Also remember, during each and every step, your TWRP should have system and Vendor mounted. Check after every step.
Your phone might reboot once or twice during first boot, which is not an issue.
How to know if you flashed it correctly?
-If your phone boots into the system with "Lenovo bootanimation" , you flashed it correctly.
If your phone is stuck in "Lenovo - powered by android" splash image for more than 5 minutes, you got something wrong.
*********************************************************************
Screenshots attached :
what about gcam nd notification bug? and one more doubt, can we flash it over treble pie ROM?
I have one question. If i install a sgsi rom can i back to trenle, non-treble rom just with a simple flash method?
muujeeb said:
what about gcam nd notification bug? and one more doubt, can we flash it over treble pie ROM?
Click to expand...
Click to collapse
gcamera is working on redmi note 5 pro. should work also here.
muujeeb said:
what about gcam nd notification bug? and one more doubt, can we flash it over treble pie ROM?
Click to expand...
Click to collapse
GCAM is working.
Notification bug is not there. Only sometimes, it seems that we get late notification.
You have to flash it over Oreo because the GSI is Oreo based. Flashing over pie should work as well, since treble ROM is required. Take a backup of your system so you can restore easily, if you face any issue.
nonamesry said:
I have one question. If i install a sgsi rom can i back to trenle, non-treble rom just with a simple flash method?
Click to expand...
Click to collapse
Yes, you can get back to the ROM you want with simple flash, no problem.
Custom kernel flashable?
ashwinonm said:
Custom kernel flashable?
Click to expand...
Click to collapse
Haven't tested, but should be flashable.
Edit : Custom kernel might brick the device. Will test and update.
Donot flash custom kernel, it causes self restart of device.
Note: Moxie kernels can be flashed, you should flash patch2 after flashing kernels. But, MIUI 10 comes with moxie R5.1 so no use flashing Moxie again.
link not working
Wow it's so beautiful!
I used Arrow OS 8.1 but it got stuck in bootloop and does'nt boot at all.. I followed all the steps accordingly but it did not boot up even after i kept my phone overnight to let it boot. I don't know where i did wrong.
muujeeb said:
I used Arrow OS 8.1 but it got stuck in bootloop and does'nt boot at all.. I followed all the steps accordingly but it did not boot up even after i kept my phone overnight to let it boot. I don't know where i did wrong.
Click to expand...
Click to collapse
Use MIUI 10 port of Narshi Shukla latest build. It works.
May be Arrow OS cannot be used.
You can also try using Vendor of MIUI 10 once. Restore this vendor and the system image of ZUI.
Here is the vendor:
https://drive.google.com/drive/mobile/folders/15QHEUfLMagMV9jZTmlUHa4hkhkNTF-RC?usp=drive_open
kany1 said:
link not working
Click to expand...
Click to collapse
Link is working fine.
jebish7 said:
Link is working fine.
Click to expand...
Click to collapse
yes it is working with mega app
I used crdroid 8.1 and got stuck in bootloop. then I try restored the vendor but could not flash the patch 2
---------- Post added at 01:19 PM ---------- Previous post was at 01:13 PM ----------
ok i try to flash it again and boot successflly
marclevine said:
I used crdroid 8.1 and got stuck in bootloop. then I try restored the vendor but could not flash the patch 2
Click to expand...
Click to collapse
I think only MIUI 10 rom works flawlessly for this GSI. I will update the main page details and ask to use MIUI 10 only.
You couldnot flash patch 2 because it requires vendor, and may be your vendor is now messed up.
So use MIUI 10 port, it works without any issue.
marclevine said:
I used crdroid 8.1 and got stuck in bootloop. then I try restored the vendor but could not flash the patch 2
---------- Post added at 01:19 PM ---------- Previous post was at 01:13 PM ----------
ok i try to flash it again and boot successflly
Click to expand...
Click to collapse
Glad To hear.
So in whatever rom I am in Oreo , I can use that firmware if I use vendor only from your backup? And shouldn't wipe it?
ashwinonm said:
So in whatever rom I am in Oreo , I can use that firmware if I use vendor only from your backup? And shouldn't wipe it?
Click to expand...
Click to collapse
Well, that's how some people got this working, so yes, it's working that way as well. ( Your ROM should be treble based though )
I will attach the "Vendor" file in the main post as well, so other members can use it too.
custom kernel possible,mine running in moxie
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.
If you are coming from LineageOS 15.1 with f2fs userdata, you need to format the userdata partition! Read the second post for more information.
As always, make sure to backup before installing this ROM.
More detailed instructions at:
Install LineageOS on kuntao
Download link:
LineageOS Downloads
Recommended Google Apps package:
Open GApps (choose the variant you want. Recommended nano package)
Required TWRP recovery
twrp-3.2.3-20190209-kuntao.img
Official root addon
LineageOS Extras
Changelog:
Changes for kuntao
Bug reports:
How to submit a bug report
LineageOS GitLab
Donate to support development:
Donate via PayPal to mikeioannina
Donate via PayPal to LineageOS
XDA:DevDB Information
Official LineageOS 16.0 for P2, ROM for the Lenovo P2
Contributors
mikeioannina, highwaystar_ru
Source Code: https://github.com/LineageOS
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.x
ROM Firmware Required: Any version of stock 6.0. Recommended: P2a42_S251_171107_ROW
Based On: LineageOS
Version Information
Status: Nightly
Created 2019-04-13
Last Updated 2019-06-17
Upgrade instructions from LineageOS 15.1
Lenovo used a very old version of f2fs which is incompatible with latest f2fs version of 3.18 kernel. In order to keep the device updated with the latest features, it was necessary to upgrade f2fs with the downside of existing users need to format the userdata partition. If you want to keep your userdata, follow these steps. Keep in mind any apps using the keystore will be broken and you will need to clear their app data and set them up from scratch. If you used ext4 for userdata, you can simply upgrade without any breakage.
If you want to keep and migrate your 15.1 data and internal storage contents (only on incoming official builds!):
1. backup userdata in your current TWRP and take an internal storage backup on your PC.
2. reboot to bootloader
3. fastboot flash recovery twrp-3.2.3-20190209-kuntao.img
4. reboot to recovery by holding vol up + vol down + home + power buttons
5. main menu -> wipe -> format data
6. main menu -> reboot -> reboot recovery
7. flash lineage zip (and gapps/whatever else you want)
8. restore userdata backup and internal storage backup
9. delete /data/system/locksettings.db, you will have to set your lockscreen protection again when it boots
If you want a completely clean install just skip steps 1, 8 and 9.
I tested this process and it worked coming from lineage-15.1 or stock ROM.
Yeah! Thaaaaaanks Mike!
Thanks dude . Love your work
Thanks a lot mike!
AWESOME! Thank you.
I can't find the official Lineage OS 16 file?
tanzeel.ahmed1306 said:
I can't find the official Lineage OS 16 file?
Click to expand...
Click to collapse
Incoming !!!
@mikeioannina
* deleted
M too cant find file Lineage OS 16
tanzeel.ahmed1306 said:
I can't find the official Lineage OS 16 file?
Click to expand...
Click to collapse
M too cant find file Lineage OS 16
Los 16.0 is replacing 15.1 so build will probably come tomorrow. I think.
At 8:00 UCT
So one hour and a half.
https://www.lineageoslog.com/build
https://www.lineageoslog.com/16.0/kuntao
Sorry! Unfortunately I was wrong.
So if I already have ext4 data partition I can simply install the new 16.0 update without having to migrate the data etc?
Do I need the new recovery too?
Normally the build of the images starts on sunday 8utc am, so 10am my time. we'll see ^^ thx mike!
@philje123 i will test it out, as soon as the rom is available. i am too on ext4 already, i am using the new twrp since february, even with the 15.1 build. i will try to simply upgrade from 15.1 to 16, so i don't have to reinstall all apps. i will write, if it was working for me.
philje123 said:
So if I already have ext4 data partition I can simply install the new 16.0 update without having to migrate the data etc?
Do I need the new recovery too?
Click to expand...
Click to collapse
Yes, you need new recovery, but flashing new recovery do NOT wipe your data. It contain a newest format of f2fs format. On TWRP page you have a guide, how to flash it step by step on your phone without meet do plug your phone to PC.
Thanks Mike waiting for awesome
Should we expect a build this sunday at 10 am european time ?
robbedoes007 said:
Should we expect a build this sunday at 10 am european time ?
Click to expand...
Click to collapse
I thing about 1 pm CEST (European Time)
I remember last year on presentation 15.1 it took a couple of days before we could download after announcement.
Mikes work is awesome. But his timing
But anyway, I'm looking forward for this rom and I thank all the developers :good:
i mean it depends, when the build for the 16 roms is starting everyday, but according to this site https://www.lineageoslog.com/build/scheduler we will get nightly builds, instead of weekly ones.
so that means, daily snapshots, like we had with 15.1 from july till november, before we only got one update a week. but no matter when, i am just happy that 16 is finally here ;D
no matter if we have to wait another day or not for the first build. but still - it's just amazing how much love the p2 gets. it is still one of the best, if not THE best device i've ever had. perfect performance for daily usage, even with slight gaming and i only need to charge my device once or twice a week. that's incredible! my device is now over 2 years old and my battery still lasts 4~6 days with one charge <3 best phone ever created hahahaha - and thx to people like mike, it is up to date too =) i hate lenovo as brand, when it comes to software updates, but the hardware is awesome, for that price tag...
Hello,
I know that ROM developement on redmi 7a has been extreemly slow, but we all know that redmi 7a is a treble enabled device and therefore we can install every android GSI as long as it is ARM32-BINDER64-AB, yes and i wouldn't explain it here you can read it over here here.
So i thought that i should give you guys a little guide on how to install GSIs and custom ROMs and yeah with volte fix too
NOTE - I AM NOT RESPNSIBLE IF YOUR DEVICE GETS BRICKED OR THERMONUCLEAR WAR TAKES PLACE, YOUR WARRANTY IS VOID FROM THIS STEP ON, I AM NOT RESPONSIBLE IF YOUR DEVICE GETS BRICKED MAKE SURE YOU HAVE MOVED YOUR DOWNLOADED ROMS AND GAPPS TO A PC OR A SD CARD I AM NOT RESPONSIBLE FOR ANYTHING
1] The very important first step is to unlock your bootloader.
2]The second step is to patch your boot image (if you want to root it with magisk)
3] Install the custom recovery of your choice
Download the TWRP file from here
you also can install TWRP forks like
PICTHBLACK RECOVERY PROJECT or PBRP from here
SHRP RECOVERY from here (i wouldn't recommend this one if you are flashing this for the first time)
If you have your device drivers installed but you dont have adb installed then please download this file and extract it to a suitable folder where your downloaded recovery is extracted and run cmd-here and follow these steps given below
Code:
fastboot devices
this will show you if your device is connected or not.
Code:
fastboot flash recovery (your recovery name.img)
Code:
fastboot reboot
you have to keep pressing you volume increase button to reboot to recovery
4] You have to wipe DATA first then, reboot to recovery and go to mount select system (if it's unchecked)
5] Go to WIPE -> ADVANCED WIPE -> Select SYSTEM - DALVIK CACHE - CACHE - INTERNAL STORAGE
6] The list for the available GSIs or ROMs is ----
1) LineageOS thanks to ExpressLuke (GSI) (You might have to downgrade your miui to be able to boot)
2) HavocOS thanks to Skulshady (GSI) (Boots just fine with any version of miui volte patch is needed)
3) Mokee thanks to GuaiYiHu (ROM) (No worries about anything)
4) AOSP Special thanks to Phhusson (GSI) (Boots just fine without any hiccups volte patch is needed)
5) CAOS by Erenmitein (GSI) (Not tested)
6) CrDroid By Erenmitein (GSI) (tested needs the bolte fix patch. please follow the steps given below)
7] Move your GSI img (extract the .xz file) the extension is going to be .img and will not visible in TWRP or it's forks unless you select the INSTALL IMAGE option in the FLASH section and GAPPs
8] Flash your GSI as a System Image
9] Reboot to recovery again and flash your GAPPS ignore if it says no OS installed when rebooting to recovery
10] The fix for VOLTE is here thanks to Khushraj Rathod
you just have to flash it from TWRP or its forks
11] The first reboot will take some time and voila your GSI has been installed (flashed).
12] For Mokee, personaly i love Mokee rom with its boot animation, you can just flash your zip through twrp with gapps.
Thanks @Faithof_Eden for your detailed instructions. So far I always failed with the already existing manuals of other authors.
One question: What if I don't want to root the device at all, neither with Magisk nor otherwise?
You wrote: "2]The second step is to patch your boot image (if you want to root it with magisk)"
Is it then necessary to carry out step number 2 at all?
kra_ppo said:
Thanks @Faithof_Eden for your detailed instructions. So far I always failed with the already existing manuals of other authors.
One question: What if I don't want to root the device at all, neither with Magisk nor otherwise?
You wrote: "2]The second step is to patch your boot image (if you want to root it with magisk)"
Is it then necessary to carry out step number 2 at all?
Click to expand...
Click to collapse
No.
A problem has occurred during flashing:
After I flashed the AOSP image (system-quack-arm32_binder64-ab-vanilla.img) using TWRP and want to restart the recovery to install GAPPS, the Redmi 7a goes directly into fastboot-mode.
No chance to get into TWRP with the Volume-up button.
Even reflashing Recovery does not help. I've done all wiping in TWRP as indicated.
Havoc (an Mokee - but I dont like it) was finally successfull, but only by formating Data and not to wipe internal Storage....
kra_ppo said:
A problem has occurred during flashing:
After I flashed the AOSP image (system-quack-arm32_binder64-ab-vanilla.img) using TWRP and want to restart the recovery to install GAPPS, the Redmi 7a goes directly into fastboot-mode.
No chance to get into TWRP with the Volume-up button.
Even reflashing Recovery does not help. I've done all wiping in TWRP as indicated.
Click to expand...
Click to collapse
Flash vbmeta
Moke os not working speaker áudio
---------- Post added at 09:27 PM ---------- Previous post was at 09:26 PM ----------
Moke os calls not work
how to get back to stock ROM ?
idcamper said:
Moke os not working speaker áudio
---------- Post added at 09:27 PM ---------- Previous post was at 09:26 PM ----------
Moke os calls not work
Click to expand...
Click to collapse
You flashed floor miui 10.0.2.5.?
can't i do this with twrp? Tutorial ?
Flammenschwert1337 said:
Flash vbmeta
Click to expand...
Click to collapse
Did you find solution?
lslayer4231 said:
Did you find solution?
Click to expand...
Click to collapse
Start with miui 10.0.2.5.
Then go on.
My phone bootloops to redmi logo and recovery after flashing, any help from this?
After installing latest havoc 3.7 gsi the call recording feature not working though normal sound recording works... Any fix?
Hey, guys!
Havoc OS GSI is selinux permissive or enforced?
Is it possible to go back to stock rom by doing a backup using twrp?
I'm sorry if I'm being dumb, but as you already noticed, I'm newbie.
MEMO#22 said:
My phone bootloops to redmi logo and recovery after flashing, any help from this?
Click to expand...
Click to collapse
Switch back to miui 10 global version and install twrp
Has anyone else got media playout over bluetooth OK and if so, which GSI or ROM and which base firmware, please? It does not work for me with AOSP on latest EU firmware. Only calls go to BT.