Hello everyone,
Is it possible to restore biometric data and Samsung Pass after unrooting a Samsung phone, relocking the OEM bootloader and doing a full factory restore (hard reset) ???
Thanks in advance for your help and feedback.
Good appetite and have a nice day
If those apps depend on Samsung security features...most likely no.
Samsung uses an "e-fuse" (basically a write once registry) that is tripped if modified or custom images are flashed to the device. It doesn't matter whether you simply rooted with Magisk, or flashed TWRP, or flashed a custom ROM - once Knox is tripped, it is permanent and cannot be reversed. Therefore, even if you restore the device to its original factory configuration, Knox will remain tripped and any apps that depend on it will not work.
Related
I'm a user who likes testing different ROMs, Kernels, etc. I had a Galaxy J3 2016 but recently I got a new J5 2017, which has that Knox protection.
I've been reading about this service but I still have some questions about it. As far as I concern, Knox's main function is to protect your device against information steal, It also knows if a modification is done to the system and that results on a warranty void. So here are the things I still don't know about Knox:
- When does Knox get triggered? When rooting your device? When you install a custom recovery? When you install a custom Kernel? Or only if you flash a custom ROM?
- How does a triggered Knox affect my device? Only voiding my warranty? Will I loose Knox's functions like the secure folder? Will I still get OTA Updates? Or I'll have to update manually?
- Is it possible to reset the Knox counter to 0?
Thank's for helping me out guys!
Hey,
I tried some custom kernels but only Magisk make success fake knox 0x0.
I read that apps like Samsung Pay can easy recognise Magisk.
For now i have now only Magisk installed but Samsung Pay wont work.
Is possible to add to Stock Oreo ROM fake knox 0x0 without Magisk?
In resultat to have "Original STOCK ROM like before knox triped"
RE: Reset knox
Please note that there isn't a solid solution yet to reset knox. The best way is to change the motherboard or buy a new device instead. Since from Samsung Galaxy S5, samsung started influencing e-fuse technology to knox implement, knox reset isn't possible at all .
And you can find knox faked samsung firmware for your device in XDA. But even thou, you couldn't able to fake or make use on Samsung pay and Samsung pass. Those applications will verify both device status ( Custom binary or root privileges ) and knox status.
Hope this helps :laugh:
Device status is easy to make Oficial by changing sysscope, only fake knox is difficulter because of Magisk it is with root.
I wanted to try make full stock with only knox mod without root ;]
Wirusx said:
Device status is easy to make Oficial by changing sysscope, only fake knox is difficulter because of Magisk it is with root.
I wanted to try make full stock with only knox mod without root ;]
Click to expand...
Click to collapse
You can't do it at all. The only way is to fake knox status by a custom kernel or modify the original kernel instead. But it's hard to modify / fake the original kernel to show knox 0x0. Because it has been encrypted and verify the original binary value in each boot. But you can give it a try..
i have a important Question and though i will my s7 flashing with the btu android 8 firmware and i use samsung pass (login with biometric fingerprint) in different sites
when i flash my phone will blow the knox counter or make samsung pass useless if so how can I prevent this and the whole thing with the oem unlocking together so if I activate oem unlocking the knox counter burns automatically ??? if all went well, then I have in the settings, the option oem unlocking start or can I turn off this option after flashing?
In advance thank you for the quick help
Knox only trips when you flash a recovery like TWRP, it will never change flashing original firmware. if your Knox is already tripped, then go ahead and root your phone, if it's not, then flash Oreo with Odin 3.13 and you should be able to use everything like Samsung pay, health, etc
Sent from my SM-G930F using XDA-Developers Legacy app
You do not need OEM unlock for flashing stock
If you flash custom you do need OEM unlock enabled, but DO NOT disable it while you are still running custom or you will brick
Stock = OEM unlock disabled
Custom = OEM unlock enabled
wegiwegi said:
Knox only trips when you flash a recovery like TWRP, it will never change flashing original firmware. if your Knox is already tripped, then go ahead and root your phone, if it's not, then flash Oreo with Odin 3.13 and you should be able to use everything like Samsung pay, health, etc
Click to expand...
Click to collapse
Thanks for the answer it was very helpful I have android 8 in my s7 now the only Stuff is I can not use Save folder that's
Although not bad but I would still like to know why it does not work
Sorry I can't help you in that one, I am rooted, so no access to it, never used either, maybe a factory reset will help, but backup your stuff before doing it
Sent from my SM-G930F using XDA-Developers Legacy app
Hey everyone,
I am new to the programming scene and this forum.
Anyways, I run a repair business in Ontario and have repairs come in daily. In particular today, I had a Samsung Galaxy S7 come in for repair and the issue the customer explained was they forgot their pin or pattern lock. I used to be able to use TWRP and go into the system and delete the gesture.keys without losing all data but I read up on the new technology now with Knox and bootloader and I was told flashing TWRP on the Galaxy s7 without bootloader unlocked will cause bootloop. All I need is to get into TWRP to delete those keys because customer CANNOT lose any DATA (very important). Is there anyway to get TWRP on the Canadian variant without wiping or causing a boot loop. I don’t need root. Just need access to the system files from recovery to delete that key file. Unless someone else can chime in and offer another solution, but please HELP!
ghostnetworksolutions said:
Hey everyone,
I am new to the programming scene and this forum.
Anyways, I run a repair business in Ontario and have repairs come in daily. In particular today, I had a Samsung Galaxy S7 come in for repair and the issue the customer explained was they forgot their pin or pattern lock. I used to be able to use TWRP and go into the system and delete the gesture.keys without losing all data but I read up on the new technology now with Knox and bootloader and I was told flashing TWRP on the Galaxy s7 without bootloader unlocked will cause bootloop. All I need is to get into TWRP to delete those keys because customer CANNOT lose any DATA (very important). Is there anyway to get TWRP on the Canadian variant without wiping or causing a boot loop. I don’t need root. Just need access to the system files from recovery to delete that key file. Unless someone else can chime in and offer another solution, but please HELP!
Click to expand...
Click to collapse
If the bootloader on that device is locked, you won't ever be able to use TWRP at all, not ever, not by any means.
If you know exactly what firmware build number thay had installed before this happened, you can try flashing that exact version of stock firnware via Odin. As long as the firmware that you flash does not contain a different(upgraded/downgraded) bootloader, it "shouldn't" wipe their personal data but it does wipe the user settings(pin/pass in this case). When flashing via Odin, the user data does not get wiped unless the bootloader on the device is upgraded or downgraded during the flashing process. Their data should stay intact if you use the firmware version that is already on the device.
If the bootloader is locked, then regardless of what you do, flashing the firmware is the only way you're going to fix this, whether it wipes their data or not. Flashing the current firmware that is already on the device is really your only option.
Sent from my LGL84VL using Tapatalk
TWRP
I’ve managed to reset the password because cudtomerbhad her Samsung account linked to the phone. Logging into Samsung online gives you the option to remotely unlock the pattern. She now has all her data and password is gone. Thanks for the quick reply regardless
ghostnetworksolutions said:
I’ve managed to reset the password because cudtomerbhad her Samsung account linked to the phone. Logging into Samsung online gives you the option to remotely unlock the pattern. She now has all her data and password is gone. Thanks for the quick reply regardless
Click to expand...
Click to collapse
Ah yeah, I forgot about that option because I don't use the Samsung account feature on my phones. Plus, I was looking from a perspective of what could be flashed or not without causing data loss.
Sent from my LGL84VL using Tapatalk
Good Morning Everyone
As the title suggests, i am looking to return my S22 Ultra back to stock.
i was on beyond rom for a bit, but too many apps complaining that my device was rooted has forced my hand to return my device back to stock once again.
I flashed the stock rom via odin, then locked my bootloader and wiped all data.
However i am still getting messages that my device is modifed.
Anyone got any ideas how to can truely return to full stock?
Thanks in advanced.
And yes i did do a search on the internet before asking, but i have been unable to find any advice outside of what i have already done.
happend to me, too. But only on the latest firmware. When I flash an older firmware, it won't appear. But after updating again to the latest ROM the message appears
Cheers mate. I'll give that a go.
Also note that if the device was rooted then you triggered the Knox flag and that one CANNOT BE RESET, it's an "efuse" (a hardware component that once changed it's state can only be reset by replacing it, i believe you need to replace the entire motherboard for that).
So, if the application checks the Knox status it will fail.
Here are a few apps that i know that will not work anymore :
- Knox itself (and any app that uses the Knox library/API )
- Samsung Pay
- Samsung Health
- Secure Folder
A few years ago I also had a banking app that failed to worked with a Knox flag triggered (on a Note 8), but after an update it allowed me to use the phone as long as i didn't have it rooted.