LineageOS 18.1 [R] [11] (Unofficial) Mi Pad 4 Plus (clover) - Xiaomi Mi Pad 4 Plus ROMs, Kernels, Recoveries, &

LineageOS 18.1, see this link
Installation instructions :
- Download the zip(s).
- Install latest TWRP for clover
- Perform a backup of your current ROM (optional)
- Wipe dalvik/cache (upgrade from lineageos 18.1) and wipe system/data if upgrade from other rom.
- Flash ROM.
- Flash GApps (NikGApps is recommended) is a must.
- Optional: Flash latest Magisk for root.
Everything should work.
Source :
sdm660

Hello !
No SD card.
Clean installation.
NikGapps-core-arm64
---------- Post added at 07:44 PM ---------- Previous post was at 07:43 PM ----------

Thank you for the LOS R. Very good rom.
Clean install with Nikgapps omni, found download in Chrome to sd card showing "download pending" and chrome will force close.

Awesome! Thanks!

rchoi999 said:
Thank you for the LOS R. Very good rom.
Clean install with Nikgapps omni, found download in Chrome to sd card showing "download pending" and chrome will force close.
Click to expand...
Click to collapse
I didn't use sdcard...it would be help if log is available...

-----> Have New Update 2020/10/19 I didn't install it, don't know the difference

addro said:
-----> Have New Update 2020/10/19 I didn't install it, don't know the difference
Click to expand...
Click to collapse
Some update in lineageos qcom repo....

Thanks a lot for working on this. I tried the following versions, but they all bootloop (bootsplash, lockscreen visible for a few seconds, then reboots):
lineage-18.0-20201017-UNOFFICIAL-clover_rev0.zip
lineage-18.0-20201018-UNOFFICIAL-clover.zip
lineage-18.0-20201019-UNOFFICIAL-clover.zip
This is with a WiFI-only miPad 4, latest TWRP, complete wipe of everything first.

sb56637 said:
Thanks a lot for working on this. I tried the following versions, but they all bootloop (bootsplash, lockscreen visible for a few seconds, then reboots):
lineage-18.0-20201017-UNOFFICIAL-clover_rev0.zip
lineage-18.0-20201018-UNOFFICIAL-clover.zip
lineage-18.0-20201019-UNOFFICIAL-clover.zip
This is with a WiFI-only miPad 4, latest TWRP, complete wipe of everything first.
Click to expand...
Click to collapse
@sabar_op, @sb56637, @amityg
Please keep in mind that there are many reports of bootloops etc using TWRP with Android 11.
TWRP officially supports all devices running Android up to 10, except devices LAUNCHED with 10 or later (having dynamic/logical partitions). There are no versions officially supporting devices running Android 11 to date:
TWRP 3.4.0 does not yet bring support for dynamic/logical partitions, which is required to support devices that launch with Android 10. It does, however, fix support for legacy devices that upgraded to Android 10, but retain the old partition scheme.
Click to expand...
Click to collapse
https://www.xda-developers.com/twrp...s-support-legacy-devices-upgraded-android-10/
Latest TWRP 3.4.0 arrived in June 2020 w/ support for devices upgraded to Android 10 (only). There's been no further versions. See here:
https://forum.xda-developers.com/ap...v1-universal-systemless-t3432382/post83725859
The solution for most using custom Android 11 based ROMs has been to KEEP STOCK Recovery and use ADB fastboot boot TWRP (NOT flash) command from PC when needing custom recovery functions to flash ROMs etc. This seems to work for most despite having no TWRP fully supporting Android 11.
Nb. To achieve root with MagiskSU, this method is probably even more critical as users are reporting bootloops with TWRP custom recovery (flashed) and Android 11 when flashing Magisk pretty much accross the board.
Nb2. Achieving root with MagiskSU can alternatively be done without custom recovery by flashing Magisk Manager patched boot.img (extracted from ROM) using ADB fastboot flash image command from PC. This may be a less fraught method.
I'm still on LOS 17.1, but the above outlines the approach I intend to take / try soon.
Hope it helps, PW

sb56637 said:
Thanks a lot for working on this. I tried the following versions, but they all bootloop (bootsplash, lockscreen visible for a few seconds, then reboots):
lineage-18.0-20201017-UNOFFICIAL-clover_rev0.zip
lineage-18.0-20201018-UNOFFICIAL-clover.zip
lineage-18.0-20201019-UNOFFICIAL-clover.zip
This is with a WiFI-only miPad 4, latest TWRP, complete wipe of everything first.
Click to expand...
Click to collapse
Can you take the log?
Never try for mipad 4 wifi only, I use mipad 4 wifi-lte, twrp 3.4.0 with previous los17.1 installed and no issue so far...

I tried your room on my mi pad 4 wifi with twrp 3.4.0 no installation problem.

Running well on mi pad 4 plus. Really good apart from no sd card. Trying to upload logs.

Running well on mi pad 4 plus. Really good apart from no sd card. Trying to upload logs.[/QUOTE]
View attachment 5123311

idcom said:
Running well on mi pad 4 plus. Really good apart from no sd card. Trying to upload logs.
Click to expand...
Click to collapse
View attachment 5123311[/QUOTE]
Can't open the attachment...send me a pm for the log link.
A quick question : is sdcard not showing in setting/storage?

