Database Info

[H918][STOCK] 10i KDZ + IMGs

10i for T-Mobile V20 H918 is out.
It's still anti-rollback v00. :good:
Android Security Patch: 2016-12-01 (dirtycow/recowvery patched)
Download Link
UPPERCUT should work if using LGUP/KDZ.
If you flash this KDZ there is no current root method for 10i... so no TWRP etc (at this very moment anyway).
Everyone who can only boot to download mode.. this should save you.
those w/TWRP already can use the images (or wait for someone to make a flashable "rom" zip.
H91810-system.img.zip is just the system.img compressed, not a flashable zip.
if flashing the stock system.img/boot.img be careful not to lose TWRP..
delete the "recovery-from-boot.p" in system while still in TWRP if you want to be extra safe.
I don't have a V20 and won't be supporting this thread. Just providing files.

Thanks for this. Wonder what the changes from v10d are (other the exploit patch)

If and when someone creates a flashable zip, can we flash SuperSU after we flash the ROM to still have root?

Great.. My replacement is coming today which means it'll probably self update on first boot before I can do anything about it..

I love you daddi

Is this also OTA? I see nothing

kyledowling said:
If and when someone creates a flashable zip, can we flash SuperSU after we flash the ROM to still have root?
Click to expand...
Click to collapse
yes, that's how it works. tho.. idk if it's user-error or what... sometimes people flash supersu and it doesn't patch the boot.img and when they boot into android they lose twrp. hasn't happened to me but ¯\_(ツ)_/¯ . so that's why I also suggested removing the recovery-from-boot.p as an option.
people could also just dd the images manually if they don't want to wait for a zip... but I guess those comfortable with dd already know that.
Swizzle82 said:
Great.. My replacement is coming today which means it'll probably self update on first boot before I can do anything about it..
Click to expand...
Click to collapse
lol just don't put a sim in or connect it to wifi before you use recowvery.

autoprime said:
yes, that's how it works. tho.. idk if it's user-error or what... sometimes people flash supersu and it doesn't patch the boot.img and when they boot into android they lose twrp. hasn't happened to me but ¯\_(ツ)_/¯ . so that's why I also suggested removing the recovery-from-boot.p as an option.
people could also just dd the images manually if they don't want to wait for a zip... but I guess those comfortable with dd already know that.
lol just don't put a sim in or connect it to wifi before you use recowvery.
Click to expand...
Click to collapse
Great idea.. Sometimes you're smart, lol

Swizzle82 said:
Great idea.. Sometimes you're smart, lol
Click to expand...
Click to collapse
altho now that i think about it.. they may force you on the setup screen. but theres no way it'll download/install in the time it takes to get through setup. so just disable internet as soon as you're setup. :good:

autoprime said:
altho now that i think about it.. they may force you on the setup screen. but theres no way it'll download/install in the time it takes to get through setup. so just disable internet as soon as you're setup. :good:
Click to expand...
Click to collapse
What I usually do is make a twrp back up from my old phone and restore it on the new phone after making a fake backup and moving the old one in the new folder the fake backup created. Theoretically this should restore my google account without ever having to initially setup my account when I turn on the new phone. Right? Or do you think it'll cause authentication issues?

Swizzle82 said:
Great.. My replacement is coming today which means it'll probably self update on first boot before I can do anything about it..
Click to expand...
Click to collapse
As long as it isn't preloaded you should be able to get around it...
Common sense isn't all that common

ZDeuce2 said:
As long as it isn't preloaded you should be able to get around it...
Common sense isn't all that common
Click to expand...
Click to collapse
I'm sure I'll get it figured out.

Hopefully @Eliminater74 will make part 1 & 2 ROM for H918 users.

mingkee said:
Hopefully @Eliminater74 will make part 1 & 2 ROM for H918 users.
Click to expand...
Click to collapse
Is he coming to the v20. Plz say yes.

System.img.zip, do I just rename it to system.img? Cause I extracted from zip file and system.img did not flash. But when I renamed it, it flashed but wouldn't boot.

kcsevo said:
System.img.zip, do I just rename it to system.img? Cause I extracted from zip file and system.img did not flash. But when I renamed it, it flashed but wouldn't boot.
Click to expand...
Click to collapse
If you really want this, just use the LG Bridge and update it through that. It's much easier than flashing manually and accomplishes the same thing.

kibmikey1 said:
If you really want this, just use the LG Bridge and update it through that. It's much easier than flashing manually and accomplishes the same thing.
Click to expand...
Click to collapse
Oh sweet! But for the file itself do I need to extracted or rename the file? I flashed the system.img and boot in twrp but it hung in LG logo. And I'm also trying to retain root.

kcsevo said:
Oh sweet! But for the file itself do I need to extracted or rename the file? I flashed the system.img and boot in twrp but it hung in LG logo
Click to expand...
Click to collapse
You don't need the file at all. Just download the LG Bridge from the LG website, install the LG Universal mobile drivers, plug in your phone and use the software update option. It does it all by itself, and will restart your phone on it's own.

kibmikey1 said:
You don't need the file at all. Just download the LG Bridge from the LG website, install the LG Universal mobile drivers, plug in your phone and use the software update option. It does it all by itself, and will restart your phone on it's own.
Click to expand...
Click to collapse
Do i need to be back factory stock including recovery to use this option? And I'm guessing this way would make me lose root? Thank you for your responses.

kcsevo said:
Do i need to be back factory stock including recovery to use this option? And I'm guessing this way would make me lose root? Thank you for your responses.
Click to expand...
Click to collapse
You only need to plug in your phone and let it work. Since this is a stock image, you will lose root. Also, the as described in the original post on page 1, the December security patch also patches the dirty cow exploit used to achieve root, so once you flash this, you'll be stock unrooted until a new method comes along.

magisk

Anyone uses magisk ? Is it worth??

cline2 said:
Anyone uses magisk ? Is it worth??
Click to expand...
Click to collapse
Why yes. If you use apps that needs SafetyNet to pass. If not you can stay on SuperSU

ante0 said:
Why yes. If you use apps that needs SafetyNet to pass. If not you can stay on SuperSU
Click to expand...
Click to collapse
Ok. Too much pain to do. I will stay with SuperSU

ante0 said:
Why yes. If you use apps that needs SafetyNet to pass. If not you can stay on SuperSU
Click to expand...
Click to collapse
How do I root with magisk? I've looked all over for a method but I can't find one that makes since. I'd rather no rebrand, root I can get with phh superuser or Supersport but i like magisk, it works great on my LG G4.,

McRoberts said:
How do I root with magisk? I've looked all over for a method but I can't find one that makes since. I'd rather no rebrand, root I can get with phh superuser or Supersport but i like magisk, it works great on my LG G4.,
Click to expand...
Click to collapse
What are you rooted with now? And what build is your firmware?

ante0 said:
What are you rooted with now? And what build is your firmware?
Click to expand...
Click to collapse
I'm rooted with phh, and I'm on L29-567-190. Thanks a ton for the help.

McRoberts said:
How do I root with magisk? I've looked all over for a method but I can't find one that makes since. I'd rather no rebrand, root I can get with phh superuser or Supersport but i like magisk, it works great on my LG G4.,
Click to expand...
Click to collapse
If you want to root with magisk, just flash the zip and you are done.

Powerlated said:
If you want to root with magisk, just flash the zip and you are done.
Click to expand...
Click to collapse
It does not work. I've tryed every version from 13 to 13.3 half way thru the flash it just jumps out of recovery and boots by its self. It doesn't bootloop or hurt anything I can tell but it just doesn't install. Ever heard of that?

McRoberts said:
It does not work. I've tryed every version from 13 to 13.3 half way thru the flash it just jumps out of recovery and boots by its self. It doesn't bootloop or hurt anything I can tell but it just doesn't install. Ever heard of that?
Click to expand...
Click to collapse
You need to be on recovery 3.0.1-1

albertobom said:
You need to be on recovery 3.0.1-1
Click to expand...
Click to collapse
3.1.0-1 actually. And if Phh/supersu is flashed you need to flash stock boot image, else it will complain about boot image.

ante0 said:
3.1.0-1 actually. And if Phh/supersu is flashed you need to flash stock boot image, else it will complain about boot image.
Click to expand...
Click to collapse
Well I decided to flash the Shield Rom and it's actually running like a dream so before I go back and start over. Is there any way I can make Magisk work on this Rom. I'm haveing the same issue. I'm going to change my TWRP now. Thanks for the help.

McRoberts said:
Well I decided to flash the Shield Rom and it's actually running like a dream so before I go back and start over. Is there any way I can make Magisk work on this Rom. I'm haveing the same issue. I'm going to change my TWRP now. Thanks for the help.
Click to expand...
Click to collapse
You need to be on firmware B182+ (which you are)
You need to have twrp 3.1.0+
You need to flash stock boot image before Magisk.
You can get stock boot either from rom zip (boot.img) or stock firmware (update.app) and extract boot using Huawei Update extractor. Then flash boot image manually.

Can't flash anything in TWRP

Hello everyone,
So today, I decided to flash the Adaptive Brightness Mod.
So what I did, I booted into newest TWRP, I flashed Adaptive Brightness Mod. Hitted reboot.
It didn't boot, so what I did is I flashed DP3 again. The system booted, so I thought "Yea **** that mod".
So I booted into TWRP again and tried to root again using magisk. I got again in a boot loop.
Does anyone have a solution? I really want to have root access.
Friendly regards,
Crewz

ItsCrewz said:
Hello everyone,
So today, I decided to flash the Adaptive Brightness Mod.
So what I did, I booted into newest TWRP, I flashed Adaptive Brightness Mod. Hitted reboot.
It didn't boot, so what I did is I flashed DP3 again. The system booted, so I thought "Yea **** that mod".
So I booted into TWRP again and tried to root again using magisk. I got again in a boot loop.
Does anyone have a solution? I really want to have root access.
Friendly regards,
Crewz
Click to expand...
Click to collapse
Try flashing Magisk 16.7

flashing magisk in twrp gave me nothing but trouble so now i install twrp and then fastboot from a patched boot to get magisk installed.

manasgirdhar said:
Try flashing Magisk 16.7
Click to expand...
Click to collapse
Yea I tried that, didnt work

RiTCHiE007 said:
flashing magisk in twrp gave me nothing but trouble so now i install twrp and then fastboot from a patched boot to get magisk installed.
Click to expand...
Click to collapse
No idea what a Patched Boot is xD

ItsCrewz said:
Yea I tried that, didnt work
Click to expand...
Click to collapse
Did you trying wiping system, and then flash ROM, TWRP, reboot, and then try Magisk?

ItsCrewz said:
No idea what a Patched Boot is xD
Click to expand...
Click to collapse
patched boot with magisk

manasgirdhar said:
Did you trying wiping system, and then flash ROM, TWRP, reboot, and then try Magisk?
Click to expand...
Click to collapse
I didn't because its an pain to reinstall all apps and place them in the correct folder :/

ItsCrewz said:
I didn't because its an pain to reinstall all apps and place them in the correct folder :/
Click to expand...
Click to collapse
Yeah, I can understand. I normally have a titanium backup. Maybe someone else will have a better helpful idea

manasgirdhar said:
Yeah, I can understand. I normally have a titanium backup. Maybe someone else will have a better helpful idea
Click to expand...
Click to collapse
Yea I have an titanium backup of apps. But u still need to replace them in correct order.
I hope someone has an other idea.

ItsCrewz said:
Yea I have an titanium backup of apps. But u still need to replace them in correct order.
I hope someone has an other idea.
Click to expand...
Click to collapse
Order shouldn't really matter in a batch restore

manasgirdhar said:
Order shouldn't really matter in a batch restore
Click to expand...
Click to collapse
I mean. Like, I need to remake how my homescreen was made

ItsCrewz said:
I mean. Like, I need to remake how my homescreen was made
Click to expand...
Click to collapse
Wouldn't that be already backed up in the launcher data?

You shouldn't be that mad because of your homescreen set-up getting wiped! Yesterday I ****ed up encryption after trying to go back to Oxygen OS 5.1.11 from Havoc OS (which has August Security Patch), I couldn't boot the device up and TWRP and all my files were encrypted. After hours of trying and flashing, I had no other choice than formatting all my data. Including internal storage. And because I'm dumb, I didn't do a back up of my data for 3 month, so now I have 3 month old data on my phone.
So don't care about your homescreen set-up, as long as you have your pictures/music/data on the phone.
Btw, I'm not sure if I have a solution for you, but can you explain what exactly is the issue now? So you can boot up in the system without magisk installed but with it, you can't?

ItsCrewz said:
Yea I tried that, didnt work
Click to expand...
Click to collapse
You can't flash Magisk 16.7 from TWRP. It causes issues more times then not. You need to flash TWRP 16.4 (1642) then let the Magisk manager update to 16.7.

Magisk 16.7 will often give you an error on boot which looks like a vendor mismatch message. I stick with 16.4.

the reason it fails only with root is because the mod he installed is still installed. It only turns on when you have root. remove mod and problem fixed. also, reflashing rom does not remove magisk mods. only uninstalling mod will fix this or a full format.
the mod lives in /data.

memocatcher said:
You shouldn't be that mad because of your homescreen set-up getting wiped! Yesterday I ****ed up encryption after trying to go back to Oxygen OS 5.1.11 from Havoc OS (which has August Security Patch), I couldn't boot the device up and TWRP and all my files were encrypted. After hours of trying and flashing, I had no other choice than formatting all my data. Including internal storage. And because I'm dumb, I didn't do a back up of my data for 3 month, so now I have 3 month old data on my phone.
So don't care about your homescreen set-up, as long as you have your pictures/music/data on the phone.
Btw, I'm not sure if I have a solution for you, but can you explain what exactly is the issue now? So you can boot up in the system without magisk installed but with it, you can't?
Click to expand...
Click to collapse
Hi can you tell me the steps you did to revert back to stock oos rom please. I am struggling with this same exact problem since 2 days and i don't know what else i could try so if you could tell me how you solved this issue ! Thanks

vinct94 said:
Hi can you tell me the steps you did to revert back to stock oos rom please. I am struggling with this same exact problem since 2 days and i don't know what else i could try so if you could tell me how you solved this issue ! Thanks
Click to expand...
Click to collapse
Do you have a USB drive with USB C connector?
It is a lifesaver

Why cant you flash 16.7 again. That's the only one I flash in my TWRP and I never have issues.

October image is up

I've always wanted to post one of these
https://developers.google.com/android/images

How do we flash the update and not lose data and root? All the guides are still for 9.0 for updates

Androider4Life said:
How do we flash the update and not lose data and root? All the guides are still for 9.0 for updates
Click to expand...
Click to collapse
There's a link to a how-to for 10 in the stickied how-to for 9 - https://forum.xda-developers.com/pixel-3-xl/how-to/guide-pixel-3-xl-android-10-0-q-t3964117.
But without twrp I don't think there's a way to retain root, I think you'll need to go the route of patching the boot image with Magisk. But for data just remove the -w switch from flash-all, that should be the same.

kerobrat said:
There's a link to a how-to for 10 in the stickied how-to for 9 - https://forum.xda-developers.com/pixel-3-xl/how-to/guide-pixel-3-xl-android-10-0-q-t3964117.
But without twrp I don't think there's a way to retain root, I think you'll need to go the route of patching the boot image with Magisk. But for data just remove the -w switch from flash-all, that should be the same.
Click to expand...
Click to collapse
I was looking thru that post and didnt wanna risk wiping the device. I just had to wipe a few days ago due to Edxposed bootloop issue lol

Ha, yeah, I feel your pain there, wiping is way too much of a pain to do that frequently

Androider4Life said:
How do we flash the update and not lose data and root? All the guides are still for 9.0 for updates
Click to expand...
Click to collapse
You can also flash the OTA file in stock recovery and not lose data.

spotmark said:
You can also flash the OTA file in stock recovery and not lose data.
Click to expand...
Click to collapse
Will it retain root or do you mean - https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation

Androider4Life said:
Retain root or have to re-root
Click to expand...
Click to collapse
Have to re-root using the Magisk method. Put stock boot on phone, patch boot with Magisk, put modded boot back on computer, and flash in fastboot. AFAIK, there is no way to retain root. Every time you flash the latest monthly patch, it flashes a new stock boot. Therefore, no root.

kerobrat said:
There's a link to a how-to for 10 in the stickied how-to for 9 - https://forum.xda-developers.com/pixel-3-xl/how-to/guide-pixel-3-xl-android-10-0-q-t3964117.
But without twrp I don't think there's a way to retain root, I think you'll need to go the route of patching the boot image with Magisk. But for data just remove the -w switch from flash-all, that should be the same.
Click to expand...
Click to collapse
There's a way with taking the ota through settings I found out how from a user on here which is:
Once received the ota , go to magisk first uninstall/restore images then download/install ota then DONT REBOOT, go back to magisk install magisk to inactive slot from the app then reboot and all should work with new ota update and have root still.

What is this update 4.3mb

Once again, my phone got bricked. I wanted to sideload, so I tried to get it into recovery, it wouldn't, so I tried a few times, and decided screw it. Now my phone bootloops. So, download the image and try flashing, it won't go into fastboot and fails. No matter what I do, I can't seem to save it. Can anyone help me with this? I'm trying a different computer in a sec, but, not sure if that will work either.
Edit: The different computer doesn't see it... FML

gettinwicked said:
Once again, my phone got bricked. I wanted to sideload, so I tried to get it into recovery, it wouldn't, so I tried a few times, and decided screw it. Now my phone bootloops. So, download the image and try flashing, it won't go into fastboot and fails. No matter what I do, I can't seem to save it. Can anyone help me with this? I'm trying a different computer in a sec, but, not sure if that will work either.
Edit: The different computer doesn't see it... FML
Click to expand...
Click to collapse
Just flash the factory image or ota thru flash.all bat file after you do/did the necessary steps like extract the images etc to platform tools folder on ur pc
Or visit here for more help/steps
https://forum.xda-developers.com/pixel-3-xl/how-to/guide-progress-available-t3876849
https://forum.xda-developers.com/pixel-3-xl/how-to/guide-pixel-3-xl-android-10-0-q-t3964117

gm007 said:
What is this update 4.3mb
Click to expand...
Click to collapse
Its just a security patch, we already had the updated rom in september, this just adds the latest security patch. Even though its only 4.3mb, its taking ages to patch, 10 mins still installing.

Jiggs82 said:
Just flash the factory image or ota thru flash.all bat file after you do/did the necessary steps like extract the images etc to platform tools folder on ur pc
Or visit here for more help/steps
https://forum.xda-developers.com/pixel-3-xl/how-to/guide-progress-available-t3876849
https://forum.xda-developers.com/pixel-3-xl/how-to/guide-pixel-3-xl-android-10-0-q-t3964117
Click to expand...
Click to collapse
You missed the part where I did try flashing the image. I've done this a hundred times, so, I did it right.
Anyway, I got it. I didn't realize my work computer had a USB-C port, so, I grabbed one and tried flashing the image with that. Worked! Thank God... I guess sdk tools doesn't like a USB 1 to C cable, and my phone doesn't like going into recovery...

Androider4Life said:
How do we flash the update and not lose data and root? All the guides are still for 9.0 for updates
Click to expand...
Click to collapse
kerobrat said:
There's a link to a how-to for 10 in the stickied how-to for 9 - https://forum.xda-developers.com/pixel-3-xl/how-to/guide-pixel-3-xl-android-10-0-q-t3964117.
But without twrp I don't think there's a way to retain root, I think you'll need to go the route of patching the boot image with Magisk. But for data just remove the -w switch from flash-all, that should be the same.
Click to expand...
Click to collapse
If you are rooted flash the boot.img of the factory image you are currently on to both slots:
Code:
fastboot flash boot --slot all boot.img
Then Do #4 'keep Data'

Homeboy76 said:
If you are rooted flash the boot.img of the factory image you are currently on to both slots:
Code:
fastboot flash boot --slot all boot.img
Then Do #4 'keep Data'
Click to expand...
Click to collapse
I am starting to feel more and more like a lot of the bootloop issues are being caused by OTAs swapping slots on install. Besides the --slot all patched boot, it might help to run the OTA twice to get it to install to both slots completely. Preferably though, quit using OTAs and work with -w removed flash-all installer (and even then possibly installing to both slots with an active slot swap in between and before rooting). The double install is common when installing custom ROMs, and the process for OTA sideloads is pretty similar.

Performance improvement, feels smooth and responsive. Glad i dont need to root this phone, ppl are having so many problems.

boe323 said:
Its just a security patch, we already had the updated rom in september, this just adds the latest security patch. Even though its only 4.3mb, its taking ages to patch, 10 mins still installing.
Click to expand...
Click to collapse
My download was 1.3 gb and took forever to install. That's more than just the security patch.. Build number is different too.
Sent from my Pixel 3 XL using Tapatalk

Worked exactly the same as the 10 and .C3 builds for me. Flash-all (minus -w) and patched boot in Magisk. No issues. It was not just security this month. See the functional patches in the bulletin.
https://source.android.com/security/bulletin/pixel/2019-10-01

is there new platform tools too?

Error on update to 11.0.12.12.KB05AA

I'm trying to update from 11.0.11.11 to 11.0.12.12 incremental update from oxygen updater and having this error:
"Fail on install system update" on 1% progress bar.
Try from system OTA and same error occur.
Somebody try and it work?
Thanks

just installed the same firmware without issue

jushhh said:
I'm trying to update from 11.0.11.11 to 11.0.12.12 incremental update from oxygen updater and having this error:
"Fail on install system update" on 1% progress bar.
Try from system OTA and same error occur.
Somebody try and it work?
Thanks
Click to expand...
Click to collapse
If you are rooted and/or have TWRP installed, then you need to restore the stock boot and/or recovery images before starting the update.

Then I will lose root access?

Not if you do it properly.
If you're using TWRP, then you'll have to restore the stock recovery.
If you're rooted then you can restore the stock boot using Magisk>Uninstall Magisk>Restore images but don't reboot or you'll lose root.
Then download and install the incremental update manually. Then install Magisk to the inactive slot and reboot.
See https://forum.xda-developers.com/t/...1-kb2003-kb2005.4178675/page-30#post-85801253

jushhh said:
Then I will lose root access?
Click to expand...
Click to collapse
1) Update software but DO NOT REBOOT
2) Open Magisk > tap install > tap Install to inactive slot > NOW reboot.
Make sure you disable any and all modules first. No need to uninstall, just disable them. Mainly just a precaution. Possibly remove security from the lockscreen too for good measure.
I lost root the other day actually forgetting to properly install Magisk before rebooting and now I have to buy a laptop just to root again.

