Today I bought HTC 10 and all day learned about rooting and so on. I have EU version, not branded (CID HTC__034) with latest MM (1.95.401.4) - I don't want Nougat for now. I unlocked bootloader, let S-ON for now, installed latest TWRP and now I want to install Magisk - I followed the very easy guide in Magisk official thread. I copied the file to SD card and flashed in TWRP. Then reboot. Magisk Manager wasn't there so I installed it manualy as is written in Magisk thread. However it says "Magisk is not installed". I tried several times, same result. I installed Superuser from Play Store, after reboot it said me to update SU binary, I clicked on that and nothing happened. What should I do? I don't want SuperSu (I didn't install it before), Magisk is way better for my needs (I wanna install OTA Nougat one day and Oreo maybe when it will be released). Thanks for any advice.
I need help to root my phone with magisk. I am currently in android root user on facebook, someone said I could get help from this forum. I tried to root my phone 6 times and all failed. Everytime I reboot system after flash the magisk or supersu, I got stuck on 1st screen of Samsung logo and then I have to flash stock firmware. And magisk uninstaller seem not work for me. I have tried SuperSu, magisk v16.3, 18.1, 19.3, 20.2, and 20.3.
This is the list of softwares I used before I flash the magisk or supersu:
-odin3_v3.13.1
-twrp 3.3.1-0 starlet Mesa v2
-no-verity-opt-encrypt 6.0
-RMM_state by pass Mesa v2
My phone information :
base model : g960fxxu7csj5
Patch level: November 1st , 2019
One UI
Android 9 pie
I have a consumer cellular branded XT2052-5. I'm running Android 10 Build Number QPGS30.82-135-16 which has the Dec 1 2021 security patch. I have successfully unlocked my bootloader, installed ofox recovery.img, and patched the boot.img using Magisk app. I'd like to update my ROM to the latest security patch.
As I understand from this webpage: https://www.thecustomdroid.com/install-ota-update-rooted-android-device-guide/ one option is use the Android Settings -> Systems -> Advanced -> System Update to download and then install the OTA, but don't reboot until after running Magisk and installing on the new partition. However, while it seems to install "Software update unsuccessful, couldn't apply system update to moto e..." (not verbatim since the message disappears quickly). Note also that the update file size is listed as only ~65MB while the example screen in the instructions at thecustomdroid.com inedicate it sholud be >1.5GB.
Anyway, I have resisted patching the boot.img and installing it in the other A/B partition via the Magisk app and am wondering how to proceed.
Can someone help me?
Mike
I had the same issue when trying to update via OTA. After testing I realized that the reason I couldn't update was because of the custom recovery installed. So I started all over went back to stock firmware using a program called RSD Lite to remove custom recovery completely and updated via OTA then patched with magisk. I ditched the custom recovery since it is not needed if you are on stock firmware.
Just got the march security update. 490mb.
Flashed -nowipe the March update over the Feb.004 update without uninstalling Magisk which has worked before. Took awhile for the initial boot, but phone booted with no problem.
When I applied Magisk 23.301 to boot.img and flashed then the phone got stuck in a boot loop.
Starting over now with flash-nowipe. Plan to let the phone settle abit before rooting. Wondering if I should use the Magisk canary build and wait for the updated Kiris kernel.
swieder711 said:
Flashed -nowipe the March update over the Feb.004 update without uninstalling Magisk which has worked before. Took awhile for the initial boot, but phone booted with no problem.
When I applied Magisk 23.301 to boot.img and flashed then the phone got stuck in a boot loop.
Starting over now with flash-nowipe. Plan to let the phone settle abit before rooting. Wondering if I should use the Magisk canary build and wait for the updated Kiris kernel.
Click to expand...
Click to collapse
My phone went into bootloop today after updating Magisk (magisk update prompt), BEFORE march update. That was a bit odd. Maybe your bootloop has nothing to do with March update, but with the new magisk version being flashed is incompatible to certain modules.
Well hell, I am failing.....and understand the message, but dont understand why or what transpired....and not sure what bootloader the message refers to.....this is a factory flash....
Checking 'product' OKAY [ 0.000s]
Checking 'version-bootloader' FAILED
Device version-bootloader is 'slider-1.0-8062051'.
Update requires 'slider-1.1-8118264'.
fastboot: error: requirements not met!
Hmm, now not exactly sure what to do....8062051 is the bootloader from the 2nd February image, so not sure where to get 8118264 so I can update.......very odd.
***EDIT: OK I see thats the bootloader from A12L not from A12.......wtf!!!!
****RE-EDIT: PEBCAK here on my end.....doh! Working now
Same here, just checked and it showed up.
I was running into issues flashing the Factory image via Fastboot so I decided to try the FLASH method from the Android Flash Tool. That worked. But when I try to install the Magisk patch file, it fails and then I get stuck in a bootloop. So there you have it. I'm going to have to deal with no root until someone figures out what's going on.
swieder711 said:
Flashed -nowipe the March update over the Feb.004 update without uninstalling Magisk which has worked before. Took awhile for the initial boot, but phone booted with no problem.
When I applied Magisk 23.301 to boot.img and flashed then the phone got stuck in a boot loop.
Starting over now with flash-nowipe. Plan to let the phone settle abit before rooting. Wondering if I should use the Magisk canary build and wait for the updated Kiris kernel.
Click to expand...
Click to collapse
Once I disabled the Typhus ROM Control module in Magisk then my phone booted with root enabled with 24.304. Magisk stable probably works too.
TimFlex said:
Just got the march security update. 490mb.
Click to expand...
Click to collapse
This in more in line with the following thread which is where you need to bring this discussion. We really don't need another misleading thread that is merely a Magisc "how do I...?"
April 10, 2023 TQ2A.230405.003.E1 Global - Root Pixel 6 Pro [Raven] / all relevant links
Pixel 6 Pro [Raven] March 9, 2023 I recommend sticking with 33.0.3. Note that two users in my Pixel 7 Pro thread have said that 34.0.1 did not work correctly for them. Someone reported it to Google (added a comment about 34.0.1 to the existing...
forum.xda-developers.com
Same issue here. Flashed March factory image. No wipe flag. Flashed Magisk patched file. Stuck in bootloop.
Reflashed factory image and didn't flash boot image and I can boot up. I guess no root until this is fixed.
I downloaded the March Factory zip and transferred the boot.img to my phone and then patched it with Magisk Stable v24.3 (I transferred the patched boot.img back to Platform TooIs Folder on PC) I tried to fastboot flash the March OTA (would only get to 48% and fail) So I used the Android Flash Tool and let it install the factory image without wiping. Now on March build with no data loss I then fastboot flashed the patched boot.img and have root
I had the same problem with Feb v2 OTA sideload (Maybe because I had a custom kernel?) anyway, I think the Android Flash Tool will be my go to for future updates
jcp2 said:
I downloaded the March Factory zip and transferred the boot.img to my phone and then patched it with Magisk Stable v24.3 (I transferred the patched boot.img back to Platform TooIs Folder on PC) I tried to fastboot flash the March OTA (would only get to 48% and fail) So I used the Android Flash Tool and let it install the factory image without wiping. Now on March build with no data loss I then fastboot flashed the patched boot.img and have root
I had the same problem with Feb v2 OTA sideload (Maybe because I had a custom kernel?) anyway, I think the Android Flash Tool will be my go to for future updates
Click to expand...
Click to collapse
Can you upload your patched file by any chance?
tonyfiore75 said:
Can you upload your patched file by any chance?
Click to expand...
Click to collapse
This is for Magisk Stable - Not Canary!!
Thesis so much @jcp2 !
Does the uninstall Magisk, OTA, and then reinstall Magisk work with this update? If so, what version of Magisk do we know that works?
Last time I lost everything on my phone. Not trying to do that again.
mkhcb said:
Does the uninstall Magisk, OTA, and then reinstall Magisk work with this update? If so, what version of Magisk do we know that works?
Last time I lost everything on my phone. Not trying to do that again.
Click to expand...
Click to collapse
Edit>>>> As long as you're on stock kernel, Canary is fine.
jcp2 said:
IDK but 100% sure to stay on Magisk Stable and not Canary --- Canary will cause bootloops!
Click to expand...
Click to collapse
I rolled back to Stable and still cannot gain back root....
I sideloaded the March OTA then rooted successfully with 24.3, but I didn't do the magisk uninstall.
jcp2 said:
IDK but 100% sure to stay on Magisk Stable and not Canary --- Canary will cause bootloops!
Click to expand...
Click to collapse
Not accurate. Using latest Canary (24304) and updated fine. Sideloaded ota in recovery, reboot to let system update complete, reboot to bootloader and flashed patched boot.img. All is fine.
did you try the patched boot.img I uploaded a few posts back? Make sure you're on March update with Magisk 24.3 stable before flashing.
Hello xda. I'm thinking about rooting my note 9 pro.. I have the EEA firmware version latest Android 12 update.
V13.0.1.0.SJZEUXM
I'm thinking about grab the boot.img from the firmware, patch it via Magisk and flash it using fast boot. I mean without twrp. Will it be possible for this phone and this android version? I rooted my mi 8 lite this way and it work like a charm no twrp needed. Did you ever tryed this way to root your note 9?
I mean I can't find a stable twrp version.. Especially for Android 12 .
So if i try the method mentioned above will it work? I don't really need twrp for anything. Only need root.
Yes, if you simply follow the official Magisk install guide by TopJohnWu (patching the boot.img with the latest Magisk app and flashing it via fastboot - no need for recovery) it will work. In case you have to use apps which need SafetyNet (running on the official ROM).. that's a whole different story.. then you will need USNF, too, etc..
On MIUI 12 (Android 11) my phone was rooted with Magisk, I updated MIUI and of course the phone got unrooted, I redid the whole boot.img Magisk patching thing and tried installing Magisk, but now it doesn't work, I went around trying a bunch of different TWRP, including unofficial ones, nothing seems to be working.