Does anyone know anything about this rom e-0.7-p-20190924-UNOFFICIAL-taimen.zip? - Google Pixel 2 XL Questions & Answers

I saw the link on AFH and it has been downloaded 67 times and I have never seen this rom before and was wondering if anyone knew anything about it for instance is it pie or android 10, what source it was bulit from etc.... Any info would be appreciated Thanks.

It's a degoogled offshoot of lineage 16 with microG included. It's a bit different, Similar to cosp without gapps. Something to play around with while we wait for a10 ROMs

Edmontonchef said:
It's a degoogled offshoot of lineage 16 with microG included. It's a bit different, Similar to cosp without gapps. Something to play around with while we wait for a10 ROMs
Click to expand...
Click to collapse
Have you flashed it? If yes then what factory img were you on in order to get it to boot properly,Thanks

bigmarv31 said:
Have you flashed it? If yes then what factory img were you on in order to get it to boot properly,Thanks
Click to expand...
Click to collapse
I was on August 9.0 I flashed nano gapps after rebooting twrp and it booted up. Didn't try without yet.

Related

[ROM][UNOFFICIAL][Flounder][8.1.0_r22] NitrogenOS[04/30/18]

Nitrogen OS is a custom ROM based on AOSP and I made it for our Nexus 9 (WIFI) today .
Thanks to the NitrogenOS project for the source
First boot takes time, just wait patiently
Features:
0. Stock kernel works and force encrypt disabled
1. Non-rooted, use magisk 16.4 for root.
P.S. Flash magisk after first boot and install magisk manager manually.
2.HW still broken
Here's a thread describe Nitrogen OS in details,I'll save the time
https://forum.xda-developers.com/go...-nitrogen-os-n-substratum-04-09-2016-t3454762
Download link : https://www.androidfilehost.com/?w=files&flid=234787
Device tree:https://github.com/LineageOS/android_device_htc_flounder modified for Nitrogen.
Awesome job
Down loading now.
Another N9 ROM. This is great. Poor Flounder has been the red headed step child for so long now. Thanks for another quality choice for our device.
Thanks very much. I love Nitrogen rom on my Shamu. I'll DL as soon as get home.
Woohoo!! I am glad, I just bought a Nexus 9 a couple of days ago and was severely disapointed with the lack of ROMs and the fact that the one that I got was a refurbished but still having the sensor issue. Happy with my Nexus 7 2013 and how fast it is with the Nitrogen OS.
---------- Post added at 02:52 AM ---------- Previous post was at 02:08 AM ----------
Woohoo!! I am glad, I just bought a Nexus 9 a couple of days ago and was severely disapointed with the lack of ROMs and the fact that the one that I got was a refurbished but still having the sensor issue. Happy with my Nexus 7 2013 and how fast it is with the Nitrogen OS.
jlokos said:
Thanks very much. I love Nitrogen rom on my Shamu. I'll DL as soon as get home.
Click to expand...
Click to collapse
Flashed this morning, and everything is working well. Thanks very much for the Nitrogen flounder.
What! Nitro for flounder too! Seems as tho all the good roms for our device came after all! Will definitely be flashing thjs afternoon. Thanks op!
Thanks for your work. Just flash rom & the lastest supersu but can't get root.
Please help
RogueSven said:
Thanks for your work. Just flash rom & the lastest supersu but can't get root.
Please help
Click to expand...
Click to collapse
The latest build is pre-rooted and SuperSU is unnecessary
Does this ROM have force encrypt disabled like other Nitrogen OS builds?
I can't get videos to play. I used opengapps stock.
ins5736 said:
I can't get videos to play. I used opengapps stock.
Click to expand...
Click to collapse
The same here. YouTube, Apple music , Amazon music, Spotify all failed to play here. Although some game can play simple audio.
Is it possible that it is missing some codec libs ?
cheeven_tsai said:
The same here. YouTube, Apple music , Amazon music, Spotify all failed to play here. Although some game can play simple audio.
Is it possible that it is missing some codec libs ?
Click to expand...
Click to collapse
Now youtube works with 0304 build. uploading
Tried to flash latest build but got stuck in a Google loop . Clean install and latest vendor. Could have been a bad download so will try again.
Gold Ribbed said:
Tried to flash latest build but got stuck in a Google loop . Clean install and latest vendor. Could have been a bad download so will try again.
Click to expand...
Click to collapse
Tried again with fresh download and all is fine thanks for another ROM to try.
I'm stuck in boot logo boot loop. I flashed rom and dynamic minimal gapps and reboot. no dice. this is also happening other ROMs I flash. 2 days ago I updated factory image from @WugFresh toolkit. again can't flash no ROMs boot logo loop every rom. can someone please point me in right direction. thx in advance
Sent From my Yes my Pixel XL
freddienuxx said:
I'm stuck in boot logo boot loop. I flashed rom and dynamic minimal gapps and reboot. no dice. this is also happening other ROMs I flash. 2 days ago I updated factory image from @WugFresh toolkit. again can't flash no ROMs boot logo loop every rom. can someone please point me in right direction. thx in advance
Sent From my Yes my Pixel XL
Click to expand...
Click to collapse
Did you try flashing custom kernel like Fire-Ice?
maelfilk said:
Did you try flashing custom kernel like Fire-Ice?
Click to expand...
Click to collapse
nope why that works?
Sent From my Yes my Pixel XL
What vendor image are we supposed to use? I flashed N4F26Q but when i boot it asks me to use the F image.

