Develop Bugs

Oreo update for rooted OnePlus 5t

Pls help me updating my 5t to oreo.i am currently on version 4.7.6 with twrp recovery nd super su root.
After updating to Oreo I again want to root my phone
Pls share links to download compatibile ROM, recovery nd super su.zip

But you already have the OREO OOS ROM installed, why not use it? Flash the Oreo recovery from codeworkx through fastboot, make sure to follow the instructions so it sticks and then flash Magisk or any root solution of your choice. It's not hard if you do some searching.

Check in ROMs' threads and come back what your interested ROM is.

What I did was flash the ota to update me to Oreo. Then had to reflash Magisk and kernel.

jcroy2828 said:
What I did was flash the ota to update me to Oreo. Then had to reflash Magisk and kernel.
Click to expand...
Click to collapse
Kernel?

jcroy2828 said:
What I did was flash the ota to update me to Oreo. Then had to reflash Magisk and kernel.
Click to expand...
Click to collapse
Pls give me link to download magisk nd what does kernel mean?

mannulko said:
Kernel?
Click to expand...
Click to collapse
Il check when I get home. I just used Magisk 15.3 from the Magisk xda thread

jcroy2828 said:
Il check when I get home. I just used Magisk 15.3 from the Magisk xda thread
Click to expand...
Click to collapse
I mean pls tell me step by step what should I do.currently I am on 4.7.6 wth twrp recovery nd rooted.i want to update my phone to Oreo nd root again