Enry44 said:
I tried your room on my mi pad 4 wifi with twrp 3.4.0 no installation problem.
Click to expand...
Click to collapse
Thanks for confirmation...it means no problem with mipad 4 wifi only... :good::good::good:

sabar_op Sure, where can I find the log?

Can't open the attachment...send me a pm for the log link.
A quick question : is sdcard not showing in setting/storage?[/QUOTE]
Have PMed you. Settings-≥Storage shows Portable but corrupted. When I format nothing changes.

sb56637 said:
Thanks a lot for working on this. I tried the following versions, but they all bootloop (bootsplash, lockscreen visible for a few seconds, then reboots):
lineage-18.0-20201017-UNOFFICIAL-clover_rev0.zip
lineage-18.0-20201018-UNOFFICIAL-clover.zip
lineage-18.0-20201019-UNOFFICIAL-clover.zip
This is with a WiFI-only miPad 4, latest TWRP, complete wipe of everything first.
Click to expand...
Click to collapse
This is probably because didn't install a *Gapps package.

sabar_op said:
Can you take the log?
Never try for mipad 4 wifi only, I use mipad 4 wifi-lte, twrp 3.4.0 with previous los17.1 installed and no issue so far...
Click to expand...
Click to collapse
Alex Kane said:
This is probably because didn't install a *Gapps package.
Click to expand...
Click to collapse
Hmm, not sure, LineageOS 17.1 works fine on this tablet without Gapps.

sb56637 said:
Hmm, not sure, LineageOS 17.1 works fine on this tablet without Gapps.
Click to expand...
Click to collapse
Yeah, but apparently LOS 18.0 beta doesn't.
I tried LOS 18.0 (beta) without gapps first and it would bootloop after reaching the home-screen. Flashing gapps would solve the issue (for me) but I don't use gapps so ... I went back to LOS 17.1.
I also experienced the issue with the sdcard not being properly detected.

Related

[ROM][5.1.1] CM12.1 Official Nightlies for Find 7A/S

