Hello, just looking for some clarification if possible before I destroy my device!
So I currently have a T-Mobile Galaxy Note 3 (SM-N900T) that has been towel rooted on kitkat 4.4.2 and then flashfire'd to the latest stock Lollipop 5.0 firmware available for my device to keep root.
I have also FlashFire'd the latest unofficial xposed framework for samsung lollipop 5.0.x by dkcldark and I do not have TRWP, or any custom recovery.
As far as I understand xposed is not compatible, or at least probably not the one im using. I'm willing to sacrifice it and go with Magisk for its ability to hide root from apps if at all possible.
I believe the root I have is not systemless. I also believe the t-mobile note 3 has an unlocked bootloader. Though I'm not 100% positive.
Edit: Final note, within Magisk Manager ... it says I am "Properly Rooted, with 2.82:SUPERSU"
So now on to the questions:
1. If I uninstall my current xposed framework and download Magisk Manager, can I successfully install Magisk and accomplish "hiding root/by passing safetynet" from apps on my device that is currently rooted probably via system without a custom recovery?
2. Will Knox also stay un-tripped at 0x0? Or since the boot.img will be modified, this would be tripped? Even though I did not use a custom recovery, or kernal at all?
Appreciate the replies XDA! Thanks.
I just replaced SuperSU with Magisk in my Galaxy S4. So, to answer your questions.
You'd have to replace SuperSU with MagiskSU in order to enable the hide feature. I don't think Towelroot is usable with Magisk, and since there is no CF-Autoroot for Magisk you'd have to install a custom recovery, which will - if I'm not mistaken - trip Knox. At this point in your Note 3's lifespan, the last thing I would be worrying about is Knox, as your warranty on the device is no longer extant.
So using the Magisk Manager app to install Magisk while on my rooted device without a custom recovery will not work and itself replace SuperSU with MagiskSU while keeping knox 0x0?
I was under the impression if you were pre-rooted u could use Magisk Manager, and it would replace the current root with Magisks. And also that it detects if you have a systemless root or not. Installing itself into the system if that's the type of root you had, otherwise systemlessly.
While yeah my device is no longer under warranty, It's just my own personal preference to preserve it.
custom recovery will trip knox... Magisk needs a custom recovery to install the framework as mentioned
i do understand your preference about maintain knox untripped...
do you really use it? (knox app... It was discontinued .... Samsung official press release ... and I did received a email about it)
or intend further sell your device as "original" at eBay? it's a joke...
imho ... knox at this point is a good security sandbox.... but there is alternative ways to secure your apps and personal/professional data...
If install a custom rom nougat flavour and Magisk performance device will increase It... lookup at note 3 devs thread
best regards
Enviado de meu Lenovo A7010a48 usando Tapatalk
Alrighty thanks for the info!
I do not currently use it, but I also don't use Samsung Pay ... and don't really *need* to play Pokemon go, or Super Mario Run... I'll keep my phone rooted, xposed framework, latest firmware, knox 0x0 for now and possibly consider tripping the knox flag at a later time. Assuming no new "root hide" work-around becomes available and based on future safetynet blocked apps.
The SM-N900T is still a very great device... Additional SD Card slot, removable battery, 3 gigs of ram, 32 gigs space, 2.3GHz Quad-Core CPU, 1080p 5.7" Full HD Super AMOLED® screen.
I see no reason yet to upgrade the phone even being about 4 years old now.
I do remember something like a "safe" custom recovery was for the note 3 line, I have used it on my note 3 from Verizon when I had it.
Just see if you can use it, and flash Magisk with it, unless it is obsolete as it may be was replaced by flashfire?
Sent from my Nexus 6P using XDA Labs
Strephon Alkhalikoi said:
I just replaced SuperSU with Magisk in my Galaxy S4. So, to answer your questions.
You'd have to replace SuperSU with MagiskSU in order to enable the hide feature. I don't think Towelroot is usable with Magisk, and since there is no CF-Autoroot for Magisk you'd have to install a custom recovery, which will - if I'm not mistaken - trip Knox. At this point in your Note 3's lifespan, the last thing I would be worrying about is Knox, as your warranty on the device is no longer extant.
Click to expand...
Click to collapse
Which Custom Rom do you use? I currently cant find a good one to root with magisk (also S4)
Well, my S4 isn't my daily driver anymore, so I threw a stock-based ROM on it: MachineX. That ROM however uses MicroG, so I had to modify an OpenGApps package to remove the MicroG components and replace them with proper Google ones.
If you're still using your S4, use an AOSP 7.1.2 ROM instead. Less hassle, and runs better.
Magisk hide hides the KNOX status. Simply replace SuperSU to MagiskSU.
Deic said:
Magisk hide hides the KNOX status. Simply replace SuperSU to MagiskSU.
Click to expand...
Click to collapse
That it does but I've yet to see anyone successfully use S Pay/Pass after tripping Knox, with or without Magisk.
Strephon Alkhalikoi said:
and since there is no CF-Autoroot for Magisk you'd have to install a custom recovery, which will - if I'm not mistaken - trip Knox.
Click to expand...
Click to collapse
Sure, CF Autoroot does not trip Knox?
But Chainfire says so here: "If you have a KNOX-enabled device, using CF-Auto-Root will trip the KNOX WARRANTY VOID status !" :crying:
@ThemGo: You got me. I must have been drinking when I mentioned CF AutoRoot. The point I was trying to make to the original poster about Knox was that there was no way to keep it at 0x0 if installing Magisk.
But, were you that bored that you had to hunt through a five month old post?
Related
A few days ago I posted a question about not being able to install any Xposed modules here, so far no one answered: https://forum.xda-developers.com/xposed/xposed-framework-installed-running-t3567230
I thought this problem had something to do with the modules specifically, but it turns out that on my phone, for whatever reason, installing the framework subsequently prevents ALL apps from installing, even those from Google Play itself, displaying a "-504" error.
I see people have asked this question before, but are also not getting answers: https://forum.xda-developers.com/xposed/install-apps-installing-framework-t3430922
Please, if anyone has any idea of why this can be and how to fix it, let me know. Any help will be infinitely appreciated!
What phone and ROM are you using?
One thing you could try is to install systemless Xposed through Magisk. Then use MagiskHide to hide both root and Xposed from all Google apps and potential sources of conflict. If it's a software limitation/conflict, this may be a workaround.
Keep in mind that you will have to root your phone with Magisk rather than SuperSU or any other form of root.
Anova's Origin said:
What phone and ROM are you using?
One thing you could try is to install systemless Xposed through Magisk. Then use MagiskHide to hide both root and Xposed from all Google apps and potential sources of conflict. If it's a software limitation/conflict, this may be a workaround.
Keep in mind that you will have to root your phone with Magisk rather than SuperSU or any other form of root.
Click to expand...
Click to collapse
Hey, thank you for your answer!
I am using a Sony Xperia M4 Aqua E2306, rom is 26.1.A.1.112 Latin America Generic. It is rooted and with TWRP installed accroding to this thread: https://forum.xda-developers.com/m4-aqua/general/root-e2306-m4-aqua-guide-t3270521
I also have a locked bootloader, and it cannot be unlocked, so unfortunately that shuts the door on most rooting options.
I never heard of Magisk before, but from what I'm seeing, it looks it TWRP is required to get root with Magisk, but some kind of root is already required on my phone in order to get TWRP. So I'm not sure how to go about this.
If your phone is already rooted, then you can download Magisk Manager application and have it installed it's necessary frameworks through the app itself. You won't be able to use Magisk's root, but you'll still be able to install systemless Xposed and hide it from other apps.
Edit: Ignore all of that actually, I just realized that magisk requires boot image modifications so you have to have an unlocked bootloader to use it.
Anova's Origin said:
If your phone is already rooted, then you can download Magisk Manager application and have it installed it's necessary frameworks through the app itself. You won't be able to use Magisk's root, but you'll still be able to install systemless Xposed and hide it from other apps.
Edit: Ignore all of that actually, I just realized that magisk requires boot image modifications so you have to have an unlocked bootloader to use it.
Click to expand...
Click to collapse
Oh well, thanks anyway. I might try it anyways, maybe it will work, you never know. Don't have much to lose at this point
Anova's Origin said:
What phone and ROM are you using?
One thing you could try is to install systemless Xposed through Magisk. Then use MagiskHide to hide both root and Xposed from all Google apps and potential sources of conflict. If it's a software limitation/conflict, this may be a workaround.
Keep in mind that you will have to root your phone with Magisk rather than SuperSU or any other form of root.
Click to expand...
Click to collapse
FIY Magisk cannot hide Xposed...
I also facing these problem on my rooted Asus zenfone 2 (ze550ml 2gb ram version, Stock ROM, bootloader unlocked) and Asus Zenpad C 7 (p01y, stock rom, bootloader unlocked). The xposed firmware (version 86) is successfully install but can't install any apps from play store and using apk...
I really hope that dev team can solve it.....
Sorry for any grammatical mistakes....
The only way is to flash the firmware
I'm getting the same problem on my LG G4 with v88.2 of Xposed :/
I don't Know if this is too late,but I also have this problem. But there is a work around, go into the xposed installer and turn the switch off so its disabled on the next boot. rebot the device and exposed and its modules are disabled, allowing you to install apps from play store and downloaded .apk files... it would still be nice to install applications while its still on.
Sent from my LG-K550 using XDA Labs
I had this issue on my LGG3. This happens when you have Lucky Patcher enabled in your xposed modules. Disabling it (Lucky Patcher) should solve the problem.
I successfully installed magisk on my samsung s8 but now the secure folder, software updates and maybe other apps don't work as they recognise my phone being rooted. I thought the point behind magisk was to hide the phone from looking rooted?
how can i fix this issue?
thanks
You tripped KNOX by flashing custom binaries. You're boned.
is there a way to root the phone without tripping KNOX?
cpu2007 said:
is there a way to root the phone without tripping KNOX?
Click to expand...
Click to collapse
There might be, but I don't think there's any going back for you. As far as I know you can't revert a triggered KNOX...
I installed magisk because I thought knox won't be tripped but I was wrong.
Does anyone know how I can use secure folder, software updates and banking apps now that my app is rooted? they can all recognise my app is rooted and won't work
cpu2007 said:
I installed magisk because I thought knox won't be tripped but I was wrong.
Does anyone know how I can use secure folder, software updates and banking apps now that my app is rooted? they can all recognise my app is rooted and won't work
Click to expand...
Click to collapse
You can still hide Magisk from many apps with Magisk. You'll just have to activate Magisk Hide in the Manager settings. SafetyNet is added by default and any other app that detects root might be fooled if you add it to the Magisk Hide list.
I've said it before and I'm sure I'll say it again. The purpose of Magisk is NOT to hide root and pass SafetyNet (it's just a really nice feature); it's to make your system modifications systemless. You could use this to keep your devices ability to update through OTA, with a couple of extra steps. But, the main advantage for me (and it's the deal-breaker) is that I don't have to redo any of my system modifications after an update. These could be changing screen density, debloating system apps, systemising apps, changing prop values, etc. Before Magisk I could spend 30-45 minutes after an update just setting upp all the system tweaks the way I wanted it, only to realise a couples of days later I'd forgotten something. Now, with Magisk - flash the update, done!
Recommended reading if you're new to Magisk:
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
https://forum.xda-developers.com/apps/magisk/magisk-details-dummies-to-developers-t3473486
And if you're having issues:
https://forum.xda-developers.com/apps/magisk/magisk-magisk-hide-troubleshooting-tips-t3561828
I have activated Magisk Hide and selected the app (Lloyds banking app) then restarted the phone but the app can still recognize that the phone is modified.
I'll look at the other solution that are being proposed in one of the links you've sent and sew how it goes but if anyone has any advice on how to fix this, that will be great.
I have backup for my bootloader,boot,system etc - flashing that back, will it revert the knox?
Thanks
cpu2007 said:
I have backup for my bootloader,boot,system etc - flashing that back, will it revert the knox?
Click to expand...
Click to collapse
I don't do Samsung, but as I understand it: nope.
More info can probably be found in your device's forum here on XDA.
cpu2007 said:
I have activated Magisk Hide and selected the app (Lloyds banking app) then restarted the phone but the app can still recognize that the phone is modified.
I'll look at the other solution that are being proposed in one of the links you've sent and sew how it goes but if anyone has any advice on how to fix this, that will be great.
I have backup for my bootloader,boot,system etc - flashing that back, will it revert the knox?
Thanks
Click to expand...
Click to collapse
Realise this is a very late reply, but if still had no joy with Lloyd's banking app, it will store it's root detection so will still think your phone's rooted even after Magisk Hide. Need to wipe the app data or reinstall.
Has anyone gotten Samsung Pay to work with Magisk? I've got it installed as a gear plugin and safetynet passes. However, somehow Samsung Pay still detects root, even though it's hidden in magisk hide.
Same. Then this droidx program protecting pay app
Sent from my SM-N910V using XDA-Developers Legacy app
Try the universal safteynet net module
Is your Knox tripped? Samsung Pay might check that independently of the root-status of your phone.
grymkmb said:
Is your Knox tripped? Samsung Pay might check that independently of the root-status of your phone.
Click to expand...
Click to collapse
I'm on an LG
I've got the same issue with galaxy tab 3
I got warranty bit warning was showing on the boot screen, so I'm pretty sure I triggered Knox. The reason I was using magisk was to prevent this issue, but I guess Google figured out how to detect its presence. I downloaded a fresh copy of the firmware, which will cause Knox to reset but it also factory resets the tablet. I will still use magisk on my new s8+ phone. I hope magisk will work more effectively to where I can use exposed and its modules. After jellybean, magisk wasn't able to allow exposed to be used because of the way Android sets up its environment to execute apps. Hopefully soon a work around will be accomplished especially since Oreo is coming to my two devices by the end of the year, I guess if not sooner.
Same problem here; Magisk works but Samsung pay won't work
Even tried freezing magisk. Though still no go must be detecting something.
hkbladelawhk said:
Has anyone gotten Samsung Pay to work with Magisk? I've got it installed as a gear plugin and safetynet passes. However, somehow Samsung Pay still detects root, even though it's hidden in magisk hide.
Click to expand...
Click to collapse
I tried the same thing but couldn't make it work. I think it is due to the fact that the "System Status" is custom (or modified) since magisk modifies the "boot" partition, and that you probably installed a custom recovery to install magisk. That's why OTA also don't work without first flashing back the original boot and recovery images. I don't have an LG to verify that the "System Status" appears on those.
If it does, what could be tried is to install xposed and a module that fakes the system status (if you've got marshmallow or before)
sevenday4 said:
I got warranty bit warning was showing on the boot screen, so I'm pretty sure I triggered Knox. The reason I was using magisk was to prevent this issue, but I guess Google figured out how to detect its presence. I downloaded a fresh copy of the firmware, which will cause Knox to reset but it also factory resets the tablet. I will still use magisk on my new s8+ phone. I hope magisk will work more effectively to where I can use exposed and its modules. After jellybean, magisk wasn't able to allow exposed to be used because of the way Android sets up its environment to execute apps. Hopefully soon a work around will be accomplished especially since Oreo is coming to my two devices by the end of the year, I guess if not sooner.
Click to expand...
Click to collapse
Sorry, once knox is tripped there is no going back. However, installing Magisk fools the phone into thinking knox is still untriggerred (0x0). By reflashing the original firmware, what you did is restore the "boot" partition that was modified by magisk. By doing that, your phone should get back its "official status", allowing OTA. However, Knox will stay tripped. Anyway, Knox does little... and is only used by samsung softwares.
There is nothing that we can do about it because Samsung Pay checks the tripped status on kernel level so it's impossible.
Iradj said:
There is nothing that we can do about it because Samsung Pay checks the tripped status on kernel level so it's impossible.
Click to expand...
Click to collapse
Booo!
someone please made an apps that can hide or fake the Knox status.
Iradj said:
There is nothing that we can do about it because Samsung Pay checks the tripped status on kernel level so it's impossible.
Click to expand...
Click to collapse
This is possible by disabling safetynet check at boot level before compiling the kernel
Iradj said:
There is nothing that we can do about it because Samsung Pay checks the tripped status on kernel level so it's impossible.
Click to expand...
Click to collapse
Does this apply for non-Samsung phones? I understand that Knox has a tripped flag, but on a non-Samsung phone, what exactly is "tripped"? As with everyone else, I'm pretty frustrated that I still can't use Samsung pay, even on a phone that passes safety checks and has MagiskHide.
gghose said:
Does this apply for non-Samsung phones? I understand that Knox has a tripped flag, but on a non-Samsung phone, what exactly is "tripped"? As with everyone else, I'm pretty frustrated that I still can't use Samsung pay, even on a phone that passes safety checks and has MagiskHide.
Click to expand...
Click to collapse
Works for me on a Samsung phone, after hide I just had to rename all busybox exe's.
Doesn't work for me on a OnePlus 3T, OOS 4.1.7, rooted with Magisk 14.0. This stopped working after the Samsung Pay (Gear version) was updated right around August 21st. Maybe I'm just missing one or more binaries or apps that still must be hidden. I don't have any busybox apps installed, though I previously did, and I removed the busybox binaries where I knew to find them. Maybe it's detecting Magisk's su install, or some other binary I still need to remove. SafetyNet passes just fine, and I can use AndroidPay and CapitalOneWallet on the phone, but I can't use the SPay tab in the Gear app without getting the "rooted phone" message.
Magisk hide 14
Hi Yeti47: I have a samsung galaxy s8 sm-g950f. It is rooted wit renovate ice and magisk 14. What modules I have to check in magisk hide to make samsung pay working? Please answer me in [email protected]. Thank you so much. Bye.
Finally solved it. Busybox can be installed in /data/local, apart from /system/xbin or /system/bin. Samsung Pay will find it there. After I removed it, I was able to get Samsung Pay (Gear Version) working again on my OnePlus 3T.
Spot on fella, just got it working on OP5 with lineage ROM.
dcbii said:
Finally solved it. Busybox can be installed in /data/local, apart from /system/xbin or /system/bin. Samsung Pay will find it there. After I removed it, I was able to get Samsung Pay (Gear Version) working again on my OnePlus 3T.
Click to expand...
Click to collapse
Root explorer won't let me remove it from xbin. How exactly did you do it?
Sent from my iPad using Tapatalk
I just got my refurbished note 4, it has been rooted and twrp and Xposed installed along with a custom rom running 6.0.1. I need to hide root so I can use my bank app as well as google pay. which of the subject apps will be easily installable?
I am leaning toward Magisk but still not sure
cmccarter said:
I just got my refurbished note 4, it has been rooted and twrp and Xposed installed along with a custom rom running 6.0.1. I need to hide root so I can use my bank app as well as google pay. which of the subject apps will be easily installable?
I am leaning toward Magisk but still not sure
Click to expand...
Click to collapse
magisk!
Hello,
I rooted and installed a custom ROM on my Note 9 a couple of months ago and yesterday I was getting annoyed not being able to use apps like Android Pay, Samsung Pay and Banking apps, So I decided to use Odin to flash the stock ROM back and set OEM Unlock to OFF. To my Horror, I found out the hard way about what a KNOX Trip was. I have no idea how I missed all the warnings on every ROM post about tripping it and not being able to change it back. I can now use my Banking apps, Android Pay and play Fortnite however, Because of the Knox being tripped I can no longer use Samsung Health and Samsung Pay
My Question is is there a way to just install a custom kernel or ROM that tricks apps like Samsung Pay and Samsung Health into working again without installing root and having modifications hidden so I can use my Banking apps and play games??
Any Help is very much appreciated!
After a bit more searching the forums and Google I now understand that no matter what I do I can't get Samsung pay to work which is fine. However any help on the rest is still appreciated! ?
You should go read some more as you also missed the part where tou can use magisk hide. but it wont get back spay.
Just use the forum sarch feature as if you were google searching ie:
magisk shealth
magisk hide
magisk google pay
magisk android pay
magisk insert what ever query
bober10113 said:
You should go read some more as you also missed the part where tou can use magisk hide. but it wont get back spay.
Just use the forum sarch feature as if you were google searching ie:
magisk shealth
magisk hide
magisk google pay
magisk android pay
magisk insert what ever query
Click to expand...
Click to collapse
I did use Magisk Hide to hide root from apps but some apps could still detect the custom rom was installed.
VortexHD said:
I did use Magisk Hide to hide root from apps but some apps could still detect the custom rom was installed.
Click to expand...
Click to collapse
so for example you went to magisk hide menu and selected your banking app and it didnt work?
bober10113 said:
so for example you went to magisk hide menu and selected your banking app and it didnt work?
Click to expand...
Click to collapse
Yes i selected my banking app along with google pay and all its services and Samsung pay with its services and none of them worked.
This also doesn't work for pokemon go and fortnite.
VortexHD said:
Yes i selected my banking app along with google pay and all its services and Samsung pay with its services and none of them worked.
This also doesn't work for pokemon go and fortnite.
Click to expand...
Click to collapse
how about safety net status, is it passing?
bober10113 said:
how about safety net status, is it passing?
Click to expand...
Click to collapse
Yes Everytime. I'm about to flash TWRP and only install a custom kernal with no root.
VortexHD said:
Yes Everytime. I'm about to flash TWRP and only install a custom kernal with no root.
Click to expand...
Click to collapse
try endurance. but besure ure rom base matches kernel ramdisk or u won't be able to get past lock screen. so do a full twrp backup in case
or just try dr ketan. usualy best all round working rom.
bober10113 said:
try endurance. but besure ure rom base matches kernel ramdisk or u won't be able to get past lock screen. so do a full twrp backup in case
or just try dr ketan. usualy best all round working rom.
Click to expand...
Click to collapse
I have installed a custom rom without root access and my banking app and games work perfectly however Google pay is detecting the unlocked bootloader. Anyway to hide this with out rooting the phone?
VortexHD said:
I have installed a custom rom without root access and my banking app and games work perfectly however Google pay is detecting the unlocked bootloader. Anyway to hide this with out rooting the phone?
Click to expand...
Click to collapse
for google pay, some actualy revert to an older version. just search the forums. for me magisk hide works great with my banking app. and for games, im not much of a gamer so i realy dknt know. but again you should try with dr. ketan rom just in case it works. just choose to flash kernel and magisk during setup.( do a clean install so factory wipe in twrp before flashing his rom)
Well i decided to just use Stock Rom and lock the bootloader so at least most of my apps then work. I installed a modified apk of Samsung Health but it doesn't contain the heart rate monitor but I suppose that's fine and I just have to accept that Samsung Pay will never work again
Where can i get the old version of Google pay which works with unlocked bootloader?
Sent from my SM-N960F using Tapatalk
S heath can work on a rooted device with a simple change to the build prop , but secure folder and spay remain a dud