Hi, All . . .
I believe it would be appropriate to label me as an intermediate-to-advanced newbie. That is, I'm not clueless, but there are lots of blind spots in my knowledge.
I just bought a 6P and while I've been waiting for my SIM card to arrive, I've gone ahead and rooted, installed TWRP 3.0.3-0, and made a few customizations here and there. One thing I don't understand is the significance of the vendor image now. I'm coming from a 6 where that wasn't an issue. Also, in the rooting instructions it indicates that one should "find the correct vendor image," without really indicating how one can go about learning which one is "right." In the end, I took the latest one I could find, because my phone did an OTA update and I simply reasoned that I should match latest with latest.
In any case, I want to install MultiROM and I keep running into this problem:
The MultiROM version of TWRP doesn't load. It hangs on the splash screen. The version it uses is 3.0.2-0, so I suspected it was an issue with that. I flashed the TWRP-only recovery version 3.0.2-0 after having no luck, and it wouldn't load beyond the splash screen, either. Finally, I re-flashed the stock system recovery and tried flashing both the 3.0.2-0 TWRP-only recovery and the MultiROM-integrated version, both without success.
Is there something about the move from 3.0.2-0 to 3.0.3-0 that makes a rollback impossible. Is it even necessary?
Re-flashing 3.0.3-0 solved the problem of basic functionality. TWRP comes right up after I do that. But I can't get the MultiROM recovery or the 3.0.2-0 TWRP recovery to work no matter what I try.
My phone says that the vendor version is N4F26J and my "build number" is N6F26Q, and I'm running PureNexus 7.1.1. Those two numbers appear like a mismatch to me, but everything I could find indicated that the vendor version I have, being the latest, is the right one.
What am I missing? Can someone with more experience solve this puzzle, or at least lead me in a direction where I know which questions to ask on my own and can get things to start making sense again?
I appreciate your help! Thanks!
KilgoreTrout71 said:
Hi, All . . .
I believe it would be appropriate to label me as an intermediate-to-advanced newbie. That is, I'm not clueless, but there are lots of blind spots in my knowledge.
I just bought a 6P and while I've been waiting for my SIM card to arrive, I've gone ahead and rooted, installed TWRP 3.0.3-0, and made a few customizations here and there. One thing I don't understand is the significance of the vendor image now. I'm coming from a 6 where that wasn't an issue. Also, in the rooting instructions it indicates that one should "find the correct vendor image," without really indicating how one can go about learning which one is "right." In the end, I took the latest one I could find, because my phone did an OTA update and I simply reasoned that I should match latest with latest.
In any case, I want to install MultiROM and I keep running into this problem:
The MultiROM version of TWRP doesn't load. It hangs on the splash screen. The version it uses is 3.0.2-0, so I suspected it was an issue with that. I flashed the TWRP-only recovery version 3.0.2-0 after having no luck, and it wouldn't load beyond the splash screen, either. Finally, I re-flashed the stock system recovery and tried flashing both the 3.0.2-0 TWRP-only recovery and the MultiROM-integrated version, both without success.
Is there something about the move from 3.0.2-0 to 3.0.3-0 that makes a rollback impossible. Is it even necessary?
Re-flashing 3.0.3-0 solved the problem of basic functionality. TWRP comes right up after I do that. But I can't get the MultiROM recovery or the 3.0.2-0 TWRP recovery to work no matter what I try.
My phone says that the vendor version is N4F26J and my "build number" is N6F26Q, and I'm running PureNexus 7.1.1. Those two numbers appear like a mismatch to me, but everything I could find indicated that the vendor version I have, being the latest, is the right one.
What am I missing? Can someone with more experience solve this puzzle, or at least lead me in a direction where I know which questions to ask on my own and can get things to start making sense again?
I appreciate your help! Thanks!
Click to expand...
Click to collapse
Hey there,
Regarding your TWRP 3.0.2-0/MultiRom 3.0.2-0 and TWRP 3.0.3 issues, check out post #1152 in the official TWRP 6P thread. If there is an update to MR to support Nougat encryption, you'll just have to follow the MR thread or Github for updates.
Here's a brief explainer from my guide in the Nexus 5X forums about Vendor.img:
9. After updating my ROM, I get this message on every boot: "There's an internal problem with your device. Contact your manufacturer."
This warning signifies a mismatched vendor and system partition. The vendor partition was integrated in the system partition for previous Nexus devices but is now a separate partition that must be flashed for each Google security update. Download a factory image and update your vendor partition using fastboot so that it matches your rom's OS base. If you have a file explorer installed on your phone, you can determine which vendor.img is installed by navigating to /vendor/build.prop and clicking on the build.prop. The specific vendor installed will be a combination of six numbers and letters listed in all capitals (example: NMF26F) in the ro.vendor.build.fingerprint line.
Vendor.img is specific to each OTA and contains proprietary binaries for the phone. The phone will fail to boot if you mismatch the vendor.img with a different OS base. For instance, a 6.0 Marshmallow vendor.img will not allow your phone to boot on 7.0 Nougat.
Click to expand...
Click to collapse
Hope this clears things up for you!
Edit: Also, certain rom teams keep an up to date listing of vendor.img available on their websites. Usually this is detailed in the rom thread OP. Find a reliable thread and bookmark their vendor.img downloads, if not download the factory image each month and extract the img.
SlimSnoopOS said:
Hey there,
Regarding your TWRP 3.0.2-0/MultiRom 3.0.2-0 and TWRP 3.0.3 issues, check out post #1152 in the official TWRP 6P thread. If there is an update to MR to support Nougat encryption, you'll just have to follow the MR thread or Github for updates.
Here's a brief explainer from my guide in the Nexus 5X forums about Vendor.img:
Hope this clears things up for you!
Edit: Also, certain rom teams keep an up to date listing of vendor.img available on their websites. Usually this is detailed in the rom thread OP. Find a reliable thread and bookmark their vendor.img downloads, if not download the factory image each month and extract the img.
Click to expand...
Click to collapse
Thanks so much for the swift reply! I'll check these links out right away. I'm sure they will fill in the gaps for me.
Best,
KT
KilgoreTrout71 said:
Hi, All . . .
I believe it would be appropriate to label me as an intermediate-to-advanced newbie. That is, I'm not clueless, but there are lots of blind spots in my knowledge.
I just bought a 6P and while I've been waiting for my SIM card to arrive, I've gone ahead and rooted, installed TWRP 3.0.3-0, and made a few customizations here and there. One thing I don't understand is the significance of the vendor image now. I'm coming from a 6 where that wasn't an issue. Also, in the rooting instructions it indicates that one should "find the correct vendor image," without really indicating how one can go about learning which one is "right." In the end, I took the latest one I could find, because my phone did an OTA update and I simply reasoned that I should match latest with latest.
In any case, I want to install MultiROM and I keep running into this problem:
The MultiROM version of TWRP doesn't load. It hangs on the splash screen. The version it uses is 3.0.2-0, so I suspected it was an issue with that. I flashed the TWRP-only recovery version 3.0.2-0 after having no luck, and it wouldn't load beyond the splash screen, either. Finally, I re-flashed the stock system recovery and tried flashing both the 3.0.2-0 TWRP-only recovery and the MultiROM-integrated version, both without success.
Is there something about the move from 3.0.2-0 to 3.0.3-0 that makes a rollback impossible. Is it even necessary?
Re-flashing 3.0.3-0 solved the problem of basic functionality. TWRP comes right up after I do that. But I can't get the MultiROM recovery or the 3.0.2-0 TWRP recovery to work no matter what I try.
My phone says that the vendor version is N4F26J and my "build number" is N6F26Q, and I'm running PureNexus 7.1.1. Those two numbers appear like a mismatch to me, but everything I could find indicated that the vendor version I have, being the latest, is the right one.
What am I missing? Can someone with more experience solve this puzzle, or at least lead me in a direction where I know which questions to ask on my own and can get things to start making sense again?
I appreciate your help! Thanks!
Click to expand...
Click to collapse
Your vendor image and build number do sound like they are mismatched. If you can't find the vendor image you need on XDA you can find the matching build on the Google site, download the whole factory image and unzip it and get the vendor image that way.
I believe TWRP 3.0.2-0 was buggy. I'm not familiar with Multi rom and I don't know why they would use that build. You should be using 3.0.2-3 or 3.0.3-0.
I personally wouldn't install a custom ROM before activating the phone. I know a couple people have reported in the past that they were unable to activate their phone on a custom ROM. Hopefully you won't have that issue.
jhs39 said:
I believe TWRP 3.0.2-0 was buggy. I'm not familiar with Multi rom and I don't know why they would use that build. You should be using 3.0.2-3 or 3.0.3-0..
Click to expand...
Click to collapse
MultiRom support for this device was released when Marshmallow was out. So MR33 is based on the Marshmallow branch and ships with 3.0.2. The developer just isn't ready to release support for Nougat 7.0 and couple that with the issues of TWRP 3.0.2-x. He's actively pushing commits to support Nougat.
Sent from my Nexus 5X using Tapatalk
jhs39 said:
Your vendor image and build number do sound like they are mismatched. If you can't find the vendor image you need on XDA you can find the matching build on the Google site, download the whole factory image and unzip it and get the vendor image that way.
I believe TWRP 3.0.2-0 was buggy. I'm not familiar with Multi rom and I don't know why they would use that build. You should be using 3.0.2-3 or 3.0.3-0.
I personally wouldn't install a custom ROM before activating the phone. I know a couple people have reported in the past that they were unable to activate their phone on a custom ROM. Hopefully you won't have that issue.
Click to expand...
Click to collapse
Thanks for the input! I actually just got my card and some of the activation seems complete. (I got my voice mails and so on, but no data connection yet.) I didn't have a problem with the Nexus 6 on PureNexus, but we'll have to see how this one plays out. I'm not able to call over WiFi yet.
KilgoreTrout71 said:
Thanks for the input! I actually just got my card and some of the activation seems complete. (I got my voice mails and so on, but no data connection yet.) I didn't have a problem with the Nexus 6 on PureNexus, but we'll have to see how this one plays out. I'm not able to call over WiFi yet.
Click to expand...
Click to collapse
It might just take a while for the service to go through. Good luck.
I'm having a very hard time flashing LineageOS to my phone. I'm using the official Twrp. I getting my builds from this site
https://www-cyanogenmods-org.cdn.am...d-devices-list-and-downloads-android-pie-9-0/
I install the bill then I go to restart the phone. The devices is telling me no OS.
Please help.
Sent from my Pixel 2 XL using Tapatalk
You may want to check out the Essential Dev Telegram Group here https://t.me/EssentialPH1DEV not some random site on the internet. There you can find Lineage as well as other ROMs.
TheGman125 said:
I'm having a very hard time flashing LineageOS to my phone. I'm using the official Twrp. I getting my builds from this site
https://www-cyanogenmods-org.cdn.am...d-devices-list-and-downloads-android-pie-9-0/
I install the bill then I go to restart the phone. The devices is telling me no OS.
Please help.
Click to expand...
Click to collapse
Are you sure you installed the ROM, Gapps, etc to the active slot (either A or B) and also made sure you rebooted to the correct, active slot within TWRP? That is typically an area where some people have had issues. If this is the problem, read up on how slots work here: https://mata.readthedocs.io/en/latest/ -Ignore the "Installing LOS" section, as it's outdated. There are also tons of posts regarding the usage of slots in several threads, including two of them below.
This thread has a lot of useful information, but you'll want to search around for current solutions since things have changed over time. Especially with TWRP, slots and which adb/fastboot environment is being used. https://forum.xda-developers.com/es...ooting-essential-ph-1-magisk-t3701976/page223
Which version of TWRP are you using? I know you mentioned the official version, but going by your link, it's showing to use an older version. So is it latest permanent solution (within the development section) or the older temporary version (twrp_11)? Latest: https://forum.xda-developers.com/es...official-twrp-3-2-3-0-essential-ph-1-t3840931
That link you provided is quite unorganized and has some outdated information for our device, especially when it comes to TWRP, from what I gathered. The link I've used for LOS 16 builds is the one from the LOS thread (within the OP) in the development section. https://updater.invisiblek.org/mata
There are also several custom Pie builds for the PH-1 on the Mata Releases Telegram group, in case you want to check that out. Also be sure that you're on the latest Essential firmware. https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681 - I'd recommend using a version that has the boot.img patched already (it'll say in the post and filename) or go fully back to stock (BTS) to start from scratch if needed. Using the December firmware for one or both. And when flashing firmware, you'll want to make sure it's being flashed to both slots. It will do that for you automatically if you use a BTS package (using the flash_all.bat file).
robertbarber said:
You may want to check out the Essential Dev Telegram Group here https://t.me/EssentialPH1DEV not some random site on the internet. There you can find Lineage as well as other ROMs.
Click to expand...
Click to collapse
Thank you for the link. I will check it out.
Sent from my Pixel 2 XL using Tapatalk
hx3 said:
Are you sure you installed the ROM, Gapps, etc to the active slot (either A or B) and also made sure you rebooted to the correct, active slot within TWRP? That is typically an area where some people have had issues. If this is the problem, read up on how slots work here: https://mata.readthedocs.io/en/latest/ -Ignore the "Installing LOS" section, as it's outdated. There are also tons of posts regarding the usage of slots in several threads, including two of them below.
This thread has a lot of useful information, but you'll want to search around for current solutions since things have changed over time. Especially with TWRP, slots and which adb/fastboot environment is being used. https://forum.xda-developers.com/es...ooting-essential-ph-1-magisk-t3701976/page223
Which version of TWRP are you using? I know you mentioned the official version, but going by your link, it's showing to use an older version. So is it latest permanent solution (within the development section) or the older temporary version (twrp_11)? Latest: https://forum.xda-developers.com/es...official-twrp-3-2-3-0-essential-ph-1-t3840931
That link you provided is quite unorganized and has some outdated information for our device, especially when it comes to TWRP, from what I gathered. The link I've used for LOS 16 builds is the one from the LOS thread (within the OP) in the development section. https://updater.invisiblek.org/mata
There are also several custom Pie builds for the PH-1 on the Mata Releases Telegram group, in case you want to check that out. Also be sure that you're on the latest Essential firmware. https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681 - I'd recommend using a version that has the boot.img patched already (it'll say in the post and filename) or go fully back to stock (BTS) to start from scratch if needed. Using the December firmware for one or both. And when flashing firmware, you'll want to make sure it's being flashed to both slots. It will do that for you automatically if you use a BTS package (using the flash_all.bat file).
Click to expand...
Click to collapse
Thank you for everything. I believe the build you provided will work great.
Sent from my Pixel 2 XL using Tapatalk
TheGman125 said:
Thank you for everything. I believe the build you provided will work great.
Click to expand...
Click to collapse
I hope so. If not, I'd imagine it's an issue with slots in some way. Either you wouldn't have the active slot set correctly, you're not sure which slot is the active one or rebooted to the other slot somehow in TWRP after the ROM, Gapps, etc installation is finished. Or you installed everything before flashing a patched boot.img.
hx3 said:
I hope so. If not, I'd imagine it's an issue with slots in some way. Either you wouldn't have the active slot set correctly, you're not sure which slot is the active one or rebooted to the other slot somehow in TWRP after the ROM, Gapps, etc installation is finished. Or you installed everything before flashing a patched boot.img.
Click to expand...
Click to collapse
I have another question. What steps do I need to take to update the lineage OS when Twrp doesn't show up on my recovery screen.
Sent from my Pixel 2 XL using Tapatalk
TheGman125 said:
I have another question. What steps do I need to take to update the lineage OS when Twrp doesn't show up on my recovery screen.
Click to expand...
Click to collapse
Do you know which version of TWRP you installed before flashing the ROM and gapps?
If you used the old version (twrp_11), then that's only temporary. You would have to flash that again to get in to TWRP every time you needed to access recovery.
If you're using the newer, official version from the TWRP thread in the Development section, it's recommended to flash it to both slots (makes things easier in case you need to switch slots within the reboot screen in TWRP). And once you finish the installation of the ROM and Gapps, you would want to flash the TWRP installer zip file within TWRP. That file is also in the OP of the official TWRP thread.
Hello All,
I picked up a OP 6T from Amazon and would like to run Lineage 16.0 and load GApps, along with a number of other apps. I have TWRP Fajita (bluespark) installed and can boot to it. I also have Lineage 16 flashed as my ROM on Slot A, to which I can also successfully boot. I have Mind the GApps .zip ARM64 version on internal storage root.
Prior to flashing Lineage, I also loaded Magisk, which is still there as an app.
In trying to load MtheGApps, I cannot get past encryption in TWRP. TWRP prompts for a password, but I have no idea what that might be. I've read (somewhere) that the password is the pin I defined for my opening screen in Lineage, which I know. That does not work. I also have fingerprint enabled and have defined a print. The pin and finger get me into lineage without any trouble.
All of this is on slot A. Slot B seems to holds an older T-Mobile ROM, which I booted at some point. Not really interested in that, so eventually, I'll want to know what to do with that slot. I'll also want to root Lineage.
Maybe I should start from scratch? ( not sure how to get back there). Any guidance greatly appreciated!
It's like that because you didn't format data. Also you can't have OOS on one slot, and an AOSP ROM on another slot.
Here's the LOS install instructions I've been posting / using for clean / first installs.
Note the part in the begining about using 9.0.17 or 10.3.1 depending on which version of LOS you are using. Don't mix Android 10 and 9. Any questions ask.
Also note when Magisk is flashed those instructions. You're close, just missed a couple steps.
Next Steps...
OhioYJ said:
It's like that because you didn't format data. Also you can't have OOS on one slot, and an AOSP ROM on another slot.
Here's the LOS install instructions I've been posting / using for clean / first installs.
Note the part in the begining about using 9.0.17 or 10.3.1 depending on which version of LOS you are using. Don't mix Android 10 and 9. Any questions ask.
Also note when Magisk is flashed those instructions. You're close, just missed a couple steps.
Click to expand...
Click to collapse
OK, finally getting back to this...
I currently have LOS 16 and twrp fajita 3.2.3-2 onboard, as well as Magisk Manager (but not magisk - shows red question mark and "magisk not installed" in Magisk mgr.).
I want to go to LOS 17, load gapps and root to remove redundant apps.
First, I need to I need to get back to stock ROM before anything else, right? I've downloaded 10.0.1-OnePlus6TOxygen_34_OTA_041_all_1911142208_af338-FASTBOOT.zip
I'll also need LOS 17.X, correct? I have this: lineage-17.1-20200104_020517-UNOFFICIAL-fajita.zip
I'll need the Q version of TWRP, right? Still looking for that. Is this version of TWRP specific to the OP 6T, or specific to Android 10? Other?
I'll need the ARM64 , Android 10 version of mindthegapps (mindthegaps supports A/B architecture, right?). Still looking for that. I've found "GApps", but not "mindthegapps". There's also "bitgapps". Should I consider this?
I'll need magisk manager. magisk uninstaller and magisk, correct? I have MagiskManager-v7.5.1.apk, Magisk-v20.3.zip and Magisk-uninstaller-20200110.zip. Not sure if these are the right ones..
I think the main thing I need help with is getting back to the stock ROM. Guessing that would be OOS10. Once I get there, there are lots of instructions around on how to get to LOS 17.
Thank you!!
NoBodyUKnow said:
OK, finally getting back to this...
Click to expand...
Click to collapse
Your version of TWRP could be part of the problem. This is the thread for the official maintainer, use these builds of TWRP even though they say "unofficial." Q is for Android 10, Pie is for Android 9. For LOS 17, download the 3.3.1-32 versions. Remember you are booting the img files, the Q version, you use the same installer for both versions of Android.
To go to LOS 17 you need Android 10 on both slots. Doesn't matter how you get there. 10.3.1 is the latest version from OP, so there is technically a newer version than what you downloaded.
Fastboot ROM page.
You have a few options:
- You can also update using TWRP, and flashing the OTA full ZIP. Just be aware, you need to flash the OTA zip, flash the TWRP installer, reboot to recovery, flash the OTA zip again. Reboot. At this point the phone won't boot, it will just go to stock recovery, wipe data (factory reset), and it should boot up into OOS. Then boot your TWRP img, install TWRP, boot to recovery, start the LOS install I linked to above.
- Use the fastboot ROM. Again as above this will require TWRP installation, etc.
- My least favorite, the MSMTool. My opinion, is the MSMTool should always be a last resort as it locks your bootloader. You can unlocking afterwards again, but if something goes wrong, it could be a bad thing. I just always try every other option before jumping to this one.
As for Gapps, I just use OpenGapps. At this point you don't even have to mess with their test or beta folders anymore. You can just select it from their homepage, and download Android 10 gapps. OpenGapps page, the 6T is Arm64, LOS17 is Android 10, I always use Nano
As for Magisk, yes 20.3. The uninstaller you don't really need as this will essentially be a clean install. The 20.3 zip will also install the Magisk Manager app.
Hopefully that clears some things up?
NoBodyUKnow said:
OK, finally getting back to this...
I currently have LOS 16 and twrp fajita 3.2.3-2 onboard, as well as Magisk Manager (but not magisk - shows red question mark and "magisk not installed" in Magisk mgr.).
I want to go to LOS 17, load gapps and root to remove redundant apps.
First, I need to I need to get back to stock ROM before anything else, right? I've downloaded 10.0.1-OnePlus6TOxygen_34_OTA_041_all_1911142208_af338-FASTBOOT.zip
I'll also need LOS 17.X, correct? I have this: lineage-17.1-20200104_020517-UNOFFICIAL-fajita.zip
I'll need the Q version of TWRP, right? Still looking for that. Is this version of TWRP specific to the OP 6T, or specific to Android 10? Other?
I'll need the ARM64 , Android 10 version of mindthegapps (mindthegaps supports A/B architecture, right?). Still looking for that. I've found "GApps", but not "mindthegapps". There's also "bitgapps". Should I consider this?
I'll need magisk manager. magisk uninstaller and magisk, correct? I have MagiskManager-v7.5.1.apk, Magisk-v20.3.zip and Magisk-uninstaller-20200110.zip. Not sure if these are the right ones..
I think the main thing I need help with is getting back to the stock ROM. Guessing that would be OOS10. Once I get there, there are lots of instructions around on how to get to LOS 17.
Thank you!!
Click to expand...
Click to collapse
OhioYJ said:
It's like that because you didn't format data. Also you can't have OOS on one slot, and an AOSP ROM on another slot.
Here's the LOS install instructions I've been posting / using for clean / first installs.
Note the part in the begining about using 9.0.17 or 10.3.1 depending on which version of LOS you are using. Don't mix Android 10 and 9. Any questions ask.
Also note when Magisk is flashed those instructions. You're close, just missed a couple steps.
Click to expand...
Click to collapse
NoBodyUKnow said:
Hello All,
I picked up a OP 6T from Amazon and would like to run Lineage 16.0 and load GApps, along with a number of other apps. I have TWRP Fajita (bluespark) installed and can boot to it. I also have Lineage 16 flashed as my ROM on Slot A, to which I can also successfully boot. I have Mind the GApps .zip ARM64 version on internal storage root.
Prior to flashing Lineage, I also loaded Magisk, which is still there as an app.
In trying to load MtheGApps, I cannot get past encryption in TWRP. TWRP prompts for a password, but I have no idea what that might be. I've read (somewhere) that the password is the pin I defined for my opening screen in Lineage, which I know. That does not work. I also have fingerprint enabled and have defined a print. The pin and finger get me into lineage without any trouble.
All of this is on slot A. Slot B seems to holds an older T-Mobile ROM, which I booted at some point. Not really interested in that, so eventually, I'll want to know what to do with that slot. I'll also want to root Lineage.
Maybe I should start from scratch? ( not sure how to get back there). Any guidance greatly appreciated!
Click to expand...
Click to collapse
OhioYJ said:
Your version of TWRP could be part of the problem. This is the thread for the official maintainer, use these builds of TWRP even though they say "unofficial." Q is for Android 10, Pie is for Android 9. For LOS 17, download the 3.3.1-32 versions. Remember you are booting the img files, the Q version, you use the same installer for both versions of Android.
To go to LOS 17 you need Android 10 on both slots. Doesn't matter how you get there. 10.3.1 is the latest version from OP, so there is technically a newer version than what you downloaded.
Fastboot ROM page.
You have a few options:
- You can also update using TWRP, and flashing the OTA full ZIP. Just be aware, you need to flash the OTA zip, flash the TWRP installer, reboot to recovery, flash the OTA zip again. Reboot. At this point the phone won't boot, it will just go to stock recovery, wipe data (factory reset), and it should boot up into OOS. Then boot your TWRP img, install TWRP, boot to recovery, start the LOS install I linked to above.
- Use the fastboot ROM. Again as above this will require TWRP installation, etc.
- My least favorite, the MSMTool. My opinion, is the MSMTool should always be a last resort as it locks your bootloader. You can unlocking afterwards again, but if something goes wrong, it could be a bad thing. I just always try every other option before jumping to this one.
As for Gapps, I just use OpenGapps. At this point you don't even have to mess with their test or beta folders anymore. You can just select it from their homepage, and download Android 10 gapps. OpenGapps page, the 6T is Arm64, LOS17 is Android 10, I always use Nano
As for Magisk, yes 20.3. The uninstaller you don't really need as this will essentially be a clean install. The 20.3 zip will also install the Magisk Manager app.
Hopefully that clears some things up?
Click to expand...
Click to collapse
It did clear some things up, thank you. However, I still end up at the Qualcomm CrashDump Screen of Death. this happens at the very end of the process, after the second load of LOS 17 and TWRP Installer, while rebooting to recovery from the TWRP .img. I'm going to list every step I take and all of the files I use. There are a couple of places where I'm not sure I'm doing the right thing, and/or the outcome of that step is not as expected.
1. Download all of files:
TWRP Q .img
TWRP Installer
OP OS 10.3.1 Fastboot ROM
lineage-17.1-20200223_133843-UNOFFICIAL-fajita.zip
First step is to flash Oxygen 10 and TWRP Recovery to both slots. I unpack the OOS Fastboot ROM zip on my laptop, boot to my 6t's bootloader and connect that to my laptop. After making sure ADB/Fastboot sees the device, I run "flash-all.bat" by clicking on it. This seems to load OOS just fine. The phone boots to OOS and I turn the phone off.
(I've done all of this several times and there are variants: I've tried becoming a developer and turning on the advanced boot options in OOS 10, but I don't think that matters, as long as I can get back to the bootloader or recovery. Let me know if that is incorrect).
At this point, your instructions say
"reboot to recovery, flash the OTA zip again."
I've tried moving the OOS fastboot zip file to my phone and flashing from TWRP, but that doesn't work. I get an error complaining of wrong format. It seems to me, a Fastboot ROM can only be flashed from adb/flashboot. Is that correct?
Therefore, I have been going back to the bootloader and re-flashing OOS 10 from adb fastboot again. After this step, contrary to your guidance above, the phone does indeed boot directly to OOS.... A loooong, what seems to be initial boot. I then turn off the phone.
I reboot to recovery again - and it is now the stock recovery - so I follow your guidance to factory reset from there. It does boot into OOS, and it is another looonnng boot. I then turn off the phone, return to the bootloader, flash the TWRP .img, install the TWRP installer and move on to the LOS 17 process linked to above.
Though I'm not sure it's necessary, I follow these steps from the beginning of he process:
Install 10.3.0 fastboot ROM again to start over, boot it once. Just to make sure everything is good.
- Reboot to fastboot.
- Boot the Q image of TWRP.
- Run the TWRP installer, reboot to recovery
Everything seems to work well, so I follow these steps, all from TWRP:
- Factory reset (This is the slider at the bottom in the wipe menu).
- Format data. (This is the button that says Format data in the wipe menu)
- Do NOT wipe cache, do not Wipe system, do NOT Wipe Dalvik / ART, do not add anything else, Just Factory Reset and Format Data. After doing those two Reboot to Recovery one more time. You must do this after formatting data.
I do all of the steps below, with no problems:
- Now transfer Lineage and TWRP to your phone, Windows / Linux should see TWRP fine as a media device when plugged in.
- Install Lineage
Just a note at this point, to highlight that this is done from TWRP, as opposed to using adb fastboot as with OOS10. This is what I've done with ROM's in the past; the fastboot ROM thing is new to me.
Next, I
- Run the TWRP Installer.
- Reboot to Recovery.
- Install Lineage (You need Lineage on both slots, so yes run it again)
- Run the TWRP Installer (yes again).
- Reboot to Recovery
This is where things go bad. In this reboot to recovery, the TWRP splash screen sits there for a long time, and then the Qualcomm CrashDump Screen of Death (QCDSoD) appears. If I hold the power button down for long time, the QCDSoD disappears and the phone reboots and starts to load LOS. Then, it switches to TWRP splash screen, and as before, end with the QCCDSoD.
I've been through this entire process maybe three times. Always the same outcome (you know what they say, about doing the same things and expecting different results...)
I did note, that on the OS Fastboot ROM page, there was some discussion of "Branded" phones, specifically T-Mobile phones. When I first got this phone, after loading TWRP, I swapped active slots. On the new, active slot, I booted the phone, and it was to a T-Mobile ROM. Not sure if that plays any part in all of this.
Appreciate your hanging with me. I'm going to rest my fingers
Is this a TMobile 6T?
NoBodyUKnow said:
OK, finally getting back to this...
I currently have LOS 16 and twrp fajita 3.2.3-2 onboard, as well as Magisk Manager (but not magisk - shows red question mark and "magisk not installed" in Magisk mgr.).
I want to go to LOS 17, load gapps and root to remove redundant apps.
First, I need to I need to get back to stock ROM before anything else, right? I've downloaded 10.0.1-OnePlus6TOxygen_34_OTA_041_all_1911142208_af338-FASTBOOT.zip
I'll also need LOS 17.X, correct? I have this: lineage-17.1-20200104_020517-UNOFFICIAL-fajita.zip
I'll need the Q version of TWRP, right? Still looking for that. Is this version of TWRP specific to the OP 6T, or specific to Android 10? Other?
I'll need the ARM64 , Android 10 version of mindthegapps (mindthegaps supports A/B architecture, right?). Still looking for that. I've found "GApps", but not "mindthegapps". There's also "bitgapps". Should I consider this?
I'll need magisk manager. magisk uninstaller and magisk, correct? I have MagiskManager-v7.5.1.apk, Magisk-v20.3.zip and Magisk-uninstaller-20200110.zip. Not sure if these are the right ones..
I think the main thing I need help with is getting back to the stock ROM. Guessing that would be OOS10. Once I get there, there are lots of instructions around on how to get to LOS 17.
Thank you!!
Click to expand...
Click to collapse
OhioYJ said:
It's like that because you didn't format data. Also you can't have OOS on one slot, and an AOSP ROM on another slot.
Here's the LOS install instructions I've been posting / using for clean / first installs.
Note the part in the begining about using 9.0.17 or 10.3.1 depending on which version of LOS you are using. Don't mix Android 10 and 9. Any questions ask.
Also note when Magisk is flashed those instructions. You're close, just missed a couple steps.
Click to expand...
Click to collapse
NoBodyUKnow said:
Hello All,
I picked up a OP 6T from Amazon and would like to run Lineage 16.0 and load GApps, along with a number of other apps. I have TWRP Fajita (bluespark) installed and can boot to it. I also have Lineage 16 flashed as my ROM on Slot A, to which I can also successfully boot. I have Mind the GApps .zip ARM64 version on internal storage root.
Prior to flashing Lineage, I also loaded Magisk, which is still there as an app.
In trying to load MtheGApps, I cannot get past encryption in TWRP. TWRP prompts for a password, but I have no idea what that might be. I've read (somewhere) that the password is the pin I defined for my opening screen in Lineage, which I know. That does not work. I also have fingerprint enabled and have defined a print. The pin and finger get me into lineage without any trouble.
All of this is on slot A. Slot B seems to holds an older T-Mobile ROM, which I booted at some point. Not really interested in that, so eventually, I'll want to know what to do with that slot. I'll also want to root Lineage.
Maybe I should start from scratch? ( not sure how to get back there). Any guidance greatly appreciated!
Click to expand...
Click to collapse
OhioYJ said:
Is this a TMobile 6T?
Click to expand...
Click to collapse
After a little research, it appears that it is a T-Mobile variant: the A6013. And, well.... I guess this may be a clue...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'm guessing this is the source of my problem. Do you agree?
My research suggests the T-Mobile variant can be converted to "Global", but I'm wondering if it may just be more efficient to return this phone to Amazon with OOS 9 or 10 on it and buy the Global variant (A6010?)
NoBodyUKnow said:
I'm guessing this is the source of my problem. Do you agree?
My research suggests the T-Mobile variant can be converted to "Global", but I'm wondering if it may just be more efficient to return this phone to Amazon with OOS 9 or 10 on it and buy the Global variant (A6010?)
Click to expand...
Click to collapse
Yeap, you have a TMobile 6T. A TMobile 6T is not a Global 6T, and even a "converted" TMobile 6T is not a Global 6T. They still require special instructions at points, and do different things. The instructions above will work perfect for a Global 6T. They (TMobile 6Ts) tend to be cheaper, but tend to have some gotchas with them.
OhioYJ said:
Yeap, you have a TMobile 6T. A TMobile 6T is not a Global 6T, and even a "converted" TMobile 6T is not a Global 6T. They still require special instructions at points, and do different things. The instructions above will work perfect for a Global 6T. They (TMobile 6Ts) tend to be cheaper, but tend to have some gotchas with them.
Click to expand...
Click to collapse
Thanks! I like the 6T, so I guess I'm gonna get a Global. I'll get back to this, when I have that phone in-hand. Will slowly chug away on my Moto G6 until then. More to come...
Oh... Should I have any trouble putting an Oxygen 9 ROM ( or 10) on both slots without TWRP, before sending it back? Guess I'll need to re-lock the bootloader too.
NoBodyUKnow said:
Oh... Should I have any trouble putting an Oxygen 9 ROM ( or 10) on both slots without TWRP, before sending it back? Guess I'll need to re-lock the bootloader too.
Click to expand...
Click to collapse
You could always use a T-Mobile MSM Tool ?
Link
MSM Tools are usually my last resort as they relock the bootloader, but in this case, it's what you are after.
OhioYJ said:
Yeap, you have a TMobile 6T. A TMobile 6T is not a Global 6T, and even a "converted" TMobile 6T is not a Global 6T. They still require special instructions at points, and do different things. The instructions above will work perfect for a Global 6T. They (TMobile 6Ts) tend to be cheaper, but tend to have some gotchas with them.
Click to expand...
Click to collapse
NoBodyUKnow said:
Thanks! I like the 6T, so I guess I'm gonna get a Global. I'll get back to this, when I have that phone in-hand. Will slowly chug away on my Moto G6 until then. More to come...
Click to expand...
Click to collapse
OK... Back this this!
This is the what I ordered to replace the T-Mobile variant I had. It arrived yesterday. Is this the "global" model, or did I again purchase the wrong phone?
This phone is a dual sim, so it is definitely different from the one I had. Model number from System Info is A6010_41_200115.
Behavior is exactly as before. First, I'm loading the Android 10 version of the OP Oxygen Rom. After the second install of the OTA as advised below...
- You can also update using TWRP, and flashing the OTA full ZIP. Just be aware, you need to flash the OTA zip, flash the TWRP installer, reboot to recovery, flash the OTA zip again. Reboot. At this point the phone won't boot, it will just go to stock recovery, wipe data (factory reset), and it should boot up into OOS. Then boot your TWRP img, install TWRP, boot to recovery, start the LOS install I linked to above.
...rather than going directly to stock recovery, the phone DOES boot to OOS. To get to recovery, I go through the minimal necessary setup steps to access the settings, so I can activate developer mode, enable advanced reboot and enable USB debug. Then I reboot to recovery (stock), perform the wipe and reset. I then reboot to Fastboot and flash the TWRP .img using adb/fastboot on my PC. I then txfr the TWRP install .zip to root and install that. All of this SEEMS to go well, but again, there's that unexpected reboot to OOS as highlighted above.
Next, I move on to the LOS 17 load.
This goes well, until I complete the second load of TWRP Installer and reboot to recovery. When I execute that step, the TWRP splash screen appears and stays there for 30-45 seconds, and then turns to the QualComm CrashDump Mode Screen.
:crying:
I guess the first thing is to determine, If I have the correct phone ....
NoBodyUKnow said:
OK... Back this this!
This is the what I ordered to replace the T-Mobile variant I had. It arrived yesterday. Is this the "global" model, or did I again purchase the wrong phone?
This phone is a dual sim, so it is definitely different from the one I had. Model number from System Info is A6010_41_200115.
Behavior is exactly as before. First, I'm loading the Android 10 version of the OP Oxygen Rom. After the second install of the OTA as advised below...
- You can also update using TWRP, and flashing the OTA full ZIP. Just be aware, you need to flash the OTA zip, flash the TWRP installer, reboot to recovery, flash the OTA zip again. Reboot. At this point the phone won't boot, it will just go to stock recovery, wipe data (factory reset), and it should boot up into OOS. Then boot your TWRP img, install TWRP, boot to recovery, start the LOS install I linked to above.
...rather than going directly to stock recovery, the phone DOES boot to OOS. To get to recovery, I go through the minimal necessary setup steps to access the settings, so I can activate developer mode, enable advanced reboot and enable USB debug. Then I reboot to recovery (stock), perform the wipe and reset. I then reboot to Fastboot and flash the TWRP .img using adb/fastboot on my PC. I then txfr the TWRP install .zip to root and install that. All of this SEEMS to go well, but again, there's that unexpected reboot to OOS as highlighted above.
Next, I move on to the LOS 17 load.
This goes well, until I complete the second load of TWRP Installer and reboot to recovery. When I execute that step, the TWRP splash screen appears and stays there for 30-45 seconds, and then turns to the QualComm CrashDump Mode Screen.
:crying:
I guess the first thing is to determine, If I have the correct phone ....
Click to expand...
Click to collapse
So if I get this right, you're trying to install LOS 17 on your OnePlus 6T which is running OOS 10? Also you have the international variant.
DarthVader said:
So if I get this right, you're trying to install LOS 17 on your OnePlus 6T which is running OOS 10? Also you have the international variant.
Click to expand...
Click to collapse
He's got the China version this time, which I believe is minus a couple LTE bands (not a deal breaker necessarily, but not ideal). Does this change his install process since it would have originally had HOS on it?
Yes, but...
DarthVader said:
So if I get this right, you're trying to install LOS 17 on your OnePlus 6T which is running OOS 10? Also you have the international variant.
Click to expand...
Click to collapse
Yes, my goal is to have Lineage OS 17 (Android 10/Q) on a OnePlus 6T. Hopefully on the phone I have now, but on whatever 6T variant I need to get. I like the phone.
I tried before with a T-Mobile version of the A6013, and I could not get there. @OhioYJ offered some assistance and suggested the problem was the phone being a T-Mobile variant; that I needed a "Global" version. Therefore, I returned that phone and purchased an "International" A6010_41_200115. Is this the Global variant?
I've followed the processes detailed above on both phones and wound up at exactly the same place: The QUALCOMM CrashDump Mode screen. This happens after the second install of TWRP, when I reboot to Recovery.
In both cases, the phones came with OOS 9, and I'm updating to OOS10 via the Fastboot ROM before proceeding to LOS 17.
Is it possible to get to LOS 17 on the phone I have now?
Thanks!!!
OhioYJ said:
He's got the China version this time, which I believe is minus a couple LTE bands (not a deal breaker necessarily, but not ideal). Does this change his install process since it would have originally had HOS on it?
Click to expand...
Click to collapse
This would be the global variant, wouldn't it? An A6013 with both GSM and CDMA...?
Mine is an A6013, I checked the phone and original box. I bought mine straight from OnePlus. TMobile ones will only have a single IMEI. The "Real" 6T will be dual sim and have two separate, unique IMEI numbers.
NoBodyUKnow said:
This would be the global variant, wouldn't it? An A6013 with both GSM and CDMA...?
Click to expand...
Click to collapse
Do this. Download the latest OOS 10.3.2 from OnePlus's Website. As well as latest Unofficial TWRP Image and Installer. Grab the Q Image, not the Pie one. The latest TWRP version as of now is 3.3.1-32. Now Boot to TWRP. Flash the OOS ZIP File and then TWRP Installer. Reboot to Recovery and again flash the OOS ZIP and TWRP Installer. Once that's done, you can once again Reboot to Recovery. Now, flash the Latest LineageOS 17.1 ZIP file and TWRP Installer. Reboot to Recovery one last time and flash Gapps. After that Format Data and Reboot System. You should now hopefully boot into Android.
DarthVader said:
Do this. Download the latest OOS 10.3.2 from OnePlus's Website. As well as latest Unofficial TWRP Image and Installer. Grab the Q Image, not the Pie one. The latest TWRP version as of now is 3.3.1-32. Now Boot to TWRP. Flash the OOS ZIP File and then TWRP Installer. Reboot to Recovery and again flash the OOS ZIP and TWRP Installer. Once that's done, you can once again Reboot to Recovery. Now, flash the Latest LineageOS 17.1 ZIP file and TWRP Installer. Reboot to Recovery one last time and flash Gapps. After that Format Data and Reboot System. You should now hopefully boot into Android.
Click to expand...
Click to collapse
@OhioYJ
I did as you suggested. As with my first phone (a T-Mobile variant), when I perform the reboot to recovery after flashing LOS 17 and TWRP, the TWRP intro screen appears for a long time ( 30 seconds + ). When it finally disappears, the Qual. Crash Dump Screen appears. By holding the power button for about 10 seconds, the phone reboots to LOS. After booting, I can navigate within LOS, but a warning flashes for a few milliseconds, about every ten seconds. I was able to capture a screenshot of the warning from the video I just linked to:
This continues to occur: if I try to reboot to recovery, the TWRP screen appears, lingers and then changes to the Qual Crash Dump screen. At this point, when I hold the power button for about 10 seconds, the phone boots to LOS. When LOS is running, the warning continues to appear at regular intervals.
Thinking I may just go for another phone, preferably one that supports GSM and CDMA, but at least a US, non-T-mobile phone with all of the GSM Bands. They are a little pricey though.
Happy to try other things with this phone though, if it might help further understanding of these phones.
Looking for w Breakthrough...
@OhioYJ @DarthVader
Gentleman,
I hope this update finds you and your loved ones safe, in this scary time.
I am still trying to get LOS 17 on my OP 6T, and I Keep ending up at the same place.: Qualcomm CrashDump Screen. l'm using the fastboot ROM's, and using those does not completely align with this part of OhioYJ's instructions:
- You can also update using TWRP, and flashing the OTA full ZIP. Just be aware, you need to flash the OTA zip, flash the TWRP installer, reboot to recovery, flash the OTA zip again. Reboot. At this point the phone won't boot, it will just go to stock recovery, wipe data (factory reset), and it should boot up into OOS. Then boot your TWRP img, install TWRP, boot to recovery, start the LOS install I linked to above.
OhioYJ mentions "flashing the OTA Full .zip". The Fastboot ROM's have "OTA" in their labels and they are .zip files, but they will not flash in TWRP. They error out. They do run - and flash - from the bootloader, and this is what I've been doing. I'm guessing there are other, TWRP flasheable .zip files for the 6T. Maybe I should try those? Can't seem to find them. If so, can you point them out to me, please?
I humbly ask that you review this thread, looking closely at your guidance and my responses. I keep ending up at the same place - the Qualcom CrashDump Mode Screen.
Thanks!
NBUK
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