mannulko said:
I mean pls tell me step by step what should I do.currently I am on 4.7.6 wth twrp recovery nd rooted.i want to update my phone to Oreo nd root again
Click to expand...
Click to collapse
If you have already installed a custom recovery and rooted your phone then you should be able to follow these instructions.
I can personally confirm that I was able to install the beta versions of Oreo and the final version of Oreo without any issues.
Here's what I did:
1. Download full .zip
2. Download Blu_Spark TWRP or Codeworkx TWRP (I personally used Blu_Spark but both should work).
3. Download Magisk 15.3 (I havent used SuperSu in a while so I can't confirm how well it works on Oreo but in my opinion Magisk is a better root method and it works in this version of android).
4. Make sure you have both ROM and Magisk on a easy to find place on your phone.
5. Boot to fastboot and fastboot flash the recovery you just downloaded.
6. Boot to recovery, wipe dalvik and cache and then install the ROM.
7. Once the installation is done, boot to system and wait till the system to finish updating. Once there you can go to settings > phone status and it should read (android version = 8.0.0 and OxygenOS version = 5.0.2, congrats, you're on the latest OxygenOS version for this phone).
8. Reboot to fastboot, and fastboot flash the custom recovery again.
9. Boot to recovery, wipe dalvik and cache again, and flash Magisk, wipe dalvik and cache once more and reboot to system.
10. Once the phone is booted up, you should be rooted with Magisk and on the latest OS.
9. Boot to recovery, wipe dalvik and cache again, and flash Magisk, wipe dalvik and cache once more and reboot to system.
10. Once the phone is booted up, you should be rooted with Magisk and on the latest OS.
NOTE: Since this is a big version update from Nougat, it's always recommended to do a clean flash although not necessary in most cases unless there are issues like big battery drain or when apps or the OS are not working properly. Also, if you are coming from a custom ROM and not the official OxygenOS, then you should definitely do a clean installation (even if said custom ROM is based on OxygenOS).

HueleSnaiL said:
If you have already installed a custom recovery and rooted your phone then you should be able to follow these instructions.
I can personally confirm that I was able to install the beta versions of Oreo and the final version of Oreo without any issues.
Here's what I did:
1. Download full .zip
2. Download Blu_Spark TWRP or Codeworkx TWRP (I personally used Blu_Spark but both should work).
3. Download Magisk 15.3 (I havent used SuperSu in a while so I can't confirm how well it works on Oreo but in my opinion Magisk is a better root method and it works in this version of android).
4. Make sure you have both ROM and Magisk on a easy to find place on your phone.
5. Boot to fastboot and fastboot flash the recovery you just downloaded.
6. Boot to recovery, wipe dalvik and cache and then install the ROM.
7. Once the installation is done, boot to system and wait till the system to finish updating. Once there you can go to settings > phone status and it should read (android version = 8.0.0 and OxygenOS version = 5.0.2, congrats, you're on the latest OxygenOS version for this phone).
8. Reboot to fastboot, and fastboot flash the custom recovery again.
9. Boot to recovery, wipe dalvik and cache again, and flash Magisk, wipe dalvik and cache once more and reboot to system.
10. Once the phone is booted up, you should be rooted with Magisk and on the latest OS.
9. Boot to recovery, wipe dalvik and cache again, and flash Magisk, wipe dalvik and cache once more and reboot to system.
10. Once the phone is booted up, you should be rooted with Magisk and on the latest OS.
NOTE: Since this is a big version update from Nougat, it's always recommended to do a clean flash although not necessary in most cases unless there are issues like big battery drain or when apps or the OS are not working properly. Also, if you are coming from a custom ROM and not the official OxygenOS, then you should definitely do a clean installation (even if said custom ROM is based on OxygenOS).
Click to expand...
Click to collapse
What is clean flash?

HueleSnaiL said:
If you have already installed a custom recovery and rooted your phone then you should be able to follow these instructions.
I can personally confirm that I was able to install the beta versions of Oreo and the final version of Oreo without any issues.
Here's what I did:
1. Download full .zip
2. Download Blu_Spark TWRP or Codeworkx TWRP (I personally used Blu_Spark but both should work).
3. Download Magisk 15.3 (I havent used SuperSu in a while so I can't confirm how well it works on Oreo but in my opinion Magisk is a better root method and it works in this version of android).
4. Make sure you have both ROM and Magisk on a easy to find place on your phone.
5. Boot to fastboot and fastboot flash the recovery you just downloaded.
6. Boot to recovery, wipe dalvik and cache and then install the ROM.
7. Once the installation is done, boot to system and wait till the system to finish updating. Once there you can go to settings > phone status and it should read (android version = 8.0.0 and OxygenOS version = 5.0.2, congrats, you're on the latest OxygenOS version for this phone).
8. Reboot to fastboot, and fastboot flash the custom recovery again.
9. Boot to recovery, wipe dalvik and cache again, and flash Magisk, wipe dalvik and cache once more and reboot to system.
10. Once the phone is booted up, you should be rooted with Magisk and on the latest OS.
9. Boot to recovery, wipe dalvik and cache again, and flash Magisk, wipe dalvik and cache once more and reboot to system.
10. Once the phone is booted up, you should be rooted with Magisk and on the latest OS.
NOTE: Since this is a big version update from Nougat, it's always recommended to do a clean flash although not necessary in most cases unless there are issues like big battery drain or when apps or the OS are not working properly. Also, if you are coming from a custom ROM and not the official OxygenOS, then you should definitely do a clean installation (even if said custom ROM is based on OxygenOS).
Click to expand...
Click to collapse
Will the official TWRP work with no problem?
I'm already on 4.7.6, offical twrp-3.2.1-1-dumpling and magisk 15.3, and don't really want to flash another recovery.

HueleSnaiL said:
If you have already installed a custom recovery and rooted your phone then you should be able to follow these instructions.
I can personally confirm that I was able to install the beta versions of Oreo and the final version of Oreo without any issues.
Here's what I did:
1. Download full .zip
2. Download Blu_Spark TWRP or Codeworkx TWRP (I personally used Blu_Spark but both should work).
3. Download Magisk 15.3 (I havent used SuperSu in a while so I can't confirm how well it works on Oreo but in my opinion Magisk is a better root method and it works in this version of android).
4. Make sure you have both ROM and Magisk on a easy to find place on your phone.
5. Boot to fastboot and fastboot flash the recovery you just downloaded.
6. Boot to recovery, wipe dalvik and cache and then install the ROM.
7. Once the installation is done, boot to system and wait till the system to finish updating. Once there you can go to settings > phone status and it should read (android version = 8.0.0 and OxygenOS version = 5.0.2, congrats, you're on the latest OxygenOS version for this phone).
8. Reboot to fastboot, and fastboot flash the custom recovery again.
9. Boot to recovery, wipe dalvik and cache again, and flash Magisk, wipe dalvik and cache once more and reboot to system.
10. Once the phone is booted up, you should be rooted with Magisk and on the latest OS.
9. Boot to recovery, wipe dalvik and cache again, and flash Magisk, wipe dalvik and cache once more and reboot to system.
10. Once the phone is booted up, you should be rooted with Magisk and on the latest OS.
NOTE: Since this is a big version update from Nougat, it's always recommended to do a clean flash although not necessary in most cases unless there are issues like big battery drain or when apps or the OS are not working properly. Also, if you are coming from a custom ROM and not the official OxygenOS, then you should definitely do a clean installation (even if said custom ROM is based on OxygenOS).
Click to expand...
Click to collapse
Thanks a lot I have updated nd rooted but now 5.0.3 is out ? how to go from 5.0.2 to 5.0.3 nd root
I also wanna format my 5t

mannulko said:
What is clean flash?
Click to expand...
Click to collapse
Wiping data and system partition which means you're wiping the entire OS and installing the new version on a clean partition. Think of it as formatting a hard drive and installing an OS instead of just upgrading your existing OS.
You obviously lose all apps installed,and it would be like when you first turned on your phone, however as long as you don't wipe internal storage, all your photos,music,etc are not wiped so you can use apps like titanium backup to restore all apps and data .
This method is recommended when switching from different custom ROM's and when upgrading from major version updates, like for example, going to Android 8 from Andorid 7.
---------- Post added at 07:13 PM ---------- Previous post was at 07:09 PM ----------
rockuman_ex said:
Will the official TWRP work with no problem?
I'm already on 4.7.6, offical twrp-3.2.1-1-dumpling and magisk 15.3, and don't really want to flash another recovery.
Click to expand...
Click to collapse
I used that same version of TWRP back during the Oreo beta and it didn't work so I had to switch to blu_spark.

HueleSnaiL said:
Wiping data and system partition which means you're wiping the entire OS and installing the new version on a clean partition. Think of it as formatting a hard drive and installing an OS instead of just upgrading your existing OS.
You obviously lose all apps installed,and it would be like when you first turned on your phone, however as long as you don't wipe internal storage, all your photos,music,etc are not wiped so you can use apps like titanium backup to restore all apps and data .
This method is recommended when switching from different custom ROM's and when upgrading from major version updates, like for example, going to Android 8 from Andorid 7.
---------- Post added at 07:13 PM ---------- Previous post was at 07:09 PM ----------
I used that same version of TWRP back during the Oreo beta and it didn't work so I had to switch to blu_spark.
Click to expand...
Click to collapse
So i took the jump and flashed blu spark and the 5.0.3 full rom.
Yes i lost the recovery to stock, but that's ok. Just want to get OTA in the future and I don't need root at the moment.
So this is what i did (coming from 4.7.6, official twrp, magisk 15.3)
Make sure you have all the necessary files (eg. blu spark img file and the full ota file on your phone
boot the fastboot and "fastboot flash recovery twrp-3.2.1-x_blu_spark_v8.68-op5_op5t.img"
On the phone, choose and go to recovery
(now i'm on blu spark) Wipe Cache and Dalvik cache (i did this 2 times just to make sure)
Choose install and select the full ota rom file
Let it run and install the rom (took less than 5 mins)
Wipe Cache and Dalvik cache again (again, i wiped 2 times just to make sure)
Reboot
Make take a while (less than 10mins) for android to start and do the upgrade etc
Done
So far so good, i don't see any immediate problem. I will play a bit more and will post if I encounter any problem :good:

I have updated to 5.0.3 through system update app. where it downloaded full ota file and installed.Now I want to install twrp nd root my phone so pls confirm my steps
1 boot into fastboot mode and flash bluespark recovery
2 wipe delvik/cache from twrp recovery
3 flash magisk zip
4 again wipe delvik cache
5 reboot
are above steps correct?

Hello,
i have latest (8.69) twrp blue_spark and i try to flash latest oxygen os
1)Oreo 5.0.3: OnePlus5TOxygen_43_OTA_029_all_1802022353_460d.zip
2)magisk 15.3
3)wipe davlik/cache
reboot system and i get stucked at bootanimation of OxygenOS.
Any help guys please ?
Thanks!
Redownloaded Magisk 15.3 and ok

BrollyG4 said:
Hello,
i have latest (8.69) twrp blue_spark and i try to flash latest oxygen os
1)Oreo 5.0.3: OnePlus5TOxygen_43_OTA_029_all_1802022353_460d.zip
2)magisk 15.3
3)wipe davlik/cache
reboot system and i get stucked at bootanimation of OxygenOS.
Any help guys please ?
Thanks!
Redownloaded Magisk 15.3 and ok
Click to expand...
Click to collapse
I'm having the same problem, I think it's version (8.69) twrp blue_spark. I'll try with version 8.68

OOS 5.1.0 Bootloop After Flashing Magisk

As the title says I am unable to boot after flashing Magisk (tried v16 and v15.3). It boots fine without magisk but of course no root and no custom recovery. Any help would be appreciated. Didn't have any problems on the previous stable build.

You need to first flash OOS 5.1 let it boot, then go to fastboot and flash twrp then go to twrp and flash magisk, only way to get root

hello, that's what I did and it worked well

this has happened here since 5.0.4

Try to use lastest blu-spark's TWRP, then flash 5.1 & Magisk without extra boot in the middle.

Things I noticed when upgrading:
A) The latest TWRP for dumpling appears to be broken. I get an error mounting /vendor when I use it. I switched to the previous version (20180309) and the error went away and everything seems to work.
B) You may very well have Xposed installed. If you do, there is an SDK bump between OOS 5.0.x and 5.1.x (26 -> 27). You'll need to disable this module either before you install the update (or assuming you already have) remove the module using something like Magisk Manager for Recovery to remove it (reboot to recovery, install module, run mm from terminal, follow prompts).
-Toucan

ToucanSam said:
Things I noticed when upgrading:
A) The latest TWRP for dumpling appears to be broken. I get an error mounting /vendor when I use it. I switched to the previous version (20180309) and the error went away and everything seems to work.
B) You may very well have Xposed installed. If you do, there is an SDK bump between OOS 5.0.x and 5.1.x (26 -> 27). You'll need to disable this module either before you install the update (or assuming you already have) remove the module using something like Magisk Manager for Recovery to remove it (reboot to recovery, install module, run mm from terminal, follow prompts).
-Toucan
Click to expand...
Click to collapse
It's not broken. The vendor error message is because it was recently updated to work better with Project treble, which uses a hidden partition for the vendor. You can simply ignore the error and it will work fine. Or if you flash a treble ROM, the error will then go away.

