Database Info

Stuck at Powered by Android please help SM-N915G

My Fried gave this phone to me (SM-N915G) which is stuck at Powered by Android, and told me to fix it.
He said that when he update to MM from LP without KIES or Odin, the phone suddenly restarted and stuck there getting HOT
He had no experiece to repair it so he asked me to fix it.
So for 3 days lately, i have tried many ways to fix it but wihout any progress, as follow :
1. Flashing Official MM wby using Odin -> still stuck
2. Downgrading Flash Official LP using Odin -> still stuck
3. Installed TWRP, and flasing CFW Micky387_MM_V3.0 for 915F/FY/G (flashing Bootloader and modem as required) -> still stuck with set warranty bit : kernel
4. After Flashing Micky CFW and Failde, i try to flash Emotion Kernel -> still stuck with Kernel is Seandroid Enforcing
5. Redoing Flash Micky CFW with other CSC -> Still Stuck (even i tried with 915F and 915FY as in the aroma installer)
6. Never failed during flash procedure with Odin or TWRP, everything is smooth
7. When stuck, the device is getting Hot slowly but and when left as long as 15 minutes, the HH is getting HOT (TWRP read 72 degree at most)
**Update
8. Tried using Official SmartSwitch sucessfully but the result is still the same -> Still Stuck and getting hot as usual T.T
Last Download Mode status is :
Odin Mode (High Speed)
Product name: SM-N915G
Current Binary: Samsung Official
System Status: Official
Reactivation Lock: Off
Knox warranty void: 0x1 (2)
Quallcomm secureboot : Enable (CSB)
RP SWREV: S1, T1, R1, A1, P1
Secure Download: Enable
UDC START
I am now thinking, should i flash another Kernel or PIT or Bootloader? but i still cant decide what to do next to revive this Phone
Please help, any suggestion is greatly appreciated, thank you.

Please give some help, thank you.

Help Please anyone?
This is Hard Brick or Soft Brick?
Any suggestion or Opinion please
Thank you

wingz17 said:
Help Please anyone?
This is Hard Brick or Soft Brick?
Any suggestion or Opinion please
Thank you
Click to expand...
Click to collapse
Have you tried a reinstall using KIES?

The Radius Kid said:
Have you tried a reinstall using KIES?
Click to expand...
Click to collapse
Yes i have try to recover but not using KIES, but using smartswitch...
Is it diffrent by using KIES or SmartSwitch?
Thank you.

wingz17 said:
Yes i have try to recover but not using KIES, but using smartswitch...
Is it diffrent by using KIES or SmartSwitch?
Thank you.
Click to expand...
Click to collapse
I can tell you that Kies and NOT Kies 3 was what worked for me when I downloaded/installed Marshmallow from Samsung's website.
Figure that one out.
That was also using a 64 bit version of Windows 7 Pro.

The Radius Kid said:
I can tell you that Kies and NOT Kies 3 was what worked for me when I downloaded/installed Marshmallow from Samsung's website.
Figure that one out.
That was also using a 64 bit version of Windows 7 Pro.
Click to expand...
Click to collapse
Thank you for the suggestion,
I will try that one out and let you know.

wingz17 said:
Thank you for the suggestion,
I will try that one out and let you know.
Click to expand...
Click to collapse
The Radius Kid said:
I can tell you that Kies and NOT Kies 3 was what worked for me when I downloaded/installed Marshmallow from Samsung's website.
Figure that one out.
That was also using a 64 bit version of Windows 7 Pro.
Click to expand...
Click to collapse
Sorry For the long response, i have tried flasing using KIES but still stuck on the android, and no progress.
Right now i am run out of option, please help, thank you.

wingz17 said:
Sorry For the long response, i have tried flasing using KIES but still stuck on the android, and no progress.
Right now i am run out of option, please help, thank you.
Click to expand...
Click to collapse
I'm going to guess that you've tried installing MM using Kies directly from Sammobile?
If so,have you tried turning off your computer's antivirus when you download/install?
It sounds like the bootloader is looking for something and can't find it.....kind of like what happened to me when I totally ripped KNOX out of my phone.
Restore time!
Good thing I did CWM backups.
In your case,your computer's anti virus could be seeing something in the download and ripping it out.
I've seen my browsers do that when I download stuff....pain in the....
Have you tried a different battery?
Maybe a search of the forums to see if anyone else has had this problem and solved it?
I kind of remember seeing something like this a while back.

