I installed linage os and i need to put back the stock android 11 taimen how do i go out doing that?
b2x said:
I installed linage os and i need to put back the stock android 11 taimen how do i go out doing that?
Click to expand...
Click to collapse
Flash the last factory image (Dec. 2020) using fastboot. Here's a guide you can use. Assuming your bootloader is already unlocked since you have LOS on there now, you can skip that section. Back up anything you need to beforehand.
[GUIDE] Unlock/Flash/Root for the Pixel 2 XL (taimen)
Introduction Hello everyone, this is a guide to assist you with customizing your Pixel 2 XL! I will be going over installing fastboot and adb, unlocking your bootloader, how to flash the factory images for clean flashes and upgrades, and how to...
forum.xda-developers.com
Related
Hello!
I'm currently running Android 6.0.1. I was planning on upgrading to Android 7.1.2 and installing Pure Nexus. So, I'm wondering If I have to install the stock image first or is there a way to just directly go to installing Pure Nexus? Maybe I could flash the radio and such separately. I'm not quite sure... Could someone help me out?
angelica_kh said:
Hello!
I'm currently running Android 6.0.1. I was planning on upgrading to Android 7.1.2 and installing Pure Nexus. So, I'm wondering If I have to install the stock image first or is there a way to just directly go to installing Pure Nexus? Maybe I could flash the radio and such separately. I'm not quite sure... Could someone help me out?
Click to expand...
Click to collapse
Download the latest Pure Nexus update from June, gapps, and the latest update of your preferred root tool (if you need root) onto your phone. Pure Nexus is not rooted from my understanding. Someone correct me if I am wrong. Download the June factory image onto your computer.
Backup your current rom in TWRP. Next, use fastboot to flash the bootloader, radio, and vendor images from the June factory image. You must update the vendor image each month that you update your custom rom, FYI. Follow this guide below to learn more regarding fastboot:
https://forum.xda-developers.com/showthread.php?t=3206928
Next, boot into TWRP again. Here, you will do a factory reset and wipe system then flash Pure Nexus, gapps and your root method (if you desire). Boot up and reinstall everything. You should be set from here.
Sent from my Nexus 5X using Tapatalk
Thanks. It worked! Now to figure out why Magisk is giving me a CTS Profile mismatch error....
angelica_kh said:
Thanks. It worked! Now to figure out why Magisk is giving me a CTS Profile mismatch error....
Click to expand...
Click to collapse
Flash Magisk 13 zip from xda and don't forget to turn on hide in settings. Also to certifie the playstore clear data and cache for it after.
Hi,
I have a Nexus 6P that has Android 7.1.2 (N2G47W) installed. I've just unlocked the bootloader, installed TWRP then installed Magisk 16.0 for root.
I'd like to next downgrade from Nougat to Marshmallow. Are there any steps to do so? Can I just boot to TWRP, and immediately install the factory image from https://developers.google.com/android/images#angler?
Or are there any additional steps I need to take?
@goister You can't with TWRP download marshmallow from Google API site. Maybe do a good wipe in TWRP before hand of course back up anything important on comouter. Then follow the hiesenberg guide for returning to stock. Your in luck cause I've read with being on the latest Oreo can no longer return to marshmallow or nougat though I haven't verified myself. Best of luck mate.
Exodusche said:
@goister You can't with TWRP download marshmallow from Google API site. Maybe do a good wipe in TWRP before hand of course back up anything important on comouter. Then follow the hiesenberg guide for returning to stock. Your in luck cause I've read with being on the latest Oreo can no longer return to marshmallow or nougat though I haven't verified myself. Best of luck mate.
Click to expand...
Click to collapse
Hi,
Not sure I get your post. My Nexus 6P is stock except for an unlocked bootloader, TWRP and Magisk root. Are you saying follow the guide at https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928 specifically step 10. How To Flash The Factory Images (And Return To Stock)?
goister said:
Hi,
Not sure I get your post. My Nexus 6P is stock except for an unlocked bootloader, TWRP and Magisk root. Are you saying follow the guide at https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928 specifically step 10. How To Flash The Factory Images (And Return To Stock)?
Click to expand...
Click to collapse
That's exactly what I'm saying unless you want to flash a marshmallow ROM. Then you can use TWRP but would still need 6.0 gapps and a computer to fastboot flash MM bootloader of that months build. MM vendor could be flashed by either fastboot or TWRP. Your best to download a MM build from Google site. Then unzip that folder and inside unzip again. You will get all the bootloader, vendor (radio optional) you will need for that months MM build. Then follow the guide from hiesenberg for returning to stock . Best to put all the images files and fastboot in the folder that is suggested in the guide . That way you can copy and paste the commands as written on the guide. There might be a flash all bat file you can use in the stock folder but not sure if MM had that I never used. If you have any more questions feel free to ask.
Yes I intend to flash the stock Marshmallow ROM from https://developers.google.com/android/images#angler specifically the latest one (MTC20L). My end goal is a rooted Nexus 6P with the MTC20L firmware. Wouldn't the stock Google build already have gapps? I don't intend to use a 3rd party ROM.
goister said:
Yes I intend to flash the stock Marshmallow ROM from https://developers.google.com/android/images#angler specifically the latest one (MTC20L). My end goal is a rooted Nexus 6P with the MTC20L firmware. Wouldn't the stock Google build already have gapps? I don't intend to use a 3rd party ROM.
Click to expand...
Click to collapse
Yes that's right gapps not needed with stock. Wasn't sure on your level of experience so mentioned that with a ROM you would need gapps of that android version . If I where you I would back up my phone completey and wipe everything in TWRP including internal before hand. So many times files get left behind especially using different versions of android to avoid any issues. Be warned though wiping internal includes pictures, downloads, music, documents etc.
Exodusche said:
Yes that's right gapps not needed with stock. Wasn't sure on your level of experience so mentioned that with a ROM you would need gapps of that android version . If I where you I would back up my phone completey and wipe everything in TWRP including internal before hand. So many times files get left behind especially using different versions of android to avoid any issues. Be warned though wiping internal includes pictures, downloads, music, documents etc.
Click to expand...
Click to collapse
Thanks. I've no issues wiping the phone as this is pretty much a fresh phone. There's nothing to even back up. The only thing I've done so far beyond rooting, was to import a certificate into /system. I suppose a factory reset would delete this certificate and bring it back to stock (but rooted)? Or should I wipe with TWRP instead?
Looking at the zip file of the stock ROM, here's what I see
bootloader-angler-angler-03.54.img
flash-all.bat
flash-all.sh
flash-base.sh
image-angler-mtc20l
radio-angler-angler-03.61.img
After wiping with TWRP, would I be able to run flash-all?
Edit: I've just TWRP wiped everything, and rebooted. However, the device is stuck at the initial "Google" screen with the lock icon at the button. How long is it supposed to take to boot up after a full TWRP wipe?
OK I solved the problem. Apparently if you reboot after the flash, you need to disconnect the USB cable, else it will boot loop.
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
Is it possible to revert from oneplus 8 pro lineage 19.1 android 12 back to stock oxygen OS11? I am unable to detect the phone in MSM tool and can’t fastboot flash stock rom. Thanks for any advice
I've been trying to figure out an easy way to do this as well
I could only flash MSM on A11versions and conversely only use the fastboot flash on A10.. I have done both ways many times. There really is no other way except manually each flash .img file.
If you read around XDA for all the mess ups of people downgrading from 12 to 11, It is evident that the only safe way to downgrade is MSM.
Apologies if this is the wrong forum.
From what I can tell, the only versions of Pixel Experience 13 require to start from OOS 12.
I have Pixel Experience 12.1 with Pixel Experience Recovery on my phone and have not been able to flash Pixel Experience 13 or Pixel Experience Recovery for 13.
Is there any way to do it, or do I need to go back to OOS somehow and start from there? I do not have easy access to a Windows computer to use MSM.
1. Never play with your device without a PC you can access
2. If there is a version of PE 13 made for your device, wipe system and clean flash thru TWRP
“Never play with your device without a PC you can access” says the “Android enthusiast who will stop at nothing to brick his device and will then beg for help on this forum”
I have access to a Linux PC and a Mac, both with working adb.
When I installed PE 12, I was only able to do it from PE Recovery, TWRP did not work so I’m wary of changing recoveries.
gongolino said:
Apologies if this is the wrong forum.
Click to expand...
Click to collapse
It's better to ask in ROM thread.
[ROM][13.0][OnePlus8T] PixelExperience [AOSP/UNOFFICIAL] - JUNE 17, 2023
YOU MUST HAVE STOCK OOS13 INSTALLED ON BOTH SLOTS TO AVOID TOUCH SCREEN ISSUES. IF YOU ARE ON A11 or A12, THEN UPDATE TO A13. IF YOU ARE ON A13 then you are good to flash this already. Use copy partions if you want to make sure firmware is on...
forum.xda-developers.com