yashsingh1/xdaforums huggingface dataset:
[Magisk] snake:
Thanks @thexile I can now start the app. There is a warning about the device may not meet compatibility requirements but I can click continue. However the face verification always failing to verify my identity now.

Could that still also have something to do with me being root? Anyone ever had this issue? This app seems really the most difficult to run ever. Older version previously ran perfectly fine with root on the same phone.
[Magisk] thexile:
I have not used face verification before and I have never received the device incompatible message. Therefore it is difficult to conclude what is the exact root cause of the problem you are facing.
[Magisk] Roidred:
i pulled the trigger of v15, intially hit problem. device certified was lost so have to clear play service data and apply in hide list and reboot. Then was able to run SP v15
[Magisk] dearestk:
I am facing similar issue setting up my oneplus 8T due to compatibility requirements. May I know what device and android version are you using?
[Magisk] snake:
Xiaomi 12 Pro with Android 12 (MIUI by xiaomi.eu 13.0.28)
[Magisk] dearestk:
I assume it is a Chinese export set device flashed with A12 global/eu rom? It could be the reason why singpass failed to setup.
[Magisk] snake:
Yes correct I bought it in China, rooted and then installed the xiaomi.eu version of MIUI. Yes might be the reason but the question is how to fix it. Safeteynet passes and all other tricky apps work fine. Singpass the only one which causes this issue for me now.
[Magisk] Roidred:
Buy from china should not be an issue. try to disable adaway app if you are using.
[Magisk] snake:
I am using adaway. Disabling and even freezing it unfortunately still brought no solution. Still get the same warning message and video ident is still also failing.
[Magisk] Roidred:
Is the device certified in playstore ?
[Magisk] snake:
Yes. It shows Device is certified.
[Magisk] alantay11:
There's been no fix for uob since right?
[Magisk] Roidred:
Every device is unique. If you have time. Do a fresh install.

Take a app backup using swiftbackup - this will help you restore app data easily.

Take a full twrp back - safety step

setup rom fresh

install magisk plus all other needed module shamiko and usnf

other setup including renaniming and deny list

add play store and play service to deny list. Also clear data for these 2 apps

now install sp - dont open sp.

add to deny list

reboot - dont be lazy any setting you apply for magisk a reboot is recommended

try to open now - hope you will be happy to see sp working now.
[Magisk] Roidred:
i dont use uob. what happens when you launch uob. i can test but i dont have an account.
[Magisk] alantay11:
Last time I tried opening the app is ok if you just used magiskhide. Without it would complain about root. But with hide once you log in it will lie and say having connection issues.
[Magisk] thexile:
For Singpass v15.1, disable the following:

Providers: o.removeOnConfigurationChangedListener & o.p0

Services: o.getVelocityThreshold$material_release
[Magisk] snake:
Thanks for the hint. Added these but unfortunately for me result is the same. I still get that warning popup about "Device may not meet compatibility requirements" and then the facial verification always just failes without any specific error message.
[Magisk] snake:
Thanks for the hint. But considering the huge effort with all my data and lots of individual setting in my phone I would prefer not to do a full wipe just for the sake of really having ruled out whether it helps or not at all.

There is not any monitoring or checking app by any chance to figure out what parameters singpass is checking in order to come up with that strange "Device may not meet compatibility requirements", is there?

