Related
Today I updated to Magisk-v13.1, first it all worked grade and SafetyNet successfully past again in an App.
Then I tried it in another app, there it didn't worked, so I wanted to restarted the system and looked again if it worked, but then I had lost Root after reboot.
I reinstalled Magisk-v13.1 and tried it again and again, but it seems like it all is working grade, even Magisk Hide on apps like Root Checker and other, but on a certain app (Seqr) it isn't working and after reboot Magisk isn't working at all and Root is gone.
Magisk log, please. Both after using the troublesome app and after the reboot (you'll have to reboot into recovery and copy the log from /cache).
I'm at my wits end trying to get Magisk back!
(The backstory is that I had been running a DirtyUnicorns OS for a year just fine, but then Pokemon Go started failing to login. So it was time to update.)
Using a Samsung Tab 4 (SM-T330NU)
Formatted and installed stock OS/boot
Used Odin to flash "twrp-3.0.0-3"
Used TWRP recovery to update to "twrp-3.3.1-0"
Installed "Lineage OS 17" (and added Gapps) - made sure it booted and all was well
Booted into TWRP recovery and installed the latest "Magisk-v20.4"
Wiped cache and rebooted
Installed the latest "MagiskManager-v7.5.1" and got "Magisk is not installed"
After a great deal of searching I learned how this is supposed to be corrected:
Took the boot.img from the Lineage OS 17 zip,
Used Magisk to patch it, creating "magisk_patched.img"
Used TWRP recovery to install "magisk_patched.img" to the boot section
Wiped cache and rebooted
Still getting "Magisk is not installed"
Booted into TWRP recovery and installed the latest "Magisk-v20.4" just in case
Still getting "Magisk is not installed"
This is all after roadblocks for hours a day for a week trying to pass safetynet using Magisk on Lineage OS 16 for about a week, so I thought this fresh start would be easier and now I'm pulling my hair out.
Any suggestions would be helpful. I just want to be able pass safetynet and my ctsProfile match fails. Which I can't even begin to work on without Magisk core.
Thanks in advance.
First thing I would check is if the Manager is installed to external/adoptable storage. The Manager can't work properly like that...
https://www.didgeridoohan.com/magisk/Magisk#hn_Magisk_not_installed
Didgeridoohan said:
First thing I would check is if the Manager is installed to external/adoptable storage. The Manager can't work properly like that...
https://www.didgeridoohan.com/magisk/Magisk#hn_Magisk_not_installed
Click to expand...
Click to collapse
Thanks for the quick reply!
How do I check to see where it's installed and/or reinstall it to the proper storage? Because that could be it.
There's no SD card or USB device plugged in and I couldn't find more information online (I even scoured didgeridoohan.com before posting here).
Also, and this may be helpful, it appears the device is not rooted. Fx file explorer and root checker apps confirm this. So it's possible even with the steps I followed that Magisk core really isn't installed and the apk is telling the truth (I'm just at a loss to know how that's possible after flashing the zip and flashing the patched boot file, both in twrp).
If you have no SD card installed adoptable storage won't be an issue.
You can easily verify through TWRP if the core Magisk files have been installed. Check in /data/adb/magisk. It should contain busybox, magisk, magiskboot and magiskinit binaries, together with addon.d, boot_patch and util_functions scripts.
Seeing the recovery log from when you attempt to install the Magisk zip in TWRP might show us something. Also try the could also be a good idea trying the Canary release to see if there's any difference from stable v20.4.
(This thread can be locked/(closed?)/answered)
I tried my damnedest and nothing worked. So I wiped/formatted lineage-17.1-20200512 and installed lineage-17.1-20200419. THIS was the ease with which I was accustomed to installing Magisk (Recovery install and immediately working on boot). Sadly, other problems abound and they are outside the scope of this subforum.
Just in case anyone reads this and cares:
- GPS Joystick was a no-go because apparently Lineage has a not-so-nifty feature that blocks the "draw over apps" android feature if your RAM is below some secret threashhold, which prevents the entire app from functioning.
- Fake GPS can take getting used to, and I'm used to it and love it, but the location and routing keeps crashing in the background, which means pogo closes when I tab back to start it back up again.
- Regardless of which I use I am rubberbanding back to my house... despite using all the tricks I can find or think of (yes, including 'smali patcher', specific app settings, systemizing the GPS app, setting off/on mock locations, etc)... but I think it's because this OS has no unique setting for the GPS data to be "device only".
Problems one and two are due to the ****ty ram on this Samsung tablet, which I've always known was an issue, so I suppose it might just be time to buy a phone specifically for this purpose. From what I read, the best cost effective option is an iPhone SE, and I'm truly not an Apple fan (I certainly would not risk my own phone being bricked or even merely wiped).
Not sure how I used it for the last year without this many issues, but it seems like that's over now unless I want to deal with DirtyUnicorn OS again, and that was it's own nightmare sometimes.
Thanks all for reading, but especially Didgeridoohan for replying and for all the resources on your pages and threads.
Hi, im running Android 10 with OneUI 2.5 rooted by Magisk v.21 on my Samsung Galaxy NOTE 10 Lite,
Root is working correctly, i have root access for donated FDE.AI, X-Plore file manager and etc..
Im using few Magisk modules, like Viper4Android and they works well too.
But, any atempt to download or install Magisk module from its own online reposirory ends with "Error downloading file", and atempt to check SafetyNet status gives me "SafetyNet API error" afzer hiting Ok to download SafetyNet API...
I searched on google, and here on the forum for similar problems, but i found topics from 2017 year (outdated)
Can anyone hp me solve this prob please?
Both those issues (module download error and SafetyNet API error) suggest that there are Internet connection problems.
There's been a couple of similar reports, but those have usually been fixed by clearing data for, or reinstalling the Manager.
Also make sure that you don't have any firewall rules or similar that might be restricting internet access for the Manager.
Thx for respone. I tried to delete Managers cache and App data too, nothing changes. I also tried to reinstall App, but no change.
About internet connection, yesterday I had to downgrade Magisk from v.21 beta to v.20.4 stable for unexpected random reboots 5times a day.. I done that in Magisk Manager App, selecting "Direct install (recommended)". Magisk downloaded necessery files without any problem and flashed it.
And, i dont use any third party security apps (antivirus, firevall).
So, any idea? After downgrade magisk reboots solved, here reported issue no.
No idea. A logcat might show what's up:
https://www.didgeridoohan.com/magisk/MagiskHelp
Heres my logcat, filters: level error, keyword magisj
Heres my new logcat, printed at error level verbose, filtered by keyword magisk.
I see only one problem, file permission (write permission), but where magisk wont write? Im able seriously give 777 permissions to this folder ?
Or did anybody see anything else?..
For now, nothing changes in my phone configuration.. FW version the same as in 1. Post, magisk v 20.4, actual stable magisk manager.. I also tried canary magisk manager, but the canary version wont load module list and crashed down at all, including UI.
KubikMichal5 said:
Heres my new logcat, printed at error level verbose, filtered by keyword magisk.
I see only one problem, file permission (write permission), but where magisk wont write? Im able seriously give 777 permissions to this folder
Or did anybody see anything else?..
For now, nothing changes in my phone configuration.. FW version the same as in 1. Post, magisk v 20.4, actual stable magisk manager.. I also tried canary magisk manager, but the canary version wont load module list and crashed down at all, including UI.
Click to expand...
Click to collapse
I have not had any opportunity to look at your log (and the new one won't download since it seems like the XDA attachments server is acting up again, good thing there's a new one on the way).
But, that the Canary Manager will crash when you try to access the modules list is yet another sign that your issue is that the Manager cannot get an internet connection (that's a currently known bug).
Thx u for your time . So, its known bug, but is there some way to solve it and get magisk manager functional? Or its not a global issue and its not specific to each user
It's a known issue that the Manager will crash when you enter the modules download section without an internet connection. It's not a common issue that the Manager can't get a connection at all.
I still suspect that there's something on your device that is blocking internet access for the Manager somehow.
Have the same problem.Magisk Manager 8.0.2 on Android 9,Magisk is working fine,but i become no update info for modules and i cant download any module,but 3 days ago all was ok,weird.
I think, that is not any app blocking magisk internet connection. The last stable mahisk manager dont have any problem to load online module list, and download of magisk core is aleays possible, as install ing core too....
But, i dont have time right now for test it, it is possible to reboot to safe mode and there run magisk?
I still cant understand that some app blocking magisk internet connection...
Look at my screenshot of magisk manager latest stable version, the connection working, magisk showing modules wich got updated today......
Sorry, but i still hope, that magisk manager do not have internet connection error, in screen, he knows about the module updated version, but it still wont download..
Im ready for N770FXXU6CTJ2 update, im going to flash it right now... Im confused of magisk support,
Is that last one with the Stable or Canary Manager? There seems to be something weird going on, and there have been some similar reports.
I suggest that you switch over to Canary again (Magisk and Manager) and grab a verbose logcat when you have connection issues. Upload that to a new GitHub issue where you also make sure to give all possible details as to what works and don't work on the stable Manager contra what works and doesn't work on the Canary Manager.
That way, better eyes than mine might be able to take a look at it and see if there is indeed something going on.
Nevermind... See below.
I solved reported issue on my device...
The reason is, Lucky Patcher and blocking ads on device...
I opened LP, opened Toolbox/Block Ads and pressed Clear local hosts file... Now everything is working fine...
Ok... Nice to know I wasn't wrong. :good:
Sad to see that app being used...
KubikMichal5 said:
I solved reported issue on my device...
The reason is, Lucky Patcher and blocking ads on device...
I opened LP, opened Toolbox/Block Ads and pressed Clear local hosts file... Now everything is working fine...
Click to expand...
Click to collapse
Awesome,hughe thanx,works for me.Cheers!!!
KubikMichal5 said:
I solved reported issue on my device...
The reason is, Lucky Patcher and blocking ads on device...
I opened LP, opened Toolbox/Block Ads and pressed Clear local hosts file... Now everything is working fine...
Click to expand...
Click to collapse
Life saver! It solved my problem too. Huge thanks!
KubikMichal5 said:
I solved reported issue on my device...
The reason is, Lucky Patcher and blocking ads on device...
I opened LP, opened Toolbox/Block Ads and pressed Clear local hosts file... Now everything is working fine...
Click to expand...
Click to collapse
Thanks!!!!
I'm having an issue also with passing safetynet on Razer Phone 2 (Cheryl 2). Rooted with Magisk 22.1 and TWRP arter Kernel. Had a rough time getting the "new" all-in-one Magisk installed properly. I'm using adfree for an adblocker. I've cleared the hosts file and rebooted MANY times, to no avail. Thinking I may need to uninstall Magisk and go back to 20.4 and install the old Magisk Mgr. app. Any help would be appreciated. If you need log files, let me know. I DO have root as Ti Backup, ROM Toolbox, adfree all have root access.
I have two G9+ phones, both rooted with Adaway installed. One has the stock ROM (Android 10) & the other has LineageOS 18.1.
On the phone with Lineage there are no ads when running a particular game. The same version of the game on Moto Android 10 has ads.
There is some app I don't understand called Moto GameTime that appeared when I started the game but I have disabled it. (I tried to move GameTime out of system using system/app mover but I got an error: "Could not remount /system".)
Still, Google ads appear with the stock ROM despite having Adaway.
Everything looked ok in Adaway. It tells me its three sources are up to date. When I try to reload & reinstall hosts from those sources I get an error: "Unable to copy hosts file to /system partition. Please check Magisk systemless module is enabled the reboot." (Magisk Manager shows Magisk 23.0 is installed.)
Something is causing problems that seem to involve lack of access to the /system partition. I don't know if that is related to the appearance of ads on the stock ROM, but any thoughts? How can I fix this?
As I've stimulated no response here, I took the ugly step of wiping the phone, flashing the experimental LineageOS and restoring everything from backup (not a fully successful process because the data for certain apps was not backed up by Super Backup & Restore).
At least there are now no ads getting through onto the phone.
The issue you are having is related to stock Android 10. It does not allow you to make any changes to the system partition, as it won't allow you to mount it as r/w. There is a workaround for it (currently in development stages). It's a flash able zip script that dumps the super partition "fixes" it and flashes it back. Your phone must have the bootloader unlocked and be rooted for it to work. It currently works for A only devices without any issues, but is throwing an lpmake error 73 for mysterious/unknown reasons, but a fix is in the works. I will post a link when I get home.
I assume the phone is rooted with Magisk which is a systemless root method. Even with older devices /system remains unmodified. All changes are only overlays/modules managed by the Magisk App.
doktorspin said:
(I tried to move GameTime out of system using system/app mover but I got an error: "Could not remount /system".)
Click to expand...
Click to collapse
This could also be done with a own module. See instructions here.
Keven11 said:
The issue you are having is related to stock Android 10. It does not allow you to make any changes to the system partition, as it won't allow you to mount it as r/w.
Click to expand...
Click to collapse
Thanks. I decided to replace the stock ROM with LOS18.1. That problem solved. (Got a new one: can't use data over the phone connection.)
doktorspin said:
Thanks. I decided to replace the stock ROM with LOS18.1. That problem solved. (Got a new one: can't use data over the phone connection.)
Click to expand...
Click to collapse
I fixed the issue by ditching Android 10 for LOS 18.1. But thanks for the pointer.
doktorspin said:
Thanks. I decided to replace the stock ROM with LOS18.1. That problem solved. (Got a new one: can't use data over the phone connection.)
Click to expand...
Click to collapse
I'm glad you got it figured out. The data issue, along with many other bugs will be rectified any day now with the new release. The issue you are having with LOS 18.1 is because at the time of development the kernel for A11 hadn't been released by Moto yet. However, they did finally release it a little under 2 weeks ago. So the new version of it will be much much better. It will be linked to the same link I posted. It's just a matter of time now, and not much of it.
Telegram Odessa Devs and testers group: https://t.me/joinchat/SaZ2BX0M8bQmkioW
So, an OTA caused a loss of root (pixel 6 pro, unlocked). Tried to go into a hidden magisk and disable modules, but everything greyed out, unable to. Tried to uninstall the manager (I was using an old MagiskAlpha build), and thought it worked, though it must have left something behind. Updating wouldn't work - would give me a failure.
Flashed new factory image, installed new magisk manager, patched boot.img in new magisk manager, loaded boot.img, and I have root; adb shell su works, all my old apps that worked with root work, but no magisk manager recognizing that I have root - and therefore no modules - working. So, no charging management, safetynet is borked, etc. Have uninstalled/reinstalled mm numerous times. No luck. Tried loading it from adb, etc.
I've dug through adb shell pm list packages and can't find anything that looks like an old version of magisk at all anywhere anymore. I think I had three different versions on the phone. They are all gone. But no luck with a freshly installed manager. Still can't see root even though it's there. Any ideas?
Of note: I have a work profile and two users on the phone. However, I can't find anything even using --user for all three users. Only thing even close I see is com.lsposed.manager still installed. That shouldn't be a factor, but I can't think of anything at this point.
TB checker, under "check root" gives pass for everything except SU binary, 2nd SU binary, root via native, and magisk specific.
Under Check xposed, I have fail for dual/work profile and xprivacyLua, and com.topjohnwu.magisk under PM Sundry APIs. Everything else is Pass.
I had never granted TB checker root before; Termux on the other hand works fine with su (as does adb shell), and Root Essentials shows root fine.
Magisk Manager was downloaded from topjohnwu's github, then I manually added the canary URL, and updated to canary. No luck.
Any other ideas?
One other thing... /data/adb/magisk was dated; all the other directories in /data/adb were new, but magisk was from my last update of MagiskAlpha, and when I looked at util_functions.sh it was aligned to my old (uninstalled) magisk alpha build
So, the /data/adb/magisk tipped me off. I pulled the hidden apk info from the magisk.db, and from there was able to (while rooted) manually delete all the references to the hidden apk string (just did a find /data/* | grep [hidden package name] ) and once they were all deleted, deleted everything from /data/adb - the magisk.db and everything - and then next time I went into magisk, it informed it was incorrectly configured, I pressed okay, it fixed itself, and full root in magisk was restored.
had to reinstall all modules, but that wasn't a very big price to pay. Safetynet fixed (google pay worked just fine at the store yesterday), xprivacylua, etc., all worked.
As of right now, other than a citi app *****ing that I'm possibly rooted (and then it still works fine anyway), haven't had any issues with leaving magisk unhidden, so not going to hide it again unless I need to. Wasn't worth the PITA to fix it if something like this happens again.