Hello all
Official CM 12.1 nightlies based on Android Lollipop 5.1.1 for Find 7A/S have been officially released effective 22nd April 2015. Its time to thank the entire CyanogenMod Team and @[U]jajb[/U] for their efforts in the development and encourage them to keep supporting us the same way in the future.
Let the flashing go on!!!!:highfive:
Nightly Downloads
CM12.1 Find 7A
http://download.cyanogenmod.org/?device=find7
CM12.1 Find 7S (QHD)
http://download.cyanogenmod.org/?device=find7s
5.1 Minimal Gapps (for a light and blazzing fast experience):highfive:
https://www.androidfilehost.com/?fid=95916177934550851
Installation Instructions
Coming from 5.0 or less ROMS
Download cm-12.1-xxxxxxxx-NIGHTLY-find7x.zip to your sdcard
Boot into Recovery
Wipe data, cache & dalvik cache
Flash cm-12.1-xxxxxxxx-NIGHTLY-find7x.zip from sdcard
Flash 5.1 Minimal GApps.zip from sdcard
Reboot:highfive:
Coming from previous CM 12.1 build
Wipe cache & dalvik cache
Flash cm-12.1-xxxxxxxx-NIGHTLY-find7x.zip from sdcard
Reboot:highfive:
Somebody successfully flashed it ? It works ?
raber111 said:
Somebody successfully flashed it ? It works ?
Click to expand...
Click to collapse
It doesn't work. http://forum.xda-developers.com/showpost.php?p=58255547&postcount=397
I tried to flash the last CM11 build and I'm still stucked there.
Anyone tried 20150119 build yet? is it working??
CyanPile said:
Anyone tried 20150119 build yet? is it working??
Click to expand...
Click to collapse
It seems so, but wifi is terribly slow.
It's going to be announced soon in CM's blog, but find7a and find7s are split now and get separate builds. You need to flash "find7" on find7a devices and "find7s" on find7s qhd devices. You should update the recovery too, but I think there are no recovery images available yet. I might provide some if nobody else does it.
I successfully flashed cm 12 1901 build . WiFi works normally. Fonts and icons too small
on 2.0.4
Can we flash this on color os 2.0.4 version without any issues or have to downgrade to 1.2.7
sheraz1015 said:
Can we flash this on color os 2.0.4 version without any issues or have to downgrade to 1.2.7
Click to expand...
Click to collapse
You will have to flash it over 1.2.x Color OS. I flashed 19 build over 1.2.7.
Installed without an issue.
For QHD use Find 7s version.
mikeioannina said:
It's going to be announced soon in CM's blog, but find7a and find7s are split now and get separate builds. You need to flash "find7" on find7a devices and "find7s" on find7s qhd devices. You should update the recovery too, but I think there are no recovery images available yet. I might provide some if nobody else does it.
Click to expand...
Click to collapse
Thank for your
help and shall flash it.
Its there any way to backup imei of oppo find 7
ganeshbiyer said:
You will have to flash it over 1.2.x Color OS. I flashed 19 build over 1.2.7.
Installed without an issue.
For QHD use Find 7s version.
Click to expand...
Click to collapse
Sent from my LG-D802 using XDA Premium 4 mobile app
You can always use tantrums recovery flasher...they recently updated to v10.....has all the latest recoveries
Anyone having problems when using unified partition layout? After I flashed the ROM the phone just tells me that there's an encryption error and I have to wipe data. I wiped data and still the same error. When I went back to previous ROM I'm using everything else is fine, except with the proximity sensor bug. Cheers
darthbadar said:
Anyone having problems when using unified partition layout? After I flashed the ROM the phone just tells me that there's an encryption error and I have to wipe data. I wiped data and still the same error. When I went back to previous ROM I'm using everything else is fine, except with the proximity sensor bug. Cheers
Click to expand...
Click to collapse
De-unify first, then flash. You need to have to revert back to 1.2.x.
Flash Open TWRP and then flash CM12 Nightlies. COs 1.2.x and CM12 do not support Unification.
ganeshbiyer said:
De-unify first, then flash. You need to have to revert back to 1.2.x.
Flash Open TWRP and then flash CM12 Nightlies. COs 1.2.x and CM12 do not support Unification.
Click to expand...
Click to collapse
Soo, there's no way I'm using CM12 Nightlies with unified storage? Thanks for answering man. :highfive:
Changelog ?
changelog here http://www.cmxlog.com/12/find7/
and here http://www.cmxlog.com/12/find7s/
Chrome
Is the only way to switch between tabs the recent apps thingy? I mean I don't habe a problem but still kinda awkward not knowing where the tab went. BTW I got twrp 2.8.4 and there's always this horizontal line where the display shifts. It's like these lines on old videos that walk through the picture. Trying my best on English (I'm German )
alex1.salge said:
Is the only way to switch between tabs the recent apps thingy? I mean I don't habe a problem but still kinda awkward not knowing where the tab went. BTW I got twrp 2.8.4 and there's always this horizontal line where the display shifts. It's like these lines on old videos that walk through the picture. Trying my best on English (I'm German )
Click to expand...
Click to collapse
Regarding the line in recovery, use Nameless TWRP recovery from HERE.
I have not tried the latest TWRP Open Recovery 2.8.4 for Find7, but with Nameless TWRP Recovery, I am able to use OTG in recovery. This allows me to take backups into 32gb usb drive and restore from there.
Custom Ringtones
Hello Just flashed to build 2015/01/21 and I noticed that I was unable to change my ringtone. This may seem like a trivial thing but I would just like to know if it's my device specific. Find 7a running CM12 stock kernels and all.
Edit: Turned off NuPlayer in developers options and set SELinux Kernel to Permissive.
Enyioha said:
Hello Just flashed to build 2015/01/21 and I noticed that I was unable to change my ringtone. This may seem like a trivial thing but I would just like to know if it's my device specific. Find 7a running CM12 stock kernels and all.
Edit: Turned off NuPlayer in developers options and set SELinux Kernel to Permissive.
Click to expand...
Click to collapse
sorry for noob question
how can I change SELinux Kernel to Permissive ?
Missing languages
In the 21/01 build, some languages are missing - texts simply do not appear and the language list is empty near the end.
EDIT:
23/01 build solves it.
EDIT2:
Gyro doesn't work, screen doesn't rotate.

[ycjeson][MIUI 8] LeEco Cool1 (C106)

