- Sep 25, 2016
Haven't seen that message, but makes sense. No root apps I've had work on external storage, so if you're using adopted storage SD, or have other separate memory partition (I understand some devices do), Magisk App installed there won't have access to or see root.I had the latest magisk. I tried to hide the app (renamed it to something else) and when I tried to restore the app, it can't. And the root is gone-- Said that "Magisk is installed to the external storage. Please move the app to the internal storage. I tried to flash magisk again and there is no change. My root is gone and I can't bring it back. I'd appreciate it if anyone can help me. Thank you.
Early days, but I hope at least reins can be passed on to someone with no conflicting interests ...
Well, first here was removed for a reason...
I have now performed the fork, as well as some offline backups. However, I don't have nearly enough spare time to work on Magisk, nor do I have nearly the amount of qualifications that John has.
3.4k of them. Probably plenty to choose from. PW
www.twitter.com/topjohnwu/status/1394835335096406023John Wu, 2h
I understand that being the developer of a popular open source project, people are *longing* for an explanation.
However, the speculation and conspiracy theories are getting out of hand, there are even attempts to sabotage my employment in the name of "saving the community"...
This is putting extreme strain on me mentally, so let me get the facts straight: nobody really knows exactly how things will go in the future.
I tweeted an assumption caused by miscommunication; I was informed it to be non factual; I deleted the tweet. That's all, really.
So please, PLEASE, put down your tinfoil hats and pitchforks, and allow me to handle the situation privately. I will update you once there is a conclusion.
Nobody is hired to kill off a project.
I did not join Google for money.
And of course, I have not betrayed the community.
Uninstall all versions of Magisk apk or manager, specially if you have hiden/renamed oneI'm trying to install Magisk 22.1 on my Samsung Galaxy S5 Marshmallow. I had before Magisk 20.4 and Magisk Manager (App) 8.0.4. I have updated TWRP recovery up to TWRP 3.5.1_9-0-klte
I've installed MAgisk 22.1 via TWRP as apk not as a zip file.
Everything was smoothly. I was able to reboot to the system. However, once I've open the MAgisk App, the App suggested to finish installation and to install some additional files. I did not follow that suggestion. So, after that the MAgisk version was 22.1, and MAgisk App version 8.0.4. I have updated the App version up to the last version 23.0. However, after the update the MAgisk seems to me stopped to recognize the version 22.1 (see screenshot).
So, what can I do now? Uninstall the MAgisk app from the phone Settings and reflash the 22.1 in recovery again and to follow the App suggestion to install additional files after reboot? Or should I completely uninstall MAgisk in TWRP and start from the scratch then? In such situation will I able to keep the root or I should root the phone again?
I don't know about advanced fastboot flash mode in LOS Recovery, but John no longer recomends using custom Recovery due to inherent problems custom recovery can introduce. So there's no guarantees here:Hi guys,
i have a problem when trying to install the magisk_patched-xxx.img
The latest LineageOS (16.05.) and Magisk App (23) is installed. I'm on Oneplus 7 Pro.
When i'm in Lineage Recovery > Advanced FastbootD
and enter this command via cmd:
fastboot flash boot /path/to/magisk_patched.img
I always get this Error
sending 'boot' (98304 KB)...
OKAY [ 2.200s]
FAILED (remote: No such file or directory)
finished. total time: 2.250s
Does anyone know how to fix this?
Thanks in advance, you guys are great!
John himself accidentally caused the panic to increase. He said, "I tweeted an assumption caused by miscommunication; I was informed it to be non factual; I deleted the tweet. That's all, really."
I don't know about advanced fastboot flash mode in LOS Recovery, but John no longer recomends using custom Recovery due to inherent problems custom recovery can introduce. So there's no guarantees here:
Looks like your device is failing to find boot partition. Perhaps Recovery mode is not calling / switching to Fastboot mode properly, or other problem.
For official method, you need adb drivers on PC, img file in PC adb directory, phone in fastboot mode ('boot to bootloader') connected with usb, execute 'fastboot flash boot magisk_patched_boot.img'
Use of Custom Recovery is NOT part of Patch Image method referred to here:
Make sure you are using Magisk and not some custom version.So I assume I've got the right lsposed version as the mocking works where it didn't before (I just got a could not find location error 12 in pogo). Whenever I remove Pokemon from the deny list, it pops up again complaining about the OS not being compatible/supported.
What folders or files should I look out for? As far as I know I've gotten rid of any Magisk related stuff...
Updated to Shamiko 47 and it works:Trying with 0f71edee-alpha (23015) but Shamiko reports that Magisk is somewhat broken and Momo still finds Zygisk
All other things work for me (SafetyNet hence DenyList and Zygisk, Superuser grants, modules - and of course, I do testing without Riru)
PS: Tested also with all other modules disabled, still Shamiko reports the same error and fails to hide Zygisk
With the updated:
This one might be a bit more confusing.Great guide, thanks... I think I followed a similar guide from you a while back, but forgot full path requirement... Pinged you as I thought you'd come through!
I didn't say MagiskBoot was part of Magisk binary however... I clearly said 'magiskboot * binary * isn't working for me'. ...
Thanks for the method. PW
While catching up last night, I missed that you are not rooted.
unzip app-debug.apk lib*
adb push lib/YourDeviceArchitecture/* /data/local/tmp/
adb push boot.img /data/local/tmp/
adb shell chmod 0755 /data/local/tmp/*.so
/data/local/tmp/should be an empty directory.
PSA: MagiskHide of Magisk v23.0 no longer passes SafetyNet, even with BASIC evalType. Tested on my Pixel 4 XL running stock Android 12 with vanilla Magisk v23.0.
MagiskHide is *officially* dead. If you need any kind of root hiding, it's the perfect time to find alternatives.
There are already plenty of "root hiding" modules out there that I'm aware of, some even utilizing the latest features of Magisk canary.
I'm obligated to distance myself from any tamper detection circumvention, so I will not assist/promote any modules. Do your own research