Database Users

[GUIDE][MOD]Move to MIUI from any custom rom through TWRP

First of all, backup your EFS.
Once done, proceed to the process.
1.Download the files below. Download the MIUI rom you want to flash and get it on your device.
2.Go to recovery. Wipe cache,dalvik cache,system and data.
3. Install the rom along with lazyflasher(link below).
Voila! You flashed it but unfortunately when you reboot it, it will vibrate once and turn off. Being in this state you can't go back to recovery too. So lets fix it.
4. Extract the RN3_unlockblonly and fastboot_edl on your pc.
5.Connect the device to pc and click on edl.cmd from the fastboot _edl.7z. Tge device screen will become black. Let it be.
6.Open Miflash tool and select RN3_unlock_only. Refresh. And then click on flash. Once done remove the device and go to recovery. Wipe cache and dalvik cache and done.
Happy MIUIing!
RN3_unlockblonly.rar https://forum.xda-developers.com/attachment.php?attachmentid=4057737&d=1488316339
Lazy falsher https://www.androidfilehost.com/?fid=529152257862700328
Fastboot_edl.7z https://forum.xda-developers.com/attachment.php?attachmentid=3775693&d=1465328762
Credits:
emuzychenko
AlexCleric
The [email protected]

Hmm... I always Just Flash official Global dev through zcx twrp and it Works without a problem.

Denis:) said:
Hmm... I always Just Flash official Global dev through zcx twrp and it Works without a problem.
Click to expand...
Click to collapse
For me,even zcx throws up the same error so i figured out this method.
Sent from my Redmi Note 3 using XDA-Developers Legacy app

deepjyoti30 said:
For me,even zcx throws up the same error so i figured out this method.
Sent from my Redmi Note 3 using XDA-Developers Legacy app
Click to expand...
Click to collapse
What error do you get?
You must flash latest miui fastboot rom, if you are still on LP bootloader.
I can flash now migrate between miui and N custom roms without problem with ZCX 0917
But thank you anyway

Denis:) said:
What error do you get?
You must flash latest miui fastboot rom, if you are still on LP bootloader.
I can flash now migrate between miui and N custom roms without problem with ZCX 0917
But thank you anyway
Click to expand...
Click to collapse
Every time i flash miui with lazy flasher just from any N custom rom i get the vibrate and turn off error. I have flashed the fastboot roms ton of times and my device had out of the box mm. I have also tried it with zcx but got the same error

deepjyoti30 said:
Every time i flash miui with lazy flasher just from any N custom rom i get the vibrate and turn off error. I have flashed the fastboot roms ton of times and my device had out of the box mm. I have also tried it with zcx but got the same error
Click to expand...
Click to collapse
I dont flash anything except recovery ROM official global dev or whichever...no lazyflasher, no firmware...
Just needed to flash once fastbotoot ROM via EDL latest global dev so I am on that firmware...I did that with one fastboot global dev from february...
I just wipe everything in twrp before, except microSD... Just flashed today new global dev, coming from NOS, format data, wipe all , flash rom, reboot

Denis:) said:
I dont flash anything except recovery ROM official global dev or whichever...no lazyflasher, no firmware...
Just needed to flash once fastbotoot ROM via EDL latest global dev so I am on that firmware...I did that with one fastboot global dev from february...
I just wipe everything in twrp before, except microSD... Just flashed today new global dev, coming from NOS, format data, wipe all , flash rom, reboot
Click to expand...
Click to collapse
I tried exactly that but it always ends up with the error

Denis:) said:
I dont flash anything except recovery ROM official global dev or whichever...no lazyflasher, no firmware...
Just needed to flash once fastbotoot ROM via EDL latest global dev so I am on that firmware...I did that with one fastboot global dev from february...
I just wipe everything in twrp before, except microSD... Just flashed today new global dev, coming from NOS, format data, wipe all , flash rom, reboot
Click to expand...
Click to collapse
I'm using MIUI Global beta latest 7.4.13
I want to try Nougat ROM but I'm afraid of getting bootloop.
So pls tell me exact procedure for Switching back to MIUI from Lineage OS using Recovery method (zcx TWRP)...
I'm using ZCX TWRP, Officially Unlocked Bootloader.
Will my Bootloader Locked after Revert back to MIUI??
Thanks

