FNB issues running on a bootloader unlocked device.

C

cjoliver

Member
Joined
Jun 30, 2013
Messages
27
Reaction score
0
Location
Centurion, Gauteng
Has any else been having issues running the latest fnb android app on a bootloader unlocked device?

I have confirm with about 6 devices that if you have an unlocked bootloader, then the FNB app doesn't open and you can't install it from the android play store. Factory reset and lock the bootloader and boom, it works again.

You can download the latest APK from a mirror site, but it only flashes the splash screen and then disappears again if started.

So far the Devs are not answering my emails.

Wanted to find out of anyone else is having the same experience?

Currently I'm running version 7.8.0-50 (85) hce as this seems the be the last version that will start on an unlocked bootloader.

Thanks
CJ
 
cjoliver said:
Has any else been having issues running the latest fnb android app on a bootloader unlocked device?

I have confirm with about 6 devices that if you have an unlocked bootloader, then the FNB app doesn't open and you can't install it from the android play store. Factory reset and lock the bootloader and boom, it works again.

You can download the latest APK from a mirror site, but it only flashes the splash screen and then disappears again if started.

So far the Devs are not answering my emails.

Wanted to find out of anyone else is having the same experience?

Currently I'm running version 7.8.0-50 (85) hce as this seems the be the last version that will start on an unlocked bootloader.

Thanks
CJ
Click to expand...
Why should they? If you unlock the bootloader the security goes out the window. Face the facts.
 
It won't install on an unlocked bootloader.

Security issues.
 
It also stopped working on a friend's Pixel 8 with GrapheneOS. Locked bootloader. No root / magisk.
If a P8 with GOS is insecure according to FNB, then I challenge them to show us a more secure phone. Looks like it's just not on the approved list / non-standard so not supported.
 
It's part of the Android security API layer implementation to determine if the bootloader is safe and not been "tampered" with.

Standard operating procedure on security. Was probably tripping the DRM key check or something.

AFAIK, you got some device-specific DRM keys on your device, such as Widevine. Once you unlock the bootloader, it wipes that keys, and cannot be restored afterwards, even if you relock the bootloader.

They don't want your device to be "compromised" with a "root kit" that can potentially be a datalogger, keylogger and potentially provide the login data to the thieves that can empty your bank account in seconds.
 
Never realised unlocking a bootloader was still a thing. What's the use case here?
 
Same story here on Pixel 8 Pro, and all my other rooted devices.
All other banking apps work fine except for FNB. I think they are being a bit ridiculous about this.

Play Integrity Check passes, SafetyNet check passes, Magisk is hidden - with Play Integrity Fix and PlayCurl modules running.

How did you get version 7.8.0-50 (85) hce? I tried a previous backup of an older version and it didn't work.

Can you re-lock the bootloader after rooting?
 
IamNoone said:
Neither did I. The last time I did that was on a Samsung Galaxy S3 just to try it and load another OS "CyanogenMod" was actually a good OS imho.
Click to expand...
Same here. See no need to play around with the security settings and load other software any more.
 
Fsck it's worse than that.

Web based, on a PC, so off topic, but. Yesterday I made a new beneficiary, paid that beneficiary, then went to manage an investment account. Got an error. So I clicked on "Contact Us"

1719900989949.png

OK, so this browser, the one I just used to pay someone, the one I've been using all year, is not good enough to _contact support?_

WTF FNB, WTF?
 
It's working again on both family members' devices (GrapheneOS and PixelOS, so both "non-standard").
 
Koos Custodiet said:
Fsck it's worse than that.

Web based, on a PC, so off topic, but. Yesterday I made a new beneficiary, paid that beneficiary, then went to manage an investment account. Got an error. So I clicked on "Contact Us"

View attachment 1734085

OK, so this browser, the one I just used to pay someone, the one I've been using all year, is not good enough to _contact support?_

WTF FNB, WTF?
Click to expand...
Which browser?

Did you try another browser?
 
I think the only reason I have an FNB account is because of the Paypal requirement back in the day. Is that even a thing anymore? Not sure it's worth this ****.
 
arent there magisk modules for spoofing this so banking apps can work

but agree with most of the feedback here... the days of unlocking and sideloading ASOP stuffs are long gone...
 
ShloshMalosh said:
arent there magisk modules for spoofing this so banking apps can work

but agree with most of the feedback here... the days of unlocking and sideloading ASOP stuffs are long gone...
Click to expand...

Used to do this since the Android Beta days before Cupcake, but the last phone I got is a vanilla bootloader and stock ROM, its definitely not necessary anymore to run custom roms to get rid of bloat or enable certain features, most of the QOL is baked into the stock ROM. The only thing I am missing is my Ad-Free mode on a custom ROM, but that I can live without for now
 
R4ziel said:
Used to do this since the Android Beta days before Cupcake, but the last phone I got is a vanilla bootloader and stock ROM, its definitely not necessary anymore to run custom roms to get rid of bloat or enable certain features, most of the QOL is baked into the stock ROM. The only thing I am missing is my Ad-Free mode on a custom ROM, but that I can live without for now
Click to expand...
adguard and revanced
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter