The last System Update notification received was the Update from Android 11 to Android 12. It installed fine. Can keep up via sideload or a full manual flash, but why no notification of updates?
Are you bootloader unlocked and/or rooted?
I have never received an OTA notice or been able to do OTAs but I rooted as soon as I got my pixel 4a.
There was one update that was offered but it was strange, and was the first and only time a separate AU firmware was made.
My children have pixel 4as and get OTAs just fine.
a1291762 said:
Are you bootloader unlocked and/or rooted?
I have never received an OTA notice or been able to do OTAs but I rooted as soon as I got my pixel 4a
Click to expand...
Click to collapse
Bootloader unlocked and rooted from Day 1. I was notified of the update from A11 to A12 and was able to use the system OTA. Otherwise I have sideloaded or flashed the Factory Image.
Even with auto update off in Dev Options, all I read says one shiuld still receive notification of the OTA. Guess I'll contune to sideload
a1291762 said:
Are you bootloader unlocked and/or rooted?
I have never received an OTA notice or been able to do OTAs but I rooted as soon as I got my pixel 4a.
There was one update that was offered but it was strange, and was the first and only time a separate AU firmware was made.
My children have pixel 4as and get OTAs just fine.
Click to expand...
Click to collapse
How long after update release (usually 5th of the month or so) do they see their 4a updates?
I have a 4a, rooted and unlocked. When new updates come out (I check the https://developers.google.com/android/ota page), I just uninstall magisk from the phone, run the system update, then re-install magisk and re-root. I believe it was Monday night April 3 when I did it last. If you don;t mind the hassle of all the reboots, I find it an easy enough way to keep updated and rooted.
amphi66 said:
How long after update release (usually 5th of the month or so) do they see their 4a updates?
Click to expand...
Click to collapse
It can vary a little (I think sometimes google stages the roll out?), but it's normally pretty soon after. The April update was already offered and installed.
augggg said:
I just uninstall magisk from the phone, run the system update, then re-install magisk and re-root.
Click to expand...
Click to collapse
How do you get the new boot image for rooting after doing the OTA?
a1291762 said:
How do you get the new boot image for rooting after doing the OTA?
Click to expand...
Click to collapse
I do it by extracting/Magisk patching the boot.img from the Factory Image. Of course I had to sideload the OTA as it didn't show up in System updates.
a1291762 said:
How do you get the new boot image for rooting after doing the OTA?
Click to expand...
Click to collapse
For 4a, go to the latest factory image here, which is at the bottom of each phone's list of images: https://developers.google.com/android/images#sunfish
Download the factory image, then unzip the file. Go into the folder you get, then unzip the next zip file you see (starts with image-sunfish*), and look for the boot.img file. Should be 64mb
Thanks @augggg and @amphi66.
I use the factory image to upgrade each month. But since I have to download it, I see no value in doing an on-device OTA (ie. Uninstall Magisk, reboot, OTA, etc.)
@augggg mentioned uninstalling Magisk to OTA so I wondered if they had an alternative way of getting the boot image besides downloading the factory image or full OTA (which is a bit harder to unpack, but also includes the whole boot.img).
I suppose one could boot TWRP to extract the new boot.img from the phone and then use Magisk to patch that... But I feel like it'd end up being a lot more work than the few changed lines it takes to flash the factory image, and my download speeds aren't bad enough to make that faster
Since I have to download the full factory image inorder to patch the boot.img, I use the factory image to update as well.
But I would like to know the status of the technique to "uninstall-restore Images" in Magisk, not reboot, update via OTA, not reboot, "install to inactive slot" in Magisk, then finally reboot.
For me, an OTA system update is never found.
lbush said:
Since I have to download the full factory image inorder to patch the boot.img, I use the factory image to update as well.
But I would like to know the status of the technique to "uninstall-restore Images" in Magisk, not reboot, update via OTA, not reboot, "install to inactive slot" in Magisk, then finally reboot.
For me, an OTA system update is never found.
Click to expand...
Click to collapse
Exactly. Worked for me once, but have not seen an OTA nofication since
Just a May followup. 10 days w/ innumerable System Update checks and still have not seen the auto-rollout of the May OTA Update. Yes, I can certainly sideload OTA or flash the (already downloaded) Factory Image, but is this a typical delay? I was thinking 2 or 3 days after release. Thanks.
amphi66 said:
Just a May followup. 10 days w/ innumerable System Update checks and still have not seen the auto-rollout of the May OTA Update. Yes, I can certainly sideload OTA or flash the (already downloaded) Factory Image, but is this a typical delay? I was thinking 2 or 3 days after release. Thanks.
Click to expand...
Click to collapse
Gave up & sideloaded May OTA, followed by flashing the Magisk-patched boot.img to retain root. Still do not know why there was no OTA notification
Related
Hey folks,
I just got the notification for a system update. TW Model, currently in Germany. However, I tried capturing the ota link for patching the boot.img, but it gives me an error. Anyone with more luck than me?
Greetings
Update:
I managed to get the OTA.zip off my phone, but the update itself fails at 24%. Restored stock boot.img before of course. Has someone already installed it?
Hong Kong variant still on 1.24.400.03, December 2017 security update [emoji23][emoji23][emoji23]
Sent from my HTC U11 plus using Tapatalk
September 2018 security on latest 1.24.709.93... Can't remember before that... And I couldn't spot any difference between the two, does anybody see anything new?
Inviato dal mio HTC_2Q4D100 utilizzando Tapatalk
I've got it too on my TW model in the Netherlands.
Besides the security patch going from June 1 to September 1 I don't see anything different yet. Then again, there weren't any bugs I'm aware of, that needed fixing. 700MB+ seems like a lot for 3 months of security patches though.
It's nice to get an update and be less behind in security patch date again.
Thanks, HTC!
U11+ from Europe...
Didn't get the june security patch, didn't get this one either...
Tw version in Malaysia. Already updated. Everything okay. Doesn't explore much because going to work. only feel different at the display color. Looked better
UK version, no update available so far and still on 1 December 2017 security patch. I'd settle for them fixing the notification issue.
Sent from my HTC U11 plus using Tapatalk
Some findings
Battery before i go to work, 75%, on airplane mode.
Come back home after 11 hours, 75%
Soooo happy.....
Hmm.... maybe I need to learn how to roll back to stock now
Received today in Belgium with TW version of the phone!
gortys said:
Received today in Belgium with TW version of the phone!
Click to expand...
Click to collapse
Very important question:
Where/in which precise folder is the OTA update saved in HTC U11+ after downloading (I cannot find it...)
Thx a lot!
marusia7 said:
Very important question:
Where/in which precise folder is the OTA update saved in HTC U11+ after downloading (I cannot find it...)
Thx a lot!
Click to expand...
Click to collapse
Ow, sorry, I don't know at all!
gortys said:
Ow, sorry, I don't know at all!
Click to expand...
Click to collapse
found it in root folder:
data/data/com.htc.updater/files/
lillypad_33 said:
Hmm.... maybe I need to learn how to roll back to stock now
Click to expand...
Click to collapse
did you manage to update?
same situation here: although I flashed back to original boot.img (included in the last OTA update end of July 2018 which was later patched by Magisk), the update stucks at 24% with red error. Luckily the phone boots normally without applied update.
Anybody any idea how to proceed? I already tried to flash back the original boot.img from the stock RUU and also to use the boot.img provided in the latest OTA: with both boot.img (although both have very same size) the phone stucks at HTC logo but does not continue to boot.
Currently the HTC U11+ boots only from the boot.img provided with 709.8 OTA, (also booting with the patched_boot.img done by Magisk derived from the same).
I am a bit stuck here: Magisk should not touch the system (so no idea why the OTA stops at 24%) and only 1 out of 3 boot images are working (although all with same size), so currently I am not able to apply the OTA update...
I have read that for OTA updates the integrity (?) of the recovery.img is important ( (although Magisk should also not touch the recovery.img (?)
Any ideas?
best regards, Marusia
Looks like htc forgot people are still buying their phones outside Taiwan, or they don't have enough money to hire a translator!! I am an old loyal customer for 8 years, but here they are doing everything to let us get another brand, it's like they stabbed themselves and slowly turning the knife to feel more pain
marusia7 said:
did you manage to update?
same situation here: although I flashed back to original boot.img (included in the last OTA update end of July 2018 which was later patched by Magisk), the update stucks at 24% with red error. Luckily the phone boots normally without applied update.
Anybody any idea how to proceed? I already tried to flash back the original boot.img from the stock RUU and also to use the boot.img provided in the latest OTA: with both boot.img (although both have very same size) the phone stucks at HTC logo but does not continue to boot.
Currently the HTC U11+ boots only from the boot.img provided with 709.8 OTA, (also booting with the patched_boot.img done by Magisk derived from the same).
I am a bit stuck here: Magisk should not touch the system (so no idea why the OTA stops at 24%) and only 1 out of 3 boot images are working (although all with same size), so currently I am not able to apply the OTA update...
I have read that for OTA updates the integrity (?) of the recovery.img is important ( (although Magisk should also not touch the recovery.img (?)
Any ideas?
best regards, Marusia
Click to expand...
Click to collapse
I also flashed the recovery.img from the latest OTA, but still the red triangle.
Is it possible to flash the whole OTA via fastboot? Maybe thats a possibility.
metaxuss said:
I also flashed the recovery.img from the latest OTA, but still the red triangle.
Is it possible to flash the whole OTA via fastboot? Maybe thats a possibility.
Click to expand...
Click to collapse
I also flashed latest OTA recovery,same result...
I guess the only way is to flash back to stock RUU (which will lead to unrooted phone), install latest OTA via WLAN, then unlock bootloader (via HTCdev website) and root again with Magisk. I never did RUU flashing, so currently backing up everything with Titanium, if I proceed I will let you know the result...
Flashing the latest OTA might brick the phone (the red triangle already indicates that something went seriously wrong, although I have no clue what it could be: never touched the system, Magisk only patches the boot.img), instructions should be in the forum.
Tried another thing: disabling the systemless Xposed (installed via Magisk), reboot, restoring boot.img via Magisk, OTA download & trying to install --> red triangle...
I cannot remember if I disabled Xposed before the last OTA update few months ago. I had there some issues too (after successful OTA install the phone stuck at boot so I had to reflash the OTA-boot.img again via fastboot), maybe this procedure broke the possibility to install current OTA.
Will maybe try to flash selectively restored stock RUU images (without applying first the whole stock RUU) on the weekend (I have been informed by PM that this procedure should be harmless), so reverting to whole stock RUU is still not the last option.
I downloaded OTA from the following link and flash "system.img" with fastboot command. I am now on 1.24.709.93
https://drive.google.com/drive/folders/1wccnIY0NaoelhZQS4uhgP8ZGIn1iXhNX
Link Credit to : nene bear
kenosis said:
I downloaded OTA from the following link and flash "system.img" with fastboot command. I am now on 1.24.709.93
https://drive.google.com/drive/folders/1wccnIY0NaoelhZQS4uhgP8ZGIn1iXhNX
Link Credit to : nene bear
Click to expand...
Click to collapse
These OTA files dont contain system.img (the system.img file should be >4Gb).
1) Did you experience also OTA update issue (red triangle) as described in this thread?
2) Just to clarify: you flashed 1st the system.img derived from the stock RUU and afterwards applied the 709.93 OTA update?
My phone keeps bugging me to upgrade to Android 10. I have systemless root, magisk etc.
Is this safe to just do? Do I need to get the image from elsewhere and start over? I've had an update alert come through from Magisk announcing Android 10 compatibility, so I'm guessing that won't be an issue...
I really only wander in here whenever I get a new phone so I have no clue how this works.
you can update to android 10 just fine with magisk installed, however you will lose it once the upgrade is done. you will need to patch your boot image with magisk once you are on android 10.
Not sure what that means.
koberulz said:
Not sure what that means.
Click to expand...
Click to collapse
You. Will. Need. To. Patch. Your. Boot. Image. With. Magisk. After. You. Update. To. Android. 10.
I can read, dude.
What's a boot image? How do I patch it? What are the actual steps here?
koberulz said:
I can read, dude.
What's a boot image? How do I patch it? What are the actual steps here?
Click to expand...
Click to collapse
https://forum.xda-developers.com/pixel-xl/how-to/guide-pixel-xl-android-10-0-q-t3964112
So start the root process over, basically? Is there any point in doing the OTA update or do I just grab the latest image from the website?
Steps 7/8 say there's no TWRP for Android 10 yet, so how does that work?
koberulz said:
So start the root process over, basically? Is there any point in doing the OTA update or do I just grab the latest image from the website?
Steps 7/8 say there's no TWRP for Android 10 yet, so how does that work?
Click to expand...
Click to collapse
you can not install twrp on android 10, you can still boot twrp though. you will not need twrp for the boot image patch.
update your phone to android 10, get the boot.img from the factory image of the version you updated to, using magisk manager patch that boot.img, boot to bootloader, flash the patched boot.img with
Code:
fastboot flash boot_a patchedboot.img
and
Code:
fastboot flash boot_b patchedboot.img
(or only flash for the boot of the current slot you are on, doesnt really matter)
Personally, on every monthly update I always flash the full factory image (deleting -w if I want to keep my stuff) and then reinstall Magisk and custom kernel by temporarily booting TWRP. I find it much less of a hassle, it applies to major upgrades too (as is your case) and it's guaranteed to work every time.
Flipz77 said:
Personally, on every monthly update I always flash the full factory image (deleting -w if I want to keep my stuff) and then reinstall Magisk and custom kernel by temporarily booting TWRP. I find it much less of a hassle, it applies to major upgrades too (as is your case) and it's guaranteed to work every time.
Click to expand...
Click to collapse
i usually do this also
Flipz77 said:
Personally, on every monthly update I always flash the full factory image (deleting -w if I want to keep my stuff) and then reinstall Magisk and custom kernel by temporarily booting TWRP. I find it much less of a hassle, it applies to major upgrades too (as is your case) and it's guaranteed to work every time.
Click to expand...
Click to collapse
There are monthly updates?
I've not been aware of anything at all until now, because now it's sending me a notification.
koberulz said:
There are monthly updates?
I've not been aware of anything at all until now, because now it's sending me a notification.
Click to expand...
Click to collapse
December will be the last one, sadly
2 months ago I decided to root my Pixel 3(to improve Camera Performance). While rooting I mistakenly download Factory Image of Pixel3 XL(crosshatch) and patch it with magisk after that phone went into boot loop . After some period of time I recognized my childish mistake and downloaded the latest factory image for pixel 3(blueline) first flash the stock image to get phone out of boot loop after then I rooted without any problem. But since that day I am not being able to receive any OTA updates for my device, is it because I removed the stock OS and flashed Factory Image of my own , and also If i want to sideload OTA updates with magisk what are the procedure for that.
P.S Thanks in Advance....much needed help
Rahul_Yf said:
2 months ago I decided to root my Pixel 3(to improve Camera Performance). While rooting I mistakenly download Factory Image of Pixel3 XL(crosshatch) and patch it with magisk after that phone went into boot loop . After some period of time I recognized my childish mistake and downloaded the latest factory image for pixel 3(blueline) first flash the stock image to get phone out of boot loop after then I rooted without any problem. But since that day I am not being able to receive any OTA updates for my device, is it because I removed the stock OS and flashed Factory Image of my own , and also If i want to sideload OTA updates with magisk what are the procedure for that.
P.S Thanks in Advance....much needed help
Click to expand...
Click to collapse
If you're rooted you can't take an ota directly. But follow this guide and you can get the ota, apply it, and root again. Pay attention to when you can reboot. https://topjohnwu.github.io/Magisk/tutorials.html
Rahul_Yf said:
2 months ago I decided to root my Pixel 3(to improve Camera Performance). While rooting I mistakenly download Factory Image of Pixel3 XL(crosshatch) and patch it with magisk after that phone went into boot loop . After some period of time I recognized my childish mistake and downloaded the latest factory image for pixel 3(blueline) first flash the stock image to get phone out of boot loop after then I rooted without any problem. But since that day I am not being able to receive any OTA updates for my device, is it because I removed the stock OS and flashed Factory Image of my own , and also If i want to sideload OTA updates with magisk what are the procedure for that.
P.S Thanks in Advance....much needed help
Click to expand...
Click to collapse
That was discussed in several posts here recently: https://forum.xda-developers.com/app...32382/page3857
Apparently it has been going on for 3 years now. Some people are impacted, others are not. Luckily, I have not been impacted so far.
You can sideload the OTA. Instructions are at https://developers.google.com/android/ota You must re-root after sideloading.
Hi,
Same problem here.
But the link https://topjohnwu.github.io/Magisk/tutorials.html doesn't work, neither this one : https://forum.xda-developers.com/app...32382/page3857
Can someone tell me how make the OTA update ?
Thanks
Nik0LaAs said:
Hi,
Same problem here.
But the link https://topjohnwu.github.io/Magisk/tutorials.html doesn't work, neither this one : https://forum.xda-developers.com/app...32382/page3857
Can someone tell me how make the OTA update ?
Thanks
Click to expand...
Click to collapse
The new link is https://topjohnwu.github.io/Magisk/
The Magisk forum on XDA has shutdown. Use Github instead.
dcarvil said:
The new link is https://topjohnwu.github.io/Magisk/
The Magisk forum on XDA has shutdown. Use Github instead.
Click to expand...
Click to collapse
Thanks for the link.
But if I follow the guide, it says:
After restoring stock images, apply OTAs as you normally would (Settings → System → System Update).
But the problem is my phone doesn't receive OTA updates
I'm stuck in November security update, and my phone doesn't see any update. So what can I do ?
Nik0LaAs said:
Thanks for the link.
But if I follow the guide, it says:
After restoring stock images, apply OTAs as you normally would (Settings → System → System Update).
But the problem is my phone doesn't receive OTA updates
I'm stuck in November security update, and my phone doesn't see any update. So what can I do ?
Click to expand...
Click to collapse
I don't get update notifications, but I see the update when I do Settings → System → System Update. If you don't even see them, you'll have to download the image from https://developers.google.com/android/ota, then sideload it and reroot. You may be able to patch the downloaded image before sideloading, but that opens the door for more potential problems. I wouldn't recommend it.
dcarvil said:
I don't get update notifications, but I see the update when I do Settings → System → System Update. If you don't even see them, you'll have to download the image from https://developers.google.com/android/ota, then sideload it and reroot. You may be able to patch the downloaded image before sideloading, but that opens the door for more potential problems. I wouldn't recommend it.
Click to expand...
Click to collapse
Unfortunately, when I do Settings → System → System Update, my phone doesn't see any update. It stucks in November
So I cannot keep my root ? There is no other way to update ?
Nik0LaAs said:
Unfortunately, when I do Settings → System → System Update, my phone doesn't see any update. It stucks in November
So I cannot keep my root ? There is no other way to update ?
Click to expand...
Click to collapse
No other way to my knowledge. You can re-root after the update.
Hi,
After installing Magisk i no longer receive OTA Updates. The safety net checks are ok. How can i fix this?
Thanks.
+1
Sent from my Pixel 3 using Tapatalk
adrianppa said:
Hi,
After installing Magisk i no longer receive OTA Updates. The safety net checks are ok. How can i fix this?
Thanks.
Click to expand...
Click to collapse
AFAIK, your only choices are to sideload the OTA from https://developers.google.com/android/ota and re-root. You can also flash the factory image and re-root. Be sure to remove the -w from flash-all.bat/sh so you don't wipe your data. I prefer the factory image method. You can patch boot.img before flashing the image, which makes re-rooting a bit easier. I believe there have been some reports of OTA working again after flashing the factory image.
well you have root duh lol, off course otas will fail, at least they dont install unlike old times when install would be error
there are many ways to install but this is the easiest for me every month
each month download full system image
copy boot to phone and patch it with magisk apk, copy back to pc
apply full system image flash all.bat but remove the -w from the .bat (Edit the bat)
this will install the lastest ota but you wont lose any data or settings, everything well be okay
root is lost, now you have to root again
boot magisk boot image
apply direct install in magisk apk
restart
this has to be done every month
you can also uninstall magisk every month and let the ota download and install but that is even slower and annoying, this is how is done
I cant do normal OTA updates, nor can I install them with the built in installer in settings (that I gained with conversion). Im not exactly sure why and trying to figure this out. Were you able to update as normal to A13?
Its possible I broke something (cant think of what), so Im restoring my after-root twrp "base" backup to see if it can OTA.
Figured Id ask in the meantime...
TimmyP said:
I cant do normal OTA updates, nor can I install them with the built in installer in settings (that I gained with conversion). Im not exactly sure why and trying to figure this out. Were you able to update as normal to A13?
Its possible I broke something (cant think of what), so Im restoring my after-root twrp "base" backup to see if it can OTA.
Figured Id ask in the meantime...
Click to expand...
Click to collapse
You have to uninstall magisk/restore images. Then start ota. Then before you reboot go into magisk again and install to opposite slot and reboot . After ota has installed. Stock boot image is the only way it works. It's will fail upon checksum of partitions by google
I figured as I just went back to my base savior A11 rom fresh root, and still nothing. Thank you!
Uninstall magisk it automatically restores boot images right?
*Actually do I need stock boot? I have twrp. Where do I get stock boot image?
Im screwed. Its unable to restore my old image from usb, so Im bricked now. No idea what to do.
mattie_49 said:
You have to uninstall magisk/restore images. Then start ota. Then before you reboot go into magisk again and install to opposite slot and reboot . After ota has installed. Stock boot image is the only way it works. It's will fail upon checksum of partitions by google
Click to expand...
Click to collapse
Do you know how I can get back to stock boot?
NM found it. So to be sure, when i want to move from A11 I need to uninstall Magisk, boot to fastboot, then fastboot flash stock boot.img?
Here
^But I have twrp, so wont restoring just bring me to unlocked bootloader unrooted with twrp? (*still not stock?)
*Sorry for the questions. It just seems TWRP has problems restoring backup completely (or I missed something, I backed up everything in TWRP maybe I dont need to do that?).
Im trying to avoid what happened a couple nights ago, because I lost confidence in TWRP on this phone. Usually, its just something ****s up? Well restore your backup, because you just made one. That didn't work completely (it didn't restore /data), and I had to set up a ton I dont want to do again, unless Im on custom A13 rom. Got savegames!
Thanks for all help.
I was on android 12 with april 2022 security update, so it was a very very early android 12 build. I couldn't update via OTA cause I kept getting "update failed" I was rooted, had data I didn't wanna lose so I just ignored it.
I'm now on A13 with root. what I did was: MSM tool back to A11, update via OTA until I reach final official build, extract the boot file through msmtool, patched it with magisk, flashed it via fastboot, job done.
Couldnt Magisk patch boot image from app? Instead of extracting it? Thats how I did it on 11.
I also dont know how to use msm tool to get to 11, or even where to get files. *I think this is it? General - OnePlus 9 11.2.22.2 (T-Mobile) MSM Download Tool | XDA Forums
*Thats exactly whats happening to me too. update failed. So I guess this would be a sure fix.
pubmastervnt said:
I was on android 12 with april 2022 security update, so it was a very very early android 12 build. I couldn't update via OTA cause I kept getting "update failed" I was rooted, had data I didn't wanna lose so I just ignored it.
I'm now on A13 with root. what I did was: MSM tool back to A11, update via OTA until I reach final official build, extract the boot file through msmtool, patched it with magisk, flashed it via fastboot, job done.
Click to expand...
Click to collapse
Wait. How did you unlock bootloader (after MSM put your phone back to lock BL I assume)? Is the option later available on Tmobile roms? Did you need a token?
pubmastervnt said:
I was on android 12 with april 2022 security update, so it was a very very early android 12 build. I couldn't update via OTA cause I kept getting "update failed" I was rooted, had data I didn't wanna lose so I just ignored it.
I'm now on A13 with root. what I did was: MSM tool back to A11, update via OTA until I reach final official build, extract the boot file through msmtool, patched it with magisk, flashed it via fastboot, job done.
Click to expand...
Click to collapse
you get update failed bec. of the magisk image. you have to restore to stock image before you download the OTA. in magisk dashboard, go to uninstall magisk. choose RESTORE IMAGES. download the ota. do not reboot. go to magisk and install magisk. choose install Magisk after OTA (or something) then press Let's go. and reboot.
jmadiaga said:
you get update failed bec. of the magisk image. you have to restore to stock image before you download the OTA. in magisk dashboard, go to uninstall magisk. choose RESTORE IMAGES. download the ota. do not reboot. go to magisk and install magisk. choose install Magisk after OTA (or something) then press Let's go. and reboot.
Click to expand...
Click to collapse
Doesn't having twrp boot image installed mean that magisk restored twrp image to when before magisk patches it (so it's not actually stock)? Doesn't it just restore a non rooted image with twrp on it?
jmadiaga said:
you get update failed bec. of the magisk image. you have to restore to stock image before you download the OTA. in magisk dashboard, go to uninstall magisk. choose RESTORE IMAGES. download the ota. do not reboot. go to magisk and install magisk. choose install Magisk after OTA (or something) then press Let's go. and reboot.
Click to expand...
Click to collapse
This fails if you have TWRP.
pubmastervnt said:
I was on android 12 with april 2022 security update, so it was a very very early android 12 build. I couldn't update via OTA cause I kept getting "update failed" I was rooted, had data I didn't wanna lose so I just ignored it.
I'm now on A13 with root. what I did was: MSM tool back to A11, update via OTA until I reach final official build, extract the boot file through msmtool, patched it with magisk, flashed it via fastboot, job done.
Click to expand...
Click to collapse
Are you tmobile? How did you unlock BL on 13?