Ajendra25 said:
I'm using MIUI Global beta latest 7.4.13
I want to try Nougat ROM but I'm afraid of getting bootloop.
So pls tell me exact procedure for Switching back to MIUI from Lineage OS using Recovery method (zcx TWRP)...
I'm using ZCX TWRP, Officially Unlocked Bootloader.
Will my Bootloader Locked after Revert back to MIUI??
Thanks
Click to expand...
Click to collapse
Why not flash xiaomi.eu rom? That won't lock your bootloader and twrp remains.

JLius said:
Why not flash xiaomi.eu rom? That won't lock your bootloader and twrp remains.
Click to expand...
Click to collapse
Even official global/china dev/stable doesnt lock BL, if you are already on MM bootloader.
+ From my experience those official roms are better compared to .eu or multirom

Denis:) said:
Even official global/china dev/stable doesnt lock BL, if you are already on MM bootloader.
+ From my experience those official roms are better compared to .eu or multirom
Click to expand...
Click to collapse
@Denis:) So If I just flash MIUI Global dev using ZCX TWRP reverting from Lineage OS it should work smoothly?
---------- Post added at 05:59 PM ---------- Previous post was at 05:57 PM ----------
Denis:) said:
Even official global/china dev/stable doesnt lock BL, if you are already on MM bootloader.
+ From my experience those official roms are better compared to .eu or multirom
Click to expand...
Click to collapse
@Denis:) So, if I just flash MIUI global dev using ZCX Reverting back from Lineage OS, it should work smoothly right?

Ajendra25 said:
@Denis:) So If I just flash MIUI Global dev using ZCX TWRP reverting from Lineage OS it should work smoothly?
---------- Post added at 05:59 PM ---------- Previous post was at 05:57 PM ----------
@Denis:) So, if I just flash MIUI global dev using ZCX Reverting back from Lineage OS, it should work smoothly right?
---------- Post added at 06:00 PM ---------- Previous post was at 05:59 PM ----------
[/COLOR @Denis:) So, if I just flash MIUI global dev using ZCX Reverting back from Lineage OS it should work smoothly right?
Click to expand...
Click to collapse
If you ever flashed MM fastboot miui on this device before, then yes. If you didnt you are still on LP bootloader, which will result in BL relock and you will have to boot to fastboot and then unlock it officialy via miunlock.
Ptocedure in twrp:
Format data (type yes)
Advanced wipe (wipe everyhing, except microSD)
Flash Recovery miui ROM, reboot:good:

Denis:) said:
If you ever flashed MM fastboot miui on this device before, then yes. If you didnt you are still on LP bootloader, which will result in BL relock and you will have to boot to fastboot and then unlock it officialy via miunlock.
Ptocedure in twrp:
Format data (type yes)
Advanced wipe (wipe everyhing, except microSD)
Flash Recovery miui ROM, reboot:good:
Click to expand...
Click to collapse
No, still I haven't flashed MM Fastboot Rom. I've checked Bootloader version in CPU-Z App but it says Bootloader - Unknown!
& Is it necessary to wipe Internal storage, bcz I don't want to remove all that my stuff!?
You told me that procedure it's for Reverting to MIUI right?

Ajendra25 said:
No, still I haven't flashed MM Fastboot Rom. I've checked Bootloader version in CPU-Z App but it says Bootloader - Unknown!
& Is it necessary to wipe Internal storage, bcz I don't want to remove all that my stuff!?
You told me that procedure it's for Reverting to MIUI right?
Click to expand...
Click to collapse
I think its neccesary to wipe data aswell...do a backup on microSD...
You will lock your BL if you flash official rom...so you will have to unlock it via fatbooot.

JLius said:
Why not flash xiaomi.eu rom? That won't lock your bootloader and twrp remains.
Click to expand...
Click to collapse
Xiaomi Eu roms having a problem its not bypassing mi account page

Thank You U helped me really Every time when i reverting back to miui same problem occurs like no recovery access nd then i am installing custom rom again now i am successfully reverted back to miui

Having problem rooting my Axon 7 A2017U