I just got the phone. Format it in recovery.
Flash latest blu spark twrp (v.8.73).
Flash the Oos ob06.
Reboot to system. Set the phone, instal apps from Play.
Reboot to Fastboot.
Reflash recovery.
Reboot to recovery.
Flash Magisk 15.3. Reboot to system. OK.
Updated Magisk with Magisk.

Hi, Can anyone help me. in my oneplus 5T after installing new rom it is working smooth but i can't upgrade to new updates. in recovery mode the files seems to be decrypted and cant find any folders where i copied the updation . instead new files are found and can't access and find any of the folders of my own. this happened after i input the security lock. i wiped the entire data and installed new roms still it seems so. somebody please help me to find a solution for this

Magisk Issues on Fresh System Image Install (Feb. 2019)

I'm going nuts here. I can't get Magisk to install properly on a Pixel device.
1) Pixel XL (non-Verizon and unlocked)
2) OS - Stock Android 9.0 / Feb. 2019 - System Image just installed fresh
3) TWRP 3.2.3.1 loaded image via fastboot
4) Magisk version 18.1 installed
Issue: Device stuck at Can't load Android system. The only way to fix it is to install the Magisk uninstaller but then I still don't have root.
I tried removing my pin (read that in the thread) and the issue still persists. I also tried an older version of Magsik and tried patching the boot.img file with the same result.
Has anyone rooted a clean install of the Feb. 2019 Android 9.0 system image? I'm at a loss. The only thing I can think to do at this point is try an older system image and see what happens.