Hi guys,
First of all, this work is not mine, is from @ycjeson, I found it here: MIUI 8 For LeEco Cool1.
I decided to start this thread, because any information about LeEco Cool1 is difficult to find and in the most part it is in Russian or Chinese...
Get to work!
Do not forget to make a DUMP of your primary system partitions (like IMEI). Trust me, do it!!!
1) Tutorial here;
2) Needed tools here.
Install TWRP Recovery from BB72TT
Tutorial and download links here!
Install MIUI 8 and make root
1) I recomend a full wipe (cache, dalvik, data, system);
2) Put MIUI 8 and Magisk v10.2 into internal SD Card;
3) Move Magisk v10.2 zip to '/cache' partition using file manager of TWRP;
4) Install MIUI 8 via TWRP;
5) Reboot system without wipe anything (first boot will be long);
6) Reboot to TWRP;
7) Flash Magisk v10.2 zip from '/cache' partition;
8) Reboot system (may be fast);
9) Install phh's root manager apk and Latest Magisk Manager apk.
Optional to remove encryption from '/data' partiton:
10) Wipe data and cache;
11) Reboot system (boot will be very long, be patience);
12) Put Magisk v10.2 into internal memory;
13) Fash Magisk v10.2 zip again;
14) Reboot system (may be fast);
15) Install phh's root manager apk and Latest Magisk Manager apk.
DOWNLOAD ROM
Magisk downloads and more informations here!
Well guys, if possible, say thanks to people who contribute to improving the LeEco Cool1 community:
BB72TT from "leeco.re" forum, for your precious TWRP recovery
partyheadgmailcom from "leeco.re" forum, for tutorials (DUMP and How to install TWRP Recovery)
@ycjeson for your precious MIUI 8
@topjohnwu for Magisk
@phhusson for Superuser
Other people I forgot to mention!
I hope it's useful! :highfive:
A big thanks for your idea of introducing the ROM here.
I own this device, it has a lot of potential from software development angle but unfortunately the lack of popularity for this device is one the main reasons why devs are not interested in developing custom ROMs
Also this device runs LE ECO EUI hence I hope Le eco will come up with some awesome updates (if not then hope someone takes the initiative for some custom ROMs specially a lineage OS ROM would be perfect)
Screen shot and bug report?
download link
please provide download link:fingers-crossed::fingers-crossed::fingers-crossed:
not work
abhipundir said:
please provide download link:fingers-crossed::fingers-crossed::fingers-crossed:
Click to expand...
Click to collapse
Try this link: download
chidosu said:
not work
Click to expand...
Click to collapse
If you performed the procedure as described, this works, I even tested it!
I just installed it working perfectly but I didn't find G apps . can I flash arm 64 g apps package from the g apps open source website??
Kaushikrex007 said:
I just installed it working perfectly but I didn't find G apps . can I flash arm 64 g apps package from the g apps open source website??
Click to expand...
Click to collapse
So, you can't flash gapps in MiUi based ROMs, because gapps is just for AOSP ROMs. Search in Google about Google apps for MiUi.
What are the bug reports?
Please report the detailed bug report of the ROM.
Kaushikrex007 said:
I just installed it working perfectly but I didn't find G apps . can I flash arm 64 g apps package from the g apps open source website??
Click to expand...
Click to collapse
did you see any camera bug???????????????and what is the android version
Roms c106 compatible model c106-9?
Enviado desde mi Redmi Note 3 mediante Tapatalk
maligno1 said:
Roms c106 compatible model c106-9?
Enviado desde mi Redmi Note 3 mediante Tapatalk
Click to expand...
Click to collapse
I think not.
Why am I losing signal at certain times? While phone calling it's shutting suddenly.
reddsmokee said:
Why am I losing signal at certain times? While phone calling it's shutting suddenly.
Click to expand...
Click to collapse
Had that issue too.. Roms bug
ceraklija said:
Had that issue too.. Roms bug
Click to expand...
Click to collapse
Thank you friend your reply. So is there any update without this issue?
reddsmokee said:
Thank you friend your reply. So is there any update without this issue?
Click to expand...
Click to collapse
I think no, the lastest version is the one from december.
Miui9 leeco cool1
http://bbs.7to.cn/thread-320449-1-1.html
sost_xda said:
Miui9 leeco cool1
http://bbs.7to.cn/thread-320449-1-1.html
Click to expand...
Click to collapse
Thank you for sharing. But a few question i have.
Does fingerprint unlock and 3g-4g internet work?
Because as i understand it, i'm confused.
Can I install it on my c103 device

[UNITY] Various Fixes for the Moto G5/G5S [9+]