Hey guys, first of all sorry about my english, im french.
So my problem is: I tried rooting my Axon 7 A2017U many times, with different guides. I always end up with a softbricked phone, having to restore to stock using MiFlash.
My bootloader is unlocked, i have stock recovery and stock rom for now.
Whenever i flash TWRP, either the signed one (from @tenfar) or unsigned (and up to date) ones, i can't go past the menu saying something like "your phone cant be checked for corruption, please lock your phone [...]" it just freeze. i did read somewhere that i should flash chainfire's root or a special .zip that, i guess, disabled some check that could prevent booting a phone with unsigned stuff/edited system (after flashing TWRP, so it could boot) that didn't work out. i think i found that information in some LineageOS thread here on XDA.
My ultimate goal would be to get a rooted stock nougat 7.1.1, up to date TWRP recovery and to be able to switch to LineageOS to try it out soon.
For what it is worth, i rooted many phones over the years, so while i'm no expert, i should be able to follow most of the steps you give me.
Thanks alot!

What version of TWRP did you flash first?

I have the same root problem i can not install in twrp install in twrp ok but su application displays no root cause i have latest twrp

KwesiJnr said:
What version of TWRP did you flash first?
Click to expand...
Click to collapse
this
https://forum.xda-developers.com/axon-7/development/recovery-official-twrp-zte-axon-7-t3515715
And @tenfar's signed one

KwesiJnr said:
What version of TWRP did you flash first?
Click to expand...
Click to collapse
this
https://forum.xda-developers.com/axon-7/development/recovery-official-twrp-zte-axon-7-t3515715
And @tenfar's signed one

Okay. Download and flash this one alone via fastboot and see what happens. This is one the I personally use. It is required for any of the newer versions to work properly.
twrp-3.0.2-2-a2017u.img
You can choose to rename it to just recovery.img, then:
1. fastboot flash recovery recovery.img
or
2.
if you choose to work with the same filename:
fastboot flash recovery twrp-3.0.2-2-a2017u.img
Select reboot to recovery from the bootloader menu now and try again.
Either way, should work fine. I know you mentioned you knew the basics, but just want to be sure.
Also forgot to mention. If TWRP works but you still can't get your phone to boot, you need to follow this guide here
You can start from the part that says:
-----------------------------------------------------
UPDATING FROM B20_Boot / B20 / B27 / B29 / B15(N)
-----------------------------------------------------
Again, that's the ROM I personally use if I want to go back to stock, not the one from the ZTE site.

Gonna try it and give feedback. thanks for taking time to help!
edit: im downloading the rom from the link you shared.
like you said, i can get TWRP to boot but not the phone.
So if i use full stock from ZTE, it can't boot with modified recovery?
edit 2: i don't know what worked, i think it might be the bootstack. or the rom by DrakenFX. now i can boot to the rom with a TWRP recovery installed. It worked, but i soft bricked again trying to flash SuperSU. So now i'm retrying with an updated TWRP.

I haven't tried that yet, but I really suspect that's the reason you're having problems. I rarely use pure stock ROMs. Like you, I'm not an expert in Android Development so I can't tell you why. Just been a flashaholic for years so made a few observations.

Which supersu are you installing? If you're swiping to the right in twrp, you need to install the dm-verity zip or supersu 2.79. There's some issues with newer builds.

Everything is working like a charm! Now im going to finally give lineageOS a try
I used Chainfire's SuperSU 2.79 stable.
Edit : Everything is working flawlessly! I'm running the lastest LineageOS nightly with root (Chainfire's 2.79). Followed their instruction and installation was smooth as butter. I should also point out i flashed the lastest official TWRP which seems more stable than the one @KwesiJnr suggested. The one he suggested was giving me some "can't read X partition" in red text everywhere in the log section, which the official one doesn't do. It was doing his job properly anyway though.
I can't thank @KwesiJnr enough, it helped me find the single mistake i was making.

lololo2 said:
Everything is working like a charm! Now im going to finally give lineageOS a try
I used Chainfire's SuperSU 2.79 stable
Click to expand...
Click to collapse
Glad you're up and running root. :good:

lololo2 said:
Everything is working like a charm! Now im going to finally give lineageOS a try
I used Chainfire's SuperSU 2.79 stable.
Edit : Everything is working flawlessly! I'm running the lastest LineageOS nightly with root (Chainfire's 2.79). Followed their instruction and installation was smooth as butter. I should also point out i flashed the lastest official TWRP which seems more stable than the one @KwesiJnr suggested. The one he suggested was giving me some "can't read X partition" in red text everywhere in the log section, which the official one doesn't do. It was doing his job properly anyway though.
I can't thank @KwesiJnr enough, it helped me find the single mistake i was making.
Click to expand...
Click to collapse
Yeah, like I mentioned before that was the base TWRP you needed to flash first, before any of the newer ones. You weren't intended to use it indefinitely.
There's a lot of Dev love for our device now and support is growing ... exciting new ROMs cropping up. Don't hesitate to try them out.

