Hi,
with the latest Magisk update I noticed the missing Magisk Hide and SafetyNet fix. So I decided to go back to Magisk 23. After a few unsuccessful attempts, I don't know what happened but now my phone is no longer rooted. So I tried some usual methods to re-root the device but nothing to do, still no root
I have used boot.img patching way with Magisk but when I send ADB command "fastboot flash boot magisk_patched.img", it seems to work fine but after reboot there is no root
So I tried the other method by booting the device with patched boot.img using ADB ("fastboot boot magisk_patched.img") then I open Magisk Manager but in the installation section there is no "direct install" option as it should be.
I also tried flashing Magisk.zip via TWRP as I did long ago and TWRP seems to do the job well but after rebooting again no root...
Any suggestions?
Nothing??
Related
Hi, I have been using Magisk for last one month. Everything worked fine. All my root apps worked like a charm. Today I tried to install an OTA update. For which I tried to restore stock boot image with Magisk. After Magisk showed, 'restore successful' message, I tried to install the OTA (April), but I couldn't, it kept on showing installation error.
I then tried to reboot my device but it got stuck in bootloop.
Using MiFlash Tool, I flashed back the stock ROM which restored everything including the bootloader but retained my data (user apps and settings, Magisk and other root apps were also retained.) I then updated my stock ROM with the OTA.
Then with ADB, I unlocked the bootloader and flashed the patched boot image file of April.
After booting up first time after the patch, Initially the Magisk and root checker, both showed me root access, but after a reboot, the root access was gone. The root checker now says - Root access is not properly installed on this device.
Magisk homescreen says, Magisk is Latest Version v16.0 but Magisk is not installed. On clicking the install button, it only shows two options - Download Zip only and Patch boot image file.
What should I do to get back my root access?
You have to reflash Magisk manually after every OTA update.
hi i installed magisk with different ways but they didn't work firstly i wanted to install magisk without twrp recovery or any custom recovery
so i tried the first method
getting boot.img from my firmware and coping it into the device
then patching it with magisk
after that flashing it with adb
but adb doesn't detect my phone in fastboot mode and i tried installing drivers and every thing so i flashed it using odin
and after that i see that magisk is not installed
my phone is saumsung a505f bootloader unlocked
so i tried patching AP file from the firmware and that is the last method i had tried
coping the AP file to the device
patching it with magisk
getting device into download mode
and install the whole firmware using the patched AP
after that wiping the phone data
then after the normal installation i see that magisk is not installed
what did i miss and is there anyother way to install it
Hello.
I'm a beginner at thing like this. Please your understanding.
I choose Magisk because the SafetyNet bypass it offered.
My device is SM-G532G with Android 6.0
How I installed Magisk:
1. I patched the boot.img and flashed it using Odin. Not with ADB because I can't boot into fastboot mode. I don't know why.
2. Magisk succesfully installed and it work properly with root apps.
The only problem is that my device can't pass the SafetyNet. It also told me that my device is not official when i booted to Download Mode.
Then I tried installing Magisk with the zip file after I clean flash my device with the official firmware. I didn't solve the problem.
I have some guess about the problem.
1. I should flashed the boot.img with ADB.
2. Since I can't boot into fastboot mode, I'm not sure whether the bootloader was unlocked or not. I got the error "Can't mount /data" message. The problem might have something to do with that.
What I want to ask:
1. Does installing Magisk using the patched boot.img and the zip file brings different outcome?
2. Is it possible to fastboot my device?
Regards.
Hi!
I have pushed my MI 9 into bootloop and need help to get it back working.
The bootloader is unlocked, Magisk and TWRP are installed. I tried to install the latest Universal SafetyNet Fix, but instead of installing it inside Magisk I have "installed" the ZIP with TWRP and wiped the delvik cache. Now the phone is in bootloop.
In the Universal SafetyNet Fix- threat I got the hint to reinstall the stock boot.img, but I am unsure how to do this and which file to use.
Can I just use one of the boot.img linked in this threat, e.g., the one in 10.2.24.0?
[Root images] Boot 10.2.24.0 & 10.2.9.0 & 10.2.26.0
Version 10.2.26.0 Version 10.2.24.0 ------------ > Stock/Root Version 10.2.9.0
forum.xda-developers.com
and install it with fastboot, i.e., "Fastboot flash boot.img" ?
Or is there another solution to my problem, e.g., uninstall the safetynet-fix-v1.1.0.zip ?
Well, I gave it a try, but it doesn't work. Now the phone doesn't even show the MIUI logo anymore. Fortunately, I had made a backup with TWRP before I tried this, and I could reflash the old boot.img with
fastboot flash boot boot.emmc.win
Now at least the MIUI logo appears again, but my original problem is still there, the phone still doesn't boot completely, but resets and goes into twrp.
Problem solved by deleting the safetynet-fix folder. Thanks to Durete for this tip!
How to Uninstall Magisk Modules Using TWRP Recovery
Removing the Magisk module manually causes bootloop. You can easily uninstall Magisk modules using TWRP recovery without resetting your device.
www.droidviews.com
Durete said:
The easy way....
How to Uninstall Magisk Modules Using TWRP Recovery | DroidViews
Click to expand...
Click to collapse
Hopefully someone can help me out here:
I'm on Mi 9T (davinici) with xiaomi.eu-cROM 12.1.2 (Stable) and OrangeFox Beta R11.0 Recovery. Bootloader is obviously unlocked.
I followed the guide for Magisk v22.0 and installed the apk first, opened it and it says
"Ramdisk No"
Alright, so I have to patch the recovery.img.
In Orangefox Recovery I open the Terminal and extract recovery.img with
Code:
dd if=/dev/block/bootdevice/by-name/recovery of=/sdcard/recovery.img
Reboot to system and I chose "Install" in Magisk, "Recovery Mode" is already selected, click "Next" and I select the newly created file "recovery.img". Magisk does it's thing and I have "magisk_patched_cOdEy.img" in my Download folder which I pull with adb.
I reboot to fastboot mode and
Code:
fastboot flash recovery magisk_patched_cOdEy.img
which works w/o problems and reboot again.
But when I open Magisk it still says it's not installed.
So, I check the guide under Magisk in Recovery, where it gets really confusing, but from what I got is that I need to start the phone with recovery button combo (Power+VolUp for Mi 9T) pushed and release at splash screen so Magisk is activated. I try this multiple times since it's really hard with the timing (milliseconds too long it kicks me into fastboot mode. idk why).
Can someone figure out what went wrong/what I did wrong? Never had problems with earlier Magisk versions.
Follow up question: There's some warning about going back to stock recovery will brick your phone in installation. Does that include installing OrangeFox again? I'm 95% sure it doesn't, but would be nice to know before I do it.
Some Xiaomi devices have their bootloaders set up so that it will accept an initramfs that was manually added to the boot image. Therefore, on these devices you'll need to patch the boot image even though there's no ramdisk. Try that.
Didgeridoohan said:
Some Xiaomi devices have their bootloaders set up so that it will accept an initramfs that was manually added to the boot image. Therefore, on these devices you'll need to patch the boot image even though there's no ramdisk. Try that.
Click to expand...
Click to collapse
Can I reinstall OrangeFox or TWRP recovery then?
I'll report back, when I tried it.
edit: So this actually works and I was able to enter TWRP recovery again after flashing.
edit 2: Now WiFi is not working anymore. fml.
edit 3: For anyone stumbling over this thread. Nothing worked, I had to do a compelte wipe and then flash Magisk "the old way", by renaming the .apk into a .zip and flashing it in recovery. That did the trick without any probems and I'm rooted now after quite a hassle.
yeah, I stumbled upon it. And I'm having the same/a very similar issue. I was very happy with Magisk up to v22 when the problems began.
I'm still at DerpFest based on Android 9.0 (from 2019 ) and TWRP-3.4.0.0.I had Magisk running since it was 19.4, upgraded it multiple times already. So didn't think much about updating to 22. Then, it said the same: no ramdisk. Pitty. OK, so I went ahead and let Magisk patch the TWRP.img I still got on my phone and flashed the patched TWRP onto recovery. Upon booting, Magisk is there, but no wifi, no sound, no light sensor, ... LTE works, though .
Anyways, I just want to get my old setup back, so I thought, I just flash the original TWRP again. According to the Magisk documentation, if I don't press any button, it should boot to Android without Magisk. Well, it always boots into Android+Magisk disregarding that. If I flash the original TWRP.img back, I always end up in TWRP. So, the order is: boot.img -> magisk-modified-recovery.img -> (boot.img?) -> system. How can I get the behaviour Magisk advertises?
And yes, I tried uninstalling Magisk (via uninstall.zip meythod), which said it would uninstall, but actually didn't. I also flashed different boot images (a backup I had in TWRP, the original boot.img I've found in the DerpFest zip...) to no avail.
So, Immortal68, which of the many wipes one can do did result in the old behaviour? And: now that you have Magisk22, does it say "Ramdisk: yes" again?