HUGE thanks to @giri45 for actually providing the fix!
What's this? ​
A Unity installer ensures that you can use this module with any kind of root solution (as long as it supports init.d)! If you have Magisk, flash the module through the Magisk Manager, but if you don't have Magisk, just flash the module through TWRP. When you want to uninstall the module, flash it again in Magisk Manager or TWRP.
As for the module itself, it provides a fix for LiveDisplay/Night Light on the Moto G5/G5S for anyone running an AOSP-based ROM running Android 9 or higher, and enables Camera2 API + EIS if you wish so.
Do NOT attempt to install this on other devices, or ROMs based on Android <9! Device and Android version checks have been applied to make sure this module will not install on incompatible devices. This module assumes that you are using the latest stock Oreo firmware (including bootloader, GPT and etc.)! Do not report issues if you are not on the latest firmware.
Tested ROMs:
Havoc OS 2.2
Pixel Experience 9.0
AOSPExtended 6.3
crDroid 5.0
Known issues:
Fix doesn't work on Nougat firmware. You must have fully flashed the stock ROM/flashed it via OTA, for this fix to work.
Downloads:
Download from Magisk Repo.​
Flash via Magisk Manager or TWRP. Make sure you have a root solution which supports init.d!
Thanx for trying to fix this. Unfortunately it's not working on my xt1794 running AospExtented. First try flashing through twrp failed, the updaterscript didn't recognize my phone (correctly), then installing as magisk module, but no night light..
Ænimal said:
Thanx for trying to fix this. Unfortunately it's not working on my xt1794 running AospExtented. First try flashing through twrp failed, the updaterscript didn't recognize my phone (correctly), then installing as magisk module, but no night light..
Click to expand...
Click to collapse
That's really weird. Installs fine and works on PE, installs fine but doesn't work on ViperOS, and now doesn't work on AOSPExtended.
Could you try providing installation logs located in the Internal storage?
Have you also tried manually replacing the files? If that works, then it's not a problem with the ROM...
JarlPenguin said:
That's really weird. Installs fine and works on PE, installs fine but doesn't work on ViperOS, and now doesn't work on AOSPExtended.
Could you try providing installation logs located in the Internal storage?
Have you also tried manually replacing the files? If that works, then it's not a problem with the ROM...
Click to expand...
Click to collapse
Deleted
PE 9.0LOG is attached
@JarlPenguin You mentioned fix is working on AOSPExtended 6.3, is that for the g5, or is there a montana build? If so, please provide a link if possible, thanx
Ænimal said:
@JarlPenguin You mentioned fix is working on AOSPExtended 6.3, is that for the g5, or is there a montana build? If so, please provide a link if possible, thanx
Click to expand...
Click to collapse
It's an internal build. You can test it out here: https://t.me/montanadevelopment
JarlPenguin said:
It's an internal build. You can test it out here: https://t.me/montanadevelopment
Click to expand...
Click to collapse
I'm running this build now and tried the fix but to no avail, still (xt1794)
Ænimal said:
I'm running this build now and tried the fix but to no avail, still (xt1794)
Click to expand...
Click to collapse
Are you on the Oreo firmware? GPT and bootloader included. Did you do a screen repair before?
JarlPenguin said:
Are you on the Oreo firmware? GPT and bootloader included. Did you do a screen repair before?
Click to expand...
Click to collapse
Nougat firmware and Oreo baseband, screen is original. Do you think that partition table is the problem?
Ænimal said:
Nougat firmware and Oreo baseband. Do you think that partition table is the problem?
Click to expand...
Click to collapse
Okay, I think I have found the problem now. What have you not upgraded?
JarlPenguin said:
Okay, I think I have found the problem now. What have you not upgraded?
Click to expand...
Click to collapse
As I said, I upgraded the baseband, the rest is firmware from nougat. On another device I'm running lollipop firmware and no problems regarding night light on pie ROMs..
Edit: I see you updated op, will report back once I fully upgraded firmware (for now I want to be able to revert back to nougat). Thanx for your efforts
Ænimal said:
As I said, I upgraded the baseband, the rest is firmware from nougat. On another device I'm running lollipop firmware and no problems regarding night light on pie ROMs..
Edit: I see you updated op, will report back once I fully upgraded firmware (for now I want to be able to revert back to nougat). Thanx for your efforts
Click to expand...
Click to collapse
Thanks. I updated the OP a while ago, but I do want to figure out the root cause of the problem, whether it is the vendor image, bootloader, GPT, or something else.
JarlPenguin said:
Thanks. I updated the OP a while ago, but I do want to figure out the root cause of the problem, whether it is the vendor image, bootloader, GPT, or something else.
Click to expand...
Click to collapse
I'm planning on upgrading everything except bootloader and gpt.bin, then I'll try your fix again and report back:good:
Edit: OK, done. I did flash bootloader, did not erase userdata and did not flash stock recovery. Good news is: system feels alot snappier - not so good news is that fix is still not working for me..
For anyone with similar issue: use cf.lumen instead and don't forget to thank the dev
Ænimal said:
I'm planning on upgrading everything except bootloader and gpt.bin, then I'll try your fix again and report back:good:
Edit: OK, done. I did flash bootloader, did not erase userdata and did not flash stock recovery. Good news is: system feels alot snappier - not so good news is that fix is still not working for me..
For anyone with similar issue: use cf.lumen instead and don't forget to thank the dev
Click to expand...
Click to collapse
That's weird... One thing I know that is that this fix doesn't work on Nougat firmware.
Working flawlessly on crDroid 9.
Thank you devs!
I have installed the mod with magisk and not working on my device with Pixel Experience 9.0
Arn'oh said:
I have installed the mod with magisk and not working on my device with Pixel Experience 9.0
Click to expand...
Click to collapse
Hehe, same like me , if you didn't updated officially than this fix won't work on any PIE ROM
zahidm said:
Hehe, same like me , if you didn't updated officially than this fix won't work on any PIE ROM
Click to expand...
Click to collapse
I had updated to Oreo official beta test with fastboot commands
Arn'oh said:
I had updated to Oreo official beta test with fastboot commands
Click to expand...
Click to collapse
Did you flash everything? Try fully flashing Stock Oreo via Fastboot and then install TWRP, custom ROM and this fix.

[ROM][UNOFFICIAL] Lineage 15.1 Manta [NEXUS10][01OCT2019][MONTHLY]

