My phone Sprint/XT1922-7_JETER_SPRINT_8.0.0 (16gb model)
I just root it and flash Disable_Dm-Verity_ForceEncrypt + Magisk
Until I saw this:
[AOSP 9.0] [2019-08-25] Phh-Treble
WARNING: You'll most probably loose ALL your data, and might break your phone. Please use with extreme caution! The goal of this ROM is to provide maximum hardware compatibility inside a Generic System Image. No feature will be added. This will...
forum.xda-developers.com
The instructions say: Flash GSI first.
Then flash Magisk.
I also don't know if Disable_Dm-Verity_ForceEncrypt would mess up?
either your device is Treble or not. check with this app
http://play.google.com/store/apps/details?id=com.kevintresuelo.treble
if yes you can flash any GSI
https://forum.xda-developers.com/t/gsi-10-lineageos-17-x-gsi-all-archs.4004673
you don't need encryption disabler, but sure you must factory reset device every time you switch ROM.
aIecxs said:
either your device is Treble or not. check with this app
http://play.google.com/store/apps/details?id=com.kevintresuelo.treble
if yes you can flash any GSI
https://forum.xda-developers.com/t/gsi-10-lineageos-17-x-gsi-all-archs.4004673
you don't need encryption disabler, but sure you must factory reset device every time you switch ROM.
Click to expand...
Click to collapse
I already flashed Disable_Dm-Verity_ForceEncrypt + Magisk on the phone.
Do I Need to remove those before I flash GSI?
No, how would you? It's too late. To undo modifications of Disable_Dm-Verity_ForceEncrypt you need to restore backup of vendor (sometimes nvram)
Is it possible/safe to flash GSI on phone that was already flashed Disable_Dm-Verity_ForceEncrypt + Magisk?
aIecxs said:
either your device is Treble or not. check with this app
http://play.google.com/store/apps/details?id=com.kevintresuelo.treble
if yes you can flash any GSI
https://forum.xda-developers.com/t/gsi-10-lineageos-17-x-gsi-all-archs.4004673
...
Click to expand...
Click to collapse
May be I'm mistaken but you can't flash ANY GSI even if device is Project Treble enabled: Read here:
Generic System Images (GSIs) | Platform | Android Developers
developer.android.com
of course I referred to builds that are built for the proper SoC (aarch64). In theory one can use "any" of these GSIs here:
https://forum.xda-developers.com/f/treble-enabled-device-development-a-ab-roms.7260
(as always: read OP for restrictions)
Is it possible/safe to flash GSI on phone that was already flashed Disable_Dm-Verity_ForceEncrypt + Magisk?
what do you mean with safe? no, you will lose all data each time you format data (which is required step for every ROM installation).
as I said if your device is treble enabled it is possible to flash GSI. doesn't matter if encryption already has been disabled or phone was rooted with Magisk previously. Magisk lives in boot partition. if you install custom ROM it will overwrite boot + system anyway (sometimes even vendor, where encryption was patched)
GSI only overwrites system partition, it won't touch boot or vendor therefore all modifications preserved.
aIecxs said:
what do you mean with safe? no, you will lose all data each time you format data (which is required step for every ROM installation).
as I said if your device is treble enabled it is possible to flash GSI. doesn't matter if encryption already has been disabled or phone was rooted with Magisk previously. Magisk lives in boot partition. if you install custom ROM it will overwrite boot + system anyway (sometimes even vendor, where encryption was patched)
GSI only overwrites system partition, it won't touch boot or vendor therefore all modifications preserved.
Click to expand...
Click to collapse
I don't care about data. I understand that each time flash a new rom --> all data in the phone would be erased.
I am asking because the guide show flash GSI first.
Then install Magisk later.
It also doesn't mention anything about Disable_Dm-Verity_ForceEncrypt. That why I worry if Disable_Dm-Verity_ForceEncrypt would mess everything up.
phone Sprint/XT1922-7_JETER_SPRINT_8.0.0 (16gb model)
Handsome Jack said:
I understand that each time flash a new rom --> all data in the phone would be erased.
Click to expand...
Click to collapse
not exactly. you should care about that last step yourself, it is highly recommended.
Handsome Jack said:
It also doesn't mention anything about Disable_Dm-Verity_ForceEncrypt. That why I worry if Disable_Dm-Verity_ForceEncrypt would mess everything up.
Click to expand...
Click to collapse
In this guide there are quick fastboot commands to revert back to stock. probably vendor is enough to repair encryption.
[guide] [root] [oreo&pie] [jeter/aljeter] [twrp, decrypt, magisk] [stock firmware]
* Your warranty is now void. * * I am not responsible for bricked devices, dead SD cards, fires, rigged elections, ligma, * thermonuclear war, or your mom getting upset with you for being on the computer all day Please * Ensure you have an...
forum.xda-developers.com
yeah, I used that guide to flashed Disable_Dm-Verity_ForceEncrypt + Magisk.
After that I found out it doesn't need those two... to flash GSI.
Related
Ultimate Guide for Flashing GENRIC SYSTEM IMAGE.
Contents:
Intro
how to flash gsi.
how to get rooted.
gapps issues
how to get back to non treble rom from gsi or treble enabled builds.
Introduction and basic information:
GSI means Generic System Image, which can be flashed over any Treble Device.
So, in simple words : same System.img can be flashed over multiple devices having Treble Support.
This happens as we now have a separate /vendor partition where all the vendor hals are stored.
Now, this will help to do easy bring ups, Treble builds are smooth af y'all know that and you'll get to flash aosp treble rom
Also, if you own 2-3 treble devices, now you'll just have to download one system.img xD it'll work for all of em ( if treble supported )
How to get Treble Support?
Flashing Treble TWRP won't give you treble support. Keep that in Mind. It'll just mount the partition in the recovery, so that vendor img can be flashed.
To get Treble Support, you'll need to flash a latest ROM which has vendor image compiled with the latest changes by mikeNG, once you flash such a ROM, you'll get the vendor stored in the vendor partition, and after that you can flash any GSI ( as it's just System.img, and all our device specifics are in /vendor so it won't mess with that)
Instructions:
Download Official LineageOS-15.1 treble enabled build from here
Download treble enabled twrp from here
Move both the downloaded files to external sd card (recommended)(optional)
boot in twrp
move to wipe option from twrp.
advanced wipe.
select data and then check if its in ext4 if not format it to ext4 ( do this from official twrp by @celoxocis )
then go to install and install the recovery provided above.
reboot to recovery.
wipe system, data, dalvik, cache & internal storage recommended.
install the lineage os zip and reboot.
download GSI of any rom of your choice. if it is in zipped format extract it and make sure you have a *.img
boot into twrp
wipe anything other than boot, micro sd & vendor
go to install option and then select install image button on bottom right corner
select the gsi of your choice which you have downloaded and install it on system partition.
reboot to recovery (important)
flash mind the gapps if you are going to use gapps in your rom. ( important open gapps have a few issues on treble like many of times gapps dont get flashed or shows some error)
reboot
Kudos you have now flashed a Genric System Image on your Lenovo P2.
for how to get rooted with magisk refer to next post.
and List Of GSI is available here
if you have any doubts even after reading this ultimate guide feel free to post it i will try to answer it and help you with that.
after following instruction as mentioned above
* download the magisk from here
* flash it normally.
A list of GSI and download links can be found here.
https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
Only A arm64 gsi are supported well on our device and based on arch of our device
how to get back to non treble rom?
* Download the non treble rom your choice
* boot into twrp do wipes as suggested on rom's thread and then flash the rom package no need to mess with vendor partition.
I have managed to flash Dirty Unicorns Rom and its working pretty much well.
Here are some screen shots.
Volte working on GSI?
Volte working on any gsi?
advaithbhat said:
Volte working on any gsi?
Click to expand...
Click to collapse
My network provider don't use volte you can try and tell me
Sent from my Phh-Treble vanilla using Tapatalk
I'm on codeexilir's twrp, can't I use that twrp to flash official los 15.1 to get vendor image and then flash any GSI. Or it is mandatory to use los twrp?
abdal2006 said:
I'm on codeexilir's twrp, can't I use that twrp to flash official los 15.1 to get vendor image and then flash any GSI. Or it is mandatory to use los twrp?
Click to expand...
Click to collapse
I believe You can but I haven't tested that.
Sent from my Phh-Treble vanilla using Tapatalk
If i want to change the gsi img then should i clean flash the los 15.1 again?
imPro01 said:
If i want to change the gsi img then should i clean flash the los 15.1 again?
Click to expand...
Click to collapse
No. Just don't wipe vendor & boot just change GSI
Sent from my Phh-Treble vanilla using Tapatalk
abhayruparel said:
No. Just don't wipe vendor & boot just change GSI
Click to expand...
Click to collapse
Thank you for reply
1) If i go to recovery and flash the new GSI img without anything wipe then it'll work?
2) If i want to go back to Los then how to do it?
Thx abhayruparel.
There is not an aosp p beta yet, no?
After flashing GSI NFC is not working
I can't make any gsi work.Always returns password and reset phone screens on reboot.Entering password says password accepted but decryption unsuccessful.Reset phone takes to TWRP but does nothing and reboots to the same password screen.What to do?
rexit1979 said:
I can't make any gsi work.Always returns password and reset phone screens on reboot.Entering password says password accepted but decryption unsuccessful.Reset phone takes to TWRP but does nothing and reboots to the same password screen.What to do?
Click to expand...
Click to collapse
Changing system and data to ext4 will do the trick probably
Miltonbaidya88 said:
Changing system and data to ext4 will do the trick probably
Click to expand...
Click to collapse
Both are already on ext4.
After flashing gsi got decryption unsuccessful error. How to solve that?
something is very wrong......
First if I flash lineage then any other gsi like pixel experience, it gives me decryption unsuccessful error.... I'm not even able to format the storage to remove encryption. I did format the encryption using an older version of twrp as the twrp provided for treble gives an error like ''
Unable to format data. Unble to remove encryption
-Now When I formatted data using earlier twrp and hen flashed the treble one and then flashed lineage. Booted and it still encrypted my phone. So the loop goes on again.
I dont know whats wrong. Treble flashing should be easy... been awake since last night trying to make it ork by using different combinations but no luck.
can anyone help?
Is there any way to enable volte in GSI?
guys, i have a little confusion:
What's the correct procedure for reinstall the stock OOS from a custom rom and the procedure for change custom rom to another one?
i ask this because every time i try i brick the phone. (so msmntool and lose internal storage)
my latest experiment:
i was on Havoc, rooted and blue_twrp
full wiped (cache's, data and system)
installed Full 9.0 OTA+ twrp on slot A
rebooted to twrp
installed again Full 9.0 OTA+ twrp on slot B
installed magisk
rebooted to system...
keep boot on recovery and also i canno't decrypt sdcard because twrp doesn't ask me the pin....
someone suggested to me to format data, but i don't want to lose my internal storage anytime...
help?
The best thing to do to avoid all of thi bs is to follow this guide:
https://forum.xda-developers.com/oneplus-6/how-to/tutorial-decrypt-flash-rom-pie-oreo-roms-t3838643
vivmar said:
guys, i have a little confusion:
What's the correct procedure for reinstall the stock OOS from a custom rom and the procedure for change custom rom to another one?
i ask this because every time i try i brick the phone. (so msmntool and lose internal storage)
my latest experiment:
i was on Havoc, rooted and blue_twrp
full wiped (cache's, data and system)
installed Full 9.0 OTA+ twrp on slot A
rebooted to twrp
installed again Full 9.0 OTA+ twrp on slot B
installed magisk
rebooted to system...
keep boot on recovery and also i canno't decrypt sdcard because twrp doesn't ask me the pin....
someone suggested to me to format data, but i don't want to lose my internal storage anytime...
help?
Click to expand...
Click to collapse
You dont have to flash the rom to both the slots. Just make a clean flash without format data.
First of all, Stay Encrypted :laugh:
Now from custom rom to Oxygen OS make a clean flash so follow the below:
Must Use Bluspark TWRP
1. Wipe Dalvik, System, Data & Cache
2. Flash the Full OxygenOS Rom Full Zip (Links available on my threads Beta or Stable Pie)
3. Flash the TWRP installer Zip
4. Reboot to RECOVERY to make sure TWRP stays and continue to root.
5. Flash Magisk Stable to maintain root (Avoid Beta)
6. Reboot System and Enjoy the latest firmware without any data loss
Make sure you follow above and also make sure:
1. Use Bluspark TWRP
2. Move from Pie To Pie / Pie to Oreo or Oreo to Pie might require a format.
Similarly follow the same if you want to move from Oxygen OS to Custom Rom, check the rom thread if the developer needs you to flash anything extra or firmware files.
Hope the above helps :good:
Funk Wizard said:
You dont have to flash the rom to both the slots. Just make a clean flash without format data.
First of all, Stay Encrypted :laugh:
Now from custom rom to Oxygen OS make a clean flash so follow the below:
Must Use Bluspark TWRP
1. Wipe Dalvik, System, Data & Cache
2. Flash the Full OxygenOS Rom Full Zip (Links available on my threads Beta or Stable Pie)
3. Flash the TWRP installer Zip
4. Reboot to RECOVERY to make sure TWRP stays and continue to root.
5. Flash Magisk Stable to maintain root (Avoid Beta)
6. Reboot System and Enjoy the latest firmware without any data loss
Make sure you follow above and also make sure:
1. Use Bluspark TWRP
2. Move from Pie To Pie / Pie to Oreo or Oreo to Pie might require a format.
Similarly follow the same if you want to move from Oxygen OS to Custom Rom, check the rom thread if the developer needs you to flash anything extra or firmware files.
Hope the above helps :good:
Click to expand...
Click to collapse
Thanks so much!
Hey guys. Iam trying 1 week to get Havoc Oreo.
I used this https://forums.oneplus.com/threads/oxygenos-9-0-ota-for-the-oneplus-6.909533/ to get base Oreo Rom on my OP6. This works.
But when i want to flash Havoc Oreo (Havoc-OS-20180904-enchilada-Official.zip) via TWRP (twrp-installer-enchilada-3.2.2-0.zip only this Version works for me) i get a loop in fastboot.
Can someone help me pls?
My instruction:
1. Flash downgrade
2. Go fastboot, boot TWRP
3. Flash TWRP via ADB SIDELOAD
4. Restart to recovery
5. Flash Havoc Oreo via ADB SIDELOAD
6. Restart
7. Bootloop Fastboot mode
thanks for any help.
RockstarLover said:
Hey guys. Iam trying 1 week to get Havoc Oreo.
I used this https://forums.oneplus.com/threads/oxygenos-9-0-ota-for-the-oneplus-6.909533/ to get base Oreo Rom on my OP6. This works.
But when i want to flash Havoc Oreo (Havoc-OS-20180904-enchilada-Official.zip) via TWRP (twrp-installer-enchilada-3.2.2-0.zip only this Version works for me) i get a loop in fastboot.
Can someone help me pls?
My instruction:
1. Flash downgrade
2. Go fastboot, boot TWRP
3. Flash TWRP via ADB SIDELOAD
4. Restart to recovery
5. Flash Havoc Oreo via ADB SIDELOAD
6. Restart
7. Bootloop Fastboot mode
thanks for any help.
Click to expand...
Click to collapse
OK, so I am not sure what exists in the OnePlus forums but lets start with:
1. You are aware there are two sets of partitions on this device correct? If not, please read here: https://forum.xda-developers.com/oneplus-6/how-to/guide-noobs-guide-to-b-partitions-op6-t3816123
2. What are you running now?
3. You need to update your TWRP to blu_spark but I am not sure if the latest (v9.91) works with Oreo... I know that v9.86 works with Oreo for sure. Read and download from here: https://forum.xda-developers.com/oneplus-6/development/kernel-t3800965
4. Get the appropriate OOS zip file from this thread: https://forum.xda-developers.com/oneplus-6/how-to/oneplus-6-mirrors-official-oxygen-os-t3792244
Specifically OOS 5.1.11: https://www.androidfilehost.com/?fid=1322778262903980680
The basic steps should be like this (all assumes you have and unlocked bootloader):
1. If you are running OOS 5.1.11, reboot to fastboot
2. Boot blu_spark TWRP.img - fastboot boot twrp.xxx.img
3. Flash OOS 5.1.11
4. Flash blu_spark TWRP.zip to get it on both slots
5. Reboot to RECOVERY
6. Flash OOS 5.1.11
7. Flash blu_spark TWRP.zip
8. Factory reset in TWRP
9. Flash Havoc Oreo zip
10. Flash blu_spark TWRP.zip
11. Reboot to RECOVERY
12. Flash GApps
13. Flash Magisk (optional if you want root)
14. Flash no-verity if you plan to run unencrypted. (optional)
My advice is to READ READ READ before going forward with anything. The A/B partition layout is far from the traditional days of a single partition layout with a recovery partition. Educate yourself or risk bricking your device and opening up a whole different set of problems.
i do this by step by step but now iam bricked. after all it want restart but it glows only the blue led
RockstarLover said:
i do this by step by step but now iam bricked. after all it want restart but it glows only the blue led
Click to expand...
Click to collapse
It does sound like you READ READ READ before proceeding... My steps were not intended as a step-by-step guide, which is why I said the steps "should look like this". You didn't answer any of my questions, so I have no idea where you started from or where things went wrong to get you into this state...
Can you get into fastboot mode?
If so, try this thread first: https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
The fastboot restore method will ONLY work if you know which OOS you were running before you got bricked...
If you can't restore from fastboot images, try this thread: https://forum.xda-developers.com/oneplus-6/how-to/tool-msmdownloadtool-v4-0-international-t3798892
I cannot stress enough, you MUST read all the steps and understand what you are doing before doing anything. If you have any questions, ASK before proceeding... Good luck.
thank u for ur help. i used the second method because the first didnt worked and now iam unbricked.
1. You are aware there are two sets of partitions on this device correct?
Click to expand...
Click to collapse
I know it
2. What are you running now?
Click to expand...
Click to collapse
Now iam running Oxygen OS 5.1.5 Android 8.1.0 and Device State is locked
Is this normal that in fastboot shows this bootloader and baseband empty ?
productname - xxx
variant -sdm ufs
bootloader version -
baseband version -
serialnumber - xxxxxxx
secure boot - yes
I want to try again to get havoc oreo. i will w8 for ur response.
RockstarLover said:
thank u for ur help. i used the second method because the first didnt worked and now iam unbricked.
I know it
Now iam running Oxygen OS 5.1.5 Android 8.1.0 and Device State is locked
Is this normal that in fastboot shows this bootloader and baseband empty ?
productname - xxx
variant -sdm ufs
bootloader version -
baseband version -
serialnumber - xxxxxxx
secure boot - yes
I want to try again to get havoc oreo. i will w8 for ur response.
Click to expand...
Click to collapse
You are back up and running, good work! Congrats!
When you say the device is 'locked', you mean the bootloader is locked again? It shows 'Locked' in fastboot? Obviously you need to unlock the bootloader again before proceeding if this is the case...
And 'Yes', it is normal for 'bootloader version' and 'baseband' to be blank. It shows the same on my device anyway, and I can flash custom ROMs with no issues, and everything works.
At this point, you should be able to follow the steps in my post, making sure you first unlock the bootloader (which will wipe all of your data). You might want to format data (not just wipe as well) to start fresh. I would also confirm that there are no issues running Havoc Oreo with encryption (I'd recommend asking the question in the Havoc OnePlus telegram channel, https://t.me/havoconeplus). After people ask to "Why are you running Oreo?!?!", you just might get an answer... I dumped being encrypted after about a week of having this device because it made moving between ROMs more difficult.
In step 14, I mention the no-verity file to remove force encryption. I have attached it to this post. Again, you may want to have /data encrypted (necessity, personal preference etc.) so this isn't mandatory but I found it made flashing different ROM's much easier (personal preference really).
do u know where u find the havoc oreo rom now ? they changed their download directory. and the overview is confusing me.
RockstarLover said:
do u know where u find the havoc oreo rom now ? they changed their download directory. and the overview is confusing me.
Click to expand...
Click to collapse
Looks like they removed Oreo builds, you might be out of luck. Check out XenonHD 8.1 thread if your set on running Oreo, was updated to Dec. Security patch.
hey brother. i have good news. i just want download again havoc oreo cause i deleted the old zip. i had thought maybe the oreo havoc zip was faulty. now i restored it with a restore tool. i tried again and now it works.
IAM ON HAVOC OREO . It starts but now i got a message.
"Android System
A vendor image mismatch has been detected. Typically this means your vendor image is out of date.Please ensure your vendor image matches OPM1.171019.011."
what is this now
RockstarLover said:
hey brother. i have good news. i just want download again havoc oreo cause i deleted the old zip. i had thought maybe the oreo havoc zip was faulty. now i restored it with a restore tool. i tried again and now it works.
IAM ON HAVOC OREO . It starts but now i got a message.
"Android System
A vendor image mismatch has been detected. Typically this means your vendor image is out of date.Please ensure your vendor image matches OPM1.171019.011."
what is this now
Click to expand...
Click to collapse
Did you flash OOS 5.1.11 on both slots? I know you said you were on OOS 5.1.5 when you did the MSM tool restore.
Unsure if the Havoc build you are running requires a certain FW. Usually the devs update the blobs on customer ROMs based on the latest releases of OOS. In this case, 5.1.11 was the last version of OOS Oreo.
i was on 5.1.5 and flashed 5.1.11 on both slots and then i flashed havoc rom
RockstarLover said:
i was on 5.1.5 and flashed 5.1.11 on both slots and then i flashed havoc rom
Click to expand...
Click to collapse
I'd recommend just going to Pie. I haven't run Havoc in over a month but the latest AEX is solid and battery life is excellent. The Pie ROMs have stabilized significantly in the last month.
i just flashed the latest havoc rom now. Really really thanks brother. ur a good boy.
have a good year
Hello!
I am on an older version of Android 11 and I would like to install the latest Android 11 OTA without losing root and TWRP.
I know that I could just manually flash the lasted Android 11 firmware, then re-install TWRP and Magisk, but this would mean losing all data and having to reinstall apps, restore backups, etc...
So I was wondering if there were a quicker way to install OTA updates without losing data and root.
I know that there are many articles on the subject but they all refer to a previous version of TWRP and Magisk. Because TWRP 3.6.0 sports a completely revamped codebase I would like to know what is the latest recommended method if any.
This is my system info:
Android 11 sargo-rq1a.201105.002-factory-2433e0c0
Magisk v23
TWRP 3.6.0-11_0
Japan region
PS I do not intend to update to Android 12 yet
I ended up flashing the latest version of the stock firmware and reinstalling TWRP and root. However if you have a solution please post it for future reference.
I was looking for the same thing, didn't find any good solution, however, you can edit the flash-all script so that it doesn't wipe your data (remove the -w argument if I remember well).
reyqn said:
I was looking for the same thing, didn't find any good solution, however, you can edit the flash-all script so that it doesn't wipe your data (remove the -w argument if I remember well).
Click to expand...
Click to collapse
The flashall script will still remove TWRP and root though, right?
blksith0 said:
The flashall script will still remove TWRP and root though, right?
Click to expand...
Click to collapse
Yeah it does, you have to reflash them after
It's annoying that we can't choose the OTA android installs, it has to be the latest one. On some phones you can choose a local file, but I didn't find a way to do so with a pixel 3a.
If you were able to do this, in theory you could just flash the magisk module for twrp retention and preflash magisk on the unactive partition after installing the ota but before rebooting. Then just reboot and you keep everything.
I'm not ready to update to android 12 either (gravitybox, twrp), but I'll try then...
LastStarDust said:
I ended up flashing the latest version of the stock firmware and reinstalling TWRP and root. However if you have a solution please post it for future reference.
Click to expand...
Click to collapse
I don't understand. Just flash the Full Factory OTA zip in TWRP. That won't remove any data. And you can just check the box to "Automatically flash TWRP after zip" so that you'll keep whatever TWRP you're using. Then you just have to reboot recovery (so that you're on the updated slot) and flash the Magisk APK in TWRP. Reboot and profit.
P.S. This post belongs in Q&A.
Captain_Throwback said:
I don't understand. Just flash the Full Factory OTA zip in TWRP
Click to expand...
Click to collapse
I wondered if you could do this, apparently TWRP doesn't recommend it.
Also I had no idea how this works on a device with A/B partitions. Does TWRP automatically flash on the inactive partition?
reyqn said:
I wondered if you could do this, apparently TWRP doesn't recommend it.
Also I had no idea how this works on a device with A/B partitions. Does TWRP automatically flash on the inactive partition?
Click to expand...
Click to collapse
That 'recommendation' is specific to incremental OTAs. Also, it not generally being supported isn't the same as it not being recommended.
TWRP will install the zip to the inactive slot, and then when you reboot, the device will automatically boot into the updated slot.
Thanks for the precisions, I'll know for the next time. TWRP really is awesome
hi everyone, i flashed pixel 3a to android 12 and now my imei is 004400.... and no service ..... what should i do?
I am still trying to fully wrap my head around Android moving to Slot partitions. I am reading as much as I can and feel I have a better understanding of it but have tried to flash lineageOS with microg but ended up with a bricked device maybe due to not doing the proper steps to switch to the active slot? My question is if I have TWRP installed and currently on OOS 11, can I just flash the zip file for lineage OS or so I need to do something additional? The TWRP script states you have to boot into Recovery to switch active slots and flash additional items. I know if I flash lineage I will end up with their Recovery as well which I obviously dont want. Can I flash the TWRP installer after flashing lineageOS zip or no? Please help confirm or deny what needs to be done given my current setup.
Thank you all in advance for any help/experiences you can share about this.