Database Info

I'm stuck

Hi guys,
for some reason after I did update to KangVIP I can't get rid off it. Besides I got no wifi and bt and I was going to start over with b023 as suggested but at this point I wont bother anymore.
I did wipe the system, I did advanced wipe using twrp but no matter what I do none of the stock firmwares are going through however the Kanga one always goes through.(KangaVIP goes through only in TWRP)
twrp 2.8.7.0
wipe
advanced wipe
I select all the partitions
mkdosfs process ended with error=1
unable to wipe /usb
unknown mtp message type: 1
unable to wipe /usb
I go back, restart to fastboot, (device is saying there is no OS installed), I restore the recovery, create dload folder on my sdcard, put there 028 (actually I tried all of them already), volume+ volume - power and I get error.
What am I missing ?
Anyone can help ?
Thanks in advance.
Eric

First you did a OTA from B029 to B209?
If so you are now on a Android 6 ROM you cant go back to Android 5 without a Rollback from Huawei.

Hirs_E_Fruit said:
First you did a OTA from B029 to B209?
If so you are now on a Android 6 ROM you cant go back to Android 5 without a Rollback from Huawei.
Click to expand...
Click to collapse
Yes I did then I wiped everything and started with b028 again.
Same thing, wifi didn't work same with BT.
Wipe again and this time I did local update and since the local update I can't go back not even b029.

77Eric77 said:
Yes I did then I wiped everything and started with b028 again.
Same thing, wifi didn't work same with BT.
Wipe again and this time I did local update and since the local update I can't go back not even b029.
Click to expand...
Click to collapse
Right now you are on a Android 5 or Android 6 ROM?
If you on a Android 5 ROM you can force update a Complete ROM to install a clean system and try if everything works.

Hirs_E_Fruit said:
Right now you are on a Android 5 or Android 6 ROM?
If you on a Android 5 ROM you can force update a Complete ROM to install a clean system and try if everything works.
Click to expand...
Click to collapse
I'm stuck on 6.0
I know I can do force update on 5.0 I said it above I just can't do it with 6.0 -> b029, only with your rom.

Anyone else is having this issue ?
The Kanga rom got a quite few problems no wifi and not BT, Google play services crashing (this can be fixed with gapps) my co worker just tried it with his own methods and same issue. After I went through the whole Kanga thread 60% of the posters got problems most of them are ignored.

I don't have any problems but I think the people with problems are people who have a DAV 701L.

Hirs_E_Fruit said:
Right now you are on a Android 5 or Android 6 ROM?
If you on a Android 5 ROM you can force update a Complete ROM to install a clean system and try if everything works.
Click to expand...
Click to collapse
Hirs_E_Fruit said:
I don't have any problems but I think the people with problems are people who have a DAV 701L.
Click to expand...
Click to collapse
I got DAV-703L, just simple question, why is the wifi and bt not working ?
When I get into Kanga I can remove the root or deny access to it is there a way to ditch it ?
Yeah I know it's working for you and it's not working for 10 other people including 703L owners. There is something wrong with the rom no doubt about it.

77Eric77 said:
I got DAV-703L, just simple question, why is the wifi and bt not working ?
When I get into Kanga I can remove the root or deny access to it is there a way to ditch it ?
Yeah I know it's working for you and it's not working for 10 other people including 703L owners. There is something wrong with the rom no doubt about it.
Click to expand...
Click to collapse
I think there was an error while flashing and without a full clean Rom flash i can't see a solution.
Before I got it to work I flashed it more than 3 times and everytime everything worked so I think don't think the ROM is that bugged.

Hirs_E_Fruit said:
I think there was an error while flashing and without a full clean Rom flash i can't see a solution.
Before I got it to work I flashed it more than 3 times and everytime everything worked so I think don't think the ROM is that bugged.
Click to expand...
Click to collapse
The first rom you introduced is working "fine" I get the wifi and bt no problem but once I switch into the latest build it's gone.
Any idea where can I get full clean Rom ?
This one is a no go http://www.needrom.com/download/p8max-dav-703l/

I managed to rollback to 5.1.1 but when I try to force flash it, it says it's not compatible.

If you don't update properly to B209, when you flash any B209 rom you are going to run into issues such as the wireless Bluetooth and sim card switching for some. If you properly updated the dload method should have completed successfully. Look at the kernel and radio version of B209 in About phone and compare it to others and see if they match.

