Database Info

How to fix Error install January security patch

1- download this Firmware NB1-488B-0-00WW-B04.qlz Via this link https://bit.ly/2CZS4Z2
2- Flash via NOST https://github.com/StollD/NOST/releases
3- download and flash thes ota update via adb sideload https://bit.ly/2Rs4y0Y
Now you can install January security patch Without any problems

iyadengle said:
1- download this Firmware NB1-488B-0-00WW-B04.qlz Via this link https://bit.ly/2CZS4Z2
2- Flash via NOST https://github.com/StollD/NOST/releases
3- download and flash thes ota update via adb sideload https://bit.ly/2Rs4y0Y
Now you can install January security patch Without any problems
Click to expand...
Click to collapse
Thumbs up for this(!), but you might want to suggest that the user just flashes the 5110 qlz since thats the official Pie build (December update).
Alternatively you can only sideload the OTA update zip that was linked, it is a full OTA and updates to Pie-December from any other build as long as you have stock recovery.

THMSP said:
Thumbs up for this(!), but you might want to suggest that the user just flashes the 5110 qlz since thats the official Pie build (December update).
Alternatively you can only sideload the OTA update zip that was linked, it is a full OTA and updates to Pie-December from any other build as long as you have stock recovery.
Click to expand...
Click to collapse
I did the sideload OTA thing (Slot B = Pie Dec., magisk patched boot image, Slot A = Oreo May (or Juin?)) stock image.
It failed for the Slot B (i think) with message timestamp of update 1543458509 is older than current image 1545911676.
Slot A was patched successfully.
After reboot magisk is gone. Total desaster
Can please someone explain how to root with magisk a pie december? or how to use the prepatched boot images?
I'd like to have a rooted system able to do the monthly OTAs (with the magisk "restore, do OTA, patch inactive slot" thing.

What I did, similar to https://forum.xda-developers.com/showpost.php?p=78171178&postcount=95, but I did not see this post before I figured it out by myself, but I think this won't work anyway, as booting the modified boot image simply does not work for me, only booting to the modified twrp boot image via "boot to recovery".
So I did:
prepare:
- backup internal "sdcard", backup apps/settings with titaniumbackup
- reset to factory default (while flashing stock pie with NOST, option erase user data)
a)
- flash the 5110 qlz pie full stock rom with NOST tool as linked and described here https://forum.xda-developers.com/showpost.php?p=78804078&postcount=2
- boot new system -> current slot is slot a with pie 01.12. (the same on both slots?)
- OTA to slot b and reboot
-> result: slot a = 1.12., slot b = 1.1., slot b is active
b)
- reboot to bootloader
- verify that current slot is b: fastboot getvar current-slot
- change to a: fastboot --set-active=a
- flash twrp boot rom to boot_a: fastboot flash boot_a "twrp... .img" from "repository" linked here https://forum.xda-developers.com/no...le-nokia-8-t3867037/post78802351#post78802351 (https://bit.ly/nokia-nb1)
- reboot to recovery
-> twrp recovery should start
- install magisk zip (copy to sd card before rebooting to bootloader)
- reboot, system boots to slot a / pie 01.12.
- install magisk via magisk manager app to the inactive slot
- reboot bootloader
- flash stock image on slot a from "repository" above
- change active slot back to b, if not active anyway (should be active already because of the "install to inactive slot"
- reboot again
-> should boot to slot b with pie 01.01.2019, and should be rooted.

.11 OTA Update Issue

Alright, I have tried just about everything and keep running into the same roadblock so I am going to post here and see if someone has an idea of what is going on and how to work around it. I will outline each method used below as detailed as I can. I'm currently on 9.5.9 and looking to upgrade to .11. I'm currently on Slot B.
First Method:
1.) Disabled all Magisk modules / themes etc
2.) Downloaded .11 OTA from OnePlus Updater
3.) Installed locally via System Updates
4.) Installed TWRP A/B Retention Script in Magisk
5.) Magisk OTA install to inactive slot
6.) Reboot
Result: Reboots to TWRP in the new slot but no pin number is requested and no files showing under Install, cannot reboot to system. I reboot to slot b and try again.
Second Method:
1.) Disabled all Magisk modules / themes etc
2.) Downloaded .11 OTA from OnePlus Updater
3.) Reboot to TWRP
4.) Flash ROM
5.) Flash TWRP installer
6.) Reboot recovery
Result: Reboots to TWRP in the new slot but no pin number is requested and no files showing under Install, cannot reboot to system. I reboot to slot b and try again.
Third Method:
1.) Disabled all Magisk modules / themes etc
2.) Download / Install via system updates message to upgrade to .10
4.) Installed TWRP A/B Retention Script in Magisk
5.) Magisk OTA install to inactive slot
6.) Reboot
Result: Reboots to TWRP in the new slot but no pin number is requested and no files showing under Install, cannot reboot to system. Upon rebooting to slot b I at least got a notification that the update had failed and to enter repair mode to attempt again, however, I decided to not do this yet to avoid issues with breaking root / TWRP.
-----
As you can see... I am getting to the point of rebooting to recovery in the new slot but am unable to do anything in terms of flashing ROM > TWRP > Magisk to update both slots or do anything in the new slot. I'm almost assuming a clean ROM flash, flash TWRP / Magisk might fix any issues but I want to prod you all first for a solution before I go with the nuclear option.

i.Design said:
Alright, I have tried just about everything and keep running into the same roadblock so I am going to post here and see if someone has an idea of what is going on and how to work around it. I will outline each method used below as detailed as I can. I'm currently on 9.5.9 and looking to upgrade to .11. I'm currently on Slot B.
First Method:
1.) Disabled all Magisk modules / themes etc
2.) Downloaded .11 OTA from OnePlus Updater
3.) Installed locally via System Updates
4.) Installed TWRP A/B Retention Script in Magisk
5.) Magisk OTA install to inactive slot
6.) Reboot
Result: Reboots to TWRP in the new slot but no pin number is requested and no files showing under Install, cannot reboot to system. I reboot to slot b and try again.
Second Method:
1.) Disabled all Magisk modules / themes etc
2.) Downloaded .11 OTA from OnePlus Updater
3.) Reboot to TWRP
4.) Flash ROM
5.) Flash TWRP installer
6.) Reboot recovery
Result: Reboots to TWRP in the new slot but no pin number is requested and no files showing under Install, cannot reboot to system. I reboot to slot b and try again.
Third Method:
1.) Disabled all Magisk modules / themes etc
2.) Download / Install via system updates message to upgrade to .10
4.) Installed TWRP A/B Retention Script in Magisk
5.) Magisk OTA install to inactive slot
6.) Reboot
Result: Reboots to TWRP in the new slot but no pin number is requested and no files showing under Install, cannot reboot to system. Upon rebooting to slot b I at least got a notification that the update had failed and to enter repair mode to attempt again, however, I decided to not do this yet to avoid issues with breaking root / TWRP.
-----
As you can see... I am getting to the point of rebooting to recovery in the new slot but am unable to do anything in terms of flashing ROM > TWRP > Magisk to update both slots or do anything in the new slot. I'm almost assuming a clean ROM flash, flash TWRP / Magisk might fix any issues but I want to prod you all first for a solution before I go with the nuclear option.
Click to expand...
Click to collapse
First method was the right method. But don't flash the ab retention script. Flash the file in system update then go to magisk and flash to inactive slot. Reboot after that and when you boot back up flash the twrp installer in magisk and reflash root and reboot to recovery to verify its there.

joemossjr said:
First method was the right method. But don't flash the ab retention script. Flash the file in system update then go to magisk and flash to inactive slot. Reboot after that and when you boot back up flash the twrp installer in magisk and reflash root and reboot to recovery to verify its there.
Click to expand...
Click to collapse
I'm assuming you mean flash TWRP installer via Magisk once rebooted? I just want to make certain before trying again.

i.Design said:
I'm assuming you mean flash TWRP installer via Magisk once rebooted? I just want to make certain before trying again.
Click to expand...
Click to collapse
Yes

joemossjr said:
Yes
Click to expand...
Click to collapse
This didn't work. I was able to at least see my storage now and installed OTA via TWRP > TWRP installer > Magisk to update Slot B now I'm having the same issue in both slots.

there has to be something else up with your device. I would try a clean flash with magisk or try the latest magisk canary build.