I tried flashing the official RRO rom (not treble) and I got stuck in a bootloop

I followed the instructions on this page and I got into a bootloop, so I flashed the stock android and it got me out of the bootloop, but i dont want to be on stock i want to be on RR so how can i not get bootlooped after flashing it? apperently im not the only one with this problem but nobody managed to fix it other than flashing the stock rom so I hope maybe somebody here can help me, btw i also flashed gapps after i flashed RR

YayJohn said:
I followed the instructions on this page and I got into a bootloop, so I flashed the stock android and it got me out of the bootloop, but i dont want to be on stock i want to be on RR so how can i not get bootlooped after flashing it? apperently im not the only one with this problem but nobody managed to fix it other than flashing the stock rom so I hope maybe somebody here can help me, btw i also flashed gapps after i flashed RR
Click to expand...
Click to collapse
I had that problem too when flashing the non-treble version. I'm not sure if this was your issue, but I had to boot back into TWRP and change slots in the reboot menu. Then it booted. So next time, you might give that a shot.
There is a step missing in the instructions too. There is no instruction on when to flash the gapps. Flashing them *after* Magisk worked for me.
If audio quality matters to you, I haven't found a custom ROM that sounds as good as stock, so I'm back on the stock ROM, even though I really liked RR.

Omineca said:
I had that problem too when flashing the non-treble version. I'm not sure if this was your issue, but I had to boot back into TWRP and change slots in the reboot menu. Then it booted. So next time, you might give that a shot.
There is a step missing in the instructions too. There is no instruction on when to flash the gapps. Flashing them *after* Magisk worked for me.
If audio quality matters to you, I haven't found a custom ROM that sounds as good as stock, so I'm back on the stock ROM, even though I really liked RR.
Click to expand...
Click to collapse
i already fixed it and it was the way u fixed it

I found solution for this just flash pie any security patch using mi flash tool which will automatically correct partition, it worked for me.

Flashing Custom rom i get stuck at fast boot but flashing xiaomi.eu works fine

Hi,
I've done countless steps and watched a ton of videos today but still can't answer this and it feels like I'm missing something simple.
I received my xiaomi 9t today and quickly unlocked the bootloader (no wait time possibly because I had a Mi8 before hand so I already had an account). I've since installed TWRP as well as tried OrangeFox Recovery and still can't get any custom roms to work, it goes directly to the fastboot screen. I can get back into TWRP and flash xiaomi.eu rom, no issue but as soon as I go to a custom rom I get fastboot.
I've flashed my Mi 8 countless times but I can't seem to get this to go. I've tried making sure the mounts were correct, I've flashed a disable forced encryption thing that I saw on some youtube videos and still nothing works.
Thanks in advance,
Joe

AbsoluteZero said:
Hi,
I've done countless steps and watched a ton of videos today but still can't answer this and it feels like I'm missing something simple.
I received my xiaomi 9t today and quickly unlocked the bootloader (no wait time possibly because I had a Mi8 before hand so I already had an account). I've since installed TWRP as well as tried OrangeFox Recovery and still can't get any custom roms to work, it goes directly to the fastboot screen. I can get back into TWRP and flash xiaomi.eu rom, no issue but as soon as I go to a custom rom I get fastboot.
I've flashed my Mi 8 countless times but I can't seem to get this to go. I've tried making sure the mounts were correct, I've flashed a disable forced encryption thing that I saw on some youtube videos and still nothing works.
Thanks in advance,
Joe
Click to expand...
Click to collapse
Hello, what OrangeFox version did you install?
You should try with R10.1_1 if you are using latest one.
If your phone is working with xiaomi.eu ROMs..., do you know xiaomi.eu ROMs are custom ROMs?
You generally only have to "Format Data" in TWRP before flashing another ROM (stock or custom).
Good luck!

Hi,
Thank you for the reply. I now have OrangeFox R10.1_1 installed. sorry I should've said other custom roms aren't working xiaomi.eu seems to be fine for some reason.
I just installed OrangeFox, reflashed xiaomi.eu and booted, worked fine. Then I went back, formatted data, rebooted back to recovery, flashed AOSPextended and gapps pico. Rebooted to system and it went to the fastboot screen again. I noticed it says during the AOSP install that "Root Status: Disabled" could that be a problem?
Thanks again for your help.

