[Q] Latest OTA with twrp ?? - ONE Q&A, Help & Troubleshooting

I've got a notification for the system update. (The latest one-20mb fixing the screen issues)
I'm rooted and have twrp installed. When I click on the system update I get a popup to update cyanogen recovery. What if I ignore it and install the update anyway. Will it work ?
Will my data be deleted ?

ronu said:
I've got a notification for the system update. (The latest one-20mb fixing the screen issues)
I'm rooted and have twrp installed. When I click on the system update I get a popup to update cyanogen recovery. What if I ignore it and install the update anyway. Will it work ?
Will my data be deleted ?
Click to expand...
Click to collapse
You cannot update that 20mb zip using twrp. You have to update using cyanogen recovery.

ronu said:
I've got a notification for the system update. (The latest one-20mb fixing the screen issues)
I'm rooted and have twrp installed. When I click on the system update I get a popup to update cyanogen recovery. What if I ignore it and install the update anyway. Will it work ?
Will my data be deleted ?
Click to expand...
Click to collapse
You can do one thing
Flash Stock recovery image only from fastboot commands and then apply this 20MB OTA and then revert back to twrp via fastboot commands

I have twrp and have updated 20+ times... Never had an issue.
Sent from my A0001 using XDA Free mobile app

Related

[Q] How can I update my rooted Moto G to 4.4.4 ?