Sensors stop working with any 7.1.1. Bullhead custom ROM

So, I'm very eager to upgrade to a 7.1.1 custom ROM from 6.0.1 (currently using Dirty Unicorns 6.0.1), but I seem to have an issue with any android 7.1.1 version of a custom ROM I install where the sensors for auto rotate and auto brightness stop working. I've tried complete wipes and resets and installed crDroid, resurrection remix dirty unicorns and lineage OS. All of them have the same result. When downloading any apps that can be used to test and calibrate sensors, they all will read for that the sensor is unavailable for all hardware in the phone except for Wifi and GPS. Is this a general issue with android 7.0.1 on nexus 5x or is this just me? I've yet to find any other forums or pages with anyone experiencing this.
Any suggestions at all on this? I don't want to be stuck using Android 6 forever.
Any advice that can be offered would be greatly appreciated!
Ryan
kvothe26 said:
So, I'm very eager to upgrade to a 7.1.1 custom ROM from 6.0.1 (currently using Dirty Unicorns 6.0.1), but I seem to have an issue with any android 7.1.1 version of a custom ROM I install where the sensors for auto rotate and auto brightness stop working. I've tried complete wipes and resets and installed crDroid, resurrection remix dirty unicorns and lineage OS. All of them have the same result. When downloading any apps that can be used to test and calibrate sensors, they all will read for that the sensor is unavailable for all hardware in the phone except for Wifi and GPS. Is this a general issue with android 7.0.1 on nexus 5x or is this just me? I've yet to find any other forums or pages with anyone experiencing this.
Any suggestions at all on this? I don't want to be stuck using Android 6 forever.
Any advice that can be offered would be greatly appreciated!
Ryan
Click to expand...
Click to collapse
Make sure you read the OP of the ROM you are installing.
Clean flash everything with correct vendor image.
kvothe26 said:
So, I'm very eager to upgrade to a 7.1.1 custom ROM from 6.0.1 (currently using Dirty Unicorns 6.0.1), but I seem to have an issue with any android 7.1.1 version of a custom ROM I install where the sensors for auto rotate and auto brightness stop working. I've tried complete wipes and resets and installed crDroid, resurrection remix dirty unicorns and lineage OS. All of them have the same result. When downloading any apps that can be used to test and calibrate sensors, they all will read for that the sensor is unavailable for all hardware in the phone except for Wifi and GPS. Is this a general issue with android 7.0.1 on nexus 5x or is this just me? I've yet to find any other forums or pages with anyone experiencing this.
Any suggestions at all on this? I don't want to be stuck using Android 6 forever.
Any advice that can be offered would be greatly appreciated!
Ryan
Click to expand...
Click to collapse
I have a similar problem with every 7.1.1 custom ROM. Lift to check phone is not working (and yes, ambient display is enabled, vendor is correct). Every stock-based 7.1.2 ROM does work. Try flashing Stock+ 7.1.2 and see if your sensors work.
indian84 said:
Make sure you read the OP of the ROM you are installing.
Clean flash everything with correct vendor image.
Click to expand...
Click to collapse
I am always clean flashing. What do you mean by correct vendor image? It's always a bullhead version of the ROM. Maybe I misunderstand what you mean.
kvothe26 said:
I am always clean flashing. What do you mean by correct vendor image? It's always a bullhead version of the ROM. Maybe I misunderstand what you mean.
Click to expand...
Click to collapse
There is something called vendor image that you have to flash along with the ROM. It's generally linked to the build number.
Read the OP of the ROM you are using, it should have the correct vendor image you should use. If THE OP does not mention anything about the Vendor image, just search the thread or politely ask what vendor image to use.
Hopefully someone should link the download link for you. If not, you can easily Google it.
indian84 said:
There is something called vendor image that you have to flash along with the ROM. It's generally linked to the build number.
Read the OP of the ROM you are using, it should have the correct vendor image you should use. If THE OP does not mention anything about the Vendor image, just search the thread or politely ask what vendor image to use.
Hopefully someone should link the download link for you. If not, you can easily Google it.
Click to expand...
Click to collapse
Ohh. I was never aware of having to do something like this. I've always just downloaded the ROM and flashed it. Really appreciate this! Thanks! I'll have to give this a try.
kvothe26 said:
Ohh. I was never aware of having to do something like this. I've always just downloaded the ROM and flashed it. Really appreciate this! Thanks! I'll have to give this a try.
Click to expand...
Click to collapse
I have a strong feeling flashing correct vendor image will solve your problems.
indian84 said:
I have a strong feeling flashing correct vendor image will solve your problems.
Click to expand...
Click to collapse
You were right!
I downloaded the latest image from google and used the flash-all.bat script through fastboot, reflashed twrp, flashed crDroid 7.1.1, got a vendor image mismatch error on boot, then flashed the recommended vendor image version and now I'm booting without error and all sensors are working! I noticed Wifi detection and connection were working a but slow before, now everything is working perfectly. I was completely unaware that this needed to be done. It never came up as an issue for me when I was on Nexus 5.
I love the XDA community! Thanks a million for your help!
kvothe26 said:
You were right!
I downloaded the latest image from google and used the flash-all.bat script through fastboot, reflashed twrp, flashed crDroid 7.1.1, got a vendor image mismatch error on boot, then flashed the recommended vendor image version and now I'm booting without error and all sensors are working! I noticed Wifi detection and connection were working a but slow before, now everything is working perfectly. I was completely unaware that this needed to be done. It never came up as an issue for me when I was on Nexus 5.
I love the XDA community! Thanks a million for your help!
Click to expand...
Click to collapse
Separate Vendor partition was introduced with 5X and 6P. It was not needed on earlier devices.

