Hey guys,
Just having a big bloody problem installing magisk on LOS 18.1.
Whenever I do the device will get hot, reception will be gone, system ui will keep crashing, device will operate on fullbright then eventually after about 2-5 mins qualcomm crashdumps to mdm_force_reset.
And even with all that happening Magisk still doesn't appear to have been installed
I have tried:
Factory reset
Magisk canary
patching boot image
reflashing rom
flashing via the (wip) twrp
flashing via sideload
All resulting in the same situation.
I have attached a full logcat dump below, device will continue to work properly with stock boot image and with stock or non stock kernal. This works on OOS just not LOS. During installation no errors occure for magisk so this has me stumped.
hmm not sure if this logs uploading on xda so heres a drive link
log.txt
drive.google.com
Have to ask, you're trying to patch and boot from the LOS boot image, right?
Try with different, non-canary Magisk too. I never used canary and it always worked for me.
daviddosa said:
Have to ask, you're trying to patch and boot from the LOS boot image, right?
Try with different, non-canary Magisk too. I never used canary and it always worked for me.
Click to expand...
Click to collapse
Yeah correct, Pulled directly off my device (also the flashing via twrp of the magisk zip has the same outcome so it can't be boot image related :^) )
Yeah tried both canary and mainline 23.0, no dice but thx for checking.
darkjake said:
Yeah correct, Pulled directly off my device (also the flashing via twrp of the magisk zip has the same outcome so it can't be boot image related :^) )
Yeah tried both canary and mainline 23.0, no dice but thx for checking.
Click to expand...
Click to collapse
What if you extract it from the payload.bin?
Patch that boot.img, boot from it(don't flash), then use Magisk to install it directly, but not on the inactive slot.
daviddosa said:
What if you extract it from the payload.bin?
Patch that boot.img, boot from it(don't flash), then use Magisk to install it directly, but not on the inactive slot.
Click to expand...
Click to collapse
Booting from it has the same result :/ cannot use Magsik to install it directly either ( since the manager still claims it isn't installed)
Magisk log just in case
magisk.log
drive.google.com
Related
I've installed the Magisk manager and can't quite get the Magisk file installed. TWRP gives an error, which I'll throw down here
Code:
- Mounting /system, /vendor, /cache, /data
- Device platform: arm64
- Constructing environment
- Adding addon.d survival script
- Found Boot Image: /dev/block/mmcblk0p58
- Unpacking boot image
- Checking ramdisk status
! Boot image patched by other programs!
! Please restore stock boot image
- Unmounting partitions
Updater process ended with ERROR: 1
Error installing zip file '/sdcard/Magisk-v14.0-zf2-20170906.zip'
Updating partition details...
...done
Do I really have to reinstall a stock image? I don't want to lose all my installed data. I've reflashed the phone a billion times getting various things to work, and now that I'm on a stable ROM, I don't want to move over. I've heard this can be an issue with having SuperSU installed. I'm just trying to get certain apps to work, like Fire Emblem Heroes or Animal Crossing Pocket Camp.
I'm welcome to answer any questions anyone has, I just want it fixed.
Kaisogen said:
I've installed the Magisk manager and can't quite get the Magisk file installed. TWRP gives an error, which I'll throw down here
Do I really have to reinstall a stock image? I don't want to lose all my installed data. I've reflashed the phone a billion times getting various things to work, and now that I'm on a stable ROM, I don't want to move over. I've heard this can be an issue with having SuperSU installed. I'm just trying to get certain apps to work, like Fire Emblem Heroes or Animal Crossing Pocket Camp.
I'm welcome to answer any questions anyone has, I just want it fixed.
Click to expand...
Click to collapse
Why did you flash older version of Magisk? Try flashing Magisk V16 or Magisk Beta V16.3.
https://forum.xda-developers.com/apps/magisk
Saktis_STi said:
Why did you flash older version of Magisk? Try flashing Magisk V16 or Magisk Beta V16.3.
https://forum.xda-developers.com/apps/magisk
Click to expand...
Click to collapse
That was from earlier. I have tried the newer version, it still gives the same error. I've also tried unrooting and it still does.
Kaisogen said:
That was from earlier. I have tried the newer version, it still gives the same error. I've also tried unrooting and it still does.
Click to expand...
Click to collapse
Reflash newer TWRP and try again.
Saktis_STi said:
Reflash newer TWRP and try again.
Click to expand...
Click to collapse
Doesn't change anything, still gives the same error. Magisk 16, and TWRP 3.2.1 for ZE552KL Unofficial
Kaisogen said:
Doesn't change anything, still gives the same error. Magisk 16, and TWRP 3.2.1 for ZE552KL Unofficial
Click to expand...
Click to collapse
Try this method:
1) Flash Oreo RAW
Link: https://forum.xda-developers.com/zenfone-3/development/updated-unlock-relock-bootloader-t3749456 (end of the main post)
2) Boot phone until homescreen
3) Flash TWRP 3.2.1 by @planet9 (make sure you flash the latest version of TWRP)
4) Flash Magisk Beta (v 16.3)
5) Reboot
P.S: Make sure you've backed up all of your important data before flashing
With "Please restore stock boot image" the Magisk installer just want's to tell you to reflash the currently installed ROM: Simply reflash the zip of your ROM (LineageOS), then flash Magisk. No data will be lost by doing that.
The word "stock" is quite misleading here as it doesn't refer to the asus rom.
Did anyone notice that doing a "fastboot boot boot-patched.img" for installing magisk sometimes hangs during boot or a stock recovery error msg "Could not load Android system. Your data could be corrupt....."
I need a few tries before it boots properly. And then installing the systemless expose module gives a similar error.
edit- It doesn't seem to be happening anymore. I tried reproduce the problem but couldn't get it to hang after many tries.
Others have reported seeing this issue as well.
Use TWRP for Magisk installation + check here https://forum.xda-developers.com/mi-a1/help/rooted-device-freezes-booting-secure-t3819483
_mysiak_ said:
Use TWRP for Magisk installation + check here https://forum.xda-developers.com/mi-a1/help/rooted-device-freezes-booting-secure-t3819483
Click to expand...
Click to collapse
Will installing magisk via TWRP break OTA? I'm assuming you boot(not flash TWRP earlier) into TWRP and flash the Magisk framework zip.
From the thread, it sounds like Magisk 16.7 beta has problems with common apps.
barrack1 said:
Will installing magisk via TWRP break OTA? I'm assuming you boot(not flash TWRP earlier) into TWRP and flash the Magisk framework zip.
From the thread, it sounds like Magisk 16.7 beta has problems with common apps.
Click to expand...
Click to collapse
If you boot TWRP to flash magisk it won't break OTA.
I installed 16.7 yesterday and no problem so far with any app.
pantezuma said:
If you boot TWRP to flash magisk it won't break OTA.
I installed 16.7 yesterday and no problem so far with any app.
Click to expand...
Click to collapse
Do you know why flashing magisk after booting into TWRP won't cause problems VS booting into patched boot.img and installing Magisk via "direct install"?? It didn't cause any big booting issue pre 8.1 for me until the last update.
barrack1 said:
Do you know why flashing magisk after booting into TWRP won't cause problems VS booting into patched boot.img and installing Magisk via "direct install"?? It didn't cause any big booting issue pre 8.1 for me until the last update.
Click to expand...
Click to collapse
I think you booted an image patched with 16.0 and not 16.7 (you can try to get an image patched with 16.7 beta just to verify).
As said before, it seems 16.0 has some issues regarding booting and secure boot solved in 16.7.
I updated my device to the last pie version (10.0.0.3); a former version of Magisk was completely uninstalled before. Then I did a backup of my boot.img via TWRP I booted temporarily. But when I patched this boot.img via Magisk Manager 18.0 and installed and booted the patched_boot.img it ended in a bootloop; only the screen with "android one" was visible and then it stopped. When I flashed back the boot.img and booted again everything worked fine again. A strange fact is that the boot.img has 64 MB, but the patched_boot.img only 16 MB. Any help would be greatly appreciated!
Keep stock boot.img installed, boot into TWRP, install Magisk from TWRP, reboot.
_mysiak_ said:
Keep stock boot.img installed, boot into TWRP, install Magisk from TWRP, reboot.
Click to expand...
Click to collapse
I have done this but facing the exact same issue, bootloop at android one logo. Kindly help.:crying:
ForTheOne said:
I have done this but facing the exact same issue, bootloop at android one logo. Kindly help.:crying:
Click to expand...
Click to collapse
I was afraid this would happen so I didn't try it. I think the Magisk patching routine is somewhat faulty on our device - see the massive difference in size of the boot images I mentioned.
zapper19 said:
I updated my device to the last pie version (10.0.0.3); a former version of Magisk was completely uninstalled before. Then I did a backup of my boot.img via TWRP I booted temporarily. But when I patched this boot.img via Magisk Manager 18.0 and installed and booted the patched_boot.img it ended in a bootloop; only the screen with "android one" was visible and then it stopped. When I flashed back the boot.img and booted again everything worked fine again. A strange fact is that the boot.img has 64 MB, but the patched_boot.img only 16 MB. Any help would be greatly appreciated!
Click to expand...
Click to collapse
The size difference is normal, compressed boot image is 16MB while not compressed is 64
If you zip a 64 MB boot image, it will be 16 mb
zapper19 said:
I was afraid this would happen so I didn't try it. I think the Magisk patching routine is somewhat faulty on our device - see the massive difference in size of the boot images I mentioned.
Click to expand...
Click to collapse
I have rooted via the same method. I didn't face any problem. The size difference is also normal.
ForTheOne said:
I have done this but facing the exact same issue, bootloop at android one logo. Kindly help.:crying:
Click to expand...
Click to collapse
How did you uninstall the previous Magisk version? I guess that incompatible Magisk module is the culprit here. Do the full uninstall with Magisk uninstaller in TWRP and install it again.
_mysiak_ said:
How did you uninstall the previous Magisk version? I guess that incompatible Magisk module is the culprit here. Do the full uninstall with Magisk uninstaller in TWRP and install it again.
Click to expand...
Click to collapse
Thanks, this worked perfectly. These are the steps which worked for me:
Flashed the uninstaller.zip from this page --https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Rebooted and installed Magisk Manager apk
Patched the stock boot image via Magisk app using "Patch boot Image"
Flashed the patched boot image via fastboot
Success!! Phone is rooted.
Let me know if you face any issues by this method @zapper19
ForTheOne said:
Thanks, this worked perfectly. These are the steps which worked for me:
Flashed the uninstaller.zip from this page --https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Rebooted and installed Magisk Manager apk
Patched the stock boot image via Magisk app using "Patch boot Image"
Flashed the patched boot image via fastboot
Success!! Phone is rooted.
Let me know if you face any issues by this method @zapper19
Click to expand...
Click to collapse
Worked like a charm - thank you! :laugh: Strange: I uninstalled Magisk via the Magisk Manager before I updated to Pie, but maybe there were some relics that prevented the new patched image from booting.
Today just received update notification as below image. Downloading now, let see what are changes and improvements.
I'm enrolled in beta for Android 11 and got the September Security patch today. Will I get the stable release soon or should I opt out from beta and go for a fresh instal?
TenTuTego said:
I'm enrolled in beta for Android 11 and got the September Security patch today. Will I get the stable release soon or should I opt out from beta and go for a fresh instal?
Click to expand...
Click to collapse
You are automatically switched to the stable release. Check in your "About" settings.
tkachenko.ic said:
You are automatically switched to the stable release. Check in your "About" settings.
Click to expand...
Click to collapse
I have readed yesterday that, when Android 11 Stable is released, u can stay on beta program for beta features and experimental updates, also you can receive updates earlier than others.
Has anyone been able to successfully root using Magisk? I tried and bootlooped.
Edit: Magisk Canary works, but you CANNOT install TWRP as it hasn't been developed to work with A11 yet.
socal87 said:
Has anyone been able to successfully root using Magisk? I tried and bootlooped.
Click to expand...
Click to collapse
Use magisk canary
Anyone have the screen record enabled in power menu and how ?
khanhcc said:
Use magisk canary
Click to expand...
Click to collapse
not working for pixel2, same bootloop
monikmax said:
not working for pixel2, same bootloop
Click to expand...
Click to collapse
Are you using a custom recovery? TWRP does not work with A11 yet.
Extract the boot image from a factory ZIP and flash it in bootloader:
Code:
fastboot flash boot "boot.img"
Then, boot TWRP:
Code:
fastboot boot "twrp.img"
And install Magisk using the canary zip. Please note that you do not use the quotation marks.
Alternatively, you can boot to TWRP and sideload the OTA, then reboot to bootloader, boot TWRP again, and install Magisk.
V0latyle said:
Are you using a custom recovery? TWRP does not work with A11 yet.
Extract the boot image from a factory ZIP and flash it in bootloader:
Code:
fastboot flash boot "boot.img"
Then, boot TWRP:
Code:
fastboot boot "twrp.img"
And install Magisk using the canary zip. Please note that you do not use the quotation marks.
Alternatively, you can boot to TWRP and sideload the OTA, then reboot to bootloader, boot TWRP again, and install Magisk.
Click to expand...
Click to collapse
Magisk is installed, but after patched boot applied phone is bootlooping.
any ideas?
monikmax said:
Magisk is installed, but after patched boot applied phone is bootlooping.
any ideas?
Click to expand...
Click to collapse
You must use the Magisk Canary zip on the stock boot image. Regular Magisk will not work.
V0latyle said:
You must use the Magisk Canary zip on the stock boot image. Regular Magisk will not work.
Click to expand...
Click to collapse
Could you describe the procedure or write out the steps for rooting our device running on Android 11?
SoloMid Hazard said:
Could you describe the procedure or write out the steps for rooting our device running on Android 11?
Click to expand...
Click to collapse
Your bootloader must be unlocked to use this method.
Start fresh, use the OTA or the factory image. I did this coming from Android 10 without wiping.
Download the Magisk Manager Canary APK and installer ZIP here
Download the latest TWRP image here, put it in your platform tools folder and rename to twrp.img
Using platform tools, reboot your phone into bootloader:
Code:
adb reboot bootloader
Then, boot (DO NOT INSTALL) TWRP:
Code:
fastboot boot twrp.img
Install the Magisk Canary ZIP, reboot to system.
Yes I am using canary latest, and did everything as you explaining, still getting bootloop. But I will get done sooner or later )
hemal_4404 said:
Today just received update notification as below image. Downloading now, let see what are changes and improvements.
Click to expand...
Click to collapse
I am trying to screen record by the official android screen recorder app my phone doesn't records the video afte the recording is done and played laters only one thing pops in the video "gboard encountered a problem" and the same thing comes up whenever I try to record. Is someone facing the same issue?
V0latyle said:
Your bootloader must be unlocked to use this method.
Start fresh, use the OTA or the factory image. I did this coming from Android 10 without wiping.
Download the Magisk Manager Canary APK and installer ZIP here
Download the latest TWRP image here, put it in your platform tools folder and rename to twrp.img
Using platform tools, reboot your phone into bootloader:
Code:
adb reboot bootloader
Then, boot (DO NOT INSTALL) TWRP:
Code:
fastboot boot twrp.img
Install the Magisk Canary ZIP, reboot to system.
Click to expand...
Click to collapse
+1 on this method, worked for me, thank you for the instructions
I'm also bootlooping. Did you solve your problem?
I installed through the OTA button. Of course, I lost root, so I followed the above instructions, but am stuck at the G loading.
The canary zip is magisk-debug.zip, correct?
EDIT: I overlooked that I had EdXposed installed with active modules and I don't think it works with Android 11 yet, at least not the modules I use (Gravity box). I'll try rooting again tonight with EdXposed modules disabled.
Chilipepprflea said:
I'm also bootlooping. Did you solve your problem?
I installed through the OTA button. Of course, I lost root, so I followed the above instructions, but am stuck at the G loading.
The canary zip is magisk-debug.zip, correct?
EDIT: I overlooked that I had EdXposed installed with active modules and I don't think it works with Android 11 yet, at least not the modules I use (Gravity box). I'll try rooting again tonight with EdXposed modules disabled.
Click to expand...
Click to collapse
Yes, both the apk and the zip are named "magisk_debug".
I am not sure why you are bootlooping. If you installed the OTA, it should have overwritten /boot with the stock image, and flashing Magisk Canary should work. It is possible that if you had modules enabled before and didn't disable them, you could have issues.
V0latyle said:
Yes, both the apk and the zip are named "magisk_debug".
I am not sure why you are bootlooping. If you installed the OTA, it should have overwritten /boot with the stock image, and flashing Magisk Canary should work. It is possible that if you had modules enabled before and didn't disable them, you could have issues.
Click to expand...
Click to collapse
I disabled the edxposed modules and still got stuck at the G logo. I'm not sure what else I could be doing wrong, but it's obviously me or my setup. I'm going to downgrade to Android 10 because the modifications I rely on from GravityBox are more important to me than the new features of Android 11.
Thanks for the help.
Chilipepprflea said:
I disabled the edxposed modules and still got stuck at the G logo. I'm not sure what else I could be doing wrong, but it's obviously me or my setup. I'm going to downgrade to Android 10 because the modifications I rely on from GravityBox are more important to me than the new features of Android 11.
Thanks for the help.
Click to expand...
Click to collapse
Anyone have luck downgrading from 11 to 10? I've tried several different 10 builds and I get "Error: Slot Unbootable: Load Error" in bootloader.
I used the same commands I always use to upgrade builds:
fastboot flash radio radio-walleye-...img
fastboot reboot bootloader
fastboot update image-walleye-...zip
I can flash 11 again and all is fine, but I haven't been able to go back to 10.
Hello there, back in the day (2019 in March or April the phone shipped with Android 9) I rooted my galaxy S10+ Exynos with Magisk and stock recovery (because TWRP method did not exist yet or did but non twrp method looked safer, I forgot the reason)
Then I forgot about TWRP and even upgraded to Android 10 like this:
(standard procedure, download android with Friya, then patch ap file with magisk, then flash it with odin)
Well I used my phone as always, forgot about twrp, but always had a little voice in my head telling me, that twrp is good idea, what if something happens, I would at least be able to copy my data)
So I decided to flash twrp, to ease my mind a bit, and also be able to copy apps to /system/priv-app
So I am using Android 10 (see no reason to upgrade, what I need is there I prefer OneUI 2.0 over later versions and I dont want to make my device slower or loose some obscure api function that I dont even know exists until I need it)
Now, can I just use official twrp app and let it do its thing (I have root), or do I need to download twrp with the app, but prepatch it with magisk before I install it? (I read conflicting info, on xda they say you need to prepatch it, while on twrp guide: https://twrp.me/samsung/samsunggalaxys10plus.html
They say to just use the app if you already have root, so I am confused now
It seams using the app is the easiest and most safe method
Thanks for Anwsering and Best Regards
only in case recovery and boot share the same partition, you will lose magisk after flashing TWRP (does not apply)
alecxs said:
only in case recovery and boot share the same partition, you will lose magisk after flashing TWRP (does not apply)
Click to expand...
Click to collapse
well, I gues this did apply to me, because I tried to flash TWRP with the app (latest version: twrp-3.7.0_9-2 that the app offered, it offered 2 files .img or .img.tar, and I chose to flash .img), and now my phone cannot boot, its stuck in download mode it says with red letters
kernel: Could not do normal boot, (DT LOAD failed)
I don't know know what happened, I only flashed recovery, and bootloader is unlocked
adb doesn't work
I cannot even get to recovery
So what now? Can at least flash TWRP somehow back so I can get ot my files (I have most of my videos on an SD card, but 2 or 3 are on internal storage )
I would reflash Android 10 anyway if it wasn't for the files
you can flash recovery.img as tar file but that is useless for backup stock ROM userdata. if you still have the magisk_patched.tar you can flash it to get your data back. don't flash unpatched stock boot.img this will most likely result in data loss.
I would first try older TWRP as DT LOAD failed (device tree) looks like TWRP problem to me.
alecxs said:
you can flash recovery.img as tar file but that is useless for backup stock ROM userdata. if you still have the magisk_patched.tar you can flash it to get your data back. don't flash unpatched stock boot.img this will most likely result in data loss.
Click to expand...
Click to collapse
OK
after installing TWRMP
3.4.0 I got into recovery
I guess the latest version twrp-3.7.0_9-2 is broken (because I tried flashing from Odin and I got the same error
but 3.4.0 works now
Well then I got into a non rooted android state (I couldnt boot into the rooted one because if I held volume up I just got into TWRMP)
I do have my magisk patched AP file (I did keep that), so I tried flashing it by odin to get into rooted state again, but then got scared because I was aftaid it would delete my data, so pulled the plug out, immediately after I discovered its flashing system.img (it just started)
thats where I interupted it
<ID:0/035> SingleDownload.
<ID:0/035> dt.img
<ID:0/035> dtbo.img
<ID:0/035> system.img
<ID:0/035> __XmitData_Write
<ID:0/035> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
So then phone would not boot, not in TWRMP not in android anymore, so I flashed TWRMP again and now at least
I am in TWRMP (I can see my files, but they are encrypted (they have wierd names but size does seam to match my files)
So how do I reflash android now, without messing with /data partition?
or can I somehow backup just data partition, reflash android and flash /data back?
let the magisk_patched.tar flash, just make sure you don't flash CSC (HOME_CSC is fine it won't erase userdata)
alecxs said:
let the magisk_patched.tar flash, just make sure you don't flash CSC (HOME_CSC is fine it won't erase userdata)
Click to expand...
Click to collapse
Yey, that did it (that was scarry), now root works, as well as android 10 (for some reason Magisk Manager does not open (but all the magisk modules work)
Now, I did patch this ap file back in the day I updated android to 10 so
I used Magisk Manager 7.4.1.291c718b
and if I remember corecly (thanks got I recorded everything) I patched the AP file for Magisk 20.2-11b7076a)
Now I have Magisk Manager 8.0.7 installed
So after I downgraded my Magisk manager to 7.5.0 it opened
Now I just have to figure out how to install Magisk v21.4 which is the version that belongs to my Magisk Manager 8.0.7, because Magisk Manager won't let me install a custom magisk, it only wants to download the latest version
you can install latest Magisk apk and patch stock boot.img again. Anyway I would do a backup with Migrate and adb pull -a /sdcard first.
or you can paste this url as custom channel and install older magisk if you want to.
https://raw.githubusercontent.com/topjohnwu/magisk_files/b0694fad86/stable.json
alecxs said:
you can install latest Magisk apk and patch stock boot.img again. Anyway I would do a backup with Migrate and adb pull -a /sdcard first.
Click to expand...
Click to collapse
aha, I see
is there any other way besides patching my AP file again? (I mean Magisk can clearly update itself somehow)
I mean, Magisk Manager does open (but only version 7.5.0, not version 8.0.7), and I have root its just that I don't have Magisk Manager 8.0.7
So how do I install a specific Magisk version from Manager? (I did try to install like a Magisk module, but now I am stuck in download mode again, so lets install Android 10 again )
look in the json for download link
https://github.com/topjohnwu/Magisk/releases/download/manager-v8.0.7/MagiskManager-v8.0.7.apk
https://github.com/topjohnwu/magisk_files/commits/master/stable.json
https://github.com/topjohnwu/magisk-files/commits/master/stable.json
alecxs said:
look in the json for download link
https://github.com/topjohnwu/Magisk/releases/download/manager-v8.0.7/MagiskManager-v8.0.7.apk
https://github.com/topjohnwu/magisk_files/commits/master/stable.json
https://github.com/topjohnwu/magisk-files/commits/master/stable.json
Click to expand...
Click to collapse
OK, after I installed Android again (with my older prepatched magisk)
Not sure what happened but now Magisk Manager 8.0.7 opens and says I have 20.2-11b7076a installed
of course as this combo should not exist, magisk Manager cannot see any modules (modules are there in /data/adb/modules and they do work, its just that Magisk Manager cannot see them installed, which means you can not easly delete them and you could install them over and over again, since Manager would not know that they are there)
So now I need to find a way to update to Magisk 21.4
So how would I do that (I tried the module install method before (I downloaded 21.4 from official github release pages) , but that just got me stuck into download mode again, so any other way, is there a patcher for computer maybe?
I mean I can only install the latest version, even if I disable internet, I cannot select a specific version
refer to post #8
Thanks, after spending 3hours to get into magisk I decided to share my procedure (because I forget it a lot)
FIrst: make sure your phones last state was power off (you can eather power off from red button or from recovery)
Then turn phone on and start holding power button + bixby + volume up, and count to 10 then release (not 11, 10, if you count to 11 you will get to recovery)
To try out if you are in magisk mode (without ruining your saved wifi passwords), you can plug the phone into the charger, if it turn on normaly, you are in magisk, if it shows battery charging, then you are not in magisk mode)
OK, I tried updating Magisk with https://raw.githubusercontent.com/topjohnwu/magisk_files/b0694fad86/stable.json
but for some wierd reason, it doesn't want to update, its stuck on 20.2-1
OK,. I tried installing Magisk Manager v7.4.1 and when launching it, it said that it patched dtbo.img and it needs reboot, so after I reboot, I am stuck on download mode again
It sayd: DT table header check fail
well, lets install Android 10 a third time
wait, you're booting into recovery to get into Magisk? you can use Nemesis kernel to skip this.
https://forum.xda-developers.com/posts/81316371
alecxs said:
wait, you're booting into recovery to get into Magisk? you can use Nemesis kernel to skip this.
https://forum.xda-developers.com/posts/81316371
Click to expand...
Click to collapse
Yes I am, but its allright, I am used to this
one day I will have to compile my own kernel anyway (to add some drivers to the phone)
Now I have to figure out why Magisk 21.4 won't install
I tried patching my AP file with it, but no matter what I do, I cannot get into it for some reason? (even my trust and tried method does not get me into it, while it got me into 20 all the time)
Is this version broken?
Whats the latest magisk version that still supports Magisk Hide (usefull thing that always worked for me)
With Nemesis kernel no need for button dance, it boots straight into Magisk. Magisk Hide exist up to v23 but there is also unofficial Magisk v25
[Discussion] Magisk Delta - Another unofficial third-party Magisk fork
This is not an officially supported topjohnwu project. If you are looking for official Magisk source, please go to this page Introduction Custom Magisk fork by HuskyDG. Sync with official Magisk adding back MagiskHide...
forum.xda-developers.com
alecxs said:
only in case recovery and boot share the same partition, you will lose magisk after flashing TWRP (does not apply)
Click to expand...
Click to collapse
Magisk needs the ramdisk of the recovery/TWRP to patch it. If flashing a non-prepatched image you will lose root.
WoKoschekk said:
Magisk needs the ramdisk of the recovery/TWRP to patch it. If flashing a non-prepatched image you will lose root.
Click to expand...
Click to collapse
Yea, I discovered that already
Now I am trying to get it back and failing
UPDATE: after installing Magisk 23 (last version that has Magisk Hide), prepatching AP file, and flashing it like 10th time, I finaly have root
Do I dare to try TWRP again? (I guess I need to prepatch it with Magisk before I install it with odin? (but which file do I install there are 2 files provided (twrp-3.4.0-2-beyond2lte.img.tar or twrp-3.4.0-2-beyond2lte.img)?
patch the tar file