clambert11 said:
I'm going nuts here. I can't get Magisk to install properly on a Pixel device.
1) Pixel XL (non-Verizon and unlocked)
2) OS - Stock Android 9.0 / Feb. 2019 - System Image just installed fresh
3) TWRP 3.2.3.1 loaded image via fastboot
4) Magisk version 18.1 installed
Issue: Device stuck at Can't load Android system. The only way to fix it is to install the Magisk uninstaller but then I still don't have root.
I tried removing my pin (read that in the thread) and the issue still persists. I also tried an older version of Magsik and tried patching the boot.img file with the same result.
Has anyone rooted a clean install of the Feb. 2019 Android 9.0 system image? I'm at a loss. The only thing I can think to do at this point is try an older system image and see what happens.
Click to expand...
Click to collapse
I flashed the Feb 2019 Factory image and was able to fastboot boot TWRP and successfully install Magisk 18.1. Are you flashing TWRP (permanent install?) or booting it? You might try booting it only to install Magisk to minimize your variables. Have you tried reflashing the full Factory image clean to ensure you truly have a good initial install before trying to install Magisk? Platform tools up to date? Your steps seem to be pretty straightforward - so not sure what could be going wrong. Good luck!

sb1893 said:
I flashed the Feb 2019 Factory image and was able to fastboot boot TWRP and successfully install Magisk 18.1. Are you flashing TWRP (permanent install?) or booting it? You might try booting it only to install Magisk to minimize your variables. Have you tried reflashing the full Factory image clean to ensure you truly have a good initial install before trying to install Magisk? Platform tools up to date? Your steps seem to be pretty straightforward - so not sure what could be going wrong. Good luck!
Click to expand...
Click to collapse
I'm not flashing TWRP, just booting into it. My platform tools were a little out of date initially but I have since updated them. I think I was 2 major versions behind.
Guess I'll just do it again. I'll try it first without restoring data since that takes forever for me (lots of apps). Thanks for the info. It's reassuring that it should work.