The Radius Kid said:
I'm going to guess that you've tried installing MM using Kies directly from Sammobile?
If so,have you tried turning off your computer's antivirus when you download/install?
It sounds like the bootloader is looking for something and can't find it.....kind of like what happened to me when I totally ripped KNOX out of my phone.
Restore time!
Good thing I did CWM backups.
In your case,your computer's anti virus could be seeing something in the download and ripping it out.
I've seen my browsers do that when I download stuff....pain in the....
Have you tried a different battery?
Maybe a search of the forums to see if anyone else has had this problem and solved it?
I kind of remember seeing something like this a while back.
Click to expand...
Click to collapse
Thank you for the response,
I was using KIES 2.64 that downloaded from Samsung website to fix the phone as your suggestion (tools->firmware upgrade and initialisation) but still fail to fix it.
Nope, the antivirus still active when KIES download the FW and Flash it into the phone, but it is new to me that antivirus will intercept ongoing dowloaded files, if so i think the antivirus will give some notification or warning about the content of the file that being downloaded and in my case, my antivirus is still cool and no notification whatsoever.
The bad thing is i do not have any cwm backup and since this is my friend phone and not mine, well... we dont have any backup for this phone.
Regarding the battery, i admit that i havent try other battery, since i dont see any connecton between it, in my opinion, the phone works well, the charging animation working, and no sign of weak battery... but i will try to do it if i can get some other battery
I have surfed many forums and websites, but almost 90% can be fixed with simple flashing from odin or just by clearing up cache and data from recovery.
Other that that, wither, no one respond to the problem, or just some discussion without conclusion, really frustrating.
I even go further to read about android booting sequence to identify whats wrong with the boot sequence, but still confused...
But i have some question if you would to answer :
1 . Stuck at Android logo, bootloader or kernel problem?
2 . Is it possible that one of the mainboard chip that have some part in booting process is malfunctioning? But if so, the phone will be dead bricked right?
3. How about the booting process is halted due some hardware failure? ex : some chip (other than chip that have part in booting process) is bad and so the bootloader init is halted
4. The Worst guess, is it possible that the phone is fake? (the serial number behind the baterry is accepted by kies though)
Thank you very much, you are the only one who still response to my problem. :good:

As it seems you use the wrong Bootlaoder. Is his phone N915P or N915G? When you flash N915G Bootloader to N915P, it will not boot but the bootloader will work correctly. Try to flash the N915P bootloader.
I have N915FY phone but did not know first if I had N915F or FY. I flashed the N915F bootloader version, which flashed successfully, but was not booting. Bootloader said that my phones model is N915F. After flashing the FY Bootloader version, it successfully booted to system.

Bordo_Bereli51 said:
As it seems you use the wrong Bootlaoder. Is his phone N915P or N915G? When you flash N915G Bootloader to N915P, it will not boot but the bootloader will work correctly. Try to flash the N915P bootloader.
I have N915FY phone but did not know first if I had N915F or FY. I flashed the N915F bootloader version, which flashed successfully, but was not booting. Bootloader said that my phones model is N915F. After flashing the FY Bootloader version, it successfully booted to system.
Click to expand...
Click to collapse
Thank you for the Response,
First, his phone is N915G (according to the box and the information in the battery compartment)
(Really sorry for the mistake i made at the thread title)
And regarding bootloader, that is also my concern at first, i think maybe i was flasing wrong region and bootloader, and so i search the way to find out the real version of the phone, but after trying many ways described on the net (by imei or serial number) , i still cannot found out the way.
But one instance when i try using KIES, and KIES asked for the version and serial number when device upgrade and initialisation, i entered the exact version and serial number that is found behind the phone in battery compartment. KIES immediately confirms that the version and serial number is valid, (i still wonder though, is KIES check it online at Samsung server or there are some serial number database embedded in the KIES) and continue to run trough the official fw download and installation by KIES but at the end still no success.
Is it possible that the version and serial number is wrong ? if so, how to determine the correct one?
and is it safe to try flasing another bootloader?
Thank you very much