ajsmsg78 said:
If you don't update properly to B209, when you flash any B209 rom you are going to run into issues such as the wireless Bluetooth and sim card switching for some. If you properly updated the dload method should have completed successfully. Look at the kernel and radio version of B209 in About phone and compare it to others and see if they match.
Click to expand...
Click to collapse
I don't want to use your rom even if you removed the Chinese it's still inside the system. Boot load times take much longer. Unexpected crashes. I did try it on 4 phones with OTA and local updates 2 are working but the Kang does crash twice a day minimum.
All what I'm asking is how to restore it to it's original settings, this was my worst mistake ever.
What I'm trying to say if I do something I do it properly just look at your thread 85% failure ratio that doesn't look like it was done properly does it ?

77Eric77 said:
I don't want to use your rom even if you removed the Chinese it's still inside the system. Boot load times take much longer. Unexpected crashes. I did try it on 4 phones with OTA and local updates 2 are working but the Kang does crash twice a day minimum.
All what I'm asking is how to restore it to it's original settings, this was my worst mistake ever.
What I'm trying to say if I do something I do it properly just look at your thread 85% failure ratio that doesn't look like it was done properly does it ?
Click to expand...
Click to collapse
Really dude?? No worries, it will be the last time I do anything for the P8Max. Maybe you should just sell the phone since you're having all sorts of issues with it....or maybe you should have left it totally stock then. Or maybe read through the Mediapad X2 forums because the two phones are very similar.

Worth it to upgrade from Android 10 Sept 2020 to Android 11 right now or wait?

Or wait a couple of months for them to tweak it a bit?
I only run Magik and not Xposed, not that it matters!

I'm not rooted, but I've been running R since the first public ßeta.
It's been the smallest update so far in a long time for Android. Very little has changed, compared to previous major version upgrades.
If you can root (and from what I read i think you can with Magisk), make a full backup and try it.
Sent from my Pixel 4 XL using Tapatalk

I don't really know what you'd be waiting for. I don't think a non-rooted person would notice much in terms of drawbacks. Magisk modules level, there were some issues... but I think most things are getting worked out. Xposed technically works, but more than half of my modules broke in a way that probably won't be fixed for a while. I still feel like I'm at a net-negative in terms of phone features. A11 brought little and broke a lot of my QoL tweaks that used Xposed.
I make no claims about SafetyNet as I use no apps that even check it.

I think A11 has been released formally by google and most of issues have been fixed or addressed.
I used magisk and edxposed. That's not a problem for me(I used Edxposed for fingerface only). Regarding of safetynet issue, it also has solution to make it pass by magisk modules and kernel side.
Until now, I'm happy with A11.

I ended up doing a full wipe and upgrade to Android 11 Oct 2020.
I have Magisk running with the SQL Lite mods for Google Pay and obviously I have root so I'm basically back where I was on Android 10.
I hadn't use Xposed yet and I don't know if I will yet. I was using Viper Audio mod but I don't know if I noticed a major difference, mostly I just stream bluetooth in my SUV.
So far, so good.

I tried it and reverted back to 10 - as mentioned didn't gain much but broke a lot. Even in stock form I can't get videos to load a subtitle file because of storage permissions and what not. A tweaked out install of 10 is faaaar nicer imo so that's what I'm running, probably until a new phone comes out sadly.

Kris Chen said:
I think A11 has been released formally by google and most of issues have been fixed or addressed.
I used magisk and edxposed. That's not a problem for me(I used Edxposed for fingerface only). Regarding of safetynet issue, it also has solution to make it pass by magisk modules and kernel side.
Until now, I'm happy with A11.
Click to expand...
Click to collapse
can i ask how you upgraded to A11? Im on 10 rooted with magisk and keep hearing mixed messages on upgrading. And is it necessary to wipe? I really don't want to.

A11 is not too bad, but as others have said little things here and there that break. Like for me I listen to SiriusXM app on mobile and for some odd reason it will stop playing all of a sudden and close. It's like the aggressive memory management kills the app for no reason. I even have battery optimization turned off and still does it.
Thinking about moving back to A10 from August, not really much I have to have to stick with latest A11 updates.

qman66 said:
can i ask how you upgraded to A11? Im on 10 rooted with magisk and keep hearing mixed messages on upgrading. And is it necessary to wipe? I really don't want to.
Click to expand...
Click to collapse
Flash the factory image, but remove the -w in the flash-all file. Then in Magisk Manager switch tot he beta channel and patch the boot image with that. Flash it and you're done.