clambert11 said:
I'm not flashing TWRP, just booting into it. My platform tools were a little out of date initially but I have since updated them. I think I was 2 major versions behind.
Guess I'll just do it again. I'll try it first without restoring data since that takes forever for me (lots of apps). Thanks for the info. It's reassuring that it should work.
Click to expand...
Click to collapse
If your platform-tools are r28.0.1
- fastboot flash boot boot.img --slot all
- fastboot boot twrp-3.2.3-1.img
- install ElementalX kernel
- tap Add more zips
- select Magisk-18.1.zip
- swipe slider to install
- reboot

Just wanted to update... Updating the Package Tools and reinstalling the factory image fixed my problem. Thanks for the info!

clambert11 said:
Just wanted to update... Updating the Package Tools and reinstalling the factory image fixed my problem. Thanks for the info!
Click to expand...
Click to collapse

I have a similar issue. I have updated platform-tools and still get the unbootable issue with Magisk. I installed the latest factory firmware and didn't erase -w so it is a fresh install. I do want to use the TWRP recovery, so I sideload that first and then side load Magisk-18.1.zip and it has the big G for a while, then reboots into recovery. I am able to run Magisk uninstaller and everything goes back to normal (sans root, of course). Any further advice?

Ivanstein said:
I have a similar issue. I have updated platform-tools and still get the unbootable issue with Magisk. I installed the latest factory firmware and didn't erase -w so it is a fresh install. I do want to use the TWRP recovery, so I sideload that first and then side load Magisk-18.1.zip and it has the big G for a while, then reboots into recovery. I am able to run Magisk uninstaller and everything goes back to normal (sans root, of course). Any further advice?
Click to expand...
Click to collapse
Forget side loading!
- fastboot flash boot boot.img --slot all
- fastboot boot twrp-3.2.3-1.img
- tap install select Twrp-3.2.3-1.zip
- swipe slider to install
- reboot recovery
- tap install select Magisk-18.1.zip
- swipe slider to install
- reboot

HELP! Bootloop when trying to Install Pixel Experience Plus

