Related
I updated Magisk Manager to 5.5.5 and it is asking if I want to update Magisk from 15.2 to 15.3. If I want to, can I just patch the boot img that is on the phone (Pixel 2) from installing 15.2 on 8.1.0 January patch, then flash that? Do I need to download the boot img again? Do I have to (should I) remove the old patched boot img prior to doing so?
Do I have this somewhat straight, or am I going off the rails? I looked for specific "upgrading" info, but just keep seeing the installing for the first time info.
Thanks in advance!
amajamar said:
I updated Magisk Manager to 5.5.5 and it is asking if I want to update Magisk from 15.2 to 15.3. If I want to, can I just patch the boot img that is on the phone (Pixel 2) from installing 15.2 on 8.1.0 January patch, then flash that? Do I need to download the boot img again? Do I have to (should I) remove the old patched boot img prior to doing so?
Do I have this somewhat straight, or am I going off the rails? I looked for specific "upgrading" info, but just keep seeing the installing for the first time info.
Thanks in advance!
Click to expand...
Click to collapse
I don't remember the actual choices, since mine is already updated, but I do it straight from Magisk Manager app. I think I choose update then the direct install (recommended) option. I believe it then shows the log as it updates and once done gives option to reboot. Once it reboots, you should be on latest (15.3) version of Magisk, and you still have root and pass Safety checks. It has never caused any boot loops for me, just smooth and simple.
HTH!
amajamar said:
I updated Magisk Manager to 5.5.5 and it is asking if I want to update Magisk from 15.2 to 15.3. If I want to, can I just patch the boot img that is on the phone (Pixel 2) from installing 15.2 on 8.1.0 January patch, then flash that? Do I need to download the boot img again? Do I have to (should I) remove the old patched boot img prior to doing so?
Do I have this somewhat straight, or am I going off the rails? I looked for specific "upgrading" info, but just keep seeing the installing for the first time info.
Thanks in advance!
Click to expand...
Click to collapse
like the other response, i am able to upgrade magisk directly from magisk manager (direct install method)
one caveat, i don't know if it's still true, i had an issue upgrading a month or two back and someone on here recommended i set my magisk to the "beta" channel (settings -> update channel). i suspect this is no longer needed, but i left it on the beta channel and have had no issues upgrading magisk every time it notifies me of a new update
Ok, so I can upgrade directly from the app. Great! I guess I was overthinking...
Thanks!
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 ask before in "guide to root motorla g stylus":
really is no way to work OTA while Magisk installed? i mean some Magisk Hide Props Config, or not install TWRP or anything? i actualy have Nokia 7 Plus (unlocked via unoficial method) and last year while not installed TWRP is possible check system update, install over air (while Magisk is installed), before reboot run MagiskManager, install Magisk to other slot, reboot, started from updated slot with Magisk installed, without need flash stock boot img before ota and flash manualy patched boot img after OTA... sure have Moto G Pro additional check or limitation and this not work? thanks...
Click to expand...
Click to collapse
without reaction, then try make separated thread, i actualy have one week "Motorola Moto G Pro" (XT2043-7), rooted, and wait for OTA, UpdateCheck in Settings not show me, try LMSA Rescue/Download and show me same version as have installed QPRS30.80-109-2-7...
Questions:
- Have any user of same phone, without root, already showed Octorber OTA?
- Is on rooted posible UpdateCheck with show if OTA avaiable?
- Have any working solution for OTA update on rooted phone without need connected with PC? Similar or same as i write about Nokia7Plus?
(i mean without flash back stock img, make ota, patch new boot.img file in MagiskManager, flash it via TWRP booted...
i think without PC be sure posible flash back stock boot.img to boot partition, before OTA, maybe download zip of full "rom" and extract boot.img, patch via MagiskManager, but not flash patched
EDIT: Sollution here
The answers to your first two questions are yes. When on stock I successfully updated. And while rooted there was a notification for ota update, it would download, but fall to install. I came across a way to do it without having to connect to pc. Some said it was successful but I was not able to try. It has something to do with placing your original boot.img into a a folder on one of the root directories but I had no idea how in the hell they came up with the system path to the file (encrypted??) Because I didn't have any of the folders on my phone and was to lazy at the time to ask for help. It was also an older thread so I didn't feel like bringing up a thread that old.
without root you updated system to higher (with Ocrober security patches) version than QPRS30.80-109-2-7 (this version have September security patches) ?
second part of you answer i think not understand, with rooted phone, put boot.img in "a" directory in one (which?where?) root folder and OTA services flash it before upgrade/reboot???
please, anyone with "Motorola Moto G Pro" (XT2043-7), channel "reteu", have already displayed update notification for "QPRS30.80-109-2-8" ?
Yesterday i finally get OTA notify with QPRS30.80-109-2-8, with Magisk installed, ofcourse failed install, then i find this solution, to update OTA over Air with Magisk installed without need any steps with PC
Code:
1. Settings System/DeveloperOptions/AutomaticSystemUpdate=Disable
2. Settings System/SystemUpdate/.../SmartUpdate=Disable
3. MagiskManager UninstallMagisk/RestoreImages
4. Settings System/SystemUpdate "doing normal update and wait for finish"
5. After OTA Instralled [B]NOT[/B] Restart
6. MagiskManager MagiskInstall/InstallToInactiveSlotAfterOTA/LetsGo "wait for finish"
7. After Magisk installed tap to Reboot button in Magisk Instalation wIndow...
Very nice writeup. With respect to step 3, I never installed Magisk Manager (I simply did the patch of boot.img) so what should I do to restore image? With respect to step 5, how do I get to that point? Is it a prompt after rebooting?
flroots said:
[...] step 3, I never installed Magisk Manager (I simply did the patch of boot.img) so what should I do to restore image?
Click to expand...
Click to collapse
you must have installed Magisk via TWRP (only temporary booted is enough), this make backup image which is latter in MagiskManager used for restore
flroots said:
[...] step 5, how do I get to that point? Is it a prompt after rebooting?
Click to expand...
Click to collapse
this is normal OTA screen, is show if you check update and if available, then show progress about installing, only is need after ota finished, not using reboot button in this OTA screen, but make steps 6 and 7
k3dar7 said:
you must have installed Magisk via TWRP (only temporary booted is enough), this make backup image which is latter in MagiskManager used for restore
Click to expand...
Click to collapse
I installed Magisk Manager via download of apk file (not TWRP). I then clicked on Magisk and chose "Select and patch a file". The end result was getting root. I never actually did a separate install of Magisk or Magisk Manager. I wonder if your step 3 will work in this case.
k3dar7 said:
this is normal OTA screen, is show if you check update and if available, then show progress about installing, only is need after ota finished, not using reboot button in this OTA screen, but make steps 6 and 7
Click to expand...
Click to collapse
Thanks
flroots said:
I installed Magisk Manager via download of apk file (not TWRP). I then clicked on Magisk and chose "Select and patch a file". The end result was getting root. I never actually did a separate install of Magisk or Magisk Manager. I wonder if your step 3 will work in this case.
Click to expand...
Click to collapse
Understand, but as i write, you must have installed Magisk via TWRP, with this method, Magisk make backup of boot image to "/data/magisk_backup_SomeRandomStrings/boot.img.gz", this file is used when you doing step 3, but if you only patch stock boot file, then ofcourse this backup is not created... i sugest you:
- revert boot to stock via same way as you flash patched before, but using stock boot.img
- boot TWRP (NOT flash, use command is section "Boot") and install Magisk.zip oficial release
- if on your phone/touchscreen variant not work touchscreen in TWRP, then (while still is booted TWRP) install it using adb
Thanks.
I have a couple questions:
1. Is it true that one shouldn't do an OTA unless the corresponding firmware can be downloaded due to the fact that you will lose root and not be able replace it until the corresponding boot.img can be obtained?
2. When downloading firmware from LMSA, does it download the latest or does it download your current version?
flroots said:
I have a couple questions:
1. Is it true that one shouldn't do an OTA unless the corresponding firmware can be downloaded due to the fact that you will lose root and not be able replace it until the corresponding boot.img can be obtained?
2. When downloading firmware from LMSA, does it download the latest or does it download your current version?
Click to expand...
Click to collapse
1. NO - i with Magisk installed, receive OTA October (delayed) and November, and hope with december be same
not need wait for avaiable boot.img, because with "Boot TWRP & Flash MagiskZip" is patched onthefly "any" version of boot partition on device.
2. not sure, i not use LMSA
k3dar7 said:
1. NO - i with Magisk installed, receive OTA October (delayed) and November, and hope with december be same
not need wait for avaiable boot.img, because with "Boot TWRP & Flash MagiskZip" is patched onthefly "any" version of boot partition on device.
Click to expand...
Click to collapse
Thanks, that sounds great. Would you mind elaborating the steps involved? I have TWRP and Magisk installed now.
k3dar7 said:
Yesterday i finally get OTA notify with QPRS30.80-109-2-8, with Magisk installed, ofcourse failed install, then i find this solution, to update OTA over Air with Magisk installed without need any steps with PC
Code:
1. Settings System/DeveloperOptions/AutomaticSystemUpdate=Disable
2. Settings System/SystemUpdate/.../SmartUpdate=Disable
3. MagiskManager UninstallMagisk/RestoreImages
4. Settings System/SystemUpdate "doing normal update and wait for finish"
5. After OTA Instralled [B]NOT[/B] Restart
6. MagiskManager MagiskInstall/InstallToInactiveSlotAfterOTA/LetsGo "wait for finish"
7. After Magisk installed tap to Reboot button in Magisk Instalation wIndow...
Click to expand...
Click to collapse
Do these steps cause loss of data? Thanks
flroots said:
Do these steps cause loss of data? Thanks
Click to expand...
Click to collapse
i ofcourse not garant ;-) but for me nothing lost, also installed magisk modules is preserved...
k3dar7 said:
Yesterday i finally get OTA notify with QPRS30.80-109-2-8, with Magisk installed, ofcourse failed install, then i find this solution, to update OTA over Air with Magisk installed without need any steps with PC
Code:
1. Settings System/DeveloperOptions/AutomaticSystemUpdate=Disable
2. Settings System/SystemUpdate/.../SmartUpdate=Disable
3. MagiskManager UninstallMagisk/RestoreImages
4. Settings System/SystemUpdate "doing normal update and wait for finish"
5. After OTA Instralled [B]NOT[/B] Restart
6. MagiskManager MagiskInstall/InstallToInactiveSlotAfterOTA/LetsGo "wait for finish"
7. After Magisk installed tap to Reboot button in Magisk Instalation wIndow...
Click to expand...
Click to collapse
Tried the above steps, but OTA update unsuccessful. Discovered that phone still rooted so obviously step 3 did not work for me. What should I try next? How about fastboot of original boot.img?
flroots said:
Tried the above steps, but OTA update unsuccessful. Discovered that phone still rooted so obviously step 3 did not work for me. What should I try next? How about fastboot of original boot.img?
Click to expand...
Click to collapse
step 3 restore boot image(what show you MagiskManager as output while you restore images??), but without reboot you have ofcourse still root, and you can't reboot if you want patch boot in other slot after ota via MagiskManager....
but i don't know reason why OTA failed anyway restoring original boot.img via fastboot be i think possible (not try in MotoGPro but manytime with Nokia7Plus)
k3dar7 said:
step 3 restore boot image(what show you MagiskManager as output while you restore images??), but without reboot you have ofcourse still root, and you can't reboot if you want patch boot in other slot after ota via MagiskManager....
but i don't know reason why OTA failed anyway restoring original boot.img via fastboot be i think possible (not try in MotoGPro but manytime with Nokia7Plus)
Click to expand...
Click to collapse
Thanks. Magisk simply says, "restoration done". Once I fastboot boot.img will I need to re-install magisk from scratch or should I continue with steps 6 and 7?
flroots said:
Thanks. Magisk simply says, "restoration done". Once I fastboot boot.img will I need to re-install magisk from scratch or should I continue with steps 6 and 7?
Click to expand...
Click to collapse
maybe magisk backup boot.img have already twrp inside if you install twrp before magisk?
anyway, if you flash stock boot.img, then step 6&7 is not applicable, because this need booted rooted system
btw: method above work for me also while i upgrade from Android10 to Android11 ;-)
I previously had Magisk installed and rooted my 8T with Build 11.6.5.KB05AA. I followed some instructions on how to install an OTA update. I uninstalled Magisk and ran the OTA update. The instructions advise me to install Magisk on the inactive slot. However, I do not have this option. Instead, I only have Preserve AVB 2.0/dm-verify and Recovery Mode. I don't have TWRP installed so I don't think this will work. I've tried selecting Preserve and not selecting Preserve and selecting Next in Magisk. My next option is to "select and patch a file". I downloaded the bin for 11.0.6.8 and extracted it using payload_dumper and Python and copied it to my phone. However, whenever I try to patch it, Magisk states installation failed.
So, I figured I would finish the install of 11.0.6.8 and rebooted the phone using the update installation reboot button. I figured I'd just start from scratch and root following the original root instructions. My bootloader is already unlocked. I copied the boot.img from 11.0.6.8 to my phone and tried to patch using Magisk (again, I only have the options above). Again, it failed.
What am I doing wrong? Why won't Magisk patch the boot.img file? Shouldn't it work like an original attempt to root it?
Thanks.
rcbjr2 said:
I previously had Magisk installed and rooted my 8T with Build 11.6.5.KB05AA. I followed some instructions on how to install an OTA update. I uninstalled Magisk and ran the OTA update. The instructions advise me to install Magisk on the inactive slot. However, I do not have this option. Instead, I only have Preserve AVB 2.0/dm-verify and Recovery Mode. I don't have TWRP installed so I don't think this will work. I've tried selecting Preserve and not selecting Preserve and selecting Next in Magisk. My next option is to "select and patch a file". I downloaded the bin for 11.0.6.8 and extracted it using payload_dumper and Python and copied it to my phone. However, whenever I try to patch it, Magisk states installation failed.
So, I figured I would finish the install of 11.0.6.8 and rebooted the phone using the update installation reboot button. I figured I'd just start from scratch and root following the original root instructions. My bootloader is already unlocked. I copied the boot.img from 11.0.6.8 to my phone and tried to patch using Magisk (again, I only have the options above). Again, it failed.
What am I doing wrong? Why won't Magisk patch the boot.img file? Shouldn't it work like an original attempt to root it?
Thanks.
Click to expand...
Click to collapse
Make sure you download the latest canary magisk manager. It sound like you might be on an older magisk version.
Qnorsten said:
Make sure you download the latest canary magisk manager. It sound like you might be on an older magisk version.
Click to expand...
Click to collapse
I seem to have the Canary Update channel set already (I thought it was set to Stable, but I guess not). Doesn't that mean I already have the latest Canary build? Manager shows that latest is 6951d926 (21402) (16) but Installed shows 658d74e0 (21402) (16). I assume this means they are different? Install doesn't seem to update it. Maybe grab the latest APK from Github? Thanks.
Later: Can I install it on my phone by download Magisk v21.4 zip and changing extension to APK and installing it? I thought I read everything is now in the zip/apk? Thanks.
FINAL UPDATE: OK, I downloaded the latest MagiskManager, not the one from Canary. I was then able to patch the boot file. The phone rebooted, but it's not working just right yet. None of my icons show up on my home screen, although if I press the recent apps list, it shows a bunch of apps, although selecting one doesn't do anything. I might have to put the original boot image back on just to get it to boot and worry about rooting later. Sigh. It's always something.
Have you tried following this guide it should work perfectly
[Guide] OnePlus 8T EASY ROOT (for all unlocked variants)
DO NOT FOLLOW THIS GUIDE IF YOU HAVE ANDROID 12 Visit this thread for more information ________________________________________________________ CAVEAT I've only tested this on my device running Android 11 (KB2005 / KB05AA), but it should be...
forum.xda-developers.com
In the latest canary apk released today he moved over to that the apk bundle magisk as well and don't need to download it anymore but it shouldn't matter for this case. There is no working custom recovery for Oneplus 8T right now. But if there was and it was updated you would be able to flash the apk.
You did not have to uninstall Magisk. When you would complete the OTA, instead of rebooting you should go into Magisk and select install to inactive slot. As you uninstalled magisk, you're not getting this option. Uninstalling magisk is different from disabling the modules.
Now you need to root it again using the same method given in other thread. Rooting 11.0.6.8 is no different from the rooting process for previous OOS versions.
alanzaki073 said:
Now you need to root it again using the same method given in other thread. Rooting 11.0.6.8 is no different from the rooting process for previous OOS versions.
Click to expand...
Click to collapse
I was able to patch the new boot image and flashed it but when I rebooted nothing worked quite right. None of my apps would run. I could get into settings but couldn't get out of it. I flashed the unrooted boot image and am able to use the phone. I'll try again tomorrow.
The instructions I followed said to uninstall Magisk first. Now wish I hadn't. I suppose worse comes to worse I can figure out how to reinstall 6.5 cause I was able to root that. Thanks for the reply.
Qnorsten said:
Have you tried following this guide it should work perfectly
[Guide] OnePlus 8T EASY ROOT (for all unlocked variants)
DO NOT FOLLOW THIS GUIDE IF YOU HAVE ANDROID 12 Visit this thread for more information ________________________________________________________ CAVEAT I've only tested this on my device running Android 11 (KB2005 / KB05AA), but it should be...
forum.xda-developers.com
In the latest canary apk released today he moved over to that the apk bundle magisk as well and don't need to download it anymore but it shouldn't matter for this case. There is no working custom recovery for Oneplus 8T right now. But if there was and it was updated you would be able to flash the apk.
Click to expand...
Click to collapse
I was looking at a different guide, but will try the one you recommend. I'm aware there is no TWRP for the 8T. I did use that method for my prior OP6. I did patch and flash the patched boot image, but none of my apps appeared on my home page so I flashed the unrooted boot image so I could at least use the phone. Thanks.
rcbjr2 said:
I was able to patch the new boot image and flashed it but when I rebooted nothing worked quite right. None of my apps would run. I could get into settings but couldn't get out of it. I flashed the unrooted boot image and am able to use the phone. I'll try again tomorrow.
The instructions I followed said to uninstall Magisk first. Now wish I hadn't. I suppose worse comes to worse I can figure out how to reinstall 6.5 cause I was able to root that. Thanks for the reply.
Click to expand...
Click to collapse
The instructions definitely lied to you...
Now:
1. Take the 11.0.6.8 boot image
2. Patch it with magisk (latest beta is fine, you don't need alpha anymore)
3. Boot the patched image
4. Install magisk manager in case it's not installed
5. Check it for root, if all is fine do install --> direct install
6. Reboot
Kollachi said:
The instructions definitely lied to you...
Now:
1. Take the 11.0.6.8 boot image
2. Patch it with magisk (latest beta is fine, you don't need alpha anymore)
3. Boot the patched image
4. Install magisk manager in case it's not installed
5. Check it for root, if all is fine do install --> direct install
6. Reboot
Click to expand...
Click to collapse
When you say Boot the patched image, I assume you mean fastboot flash it to the device?
I tried updating Magisk using a beta channel, but then manager wouldn't work at all. I just wouldn't run. So I reinstalled Manager 8.0.7 from the APK I downloaded and now I don't have Canary as an update channel. I keep alternative between having a Magisk icon and a separate manager icon. Weird. I'm trying to only wind up with latest manager installed so I can re-root the phone. Thanks.
LATER: Success! I followed the steps here: https://forum.xda-developers.com/t/guide-oneplus-8t-easy-root-for-all-unlocked-variants.4210775/. And everything worked (which was linked in a prior message). Thanks to all!
rcbjr2 said:
When you say Boot the patched image, I assume you mean fastboot flash it to the device?
I tried updating Magisk using a beta channel, but then manager wouldn't work at all. I just wouldn't run. So I reinstalled Manager 8.0.7 from the APK I downloaded and now I don't have Canary as an update channel. I keep alternative between having a Magisk icon and a separate manager icon. Weird. I'm trying to only wind up with latest manager installed so I can re-root the phone. Thanks.
LATER: Success! I followed the steps here: https://forum.xda-developers.com/t/guide-oneplus-8t-easy-root-for-all-unlocked-variants.4210775/. And everything worked (which was linked in a prior message). Thanks to all!
Click to expand...
Click to collapse
Nope i mean "fastboot boot xxxxx.img"
Kollachi said:
Nope i mean "fastboot boot xxxxx.img"
Click to expand...
Click to collapse
I figured out that's what you meant when I followed the instructions linked in another message. I had never booted that way previously. Thanks!
I am about to root my 8t using the guide someone linked above. My question is.. I'm on ver. 11.0.5.6.KB05AA will I still be able to root if I update or will it take away the ability to root.. also, will it affect the quality of the root ? Thanks in Advance.
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?