yashsingh1/xdaforums huggingface dataset:
[Magisk] jcmm11:
1 - if you flash a stock (unrooted) boot image then yes, you will lose root.

2 - exact details depend on your phone and if you have a/b system partitions or not. See https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation but generally speaking if you have a/b partitions then you can "turn off" Magisk then turn it back on. If you don't then you can't - you'll have to reinstall Magisk after applying the OTA and rebooting. (Note, you can't successfully apply an over the air OTA if you've modified system or vendor in any way, including just mounting it rw. Custom kernels will also prevent over the air OTAs)

3 - I have no clue. A more detailed explanation of the issues you're having may be helpful.

Changing (only) the boot image will NOT erase any data.
[Magisk] Javi22:
So I also noticed Google pay is no longer working. But also not my other bank apps, is it coincidence?

Are they supposed to still working? Safety net passes but all my apps says phone is rooted

My problem is even if I uninstall magisk, I can not use them! Any help here?

Enviado desde mi Pixel 2 XL mediante Tapatalk
[Magisk] garylawwd:
2000 posts? You should know better brother https://xdaforums.com/apps/magisk/discussion-google-pay-magisk-discussion-t3906703/page46
[Magisk] Javi22:
Yes... I'm sorry, not my best day. Thank you so much!

Enviado desde mi Pixel 2 XL mediante Tapatalk
[Magisk] jonners59:
THANK YOU.

Now just need to find the time to rebuild the phone... Is there ever a good one.
[Magisk] Mixedability:
Yes, I've tried this endlessly...it may well be a timing issue, but the endless lack of success tells me it can't be done now. It has a small hole marked 'reset' which I can poke and it switches off. But just quickly touching the power button brings it straight to life as if it were just sleeping rather than rebooting.

If I were to disconnect the battery would this put it into a different state? One that I could work with?

Is it possible that with an unlocked bootloader and having only flashed the boot.img, I may actually not have any recovery to go to anyway? I had wiped user data and cache before flashing only the boot.img. I feel a knob for being negligent but I need to know what, if anything, I can now do...
[Magisk] kotuamoalt:
Have you tried holding the reset button for a longer amount of time? Say, 15 to 30 seconds?
[Magisk] R3van:
Hello,

i`m on Stock Samsung ROM and rooted with Magisk.

Today i`ve got a message from Magisk Manager that an update is available.

Magisk Manager showed me that there were no root installed.

I started TWRP, flashed latest Magisk (18.1) and rebooted. since then i`m Stuck at the flashing Samsung Logo.

I`v hidden the Magisk Manager app within itself with a random package name.

Now i would like to uninstall the Manager app via TWRP to see if that helps. I`ve found a package with a name that looks like randomly arranged letters, can i assume that this is Magisk Manager?
[Magisk] martyfender:
More than likely, yes, because most apps have a name like the app name or developer name in the package name like com.topjohnwu.magisk.

An easier way would have been to unhide the Magisk Manager in settings, before you tried to update, though.
[Magisk] R3van:
Removed the app, but it doesn`t helped.