I have downloaded the 11 update via OxygenUpdater using VPN (Location is set to France)
Since i diden't get the update on my real location.
Rebooted to TWRP->Flashed 11 update->Flashed TWRP->Rebooted to TWRP>Flashed Magisk>Flashed Kernel>Rebooted to System.
Everything seems to be working.

Try this simple and straight forward method,
Download the full zip 9.5.11, not the update zip but full zip,
Transfer to phone storage,
wipe only dalvik cache and data, DO NOT WIPE SYSTEM OR VENDOR, OR INTERNAL STORAGE,
Flash the oos zip,
Flash twrp, Reboot recovery,
Flash oos zip file again followed by twrp,
Reboot recovery,
Flash magisk 19.3,
Now Reboot system,
Do not click on any slots in twrp let the system select the appropriate slot, system will take some time to boot also will Reboot itself, but will boot eventually,
hope this helps, cheers.

How this helps, worked for me, I don't have T-Mobile version
i.Design said:
Alright, I have tried just about everything and keep running into the same roadblock so I am going to post here and see if someone has an idea of what is going on and how to work around it. I will outline each method used below as detailed as I can. I'm currently on 9.5.9 and looking to upgrade to .11. I'm currently on Slot B.
First Method:
1.) Disabled all Magisk modules / themes etc
2.) Downloaded .11 OTA from OnePlus Updater
3.) Installed locally via System Updates
4.) Installed TWRP A/B Retention Script in Magisk
5.) Magisk OTA install to inactive slot
6.) Reboot
Result: Reboots to TWRP in the new slot but no pin number is requested and no files showing under Install, cannot reboot to system. I reboot to slot b and try again.
Second Method:
1.) Disabled all Magisk modules / themes etc
2.) Downloaded .11 OTA from OnePlus Updater
3.) Reboot to TWRP
4.) Flash ROM
5.) Flash TWRP installer
6.) Reboot recovery
Result: Reboots to TWRP in the new slot but no pin number is requested and no files showing under Install, cannot reboot to system. I reboot to slot b and try again.
Third Method:
1.) Disabled all Magisk modules / themes etc
2.) Download / Install via system updates message to upgrade to .10
4.) Installed TWRP A/B Retention Script in Magisk
5.) Magisk OTA install to inactive slot
6.) Reboot
Result: Reboots to TWRP in the new slot but no pin number is requested and no files showing under Install, cannot reboot to system. Upon rebooting to slot b I at least got a notification that the update had failed and to enter repair mode to attempt again, however, I decided to not do this yet to avoid issues with breaking root / TWRP.
-----
As you can see... I am getting to the point of rebooting to recovery in the new slot but am unable to do anything in terms of flashing ROM > TWRP > Magisk to update both slots or do anything in the new slot. I'm almost assuming a clean ROM flash, flash TWRP / Magisk might fix any issues but I want to prod you all first for a solution before I go with the nuclear option.
Click to expand...
Click to collapse
OP7PRO, stock ROM, stock kernel
This has been ABSOLUTELY working for me and how i was used doing it back in the days..
*After switching off all modules in Magisk and do a system reboot to apply this..
(Do I have to mention it's probably best, when updating to disable any password/fingerprint protection when rebooting AFTER FLASHING OTA, TWRP and Magisk in recovery?)
*I didn't use local update setting.
*What's on in developer options?
-OEM Unlock allowed
-Advanced reboot
-USB Debugging
*Don't know if having these developer settings otherwise would interfere, I just try to write it down as specific as of how i did this.
*Also: I didn't even bother looking at A/B partitioning and where to install what, please correct me if i could be wrong, but using this method worked for me and also when installing TWRP zip in recovery, the log showed A/B sloth solution success when installing.
*Not using substratum themes etc., but I want to say it's probably best to go as clean as you can anyway, since you can always go back being beautiful afterwards I guess?
So try remember where you left off being a makeup loving customiser and momentary revert being as clean as possible.. at least for maybe 20 minutes okay?
How I did it:
-Download the OTA update zip on your phone (full update file zip just shy of 2 Gb) using oxygen updater app in Google playstore.
(Don't install the systemsoftware zip from the oxygen updater once downloaded), you're going to install the systemsoftware.zip in TWRP recovery as opposed to update via Magisk to install the new systemsoftware).
-Download TWRP (INSTALLER!!) have this ZIP on phone (Find it by reading some posts about TWRP Installer zip or use link below)
*I used: twrp-installer-3.3.1-4-guacamole.zip
https://dl.twrp.me/guacamole/ (for TWRP zip)
-Download Magisk zip
*I used: Magisk-v19.3.zip
(So far 3 zip files, have them somewhere pretty obvious on your phone)
-Boot into recovery (I did this by using this option in Magisk manager)
Then:
-Flash the update OTA ROM.zip (just shy of 2Gb)
*DON'T REBOOT*!!!!
-Go back in TWRP recovery menu, Flash TWRP Installer zip
-Still in TWRP recovery menu go back, Reboot to recovery
-Back in TWRP, flash Magisk zip
-Clear Dalvik cache (not sure if this is actually still needed)
-Reboot system normally, enable Magisk modules you want, reboot system...
Updated to 9.5.10 works
Updated to 9.5.11 works
Updated to 10.0.0 works

I can't find the full zip for 9511 anywhere

joemossjr said:
there has to be something else up with your device. I would try a clean flash with magisk or try the latest magisk canary build.
Click to expand...
Click to collapse
I ended up having to reformat to deal with the encryption issue. After reformatting I was able to boot to slot b and am at .11 now!
I'm really hoping this ordeal fixed whatever the problem was so that future OTA's aren't this much of a headache. I'll keep the tips in mind. I'm just glad to have a working device at .11 with root even if I have to re-install all of my apps etc.

virtyx said:
I can't find the full zip for 9511 anywhere
Click to expand...
Click to collapse
It's live on XDA frontpage.
---
I think best update method is get full zip, do local upgrade, flash Magisk after OTA on inactive slot, reboot, flash TWRP installer via magisk and reflash magisk (direct method). Reboot and zero issues.

smariob said:
It's live on XDA frontpage.
---
I think best update method is get full zip, do local upgrade, flash Magisk after OTA on inactive slot, reboot, flash TWRP installer via magisk and reflash magisk (direct method). Reboot and zero issues.
Click to expand...
Click to collapse
just came up now
what i normally do is flash full zip
reboot
then reboot fastboot and boot twrp, then flash twrp then magisk.
i like the OS boot first time without twrp or magisk, just habit i guess
everything working fine, nightscape also
EDIT:
i think SWAP has been turned off in 9.5.11
it no longer displays in ElementalX app (with stock kernel)

What did I do wrong?
Someone help me shed some light. I'm not sure what I did wrong while updating using magisk.
So this is the steps I did.
1. Installed the OTA update
2. In magisk went to install to inactive slot (after OTA)
3. Then it went through the motions and restarted.
At the screen where you put the password in it shut down and then went to the stock recovery. Tried again, same thing. So after some panicking I did this.
Reflashed twrp via computer
Flashed the uninstall of magisk
Flashed twrp zip
Restarted it and everything is fine now. I just had to re-flash the modules which was quite annoying.
So what did I do wrong? Have I buggered up anything to do with the inactive slots or partitions?

I don't know why people have such difficulty?
1. Get the full zip via Oxygen Updater or some other method.
2. Do a local install vis the settings. DO NOT REBOOT.
3. Install Magisk via the "Install after OTA" from Magisk Manager.
4. Reboot
5. You will now have the slot rooted that you updated.
6. Run the local install again. This will install to the other slot. It will fail the first attempt. Do it again.
7. Install Magisk via the OTA option and reboot.
You have now updated both slots and rooted them.
If you would like TWRP or custom kernels, follow those instructions.
If you install TWRP, you MUST install Magisk in the same slot or you will get a boot loop for that slot.
That is the reason why I keep both slots at the same OS level and rooted with TWRP installed.

What country guys you are from that you are getting update? Im in USA and still got nothing.

netgar said:
What country guys you are from that you are getting update? Im in USA and still got nothing.
Click to expand...
Click to collapse
Using oxygen updater, try disabling all.mods before checking for update. Or in oxygen updater settings, select advanced mode, and see if update is available.

Krsmqn said:
Using oxygen updater, try disabling all.mods before checking for update. Or in oxygen updater settings, select advanced mode, and see if update is available.
Click to expand...
Click to collapse
By mods you mean magisk modules?
Update
Advanced option did the job. Updated with magisk and few magisk modules + few substratum themes.
Thx

netgar said:
By mods you mean magisk modules?
Update
Advanced option did the job. Updated with magisk and few magisk modules + few substratum themes.
Thx
Click to expand...
Click to collapse
Yeah, meant magisk modules, sorry. But looks like you got it anyway. ?

All update methods to 11 failed.

Update firmware on custom ROM

I am currently on LineageOS 17.1 on both slots, which I flashed over OOS 10.0.4. As I am coming from a OnePlus One, I am still unfamiliar with the A/B slots and I didn't found detailed instructions. Now I want to update the vendor image to 10.0.5 and stay with LineageOS. Is the following procedure correct if I want to keep my data (<- important)?
1. Download 10.0.5 from here: https://forum.xda-developers.com/on...ygen-os-10-0-5-live-oxygen-os-10-0-5-t4080943 (full: https://otafsg1.h2os.com/patch/amaz....25_OTA_025_all_2003270113_4588ebe57af551.zip)
2. Deactivate Magisk modules
3. Open sideload in LineageOS recovery
4. Flash 10.0.5 via adb sideload
5. Flash TWRP via adb sideload (https://sourceforge.net/projects/ma...le-unified-installer-mauronofrio.zip/download)
6. Reboot to TWRP
7. Open sideload in TWRP
8. Flash 10.0.5 via adb sideload
9. Flash TWRP via adb sideload
10. Reboot to TWRP
11. Repeat Steps 3 to 9 , but with newest LineageOS nightly
12. Reboot to LineageOS, reactivate Magisk modules
Is this correct? Am I missing something? I would be happy about improvements.

Bump

I think you will break your data partition if you do this. You can try it, but I think it won't work.
I would backup the phone phone (apps + internal storage) and do the procedure, most likely it will fail.
BTW, its illegal on the internet to pretend to be another (real) person
Just use another username and profile picture (I think you don't have the copyright?)

Thanks for your answer! Hmmm... I don't wanna break my data partition. If I understand you correctly, there's no way to avoid this? Or is there a way and my approach is wrong?
Right about the picture, I'm deleting that.
Edit: New profile picture

my usual update round
- reboot into recovery (assume TWRP already flashed)
- data backup and get current slot
twrp -> settings -> timezone (for nicer local datestamp)
twrp -> backup data (compress) -> /sdcard/TWRP/BACKUPS/
twrp -> enter reboot menu -> show current slot
- upload archives to virtual sdcard
host # adb shell mkdir /sdcard/TWRP/image/
host # adb push oos/OB12-OnePlus7ProOxygen_13.W.31_OTA_031_all_2004111755_397ef15c84.zip /sdcard/TWRP/image/
host # adb push los/lineage-17.1-20200420-nightly-guacamole-signed.zip /sdcard/TWRP/image/
host # adb push twrp/twrp-3.3.1-79-guacamole-unified-installer-mauronofrio.zip /sdcard/TWRP/image/
host # adb push magisk/Magisk-v20.4.zip /sdcard/TWRP/image/
- install/sideload archives via TWRP (every install will usually go into inactive slot)
twrp -> install OOS zip (for vendor/baseband firmware update)
twrp -> install LOS zip (for fun)
twrp -> install TWRP zip (for override LOS recovery) [will patch both slots - against A/B logic]
- switch slot
twrp -> reboot menu -> select other slot
twrp -> reboot into recovery
- rebooted into recovery (verify TWRP version, current slot, correct /data decryption)
twrp -> install Magisk (for LOS17 with SU/root support) [will install into current slot - against A/B logic]
- reboot into new flashed system (verify current slot, LOS version, baseband version)

How to install LineageOS with MicroG

Hi,
Phone : Realme 5 Pro EU version 4GB/128GB.
As the title says, I am trying to install LineageOS then MicroG on my Realme 5 Pro. So far... I've been at this for a couple of days and I've learned a lot, but that was worth it. Still have to see after a couple of days if this install is stable enough.
Usual disclaimer that this is not because it worked for me that it'd work for you etc...
What files are necessary to follow this post?
-> vbmeta.img & twrp.img here : https://drive.google.com/drive/folders/1MUEJkl25gL7zUPXNKFx_I5HLHyfCAzz7 as posted in this guide : https://forum.xda-developers.com/t/...install-twrp-and-install-custom-roms.4177511/
-> C12 Stock ROM from realme : https://download.c.realme.com/osupdate/RMX1971EX_11_OTA_1120_all_s0mRvUGlCJAI.ozip
-> the Lineage 17.1 ROM provided by @kemo12533 here : https://sourceforge.net/projects/myholly****/files/ROMs/RMX1971/LineageOS/
-> the NikGApps Core for Android 10 ARM64 : https://sourceforge.net/projects/ni...ps-core-arm64-10-20210130-signed.zip/download
-> Magisk : https://github.com/topjohnwu/Magisk/releases/download/v22.1/Magisk-v22.1.apk
-> NanoDroid-patcher : https://downloads.nanolx.org/NanoDroid/Stable/NanoDroid-patcher-23.1.2.20210117.zip
-> NanoDroid-MicroG : https://downloads.nanolx.org/NanoDroid/Stable/NanoDroid-microG-23.1.2.20210117.zip
What I have done so far that works (after tons of FAIL)?
-> Unlocked the device
I managed to unlock the device without too much issue following the guide (link to the guide on this forum is provided above).
-> Installed TWRP
rebooted into bootloader.
"fastboot flash recovery twrp.img"
then proceeded in recovery to TWRP.
Lesson Learned: when "fastboot flash ..." behaves funky (as in not the expected result which is OK), change cable/usb port/computer and don't bother trying to troubleshoot it (I spend a day on this for no result). I have to go on my parents windows computer to fastboot flash but hey it works.
-> Installed latest version of RealmeUI OS (C12 from late march 2021)
TWRP wiped (Dalvik, Cache, System, Vendor, Data)
TWRP format data.
TWRP installed RealmeUI OS C12 without issue
(I did boot it without problem and enabled debugging but I don't think it is required)
-> reinstalled TWRP that had just been overwritten by C12 install.
rebooted in bootloader
"fastboot flash recovery twrp.img"
"fastboot flash vbmeta vbmeta.img"
then booted in recovery to TWRP.
-> Installed LineageOS 17.1 with NikGApps.
TWRP wiped (Dalvik, Cache, System, Vendor, Data) and then formatted data.
TWRP installed LineageOS 17.1
TWRP Install NikGApps.
TWRP installed magisk (which roots the OS).
Rebooted and LineageOS booted without issue.
Note 1 : I tried to install this LineageOS on its own to do a clean MicroG install but on its own it wouldn't boot (same with OpenGApps pico). BitGApps and NikGapps Core both make Lineage Boot, but I settled on NikGApps because it seems automatically 'removed' afterwards when installing MicroG, see later.
Note 2 : The magisk app says that the realme5pro does not have ramdisk. It seems that this is wrong: Magisk does say that phones from 2019 & 2020 are a mess to detect and that the RAMDISK test (Yes or No) is unreliable for those. I followed the manual for No Ramdisk and it corrupted my recovery partition. I followed the manual for yes and it works without issue since.
-> Installing MicroG.
I am now in LineageOS
Magisk Installed Magisk from the same apk and follow instructions to install Magisk properly.
Magisk Installed NanoDroid-patcher & rebooted
Magisk Installed NanoDroid-MicroG & rebooted
at this point the play store icon and app have disappeared (most probably removed by the NanoDroid-MicroG install) and the MicroG Settings app is installed. You still have some permissions to give MicroG and configure it properly, but the following video does a good job of that so I'll leave is at that.
Learned along the way :
It seems to be really hard to brick that phone (good stuff). As long as you can still boot in fastboot you can recover, even if system and recovery don't work.
when "fastboot flash ..." commands don't work when "fastboot devices" lists your device, find another computer, don't waste your time trying to fix this with no result.
write down what works for future reference. I am now documenting every step that works.
Edit 1 : Added Magisk bit. Reorganised post and added details.
Edit 2 : Added MicroG bit. Reorganised post and added details. I guess it's a sort of a guide now...

Hi there!
Does anyone know if it is currently possible to install LineageOS+MicroG on a Samsung Galaxy S20FE Exynos with OneUI 4.1 and Android 12 (SM-G780F/DS)?
Or is there another OS that would allow me to have a degoogled and privacy-friendly smartphone?
Thank you all for your help!

Search for "Lineageos with microg". LineageOS with microgn and f-droid already installed

How to flash TWRP onto both Slot A and Slot B? - Can't find a straight answer.

Hello, my goal is to flash TWRP onto both Slot A and Slot B.
I've flashed TWRP into Slot A, while Slot B is flashed with LineageOS recovery, currently.
I'm pretty sure I then flashed the OS/ROM with TWRP into Slot A but afterward I had a warning that read, "No OS Installed" - I thought it was a fluke, I rebooted System and it went back to TWRP with Slot A active.
I manually switched to Slot B and rebooted System and LineageOS loaded. Rebooted into recovery and discovered Slot B is still using LineageOS recovery.
From there, in the recovery interface, there's no option to manually change back to Slot A. Rebooted into fastboot and connected phone to PC and ran command:
fastboot set_active other
This switched back to Slot A
I rebooted the device which loaded TWRP on Slot A.
At this point what do I need to do to install TWRP onto Slot B and flash LineageOS onto Slot A and Slot B?
I assume through TWRP on Slot A - I can flash TWRP onto Slot B. Then manually change to Slot B - reboot into recovery and verify TWRP is installed on Slot B?
Doing this of course, will break (assumption again) the LineageOS installation and will have to re-install LineageOS.
Once verified, flash LineageOS onto both Slot A and Slot B.
I feel like I missed something but honestly I'm using multiple guides and I feel I'm going to end up breaking something since not all guides align well.
I know this is a noob question, so I apologize, but I am trying to follow guides, none of which are instructing from A-Z the processes to achieve this goal. I have no issues following instructions, if I did, I'd have broken linux boxes, including a linux server.
I'm willing to start from scratch if I have to, I just want to get it right once and for all.

This should be posted in the Q/A section.
Anyways, you can simply flash the twrp img to both slots using:
Code:
fastboot flash recovery_a name_of_twrp.img
fastboot flash recovery_b name_of_twrp.img
Then, once TWRP is flashed, just flash the installer zip after flashing a rom to keep twrp flashed to both slots.

azoller1 said:
This should be posted in the Q/A section.
Anyways, you can simply flash the twrp img to both slots using:
Code:
fastboot flash recovery_a name_of_twrp.img
fastboot flash recovery_b name_of_twrp.img
Then, once TWRP is flashed, just flash the installer zip after flashing a rom to keep twrp flashed to both slots.
Click to expand...
Click to collapse
This is in Slot A
Completed commands without error. Instead of installer zip, I have the twrp.img
Advanced > Install Recovery Ramdisk > select twrp.img
Swipe to install
Then instead of reboot, the instructions I'm following says to go Back into Advanced and then select Fix Recovery Bootloop then Swipe to confirm.
Here I receive an error related to magisk (Error 1) - Error patching kernel
The error message is: cd /tmp/repackorig/ && /system/bin/magiskboot hexpatch kernel ...
If I reboot system - I'm thrown back into TWRP recovery interface.
This indicates that I need to install the boot.img
Install > Tap Install Image > Select boot.img > select Boot partition > Swipe ton confirm
[IMAGE FLASH COMPLETE]
Reboot System is selected and LineageOS loads.
Open Magisk > Install > Patch boot.img
However, when I first installed LineageOS and set it up with Magisk and TWRP - I had already patched the boot.img - literally this happened yesterday.
Would I need to do it again? I would assume not.
So I go back into TWRP > Install > Image > select the Magisk patched boot.img > check the box to install on both Slots A and B > Swipe to confirm
LineageOS loads.
Now back to TWRP to complete the process of permanently installing TWRP Recovery:
Advanced > Install Recovery Ramdisk > select twrp.img
Tap Back into Advanced > Fix Recovery Bootloop > Swipe to confirm
This time no error - SUCCESS!
Reboot System, but boots into TWRP. No access to LineageOS.
In TWRP I go to Reboot > Select System Partition with Slot A active and it once again reboots into TWRP.
I repeat the process this time selecting Slot B and again reboots into TWRP.
I go back into TWRP, Install > Image > Magisk patched Boot.img > Reboot
LineageOS loads.
Is this the correct process? If so, I imagine that after flashing TWRP onto both Slot A and Slot B, I need to repeat this process on Slot B now?

Also another assumption - is the magisk patched boot.img an actual nandroid backup? Because it flashed the exact image (apps/settings etc..) that I had patched with magisk.
However, if it is, for whatever reason a good portion of my apps are broken. When I open them - they crash. I have to uninstall the app and then re-install it from Aurora Store.
It's not a big deal but I would love for the image to be 100% complete without the apps or even settings being broken/different. But maybe I'm getting ahead of myself here.

Fumetsu_Guritto said:
This is in Slot A
Completed commands without error. Instead of installer zip, I have the twrp.img
Advanced > Install Recovery Ramdisk > select twrp.img
Swipe to install
Then instead of reboot, the instructions I'm following says to go Back into Advanced and then select Fix Recovery Bootloop then Swipe to confirm.
Here I receive an error related to magisk (Error 1) - Error patching kernel
The error message is: cd /tmp/repackorig/ && /system/bin/magiskboot hexpatch kernel ...
If I reboot system - I'm thrown back into TWRP recovery interface.
This indicates that I need to install the boot.img
Install > Tap Install Image > Select boot.img > select Boot partition > Swipe ton confirm
[IMAGE FLASH COMPLETE]
Reboot System is selected and LineageOS loads.
Open Magisk > Install > Patch boot.img
However, when I first installed LineageOS and set it up with Magisk and TWRP - I had already patched the boot.img - literally this happened yesterday.
Would I need to do it again? I would assume not.
So I go back into TWRP > Install > Image > select the Magisk patched boot.img > check the box to install on both Slots A and B > Swipe to confirm
LineageOS loads.
Now back to TWRP to complete the process of permanently installing TWRP Recovery:
Advanced > Install Recovery Ramdisk > select twrp.img
Tap Back into Advanced > Fix Recovery Bootloop > Swipe to confirm
This time no error - SUCCESS!
Reboot System, but boots into TWRP. No access to LineageOS.
In TWRP I go to Reboot > Select System Partition with Slot A active and it once again reboots into TWRP.
I repeat the process this time selecting Slot B and again reboots into TWRP.
I go back into TWRP, Install > Image > Magisk patched Boot.img > Reboot
LineageOS loads.
Is this the correct process? If so, I imagine that after flashing TWRP onto both Slot A and Slot B, I need to repeat this process on Slot B now?
Click to expand...
Click to collapse
I am not sure where you are seeing Advanced > Install recovery ramdisk in twrp. You should never have to used the advanced menu in twrp, unless for very specific reasons.
Ok, lets assume you are running the latest stock OOS.
1. First, you unlock the bootloader and can now use fastboot.
2. Reboot to bootloader
3. At this point you flash the twrp.img file to both recovery slots like i mentioned in my other post.
4. At this point you have twrp forever until something else overwrites the recovery partitions (flashing rom, flashing other custom recovery, etc).
5. Now, you need to factory reset, go to reboot then switch to the inactive slot, dont reboot, go back to install, then flash the rom zip file.
6. After flashing the rom zip file, flash the twrp installer zip file to overwrite the rom recovery.img so you can retain twrp.
7. Then you can reboot system and you will boot to the other slot where the rom was just flashed and everything should be ok.
Since twrp for the 8T is still not fully stable, but works very well, I dont think its good to flash .imgs directly in twrp, im sure it works but I usually just flash compatible zip files in twrp and use fastboot manually to flash a specific img if desired.
For magisk, the dev states in the instructions that flashing in twrp is not recommended (for the 8t in this case) and is better to boot the patched img from fastboot then go into magisk and direct install. Flashing using fastboot should work 100% of the time without issues. I have always just flashed the patched boot.img directly in fastboot and reboot with no issues.
However, if you prefer to flash in twrp, you must reboot back into recovery (reboot then press recovery) after flashing the rom and the twrp installer, so your device is updated to the other slot where the rom was flashed. Now you can flash magisk and it will flash to the correct boot.img slot.

Fumetsu_Guritto said:
Also another assumption - is the magisk patched boot.img an actual nandroid backup? Because it flashed the exact image (apps/settings etc..) that I had patched with magisk.
However, if it is, for whatever reason a good portion of my apps are broken. When I open them - they crash. I have to uninstall the app and then re-install it from Aurora Store.
It's not a big deal but I would love for the image to be 100% complete without the apps or even settings being broken/different. But maybe I'm getting ahead of myself here.
Click to expand...
Click to collapse
A magisk patched img is a boot.img unpacked and magisk is then injected and repacked. The size is 96mb.