Help me diagnose "Files has stopped" error - OnePlus 3T Questions & Answers

Device info:
Oneplus 3T, OOS 5.0.1 (Android 8.0), rooted with Magisk v15.3
Recently, my phone has been giving me an error message "Files has stopped " whenever I do anything that requires me to pick a file. and sometimes for no reason. Some examples include selecting a module to install in Magisk Manager, or selecting a file to attach in Gmail.
I highly doubt my root is involved, as I even reflashed the OOS 5.0.1 OTA to try to fix it. I've also tried wiping the cache of the apps File Manager, Files, and all caches in TWRP recovery.
The problem disappears if I reboot into safe mode, meaning it might be due to a rogue app. The problem also seemed to start after I used a USB OTG thumbdrive if it helps, that's the only major thing I remember doing.
Any ideas? Is there any info I can find in logcat to diagnose the problem?

Emeraldscorpion said:
...
I've also tried wiping the cache of the apps File Manager, Files, and all caches in TWRP recovery.
...
Click to expand...
Click to collapse
Try clearing the apps' data in Settings>Apps.
Also, have you installed a theme using Substratum? If so, try disabling it for the File* apps.
Sent from my OnePlus3T using XDA Labs

BillGoss said:
Try clearing the apps' data in Settings>Apps.
Click to expand...
Click to collapse
Yup, already tried clearing data in Settings.
BillGoss said:
Also, have you installed a theme using Substratum? If so, try disabling it for the File* apps.
Click to expand...
Click to collapse
Not using Substratum. I think it's safe to rule out any modifications to /system or any that require root, as the problem persisted even after I reflashed the 5.0.1 OTA.

If you're by chance using Xposed, then Scoop app might be helpful. But if not, you would have to connect your phone to PC, run logcat from there and pause when crash occurs.
With logs it will be easier to debug

przemcio510 said:
If you're by chance using Xposed, then Scoop app might be helpful. But if not, you would have to connect your phone to PC, run logcat from there and pause when crash occurs.
With logs it will be easier to debug
Click to expand...
Click to collapse
I've tried to browse it on-device using the app CatLog, but I have no idea what I'm supposed to be looking for! Any tips on what I should be focusing on?

Emeraldscorpion said:
I've tried to browse it on-device using the app CatLog, but I have no idea what I'm supposed to be looking for! Any tips on what I should be focusing on?
Click to expand...
Click to collapse
Maybe do it another way - start logging in an app, make Files crash and then stop. Paste the log at pastebin.com and link it here, we will see what's wrong

Been MIA due to exams.
I was trying the adb logcat method when I realised that the problem disappeared! Weird. Maybe the app causing it update again. Anyway, thanks for the help!

Related

! /data/adb/magisk_merge.img mount failed