GjorgiDxc said:
Flash the factory image, but remove the -w in the flash-all file. Then in Magisk Manager switch tot he beta channel and patch the boot image with that. Flash it and you're done.
Click to expand...
Click to collapse
You do know the latest version of magisk has a11 support?

GjorgiDxc said:
Flash the factory image, but remove the -w in the flash-all file. Then in Magisk Manager switch tot he beta channel and patch the boot image with that. Flash it and you're done.
Click to expand...
Click to collapse
Ok so I shouldn't install it via the ota? I keep getting the pop up to update every day.

Does using Magisk to dl / install the OTA, then patch the non-live and newly flashed partition, then finally rebooting not work?
When I was rooted that was always the easiest way.
And based upon the post 2 above this one, Magisk now supports A11 without ẞeta, right?
From Coral, with Tapatalk.

kdoggy said:
I ended up doing a full wipe and upgrade to Android 11 Oct 2020.
I have Magisk running with the SQL Lite mods for Google Pay and obviously I have root so I'm basically back where I was on Android 10.
I hadn't use Xposed yet and I don't know if I will yet. I was using Viper Audio mod but I don't know if I noticed a major difference, mostly I just stream bluetooth in my SUV.
So far, so good.
Click to expand...
Click to collapse
How is 11 for you going so far, I am thinking in reverting back to 10, battery is awful on 11

stable android 11 released for op7p

why is no one discussing stable android 11 for op7p ? got my update round 3 a.m. this morning. been searching all day for a working twrp since the stable android 11 been released. no luck though......

Hi,
Today I installed the update manually and my phone keeps flashing the TWRP load-screen at boot. It's stuck now. Is that because there is no compatible TWRP version yet? How do I fix this?? Any idea?

There is no working TWRP yet for Android 11. You'll need to flash the stock boot.img or rooted boot.img from one of the threads in the news, guides section.
Edit: TWRP screen flashing is because it's incompatible. I had the same issue on the open betas.

Have the exact same issue as above, Twrp screen flashing, cannot boot back to normal even with adb... anybody has a rooted boot.img link that knows works with Android 11?
Should have checked on xda first *slaps his face*
Always check xda first *slaps his face again*
EDIT: For other poor saps with this issue use this -> https://www.androidfilehost.com/?fid=2188818919693770594 I didnt managed to get booted with rooted img but the original boot img file worked well ... at least I got a phone now...

im on 10.3.8 and rooted..
can i just do the same old process.. twrp isnt an issue as long as may apps are safe and root..

santiagoruel13 said:
im on 10.3.8 and rooted..
can i just do the same old process.. twrp isnt an issue as long as may apps are safe and root..
Click to expand...
Click to collapse
No, its not the same process.... For me for example I couldnt get wifi to actually work on rooted image AND you lose the ability to do backups via TWRP..... Refer here for the latest on this: https://forum.xda-developers.com/t/...p-recovery-for-oneplus-7-pro.3931322/page-153

dejjem said:
No, its not the same process.... For me for example I couldnt get wifi to actually work on rooted image AND you lose the ability to do backups via TWRP..... Refer here for the latest on this: https://forum.xda-developers.com/t/...p-recovery-for-oneplus-7-pro.3931322/page-153
Click to expand...
Click to collapse
I mean.. same steps.. that ive used so far amd retain its root.
1. Download rom via o2 updater
2. Flash it via local update
3. Install magisk to inactive slot
4. Reboot.
So if i do this.. wifi wont work??? Is that it???
Finished updating my phone..after downloading it for about 2 hours.
And im quite satisfied with the results. No problems whatsoever..

Glad for you... You probably had already removed the encryption on your mobile... from what I'm reading that is the main incompatibility issue with TWRP...
FWIW after playing around for a day, I had to revert everything Phone wifi was weird (weirder with root and all mods disabled) and system was a little unstable in some 3p apps and there seems to be some bugs with the phone screen 60/90 refresh... Gonna wait a bit to update again.

