edl
Magisk
edl | Magisk | |
---|---|---|
26 | 430 | |
1,400 | 44,310 | |
- | - | |
8.7 | 9.6 | |
11 days ago | 6 days ago | |
Python | C++ | |
GNU General Public License v3.0 only | GNU General Public License v3.0 only |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
edl
-
Rooting the Boox Tab Mini C
Open up QFIL (which should have been installed as part of the QPST tool). Click "Configuration" -> "FireHose Configuration" and in the window which pops up change the "Device Type" to UFS as informed by the article here "https://www.ereaderpro.co.uk/en/blogs/news/e-ink-product-follow-up-boox-tab-mini-c-and-page-versus-previous-generation". The article indicates that the device uses UFS2.1 as it's storage protocol. It also indicates that the device uses a Qualcomm® Snapdragon™ 662. In order to properly program the chip we need an appropriate programmer which is `prog_firehose_life_ddr_patched.zip`. The driver to communicate with the Qualcomm chip was originally found in a git thread (https://github.com/bkerler/edl/issues/200) attached to a comment as `prog_firehose_life_ddr_patched.zip` here: https://github.com/bkerler/edl/files/7991604/prog_firehose_life_ddr_patched.zip. To use this change the "Select Build Type" to be "Flat Build" and then click "Browse" for the "Programmer Path" and point it to `prog_firehose_life_ddr_patched.zip`.
-
Windows 11 has made the “clean Windows install” an oxymoron
YMMV, but in my experience it works flawlessly.
If that fails there are chip specific tools you can use to read/write to the right partitions, such as the fantastic EDL tool for Qualcomm devices:
https://github.com/bkerler/edl
-
Oneplus 7t resetted itself after update
EDL is the offical protocol used by support to debug and reset your phone. Issuing the following command should reboot you into fastboot.
-
Owning the Netgear M6 Pro MR6400
Sierrakeygen HOW-TO on Windows 1. Original information from https://github.com/bkerler/edl
- Cheap android phone I can run void on?
-
Oneplus 3 display remains black
As for tracking down the issue on your side, it would be a matter of setting up this and then creating a memory dump while in EDL mode. The "how to get logs out of this" part we'll have to figure out afterwards.
-
Sony Xperia XZ2 bricked
After flashed wrong abl from LG G7 to abl_a partition and reboot, my phone was bricked. No Flash mode nor fastboot, I was use paper clip and short to testpoint in mainboard, its recogized as QUSB_BULK_CID:0402_SN:XXXXXXXX. I can send hello packet to sahara (edl mode) and got these information when using EDL tools (https://github.com/bkerler/edl). Seem like Sony sake authencation and Secure boot prevented me load different loader to sahara, Is there anyway or who can find the correct firehose loader programmer file for this XZ2? :
-
USB > virtual machine connexion issues (windows 10) VM inside Virt manager/Virtual machine manager
I had this problem too, I find it simpler to use something like hirensboot CD (a windows live image) or an edl tool to directly flash the image from Linux, like this, first you'll need to decompress the image with this.
-
stuck on mi logo after flashing patched boot.img
You might be able to use bkerlers edl to unbrick the phone. https://github.com/bkerler/edl
-
OnePlus 9 Pro Hard Bricked, just like my heart :(
I did. Kinda funny that all the links in those search results are marked as linked. I tried every possible solution that I could find. Even this https://github.com/bkerler/edl but still no luck. Thanks for your reply though.
Magisk
- Google Fit APIs get shut down in 2025, might break fitness devices
- [Discussion] Can anyone ELI5 what is play integrity, what Google is doing to it, and does it only affect rooted users?
-
⟳ 4 apps added, 39 updated at f-droid.org
Magisk (version 26.4): The Magic Mask
-
⟳ 0 apps added, 15 updated at apt.izzysoft.de
Magisk (version 26400): Companion app for Magisk
-
Rooting the Boox Tab Mini C
At this point download locally the Magisk APK onto your computer found here: https://github.com/topjohnwu/Magisk/releases. Reboot your Tab Mini C by holding the power button until you see the power come back on and the default power on screen begin loading. Once it has fully booted copy the Magisk APK, `boot_a.bin`, and `boot_b.bin` files via USB. Make certain to have backups of the `boot_a.bin` and `boot_b.bin` files in case something goes wrong (such as you bricking your device) and you need the old firmware. Install the Magisk APK. For the rest of this we will be following a summarized version of the instructions here: "https://topjohnwu.github.io/Magisk/install.html". Once the Magisk app is installed open it and press the "Install" button. Then click "Select and Patch a File" and select `boot_a.bin` then `boot_b.bin` files to install Magisk on both. At this point one should rename them to be `magisk_patched-boot_a.img` and `magisk_patched-boot_b.img` based on which one Magisk patched to make it easier for you. At this point transfer `magisk_patched-boot_a.img` and `magisk_patched-boot_b.img` back to the main computer over USB. Open up QFIL and once again run `adb reboot edl`. FAIRLY QUICKLY to avoid errors click the "Select Port" button and click the USB port which the Tab Mini C is plugged into and then click OK. Still quickly click "Tools" -> "Partition Manager" and then click OK on the popup. Within the partition manager find `boot_a` and `boot_b`. For each individually right click on the partition and then click "Manage Partition Data". Then click "Load Image" and point to the corresponding `magisk_patched-boot_a.img` and `magisk_patched-boot_b.img` depending on which partition you're patching. Once both of them are patched, quit out of QFIL. Force the reboot of the device by holding down the power button. Open the Magisk app and click on "Install" at which point their should be a new option "Direct Install". Use that to install directly onto the device after which it should give you the option to reboot. Reboot it and you now have a wonderfully rooted device. Happy reading
- Magisk: The Magic Mask for Android
-
[ROOTED METHOD #2] Smali Patcher Guide for Android 7, 8, 9, 10, and 11 with a Magisk Rooted device
Install Magisk app onto your device: https://github.com/topjohnwu/Magisk/releases/download/v25.2/Magisk-v25.2.apk
- Magisk v26.3 Stable
-
[Help] I flashed magisk.apk and not the .zip by mistake and phone is bricked!
Magisk Version: Magisk v26.2
- Magisk version 26.2 released
What are some alternatives?
mtkclient - MTK reverse engineering and flash tool
Termux-ADB - Install ADB & FastBoot Tools in Termux!
sahara - A multi-platform tool for working with Qualcomm Sahara protocol using QT5 and libopenpst
Xposed-NetworkSpeedIndicator - Network Speed Indicator
kernel_msm-redbull - Kernel sources for the Pixel 4a (5G), Pixel 5 and Pixel 5a.
Riru - Inject into zygote process
streamlink - Streamlink is a CLI utility which pipes video streams from various services into a video player
safetynet-fix - Google SafetyNet attestation workarounds for Magisk
river - 🌊 Online machine learning in Python
LSPosed - LSPosed Framework
git - A fork of Git containing Windows-specific patches.
universal-android-debloater - Cross-platform GUI written in Rust using ADB to debloat non-rooted android devices. Improve your privacy, the security and battery life of your device.