Database Info

Unlock/Root/TWRP OTA updates?

I've only had two phones prior to this but I have always unlocked the boot loader / rooted the device / installed a custom recovery / installed custom ROMS.
I believe with my MOTO X 1st gen this disabled the OTA updates.
Is that the case with the Honor 8? I'm wondering if it is worth it to install TWRP at this point as there seems to be so little in the way of kernels and ROMS.
Would I still be able to use SU or Xposed modules without Root?
What is the best move with this phone?

I have unlocked my bootloader as well as rooted my Honor 8. The only way to get SU and Xposed is by doing both of these procedures(root involves getting TWRP).
As for any Xposed modules, I tried amplify+greenify but instead of getting better battery life, my standby time decreased significantly. I am not sure why, but for some reason my Cell standby was showing to be eating a ton of my battery. Another big problem was that the dialer app would not let me call anyone, it kept crashing whenever I tried to. Both problems were fixed after I managed to get amplify+greenify uninstalled. Currently I am just running YouTube AdAway and MinMinGuard which seem to work fine.
So at this point, is it worth unlocking bootleader, installing TWRP, and rooting your phone? Well if there are certain Xposed modules that you really want then sure, and if there are certain apps you like that require root, then yes go ahead and root your phone. Note that if you try any OTA updates, you will have to remove TWRP as having your phone automatically restart and try to install the update wont work.

Imagine that the Honor 8 receives an update to say, Nougat, what is the pathway to update for someone who has rooted their phone. Will the OTA be able to be flashed if a .zip is provided here? Would we need to flash an entirely new ROM?
This is what I faced with my MOTO X. When Marshmallow came out there was talk... but no one was working on the at phone any longer so was never able to update.

pairustwo said:
Imagine that the Honor 8 receives an update to say, Nougat, what is the pathway to update for someone who has rooted their phone. Will the OTA be able to be flashed if a .zip is provided here? Would we need to flash an entirely new ROM?
This is what I faced with my MOTO X. When Marshmallow came out there was talk... but no one was working on the at phone any longer so was never able to update.
Click to expand...
Click to collapse
It doesnt matter whether or not your phone is rooted. You will get updates the same way, through OTA. Of course you can find .zip files to flash(although personally I am struggling to get the latest update flashed through TWRP).
The real question is for how long will we be receiving updates? Nougat is pretty much guaranteed with the new EMUI update. Huawei/Honor has promised up to 2 years of updates from what I have heard, but who knows what that actually means. They have also have a "partnership" with XDA, and the phone is decently popular so I am sure there will be a few roms, just not as many as say a OP3.

Why are people trying to flash via TWRP if the OTA updates still work after rooting and unlocking the boot loader?

pairustwo said:
Why are people trying to flash via TWRP if the OTA updates still work after rooting and unlocking the boot loader?
Click to expand...
Click to collapse
Okay so I just figured it out, but for the OTA update to work after rooting and having a non-stock recovery, you need to go to Settings->Updater->Menu(located on the bottom)->Download latest full package.
The full package is ~1.6GB and the regular update is ~280mb. The full package will work even if you have TWRP installed. But if you want the regular 280mb update, you need to get rid of TWRP and go back to a stock recovery.
Of course you will need to reinstall TWRP and root your phone again after doing this update.

Rakeen70210 said:
Okay so I just figured it out, but for the OTA update to work after rooting and having a non-stock recovery, you need to go to Settings->Updater->Menu(located on the bottom)->Download latest full package.
The full package is ~1.6GB and the regular update is ~280mb. The full package will work even if you have TWRP installed. But if you want the regular 280mb update, you need to get rid of TWRP and go back to a stock recovery.
Of course you will need to reinstall TWRP and root your phone again after doing this update.
Click to expand...
Click to collapse
I see the full package but I cant click on this, nothing is happened when I click on this.

Nas42O said:
I see the full package but I cant click on this, nothing is happened when I click on this.
Click to expand...
Click to collapse
I am not sure what you mean. Do you mean you can see the text "Download latest full package" but it is greyed out? If so please check to see if you arent currently at the latest version. If there is another problem, you might want to try to find a .zip of the full package and flash it that way.

Rakeen70210 said:
I am not sure what you mean. Do you mean you can see the text "Download latest full package" but it is greyed out? If so please check to see if you arent currently at the latest version. If there is another problem, you might want to try to find a .zip of the full package and flash it that way.
Click to expand...
Click to collapse
Yes , not greyed , but red color , and cant click on this .
I downloaded a full update of B31 about 1.77giga , just copy to the phone and flash it in twrp ?

Nas42O said:
Yes , not greyed , but red color , and cant click on this .
I downloaded a full update of B31 about 1.77giga , just copy to the phone and flash it in twrp ?
Click to expand...
Click to collapse
The exact latest update that I currently have is FRD-L04C567B150. I am not sure where you got your update but I suggest you just flash back to a complete stock image and try to update again from there.

Rakeen70210 said:
The exact latest update that I currently have is FRD-L04C567B150. I am not sure where you got your update but I suggest you just flash back to a complete stock image and try to update again from there.
Click to expand...
Click to collapse
its normal , you live in India no ?
i'm live in European country , so update are different .. Last update for us is FRD-L04C432B130

