Related
I read some stuff about doing an OTA update with Magisk (v18) on my Pixel 3 (Feb 2019), but I still have a few questions about doing it. I'd rather avoid re-installing TWRP and Magisk from recovery again, and I'd like to be able to do this all without my computer if possible (see planned process below).
1. From what I've read, I should be able to restore a stock boot image to the inactive boot partition (from within Magisk Manager) , then install the Update (both steps 1 and 2), then reinstall Magisk Manager to the inactive boot partition.. And then reboot, and I should have the update, and keep TWRP and Magisk, right? (just looking for confirmation of the process)
2. I never provided a stock image to Magisk when I installed it originally, and I don't have one right now. How do I extract the boot image from the stock image on the Android website?
3. And do I need to indicate to Magisk that I have a boot image, or will it ask me when I go in to restore non-root?
4. Are OTA updates cumulative, or do I need to update the stock boot image each update?
Thanks!
madhattr999 said:
I read some stuff about doing an OTA update with Magisk (v18) on my Pixel 3 (Feb 2019), but I still have a few questions about doing it. I'd rather avoid re-installing TWRP and Magisk from recovery again, and I'd like to be able to do this all without my computer if possible (see planned process below).
1. From what I've read, I should be able to restore a stock boot image to the inactive boot partition (from within Magisk Manager) , then install the Update (both steps 1 and 2), then reinstall Magisk Manager to the inactive boot partition.. And then reboot, and I should have the update, and keep TWRP and Magisk, right? (just looking for confirmation of the process)
2. I never provided a stock image to Magisk when I installed it originally, and I don't have one right now. How do I extract the boot image from the stock image on the Android website?
3. And do I need to indicate to Magisk that I have a boot image, or will it ask me when I go in to restore non-root?
4. Are OTA updates cumulative, or do I need to update the stock boot image each update?
Thanks!
Click to expand...
Click to collapse
Although what you described works for some devices it won't on the pixel. To update and have twrp and root you'll need a pc. If the ota would flash when you have twrp and root, it won't, it would overwrite twrp and the patched boot image. So you're back to needing a pc to get twrp and install magisk.
For your other questions, if you extract the factory image you'll find another zip file in there. That's were the image files are and you need to extract that zip. And, ota's are cumulative so you don't need install previous ones. But specifically to the boot image, a previous months boot image may or may not be the same as the current one, etc.
jd1639 said:
Although what you described works for some devices it won't on the pixel. To update and have twrp and root you'll need a pc. If the ota would flash when you have twrp and root, it won't, it would overwrite twrp and the patched boot image. So you're back to needing a pc to get twrp and install magisk.
Click to expand...
Click to collapse
I'm confused then. Isn't the method I described specifically for a phone with two boot partitions?
The instructions I am trying to reference:
Devices with A/B Partitions
Due to the fact that these devices have two separate partitions, it is possible to have the OTA installed to the inactive slot and have Magisk Manager to install Magisk onto the updated partition. The out-of-the-box OTA installation works seamlessly and Magisk can be preserved after the installation.
After restoring stock boot image, apply OTAs as you normally would (Settings → System → System Update).
Wait for the installation to be fully done (both step 1 and step 2 of the OTA), do not press the restart button!! Instead, go to (Magisk Manager → Install → Install to Inactive Slot) and install Magisk to the slot that the OTA engine just updated.
After installation is done, press the reboot button in Magisk Manager. Under-the-hood Magisk Manager forces your device to switch to the updated slot, bypassing any possible post-OTA verifications.
After the reboot, your device should be fully updated, and most importantly, Magisk is still installed to the updated system!
Click to expand...
Click to collapse
madhattr999 said:
I'm confused then. Isn't the method I described specifically for a phone with two boot partitions?
The instructions I am trying to reference:
Click to expand...
Click to collapse
It is, but it doesn't work on the pixel. Google's security, probably the M chip, but I may be wrong, prevents it from working. In theory, magisk should be able to patch a boot image on your device and you shouldn't need the magisk zip but that doesn't work either. You can certainly try what you're describing but backup at least your data partition with twrp and have it off your device before you try. Get the contents of your internal sdcard to if you have stuff there you don't want to lose.
Most likely restoring the stock boot image and trying to install the ota will just not work, but you never know.
jd1639 said:
It is, but it doesn't work on the pixel. Google's security, probably the M chip, but I may be wrong, prevents it from working. In theory, magisk should be able to patch a boot image on your device and you shouldn't need the magisk zip but that doesn't work either. You can certainly try what you're describing but backup at least your data partition with twrp and have it off your device before you try. Get the contents of your internal sdcard to if you have stuff there you don't want to lose.
Most likely restoring the stock boot image and trying to install the ota will just not work, but you never know.
Click to expand...
Click to collapse
Thanks, I'll back up my files and try that.
Well, as far as I know twrp backups only work for data (with verity and all that). Always bootloop on a vendor or system restore. Back up your data a million times and go for it. Worse thing that happens is back to zero. Wait, you said no computer? Well, put it on a free cloud saving service, have your data backed up out there. Not advertizing for any service in particular, but backing up data is something everyone should be thinking about.
I am about to go for broke on this device for the 4th time. Non boot several times, flashing, flashing, building, flashing. I have the added benefit of figuring out if cell service works as the vendor.img always breaks it. Good times mate.
I might be missing something here, so please clarify if there is a way to "Get March OTA without having to re-install Magisk/TWRP", and how. Wondering about exactly that. Thank you.
madhattr999 said:
I'm confused then. Isn't the method I described specifically for a phone with two boot partitions?
The instructions I am trying to reference:
Click to expand...
Click to collapse
What you have quoted works fine for me. I did both February and March update with this method on my P3 and no problems.
The only thing i noticed is that it takes more than 20 minutes to do step 2 of the instalation (optimizing apps)
But to be on the safe side, please backup.
Another thing: i don't have TWRP recovery, just Magisk root
fronten said:
I might be missing something here, so please clarify if there is a way to "Get March OTA without having to re-install Magisk/TWRP", and how. Wondering about exactly that. Thank you.
Click to expand...
Click to collapse
There is no way to do so. Either side loading the OTA, or fastbooting the factory image, will still require you to install root and twrp. Which, really isn't a big deal at all :good:
Badger50 said:
There is no way to do so. Either side loading the OTA, or fastbooting the factory image, will still require you to install root and twrp. Which, really isn't a big deal at all :good:
Click to expand...
Click to collapse
But the person above you said he was able to do it on both recent updates...
madhattr999 said:
But the person above you said he was able to do it on both recent updates...
Click to expand...
Click to collapse
He doesn't have twrp and if you do have twrp the ota won't work for sure. So you're welcome to try if you're only rooted, no twrp. But patching the boot image and installing it from magisk hasn't worked, but maybe it does now. Let us know.
dracushor87 said:
What you have quoted works fine for me. I did both February and March update with this method on my P3 and no problems.
The only thing i noticed is that it takes more than 20 minutes to do step 2 of the instalation (optimizing apps)
But to be on the safe side, please backup.
Another thing: i don't have TWRP recovery, just Magisk root
Click to expand...
Click to collapse
@dracushor87, can you confirm that the process described by @madhattr999 worked correctly? I have a Pixel 3, rooted with Magisk, without TWRP. I would like to apply the monthly updates as easily as possible: without wiping data, uninstall/reinstall Magisk, etc.
Specifically:
madhattr999 said:
1. From what I've read, I should be able to restore a stock boot image to the inactive boot partition (from within Magisk Manager) , then install the Update (both steps 1 and 2), then reinstall Magisk Manager to the inactive boot partition.. And then reboot, and I should have the update, and keep TWRP and Magisk, right? (just looking for confirmation of the process)
Click to expand...
Click to collapse
I looked through Magisk Manager, and don't see a way to "restore a stock boot image to the inactive boot partition".
In the installed state, I don't see any functions for patching or installing boot images within Magisk Manager.
timg11 said:
@dracushor87, can you confirm that the process described by @madhattr999 worked correctly? I have a Pixel 3, rooted with Magisk, without TWRP. I would like to apply the monthly updates as easily as possible: without wiping data, uninstall/reinstall Magisk, etc.
Specifically:
I looked through Magisk Manager, and don't see a way to "restore a stock boot image to the inactive boot partition".
In the installed state, I don't see any functions for patching or installing boot images within Magisk Manager.
Click to expand...
Click to collapse
Yes, i confirm. Before you start, please check if there is an update available. If there is, restore image, update, reinstall magisk and then reboot. If you reboot without reinstalling magisk, you will lose root. To install on the inactive slot, just click install in magisk manager and then you will be asked what method to use. If what i said is unclear, just requote me
dracushor87 said:
Yes, i confirm. Before you start, please check if there is an update available. If there is, restore image, update, reinstall magisk and then reboot. If you reboot without reinstalling magisk, you will lose root. To install on the inactive slot, just click install in magisk manager and then you will be asked what method to use. If what i said is unclear, just requote me
Click to expand...
Click to collapse
Used this method after the May update finally arrived for me yesterday. Backed up everything just in case, but it worked flawlessly.
I'm at my wit's end here. I know I'm probably missing some critical step, but I haven't been able to install any OTAs since installing TWRP and Magisk. Fortunately, I was able to update to the latest TWRP before trying (the one that has working decryption) and backup Boot, the two Systems, and Data. I cannot stress enough how important this is!.
The OTA installer detects the device is rooted (or unlocked, if magisk isn't installed) and downloads the OTA. It then asks to install (which is does while booted to system, presumably to the side (A or B) that isn't updated), and asks to reboot. After reboot, the system fails to boot, then goes to the original OnePlus recovery (with the Chinese characters).
I seem to remember reading somewhere that I needed to shut the phone down instead of rebooting, but that doesn't seem to help. I want to know the correct procedure for updating, but I also want to better understand what is actually going on. I'm guessing the boot image on the other side gets overwritten by the OTA, which then flips you to that side, but I don't understand why it doesn't boot. Non-patched boot.img, I suppose?
These steps worked for me:
1 install ota
2 flash TWRP_A_B_Retention_Script-Magisk.zip via magisk
3 install magisk on inactive slot
4 reboot
RocketGeeezer said:
These steps worked for me:
1 install ota
2 flash TWRP_A_B_Retention_Script-Magisk.zip via magisk
3 install magisk on inactive slot
4 reboot
Click to expand...
Click to collapse
Awesome. I had not even heard of the retention script, but it sounds like exactly what I'm missing.
As for step 3, how do you install Magisk on the inactive slot?
Flapjack said:
Awesome. I had not even heard of the retention script, but it sounds like exactly what I'm missing.
As for step 3, how do you install Magisk on the inactive slot?
Click to expand...
Click to collapse
Open magisk, click the first install option and download that zip. Then a box with four options should appear. Click the last option to install on another slot.
whatthekj said:
Open magisk, click the first install option and download that zip. Then a box with four options should appear. Click the last option to install on another slot.
Click to expand...
Click to collapse
Thanks! Trying now!
Flapjack said:
Thanks! Trying now!
Click to expand...
Click to collapse
No problem. Let me know if you have any issues.
Well, it's different (booting to TWRP instead of stock recovery), but it still didn't work. It booted through the "warning...unlocked bootloader" screen twice, then went to TWRP, though without encryption. I was able to switch the boot slot and get into system again (just as it was before the flash), but I don't know what I did wrong.
The only thing different I did was use the tools under EX Kernel Manager to flash the TWRP retention script, as I couldn't find where Magisk could do that.
**EDIT**
Now when I try to do the OTA, I get a "System update installation failed".
I cleared the cache and tried it again, this time doing the retention zip from inside Magisk > Modules > Add (+ sign) option, which is what I'm assuming you did.
It did the exact same thing. After step four, I rebooted, and it went straight into recovery (without the option to decrypt).
I think you have to root your phone again If you have the chinese twrp you can do it via twrp. Otherwise put tj magisk installer on a USB stick
RocketGeeezer said:
I think you have to root your phone again If you have the chinese twrp you can do it via twrp. Otherwise put tj magisk installer on a USB stick
Click to expand...
Click to collapse
I can install/uninstall Magisk all day long, now that I've put TWRP 3.3.1-30 on. Even after a failed update, where it fails to ask to decrypt, I can still sideload via USB and install it (even though I can't see the internal storage).
Flapjack said:
I can install/uninstall Magisk all day long, now that I've put TWRP 3.3.1-30 on. Even after a failed update, where it fails to ask to decrypt, I can still sideload via USB and install it (even though I can't see the internal storage).
Click to expand...
Click to collapse
Can you lflash the ota image again? And after that twrp and after that magisk again. After that reboot to system again. This worked on my pixel. Not shure if this works on the 7 pro...
Maybe do some research first. There is also a unbrick thread
RocketGeeezer said:
Can you lflash the ota image again? And after that twrp and after that magisk again. After that reboot to system again. This worked on my pixel. Not shure if this works on the 7 pro...
Click to expand...
Click to collapse
I've tried that... several times. I wish it worked.
Maybe do some research first. There is also a unbrick thread
Click to expand...
Click to collapse
I've been doing a lot of research. There are some pretty in-depth threads on reddit how the A/B treble system works. Nothing I didn't already know. It's certainly different than pre-treble, but not rocket science... something is wrong with the phone. I would just like to know what I did wrong in the first place so I don't do it again.
Fortunately, I still have a bootable system with root on my B partition, so I was able to run TB and backup everything, along with all my pictures and such. I'll be restoring it to stock and just going from there. Looks like I don't have any other choice.
Flapjack said:
I've tried that... several times. I wish it worked.
I've been doing a lot of research. There are some pretty in-depth threads on reddit how the A/B treble system works. Nothing I didn't already know. It's certainly different than pre-treble, but not rocket science... something is wrong with the phone. I would just like to know what I did wrong in the first place so I don't do it again.
Fortunately, I still have a bootable system with root on my B partition, so I was able to run TB and backup everything, along with all my pictures and such. I'll be restoring it to stock and just going from there. Looks like I don't have any other choice.
Click to expand...
Click to collapse
Okay I updated just like we do with our pixels when we flash a custom ROM. TW RP flash your ota.zip,TWRP zip, reboot to recovery that will switch slots , because your update just flashed to the other slot, then flash magisk then reboot. That's how I did this last update. Oh and it's got to be the full ota from what I read anyways.
*Note* Some people have had success with this, while some others have not. You do this at your own risk.
Prerequisites:
Magisk Manager might need to be unhidden based on reports from some users.
Magisk needs to have a backup of stock boot.img.
Preserve AVB 2.0/dm-verity must be enabled. (Have gotten mixed reports on this it might or might not be needed)
Check the following post if you don't meet the prerequisites
https://forum.xda-developers.com/showpost.php?p=81186247&postcount=73
Update Process
When phone detects update
1. Disable any desired Magisk modules, ex. Edxposed (I usually disable all modules just to be safe)
2. Reboot
3. In Magisk, select Uninstall, press Restore Images
4. Do NOT Reboot
5. Install OTA Update via Settings -> System -> System Updates
6. When prompted to reboot, Do NOT Reboot
7. In Magisk Manager press Install
8. Select Install to Inactive Slot
9. Reboot
10. Enable the Magisk modules one by one
In case of bootloop after enabling a module there are 2 ways that I know of on how to retain root and fix bootloop.
One requires ADB
While phone is stuck in bootloop, connect phone to PC and run this commands via ADB.
adb wait-for-device shell magisk --remove-modules
adb reboot
This will remove all modules and you should be able to boot.
The second way is via fastboot. More information in this thread.
https://forum.xda-developers.com/pixel-4-xl/themes/magisk-modules-disabler-booting-magisk-t3990557
Some information that might help some people.
eg1122 said:
I know some users flash patched boot.img that someone else patched, thus bypassing the creation of a backup. I think choosing or not choosing to preserve avb 2.0/dm-verity also affects if phone will take OTA. I always preserve mine and always patch my own boot.img so I haven't ran into any issues. I'll just have to wait and see what happens on my end once I get the update. This reminds me of some issues some people where getting early on when rooting. Some people had to flash the patched boot.img to both a/b slots and some people didn't. Having both slots with a patched boot will also break the restoring of stock boot.img as Magisk only restores the active slot.
Click to expand...
Click to collapse
If you do it this way you'll be using the patched boot image from the previous update and not the current one.
airmaxx23 said:
If you do it this way you'll be using the patched boot image from the previous update and not the current one.
Click to expand...
Click to collapse
No it doesn't. When you select install to inactive slot it patches the newly installed boot.img that has been installed to the inactive slot. Only reason phone promts you to reboot after an update is to switch slots.
For whatever reason, whenever I would try to do Uninstall - Restore images (in step 3 of the OP), I would get a toast error saying "Stock backup does not exist"
I'm not sure why the expected backup files hadn't been created. I suspect it has to do with the process of manually patching the boot image whilst initially rooting, as suggested in this Git issue.
Anyway, I was ultimately able to work around this, and was eventually able to get Uninstall - Restore images to work.
I wrote about my workaround method here.
pdfruth said:
For whatever reason, whenever I would try to do Uninstall - Restore images (in step 3 of the OP), I would get a toast error saying "Stock backup does not exist"
I'm not sure why the expected backup files hadn't been created. I suspect it has to do with the process of manually patching the boot image whilst initially rooting, as suggested in this Git issue.
Anyway, I was ultimately able to work around this, and was eventually able to get Uninstall - Restore images to work.
I wrote about my workaround method here.
Click to expand...
Click to collapse
Yeah, there needs to be a backed up stock boot img for this to work. Being able to restore images the way stated in the issue would solve this as you could just restore a stock boot.img then continue doing the steps.
So does this work for every update? Just do the steps and it works? Im a complete noob when it comes to this stuff i just follow the write ups and pray!
DemonicMurderer said:
So does this work for every update? Just do the steps and it works? Im a complete noob when it comes to this stuff i just follow the write ups and pray!
Click to expand...
Click to collapse
Yes, it has worked for me all the time. These are the exact steps recommended by topjohnwu, I just made them more readibly available to users. Here is a link to his tutorial.
https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation
This work for the Verizon Pixel 4 XL???
SAMCR02018 said:
This work for the Verizon Pixel 4 XL???
Click to expand...
Click to collapse
Why would you need to since your not rooted with a locked bootloader? Just take the OTA.
Badger50 said:
Why would you need to since your not rooted with a locked bootloader? Just take the OTA.
Click to expand...
Click to collapse
Ok the can the Verizon version get the BL unlocked?
SAMCR02018 said:
Ok the can the Verizon version get the BL unlocked?
Click to expand...
Click to collapse
Nope. Unless you got lucky and they sold you a google version by mistake.
SAMCR02018 said:
Ok the can the Verizon version get the BL unlocked?
Click to expand...
Click to collapse
There is a write up for that.
Does anybody know if this also work with a custom kernel? I thought removing root and let magisk install old (boot) image should reinstall stock boot.img (if magisk first was installed through fastboot with stock kernel). Then i can take ota, patch inactive slot with magisk and then reboot. After reboot i can install custom kernel again througj ex kernel manager app. Does anybody know if this works?
Donric13 said:
Does anybody know if this also work with a custom kernel? I thought removing root and let magisk install old (boot) image should reinstall stock boot.img (if magisk first was installed through fastboot with stock kernel). Then i can take ota, patch inactive slot with magisk and then reboot. After reboot i can install custom kernel again througj ex kernel manager app. Does anybody know if this works?
Click to expand...
Click to collapse
Yes this method works with custom kernel. Magisk removed custom kernel when it restores stock boot.img
When does the dec patch come out, on the 5th?
I just started the process then realized it wasn't out yet so I haven't rebooted. When I go to the step of installing to the inactive slot I get a warning that you should only do this after the ota update - does anyone know if I'll be OK to go ahead with it even though I haven't done the ota yet?
in_dmand said:
When does the dec patch come out, on the 5th?
I just started the process then realized it wasn't out yet so I haven't rebooted. When I go to the step of installing to the inactive slot I get a warning that you should only do this after the ota update - does anyone know if I'll be OK to go ahead with it even though I haven't done the ota yet?
Click to expand...
Click to collapse
I wouldn't do it until the Dec ota comes out and that may be later today or sometime this week. Which is weird since all the other Pixels got it but hey it's Google
in_dmand said:
When does the dec patch come out, on the 5th?
I just started the process then realized it wasn't out yet so I haven't rebooted. When I go to the step of installing to the inactive slot I get a warning that you should only do this after the ota update - does anyone know if I'll be OK to go ahead with it even though I haven't done the ota yet?
Click to expand...
Click to collapse
Since it's not out yet, just do a direct install in Magisk to re-install it
Thanks for this guide !
Does anyone know how to update and maintain root for manually updating using OTA files ? Usually the update takes a long time to reach my phone, so I update using OTA files.
mkpansare said:
Thanks for this guide !
Does anyone know how to update and maintain root for manually updating using OTA files ? Usually the update takes a long time to reach my phone, so I update using OTA files.
Click to expand...
Click to collapse
The other way I update is using full factory images. Once you download the zip, extract it and find and open (via Notepad++ or similar advanced text editor) the flash-all.bat or flash-all.sh (depends on your system), find this line
fastboot -w update
replace with
fastboot update
Basically remove the -w, this will prevent a factory reset (wipe) on your device. Once it is done you will need to patch new boot.img via magisk and flash the newly patched boot.img via fastboot.
Hope this helps!
ps. I recommend to always disable Magisk Modules before updating as they could cause FC
eg1122 said:
Since it's not out yet, just do a direct install in Magisk to re-install it
Click to expand...
Click to collapse
Thanks that worked perfect... Was gonna be a long week without adblocker and lmt pie lol
Just a heads up to anyone who is wondering about root for this phone - I successfully rooted it with Magisk. It was pretty easy. Basically I just followed the same steps as outlined in this thread, which was for rooting last year's Moto G Stylus model, and it worked. Obviously you need to have already unlocked the bootloader before doing any of this.
I got the stock boot.img from the firmware linked in this thread. I patched it using Magisk Manager (v8.0.7) then flashed it via fastboot. My installed Magisk version is 21.4 (21400).
-- A WORD OF CAUTION: --
As of now there is no TWRP or any other custom recovery for this phone that I am aware of, so if you mess something up due to root, your only option to fix it might be to reflash the stock firmware.
A note about mobile banking apps:
After I installed Magisk Manager, my banking app stopped working and SafetyNet check was failing. After flashing the patched boot.img and rebooting, the SafetyNet check passed but my banking app still wasn't working. I used Magisk Hide and checked off the banking app in the list, but that didn't help either. What I had to do was use the Hide Magisk Manager option where it reinstalls Magisk Manager under a different name. Now my banking app is working again.
DM.IDOL said:
... - I successfully rooted it with Magisk. It was pretty easy. Basically I just followed the same steps as outlined in this thread, which was for rooting last year's Moto G Stylus model, and it worked. ...
Click to expand...
Click to collapse
It worked for me too. It was also easy for me because the only RETUS upload on the mirrors.lolinet site was my exact firmware version. Downloaded that, extracted and used that boot.img for magisk-patching.
The only issues I'm left with are:
1. Adaway isn't working (can't write to any of the canned hosts file paths) and I haven't figured out where I might be able to store a writable hosts file, and . . .
2. Titanium Backup (Pro) works to freeze almost every app that I wanted to disable. The one exception was Motorola Update Service. TiBu toasts that it was disabled and "invisible from the app drawer", but it actually wasn't disabled and still isn't. It still shows under System Applications. So I dunno . . . it's not a deal breaker as long as auto updating stays turned off.
Bootloader is unlocked and rooting via Magisk worked on my Stylus 2021, exactly as advertised.
Update: My solution for AdAway was here, AdAway 5.3 (newest version I believe).
Update2: Sans freezing Motorola Update Service, updates are of course frozen from actually running because of system changes by root & TWRP. So no big worries, just the nuisance of notifications.
cant the new maagisk be used as an alternative custom recovery? Something about renaming the apk to zip and then flashing zip file on recovery?
Mr.Morgan said:
cant the new maagisk be used as an alternative custom recovery? Something about renaming the apk to zip and then flashing zip file on recovery?
Click to expand...
Click to collapse
No, Magisk is not custom recovery.
There are two ways to install Magisk, using the .zip version, with a custom recovery like TWRP or
Using the magisk app to patch a boot.img then flash with fastboot.exe
sd_shadow said:
No, Magisk is not custom recovery.
There are two ways to install Magisk, using the .zip version, with a custom recovery like TWRP or
Using the magisk app to patch a boot.img then flash with fastboot.exe
Click to expand...
Click to collapse
I appreciate the knowledge, but perhaps you can shed some light on what the app means by " Custom Recovery lovers, no worries! The Magisk app APK itself is a custom recovery flashable zip, just like MAGIC. Check out the updated installation guide for more info"
Mr.Morgan said:
I appreciate the knowledge, but perhaps you can shed some light on what the app means by " Custom Recovery lovers, no worries! The Magisk app APK itself is a custom recovery flashable zip, just like MAGIC. Check out the updated installation guide for more info"
Click to expand...
Click to collapse
You are partly correct, there has been a big change with Magisk.
You can just change the Magisk.apk to Magisk.zip
But the zip does not replace a custom recovery.
It just eliminates the need for a separate manager.zip
In some custom recoveries, the installation may fail silently (it might look like success but in reality it bootloops). This is because the installer scripts cannot properly detect the correct device info or the recovery environment does not meet its expectation. If you face any issues, use the Patch Image method as it is guaranteed to work 100% of the time. Due to this reason, installing Magisk through custom recoveries on modern devices is no longer recommended. The custom recovery installation method exists purely for legacy support
Click to expand...
Click to collapse
Magisk in Recovery
If your device does not have ramdisk in boot images, Magisk has no choice but to be installed in the recovery partition. For these devices, you will have to reboot to recovery every time you want Magisk.
When Magisk is installed in your recovery, you CANNOT use custom recoveries to install/upgrade Magisk! The only way to install/upgrade Magisk is through the Magisk app. It will be aware of your device state and install to the correct partition and reboot into the correct mode.
Since Magisk now hijacks the recovery of the device, there is a mechanism to let you actually boot into recovery mode when needed: it is determined by how long you press the recovery key combo.
Click to expand...
Click to collapse
This does not replace the stock recovery, just patches the recovery.
I recently purchased this phone, Moto G Stylus 2021, from Amazon. When I enter the dev options menu, OEM Unlocking is greyed out. I did a bit of research and found another thread online where another two users had the same problem, for all of two days.
After two days, the option to enable OEM Unlocking was no longer greyed out for the both of them. Fascinating! I may return this phone before that time is up, but if I don't, I'll report back on any changes for sure.
EDIT: I've decided to return this phone and get a Galaxy Tab S7 instead; there's more room to draw and a better pen!
Can't find my firmware on lolinet (boost mobile qpc30.q4-31-93)
Tried lenovo's rescue tool to see if I could grab the firmware that way and it just kept giving me errors.
If anyone has some how acquired the appropriate firmware would you mind sending it to me?
I can't remember exactly where I seen someone else commenting on this topic but they had lost their cellular network after rooting ,
My problem / question is that I have also my lost my cellular network connection after rooting but not completley only to the original carrier I got t this phone with witch is boost, but if I try another carrier such as tmobile or sprint or even metro it will work because they are basically all 1 company now , but how do I fix this problem to get my phone to read my sim card as valid (I get the invalid sim msg) when I put my original sim in and I just went and got a brand new replacement sim from them to see if that would solve the issue.also going off reading the forums on here I went with the mask retus firmware for flashing because there isn't one on there anywhere for so any help would be hysteria l greatly appreciated. This is my only problem I'm having since rooting everything else is working perfectly fine.
BobbyBlunt said:
Can't find my firmware on lolinet (boost mobile qpc30.q4-31-93)
Tried lenovo's rescue tool to see if I could grab the firmware that way and it just kept giving me errors.
If anyone has some how acquired the appropriate firmware would you mind sending it to me?
Click to expand...
Click to collapse
just an idea but on the site that has all the firmware im thinking could submit a request to them using that telegram messenger thing for the firmware needed.....it may be kind of a longshot but just thought of that myself and the closest one i see to what you posted is the metro version
riggin said:
just an idea but on the site that has all the firmware im thinking could submit a request to them using that telegram messenger thing for the firmware needed.....it may be kind of a longshot but just thought of that myself and the closest one i see to what you posted is the metro version
Click to expand...
Click to collapse
I tried the lenovo recovery tool again and this time it was able to find the appropriate firmware. I was able to successfully root
Hey well i just installed latest magisk and patched boot img and moved it to my pc and went thru fast boot and just did fastboot flash boot patched.img and it works fine. I dunno if latest update fixed whatever was wrong on yours but if i installed the older one it would not even let me pick the boot img to patch *shrugs* but all working on mine now...we just need full device tree etc so we can get us a a recovery def want that before i go adding mods. If it helps any I have cricket same as ATT the person who lost cell may need to redo their apn or take sim card out and reapply it hope that works.
Moondroid said:
The one exception was Motorola Update Service. TiBu toasts that it was disabled and "invisible from the app drawer", but it actually wasn't disabled and still isn't. It still shows under System Applications.
Click to expand...
Click to collapse
I've been having the same problem trying to disable the update prompts. Titanium Backup doesn't work, nor can I disable it via terminal using pm. The system update screen will pop up multiple times a day, interrupting whatever I'm currently doing to tell me I have an update. It's really annoying that it can't be frozen.
Well after a few days of LTE connection my own unlock now works got root
riggin said:
just an idea but on the site that has all the firmware im thinking could submit a request to them using that telegram messenger thing for the firmware needed.....it may be kind of a longshot but just thought of that myself and the closest one i see to what you posted is the metro version
Click to expand...
Click to collapse
hey was just wondering since im kinda in the same situation you were in with not being able to obtain exact firmware need at first for boost model if maybe you can proovide tthe brief steps you made to get the lmsa tool to recognize it and pull the corerct firmware....ty so much if u can
riggin said:
hey was just wondering since im kinda in the same situation you were in with not being able to obtain exact firmware need at first for boost model if maybe you can proovide tthe brief steps you made to get the lmsa tool to recognize it and pull the corerct firmware....ty so much if u can
Click to expand...
Click to collapse
Unfortunately, either LMSA determines the correct firmware or it doesn't, there isn't anything that can be done to fix it, except contacting Motorola.
For other options see
[Guide] Using Fastboot.exe with Motorola devices
Guide: Using Fastboot.exe with Motorola Devices If your device has its own section please post in that section. You can ping me with @sd_shadow MediaTek or Qualcomm Chip? Do I have a MediaTek Device? see post #26 Info: If you have a MediaTek...
forum.xda-developers.com
Hey Guys, I'm continuing on this thread since I've gotten further. I used LMSA to download the firmware zip using the Resuce button. Afterwards I copy that zip (2+ gigs) to my download folder. I open up Magisk and select intall and select the firmware zip. I starts out successfully but then fails. I get this in the log folder.
- Device platform: arm64-v8a
- Installing: 23.0 (23000)
- Copying image to cache
- Unpacking boot image
Parsing boot image: [/data/user_de/0/com.topjohnwu.magisk/install/boot.img]
! Unsupported/Unknown image format
! Installation failed
I even tried to resuce the phone using the firmware provided by the LMSA program which essentially wipes my phone and try again with a clean Magisk load and I'm getting the same. The only thing I'm thinking is I could be getting my Magisk from another source. I'm using version 23 from github.
steppinthrax said:
Hey Guys, I'm continuing on this thread since I've gotten further. I used LMSA to download the firmware zip using the Resuce button. Afterwards I copy that zip (2+ gigs) to my download folder. I open up Magisk and select intall and select the firmware zip. I starts out successfully but then fails. I get this in the log folder.
- Device platform: arm64-v8a
- Installing: 23.0 (23000)
- Copying image to cache
- Unpacking boot image
Parsing boot image: [/data/user_de/0/com.topjohnwu.magisk/install/boot.img]
! Unsupported/Unknown image format
! Installation failed
I even tried to resuce the phone using the firmware provided by the LMSA program which essentially wipes my phone and try again with a clean Magisk load and I'm getting the same. The only thing I'm thinking is I could be getting my Magisk from another source. I'm using version 23 from github.
Click to expand...
Click to collapse
It isn't a zip file it's a folder or at least every firmware I have downloaded is automatically unzipped by LMSA.
You only need to copy the boot.img and maybe the recovery.img to the device.
sd_shadow said:
It isn't a zip file it's a folder or at least every firmware I have downloaded is automatically unzipped by LMSA.
You only need to copy the boot.img and maybe the recovery.img to the device.
Click to expand...
Click to collapse
Thanks I figured it out last night. I also figured out pretty quickly that once you root a phone certain applications will no longer function. I didn't deal with this before, but since I work from home I have to use some of those apps that create a "Work Profile". The one app "Intelligent Hub" removed itself and my work profile. When trying to re-install and authenticate with my work it literally said "Won't provision a compromised device".
Within Magsik I used the Magsik hide feature and tried selected that app and hiding all methods that it could detect root. I even then rebooted, removed/reinstall etc. Nothing worked. The app still kept detecting root. I know that the Xposed Framework modules may work in hiding root but I decided to go all the way back to normal since there's little benefit for me to root except for the ability for me to remove bloatware. This is a retail unlocked and there's little if any bloatware on the device.
I removed Magsik and any other junk, turned on OEM locking and rebooted and I'm back to mormal. Thank you everyone this was a leaning exp. I haven't rooted in like 5 years.
DM.IDOL said:
I've been having the same problem trying to disable the update prompts. Titanium Backup doesn't work, nor can I disable it via terminal using pm. The system update screen will pop up multiple times a day, interrupting whatever I'm currently doing to tell me I have an update. It's really annoying that it can't be frozen.
Click to expand...
Click to collapse
FYI, for posterity, instead of getting multiple notifs per day I just tap and let it try to update. It fails quickly and the notification is nixed for a while.
Got a brand new KB2005
I haven't put in a SIM Card yet; haven't even connected it to my Google account (I want to get everything set up first)
So, my first actions were to unlock the bootloader, and root the phone using Magisk.
Build number Oxygen OS 11.0.8.13.KB05AA
My phone won't connect to wifi.
If I go to Wifi Settings, Wifi is off.
If I turn it on, it shuts itself off again.
Wifi was working before I rooted, because it has 1 saved network.
Is this a known issue - no wifi without a Sim - or is something wrong?
Any troubleshooting tips?
Thanks in advance!
sounds similar to this
solved: lost wifi while rooting, can I reflash modem and get it back?
So I updated to 11.0.08.14.KB05BA. I then rooted using the guide here, via Magisk Rooted, everything works, except: My wifi connection will not turn on (let alone connect). I hit the wifi icon, it "turns on" and then "turns off" I go to the wifi...
forum.xda-developers.com
Darn.
I tried to be extremely careful to match the version/build.
So how do I revert/repair it?
Better use "dd" command in modified recovery or use Payload Dumper get boot.img directly form your system or full update.zip.
Otherwise very easy got mistake, the source may be wrong in the first place.
You can use same version full update.zip update again, or fastboot flash the correct boot.img.
My magisk patched boot.img from 11.0.8.13 KB05AA.
img MD5: 8d:60:d9:38:6d:f4:f1:2d:16:59:a6:a1:e0:4d:13:70
ULTRAJC said:
My magisk patched boot.img from 11.0.8.13 KB05AA.
img MD5: 8d:60:d9:38:6d:f4:f1:2d:16:59:a6:a1:e0:4d:13:70
Click to expand...
Click to collapse
Thank you VERY much - that worked!
cheshyre said:
Thank you VERY much - that worked!
Click to expand...
Click to collapse
If you have to use online source patched boot.img, don't flash, only do "fastboot boot boot.img", if it can successfully boot into the system, then use magisk patch current system boot.img and reboot.
ULTRAJC said:
If you have to use online source patched boot.img, don't flash, only do "fastboot boot boot.img", if it can successfully boot into the system, then use magisk patch current system boot.img and reboot.
Click to expand...
Click to collapse
Sorry, saw this too late.
Was about to post a new Q because I can't install the OTA update, but maybe you know the answer?
Download and install update returns "Installation problem"
In Magisk, Uninstall Magisk > Restore Images says "Stock backp does not exist"
Help me, Obi-Wan Kenobi...
fwiw, I haven't yet done much customizing of my device, so if it's easiest to just wipe everything and start fresh, I can do that.
cheshyre said:
Sorry, saw this too late.
Was about to post a new Q because I can't install the OTA update, but maybe you know the answer?
Download and install update returns "Installation problem"
In Magisk, Uninstall Magisk > Restore Images says "Stock backp does not exist"
Help me, Obi-Wan Kenobi...
Click to expand...
Click to collapse
Incremental update requires the system has not been modified, and little tricky, do not directly patch inactive slot befor reboot, let upgrade process boot up system say successful, then patch.
Original boot.img (11.0.8.13 KB05AA):
MD5: 75ba083950c2a75c6b423442ef2dfc37
Thank you very very VERY much for all your help.
Finally got the phone rooted, and while I'm still configuring some of my apps & settings, I couldn't've gotten this far without your assistance.