Hello, there is no bootloader related to serial number or something. There are different bootloaders for different models and android version. When you flash MM-Version, you need to be sure that you use the right bootloader and baseband files for MM. If you flash different region-locked firmware/bootloader, it will not affect btw. not solve the boot-stuck problem.
http://samsung-updates.com/device/?id=SM-N915G Try to flash 6.0.1 firmware that is related to your region if you still want to try to flash different region-firmware.
Maybe download the XSA 6.0.1 Firmware with the pit file XSA http://gsm-firmware.com/index.php?a=browse&b=file-info&id=15892.
Then flash XSA 6.0.1 and TBLTE_SEA_XSA.pit together in odin. Under Odin 3 V3.12 ticke the re-partition at option-tab and select TBLTE_SEA_XSA.pit under pit-tab.

Bordo_Bereli51 said:
Hello, there is no bootloader related to serial number or something. There are different bootloaders for different models and android version. When you flash MM-Version, you need to be sure that you use the right bootloader and baseband files for MM. If you flash different region-locked firmware/bootloader, it will not affect btw. not solve the boot-stuck problem.
http://samsung-updates.com/device/?id=SM-N915G Try to flash 6.0.1 firmware that is related to your region if you still want to try to flash different region-firmware.
Maybe download the XSA 6.0.1 Firmware with the pit file XSA http://gsm-firmware.com/index.php?a=browse&b=file-info&id=15892.
Then flash XSA 6.0.1 and TBLTE_SEA_XSA.pit together in odin. Under Odin 3 V3.12 ticke the re-partition at option-tab and select TBLTE_SEA_XSA.pit under pit-tab.
Click to expand...
Click to collapse
Thanks for the reply!
Although there is no bootloader related to serial number, but if we put the serial number in KIES, it will identify what CSC and region, which can be use as a guide to choose the correct FW or let KIES do the Flashing according to the inputted serial number, and as long as the serial number is correct one, that is my opinion but please CMIIW.
When flashing MM, if i use the MM that has been downloaded, the bootloader and baseband is included in the MM image right? or shouuld i flash it separately?
i have tried your suggestion but with no sucess, i have dowloaded the PIT and the FW, flash it trough odin which was sucess, but still stuck.
I do not tick auto restart at Odin, so i manually restart the phone, but i encounter an event which at 20% installing system update (below the greed droid guy) the progress bar is vanished and replaced with erasing, and after that the phone stuck again at the same spot.
Do you have any idea why?
Thank you very much.

Just thinking, should i erase the NAND in ODIN?
If so, how to restore it?
I think that if i backup the NAND using custom recovery and restore it later, it just bring back the same problem, if the NAND causing all this.
Do anyone have some NAND backup that i could use? or any other suggestion?
Thank you

Can you boot to recovery? if yes, try to wipe data and cache.
If it still not working, try to backup your efs with a custom recovery (ex. TWRP), or better the entire System like data, system, boot, efs, modem and save it to your computer.
After saving the backup, try to flash the firmware with pit file while checked NAND erase all.
When its finished and your device boots up, you can flash back your custom recovery and recover only the efs-partition.
If its not working, then there is maybe problems with your eMMC. But be aware using nand erase all. It is the last riskfully option left after trying several things.
I have a backup of my resurrection rom. If you want it I can upload it.

Custom Binary Blocked By FRP Lock - after regular boot

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

S8+ G955FXXU2CRED with Bootloader V2 - options for flashing, downgrade, FRP Unlock?

Short question: how can I downgrade or FRP unlock a S8+ G955F that is FRP locked and on very recent firmware?
Here are the details:
I am trying to assist a family member with a Galaxy S8+ (SM-G955F) that they have just purchased online. When purchasing it they were not told that FRP lock is on (FRP LOCK: ON) and OEM lock is on (OEM LOCK: ON). It was running Bootloader v2 on very recent stock firmware. It has been successfully flashed with BL_G955FXXU2CRED and AP_G955FXXU2CRED...
It was on G955FXXU2CRED firmware. I was able to successfully able to flash the Combination ROM COMBINATION_FA70_G955FXXU2ARE1 (full name COMBINATION_FA70_G955FXXU2ARE1_CL12792727_QB18097821_REV00_user_mid_noship.tar)
With combination rom, it seemed that I could enable USB Debugging, and also follow the steps for *#0808# IME to enable the appropriate mode for adb codes to be entered. I was able to find the device with 'adb devices', and I thought that the FRP unlock codes on the command line worked. But after re-flashing to the current Stock Firmware again, FRP lock was still there.
It seems I need to downgrade to Nougat 7.0, but I am on Bootloader V2. Odin identifies it by a FAIL with binary not matched (2 vs 1). So it seems that if I could get a method to keep Bootloader V2 and install Stock Firmware for Android 7.0 Nougat, I would be halfway there to fixing the FRP problem. However, I can't find any firmware or ROMs for G955F that includes Bootloader V2. This is identified by a U2 in the firmware name, like: G955FXXU2CRED . Is there a way to keep the BL Bootloader V2 but install AP ROM from Nougat?
I have spent many hours on this so far, and I just wanted to say thank you to all you guys who are helping on XDA, I really appreciate it. I have read about 7 day waiting periods for OEM UNLOCK but I don't see how it applies, as I can't do anything aside from use Combination ROM, use Odin, or go to the FRP locked FW which seems to be a dead end?
If there was a reliable method for rooting this G955F device with this G955FXXU2CRED firmware, I would be open to trying it.

details
Another note: AP SW Rev is identified as B:2 K:1 S:1

I don't think once a phone has the boot loader CRED, that the phone can be downgraded. Hope I am wrong.

JeffDC said:
I don't think once a phone has the boot loader CRED, that the phone can be downgraded. Hope I am wrong.
Click to expand...
Click to collapse
I think you are right. The combination ROM seems to built on selinux version 7.
I think I need to root with twrp. But first I need to enable OEM unlock. I'm not sure if that will be possible with combination ROM or if I should flash latest stock and then wait 7 days??

same problem here... If an solution available pls write here

anonan said:
I think you are right. The combination ROM seems to built on selinux version 7.
I think I need to root with twrp. But first I need to enable OEM unlock. I'm not sure if that will be possible with combination ROM or if I should flash latest stock and then wait 7 days??
Click to expand...
Click to collapse
Flashing stock rom and waiting 7 days would be the safe option.
I am not exactly sure what you are trying to achieve.
https://www.samsung.com/us/support/frp/

anonan said:
I think you are right. The combination ROM seems to built on selinux version 7.
I think I need to root with twrp. But first I need to enable OEM unlock. I'm not sure if that will be possible with combination ROM or if I should flash latest stock and then wait 7 days??
Click to expand...
Click to collapse
I think I read someone on CarHDRom who flashed the rom via TWRP, and then when the phone booted into system for the first time at setting up, they changed the date to 8 days earlier, and when the phone setup was completed and booted into system, the OEM unlock was available.
Re: CRED I believe once it has been installed on a phone, you can not go back to a previous version (pre CRED).

JeffDC said:
I think I read someone on CarHDRom who flashed the rom via TWRP, and then when the phone booted into system for the first time at setting up, they changed the date to 8 days earlier,.
Click to expand...
Click to collapse
I wonder if I can do this date trick with combination FW to enable OEM unlock.

anonan said:
I wonder if I can do this date trick with combination FW to enable OEM unlock.
Click to expand...
Click to collapse
It seems there are a few solutions to frp if you can selectively restore flash files. It looks like Samsung tool Pro can do this, but is there any free adb method?
http://forum.gsmhosting.com/vbb/f453/new-solution-remove-frp-s8-plus-sm-g955f-last-security-2422242/
Especially this http://forum.gsmhosting.com/vbb/f453/g955f-rev-2-frp-100-no-box-2417931/