Nas42O said:
its normal , you live in India no ?
i'm live in European country , so update are different .. Last update for us is FRD-L04C432B130
Click to expand...
Click to collapse
No I am in the US. I am not sure about the EU version, but yes if you can find a .zip update file just put it on your phone and go into TWRP to install it. Might wanna make a backup too and wipe cache too just in case.

So if i download the full package in update and install it, bootloader will still be open? No full wipe? And later i only need to install twrp and root the phone again?

Palindrom87 said:
So if i download the full package in update and install it, bootloader will still be open? No full wipe? And later i only need to install twrp and root the phone again?
Click to expand...
Click to collapse
Updating or wiping your phone does not lock the Bootloader. The only way to lock the Bootloader again is by doing it manually yourself.
Yes after doing a full update you will need to reinstall TWRP as it will be replaced with the stock recovery and then re-root your phone again.

Rakeen70210, you sound really confident about doing full updates after rooting. Will these full updates also replace the kernel?
palendrome87 and NAS420 could you guys report back with any success or errors you have flashing full updates?
Where can one download full updates for Honor 8?

pairustwo said:
Rakeen70210, you sound really confident about doing full updates after rooting. Will these full updates also replace the kernel?
palendrome87 and NAS420 could you guys report back with any success or errors you have flashing full updates?
Where can one download full updates for Honor 8?
Click to expand...
Click to collapse
Seeing as how the full update package was ~1.65GB in size, I think its ok to assume that it replaces everything with the stock Honor 8 image. So yes it will replace the kernel too.
For downloading full updates, the only way I got mine was an OTA directly from the phone itself. Look at my previous comments to see how I got this update. If for some reason you cant update, check if your model is ready for an update. If it is and you cant update, try to flash back to a stock image. You should be able to find one on this site or anywhere else.

Flash stock recovery will lock boot loader ?

Nas42O said:
Flash stock recovery will lock boot loader ?
Click to expand...
Click to collapse
No, the only way to lock the bootloader is to manually lock it yourself using a similar operation to unlocking it.

Rakeen70210 said:
No, the only way to lock the bootloader is to manually lock it yourself using a similar operation to unlocking it.
Click to expand...
Click to collapse
I thought the same thing, but after taking the full OTA update my bootloader was locked again. If you want to update I would suggest first making a full backup to the external SD card in TWRP.

Then , its better to download à full update ( update.zip) ,copy to root of the phone , reboot in twrp and flash it ? Anyone already did it ?

Question about rooting and OTA updates

This is the first phone where I don't plan to install a custom ROM, and I don't know how OTA updates work while rooted.
Can they still be downloaded/installed normally while rooted? If so do I need to re-apply root each update? Does updating while rooted, or reapplying root afterwords wipe apps/settings?
I'm not sure if these are questions that can even be answered now, before anything has shipped, but worth a shot.

I might be wrong but I believe once you root you have to side load any OTA updates that come along and you may have to reroot and no this won't wipe ur phone

Flash Fire will be the way to go....

On rooted 2016 pixel never got flashfire to work for an ota. As for sideloading, that didn't work either. Had to download latest full image and use minimal adb to flash the full image. That can be done without wiping the phone and the detailed instructions are on XDA. I wonder if the pixel2 will be rootable by the same method to root the 2016 pixel. If I trade in for the pixel2 I will try it.

me_droid said:
On rooted 2016 pixel never got flashfire to work for an ota. As for sideloading, that didn't work either. Had to download latest full image and use minimal adb to flash the full image. That can be done without wiping the phone and the detailed instructions are on XDA. I wonder if the pixel2 will be rootable by the same method to root the 2016 pixel. If I trade in for the pixel2 I will try it.
Click to expand...
Click to collapse
I started with full image and removing the w.
Then Google started releasing OTA So I used flashfire and it worked fine.
I tried sideloading and it worked also.
During the whole period, I never lost root or hotspot accept for the last update I lost hotspot because of an update changing Carrier entitlement. So I had to go about modding system file but. My hats off to developers. I suggest everyone donates to the people who make things available.
Thanks,

There is a tutorial for using Magisk Manager with OTA Updates and A/B partition. I hope this will work with Pixel 2?
github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips

FSMcas said:
There is a tutorial for using Magisk Manager with OTA Updates and A/B partition. I hope this will work with Pixel 2?
github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips
Click to expand...
Click to collapse
Nice tutorial. Is there a way to install magisk any easier if I don't care about OTA's? Can't I just flash magisk and carry on or do I still have to worry about the A/B partitions?

I did this and now I'm stuck in a bootloop!
FSMcas said:
There is a tutorial for using Magisk Manager with OTA Updates and A/B partition. I hope this will work with Pixel 2?
github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips
Click to expand...
Click to collapse
I followed this procedure and everything seemed to be fine until reboot. At first it would attempt to boot, get to the screen with the G logo, and then after a few seconds reboot again, showing the unlocked bootloader warning screen. i interrupted the loop with the power button, and now I get to the G logo with the small grey animated progress bar going back and forth, but it hangs there and never completes booting..

[November 13th 2018] System Update 1.24.709.93 rolling out

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?

Pixel 4a Does Not Receive System Update Notification

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

Question Tmo users who converted to global at A11-OOS11, how did you get to 13 rooted?

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?