Hi!
I’m the new owner of a Xiaomi Redmi Note 8T. I can’t use TWRP for installing eOS, because TWRP breaks it, badly. I’ve installed eOS 1.8.1 with the e-Recovery, and that works fine.
Now I want to root my device. How can this be done without TWRP? There’s some documentation on how to install Magisk without TWRP, by tweaking the Zip of the OS, which is to be installed. That looks awfully complicated. Are there any other options?
Cheers,
Volker
Hi,
You have to use fastboot to flash the “magisk-patched-recovery.img”
Which version of TWRP are you using?
Not every TWP version is equally suitable for every Android version!
I recommend not to use the current TWRP version 3.7.0 but an earlier version.
You can also install TWRP only temporarily and try to install Magisk-v25.2.zip with it.
Hi!
I’ve tried at least two TWRP versions (3.7.0 and 3.6.2), and eOS 1.7 and 1.8.1.
Anyone, don’t install TWRP temporarily. It breaks eOS to just install it. I’ve tried it, with eOS 1.8.1 being the installed version. I’ve went into recovery in order to see if it still asks for a password. I haven’t done anything. But that was enough to cause a weird problem again. It’s the settings app crashing immediately after starting it. I’ve had the same problem before, when using TWRP to flash eOS (1.8.1 and 1.7).
Bye, Volker
The subsequent installation of TWRP on an existing /e/OS ‘R’ or ‘S’ + eRecovery is often problem loaded. That’s why I wrote “Try it”. It failed for me as well.
However, a new installation from scratch with /e/OS e-1.8.1-r-20230206257804-dev-ginkgo willow + TWRP + magisK worked on the first try.
The fact that the BlissLaucher app shuts down with the message “BlissLauncher keeps stopping” and the screen flickers is not unique to the Note 8T, but has already happened to me on several other devices with /e/OS.
All in all, a rooted /e/OS is not necessary for me.
I thought temporarily using TWRP meant fastboot booting its img. Would allow for flashing or other task without it ever being installed. Not sure nowadays.
Not aware of any Magisk zip tweaking. Just a Magisk.apk copied to Magisk.zip and flash / sideload.
Usually works but no longer recommended.
How to in samsung galaxy note10+ (d2s) ?
Unfortunally rooting instruction are very few for /e/OS and it is the only way to have a smoot migration from a smartphone to another with titaniumbackup
Hi. You can root eOS with the eOS-Recovery. In order to do it like me, you need ADB installed on a computer.
You boot into the eOS recovery. Then you chose “Apply Update → Apply from ADB”. On the computer, do “adb sideload Magisk-vXXX.zip”. Replace “XXX” with your Magisk version. Then touch the arrow to the left (upper left corner) and do “Reboot System Now”.
You can probably do it without ADB, although I haven’t tried it. You’d need to copy the Magisk package (Magisk-vXXX.zip) to the SD card of the phone and chose to flash it, somewhere from in the eOS recovery.
Good luck!
Volker
I am in recovery 2.7 (d2s).
“adb devices” returns me “xxxxxxxxxx sideload”
“adb sideload magisk_xxxxx.tar” returned me after some seconds “error: protocolo fault (no status)”
Hmmm… That doesn’t tell me anything. “adb devices” should print a hex code and “device”. There’s something fundamental wrong. Have you tried the command when your phone is running normally? What do you get?
Cheers, Volker
must be a .zip, the recovery-e cannot manage .tar that are for Odin…
xxxxx… is my hex code…
the phone seems work ok until I try to sideload
also renaming the patched file from magisk to .zip gives me the same error…
Maybe that the AP file I patched with magisk is corrupted (downloaded from internet): can I download th AP file from my phone or extract from /e/OS downloaded image ?
What is an AP file?
You can download the latest Magisk .apk from here: Release Magisk v28.1 · topjohnwu/Magisk · GitHub
Then rename it to .zip and try to sideload again. Hope this helps.
“AP” files are .TAR files to use with Odin3 Windows or Odin4Linux or Galaxy-Flasher, the ultimate graphical tool for Samsung devices
Hi. I don’t completely get what you’ve done. But your’e not supposed to patch anything with Magsik. You install the original Magisk .apk file (renamed to .zip) in the eOS-Recovery like I’ve described.
Cheers, Volker
depend on the device type, for some (like my old samsung s4) official instruction is to install the app from the store, then patch the boot.img include in the /e/OS.zip using the app, and flash it to the device.
without TWRP, it is possible using fastboot or for Samsung devices you can use heimdall, heimdall-front-end,thor, Odin3 windows, odin4linux or Galaxy-Flasher, the ultimate graphical tool for Samsung devices
Thank you very much !!
Any instruction I’ve found was different but with eOS-recovery + e\OS\ + d2s seems that as you mentioned is so simple… just apply update adb in eOSrecovery and “adb sideload magisk.zip” and complet the setup with magisk app after reboot !! 
I hope will be so simple for every device (not only d2s) with e\OS\ and it’s recovery…
I hope also that in the future eOS-recovery will be able to take encrypted full nandroidbackup and restore
Yes, a Nandoid backup feature, like in TWRP, is something I miss in the eOS recovery as well.
Cheers, Volker
