Hi, since the last update i can no longer root my Pixel. When I try to flash the patched file from magisk after the latest update, I get a bootloop. If I do a downgrade, I can root it again without any problems. The last security update where it still works is from October 5th. Does anybody have the same Problem?
I had the same issue on the Dec. update. Download the most recent factory image that corresponds with the January factory update and flash the boot image with fastboot. Once you're able to boot up, use Magisk to patch that boot image and flash the patched boot image through fastboot, and you should be good to go.
Related
So I'd like to install the February security patches (to get rid of the annoying popup and for what they provide). I'm on stock with SuperSu 2.67 and a custom Kernel. I've uninstalled SuperSu with its built in Full unroot and used Flashify to restore my stock kernel that I backed up with it before installing a custom. After doing both of these things and installing the February patch - I'm still on January. What am I missing and is there anyway to get February to install without having to re-flash a factory image?
Thanks
Gabbyii said:
So I'd like to install the February security patches (to get rid of the annoying popup and for what they provide). I'm on stock with SuperSu 2.67 and a custom Kernel. I've uninstalled SuperSu with its built in Full unroot and used Flashify to restore my stock kernel that I backed up with it before installing a custom. After doing both of these things and installing the February patch - I'm still on January. What am I missing and is there anyway to get February to install without having to re-flash a factory image?
Thanks
Click to expand...
Click to collapse
I just pull out the boot.img, radio img, and system.img from the full factory image and flash with fastboot one by one, works every time for me.
Thanks.
Received the update of seguiridad August for Moto XT1063 but not me I settle for being rooted and TWRP, someone will have the Zip OTA to flash it, I have the rom stock but rooteada or there is some other method without flash of rom stock again.
As I can cancel the action does not appear to me,? Since it is not installed because I have root and TWRP and do not want to flash and having to back up everything, any suggestions?
I keep having a notification of failure of october update to be installed on my devices after many attemps to download it complete downloading but fail to install
Please help
I unlocked the bootloader and root my device could it be the cause of the issue !!?
Flash boot stock your version OTA A/B and then install it and again flash.
https://sourceforge.net/projects/others/files/MiA2/
I've updated my moto g5s plus to 8.1.0 and the rooted with magisk and now I'm getting October security update OTA which I can not install due to twrp as recovery and of course because magisk have replaced my stock boot.img.
What I've already tried:
Uninstalling magisk (With the provided magisk uninstall.zip) (If I unstall magisk I get BAD_KEY error.)
Flashing stock recovery.img and boot.img through fastboot.
Flash it through flashify.apk
Flash OTa through twrp.
Flash it through ADB sideload.
None Worked till now.
Please help me to install october patch without re-flashing stock rom.
Same boat and have done everything you have. Last think i want to do is wipe and load pure stock and deal with backing up and restoring 200+ apps and data.
so google says I've been up to date since January and I haven't bothered fixing this. Most importantly I want to keep root access. What is the right way to go about this? I know I can flash the ota and -w to keep data in fastboot but I'm just confused as to what I do to keep root.
Download the June update then extract the boot image, transfer it to your phone and patch it then transfer it back to your computer. Flash the update, after its updated boot into fastboot then flash the patched boot image. Updated, rooted, done. Also disable all magisk modules before you update because I've had compatibility issues with some of the updates that caused boot loops.