I haven't had any issues using Magisk until today.
I upgraded from Android 7.0 to 8.1 (I wanted to be able to use Swift Installer), now that it's been released for my device.
After flashing Magisk, the phone isn't detecting my SIM, and there's a constant error message that pops up, but it's so fast that I never have the chance to see what it actually says.
Is there a fix for this?
Samsung Galaxy J3 (SM-J327U).
17.3 was working perfectly fine on the phone running 7.0. It's broken with 8.1.
I doubt that it is a Magisk error. It is either your SIM card going bad or an issue your system.
Sent from my SM-G900V using Tapatalk
Kaliaila said:
I doubt that it is a Magisk error. It is either your SIM card going bad or an issue your system.
Sent from my SM-G900V using Tapatalk
Click to expand...
Click to collapse
It's not a system issue nor a SIM issue. It's ONLY after flashing Magisk on 8.1. It doesn't occur on 7.0, it doesn't occur on 7.0 with Magisk flashed, and it doesn't occur on 8.1 without Magisk flashed. It's the combination of Magisk and 8.1.
Everything works fine using any other combination with Magisk, or just stock ROMs alone.
The IMEI, etc, is showing UNKNOWN after I flash Magisk on 8.1.
Are you using stock or a different rom?
Sent from my SM-G900V using Tapatalk
Kaliaila said:
Are you using stock or a different rom?
Sent from my SM-G900V using Tapatalk
Click to expand...
Click to collapse
I'm using stock both with and without Magisk flashed. I don't use custom ROMs.
I source my firmware from Updato.
Well, just know that on other phones and different Roms that have had that exact problem, it would occur sporadically with and without Magisk being installed. In most cases it was a bug in the rom and not Magisk.
I personally do not know how it could be caused by Magisk.
Sent from my SM-G900V using Tapatalk
Kaliaila said:
Well, just know that on other phones and different Roms that have had that exact problem, it would occur sporadically with and without Magisk being installed. In most cases it was a bug in the rom and not Magisk.
I personally do not know how it could be caused by Magisk.
Sent from my SM-G900V using Tapatalk
Click to expand...
Click to collapse
It's not possible to revert to 7.0 without a backup is it?
I would wait and see if anyone else replies first, but I think there are ways but they are not necessarily simple.
You would probably be better off asking that in a forum for your specific phone.
Sent from my SM-G900V using Tapatalk
Had the same issue, no Magisk installed. I dropped my phone a few times. Noticed sim card warning a few boot ups later. So I opened up the back and took out card and put it in again. No problem.
Same issue here. After flash Magisk 17.1 or 17.3, system doesn't detect SIM card. Android 7.1.2, MTK6580 soc. Works relatively well with the Magisk 16, however there is always the message "emergency call only" and I must manually change radio frequency. So yes, Magisk affects radio operation on some devices.
In another device with Snapdragon, no issues related.
Related
I have rooted my note 3 N900A with towelroot and installed safestrap v3.75 .
Everything seems to have installed correctly, when I check to see if I have root with root checker pro, it says I have root and that I have busybox installed as well.
When I go into safestraps/recovery and do a backup of my stock slot. Everything works for the backup. But then when I try to install a rom in any one of the slots it goes through the whole process just fine until the very end when it says in red fail.
It does the fail with every rom that I try to install. And if I try to do a restore in any slot with the backup that I made in the recovery it will fail as well.
So this just leaves me with having to use the stock slot with the original stock phone software.
Also when I try to install titanium backup on my phone that is saying it's rooted, The app won't work because it says that I don't have root. There was another app that would not work when I tried to instead it too because life the same reason. It said that I don't have root as well.
After trying to look for a solution to this, I found that there is an app that I could try to fix what has happened, called
SELinux Mode Changer
After I installed that app and tried to use it. The app made it look like it was working but really it was not doing anything. When I went into the phone info in settings, it still said that selinux was still enforcing.
Does anyone know if there is a solution to this? I would really like to be able to install a new rom on one of the other slots, heck ide settle for being able to put my stock backup on one of the other slots besides the stock slot.
Sent from my Rooted AT&T N900A Samsung Galaxy Note 3 Using XDA Premium HD app
I ran into a similar situation.. After wiping everything and then manually updating my stock to Kit Kat (MLG) I was then able to load custom roms in available slots. I used safestrap version 3.72 along with busy box. Also be sure to format the slot and wipe the cache and dalvik after installation.
The only ROM I am unable to install is Dynamic Kat xtreme. After loading that guy, the flash just fails.
UPDATE: I for unknown reasons to me, was able to successfully install one of my restore files to slot 1. Then after it reboots the phone acts as if it is restarting correctly, but ason as it gets past the safestrap logo with recovery/startup. It goes right into the phones recovery, and it keeps saying that it is installing "multiple csc or something.
Can someone help me with this?
Sent from my Rooted AT&T N900A Samsung Galaxy Note 3 Using XDA Premium HD app
After hitting rock bottom with many of the roms, I finally checked out my external sdcard and realized that it was having issues. After using a different card, I was then able to install all roms for testing.
I had to downgrade safe strap to 3.72 for it to work on my device.
Sent from my SM-N900A using XDA Free mobile app with Dynamic Kat 4.2 the kat is awesome.
For some strange reason everything stayed to work and I have no idea how..but I now have another problem the aliancerom that i installed on slot 1 works fine with the exception that the aliancerom that i installed won't let the wifi work. After i put in the info for the at&t 3g, The phone's 3g worked but the home wifi won't. Any ideas?
Sent from my Rooted AT&T N900A Samsung Galaxy Note 3 Using XDA Premium HD app
marknderm said:
For some strange reason everything stayed to work and I have no idea how..but I now have another problem the aliancerom that i installed on slot 1 works fine with the exception that the aliancerom that i installed won't let the wifi work. After i put in the info for the at&t 3g, The phone's 3g worked but the home wifi won't. Any ideas?
Sent from my Rooted AT&T N900A Samsung Galaxy Note 3 Using XDA Premium HD app
Click to expand...
Click to collapse
if it is the kk version it needs to be installed in the stock slot other slots do not work with kk yet
Have anyone succesfully got Xposed Framework running on stock 5.0.2 L90 D415??
I think you have to get a new recovery (twrp) in order to install xposed and then install the rom again.
Correct me if I'm wrong.
I flashed the zip file, wiped cache, and reboot. My phone booted up but i got com.android.phone force closing. Weather app also force closes. And since com.android.phone force closes you get no signal.
My experience...did the lollipop ota for tmo, didn't really care for it much. Used one click root, added flashify and twrp custom recovery and did a nandroid backup. Installed xposed arm zip and it just stuck on the lg logo for quite a long time. Second attempt i did the wipe after installing xposed and it made it past lg logo to tmo boot and hung up. In my reading, saw something about xposed will not work on stock firmware. But isn't xposed for people that want to mod stock roms? Main thing is...back up before anything. Have already used mine 4 times.
So I originally flashed the latest xposedv66 and was not successful. Found xposed-arm-20150213b.zip everything looked good, even had signal. Like you, weather app stopped. So, I tried file manager to get to the installer and it stopped also..
If you're going to do it, BACK UP BEFORE YOU INSTALL. I cannot get it to work, reason why? I do not have the logs but if you install liveboot and activate it, then install the zip and reboot, liveboot will show you a command that is supposed to activate but fails and retries. Its essentially a bootloop but without the reboot. It will not allow you to boot without that feature being activated. Do it for yourself but remember to back up all system partitions and restore them. When you reboot after restore, the system will do the whole 'optimizing apps 1 out of 200' thing so don't worry if it takes a while to boot. Will have more on this when I get home to my laptop.
Xblackberryuser said:
So I originally flashed the latest xposedv66 and was not successful. Found xposed-arm-20150213b.zip everything looked good, even had signal. Like you, weather app stopped. So, I tried file manager to get to the installer and it stopped also..
Click to expand...
Click to collapse
Can you share that xposed? Because im trying to find one that works and can only find latest version..
Enviado do meu LG-D405 através de Tapatalk
Warimation said:
Can you share that xposed? Because im trying to find one that works and can only find latest version..
Enviado do meu LG-D405 através de Tapatalk
Click to expand...
Click to collapse
Here you go.
Found another one from March and April, but I haven't tried them.
Xblackberryuser said:
Here you go.
Found another one from March and April, but I haven't tried them.
Click to expand...
Click to collapse
I tried the one you suggested and I successfully rebooted. However, Lollipop ran slower and then I opened the alpha apk that came on the official thread. It said alpha 3.0 was installed but not activated. So I just decided to restore to before I installed. Xposed is being worked on and its in its alpha stage. Its bound to have bugs. Since THE D415 already has root, I'm fine to wait for an official version of Xposed that works to come out. Also, Even though I had 2 Gigs of data left on internal, there was a notification pestering me saying there was little to no storage left on my phone. Otherwise, no app crashes.
jesuita said:
I think you have to get a new recovery (twrp) in order to install xposed and then install the rom again.
Correct me if I'm wrong.
Click to expand...
Click to collapse
Flashing the ROM again will only wipe/remove xposed.
It's a known fact that lg weather doesnt work on xposed lollipop i also found that file manager didnt work during my period of testing, i don't know if i experienced com.android.phone force closing since I restored from my backup but xposed is definitely not usable on stock lollipop.
Newest xposed version v68 works great! No phone FCs. Now go download it!!!
Where can I download the newest version at because all of them up to this point are not stable on my lg 90 415d , I tried v71 and everytime I try to open my gmail Google Play services force closes
Sent from my LG-D415 using XDA Premium 4 mobile app
jbonilla51 said:
Newest xposed version v68 works great! No phone FCs. Now go download it!!!
Click to expand...
Click to collapse
Weather app, File manager app works on Lollipop D415 no problem or still buggy with some apps but fixed some others?
krchi said:
Weather app, File manager app works on Lollipop D415 no problem or still buggy with some apps but fixed some others?
Click to expand...
Click to collapse
There are newer versions of xposed that fix compatibility issues with LG's encrypted apps (weather, etc) since my post, so they should work with the newer versions of xposed. I only recommended version v68 because I never really use LG apps so I went ahead with such an update. Hope this helps!
Xposed for visually impaired users
Hi, everyone!
I'm visually impaired and I've been "adapting" and customizing my stuff (for a better, more comfortable usability) since 1998 (for Win and Mac) and 2010 for mobile devices, with great success.
I could install the Xposed framework to my Galaxy Tab 3 running KK 4.4.2 (Serbian Stock) back in 2012. But I cannot find a way to install it to my LG L90 D410 running Lollipop 5.0.2.
The option for those specific brands and models in based on the need for good cost-benefit ratio pieces of equipment, so that anyone can benefit from my findings, even those running on a low budget.
I'm preparing a podcast and an YouTube channel on accessibility.
All that put, I'd appreciate any input on how to make the Xposed framework to work on the LG L90. Suggestions o modules that can be useful for vision impaired people will be very welcome too.
Thanks in advance for any help I can get.
I haven't been able to find a thread on this. So here goes… I'm not able to get the Blackberry Work app that my firm uses to load without detecting root on Magisk v14.0,
What i have tried so far:
- Hide the app using Magisk hide
- Hide Magisk Manager
- Restarting the phone after applying settings above
- Switching between Core/Non-core modes
I can't imagine i am the only one experiencing this issue. Would be real greatly if someone could advise if Magisk can be configured to circumvante BB Work's detection. I really need this app for work (non pun intended)
Which version of BlackBerry Work are you using? Is it newer than 2.7.1.822? Is it asking you for an unlock code?
There was a problem with Huawei devices in some versions. They already fixed it, but for unknown reason 2.7.1.822 is still the latest that works on my Zenfone 2.
Wysłane z mojego ASUS_Z00A przy użyciu Tapatalka
I'm using the latest version. I can get pass all the password/codes, the problem starts after that. The app detects the root after login and i'm bounched back to the logon screen again. If i try to login now, it'll block me and i'm asked to contact my system admin.
I'll try to use the version you mentioned below when i get to the office tomorrow and see how it goes.
Still looking for a way to run Blackberry work app on rooted android!
Has anyone found a way??
deepchakra said:
Still looking for a way to run Blackberry work app on rooted android!
Has anyone found a way??
Click to expand...
Click to collapse
I've just checked this and the current version of BB Work from Google Play doesn't work with Magisk.
The last version that works fine is 2.7.1.822
Wysłane z mojego ASUS_Z00A przy użyciu Tapatalka
If you run a ROM unrooted, will Blackberry Work still detect the unlocked bootloader and/or custom recovery?
Can i write a Magisk module to spoof the device name that blackberry work reads? My company has a policy that only allows iPhones on blackberry work.
Anyone have a solution? I'm am running stock Android pie rooted and can't get bb work to work.
stu5797 said:
Anyone have a solution? I'm am running stock Android pie rooted and can't get bb work to work.
Click to expand...
Click to collapse
Im also running Pie. I have BB Work and UEM Client working fine on my setup with Magisk 17 and manager 5.9.6 or whatever that recent one is. I think the key is you need to use Elemental x kernel as well. So assuming you already have TWRP installed then you would:
1. Boot to TWRP
2. Install Elemental X Kernal
3. Install Magisk 17
4. Install Verified Boot signer v8
5. reboot and if you havent already install Magisk Manager
6. Make sure magisk manager is "hidden" in the settings, also use Magisk Hide to hide all the BB apps as well as one called something like "android.auto_generated.rro_..." I also run it in Core Only mode.
7. Reboot, delete any BB apps you might have already installed and then redownload and resetup. Just make sure everything is Hidden in Magisk Hide before launching it the first time. I can assure you that BB apps can be gotten to work with Magisk and Anrdoid 9.
---------- Post added at 08:47 AM ---------- Previous post was at 08:46 AM ----------
napes22 said:
If you run a ROM unrooted, will Blackberry Work still detect the unlocked bootloader and/or custom recovery?
Click to expand...
Click to collapse
No it wont.
Thanks so much. I noticed if you install blackberry work and it detects anything, the code deactivates so you can not use the app. It must be a prefect install or it won't work
stu5797 said:
Thanks so much. I noticed if you install blackberry work and it detects anything the code deactivates so you can use the app. It must be a prefect install or it won't work
Click to expand...
Click to collapse
Make sure you hide Magisk Manager and that you use Magisk hide to hide Magisk from both Blackberry Work and Blackberry Work profile.
If you take those 2 steps it'll work.
napes22 said:
Make sure you hide Magisk Manager and that you use Magisk hide to hide Magisk from both Blackberry Work and Blackberry Work profile.
If you take those 2 steps it'll work.
Click to expand...
Click to collapse
This works perfectly. Excellent. :good:
What is "Blackberry Work profile"? I don't see that in the list of apps...
Is anyone still using latest app with magisk?
someuser08 said:
Is anyone still using latest app with magisk?
Click to expand...
Click to collapse
2.16.0.1156 BB Work (disabled auto update) on LineageOS 15.1 (Oreo 8.1.0). Magisk 18.1 with Manager 7.0.0. It's still working albeit the phone must be rebooted from time to time because Magisk disappears. This has been an issue for me on the past few versions of Magisk installed systemless.
I can't seem to get it to work for the last half of year (it was OK before). Its almost like work app detecting something else rather than root...
someuser08 said:
I can't seem to get it to work for the last half of year (it was OK before). Its almost like work app detecting something else rather than root...
Click to expand...
Click to collapse
https://forum.xda-developers.com/apps/magisk/blackberry-app-magisk-t3742178/page2
I removed magisk completely and it still doesn't work for me - I now think its detection of custom ROMs or unlocked bootloaders that kick in...
someuser08 said:
I removed magisk completely and it still doesn't work for me - I now think its detection of custom ROMs or unlocked bootloaders that kick in...
Click to expand...
Click to collapse
I have auto update turned off on my BB apps now. Currently running 2.16.0.1156 still. With Magisk 19.0 and Manager 7.1.1, all BB apps are working on LineageOS 15.1 (Oreo 8.1). If you use the "Basic" configuration guide for Magisk on these versions, you should be in business.
Settings like debugging and dev options could be some off the culprits preventing proper detection circumvention.
I found an old phone, formatted internal storage and got LOS 15.1 on it. BB is the only app installed(no magisk). After retrieving policies from the server it self wipes due incompatible security policy. I can only assume it detects custom ROM (tried the same with AEX). Is there a module in magisk that makes your phone look like official factory state?
Hello Fellas,
I have some issues and hope you guys can help me out.
I have a Samsung Note 8 (SM-N950F), I have Rooted it today (Using Exynos menthos) and it went flawless without any Errors. After Rooting my Phone I have Flashed Xposed (by PurifyOS) but it seems not working well and I am not sure if it is the Root the Problem or Xposed.
The Problems are :
1. In Xposed the Modules I have Downloaded seems not working/not getting Activated. I have downloaded AdBlock and Youtube Background, checked both of them and restarted my Phone so the Modules get Activated. Well Youtube Background dosent work & Adblock says "The Module hasnt been Activated" but in Xposed it shows me it is Acivated.
2. I have Downloaded 2 Apps which needs Root Access (Freedom & XModGames) and everytime I launch them it Crash my hole Phone and restart my Phone.
The Root & Flashing Xposed went without any Errors.
Any reason you haven't used the official? Try it, may fix your issue
Also what root are you using?
Sent from my SM-G935F/FD/W8/S/K/L using Tapatalk
Mr.R™ said:
Any reason you haven't used the official? Try it, may fix your issue
Also what root are you using?
Sent from my SM-G935F/FD/W8/S/K/L using Tapatalk
Click to expand...
Click to collapse
Before I Flashed Xposed (by PurifyOS) , I have Flashed a another Xposed (not sure if it was the official one) but it Failed install. /Reason : Required ARM64 Type, Xposed Type : ARM/
I Rooted my Phone using this Tutorial : https://forum.xda-developers.com/galaxy-note-8/how-to/guide-how-to-root-note8-efs-backup-t3677038 (Root with SuperSU)
So I have a new Error,
"SU Binarz Occupied"
Help pls ;c
I'm running into a rather annoying problem when trying to install the Stereo Sound Mod for my One Plus 5t. Stock ROM and kernel. When attempting to flash the zip via magisk, it tells me that 'Magisk is not activated' and then proceeds to abort/fail the process. Ran into the same results when trying to flash via twrp. In fact, I've ran into this error a number of times - like when trying to install xposed via magisk manager. I'm not sure what the problem is since magisk is clearly installed and I'm properly rooted. I checked the data partition and the magisk.img file is there. Any ideas? I've attached the log from MM and the logcat filtered with 'magisk' as search parameters
nightraving said:
I'm running into a rather annoying problem when trying to install the Stereo Sound Mod for my One Plus 5t. Stock ROM and kernel. When attempting to flash the zip via magisk, it tells me that 'Magisk is not activated' and then proceeds to abort/fail the process. Ran into the same results when trying to flash via twrp. In fact, I've ran into this error a number of times - like when trying to install xposed via magisk manager. I'm not sure what the problem is since magisk is clearly installed and I'm properly rooted. I checked the data partition and the magisk.img file is there. Any ideas? I've attached the log from MM and the logcat filtered with 'magisk' as search parameters
Click to expand...
Click to collapse
Did you try rebooting?
Sent from my LG-LS997 using Tapatalk
Yep, rebooted several times and it's still not working. I don't seem to have a problem when installing modules that are already listed in the repo though. It just doesn't like me installing modules that I've downloaded separately
nightraving said:
Yep, rebooted several times and it's still not working. I don't seem to have a problem when installing modules that are already listed in the repo though. It just doesn't like me installing modules that I've downloaded separately
Click to expand...
Click to collapse
They may not be updated to support the new Magisk. You may have to wait till they are updated.
Sent from my LG-LS997 using Tapatalk
rootlinux said:
They may not be updated to support the new Magisk. You may have to wait till they are updated.
Sent from my LG-LS997 using Tapatalk
Click to expand...
Click to collapse
I suspect you're probably right with that one. I also had it happen with the xposed module. So presume that's not updated to support the new Magisk either?
I don't think it is yet.
Sent from my LG-LS997 using Tapatalk
I'm M having the same problem with all modules, including the ones in the repo,