For the moment I just use singpass on my old spare phone and everything else is good on my new phone. Still wish somehow there could be a better universal root hide that works instead of fiddling around with so many apps such as app manager, hide my applist, shamiko etc.
[Magisk] Roidred:
Your phone your choice !
[Magisk] Roidred:
Tried airfrozen ? try to freeze the renamed magisk app and then reboot.
[Magisk] snake:
Just tried but still same effect as before. I mean it does not detect root or Magisk. That seems not the problem. When that was the case SingPass would not start at all and complaining the device is rooted. After applying the AppManager magic now it is just this obscure warning popup and I can continue it scans the face but then just fails with an unspecific error. So I suspect there must be some ID or some property value the app is checking that in my phone differs from those unrooted original vendor Androids. Would really love to know what exactly is being checked here that leads to this situation. So I guess the solution must be to spoof some other check if we only knew what exactly.
[Magisk] Roidred:
i am using GSI ROM and SP works fine.
[Magisk] Roidred:
May be something wrong with your ROM, some value to tripped. Try a clean install after taking a TWRP backup. Its hard to find out what's it checking. Just install only SP and test it.
[Magisk] Zenns:
This is odd

I can't complete the register at all it throws me an error 82-T991 when last stage of register

Any idea about this tried everything
[Magisk] kaienx:
with the latest update of 15.1.2 sp, keep detecting as root no many what i did, tried everything in this thread, anyone else has issues?
[Magisk] xpr0_:
same here. Also, is there a thread that details how to disable service o.getInstalledModules and provider o.ParcelableSnapshotMutableState?
[Magisk] Lu5ck:
doesnt work for me

i simply install the old version and not update singpass

can you download play integrity api checker to see if you are strong integrity?
[Magisk] Spartacus500:
The method works, the application only checks SafetyNet compliance, does not check integrity devices Strong. After Magisk root, everyone has integrity devices Strong - fail. So far, no banking application checks it.
[Magisk] Lu5ck:
Ah, I missed out "o.setAttachListener"

:ROFLMAO::ROFLMAO::ROFLMAO:
[Magisk] yangzai:
I'm not sure if it's the case for everyone but it only works until you actually use it to login any gov sites, and then an error pops up again.
[Magisk] thexile:
For Singpass v15.2.2, disable the following:

Services: o.recompose

Providers: o.forceUniformWidth, o.u6
[Magisk] wyt18:
Thanks! This worked for me after using shell command to disable the service/providers. App Manager didn't disable them properly

- android 12.1, oneui 4.1, rooted, magisk 25.2, shamiko, lsposed 1.8.4, displax usnf 2.3.2
[Magisk] Roidred:
This worked for me. They plugged the trigger was in older version and was forced to update.

If having issue with app manager to disable. Then make a script and put into magisk folder. It will run after the boot. Plz Google to find it. App manager was good enough in my case to disable the service and providers.
[Magisk] thexile:
If anyone has issue with App Manager (download from F-Droid), you can try Lucky Patcher.
[Magisk] Gill_:
Hi

Was hoping someone can reply on this, I'm using AOSPA Topaz for my device OnePlus 9

My safetynet is certified and it shows everything as pass, I don't have any issue opening up bank application and using them, so far other application is working fine

But when I tried to register for singpass it boots me out with 82-T991 error.

Yes I run a custom ROM but my device is not rooted, I don't see how this is an issue

Custom ROM are known for fast security update and resloving bugs. I don't wish to root my phone just prefer to use custom ROM that's all.
[Magisk] doclucas:
Can anyone please have a look at UOB Mighty/UOB TMRW app with shamiko and app manager? It exits with a tempering error upon launch, so no need to even have a bank account to test it.
[Magisk] Roidred:
i dont have your same device or ROM. I am on DSP (Direct System Port) ROM A13 rooted. All works fine.

1. take a back on recovery and do a clean install. Install only SP and see if it works.

2. Root it man. - That will help to run sp.

3. Check if there is any inbuilt ad blocker in the ROM. I do see the screenshot but still can register.
[Magisk] Lu5ck:
Shamiko v0.6 can now hide root from singpass
[Magisk] wyt18:
Latest version of singpass 16.1.2 seems to have detected root again. Any workarounds?
[Magisk] abbradar:
Newest K PLUS (Kasikorn Bank) 5.16.6 also detects a non-factory device; unpacked APK hints at V-key. K PLUS 5.16.4 works well with Magisk's DenyList.
[Magisk] Sundarganesh:
How to block this
[Magisk] Sundarganesh:
How to disable this featur.

