Database Info

[Q] OTA updates after root/unlock?

Will I continue to get OTA software updates if I root and unlock the boot loader (to install TWRP)?
Thanks,
Hish747

Yes, make sure to untick to update the recovery in the debug options
Send from OnePlus One using Tapatalk

Yes.Of course.But it happened to me that the update script showed some errors. I had to fix them by downloading the original files and replacing my system files.

want to love this device but it seems like its always something.
---------- Post added at 04:35 PM ---------- Previous post was at 04:33 PM ----------
Sorry wrong thread...

Satras said:
Yes, make sure to untick to update the recovery in the debug options
Send from OnePlus One using Tapatalk
Click to expand...
Click to collapse
Can I dirty flash the nightlies from CM11S if I have just unlocked the bootlader and rooted?

There is no nightly for CM11s just for CM11.
I recommend to do a clean install including factory reset.
Keep in mind that after flashing something, you need to flash root at the end too
Send from OnePlus One using Tapatalk

So we will still get OTA's great! Great phone for costumizations.

ZTube said:
Yes.Of course.But it happened to me that the update script showed some errors. I had to fix them by downloading the original files and replacing my system files.
Click to expand...
Click to collapse
That does not happen if you just unlock, root and install a custom recovery.
Also a custom kernel would be fine
Send from OnePlus One using Tapatalk

Sorry if this is a bit of a n00b question (I know people are sensitive about that!) but I have searched around a bit and not found a solution to this issue. Here's the situation...
So what i've done so far is unlocked the bootloader, installed TWRP, and SuperSU (so I have root). I also unchecked the update recovery box in dev options. When told I need to update I downloaded the update, hit install, the phone reboots and takes me to TWRP. When in TWRP I hit install, navigate to the cache and try to install the update /cache/cm-bacon-d22b777afa-to-4f280f505a-signed.zip
When I do that, I get the following:
"
E:Error installing zip file '/cache/cm-bacon-d22b777afa-to-4f280f505a-signed.zip'
Done processing script file
Installing '/cache/cm-bacon-d22b777afa-to-4f280f505a-signed.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
Can't install this package on top of incompatible data. Please try another package or run a factory reset
E: Error executing updater binary in zip ''/cache/cm-bacon-d22b777afa-to-4f280f505a-signed.zip'
Error flashing zip ''/cache/cm-bacon-d22b777afa-to-4f280f505a-signed.zip'
Updating partition details...
"
Anybody got any ideas?

Seems TWRP expects a MD5 file.
I use CWM as recovery and can install the update OTA. Maybe try CWM recovery
Send from OnePlus One using Tapatalk

Satras said:
Seems TWRP expects a MD5 file.
I use CWM as recovery and can install the update OTA. Maybe try CWM recovery
Send from OnePlus One using Tapatalk
Click to expand...
Click to collapse
Most people that ive read about are using twrp and had no problem updating.

aamir.m.ali said:
Sorry if this is a bit of a n00b question (I know people are sensitive about that!) but I have searched around a bit and not found a solution to this issue. Here's the situation...
So what i've done so far is unlocked the bootloader, installed TWRP, and SuperSU (so I have root). I also unchecked the update recovery box in dev options. When told I need to update I downloaded the update, hit install, the phone reboots and takes me to TWRP. When in TWRP I hit install, navigate to the cache and try to install the update /cache/cm-bacon-d22b777afa-to-4f280f505a-signed.zip
When I do that, I get the following:
"
E:Error installing zip file '/cache/cm-bacon-d22b777afa-to-4f280f505a-signed.zip'
Done processing script file
Installing '/cache/cm-bacon-d22b777afa-to-4f280f505a-signed.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
Can't install this package on top of incompatible data. Please try another package or run a factory reset
E: Error executing updater binary in zip ''/cache/cm-bacon-d22b777afa-to-4f280f505a-signed.zip'
Error flashing zip ''/cache/cm-bacon-d22b777afa-to-4f280f505a-signed.zip'
Updating partition details...
"
Anybody got any ideas?
Click to expand...
Click to collapse
Yeah, you gotta open the zip on your pc, modify META-INF/com/google/android/updater-script and remove the code (its in the top part) that mentions the incompatible data error. Then try flashing again.

