Related
Hello, I have a soft bricked (hopefully thats the case) Samsung Galaxy S6 SM-G920F xme region (Malaysia) with android 6.0.1 latest stock rom.
It started when my device suddenly restarted and got stuck at the samsung logo (first screen).
I am able to boot it into Download Mode, tried reflashing with a fresh stock rom MM 6.0.1 with odin, flashing proccess was completed with no fail but it still stuck at the same screen.
I can't even boot into recovery mode so i can't wipe the cache partition, i noticed the Reactivaction Lock status is ON, i suspect that might be the culprit?
The things i tried so far:
1- Reflash with the latest stock firmware. Ticking the NAND erase all and repartition it with pit file also didn't work.
2- Samsung Smart Switch and Kies3. Flash completed but no effect.
3- Flashing any recovery files returns with "Custom binary(recovery) Blocked by R/L".
4- Sent it to my nearest Samsung service centre, they did try to repair it but only to be told that my S6 need a new motherboard the next day, which is out of my budget limit. But i am still hoping to find some other way to fix it, i believe this is just a "soft-brick" not a hard brick device.
Ideas guys? thanks.
Try to re flash stock odin firmware with erase all ticked ok ,
Good luck ,,
thereassaad said:
Try to re flash stock odin firmware with erase all ticked ok ,
Good luck ,,
Click to expand...
Click to collapse
Already tried that, still no luck..
mrkage said:
Hello, I have a soft bricked (hopefully thats the case) Samsung Galaxy S6 SM-G920F xme region (Malaysia) with android 6.0.1 latest stock rom.
It started when my device suddenly restarted and got stuck at the samsung logo (first screen).
I am able to boot it into Download Mode, tried reflashing with a fresh stock rom MM 6.0.1 with odin, flashing proccess was completed with no fail but it still stuck at the same screen.
I can't even boot into recovery mode so i can't wipe the cache partition, i noticed the Reactivaction Lock status is ON, i suspect that might be the culprit?
Ideas guys? thanks.
Click to expand...
Click to collapse
Try Samsung Smart Switch, it has some recovery features that can automate the process for you.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
Droidriven said:
Try Samsung Smart Switch, it has some recovery features that can automate the process for you.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
Click to expand...
Click to collapse
Thank you for taking a look at my problem here, i forgot to mention that i did try Samsung Smart Switch and Kies3, both managed to succesfully flashed the stock firmware, it reboots my device and still stuck at the same first screen.
mrkage said:
Thank you for taking a look at my problem here, i forgot to mention that i did try Samsung Smart Switch and Kies3, both managed to succesfully flashed the stock firmware, it reboots my device and still stuck at the same first screen.
Click to expand...
Click to collapse
I believe it is doing that because you have a locked bootloader. Normally that shouldn't be a problem unless you're trying to flash a firmware that is older than what you had.
What stock firmware version/build number did your device have? What firmware version/build number is what you are flashing? If what you're flashing is older it might be downgrading your bootloader, bootloader can't be downgraded on most locked bootloader Samsung devices these days.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
Droidriven said:
I believe it is doing that because you have a locked bootloader. Normally that shouldn't be a problem unless you're trying to flash a firmware that is older than what you had.
What stock firmware version/build number did your device have? What firmware version/build number is what you are flashing? If what you're flashing is older it might be downgrading your bootloader, bootloader can't be downgraded on most locked bootloader Samsung devices these days.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
Click to expand...
Click to collapse
Don't remember the build number, but it was a 6.0.1 firmware, i flashed it with the same stock firmware version.. but maybe the build number didn't match.
I read somewhere about the engineering bootloader, i know it is not so easy or even possible at the moment to find one for my current firmware version, but let's say if i have it, will it be possible for me to use it to remove the RL on my device?
mrkage said:
Don't remember the build number, but it was a 6.0.1 firmware, i flashed it with the same stock firmware version.. but maybe the build number didn't match.
I read somewhere about the engineering bootloader, i know it is not so easy or even possible at the moment to find one for my current firmware version, but let's say if i have it, will it be possible for me to use it to remove the RL on my device?
Click to expand...
Click to collapse
Did you flash a firmware from a different g920 series device? Or did you flash the firmware for your specific model number and your and carrier?
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
Droidriven said:
Did you flash a firmware from a different g920 series device? Or did you flash the firmware for your specific model number and your and carrier?
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
Click to expand...
Click to collapse
Only did for my specific model number and carrier
mrkage said:
Only did for my specific model number and carrier
Click to expand...
Click to collapse
Let me backtrack. Do you know if USB debugging is on?
Did you flash TWRP with a locked bootloader before this happened? Is that what caused the issue?
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
Droidriven said:
Let me backtrack. Do you know if USB debugging is on?
Did you flash TWRP with a locked bootloader before this happened? Is that what caused the issue?
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
Click to expand...
Click to collapse
USB debugging and Developer Mode was never turned on that device.
Negative, i did try flashing TWRP but it was after it got stuck at the logo screen and only able to boot into Download Mode, the flashing came back failed with "Custom Binary (recovery) Blocked by RL" message.
Flashing it with the latest stock recovery i found online also gave me the same error message.
mrkage said:
USB debugging and Developer Mode was never turned on that device.
Negative, i did try flashing TWRP but it was after it got stuck at the logo screen and only able to boot into Download Mode, the flashing came back failed with "Custom Binary (recovery) Blocked by RL" message.
Flashing it with the latest stock recovery i found online also gave me the same error message.
Click to expand...
Click to collapse
Just out of curiosity, have you tried booting to safe mode? If any of the apps that you installed before this happened were causing an issue or bootloop before you flashed are still there, it/they could still be causing the bootloop. Remember, I said that it doesn't wipe data unless you are upgrading or downgrading bootloader/baseband, what you flashed wasn't an upgrade or a downgrade so your data is there. Boot to safe mode and disable/uninstall the apps that might be causing the issue.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
Droidriven said:
Just out of curiosity, have you tried booting to safe mode? If any of the apps that you installed before this happened were causing an issue or bootloop before you flashed are still there, it/they could still be causing the bootloop. Remember, I said that it doesn't wipe data unless you are upgrading or downgrading bootloader/baseband, what you flashed wasn't an upgrade or a downgrade so your data is there. Boot to safe mode and disable/uninstall the apps that might be causing the issue.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
Click to expand...
Click to collapse
Didn't try that... but nevermind. I accidentally damaged my screen while trying to dissasemble it last night, a very stupid mistake from me.
Thank you for trying to help me mate. Forum mods can close this thread now. Thanks all.
problem
i have too but with A/L
Hello fellas,
I have a SM-G930F running Super Stock Rom 2.8, rooted with Magisk 12. This morning I was a little high and worried about getting my device stolen (my S6 was stolen at gun point three months ago), so I disabled OEM Unlock and USB debug in Developer mode, in a crazy attempt to increase the security and make things more difficult for the thief. WRONG! I have really screwed things up.
Now I get CUSTOM BINARY BLOCKED BY FRP LOCK and my device won't boot. The DOWNLOAD mode shows FRP LOCK is ON, this means I won't be able to flash anything with ODIN because it will fail at writing (that is what the FRP Lock is for). I am at work and my computer has the USB ports disabled, so there's nothing I can do until I get home.
This guy did the same stupid thing, except that he wasn't high
https://forum.xda-developers.com/s7-edge/help/s7-edge-custom-binary-block-frp-lock-t3347688
I know that attempting a flash with ODIN can also cause this problem:
https://forum.xda-developers.com/showpost.php?p=71692103&postcount=25
As soon as I get home, I will attempt the Smart Switch Emergency Recovery Function and I hope everything will be OK. Since it was my google account logged in, I won't have any problems with FRP (theoretically, it will ask me to login with the last account used on the previous configuration).
[UPDATE] There is this ADB thing I am completely unfamiliar with, not to mention I have disabled USB debug on the device prior to this. This file will disable FRP Lock but I don't know the procedure.
https://www.androidfilehost.com/?fid=24591000424958372
Any help will be much appreciated. This is my only phone and now I can't use it.
Just Flash with stock frimware to make it worked than it will stuck on google lock account than try to find ways on youtube.
asadnow2k said:
Just Flash with stock frimware to make it worked than it will stuck on google lock account than try to find ways on youtube.
Click to expand...
Click to collapse
Thanks for replying. Flashing stock firmware with FRP Lock will cause a write failure, are you sure about this? I will try it as soon as I arrive home. I didn't get that part where it will get stuck on google lock account, the device is mine and the latest google account used before was my personal google account. Could you please provide more details to complete the process?
I am also considering Smart Switch Emergency Factory Restore, that is my last shot before taking it to repair shop.
Dear sir kindly be sure the software is latest/i mean firmware
Hi,
had my phone locked too. Smart switch worked, aftter flashing twrp same problem. Got a factory rom from sammonbile and flashed cp, bl and ap with odin which brought it back.
Regards,
dennis
demmis_ said:
Hi,
had my phone locked too. Smart switch worked, aftter flashing twrp same problem. Got a factory rom from sammonbile and flashed cp, bl and ap with odin which brought it back.
Regards,
dennis
Click to expand...
Click to collapse
asadnow2k said:
Dear sir kindly be sure the software is latest/i mean firmware
Click to expand...
Click to collapse
I managed to solve it using Smart Switch, the firmware update did the trick. After restoring the system asked for last used credentials on previous configuration, like it was supposed to. Since it was my personal google account, there wasn't any problem with FRP Lock. Now I have installed TWRP and Super Stock Rom 2.8 again.
Leason learned, I will NEVER deactivate OEM Unlock again with a Custom ROM.
Thanks to everyone, this thread can be closed now.
hemp_invader said:
I managed to solve it using Smart Switch, the firmware update did the trick. After restoring the system asked for last used credentials on previous configuration, like it was supposed to. Since it was my personal google account, there wasn't any problem with FRP Lock. Now I have installed TWRP and Super Stock Rom 2.8 again.
Leason learned, I will NEVER deactivate OEM Unlock again with a Custom ROM.
Thanks to everyone, this thread can be closed now.
Click to expand...
Click to collapse
hiiii can you help how to get out, i also have a private google account logged in plzzz help, i have also disabled oem mistakely
Thank You
Hello and sorry for my bad english. By foolishness, turn off OEM-unlocking when the full custom rom was installed. I panicked and repeated many times flash stock rom with the help of Odin. Now when restoring via Kies or Smart Switch phone writes errors about loss of DRK-key, dm-verify error and other. When i try to flash custom-recovery (because i have twrp-backup) in download mode, phone writes error "Custom binary block by FRP". What can i try to do?
I already try https://forum.xda-developers.com/sprint-galaxy-note5/help/frp-lock-help-please-t3196971
https://forum.xda-developers.com/s7-edge/how-to/guide-remove-frp-s7-s7-edge-t3590670
Flash stock rom thern root using cf-autoroot to pass drk error, phone will be able to be powered on, then you will have to fix drk
johnny.goldy said:
Flash stock rom thern root using cf-autoroot to pass drk error, phone will be able to be powered on, then you will have to fix drk
Click to expand...
Click to collapse
Thank you, but it not work
unterno said:
Hello and sorry for my bad english. By foolishness, turn off OEM-unlocking when the full custom rom was installed. I panicked and repeated many times flash stock rom with the help of Odin. Now when restoring via Kies or Smart Switch phone writes errors about loss of DRK-key, dm-verify error and other. When i try to flash custom-recovery (because i have twrp-backup) in download mode, phone writes error "Custom binary block by FRP". What can i try to do?
I already try https://forum.xda-developers.com/sprint-galaxy-note5/help/frp-lock-help-please-t3196971
https://forum.xda-developers.com/s7-edge/how-to/guide-remove-frp-s7-s7-edge-t3590670
Click to expand...
Click to collapse
U need to downgrade all the way back to the latest mm rom and frp bypass which I am not saying is legal but it is the only way for now,if u look in the right places it's pretty easy but android 7.0 frp bypass is not working ,first go down through each firmware till u get to mm
miko12312 said:
U need to downgrade all the way back to the latest mm rom and frp bypass which I am not saying is legal but it is the only way for now,if u look in the right places it's pretty easy but android 7.0 frp bypass is not working ,first go down through each firmware till u get to mm
Click to expand...
Click to collapse
You mean that I need to flash all the stock firmware that went to my phone in reverse order from the newest to the first with which the phone was in the box?
unterno said:
You mean that I need to flash all the stock firmware that went to my phone in reverse order from the newest to the first with which the phone was in the box?
Click to expand...
Click to collapse
Yes because I'm not sure exactly which ones u can skip ,but not to out of the box just to the latest mm android 6.0 rom and u can frp bypass , let's say it has been done many times but android 6.0 is the easiest to do I cant put were the files are but they are easy to get just Google it , follow the guide and unlock possible basically it adds a Google account and bypass is achieved no matter how many times u flash a firmware frp will come up on activation but find the right files and guide and ur all set but u must do it on the pc , and it must be done correctly after restore or u have to factory reset to do it again or reflash
---------- Post added at 02:26 AM ---------- Previous post was at 02:25 AM ----------
miko12312 said:
Yes because I'm not sure exactly which ones u can skip ,but not to out of the box just to the latest mm android 6.0 rom and u can frp bypass , let's say it has been done many times but android 6.0 is the easiest to do I cant put were the files are but they are easy to get just Google it , follow the guide and unlock possible basically it adds a Google account and bypass is achieved no matter how many times u flash a firmware frp will come up on activation but find the right files and guide and ur all set but u must do it on the pc , and it must be done correctly after restore or u have to factory reset to do it again or reflash
Click to expand...
Click to collapse
U will need a aim card also (hint)
flashing the oldest rom from https://www.sammobile.com/firmwares/ with Odin worked for me. You don't need to flash all the firmwares in reverse order, just the oldest, then FRP unlock using any of the working methods ! Once unlocked you can flash the newest from sammobile
miko12312 said:
Yes because I'm not sure exactly which ones u can skip ,but not to out of the box just to the latest mm android 6.0 rom and u can frp bypass , let's say it has been done many times but android 6.0 is the easiest to do I cant put were the files are but they are easy to get just Google it , follow the guide and unlock possible basically it adds a Google account and bypass is achieved no matter how many times u flash a firmware frp will come up on activation but find the right files and guide and ur all set but u must do it on the pc , and it must be done correctly after restore or u have to factory reset to do it again or reflash
---------- Post added at 02:26 AM ---------- Previous post was at 02:25 AM ----------
U will need a aim card also (hint)
Click to expand...
Click to collapse
Thanks guys for trying to help, but it looks like you can not hear me. When I'm flash any stock firmware the system does not boot. At the stage of the blue screen and the Android logo, an error appears about the DRK-Key.
I can not boot even in the welcome menu, which would try to turn off the FRP by following the instructions on the Internet
unterno said:
Thanks guys for trying to help, but it looks like you can not hear me. When I'm flash any stock firmware the system does not boot. At the stage of the blue screen and the Android logo, an error appears about the DRK-Key.
I can not boot even in the welcome menu, which would try to turn off the FRP by following the instructions on the Internet
Click to expand...
Click to collapse
Hi! 2 month after I get S7 edge from ebay. When I turn phone to bootloader I see on screen "FRP LOCK ON". And I just google it how to bypass s7 edge google lock. One video I found.
Step 1. Downgrade to 6.0.1
Step 2. Just watch to video.
Video name is " Bypass Google Account (FRP) Protection on Android on All Samsung S6, S7 edge Android N 7 0"
unterno said:
Thanks guys for trying to help, but it looks like you can not hear me. When I'm flash any stock firmware the system does not boot. At the stage of the blue screen and the Android logo, an error appears about the DRK-Key.
I can not boot even in the welcome menu, which would try to turn off the FRP by following the instructions on the Internet
Click to expand...
Click to collapse
S
Post pic
Hi all,
I have this model
Phone: SM-G955F
Android version: 7.0
Build number: NRD90M.G955FXXU1AQDD
I haven't touched anything or updated anything in at least 6 months and the work has been working fine.
I did update yesterday the "Samsung music" app however, not sure if that has anything to do with my problem.
This morning I got a message "Please restart your device, some apps are overloading the system".
So I did a reboot and now the device won't start.
I hate the red message "Custom Binary Blocked By FRP Lock" and the device stays turned off.
I didn't touch anything, so what on earth caused this?!
OEM Lock appears to be ON. FPR Lock is also ON now.
I had the phone rooted when I bought it but I'm using stock firmware.
Also, haven't had any issues in over 6 months so this I am very curious what could cause this to suddenly happen.
I read some guides that I have to re-flash stock firmware again, but I don't see how that will prevent the issue from happening again
Please help
I downloaded Odin and then what looks like the latest stock firmware.
Not sure how that is going to help. I had stock firmware before too
Hum. What can you boot into, recovery (is it stock recovery)? download mode? will it boot to setup in system, as it should if you have an FRP happening.
I had a nightmare of a day yesterday.
Downloaded the latest stock rom and flashed it using Odin. That worked fine.
Then I added TWRP and the phone got soft-bricked because apparently TWRP is not compatible with any of the latest firmware versions (who knew!)
Then I spent hours looking at hacks and found that Notorious zip that you can flash after getting into TWRP via the old BL/smash Start on Odin trick
Then phone showed verification error with the only option to Wipe all data (which I didn't want to do)
Then I managed to reflash the latest stock rom and leave it unrooted for now.
It's a learning experience but I don't like the high stress levels.
The most important thing is that I did nothing to cause the FPR lock and I'm now afraid it might randomly happen every few months
nkomp18 said:
I had a nightmare of a day yesterday.
Downloaded the latest stock rom and flashed it using Odin. That worked fine.
Then I added TWRP and the phone got soft-bricked because apparently TWRP is not compatible with any of the latest firmware versions (who knew!)
Then I spent hours looking at hacks and found that Notorious zip that you can flash after getting into TWRP via the old BL/smash Start on Odin trick
Then phone showed verification error with the only option to Wipe all data (which I didn't want to do)
Then I managed to reflash the latest stock rom and leave it unrooted for now.
It's a learning experience but I don't like the high stress levels.
The most important thing is that I did nothing to cause the FPR lock and I'm now afraid it might randomly happen every few months
Click to expand...
Click to collapse
Generally for the 955F (Exynos, yes?), it's a pretty straight forward process. Yes, you do have to make sure you have the correct TWRP . . .
https://forum.xda-developers.com/s7...overy-official-twrp-hero2lte-3-0-0-0-t3334084
once you flash TWRP, right at the end, or just before then end of the flash, press Vol up, Bixby and power to boot directly into TWRP. Should work just fine. If not, usually re-flashing TWRP and a direct boot to recovery works. Sometimes it take a few times to get the key pressing/timing down.
Yeah, you are right, it can feel pretty stressful.
hi, did you finally fix this problem? I have a s9+ stock firm, got TWRP and rooted and has been using it for a couple of months without issue, including reboot. but today I was using a bank app it kept stopping itself, so without further thinking I restarted the phone and got the red FRP lock on the screen. tried getting into TWRP but said it's blocked by FRP lock. then using ODIN I reflashed the same stock firm, got into the phone, everything is there except root, and of course Titanium works no more!
my question is, if anyone is reading this, is the TWRP still there or not? in order to find out I'll have to flip the OEM lock off and tried to get into TWRP, but would that trigger a factory reset? but if the TWRP is not there anymore, in order to root I'll have to do a system wipe. either way it gonna be troublesome. and besides, what's to prevent its happening all over again?
I'd appreciate any help! thanks))
Simple solution to that DONT turn the OEM unlocking OFF
This toggle unlocks the bootloader for use with custom binarys and recoveries such as TWRP toggling the OEM unlocking off will stop any custom recovery from being flashed with odin and will also not allow the custom recovery on it to be booted for security reasons related to the FRP lock
The OEM lock is linked to the FRP lock both are run through the same toggle you would have noticed when you enabled it that a warning message appeared about the device losing all FRP security measures when enabled if you switch this toggle back to off your FRP lock re activates and the custom recovery that is already installed will now be blocked from being used and the system will render it a security issue and will not allow your system to boot,
So again to save you all this trouble in the future DO NOT tuurn off your oem unlock while you have a custom binary installed,
Yes your devices security is gone but this is the cost you pay when you decided you wanted to root your device,
There is an alternative though if you know what your doing enable oem unlock flash TWRP flash your root and what not then when finished if you know how to pull the recovery from stock firmware and make it into a flashable file with odin you can have root and what not and also keep your oem unlock switched to off bu ti strongly suggest do your reaearch if you choose to take this path.
Hope this helps guys
Matty1993 said:
Simple solution to that DONT turn the OEM unlocking OFF
This toggle unlocks the bootloader for use with custom binarys and recoveries such as TWRP toggling the OEM unlocking off will stop any custom recovery from being flashed with odin and will also not allow the custom recovery on it to be booted for security reasons related to the FRP lock
The OEM lock is linked to the FRP lock both are run through the same toggle you would have noticed when you enabled it that a warning message appeared about the device losing all FRP security measures when enabled if you switch this toggle back to off your FRP lock re activates and the custom recovery that is already installed will now be blocked from being used and the system will render it a security issue and will not allow your system to boot,
So again to save you all this trouble in the future DO NOT tuurn off your oem unlock while you have a custom binary installed,
Yes your devices security is gone but this is the cost you pay when you decided you wanted to root your device,
There is an alternative though if you know what your doing enable oem unlock flash TWRP flash your root and what not then when finished if you know how to pull the recovery from stock firmware and make it into a flashable file with odin you can have root and what not and also keep your oem unlock switched to off bu ti strongly suggest do your reaearch if you choose to take this path.
Hope this helps guys
Click to expand...
Click to collapse
thanks Matty! now that I think about it I might have turned OEM unlock off because some bank app suddenly stopped working and I was trying to guess what went wrong.
Matty1993 said:
Simple solution to that DONT turn the OEM unlocking OFF
This toggle unlocks the bootloader for use with custom binarys and recoveries such as TWRP toggling the OEM unlocking off will stop any custom recovery from being flashed with odin and will also not allow the custom recovery on it to be booted for security reasons related to the FRP lock
The OEM lock is linked to the FRP lock both are run through the same toggle you would have noticed when you enabled it that a warning message appeared about the device losing all FRP security measures when enabled if you switch this toggle back to off your FRP lock re activates and the custom recovery that is already installed will now be blocked from being used and the system will render it a security issue and will not allow your system to boot,
So again to save you all this trouble in the future DO NOT tuurn off your oem unlock while you have a custom binary installed,
Yes your devices security is gone but this is the cost you pay when you decided you wanted to root your device,
There is an alternative though if you know what your doing enable oem unlock flash TWRP flash your root and what not then when finished if you know how to pull the recovery from stock firmware and make it into a flashable file with odin you can have root and what not and also keep your oem unlock switched to off bu ti strongly suggest do your reaearch if you choose to take this path.
Hope this helps guys
Click to expand...
Click to collapse
hi i need your help, i have a samsung galaxy s7 and it's locked by frp (sorry for my english but i'm italian), i try to install official firmware by odin but it say an error sboot.bin fail! (with bt file) and say recovery.img fail! (with ap file), now i understand that my bootloader il blocked by oem block, there is a way to unlock by odin mode or others? i can't have access to recovery or phone.
please help me i'm desperate!
corvasce03 said:
hi i need your help, i have a samsung galaxy s7 and it's locked by frp (sorry for my english but i'm italian), i try to install official firmware by odin but it say an error sboot.bin fail! (with bt file) and say recovery.img fail! (with ap file), now i understand that my bootloader il blocked by oem block, there is a way to unlock by odin mode or others? i can't have access to recovery or phone.
please help me i'm desperate!
Click to expand...
Click to collapse
You need to flash the correct bootloader version to your device IE check the binary number on the firmware file and compare to what is listed on download mode
File binarys have the letter U? example is
G930FXXU2ARA1 or G930FXXU3ARA1
Take note of the number
Now in download mode on the device
Find AP SWREV B: ? An example is
AP SWREV B:2 K:0 S:0
The 2 signifies it's a bit 2 bootloader so the firmware package needed for this device would be for example G930FXX"U2"ABCD
all you have to do is match them up,
AP SWREV B1 = U1 or S1
AP SWREV B2 = U2 or S2
AP SWREV B3 = U3 or S3
As for the flash error message " custom binary blocked by frp lock" means someone has tampered with the firmware, I'd assume you didnt get it from sammobile ? or it's not made for model number check the backing to your S7 model number is located at the bottom in small writing
Will be G930"F" for example also compare the letter to the binary file to make sure your flashing the correct model,
Also what version of odin3 are you using to flash as 6.0 to 7.0 binaries can be flashed with V3.12 as the binary files don't use .lz4 compression however 8.0 binaries do use .lz4 compression this is a new type of compression so requires Odin3 3.13.1 as this odin3 has the capabilities to read and flash the .lz4 binaries to the device
And I'm not sure if your aware but the factory binaries dont have OEM unlock in them to remove the FRP however there is a way that I know how to do it on this particular model but it will vary the B:? In download mode and to if a combination rom is available for your binary number COLOR="Silver"]
---------- Post added at 04:08 AM ---------- Previous post was at 03:57 AM ----------
[/COLOR]
snooyy said:
thanks Matty! now that I think about it I might have turned OEM unlock off because some bank app suddenly stopped working and I was trying to guess what went wrong.
Click to expand...
Click to collapse
All good mate , yeah once that OEM unlock is turned back off all security features are re activated that was your problem did you manage to fix it yet if not all you gotta do is flash the stock recovery and you shouldn't lose your data
Matty1993 said:
---------- Post added at 04:08 AM ---------- Previous post was at 03:57 AM ----------
All good mate , yeah once that OEM unlock is turned back off all security features are re activated that was your problem did you manage to fix it yet if not all you gotta do is flash the stock recovery and you shouldn't lose your data
Click to expand...
Click to collapse
thanks mate yes I got my data back, but re-root it would mean loosing them so I'm running without the root now. good thing is Netflix, prime vedio, bank stuff are all working, bad thing is no titanium(
Matty1993 said:
You need to flash the correct bootloader version to your device IE check the binary number on the firmware file and compare to what is listed on download mode
File binarys have the letter U? example is
G930FXXU2ARA1 or G930FXXU3ARA1
Take note of the number
Now in download mode on the device
Find AP SWREV B: ? An example is
AP SWREV B:2 K:0 S:0
The 2 signifies it's a bit 2 bootloader so the firmware package needed for this device would be for example G930FXX"U2"ABCD
all you have to do is match them up,
AP SWREV B1 = U1 or S1
AP SWREV B2 = U2 or S2
AP SWREV B3 = U3 or S3
As for the flash error message " custom binary blocked by frp lock" means someone has tampered with the firmware, I'd assume you didnt get it from sammobile ? or it's not made for model number check the backing to your S7 model number is located at the bottom in small writing
Will be G930"F" for example also compare the letter to the binary file to make sure your flashing the correct model,
Also what version of odin3 are you using to flash as 6.0 to 7.0 binaries can be flashed with V3.12 as the binary files don't use .lz4 compression however 8.0 binaries do use .lz4 compression this is a new type of compression so requires Odin3 3.13.1 as this odin3 has the capabilities to read and flash the .lz4 binaries to the device
And I'm not sure if your aware but the factory binaries dont have OEM unlock in them to remove the FRP however there is a way that I know how to do it on this particular model but it will vary the B:? In download mode and to if a combination rom is available for your binary number COLOR="Silver"]
---------- Post added at 04:08 AM ---------- Previous post was at 03:57 AM ----------
[/COLOR]
All good mate , yeah once that OEM unlock is turned back off all security features are re activated that was your problem did you manage to fix it yet if not all you gotta do is flash the stock recovery and you shouldn't lose your data
Click to expand...
Click to collapse
thanks for answer, in odin mode it say rp swrev b3 k1 s2, where can i find the frmware with my binary number?
corvasce03 said:
thanks for answer, in odin mode it say rp swrev b3 k1 s2, where can i find the frmware with my binary number?
Click to expand...
Click to collapse
No worries so you have a bit 3 bootloader what does the model number say also in download mode ?
I'll provide you the link to the correct firmware to download that will be 100% official
matty1993 said:
no worries so you have a bit 3 bootloader what does the model number say also in download mode ?
I'll provide you the link to the correct firmware to download that will be 100% official
Click to expand...
Click to collapse
all it say
odin mode
download speed: Fast
product name: Sm-g930f
current binary: Samsung official
system status: Custom
frp lock: On
secure download: Enabled
warranty void: 1 (0x030c)
rp swrev: B3 k1 s2
corvasce03 said:
all it say
odin mode
download speed: Fast
product name: Sm-g930f
current binary: Samsung official
system status: Custom
frp lock: On
secure download: Enabled
warranty void: 1 (0x030c)
rp swrev: B3 k1 s2
Click to expand...
Click to collapse
Yep sweet also what region are you in also so I can make sure the firmwares modem is also region appropriate as they all run on different frequencies other than that that's all the info I need my friend product name is model number you have the same model as me I have G930F also give me two seconds and I'll get the link for you for the correct firmware, as for frp lock your very much quite lucky the warranty void is only "warranty void 1 (0×030c)
If it were : 1 (0×500b) youd be royally screwed for some reason combination roms will not boot on any Knox tripped S7 with : 1 (0×500b) but will boot on any Knox tripped device with : 1 (0×030c) I know this as I have a variety of S7 as I run a phone repair shop and have tested on tripped devices with Knox tripped as both
---------- Post added at 05:34 PM ---------- Previous post was at 05:27 PM ----------
corvasce03 said:
all it say
odin mode
download speed: Fast
product name: Sm-g930f
current binary: Samsung official
system status: Custom
frp lock: On
secure download: Enabled
warranty void: 1 (0x030c)
rp swrev: B3 k1 s2
Click to expand...
Click to collapse
Not sure what region you are but here the link to the S7 G930F pages just scroll down select your country and the select the first available firmware that appears with a U3 or S3 when you have selected your region,
https://www.sammobile.com/firmwares/galaxy-s7/SM-G930F/
Matty1993 said:
Yep sweet also what region are you in also so I can make sure the firmwares modem is also region appropriate as they all run on different frequencies other than that that's all the info I need my friend product name is model number you have the same model as me I have G930F also give me two seconds and I'll get the link for you for the correct firmware, as for frp lock your very much quite lucky the warranty void is only "warranty void 1 (0×030c)
If it were : 1 (0×500b) youd be royally screwed for some reason combination roms will not boot on any Knox tripped S7 with : 1 (0×500b) but will boot on any Knox tripped device with : 1 (0×030c) I know this as I have a variety of S7 as I run a phone repair shop and have tested on tripped devices with Knox tripped as both
---------- Post added at 05:34 PM ---------- Previous post was at 05:27 PM ----------
Not sure what region you are but here the link to the S7 G930F pages just scroll down select your country and the select the first available firmware that appears with a U3 or S3 when you have selected your region,
https://www.sammobile.com/firmwares/galaxy-s7/SM-G930F/
Click to expand...
Click to collapse
ok thanks i try to download it and update you if it go or not
corvasce03 said:
ok thanks i try to download it and update you if it go or not
Click to expand...
Click to collapse
Hey mate no it will 100% work just select your country all firmware from sammobile is guaranteed to be 100% official I use them myself, the only thing however is you need to make an account but the good news its 100% free to make an account but then there another little downfall download speeds are a little slow in free subscription but well worth the wait as I guarantee it will work
Matty1993 said:
Hey mate no it will 100% work just select your country all firmware from sammobile is guaranteed to be 100% official I use them myself, the only thing however is you need to make an account but the good news its 100% free to make an account but then there another little downfall download speeds are a little slow in free subscription but well worth the wait as I guarantee it will work
Click to expand...
Click to collapse
thanks!!!!! it workk it's beautiful!!! thanks thanks thanks!
OK someone please help. I'm having this same issue, except I got a galaxy s6, however when I boot into download mode and plug cable up it recognizes the driver as a modem or sometimes I get it to show up in ports but its named USB serial device, so I'm unable to flash anything through odin. I tried plugging my wife's galaxy s7 up to PC through download mode and her phone doesn't even show up as a USB diagnostic port....I'm seriously stumped on this and having a hell of a time trying to find any info on this My dumbass had stay awake checked at the time and when I went to turn it off I must have accidently unchecked the OEM unlock option resulting in.....a good headache lol....thanks for ur time guys.
corvasce03 said:
thanks!!!!! it workk it's beautiful!!! thanks thanks thanks!
Click to expand...
Click to collapse
No problem mate glad I could help
---------- Post added at 01:56 AM ---------- Previous post was at 01:49 AM ----------
jfoley420 said:
OK someone please help. I'm having this same issue, except I got a galaxy s6, however when I boot into download mode and plug cable up it recognizes the driver as a modem or sometimes I get it to show up in ports but its named USB serial device, so I'm unable to flash anything through odin. I tried plugging my wife's galaxy s7 up to PC through download mode and her phone doesn't even show up as a USB diagnostic port....I'm seriously stumped on this and having a hell of a time trying to find any info on this My dumbass had stay awake checked at the time and when I went to turn it off I must have accidently unchecked the OEM unlock option resulting in.....a good headache lol....thanks for ur time guys.
Click to expand...
Click to collapse
Hey mate i run a phone repair shop it's got nothing to do with the phones it's the computer or drivers
#1 What version of Odin are you using, you should be using the latest I use 3.13.1 as it supports new .lz4 compression for 8.0 oreo firmware,
#2 did you install the latest Samsung drivers.exe because if you didnt the information is not on your computer to read samsungs devices all the information to communicate to the device is stored in these drivers,
If you havent this is your problem, go to Google type in "latest Samsung USB driver.exe download" or check the forums here for it also, download it and simply open the exe and install the drivers,
Reboot and now try, if you still have the same issue what USB cord are you using, try an original Samsung USB cable or decent branded one,
If there error still persists what version of windows are you using,
Thanks
In case you guys know already, the android 10 has been released for the F907N
I cant find any thread for the F907N so I just opened a new one so that you guys can come and discuss!!!
Thanks!!!
what you think of the update so far
I can tell its good!!!
Very smooth, stable!!!
Especially the full screen gesture!!! No you can access the phone from any corner, any side of the phone (thanks to the One UI 2.1)
For the other aspects, android 9 is good already so this one just somehow improved it!!!
yes the performance is good, phone has become smoother and more buttery. I just wish I could have managed to get Samsung members for India and Samsung pay, I am in India and Korean language is something I dont understand,
anybody guide for rebrand 900n to inter rom, or just debloat korean apps is quite annoying
Hi all,
I already posted this query in another form, but maybe this form seems to be the right place.
I have the Korean version FOLD 5G SM-F907N. I am having problem in receiving 5G signal in UAE although all setup is done with coverage.
Will I be able to install the Stock Firmware? Which one I should install? is installing European version a possibility? (i.e. SM-F907B or others) or I will run the risk of bricking the device?
latif99 said:
Hi all,
I already posted this query in another form, but maybe this form seems to be the right place.
I have the Korean version FOLD 5G SM-F907N. I am having problem in receiving 5G signal in UAE although all setup is done with coverage.
Will I be able to install the Stock Firmware? Which one I should install? is installing European version a possibility? (i.e. SM-F907B or others) or I will run the risk of bricking the device?
Click to expand...
Click to collapse
I would like to do the same too, tried to find info on this -- but nothing much on it. Does the Euro one also seem to get more monthly patches?
While I note the PDA is the same, we're one month behind on the patches as we speak. Also, Korean bloatware is annoying.
Did you have any luck?
How to rebrand 907N to another?
nipuna said:
I would like to do the same too, tried to find info on this -- but nothing much on it. Does the Euro one also seem to get more monthly patches?
While I note the PDA is the same, we're one month behind on the patches as we speak. Also, Korean bloatware is annoying.
Did you have any luck?
Click to expand...
Click to collapse
I am waiting
deadlyheart4u said:
yes the performance is good, phone has become smoother and more buttery. I just wish I could have managed to get Samsung members for India and Samsung pay, I am in India and Korean language is something I dont understand,
Click to expand...
Click to collapse
exact issue i am facing, no samsung pay and presence of bloatwares, did you found any solution?
rammy1991 said:
exact issue i am facing, no samsung pay and presence of bloatwares, did you found any solution?
Click to expand...
Click to collapse
Nope, I bought s20 ultra in May and have sold the fold waiting for z fold 2
Sent from my SM-G988B using Tapatalk
Hi, anyone tried this link fo F907N model?
https://support.halabtech.com/index.php?a=downloads&b=folder&id=71632
shameemindia said:
Hi, anyone tried this link fo F907N model?
https://support.halabtech.com/index.php?a=downloads&b=folder&id=71632
Click to expand...
Click to collapse
how to install this?
shaifullah.ahad said:
how to install this?
Click to expand...
Click to collapse
First unlock its bootloader. Select OEM Unlocking from Settings → Developer Options, then reboot to Device Unlock mode to actually unlock the bootloader. This will have the side-effect of resetting the device.
unzip the downlaoded file and flash through odin. and then install Magisk application for root.
https://topjohnwu.github.io/Magisk/install.html#samsung-system-as-root
shameemindia said:
First unlock its bootloader. Select OEM Unlocking from Settings → Developer Options, then reboot to Device Unlock mode to actually unlock the bootloader. This will have the side-effect of resetting the device.
unzip the downlaoded file and flash through odin. and then install Magisk application for root.
https://topjohnwu.github.io/Magisk/install.html#samsung-system-as-root
Click to expand...
Click to collapse
I turned on OEM Unlock from developer mode. And tried to install this by Odin but showing error oem lock. Please explain how to unlock bootloader? I select unlock oem from developer mode but it showing error when trying to install by odin
---------- Post added at 10:41 AM ---------- Previous post was at 10:18 AM ----------
"md5 error! Binary is invalid" for BL, CP, CSC
and
"Custom Binary (vbmeta) Blocked By OEM Lock" for AP.
What can I do now?
shaifullah.ahad said:
I turned on OEM Unlock from developer mode. And tried to install this by Odin but showing error oem lock. Please explain how to unlock bootloader? I select unlock oem from developer mode but it showing error when trying to install by odin
---------- Post added at 10:41 AM ---------- Previous post was at 10:18 AM ----------
"md5 error! Binary is invalid" for BL, CP, CSC
and
"Custom Binary (vbmeta) Blocked By OEM Lock" for AP.
What can I do now?
Click to expand...
Click to collapse
How To Unlock Bootloader of Samsung Galaxy Fold
Open your device settings and head towards the about phone section
There click on the built number for 6-7 times until the pop up shows “You are a Developer now”
Now in your smartphone’s settings open Developer options
In the Developer, option menu look for the OEM unlocking
Switch the OEM unlocking ON and switch off your device
While switched off try to reboot your phone into the download mode by pressing and holding the power and volume down button for sometime
Once in the download mode, long-press the volume up button, this will unlock your bootloader
Now if you wish to install a custom ROM on your device you have to bypass the Vaultkeeper security, to do so go through the initial setup
Enable developer options again from the settings, and verify that the OEM unlocking option still exists and switched on! The VaultKeeper service will automatically remove the conditions from the bootloader after it verifies that the user has enabled the OEM unlocking option.
Now your custom firmware will be installed easily and your bootloader will be unlocked finally.
While switched off try to reboot your phone into the download mode by pressing and holding the power and volume down button for sometime
Once in the download mode, long-press the volume up button, this will unlock your bootloader
Not working for me. In download mode when long press volume up key nothing happen
I am able to install this rom but it is not pre-rooted. and SM-F907N has no twrp so i can not install magisk in it
---------- Post added at 07:40 AM ---------- Previous post was at 07:40 AM ----------
shameemindia said:
Hi, anyone tried this link fo F907N model?
https://support.halabtech.com/index.php?a=downloads&b=folder&id=71632
Click to expand...
Click to collapse
I am able to install this rom but it is not pre-rooted. and SM-F907N has no twrp so i can not install magisk in it
shaifullah.ahad said:
I am able to install this rom but it is not pre-rooted. and SM-F907N has no twrp so i can not install magisk in it
---------- Post added at 07:40 AM ---------- Previous post was at 07:40 AM ----------
I am able to install this rom but it is not pre-rooted. and SM-F907N has no twrp so i can not install magisk in it
Click to expand...
Click to collapse
did you install magisk apk?
i need the global version to use Samsung pay anyone has a way to do that ?