Database Develop

Magisk Hide

Magisk Hide doesn't seem to be working when it comes to my automobile's app, Uconnect. I'm rooted and now the Uconnect app states that I'm using an unsupported device. It worked before rooting.View attachment magisk_log_20181022_153305.log
{
"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"
}

tried clearing apps data?

kamilmirza said:
tried clearing apps data?
Click to expand...
Click to collapse
Yes. I even uninstalled, then reinstalled the Uconnect app.

destiple said:
Yes. I even uninstalled, then reinstalled the Uconnect app.
Click to expand...
Click to collapse
THIS great module might help :fingers-crossed:

Destiple, can you confirm whether MagiskHide Props Config, which kamilmirza referred you to, worked?
Alternately, did you find another solution to get Uconnect working?

If you haven't already you're probably better off testing the brand new MagiskHide (rewritten from scratch) in the Canary builds (currently at build 18110).

Didgeridoohan said:
If you haven't already you're probably better off testing the brand new MagiskHide (rewritten from scratch) in the Canary builds (currently at build 18110).
Click to expand...
Click to collapse
That's very good to know. I'm nervous about running a Canary build on my normal phone, but I'll see if I can find a spare to test it on.
Will the new MagiskHide be on the next Magisk update, or is it several versions away from being in the stable build?

Try using the "Hide Magisk Manager" option in the settings. I was having the same problem, but after doing that and restarting I can use the Uconnect app again.

Coop9 said:
Try using the "Hide Magisk Manager" option in the settings. I was having the same problem, but after doing that and restarting I can use the Uconnect app again.
Click to expand...
Click to collapse
Good to know! I tried it - hiding the manager by itself wasn't enough. But once I added Uconnect to the apps being hidden, *then* the app finally loaded.
Of course, upon trying to log in, the app immediately crashes. Would that have anything to do with it being added to the MagiskHide list?

Banking app is detecting root

Hi there
I am on LOS17, my bank app forced me to update, then it started detecting root
it was hidden through magisk, the safteynet is passed
deleted twrp folder
uninstalled - reinstalled
used island
no luck
if someone can check the app please
BankMuscat Mobile banking - Apps on Google Play
thanks

I checked with me on Samsung S7 9.0 Pie, Magisk root, tried different methods, does not work, detects root after entering login details
{
"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"
}

Same issue with me in Bank Muscat app.

https://www.reddit.com/r/androidroot/comments/kq6gy3

thewise999 said:
Same issue with me in Bank Muscat app.
Click to expand...
Click to collapse
I do not know what is the method they are using
Thanks for your try

Spartacus500 said:
I checked with me on Samsung S7 9.0 Pie, Magisk root, tried different methods, does not work, detects root after entering login details
View attachment 5151217
Click to expand...
Click to collapse
Thanks for your try
It seems a server side
Can we spoof it?

I'm still stuck with bankmuscst, i remember last time there was a folder to be renamed, but can't recall which folder exactly

shiko0o said:
I'm still stuck with bankmuscst, i remember last time there was a folder to be renamed, but can't recall which folder exactly
Click to expand...
Click to collapse
any luck?
which rom you are you using?
i have passed all of the safety net test but this bank still is a pain

eraser0 said:
any luck?
which rom you are you using?
i have passed all of the safety net test but this bank still is a pain
Click to expand...
Click to collapse
Try this
Comdirect photoTAN app detecting root
Since version 8.3.0 additional measures to detect root have been added, do not update as MagiskHide won't be able to prevent detection. Until a solution is found I would recommend staying on the previous version for as long as possible. Finding...
forum.xda-developers.com

eraser0 said:
Hi there
I am on LOS17, my bank app forced me to update, then it started detecting root
it was hidden through magisk, the safteynet is passed
deleted twrp folder
uninstalled - reinstalled
used island
no luck
if someone can check the app please
BankMuscat Mobile banking - Apps on Google Play
thanks
Click to expand...
Click to collapse
Hi bro try this
Magisk App hidden (unhide is possible), Magisk Hide activated
Modules:
Riru
Riru LSPosed
Riru - Enhanced mode for Magisk Hide v2
XPrivacyLua activated via LSPosed and marked Get Applications for the Bankmuscat app in XPrivacyLua.
It's worked for me

Unable to pass ctsProfile

Hello All,
My device was brick when I dirty flash the Lineage OS 20211003 to 20211110.
So the flash it back to stock Android 11 (Nov 2021 update) via fastboot, then flash Lineage OS 20211110 again.
And this time everything is fine except I can get the ctsProfile pass at 20211003, but failed this time.
I have try though the process at https://forum.xda-developers.com/t/tutorial-unlock-bootloader-get-root-and-valid-safetynet.4178673/
but no luck.
Magisk version is 23.0
Spoiler
{
"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"
}
And the modules I currently installed, tried riru - LSposed but it is not helping so I removed.
Spoiler
Any ideas I can fix the ctsProfile issue?
{Mod edit: Spoiler added for better reading & scrolling experience}

Is that build of LOS using a certified device fingerprint out of the box? Otherwise you need to apply one to pass CTS.

Didgeridoohan said:
Is that build of LOS using a certified device fingerprint out of the box? Otherwise you need to apply one to pass CTS.
Click to expand...
Click to collapse
Humm ... I'm not sure, may I ask how to check?
Ok, I installed MagiskHide Props Config, and got a string as following:
google/redfin/redfin:11/RQ3A.211001.001/7641976:user/release-keys
but I'm not sure it is certified or not