aamir.m.ali said:
Most people that ive read about are using twrp and had no problem updating.
Click to expand...
Click to collapse
Yeah, I don't like TWRP and got CWM installed, so I can only give support about that [emoji213]
Send from OnePlus One using Tapatalk

[Q] OTA version XNPH38R Incremental does not install

I'm prompted to install the XNPH38R Incremental with the message "System update is ready"
I tap on Install update, the phone then does it's thing, reboots and shows the splash screen logo a few seconds, then the recovery comes up and the text scrolls at lightning speed (a second or so) then the phone powers up in full and is ready for use.
When I go to my homescreen the prompt is there again for me to upgrade with the "System update is ready" message.
As such the update doesn't apply successfully. No error messages at all.
Phone is stock ROM (version 11.0-XNPH33R), only thing I did extra was to unlock the bootloader using OnePlus One Toolbox v2 (64 GB). This was done in order for me to root it. Oh, I also installed PhilZ Recovery using this same toolbox.
Any ideas why this happens?
...or suggestions as to how I can do the update?
PS, I saw that there's another tread (http://forum.xda-developers.com/oneplus-one/help/apply-ota-stock-root-franco-23r-twrp-t2900311) with a OTA update failure but that one is different as there's errors involved so I felt that the suggestions were not applicable in my case.

try manually going thru the recovery and run update file from /cache directory. and see what errors is trowing
look for cm-bacon-3628510d76-to-ac1ccf7921-signed.zip

NiTRoN69 said:
try manually going thru the recovery and run update file from /cache directory. and see what errors is trowing
look for cm-bacon-3628510d76-to-ac1ccf7921-signed.zip
Click to expand...
Click to collapse
I found the update file and tried to install in manually. The attached image shows the error message which has no meaning to me. I then cleared the cache and also the dalvik cache, booted up, checked for update, downloaded the update and install.
Same problem happened so back to square one

JJD809 said:
I found the update file and tried to install in manually. The attached image shows the error message which has no meaning to me. I then cleared the cache and also the dalvik cache, booted up, checked for update, downloaded the update and install.
Same problem happened so back to square one
Click to expand...
Click to collapse
That error message is saying that you have a modified lockscreen.
Transmitted via Bacon