dejjem said:
Glad for you... You probably had already removed the encryption on your mobile... from what I'm reading that is the main incompatibility issue with TWRP...
FWIW after playing around for a day, I had to revert everything Phone wifi was weird (weirder with root and all mods disabled) and system was a little unstable in some 3p apps and there seems to be some bugs with the phone screen 60/90 refresh... Gonna wait a bit to update again.
Click to expand...
Click to collapse
i dont mind not having TWRP for the meantime,, i just used TWRP previously for flashing CUSTOM kernels.. hehehehe.
anyways, what problem have you encountered regarding wifi?? i dont seem to experience those,, maybe because i came from stable oos 10.3.8..
what app crashed and problems have you encountered???

[Root] Stuck in Boot loop after taking OTA

Hi everyone, I could really use some help. My KB2005 is stuck in what looks like a boot loop. I took an OTA update after going into magisk and restoring images. After the update finished installing and before rebooting, I installed magisk to the inactive slot. Now when my phone boots up, it is stuck on the spinning circle boot up logo. It stays there, screen goes black, then maybe 30 seconds later I see the boot logo again.
I used MSM download to restore my phone to stock. Re rooted + safetynetfix, attempted to take the OTA update using the procedure above, and the same result happened (boot loop).
I then used the fastboot method to unbrick. Re rooted + safetynet fix, attempted to take OTA update using the procedure above, and again the same thing happened.
My phone will successfully take an OTA and not boot loop if I'm not rooted.
I could root + safetynet fix after taking the OTA, but the next time an update comes along, I'd like to be confident that using the magisk method to install the OTA will work.
Any help would be greatly appreciated. If there is any other information I can provide that can help please let me know. Cheers
EDIT - I did some digging - according to getvar all, my slot b is not 'successful'. To confirm, I force booted slot b and get a qualcomm crush dump screen.

behel1t said:
Hi everyone, I could really use some help. My KB2005 is stuck in what looks like a boot loop. I took an OTA update after going into magisk and restoring images. After the update finished installing and before rebooting, I installed magisk to the inactive slot. Now when my phone boots up, it is stuck on the spinning circle boot up logo. It stays there, screen goes black, then maybe 30 seconds later I see the boot logo again.
I used MSM download to restore my phone to stock. Re rooted + safetynetfix, attempted to take the OTA update using the procedure above, and the same result happened (boot loop).
I then used the fastboot method to unbrick. Re rooted + safetynet fix, attempted to take OTA update using the procedure above, and again the same thing happened.
My phone will successfully take an OTA and not boot loop if I'm not rooted.
I could root + safetynet fix after taking the OTA, but the next time an update comes along, I'd like to be confident that using the magisk method to install the OTA will work.
Any help would be greatly appreciated. If there is any other information I can provide that can help please let me know. Cheers
EDIT - I did some digging - according to getvar all, my slot b is not 'successful'. To confirm, I force booted slot b and get a qualcomm crush dump screen.
Click to expand...
Click to collapse
After you used magisk to flash to the inactive slot, did you disable all of the modules before rebooting? That might help. And you are not using twrp correct?

azoller1 said:
After you used magisk to flash to the inactive slot, did you disable all of the modules before rebooting? That might help. And you are not using twrp correct?
Click to expand...
Click to collapse
Hi, correct I am not using twrp. I tried unlocking the boot loader and not rooting. Receiving an OTA works and I can reboot. But oddly enough if I do a --set-active=otherslot, i get a qualcomm crashdump.
It appears that whenever I or magisk force change the active slot, I get a crash dump.
EDIT - Still unsuccessful. I've tried numerous times using MSM Download and the fastboot unbrick method by coomac. I haven't been able to --set-active=b a single time, it always ends up in a qualcomm crash dump. I suspect slot is B is corrupt.

Try to restore both slots with an older version of rom using local update. Then take ota and try.

kjslabber said:
Try to restore both slots with an older version of rom using local update. Then take ota and try.
Click to expand...
Click to collapse
I'd like to give this a shot but I have a couple of follow up questions: does an older version of the rom restore both slots vs newer versions just containing one slot? Or if I have that wrong, how do I flash both slots from local upgrade?

behel1t said:
I'd like to give this a shot but I have a couple of follow up questions: does an older version of the rom restore both slots vs newer versions just containing one slot? Or if I have that wrong, how do I flash both slots from local upgrade?
Click to expand...
Click to collapse
Install rom to first slot, boot system and do local update again and reboot. That will put same version on both slots. Then take the regular update to current new version. You do know how to do local updates don't you?

