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.
Related
Hello
My Device is running on Stock Android Q BN 11.0.5.0
Recently i installed magisk in my device (keeping OTA).
When i install Magisk Module for Internal audio recording and reboot device it was stucked in bootloop.
Then i flashed stock boot img
After flashing i reboot the device and it is rebooted successfully. But Magisk and Root Access has gone.
Then after i again flash Magisk patched img created by Magisk installer but this time it is again stucked in bootloop.
I tried to flash zip with temporary Twrp but problem is not solved.
Currently i dont have Magisk installed.
Please Help Me to gain root access again
Thank you.
Please reply or DM me https://t.me/adarsh_ad007
1. Reboot to bootloader (fastboot mode) and boot into TWRP (I prefer 3.3.1-5 4pda_edition) in fastboot, go to Advanced -> File Manager -> data -> adb - > modules, and delete all files (directory) belonging to a problematic module
2. Reboot to fastboot and boot into stock boot.img thus checking that it boots;
3. if stock boots, reboot to bootloader and try to boot into magisk_patched.img thus checking that it boots;
4. After that you can make root permanent in MagiskManager, if you wish
thank you bro it diid not work. i tried but not working
Aerobatic said:
1. Reboot to bootloader (fastboot mode) and boot into TWRP (I prefer 3.3.1-5 4pda_edition) in fastboot, go to Advanced -> File Manager -> data -> adb - > modules, and delete all files (directory) belonging to a problematic module
2. Reboot to fastboot and boot into stock boot.img thus checking that it boots;
3. if stock boots, reboot to bootloader and try to boot into magisk_patched.img thus checking that it boots;
4. After that you can make root permanent in MagiskManager, if you wish
Click to expand...
Click to collapse
not working
adarsh.ad007 said:
not working
Click to expand...
Click to collapse
Which step is not working? What is final result? How can you get help if you do not describe anamnesis? No telepathists here, as far as I know.
Aerobatic said:
Which step is not working? What is final result? How can you get help if you do not describe anamnesis? No telepathists here, as far as I know.
Click to expand...
Click to collapse
I did everything what you said but problem is still there.
adarsh.ad007 said:
I did everything what you said but problem is still there.
Click to expand...
Click to collapse
Ohhhhh, why should we torture you to get answers needed to help you?
What does MagiskManager show when you boot to supposedly correct magisk_patched.img?
Can you attach screenshot or describe in detail?
Aerobatic said:
Ohhhhh, why should we torture you to get answers needed to help you?
What does MagiskManager show when you boot to supposedly correct magisk_patched.img?
Can you attach screenshot or describe in detail?
Click to expand...
Click to collapse
Thanks for you support and attention dear.
Actually i flashed PE ROM and then install magisk. Now it works.
And i was booting correct patched img.
I created it via magisk manager myself.
adarsh.ad007 said:
..And i was booting correct patched img. I created it via magisk manager myself.
Click to expand...
Click to collapse
Maybe there was still something that skipped your attention. Pls look at scenario:
- patch stock boot image using MagiskManager with, let us say, Magisk 20.1; boot this patched image, make direct install - root got;
- update Magisk to. e.g., 20.3 installing Magisk-v20.3(20300).zip (root got, everything ok);
- play with new Magisk modules, install wrong version, get bootloop;
- make some otherwise correct steps, like reflashing stock boot;
- finally try to get root with boot image previously patched by Magisk 20.1.
Result: no root, MagiskManager does not accept Magisk 20.1., it expects boot image patched with 20.3
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
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?
Hello forum, I have been trying to root my motorola G6..
After much struggle, getting stuck in a boot loop and other issues I finally have restored stock roms and now have build PPS29-118-15-11 installed. So at least the phone works again My bootloader is unlocked.
But I still want to root it.
I think I understand the procedure well enough, but I am unsure of the correct/best versions I need for the ROMS/boot, Magisk, and TWRP.
ROMS/boot:
I found a youtube with instructions for updating Android v9
But I haven't tried it as this recommends a boot img:
OPS27.104-15-10_no-verity_boot.img
OPS27.104-15-10_no-verity_boot.img | by dejello for Moto G6
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
I am reluctant to use the above as it looks to be a downgrade from my current version 29-118-15-11.
Also, I thought that the filename prefix "O" indicated oreo instead of "P" for pie? So would this be a version 8 file?
TWRP:
Similarly, I am not sure if I am using the right, or best TWRP version. I currently have twrp-v3.2.3-ali.img
I flash this (with fastboot) and it works but shortly after I encounter the "no command" error (when booting to recovery) and I have to redo it. I am NOT overwriting it with a stock recovery.img.
I have also run into the "encryption password" problem, where I am unable to provide one to decrypt the data partition. So I can't backup the data with twrp (something I really would like to do).
Magisk
I have Magisk-23-0.zip
But I saw a post from brunogroa that recommends installing Magisk 19 and updating it to 23 later. Is this something that is required or can I just install v23?
So, I am looking for the correct versions for ROM, Magisk and TWRP to use, given that I have installed PPS29-118-15-11
Any assistance will be greatly appreciated.
Well I finally have it I think. I noticed a comment in
[GUIDE][ROOT][Moto G6][ALI] TWRP, Root, and Magisk installation guide. by djello
"(you may not need a modified boot image for Magisk)"
When using PIE instead of OREO.
Being an optimist, I gave it a try and it worked... I installed Magisk and was able to verify root access using the Root Checker Basic App. Kept stock boot img.
This is probably not too amazing for the old hands but us newbies need a break every now and them
So in the end, all I had to do was:
(0) Unlock bootloader
(1) Install stock PPS29-118-15-11
Done earlier with another version of twrp.
Install TWRP 3.5.2
(2) fastboot flash recovery twrp-3.5.2_9-0-ali.img
(3) Use twrp to install Magisk
adb push Magisk-v23-0.zip /tmp
Boot phone into recovery and use twrp to install Magisk
(4) Boot the phone into System and verify Magisk is there and use Root Checker App to confirm I am now rooted.
Issues:
I noticed that a security update for
PPS29-118-15-11-5 failed to apply.
The phone boots into recovery mode and asks for the decrypt password. I don't know the password to decrypt data and how to proceed from here.
I suspect that if I flash the stock recovery img the security update might work. If anyone knows please comment ; I will research this also and maybe just try it.
pdpantages said:
Well I finally have it I think. I noticed a comment in
[GUIDE][ROOT][Moto G6][ALI] TWRP, Root, and Magisk installation guide. by djello
"(you may not need a modified boot image for Magisk)"
When using PIE instead of OREO.
Being an optimist, I gave it a try and it worked... I installed Magisk and was able to verify root access using the Root Checker Basic App. Kept stock boot img.
This is probably not too amazing for the old hands but us newbies need a break every now and them
So in the end, all I had to do was:
(0) Unlock bootloader
(1) Install stock PPS29-118-15-11
Done earlier with another version of twrp.
Install TWRP 3.5.2
(2) fastboot flash recovery twrp-3.5.2_9-0-ali.img
(3) Use twrp to install Magisk
adb push Magisk-v23-0.zip /tmp
Boot phone into recovery and use twrp to install Magisk
(4) Boot the phone into System and verify Magisk is there and use Root Checker App to confirm I am now rooted.
Issues:
I noticed that a security update for
PPS29-118-15-11-5 failed to apply.
The phone boots into recovery mode and asks for the decrypt password. I don't know the password to decrypt data and how to proceed from here.
I suspect that if I flash the stock recovery img the security update might work. If anyone knows please comment ; I will research this also and maybe just try it.
Click to expand...
Click to collapse
I am stuck in a similar position.
SOLVED IT!!! Followed all of the steps that you posted except I installed Magisk with the patch method because I couldn't get the zip file to push onto the device. Kept getting a read only error, maybe because it wasn't rooted?
Anyway, I am rooted now!!!
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??