BillGoss said:
Not if you do it properly.
If you're using TWRP, then you'll have to restore the stock recovery.
If you're rooted then you can restore the stock boot using Magisk>Uninstall Magisk>Restore images but don't reboot or you'll lose root.
Then download and install the incremental update manually. Then install Magisk to the inactive slot and reboot.
See https://forum.xda-developers.com/t/...1-kb2003-kb2005.4178675/page-30#post-85801253
Click to expand...
Click to collapse
Thanks @BillGoss, your instructions are perfect. Work like a charm.

Anyone have the stock firmware or stock image for 11.0.12.12.KB05AA? Trying to root it.

ClassickWORLD said:
Anyone have the stock firmware or stock image for 11.0.12.12.KB05AA? Trying to root it.
Click to expand...
Click to collapse
Use TWRP: https://forum.xda-developers.com/t/guide-rooting-oos-with-twrp.4327417/

since i did it manually and ended up with no boot.img backup from magisk, i had to manually extract boot.img from my last ota 11.0.11.11.KB05AA and reflash it through fastboot. then it let me update and i rerooted.

I get the notification but can't even try it because when i tap on it, it does nothing.

dazoe said:
I get the notification but can't even try it because when i tap on it, it does nothing.
Click to expand...
Click to collapse
I managed to install the update, I used oxygen updater to download the update, used restore images option in magisk, installed update (DID NOT REBOOT), used install to inactive slot in magisk, then rebooted.
Seems like it all went well.