AbsoluteZero said:
Hi,
I've done countless steps and watched a ton of videos today but still can't answer this and it feels like I'm missing something simple.
I received my xiaomi 9t today and quickly unlocked the bootloader (no wait time possibly because I had a Mi8 before hand so I already had an account). I've since installed TWRP as well as tried OrangeFox Recovery and still can't get any custom roms to work, it goes directly to the fastboot screen. I can get back into TWRP and flash xiaomi.eu rom, no issue but as soon as I go to a custom rom I get fastboot.
I've flashed my Mi 8 countless times but I can't seem to get this to go. I've tried making sure the mounts were correct, I've flashed a disable forced encryption thing that I saw on some youtube videos and still nothing works.
Thanks in advance,
Joe
Click to expand...
Click to collapse
Use the official TWRP.

You should install latest stable xiaomi.eu rom or install latest China rom through MI flash, you need latest vendor partition for latest custom roms to boot properly.

jaggyjags said:
You should install latest stable xiaomi.eu rom or install latest China rom through MI flash, you need latest vendor partition for latest custom roms to boot properly.
Click to expand...
Click to collapse
I installed the latest Global Rom 11.0.5. via OrangeFox. I couldn't get it to go with Mi Flash. Not sure how to create the flash_all.bat and where to get all the files from. Is that the same? What are the steps from here?
Thank you

The same exact issue I am facing. Tried multiple custom roms and everything failed to boot only resulting in bricked or error. Even my previous budget phone redmi 3s was much better than this.

Stuck at bootloader--HELP!

Let's get this out of the way. I don't have much experience flashing ROMs. I've done it on a few phones, but I can't say I really understood what I was doing. I'm just good at following directions. So, I know about enough to get into trouble.
And ...I've gotten into trouble. My goal is to install LineageOS on my brother's Essential Phone. Based on directions I found here, I determined the active slot was b, so I installed TWRP on slot a. TWRP worked in recovery, but without touch. I then flashed twrp-3.2.3-0-mata.img to the non-active slot. Lastly, I sideloaded twrp-installer-mata-3.2.3-0.zip. I then changed the active slot back to b and rebooted. It now boots only to the bootloader and not to the OS. No matter what option I select--Start, Bootloader, Recovery--it reboots to the bootloader.
Any help to get out of this would be greatly appreciated.

Lineage can be installed more easily using Lineage's own Recovery rather than using TWRP. The Lineage Recovery is a pre-built replacement for your boot.img file.
Links for Lineage OS 17.1 (mata) and its corresponding Recovery (mata):
https://download.lineageos.org/mata
Link for Installation using Lineage Recovery:
https://wiki.lineageos.org/devices/mata/install
Hope this helps

MuddyDog said:
Lineage can be installed more easily using Lineage's own Recovery rather than using TWRP. The Lineage Recovery is a pre-built replacement for your boot.img file.
Links for Lineage OS 17.1 (mata) and its corresponding Recovery (mata):
https://download.lineageos.org/mata
Link for Installation using Lineage Recovery:
https://wiki.lineageos.org/devices/mata/install
Hope this helps
Click to expand...
Click to collapse
Thanks for the suggestion. I had actually already tried that. That's when I got desperate and tried generic TWRP. When I try to flash the Lineage recovery image I get a "No such partition" error, no matter which partition is active. I read somewhere that the flash boot_[letter] command might work, but I get "Couldn't parse partition size '0x'.

mcmc08 said:
Thanks for the suggestion. I had actually already tried that. That's when I got desperate and tried generic TWRP. When I try to flash the Lineage recovery image I get a "No such partition" error, no matter which partition is active. I read somewhere that the flash boot_[letter] command might work, but I get "Couldn't parse partition size '0x'.
Click to expand...
Click to collapse
Try:
Fastboot flash:raw boot_slot recovery.img

So, I found a solution. In order to overcome the errors I was getting, I had to use the raw command. So it was fastboot flash:raw boot [image file]. Once Lineage recovery was installed, I could boot to recovery and sideload Lineage.

MuddyDog said:
Try:
Fastboot flash:raw boot_slot recovery.img
Click to expand...
Click to collapse
I guess our replies crossed. At any rate, the raw command did the trick. Thanks for your help.