Hi, could you send me a link of the combination firmware please Can't find it anywhere My email address is [email protected] I currently have similar experience of yours I thought everythings gonna be okay but it was too good to be true Help
anonan said:
Short question: how can I downgrade or FRP unlock a S8+ G955F that is FRP locked and on very recent firmware?
Here are the details:
I am trying to assist a family member with a Galaxy S8+ (SM-G955F) that they have just purchased online. When purchasing it they were not told that FRP lock is on (FRP LOCK: ON) and OEM lock is on (OEM LOCK: ON). It was running Bootloader v2 on very recent stock firmware. It has been successfully flashed with BL_G955FXXU2CRED and AP_G955FXXU2CRED...
It was on G955FXXU2CRED firmware. I was able to successfully able to flash the Combination ROM COMBINATION_FA70_G955FXXU2ARE1 (full name COMBINATION_FA70_G955FXXU2ARE1_CL12792727_QB18097821_REV00_user_mid_noship.tar)
With combination rom, it seemed that I could enable USB Debugging, and also follow the steps for *#0808# IME to enable the appropriate mode for adb codes to be entered. I was able to find the device with 'adb devices', and I thought that the FRP unlock codes on the command line worked. But after re-flashing to the current Stock Firmware again, FRP lock was still there.
It seems I need to downgrade to Nougat 7.0, but I am on Bootloader V2. Odin identifies it by a FAIL with binary not matched (2 vs 1). So it seems that if I could get a method to keep Bootloader V2 and install Stock Firmware for Android 7.0 Nougat, I would be halfway there to fixing the FRP problem. However, I can't find any firmware or ROMs for G955F that includes Bootloader V2. This is identified by a U2 in the firmware name, like: G955FXXU2CRED . Is there a way to keep the BL Bootloader V2 but install AP ROM from Nougat?
I have spent many hours on this so far, and I just wanted to say thank you to all you guys who are helping on XDA, I really appreciate it. I have read about 7 day waiting periods for OEM UNLOCK but I don't see how it applies, as I can't do anything aside from use Combination ROM, use Odin, or go to the FRP locked FW which seems to be a dead end?
If there was a reliable method for rooting this G955F device with this G955FXXU2CRED firmware, I would be open to trying it.
Click to expand...
Click to collapse

anonan said:
It seems there are a few solutions to frp if you can selectively restore flash files. It looks like Samsung tool Pro can do this, but is there any free adb method?
http://forum.gsmhosting.com/vbb/f453/new-solution-remove-frp-s8-plus-sm-g955f-last-security-2422242/
Especially this http://forum.gsmhosting.com/vbb/f453/g955f-rev-2-frp-100-no-box-2417931/
Click to expand...
Click to collapse
It worked! Flashed the Comb file with Odin and do what he does in the video, then flashed the Stock G955FXXU2CRED and now its unlocked I dont know how i did this but its worked!

darknagel said:
It worked! Flashed the Comb file with Odin and do what he does in the video, then flashed the Stock G955FXXU2CRED and now its unlocked I dont know how i did this but its worked!
Click to expand...
Click to collapse
Excellent.

I still can't get this to work. Have you purchased Samsung tool Pro to do the flashing of individual boot files? What version?

Hi there. I already bypassed the frp.. If you need. Hp with android 8.0 even with the binary 2. I have some comb files and working stock roms through odin. Feel free to pm me via my email [email protected]. Thanks!

how
darknagel said:
It worked! Flashed the Comb file with Odin and do what he does in the video, then flashed the Stock G955FXXU2CRED and now its unlocked I dont know how i did this but its worked!
Click to expand...
Click to collapse
Hi
Can you let me know the steps as i am trying but i cant flash the stock firmware after the factory binary
thx

oz_ezekiel said:
Hi
Can you let me know the steps as i am trying but i cant flash the stock firmware after the factory binary
thx
Click to expand...
Click to collapse
Download latest odin and try again. I too got stuck in similar situation. Realised the issue is due to Odin. If you are using latest and encountered this error, try one version earlier.

I too can confirm that the combination-ROM works like a charm with odin. FRP kinda unlocked itself

Combination Firmware A8 (2018) SW rev check fails device 3 binary 2.

I know this should be in Rom,kernels,rev. I'm a junior member so I can't post their yet
So I've recently rooted my phone. I got too excited and tried installing a custom boot animation that screwed up my phone and it couldn't shut down only restart.
Then I had an idea to wipe the system through TWRP and I accidentally deleted everything (Wiped internal storage) so download mode was blank. Then I tried installing stock Rom but I extracted it, removed the stock recovery.img.lz4 and replaced it with the TWRP Recovery. For some weird reason the firmware was acting weird with T mobile roaming and stuff that wasn't supposed to be there cause I'm not a t mobile customer. Then I just flashed stock Rom (Augaust security patch) with Odin. Aaand I got RMM Locked again :crying::crying:
I thought flashing combination firmware again would allow me to access the OEM unlock option and flash TWRP again.
When I tried to flash I got an error SW rev check fails device 3 binary 2. If anyone could help me I would really appreciate it. Also if anyone knows why I got the T mobile stuff after I did the TWRP thing (out of curiosity) I would like to know. Please respond.

DeadRatGames said:
I know this should be in Rom,kernels,rev. I'm a junior member so I can't post their yet
So I've recently rooted my phone. I got too excited and tried installing a custom boot animation that screwed up my phone and it couldn't shut down only restart.
Then I had an idea to wipe the system through TWRP and I accidentally deleted everything (Wiped internal storage) so download mode was blank. Then I tried installing stock Rom but I extracted it, removed the stock recovery.img.lz4 and replaced it with the TWRP Recovery. For some weird reason the firmware was acting weird with T mobile roaming and stuff that wasn't supposed to be there cause I'm not a t mobile customer. Then I just flashed stock Rom (Augaust security patch) with Odin. Aaand I got RMM Locked again :crying::crying:
I thought flashing combination firmware again would allow me to access the OEM unlock option and flash TWRP again.
When I tried to flash I got an error SW rev check fails device 3 binary 2. If anyone could help me I would really appreciate it. Also if anyone knows why I got the T mobile stuff after I did the TWRP thing (out of curiosity) I would like to know. Please respond.
Click to expand...
Click to collapse
It seems that your filmware is corrupt.
Which bootloader binary are you on, binary 2 or 3, Nougat or Oreo?
Remember that if you have binary 3 you cannot downgrade to binary 2.
And don't use the combination rom anymore because you have to know what you're doing its risky.
I can advise you to do a fresh install of the official country filmware from out of the box, and after that update to the latest filmware version, and a big chance to get rid of RMM prenormal state, with oem-unlock back.
If you're on binary 2, just flash an official filmware from your country before the August security patch, after that update it again to the latest version.

solamente said:
It seems that your filmware is corrupt.
Which bootloader binary are you on, binary 2 or 3, Nougat or Oreo?
Remember that if you have binary 3 you cannot downgrade to binary 2.
And don't use the combination rom anymore because you have to know what you're doing its risky.
I can advise you to do a fresh install of the official country filmware from out of the box, and after that update to the latest filmware version, and a big chance to get rid of RMM prenormal state, with oem-unlock back.
If you're on binary 2, just flash an official filmware from your country before the August security patch, after that update it again to the latest version.
Click to expand...
Click to collapse
Thanks for responding, I'm currently on binary 3 on android Oreo August security patch.
What do you mean by a fresh install from out of the box. Like Download the latest version from updato?
I apologise if I seem a little clueless lol.

DeadRatGames said:
Thanks for responding, I'm currently on binary 3 on android Oreo August security patch.
What do you mean by a fresh install from out of the box. Like Download the latest version from updato?
I apologise if I seem a little clueless lol.
Click to expand...
Click to collapse
What I meant is the first official filmware you had when the phone was bought,and if you were on binary 2, but that doesn't matter now you're on binary 3.
Now you have to flash the official filmware from your country, it must be a binary 3 filmware because downgrading will not work.
After that you have to do jailtime for 168 hours untill oem unlock is gonna appear again.
Do not restart the phone or disconnect the network at this time.

solamente said:
What I meant is the first official filmware you had when the phone was bought,and if you were on binary 2, but that doesn't matter now you're on binary 3.
Now you have to flash the official filmware from your country, it must be a binary 3 filmware because downgrading will not work.
After that you have to do jailtime for 168 hours untill oem unlock is gonna appear again.
Do not restart the phone or disconnect the network at this time.
Click to expand...
Click to collapse
Do I really need to wait 168 hours lol?

DeadRatGames said:
Do I really need to wait 168 hours lol?
Click to expand...
Click to collapse
Unfortunately you do with the 1 august patch, if you can find a previous official filmware, for example april, may, june or juli patch you can do the trick to set back the date and time 7 days and get oem unlock back.
But this does not work anymore with the august patch or later, that means you have to wait 7 days.

solamente said:
Unfortunately you do with the 1 august patch, if you can find a previous official filmware, for example april, may, june or juli patch you can do the trick to set back the date and time 7 days and get oem unlock back.
But this does not work anymore with the august patch or later, that means you have to wait 7 days.
Click to expand...
Click to collapse
How do I downgrade though?

DeadRatGames said:
How do I downgrade though?
Click to expand...
Click to collapse
At this time its impossible to downgrade from a binary 3 towards 2 or from 2 to 1.
You can only upgrade, Samsung has blocked the downgrading from a higher to a lower binary, therefore it is useless to try it with Odin, it won't succeed.
Maybe someone else knows a way around to downgrade, but I don't.

DeadRatGames said:
I know this should be in Rom,kernels,rev. I'm a junior member so I can't post their yet
So I've recently rooted my phone. I got too excited and tried installing a custom boot animation that screwed up my phone and it couldn't shut down only restart.
Then I had an idea to wipe the system through TWRP and I accidentally deleted everything (Wiped internal storage) so download mode was blank. Then I tried installing stock Rom but I extracted it, removed the stock recovery.img.lz4 and replaced it with the TWRP Recovery. For some weird reason the firmware was acting weird with T mobile roaming and stuff that wasn't supposed to be there cause I'm not a t mobile customer. Then I just flashed stock Rom (Augaust security patch) with Odin. Aaand I got RMM Locked again :crying::crying:
I thought flashing combination firmware again would allow me to access the OEM unlock option and flash TWRP again.
When I tried to flash I got an error SW rev check fails device 3 binary 2. If anyone could help me I would really appreciate it. Also if anyone knows why I got the T mobile stuff after I did the TWRP thing (out of curiosity) I would like to know. Please respond.
Click to expand...
Click to collapse
1. You didn't posted in the wrong section. This one is the correct one, the one where you wanted to post is reserved to ROMs, kernels and other projects.
2. Modifying Official firmwares is a bad idea if you don't know how to do it. Seems also you downloaded the wrong firmware for your phone.
3. Flashing Combination firmware is useless since OEM Toggle is still enabled (you said you were rooted so I suppose yes). RMM flag is still stored in RPMB and doesn't gets resetted by flashing that factory fw, to set RMM back to Normal you need to flash the full stock firmware for your country and wait the classic 168h countdown.
4. The "SW REV. CHECK FAIL (BOOTLOADER) DEVICE: x, BINARY: x" is caused because you're trying to flash a firmware with a lower rev. than the one installed in your phone. You need to flash a firmware with the same or higher rev (In this case, you need a XXU3/XXS3 or higher fw). Forget to flash a fw with a lower rev since RP fuse prevents you to do it (if you force install the bl via TWRP you get an hardbrick)