kjslabber said:
Install rom to first slot, boot system and do local update again and reboot. That will put same version on both slots. Then take the regular update to current new version. You do know how to do local updates don't you?
Click to expand...
Click to collapse
Thanks for the reply. I do yes. I'll give this method a shot. Cheers
UPDATE - Just finished using msm download to restore OOS 11.0.5.6 and then used local upgrade to flash OnePlus8TOxygen_15.O.20_GLO_0200_2011132216 (both 11.0.5.6). I can now successfully boot both slots!
Now I am going to root. install riru and safetynet fix in magisk.
When I am ready to take an OTA, the correct process would be to uninstall the safetynet fix and riru. Then uninstall magisk using restore images, download and install OTA but do not reboot. Go into magisk and install to other slot. Then providing a successfully boot, reinstall safetynet and riru. Is this correct?
UPDATE 2 - Qualcomm crashdump happened after taking an OTA using the method I outlined above. So I reverted back to the previous slot and am in the process of doing a local upgrade again using 11.0.5.6 to hopefully restore that slot to working.

Something about magisk installing to the other slot and forcing a slot change is causing this crash dump.
I had 11.0.5.6 on both slots. I rooted. I then completely unrooted (not restore images). Took an update. That booted. I booted that. Rooted it. Then for testing, completely unrooted again. Then I received the latest OTA. That installed and booted. So I'm rooting now on the latest getting ready for daily use.
I have no idea why using magisk to install root to the other slot and forcing a slot change is not working. I'm grateful that, with extra steps, i can at least reliably receive OTAs and continue on living rooted life.

So, right after the ota is finished installing, before rebooting, you go to magisk and install to inactive slot, then you reboot immediately correct?

azoller1 said:
So, right after the ota is finished installing, before rebooting, you go to magisk and install to inactive slot, then you reboot immediately correct?
Click to expand...
Click to collapse
Yup. Doing exactly that results in a Qualcomm crash dump every single time.
Only way for me to bypass the crash dump is to completely uninstall magisk. I take the OTA and reboot losing root. I use twrp to dump updated boot partition, and reinstall magisk to patch the boot dump. Then fastboot flash the new rooted boot dump.

behel1t said:
Yup. Doing exactly that results in a Qualcomm crash dump every single time.
Only way for me to bypass the crash dump is to completely uninstall magisk. I take the OTA and reboot losing root. I use twrp to dump updated boot partition, and reinstall magisk to patch the boot dump. Then fastboot flash the new rooted boot dump.
Click to expand...
Click to collapse
Well, that's really weird. Have you tried magisk-canary? Or are you using the stable v23?

azoller1 said:
Well, that's really weird. Have you tried magisk-canary? Or are you using the stable v23?
Click to expand...
Click to collapse
I'm on v23, I haven't tried Canary.
This used to work on v23, the Qualcomm crash dump just started four days ago. What happened? In early September, I started failing safetynet out of the blue. Safetynetfix was not working so I followed the steps that are now crossed out (they were not then) at the following link. About a week after following those steps, I revisited the site to find that a new safetynetfix was released that worked. It didn't need LSposed or Xprivacylua. I went into Xprivacylua and reversed the changes i made, and uninstalled it and Lsposed. Then I applied the new safetynetfix. Immediately upon reboot, my finger print sensor started say 'finger print hardware failure' on the lock screen, and I was unable to enroll any new fingerprints; I would get a popup error saying enrollment failed.
At this point I decided to restore my phone using an unbrick method for a couple of reasons: 1) I wanted my finger print scanner to work, 2) I wanted to start fresh on my phone for a few months, and 3) I used to unbrick my phone to restore to factory all the time when I messed around with my OP5T. This is when the Qualcomm crash dumps started happening every time when Magisk installs to the other slot. I've used the MSM download linked on this forum and the fastboot unbrick method. I Qualcomm crash every time magisk installs to the other slot and switches slots.