timmaaa said:
That error message is saying that you have a modified lockscreen.
Transmitted via Bacon
Click to expand...
Click to collapse
Ah! that makes sense. I got the lockscreen after reading an article about it on the XDA news pages (http://www.xda-developers.com/android/dynamic-oneplus-one-lock-screen/) which took me to this thread http://forum.xda-developers.com/oneplus-one/development/dynamic-oneplus-one-lockscreen-t2890808
From here forward, how do you suggest I proceed. Is there a way to "uninstall" this lock screen or is it a matter of me doing a factory reset and starting afresh?

Unless there's a return to stock zip in the thread where you got your modified lockscreen, you'll need to start fresh.
Transmitted via Bacon

Trying to apply on a stock Oneplus One, just with root and TWRP.
Code:
asset failed: apply_patch_check("/system/app/Music2.apk","....","....")
E: Error executing updated binary in zip '/cache/cm-bacon...signed.zip
Any ideas?

timmaaa said:
Unless there's a return to stock zip in the thread where you got your modified lockscreen, you'll need to start fresh.
Transmitted via Bacon
Click to expand...
Click to collapse
hi, I have the almost the same problem, I did a factory reset but it gives me error again, what should I do

fackamato said:
Trying to apply on a stock Oneplus One, just with root and TWRP.
Code:
asset failed: apply_patch_check("/system/app/Music2.apk","....","....")
E: Error executing updated binary in zip '/cache/cm-bacon...signed.zip
Any ideas?
Click to expand...
Click to collapse
System modification on Music2.apk. Read the above advice by timmaaa.
---------- Post added at 05:11 PM ---------- Previous post was at 05:08 PM ----------
shcxatter2 said:
hi, I have the almost the same problem, I did a factory reset but it gives me error again, what should I do
Click to expand...
Click to collapse
Boot on TWRP recovery and flash XNPH38R OTA zip. See here: 4. Latest OTA incremental update zip

Primokorn said:
System modification on Music2.apk. Read the above advice by timmaaa.
---------- Post added at 05:11 PM ---------- Previous post was at 05:08 PM ----------
Boot on TWRP recovery and flash XNPH38R OTA zip. See here: 4. Latest OTA incremental update zip
Click to expand...
Click to collapse
that's exactly what my problem is I cannot install the update , twrp just gives me error

Use the modified XNPH38R update. You can find it in the xnph38r thread in general.
You did system modifications. By using the modified script, it won't check for those files.
This is why I say when you want to do system changes, just use a custom ROM because OTAs are going to be a headache for you if u dont intend on using what the OTA provided to you.

zephiK said:
Use the modified XNPH38R update. You can find it in the xnph38r thread in general.
You did system modifications. By using the modified script, it won't check for those files.
This is why I say when you want to do system changes, just use a custom ROM because OTAs are going to be a headache for you if u dont intend on using what the OTA provided to you.
Click to expand...
Click to collapse
I'm trying to figure out what "system modifications" I've done. It's probably freezing apps in titanium backup, as google's music always FC's on all devices, so had to be ignored.

fackamato said:
I'm trying to figure out what "system modifications" I've done. It's probably freezing apps in titanium backup, as google's music always FC's on all devices, so had to be ignored.
Click to expand...
Click to collapse
Freezing apps in TB does nothing for those system modifications. Just flash the modified script XNPH38R update and you'll be able to update. I've said this 2 times now.

zephiK said:
Freezing apps in TB does nothing for those system modifications. Just flash the modified script XNPH38R update and you'll be able to update. I've said this 2 times now.
Click to expand...
Click to collapse
Thanks. I think it only has the full one not the incremental one?

After Custom Recovery OTA and Recovery-flashable Incrementals Don't work

I've had the OPO for over a year, and just now had the need to root it. An OTA happened to come in the next day, and the update process didn't work as I expected. So I'd like to know if I did something wrong, a random problem occurred, or this is the way it's supposed to work.
Until a couple days ago, the OPO was stock + all OTAs that had been released. I unlocked the bootloader, installed TWRP recovery, and installed SuperSU. All that went as expected. When the OTA notification arrived the next day, I tried to install it with "Update Cyanogen recovery" still unchecked (because original reports with CM 11S said you could keep your custom recovery with an OTA).
When I tried to install the update, the phone just rebooted to TWRP and the update was not stored anywhere on /sdcard. I then checked "Update Cyanogen recovery" and tried to install the OTA again. It did not install, and TWRP was still my recovery. Several repeats of this had no different result.
Then I flashed the stock CM recovery with fastboot. After verifying I had the CM recovery, I installed the OTA again, and it failed again, reboting to recovery and doing nothing else. Then I downloaded the incremental update and tried to flash that via CM recovery, and that failed too. I checked the file /System/build.opt, and line "ro.build.version.incremental" said 49d90510ef, which meant I should have been able to install the cm-bacon-49d90510ef-to-d91bf047f5-signed.zip file. But it failed and said the current build number was not as expected. The number it gave me was not anything that made sense looking at the list of recent incremental updates.
So at that point I bailed out and installed via recovery the full flashable zip file, and that worked.
If this is what I have to do each time, it's certainly doable, but I don't think this is how it's supposed to go. I'm surprised the OTA didn't work with the custom recovery installed, and I'm even more surprised that the incremental installation failed. Maybe trying to install the OTA without updating the CM recovery messed things up, but that doesn't seem likely either. When the next OTA comes out, I'll see if any of these troubles are repeated. But I'd like to know how the OTA was supposed to work after installing a custom recovery.

I am still yet to figure this one out also, my friend I'm sure with time someone will respond who had better experience with this; just be patient
Have you been able to root yet? I can't seem to be able to on the new incremental yet.
@MidnightJava

Looks like I'm not the only one with this problem.
I'm trying to find now the link for Cyanogen Recovery flashable to see it that fix the OTAs

Check the CyanogenMod website, @distante

vince.lupe said:
Have you been able to root yet? I can't seem to be able to on the new incremental yet.
@MidnightJava
Click to expand...
Click to collapse
After installing the latest CM 12.1 ROM, I had to re-flash SuperSU. After doing that, root access is working fine. If you're having trouble rooting after installing the incremental, then my experience is perhaps not applIcable—since I was not able to do an incremental installation and had to re-flash the entire ROM.

distante said:
Looks like I'm not the only one with this problem.
I'm trying to find now the link for Cyanogen Recovery flashable to see it that fix the OTAs
Click to expand...
Click to collapse
This thread with Cyanogen mirrors and info has exactly what you need.

MidnightJava said:
After installing the latest CM 12.1 ROM, I had to re-flash SuperSU. After doing that, root access is working fine. If you're having trouble rooting after installing the incremental, then my experience is perhaps not applIcable—since I was not able to do an incremental installation and had to re-flash the entire ROM.
Click to expand...
Click to collapse
I had to completely re-flash stock 3JL full also, but this time root doesn't work. Tried to use WugFresh's Bacon Root Toolkit - didn't work - then, I tried to flash SuperSu via TWRP recovery (after unlocking bootloader), and that didn't work either? In other words, I have bootloader unlock, custom recovery installed, but no root :/

vince.lupe said:
I had to completely re-flash stock 3JL full also, but this time root doesn't work. Tried to use WugFresh's Bacon Root Toolkit - didn't work - then, I tried to flash SuperSu via TWRP recovery (after unlocking bootloader), and that didn't work either? In other words, I have bootloader unlock, custom recovery installed, but no root :/
Click to expand...
Click to collapse
What happens when you try to root? Does it seem successful, but then you don't actually have root access? Or do you get some failure indication when you flash SuperSU? I've rooted a few phones in the last few years, but I'm far from an expert. Hopefully someone else will jump in with some idea of what went wrong. Shooting somewhat in the dark, I'd say look at the version of SuperSU and make sure it's the latest and the right one for the ROM, look at read-write permissions on your storage (if you can, you may need root access to check it properly). Of course wiping cache is always a good step, and if nothing else works, maybe factory reset, re-lock the bootloader, and then unlock and flash custom recovery again, and see if root can be successful then.

Once on custom recovery ( TWRP ) OTAs will NOT not install, unless you revert back to CM stock recovery. If you don't want to do that, wait for a signed flashable version to come out, which is normally 1-2 days after. Everytime you flash an update you will have to reinstall TWRP and SuperSU.
---------- Post added at 03:31 PM ---------- Previous post was at 03:25 PM ----------
vince.lupe said:
I had to completely re-flash stock 3JL full also, but this time root doesn't work. Tried to use WugFresh's Bacon Root Toolkit - didn't work - then, I tried to flash SuperSu via TWRP recovery (after unlocking bootloader), and that didn't work either? In other words, I have bootloader unlock, custom recovery installed, but no root :/
Click to expand...
Click to collapse
Did you guys remove the " Update Cyanogen recovery" in Dev options and "respect CM root settings " In SuperSU settings ?

Cholerabob said:
Once on custom recovery ( TWRP ) OTAs will NOT not install, unless you revert back to CM stock recovery. If you don't want to do that, wait for a signed flashable version to come out, which is normally 1-2 days after. Everytime you flash an update you will have to reinstall TWRP and SuperSU.
Click to expand...
Click to collapse
I figured that was the case when it failed. What seems anomalous in my case is that even after reverting to the stock recovery and verifying that it was installed, OTAs would not succeed. I didn't know about the "respect CM root settings " In SuperSU settings that you mentioned. Maybe that was the problem? Either that or the fact that I tried to install the OTA first with the custom recovery. Certainly the fact that the incremental installation reported I was at a different build number than what was listed in /System/build.opts indicates something was out of whack on my phone.
Temporarily reverting to the stock recovery and installing the OTA, then going back to custom recovery, seems a bit simpler than flashing the signed zip file and then re-installing recovery and SuperSU, but either way is not too bad. But being an engineer, I always have to find the optimum path and understand why things don't work the way I thought they should.

MidnightJava said:
What happens when you try to root? Does it seem successful, but then you don't actually have root access? Or do you get some failure indication when you flash SuperSU? I've rooted a few phones in the last few years, but I'm far from an expert. Hopefully someone else will jump in with some idea of what went wrong. Shooting somewhat in the dark, I'd say look at the version of SuperSU and make sure it's the latest and the right one for the ROM, look at read-write permissions on your storage (if you can, you may need root access to check it properly). Of course wiping cache is always a good step, and if nothing else works, maybe factory reset, re-lock the bootloader, and then unlock and flash custom recovery again, and see if root can be successful then.
Click to expand...
Click to collapse
It just tells me that I don't have access :/ Everything flashes perfectly fine, but then when I boot up and try to access root, it tells me that I don't have access. I've tried everything already :/
---------- Post added at 06:51 PM ---------- Previous post was at 06:47 PM ----------
Cholerabob said:
Did you guys remove the " Update Cyanogen recovery" in Dev options and "respect CM root settings " In SuperSU settings ?
Click to expand...
Click to collapse
I did do both :/

MidnightJava said:
I figured that was the case when it failed. What seems anomalous in my case is that even after reverting to the stock recovery and verifying that it was installed, OTAs would not succeed. I didn't know about the "respect CM root settings " In SuperSU settings that you mentioned. Maybe that was the problem? Either that or the fact that I tried to install the OTA first with the custom recovery. Certainly the fact that the incremental installation reported I was at a different build number than what was listed in /System/build.opts indicates something was out of whack on my phone.
Temporarily reverting to the stock recovery and installing the OTA, then going back to custom recovery, seems a bit simpler than flashing the signed zip file and then re-installing recovery and SuperSU, but either way is not too bad. But being an engineer, I always have to find the optimum path and understand why things don't work the way I thought they should.
Click to expand...
Click to collapse
Not really since the signed zip file come with superSU, after the install it will ask you if you want to install superSU automatically, and TWRP will too when you start your TWRP app on your phone after reboot. But to each his own
---------- Post added at 08:22 PM ---------- Previous post was at 08:19 PM ----------
vince.lupe said:
It just tells me that I don't have access :/ Everything flashes perfectly fine, but then when I boot up and try to access root, it tells me that I don't have access. I've tried everything already :/
---------- Post added at 06:51 PM ---------- Previous post was at 06:47 PM ----------
I did do both :/
Click to expand...
Click to collapse
Is your bootloader unlocked ? Reinstalled superSU ? Did you check with the fastboot command ? If you don't know how, look at Heisenberg's guide.

Cholerabob said:
Not really since the signed zip file come with superSU, after the install it will ask you if you want to install superSU automatically, and TWRP will too when you start your TWRP app on your phone after reboot. But to each his own
---------- Post added at 08:22 PM ---------- Previous post was at 08:19 PM ----------
Is your bootloader unlocked ? Reinstalled superSU ? Did you check with the fastboot command ? If you don't know how, look at Heisenberg's guide.
Click to expand...
Click to collapse
Yes, bootloader is unlocked and SuperSu was reinstalled :/

Is it safe to do system updates while rooted?

Hello everyone!
Today I got my Mate9 toyed around and then decided to root it. All went smooth as butter and everything is working perfectly.
Just about 1 hour ago, I see a notification saying that there is a system update available: later or restart now?
I am wondering, will this system update mess up my phone, since it is rooted, or not? I'd like to avoid any possible mess up for the time being

N3sh said:
Hello everyone!
Today I got my Mate9 toyed around and then decided to root it. All went smooth as butter and everything is working perfectly.
Just about 1 hour ago, I see a notification saying that there is a system update available: later or restart now?
I am wondering, will this system update mess up my phone, since it is rooted, or not? I'd like to avoid any possible mess up for the time being
Click to expand...
Click to collapse
Depends on how you rooted.
For a successful OTA install your device probably must meet the following criteria
HUAWEI stock recovery installed
unaltered /system, /product and /vendor partitions
So if you rooted with a "systemless" method (e.g. Magisk, recent SuperSU) and haven't done other installs/modifications that typically change /system you could try it. And you have to flash stock recovery (i.e. get rid of TWRP temporarily for the OTA install).

st_voss said:
Depends on how you rooted.
For a successful OTA install your device probably must meet the following criteria
HUAWEI stock recovery installed
unaltered /system, /product and /vendor partitions
So if you rooted with a "systemless" method (e.g. Magisk, recent SuperSU) and haven't done other installs/modifications that typically change /system you could try it. And you have to flash stock recovery (i.e. get rid of TWRP temporarily for the OTA install).
Click to expand...
Click to collapse
Here is what I did:
- Unlocked bootloader with Huawei code
- Installed new TWRP recovery
- Flashed supersu via adb (no SD card atm)
- Installed supersu apk
- Ta-da!
I actually checked the changelog of the new "update" and it is basically to restore the system back to before the change. Does it mean I am stuck with this version forever now?

N3sh said:
Here is what I did:
- Unlocked bootloader with Huawei code
- Installed new TWRP recovery
- Flashed supersu via adb (no SD card atm)
- Installed supersu apk
- Ta-da!
I actually checked the changelog of the new "update" and it is basically to restore the system back to before the change. Does it mean I am stuck with this version forever now?
Click to expand...
Click to collapse
What supersu zip did you use?
And no you are not stuck with your version forever. But updating will probably require more than simply applying an OTA update.

st_voss said:
What supersu zip did you use?
And no you are not stuck with your version forever. But updating will probably require more than simply applying an OTA update.
Click to expand...
Click to collapse
Followed this: https://forum.xda-developers.com/mate-9/development/recovery-unofficial-twrp-huawei-mate-9-t3515617

N3sh said:
Followed this: https://forum.xda-developers.com/mate-9/development/recovery-unofficial-twrp-huawei-mate-9-t3515617
Click to expand...
Click to collapse
So you are using Phh's superuser? I don't think that it's "systemless".
I would recommend a complete reinstall/update using https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108 and using the lastest Magisk for rooting.

Mmm, I might just keep this until I have the need to reinstall. Thanks

It doesn't seem a system update allows you to skip it.
If the phone is rebooted, will it enter a loop or just fail the installation and carry on as normally?

I removed auto-download and rebooted, nothing different. Great

4thfloorcaveman said:
It doesn't seem a system update allows you to skip it.
If the phone is rebooted, will it enter a loop or just fail the installation and carry on as normally?
Click to expand...
Click to collapse
I think it's (stock) recovery that installs an OTA. I don't know the mechanism that allows the recovery to find the OTA file (maybe the OTA file is copied to a directory where recovery is lookup for update files or some boot parameter is modified) but a normal reboot should not trigger an OTA install attempt.

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