Download Adb Fastboot For Android Ndk Magisk Module
Marylee Guffy
So first, your device is stuck in a bootloop after installing a wrong module. What to do and what do you need? 1- stock boot img So the boot img file that you used to patch it using magisk at the beginning to root your device is necessary.
d. Now you're in safe mode, go back to power shell and type: adb devices ( again to make sure the device is connected) Then type: adb shell magisk --remove-modules Press enter and your device will reboot and all of the modules will be gone. Reinstall what you need and use your device normally again.
We run a bit offtopic but there is probably an easy way to
a) change the order and set nix to the second position (it is not in /.profile)
b) exclude adb and fastboot from PATH
c) install only adb and fastboot from nix (nix android-tools)
The title says my problem, i accidentally flashed magisk.zip through fastboot instead of magisk.img and now i have a bootloop please help i don't care how and i don't care about the data i just want it working again, if it's any help bootloader's unlocked and it had the latest PixelExperience plus build by ponces it already had usb debugging enabled but i also can't reboot to recovery and as it's to expect, fastboot and adb don't recognize the device because it isn't booting to the system and i can't access recovery mode, i know it was a dumb error but i need help, this also was my first time rooting but i had a typo that led me to this, i had no magisk modules and this was my first install, i didn't find a custom recovery for it so when this happened it also had no custom recovery so i don't have a custom recovery and i don't know what to do if it helps i also run linux and i have the 4 GB of ram/128 GB of storage version pls help! i'm desperate!
I tried to root, patched an image, but i also had a magisk.zip in case i needed to sideload it, anyways, i was gonna flash magisk.img using fastboot flash boot magisk.img but instead i put a typo and it resulted fastboot flash boot magisk.zip, i was worried but i expected it to work anyways, but no i'm on a bootlooop and i can't access recovery nor turn off the device, i'm worried that it might be really badly damaged
Do I understand that I should patch boot.img of stock mui android 13 room, still being at my current os (android 12)? I suppose it is because of safety considerations and I should download magisk, patch the file and transfer to my machine. Is that correct?
In any case you will need the ADB and Fastboot Utilities. Most Linux distributions provide them in a package named android-tools, or split in two packages android-tools-adb plus android-tools-fastboot. For other systems you can find hints at Stack Exchange: Is there a minimal installation of ADB?
35fe9a5643