Related
Hello guys,
I made an update in TWRP and installed Havoc 2.4 to try it. After 1 hour I restored my backup and changed back to MIUI. I couldn't log in, so I cleaned the keyfiles to set a new pin.
I reflashed new Beta (25.4 MIUI - Xiaomi.eu) ROM and Magisk but root does not apply on my device... What is wrong? Seems that it's not possible to root anymore... Its does not give me any fails when installing the magisk 18.1 zip in TWRP...
thanks in advance
Have you tried a simple reboot? Usually it takes a reboot more to apply.
no it's not that. now its always booting into twrp when I try to flash magisk
makmak001 said:
no it's not that. now its always booting into twrp when I try to flash magisk
Click to expand...
Click to collapse
Extract the boot.image from the rom and place it in your downloads folder.
Now with Magisk Manager , download and install Magisk to that boot image
Magisk will write root to the boot.image file and then will automatically flash the the updated boot image, and restart to system >>> Issue resolved.
I fixed it by wiping data... now its working
tsongming said:
Extract the boot.image from the rom and place it in your downloads folder.
Now with Magisk Manager , download and install Magisk to that boot image
Magisk will write root to the boot.image file and then will automatically flash the the updated boot image, and restart to system >>> Issue resolved.
Click to expand...
Click to collapse
I have the same problem with magisk, after weekly update and after magisk installed, boot only TWRP. I tried with18.1 version but will not recognise. Boot image and Magisk 19.1 are in downloads but no success. Anyway, with this weekly update all people have loosen magisk, I have read in Xiaomi forum.
slave2007 said:
I have the same problem with magisk, after weekly update and after magisk installed, boot only TWRP. I tried with18.1 version but will not recognise. Boot image and Magisk 19.1 are in downloads but no success. Anyway, with this weekly update all people have loosen magisk, I have read in Xiaomi forum.
Click to expand...
Click to collapse
Nope, no issues on my Mi 8. Here is the trick. When updating do not flash Magisk until you out have booted into the system and ran updates and deleted cache and trash, then reboot to recovery and flash Magisk.
If the method that I described before in the previous post doesn't work, then unpack the boot image from the update and flash it to boot in recovery then flash Magisk Canary debug.
I have been doing this for every weekly update using the beta ROM.
I had an issue just once that was resolved by flashing SuperSu, booting to system confirming root, then reboot to recovery and removing Su, flashing the boot and Magisk Canary
Sent from my Xiaomi MI 8 using XDA Labs
slave2007 said:
I have the same problem with magisk, after weekly update and after magisk installed, boot only TWRP. I tried with18.1 version but will not recognise. Boot image and Magisk 19.1 are in downloads but no success. Anyway, with this weekly update all people have loosen magisk, I have read in Xiaomi forum.
Click to expand...
Click to collapse
Here you can see that I have root and latest update
Sent from my Xiaomi MI 8 using XDA Labs
tsongming said:
Nope, no issues on my Mi 8. Here is the trick. When updating do not flash Magisk until you out have booted into the system and ran updates and deleted cache and trash, then reboot to recovery and flash Magisk.
If the method that I described before in the previous post doesn't work, then unpack the boot image from the update and flash it to boot in recovery then flash Magisk Canary debug.
I have been doing this for every weekly update using the beta ROM.
I had an issue just once that was resolved by flashing SuperSu, booting to system confirming root, then reboot to recovery and removing Su, flashing the boot and Magisk Canary
Click to expand...
Click to collapse
Man has found the guilty in Xiaomi.eu/community.
It is not Magisk, but Viper 4.2. I have flashed Magisk, after reboot again in recovery and wanted to flash version 4.1. It was uninstalled, have no Viper, but Magisk is installed ?
slave2007 said:
Man has found the guilty in Xiaomi.eu/community.
It is not Magisk, but Viper 4.2. I have flashed Magisk, after reboot again in recovery and wanted to flash version 4.1. It was uninstalled, have no Viper, but Magisk is installed ?
Click to expand...
Click to collapse
I no longer use Viper because my phone has 1 speaker and for me Ainur Sauren works pretty well for all sounds.
For listening to music I have the Pro version of Power amp which has every wanted option such as dynamic compression, dynamic EQ, convolution reverb, limiting , tag editing, visualizations etc, I bought it 5 years ago for $3. Best 3 bucks that I ever spent!
Seriously, I can't recommend Poweramp highly enough, its worth its weight in gold.
Sent from my Xiaomi MI 8 using XDA Labs
6- https://otafsg1.h2os.com/patch/amaz...22_OTA_061_all_1911200429_a3efe64891d2c42.zip
6T- https://otafsg1.h2os.com/patch/amaz..._41_OTA_061_all_1911200419_f2e12518eef8ae.zip
Found this today. File has a date of 11/20/19. I put in root and do manual update thru settings/update.
Magisk patched boot.img for the above 6T ROM.
https://drive.google.com/open?id=1DIoNvGG81IC6FdWiOgSRawG0-eAKUqBF
I had a boatload of bugs with the OB1. I have a 6T converted. Couldnt answer or make calls, reboots, freezes, crashes, WIFI didnt work, no pic messages, etc. I just tested for a second and I could make calls and wifi works. Do not try to install the Magisk patched boot.img. It will give the problems I had with OB1. I tried.
Def works a lot better. No freezes or reboots. My phone was useless on OB1 and I didn't want to flash back to 9 and lose my data. I had to forward my calls to another phone and wait for an updated ROM. But this def fixed a lot of the problems I encountered.
Edit: Still cant flashboot boot twrp.img.(3.3.1-1) Same error as before (failed remote unknown command)
Here's a bonus: Magisk patched boot.img for this OB2. Tested and verified root and no problems. Patched myself. For 6T. Extracted the boot.img from the payload.bin and patched.
https://drive.google.com/open?id=1DIoNvGG81IC6FdWiOgSRawG0-eAKUqBF
shatty said:
Here's a bonus: Magisk patched boot.img for this OB2. Tested and verified root and no problems. Patched myself. For 6T. Extracted the boot.img from the payload.bin and patched.
https://drive.google.com/open?id=1DIoNvGG81IC6FdWiOgSRawG0-eAKUqBF
Click to expand...
Click to collapse
@shatty, thanks.
What did you do to upgrade ? Actually i'm in OB1 Android 10 and Root with patched boot. So you upgrade with OTA or local upgrade ? You loose Root, and you put the new patched in adb? IS it ok?
Thanks
g4seb said:
@shatty, thanks.
What did you do to upgrade ? Actually i'm in OB1 Android 10 and Root with patched boot. So you upgrade with OTA or local upgrade ? You loose Root, and you put the new patched in adb? IS it ok?
Thanks
Click to expand...
Click to collapse
If you're rooted use the same method as always, use local update ( you don't have access to incremental update anyway as you are rooted) and BEFORE rebooting go in Magisk manager and install Magisk again but on other slot. You don't need to play with adb or fastboot.
@Striatum_bdr :
Thanks, so download the update, do local update and after juste install magisk on the other slot.
shatty said:
Here's a bonus: Magisk patched boot.img for this OB2. Tested and verified root and no problems. Patched myself. For 6T. Extracted the boot.img from the payload.bin and patched.
https://drive.google.com/open?id=1DIoNvGG81IC6FdWiOgSRawG0-eAKUqBF
Click to expand...
Click to collapse
wiped my device and flashed A10 beta 2, but every time flash this patched img file from fastboot my not booting. is there any other way to flash this patched img ?
ariyan rana said:
wiped my device and flashed A10 beta 2, but every time flash this patched img file from fastboot my not booting. is there any other way to flash this patched img ?
Click to expand...
Click to collapse
It worked on my 6t converted from tmo. Anyone else try this patched boot.img? Why wipe? Upgrade works fine.
So after hours of using the ob2 I didn't have any freezes or reboots. 1000000x better than my experience on ob1
shatty said:
So after hours of using the ob2 I didn't have any freezes or reboots. 1000000x better than my experience on ob1
Click to expand...
Click to collapse
Same here bud. Thanks.
shatty said:
Def works a lot better. No freezes or reboots. My phone was useless on OB1 and I didn't want to flash back to 9 and lose my data. I had to forward my calls to another phone and wait for an updated ROM. But this def fixed a lot of the problems I encountered.
Edit: Still cant flashboot boot twrp.img.(3.3.1-1) Same error as before (failed remote unknown command)
Click to expand...
Click to collapse
For now the right command is fastboot flash boot twrp mauronofrio.img version and then flash the installer zip through recovery.
It's a Oneplus's problem.
[EDIT 1]
After a few tries it worked! Now I try to install twrp (mauronofio version) and root the phone.
P.s. I'm trying to update (come form OB-1) I removed all magisk's modules, flashed magiks unistaller but the update with update manager keep failing...any idea?
[EDIT2]
ok, now I'm rooted and I've twrp but wifi doesn't work it's turn off automatically!
[EDIT3]
I've fix it! I've talked with mauronofrio and he said that it's due to flashing the twrp in the boot partition, so he suggested me two ways:
1. Root your device and flash the twrp installer using magisk manager
2. After the command fastboot flash boot twrp.img reboot in recovery, flash the stock boot.img flash twrp installer.zip and finally flash magisk.
I choosen the second way and it worked! Now I've OB_2, twrp, magisk and wifi connection.
Thx a lot for the links and Infos.
I have flashed it and it feels definitely smoother and I hope the random reboots are fixed.
From the changelog they should be.
Here is a small how to, how the upgrade from 10 to 10 ob2 went smooth. Also using this on every update.
1. Just use normal systen ota & let it install or Flash full OOS 10 zip via local update . (DO NOT REBOOT)
2a. Flash newest TWRP: fajita twrp 3.3.1-28.zip (or newer) by @mauronofrio via Magisk Manager (DO NOT REBOOT)
or 2b. go into magisk manager, search for a module called "twrp a/b retention script" Install it (DO NOT REBOOT)
3. Flash magisk to 2nd slot via MAgisk Manager (Magisk Manager → Tap on Install → Then select Install to Inactive Slot)
4. Reboot, wait and enjoy
pOpY
Gesendet von meinem ONEPLUS A6013 mit Tapatalk
Be very careful with the patched boot image. It hard-bricked my OP6T! Full details here:
https://forum.xda-developers.com/oneplus-6t/help/spent-6-hours-trying-to-rooted-android-t4012909
It looks like they took FactoryMode away using *#808# when using the dialer... anyone noticed?
Did they fix the extra blank space under navigation keyboard when type? Thanks
nicche said:
For now the right command is fastboot flash boot twrp mauronofrio.img version and then flash the installer zip through recovery.
It's a Oneplus's problem.
[EDIT 1]
After a few tries it worked! Now I try to install twrp (mauronofio version) and root the phone.
P.s. I'm trying to update (come form OB-1) I removed all magisk's modules, flashed magiks unistaller but the update with update manager keep failing...any idea?
[EDIT2]
ok, now I'm rooted and I've twrp but wifi doesn't work it's turn off automatically!
Click to expand...
Click to collapse
same thing happened to me. Have you found the fix sir?
OK just reflash the rom and dont forget to flash twrp and magisk again
anddd boom i got wifi working again
Anyone else having issues like the systems is getting slower animation is choppy and it just lag. I noticed it as well when playing games when that happens and it feels like i dont get as much framerates but a reboot of system fixed it for me. I thought by updating to ob2 it would fix this choppy feeling but its still there
I upgraded from OOS 10 Stable to OOS Beta 2 and all went on okay. No data lost.
Rickydwi said:
Anyone else having issues like the systems is getting slower animation is choppy and it just lag. I noticed it as well when playing games when that happens and it feels like i dont get as much framerates but a reboot of system fixed it for me. I thought by updating to ob2 it would fix this choppy feeling but its still there
Click to expand...
Click to collapse
I don't have this issue, but I do have the Bluetooth not working bug
Hi all, as the title implies, I'm a newbie to all this. I tried to root my phone using an online guide on how to root xiaomi mi 9 using TWRP and Magisk. I faced some problems but eventually everything was done as the tutorial said.
Here are the exact steps I've done...
- unlocked the phone via Mi unlocking tool
- started fastboot and installed TWRP 3.3.1-0 ( I installed a version first that didn't start when I pressed both power and volume up, then installed the 331-0 version that worked)
- inside TWRP i installed Magisk 20.4
- The phone restarted but never reach the system. It hangs for sometime on android screen then restarts again and then brings me again to TWRP
I spent quiet sometimes reading online solutions but nothing worked for me...
I tried installing Magisk uninstaller.zip nothing changed. tried wiping cache. Tried installing magisk 20 and 20.3
some solutions recommended installing Magisk 19 0r 17 but they both ended up with error for me.
Please help. I'm on Android 10 with MIUI 11
Never had any problems with magisk What TWRP version have you used?
The steps are the same:
-Unlocked phone.
-TWRP.
-Flash magisk zip (you can install magisk manager, then download latest official magisk zip from it and then flash downloaded zip from TWRP).
-reboot.
Anyway you can fix your system by:
-wipe cache/dalvik.
-FORMAT data (with yes).
I don't think you need this 2 first steps for flashing fastboot ROM but it won't hurt.
-Flash official fastboot ROM in fastboot mod, using mi flash tool or included batch/bash scripts (don't lock your device if you don't want to, choose the right option when you flash, with or without "lock").
Mi 9 Fastboot V11.0.5.0.QFAMIXM Global
Mi 9 Fastboot V11.0.8.0.QFAEUXM EEA
You will loose all your data, apps and settings.
Thanks for your help mate...
I'm using this TWRP version..
----//dl.twrp.me/cepheus/
Strangely enough, my phone started after flashing Magisk-uninstaller-20191011.zip I'm sure i tried this before and it doesn't work.
Anyway, all my app and data are gone. I still want to root though, can you help me? what version of TWRP and Magisk i should use?
F.Ashour said:
Thanks for your help mate...
I'm using this TWRP version..
----//dl.twrp.me/cepheus/
Strangely enough, my phone started after flashing Magisk-uninstaller-20191011.zip I'm sure i tried this before and it doesn't work.
Anyway, all my app and data are gone. I still want to root though, can you help me? what version of TWRP and Magisk i should use?
Click to expand...
Click to collapse
Use twrp-3.3.1-62-cepheus-mauronofrio.img.
Magisk-v20.4.zip
antonio52 said:
Use twrp-3.3.1-62-cepheus-mauronofrio.img.
Magisk-v20.4.zip
Click to expand...
Click to collapse
Thanks for your time mate...
I tried this twrp and magisk your mentioned. same issue. boots back to twrp never to system. Any solutions?
F.Ashour said:
Thanks for your time mate...
I tried this twrp and magisk your mentioned. same issue. boots back to twrp never to system. Any solutions?
Click to expand...
Click to collapse
I would try flash latest fastboot ROM as i said before it will reflash almost everything And then flash magisk by installing magisk manager and download latest magisk zip through it and flash it with twrp-3.3.1-62-cepheus-mauronofrio TWRP
Sometimes first flash of TWRP don't work, just flash it ones more by fastboot flash twrp twrp-3.3.1-62-cepheus-mauronofrio.img from your pc.
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?
For some odd reason Magisk breaks auto-rotation and sets selinux to permissive on boot after updating to 25.2 (from 25.1).
This is not the first time Magisk messes up Selinux rules. I usuall solved this by making a fresh OS install already with patched boot and by installing the managing app afterwards.
However, this time autorotation stopped working for some reason. And when i try to uninstall Magisk using its app -- OS no longer boots, as if it fails to restore initial boot image.
This selinux problem began since v25.
I use latest official build of Lineage OS 18.1. I have TWRP installed, which i use to install LineageOS.
What am i doing wrong? Has anyone experienced such issues?
I posted the same problem here (did not notice/checked SELinux back then and sound is probably also not working), figured out that all sensors do not work, checked with "Sensor Test" app. I was already considering a separate thread, thus I'll continue here, because this issue definitely deserves a separate thread. Documentation is so scattered and sometimes so confusionly described, that it was hard to make sense of it all...
(Disclaimer: Although I have necessary experience with installing custom ROMs etc., everything stated below is at my own understanding ).
My device: Samsung Galaxy Tab S5e LTE
My goal was: TWRP, LineageOS and Magisk. How hard can it be?
Problems are that (most of the) Samsung devices do not have a "ramdisk" partition where Magisk is normally installed, also the increasingly complexity of encryption en integrity checks makes this more annoying.
First, let me retrace my steps, as far as I can.
When reading the TWRP page, we get a clue where to start: "You are therefore strongly advised to first root your device with Magisk and then pre-root a TWRP image before flashing it to recovery", this is because "Both TWRP and Magisk-rooted Android boot using the recovery kernel, with the device's hardware keys used to choose between TWRP and Android at boot time".
(Magisk "hijacks" part of the recovery partition, since the absence of a ramdisk partition.)
Spoiler: later on you learn this is not completely the case any more, but I would still recommend to hold on to this method, because the TWRP page also states that: "The usual path of installing TWRP prior to rooting is problematic on this device, because the Magisk installer does not support installation to recovery from TWRP. Furthermore, prior rooting of the device with Magisk carries the significant advantage of disabling various device protection mechanisms that you will otherwise need to take care of manually.", and it continues with more scary warnings...
1. Thus followed the Samsung section of the Magisk documentation to have the bootloader unlocked and Magisk installed, but stock firmware is still installed, no problem whatsoever.
Then decipher the already mentioned instruction: "...pre-root a TWRP image before flashing it to recovery". This apparently means that Magisk has to patch the TWRP image, just like as was done with the Samsung firmware.
2. Downloaded the *.tar file of TWRP, extracted the image, patched with Magisk and repacked to the *.tar file with 7-Zip in order to be able to flash it with Odin (see step 4).
*3. I do not recall when I installed the "VBMeta file", although this is instructed in the Lineage OS installation instructions, when following the TWRP instructions it says "...you can now jump to its own section", thus skipping it?? (I did it somewhere in the process...)
Unknown: whether it is still required to patch and flash VBmeta (to disable some verification process)...
4. Flash TWRP recovery, see YouTube video below. This video mentions the use of "multidisabler-samsung", which disables "FBE, proca, Vaultkeeper and auto-reflash of stock recovery on Samsung Pie devices". Current latest version was 3.1, downloaded from this XDA post, I think.
Just as in the YouTube video, I also was stuck at the Samsung logo. After booting into the stock firmware you can check if Magisk still works.
Not sure: "multidisabler-samsung" needed?
5. Install LineageOS (and GApps). The most straightforward step, just install LineageOS, read the instructions. Then install GApps (e.g., BiTGApps).
6. After booting (power and volume + button) and setting up LineageOS, a Magisk icon should be visible in the app drawer, click it and the Magisk app is installed, when opened, Magisk is setting up a few more things and reboots the tablet.
*******************************************************************************************
This is the point were you finally think you made it, but no, here the issues arise.
Issues thus being SELinux permissive status (Xandros Darkstorm), no sound and non-working sensors, thus "auto rotating" feature is not working.
At this point I started to regret my purchase...
In the search of a solution to the problem I stumbled upon the following familiar and solved Magisk issue #4911 (LineageOS 18.1 no sound and no sensors after booting with Magisk), which refers to issue #4394 (Magisk > 21.4 is difficult to install on LineageOS (18.1) with TWRP (Direct Install not enabled unless you use old zip)).
In short: this post mentioned patching the boot image instead of the recovery image.
*******************************************************************************************
I. I extracted "boot.img" from the LineageOS zip file, patched it via Magisk (ramdisk is added to the boot image) and replaced the "boot.img" in the zip file with 7-Zip.
II. Booted into TWRP, flashed an original TWRP image, so recovery is replaced. (Rebooted I guess.)
III. Then wiped previously LineageOS installation and, flashed the LineageOS zip file with patched boot image and GApps and rebooted to system.
IV. After setting up, install Magisk, let is do its thing.
V. I installed "Root Checker Basic" in order to check I gained root checker. It was a PASS! And checked with "Sensor Test" if all sensors worked, they did! And sound also worked .
Yay!
Clearly, all of this can be optimized. Some questions remain, what steps are really necessary and I am also still wondering how to apply a LineageOS update... Anyhow at least it is working.
What resolved
Xandros Darkstorm said:
For some odd reason Magisk breaks auto-rotation and sets selinux to permissive on boot after updating to 25.2 (from 25.1).
This is not the first time Magisk messes up Selinux rules. I usuall solved this by making a fresh OS install already with patched boot and by installing the managing app afterwards.
However, this time autorotation stopped working for some reason. And when i try to uninstall Magisk using its app -- OS no longer boots, as if it fails to restore initial boot image.
This selinux problem began since v25.
I use latest official build of Lineage OS 18.1. I have TWRP installed, which i use to install LineageOS.
What am i doing wrong? Has anyone experienced such issues?
Click to expand...
Click to collapse
What fixed this for me is after re-flashing stock in Odin to get everything working again, just rename the magisk apk to install.zip and flash that in twrp, and open the magisk app once booted, no other steps needed for install, no image patching or anything.
Might be worth seeing if this is the same issue or if there's a more fundamental problem with 25.2
Hi,
I stumbled upon this thread while searching for a way to install Magisk on a S5e.
Following the guide here: https://wiki.lineageos.org/devices/gts4lvwifi/install I already unlocked the bootloader, flashed vbmeta.tar with Odin, flashed lineage-19.1-20221114-recovery-gts4lvwifi.img with Odin and flashed lineage-19.1-20221114-nightly-gts4lvwifi-signed.zip with TWRP-recovery.
Lineage is working fine, but I would also like to use Magisk.
I understood, that the order I follwed is not the recommended order for having both Magisk and Lineage. At least, that is, what you described at the beginning of your post.
But as with your last part you mentioned, that there where issues with sensors, ...
And the solution was to
I. Replace recovery with a patched boot.img of Lineage zip and wipe a prev. Lineage installation
I guess, I might be able to stiull do that though I already have Lineage on the S5e (currently with Lineage/TWRP recovery), right?
I can patch the boot.img from within lineage-19.1-20221114-nightly-gts4lvwifi-signed.zip with Magisk app, right?
Or would I have to patch lineage-19.1-20221114-recovery-gts4lvwifi.img
Is there anything to consider, when zipping the image with the patched boot.img again?
Which TWRP image did you choose to be flashed at step II.?
Barium said:
I. I extracted "boot.img" from the LineageOS zip file, patched it via Magisk (ramdisk is added to the boot image) and replaced the "boot.img" in the zip file with 7-Zip.
II. Booted into TWRP, flashed an original TWRP image, so recovery is replaced. (Rebooted I guess.)
III. Then wiped previously LineageOS installation and, flashed the LineageOS zip file with patched boot image and GApps and rebooted to system.
IV. After setting up, install Magisk, let is do its thing.
V. I installed "Root Checker Basic" in order to check I gained root checker. It was a PASS! And checked with "Sensor Test" if all sensors worked, they did! And sound also worked .
Yay!
Clearly, all of this can be optimized. Some questions remain, what steps are really necessary and I am also still wondering how to apply a LineageOS update... Anyhow at least it is working.
Click to expand...
Click to collapse
Thanks
If this is also a solution, can you please let me know, if there is anyhting to consider, when flashing the stock (got it from SAMMOBILE)? Can the lineage-19.1-20221114-recovery-gts4lvwifi.img still be left on the tab?
After re-flashing the stock, I guess you flashed lineage again, right?
Or did you stay with the stock and just flashed magisk (after renaming the apk to zip)?
Thanks
TheTofu said:
What fixed this for me is after re-flashing stock in Odin to get everything working again, just rename the magisk apk to install.zip and flash that in twrp, and open the magisk app once booted, no other steps needed for install, no image patching or anything.
Click to expand...
Click to collapse
I dared patching the TWRP recover for S5e and flashed it via Odin (AP).
S5e boots up in Lineage, Magisk is working fine.
But when I power off the tablet or restart, Lineage Recovery shows up telling me, that my data would be corrupt.
My only options are to try again or to do a factory reset.
Only way out of this is to re-flash the above mentioned recovery image again.
So how do I get the Magisk patched TWRP recovery permanent?
I wiped system? and re-flashed Lineage via TWRP, got "original" TWRP Recovery for S5e Magisk permanent.
I have to admid, I tried several things and got lucky I did not break something.
I had nearly, what I wanted - TWRP, Lineage and Magisk, but there were issues with the sensors (no auto rotate).
Again I helped myself:
1) flashed the original, unpatched TWRP Recovery for S5e
2) flashed unpatched Lineage for S5e
3) flashed MindTheGapps
4) flashed Magisk-v25.2.apk
No bootloop, original TWRP permanent, Magisks working fine, no issues with sensors.
Tried steps 1, 2 and 4 with the Lineage Recovery and it worked too.