hi
i have a samsung note3 N9005, stock firmware 5.0
i flashed xposed framework sdk21 , i made a wipe dalvik
but phone refuses to start, it hangs at samsung logo
what was wrong ?? how to fix it ? or there is a way to uninstall xposed ??
thanks
is there a specific xposed framework sdk21 for samsung ??? the one i used, i download it from magisk modules list
Uninstaller here (I don't know if it'll work with the systemless one, worth a try):
https://dl-xda.xposed.info/framework/uninstaller/
Try this Xposed instead:
https://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-5-0-x-t3455992
thanks a lot my friend !!!! it worked !!!
the question now is which version of xposed to flash ??? Samsung note3 N9005 Android 5.0
falciatrice10 said:
the question now is which version of xposed to flash ??? Samsung note3 N9005 Android 5.0
Click to expand...
Click to collapse
Read the thread I sent (I edited the previous post with it). It explain everything there and there's only one zip there also (attached to the thread). Also, don't forget to clean the caches after you flash it, it's important.
that one is for xposed installer not for Magiks !!! i dont want to bootloop my phone again
falciatrice10 said:
that one is for xposed installer not for Magiks !!! i dont want to bootloop my phone again
Click to expand...
Click to collapse
Dude... The zip is attached there, and as you said the magisk one DON'Twork for you... So, there's nothing to do, try the one I sent, the zip is attached there so is the uninstaller, which means that if something goes wrong like a loop, just flash it and gone. Let's finish this useless conversation, solution is already there lol.
The only difference btw the magisk one and the normal one is that the magisk one is systemless.
we are here to help each other, tahts purpose of forums.
I was using xposed with normal root (superSu) and now I want to install magisk and systemless xposed, because my bank app refuse to starts (it detects root).
I tried these files
xposed-v87.1-samsung-5.0.x-sdk21-by-dkcldark-arm.zip
Xposed_Framework_(SDK_21)-89.3_(Systemless).zip
Xposed_Framework-v89-v90b3r8.zip
and all of them give bootloop
falciatrice10 said:
We are here to help each other, thats purpose of forums.
I was using xposed with normal root (superSu) and now I want to install magisk and systemless xposed, because my bank app refuse to starts (it detects root).
I tried these files
and all of them give bootloop
Click to expand...
Click to collapse
I know, my bad if it sounded rude.
Anyways, did you even read the Xposed Systemless thread? It says there clearly that you won't be able to pass the SafetyNet either with the original or with the systemless one, which means that no matter which one you choose, your bank app will still detect it, since it break the SafetyNet. That's it.
After all, you gotta choose between using Xposed but not pass the SafetyNet, or not use Xposed and pass it.
I have two recommendations for you now:
- 1st is to not use Xposed.
- 2nd (if Xposed is really that important and you'll die if you can't have it) is to update your device, Lollipop is so old, neither that system itself or Xposed for it have support, for a long time ago...
Use a custom rom to update your device to the latest Android if possible or if Samsung didn't release any further update for you (you can search for one for your device model here). Although, even if you update, Xposed will still break the SafetyNet, but it'll at least work and not loop...
Also read this in RED (from official Xposed thread):
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
it will not work even with magisk hide ???
could you please test it in your phone https://play.google.com/store/apps/details?id=com.uib.uibmobile ???
falciatrice10 said:
it will not work even with magisk hide ???
could you please test it in your phone https://play.google.com/store/apps/details?id=com.uib.uibmobile ???
Click to expand...
Click to collapse
It won't fellow, I assure you, if you don't believe me, just see check the threads I mentioned, they say the same. This app you sent is not available in my country though.
If you really want xposed you can just Uninstaller xposed installer app and disable xposed in Magisk to use your banking app (and pass SafetyNet) then just re-enable when done
*Why not just use the banks website instead of the app, then you wouldn't have to worry about it at all.
falciatrice10 said:
it will not work even with magisk hide ???
could you please test it in your phone https://play.google.com/store/apps/details?id=com.uib.uibmobile ???
Click to expand...
Click to collapse
Sent from my SM-N920G using Tapatalk
BurnedDrake said:
If you really want xposed you can just Uninstaller xposed installer app and disable xposed in Magisk to use your banking app (and pass SafetyNet) then just re-enable when done
*Why not just use the banks website instead of the app, then you wouldn't have to worry about it at all.
Click to expand...
Click to collapse
Read from the beginning, he's unable to use Magisk one since it gives him a loop, also the original one, and he's using lollipop.
I did, but I'm understanding it as the Magisk one worked fine, he just couldn't use his banking app, so he tried to flash regular xposed (but the wrong version for his phone) and it bootlooped. So I was giving him suggestions on how to work around his problem.
Are we sure it bootlooped? Some phones take upwards of 20-30 minutes for that first boot after installing xposed
abacate123 said:
Read from the beginning, he's unable to use Magisk one since it gives him a loop, also the original one, and he's using lollipop.
Click to expand...
Click to collapse
Sent from my SM-N920G using Tapatalk
i was using regular xposed, but now i want to use the systemless one in order to use the bank app.
falciatrice10 said:
i was using regular xposed, but now i want to use the systemless one in order to use the bank app.
Click to expand...
Click to collapse
And I already told you that you won't. Better do some research about SafetyNet and how Xposed affect it. Unless you do what I've recommended to you, and the tips given above by BurnedDrake will also help you.
See:
Related
Grettings...is it possible to make a module that disable Apps/apk signature? I know this is kinda dangerous but also useful for those who want to downgrade apps without having to uninstalled it...right now the only way to downgrade an apk is using Titanium Backup (backup apps & data then restore data only) after uninstalled latest apk and reinstalled previous apk or use Xposed Module...
Sent from my A0001 using Tapatalk
iPusak Gaoq™ said:
Grettings...is it possible to make a module that disable Apps/apk signature? I know this is kinda dangerous but also useful for those who want to downgrade apps without having to uninstalled it...right now the only way to downgrade an apk is using Titanium Backup (backup apps & data then restore data only) after uninstalled latest apk and reinstalled previous apk or use Xposed Module...
Click to expand...
Click to collapse
You can use the nano mod patcher to deactivate the app signature but this variant isn't system less
Sent from my MI 5s using XDA Labs
So no systemless options? Anyone have any suggestions other than having to uninstall and reinstall the app?
hshah said:
So no systemless options? Anyone have any suggestions other than having to uninstall and reinstall the app?
Click to expand...
Click to collapse
Use lucky Patcher and get root access.
tap on toolbox→Patch to android→tick on Disable signature verification in the package manager→tap on apply and wait to apply it will auto reboot your phone→Done.
Now you can install any older version app over the newer one without uninstalling it.
Eng.Raman said:
Use lucky Patcher and get root access.
tap on toolbox→Patch to android→tick on Disable signature verification in the package manager→tap on apply and wait to apply it will auto reboot your phone→Done.
Now you can install any older version app over the newer one without uninstalling it.
Click to expand...
Click to collapse
Lucky patcher is considered warez on xda and condoning its use, or discussing it in any way is prohibited.
The Merovingian
Senior Moderator
Does anyone know if "you know what" breaks SafetyNet?
Sent from my Samsung Galaxy Note 8 using XDA Labs
hshah said:
Does anyone know if "you know what" breaks SafetyNet?
Sent from my Samsung Galaxy Note 8 using XDA Labs
Click to expand...
Click to collapse
Lord Voldemort? I'm sure he'd trip it...
Good idea.. I'll look into it.
hshah said:
So no systemless options? Anyone have any suggestions other than having to uninstall and reinstall the app?
Click to expand...
Click to collapse
You can change the app version with APK Editor
Sent from my MI 5s using XDA Labs
Didgeridoohan said:
Lord Voldemort? I'm sure he'd trip it...
Click to expand...
Click to collapse
Its sure ahahah :fingers-crossed:
Can someone who wants to disable app signatures upload a deodexed services.jar.. I need you to help me test my new patcher.
Been a productive afternoon:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
fOmey said:
Can someone who wants to disable app signatures upload a deodexed services.jar.. I need you to help me test my new patcher.
Been a productive afternoon:
Click to expand...
Click to collapse
My Zenfone 2 Z00A deodexed services.jar
Eng.Raman said:
My Zenfone 2 Z00A deodexed services.jar
Click to expand...
Click to collapse
Perfect, would you like to test this module.. let me know how you go.
NOTE: Other users do not use this module, this was generated specifically for his device/rom !
XDA is lagging.. excuse the double post.
fOmey said:
Perfect, would you like to test this module.. let me know how you go.
NOTE: Other users do not use this module, this was generated specifically for his device/rom !
Click to expand...
Click to collapse
I'm installed SmaliPatcher.zip and it caused a bootloop .
Rom: Stock android 6.0.1
Magisk stable 14.0 / magisk manager 5.3.0 installed .
Eng.Raman said:
I'm installed SmaliPatcher.zip and it caused a bootloop .
Rom: Stock android 6.0.1
Magisk stable 14.0 / magisk manager 5.3.0 installed .
Click to expand...
Click to collapse
My mistake, I zipped the module wrong.. sorry about that !
Try this one:
fOmey said:
My mistake, I zipped the module wrong.. sorry about that !
Try this one:
Click to expand...
Click to collapse
It works now. :good:
Thanks bro you are the man. :fingers-crossed:
Eng.Raman said:
It works now. :good:
Thanks bro you are the man. :fingers-crossed:
Click to expand...
Click to collapse
Sweet.. Ah also I noticed your using my mock locations patcher... if you have patched the service.jar you uploaded with the mock locations patcher you no longer need that module as the smalipatcher.zip will contain it. You should remove/disable the mock locations module.. hopefully that sentence made sense.
fOmey said:
Sweet.. Ah also I noticed your using my mock locations patcher... if you have patched the service.jar you uploaded with the mock locations patcher you no longer need that module as the smalipatcher.zip will contain it. You should remove/disable the mock locations module.. hopefully that sentence made sense.
Click to expand...
Click to collapse
Yes, I use mock location patcher will remove it as soon as my SmaliPatcher contain all three patches.
Thanks again bro for your time and patching tools. :good:
So in what shall not be named, you have the option of patching only the Dalvik Cache version to remove the signature verification. I tried that and it works AND it doesn't break SafetyNet. Yay!
Sent from my Samsung Galaxy Note 8 using XDA Labs
I first want to start off by apologizing if this is posted in the wrong section/area.
My goal is to basically allow playing Pokemon Go, and using Android Pay on my LG G3 with root abilities.
I've gone ahead and installed Magisk, which was a bit of a process. My LG G3 is a Sprint LS990.
The process went like this:
Factory clean Flash using LG tool -> Rooted phone using Stump Root -> Installed latest TWRP (3.2.1-0) using Flashify -> then proceeded with root stock rom flash ( I did not flash modem in link )-> Installed Magisk using TWRP recovery.
It was a bit of a hassle, but it was installed. But now as title states, I'm unable to pass SafteyNet even with troubleshooting that is found around searching Google.
Info:
Android: 5.0.1
Kernel version: 3.4.0
Magisk v15.3
Any ideas on what I could be doing wrong?
CP87 said:
Kernel version: 3.4.0
Click to expand...
Click to collapse
Take a look at the requirements for MagiskHide to function: https://forum.xda-developers.com/showpost.php?p=73145989&postcount=5
This is a huge bummer. Didn't even realize that. Looks like I'll need to go looking for a replacement phone after all.
CP87 said:
I first want to start off by apologizing if this is posted in the wrong section/area.
My goal is to basically allow playing Pokemon Go, and using Android Pay on my LG G3 with root abilities.
I've gone ahead and installed Magisk, which was a bit of a process. My LG G3 is a Sprint LS990.
The process went like this:
Factory clean Flash using LG tool -> Rooted phone using Stump Root -> Installed latest TWRP (3.2.1-0) using Flashify -> then proceeded with root stock rom flash ( I did not flash modem in link )-> Installed Magisk using TWRP recovery.
It was a bit of a hassle, but it was installed. But now as title states, I'm unable to pass SafteyNet even with troubleshooting that is found around searching Google.
Info:
Android: 5.0.1
Kernel version: 3.4.0
Magisk v15.3
Any ideas on what I could be doing wrong?
Click to expand...
Click to collapse
Do you checked your Google play. Do you have certificate and why you don't added screen when you can pass safety net
chudy_85 said:
Do you checked your Google play. Do you have certificate and why you don't added screen when you can pass safety net
Click to expand...
Click to collapse
Google Play is checked off. I'm not too sure what you mean by certificate. But I figured a screen shot wasn't worth it as my kernel version isn't supported.
Requirements:
A Linux kernel version of at least 3.8
Click to expand...
Click to collapse
Since mine is only 3.4.0, there is pretty much nothing I can do with this phone in terms of having it rooted with those apps.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
CP87 said:
Google Play is checked off. I'm not too sure what you mean by certificate. But I figured a screen shot wasn't worth it as my kernel version isn't supported.
Since mine is only 3.4.0, there is pretty much nothing I can do with this phone in terms of having it rooted with those apps.
Click to expand...
Click to collapse
Why not flash a rom? Lineage will pass. Phone is not useless, just stock is.
https://download.lineageos.org/ls990
madbat99 said:
Why not flash a rom? Lineage will pass. Phone is not useless, just stock is.
https://download.lineageos.org/ls990
Click to expand...
Click to collapse
I'm still somewhat new to the whole "flashing" / "rooting" devices. It's been a fun learning curve so far.
So flash Lineage using TWRP? Is there a guide I should be looking out for? Would be awesome if I could use my apps with this.
Maybe install safetynet fix module?
madbat99 said:
Why not flash a rom? Lineage will pass. Phone is not useless, just stock is.
https://download.lineageos.org/ls990
Click to expand...
Click to collapse
If they've updated the kernel, yes it might pass. But it's far from certain that they have...
BajinganTengik said:
Maybe install safetynet fix module?
Click to expand...
Click to collapse
It won't make any difference if the kernel doesn't support mount namespace.
CP87 said:
I'm still somewhat new to the whole "flashing" / "rooting" devices. It's been a fun learning curve so far.
So flash Lineage using TWRP? Is there a guide I should be looking out for? Would be awesome if I could use my apps with this.
Click to expand...
Click to collapse
Yep, wipe system,data, cache, dalvik/art. Flash rom, gapps and magisk. Backup everything you want to keep. Better check in your device's forum for specific instructions. It passes on my Sprint see who's last official update was KitKat, but has official lineage 14.1
madbat99 said:
Yep, wipe system,data, cache, dalvik/art. Flash rom, gapps and magisk. Backup everything you want to keep. Better check in your device's forum for specific instructions. It passes on my Sprint see who's last official update was KitKat, but has official lineage 14.1
Click to expand...
Click to collapse
Do you have the LG G3 from Sprint as well?
I'll remove magisk and try flashing the LineageOS. Anything special I should know afterwards? My current version on LG G3 is 5.0.1 // Lollipop. So should I factory reset and go back to KitKat?
CP87 said:
Do you have the LG G3 from Sprint as well?
I'll remove magisk and try flashing the LineageOS. Anything special I should know afterwards? My current version on LG G3 is 5.0.1 // Lollipop. So should I factory reset and go back to KitKat?
Click to expand...
Click to collapse
No you don't need to go to KitKat. Lineage is nougat. The usual procedure is, Download the rom zip for your device, download gapps for 7.1 and magisk. Then boot to recovery, full wipe and factory reset, then flash rom, gapps and magisk.
Check here
And this post says magisk works fine and passes safetynet.
Have fun
I will give this a try and report back on results.
Thanks so much for the help so far!
Just giving a quick update that SafteyNet is now passing, and Android Pay along with other apps are working like a charm w/root.
Thanks again!
Sorry for creating a thread about this, but I'm not sure if it goes under the bug reporting thread! If it's in the wrong place please let me know!
I've tried every solution that I've been able to find, none have worked! I've attached screenshots of the problems.
I haven't tried reflashing my phone with a stock ROM just because it'll be a lot more work than it's worth imo.
I've tried uninstalling Magisk, running the unSU zip to remove all trace files, but other people with the same error say it has to do with their internet somehow blocking the safetynet files?
If someone would please let me know why it's happening I'd really appreciate it!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'm getting this as well but banking apps haven't kicked me out yet
It's google. Their servers are wonky. It even fails when going back to stock completely. Save yourself the trouble and just ignore. As long as google play store still says certified, wouldn't worry about it. Dealt with this issue quite awhile and this is the conclusion.
Ignore or otherwise you be pulling your hair out with pass fail pass fail fail, or the reponse is invalid. So just ignore and happy rooting
Gold_Diesel said:
I'm getting this as well but banking apps haven't kicked me out yet
Click to expand...
Click to collapse
It's weird because when Pokemon Go came out with the SafetyNet **** it was bypassed just fine, but when I tried to get fortnite working it said this, and when I checked again it started saying I failed
Yeah, this happens pretty often lately.
I usually enable core only mode in the Magisk Manager settings, reboot, test safetynet, disable core only mode, and then reboot again.
Fixes it for a while (in my experience).
https://twitter.com/topjohnwu/status/1029239685338419200
Here's why SafetyNet isn't working: because all apps on Play Store, including Magisk Manager, uses the old API, which is recently blocked!
Click to expand...
Click to collapse
Didgeridoohan said:
https://twitter.com/topjohnwu/status/1029239685338419200
Click to expand...
Click to collapse
Oh thank you so much!
Didgeridoohan said:
https://twitter.com/topjohnwu/status/1029239685338419200
Click to expand...
Click to collapse
So I won't be able to tell what's causing safetynet to fail? :/
Mew351 said:
So I won't be able to tell what's causing safetynet to fail? :/
Click to expand...
Click to collapse
Bruh....it's not actually failing. Any app that requires the safety net check will still work. This just means Magisk uses an old API that is no longer in use so it can no longer check safetynet properly until its updated. If you passed safety net before you'll be passing it now.
Put this in play store and install beta
pname:"org.freeandroidtools.root_checker"
DroidJP said:
It's google. Their servers are wonky. It even fails when going back to stock completely. Save yourself the trouble and just ignore. As long as google play store still says certified, wouldn't worry about it. Dealt with this issue quite awhile and this is the conclusion.
Click to expand...
Click to collapse
This. Good way to check. My Google Pay still works.
mkdante381 said:
Put this in play store and install beta
pname:"org.freeandroidtools.root_checker"
Click to expand...
Click to collapse
Thanks
it passes safety-net test
Mew said:
It's weird because when Pokemon Go came out with the SafetyNet **** it was bypassed just fine, but when I tried to get fortnite working it said this, and when I checked again it started saying I failed
Click to expand...
Click to collapse
Same situation for me, i have a xiaomi black shark new and can´t play fortnite, not rooted, it´s stock.
I try the root checker beta and get a cts profile: false, i don't understand why.
PS: i can play pokemon go and don't have magisk installed.
alceca said:
Same situation for me, i have a xiaomi black shark new and can´t play fortnite, not rooted, it´s stock.
I try the root checker beta and get a cts profile: false, i don't understand why.
PD: i can play pokemon go and don't have magisk installed.
Click to expand...
Click to collapse
CTS Profile reporting false means your device isn't certified by Google (China ROM?), you have an unlocked bootloader or you are using a custom ROM that isn't spoofing a certified device.
Didgeridoohan said:
CTS Profile reporting false means your device isn't certified by Google (China ROM?), you have an unlocked bootloader or you are using a custom ROM that isn't spoofing a certified device.
Click to expand...
Click to collapse
It's a xiaomi black shark, it comes with joy-ui (it's similar to miui), it has a China-english ROM no global ROM has been release yet.
In the fornite compatible devices list the xiaomi black shark appear.
A friend with the same phone is in the same situation, is weird that the phone is in the list but get an error.
alceca said:
It's a xiaomi black shark, it comes with joy-ui (it's similar to miui), it has a China-english ROM no global ROM has been release yet.
In the fornite compatible devices list the xiaomi black shark appear.
A friend with the same phone is in the same situation, is weird that the phone is in the list but get an error.
Click to expand...
Click to collapse
Check This Thread https://forum.xda-developers.com/apps/magisk/qa-want-to-install-modules-magisk-v13-3-t3800435.
Dreamer(3MF) said:
Check This Thread https://forum.xda-developers.com/apps/magisk/qa-want-to-install-modules-magisk-v13-3-t3800435.
Click to expand...
Click to collapse
do i need to install magisk or root the phone? i want to stay stock, there is no ROM to flash or unbrick yet.
alceca said:
do i need to install magisk or root the phone? i want to stay stock, there is no ROM to flash or unbrick yet.
Click to expand...
Click to collapse
Yes, You Need To Install Magisk To Use The Modules.
mkdante381 said:
Put this in play store and install beta
pname:"org.freeandroidtools.root_checker"
Click to expand...
Click to collapse
I have Magisk v.16.7 installed on both a Galaxy S5 (Marshmallow) and Galaxy Tab S3 (Oreo) and have been getting "The response is invalid" message for awhile on both devices when running the check on Magisk Manager. I have installed various of the SafetyNet checking apps from the Play Store and SafetyNet test fails on many, but does pass on a couple. I have found the the app SafetyNet Check has been reliable as it shows CTS Profile match and Basic Integrity pass on both my devices.
Just to be sure that the Galaxy S5 would work with Google Pay, I had installed the GooglePayHider4Magisk but don't think it was necessary.
I have a completely stock device. Not rooted or custom recovery. I downloaded the app mentioned on the previous page and I still get safetynet failed. Clearly Google screwed something up.
I have a unlocked, rooted Xiaomi Redmi Note 4 running 7.2.1 (Viper mido version)
Got the Magisk v17.1 update this morning. I needed to remove Magisk 16.x via the uninstaller, and install the new update from TWRP Recovery. (a pain, but it seems to work. regular upgrading has a few issues)
Then I installed my preferred Magisk modules. All seem to work as they should except the Xpose Framework v89-v90b3r11 module. When installed it kills Magisk Hide and SafetyNet fails, when I uninstall it, SafetyNet succeeds again (Magisk Hide is usable).
For for now, until the Xpose Framework module is fixed, if you want to use Magisk Hide, probably can't install the Xpose module.
Cheers,
AB
You won't be able to pass SafetyNet if you have Xposed installed on your device. This has been the same since the start and not a Magisk v17.1 thing.
Sent from my #FlagshipKiller3T using Tapatalk
Read the threads
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
DarkSJ1998 said:
You won't be able to pass SafetyNet if you have Xposed installed on your device. This has been the same since the start and not a Magisk v17.1 thing.
Sent from my #FlagshipKiller3T using Tapatalk
Click to expand...
Click to collapse
Funny that, I had it working before. Possibly blind luck. I had Magisk installed and the Xpose Framework, and SafetyNet/Magic Hide was usable.
I just was using only one of Xpose's Module. So I don't need Xpose at all.
airbrushwerx said:
Funny that, I had it working before. Possibly blind luck. I had Magisk installed and the Xpose Framework, and SafetyNet/Magic Hide was usable.
I just was using Xpose's LuckyPatcher Module.
Click to expand...
Click to collapse
Maybe when you were using it, that particular app wasn't able to detect Xposed framework & only checked for root, which was tricked by Magisk Hide. And now the developer might have improved the checks or what not.
Sent from my #FlagshipKiller3T using Tapatalk
Bro, I need to hide magisk from a banking app, Now what can i do?
v 17.1
thanks everyone, It's working :victory:
BengaliBhai said:
Bro, I need to hide magisk from a banking app, Now what can i do?
v 17.1 here is nothing. how can i hide
Click to expand...
Click to collapse
buy other phone for banking
BengaliBhai said:
Bro, I need to hide magisk from a banking app, Now what can i do?
v 17.1 here is nothing. how can i hide
Click to expand...
Click to collapse
Does your banking work without Xposed Installer app installed? My internet banking app detects root if Xposed Installer manager is installed. So what I do is installing or updating the Xposed modules, rebooting, and then uninstalling Xposed manager, and all modules will still work, as they only require that Xposed systemless files (v89.3) are installed.
DarkSJ1998 said:
Maybe when you were using it, that particular app wasn't able to detect Xposed framework & only checked for root, which was tricked by Magisk Hide. And now the developer might have improved the checks or what not.
Sent from my #FlagshipKiller3T using Tapatalk
Click to expand...
Click to collapse
Yes, it looks like it might have been the way I installed the apk after Magisk, but before Xpose-framework. I inadvertently used some 'loophole' that allowed it not detect root, but still have Xpose installed.
Cheers,
AB
BengaliBhai said:
Bro, I need to hide magisk from a banking app, Now what can i do?
v 17.1 here is nothing. how can i hide
Click to expand...
Click to collapse
BengaliBhai,
You probably need to reinstall Magisk.
1) Download the Magisk-uninstaller.
2) Boot to TWRPS (reovery)
3) run the uninstaller. (which should bring back your original boot partition)
4) then install Majisk v17.1
5) reboot into system.
Now Majisk Manager should be fully functional.
I ran into this, v17.0 installed, but MM 5.9..0 wasn't working correctly, not showing modules, not allowing access, etc... Then I got the v17.1/5.9.1 update and still did the same. No boot-looping, but 'root limbo'. The above process resolved it all.
Cheers,
AB
Try xposed module rootcloak works great with my bank app oreo
david6910 said:
Try xposed module rootcloak works great with my bank app oreo
Click to expand...
Click to collapse
Lucky patcher isn't banned from xda? ?
If Your Device Didn't Pass The SafetyNet, Try DeviceSpoofingTool4Magisk From This Thread https://forum.xda-developers.com/apps/magisk/qa-want-to-install-modules-magisk-v13-3-t3800435.
youtuber123 said:
Lucky patcher isn't banned from xda? ?
Click to expand...
Click to collapse
Im not talking about lucky patcher... I talking about a xposed module lol
airbrushwerx said:
Yes, it looks like it might have been the way I installed the apk after Magisk, but before Xpose-framework. I inadvertently used some 'loophole' that allowed it not detect root, but still have Xpose installed. I also use LuckyPatcher to mod/patch apks. I'll concede that it might have been a combination of them that allowed that it to work until i needed to reinstall Magisk. No foul, no harm.
Cheers,
AB
Click to expand...
Click to collapse
Do not discuss warez here. That is designed to steal from developers. This is a site for developers. You will be banned for discussing it here.
Tr4sHCr4fT said:
buy other phone for banking
Click to expand...
Click to collapse
Bro use RootCloak Xposed Module to hide Banking app from root and make it usable....
Hey so I realized that Magisk won't open after update v22 if im not mistaken. It just opens, asks to do a "full installation", when I press ok it does some stuff in the background and closes asking to restart the app over and over. I'm confused why this happens as Magisk has worked previously.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I have a samsung galaxy note 4 (snapdragon) with a custom rom running on android 10.
goto magisk github and download magisk v22 apk manually then install it usually when that error box show it open google chrome but on your case it didn't ...
oh upon reinstalling it, it seems like the app "works" now for the most part but I have a new issue. I have lost root access and can't manage to get it working back. I flashed the apk in my recovery as the instruction said, according to twrp logs everything installed properly (didnt exit with any error codes) and after I rebooted my phone Magisks detected the installed state as N/A.
Any idea why?
N1PE said:
oh upon reinstalling it, it seems like the app "works" now for the most part but I have a new issue. I have lost root access and can't manage to get it working back. I flashed the apk in my recovery as the instruction said, according to twrp logs everything installed properly (didnt exit with any error codes) and after I rebooted my phone Magisks detected the installed state as N/A.
Any idea why?
Click to expand...
Click to collapse
so previously you have magisk fully working but decided to update Magisk to v22 then now it just show N/A on Installed?
ineedroot69 said:
so previously you have magisk fully working but decided to update magisk to v22 then now it just show N/A on Installed?
Click to expand...
Click to collapse
yeah pretty much, didn't notice there was an issue after installing at first since I only occasionally use root for few miscleanous stuff
N1PE said:
yeah pretty much, didn't notice there was an issue after installing at first since I only occasionally use root for few miscleanous stuff
Click to expand...
Click to collapse
since its say N/A you need to reinstall it like from the beginning
what do you mean, I already uninstalled the app and tried reflashing it like 5 times
N1PE said:
what do you mean, I already uninstalled the app and tried reflashing it like 5 times
Click to expand...
Click to collapse
https://i.pinimg.com/236x/77/19/e2/7719e28b56018268fff940a8c1f49afc.jpg
how did this happen anyway? so you are running magisk then installed update 22.0 did you follow the changelog? it say you need to disable Magisk Hide before upgrading to v22.0
oh I think I might not have disabled it, either ways when I updated to v22 I just casually installed it like any other updates so far...
N1PE said:
oh I think I might not have disabled it, either ways when I updated to v22 I just casually installed it like any other updates so far...
Click to expand...
Click to collapse
you're still lucky since your device is still in working conditions there are user who completely bricked there device and force to buy new one since they can't fix the bootloop cause by Magisk 22.0 for not reading the changelog ...
ohhhh wait I fixed it, there were 2 Magisk manager apps somehow so after uninstalling the older one, everything works normally now
N1PE said:
ohhhh wait I fixed it, there were 2 Magisk manager apps somehow so after uninstalling the older one, everything works normally now
Click to expand...
Click to collapse
https://i.pinimg.com/750x/55/d8/3c/55d83c65008c4b856758fffc64efe39e.jpg
thank you so much for your time, I have one last question though: how do I close a thread/mark as solved/ or archive it.
I'm new to XDA so don't really know
N1PE said:
thank you so much for your time, I have one last question though: how do I close a thread/mark as solved/ or archive it.
I'm new to XDA so don't really know
Click to expand...
Click to collapse
you can't
ineedroot69 said:
you're still lucky since your device is still in working conditions there are user who completely bricked there device and force to buy new one since they can't fix the bootloop cause by Magisk 22.0 for not reading the changelog ...
Click to expand...
Click to collapse
Solving the same issue as OP right now. Can't see about disabling magisk hide in the changelog, am I at the right page? https://topjohnwu.github.io/Magisk/changes.html
EDIT: nevermind, found it: https://topjohnwu.github.io/Magisk/releases/22000.html
Anyway is there a way how to disable Magisk Hide without Magisk Manager?
Hello I have the same problem. I Updated magisk to 23.0 without disabling the hide magisk. Root seems to be lost , NA indicated in magisk. Magisk manager no more available. I can't see any magisk manager installed anywere. I did you succeed to remove one magisk manager ? Using which tool ? I use a redmi note 9 pro
A bit of a necro, so I won't tag the OP, but when something is resolved, you can either Edit the OP, or choose the three-dots in the upper-right corner of the OP, and choose Edit, and then add the tag:
[SOLVED]
in front of the current thread title.
The poster can additionally Report the OP and ask that the thread be closed, if necessary.
Cheers!