Related
Phone: Samsung Galaxy Core Prime
MetroPCS
Model: SM-G360T1
ROM and Kernal: Stock
Issue: Touchscreen doesn't work in TWRP.
Links:
Where I got TWRP: https://dl.twrp.me/coreprimelte/
The guide I followed: http://www.android.gs/install-twrp-recovery-v3-0-0-on-samsung-galaxy-core-prime/
I got this phone from a friend. I tried to install TWRP via ODIN, but I've had some trouble. Initially, when I installed TWRP it didn't appear after I rebooted the phone. After doing some research, I found that this is normal for stock ROM's, and that they tend to replace any custom recovery with the stock one. I learned that in order to access TWRP, I need to remove the batter before rebooting, and then reboot directly into TWRP without letting the OS see the light of day. But when I get to TWRP, the touchscreen breaks. I can't interact with anything. I can still boot into the operating system just fine, but doing so removes the recovery, and I can't interact with TWRP outside of locking it by using the power button. I think this issue could be solved by installing a custom ROM, but I don't know if that's even possible without TWRP. This seems to be a loop of nothing, never going anywhere.
All I need is for the touchscreen to work in TWRP, I can handle the rest from there. Thank you for any help, and Happy Holidays!
Edit: After further research, I've discovered that the problem could lay in the recovery I'm using. I'm trying to install the latest TWRP version found in the link above, but I've tried almost all of them. Is there any information on any specific version of TWRP I should use?
Today I wanted to install the lineage os, but, to ensure, I installed the stock rom in my moto g4 plus.
I wiped dalvik, system, data and cache.
Then I flashed the rom and the gapps, but when I did the reboot the cell phone was in an infinite loop, but not normal, the bootanimation of the lineage appears but it never stops.
what do I do??
Sorry for the spelling mistakes, I used google translate
Try lineage oms. https://forum.xda-developers.com/showthread.php?p=69421261
Sent from my Moto G4 using Tapatalk
robot_head said:
Try lineage oms. https://forum.xda-developers.com/showthread.php?p=69421261
Sent from my Moto G4 using Tapatalk
Click to expand...
Click to collapse
I can't acces my custom recovery and can't install trough my computer
advanced_gamerBR said:
I can't acces my custom recovery and can't install trough my computer
Click to expand...
Click to collapse
Which stock ROM and custom recovery did you install, by the way?
echo92 said:
Which stock ROM and custom recovery did you install, by the way?
Click to expand...
Click to collapse
I installed Lineage OS 14.1 2017/02/21 nightly
The stock rom is this https://mega.nz/#!2skAzDKL!9VB2h6GpbrqINSpsiMLoenZEpuuCbTVGi8QtR8lWKf0
And the custom recovery is TWRP 3.0.2-0
advanced_gamerBR said:
I installed Lineage OS 14.1 2017/02/21 nightly
The stock rom is this https://mega.nz/#!2skAzDKL!9VB2h6GpbrqINSpsiMLoenZEpuuCbTVGi8QtR8lWKf0
And the custom recovery is TWRP 3.0.2-0
Click to expand...
Click to collapse
Thanks, can I ask what region/what device you have as well? I'm just wondering if that's the correct stock firmware for your device/region. Did you let your device update on OTA before flashing the LineageOS build? Are you able to roll back to a backup of your Marshmallow installation?
Also, there's a newer version of TWRP available: https://forum.xda-developers.com/mo...covery-twrp-3-0-2-r3-moto-g4-g4-plus-t3494337 Might be worth looking into installing given the TWRP version you've installed hasn't been maintained in a while. TWRP 3.0.3n2 is a good option to go for, since it's running stably for me.
Finally, though some bugs appear to have been fixed in the latest Lineage OS nightlies, might be worth using the 13/02 build (or robot_head's suggestion of the unofficial Lineage OMS ROM) to rule out any issues with the ROM, until at least we can get your phone booting again with a custom ROM.
echo92 said:
Thanks, can I ask what region/what device you have as well? I'm just wondering if that's the correct stock firmware for your device/region. Did you let your device update on OTA before flashing the LineageOS build? Are you able to roll back to a backup of your Marshmallow installation?
Also, there's a newer version of TWRP available: https://forum.xda-developers.com/mo...covery-twrp-3-0-2-r3-moto-g4-g4-plus-t3494337 Might be worth looking into installing given the TWRP version you've installed hasn't been maintained in a while. TWRP 3.0.3n2 is a good option to go for, since it's running stably for me.
Finally, though some bugs appear to have been fixed in the latest Lineage OS nightlies, might be worth using the 13/02 build (or robot_head's suggestion of the unofficial Lineage OMS ROM) to rule out any issues with the ROM, until at least we can get your phone booting again with a custom ROM.
Click to expand...
Click to collapse
I think that's the correct stock firmware because I already installed it before and there wasn't bugs .
The problem is I can't rool back to a backup because I can't access de TWRP or use the fastboot.
Thank you for helping me, I was able to access TWRP when my battery ran out, which interrupted the loop
advanced_gamerBR said:
I think that's the correct stock firmware because I already installed it before and there wasn't bugs .
The problem is I can't rool back to a backup because I can't access de TWRP or use the fastboot.
Click to expand...
Click to collapse
Hmm, so what happens if you power off your phone by pressing the power button for 2-3 [edit: minutes] (credit: https://forum.xda-developers.com/showpost.php?p=70973812&postcount=5), as this may cause a hard reset and possibly break the bootloop?
What do you mean by fastboot not beng useable, as in your device does not show up in ADB or that you cannot boot into fastboot?
Alternatively, are you able to access the bootloader/fastboot mode by powering off, then holding down the power and volume down keys? If so, you may be able to re-flash your stock ROM as before.
echo92 said:
Hmm, so what happens if you power off your phone by pressing the power button for 2-3 seconds (credit: https://forum.xda-developers.com/showpost.php?p=70973812&postcount=5), as this may cause a hard reset and possibly break the bootloop?
What do you mean by fastboot not beng useable, as in your device does not show up in ADB or that you cannot boot into fastboot?
Alternatively, are you able to access the bootloader/fastboot mode by powering off, then holding down the power and volume down keys? If so, you may be able to re-flash your stock ROM as before.
Click to expand...
Click to collapse
I said I could not use fastboot because I was stuck on the Lineage loading screen
It was like if the boot animation was infinite, then when I tried to use the fastboot the cell phone was not recognized.
But the "loop" stopped when the battery ran out, so I was able to initialize the TWRP
advanced_gamerBR said:
I said I could not use fastboot because I was stuck on the Lineage loading screen
It was like if the boot animation was infinite, then when I tried to use the fastboot the cell phone was not recognized.
But the "loop" stopped when the battery ran out, so I was able to initialize the TWRP
Click to expand...
Click to collapse
So you're back into TWRP now? Okay, are you restoring your backup or re-flashing your stock ROM? I'd like to check your device can boot normally again and is up to date before trying again with the custom ROM.
By the way, I made an error in my last post - I miswrote how long you hold the power button down for, it's 2-3 minutes and should achieve the same as when your battery ran out - allowing you to boot back into TWRP.
echo92 said:
So you're back into TWRP now? Okay, are you restoring your backup or re-flashing your stock ROM? I'd like to check your device can boot normally again and is up to date before trying again with the custom ROM.
By the way, I made an error in my last post - I miswrote how long you hold the power button down for, it's 2-3 minutes and should achieve the same as when your battery ran out - allowing you to boot back into TWRP.
Click to expand...
Click to collapse
I've re-flashed the stock rom and it's working well
First of all why did this happen, presumably I wasn't doing anything wrong or uninformed. I just unlocked the bootloader successfully, afterward as many threads claimed I flashed twrp-3.3.1-2-davinci-fix, and now it simply wont boot neither to system nor twrp. Why did this happen?
Does anyone know how to fix this? Thank you!
Mi 9T (M1903F10G)
Did you try to power off and then turn back on holding power and volume up? I had this issue yesterday but doing the vol up and power got me to twrp then did format and it booted up
cmlucht said:
Did you try to power off and then turn back on holding power and volume up? I had this issue yesterday but doing the vol up and power got me to TWRP then did format and it booted up
Click to expand...
Click to collapse
Thank you for your reply. You can't even power off, it will simply bootloop forever into fastboot. Nonetheless I managed to fix it by flashing fastboot ROM using MIFlash, but man, didn't expect root solutions to be this complicated, unstable, and outdated for our beloved Mi 9T. I simply want to achieve root in the stock rom, and wasted 7 hours yesterday and still got nowhere. I come from a classic LG G2, when things were much simple and straight forward back then. You can stop reading here, but now I had to:
Wait 1 week for bootloader unlock.
Flash TWRP, which soft bricked my phone right away. Why on earth, a recovery image provided in many reliable tutorials from multiple sources cause soft-brick in the second step is beyond my comprehension. I am still genuinely curious why did this happen, and why such a broken image is still circulating here?
Then I had to inform myself all about Anti Rollback, in order to prevent it happening, and concluded that MiFlash is safe, so I got MiFlash and a fastboot rom.
Apparently Mi Flash is terribly buggy and kept showing .net error exceptions because a "LOG" folder was missing in root folder, so let's waste one hour scratching our heads what the hell is happening because the developer missed a simple MkDir line during development.
After creating LOG folder, and installing drivers, couldn't flash any fastboot ROM because my 9T antiroll back number is 1 while fastboot rom ARB index was 0.
Then it appears that this error has actually nothing to do with ARB, but it is because I had to a) start MiFlash from C:\, b) remove name spaces in target address and c) shorten fastboot ROM folder name. So I had to get all these 3 variables right in order to resurrect my phone. MiFlash terrible programming didn't stop at step 4) but it extends into showing entirely confusing ARB errors that have nothing to with the real problem, rather petty programming bugs such as folder naming.
Finally managed to boot up 9T, and we're back at square one.
Afterward successfully flashed mauronofrio TWRP including vbmeta and got recovery working.
I decided to try out few custom ROMs since all my data were erased anyway, but it appears my system was encrypted and TWRP showed encrypted alphanumeric characters, so I had to format data in order to flash files.
Now every-time I flash stock ROM .zip I lose TWRP, and every-time I reflash mauronofrio TWRP I end up in recovery bootloop, and so I can't manage to have both at same time in order to move with the Magisk flash.
10 steps and 7 hours later and still got nowhere, just risked bricking my phone.
Now we have to deal with
a) bootloader wait,
b) twrp encryption mess,
c) anti roll back risk,
d) buggy MiFlash
e) safety net measures
f) no custom ROMs that are pre-rooted and simple
g) dependency of stock ROM files - meaning you can't wipe everything including system and just flash custom ROM .zips, like I used to do with 5 android phones before this one. Now you are somehow dependent on original ROM files which probably means you will have to base install stock MI before you flash anything Xiaomi.EU, Evolution X, PixelExperience etc. When did things get so complicated? It seems every year new limitations are introduced and the sheer combination to get them all right give headaches.
Anyway, all I want is to install latest stock ROM from TWRP and keep TWRP so I can also flash Magisk. In other words, how to simply have a rooted stock?
Your mistake is to not use Official TWRP instead of an old TWRP version...
Micdu70 said:
Your mistake is to not use Official TWRP instead of an old TWRP version...
Click to expand...
Click to collapse
Thanks for your reply! Yes, that must have been it. Those outdated tutorials should be removed.
Now I flashed miui_DAVINCIEEAGlobal_V11.0.4.0.QFJEUXM through latest TWRP, but it removed TWRP. When I reflash latest TWRP then it ends up in bootloop.
EDIT: Ended up reflashing all over again using MiFlash. Now the only problem remaining is which version of Magisk is compatible with miui_DAVINCIEEAGlobal_V11.0.4.0.QFJEUXM?
What are you flashing with? I am now using xiaomitools v2 and it installed twrp and magisk with no problems.
I flashed the EU custom stable, I was global but I wanted to compare the 2 and I like the EU better.
I came from a non rootable lg g7.
I have not flashed custom ROMs since my old Galaxy note days.
cmlucht said:
What are you flashing with? I am now using xiaomitools v2 and it installed twrp and magisk with no problems.
I flashed the EU custom stable, I was global but I wanted to compare the 2 and I like the EU better.
I came from a non rootable lg g7.
I have not flashed custom ROMs since my old Galaxy note days.
Click to expand...
Click to collapse
Never heard of XiaomiTools v2, it seems like a great alternative. I used buggy MiFlash to flash fastboot ROM, flashed TWRP, then got a bootloop, formatted data from TWRP and flashed Magisk. It seems everything is working fine now, but in the future I'll make sure to check XiaomiTools v2.
I never used stock ROMs in any of my past phones, first thing I did when I bought a new phone is unlock bootloader and install Lineage or Cyanogenmod back in the days. But somehow I like MIUI so all I needed was root.
It is hard to believe that there are actually phones that have no root at all.
blackmatrix64 said:
Thank you for your reply. You can't even power off, it will simply bootloop forever into fastboot. Nonetheless I managed to fix it by flashing fastboot ROM using MIFlash, but man, didn't expect root solutions to be this complicated, unstable, and outdated for our beloved Mi 9T. I simply want to achieve root in the stock rom, and wasted 7 hours yesterday and still got nowhere. I come from a classic LG G2, when things were much simple and straight forward back then. You can stop reading here, but now I had to:
Wait 1 week for bootloader unlock.
Flash TWRP, which soft bricked my phone right away. Why on earth, a recovery image provided in many reliable tutorials from multiple sources cause soft-brick in the second step is beyond my comprehension. I am still genuinely curious why did this happen, and why such a broken image is still circulating here?
Then I had to inform myself all about Anti Rollback, in order to prevent it happening, and concluded that MiFlash is safe, so I got MiFlash and a fastboot rom.
Apparently Mi Flash is terribly buggy and kept showing .net error exceptions because a "LOG" folder was missing in root folder, so let's waste one hour scratching our heads what the hell is happening because the developer missed a simple MkDir line during development.
After creating LOG folder, and installing drivers, couldn't flash any fastboot ROM because my 9T antiroll back number is 1 while fastboot rom ARB index was 0.
Then it appears that this error has actually nothing to do with ARB, but it is because I had to a) start MiFlash from C:\, b) remove name spaces in target address and c) shorten fastboot ROM folder name. So I had to get all these 3 variables right in order to resurrect my phone. MiFlash terrible programming didn't stop at step 4) but it extends into showing entirely confusing ARB errors that have nothing to with the real problem, rather petty programming bugs such as folder naming.
Finally managed to boot up 9T, and we're back at square one.
Afterward successfully flashed mauronofrio TWRP including vbmeta and got recovery working.
I decided to try out few custom ROMs since all my data were erased anyway, but it appears my system was encrypted and TWRP showed encrypted alphanumeric characters, so I had to format data in order to flash files.
Now every-time I flash stock ROM .zip I lose TWRP, and every-time I reflash mauronofrio TWRP I end up in recovery bootloop, and so I can't manage to have both at same time in order to move with the Magisk flash.
10 steps and 7 hours later and still got nowhere, just risked bricking my phone.
Now we have to deal with
a) bootloader wait,
b) twrp encryption mess,
c) anti roll back risk,
d) buggy MiFlash
e) safety net measures
f) no custom ROMs that are pre-rooted and simple
g) dependency of stock ROM files - meaning you can't wipe everything including system and just flash custom ROM .zips, like I used to do with 5 android phones before this one. Now you are somehow dependent on original ROM files which probably means you will have to base install stock MI before you flash anything Xiaomi.EU, Evolution X, PixelExperience etc. When did things get so complicated? It seems every year new limitations are introduced and the sheer combination to get them all right give headaches.
Anyway, all I want is to install latest stock ROM from TWRP and keep TWRP so I can also flash Magisk. In other words, how to simply have a rooted stock?
Click to expand...
Click to collapse
Hey, I'm facing the same issue you faced here. Waited 7 days to unlock bootloader, after unlocking it, flashed a twrp i found on one of the youtube tutorials. Immediate bootloop. Im fairly new to all of this, and dont understand what certain words even mean tbh. Do you mind guiding me in fixing my phone? Any help would be really appreciated. Thank you.
blackmatrix64 said:
Never heard of XiaomiTools v2, it seems like a great alternative. I used buggy MiFlash to flash fastboot ROM, flashed TWRP, then got a bootloop, formatted data from TWRP and flashed Magisk. It seems everything is working fine now, but in the future I'll make sure to check XiaomiTools v2.
I never used stock ROMs in any of my past phones, first thing I did when I bought a new phone is unlock bootloader and install Lineage or Cyanogenmod back in the days. But somehow I like MIUI so all I needed was root.
It is hard to believe that there are actually phones that have no root at all.
Click to expand...
Click to collapse
i miss the Cyanogenmod days
Hello lovely people!
I have a bought-when-new OP5 (A5000) with OxygenOS 4.5.6 and Android 7.1.1. I flashed it with TWRP 3.1.1-0, rooted it, and have been using it happily ever since.
However, because some apps I'd like to use require a more modern version of Android I'd now like to upgrade to a "modern" OS -- e.g. Pixel Experience or LineageOS, with good security -- ideally without losing all my data & apps. What's the best way to proceed? (What 3rd-party mod is best for battery life?)
Thank you very much for your help!
Dirty upgrade is not the best choice. However, you can first install 5.1.4 and then you can install latest 9.0.11 or 10.0.0
PierreVicquery02 said:
Dirty upgrade is not the best choice. However, you can first install 5.1.4 and then you can install latest 9.0.11 or 10.0.0
Click to expand...
Click to collapse
Thank you very much for this. I agree with that "not the best choice" statement. Here's my evenings' experiences:
-- Made nandroid with TWRP; also used migrate to generate ∆zips
– Flashed updated TWRP when ordinary TWRP didn't recognise the 5.4.1 oneplus rom as being a oneplus 5
-- 3.3.1 twrp and bluesparx didn't work; wouldn't lead to a fastboot screen or anything other than a blue LED. Fortunately 'fastboot recovery' while rebooting holding down worked (eventually -- most of the time it wasn't detected).
-- Reflashed a point upgrade to the version I had, 3.1.1.-1 which did at least let fastboot appear as before.
-- Still couldn't flash the right OTA image
-- Went with Codeworkx recovery ("Cheeseburger dumplings"),https://forum.xda-developers.com/on...overy-twrp-3-2-1-0-oreo-oxygenos-5-0-t3725723 specifically 3.2.1-0 (it worked)
-- Installed OTA without zip signature verification after manually verifying the md5sum
-- Saw firmware patches (phew!)
-- wiped dalvik / cache
-- Rebooted, logged in, waited. Took a *very* long time showing the spinning dots.
-- Realised that the ring was going around in a loop, similarly to this link: https://forum.xda-developers.com/oneplus-5/help/qa-help-thread-newbies-post-t3624656/post77294880
-- Noted that TWRP had been replaced by the stock recovery.
Couldn't stop the bootloop despite cache wipes / etc. Did a factory wipe.
-- Reflashed twrp 3.2.
-- Downloaded OxygenOS 9.0.11. Installed magisk 20.4 and the manager.
-- Logged in to 9.0.11. Let stuff set up, including encryption, which I wanted. Took a while. Phone obviously did a firmware upgrade.
-- Reflashed blu_sparks (most recent twrp + encryption support)
-- Finally was able to reboot into blu_sparks without error
-- Used a previously made Migrate backup to restore data & apps.
-- Have a slightly updated daily driver. Will flash 10 as soon as it's not in beta to try and minimise pain in the future and/or when I have another free few hours...
Would highly recommend anyone in the same situation to do a proper backup, bite the bullet. Make detailed backups. Test them. Wipe the thing, and don't worry too much about it. Migrate really is a brilliant app.
I hope that helps anyone else in my situation
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