I'll get to the point:
1) What is currently the best ROM for stability, performance and battery life?
2) From the research I've done myself, Pixel Experience seems to be the best for that, but is 9.0 stable enough to be used as a daily driver or should I stick with 8.1?
3) Do ROMs get OTA updates? As in, if theres a new version of Pixel Experience for example, I can get the update just like any stock update? Would I lose root?
4) If I wanted to go back to stock and start completely from scratch (no root and stuff), all I would need to do is flash a stock image with Mi Flash Tools, right?
5) What is slot A and slot B? Do they matter when I flash a ROM?
6) What permanent TWRP Recovery should I use for ROMs? ComicDan's seems to be the only one for 8.1 that is permanent, but I dont wanna mess with Treble. It also seems that his TWRP cant flash Lineage-based ROMs, but I dont care about Lineage so thats a non-issue
Thanks
Reacerbytes said:
I'll get to the point:
1) What is currently the best ROM for stability, performance and battery life?
2) From the research I've done myself, Pixel Experience seems to be the best for that, but is 9.0 stable enough to be used as a daily driver or should I stick with 8.1?
3) Do ROMs get OTA updates? As in, if theres a new version of Pixel Experience for example, I can get the update just like any stock update? Would I lose root?
4) If I wanted to go back to stock and start completely from scratch (no root and stuff), all I would need to do is flash a stock image with Mi Flash Tools, right?
5) What is slot A and slot B? Do they matter when I flash a ROM?
6) What permanent TWRP Recovery should I use for ROMs? ComicDan's seems to be the only one for 8.1 that is permanent, but I dont wanna mess with Treble. It also seems that his TWRP cant flash Lineage-based ROMs, but I dont care about Lineage so thats a non-issue
Thanks
Click to expand...
Click to collapse
1. It's all about your preferences, preferably go with official roms.
2. Same answer as 1.
3. Only official builds get ota updates, with unofficial builds you have to flash the "ota" via twrp (besides lineage os, unofficial builds also get ota).
4. Correct, you can't restore using twrp because stock image/data are encrypted, you'll end up in a boot loop (found that the hard way ).
5. They do matter, follow the instructions and ONLY the instructions say. Idk what they mean, but newer devices have them.
6. Depending on the rom (from my knowledge), you have to install twrp installer zip everytime you flash a rom.
Hope I cleared that up for you.
I'm on stock 8.1 by the way. I used to use liquid remix 10.
If you ask me what's my favourite rom(s), here is my list in order :
1. Lineage os
2. Pixel experience
3. Dot os
4. Resurrection Remix
When I am flashing any 9.0 custom rom, it installs properly but always there are two camera apps both of which do not work and when I call or receive call the volte icon in status bar disappears and the call drops. The same roms when flashed on my friends mi A1 they work fine. I am not able to understand what the problem is. I have already tried clean flashing stock rom with flashtool. Also Camera was not working in 8.1 custom roms.
ramitzoro said:
When I am flashing any 9.0 custom rom, it installs properly but always there are two camera apps both of which do not work and when I call or receive call the volte icon in status bar disappears and the call drops. The same roms when flashed on my friends mi A1 they work fine. I am not able to understand what the problem is. I have already tried clean flashing stock rom with flashtool. Also Camera was not working in 8.1 custom roms.
Click to expand...
Click to collapse
Which ROM are u flashing exactly? Are you using stock gapps? Stock gapps seem to mess with camera provided by ROM. So try lower version preferbly micro/nano/pico..
WhatzIt2Ya said:
1. It's all about your preferences, preferably go with official roms.
2. Same answer as 1.
3. Only official builds get ota updates, with unofficial builds you have to flash the "ota" via twrp (besides lineage os, unofficial builds also get ota).
4. Correct, you can't restore using twrp because stock image/data are encrypted, you'll end up in a boot loop (found that the hard way ).
5. They do matter, follow the instructions and ONLY the instructions say. Idk what they mean, but newer devices have them.
6. Depending on the rom (from my knowledge), you have to install twrp installer zip everytime you flash a rom.
Hope I cleared that up for you.
I'm on stock 8.1 by the way. I used to use liquid remix 10.
If you ask me what's my favourite rom(s), here is my list in order :
1. Lineage os
2. Pixel experience
3. Dot os
4. Resurrection Remix
Click to expand...
Click to collapse
What made you leave liquid remix? Just asking
---------- Post added at 01:21 PM ---------- Previous post was at 01:16 PM ----------
Reacerbytes said:
I'll get to the point:
1) What is currently the best ROM for stability, performance and battery life?
2) From the research I've done myself, Pixel Experience seems to be the best for that, but is 9.0 stable enough to be used as a daily driver or should I stick with 8.1?
3) Do ROMs get OTA updates? As in, if theres a new version of Pixel Experience for example, I can get the update just like any stock update? Would I lose root?
4) If I wanted to go back to stock and start completely from scratch (no root and stuff), all I would need to do is flash a stock image with Mi Flash Tools, right?
5) What is slot A and slot B? Do they matter when I flash a ROM?
6) What permanent TWRP Recovery should I use for ROMs? ComicDan's seems to be the only one for 8.1 that is permanent, but I dont wanna mess with Treble. It also seems that his TWRP cant flash Lineage-based ROMs, but I dont care about Lineage so thats a non-issue
Thanks
Click to expand...
Click to collapse
1. I dont really know but rn I use liquid remix and it checks all those boxes
2. If you hear the rom is stable it means its stable. No matter the android version. I use liquid remix and its pretty stable and I think pixel experience is even stabler
3. Some roms offer ota through a button in the phone. But most of the roms you will need to reflash the new update through twrp
4. Yes. I don't know what the other guy was talking about but I did that multiple times and it worked fine
5. Not really
6. Use it. Its treble compatible but you dont require to have treble to use it (and again I dont know what the other guy is talking about. Cosmicdan twrp reinstalls itself)
YayJohn said:
What made you leave liquid remix? Just asking
---------- Post added at 01:21 PM ---------- Previous post was at 01:16 PM ----------
1. I dont really know but rn I use liquid remix and it checks all those boxes
2. If you hear the rom is stable it means its stable. No matter the android version. I use liquid remix and its pretty stable and I think pixel experience is even stabler
3. Some roms offer ota through a button in the phone. But most of the roms you will need to reflash the new update through twrp
4. Yes. I don't know what the other guy was talking about but I did that multiple times and it worked fine
5. Not really
6. Use it. Its treble compatible but you dont require to have treble to use it (and again I dont know what the other guy is talking about. Cosmicdan twrp reinstalls itself)
Click to expand...
Click to collapse
I flashed extreme kernel and it won't detect my sim, and the rom became unusable..
Related
Hi guys, its been a few days since I joined here. [Read : I am a noob/newbie in Android related things, and I desperately need help.]
In July (maybe, I forgot), I rooted my ZE550KL, using exactly this method from the website of www-asus-zenfone-com. :cyclops:
Now that, my android seems aged, I wanna shift/upgrade to Marshmallow/Nougat, be it Stock or Custom ROM.
Few days earlier, I unlocked my Bootloader using the Unofficial Bootloader Unlocking Method, as found on this Forum.
I also installed TWRP Recovery, and I tried to flash CM-14.1 [7.1] Nougat-Nightly through TWRP, but, unfortunately, resulted in Status 7 Error. I tried to solve the problem by removing "asserts" section in Update-Binary text file, in the build. But, again, I seemingly worsened the problem; as I got Status 6 error thereby. So, I did factory reset, and I still retain root.
Now, today as I am going through the Official thread of CM 14.1 Nougat, I saw numerous users reporting Bugs of connection issues (something like Wifi to Mobile Data switch problem), which I would like to OBVIOUSLY AVOID, as I want a stable, bug-less build. So, I am thinking to go with the last snapshot build of CM 13.0 Marshmallow.
Here comes the my question : " SHOULD I FLASH CM 13.0 MM -- OR -- STOCK ROM OF MM -- OR -- RESURRECTION REMIX MM ROM?? "
In any of the case, please guide me through the process of doing so.
And, if I have to flash CM 13.0 MM, what would I do if I encounter Status Error 7 again ? :crying:
first you have to upgrade it to marshmallow using stock rom. Then you can flash cm13 or cm14.1
Devc100 said:
first you have to upgrade it to marshmallow using stock rom. Then you can flash cm13 or cm14.1
Click to expand...
Click to collapse
Please, like I said, guide me through how to do it. Thanks in advance, in case you help. :good:
Ph4nToM_Z3rO said:
Hi guys, its been a few days since I joined here. [Read : I am a noob/newbie in Android related things, and I desperately need help.]
In July (maybe, I forgot), I rooted my ZE550KL, using exactly this method from the website of www-asus-zenfone-com. :cyclops:
Now that, my android seems aged, I wanna shift/upgrade to Marshmallow/Nougat, be it Stock or Custom ROM.
Few days earlier, I unlocked my Bootloader using the Unofficial Bootloader Unlocking Method, as found on this Forum.
I also installed TWRP Recovery, and I tried to flash CM-14.1 [7.1] Nougat-Nightly through TWRP, but, unfortunately, resulted in Status 7 Error. I tried to solve the problem by removing "asserts" section in Update-Binary text file, in the build. But, again, I seemingly worsened the problem; as I got Status 6 error thereby. So, I did factory reset, and I still retain root.
Now, today as I am going through the Official thread of CM 14.1 Nougat, I saw numerous users reporting Bugs of connection issues (something like Wifi to Mobile Data switch problem), which I would like to OBVIOUSLY AVOID, as I want a stable, bug-less build. So, I am thinking to go with the last snapshot build of CM 13.0 Marshmallow.
Here comes the my question : " SHOULD I FLASH CM 13.0 MM -- OR -- STOCK ROM OF MM -- OR -- RESURRECTION REMIX MM ROM?? "
In any of the case, please guide me through the process of doing so.
And, if I have to flash CM 13.0 MM, what would I do if I encounter Status Error 7 again ? :crying:
Click to expand...
Click to collapse
While flashing CM13 if that error 7 includes "asus.verify trustzone failed..." Then its bcoz of need to update modem files (LP to MM)....
Easy way to overcome it is..... download MM modem ZIP from second post of OFFICIAL CM13 thread (120MB) and flash it using TWRP (If you are using twrp).... THEN you can flash cm13 hopefully without error 7....
If you are using stock recovery then Either u can flash twrp and use above method... OR... Download ASUS ZE550KL firmware zip file from ASUS site (1.6GB) .... Put it in SDCARD... Then boot to stock recovery and use "apply update from sdcard" option... select ZIP... Alongwith firmware Ur Modem files will also update to MM... and now u can flash twrp and then cm13...
sorry.. I know if i am lazy to post direct links...
Try it.. I will help if i can
aadi50 said:
While flashing CM13 if that error 7 includes "asus.verify trustzone failed..." Then its bcoz of need to update modem files (LP to MM)....
Easy way to overcome it is..... download MM modem ZIP from second post of OFFICIAL CM13 thread (120MB) and flash it using TWRP (If you are using twrp).... THEN you can flash cm13 hopefully without error 7....
If you are using stock recovery then Either u can flash twrp and use above method... OR... Download ASUS ZE550KL firmware zip file from ASUS site (1.6GB) .... Put it in SDCARD... Then boot to stock recovery and use "apply update from sdcard" option... select ZIP... Alongwith firmware Ur Modem files will also update to MM... and now u can flash twrp and then cm13...
sorry.. I know if i am lazy to post direct links...
Try it.. I will help if i can
Click to expand...
Click to collapse
Thanks, dude. One question, should I get CM 13.0 or Resurrection Remix ?
Ph4nToM_Z3rO said:
Thanks, dude. One question, should I get CM 13.0 or Resurrection Remix ?
Click to expand...
Click to collapse
We have both stable RR and CM13.
CM is simple and clean and less loaded.... RR is most feature rich Custom rom we have alongwith stability...
Rest depends on what type of user, u are... If u like trying differnt ROMs... Start with CM13...
If u just want to have a feature rich longtime setup, U can use RR directly without wasting time... It is based on CM, So it obviously have everything CM has.... :good:
Ph4nToM_Z3rO said:
Please, like I said, guide me through how to do it. Thanks in advance, in case you help. :good:
Click to expand...
Click to collapse
Latest Stock Marshmallow:
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE550KL/UL-Z00L-WW-21.40.1220.1877-user.zip
Stock RecoveryRestore it using TWRP)
https://drive.google.com/open?id=0B2BGto29cXq1NjYySjRES21yOTg
Last Lollipop Software:
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE550KL/UL-Z00L-WW-1.17.40.1531-user.zip
First Lollipop Software:
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE550KL/UL-Z00L-WW-1.11.40.299-user.zip
First Do A nandroid backup of your phone. So that if any thing goes wrong, U can recover it.
Then Download both the Stock MM and Recovery file named TWRP.zip.
Extract TWRP.zip.
Then take both the MM software and Xtracted TWRP folder in a memory card.
Then Open TWRP recovery in ur phone and restore the stock recovery.
Then Erase Every Thing including System.
Then Restart The recovery. Now you will see that the recovery has gone back to the stock recovery.
Now flash the stock marshmallow from your memory card.
Then flash TWRP from fastboot and thn u can flash any supported custom Android MM or Android N.
N.B. If it dosent work. Then you have to first install the last lollipop Zenfone 2 Laser(Z00LD) software then install the marshmallow.
Scanning the forum today, I came across this:
[ROM] Z.A.D.Mix7 -Stock Base Rom-
Click to expand...
Click to collapse
It looks like it would solve all the issues I'm having with my A7:
Enable multi-user mode
Enable on-screen buttons
Replace ZTE's built-in apps.
Is this a safer route to go in general than installing Cyanogenmod (when it's ready)? I've got CM on my Nexus 4, and yes, there's nice stuff there that's probably not here, but is a de-bloated stock ROM more likely to be bug-free? More likely for the camera and sound system to work fully? Also, will a debloated ROM allow for OTA updates - or allow for them to be sideloaded? I guess I'm asking, if I were to install this, what would be the procedure to get Nougat once ZTE comes out with it? Wipe and re-flash? Or wait for a de-bloated ZTE nougat ROM and flash that?
In order to flash a ROM on your axon 7 you need to unlock your bootloader which causes your warranty to be void and you can no longer receive OTA updates. Also if you are running a custom ROM you will have to wipe your phone before flashing an OTA update. However if you are running the stock rom you will probably only need to flash the update. I've tried both CyanogenMod and Z.A.DMix7 and honestly Z.A.DMix7 is definitely the way to go. In my experience using Z.A.DMix7 it seemed to be as stable as the stock rim and didn't have any major bugs. The only problem I had with it is that since it it rooted there is no way to log into Snapchat. How ever if you don't want root I think there may be an way to remove root from the ROM however I haven't tried it so I'm not sure if it'll work.
I use the debloated rom with android n-ify, xStana, and gravitybox and it is much better than the stock rom. I haven't tried the cm rom. You would have to flash the stock rom and recovery to get OTA updates.
Hello,
It's been almost a little over a year since I was last really into android customization. Since it's been so long it has become clear to me that my phone is outdated in many ways. I'm still running OxygenOS 2.2.1 with Android 5.1.1. I've been wanting to update up to Android N (7.x.x) for a long time now, but haven't seen any real stable roms or haven't really had the time to look for one. Now I've finally found my self with free time and ready upgrade my rom. I've just faced couple of problems, I can't really find what should I do when upgrading from 5.1.1 to 7.x.x since no-one is really doing that anymore. I remember reading sometime back that if you dont have the right firmwares you'll brick ur phone, and I wouldn't really want to go through that hassle at the moment. Is it still a thing or should it be just fine for me to flash a new rom just on top of this? (Ofc with clearing memory etc) Other question that is in my mind is that is there any critical bugs in Android N roms? It's bit unclear to me since there are such many roms that have their status as work in progress or beta etc, but some roms have status as stable. Are there any roms that I should clearly avoid? Im not new to this so I don't really need any deep info how to do everything etc, just a bit of a oversight on how things are going atm.
Thanks.
first of all is ur device rooted?? If yes then install the latest twrp recovery...then take a backup.. and flash any nougat rom which u like...If at all u would need Volte support then u l have to flash the 3.5.7 firmware..or else the 3.1.0 firmware works fine with most of the nougat roms..some nougat roms i would recommend are AICP, Resurrection Remix and AOSP extended .... In my suggestion u should probably first upgrade the Oxygen Os on ur device through official updates via OTA atleast upto the 3.5.6 firmware
there's no need to update until 3.5.6, unless you aren't going to plan staying with OOS [the only "stable" firmware which provides you VoLTE working, but it's still M-based and not N].
as @mhd athiq said, unlock your bootloader [just in case you still haven't done it before] then update your TWRP recovery to the latest version.
then flash the incrementals OTAs until OOS 3.1.x and you are good to go to flash any custom ROM which is N-based.
to avoid any mistake, please make a EFS backup via terminal [just to have a backup of your modems] and save the files to a safe location.
I don't have a specific ROM to suggest to you, but in my experience I have found the CAF/AOSP-based ones to be the ones with the best battery backup and less bugs then LOS-based ones.
I have used happily for a few months CypherOS version 3.5.1 [not the latest one, I find it quite unstable as the developers tried to implement OMS].
sidenote:
flashing N-based custom ROMs upon OOS 3.5.6 firmwares gives random reboots and unstable network in many cases/scenarios.
so don't update to that OOS version unless you have a mandatory VoLTE feature required [but you'll have to live with random reboots and poor network stability].
Hi guys,
Everything was working great with LineageOS 15.1 (Android 8.1), but they have discontinued the support for this version and switched to 16.0, and a FOTA update of Lineage from 15 to 16 isn't possible, so I had to download the zip manually, and flashed it using TWRP, around the end of April. Since then the Wi-Fi does not work.
I should explain what this "does not work" mean: I turn it on (either from the pull-down curtain, or from the Settings -> Network -> Wi-Fi menu), it pretends to switch on for 1-2 seconds, and then the switch turns off by itself, so it doesn't even have time to scan the available networks.
I have tried to burn a newer image again, around the beginning of May, but it didn't fix the Wi-Fi problem. I was googling a lot, but seems like nobody reports such a problem.
Any ideas how to fix it, other than going back to Android 8.1? Preferably I'd like to stay with LOS, but if I have no choice, I can consider moving to RR, or AOSP Extended or whatever.
Thanks!
I think its a boot.img problem. I have seen this error in stock too. The wifi/bluetooth used to turn off immediately after i turned them on and the error was because i flashed the wrong boot.img . If i were you i would clean flash the rom again
What do you mean by "wrong boot.img"? I don't flash any boot.img separately, I just flash the whole LineageOS rom (and then Gapps) from TWRP. Should I flash anything else? I don't think so...
Well, in my case at least the Bluetooth works properly (with both headphones and smart watch).
SOLVED!
Surprisingly, the problem seems to be solved now.
After flashing lineage-16.0-20190426 and later lineage-16.0-20190530 versions, where the Wi-Fi didn't work - today I have flashed lineage-16.0-20190704, and guess what? It is back now!
Thought it should be important to update the thread here.
xdauseril said:
Surprisingly, the problem seems to be solved now.
After flashing lineage-16.0-20190426 and later lineage-16.0-20190530 versions, where the Wi-Fi didn't work - today I have flashed lineage-16.0-20190704, and guess what? It is back now!
Thought it should be important to update the thread here.
Click to expand...
Click to collapse
It would be safer to update to stock pie first then flash custom pie roms..
Jt380p said:
It would be safer to update to stock pie first then flash custom pie roms..
Click to expand...
Click to collapse
You mean, even if I upgrade from Lineage 15.1 to 16 I need to flash the stock rom first? Why?
BTW I saw some reports on Wi-Fi problem while going back from custom to stock rom too, and there was some patch suggested to fix it.
xdauseril said:
You mean, even if I upgrade from Lineage 15.1 to 16 I need to flash the stock rom first? Why?
BTW I saw some reports on Wi-Fi problem while going back from custom to stock rom too, and there was some patch suggested to fix it.
Click to expand...
Click to collapse
Because its a prerequisite on Lineage 16, it depends on parts of stock Pie rom being installed.
The LO16 thread also listed a migration step if you didn't flash the stock Pie rom beforehand.
barrack1 said:
Because its a prerequisite on Lineage 16, it depends on parts of stock Pie rom being installed.
The LO16 thread also listed a migration step if you didn't flash the stock Pie rom beforehand.
Click to expand...
Click to collapse
Probably I have missed it.
Still can't find it neither on "install" nor "update" page:
https://wiki.lineageos.org/devices/tissot/install
https://wiki.lineageos.org/devices/tissot/update
xdauseril said:
Probably I have missed it.
Still can't find it neither on "install" nor "update" page:
https://wiki.lineageos.org/devices/tissot/install
https://wiki.lineageos.org/devices/tissot/update
Click to expand...
Click to collapse
Its on the xda thread, not on the lineageos website.
Xiaomi made some changes during the upgrade from Oreo->Pie and introduced ARB. Now you cannot downgrade back to Oreo easily. Just flashing back to Oreo(stock or custom rom) will cause the phone to bootloop. For the same reason your phone probably faced issues when you flashed (Pie) LO16 without the Pie firmware.
barrack1 said:
Its on the xda thread, not on the lineageos website.
Xiaomi made some changes during the upgrade from Oreo->Pie and introduced ARB. Now you cannot downgrade back to Oreo easily. Just flashing back to Oreo(stock or custom rom) will cause the phone to bootloop. For the same reason your phone probably faced issues when you flashed (Pie) LO16 without the Pie firmware.
Click to expand...
Click to collapse
Well, I did not try to downgrade from Pie to Oreo. All I tried to do was an upgrade from LOS 15.1 to LOS 16 (15.1 worked excellent). And I had no idea I needed to flash the stock rom in between, so I just flashed 16 over 15.1, without wiping the data partition (only wiped dalvik cache).
Can you please point me to the XDA thread you mention, where it says I had to flash the stock rom first?
Anyway, since everything works OK now (or, at least, I don't find any malfunctioning, probably except for the native camera app, so I use an external app), I don't think I should play around with it again, right?
xdauseril said:
Well, I did not try to downgrade from Pie to Oreo. All I tried to do was an upgrade from LOS 15.1 to LOS 16 (15.1 worked excellent). And I had no idea I needed to flash the stock rom in between, so I just flashed 16 over 15.1, without wiping the data partition (only wiped dalvik cache).
Can you please point me to the XDA thread you mention, where it says I had to flash the stock rom first?
Anyway, since everything works OK now (or, at least, I don't find any malfunctioning, probably except for the native camera app, so I use an external app), I don't think I should play around with it again, right?
Click to expand...
Click to collapse
Some parts of the firmware might not be overwritten by LOS/stock depending on the version. The original LO16 used Oreo firmware iirc. The thread is not hard to find, just look for it.
Hi,
Its been a long time since I last rommed any phone. Last Was my beloved 'Bacon' (Oneplus One) which I rommed till it died.
I am trying to install a custom rom on my wife's Mi A1. Have a few questions.
Which is the most stable rom (Android 11 preferred but if android 11 isn't stable then android 10 will do). Trying to replace the boring stock rom with some much needed features. but don't need a super tweaked up rom. Stability is most important. : edit: installed lineage 18.1.
Can I directly flash TWRP 3.6.0_9-0-tissot over stock? As with Bacon, I needed to flash One recovery then another to get a version jump. like I cant directly flash twrp 3.x over stock. I needed to flash TWRP 2.xy and then 3.0. (example, not real version numbers.)
I don't need root. But I do need the device to pass SafetyNet as I need it to operate apps like Gpay (which does not work if device fails SafetyNet).
Can I re lock the bootloader after flashing TWRP? Would it help with SafetyNet situation?
OpenGapps still good?
xeltos said:
Hi,
Its been a long time since I last rommed any phone. Last Was my beloved 'Bacon' (Oneplus One) which I rommed till it died.
I am trying to install a custom rom on my wife's Mi A1. Have a few questions.
Which is the most stable rom (Android 11 preferred but if android 11 isn't stable then android 10 will do). Trying to replace the boring stock rom with some much needed features. but don't need a super tweaked up rom. Stability is most important.
Can I directly flash TWRP 3.6.0_9-0-tissot over stock? As with Bacon, I needed to flash One recovery then another to get a version jump. like I cant directly flash twrp 3.x over stock. I needed to flash TWRP 2.xy and then 3.0. (example, not real version numbers.)
I don't need root. But I do need the device to pass SafetyNet as I need it to operate apps like Gpay (which does not work if device fails SafetyNet).
Can I re lock the bootloader after flashing TWRP? Would it help with SafetyNet situation?
OpenGapps still good?
Click to expand...
Click to collapse
1. There are plenty of stable roms, you can look at Xiaomi Mi A1 ROMs section to check them.
2. You can directly flash TWRP on stock rom.
3. ?
4. No
5. I use roms with pre-installed GApps for stablity.
mahyarmo said:
1. There are plenty of stable roms, you can look at Xiaomi Mi A1 ROMs section to check them.
2. You can directly flash TWRP on stock rom.
3. ?
4. No
5. I use roms with pre-installed GApps for stablity.
Click to expand...
Click to collapse
Installed lineage 18.1 with opengapps micro.