behel1t said:
I'm on v23, I haven't tried Canary.
This used to work on v23, the Qualcomm crash dump just started four days ago. What happened? In early September, I started failing safetynet out of the blue. Safetynetfix was not working so I followed the steps that are now crossed out (they were not then) at the following link. About a week after following those steps, I revisited the site to find that a new safetynetfix was released that worked. It didn't need LSposed or Xprivacylua. I went into Xprivacylua and reversed the changes i made, and uninstalled it and Lsposed. Then I applied the new safetynetfix. Immediately upon reboot, my finger print sensor started say 'finger print hardware failure' on the lock screen, and I was unable to enroll any new fingerprints; I would get a popup error saying enrollment failed.
At this point I decided to restore my phone using an unbrick method for a couple of reasons: 1) I wanted my finger print scanner to work, 2) I wanted to start fresh on my phone for a few months, and 3) I used to unbrick my phone to restore to factory all the time when I messed around with my OP5T. This is when the Qualcomm crash dumps started happening every time when Magisk installs to the other slot. I've used the MSM download linked on this forum and the fastboot unbrick method. I Qualcomm crash every time magisk installs to the other slot and switches slots.
Click to expand...
Click to collapse
Sorry, at this point I don't know why it isn't working. You seem to be doing everything correctly so I am not sure why it's not working properly. The only thing I could think of that might be the issue is, as far as I know, that Oneplus hasn't pushed a september update yet to merge the september security patch which could be the culprit, but I cant say for certain. I know for me, I use Sakura ROM, SafetyNet was failing early september when android had pushed the september patch, but Sakura ROM hadnt merged it yet, but when they did merge it everything was working fine. Anyways, hopefully someone else may be able to give you a better answer.
EDIT: It seems the latest OOS incremental update is breaking when trying to upgrade while rooted. You need to use the full ota zip and do local manual upgrade. See the last couple of posts in here: https://forum.xda-developers.com/t/oneplus-8t-rom-ota-oxygen-os-repo-of-oxygen-os-builds.4193183/

azoller1 said:
Sorry, at this point I don't know why it isn't working. You seem to be doing everything correctly so I am not sure why it's not working properly. The only thing I could think of that might be the issue is, as far as I know, that Oneplus hasn't pushed a september update yet to merge the september security patch which could be the culprit, but I cant say for certain. I know for me, I use Sakura ROM, SafetyNet was failing early september when android had pushed the september patch, but Sakura ROM hadnt merged it yet, but when they did merge it everything was working fine. Anyways, hopefully someone else may be able to give you a better answer.
EDIT: It seems the latest OOS incremental update is breaking when trying to upgrade while rooted. You need to use the full ota zip and do local manual upgrade. See the last couple of posts in here: https://forum.xda-developers.com/t/oneplus-8t-rom-ota-oxygen-os-repo-of-oxygen-os-builds.4193183/
Click to expand...
Click to collapse
Thanks for bringing this to my attention. This is definitely what is happening. You just just saved me from spending any more time on this mess. Cheers!

I just wanted to add that I had same problem with my OP8T and couldn't reflash the ROM and had to send my phone to OP to get the ROM put back on. Slot B still doesn't work. You at least were able to get the phone back working with MSN.

Question Solved - C.44 update won't install after magisk boot

Hi guys,
Sorry if I'm missing something very obvious but I can't install the latest update on my rooted oneplus 9
I have a LE2110 model, currently on 11.2.10.10..LE25BA. I'm rooted with magisk, confirmed with root checker.
I've downloaded the C44 update, went to updater, install from storage, then to magisk where I disable all my modules and select install to inactive slot, 'lets go' and 'reboot'.
The phone reboots and displays a message saying that the update did not install try again or try reapir.
Anyone know if I'm missing anything in the process? Any help would be appreciated.
Cheers everyone
Edit: Thanks for all the responses..using canary magisk instead has worked.

chinbags said:
Hi guys,
Sorry if I'm missing something very obvious but I can't install the latest update on my rooted oneplus 9
I have a LE2110 model, currently on 11.2.10.10..LE25BA. I'm rooted with magisk, confirmed with root checker.
I've downloaded the C44 update, went to updater, install from storage, then to magisk where I disable all my modules and select install to inactive slot, 'lets go' and 'reboot'.
The phone reboots and displays a message saying that the update did not install try again or try reapir.
Anyone know if I'm missing anything in the process? Any help would be appreciated.
Cheers everyone
Click to expand...
Click to collapse
You have to fastboot flash the stock untouched boot.img back. Magisk patched the boot partition to root. Therefore the partition is modified. Ota fails. Try uninstall Magisk and see if it restores stock boot image. Or get full build run payload him through payload extractor and nab boot.img there.

Thanks, so I basically need to unroot, restore to stock, update to C44, then reroot from scratch again?

chinbags said:
Thanks, so I basically need to unroot, restore to stock, update to C44, then reroot from scratch again?
Click to expand...
Click to collapse
Wrong magisk was used. You must use canary magisk.

