Singpass App on Custom ROMs

x3dbripper

Junior Member
Joined
Dec 11, 2023
Messages
9
Reaction score
0
singpass not working on china phone (motorola) with china rom:ROFLMAO:, getting 83-T991

But my other china phone (huawei) is working
 
Last edited:

Jerry91

Junior Member
Joined
Sep 19, 2005
Messages
19
Reaction score
10
Strange though, build 133 alone is being detected. Are you using HMA or other similar tools to augment the hiding?
(there's moles in this thread though so not answering may be better)
I found a workaround, quite interesting one. Anyway I went on to the next build version of ZygiskNext maybe that's caused the problem. But resolved alr without rolling back.
I agree. Let's just say I did some trial and error with all the possibilities till it worked 😆. But I am glad the latest version worked for you as it did for me.
is it still working?
Working fine on my side (y).
 

Nuclear Boy

Arch-Supremacy Member
Joined
Dec 19, 2009
Messages
22,014
Reaction score
11,576
I flashed EvoX 7.9.9 (A13) on my RN12 Turbo (Poco F5) and been using it since last week.

I am using latest Magisk Delta with the built-in Zygisk, Magisk Hide and Enforce SuList, together with latest PIF. (Keyword: latest)

Momo only sees unlocked bootloader. Integrity API checker indicates passes for Basic and Device. Singpass, POSB, GPay+Wallet all work fine. (Device integrity is the main factor; POSB runs even without that though)

That's if the fingerprint isn't banned. It's pretty much a cat-and-mouse game. PIF update would last a few days until FP is banned, then need to update, reboot, clear storage for GPay+Wallet (I use these as the testing "canary birds" to see if FP Is banned; never touch Singpass before this; POSB app seems quite forgiving even if Device integrity fail)

I will give fresh A14 ROMs a try soon and see how it goes without any kind of root. Some of them like EvoX apparently come with Integrity passes by default.
 
Last edited:

highdiver_2000

Master Member
Joined
Dec 26, 2009
Messages
2,534
Reaction score
178

coseas

Junior Member
Joined
Apr 28, 2019
Messages
36
Reaction score
9
I got a custom fingerprint from old phone's Rom for PIF and still works today. Guess it is still good to find a fingerprint yourself so that it will not get ban easily.
 

IOKNEE

Member
Joined
Dec 16, 2011
Messages
227
Reaction score
48
I got a custom fingerprint from old phone's Rom for PIF and still works today. Guess it is still good to find a fingerprint yourself so that it will not get ban easily.
If the PIF dev happens to use the same fingerprint as yours, then it's likely that you'll need to find another one soon. But I agree with your point that each of us needs to get a fingerprint oneself, so that it's less likely to abuse the same fingerprint.
 

SkyShroud

Arch-Supremacy Member
Joined
Oct 28, 2005
Messages
21,056
Reaction score
1,513
I flashed EvoX 7.9.9 (A13) on my RN12 Turbo (Poco F5) and been using it since last week.

I am using latest Magisk Delta with the built-in Zygisk, Magisk Hide and Enforce SuList, together with latest PIF. (Keyword: latest)

Momo only sees unlocked bootloader. Integrity API checker indicates passes for Basic and Device. Singpass, POSB, GPay+Wallet all work fine. (Device integrity is the main factor; POSB runs even without that though)

That's if the fingerprint isn't banned. It's pretty much a cat-and-mouse game. PIF update would last a few days until FP is banned, then need to update, reboot, clear storage for GPay+Wallet (I use these as the testing "canary birds" to see if FP Is banned; never touch Singpass before this; POSB app seems quite forgiving even if Device integrity fail)

I will give fresh A14 ROMs a try soon and see how it goes without any kind of root. Some of them like EvoX apparently come with Integrity passes by default.
Using my own print, 2 weeks and counting~
 

SkyShroud

Arch-Supremacy Member
Joined
Oct 28, 2005
Messages
21,056
Reaction score
1,513
I realize the hosts in KSU unmount injector by HuskyDG actually doesn't work. While your adaway will run without error, the hosts file accessed by the system is actually not updated. Thus if you try to access the supposedly blocked sites, you can still access it.

Apparently hosts need persistent mounting which is not possible because singpass detect these mounts thus know you rooted.
I also don't think you can mount the hosts to rw and then mount it to r only.
 

IOKNEE

Member
Joined
Dec 16, 2011
Messages
227
Reaction score
48
I realize the hosts in KSU unmount injector by HuskyDG actually doesn't work. While your adaway will run without error, the hosts file accessed by the system is actually not updated. Thus if you try to access the supposedly blocked sites, you can still access it.

Apparently hosts need persistent mounting which is not possible because singpass detect these mounts thus know you rooted.
I also don't think you can mount the hosts to rw and then mount it to r only.
When KSU unmount injector is installed, the hosts file in my /system/etc/ is 4MB, and my Singpass app doesn't complain.
When KSU unmount injector is uninstalled, the hosts file in my /system/etc/ is 56 bytes, and I'm unable to modify it.

I'm not using AdAway, I use shell commands to download & directly update /system/etc/hosts.

Xiaomi Redmi Note 9 Pro Global (joyeuse)
MIUI Global 14.0.3 Stable (Android 12)
KSU 11366
 
Last edited:

dildildildil

Junior Member
Joined
Jan 9, 2012
Messages
4
Reaction score
0
We're cooked. POSB app also can't work now on KSU PIF w basic integrity. Idk what's next. Gpay works with basic integrity.
 
Important Forum Advisory Note
This forum is moderated by volunteer moderators who will react only to members' feedback on posts. Moderators are not employees or representatives of HWZ Forums. Forum members and moderators are responsible for their own posts. Please refer to our Community Guidelines and Standards and Terms and Conditions for more information.
Top