Kindly guide me
[Magisk] uddevallare:
My wife saw a problem with her newest K PLUS (Kasikorn Bank) 5.16.6, app would not load due to a non play store app being installed on her phone. She have several apps that are not from play store.

She is using a S22 Ultra, android 13, no root.

After uninstalling Call recorder by Skavlax, K Plus start.

Is there any solution for a non rooted user to bypass V-Key? Is there anything Skavlax can do to his app Call recorder so that K Plus will not detect it?
[Magisk] SnarfSnarf:
I updated K Plus app today. The version I was using was from early last year, anyhow big mistake. I pass saftey net, and use zygisk to hide the app. Had to revert back to a older version. I dont know how its detecting my phone is rooted. There seems to be quite a bit of data being transferd ingress and egress at first run. This war on rooted phones irks me. Thinking about buying a cheap phone just for bank apps and uber.
[Magisk] SnarfSnarf:
Kasikorn app has a message today that nothing less than version 5.16.8 (latest) will work after Feb 12 2023 (next week).

So I uninstalled busybox and used aurora store to download latest since I know what is going to happen. This is interesting, before I launched the app I go to magisk zygisk and check if I need to add any other things to zygisk deny list. Check the picture of the 2 newest parts of the app. Do you see the name? com.kasikorn.retail.mbanking.wap_zygote

zygote is a near spelling of zygisk

so I toggle everything on for kasikorn and reboot,

I got the dreaded 'your phone blah blah blah', but then the msg went away and app continued to load.

So i guess its working for me at the moment, version 5.16.8
[Magisk] SnarfSnarf:
KBank app detected my modified phone again. Downloaded V-Key Diagnostic apk from aurora store. Its from the same people in Singapore.

Somehow it can find supersu. I went to magisk, disabled su prompt and turned some settings off, no luck.

There is a couple of files that show up in /sdcard/Android/ named:

.com_vkey_diagnostic.vguard

.com_vkey_diagnostic.vos

I tired disabling the service for vkey, but then the message changed from the supersu found to your device has been tampered with. sigh I only have 15 or so apps on my phone, and to monkey around with this I have to install a bunch of other apks. I bet my device is really watching me now.
[Magisk] wyt18:
any workarounds for Singpass 17.1.0 to work?
[Magisk] kleptonez:
Downgrade to 6.2.1
[Magisk] wyt18:
What do you need to disable in this version (services, providers)?
[Magisk] kleptonez:
I didn't have to disable anything. But I have shamiko installed.
[Magisk] wyt18:
I have shamiko as well, and use HMA lsposed. But it still detects root
[Magisk] wyt18:
Can you share more about your setup (magisk or delta, unsf version, etc)?
[Asus ZenWatch 2] Droid_Nut:
I was able to boot into CSC fastboot mode through the USB port, and "adb reboot bootloader" But when I enter "fastboot oem unlock" I get < waiting for any device > endlessly. If anyone has any ideas, please help.

Thank You
[Asus ZenWatch 2] Droid_Nut:
Never mind, I used "Tool All In One", and I unlocked the bootloader easily. Just select "generic device".

Home - Tool All In One

TOOL ALL IN ONE This tool support 67 different devices of some different OEMs. DOWNLOAD CHANGELOG XDA THREAD OTHERS PROJECTS

toolaio.tk
[Touch Diamond, MDA Compact IV General] schreda:
Hi

I have this problem if i want to update my SPL to HardSPL, i does not flased anything yet, because i get my phone today!
[Touch Diamond, MDA Compact IV General] kien:
Try another version of HardSPL.
[Touch Diamond, MDA Compact IV General] 964rs777:
i second that use a differant one.
[Touch Diamond, MDA Compact IV General] schreda:
I tried all Versions of HardSPL but nothing works ...

