Related
So I have a problem guys, I'm going to tell you all the long story, I just recently bought a S4 from Telcel in México, LTE edition, the model is SGH-I337M, and came with build I337MUMUAMG1, 4.2.2.
I was anxious to tinker with it, so first thing I did as soon as I came home was rooting it with CF-Auto-Root, everything until that point was smooth sailing, but I couldn't make the I337M version of Philz Touch Recovery to flash via Odin, so I flashed the GT-i9505 version and IT WORKED, it booted to recovery normally, rebooted to system, etc. So I thought "oh boy, I'm ready to go". But before that, I read that for data & Wi-Fi to work properly in 4.3 Custom Roms I had to flash the 4.3 modem.bin file via Odin, so I did that. No OTA, no 4.3 Stock Rom, only the modem-bin file. The modem version never changed in the "About Device" tab to "I337MVLUEMK6" like it was supposed to do, it stayed as "I337MUMAMB2" but I also read that was normal so I didn't think about it much.
After that I went into recovery with my ready-to-flash files in my SD, wipe my system/data/cache/etc without making a Backup because that's how retarded I am and try to flash my ROM only to get it aborted every time due to "assert failed: getprop("ro.product.device") == "jfltecan" ||" issues, so I assumed it had to do with me using the GT-i9505 version of Philz Touch with a I337M Canadian Custom ROM. I shat bricks for a while because I had wiped my system and I had no backup, so I just turned my phone off, downloaded the "I337MUMUAMG1" Telcel Stock Rom, turned on my phone in Download Mode and flashed it via Odin while I prayed.
It worked, it booted, everything was alright with the world again (but not so much on my pants where tons of bricks were shat), I had voided my warranty but whatever, I was gonna Root and Triangle Away that thing to make my phone fully stock again, so I get ready to do exactly that, get my phone into Download Mode, and Root it with CF-Auto-Root, again, it worked, it booted, and had the SuperSU icon, smooth sailing again, OR SO I THOUGHT.
I open SuperSU to update dem binaries and a pop-up emerges saying that Samsung Knox had been detected and if I want to attempt to disable it. Oh boy, I was not ready for this, I hadn't recovered from the last shatbricking session, and now my pants were a national disaster area. Anyway, I also read that using Triangle Away with a Knox enabled phone was a highway to a very expensive paperweight, so thankfully I was smart enough to don't try it.
As I kept shatting bricks I decide to reflash the Stock "I337MUMUAMG1" Telcel Rom via Odin to keep my phone as safe and near stock as possible, everything worked, and now I'm running the "I337MUMUAMG1" build, with no root, stock, with yellow triangle and apparently, Knox. :crying:
I got curious about it, so I went into Download Mode to search for the Knox Warranty Void Flag... But I didn't got it, neither the Warranty Bit. On Download Mode I get only the Usual:
ODIN MODE
PRODUCT NAME: SGH-I337M
CURRENT BINARY: SAMSUNG OFFICIAL
SYSTEM STATUS: OFFICIAL
USB-CONFIG-LSB: 0x30
WRITE PROTECTION: Enable
And I don't have any Knox apps on my drawer, but they appear on the "Application Manager -> All" menu, so I'm confused as hell, and since I can't check my Bootloader version I can't know if I have Knox on my bootloader or only on my Rom. And I'm way to scared to try anything, and also scared about OTAs and updates since I don't know the state of my phone. Any help on this?
tl;dr: Got brand new SGH-I337M with I337MUMUAMG1 as Stock. Rooted, Flashed Philz Touch for GT-i9505, Flashed 4.3 modem.bin only, Tried to flash Custom Rom, messed up, Flashed Stock I337MUMUAMG1 again, Rooted, got Knox popup upon opening SuperSU for the first time, shat bricks, Flashed Stock I337MUMUAMG1 again to be as stock as posible. If I boot into download mode I don't get Knox Warranty Void Flag in the Download Mode, don't have Knox apps on my App Drawer but I see them on the Application Manager -> All. Too scared to try anything until I know if I have Knox enabled on my Bootloader or only Knox Apps on my Rom.
Any help with this will be greatly appreciated, many thanks in advance, and thanks for reading.
EDIT: FORGOT ABOUT SOMETHING. After Flashing Stock I337MUMUAMG1 For the second time after getting the Knox warning popup on SuperSU, I got an OTA, couldn't cancel it but I don't know if it changed anything, since my build number was it was I337MUMUAMG1 still, it was a 250mb file.
sounds like you have knox yes. As to why it doesnt show in download mode, I can only speculate that when you flashed back to 4.2.2 the recovery was replaced with a pre-knox variant. If you're seeing knox in app manager>all as you mentioned, then you have knox yep. I have the same, just a shortcut, then knox crap in app manager> all.
Interestingly, I came from gummy 1.1, with root and CWM recovery. However since i was rooted, i couldnt obtain the 4.3 update OTA. So, I downloaded the 4.3 stock, flashed with odin (auto-reboot/f reset selected) and my knox shows 0x0. Granted I don't have root, but my main reason for this was battery life, which sucked balls on 4.2.2 rogers variant. 4.3 rogers variant is MUCH improved. I'm actually getting better life out of the stock fw, then i was with gummy 1.1. I hear all these horror stories, but I have yet to have a single app crash on 4.3 stock (i do miss xposed tho)
I haven't' re-flashed and tripped KNOX because it isn't just some security crap samsung threw on to stop custom recoveries/kernel's etc. It's actually Samsungs corporate solution for BYOD policies. The whole reason it blows the fuse, isnt just to stop warranties either, it's to communicate with exchange/corporate policies and let exchange/network know that your device is secure and following corporate policies. We all know android and linux are one in the same, adding this now gives samsung the ability to sell a managment suite (like BES in blackberry world) that uses knox for remote wipes/locks/factory reset/anti-theft. granted these exist already, but in a basic state. Look for these to be expanded on shortly.
If you blow your efuse, and use active sync , your going to be up **** creek shortly. I'm going to wait until this is defeated. Yes Knox is a hardware based efuse (the flag), but make no mistake, it is software solution and thus can be exploited. Patience is key here, imho. Just wait until the knox based sys admin tool is released for admins. anyone with a tripped flag is going to have a problem (if in business world). Sorry if I ran on a bit there, but yes, it sure seems you have knox and you should treat the device as though you do.
oh and the new SSO functionality is provided by knox, so if you can't use it, no single sign on for you i'm afraid.
http://www.samsung.com/global/business/mobile/solution/security/samsung-knox
Certain KNOX elements are present in 4.2.2 builds, however, the entire KNOX implementation (Kernel and KNOX suite) are only on 4.3 builds. More than likely, the version of SuperSU you are using detected that those certain KNOX apks (from 4.2.2) are on your phone and reported the "Samsung KNOX has been detected..." message.
scott14719 said:
Certain KNOX elements are present in 4.2.2 builds, however, the entire KNOX implementation (Kernel and KNOX suite) are only on 4.3 builds. More than likely, the version of SuperSU you are using detected that those certain KNOX apks (from 4.2.2) are on your phone and reported the "Samsung KNOX has been detected..." message.
Click to expand...
Click to collapse
So that means there is no Knox in my boot loader so I can reset my triangle counter to be as stock as possible to keep my warranty?
Aelyus said:
So that means there is no Knox in my boot loader so I can reset my triangle counter to be as stock as possible to keep my warranty?
Click to expand...
Click to collapse
I have no idea about resetting the triangle counter. I've never needed to do it, so I can't help you there.
Guys, I have a question related to this.
I have I9195L (Latin version of S4 mini) and I have read about knox software which may cause issues to rom flashers like me (I used to have S Advance and tried many roms until it died)
When I enter into flash mode, I noticed that there was no knox flag at all (like the ones I saw on some other users shots), so my question is, do
Do I have that knox crap or not?
I do realized that I have some knox software installed, like knox store (I didnt touched anything of this just in case).
Can I safely try other ROMs, including Cyanogen mod?
I have rooted using the safe method posted somewhere around here in the forums.
BTW: I have stock rom... for the moment...
Please let me know.
Thank you in advance.
Aelyus said:
So that means there is no Knox in my boot loader so I can reset my triangle counter to be as stock as possible to keep my warranty?
Click to expand...
Click to collapse
Yes. However, the best way to keep knox untripped to return for warranty is to simply flash the stock fw via odin. Poof, root gone, and check the f reset flag to reset the flash counter safely. You also have same scenario I did. I was running gummy 1.1 (back in nov) when 4.3 ota was released, so I flashed 4.3 via odin and knox is still 0x0. Kingo will root 4.3 and keep knox at 0x0, it did for my i377m and a coworkers as well. You can use wanam to fake official and keep ota updates for the upcoming kitkat update. Just be prepared to flash it via odin, as nobody really knows how supersu in survival mode will react to the 4.4.2 update ota. Only stipulation is you CANNOT run a custom recovery without tripping knox, or a custom rom. So I simply use xposed + wanam and customize the TW firmware that way. I have root, I have my warranty, and I can rip out any bloat I care to. HTH.
Guys, cyanogen does trip Knox and Odin does not trip Knox?
Enviado desde mi GT-I9195L mediante Tapatalk
cenovita said:
Guys, cyanogen does trip Knox and Odin does not trip Knox?
Enviado desde mi GT-I9195L mediante Tapatalk
Click to expand...
Click to collapse
Cyanogen trips knox yes. Odin will not, provided you arent attempting to downgrade to say, 4.2.2 from 4.3. Once on a knox "infected" bootloader, cant downgrade without knox tripping.
Sent from my SGH-I337M
azuziel said:
Cyanogen trips knox yes. Odin will not, provided you arent attempting to downgrade to say, 4.2.2 from 4.3. Once on a knox "infected" bootloader, cant downgrade without knox tripping.
Sent from my SGH-I337M
Click to expand...
Click to collapse
Thank you very much for your response.
Final question, if I don't have Knox in my loader (I don't see the flag in Odin mode) I can install cyanogen and go back to stock (4.2.2) if I want to and the guaranty should be fine, right?
Enviado desde mi GT-I9195L mediante Tapatalk
cenovita said:
Thank you very much for your response.
Final question, if I don't have Knox in my loader (I don't see the flag in Odin mode) I can install cyanogen and go back to stock (4.2.2) if I want to and the guaranty should be fine, right?
Enviado desde mi GT-I9195L mediante Tapatalk
Click to expand...
Click to collapse
Provided you dont see any knox lines while in download mode, or odin mode, yes.
Sent from my SGH-I337M
azuziel said:
Provided you dont see any knox lines while in download mode, or odin mode, yes.
Sent from my SGH-I337M
Click to expand...
Click to collapse
Nope, no lines related to Knox in download mode.
Thank you!
Enviado desde mi GT-I9195L mediante Tapatalk
Hello , I would like to put my flash counter to 0 with triangle away, I have an S4 i9505 with CM12, but the problem is that it flash the kernel, but never restarts with options to reset, I have to manually restart the it boot normally, I do not understand ..; HELP
Hello,
Our device doesn't have flash counter. That's the Knox warranty void flag, once becomes 0x1 can't return to 0x0
AntaresOne said:
Hello,
Our device doesn't have flash counter. That's the Knox warranty void flag, once becomes 0x1 can't return to 0x0
Click to expand...
Click to collapse
The famous AntaresOne that meets me. It's an honor. Knowing that I have your rom . Thank you, but I do not understand, triangle away is supposed to furnish the counter to 0? But it's not happening, yet s4 is compatible. I read everywhere that it is possible to reset the flag to Knox warranty void 0x0; I do not understand Sorry for my english
Some versions of Android available on the S4 had a bootloader that did not utilize the Knox security software. The devices with this bootloader had a counter that would show how often the device's firmware was flashed. This is the flash counter that Triangle Away refers to, and it could be reset with that app. When the new bootloader with Knox was included, the flash counter was removed. In its place was a new counter, what we call the "Knox flag". On devices where the firmware has not been altered, it would read "0x0". Devices that have a custom kernel, recovery, or ROM installed would have this new counter change to "0x1".
Unlike the earlier flash counter, the Knox flag cannot be reset by any software available to us once it has changed to "0x1". This means Triangle Away is useless if Knox is involved.
Strephon Alkhalikoi said:
Some versions of Android available on the S4 had a bootloader that did not utilize the Knox security software. The devices with this bootloader had a counter that would show how often the device's firmware was flashed. This is the flash counter that Triangle Away refers to, and it could be reset with that app. When the new bootloader with Knox was included, the flash counter was removed. In its place was a new counter, what we call the "Knox flag". On devices where the firmware has not been altered, it would read "0x0". Devices that have a custom kernel, recovery, or ROM installed would have this new counter change to "0x1".
Unlike the earlier flash counter, the Knox flag cannot be reset by any software available to us once it has changed to "0x1". This means Triangle Away is useless if Knox is involved.
Click to expand...
Click to collapse
Your explanation is very clear! Thank you, you believe that one day this kind of software exist? There to be a way to with what we do today, right?
The Knox flag is an "E-fuse", located within the CPU. One person on the forum here claimed that his Knox flag was reset, but the reality is that he more than likely had his motherboard replaced. If I were Samsung that's what I would have done. Regardless, the only way to restore the Knox flag to 0x0 would be to somehow rewrite the bootloader so that the flag pointed to a different E-fuse than the one that was tripped. In short, that's not happening.
AntholifeV2 said:
The famous AntaresOne that meets me. It's an honor. Knowing that I have your rom . Thank you, but I do not understand, triangle away is supposed to furnish the counter to 0? But it's not happening, yet s4 is compatible. I read everywhere that it is possible to reset the flag to Knox warranty void 0x0; I do not understand Sorry for my english
Click to expand...
Click to collapse
I didn't explain about flash counter (on the pre-Knox bootloader) since was already clear that with you Triangle Away didn't have success (supposed that you have root otherwise you can't use at all that app, this can only mean that you are on Knox bootloader)
Like the other user said, once we had a bootloader with flash counter that was removed on the Knox one. Until today, nobody had success into resetting it due to the eFuse used inside the SoC (once it is blown, its value can't change anymore).
A impossible (because on top of the SoC there's another IC) operation would be to phisically swap the SoC (with non-blown eFuse) from another motherboard to the one with Knox 0x1
Recompiling the bootloader (removing the fuse check) may be a good option, but Samsung doesn't give bootloader source code.
Triangle away
AntholifeV2 said:
Hello , I would like to put my flash counter to 0 with triangle away, I have an S4 i9505 with CM12, but the problem is that it flash the kernel, but never restarts with options to reset, I have to manually restart the it boot normally, I do not understand ..; HELP
Click to expand...
Click to collapse
I would like to unroot and reset knox counter but the latest version of triangle away app is not woking.
Samsung galaxy s4 gti9500
Cyanogen mod v12.1
Lollipop 5.0.1
Clearly you didn't bother reading the thread. Resetting the Knox flag cannot be done.
Is there any similar app that would do the same as Knox?
Read the thread, and you'll answer your question.
Strephon Alkhalikoi said:
Read the thread, and you'll answer your question.
Click to expand...
Click to collapse
I don't think you quite understood my question... wasn't talking about Triangle Away.. i knwo and understant it is useless as the counter is eFuse wise.
I was asking if there is a replacement for the Knox program - as I am among the ones with burned eFuse.
Thanks
If I misread your question, it's likely because no one has ever asked that question before. In answer however, as far as I know, there is nothing to replace Knox.
Strephon Alkhalikoi said:
Read the thread, and you'll answer your question.
Click to expand...
Click to collapse
Strephon Alkhalikoi said:
If I misread your question, it's likely because no one has ever asked that question before. In answer however, as far as I know, there is nothing to replace Knox.
Click to expand...
Click to collapse
Thank you!
Hy,i recently root my samsung note 3 sn9005 and after that i see KNOX it wasnt work annymore,i can open the aplication,the loading screen apper but then sudenly it just close...anyone know how to fix this?
VaRyOss said:
Hy,i recently root my samsung note 3 sn9005 and after that i see KNOX it wasnt work annymore,i can open the aplication,the loading screen apper but then sudenly it just close...anyone know how to fix this?
Click to expand...
Click to collapse
Reflashing stock rom and without root your device again.
VaRyOss said:
Hy,i recently root my samsung note 3 sn9005 and after that i see KNOX it wasnt work annymore,i can open the aplication,the loading screen apper but then sudenly it just close...anyone know how to fix this?
Click to expand...
Click to collapse
Wow
VaRyOss said:
Hy,i recently root my samsung note 3 sn9005 and after that i see KNOX it wasnt work annymore,i can open the aplication,the loading screen apper but then sudenly it just close...anyone know how to fix this?
Click to expand...
Click to collapse
Deroot your device and flash stock rom..... try and post your feedback here
Joku1981 said:
Reflashing stock rom and without root your device again.
Click to expand...
Click to collapse
more instructions please,how to reflashing ?
VaRyOss said:
more instructions please,how to reflashing ?
Click to expand...
Click to collapse
You can easily search on the q&a section on how to reflash your phone. But if you don't know how to do that, I suggest you read a LOT before you attempt to reflash.
Your original post shows that you have absolutely NO idea about how to do anything to your phone and keep it in a working state, or what any modification implies.
If you lost knox, there is absolutely NO way to get it back. Reflashing to stock will have NO impact on the state of the knox. If the knox flag is triggered, then your knox apps have stoppped functioning and, like I said before, there is ABSOLUTELY NO WAY to reverse that.
I really don't know why the others told you to reflash to stock. I thought it was general knowledge that once you lose knox, it cannot be reversed and you also lose the knox apps.
I know i repeated myself a couple of times, but with your kind of people, repetition is the only way to make oneself understood.
Good luck dude!
VaRyOss said:
Hy,i recently root my samsung note 3 sn9005 and after that i see KNOX it wasnt work annymore,i can open the aplication,the loading screen apper but then sudenly it just close...anyone know how to fix this?
Click to expand...
Click to collapse
To my knowledge every Root related thread mentions, very explicitly, that rooting prevents you from using the KNOX app.
Which makes perfect sense, since KNOX is a security container meant for storing secure data. Once you root, no part of the device is truly safe from tampering.
Once the KNOX flag is 0x1, The KNOX app is disabled and can not be restored. If you want to use KNOX, I'm afraid you'll have to buy a new device. The 0x1 flag can't be reset.
ShadowLea said:
To my knowledge every Root related thread mentions, very explicitly, that rooting prevents you from using the KNOX app.
Which makes perfect sense, since KNOX is a security container meant for storing secure data. Once you root, no part of the device is truly safe from tampering.
Once the KNOX flag is 0x1, The KNOX app is disabled and can not be restored. If you want to use KNOX, I'm afraid you'll have to buy a new device. The 0x1 flag can't be reset.
Click to expand...
Click to collapse
uhmm....k..i understand that. there is another app. similar to KNOX?
i find a app. in magazin play called "Knoxx",work's close anought for me. For people who want to know is the one with a yellow K
I was trying to make sure my KNOX counter wasnt tripped before I ordered the services being provided by imeigurus.com I thought I could just check and return to the home screen. not the case. what do I do please help. I dont know what im doing.
I foolishly did the following:
**YOUR DEVICE CAN NOT HAVE TRIPPED KNOX*** KNOX COUNTER MUST BE 0X000
FIND THAT BY POWERING YOUR DEVICE OFF.
please take it easy on me when you reply. I now realize how STUPID it was for me to do something without knowing what I was doing in the first place.
You seem to have some issue you're not describing at all.
About knox tho all you need to do is boot the phone into bootloader mode, or download a knox checker app from play store.
Honestly unless your flashing roms and kernels or custom recovery to the phone, or if you rooted it in any way except by using the engineering version bootloader, your not going to have tripped knox. If you have tripped knox you cant untrip it. It is an actual fuse in the phone that literally blows. All the knox counter really does is check if the fuse is blown and counts the number of times unauthorised changes were made to the system.
rayne980 said:
I was trying to make sure my KNOX counter wasnt tripped before I ordered the services being provided by imeigurus.com I thought I could just check and return to the home screen. not the case. what do I do please help. I dont know what im doing.
I foolishly did the following:
**YOUR DEVICE CAN NOT HAVE TRIPPED KNOX*** KNOX COUNTER MUST BE 0X000
FIND THAT BY POWERING YOUR DEVICE OFF.
please take it easy on me when you reply. I now realize how STUPID it was for me to do something without knowing what I was doing in the first place.
Click to expand...
Click to collapse
What do you mean by you can't return to the home screen. Have you tried holding the power, home button and volume down button until the phone restarts. And what djdunn said is correct and you haven't fully explained the problem for people to fully help you.
Hello
How to use secure folder with Knox 0x1 ?
It there any way to do this ?
no
locarno said:
Hello
How to use secure folder with Knox 0x1 ?
It there any way to do this ?
Click to expand...
Click to collapse
Once your Knox is tripped you can not use secure folder. There is no fix for a tripped Knox.
Is it possible to mask the 0x1 to make Knox and Samsung Pay work?
WilliamBlake said:
Is it possible to mask the 0x1 to make Knox and Samsung Pay work?
Click to expand...
Click to collapse
Yes MagiskHide masks the 0x1 Value to 0x0 and it might work to use some of the features that check for the Knox counter value.
0. You need to be rooted with the latest version of Magisk.
1. You need to change the name of the Magisk Manager app to a different name using the "Hide Magisk Manager" function.
2. Turn on MagiskHide in settings and check Samsung pay and Secure folder (And all the apps that help them run like Samsung pay framework etc.) in the MagiskHide tab.
3. Delete any files in your internal storage that have Magisk in the name.
4. (Optional) If you dont want to be rooted you can also disable Superuser access within the Magisk Manager App.
Edit: You may also have to enable "Magisk Core Only Mode" so that no modules or anything extra is loaded that Samsung Pay could possibly detect.
This is not 100% guarenteed to work but it is worth a try as it is close as you are going to get to knox 0x0.
JJcoder said:
Yes MagiskHide masks the 0x1 Value to 0x0 and it might work to use some of the features that check for the Knox counter value.
0. You need to be rooted with the latest version of Magisk.
1. You need to change the name of the Magisk Manager app to a different name using the "Hide Magisk Manager" function.
2. Turn on MagiskHide in settings and check Samsung pay and Secure folder (And all the apps that help them run like Samsung pay framework etc.) in the MagiskHide tab.
3. Delete any files in your internal storage that have Magisk in the name.
4. (Optional) If you dont want to be rooted you can also disable Superuser access within the Magisk Manager App.
This is not 100% guarenteed to work but it is worth a try as it is close as you are going to get to knox 0x0.
Click to expand...
Click to collapse
Once Knox is tripped it triggers an Efuse, that can only be fixed by a motherboard replacement. Samsung Pay will never work once Knox has been tripped.
stonedpsycho said:
Once Knox is tripped it triggers an Efuse, that can only be fixed by a motherboard replacement. Samsung Pay will never work once Knox has been tripped.
Click to expand...
Click to collapse
I know, but MagiskHide masks the value to 0x0.
JJcoder said:
I know, but MagiskHide masks the value to 0x0
on boot.
Click to expand...
Click to collapse
That will not make Samsung Pay work.
stonedpsycho said:
That will not make Samsung Pay work.
Click to expand...
Click to collapse
Are you sure? Maybe if you just enable MagiskHide it wont work; but if you follow all of my steps how can Samsung pay detect Knox 0x1 and root? Maybe you have to reinstall Samsung Pay? I am still on the 7 day jail (RMM state lock) on my S8 so I can't experiment with it right now.
JJcoder said:
Are you sure? Maybe if you just enable MagiskHide it wont work; but if you follow all of my steps how can Samsung pay detect Knox 0x1 and root? Maybe you have to reinstall Samsung Pay? I am still on the 7 day jail (RMM state lock) on my S8 so I can't experiment with it right now.
Click to expand...
Click to collapse
It will not fix the Efuse though.
stonedpsycho said:
It will not fix the Efuse though.
Click to expand...
Click to collapse
You are right! I'm not trying to revert the eFUSE that
is not possible. I am trying to mask the value so that Samsung Pay and other apps will think that Knox is 0x0 and that the phone is not rooted. My question is
how can Samsung Pay detect Knox 0x1 even when following all of the steps I listed above while all of the Knox Status apps on the Play Store say 0x0 while simply enabling MagiskHide and checking the app in the MagiskHide tab?
JJcoder said:
You are right! I'm not trying to revert the eFUSE that
is not possible. I am trying to mask the value so that Samsung Pay and other apps will think that Knox is 0x0 and that the phone is not rooted. My question is
how can Samsung Pay detect Knox 0x1 even when following all of the steps I listed above while all of the Knox Status apps on the Play Store say 0x0 while simply enabling MagiskHide and checking the app in the MagiskHide tab?
Click to expand...
Click to collapse
I am no expert and don't understand how it all works but if there was a way or workaround for Samsung Pay to work I think the talented Devs here on XDA would have found a solution by now, like one did for Secure Folder.
stonedpsycho said:
I am no expert and don't understand how it all works but if there was a way or workaround for Samsung Pay to work I think the talented Devs here on XDA would have found a solution by now, like one did for Secure Folder.
Click to expand...
Click to collapse
Did anyone actually try following the steps I listed? Maybe you also have to enable Magisk Core only mode so no modules or anything extra is loaded that Samsung Pay could possibly detect? If that doesn't work then what about reinstalling Samsung Pay and it's framework after following these steps?
As I said I wish I could try myself but I am still in RMM state: Prenormal
JJcoder said:
Did anyone actually try following the steps I listed? Maybe you also have to enable Magisk Core only mode so no modules or anything extra is loaded that Samsung Pay could possibly detect? If that doesn't work then what about reinstalling Samsung Pay and it's framework after following these steps?
As I said I wish I could try myself but I am still in RMM state: Prenormal
Click to expand...
Click to collapse
I have never tried that but I highly doubt it will work still.
Jail time! You tried the trick of moving the clock forward 7+ days?
stonedpsycho said:
I have never tried that but I highly doubt it will work still.
Jail time! You tried the trick of moving the clock forward 7+ days?
Click to expand...
Click to collapse
Yes, but it didn't work for me (because I think it only works on Oreo and im on Pie)
So I just have to wait 7 days.
JJcoder said:
Yes, but it didn't work for me (because I think it only works on Oreo and im on Pie)
So I just have to wait 7 days.
Click to expand...
Click to collapse
I know it can be hit and miss and can take a few attempts, probably worth another try. I only faced jail time on Oreo, but I use a Note 8.
If you do get Spay to work though, please let us know as so many people will be very happy with you :fingers-crossed:
stonedpsycho said:
I know it can be hit and miss and can take a few attempts, probably worth another try. I only faced jail time on Oreo, but I use a Note 8.
If you do get Spay to work though, please let us know as so many people will be very happy with you :fingers-crossed:
Click to expand...
Click to collapse
Well im already on my third day and if the date trick doesn't work then i'll have to start all over again.
As yes I will let everyone know if I can get Samsung Pay to work