Never had any issues with Magisk on my S8+.
However I flashed toe v17.1 Magisk zip today using TWRP and it booted just fine (first time).
Then I used a service disable app to disable my Samsung Location service (like I did a million times before for Pokémon GO) and rebooted.
It stuck on the Samsung logo.
After a force reboot it booted straight to the system (to my surprise). However the system isn't really usable at that point as an annoying message keeps popping up all the time telling me, that I have to restart my phone to use my "new" (it isn't new) SIM card.
No matter how often I reboot, the message keeps popping up.
Any ideas?
I have the same problem with my RN4. Had to downgrade to 16 from 17!
Hope they fix it soon!
Edit: i completely uninstalled magisk and reinstalled it through twrp. And that fixed the problem for 17.1!
I should have tried it. Instead I installed the V17.1 through TWRP multiple times as it worked very often on the first reboot after doing that.
However at least at every second reboot that annoying popup appeared again.
I ended up giving up and taking the "opportunity" to set up my phone from scratch. I made a backup of the most important apps with Titanium Backup and flashed the newest stock firmware from Samsung (now I have Oreo) then I flashed TWRP again and installed Magisk from there. Now my phone is working again.
Unfortunately I forgot to backup my media files of WhatsApp (only the app data with Titanium) and restored it from there instead of letting it restore from Google Drive.
Now I have my chat history but all my media files (images/videos/voicemails) are gone for good and since I noticed that too late, WhatsApp did backup that "new state" to GoogleDrive so all media files got deleted from there as well and now I'm doomed.
Related
I have a Samsung Galaxy J1, runnning Android 4.4.4 and TWRP 2.7.1. My phone has only 2.1GB of usable storage space.
As I installed using a zip file, SuperSU was a system app and cannot be moved to my SD card. This app was taking up 300ish MB on my system, and it came to the point where I couldn't even send a voice note on WhatsApp any more because of the little free space I had. When I saw that SuperSU was taking this much space, I tapped the [Uninstall Updates] button, finished uninstalling and my phone froze. It stayed frozen for about 3 minutes, when it started getting really hot. Then I removed the battery.
Upon restarting, the phone was very slow and unresponsive. I figured it could be a memory leak caused by some app, so I ignored it. However, my phone started locking up completely. I restarted again, opened SuperSU and disabled root since I thought that could be the cause of the slowness. It became more responsive, however apps like FolderMount and Kernel Aduitor stopped working. So I tried to fix it.
I went and flashed the latest SuperSU zip, but that did not fix the problem. I updated the binary from within the app, but that didn't work either. I selected [Cleanup for permanent unroot] inside the app, restarted, reflashed the zip and tried again. Nada. Finally, I went and dirty flashed my phone's stock firmware through Odin, reflashed TWRP, then SuperSU and that still didn't work.
I then hit up adb shell on my computer and entered the terminal, doing some /system exploration. I went to /system/xbin and noticed the lack of a su file. I then grabbed the file from my properly rooted Galaxy Tab 3 running CM 13 and SuperSU, then I pushed the file to /system/xbin using my recovery and set the persmissions to 777. I then enabled Superuser from within SuperSU, ran the su command in adb shell and got a "not executable: magic 7F45" error. I tried disabling and reenabling root in SuperSU, and then the system just hanged at the su command.
So can someone guide me into fixing my root? Lots of functions such as a custom LMK curve (for browsing Reddit using Sync and listening to music using Poweramp at the same time [having low RAM is a struggle]) and using FolderMount (to mount my massive WhatsApp folder onto my memory card to save on storage space) depend on it.
Hello World,
before I explain my problem, I am most humbly asking for one small favour:
Please(!!) nobody give me any advice along the line of: Just do a factory reset and start from scratch
I've got almost a thousand apps installed on my system and I'm in no mood to even try to reconfigure it all over again.
Some time ago I installed the latest beta of Cyanogenmod on my Samsung Galaxy Note Tablet SM-P900.
After some time I encountered so many quirks with it, that I decided to flash back to the latest stable build 12.1-20151029 (Android v5.1.1).
Since I was always able to upgrade w/o wiping data, I did the same here, but right after the downgrade the system started misbehaving.
Matter of fact, I could only boot through to the desktop, once I had removed some google.* related dirs from the data/data location. Right afterwards I reinstalled the affected apps from backup and that fixed that.
Unfortunately during the proces of peeking and poking in data/data I messed up some ownership/permission settings.
I also managed to fix those via an old backup (via: chmod/chown --reference), *but* now I am getting a popup message telling me:
"There is something wrong with your data partition..." everytime I reboot the system.
Afterwards I can work just fine with the tablet, but every 3rd or 4th day it suddenly reboots - then being stable again for another couple of days.
If I could only find out what fault this messages refers to, I could fix it manually - but I couldn't find anything useful by reviewing the logcat info.
DESCRIPTION
If you have the Pixel Experience module installed on your phone and installed Google Phone from the Play Store or ever tried to use a patched Google Phone version (such as this one), you may have noticed that Google Phone force closes when you try to search for a contact or while opening the keypad. This Magisk module attempts to fix that and it works by replacing your non-AOSP contacts storage with Google's own version, the one supported by Google Phone.
IMPORTANT NOTES
Supports Android versions from Android 7 (Nougat) to Android P.
It will remove any phone/dialer/contacts/people applications from your phone (if supported) because they are incompatible with Google's Contacts Storage.
You should only install this module if you want/need to use Google Phone and Google Contacts.
TESTED/SUPPORTED DEVICES
HTC 10 (Sense based ROMs).
Note: It should work with other devices but I have no means no test them myself, I can only rely on the community to test this for me.
SPECIAL INSTRUCTIONS
Install the Magisk module as usual but DO NOT reboot your device just yet.
Go into "Settings » Accounts & Sync" and disable "Automatically sync data".
Go into "Settings » Apps" a, look for "Contacts Storage" (it's a system app) and clear application data.
Reboot your device now!
Go into "Settings » Accounts & Sync" and enable "Automatically sync data".
Google Phone should now work without force closing, hopefully.
Note: If you ever want/need to disable this module, you should also follow the procedure above (disable module, disable data synchronization, clear contacts storage data, reboot, and re-enable contacts synchronization).
DISCLAIMER
Install this module at your own risk.
Developer is not responsible for what you do on your device.
Please take all necessary precautions (like a nandroid backup) before installing this module.
DOWNLOADS
Google-Contacts-Storage-v0.0.0-TESTING.4.zip
XDA:DevDB Information
Google Contacts Storage, Tool/Utility for the XDA Community Apps
Contributors
rfgamaral
Version Information
Status: Testing
Current Beta Version: v0.0.0-TESTING.4
Beta Release Date: 2018-08-02
Created 2018-08-01
Last Updated 2018-08-02
@rfgamaral after installing magisk module and rebooting i keep getting android.process.acore has stopped.
I cannot get rid of it. By pressing ok all the time i managed to arrive to Apps but there is no Contact Storage app to clear data/cache after the reboot.
stathis95194 said:
@rfgamaral after installing magisk module and rebooting i keep getting android.process.acore has stopped.
I cannot get rid of it. By pressing ok all the time i managed to arrive to Apps but there is no Contact Storage app to clear data/cache after the reboot.
Click to expand...
Click to collapse
I also got that error when developing this module but I never got it after installing/enabling it, only after disabling it.
For some reason, the system does not recognize the /system/priv-app/ContactsProvider/ContactsProvider.apk (although the file is there). I'm not sure how to fix this to be honest, so I recommend you restore your backup to get you back to a working state. Maybe try the whole process again (makre sure you follow every single step) and instead of rebooting the system after installing the module, reboot to recovery and wipe dalvik/ART and cache. If that doesn't help, restore the device again until a solution for this problem is found.
Like I said, I also had this problem and because I live on the edge, I didn't make a backup of my system (idiot me). I had to make the system recognize the ContactsProvider.apk file and wen into recovery, deleted, copied it back from my ROM, set proper folder/file permissions, wiped dalvik/ART and cache and rebooted, the problem was gone. I installed my module again and it worked. But I'm honestly afraid to disable it and get that error back.
Which is weird because I'm replacing this file systemlessly, that's the whole point of Magisk. Maybe I'm doing something wrong, I'm no expert... We'll probably need help from someone with more knowledge on the whole Android system. But for the record, I currently have the version available on this thread installed on my phone. I have the Pixel Experience module installed and installed Google Phone from the store, it doesn't force close and all features seem to be working. I just need to get this module stable.
@stathis95194 Were you able to restore your device? I hope so... I've uploaded a new test version, didn't change much, not sure if it fixes anything.
rfgamaral said:
@stathis95194 Were you able to restore your device? I hope so... I've uploaded a new test version, didn't change much, not sure if it fixes anything.
Click to expand...
Click to collapse
Yeap I always take a nandroid before messing with the phone. Let me try the new version and report
Sent from my HTC 10 using Tapatalk
@rfgamaral soooo after flashing 0.0.4 i faced the same issue with android.process.acore has stopped popping all the time.
This time i took a different approach and didn't restore my nandroid. Instead i dirty flashed my LeeDroid rom.
Rebooted and lo and behold, stock dialer and contacts were missing and google phone was working perfectly. No crashing on searching (nearby places is working)
Now i need to test caller id and spam filter
I will keep testing and let you know.
stathis95194 said:
@rfgamaral soooo after flashing 0.0.4 i faced the same issue with android.process.acore has stopped popping all the time.
This time i took a different approach and didn't restore my nandroid. Instead i dirty flashed my LeeDroid rom.
Rebooted and lo and behold, stock dialer and contacts were missing and google phone was working perfectly. No crashing on searching (nearby places is working)
Now i need to test caller id and spam filter
I will keep testing and let you know.
Click to expand...
Click to collapse
Awesome, glad you got it working.
Now I just need to understand why installing this module crashes android.process.acore... But it's a bummer that this is happening, a little price to pay, I guess? At least until a fix is found... That and that whole install procedure which is required to avoid other different crashes because of incompatible storages.
Hi
I'm running 2.42.400.3 on U11.
I installed this and google phone from
https://forum.xda-developers.com/android/apps-games/app-google-phone-v14-0-175904292-bubble-t3708218
Dialer kept crashing so I installed your mod.
After that,com.android .phone keeps crashing.
I unistalled it and then I got acore crashing.
I restored feom nandroid but for some reason kept getting the acore crash, so I completely uninstalled magisk.
Now.... everything works. Even the dialer.
I'm really not sure what happened but.... thanks
gunnerhk said:
Hi
I'm running 2.42.400.3 on U11.
I installed this and google phone from
https://forum.xda-developers.com/android/apps-games/app-google-phone-v14-0-175904292-bubble-t3708218
Dialer kept crashing so I installed your mod.
After that,com.android .phone keeps crashing.
I unistalled it and then I got acore crashing.
I restored feom nandroid but for some reason kept getting the acore crash, so I completely uninstalled magisk.
Now.... everything works. Even the dialer.
I'm really not sure what happened but.... thanks
Click to expand...
Click to collapse
That's really weird, on so many levels... :/
Screenshot as proof :laugh:
This morning Pokemon Go stopped working on my phone. I found this which said to use the "Hide Magisk Manager" option from within Magisks Settings page, and then delete the MagiskManager folder from the SD card. I did that, restarted my phone, and Go started working again. Oddly though, Chrome wouldn't work, and kept crashing with "Unfortunately, Chrome has stopped." (whether I was actively trying to use it or not). Off of a fresh restart I could open chrome, but if I tried to load any webpages it would stay loading forever.
To try and fix that, I went back into Magisk and hit the "Restore Magisk Manager" option, and restarted my phone. Now, my phone won't boot -- it gets stuck loading on the splash screen. I seem to only be digging myself a deeper and deeper hole with each thing I do. How do I get my phone back up and running?
I'm running the latest RR (I think it's 6.1.0?)
Flash the Magisk uninstaller from here https://forum.xda-developers.com/ap...v7-universal-systemless-t3473445/post68966662
You should then be back to an unrooted state.
Sent from my [device_name] using XDA-Developers Legacy app
Have you tried reflashing your Rom?
Also, what did you expect to Halen with magisk, after you have decided to delete it's manager folder?
Sent from my ONEPLUS A3003 using Tapatalk
Logue1021 said:
This morning Pokemon Go stopped working on my phone. I found this which said to use the "Hide Magisk Manager" option from within Magisks Settings page, and then delete the MagiskManager folder from the SD card. I did that, restarted my phone, and Go started working again. Oddly though, Chrome wouldn't work, and kept crashing with "Unfortunately, Chrome has stopped." (whether I was actively trying to use it or not). Off of a fresh restart I could open chrome, but if I tried to load any webpages it would stay loading forever.
To try and fix that, I went back into Magisk and hit the "Restore Magisk Manager" option, and restarted my phone. Now, my phone won't boot -- it gets stuck loading on the splash screen. I seem to only be digging myself a deeper and deeper hole with each thing I do. How do I get my phone back up and running?
I'm running the latest RR (I think it's 6.1.0?)
Click to expand...
Click to collapse
Repackaging and restoring the Magisk Manager should not have anything to do with the issues you started experiencing. If you can get your device up an running again (as already suggested, uninstalling Magisk might be a good way), could you recreate the problem and grab a logcat when Chrome crashes and when the phone get's stuck on boot.
RASTAVIPER said:
Have you tried reflashing your Rom?
Also, what did you expect to Halen with magisk, after you have decided to delete it's manager folder?
Sent from my ONEPLUS A3003 using Tapatalk
Click to expand...
Click to collapse
Deleting the MagiskManager folder from the internal storage is harmless. It's just used to store downloaded Magisk zips, module zips and saved logs. It'll be recreated when needed. Pokemon Go have started to detect this folder and use it as a sign of a rooted device. Deleting it is one way of getting PoGo running again.
I'm trying to keep myself in SuperSU, is easier and compatible with almost any app, I know that development stopped. But I feel that Magisk is a great tool but can be complicated.
First try using your computer to create a file without a name and with disable_.magisk as an extension.
Kinda like. disable_magisk
And use TWRP to copy this to /cache.
See if it boots up.
Hello I have the same problem unauthorized_device_lockout
The problem its that i had used super su before. Uninstalled it. Now i dont have any root and still happening (in pokemon go) please help
Logue1021 said:
This morning Pokemon Go stopped working on my phone. I found this which said to use the "Hide Magisk Manager" option from within Magisks Settings page, and then delete the MagiskManager folder from the SD card. I did that, restarted my phone, and Go started working again. Oddly though, Chrome wouldn't work, and kept crashing with "Unfortunately, Chrome has stopped." (whether I was actively trying to use it or not). Off of a fresh restart I could open chrome, but if I tried to load any webpages it would stay loading forever.
To try and fix that, I went back into Magisk and hit the "Restore Magisk Manager" option, and restarted my phone. Now, my phone won't boot -- it gets stuck loading on the splash screen. I seem to only be digging myself a deeper and deeper hole with each thing I do. How do I get my phone back up and running?
I'm running the latest RR (I think it's 6.1.0?)
Click to expand...
Click to collapse
Hi i found a fix, you just need to reflash magisk patched boot.img from your phone(hope you backed it up) and the system.img / custom os (i didnt even have to wipe my data) lol
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.