MrSteelX said:
Wrong magisk was used. You must use canary magisk.
Click to expand...
Click to collapse
Wrong . I'm on stock A12 and it's rooted with 23.0. passing safety net,modules,Magisk hide all working

in order for magisk to work on A12 and booting to an inactive slot it has to be the alpha build ill post it but its also in the root guide for oos on 12 the table shows the only one that works on 12 is this build, same thing happened to me

chinbags said:
Thanks, so I basically need to unroot, restore to stock, update to C44, then reroot from scratch again?
Click to expand...
Click to collapse
no need for any of that

mattie_49 said:
Wrong . I'm on stock A12 and it's rooted with 23.0. passing safety net,modules,Magisk hide all working
Click to expand...
Click to collapse
yes it is true but you did the manual way. every one else wants the automatic way which requires canary or alpha.

MrSteelX said:
yes it is true but you did the manual way. every one else wants the automatic way which requires canary or alpha.
Click to expand...
Click to collapse
Everyone does want bleeding edge.

Thanks for all the info guys, sounds like a bit more reading needed on my end but all of the above should steer me in the right direction.

I was able to jump from rooted 11.10.10 to c44 using canary magisk.
Downloaded the 4gb c44 from oxygen updater, then local udpate and DONT reboot then install magisk in inactive slot.

Ok, this has worked, original posted uodated, thanks everyone.

One last question...and slightly unrelated. I can't find my list of hidden apps in magisk. I've hidden the app in settings and have the magisk hideprops config module enabled. My banking app is telling me I'm rooted...I'm pretty sure I added it to a list in the past. None of the options at the bottom bring me to it either..anyone have the same issue?

chinbags said:
One last question...and slightly unrelated. I can't find my list of hidden apps in magisk. I've hidden the app in settings and have the magisk hideprops config module enabled. My banking app is telling me I'm rooted...I'm pretty sure I added it to a list in the past. None of the options at the bottom bring me to it either..anyone have the same issue?
Click to expand...
Click to collapse
the alpha build doesnt have magisk hide built in. and he literally just posted the updated v24 stable build an hour ago and is supposed to fully support android 12. but he also announced that he removed Magisk hide all together and is no longer going to support it.
so its still early, not sure how to fix your problem , those are the only two builds i see for 12

jruizdesign said:
the alpha build doesnt have magisk hide built in. and he literally just posted the updated v24 stable build an hour ago and is supposed to fully support android 12. but he also announced that he removed Magisk hide all together and is no longer going to support it.
so its still early, not sure how to fix your problem , those are the only two builds i see for 12
Click to expand...
Click to collapse
Ok, thanks. Could a rollback to v23 APK work? Happy to give it a whirl unless you think it could bork my phone

chinbags said:
Ok, thanks. Could a rollback to v23 APK work? Happy to give it a whirl unless you think it could bork my phone
Click to expand...
Click to collapse
i would try and delete the version you have and install stable 23, dont repack the boot.img or anything only replace the app, that wont hurt you

jruizdesign said:
i would try and delete the version you have and install stable 23, dont repack the boot.img or anything only replace the app, that wont hurt you
Click to expand...
Click to collapse
No dice, v23 will install and the option is available in settings, I just still can't find where I add an app to the hidden list. Bank apps not loading.

Magisk is dropping support for hiding root access from apps
Magisk, the popular Android rooting tool, will continue to be developed by topjohnwu, but without its root hiding feature called MagiskHide.
www.xda-developers.com

Have you tried using USNF? https://forum.xda-developers.com/t/magisk-module-universal-safetynet-fix-1-1-0.4217823/
I'm also having troubles updating to c44 with magisk v23, but don't wanna lose the magisk hide option. While looking for alternatives, I came across this the USNF solution in here :
How to pass SafetyNet on Android after rooting or installing a custom ROM
It is possible to pass SafetyNet, even after extensive modding like rooting or installing a custom ROM. Check out how to do that here!
www.xda-developers.com
Didn't try it myself yet...

I can confirm USNF works for me, and I have some very strict apps detecting root access, DenyList hides the root from the apps, but it doesn't try to fix safetynet, with USNF I have no more problems even in apps that didn't work with DenyList only (remember to turn on Zygisk and Enforced DenyList).
If you are using permissive mode on SELinux you will also need SELinux switch to get back to enforcing mode for some apps, but that is an edge case
EDIT: It seems if you are on custom ROM MagiskHidePropsConf might help, not sure if USNF is enough but I can't test it