After updating to Android Nougat official BTU Samsung pass won't work.
Everytime when I enter my login datas (yes they're correct) it shows that Samsung Pass is currently not available and that I should try it a little later.
Does anyone face the same problem or know how to fix it?
ON ROOTED DEVICE!
Edit: Noticed now that you only have to delete samsung pass from system/priv-app to get fingerprint login in samsung browser to work.
Same here
Same here. It is not possible anymore to use your fingerprint for any service. Samsung pass is never available...
Nougat 7.0 BTU (Installed with full wipes)
S7Edge
PS: This is the first problem I found in Nougat.
Same for me, I flashed from LUX to BTU.
Works perfect here
Pet1981 said:
After updating to Android Nougat official BTU Samsung pass won't work.
Everytime when I enter my login datas (yes they're correct) it shows that Samsung Pass is currently not available and that I should try it a little later.
Does anyone face the same problem or know how to fix it?
Click to expand...
Click to collapse
I had the same issue. But after trying out a few times it worked
Tried already 30-40 times but won't work else...
Works perfectly fine here too, in fact, ive got no issues with Android N on this phone at all so far, they even seem to of fixed the over sensitive screen.
Have you ever rooted or flashed a custom recover or rom ? is your Knox counter still at 0x0, if no then this will explain why its not working as it uses Knox.
Seanie280672 said:
Works perfectly fine here too, in fact, ive got no issues with Android N on this phone at all so far, they even seem to of fixed the over sensitive screen.
Have you ever rooted or flashed a custom recover or rom ? is your Knox counter still at 0x0, if no then this will explain why its not working as it uses Knox.
Click to expand...
Click to collapse
Mhm...maybe that's a hint. I didn't root...also my knox-counter is 0...but I disabled knox with package disabler pro.
Seanie280672 said:
Works perfectly fine here too, in fact, ive got no issues with Android N on this phone at all so far, they even seem to of fixed the over sensitive screen.
Have you ever rooted or flashed a custom recover or rom ? is your Knox counter still at 0x0, if no then this will explain why its not working as it uses Knox.
Click to expand...
Click to collapse
Works fine even if Knox is tripped.
I enabled all disabled apps...rebooted...but doesn't work else.
Also deleted Samsung Pass Data...doesn't help...
Strange.
Will try now a factory reset.
Nothing...
I have tried everything... still not working.
Clean phone. No root. Stock.
Also tried to reflash but still not working.
Knox Is 0X0 .
Anybody has an Idea?
bentrama said:
Also tried to reflash but still not working.
Knox Is 0X0 .
Anybody has an Idea?
Click to expand...
Click to collapse
Same here...even factory reset didn't help.
If you are rooted or if your Device Root key (DRK) is corrupt or missing, Samsung Pass will not work
All works perfect for me
Flashed ITV to BTU
I'm also downloading now the BTU flashing over ITV ....we'll see if Samsung pass will work
Everything works fine it's just Samsung pass. Even knox world fine.
No Root, Knox fine, Samsung Pass not working.
It can be because I'm not in a supported country ? I'm in Belgium and there's no official nougat here.
I flashed BTU. No root but Knox 0x1 and Samsung Pass works fine.
Related
Hi,
After flashing the MJ6 ROM with the Universal root de la vega method (I have the old bootloader from MJ1) and flash the MJ4 modem, the camera and and wifi were not working, I tried to downgrade the modem to MJ2 with Odin to give a try.
However now I'm facing several boot loops (on first notification model screen) and when the Note succeed in corectly booting, I have an FC from system process, and some others applications.
I tried to check the phone parameters and saw that baseband was "unknown", but didn't succeed to see the screen where the IMEI is displayed because the phone is rebooting automaticaly when I try to access to this screen.
The phone is very instable : sometimes I'm not able to access to parameters with the tactil button.
In all cases the phone is auto rebooting after several minutes.
I tried several things withoot result :
- Wipe cache + factory reset
- Flash several modems
- Flash MI7 stock ROM with Odin
> no change
Actually I have :
- baseband unknown
- boot looping
- no wifi
- no sound
- no root
- acces to download mode and stock recovery is OK.
As someone have some cloues to help me?
Crystal7_Magic said:
Hi,
After flashing the MJ6 ROM with the Universal root de la vega method (I have the old bootloader from MJ1) and flash the MJ4 modem, the camera and and wifi were not working, I tried to downgrade the modem to MJ2 with Odin to give a try.
However now I'm facing several boot loops (on first notification model screen) and when the Note succeed in corectly booting, I have an FC from system process, and some others applications.
I tried to check the phone parameters and saw that baseband was "unknown", but didn't succeed to see the screen where the IMEI is displayed because the phone is rebooting automaticaly when I try to access to this screen.
The phone is very instable : sometimes I'm not able to access to parameters with the tactil button.
In all cases the phone is auto rebooting after several minutes.
I tried several things withoot result :
- Wipe cache + factory reset
- Flash several modems
- Flash MI7 stock ROM with Odin
> no change
Actually I have :
- baseband unknown
- boot looping
- no wifi
- no sound
- no root
- acces to download mode and stock recovery is OK.
As someone have some cloues to help me?
Click to expand...
Click to collapse
I'm pretty sure your Knox warranty void has been tripped... Flash the MJ6 stock firmware. You have the new bootloader now anyway, that's why you are in the bootloop.. I had the same problem and when I checked and found warranty void triggered I figured can't hurt.
Flashed stock MJ6 firmware. Baseband comes back, all thos little things not working get fixed. I then flashed CF-root as the warranty void was 0x1...
It seems if you flash the Modem.bin file you are stuck, you need to flash the MJ6 firmware to fix....
ultramag69 said:
I'm pretty sure your Knox warranty void has been tripped... Flash the MJ6 stock firmware. You have the new bootloader now anyway, that's why you are in the bootloop.. I had the same problem and when I checked and found warranty void triggered I figured can't hurt.
Flashed stock MJ6 firmware. Baseband comes back, all thos little things not working get fixed. I then flashed CF-root as the warranty void was 0x1...
It seems if you flash the Modem.bin file you are stuck, you need to flash the MJ6 firmware to fix....
Click to expand...
Click to collapse
I had the same pb ..... and flash MJ6 full and now it's OK .... so I rooted ... Knox 1 ....but everything OK I am happy
Ok, but normaly I always have the old bootloader because I do not have flash the MJ6 stock > It has been modified with universal root de la vega before flashing with Odin, and my flag is still on 0x0.
> So normaly the MJ6 I flashed should not contain the new bootloader.
It will be troublesome for me if flashing a stock MJ6 is needeed as I do not want to trigger the Knox flag.
I always have the solution to return my Note to my seller for refund, so I'm seeking for a way which do not trigger Knox
ultramag69 said:
I'm pretty sure your Knox warranty void has been tripped... Flash the MJ6 stock firmware. You have the new bootloader now anyway, that's why you are in the bootloop.. I had the same problem and when I checked and found warranty void triggered I figured can't hurt.
Flashed stock MJ6 firmware. Baseband comes back, all thos little things not working get fixed. I then flashed CF-root as the warranty void was 0x1...
It seems if you flash the Modem.bin file you are stuck, you need to flash the MJ6 firmware to fix....
Click to expand...
Click to collapse
LIPA said:
I had the same pb ..... and flash MJ6 full and now it's OK .... so I rooted ... Knox 1 ....but everything OK I am happy
Click to expand...
Click to collapse
Finaly I have decided to flash the MJ6 stock ROM and everything go ok.
I still have my knox 0x0 but will trigger to 0x1 if I try to root by now : hard decision.
Thanks for your help you two
Crystal7_Magic said:
Finaly I have decided to flash the MJ6 stock ROM and everything go ok.
I still have my knox 0x0 but will trigger to 0x1 if I try to root by now : hard decision.
Thanks for your help you two
Click to expand...
Click to collapse
Mate, I modified with root de la vega myself but it seems the new bootloader got through....
Where can I find the MJ6 firmware
ultramag69 said:
Mate, I modified with root de la vega myself but it seems the new bootloader got through....
Click to expand...
Click to collapse
It will be strange, because I succedeed to root the Note withoot triggering Knox
You have to be sure that you do not have take update from OTA or official stock ROM when you was on ROM before MJ3 (if you take stock MJ3 bootloader is altered)
yazzie said:
Where can I find the MJ6 firmware
Click to expand...
Click to collapse
You can find it on Sammobile website (create an account is needed to access to download section)
http://www.sammobile.com/firmwares/1/?model=SM-N9005&pcode=0#firmware
After flashing the MJ6 stock firmware to recover my baseband, I have juste noticed that wifi is not properly working.
> Wifi is blocked on activation
> Sometime the Note succeed to activate wifi and show me networks which are available, however when I'm trying to connect to one of them I got a freeze then wifi go back to activating statuts.
Any explanation?
SM-N900W8 Boot Loop
Has anyone else resolved this issue. Phone was rooted with "CF-Auto-Root-hltecan-hlteub-smn900w8" and used TWRP 2.6.3.0. Upon doing a restore with TWRP, the phone is now in this crazy loop. Phone boots but always fails prior to seeing home screen. Tried going to SamMobile and restoring original Rogers firmware with no resolution.
Any help is most appreciated.
ultramag69 said:
Mate, I modified with root de la vega myself but it seems the new bootloader got through....
Click to expand...
Click to collapse
thanks a million. i had the same problem, following my ordeal with samsung on region sim lock.
i tried the mj6, it seemed too work, for now.
will root it and see how that goes. thanks once again
Ahmads001 said:
thanks a million. i had the same problem, following my ordeal with samsung on region sim lock.
i tried the mj6, it seemed too work, for now.
will root it and see how that goes. thanks once again
Click to expand...
Click to collapse
If you flashed the stock MJ6 then you have the new anti-root bootloader. ANY attempt to root will end in Warranty void being triggered...
Unfortunately this is a problem that hasn't been fixed yet. Just a heads up to let you know you will probably trigger the warranty void.
Then again Designgears is back developing RDLV again so it might be updated soon... :fingers-crossed:
ultramag69 said:
If you flashed the stock MJ6 then you have the new anti-root bootloader. ANY attempt to root will end in Warranty void being triggered...
Unfortunately this is a problem that hasn't been fixed yet. Just a heads up to let you know you will probably trigger the warranty void.
Then again Designgears is back developing RDLV again so it might be updated soon... :fingers-crossed:
Click to expand...
Click to collapse
thanks again for usual insight.
unfortunately, the bootloop problem was back after a restart yesterday. took several loops (about 30 mins) before it started up. i had to reflash with the latest stock N9005XXUDMJ7_N9005OJVDMJ4_KSA. now im scared to restart the phone for any reason, since i cant tell if it will entre bootloop again - it gets worse with every reset.
Since the knox already tripped 0x1, i still desire to root it ASAP.
So,
1. how do i get rid of this bootloop menace, PERMANENTLY
2. how do i safely root the phone (SM-N9005)
will appreciate a lot of help.
Ahmads001 said:
thanks again for usual insight.
unfortunately, the bootloop problem was back after a restart yesterday. took several loops (about 30 mins) before it started up. i had to reflash with the latest stock N9005XXUDMJ7_N9005OJVDMJ4_KSA. now im scared to restart the phone for any reason, since i cant tell if it will entre bootloop again - it gets worse with every reset.
Since the knox already tripped 0x1, i still desire to root it ASAP.
So,
1. how do i get rid of this bootloop menace, PERMANENTLY
2. how do i safely root the phone (SM-N9005)
will appreciate a lot of help.
Click to expand...
Click to collapse
As Knox is tripped use cf-autoroot found in the original android developement section of the Note 3 forum. This will give you root...
I would also try a different region rom, I used MJ7 from the UK. It didn't cause any issues.
I had bootloops and found going to wifi, clicking on menu button, advanced.& unticking "Scanning always available" seemed to fix my bootloops but this was for my MJ1 firmware.
Otherwise can't really help anymore tonight. Gotta go to work tomorrow and its 2am here in Oz....
ultramag69 said:
As Knox is tripped use cf-autoroot found in the original android developement section of the Note 3 forum. This will give you root...
I would also try a different region rom, I used MJ7 from the UK. It didn't cause any issues.
I had bootloops and found going to wifi, clicking on menu button, advanced.& unticking "Scanning always available" seemed to fix my bootloops but this was for my MJ1 firmware.
Otherwise can't really help anymore tonight. Gotta go to work tomorrow and its 2am here in Oz....
Click to expand...
Click to collapse
thanks, and good morning.
will be back later (sorry some of us -docs- dont actually have the 'day/night' thing).
will try the wifi thing, and see what happens.
once again, thanks
Same problem here :
- Supposed to be MK2 rom (N9005XXUDMK2) and was rooted
- Recovery and download mode are OK
- Flashed several time with ODIN, including modem.bin from the same archive
- Obviously Knox is 0x01
But phone is still unuseable ....Boots up, pass the intial setting. Then error message about system not responding and reboot ...
Any help would be appreciated
Follow this it'll fix it http://forum.xda-developers.com/showthread.php?p=47014662
Sent from my SM-N9005 using XDA Premium 4 mobile app
You saved my day !!! Thanks
Crystal7_Magic said:
After flashing the MJ6 stock firmware to recover my baseband, I have juste noticed that wifi is not properly working.
> Wifi is blocked on activation
> Sometime the Note succeed to activate wifi and show me networks which are available, however when I'm trying to connect to one of them I got a freeze then wifi go back to activating statuts.
Any explanation?
Click to expand...
Click to collapse
I have the same problem
You solved your problem?
Thanks
sbdz said:
I have the same problem
You solved your problem?
Thanks
Click to expand...
Click to collapse
Hi,
Unfortunately for you no, I made a swap with a brandnew one with the seller.
Got my S7 yesterday, played around with root, and decided to go with a stock experience for the time being so I can use Samsung Pay and MST (blasphemous, I know). I used ODIN to restore back to stock, verified KNOX counter wasn't tripped, and went on setting everything up.
I installed Samsung Pay and launched, only to run into the access denied message you would see if you were attempting to open it with a rooted device. Any thoughts as to what could be happening?
Song0330 said:
Got my S7 yesterday, played around with root, and decided to go with a stock experience for the time being so I can use Samsung Pay and MST (blasphemous, I know). I used ODIN to restore back to stock, verified KNOX counter wasn't tripped, and went on setting everything up.
I installed Samsung Pay and launched, only to run into the access denied message you would see if you were attempting to open it with a rooted device. Any thoughts as to what could be happening?
Click to expand...
Click to collapse
I would make sure you followed the return to stock instructions in psouza4 thread (http://forum.xda-developers.com/ver...-to-notes-root-install-xposed-unroot-t3411039). I flashed through odin yestererday and took the pf2 update that was available when I was done. I am able to install and access Samsung pay. What all did you flash in ODIN?
thefirst__noel said:
I would make sure you followed the return to stock instructions in psouza4 thread (http://forum.xda-developers.com/ver...-to-notes-root-install-xposed-unroot-t3411039). I flashed through odin yestererday and took the pf2 update that was available when I was done. I am able to install and access Samsung pay. What all did you flash in ODIN?
Click to expand...
Click to collapse
Resolved! Actually, it was my strict adherence to the instructions that led to the issue - the instructions only tell you to flash AP, CP, and CSC back down to PE1. Which was fine and dandy, but my BL remained at PF2, which is the reason why I had issues loading Samsung Pay. I was afraid that I had either tripped the mythical physical e-fuse somehow, or my phone was blacklisted from Samsung Pay servers - fortunately this was not the case! Once I updated everything back to PF2, Samsung Pay was able to load.
Help Galaxy s7
Hello friends, I made the root process in my S7 GALAXY, but the direct method cf self root, now my knox is 0x1. Is this with your method, I can return to the original state knox 0x0 and able to use the Samsung pay ???
[email protected] said:
Hello friends, I made the root process in my S7 GALAXY, but the direct method cf self root, now my knox is 0x1. Is this with your method, I can return to the original state knox 0x0 and able to use the Samsung pay ???
Click to expand...
Click to collapse
Sorry but there's no method at this time to reset Knox back to 0x0. The method of root that was posted here wouldn't trip Knox which is why when flashing back to stock they are able to use Samsung Pay again.
how to trip that knox again? and how to check knox state? I had installed stock samsung s7 edge India ROM latest but now smart tutor apps is gone (that i intalled from playstore) and samsung pay is not working
Hi!
I'm trying to go back to stock to try knox features like secure folder. I have restored my device (Spain unbranded) with SmartSwitch and flashing firmware through Odin.
My problem is that Knox and Secure folder says that it can not work because I have installed unauthorized software. SafetyNet passes, on download mode, I see all official, and Apps (like banking apps) works fine without detecting root.
I have warranty void bit = 1. This means that, even flashing again stock firmware, I will never be able to use Knox? I'm worried about using root cloacks methods because of something stops working (for example due an update) I will unable to access to secure folder.
Thanks a lot in advance!
runtime_Err0r said:
Hi!
I'm trying to go back to stock to try knox features like secure folder. I have restored my device (Spain unbranded) with SmartSwitch and flashing firmware through Odin.
My problem is that Knox and Secure folder says that it can not work because I have installed unauthorized software. SafetyNet passes, on download mode, I see all official, and Apps (like banking apps) works fine without detecting root.
I have warranty void bit = 1. This means that, even flashing again stock firmware, I will never be able to use Knox? I'm worried about using root cloacks methods because of something stops working (for example due an update) I will unable to access to secure folder.
Thanks a lot in advance!
Click to expand...
Click to collapse
As your knox is tripped already i.e. showing 0×1 so you will never be able to use knox related security features as well as samaung pay on your phone..When knox is tripped once while in rooting or trying any unauthorised software installation, it will never been reset to initial state either by trying to install stock firmware again..
DroidHackeR said:
As your knox is tripped already i.e. showing 0×1 so you will never be able to use knox related security features as well as samaung pay on your phone..When knox is tripped once while in rooting or trying any unauthorised software installation, it will never been reset to initial state either by trying to install stock firmware again..
Click to expand...
Click to collapse
Ok thanks a lot for the info!
runtime_Err0r said:
Ok thanks a lot for the info!
Click to expand...
Click to collapse
https://forum.xda-developers.com/s7-edge/how-to/guide-secure-folder-samsung-knox-s-t3560079
^^That thread has a tutorial on how to get knox features working if your knox was tripped however I don't think it will as secure as it would be if used the knox features without knox being tripped.
runtime_Err0r said:
Ok thanks a lot for the info!
Click to expand...
Click to collapse
I can recommend you flashing ambasadii's ROM. I'm currently using it with the latest SuperStock Kernel and have secure folder fully working. You'll have to download the full 10.1 ROM and the 10.2 OTA which is about 500mb
I Haven't rooted my phone yet but it keeps telling me this when I open android pay, when I first got my phone I set my up my card but now it saying that phone is either rooted or bootloader unlocked which isn't the case.
On Vodafone UK, before this I used my OP3 with Magisk with Android Pay but I haven't used that since I've got my s8 so I'm not sure what the issue could be.
Any insight to this?
Besides the usual factory reset.
same here EE UK S8 not rooted (yet) but comes up with same error message. It worked fine on my rooted and hidden with magisk S6
edit - oh and factory reset doesn't work as I already tried that. I thought it might have had something to do with bringing over magisk app from my google backup but I specifically didnt install that the 2nd time around. Knox hasn't been tripped so its not that
I'm having the same issue on a Galaxy S8 via Tmobile. I've never rooted it, have no clue if the bootloader is unlocked and I'm stock since I reset the phone the first time I got the error. Still getting the error and Android pay help chat was not useful.
Same issue here, on Voda UK. I used Package Disabler pro and thinking I might have disabled something I need.
So since I had OEM unlock enabled after disabling it, it passes and safetynet now.
I had no problems adding cards, but a few days later when I wanted to add more cards, I get the error. I can't remember what I did in between that would've caused this, but definitely not rooting! I turned developer option to off and still get the error.
My S7 is rooted and TWRPed and have no problems adding cards!!!!???
Very weird. Working just fine on my rooted s8+ with magisk.
I'm on T-Mobile with a S8 and Android Pay connected to my PayPal is getting card read error everywhere I try to use it.
Safety net says everything is ok too. Not sure what's going on. I have the newest update and not rooted.
Sent from my SM-G950U using Tapatalk
I installed different Samsung Pay Framework apk and now I want to revert back and downgrade to another version to make Spay work.. when I click uninstall updates it wont let me. (Gives message that App is needed by system administrator.. when I open sys admin nothing there. hidden app)
Any ideas or suggestions on how to downgrade Samsung Pay Framework?
Thank you in advance,
Joe
xeathpk said:
Very weird. Working just fine on my rooted s8+ with magisk.
Click to expand...
Click to collapse
Hi Can you let me know how you managed to root with Magisk and get Android pay etc to work?
My phone:
Model: SM-G955F
SW: G955FXXU1AQF7
I tried rooted and couldn't get it working, and now recovered to official ROM and still can't get it to work?!?
Dont you people know anythin?
All EU(exynos) S8 and other galaxies come with unlocked bootloaders. Thats causing the problem
Lock it
Hi all,
I already posted a question in the Official stock upgrade but it got lost in the other comments, so I'm trying my luck again.
I had an italian branded SM-G950F (OMN), I wanted to remove all the Vodafone stuff, so I installed a MULTI-CSC as per the official stock firmware upgrade thread, when I did it I had my Australian sim card in and I got a weird UK CSC (the multi CSC didn't have australia in it), after installing everything I noticed that Android Pay didn't work, so I did a factory reset with my italian sim card in and still Android Pay was complaining that my firmware was modified or rooted.
I decided to use an australian specific firmware so I downloaded an XSA firmware and did the procedure again.
At this stage Secure Folder and Samsung Pay work (the phone is NOT rooted, this update has been the only "mod" I have done) but Android Pay is still saying that my rom may be modified or rooted so it doesn't open.
It is pretty important for me because my back supports android pay but not samsung pay
The phone is not rooted, if I reboot the phone in download mode the warranty void bit is 0 (which is good).
If I use Root Checker Pro, under safety net tab, I get CTS profile match as FAIL, I was thinking this could cause Android Pay to fail.
any idea?
start to uninstall suspicious apps, then restart . worked with my un-rooted S8. OEM unlock: OFF
degsyh said:
same here EE UK S8 not rooted (yet) but comes up with same error message. It worked fine on my rooted and hidden with magisk S6
edit - oh and factory reset doesn't work as I already tried that. I thought it might have had something to do with bringing over magisk app from my google backup but I specifically didnt install that the 2nd time around. Knox hasn't been tripped so its not that
Click to expand...
Click to collapse
Does rooting in UK\Europe void our warranty?
mariuscrist said:
start to uninstall suspicious apps, then restart . worked with my un-rooted S8. OEM unlock: OFF
Click to expand...
Click to collapse
Hi mariuscrist,
I'm not sure what app can be suspicious, I have reinstalled the apps I had before the firmware update and I could use android pay then. I'll see what it can be, probably it could be worth to do a factory reset and test android pay before anything else?
need urgent help really.
my phone has been rooted and has twrp installed for months now with no issues, all of a sudden my phone rebooted to the samsung logo screen with the mentioned error message. i have no idea how and why this error has occured but my phone wont boot to system. i really dont want flash stock firmware as i havent backed things up, is there a way to fix this issue with out doing a full wipe?
you might have accidentally disable oem unlock. so phone is bricked , and you need to flash stock firmware with odin , no other choices . and as you know knox counter will stay 0x1 , root or no root, once you break knox its permanent as knox is hardware, once you root it break an electronic fuse so once you flash stock firmware I really suggest you to install custom rom and twrp again as many things will be blocked if you stay on stock firmware as your device will stay marked as " rooted "
robhug said:
you might have accidentally disable oem unlock. so phone is bricked , and you need to flash stock firmware with odin , no other choices . and as you know knox counter will stay 0x1 , root or no root, once you break knox its permanent as knox is hardware, once you root it break an electronic fuse so once you flash stock firmware I really suggest you to install custom rom and twrp again as many things will be blocked if you stay on stock firmware as your device will stay marked as " rooted "
Click to expand...
Click to collapse
Yeah I had to do firmware install in the end. It's just crazy though. I very rarely go into dev options, I had noto kernel installed and everything on stock aqh3, rooted with magisk and everything worked great, so annoying as this happened at 3am and I have slow internet connection and took me 2 hours to download the 3.5gb firmware file. Urgh o was on the verge of installing a custom rom too, ah well good job I had a lot of stuff saved in Samsung cloud.
sofir786 said:
Yeah I had to do firmware install in the end. It's just crazy though. I very rarely go into dev options, I had noto kernel installed and everything on stock aqh3, rooted with magisk and everything worked great, so annoying as this happened at 3am and I have slow internet connection and took me 2 hours to download the 3.5gb firmware file. Urgh o was on the verge of installing a custom rom too, ah well good job I had a lot of stuff saved in Samsung cloud.
Click to expand...
Click to collapse
yes hopefully cloud is our new god ^^ yes its annoying I agree but its also a great feeling to begin with a clean phone like new after a reset , and I have also a crappy download speed so yes its a pain to download 4gb , and even better when its corrupted and need to download agin good luck with your device
Hey guys I need help.
My phone got bricked as you said (I accidentally turned off OEM unlock on my rooted phone) so I tried to flash stock firmware, but odin fails and on my phone it says (sw rev. check fail. device:3 binary:2). Plz help!
My phone: S8+
FIRMWARE: CRF7
FRP LOCK: ON
OEM LOCK: ON
Just had the very same problem meself ?
Thank god for Odin and https://updato.com/
Bt like previous posters says its like havin a new phone apart from samsung pay not working
Can someone help??
I got the "FRP lock" on my Samsung S8 (Exynos) and tried to flash Stock Oreo but Odin fails and the device shows "KERNEL REV. CHECK FAIL. DEVICE:3 BINARY:2".
This stock Samsung Rom worked earlier today so it should be the right Rom for my phone.
Also tried to flash TWRP recovery via AP in Odin which failed with "RFP lock" message showing on the device..
I tried to add a snapshot here but couldn't.
Anyone please, I'm helpless..
nattyniz said:
Can someone help??
I got the "FRP lock" on my Samsung S8 (Exynos) and tried to flash Stock Oreo but Odin fails and the device shows "KERNEL REV. CHECK FAIL. DEVICE:3 BINARY:2".
This stock Samsung Rom worked earlier today so it should be the right Rom for my phone.
Also tried to flash TWRP recovery via AP in Odin which failed with "RFP lock" message showing on the device..
I tried to add a snapshot here but couldn't.
Anyone please, I'm helpless..
Click to expand...
Click to collapse
Your issue is trying to flash older firmware than what is on your phone. You will need to download firmware with bootloader ver. 3 or higher ( bl ver no. is 5th number from right of firmware name )
Flashing twrp failed because of locked bootloader.
spawnlives said:
Your issue is trying to flash older firmware than what is on your phone. You will need to download firmware with bootloader ver. 3 or higher ( bl ver no. is 5th number from right of firmware name )
Flashing twrp failed because of locked bootloader.
Click to expand...
Click to collapse
That helped. Flashing the right version worked just fine.
Thanks!!
FRP lock
Hi people,
I got the "FRP lock" on my Samsung S8 SM-G950F(Exynos) and tried to flash Stock Oreo but when I press start Odin say PASS but recovery won't start.
please help
i flashed my S8 SM-G9500 variant however the phone has been locked and it is saying that i need to see the samsung service provider for the device has been locked. how can i solve this problem
Mark Nyombi said:
i flashed my S8 SM-G9500 variant however the phone has been locked and it is saying that i need to see the samsung service provider for the device has been locked. how can i solve this problem
Click to expand...
Click to collapse
can you get a pic of the screen youre talking about?
Hello guys i rooted my S8+ G-955F and i turned off usb debugging and ome lock
And i have android 9 installed on my device, i tried all the way but for nothink , any help please