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

Search This thread

TimmyP

Senior Member
Mar 5, 2008
530
100
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...
 

mattie_49

Senior Member
Feb 4, 2010
3,735
1,195
Seymour Tn
OnePlus 9
OnePlus 9 Pro
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...
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
 
  • Like
Reactions: TimmyP and jmadiaga

TimmyP

Senior Member
Mar 5, 2008
530
100
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?
 
Last edited:

TimmyP

Senior Member
Mar 5, 2008
530
100
Im screwed. Its unable to restore my old image from usb, so Im bricked now. No idea what to do.
 

TimmyP

Senior Member
Mar 5, 2008
530
100
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
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?
 
Last edited:

mattie_49

Senior Member
Feb 4, 2010
3,735
1,195
Seymour Tn
OnePlus 9
OnePlus 9 Pro
Here
 

Attachments

  • Screenshot_20230323-124918_Magisk.png
    Screenshot_20230323-124918_Magisk.png
    172.4 KB · Views: 9
  • Screenshot_20230323-124914_Magisk.png
    Screenshot_20230323-124914_Magisk.png
    148.6 KB · Views: 9
  • Screenshot_20230323-124858_Magisk.png
    Screenshot_20230323-124858_Magisk.png
    142.1 KB · Views: 9
  • Like
Reactions: TimmyP

TimmyP

Senior Member
Mar 5, 2008
530
100
^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.
 
Last edited:

pubmastervnt

Member
Mar 27, 2017
16
5
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.
 
  • Like
Reactions: TimmyP

TimmyP

Senior Member
Mar 5, 2008
530
100
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.
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?
 

jmadiaga

Senior Member
Aug 25, 2013
128
12
pasig
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.
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.
 

TimmyP

Senior Member
Mar 5, 2008
530
100
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.
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?
 

TimmyP

Senior Member
Mar 5, 2008
530
100
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.
This fails if you have TWRP.
 

TimmyP

Senior Member
Mar 5, 2008
530
100
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.
Are you tmobile? How did you unlock BL on 13?
 

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    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...
    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
    1
    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.