Have tried to clean flash latest PE Plus ROM 3 times today. I have a recovery backup of Havoc that I was able to get back to, but can't get past Google boot screen when flashing PE Plus.
Here is my process.
- Download latest Pixel Experience Plus (file name PixelExperience_Plus_whyred-9.0-20190906-0859-OFFICIAL.zip from Pixel Experience website) and save to SD card
- Download Magisk 19.3.zip from Magisk and save to SD card
- Download latest firmware from xiaomifirmwareupdater.com (stable, V10.3.2.0.PEIMIXM, 9.0 Global)
- Boot to TWRP 3.3.1-0
- Press Wipe - Wipe - Davlik, Cache, Data, System, Vendor
- Press install - Choose firmware file (stable V10.3.2.0.PEIMIXM 9.0 Global)
- Swipe to install
- Back home
- Press Install - Choose PixelExperience file from SD Card, press Add Zip, Choose Magisk 19.3zip from SD card
- Swipe to install
- After install finishes, choose swipe to reboot. Then choose swipe to install TWRP.
Phone reboots. Shows Mi logo for a couple seconds. Shows "Google" logo for a couple seconds. Google logo becomes the google multi-colored "G" with a progress bar going below the "G". Phone will stay here and not go any further.
Advice? Am I missing something in my flashing process?
Thank you in advance if you can help.

try not install magik on the first time booting

Tried to flash PE plus
used the same process
didn't flash magisk or any other type of root
same outcome, only thing different is that I lost my backup data after getting a password prompt on twrp and solve it like an idiot by wiping everything.
any help is appreciated I really like this rom :crying:
Edit: Fixed the problem by flashing again twrp recovery right after flashing the firmware, than proceeding with the same steps, Didn't take long in the fist boot. yet another problem, It's detecting my sim card and can't connect to wifi so I'm stuck on the setup; tried clean flashing another rom ( bootleggers) after I gave up on PEE but the same problem. I have no idea what to do now

I would start over with original miui fastboot rom via mi flash tool. It should make everything work again. Then you could try orangefox recovery instead of twrp to flash pixel experience rom.

lcdkhoa said:
try not install magik on the first time booting
Click to expand...
Click to collapse
when i installed PE it was clear and safe.. but install magisk 19.3 bootloop again...

nirvanakevin said:
when i installed PE it was clear and safe.. but install magisk 19.3 bootloop again...
Click to expand...
Click to collapse
Use magisk 20 .1

Redmi note 8 pro PE stuck bootloop G logo
nirvanakevin said:
when i installed PE it was clear and safe.. but install magisk 19.3 bootloop again...
Click to expand...
Click to collapse
I have a Redmi Note 8 pro used orange fox recovery and still the G google logo stuck. i tried everything its just not working
---------- Post added at 05:42 PM ---------- Previous post was at 05:38 PM ----------
nirvanakevin said:
when i installed PE it was clear and safe.. but install magisk 19.3 bootloop again...
Click to expand...
Click to collapse
Can you explain what steps you took to get the google PE to install safe

Hello,
I have a Redmi Note 8 Pro. I downloaded the ROM from PE site. https://download.pixelexperience.org/begonia. I install this ROM but after a reboot I can only see the REDMI Logog and than is a bootloop.
Any ideas?

Only way
the only way out is try clearing data partition in manage partition section of orange fox recovery or twrp,this would help but all data would be wiped.

Rarohd said:
Tried to flash PE plus
used the same process
didn't flash magisk or any other type of root
same outcome, only thing different is that I lost my backup data after getting a password prompt on twrp and solve it like an idiot by wiping everything.
any help is appreciated I really like this rom :crying:
Edit: Fixed the problem by flashing again twrp recovery right after flashing the firmware, than proceeding with the same steps, Didn't take long in the fist boot. yet another problem, It's detecting my sim card and can't connect to wifi so I'm stuck on the setup; tried clean flashing another rom ( bootleggers) after I gave up on PEE but the same problem. I have no idea what to do now
Click to expand...
Click to collapse
This is one freakin helpful information.Worked right away when facing same issue in my redmi 5a