Has anybody tried Linage 15.1 unofficial

Was just wondering if anybody had tried this unofficial linage from erfanoabdi i found on android file host https://androidfilehost.com/?w=files&flid=248828, would like to know if its working or not before i unlock my bootloader.
Cheers Shane.
riskyfuture said:
Was just wondering if anybody had tried this unofficial linage from erfanoabdi i found on android file host https://androidfilehost.com/?w=files&flid=248828, would like to know if its working or not before i unlock my bootloader.
Cheers Shane.
Click to expand...
Click to collapse
download.invisiblek.org/roms/lineage-15.1/nash/lineage-15.1-20180411-UNOFFICIAL-nash.zip
More up to date. Follow same install instructions from AOSiP thread in ROM section.
Screenie. Works fine
Uzephi said:
download.invisiblek.org/roms/lineage-15.1/nash/lineage-15.1-20180411-UNOFFICIAL-nash.zip
More up to date. Follow same install instructions from AOSiP thread in ROM section.
Click to expand...
Click to collapse
Cheers will check I out
Any conflicts with pantheon kernel?
badhalf said:
Any conflicts with pantheon kernel?
Click to expand...
Click to collapse
Motomods currently don't work with pantheon kernel. Everything else is the sane, minus the upstream patches and the features in pantheon which work fine except 230 MHz UC of the CPU. Will work on it this weekend.
between Lineage or AOSiP, which would you recommend @Uzephi?
cervantesjc said:
between Lineage or AOSiP, which would you recommend @Uzephi?
Click to expand...
Click to collapse
That's on preference. I like the custom options of the owl's best in AOSiP personally
Uzephi said:
download.invisiblek.org/roms/lineage-15.1/nash/lineage-15.1-20180411-UNOFFICIAL-nash.zip
More up to date. Follow same install instructions from AOSiP thread in ROM section.
Click to expand...
Click to collapse
Ok so something curious happened to me, tried installing the invisiblek version of lineageOS on Twrp and now I hardbricked my cellphone. So now I just wasted $400 on a cellphone im not ever gonna use
Going to wait for a bit before I go ahead with rooting my phone as I have a Vodafone branded xt1789-06 international version. Don't want to risk bricking or loosing my IMEI as I made this mistake with my I9505. So I'm going to wait for some more development on my device.
PoisonDash2 said:
Ok so something curious happened to me, tried installing the invisiblek version of lineageOS on Twrp and now I hardbricked my cellphone. So now I just wasted $400 on a cellphone im not ever gonna use
Click to expand...
Click to collapse
Worked for me, so must have been how it was flashed. Did you flash the firmware files first for Nash? If not, you didn't flash right. A flash all fixed it for me when I forgot that.
I've been using linage for a few days now, I like how is a little more stable than AOSIP, and Moto mods work better on lineage, but I have a question, where can I see if the rom gets updated?
@Uzephi do you know if Lineage has been updated at all?
cervantesjc said:
I've been using linage for a few days now, I like how is a little more stable than AOSIP, and Moto mods work better on lineage, but I have a question, where can I see if the rom gets updated?
Click to expand...
Click to collapse
Audio work when recording video? That's really the only thing I'm waiting for on any of these ROMs before I flash. I have a motomod battery, so it's nice to know that'll work, but having audio while recording is way more important to me.
davehasninjas said:
Audio work when recording video? That's really the only thing I'm waiting for on any of these ROMs before I flash. I have a motomod battery, so it's nice to know that'll work, but having audio while recording is way more important to me.
Click to expand...
Click to collapse
That's still an issue, I really don't record that many videos, so really not an issue for me.
cervantesjc said:
@Uzephi do you know if Lineage has been updated at all?
Click to expand...
Click to collapse
Besides the normal LoS updates? None that I have seen on gerrit. You can always follow the development of LoS and our device by following their gerrit. I haven't checked it since two weeklies ago.
https://review.lineageos.org/#/q/nash
Link for our device specific additions, conflicts, abandons, etc.
Thanks for the reply, I found out that lineage takes advantage of Android seamless update, and I've been getting updates, just minor ones, but hopefully it'll be a fully working rom pretty soon.
I was using the build 20180515 from invisiblek and it was working very well. Today I installed the build 20180517 and the colours became funky and messy unfortunately, it cannot be used. I had to go back to the previous build.
Just sharing this here for you to know.
Scratch that, after a clean install it's all fine. No dirty flash from 0515 to 0517 then.
Does anyone know if lte is working on sprint?
always6s said:
Does anyone know if lte is working on sprint?
Click to expand...
Click to collapse
Yes, been working for the past couple of weeks

[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.

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