I'm having the same problem, and the raw command doesn't seem to help. Trying to install twrp causes it to be stuck in the bootloader. I somehow was able to install the lineage recovery, then to install the lineage OS. Because I am thinking of trying other ROMs, I decided to go back to trying the TWRP install. Now everything seems broken. When I use the a slot (where I installed TWRP), I'm stuck in the bootloader. When I shift to the b slot, I'm stuck on the Lineage splash page.
(By the way, while I was in the Lineage recovery at some point in the middle of all this, I also sideloaded the TWRP install zip.)
I've tried flashing the TWRP numerous times, and it always seems to work, but the result still is the same.
Any help would be appreciated.
Edit: I was able to get out of the loop by reflashing the Lineage Recovery, booting into that recovery, then doing a factory wipe. I was able to boot into Lineage. But why can't I successfully install TWRP? Or, I guess, alternately, is it possible to use the Lineage Recovery to flash different ROMs? (Sorry if this goes beyond the scope of the original question.)

Is Lineage using an Android 10 security update after January? January is the last update for Android 10 that TWRP worked with. Once Essential went belly up the TWRP devs just stopped updating when it broke with February security update. Anyway, I just thought I would mention it.

rocketrazr1999 said:
Is Lineage using an Android 10 security update after January? January is the last update for Android 10 that TWRP worked with. Once Essential went belly up the TWRP devs just stopped updating when it broke with February security update. Anyway, I just thought I would mention it.
Click to expand...
Click to collapse
I installed Lineageos directly on the february android stock version. (which is the last one from Essential)
Simply by following the tutorial on the LineageOS website.
Everything worked the first time.
So there is no need to switch back to the January android stock version. The image recovery provided by Lineage works very well.
And for your information LineageOS is updated almost every Monday.
Moreover the developers of the TWRP are not the developers of Essential. Company which closed at the end of February.
---------- Post added at 11:18 AM ---------- Previous post was at 11:14 AM ----------
KJannot said:
I'm having the same problem, and the raw command doesn't seem to help. Trying to install twrp causes it to be stuck in the bootloader. I somehow was able to install the lineage recovery, then to install the lineage OS. Because I am thinking of trying other ROMs, I decided to go back to trying the TWRP install. Now everything seems broken. When I use the a slot (where I installed TWRP), I'm stuck in the bootloader. When I shift to the b slot, I'm stuck on the Lineage splash page.
(By the way, while I was in the Lineage recovery at some point in the middle of all this, I also sideloaded the TWRP install zip.)
I've tried flashing the TWRP numerous times, and it always seems to work, but the result still is the same.
Any help would be appreciated.
Edit: I was able to get out of the loop by reflashing the Lineage Recovery, booting into that recovery, then doing a factory wipe. I was able to boot into Lineage. But why can't I successfully install TWRP? Or, I guess, alternately, is it possible to use the Lineage Recovery to flash different ROMs? (Sorry if this goes beyond the scope of the original question.)
Click to expand...
Click to collapse
Which Rom would you like to install instead of Lineage?

groovebox said:
Which Rom would you like to install instead of Lineage?
Click to expand...
Click to collapse
I'm of two minds; one is just to go with something stock android-ish, which leads me to Evolution X or Pixel Experience. The other is to cut myself from Google entirely, which leads me to /e/. I'm also looking at Paranoid, just because it looks like it's stable. Any thoughts on any of those?
I had updated Essential to the February update; would that be why TWRP would not successfully install on my phone?
Would that still be true if I had flashed Lineage?

KJannot said:
I'm of two minds; one is just to go with something stock android-ish, which leads me to Evolution X or Pixel Experience. The other is to cut myself from Google entirely, which leads me to /e/. I'm also looking at Paranoid, just because it looks like it's stable. Any thoughts on any of those?
I had updated Essential to the February update; would that be why TWRP would not successfully install on my phone?
Would that still be true if I had flashed Lineage?
Click to expand...
Click to collapse
Paranoid Android: What I heard is VoLTE broken, if you enable it, SMS/MMS might not work properly.
Evolution: No update in Android 10 since August, not sure they contine to support Essential phone for Android 11
Pixel Experience: I don't think they Anroid 10 for Essential phone, only official Anroid 9 which is too old
TWRP issue: You need to go back to Jan stock rom before going to any rom if you just flashed LOS
What current stable rom with Nov security update: I'm using crDroid 6.12 (unofficial release but from XDA reliable source)
https://forum.xda-developers.com/essential-phone/development/rom-crdroid-v6-7-t4129739