Barker88 said:
Have tried to clean flash latest PE Plus ROM 3 times today. I have a recovery backup of Havoc that I was able to get back to, but can't get past Google boot screen when flashing PE Plus.
Here is my process.
- Download latest Pixel Experience Plus (file name PixelExperience_Plus_whyred-9.0-20190906-0859-OFFICIAL.zip from Pixel Experience website) and save to SD card
- Download Magisk 19.3.zip from Magisk and save to SD card
- Download latest firmware from xiaomifirmwareupdater.com (stable, V10.3.2.0.PEIMIXM, 9.0 Global)
- Boot to TWRP 3.3.1-0
- Press Wipe - Wipe - Davlik, Cache, Data, System, Vendor
- Press install - Choose firmware file (stable V10.3.2.0.PEIMIXM 9.0 Global)
- Swipe to install
- Back home
- Press Install - Choose PixelExperience file from SD Card, press Add Zip, Choose Magisk 19.3zip from SD card
- Swipe to install
- After install finishes, choose swipe to reboot. Then choose swipe to install TWRP.
Phone reboots. Shows Mi logo for a couple seconds. Shows "Google" logo for a couple seconds. Google logo becomes the google multi-colored "G" with a progress bar going below the "G". Phone will stay here and not go any further.
Advice? Am I missing something in my flashing process?
Thank you in advance if you can help.
Click to expand...
Click to collapse
WAIT FOR SOME TIME LIKE 10 MINUTES.. EVEN I THOUGHT IT WAS IN BOOT LOOP

Question Upgrade to LineageOS 19 gone wrong

I need help bad - can't figure out how to get my phone working again and it is basically stuck in fastboot.
This is a POCO F3 (alioth) and I previously had Lineage 18 and TWRP recovery installed (since I like to do full backups)
I flashed new firmware, then the OS, then gapps, rebooted, looks great. Awesome. Now I'm just gonna go back and install the latest TWRP and be done. This is where I must have gone wrong.
I used fastboot flash boot twrp.img with the latest version of TWRP (I had to do the same to sideload Lineage 19 since the older version I had was apparently not compatible and couldn't get the Lineage recovery to load) rebooted to recovery, and TWRP asked for my pattern to decrypt as usual. But it would not accept my pattern. I hit cancel, and because I didn't have access to my data I wasn't able to install TWRP by having it patch the ramdisk. Okay, maybe it's a glitch, I tried booting into TWRP again and got the same thing. When I went to reboot again I noticed the slot was A, instead of B which it had always been previously. So I thought maybe my system partition was on B and switching that would solve it. But after I switched that slot, TWRP has never gotten past the splash screen before it reboots and I can't boot into my system at all. Essentially the only thing I can boot into is Fastboot.
I have tried flashing the latest Lineage recovery (does not boot), an older version of TWRP (boots but sees none of my data) and stock MIUI boot.img (boots to recovery but has no options besides wipe).
I am at a loss here - I know I probably did something wrong in there, but is my system wiped? I have a lot of data on there I'd like to retain. I don't think it is wiped but I don't understand the a/b partition setup or why TWRP boot-loops on me. Any help would be greatly appreciated.

stevencrayne2 said:
Upgrade to LineageOS 19 gone wrong...
I need help bad - can't figure out how to get my phone working again and it is basically stuck in fastboot.
This is a POCO F3 (alioth) and I previously had Lineage 18 and TWRP recovery installed (since I like to do full backups)
Click to expand...
Click to collapse
FWIW althafvly who is one of the LineageOS maintainers of the Xiaomi POCO F3 / Redmi K40 / Mi 11X (alioth) wrote in the post #1 of his XDA thread [ROM][OFFICIAL][alioth/aliothin][12.1] LineageOS 19.1 *(bolded by him)*:
Flashing LineageOS through TWRP is NOT SUPPORTED and NOT ADVISED.
***

I figured out what seems to be a solution for preserving my data - for anyone else who has a similar issue, here are the steps I used to solve:
If Lineage recovery boots for you, by all means use that. I couldn't get it to boot from fastboot.
Select slot A in fastboot. flash latest TWRP to boot_a. Select slot A again. boot to recovery. TWRP should load, it will not decrypt your data but it doesn't wipe it either. Hit cancel there. Then go to advanced and ADB sideload. Sideload Lineage ROM. reboot to recovery, and finally Lineage recovery shows up. Sideload Gapps there and whatever else. Boot to system. DO NOT REINSTALL TWRP.
Apparently TWRP can access the disk somehow, but won't decrypt existing data. Hope this helps someone.