Now i`m running out of ideas
[Magisk] martyfender:
Have you tried running the Magisk uninstaller,followed by reflashing Magisk in TWRP, all before rebooting? When running the uninstaller, you should see a message that the stock boot.img was successfully restored. If the stock boot.img is not successfully restored for some reason, you might have to flash the stock boot.img before reflashing Magisk, all before rebooting.

If you run the uninstaller, you will have to reinstall any modules you are using.

You could also try the latest Canary build.
[Magisk] R3van:
I tried that already, uninstalling reflashing, without rebooting between, with rebooting between, deleting Dalvik&Cache and so on.

When i flash the uninstaller, the message says always that stock image was successfully restored.

Whe i try to boot to System after uninstalling Magisk i get immediatly bootloops.

Can i securely flash stock BL with Odin without losing anything?

Another idea that i have is maybe to related to swift installer overlays. I tried to find them in twrps file manager and via adb but no luck here.

Edit: Tried Canary Build, no luck
[Magisk] kazu.galaxy:
Magisk 18.1 doesnt work on Japanese S8+

SC03JOMU1BSA1

Oreo

After installed Magisk 18.1, boot loop.

Please fix.
[Magisk] Windowlicker001:
Hi, yes....over a minute and it comes back to life afterwards (having to press power button for 15 secs) to the flashing red triangle again.

Could I ask if someone can kindly confirm that I have managed to actually kill this tablet?

To sum up:

I have tried to reinstall the stock rom through a Mac's terminal command line on an unlocked bootloader having wiped user data and cache. Unfortunately I ignorantly only flashed the boot image and not the entire stock rom folder which included the recovery. Now, on boot it flashes the Android red triangle man and says 'supported API:3'. I can only switch this off by poking the reset button. It cannot be recognised through ADB shell via USB.

Are my attempts to find a recovery mode futile as I have managed to delete the initial recovery?

Is there a scenario by which an Android device can be rendered completely useless, and if so, have I found it?

I've read of SP Flash tools...can this toolkit communicate (via Windows machine)?

How do manufacturers install onto a completely empty disk in the first place, and is there a route to recovery via that?

Again, I am very grateful for this community for the support offered...trying to learn by the empirical route certainly comes at a price!
[Magisk] lyoks:
Hey guys, only magisk version works for me, all that above leads to a reboot in recovery (twrp). Any ideas how to fix?
[Magisk] jcmm11:
What device? What ROM/Android version? Install logs? Any other possible relevant details? (No logs means everything is working just fine)
[Magisk] guest4711:
Either force Magisk to run in core-only mode or if you are on an current Magisk use the filemanager in TWRP to delete the module from /data/adb/magisk/modules/

To enable core-only mode you can open a shell/terminal from TWRP and enter

touch /cache/.disable_magisk

- as far as I remember. Search in this thread to find the correct spelling if it does not work.

Edit: The spelling is correct. Please note the dot before disable; the char behind is an underline...
[Magisk] Wani Aamir:
Whenever i uninstall any app my phone locks,am facing this issue from past 4 days,i don't know why it is happening,any solution?

Am on Magisk 18.1
[Magisk] lyoks:
Device: asus zenfone 3 max zc553kl, lenovo x103f, All android 7.1.1.

This is a problem not only for me, but also for other guys.
[Magisk] guest4711:
Without proper logs it's impossible to tell you what's going on and how to solve your problem. But I don't think it's related to Magisk...
[Magisk] Ssnurzel:
I have a big problem. Sometimes, i get the lockscreen issue and cant pass it. Then the device reboots. I tried the newest canary uninstaller and magisk build but no sucess.

What can i do?

Thx in advance for the answer.
[Magisk] The War Profiteer:
It didn't work either, it was probably a compatibility issue of Viper4Android since the v4a shell file was running even when I uninstall it by flashing the image again. I just flashed the rom again, I have no time to spare such stuff, cuz I already spent 4 hours on this... Thanks anyways.

---------- Post added at 07:53 PM ---------- Previous post was at 07:45 PM ----------

You should provide the logs of failed installations. Flash the image, then let the stuff happen. Then go back to recovery and use "adb pull /cache/magisk.log", send us the log.
[Magisk] martyfender:
I have that happen sometimes on recent Canary and unofficial builds, randomly, on 5 devices.

I have never reported it.

For me it usually occurs with the first boot bootloop, when I have to force a shutdown, then a cold boot. I have reported the bootloop.
[Magisk] martyfender:
I used SP Flash tools on my first Android tablet, given to me when a co-worker asked me to help him restore a Samsung S3. I had never used an Android device, but I was able to restore his device for him so he gave me a Android tablet and I used that tool to flash a modifed rom on it.

The SP Flash tool is for devices that have MTK chipsets on them. Unless you know otherwise, I don't believe your tablet has an MTK chipset. I was not able to determine from the manufacturers site if it had MTK, or not.

I don't really know how to answer your above questions.
[Magisk] jcmm11:
Did you install Viper as a module or via Viper4Arise? Just asking because you said that it got removed by flashing the ROM, which indicates A.R.I.S.E. to me.

If so try the apk from XDA Labs instead. See the relevant thread https://xdaforums.com/android/apps-games/app-viper4android-fx-2-6-0-0-t3774651

Or, my current preferred solution, JamesDSP Magisk module + Sauron + AML

https://xdaforums.com/android/apps-games/app-reformed-dsp-manager-t3607970

https://xdaforums.com/android/software/soundmod-ainur-audio-t3450516

https://xdaforums.com/apps/magisk/mod-audio-modification-library-t3745466
[Magisk] Mixedability:
Thank you ..yes MTK Quad core device. So, can you tell me if I have the MTK drivers, a Windows machine and SP Flash tools that I am able to a.communicate with the tablet and b.flash the stock ROM back onto it?
[Magisk] martyfender:
The only way to know for sure is to try it. It has been too many years, but it is very finicky. I remember having problems loading a proper scatter file. I think if you have the stock rom, which I did not, you should not have any problems.

As I recall, there are tutorials to be found on the net for the tool. Other users here, with more experience, may have some better input.

Here is one such tutorial I found by searching:

https://androidmtk.com/flash-stock-rom-using-smart-phone-flash-tool

The tutorial mentions removing the battery, if removable. Like you, I had a tablet so I just started with the unit shut down, I did not disassemble and remove the battery.

I am afraid, that is about all I remember and that old tablet had Kitkat on it. I flashed a custom rom because the stock was not available for it.
[Magisk] chooks06:
[MENTION=9771902]Mixedability[/MENTION]

Just sharing my previous experience..

To add on, SPFT loads the device only when device is powered OFF.

If you've the Vicom and MTK drivers already installed (I assume that you have previously connected the tablet to the Windows PC), there should not be any problem.

However, I've had a situation where my phone couldn't power down..

What I did was open SPFT, load the scatter file, click download, connect device then used the buttons on the device to force shut down. The moment it was detected as shut down, SPFT will start download (red line on the app window).

HOWEVER, this part can be touch and go. Some devices (like some Umidigi, Chinese branded models) require pressing volume or power button (in the powered off state) to enable SPFT to detect the device. I've had a Ulefone that required this and Umidigi that did not.

AFAIK, it won't break the device any further trying this.

Important that the scatter file is the correct one. Once loaded in SPFT, it will show the MTK model number - ensure it's same as the one fitted ( like [MENTION=8126387]martyfender[/MENTION], I couldn't find info on what it actually is on your device).

I suggest you Google more about using SPFT to get a better idea. Or you can head to Umidigi forum under ROM. There are some instructions how to flash using SPFT though not all may apply to another OEM device, but it gives a good idea.

Edit..I agree with [MENTION=8126387]martyfender[/MENTION] that SPFT is finicky.. At least for the earlier versions.
[Magisk] seb_131:
Hi All

sorry if am asking a question already answered, but did search but didn't find.

I have a poco F1 with latest stock MIUI ROM (and original recovery) and the latest magisk installed. All was working fine, but one day all the modules were not loaded, and everytime I am installing one, after the reboot the module list is still empty. Note that root and hide-root are still working fine.

I uninstalled and reinstalled Magisk and its Magisk manager, but this is still the same.

Any idea how to fix this weird issue?

Thanks.

Seb

Found out: the Core Only mode was activated (I don't remenber having done this... but it is working fine :) )
[Magisk] Paresh18shah:
Magisk not working properly in a f2fs system..

after every module update and restart all modules are gone and after flashing magisk again modules are back..

So is there any problem with f2fs support for magisk.?
[Magisk] Didgeridoohan:
Lots of problems. That's why the image approach has been ditched in the current code base. Either wait for the next release (should be arriving as a public beta shortly) or give the Canary builds a try (expect bugs).
[Magisk] Paresh18shah:
Sir Facing this problem in stable as well as canary builds..
[Magisk] Didgeridoohan:
In that case you've got other issues. Providing more details and logs is the only way to know more about what's going on...
[Magisk] Paresh18shah:
logcat_magisk1 is after flashing magisk18.1

logcat_magisk2 is after flashing one module so after reboot modules are gone

and image of adb folder there are 2 .img files

Hope this will help..
[Magisk] Didgeridoohan:
Those logs unfortunately doesn't show much. The Magisk log and possibly module installation logs would be more interesting.

And that screenshot tells us that you're not using an up-to-date Canary release... Please do when providing logs (look at the link I posted, please, it's all explained there).
[Magisk] Paresh18shah:
Ok Sir I had checked all the instructions.

I am using stable 18.1 build and Magisk manager Version 7.0.0.

Take magisk log as you said please check and confirm.

So just want to know is problem in f2fs or magisk.

(And sorry for spamming but need permanent solution)

Hope you will help.
[Magisk] Didgeridoohan:
Logs from v18.1 is unfortunately (almost) completely useless in this case... I say "almost" because they show that Magisk isn't properly installed on your device. Why I have no idea.

But... Like I said in my previous posts and like it says in my guide, you need to use the current Canary debug release when posting about stuff like this. Anything else is pointless...

Apart from the Magisk debug log and module installing logs that I've mentioned earlier, the Magisk install log might also be useful.
[Magisk] ManDone.vRs:
java.lang.NullPointerException: Attempt to invoke virtual method 'java.lang.String java.lang.String.toLowerCase()' on a null object reference

at com.topjohnwu.magisk.adapters.ReposAdapter.filter(ReposAdapter.java:134)

at com.topjohnwu.magisk.fragments.ReposFragment$1.onQueryTextChange(ReposFragment.java:101)

at android.widget.SearchView.onTextChanged(SearchView.java:1250)

at android.widget.SearchView.-wrap9(Unknown Source:0)

at android.widget.SearchView$8.onTextChanged(SearchView.java:1776)

at android.widget.TextView.sendOnTextChanged(TextView.java:9371)

at android.widget.TextView.handleTextChanged(TextView.java:9458)

at android.widget.TextView$ChangeWatcher.onTextChanged(TextView.java:11943)

at android.text.SpannableStringBuilder.sendTextChanged(SpannableStringBuilder.java:1252)

at android.text.SpannableStringBuilder.replace(SpannableStringBuilder.java:573)

at android.text.SpannableStringBuilder.replace(SpannableStringBuilder.java:504)

at android.text.SpannableStringBuilder.replace(SpannableStringBuilder.java:502)

at android.view.inputmethod.BaseInputConnection.replaceText(BaseInputConnection.java:843)

at android.view.inputmethod.BaseInputConnection.setComposingText(BaseInputConnection.java:616)

at com.android.internal.view.IInputConnectionWrapper.executeMessage(IInputConnectionWrapper.java:396)

at com.android.internal.view.IInputConnectionWrapper$MyHandler.handleMessage(IInputConnectionWrapper.java:85)

at android.os.Handler.dispatchMessage(Handler.java:106)

at android.os.Looper.loop(Looper.java:176)

at android.app.ActivityThread.main(ActivityThread.java:6635)

at java.lang.reflect.Method.invoke(Native Method)

at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:547)

at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:823)

This show me when y try to search a module rn5 ...
[Magisk] Didgeridoohan:
What Manager version is that from? Unless it is from the latest Canary release (currently Manager v7.0.0 build 200), it isn't really interesting...

If you just want to try to fix it on your device, you can try clearing the repo cache in the Manager settings or clearing data for the Manager itself.
[Magisk] Paresh18shah:
Here is canary debug build logs
[Magisk] Didgeridoohan:
Don't use Universal SafetyNet Fix. As you have found, it is a severely broken module that messes with Magisk's internals...

There are other (working) alternatives that don't break Magisk available in the Magisk repo (Manager - Downloads).
[Magisk] sam0658:
Magisk doesn't detect phone app

Hi guys,

I'm running a rooted HTC 10 and I'm trying to use the Barclays banking app. I believe this app uses dependencies to check for root as it requests access to make phone calls. I've found other posts which say to get the Barclays app working I need to use Magisk hide to hide the Barclays app, the phone app and hide Magisk manager itself.

My problem is, Magisk hide doesn't show the phone in the list of apps so I'm unable to hide it.

Does anyone know how to fix this?

Thankyou in advance ?

PS. Hope I'm posting in the right place ?
[Magisk] jcmm11:
Try 3 dot menu on upper right. Check "show system apps"
[Magisk] sam0658:
Yeah I've tried that but it still doesn't show up. Thanks for the suggesting though ?
[Magisk] Mrw126:
idk
[Magisk] Paresh18shah:
Thank a lot Sir..Problem solved.. .:highfive::fingers-crossed:

So Universal SafetyNet Fix causing that problem.
[Magisk] Muskym:
I have a question.

I have Magisk 15.3 on a rooted Galaxy note 4. with Magisk Manager version 6.0.0. I want to update Magisk to version 18.1 and I've read that the best way of doing that is through the Magisk manager app, but I don't see how to update Magisk in the app. I updated the app to 7.0.0 but now it says it is not compatible with older versions of Magisk lower then 18.1 and closes.

Can someone tell me what I'm missing?
[Magisk] ManDone.vRs:
Tried . Didn't work .... M 17.1

5.9.1 (139) apk
[Magisk] Didgeridoohan:
So, like I said: not really interesting... Thats such an old release that you can't expect much support. If clearing repo cache and data for the app doesn't help it's likely a bug that's been fixed in later releases.

---------- Post added at 06:17 ---------- Previous post was at 06:14 ----------

Download the release zip here and flash from the Modules section of the Manager (+ button and pick the zip, like you would when flashing a module manually).
[Magisk] Muskym:
[MENTION=4667597]Didgeridoohan[/MENTION]

Thank you very much! Worked great! I don't know how I missed that, maybe because it was too simple. :)
[Magisk] Jos_Hdez22:
I have a silly question ... where can I get the previous versions of magisk? both stable and canary? I need the stable version 17.3 and the canary version 118, I hope you can help me.
[Magisk] martyfender:
https://github.com/topjohnwu/Magisk/releases/tag/v17.3

https://github.com/topjohnwu/magisk_files/tree/0d02d13b6eb636094f4c2179b5c629338d72ea50/canary_builds
[Magisk] husky69:
Installed Magisk 18.1 on my LG G6 (rooted stock ROM) without problems, and just recently it started to crash occasionally for no reason obvious to me. Tell-tale sign the notification that there's a new version available. Upon opening Magisk Manager it reports Magisk not to be installed at all.

Rebooting fixes that for a while, but it's a nagging problem.

Anyone else witnessing this? How can I help track this down?

Thanks for telling :)
[Magisk] riyosakura:
Hei there.

Com.telkom.mwallet AKA LinkAja app still recognize magisk as root even though i've already hide the app.

Repackaging magisk manager helped though, but it would be nice if it work without repackaging magisk.

Or anyother suggestion for solution beside repackaging magisk?

The app used for payment with nfc.

Edit :

I'm using canary magisk 18.2.
[Magisk] Didgeridoohan:
There's really no drawback to having the Manager repackaged... Only other alternative would be to uninstall the Manager altogether, but that's hardly optimal.
[Magisk] Umbardacil:
Suddenly, my Google Pay says, that I can not pay with this phone anymore. It seems that Magisk doesn't hide it good anymore. What could cause that? Everything is green under Magisk manager... Debugging turned of....
[Magisk] garylawwd:
https://xdaforums.com/apps/magisk/discussion-google-pay-magisk-discussion-t3906703/page46
[Magisk] Peter_File:
I got a problem with magisk manager installation. Get the "app not installed" error when trying to install the apk of 7.0.

As google play did not work anymore I tried to install 7.1 manager from the gpay thread. As it didn't work I uninstalled it via launcher but there seem to be leftover files that I can't find? Help highly appreciated.
[Magisk] ashyx:
To get this to work I used the magisk uninstaller, installed latest canary.

Hid the app and magisk manager, hid Google services framework.

Don't be fooled by granting the app root access when it asks.

Don't install busy box.
[Magisk] zipsu:
*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
Build fingerprint: 'Xiaomi/sagit/sagit:8.0.0/OPR1.170623.027/V9.2.3.0.OCAMIEK:user/release-keys'
Revision: '0'
ABI: 'arm64'
pid: 23368, tid: 23368, name: opjohnwu.magisk >>> com.topjohnwu.magisk <<<
signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0xc
Cause: null pointer dereference
x0 8000000000000000 x1 0000000073137550 x2 000000000000000a x3 0000000000000000
x4 0000000000000000 x5 0000000000000000 x6 00000000707403a0 x7 0000000000002600
x8 cbe019a27b893ad8 x9 0000000000000024 x10 0000007feee7e7c0 x11 0000000000000eca
x12 000000006fb03bc8 x13 0000000000000001 x14 000000000000001a x15 0000000000000008
x16 0000007305617648 x17 0000007308488d70 x18 0000000000000020 x19 0000007feee799e0
x20 8000000000000000 x21 0000000073137550 x22 0000000000000000 x23 0000000000000025
x24 000000730767a410 x25 0000000000000040 x26 000000730561c138 x27 0000007feee7e5b0
x28 0000000000000001 x29 0000007feee79800 x30 0000007305482184
sp 0000007feee797a0 pc 0000007305108948 pstate 0000000080000000

backtrace:
#00 pc 00000000000db948 /system/lib64/libart.so (_ZN3art9ArtMethod23GetOatQuickMethodHeaderEm+44)
#01 pc 0000000000455180 /system/lib64/libart.so (_ZN3art12StackVisitor9WalkStackILNS0_16CountTransitionsE0EEEvb+512)
#02 pc 000000000045998c /system/lib64/libart.so (_ZN3art12StackVisitor16ComputeNumFramesEPNS_6ThreadENS0_13StackWalkKindE+84)
#03 pc 0000000000256348 /system/lib64/libart.so (_ZZN3art15instrumentationL27InstrumentationInstallStackEPNS_6ThreadEPvEN19InstallStackVisitor10VisitFrameEv+512)
#04 pc 00000000004553f0 /system/lib64/libart.so (_ZN3art12StackVisitor9WalkStackILNS0_16CountTransitionsE0EEEvb+1136)
#05 pc 0000000000251a38 /system/lib64/libart.so (_ZN3art15instrumentationL27InstrumentationInstallStackEPNS_6ThreadEPv+148)
#06 pc 00000000000dcdf8 /system/lib64/libart.so (_ZN3artL43StackReplaceMethodAndInstallInstrumentationEPNS_6ThreadEPv+124)
#07 pc 000000000047d28c /system/lib64/libart.so (_ZN3art10ThreadList7ForEachEPFvPNS_6ThreadEPvES3_+48)
#08 pc 00000000000dca30 /system/lib64/libart.so (_ZN3art9ArtMethod16EnableXposedHookERNS_18ScopedObjectAccessEP8_jobject+772)
#09 pc 00000000000047cc /system/lib64/libxposed_art.so (_ZN6xposed29XposedBridge_hookMethodNativeEP7_JNIEnvP7_jclassP8_jobjectS5_iS5_+616)
#10 pc 0000000000002908 /data/dalvik-cache/arm64/system@framework@XposedBridge.jar@classes.dex (offset 0x2000)

I can't get magisk manager 7 nor its canary version running no matter what I try, uninstalling etc. makes no difference. Only MM 6.1 works without crashing.. Using magisk 18.1 on oreo.