btw. is it rght to go into the colored screen by turning off the phone, then turn it on with the volume down button?
[Touch Diamond, MDA Compact IV General] darkenergy:
depends what version diamond rom you have and to wich rom you want to upgrade, its usually mentioned wich spl is best in the rom-thread

rushing into this forum and blindly flashing can lead to a brick aka dead phone so take great care when proceeding :)
[Touch Diamond, MDA Compact IV General] psytech:
I'm having the same issues and I tried all the HardSPL versions myself.

once the upgrade begins, the phone screen just hangs and the installation is stuck at 0% for a while. After which it gives me either one of the following errors:

Error 202 Connection

Error 260 Connection

Only a restart of the phone will release it from the hang.
[Touch Diamond, MDA Compact IV General] Artbij:
Yes I used it, but no luck.
[Touch Diamond, MDA Compact IV General] deepu1117:
@ some 1

even i got same problem with my diamond i m not able to understand where i went wrong...any help appreciated
[Touch Diamond, MDA Compact IV General] juups7:
same proplem

i have same proplem.. first everything looks just fine but when i try to update it stuck couple of seconds at 0% and then it gives error 202
[Touch Diamond, MDA Compact IV General] kilolum:
same problem here.. :(
[Touch Diamond, MDA Compact IV General] BBEENN03:
+1

+1

+1

+1

+1

+1

+1.................
[General Questions and Answers] Ozakong:
Like in this video:

What are all the recovery mode's that can have this option that you are know about them?
[General Questions and Answers] It_ler:
I saw this for TWRP recovery only.

But have you seen this statement on TWRP website:

Why doesn't TWRP have password protection?

I’ve had people ask enough for a protected TWRP that I’m creating this page as a response so I don’t have to retype. If you’re seeing this page, you’re proba...

twrp.me
[General Questions and Answers] :
I have TWRP recovery ( the one shown in the video ) installed but I never saw a pattern lock in it. I just swipe to unlock which is default option in it.
[Fire Original Android Development] sudoers:
Hello dear community,

I have a 9th generation Fire 7 with OS 7.3.1.7 from a good friend.

The device is to be bricked.

Professionally I am an IT system electronics technician and as a hobby I am a tecnican-freak, but this is where I reach my limits.

I have already opened the device and tried the hardware method, but I also get an error message in the terminal. So that I cannot unlock the device or the bootloader.

With MTK-SU this is no longer possible with the OS as I have already read and tested.

My question is, is it still possible to crack the device with this build (date 12/20/20)?

Or am I doing something wrong?

Linux installation

mustang

magisk

everything followed as described in these instructions https://xdaforums.com/t/fire-7-2019-mustang-unbrick-downgrade-unlock-root.3944365/

A reasonable instruction video would be desirable if something like that exists

I'm from Germany so sorry if the English is a bit broken

But I hope there is some way to help me

Many Thanks

Edit:

regularly at Check GPT it breaks off see on pic 2
[Fire Original Android Development] Michajin:
What device is listed as a lsusb? If you can access the bootrom (MediaTek Phone 6227) you have hope
[Fire Original Android Development] -ANDROlD-:
If you are willing to experiment I have a couple ideas I've been contemplating as I have a device I want to root also.

Basically two methods mirroring the original, a hardware method (involves probing SPI/UART) or software method leveraging finding a exploit in userspace. (linux or arm based)

WARNING: DO NOT PROCEED IF YOU WANT TO KEEP YOUR DEVICE

I HAVE NOT TESTED ANYTHING PERSONALLY!

I'm just spitballing from a perspective of a advanced Electronics engineer and Linux backround. (none in pentesting or ANDROID environments) Which is what we need.

The Mediatek vulnerability was a once in 5 years exploit and it seems unlikely to find another exploit that wide open.

For the hardware method you'd need a USB - > TTL/UART/SPI adaptor you could try to crack root but if there isn't even a login console then you are out of luck with that aspect.

Proposed software methods:

This might be made to work if compiled for arm32-bit

GitHub - liamg/traitor: :arrow_up: :fire: Automatic Linux privesc via exploitation of low-hanging fruit e.g. gtfobins, pwnkit, dirty pipe, +w docker.sock

:arrow_up: :skull_and_crossbones: :fire: Automatic Linux privesc via exploitation of low-hanging fruit e.g. gtfobins, pwnkit, dirty pipe, +w docker.sock - GitHub - liamg/traitor: :arrow_up: :fire: ...

github.com

If we can get a stock fireOS image we could run

GitHub - cruise-automation/fwanalyzer: a tool to analyze filesystem images for security

a tool to analyze filesystem images for security. Contribute to cruise-automation/fwanalyzer development by creating an account on GitHub.

github.com

or

GitHub - fkie-cad/FACT_core: Firmware Analysis and Comparison Tool

Firmware Analysis and Comparison Tool. Contribute to fkie-cad/FACT_core development by creating an account on GitHub.

github.com

Also found some shell scripts that don't need compilation.

GitHub - peass-ng/PEASS-ng: PEASS - Privilege Escalation Awesome Scripts SUITE (with colors)

PEASS - Privilege Escalation Awesome Scripts SUITE (with colors) - peass-ng/PEASS-ng

github.com

GitHub - pentestmonkey/unix-privesc-check: Automatically exported from code.google.com/p/unix-privesc-check

Automatically exported from code.google.com/p/unix-privesc-check - pentestmonkey/unix-privesc-check

github.com

There's also Ghidra if you are a pro binary analyzer which might be the best bet but also the hardest.
[Fire Original Android Development] stickfiretv2020:
Got a interesting idea i'm working on, todo with fbtool and unbrick on this particular type of Fire 7, requires compiling lineage, possibly a bit of reverse engineering - currently thinking about it still:

https://xdaforums.com/t/fire-7-2020-mustang-brainstorming.4295541/
[Fire Original Android Development] fleisch80:
The problem is that they secretly revised the hardware for that model .

After the first production run made in 2019 , without the public knowing

They started to lock down the whole tablet.

its not only software locked , its hardware locked on the chip .

Most people didn't realize they did this after the initial 2019 production run .

Any chance I get I advise people not to purchase a newer amazon tablet . especially

The gen 9 .

You can't go wrong with the tablet 7 , gen 7 .

every variant for that Amazon model is flashable . even the ones that need to be opened up

to do the hardware short .

It doesn't look good for the gen 9 model ,

Its locked down harder then Pam Anderson growing up in the 80s .
[Fire Original Android Development] ForForkSake:
I've successfully downgraded from FireOS 7 using the hardware method. Latest magisk canary etc
[Fire Original Android Development] fleisch80:
That sounds good .

just curious , what year is that 9gen .

That could be more documentation on exactly what year model 7 , gen 9 could

be modded . maybe you found something different that could work after the

2019 batches that were shipped. Idk . I just know what I seen until know ,

but absolutely there could always be exceptions.

Chris.
[Fire Original Android Development] ForForkSake:
Sure let

View attachment 5854183

Does that help? Registered 26th October 2019
[Fire Original Android Development] ForForkSake:
mtksu software method will never work on fire os7

However, you can use the hardware method, which installs twrp and allows for downgrade back to 6
[JASJAR, XDA Exec, MDA Pro ROM Development] d3v123:
Hello everyone,

i'm trying to update my universal(T-mobile MDA Pro version) to WM6. I've tried every guide I found here, read the whole wiki and googled hours and hours for error 222. No solution...

I'm stuck at the first step when I'm installing Button 1.05 ROM. Every time I run it I get error 222 (Device is not responding).

The phone was already SIM unlocked when I got it and bootloader ver. says 1.01. SIM and memory cards are not in the phone.

I've provided more info below. Also tried with few difrent cables on difrent computers... Always error 222.

I would very much appreciate every help you can provide...

Thx

------------------------------------------

Some info from WST

Wizard Service Tool v4.2.2

05/09/08 15:58:23

CPU Manuf. FAILED

IMEI:

=> Bootloaders:

IPL: (G3 device)

SPL date unknown

=> Firmware:

OS: 5.1.xxx (Build 14847.2.0.0)

ROM: 0.0

Registry AKU: .2.0.0

Radio values FAILED

=>Extended_ROM:

Version: UNLOCKED

Name: Extended_ROM

Status: visible

=> Drives and partitions:

|--Handle--|---Size---|

33ef0c1a - 1.89G (0x79120e00)

d3d6540a - 9.99M (0x9fd800)

33e2010e - 44.43M (0x2c6dc00)

f3e71212 - 56.75M (0x38c0000)

13e71026 - 3.19M (0x330000)

f3e71002 - 3.06M (0x30fc00)

=> DOC chip unique ID:

0000000084180102153903ee0e0605d0

Key Index: 26

All Done.

------------------------------------------------

Info from Device Information:

ROM version: 1.30.115 WWE

ROM date: 4.17.06

Radio version:1.10.03

Protocol version 42.44.P8

ExtROM version: UNLOCKED

-----------------------------------------------
[JASJAR, XDA Exec, MDA Pro ROM Development] d3v123:
No ideas? :(

I have yet another question. Since this is a T-mobile, after a hard reset it installs a bunch of custom programs. Is there a way to stop it from doing this? Clear out ext rom?

EDIT : Don't bother. Maneged to solve it.
[JASJAR, XDA Exec, MDA Pro ROM Development] akcarash:
Use an extended rom unlocker first and then hard reset. After that you will have access to the extended rom. Delete whatever and agian hard reset...

For your first problem try to unlock your phone completely.
[JASJAR, XDA Exec, MDA Pro ROM Development] d3v123:
thx 4 second...

As for first, that's what I'm trying... I can't CID unlock it with WST (it says that my DOC chip is locked). In various wiki guides i'm suppoused to flash the button 1.05 rom first, but i can't do it because of error 222.

I've found this link with some tools to unlock the device. Which tool should I use to CID unlock it? :confused:

In topic about tomal's new memory card flashing there was a suggestion to CID unlock with this. I thought it was only for SIM unlocking. Can I use it to CID unlock as well? :confused:
[Xiaomi Redmi Note 7 ROMs, Kernels, Recoveries, & O] strongst:
Thread closed

OP: Please check your Message-Inbox for more information.

Thank's

strongst

Forum Moderator
[Samsung Galaxy S10e Questions & Answers] snick17:
Starting sometime about 1.5-2 weeks ago, two games on my phone don't run. I wasn't really paying attention but I think there was a small software update shortly before this problem came up but I can't be positive. The games are Void Tyrant (which crashes immediately on launch) and Dungeon Tales (which opens to main menu and the menus work but crashes once I enter game play).

Thoughts or suggestions? I have restarted the phone a couple of times. I'm not out of memory.

TIA.
[Samsung Galaxy S10e Questions & Answers] snick17:
And two days after posting this, both games suddenly worked again! Then yesterday's Samsung update broke them both once more...
[OnePlus 7T Questions & Answers] thetoady:
I have a t-mobile branded 7T that I unlocked and global'ified to use dual SIMs. as I live overseas, I have both my t-mobile sim (for text message for 2FA) and my local sim. To avoid accidentally picking up the phone for scam calls, I did unconditionally forwarding to my google voice number. But because of this, it now shows an annoying notification "forwarding all calls" that can't be dismissed.

I've gone into the notification settings and deprioritized it as much as I can (so its generally on the bottom and "minimized") but wondering if anyone knows a way to get rid of it for good on a non rooted phone?