BlackMesa123 said:
1. You didn't posted in the wrong section. This one is the correct one, the one where you wanted to post is reserved to ROMs, kernels and other projects.
2. Modifying Official firmwares is a bad idea if you don't know how to do it. Seems also you downloaded the wrong firmware for your phone.
3. Flashing Combination firmware is useless since OEM Toggle is still enabled (you said you were rooted so I suppose yes). RMM flag is still stored in RPMB and doesn't gets resetted by flashing that factory fw, to set RMM back to Normal you need to flash the full stock firmware for your country and wait the classic 168h countdown.
4. The "SW REV. CHECK FAIL (BOOTLOADER) DEVICE: x, BINARY: x" is caused because you're trying to flash a firmware with a lower rev. than the one installed in your phone. You need to flash a firmware with the same or higher rev (In this case, you need a XXU3/XXS3 or higher fw). Forget to flash a fw with a lower rev since RP fuse prevents you to do it (if you force install the bl via TWRP you get an hardbrick)
Click to expand...
Click to collapse
Thanks for responding currently I am on stock official firmware for my country and waiting 7 days,6 days left. I appreciate you all for responding. I want to ask one last thing, if I wipe internal storage through TWRP and delete the OS (blank download mode) can I not install a binary 2 boot loader?

DeadRatGames said:
Thanks for responding currently I am on stock official firmware for my country and waiting 7 days,6 days left. I appreciate you all for responding. I want to ask one last thing, if I wipe internal storage through TWRP and delete the OS (blank download mode) can I not install a binary 2 boot loader?
Click to expand...
Click to collapse
Already replied: no. First, there's no relation between bootloader and system (why should a wipe let you flash a lower rev bootloader lol). And as I already explained, Rollback Prevention fuse avoids you to do that: in Odin if you try to flash a lower rev bin it returns an error. If you try to force install it via TWRP, you'll hard brick your device and get a dead phone

BlackMesa123 said:
Already replied: no. First, there's no relation between bootloader and system (why should a wipe let you flash a lower rev bootloader lol). And as I already explained, Rollback Prevention fuse avoids you to do that: in Odin if you try to flash a lower rev bin it returns an error. If you try to force install it via TWRP, you'll hard brick your device and get a dead phone
Click to expand...
Click to collapse
When I say wipe I mean like complete wipe. Delete everything not just date like fully wipe internal storage. But anyway thanks.

Reformat system.

DeadRatGames said:
When I say wipe I mean like complete wipe. Delete everything not just date like fully wipe internal storage. But anyway thanks.
Click to expand...
Click to collapse
Don't take any risks or you will be ending up with a hard brick, like Mesa said!
Just do your time 6 days I think.

solamente said:
Don't take any risks or you will be ending up with a hard brick, like Mesa said!
Just do your time 6 days I think.
Click to expand...
Click to collapse
Ok. Thanks

ok so i have 2 of my a8's that are frp locked right now to the same frikken account and i can't remember what it is now. one is binary 2 and the other 3. both have no oem unlock in combination so i can't bypass... will this work for me? if so how do i know what my original firmware was? or do you mean just original carrier? also when waiting the 7 days where do i let them idle during the wait if i can't get passed google login during install?
both are sm-a530w both on oreo. binary 2 and 3

vibespredah said:
ok so i have 2 of my a8's that are frp locked right now to the same frikken account and i can't remember what it is now. one is binary 2 and the other 3. both have no oem unlock in combination so i can't bypass... will this work for me? if so how do i know what my original firmware was? or do you mean just original carrier? also when waiting the 7 days where do i let them idle during the wait if i can't get passed google login during install?
both are sm-a530w both on oreo. binary 2 and 3
Click to expand...
Click to collapse
same questions

vibespredah said:
ok so i have 2 of my a8's that are frp locked right now to the same frikken account and i can't remember what it is now. one is binary 2 and the other 3. both have no oem unlock in combination so i can't bypass... will this work for me? if so how do i know what my original firmware was? or do you mean just original carrier? also when waiting the 7 days where do i let them idle during the wait if i can't get passed google login during install?
both are sm-a530w both on oreo. binary 2 and 3
Click to expand...
Click to collapse
use this technic and your problem will be solved : youtube/watch?v=WmvjDEk6w4E

amazing. youre the man. cheers.
samalderon said:
use this technic and your problem will be solved : youtube/watch?v=WmvjDEk6w4E
Click to expand...
Click to collapse
omg youre the best. thanks so much.

Someone HELP!!!

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