Arlik said:
Humm ... I'm not sure, may I ask how to check?
Ok, I installed MagiskHide Props Config, and got a string as following:
google/redfin/redfin:11/RQ3A.211001.001/7641976:user/release-keys
but I'm not sure it is certified or not
Click to expand...
Click to collapse
You mean that's the reported used fingerprint? Looks ok, but it's also possible that the ROM has a security patch date that doesn't match the print. Try applying a Pixel 5 print from the module and see if that helps.

Try to apply Pixel 5, 5a, 3a Android 11's fingerprint by pressing
f - Pick a certified fingerprint
After reboot, it still show
google/redfin/redfin:11/RQ3A.211001.001/7641976:user/release-keys
Did I do something wrong?

Just an update.
The issue should be relay to the November update of LOS
now I redo all my process with LOS 20211020 version, safetyNet has passed.

Arlik said:
Just an update.
The issue should be relay to the November update of LOS
now I redo all my process with LOS 20211020 version, safetyNet has passed.
Click to expand...
Click to collapse
All of a sudden, my SafetyNet is failing. I've tried these tricks posted online like Riru, Universal Safety Fix, etc. None of them work! I am on LOS 20211229. If the 20211020 version would work, I don't mind going back. Where can I download it? The official LOS site now has only the Dec 2021 version. I tried to Google for this older version but can't find it. Thank you

Question Can’t make any google pay or wallet pay as unable to attach my card to 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"
}
any body facing such issue as can’t make any payment or after u try to attach your bank’s information, hereby it shows up in this scenario.
Any solution for this? Thanks guys!

Hi if you have unlocked bootloader.
Then root with magisk and flash saftynet fix and shamiko.
Open magisk setting and enable zygisk and add to black list:
GM's (Google play services), Google play, Google pay/wallet then wipe the data from all these apps and restart

MrScarl3t said:
Hi if you have unlocked bootloader.
Then root with magisk and flash saftynet fix and shamiko.
Open magisk setting and enable zygisk and add to black list:
GM's (Google play services), Google play, Google pay/wallet then wipe the data from all these apps and restart
Click to expand...
Click to collapse
Really don't need to do half of that. Just magisk, zygote, enforce list and add the universal safety net fix module.

That did not work for me. So ya

MrScarl3t said:
That did not work for me. So ya
Click to expand...
Click to collapse
clear the data from google pay

I suppose Google has changed their safetynet pass
You could find fix in this thread https://forum.xda-developers.com/t/discussion-google-pay-magisk-discussion-thread.3906703/page-139

helgi1507 said:
I suppose Google has changed their safetynet pass
You could find fix in this thread https://forum.xda-developers.com/t/discussion-google-pay-magisk-discussion-thread.3906703/page-139
Click to expand...
Click to collapse
I'm using this version and it's fine.
Zygisk and safety net fix applied..reboot after both fixes are applied then install gpay

MrScarl3t said:
But just as if we don’t do any root on it, shall I still by pass through the magisk? Because this are just ordinary use as never had any root before.
Unless kind of CN set which been flushed to global Rom also consider as rooting.
Hi if you have unlocked bootloader.
Then root with magisk and flash saftynet fix and shamiko.
Open magisk setting and enable zygisk and add to black list:
GM's (Google play services), Google play, Google pay/wallet then wipe the data from all these apps and restart
Click to expand...
Click to collapse

helgi1507 said:
I suppose Google has changed their safetynet pass
You could find fix in this thread https://forum.xda-developers.com/t/discussion-google-pay-magisk-discussion-thread.3906703/page-139
Click to expand...
Click to collapse
Seconded - that thread will be the best resource for finding help.

Question [HELP][A12][MIUI13][BETACN] Apps not compatible with the device

I recently changed my default rom to do some tests with the miui beta china, but I ended up coming across this message in some apps that I tried to install:
{
"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"
}
My device is not rooted at the moment!

OYH0 said:
I recently changed my default rom to do some tests with the miui beta china, but I ended up coming across this message in some apps that I tried to install:
My device is not rooted at the moment!
Click to expand...
Click to collapse
Probably because the bootloader is unlocked and the play store not certified.
If your device is a Chinese version you cannot lock the bootloader (brick) with a Global, EEA, etc. version.
Root +magisk hide necessary.
For other versions locking possible with Miflash.
Or
Install these Roms (based on china ,stable or Weekly) you will have the play store certified without root and without locking the bootloader.

NOSS8 said:
Probably because the bootloader is unlocked and the play store not certified.
If your device is a Chinese version you cannot lock the bootloader (brick) with a Global, EEA, etc. version.
Root +magisk hide necessary.
For other versions locking possible with Miflash.
Or
Install these Roms (based on china ,stable or Weekly) you will have the plastore certified without root and without locking the bootloader.
Click to expand...
Click to collapse
I've already done some procedure to hide magisk, like installing safetyNet Fiz, Shamiko and Airfrozen
I saw some things as soon as there are some modules that solve this problem, like the play store visa or vending visa, but if there is another module that can help me?

OYH0 said:
I've already done some procedure to hide magisk, like installing safetyNet Fiz, Shamiko and Airfrozen
I saw some things as soon as there are some modules that solve this problem, like the play store visa or vending visa, but if there is another module that can help me?
Click to expand...
Click to collapse
Did you try Magisk Beta which can be activated from the classic apps.