Again, credits to the great @followmsi
Disclaimer:
Not responsible for any injuries you do to yourself or your device being damaged caused by this ROM.
Known issues:
- Camera is not working (broken HAL1 camera and unsupported HAL2 camera)
- Headphone jack is not fully working
Instructions:
1. Flash ROM
2. Flash Gapps (I use opengapps PICO)
3. Reboot to OS
4. Profit?
5. Reboot to Recovery to install Magisk (Optional)
Download Link:
https://drive.google.com/open?id=1BL...oJRV5Vms_MZF3N
Sources:
https://github.com/KiDwayne/android_kernel_samsung_manta
https://github.com/LineageOS
Credits to:
LineageOS Team
@followmsi
Initial release:
Direct Link https://drive.google.com/open?id=1WMwEpiBSzJX8X56rEg6NUz6IhXD-kh_v
May Patch
Others are sticking to LOS
Whatever doesnt work in Nougat doesn't work in Oreo
Opening post download link doesn't work. You copy pasted the text with the .... instead of using the link
Just downloading now to install over older 15.1 build.
Thanks for taking over. Everything is working fine.
flashed on my manta to use it as a daily driver as an home automation display, seems to work pretty good, subscribing for new updates.
Thanks!
Thanks a bunch, may build runs smooth.
Gonna test this one, too.
Are there any users who installed both the 14.1 and 15 versions? How do they compare?
Is there a kink for the opengapps PICO?
The download link is not working anymore.
Markster93 said:
The download link is not working anymore.
Click to expand...
Click to collapse
Check 2nd post , link working
Sent from my Nexus 10 using Tapatalk
New Build up! Terribly sorry for the holdup.
Direct Link: https://drive.google.com/open?id=1b9B6wr4NTlP5ItCLrEbzgivw8CXTNB_f
Changelog:
-June Security Patch
-LOS side updates and optimization
Hi, Downloaded the latest ROM and it flashed fine. I then factory reset the tablet, as I'm planning to give it to my father. Unfortunately, the setup wizard keeps stopping Is there any possibility this can be fixed? It would be much appreciated!
fhyfds said:
Hi, Downloaded the latest ROM and it flashed fine. I then factory reset the tablet, as I'm planning to give it to my father. Unfortunately, the setup wizard keeps stopping Is there any possibility this can be fixed? It would be much appreciated!
Click to expand...
Click to collapse
I dirty flashed fine. Might be something at the back.
For now I am working with the LOS14.1 issues, worst case scenario, try this, clean flash previous build, setup and then dirty update. Tell me if it works! So sorry for the inconveniences.
Thanks, that worked great! Thank you for your work!
Works fine so far. But there's a folder "!ReadyToFlash\Root_Files" which includes amongst others "busybox_signed.zip" and "SR2-SuperSU-2.79....zip".
I've flashed them both successfully in TWRP but after reboot I can't see Busybox nor SuperSU and the Device is still unrooted (developer options offers root access as "only ADB" only).
Tried to root the Device again. This Time with Nexus Root Toolkit, which installs it's own SuperSU. But no effect again.
After this I found the official LineageOS 15.1 addonsu-15.1-arm-signed.zip and flashed it as well. Again to no avail.
Bootloader Mode says "Lock State: Unlocked". So what's wrong here?
And as I've now flashed so far three different versions of SuperSU and BusyBox (which I can't find anywhere although a root checker says it's installed), do I have to uninstall these files to prevent further problems caused by orphan files from these Installations?
cobalt100b said:
Works fine so far. But there's a folder "!ReadyToFlash\Root_Files" which includes amongst others "busybox_signed.zip" and "SR2-SuperSU-2.79....zip".
Click to expand...
Click to collapse
Maybe these are left-overs from a previous ROM? Better delete them and use Magisk which is known to work with this ROM.
New Update Finally Up!
Sorry caught up by work, resyncing and stuff took awhile.
Direct Link: https://drive.google.com/open?id=1eFj7mbLsGvoBle4nYS-PAHh6AUm5wYKq
Changelogs:
Huge LOS Side updates(causing delay)
September Security Patch
New Update Finally Up!
Sorry caught up by work, resyncing and stuff took awhile.
Direct Link: https://drive.google.com/open?id=1eFj7mbLsGvoBle4nYS-PAHh6AUm5wYKq
Changelogs:
Huge LOS Side updates(causing delay)
September Security Patch
KiD3991 said:
New Update Finally Up!
Sorry caught up by work, resyncing and stuff took awhile.
Direct Link: https://drive.google.com/open?id=1eFj7mbLsGvoBle4nYS-PAHh6AUm5wYKq
Changelogs:
Huge LOS Side updates(causing delay)
September Security Patch
Click to expand...
Click to collapse
Thanks for your ongoing great support! Just downloaded and flashed successfully.

my experiences - flashing custom rom Xiaomi Mi Play (lotus)

