Here is a fastboot bootable image to boot you into Magisk core-only mode in case you bootloop due to flashing a bad module and TWRP is not enough.
Once in fastboot:
fastboot boot image-newpixelxl.img
You will boot with root but modules disabled. If something additional is needed, once booted to core-only, unzip the attached zip onto your pc where you can run ADB/fastboot and run the bat file. It will push .disable_magisk to your cache folder so that your modules will be disabled even after a reboot (zip says crosshatch but will work on any phone)
Boot image uploaded 11-4-19
https://www.androidfilehost.com/?fid=4349826312261618461
Hey so this would save my life but the boot image attached couldn't be flashed through fastboot and then I realized that the flashing command is mispelled. It should be
fastboot flash boot image....img
So this file didn't quite work, it makes Magisk Manager crash so I can't uninstall a conflicting module. I tried flashing the latest boot.img from the december update and it's enough to boot the phone but it disables magisk, obviously. Is there anyway you can update this file to the latest image? Pleaaaase
EDIT: I ended up reflashing the magisk patched image and manually deleting the folders of my conflicting modules.
Related
guys please give me noob friendly instructions for installing magisk latest ver on my lenovo p2 15.1 latest build .
Same
First make sure you have USB debugging enabled on your phone, then install ADB on your PC. Connect the phone to the PC and in the installation folder (ADB > platform-tools) shift right click and choose Open command window here. Type adb devices and authorize your PC on the phone. Download the ROM and extract boot.img from it, transfer it to your phone. On the phone install Magisk Manager and patch the boot.img (Install > Patch boot image). Transfer patched_boot.img back onto the PC (to the ADB > platform-tools folder), then boot your phone into fastboot (VOL down and POWER buttons). Repeat the Open command window here step and type fastboot flash boot patched_boot.img. Reboot your phone (fastboot reboot). You are now rooted on custom ROM.
After installing magisk , do I need to install any module to prevent boot loop like f2fs loop module etc .
Check if you can install modules. If you're facing problems, then you will need to change a few things. The "cannot mount magisk_merge.img" issue for example can be solved by patching and flashing boot image from here https://forum.xda-developers.com/lenovo-p2/development/kernel-f2fs-upstreamed-kernel-twrp-t3845976. I tried tinkering with modules for it and ended up bricking my phone. I would also recommend using TWRP from this thread, it got rid of my second problem (which I now forgot).
Just remember that you will need to flash the patched custom kernel after any ROM update.
I found a way to install twrp when you are trying to flash recovery image as boot image (there is a thread with all the instructions) So, i've tried final steps:
fastboot flash boot twrp.img
fastboot reboot and pressing vol up to boot recovery and flash recovery installer
Surprise, I enter to fastboot mode again when reboot, no matter if i want to boot normally or recovery, always reboot to fastboot.
Then I tried some things and finally found a way to install TWRP.
1. Copy boot.img to internal storage
You can copy to internal or external, whatever, if you have downloaded a firmware just copy it
Here is boot for android 10: https://drive.google.com/file/d/1zjOY1urQ4Zp3xNvgZM6Y1fm0kYCZ2iYs/view?usp=sharing
2. Download and install magisk manager
I used lastest version from magisk official site
Open magisk and click select and patch, wait until finished and copy the magisk patched boot to your pc (same folder as your minimal and fastboot)
3. Install patched boot
Type these command
fastboot devices (you can skip this one)
fastboot flash boot magisk_patched.img
fastboot reboot
4. Install Smart Flasher
Go to play store an search smart flasher
or there is the link: https://play.google.com/store/apps/details?id=com.smartpack.smartflasher
5. Flashing TWRP installer
Open app and click flash icon and search your TWRP installer, just wait and in a few minutes you will have TWRP installed
6. Install SHRP (optional)
SHRP is the best for me, you have a lot of extra features (manage magisk modules, a better file explorer, customization)
After you finished TWRP installation, just reboot to recovery and flash SHRP installer, and enjoy
It maybe seems tedious, but trust me, it's easier than be fighting against fastboot mode, sorry if i have bad english, i tried to explain it the best i could.
Is there TWRP for EMUI 9.1? My device is BND-L21. I've recently unlocked my device with PotatoNV and now I'm stuck here trying to find a TWRP image compatible with my device so I can install Magisk. Thank you
I've solved this issue by patching the twrp recovery image in the Magisk installer menu. Magisk will be enabled after this. The problem is, that you won't able to boot into the recovery after that. When you flash the unpatched recovery image again, magisk won't be activated anymore, but you'll be able to boot into twrp again.
First step:
Boot into fastboot mode
adb reboot bootloader
Click to expand...
Click to collapse
Second step:
You can use my attached patched image file and flash it in fastboot mode (Magisk v23.0):
fastboot flash recovery_ramdisk magisk_patched-twrp.img
Click to expand...
Click to collapse
Last step and important to activate magisk:
Boot into the recovery. You won't see the recovery, so don't worry about that.
adb reboot recovery
Click to expand...
Click to collapse
After that, magisk should be active
Just for your information:
--------------------------------------------------
The unpatched twrp is booting, but doesn't decrypt the data partition and is not able to flash magisk.zip, even if it seems that everything works fine when installing the zip file:
fastboot flash recovery_ramdisk unpatched_twrp.img
Click to expand...
Click to collapse
I also attached the original emui 9 recovery,:
fastboot flash recovery_ramdisk recovery_ramdisk.img
Click to expand...
Click to collapse
You can also patch the recovery_ramdisk.img in Magisk and use it to gain root access if you like.
But remember: you wont be able to boot into recovery if you do this, until you flash the unpatched file again.
jonnymcweed said:
I've solved this issue by patching the twrp recovery image in the Magisk installer menu. Magisk will be enabled after this. The problem is, that you won't able to boot into the recovery after that. When you flash the unpatched recovery image again, magisk won't be activated anymore, but you'll be able to boot into twrp again.
You can use my attached patched image file and flash it in fastboot mode (Magisk v23.0):
The unpatched twrp is booting, but doesn't decrypt the data partition and is not able to flash magisk.zip, even if it seems that everything works fine when installing the zip file:
I also attached the original emui 9 recovery,:
You can also patch the recovery_ramdisk.img in Magisk and use it to gain root access if you like.
But remember: you wont be able to boot into recovery if you do this, until you flash the unpatched file again.
Click to expand...
Click to collapse
Can you upload boot.img file please.
jonnymcweed said:
I've solved this issue by patching the twrp recovery image in the Magisk installer menu. Magisk will be enabled after this. The problem is, that you won't able to boot into the recovery after that. When you flash the unpatched recovery image again, magisk won't be activated anymore, but you'll be able to boot into twrp again.
You can use my attached patched image file and flash it in fastboot mode (Magisk v23.0):
The unpatched twrp is booting, but doesn't decrypt the data partition and is not able to flash magisk.zip, even if it seems that everything works fine when installing the zip file:
I also attached the original emui 9 recovery,:
You can also patch the recovery_ramdisk.img in Magisk and use it to gain root access if you like.
But remember: you wont be able to boot into recovery if you do this, until you flash the unpatched file again.
Click to expand...
Click to collapse
Is this device specific ?!
My device is Honor 7x(BND-AL10); EMUI - 9.1.0; Android - 9
kurangan said:
Is this device specific ?!
My device is Honor 7x(BND-AL10); EMUI - 9.1.0; Android - 9
Click to expand...
Click to collapse
I don't know to be honest.
My device is BND-L21.
You can try to patch my unpatched twrp or original ramdisk file and flash it via fastboot as I described it.
Maybe you can also extract the files from the specific rom image of your device, if you can find it.
I want to use Magisk and update boot.img to the patched boot.img. Unable to use fastboot to complete the process.
Background
I have updated the Android 6 OS on Galaxy Tab S MT-800 device to Android Nougat 7.0. Now the SafetyNet test fails. Read about Magisk to help with this issue.
Steps taken:
1. Installed TWRP via ODIN
2. Downloaded Magisk 25.2 and flashed it using TWRP
3. Granted storage permissions and clicked on Magisk on Tablet
4. Magisk installation menu walked walked through the download
5. Within Magisk I created a modified boot.img
6. Copied Boot.img to PC
7. ADB identifies my device
8. Fastboot does not identify my device. Says <waiting for device>
Qn: How can I flash the modified boot.IMG without using Fastboot flash command?
Hiya folks.
Well that was a fun brick - And I still don't really know what I did wrong.
I have a T-Mobile LE2127 and it was on Android 12 - I don't need to use it yet, so I am happy to play with it. Bootloader and SIM are unlocked, I can fastboot boot magisk_patched-25200_JdBlm.img to get root, and I can fastboot twrp-3.6.2_11-0-lemonadep
In TWRP-3.6.2 I used dd to grab the boot.img dd if=/dev/block/bootdevice/by-name/boot of=/usbdrive/boot.img and I patched that with the latest Magisk (1)
I tested to see if that would boot up with a fastboot boot and it worked fine - Sooo, I decided to "fastboot flash boot" it and then everything went very wrong.
The boot told me: "Qualcomm CrashDump Mode / da-verity device corrupted / verify_ctr" -- And then it went into an infinite bootloader loop which wouldn't let me into EDL mode (2)
When I was in the infinite loop, I couldn't "fastboot boot" anything, it told me it wouldn't load anything with: error: FAILED (remote: Failed to load/authenticate boot image: Load Error)
Eventually, I used the very useful MSM/lemonadept_22_O.04_210409 package to recover it and now it's working again. (3)
So - What did I do wrong? -- I suspect it may have patched my boot to slot B but I am not sure that should have mattered too much, I popped one back into Slot A as well.
I see a thread on using "adb reboot "dm-verity enforcing" but I didn't have to do that with things I booted from rather than flashed... And I couldn't get into adb at that point anyway. Does this mean my patched boot.img will not do what I want it to anyway?
Anyway, I should stop speculating and ask the experts!
Thanks.
(1) https://www.droidwin.com/extract-boot-img-directly-from-device-without-downloading-firmware/
(2) https://www.droidwin.com/boot-oneplus-9-pro-9r-9rt-to-edl-mode-5-methods/
(3) https://forum.xda-developers.com/t/oneplus-9-11-2-22-2-t-mobile-msm-download-tool.4276119/ -- [No instructions, but just run it as admin, connect phone and it does it all].
What I do is in bootloader mode, fastboot boot twrp, in twrp I install magisk.zip, then reboot system and tap on magisk app and follow prompts. Done
If you have the boot image, place it in your root folder on the phone. Use the magisk manager app ( install on phone) to patch the boot.IMG. Place the patched boot.IMG on your PC. Should be in downloads folder. Fastboot boot this patched IMG. It should boot your phone. Go to magisk manager app and install magisk directly. ( option in manager install). Reboot -- done.
kjslabber said:
If you have the boot image, place it in your root folder on the phone. Use the magisk manager app ( install on phone) to patch the boot.IMG. Place the patched boot.IMG on your PC. Should be in downloads folder. Fastboot boot this patched IMG. It should boot your phone. Go to magisk manager app and install magisk directly. ( option in manager install). Reboot -- done.
Click to expand...
Click to collapse
Ah! That worked and was very simple, thanks... For some reason in my head, I was thinking that Magisk would only patch the booted image, which would be pointless; but it patched the real phone one.
I assume I'll just have to do the same every update.
Thanks!