Hi ! I tried to update to 4.4.4 when my phone asked me to, but the process failed and my phone was stuck in a booting loop. I managed to delete the file causing the error, but now I don't know how to update to 4.4.4 without having the same error. I understand that because I rooted my phone I must follow a special process, but I don't know exactly what to do. Should I un-root my phone to make the update ?
Thanks for the help !
JayZeus said:
Hi ! I tried to update to 4.4.4 when my phone asked me to, but the process failed and my phone was stuck in a booting loop. I managed to delete the file causing the error, but now I don't know how to update to 4.4.4 without having the same error. I understand that because I rooted my phone I must follow a special process, but I don't know exactly what to do. Should I un-root my phone to make the update ?
Thanks for the help !
Click to expand...
Click to collapse
If you made some modification to the 4.4.2 rom you'll have to restore the stock before upgrading to 4.4.4.
Bootloader can be unlocked, Recovery can be custom but any mod/root to the room will cause the error.
To restore to stock follow this guide: http://forum.xda-developers.com/showthread.php?t=2542219
Thanks a lot, it worked!
By the way is the part where you erase you data mandatory ? In case I have to do this again.
Erase cache and erase userdata delete your stuff so if you want to keep it just do the procedure without those 2 lines and you are good to go (that's what I did and it worked flawlessly I restored without losing any data) :beer:
Sent from my XT1032 using XDA Free mobile app
mr_nooby said:
Erase cache and erase userdata delete your stuff so if you want to keep it just do the procedure without those 2 lines and you are good to go (that's what I did and it worked flawlessly I restored without losing any data) :beer:
Sent from my XT1032 using XDA Free mobile app
Click to expand...
Click to collapse
Good to know ! Thank you.
mr_nooby said:
Erase cache and erase userdata delete your stuff so if you want to keep it just do the procedure without those 2 lines and you are good to go (that's what I did and it worked flawlessly I restored without losing any data) [emoji481]
Sent from my XT1032 using XDA Free mobile app
Click to expand...
Click to collapse
This way I'll keep my installed applications?
Thanks.
4.4.2 > 4.4.4. just rolled out in UK (o2 moto g).
right after i get my phone rooted and started setting it up...
Thanks for this thread.. what's the minimum we have to restore, basically the system partition so it's unrooted?
If we have stock 4.4.2 (rooted) can we flash JUST these 3 files?
system.img_sparsechunk1
system.img_sparsechunk2
system.img_sparsechunk3
and skip the rest? I want to save redo-ing as much as possible..
I got the 4.4.4 OTA today (210.12.40.en.GB) and I have unlocked bootloader + Philz recovery - Philz worked fine for the 4.4.2 OTA update, but when I downloaded the 4.4.4 OTA and rebooted Philz would abort with "a status 7" mismatch error and then the phone would boot to Android, then 20 seconds later shutdown and reboot to Philz again, continuously. After some playing, I did the following:
1. Flashed stock recovery (taken from Mototool AIO's 4.4.2 stock.img) from fastboot - re-downloaded the 4.4.4 OTA but that failed with "Error!"
2. Flashed stock kernel (I was running faux123) - same issue, 4.4.4 OTA failed still.
3. Flashed latest Philz recovery again (philz_touch_6.50.6-falcon.zip) then
4. Flashed stock 4.4.2 GB kernel (to match my OTA version) - kernel from here http://forum.xda-developers.com/showthread.php?t=2649763 - success... OTA downloaded and this time installed.
SO, conclusion is you don't need stock recovery to flash OTA, BUT you do need the correct kernel for your update and having a custom kernel causes the mismatch error.
Hope this helps someone!
So the UPDATE-SuperSU-v1.91.zip in MotoG-Tools.zip still works to root 4.4.4 right?
i found it here
http://www.swedroid.se/forum/showthread.php?t=106595
and this is what i used for 4.4.2
Most of the old guides around no longer worked in 4.4.2, i dunno if they closed any other holes in 4.4.4?
edit: version typo sorry
just for informations, I updated succesfully from 4.4.2 to 4.4.4. Kitkat 176.44.1falcon-retail en.GB with ClockWordMod recovery v6.0.4.7
Everything worked without problems, CWM alerted me about not verified files, and gave me the option to install updates anyway.
I only have to refix the bootloader unlocked warning
JayZeus said:
I managed to delete the file causing the error, but now I don't know how to update to 4.4.4 without having the same error.
Click to expand...
Click to collapse
JayZeus,
How did you manage to delete the file? I'm assuming it's the update.zip file? At this point, I just want to use the phone and not worry about updating to 4.4.4 at this time. Thanks.
agoodhi said:
JayZeus,
How did you manage to delete the file? I'm assuming it's the update.zip file? At this point, I just want to use the phone and not worry about updating to 4.4.4 at this time. Thanks.
Click to expand...
Click to collapse
I figured it out... I simply did a delete cache from CWM recovery and now no more boot loop.
fatechand said:
just for informations, I updated succesfully from 4.4.2 to 4.4.4. Kitkat 176.44.1falcon-retail en.GB with ClockWordMod recovery v6.0.4.7
Everything worked without problems, CWM alerted me about not verified files, and gave me the option to install updates anyway.
I only have to refix the bootloader unlocked warning
Click to expand...
Click to collapse
you just updated with the OTA update (as normal)?
is it possible to do an OTA update with a rooted phone, just delete cache, keep userdata? or you have to go through all the hassle with restoring stock?
more important, is it possible to tell phone not to check for updates? if this bootloop happens with every OTA update in future, then this is not a good idea (to mod/root phone) as a user may do this and break their phone at any time. the phone is prompting regularly to apply the update.
edit: i'm guessing freezing using Titanium, MotorolaOTA 1.0 might stop update notificiations, anyone confirm if this works and is safe?
there's a nice list here but the colours don't make sense http://forum.xda-developers.com/moto-x/moto-x-qa/guide-freezing-moto-x-bloat-titanium-t2432729
Smiff2 said:
you just updated with the OTA update (as normal)?
is it possible to do an OTA update with a rooted phone, just delete cache, keep userdata? or you have to go through all the hassle with restoring stock?
more important, is it possible to tell phone not to check for updates? if this bootloop happens with every OTA update in future, then this is not a good idea (to mod/root phone) as a user may do this and break their phone at any time. the phone is prompting regularly to apply the update.
edit: i'm guessing freezing using Titanium, MotorolaOTA 1.0 might stop update notificiations, anyone confirm if this works and is safe?
there's a nice list here but the colours don't make sense http://forum.xda-developers.com/moto-x/moto-x-qa/guide-freezing-moto-x-bloat-titanium-t2432729
Click to expand...
Click to collapse
I confirm that just updated my rooted motog following Ota update, without deleting any cache or anyrhing else and of course without loosing any data.
fatechand said:
I confirm that just updated my rooted motog following Ota update, without deleting any cache or anyrhing else and of course without loosing any data.
Click to expand...
Click to collapse
Still can't do OTA update with rooted phone and CWM installed. For now, I'm just postponing the OTA each time it pops up. When I get the time, I'll put back stock recovery and try again.
Has anyone been able to OTA update to 4.4.4 with CWM (v6.0.4.6) installed?
---------- Post added at 06:32 AM ---------- Previous post was at 06:14 AM ----------
agoodhi said:
Still can't do OTA update with rooted phone and CWM installed. For now, I'm just postponing the OTA each time it pops up. When I get the time, I'll put back stock recovery and try again.
Has anyone been able to OTA update to 4.4.4 with CWM (v6.0.4.6) installed?
Click to expand...
Click to collapse
CWM message:
E: failed to verify whole-file signature
E: signature verification failed
Installing update...
assert failed: getprop("ro.product.device) == "falcon_cdma" || getprop("ro.build.product") == "falcon_cdma"
E: Error in /cache/Blur_Version.173.44.20.falcon_cdma.Verizon.en.US.zip
(Status 7)
Installation aborted.
Rebooting...
fatechand said he had CWM 6047 installed and OTA update was ok. he just had to re-root? perhaps difference between 6046 and 6047 CWM, or some difference in way you rooted?
I have same recovery, rooted, 4.4.2, so should work... ?

Problem while updating CM12

Since I've CM12 in my OPO I can't update the nightlies using OTA. I can download the update but when it restarts to recovery to install the new update I have always the same error and I have to do the wipes with each update to solve it. I've been looking for a solution in xda but I haven't found it. See the attachment please. Thanks in advance.
it's the same for me as I have red lines after reboot and upade is installed
Jjul said:
it's the same for me as I have red lines after reboot and upade is installed
Click to expand...
Click to collapse
I've the error but the ROM doesn't update
I got the error too, manually flash the file that gets downloaded into the cmupdater folder and it updates.
Kitch16 said:
I got the error too, manually flash the file that gets downloaded into the cmupdater folder and it updates.
Click to expand...
Click to collapse
Yeah. I've tried it before but when I restart the OPO after install manually the zip, the screen stuck at "Finishing boot" and I have to do wipes again

Moto G (1st gen) OTA to Lollipop fails

Hi folks, so, I received OTA update for my Moto G (XT1032).
Phone was rooted (I did unroot from SuperSU). Also, I've re-installed Stock recovery (to make sure) and wiped cache/dalvik.
But, update still fails.
I don't have much root-related soft (like Xposed etc) installed - so pretty sure this should not cause an issue.
But still, update fails.
Any ideas how to troubleshoot/make it work? Maybe installing OTA somehow from recovery (custom one, TWRP)?
Any comments - much appreciated. I guess I'm not alone in this, but still...
Thanks
Same problem here
Ulverinho said:
Hi folks, so, I received OTA update for my Moto G (XT1032).
Phone was rooted (I did unroot from SuperSU). Also, I've re-installed Stock recovery (to make sure) and wiped cache/dalvik.
But, update still fails.
I don't have much root-related soft (like Xposed etc) installed - so pretty sure this should not cause an issue.
But still, update fails.
Any ideas how to troubleshoot/make it work? Maybe installing OTA somehow from recovery (custom one, TWRP)?
Any comments - much appreciated. I guess I'm not alone in this, but still...
Thanks
Click to expand...
Click to collapse
Have to install stock ROM again then update it via ota. Could also try flashing an ota update file via the official recovery of your phone.
A_Bunny said:
Have to install stock ROM again then update it via ota. Could also try flashing an ota update file via the official recovery of your phone.
Click to expand...
Click to collapse
Yep, my guess was the same. As per official recovery - I'll try adb sideload, but first time it couldn't find phone (all drivers installed and up-to-date).
http://forum.xda-developers.com/moto-g/help/driver-fastboot-falcon-s-t2820848
This error pops up - I can't find solution also...
Ulverinho said:
Yep, my guess was the same. As per official recovery - I'll try adb sideload, but first time it couldn't find phone (all drivers installed and up-to-date).
http://forum.xda-developers.com/moto-g/help/driver-fastboot-falcon-s-t2820848
This error pops up - I can't find solution also...
Click to expand...
Click to collapse
Install the recovery with fastboot not adb.
A_Bunny said:
Install the recovery with fastboot not adb.
Click to expand...
Click to collapse
Well, I might misunderstood, but:
I have official recovery (fastboot is mode of it, I guess, when U press Power+volume key?)
I've read about adb sideload zip_name_of_OTA.zip
I don't know any other way to install OTA apart from let phone handle it OR adb sideload.
Ulverinho said:
Well, I might misunderstood, but:
I have official recovery (fastboot is mode of it, I guess, when U press Power+volume key?)
I've read about adb sideload zip_name_of_OTA.zip
I don't know any other way to install OTA apart from let phone handle it OR adb sideload.
Click to expand...
Click to collapse
Just load it onto your phone before you flash it. Your ROM does work.
A_Bunny said:
Just load it onto your phone before you flash it. Your ROM does work.
Click to expand...
Click to collapse
Load ZIP of OTA on SD Card and install it from Recovery? Will it work?
Ulverinho said:
Load ZIP of OTA on SD Card and install it from Recovery? Will it work?
Click to expand...
Click to collapse
It may work if it is the stock recovery.
A_Bunny said:
It may work if it is the stock recovery.
Click to expand...
Click to collapse
Got this, screenshot in attachment.
Fingerprints are wrong. In build.prop - I can see it's fine, fingerprint of current 4.4.4. - matches expected.
But as soon as update starts - it says that 4.4.2 is fingerprint of my OS. Bollocks.
Edited OTA zip, edited some metadata file...
Why it won't install on pretty clean phone - I can't understand...Previous installs of OTA went fine with root etc.
Ulverinho said:
Got this, screenshot in attachment.
Fingerprints are wrong. In build.prop - I can see it's fine, fingerprint of current 4.4.4. - matches expected.
But as soon as update starts - it says that 4.4.2 is fingerprint of my OS. Bollocks.
Edited OTA zip, edited some metadata file...
Why it won't install on pretty clean phone - I can't understand...Previous installs of OTA went fine with root etc.
Click to expand...
Click to collapse
Well the only thing I would recommend would be to install the stock system though fastboot manualy.
Ulverinho said:
Hi folks, so, I received OTA update for my Moto G (XT1032).
Phone was rooted (I did unroot from SuperSU). Also, I've re-installed Stock recovery (to make sure) and wiped cache/dalvik.
But, update still fails.
I don't have much root-related soft (like Xposed etc) installed - so pretty sure this should not cause an issue.
But still, update fails.
Any ideas how to troubleshoot/make it work? Maybe installing OTA somehow from recovery (custom one, TWRP)?
Any comments - much appreciated. I guess I'm not alone in this, but still...
Thanks
Click to expand...
Click to collapse
i feel ya same thing here, than i tryed installing a stock lollipop from here via twrp witch ended up messing my phone with failing the procedure wondered around couldnt revert to stock since im a noob and didnt even backed up the rom,but at the and of the day thank god for the cm12.1 finally menaged to make my phone running again at least
Greetings, I have the same problem, it is the last screen that appears when you install the update, and then restarts it goes off the screen update error ...
To anyone having issues:
1. Make sure you're on completely stock 4.4.4 (Refer to http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-rom-collection-t2854688 and use only untouched 4.4.4 version for your phone if you have to reflash before continuing)
2. Make sure you're on stock recovery (Refer to http://forum.xda-developers.com/showthread.php?t=2649763)
*Uninstall XPOSED if using it
3. I personally let update run on its own after reverting everything to stock.
fusionice said:
To anyone having issues:
1. Make sure you're on completely stock 4.4.4 (Refer to http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-rom-collection-t2854688 and use only untouched 4.4.4 version for your phone if you have to reflash before continuing)
2. Make sure you're on stock recovery (Refer to http://forum.xda-developers.com/showthread.php?t=2649763)
*Uninstall XPOSED if using it
3. I personally let update run on its own after reverting everything to stock.
Click to expand...
Click to collapse
Yeah, that's the better way.
But I guess, I can install Stock 5.* straight away after wiping? Why bother about OTA, if there is ROM available?
fusionice said:
To anyone having issues:
1. Make sure you're on completely stock 4.4.4 (Refer to http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-rom-collection-t2854688 and use only untouched 4.4.4 version for your phone if you have to reflash before continuing)
2. Make sure you're on stock recovery (Refer to http://forum.xda-developers.com/showthread.php?t=2649763)
*Uninstall XPOSED if using it
3. I personally let update run on its own after reverting everything to stock.
Click to expand...
Click to collapse
Yep.
The solution is backup data, restore stock last firmware using fastboot guide posted in this forum and not even update apps (cancel gmail registration and everything it asks when it first starts) ONLY update motorola update services so you can get the ota again an install it. If you have the ota downloaded you can flash it through recovery but using the last recovery version (.61) and of course last firmware version. If you guys flash it all through fastboot, it should install w/o any problems.

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

Categories

Resources