I tried to flash any custom rom on my device, but I couldn't find any build for mi play. I started to mine on the internet, and I found Project Treble. Generally any device that has at least Android Oreo must support Project Treble, stock android version on mi play is Android 8.1, so it must support this project.
I downloaded an app Treble Info (https://play.google.com/store/apps/details?id=tk.hack5.treblecheck&hl=pl&gl=US). It said that I have to look for an image with device category a for (of course) arm64. Unfortunately the only rom I found then was unofficial build of lineage os 16 (https://sourceforge.net/projects/andyyan-gsi/files/lineage-16.x/). It was long ago, so there was still no twrp build for mi play (https://forum.xda-developers.com/t/unofficial-twrp-recovery-3-5-2_9-0.4344611/). I was confused about gapps but I managed to install microG. I just installed magisk (by patching boot image), and i installed magisk module microG_installer (https://github.com/nift4/microg_installer_revived).
Week ago I decided to install other rom. I found couple of them. HavocOS, Resurrection Remix, AOSP and CrDroid R MOD. Every of this rom didn't work. Only HavocOS and AOSP showed their boot splashes, but AOSP never booted to actual OS and HavocOS made boot loop.
I think, GSI (project treble) rom on Xiaomi Mi Play must have two things to have even a chance to boot. First thing is version of android - maximum is Android Pie. Second thing is phh. The image must be "Phh-treble" (just look form images with phh in name or description), but this is only my theory.
Finally I decided to flash back lineage os 16 from Andy Yan, but with open gapps (https://opengapps.org). I tried to flash nano, but there was error, that i have to small free space on system partition. Fortunately I successfully flashed pico, but after booting I couldn't even proceed by google device confguration.
So if you want to have custom rom on your Xiaomi MI Play I recommend you to:
Flash Lineage OS 16 from Andy Yan's builds (https://sourceforge.net/projects/andyyan-gsi/files/lineage-16.x/)
Flash magisk (you can do it from twrp https://forum.xda-developers.com/t/unofficial-twrp-recovery-3-5-2_9-0.4344611/)
Install microG_installer magisk module (https://github.com/nift4/microg_installer_revived)
I hope this post was useful for you
Can you share the link of the other builds please?
RezaUllah__ said:
Can you share the link of the other builds please?
Click to expand...
Click to collapse
Havoc: https://download.havoc-os.com/?dir=arm64-aonly
CrDroid R Mod: https://forum.xda-developers.com/t/unofficial-crdroid-r-mod-crdrom11.4269719/
AOSP: https://forum.xda-developers.com/t/aosp-9-0-2019-08-25-phh-treble.3831915/
Ressurection: https://forum.xda-developers.com/t/resurrection-remix-unofficial-2018-06-28-phh-treble.3767688/
Good blog! I truly love how it is simple on my eyes and the data are well written. I’m wondering how I could be notified when a new post has been made. I have subscribed to your feed which must do the trick! Have a great day!
meta trader 4
IpyZ said:
I tried to flash any custom rom on my device, but I couldn't find any build for mi play. I started to mine on the internet, and I found Project Treble. Generally any device that has at least Android Oreo must support Project Treble, stock android version on mi play is Android 8.1, so it must support this project.
I downloaded an app Treble Info (https://play.google.com/store/apps/details?id=tk.hack5.treblecheck&hl=pl&gl=US). It said that I have to look for an image with device category a for (of course) arm64. Unfortunately the only rom I found then was unofficial build of lineage os 16 (https://sourceforge.net/projects/andyyan-gsi/files/lineage-16.x/). It was long ago, so there was still no twrp build for mi play (https://forum.xda-developers.com/t/unofficial-twrp-recovery-3-5-2_9-0.4344611/). I was confused about gapps but I managed to install microG. I just installed magisk (by patching boot image), and i installed magisk module microG_installer (https://github.com/nift4/microg_installer_revived).
Week ago I decided to install other rom. I found couple of them. HavocOS, Resurrection Remix, AOSP and CrDroid R MOD. Every of this rom didn't work. Only HavocOS and AOSP showed their boot splashes, but AOSP never booted to actual OS and HavocOS made boot loop.
I think, GSI (project treble) rom on Xiaomi Mi Play must have two things to have even a chance to boot. First thing is version of android - maximum is Android Pie. Second thing is phh. The image must be "Phh-treble" (just look form images with phh in name or description), but this is only my theory.
Finally I decided to flash back lineage os 16 from Andy Yan, but with open gapps (https://opengapps.org). I tried to flash nano, but there was error, that i have to small free space on system partition. Fortunately I successfully flashed pico, but after booting I couldn't even proceed by google device confguration.
So if you want to have custom rom on your Xiaomi MI Play I recommend you to:
Flash Lineage OS 16 from Andy Yan's builds (https://sourceforge.net/projects/andyyan-gsi/files/lineage-16.x/)
Flash magisk (you can do it from twrp https://forum.xda-developers.com/t/unofficial-twrp-recovery-3-5-2_9-0.4344611/)
Install microG_installer magisk module (https://github.com/nift4/microg_installer_revived)
I hope this post was useful for you
Click to expand...
Click to collapse
The 2nd link is twrp ryt?
RezaUllah__ said:
The 2nd link is twrp ryt?
Click to expand...
Click to collapse
3rd link
It’s nearly impossible to find knowledgeable folks on this topic, however, you appear to be there’s more you are talking about! Thanks
Monoprice 110010
IpyZ said:
I tried to flash any custom rom on my device, but I couldn't find any build for mi play. I started to mine on the internet, and I found Project Treble. Generally any device that has at least Android Oreo must support Project Treble, stock android version on mi play is Android 8.1, so it must support this project.
I downloaded an app Treble Info (https://play.google.com/store/apps/details?id=tk.hack5.treblecheck&hl=pl&gl=US). It said that I have to look for an image with device category a for (of course) arm64. Unfortunately the only rom I found then was unofficial build of lineage os 16 (https://sourceforge.net/projects/andyyan-gsi/files/lineage-16.x/). It was long ago, so there was still no twrp build for mi play (https://forum.xda-developers.com/t/unofficial-twrp-recovery-3-5-2_9-0.4344611/). I was confused about gapps but I managed to install microG. I just installed magisk (by patching boot image), and i installed magisk module microG_installer (https://github.com/nift4/microg_installer_revived).
Week ago I decided to install other rom. I found couple of them. HavocOS, Resurrection Remix, AOSP and CrDroid R MOD. Every of this rom didn't work. Only HavocOS and AOSP showed their boot splashes, but AOSP never booted to actual OS and HavocOS made boot loop.
I think, GSI (project treble) rom on Xiaomi Mi Play must have two things to have even a chance to boot. First thing is version of android - maximum is Android Pie. Second thing is phh. The image must be "Phh-treble" (just look form images with phh in name or description), but this is only my theory.
Finally I decided to flash back lineage os 16 from Andy Yan, but with open gapps (https://opengapps.org). I tried to flash nano, but there was error, that i have to small free space on system partition. Fortunately I successfully flashed pico, but after booting I couldn't even proceed by google device confguration.
So if you want to have custom rom on your Xiaomi MI Play I recommend you to:
Flash Lineage OS 16 from Andy Yan's builds (https://sourceforge.net/projects/andyyan-gsi/files/lineage-16.x/)
Flash magisk (you can do it from twrp https://forum.xda-developers.com/t/unofficial-twrp-recovery-3-5-2_9-0.4344611/)
Install microG_installer magisk module (https://github.com/nift4/microg_installer_revived)
I hope this post was useful for you
Click to expand...
Click to collapse
Bro it shows this...why?
IpyZ said:
I tried to flash any custom rom on my device, but I couldn't find any build for mi play. I started to mine on the internet, and I found Project Treble. Generally any device that has at least Android Oreo must support Project Treble, stock android version on mi play is Android 8.1, so it must support this project.
I downloaded an app Treble Info (https://play.google.com/store/apps/details?id=tk.hack5.treblecheck&hl=pl&gl=US). It said that I have to look for an image with device category a for (of course) arm64. Unfortunately the only rom I found then was unofficial build of lineage os 16 (https://sourceforge.net/projects/andyyan-gsi/files/lineage-16.x/). It was long ago, so there was still no twrp build for mi play (https://forum.xda-developers.com/t/unofficial-twrp-recovery-3-5-2_9-0.4344611/). I was confused about gapps but I managed to install microG. I just installed magisk (by patching boot image), and i installed magisk module microG_installer (https://github.com/nift4/microg_installer_revived).
Week ago I decided to install other rom. I found couple of them. HavocOS, Resurrection Remix, AOSP and CrDroid R MOD. Every of this rom didn't work. Only HavocOS and AOSP showed their boot splashes, but AOSP never booted to actual OS and HavocOS made boot loop.
I think, GSI (project treble) rom on Xiaomi Mi Play must have two things to have even a chance to boot. First thing is version of android - maximum is Android Pie. Second thing is phh. The image must be "Phh-treble" (just look form images with phh in name or description), but this is only my theory.
Finally I decided to flash back lineage os 16 from Andy Yan, but with open gapps (https://opengapps.org). I tried to flash nano, but there was error, that i have to small free space on system partition. Fortunately I successfully flashed pico, but after booting I couldn't even proceed by google device confguration.
So if you want to have custom rom on your Xiaomi MI Play I recommend you to:
Flash Lineage OS 16 from Andy Yan's builds (https://sourceforge.net/projects/andyyan-gsi/files/lineage-16.x/)
Flash magisk (you can do it from twrp https://forum.xda-developers.com/t/unofficial-twrp-recovery-3-5-2_9-0.4344611/)
Install microG_installer magisk module (https://github.com/nift4/microg_installer_revived)
I hope this post was useful for you
Click to expand...
Click to collapse
Ok it I flashed it ...but it shows that I can't wipe data ..shows error
RezaUllah__ said:
Ok it I flashed it ...but it shows that I can't wipe data ..shows error
Click to expand...
Click to collapse
Data is encrypted. You can't just wipe it. Before you enter advanced vipe, theres an option "format data". Enter it, type "yes" (it's just a confirmation) and ur data is formated
If you then run MIUI or flash lineage and run it, it will again encrypt data
IpyZ said:
Data is encrypted. You can't just wipe it. Before you enter advanced vipe, theres an option "format data". Enter it, type "yes" (it's just a confirmation) and ur data is formated
If you then run MIUI or flash lineage and run it, it will again encrypt data
Click to expand...
Click to collapse
So if I just use format data ...I am good to go?
RezaUllah__ said:
So if I just use format data ...I am good to go?
Click to expand...
Click to collapse
Yeah. Format data just reformat partition. It clears every encryption, or any other things that can possibly block you from wiping it.
IpyZ said:
Yeah. Format data just reformat partition. It clears every encryption, or any other things that can possibly block you from wiping it
Click to expand...
Click to collapse
Reformat partition? How do you do that?
RezaUllah__ said:
Reformat partition? How do you do that?
Click to expand...
Click to collapse
I mean, option "format data" is doing it for you
IpyZ said:
I mean, option "format data" is doing it for you
Click to expand...
Click to collapse
Ohhh ok
So I go to wipe , format data , type yes , after that go to install ...then flash the ROM ? Like this ?
RezaUllah__ said:
Ohhh ok
So I go to wipe , format data , type yes , after that go to install ...then flash the ROM ? Like this ?
Click to expand...
Click to collapse
Yeah that should work.
Please remember that all your personal data like photos or documents will be gone so, make sure u made a backup
You produced some decent points there. I looked on the internet with the problem and discovered most individuals go in addition to along with your website.
Internet Plans and Offers
how stable is the rom?
Well, many apps just don't works, because they are thinking that the device is rooted. In some way it's true.
There are some strange behaviours of fingerprint detector.
But overall the ROM is not crushing
I haven't noticed any other bugs or I do not remember them. But that was mine main pain about this rom
alcatel4010x said:
how stable is the rom?
Click to expand...
Click to collapse

Categories

Resources