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
Hi guys
I need a helping hand.
I have a s7 (G930F fxxu2drb6) with frp lock.
It did not work either realterm, bluetooth, or downgrade (SW REV CHECK FAIL DEVICE 2, BINARY 1 SAMSUNG).
On gsm-hosting they suggested to me to flash the combination file "COMBINATION_FA60_G930FXXU2ARA2_CL7964511_QB165812 9 6_REV00_user_mid_noship.tar.md5".
After the flash I can not yet downgrade (W REV CHECK FAIL DEVICE 2, BINARY 1 SAMSUNG), not even flash again "fxxu2drb6" (FAIL RQT_close).
Can someone help me get out of this situation?
Thank you in advance
marcoar said:
Hi guys
I need a helping hand.
I have a s7 (G930F fxxu2drb6) with frp lock.
It did not work either realterm, bluetooth, or downgrade (SW REV CHECK FAIL DEVICE 2, BINARY 1 SAMSUNG).
On gsm-hosting they suggested to me to flash the combination file "COMBINATION_FA60_G930FXXU2ARA2_CL7964511_QB165812 9 6_REV00_user_mid_noship.tar.md5".
After the flash I can not yet downgrade (W REV CHECK FAIL DEVICE 2, BINARY 1 SAMSUNG), not even flash again "fxxu2drb6" (FAIL RQT_close).
Can someone help me get out of this situation?
Thank you in advance
Click to expand...
Click to collapse
Try to connect with smart switch.
On windows pc or laptop
Sent from my [device_name] using XDA-Developers Legacy app
---------- Post added at 11:21 PM ---------- Previous post was at 11:20 PM ----------
marcoar said:
Hi guys
I need a helping hand.
I have a s7 (G930F fxxu2drb6) with frp lock.
It did not work either realterm, bluetooth, or downgrade (SW REV CHECK FAIL DEVICE 2, BINARY 1 SAMSUNG).
On gsm-hosting they suggested to me to flash the combination file "COMBINATION_FA60_G930FXXU2ARA2_CL7964511_QB165812 9 6_REV00_user_mid_noship.tar.md5".
After the flash I can not yet downgrade (W REV CHECK FAIL DEVICE 2, BINARY 1 SAMSUNG), not even flash again "fxxu2drb6" (FAIL RQT_close).
Can someone help me get out of this situation?
Thank you in advance
Click to expand...
Click to collapse
It will flash stock firmware and solve all binary problem
Sent from my [device_name] using XDA-Developers Legacy app
---------- Post added at 11:22 PM ---------- Previous post was at 11:21 PM ----------
marcoar said:
Hi guys
I need a helping hand.
I have a s7 (G930F fxxu2drb6) with frp lock.
It did not work either realterm, bluetooth, or downgrade (SW REV CHECK FAIL DEVICE 2, BINARY 1 SAMSUNG).
On gsm-hosting they suggested to me to flash the combination file "COMBINATION_FA60_G930FXXU2ARA2_CL7964511_QB165812 9 6_REV00_user_mid_noship.tar.md5".
After the flash I can not yet downgrade (W REV CHECK FAIL DEVICE 2, BINARY 1 SAMSUNG), not even flash again "fxxu2drb6" (FAIL RQT_close).
Can someone help me get out of this situation?
Thank you in advance
Click to expand...
Click to collapse
Intall smart connect or smart switch in pc
Sent from my [device_name] using XDA-Developers Legacy app
marcoar said:
Hi guys
I need a helping hand.
I have a s7 (G930F fxxu2drb6) with frp lock.
It did not work either realterm, bluetooth, or downgrade (SW REV CHECK FAIL DEVICE 2, BINARY 1 SAMSUNG).
On gsm-hosting they suggested to me to flash the combination file "COMBINATION_FA60_G930FXXU2ARA2_CL7964511_QB165812 9 6_REV00_user_mid_noship.tar.md5".
After the flash I can not yet downgrade (W REV CHECK FAIL DEVICE 2, BINARY 1 SAMSUNG), not even flash again "fxxu2drb6" (FAIL RQT_close).
Can someone help me get out of this situation?
Thank you in advance
Click to expand...
Click to collapse
Flash latest stock firmware for your region and enable OEM unlock in developer settings to avoid FRP in future. Also try to remember your google account password :silly:
Solved. I flash the latest firmware with an old version of odin
frp lock
marcoar said:
Solved. I flash the latest firmware with an old version of odin
Click to expand...
Click to collapse
Hi ! Which version of odin did you use ? Marcoar
And which version of android do you have before the flash ?
kira31390 said:
Hi ! Which version of odin did you use ? Marcoar
And which version of android do you have before the flash ?
Click to expand...
Click to collapse
Odin 3.12.5
Firmware: fxxu2drb6
marcoar said:
Hi guys
I need a helping hand.
I have a s7 (G930F fxxu2drb6) with frp lock.
It did not work either realterm, bluetooth, or downgrade (SW REV CHECK FAIL DEVICE 2, BINARY 1 SAMSUNG).
On gsm-hosting they suggested to me to flash the combination file "COMBINATION_FA60_G930FXXU2ARA2_CL7964511_QB165812 9 6_REV00_user_mid_noship.tar.md5".
After the flash I can not yet downgrade (W REV CHECK FAIL DEVICE 2, BINARY 1 SAMSUNG), not even flash again "fxxu2drb6" (FAIL RQT_close).
Can someone help me get out of this situation?
Thank you in advance
Click to expand...
Click to collapse
Hi there
When you flashed the combination rom you described did it actually boot into the factory binary ?
Im just curious as i have the same combination rom though my firmware is G930FXXU2DRBE and when i flash the binary with odin it will turn on but wont boot past the samsung S7 screen rhough the blue light comes on and pulsates though this is all it does i was just wonderng if yours did the same.
Thanks
Matty1993 said:
Hi there
When you flashed the combination rom you described did it actually boot into the factory binary ?
Im just curious as i have the same combination rom though my firmware is G930FXXU2DRBE and when i flash the binary with odin it will turn on but wont boot past the samsung S7 screen rhough the blue light comes on and pulsates though this is all it does i was just wonderng if yours did the same.
Thanks
Click to expand...
Click to collapse
after the combination file flash, the phone normally starts with the combination firmware
marcoar said:
after the combination file flash, the phone normally starts with the combination firmware
Click to expand...
Click to collapse
Thanks so much for the reply i appreciate it i might try my combination file with the G930FXXU2DRB6 firmware you used as i need to test my hardware and fix imei but cant get the factory binary to boot on G930FXXU2DRBE firmware my thinking that it wouldnt boot was as its FA60 is android 6.0 MM where as my U2DRBE firmware is FA70 7.0 nougat is your device nougat or marshmallow ? Just trying to work out whats going wrong where for it to not boot on my device as ive lost my imei number flashing a custom rom and dont have access to my TWRP back up for another 3 weeks
Thanks
Hello. I have a similar problem. I have the latest firmware on it: G930FXXS2DRDI There are no ways to lift the Google lock. I have tried everything possible: Bluetooth does not work, Talkback, Realterm, etc. Please for help
My Android Version is: 7.0 (Nougat)
Frp g930fxxu2ara1
Hello my friend, i have this problem too. Have you a fix? this security patch for FRP is incredible....
You CAN bypass FRP on later Samsung models using Combination FW. I have succsesfully done this with S8+/G955F, it should work with any device that has compatible Stock/Combinaton FW.. Here are the steps. Download a compatible STOCK ROM, and some similar COMBINATION FW (by similar i mean both FW to be with the same binary and same android version, duh..) Here are some firmware download links, but you can use whatever you want, according to your device.. G930F STOCK ROM/G930F Combination FW
First, using Odin flash the COMBINATION FW to your phone. After flashing is complete and the phone reboots, allow a few minutes for the phone to boot. If it doesn't boot/gets stuck at bootlogo, reboot/boot to recovery and wipe data/cache, and reboot again. MOST IMPORTANT THING! After the phone boots, go to Settings, enable Developer Options if not enabled, enable USB Debugging, and turn the device OFF using Power button. After the device shuts down, enter Download mode, open Odin, place all 4 files in their respective fields (BL,AP,CP,CSC), and here is the SECOND MOST IMPORTANT THING! In the CSC field place the CSC file that starts with HOME/HOME_CSC (There will/should be 2 different CSC files in the FW archive, one starting with CSC, and the other with HOME_CSC). After flashing is complete, allow the phone to boot normally (don't do anything, don't enter recovery/wipe data). If you followed my instructions correctly, after the phone boots, you should be able to finish the initial setup/skip all steps, without requiring any account. Then go to Settings, enable Developer Options, turn OEM Unlock ON, and finally factory reset the device to complete the process and start fresh.
Don't forget to hit THANKS button if this method worked fo you!
ATRAC3, do you have the combination files and firmware for the SAMSUNG S7 SM-G930FD please and thank you for your wonderful tutorial here.
my odin(tried on v3.12.5/v3.12.7/v3.13.1 ) keep failing while flashing HOME_CSC but will success with CSC, and still required to login google account, what is the issue here ? (are we supposed to insert the pit file by ATRAC3 ? )
flashing at the lastest FW G930FXXS2DRCE
phone version:SM-G930F
ATRAC3 said:
You CAN bypass FRP on later Samsung models using Combination FW. I have succsesfully done this with S8+/G955F, it should work with any device that has compatible Stock/Combinaton FW.. Here are the steps. Download a compatible STOCK ROM, and some similar COMBINATION FW (by similar i mean both FW to be with the same binary and same android version, duh..) Here are some firmware download links, but you can use whatever you want, according to your device.. G930F STOCK ROM/G930F Combination FW
First, using Odin flash the COMBINATION FW to your phone. After flashing is complete and the phone reboots, allow a few minutes for the phone to boot. If it doesn't boot/gets stuck at bootlogo, reboot/boot to recovery and wipe data/cache, and reboot again. MOST IMPORTANT THING! After the phone boots, go to Settings, enable Developer Options if not enabled, enable USB Debugging, and turn the device OFF using Power button. After the device shuts down, enter Download mode, open Odin, place all 4 files in their respective fields (BL,AP,CP,CSC), and here is the SECOND MOST IMPORTANT THING! In the CSC field place the CSC file that starts with HOME/HOME_CSC (There will/should be 2 different CSC files in the FW archive, one starting with CSC, and the other with HOME_CSC). After flashing is complete, allow the phone to boot normally (don't do anything, don't enter recovery/wipe data). If you followed my instructions correctly, after the phone boots, you should be able to finish the initial setup/skip all steps, without requiring any account. Then go to Settings, enable Developer Options, turn OEM Unlock ON, and finally factory reset the device to complete the process and start fresh.
Don't forget to hit THANKS button if this method worked fo you!
Click to expand...
Click to collapse
Hi mate ive used the G930FXXU2DRBE XSA Firmware and also G930FXXU2DRB6 firmware with the G930FXXU2ARA2 combination rom however it will not boot past the samsung logo the nad passes and is provisioned in top left corner and when plugged into the computer comes online with ADB bypass flasher but it just sits there even if i do a cache wipe and factory reset it comes up with a tango console error or something like that when reset then reboots back to samsung logo and when re installing firmware HOME-CSC will fail every time the only thing ive been able to put it down to is that (1) the firmware is FA_70 which is nougat OS and the combination rom is FA_60 MM or (2) my knox warranty bit is tripped and will not allow a samsung factory binary to be run on it, may i ask what would be the difference with the firmware you have listed to the firmware im already using with the combination rom ? Need to sort my imei number out with the factory nad asap dont have access to my TWRP backup for another week and a half, if it helps my device is not FRP locked and is oem unlocked.
Thanks
Matthew
P.S to all those whom have a bit 2 bootloader on S7 all the loopholes have been patched the only way is to use the combination files ive been through absolutely everything and tried everything this new bootloader update is impenetrable i can google unlock samsung S8 and S9 no dramas and with S9 the OEM lock option dissapears for a week if tampered with but still 15 minutes and its done this **** but got me goin loco holmes !!!!! Maybe they figured this out also as there is only bit 1 bootloaders for both the S8 and the S9 however with S8 i found a stock firmware that allows another way to unlock the device without the need to flash any combination rom.
So in short no hope now to unbrick our Samsung S7 SM-G930F/FD or what.....?
LEVY P said:
So in short no hope now to unbrick our Samsung S7 SM-G930F/FD or what.....?
Click to expand...
Click to collapse
If it gets stuck on the console error and wont reboot to download mode then hold the power button volume down button and power button for 40 seconds and it will re boot to download mode for stock firmware re installation in short basically no theres way to remove the FRP unless you can get the combination rom to boot which from what ive seen some will boot the binary but then it also depends if HOME_CSC will flash to keep usb debugging enabled to use adb bypass program im now using the new G930FXXU2ERE2 8.0 OREO so I've given up on the binary 2 nougat FRP unlocking for now might be best to wait a while for someone to receive a factory binary on the nougat or oreo when sent off and returned so it can be dumped and built into a flashable rom until then not much can be done and i may have to wait another week and a half for my EFS backup :'(
We will be waiting from u for the new combination file when out bro, our hope are hinged on u!
No one is coming up with any method about the bootloader binary 2 for the Samsung S7 G930FD...?
Sent from my SM-G930F using Xposed Modules
FRP can be done so easy from any GSM tool by combination, anyone need it it will be my pleasure to help
Alright so I guess I'm stuck in a situation. I recently updated my firmware to Sprint's latest one (CRD4) and I didn't realize that the bootloader was rev3 and I tried flashing a lower bootloader version. I got a fail in odin and now my phone just reboots to recovery (it doesn't fully enter recovery either, it just says error or installing update). I've tried flashing:
G955USQS2BQL1 (Sprint)
G955USQU2CRC5 (Sprint)
G955USQU3CRD4 (T-Mobile)
and it still says fail. I have no idea what else to do next besides taking it to Sprint but I cracked the corner of my screen and I'm sure they will charge me to fix it. Any help would be greatly appreciated, thanks.
Unfortunately you are stuck on it. In the disclaimer is said you would not be able to downgrade to a previous version for security reasons. You will probably have to wait till the new Sprint version is available to download.
esjames said:
Unfortunately you are stuck on it. In the disclaimer is said you would not be able to downgrade to a previous version for security reasons. You will probably have to wait till the new Sprint version is available to download.
Click to expand...
Click to collapse
How long do you think that will take since this is my only phone?
You will have to wait until an Odin flashable package of CRD4 or another bootloader 3 firmware becomes available. Without a complete BL3 system flash you are SOL
I think I'll hold off on the OTA update until I hear some safe reports
LordAbolition said:
Alright so I guess I'm stuck in a situation. I recently updated my firmware to Sprint's latest one (CRD4) and I didn't realize that the bootloader was rev3 and I tried flashing a lower bootloader version. I got a fail in odin and now my phone just reboots to recovery (it doesn't fully enter recovery either, it just says error or installing update). I've tried flashing:
G955USQS2BQL1 (Sprint)
G955USQU2CRC5 (Sprint)
G955USQU3CRD4 (T-Mobile)
and it still says fail. I have no idea what else to do next besides taking it to Sprint but I cracked the corner of my screen and I'm sure they will charge me to fix it. Any help would be greatly appreciated, thanks.
Click to expand...
Click to collapse
There is now an ODIN file for bootloader 3 CRD4. You can find the link in the Oreo Beta thread. It should fix your phone
Nitefire77 said:
There is now an ODIN file for bootloader 3 CRD4. You can find the link in the Oreo Beta thread. It should fix your phone
Click to expand...
Click to collapse
Thank you for telling me. It gives me an error though when I try to download it from SamFirm
Code:
Checking firmware for SM-G955U/SPR/G955USQU3CRD4/G955UOYN3CRD4/G955USQU3CRD4/G955USQU3CRD4
Error: Could not send BinaryInform. Status code 200/400
Request was invalid. Are you sure the input data is correct?
Update: Nvm found it. Had to go to the last page
Do you have z3x?
You dont need z3x to flash the tmobile variant, but it makes it far simpler. Which version of odin are you using? If its the prince comsey you will more than likely get the mismatch error.
LordAbolition said:
Thank you for telling me. It gives me an error though when I try to download it from SamFirm
Code:
Checking firmware for SM-G955U/SPR/G955USQU3CRD4/G955UOYN3CRD4/G955USQU3CRD4/G955USQU3CRD4
Error: Could not send BinaryInform. Status code 200/400
Request was invalid. Are you sure the input data is correct?
Update: Nvm found it. Had to go to the last page
Click to expand...
Click to collapse
I'm in the same situation as you ... but instead i have the s8 not the s8+ .... been searching like crazy but only see the odin files for s8+ ... do you by any chance know where I can get the files for the s8? Thanks in advance if you can help.
SprintBama said:
I'm in the same situation as you ... but instead i have the s8 not the s8+ .... been searching like crazy but only see the odin files for s8+ ... do you by any chance know where I can get the files for the s8? Thanks in advance if you can help.
Click to expand...
Click to collapse
No worries. I fixed the situation. Thanks for reading!
I am clarifying this, this is s8 plus now stuck on rev3? I got an s8 and went to another forum thread and was told this isn't true. I am stuck on rev3. FYI, updato has the new s8plus firmware if you haven't got it already.
Hi all,
I'm having a nightmare of a time with my Galaxy S7... For some unknown reason I decided to root my phone about 2 months ago using CF Auto Root.. worked great.. This morning, was having bad lag issues, so I restarted the phone.. as soon as the Samsung logo came up, I got a red message at the top of the screen saying "Custom Binary locked by FRP".. kind of freaked out and booted the phone into Recovery mode.. wiped Cache and wiped phone (to go back to factory setting I guess).. restarted... since then, I had no boot.. it did loop for a while as I was trying to charge the phone.. but that's it.
Now, the only way the phone will power on is if I plug it into my computer in Download Mode. I am trying to flash the ROM, custom or stock, but Odin fails almost as soon as it starts the sboot.bin and the phone screen shows "SW REV. CHECK FAIL (BOOTLOADER) DEVICE: 6, BINARY: 1".. Also, When I try to power on the phone, it HAS to be plugged in to my computer or charger cable and it just loops with a message at the top of the screen.
I can't do anything with this phone and cant find any solutions online... please help! :crying:
PM me for images of all screens please
I had the some problem while playing with my handset I switched off OEM unlock for some reason under developer option..
Next time i reset my handset it stuck on that warning
You need to download combination file, flash it with odin, then unlock developer mode, toggle OEM unlock, than flash back your current firmware, or if you have full twrp back up restore it
JayMor81 said:
Hi all,
I'm having a nightmare of a time with my Galaxy S7... For some unknown reason I decided to root my phone about 2 months ago using CF Auto Root.. worked great.. This morning, was having bad lag issues, so I restarted the phone.. as soon as the Samsung logo came up, I got a red message at the top of the screen saying "Custom Binary locked by FRP".. kind of freaked out and booted the phone into Recovery mode.. wiped Cache and wiped phone (to go back to factory setting I guess).. restarted... since then, I had no boot.. it did loop for a while as I was trying to charge the phone.. but that's it.
Now, the only way the phone will power on is if I plug it into my computer in Download Mode. I am trying to flash the ROM, custom or stock, but Odin fails almost as soon as it starts the sboot.bin and the phone screen shows "SW REV. CHECK FAIL (BOOTLOADER) DEVICE: 6, BINARY: 1".. Also, When I try to power on the phone, it HAS to be plugged in to my computer or charger cable and it just loops with a message at the top of the screen.
I can't do anything with this phone and cant find any solutions online... please help! :crying:
PM me for images of all screens please
Click to expand...
Click to collapse
This problem appears on the forum over and over. Its a direct result of not understanding what type of S7 you have and what you need to do before modification.
The error you have in Odin means the firmware you are trying to flash is older than the bootloader file on your device. You can never downgrade a bootloader only upgrade.
In your case you need to flash a firmware version 6 or above for your device. So if you have a branded T Mobile for example you will need to download and flash T Mobile firmware version 6 or above. The firmware must also be for your region where you live.
The FRP lock is because you didn't sign out of, or remove the Google account on the device before modification. Its a security feature. It will still appear after you've flashed firmware but as long as you know the email and password the phone will start fine.
cooltt said:
This problem appears on the forum over and over. Its a direct result of not understanding what type of S7 you have and what you need to do before modification.
The error you have in Odin means the firmware you are trying to flash is older than the bootloader file on your device. You can never downgrade a bootloader only upgrade.
In your case you need to flash a firmware version 6 or above for your device. So if you have a branded T Mobile for example you will need to download and flash T Mobile firmware version 6 or above. The firmware must also be for your region where you live.
The FRP lock is because you didn't sign out of, or remove the Google account on the device before modification. Its a security feature. It will still appear after you've flashed firmware but as long as you know the email and password the phone will start fine.
Click to expand...
Click to collapse
Dammit.. I tried to put as much detail as possible in there lol.. obviously I forgot some.. My mistake the Galaxy s7 that I am using is a Rogers Mobile (Canada) SM-G930W8. As for not signing out before modification, omfg, that makes perfect sense.. didn't even think of doing that before rooting.. I appreciate the help!! I will give this a go and see what outcome I get.. Thanks!
[/COLOR]That was nice of you to respond so helpfully, despite you having seen the scenario posted over and over.
cooltt said:
This problem appears on the forum over and over. Its a direct result of not understanding what type of S7 you have and what you need to do before modification.
The error you have in Odin means the firmware you are trying to flash is older than the bootloader file on your device. You can never downgrade a bootloader only upgrade.
In your case you need to flash a firmware version 6 or above for your device. So if you have a branded T Mobile for example you will need to download and flash T Mobile firmware version 6 or above. The firmware must also be for your region where you live.
The FRP lock is because you didn't sign out of, or remove the Google account on the device before modification. Its a security feature. It will still appear after you've flashed firmware but as long as you know the email and password the phone will start fine.
Click to expand...
Click to collapse
Can't make or receive calls
Please I need help my I rooted my S7 (flat) flashed the original OS with odin Installed Twrp flashed Andriod 9 and since then I can't make or receive calls wifi seems fine. Someone please come to my rescue:crying:
Cesilina said:
Please I need help my I rooted my S7 (flat) flashed the original OS with odin Installed Twrp flashed Andriod 9 and since then I can't make or receive calls wifi seems fine. Someone please come to my rescue:crying:
Click to expand...
Click to collapse
The S7 didn't receive Android 9 so the ROM is a custom one. Any issues with custom ROM's should be asked on the ROM thread itself where you got the ROM from. It's quite normal for custom ROM'S to have bugs.
You can try flashing the ROM (Android 9 Pie) again to see if it works. If not there are several different A9 ROM's to choose from.
cooltt said:
The S7 didn't receive Android 9 so the ROM is a custom one. Any issues with custom ROM's should be asked on the ROM thread itself where you got the ROM from. It's quite normal for custom ROM'S to have bugs.
You can try flashing the ROM (Android 9 Pie) again to see if it works. If not there are several different A9 ROM's to choose from.
Click to expand...
Click to collapse
Thank you for reply. I have tried atleast 4 different custom ROMs but to avail
Cesilina said:
Thank you for reply. I have tried atleast 4 different custom ROMs but to avail
Click to expand...
Click to collapse
Do you still have an imei number listed in settings?
Can't make or receive calls
cooltt said:
Do you still have an imei number listed in settings?
Click to expand...
Click to collapse
Yes please I still have an IMEI number
Tried to root using a method that involved 4 odin files which I guess is most methods nowadays. Im used to old root methods were there is only one file I need to flash so I only flashed one file and it failed I don't have snapdragon chip set I don't think I googled my IMEI number and it said I didn't. Now my phone is stuck in Bootloop I tried flashing stock firmware I got from Sammobile and other sites making sure it was the latest version and it didn't work. I went into Maintenance recovery and tried factory reset it gave me the erasing screen but would still not boot up. I can still enter download mode and recovery but nothing seems to work please help.
Tried flashing ENG boot although I have no clue what it is but it made no difference. Tried also flashing TWRP I got error: SECURE CHECK FAIL: recovery. I did some research and apparently I might have a locked bootloader.
I just want to boot into my phone whatever it takes please help
Last OS update I got was either may or june
IMEI: 358166076487955
If your phone is model SM-G935V, aka Verizon, you have a Snapdragon chip. Therefore, there is no TWRP. And, depending on the bootloader version you had prior to attempting root, you might be out of luck.
What was your firmware version BEFORE you attempted root? (For example, mine is: G935VVRS4CRI1). The 5th digit from the right is the important one.
SkylineDriver said:
If your phone is model SM-G935V, aka Verizon, you have a Snapdragon chip. Therefore, there is no TWRP. And, depending on the bootloader version you had prior to attempting root, you might be out of luck.
What was your firmware version BEFORE you attempted root? (For example, mine is: G935VVRS4CRI1). The 5th digit from the right is the important one.
Click to expand...
Click to collapse
Thank you for your help but i figured it out. Finally found my specific firmware and got it to boot. the thing is I googled my IMEI and it says I dont have a snapdragon I have an exynos chipset. Did some more digging and it confirmed I had an exynos chipset. Problem is fixed though thank you for the help.
If you have Exynos then it is not a Verizon branded phone. Your phone might be working on the Verizon network, but....
Either way, thanks for the update. Glad you got it sorted.