Hello.
Unable to flash magisk modules.
! /data/adb/magisk_merge.img mount failed.
Even via twrp recovery is no possible to flash magisk modules, says something like error 1.
The device is a doogee mix 2.
I was forced to install the normal xposed framework just to use it.
Root works; only modules have problems.
Can some expert find a solution, please?
Thank you in advance to everyone gives good news!
MasterSheea said:
Hello.
Unable to flash magisk modules.
! /data/adb/magisk_merge.img mount failed.
Even via twrp recovery is no possible to flash magisk modules, says something like error 1.
The device is a doogee mix 2.
I was forced to install the normal xposed framework just to use it.
Root works; only modules have problems.
Can some expert find a solution, please?
Thank you in advance to everyone gives good news!
Click to expand...
Click to collapse
Hi, Can you attach logs while flashing ?? from both MM and recovery
MasterSheea said:
Hello.
Unable to flash magisk modules.
! /data/adb/magisk_merge.img mount failed.
Even via twrp recovery is no possible to flash magisk modules, says something like error 1.
The device is a doogee mix 2.
I was forced to install the normal xposed framework just to use it.
Root works; only modules have problems.
Can some expert find a solution, please?
Thank you in advance to everyone gives good news!
Click to expand...
Click to collapse
Known issue on some MTK devices. Loop mounting doesn't work.
There are lots of reports like this for Doogee... There's been some investigating into it in the beta thread, but as of yet there's no solution, I believe.
Hello!
Yes, of course!
Logs of magisk installer and TWRP recovery here:
https://drive.google.com/file/d/11vzWdbQfTtlmdc7VchaKxSGU4RkaOcog/view?usp=drivesdk
Ignore the crittografy error; I have tried to disable the crittografy and all is the same. Same problem.
In more, yesterday I had another annoying problem with magisk: before the options of the magisk app disappeared (there is the pic in the folder I attached. Then magisk is totally disappeared: magisk is not installed anymore in your device.
Tried to re-install magisk: nothing happens.
I have re-flashed the ROM and re- installed magisk: at moment is working.
Root files and SuperSU are not working.
I will open a new forum discussion for this problem.
Thank you in advance.
Greetings
MasterSheea said:
Hello!
Yes, of course!
Logs of magisk installer and TWRP recovery here:
https://drive.google.com/file/d/11vzWdbQfTtlmdc7VchaKxSGU4RkaOcog/view?usp=drivesdk
Ignore the crittografy error; I have tried to disable the crittografy and all is the same. Same problem.
In more, yesterday I had another annoying problem with magisk: before the options of the magisk app disappeared (there is the pic in the folder I attached. Then magisk is totally disappeared: magisk is not installed anymore in your device.
Tried to re-install magisk: nothing happens.
I have re-flashed the ROM and re- installed magisk: at moment is working.
Root files and SuperSU are not working.
I will open a new forum discussion for this problem.
Thank you in advance.
Greetings
Click to expand...
Click to collapse
The file is not accessible
Sorry.
Try now, please.
https://drive.google.com/file/d/11vzWdbQfTtlmdc7VchaKxSGU4RkaOcog/view?usp=drivesdk
MasterSheea said:
Sorry.
Try now, please.
https://drive.google.com/file/d/11vzWdbQfTtlmdc7VchaKxSGU4RkaOcog/view?usp=drivesdk
Click to expand...
Click to collapse
Looks like recovery can't decrypt /data, so that's likely an issue there. But it'd be easier to tell if you had provided the recovery log rather than a screenshot (Advanced - Copy log after trying to flash).
And, it would also be very useful if you had provided a Magisk log rather than only installation logs.
But, it's probably a moot point anyway. Like I said earlier, this is a known issue with loop mounting on Doogee devices (and other devices using Mediatek). No solution as of yet...
Didgeridoohan said:
Looks like recovery can't decrypt /data, so that's likely an issue there. But it'd be easier to tell if you had provided the recovery log rather than a screenshot (Advanced - Copy log after trying to flash).
And, it would also be very useful if you had provided a Magisk log rather than only installation logs.
But, it's probably a moot point anyway. Like I said earlier, this is a known issue with loop mounting on Doogee devices (and other devices using Mediatek). No solution as of yet...
Click to expand...
Click to collapse
Same here, provide good logs
Ok, thanks.
I will try to send you good logs.
About encryption, I have tried to disable encryption and to install all without encryption: nothing changes.
Before I must understand why magisk disappears from system, then I will collect logs about modules installation. Magisk is the only way to root this damned phone, SuperSU does not works.
Thank you in advance
MasterSheea said:
Ok, thanks.
I will try to send you good logs.
About encryption, I have tried to disable encryption and to install all without encryption: nothing changes.
Before I must understand why magisk disappears from system, then I will collect logs about modules installation. Magisk is the only way to root this damned phone, SuperSU does not works.
Thank you in advance
Click to expand...
Click to collapse
There was no need to start a new thread about that... You've already got this one going.
The screenshot of the Manager you provided simply showed a Manager without internet access. Completely normal.
About losing root completely, make sure you don't have any aggressive battery optimisation on the Manager. More here:
https://www.didgeridoohan.com/magisk/Magisk#hn_Randomly_losing_root
Ok, good, I close the other thread
Yes true, that is a normal screenshot of magisk offline. Yesterday I did formatted data to disable encryption and I lost all the other screenshots, but was like this: before all options disappeared, then magisk disappeared.
No, no aggressive battery optimization running, but I have installed greenify and amplify... Perhaps one of this app makes problem?
I wish to close the other thread, but I do not know how to do it.
How to do it, please?
MasterSheea said:
Ok, good, I close the other thread
Yes true, that is a normal screenshot of magisk offline. Yesterday I did formatted data to disable encryption and I lost all the other screenshots, but was like this: before all options disappeared, then magisk disappeared.
No, no aggressive battery optimization running, but I have installed greenify and amplify... Perhaps one of this app makes problem?
Click to expand...
Click to collapse
Make sure the Manager is removed from Battery optimisation and that it isn't selected I'm Greenify. It's not certain that this is the issue, but it's worth ruling out.
Other than that, a logcat of it happening, or even just a screenshot of the Manager when things aren't working. A Magisk log is also useful, of course.
MasterSheea said:
I wish to close the other thread, but I do not know how to do it.
How to do it, please?
Click to expand...
Click to collapse
Just let it be...
Oki.
I removed magisk from battery optimization.
I hope that at least the root will work.
But I seen in another thread that there is a solution known as f2fs workaround bug fixer. But is still not working. I hope that someone will fix it soon.
Anyhow, thank you for all
Move to thread https://forum.xda-developers.com/apps/magisk/guide-magisk-official-version-including-t3577875. Flash last zip. Move to magisk manager, install updated (2018.3.6) version. All modules should now install fine.
Hello.
Thank you for the answer.
I have tried to flash the zip without success.
No magisk installation found or installed version is not supported.
Error process 1.
The magisk version I have installed is v16. - 5.6.4(112).
The last one, suppose.
Any suggestions, please?
Thank you in advance ?
I made also the this attempt: I have flashed a magisk module using flashify.
The flashing was successful, but the module is not in the magisk list.
Can be a permission problem? Someone knows where is the folder of installed magisk modules, please? Perhaps is a permission problem and changing permissions will work...
Download f2fs-loopback-bug-workaround-2018.1.31.zip from the thread. Place it in Download folder of internal storage. Reboot to recovery. Flash zip in twrp. Reboot. Open magisk manager. F2FS Loopback Bug Workaround should be installed in modules. I hope any module can be installed from now on.
Dear Pragnan Saha,
Thank you for your answer.
I have tried to flash f2fs-loopback-bug-workaround-2018.1.31.zip, but without success.
TWRP says: No magisk installation found or installed version is not supported. Error process 1.
Some suggestions, please?
Thank you in advance
Didgeridoohan said:
There was no need to start a new thread about that... You've already got this one going.
The screenshot of the Manager you provided simply showed a Manager without internet access. Completely normal.
About losing root completely, make sure you don't have any aggressive battery optimisation on the Manager. More here:
https://www.didgeridoohan.com/magisk/Magisk#hn_Randomly_losing_root
Click to expand...
Click to collapse
What thread? And is it about exact the same error ! /data/adb/magisk_merge.img ... What this thread is about?
Do you know if there's a fix already? I'm on ext4 so f2fs loopback makes no sense for me
And @MasterSheea do you have a fix?
I've got exactly the same error with flashing modules, after clean flask is possible to install modules but after 1 reboot it fails

Magisk Manager Has Stopped. (Crashing on open)

Phone: LG Aristo (LGMS210)
ROM / Android version: Android 7.0
Root (yes/no): Yes
Xposed, or any other modifications: no
Any physical damage prior to defect: no
Magisk Manager keeps stopping. I opened it today and I got the message "Magisk Manager has stopped, open app again" I can't open it without it crashing. I've tried clearing cache, clearing data, reinstalling the APK. What do I do? This is a very big problem as i cannot run any rooted apps without getting the message that magisk has stopped.
Logcat (use ADB)?
Have you tried uninstalling Magisk and then reinstalling?
Have you tried uninstalling Magisk and then reinstalling?[/QUOTE]
I have tried clearing data, clearing cache, and uninstalling and reinstalling. I am VERY new to this so any help is good help.
MMJv3 said:
I have tried clearing data, clearing cache, and uninstalling and reinstalling. I am VERY new to this so any help is good help.
Click to expand...
Click to collapse
When you say you've uninstalled and reinstalled, are you talking about Magisk or the Magisk Manager? I'm talking about completely uninstalling Magisk by using the uninstall zip.
And what about that logcat?
I've got a similar problem. Mgisk Manager keeps crashing, but If I'm not connected to the internet the APP runs fine,
dafreaking said:
I've got a similar problem. Mgisk Manager keeps crashing, but If I'm not connected to the internet the APP runs fine,
Click to expand...
Click to collapse
Likely caused by a bug with checking the Magisk repo. It's been fixed but not yet released.
Clear Repo Cache
Disconnect from internet, go to settings and clear the repo cache helped me to open it again
Didgeridoohan said:
When you say you've uninstalled and reinstalled, are you talking about Magisk or the Magisk Manager? I'm talking about completely uninstalling Magisk by using the uninstall zip.
And what about that logcat?
Click to expand...
Click to collapse
I am facing the same issue. Magisk Manager crashes as soon as I open it (precisely within 3-5 sec of opening the app). Though the root is working perfectly and all apps requiring root behave as intended.
I am attaching a magisk log taken from the magisk manager within the 3-5 seconds window.
Kindly let me know if it's the correct log. I am a noob and still learning the intricacies.
Any help/guidance will be greatly appreciated
Magisk Manager works for me when I wait for a few seconds after opening the app. Cool Tool shows high CPU activity right after starting MM. Once the CPU idles again, MM works without crashing.
This is not a fix, but it may help until a new version gets released.
Didgeridoohan said:
Likely caused by a bug with checking the Magisk repo. It's been fixed but not yet released.
Click to expand...
Click to collapse
v5.8.0 just released does fix this.
Didgeridoohan said:
Logcat (use ADB)?
Have you tried uninstalling Magisk and then reinstalling?
Click to expand...
Click to collapse
Hi, Magisk crash when I go to download and try to search any moudle under it as soon I type two three words it crashes , I tried to use 16.7, 17.1 fresh install but still it does the same
I dont have any xposed root works fine, Im on crDroid Oreo running on g900v unlock bootloader
zfk110 said:
Hi, Magisk crash when I go to download and try to search any moudle under it as soon I type two three words it crashes , I tried to use 16.7, 17.1 fresh install but still it does the same
I dont have any xposed root works fine, Im on crDroid Oreo running on g900v unlock bootloader
Click to expand...
Click to collapse
I encounter the same issue today !!
eric672913 said:
I encounter the same issue today !!
Click to expand...
Click to collapse
Enter this url in the Magisk Manager settings, update channel,custom:
https://bit.ly/2MPKGY5
zfk110 said:
Enter this url in the Magisk Manager settings, update channel,custom:
https://bit.ly/2MPKGY5
Click to expand...
Click to collapse
Great! Thanks a lot.
For those of you that remain stuck on this issue: Magisk Manger doesn't like being used from an external SD card. If that is the case (see app menu) move it back to internal memory. It will work properly then.
JoostA said:
For those of you that remain stuck on this issue: Magisk Manger doesn't like being used from an external SD card. If that is the case (see app menu) move it back to internal memory. It will work properly then.
Click to expand...
Click to collapse
Thanks for this! Was exactly my problem.
Phone: Sony Xperia Z3 Compact (D5803)
ROM / Android version: Android 7.1.2 (LineageOS)
Root (yes/no): Yes
Xposed, or any other modifications: AFwall+ 3.0.4 (IPv6 disabled)
Any physical damage prior to defect: no
After flashing new LineageOS + Magisk.zip and installing the Magisk Manager Apk, the app is also crashing with no internet connection for me. But if I make airplane mode on, then it does work for me.
Magisk not opening or crashing again and again.
First of all desable or uninstall your superuser app and then open magisk manager app again it's very simple. When you done all of magisk installation then you can again activate or install your superuser app.
If it is not working then please tell me i can help you.
Nexus 6, 7.1.1, Magisk root - Google play and Magisk Crashing
Making a long story as sort as I can my Nexus 6 running Magisk to hide the root from Google play, and a stock 7.1.1 ( 7.1.1 (N6F27M, Oct 2017 if it matters) google image, was working flawlessly a couple years ago when I stopped using it.
A few weeks ago I turned it on, clicked Google play and it never opens. Just hangs on the app loading screen unless I disconnect the internet from it. I read somewhere that this may be an issue from something that Google implemented since then In there play services to detect root.
Connected to the internet (WiFi) I opened Magisk and was able to update the Manager app before it quickly crashed. I opened it again and there seems to be a Magisk update but app crashes too fast for me to click update.
What is going on here and/or how do I fix this?
Nexus 6, 7.1.1, Magisk root - Google play and Magisk Crashing SOLVED
jhavron said:
Making a long story as sort as I can my Nexus 6 running Magisk to hide the root from Google play, and a stock 7.1.1 ( 7.1.1 (N6F27M, Oct 2017 if it matters) google image, was working flawlessly a couple years ago when I stopped using it.
A few weeks ago I turned it on, clicked Google play and it never opens. Just hangs on the app loading screen unless I disconnect the internet from it. I read somewhere that this may be an issue from something that Google implemented since then In there play services to detect root.
Connected to the internet (WiFi) I opened Magisk and was able to update the Manager app before it quickly crashed. I opened it again and there seems to be a Magisk update but app crashes too fast for me to click update.
What is going on here and/or how do I fix this?
Click to expand...
Click to collapse
Updated Magisk Manager and was able to download the updated apk using the manager. I then rebooted to recovery and installed the new APK, cleared delvik, & cache, rebooted. Bam! SOLVED

N960U1 and could not update software. Need help.

Hi everyone,
So straight into the problem: I got my phone around the end of November 2018, which was when the Security Patch for that month came out. After that last update, I checked manually every month to see if there was another one. But after 12/14/2018, which was the last time I was able to check for updates, the phone would keep saying that it failed to download update, and a network or server error has occurred. I desperately need help.
View attachment 4685945
NahteT said:
So straight into the problem: I got my phone around the end of November 2018, which was when the Security Patch for that month came out. After that last update, I checked manually every month to see if there was another one. But after 12/14/2018, which was the last time I was able to check for updates, the phone would keep saying that it failed to download update, and a network or server error has occurred. I desperately need help.
View attachment 4685945
Click to expand...
Click to collapse
Boot into recovery & wipe the cache partition,reboot to system & then try again.
If that doesn't help,try using Samsung Smart Switch on your PC to update.
https://www.samsung.com/us/support/owners/app/smart-switch
KOLIOSIS said:
Boot into recovery & wipe the cache partition,reboot to system & then try again.
If that doesn't help,try using Samsung Smart Switch on your PC to update.
https://www.samsung.com/us/support/owners/app/smart-switch
Click to expand...
Click to collapse
Sadly, none of the two options worked for me. I have also tried booting into Safe mode, but the same problem would occur again. What else can I do, other than a factory reset?
NahteT said:
Sadly, none of the two options worked for me. I have also tried booting into Safe mode, but the same problem would occur again. What else can I do, other than a factory reset?
Click to expand...
Click to collapse
The only thing I can think of ATM is find the system apps responsible for system updates (two,I believe) wipe the cache & data ,if possible,from both,& try again.
If you are running an unadulterated version of the firmware that shipped with the phone,I'm stumped as to why you cannot update.
If you have any disabled apps perhaps enable them to rule out anything that might be causing this.
KOLIOSIS said:
The only thing I can think of ATM is find the system apps responsible for system updates (two,I believe) wipe the cache & data ,if possible,from both,& try again.
If you are running an unadulterated version of the firmware that shipped with the phone,I'm stumped as to why you cannot update.
If you have any disabled apps perhaps enable them to rule out anything that might be causing this.
Click to expand...
Click to collapse
Do you have to rely on ADB to wipe the cache and data? I found the two system apps that are used for Software Update (com.sec.android.soagent , com.wssyncmldm), but I can't seem to find the command code to do that.
NahteT said:
Do you have to rely on ADB to wipe the cache and data? I found the two system apps that are used for Software Update (com.sec.android.soagent , com.wssyncmldm), but I can't seem to find the command code to do that.
Click to expand...
Click to collapse
No,just navigate to Settings > Apps & tap on the 3-dot menu in the corner,select to view all/system apps & wipe each software update app.
If the buttons are greyed-out,then of course that can't be done.
KOLIOSIS said:
No,just navigate to Settings > Apps & tap on the 3-dot menu in the corner,select to view all/system apps & wipe each software update app.
If the buttons are greyed-out,then of course that can't be done.
Click to expand...
Click to collapse
I have just tried wiping the cache and data for the system apps, and also wipe the cache partition of the phone, yet nothing changes. I think what happened was that I accidentally disabled the two system packages for Software Update through ADB before this problem occurs, and now re-enabling them would have no effect.
NahteT said:
I have just tried wiping the cache and data for the system apps, and also wipe the cache partition of the phone, yet nothing changes. I think what happened was that I accidentally disabled the two system packages for Software Update through ADB before this problem occurs, and now re-enabling them would have no effect.
Click to expand...
Click to collapse
You can't re-enable apps that have been disabled by ADB w/o a factory reset.
In the future, you may want to consider using one of the Package Disabling apps that are available to avoid situations like this.
KOLIOSIS said:
You can't re-enable apps that have been disabled by ADB w/o a factory reset.
In the future, you may want to consider using one of the Package Disabling apps that are available to avoid situations like this.
Click to expand...
Click to collapse
If that's the case, then it wouldn't make sense that I were able to re-enable quite a lot of apps disabled by ADB. Or is this a special case where the crucial system apps that when disabled, they can't be re-enabled again?
NahteT said:
If that's the case, then it wouldn't make sense that I were able to re-enable quite a lot of apps disabled by ADB. Or is this a special case where the crucial system apps that when disabled, they can't be re-enabled again?
Click to expand...
Click to collapse
That would be my guess, otherwise, you should be able to update.
KOLIOSIS said:
That would be my guess, otherwise, you should be able to update.
Click to expand...
Click to collapse
Okay, I'll do a factory reset to see if this would solve the problem. Thanks for your help.
NahteT said:
Okay, I'll do a factory reset to see if this would solve the problem. Thanks for your help.
Click to expand...
Click to collapse
Please keep us posted on your outcome.
KOLIOSIS said:
Please keep us posted on your outcome.
Click to expand...
Click to collapse
So problem is solved: I did a factory reset, and the software update works just fine. I guess that the assumption about disabling crucial system apps caused them to not become re-enabled again must be right. Well I learned my lesson now - not to abuse ADB too much when it comes to bloatware. Thank you once again, I appreciate your help a lot.
NahteT said:
So problem is solved: I did a factory reset, and the software update works just fine. I guess that the assumption about disabling crucial system apps caused them to not become re-enabled again must be right. Well I learned my lesson now - not to abuse ADB too much when it comes to bloatware. Thank you once again, I appreciate your help a lot.
Click to expand...
Click to collapse
No problem, glad to be of help.
As for the ADB Removal & re-install of apps, I 1st heard about it from this XDA article/how-to:
https://www.xda-developers.com/uninstall-carrier-oem-bloatware-without-root-access/amp/
As it mentions the inability to re-install/re-enable apks, I just took their word for it & never uninstalled anything that I might need at some point.
That's why I like using package disablers, it's easily reversible without a reset.
Regardless, a factory reset isn't the end of the world, just a PITA at most.
Glad you got things going again.
Sorry to bother you again, but now I have problems with package disablers. I'm currently using a package disabler app, and it requires Device Owner App permission in order to disable bloatware apps, which can easily be done through ADB.
adb shell dpm set-device-owner com.pdp.deviceowner/.receivers.AdminReceiver
However, upon doing this, the lock screen of the phone will now show "This device is managed by your organization" at the bottom of the screen, and I don't feel comfortable about it. I have tried to uninstall the package disabler after done removing bloatware, but it wouldn't let me because the app is now a device administrator. I kind of screwed up myself after using the uninstall option inside the app, without knowing that it has completely uninstalled all the bloatware I disabled (instead of uninstalling the app itself), and caused my phone to stuck in boot loop, but I managed to fix that by another factory reset.
What kind of ADB command do I need so I can remove Device Owner App from the package disabler after I'm done disabling the bloatware?? (this is so ironic: disable a package disabler). Very sorry to disturb you again.
NahteT said:
Well I learned my lesson now - not to abuse ADB too much when it comes to bloatware..
Click to expand...
Click to collapse
Glad the problem was solved. My view is that concern with bloatware is a vestige of the past. On present-day phones, I'd guess that less than 0.1% of storage, memory, processor time, or battery charge are tied up with bloatware apps. So trying to identify and disable them won't have any noticeable benefit, and may well break things.
NahteT said:
Sorry to bother you again, but now I have problems with package disablers. I'm currently using a package disabler app, and it requires Device Owner App permission in order to disable bloatware apps, which can easily be done through ADB.
adb shell dpm set-device-owner com.pdp.deviceowner/.receivers.AdminReceiver
However, upon doing this, the lock screen of the phone will now show "This device is managed by your organization" at the bottom of the screen, and I don't feel comfortable about it. I have tried to uninstall the package disabler after done removing bloatware, but it wouldn't let me because the app is now a device administrator. I kind of screwed up myself after using the uninstall option inside the app, without knowing that it has completely uninstalled all the bloatware I disabled (instead of uninstalling the app itself), and caused my phone to stuck in boot loop, but I managed to fix that by another factory reset.
What kind of ADB command do I need so I can remove Device Owner App from the package disabler after I'm done disabling the bloatware?? (this is so ironic: disable a package disabler). Very sorry to disturb you again.
Click to expand...
Click to collapse
The message is just a generic one (as used when you grant admin rights for work e-mail,for example).
What it comes down to is if you trust the package disabler app & its developer,as I don't think there is any way to revoke the permission as long as you are using it to disable any apps at all.
I may be wrong on that,but,it seems like that's what's going on here.
If this still bothers you,then the next best solution is to continue using the disabling app long enough to determine which apps you are 100% certain are not needed/wanted.
Make a list & then switch to the ADB method.
That way,you get the admin rights to the disabler app off of your phone,but,you do give up the flexibility of the app as well.
The only way I see around your predicament is gaining root access & using the disabler app w/o admin rights,or,another app such as SD Maid Pro or Titanium Backup Pro.

Run GPS Joystick in system mode on stock (unencrypted, rooted with Magisk) firmware?

I'm trying to run GPS Joystick in system app mode on a stock firmware. The firmware is unencrypted and Magisk is installed.
On custom firmware it's as easy as to use Link2SD to make the GPS Joystick app a system app, but here it doesn't seem to work this way. The option in GPS Joystick remains grayed out.
After much manually copying around I got it to work one time and it worked great. Since it was a lot of trial and error I sadly can't quite reproduce the steps. Also sadly, it wasn't persistent. After a reboot of the system, the option was grayed out again.
So does anybody know of a way to get this to work in a persistent manner? Any help would be much appreciated!
Slowking said:
I'm trying to run GPS Joystick in system app mode on a stock firmware. The firmware is unencrypted and Magisk is installed.
On custom firmware it's as easy as to use Link2SD to make the GPS Joystick app a system app, but here it doesn't seem to work this way. The option in GPS Joystick remains grayed out.
After much manually copying around I got it to work one time and it worked great. Since it was a lot of trial and error I sadly can't quite reproduce the steps. Also sadly, it wasn't persistent. After a reboot of the system, the option was grayed out again.
So does anybody know of a way to get this to work in a persistent manner? Any help would be much appreciated!
Click to expand...
Click to collapse
You could try the magisk module app systemizer (terminal emulator)
That worked. Thank you very much.
Slowking said:
That worked. Thank you very much.
Click to expand...
Click to collapse
No problem. Glad it worked.
Strange. I tried systemize (LOS 17.1 / Magisk 20.4 / Galaxy S10e) and the option remains greyed out. Anyone else has this issue?
I have the same problem on a galaxy a8 2018 running Android 9, app is as system app but still can't enable system mode

how to open Magisk after it's hidden?

I outsourced rooting my device. Now I need access to Magisk to change the settings for the monitoring software I need to install. How do I open the Magisk app after it's been hidden? TIA!!!
It's in your app drawer, named "Manager".
gamoses said:
I outsourced rooting my device. Now I need access to Magisk to change the settings for the monitoring software I need to install. How do I open the Magisk app after it's been hidden? TIA!!!
Click to expand...
Click to collapse
Just run the app "Magisk Manager" or "Manager" (with the Magisk icon) that is on your app drawer.
Don't you have it? Well, then you don't have a proper installation of Magisk, at least the Manager is lacking. Download it (the apk) and install. Then open it and see if everything is fine or not. Check main Magisk release thread for links.
Thank you so much for replying! Magisk Manager is not in my app drawer, but it *is* listed in the device settings as an installed app. I just can't figure out how to open it. I assumed that app had also been hidden somehow. Advice?
Whoever you outsourced it to have done something that's not standard. Ask them...
Bummer. They'll probably charge me again. Thanks for your help, though!!!
gamoses said:
Bummer. They'll probably charge me again. Thanks for your help, though!!!
Click to expand...
Click to collapse
By the sound of it, they've messed up. So if I were you I would demand they fix things free of charge.
Didgeridoohan said:
By the sound of it, they've messed up. So if I were you I would demand they fix things free of charge.
Click to expand...
Click to collapse
Yeah, that didn't work. So I'm again trying to DIY...
Your wonderful guide says:
Unhiding the Magisk Manager
Go to the Manager settings and choose "Restore Magisk Manager".
Click to expand...
Click to collapse
But I can't do that because "Manager" is not in my app drawer.
You also have:
Starting MagiskHide manually
MagiskHide is enabled by default and should start automatically on boot. If it isn’t working, try toggling MagiskHide off and on in the Manager settings. If MagiskHide just won't start when toggling it in the Magisk Manager (check the Magisk log, it might have started but the Manager doesn't reflect it), try starting it manually. This can be done in a terminal emulator (as su) by executing the following command:
su
magiskhide --disable
magiskhide --enable
Click to expand...
Click to collapse
So I downloaded a terminal emulator and ran this command, but got this error message: su: unrecognized option '--disable'
Any more tips before I lose more money? Should I just try and reinstall Magisk completely? Having watched the tech guy do it the first time, I'm not sure I'm completely up for the task. Would it be easier after it's already been successful? Should this be straightforward, or am I better off handing over my wallet?
THANK YOU so much!!!
gamoses said:
Yeah, that didn't work. So I'm again trying to DIY...
Your wonderful guide says:
But I can't do that because "Manager" is not in my app drawer.
Click to expand...
Click to collapse
I'm curious... What happens when you want to grant superuser access to an app? Do you get the prompt to accept or deny?
I'm also curious what Magisk version you actually have installed. What's the result if you run this command in the terminal emulator:
Code:
magisk
You also have:
So I downloaded a terminal emulator and ran this command, but got this error message: su: unrecognized option '--disable'
Click to expand...
Click to collapse
You need to run the three commands separately, not all together.
Any more tips before I lose more money? Should I just try and reinstall Magisk completely? Having watched the tech guy do it the first time, I'm not sure I'm completely up for the task. Would it be easier after it's already been successful? Should this be straightforward, or am I better off handing over my wallet?
THANK YOU so much!!!
Click to expand...
Click to collapse
My first tip is to not trust your "tech" guy... From what you've described here it doesn't at all sound like he knows what he's doing.
Secondly, I would try to install the Manager and see what happens. Download the apk from here (that's the current version of Manager v7.2.0) and install that. If that works you're golden, if it doesn't report back...
I'm curious... What happens when you want to grant superuser access to an app? Do you get the prompt to accept or deny?
Click to expand...
Click to collapse
I don't know what this means or how to do that.
I'm also curious what Magisk version you actually have installed. What's the result if you run this command in the terminal emulator:
Click to expand...
Click to collapse
19.1
Secondly, I would try to install the Manager and see what happens. Download the apk from here (that's the current version of Manager v7.2.0) and install that. If that works you're golden, if it doesn't report back...
Click to expand...
Click to collapse
So I downloaded and installed this apk. I think. All that's necessary to do that is just click on it while on the phone, right? It said it was updating my previously installed Magisk Manager, so I assume it worked. But both immediately and after a reset, there is still nothing new in the app drawer. It still shows in my phone settings->apps, but that's it.
I've attached a log from my results in the terminal emulator regarding magisk and magiskhide. I'm sure I'm doing something wrong.
What launcher do you have? Sounds like the guy just his it from showing up the app drawer?
Sent from my MI 6 using Tapatalk
I was about to kick myself if it was that easy. Just installed Nova to check, and still no Manager app.
So should I just try to reinstall Magisk completely? Do I need to uninstall first? Is it as simple as opening the .apk on the device?
Hi, I have the same problem, did you find a solution?

Categories

Resources