BillGoss said:
If you are rooted and/or have TWRP installed, then you need to restore the stock boot and/or recovery images before starting the update.
Click to expand...
Click to collapse
Do I have root and twrp, what should I restore? Only recovery? If so, you have maybe some stock for 11.0.11.11 kb05ba? I don't know why, but I only have a copy of the boot.

e1thx said:
Do I have root and twrp, what should I restore? Only recovery? If so, you have maybe some stock for 11.0.11.11 kb05ba? I don't know why, but I only have a copy of the boot.
Click to expand...
Click to collapse
Use payload dumper to get a copy of the .11 recovery.

BillGoss said:
Use payload dumper to get a copy of the .11 recovery.
Click to expand...
Click to collapse
I have root and twrp, what should I restore? Only recovery? And then magic restore?

e1thx said:
I have root and twrp, what should I restore? Only recovery? And then magic restore?
Click to expand...
Click to collapse
Read Post #5.

BillGoss said:
Read Post #5.
Click to expand...
Click to collapse
I have read it, that's why I am asking.I need to recover two partitions? Or one

e1thx said:
I have read it, that's why I am asking.I need to recover two partitions? Or one
Click to expand...
Click to collapse
What don't you understand in post #5? You said you're rooted. So post #5 tells you what to do.

BillGoss said:
What don't you understand in post #5? You said you're rooted. So post #5 tells you what to do.
Click to expand...
Click to collapse
Sorry Bill, I get it all now. I just have to do as You wrote:
1) restore the stock boot using Magisk>Uninstall Magisk>Restore images but don't reboot or you'll lose root
2) install update manually, System update>Gear icon (local upgrade)
3) install Magisk to the inactive slot and reboot
Last question, where or how to download update manually?

e1thx said:
Sorry Bill, I get it all now. I just have to do as You wrote:
1) restore the stock boot using Magisk>Uninstall Magisk>Restore images but don't reboot or you'll lose root
2) install update manually, System update>Gear icon (local upgrade)
3) install Magisk to the inactive slot and reboot
Last question, where or how to download update manually?
Click to expand...
Click to collapse
Ah, well that's tricky if it's not available from OnePlus or the XDA rom thread. I believe Oxygen updater app will give you the rom also, but I've never used it.
Edit: just read your post again and I'm confused: what rom exactly are you looking for?
This thread is about ending up on 11.0.12.12.KB05AA
And if you're looking for that one you'll find it in https://forum.xda-developers.com/t/updates-thread.4188149/post-86165983