Develop Bugs

[Solved] Custom binary (recovery) blocked by frp lock after Note FE rom install

Hello everyone,
According to this post i did install note FE rom on my note 7 sm-n930F.
I did not have any problem flashing my first n930f.
Unfortunately, for my second install, i stupidly FORGOT to enable OEM unlock when flashing TWRP. :crying::crying:
I continued to install the ROM without problem but after the first reboot, the phone is blocked with the message "custom binary (recovery) blocked by frp lock"
I can boot in download mode (power + volume down + home) so i tried to flash a N930F stock rom but it fails with the message "check fail : device : 2 binary : 1"
(I think this is due to the fact that the stock rom is Android 6 and the device's rom is Android 7).
I tried Emergency Device Recovery from SmartSwitch PC without success : the device is not recognized by SmartSwitch.
I do not know what to do, can someone help me unbrick this phone ?
Thank you for your help.

Same for me. I cant believe it! No solution here from XDA community!

Open Odin flash TWRP , flash rom .

minhcanh97 said:
Open Odin flash TWRP , flash rom .
Click to expand...
Click to collapse
not so simple...
unable to flash TWRP -> blocked by FRP lock
I finally found the right stock rom for my N-930F (N930FXXU2BPI7) with help from pvpaco (see here)

I had the same problem (forgot to toggle oem lock) just flash the stock firmware for your device and it will boot (using odin) if you had a Google account it may ask you to sign in again if not just set up the device toggle the oem switch and flash twrp

The problem no flashable available stock rom for Korean models S/L/K. All failed in Odin. I had also a frp on , I can't flash any custom file.

For the note 7 or FE?

CrypticVorttex said:
For the note 7 or FE?
Click to expand...
Click to collapse
Note 7

What processor do you have snapdragon or exynos ?

CrypticVorttex said:
What processor do you have snapdragon or exynos ?
Click to expand...
Click to collapse
Exynos

so I found the firmware you need but it will take an age to download but you may not have a choice https://alfafile.net/file/FiXh this is for the n930s

CrypticVorttex said:
so I found the firmware you need but it will take an age to download but you may not have a choice https://alfafile.net/file/FiXh this is for the n930s
Click to expand...
Click to collapse
Thanks but it doesn't work already flashed. My device binary is on 2.

Can you boot to download mode? if so can you send a picture of that screen

Sorry I didn't tried this version, worked for u to solve frp lock?
---------- Post added at 06:03 PM ---------- Previous post was at 05:54 PM ----------
CrypticVorttex said:
Can you boot to download mode? if so can you send a picture of that screen
Click to expand...
Click to collapse
Yes I can but I need a version with binary 2.

Flashing stock firmware will get past the frp lock all I can suggest is try the firmware I posted and see if it works, keep me updated

CrypticVorttex said:
Flashing stock firmware will get past the frp lock all I can suggest is try the firmware I posted and see if it works, keep me updated
Click to expand...
Click to collapse
Samsung don't allow downgrading, I need the latest ota with 15 % battery limitation.

translpro said:
Samsung don't allow downgrading, I need the latest ota with 15 % battery limitation.
Click to expand...
Click to collapse
hmmm, not sure I can be any help then, unless you can find the correct official rom for your phone then the only other option would be to take it to a Samsung service centre (although the phone should be recalled they might still be able to help you)
sorry I cant help any more

Hi guys, I've got a note 7 UK n930f with 0% battery update, I can still access download mode but not recovery or system boot. OEM unlock is not switched on so I can install twrp or root or anything like that. I've tried lots of different firmwares but they all fail , see pics...
Does anyone have any info on what I can do next?
Thanks
Kev

Stuck with frp block on N930F. But I don't understand the title.. How is this a solved case? Could anybody anywhere find the 0% battery update firmware?

Dear all i hope somone of you can halpe i have samsung sm-n910p not 4 it has 6.0.1
N910pVPU5DQI5 and icant root or log in to the phone becaused it's block by google account

After TWRP & Root, Freeze, Softbrick, Only Official Released Binaries...

SM-G960F/DS
RMM State: Prenormal
OEM LOCK: OFF
FRP LOCK: OFF
KNOX tripped: 1
Current binary: Custom
I just flashed TWRP, Magisk, no-verity, and the samsung root preventer disabler following the guide here. I used Magisk 16.6 (supposedly S9 is officially supported now, but it's still in beta).
Everything was going fine, then after an hour or two it froze on the lock screen, and would NOT come out of it. After a couple minutes, I held volume down and power to reboot, and it went into a soft brick.
I can't flash via download mode as it gives the error "Only official released binaries are allowed to be flashed". It gives that error when I try to start the phone or boot into TWRP as well.
So what are my options to fix this, and is it possible to prevent this in the future?

you must flash the latest firmware, yesterday I happened the same.

angel8502 said:
you must flash the latest firmware, yesterday I happened the same.
Click to expand...
Click to collapse
Man, I was hopeful ng that wasn't the case. I've already started downloading from sammobile.
So what are you going to do from here? Try rooting again? Is there a more up-to-date RMM disabler?

Any one else have any ideas about why this happens ? I just flashed EdyoBlue ROM after being on Soldier ROM --- all was uneventful
Upon first reboot I came to the screen about Custom Binaries --- seemed to have lost TWRP etc.
Only way out was to flash stock, lose root and I assume WAIT ANOTHER 7 DAYS !!!
Any other ideas ? Or ideas on how to prevent in the future?

jcrompton said:
Any one else have any ideas about why this happens ? I just flashed EdyoBlue ROM after being on Soldier ROM --- all was uneventful
Upon first reboot I came to the screen about Custom Binaries --- seemed to have lost TWRP etc.
Only way out was to flash stock, lose root and I assume WAIT ANOTHER 7 DAYS !!!
Any other ideas ? Or ideas on how to prevent in the future?
Click to expand...
Click to collapse
Did you also flash the rmm state bypass? I did, and I'm going to try again with v2.

LysolPionex said:
Did you also flash the rmm state bypass? I did, and I'm going to try again with v2.
Click to expand...
Click to collapse
Well I didn't flash anything prior to EdYoBlue ROM -- I had been running Soldier ROM for a while and it was my understanding that the RMM bypass was included in those custom ROMs and or kernels
Obviously I did something wrong

jcrompton said:
Well I didn't flash anything prior to EdYoBlue ROM -- I had been running Soldier ROM for a while and it was my understanding that the RMM bypass was included in those custom ROMs and or kernels
Obviously I did something wrong
Click to expand...
Click to collapse
Oh... Yeah I don't know about that.

Same problem. Samsung Galaxy S9+ (SM-G965F)
I rooted my Samsung Galaxy S9+ (SM-G965) yesterday with
Odin, Magisk (modified version as official verson doesn't work apparently) and TWRP.
Took about 10 minutes to do all up, and root was successful!!! 20 minutes later it turned itself off!! No matter what i did or tried.....I couldn't turn it back on nor get into recovery (TWRP). All while it was constantly flashing........ (ONLY OFFICIAL RELEASE BINARIES TO BE FLASHED)
Figured it was somehow a soft brick. So i flashed original firmware back onto phone with Odin and all was well. ILL BE TRYING A NEW WAY AND WILL POST RESULTS.

1AussieTradie said:
I rooted my Samsung Galaxy S9+ (SM-G965) yesterday with
Odin, Magisk (modified version as official verson doesn't work apparently) and TWRP.
Took about 10 minutes to do all up, and root was successful!!! 20 minutes later it turned itself off!! No matter what i did or tried.....I couldn't turn it back on nor get into recovery (TWRP). All while it was constantly flashing........ (ONLY OFFICIAL RELEASE BINARIES TO BE FLASHED)
Figured it was somehow a soft brick. So i flashed original firmware back onto phone with Odin and all was well. ILL BE TRYING A NEW WAY AND WILL POST RESULTS.
Click to expand...
Click to collapse
What's the new way? Are you able to flash again already, or do you have to wait 7 days again?

same issue i had to re flash the stock OS & wait for 7 days for OEM unlock now i have that option but i am not sure which method should i use.

RMM STATE PRENORMAL is also what blocks custom binaries from being flashed
Check the TWRP guide on how to deal with that too

LysolPionex said:
What's the new way? Are you able to flash again already, or do you have to wait 7 days again?
Click to expand...
Click to collapse
Unfortunately no success. Have to wait the 7 days . Currently trying to find a work around. Will keep informed.

Any news I got my OEM unlock back any way to root the phone and get a custom firmware to work

rockykv2 said:
Any news I got my OEM unlock back any way to root the phone and get a custom firmware to work
Click to expand...
Click to collapse
Once my RMM status is normal, I'm going to try Soldier's Rom. I've heard good things about it.
You'll need to follow the official TWRP guide first. Both in this S9 forum.

I already tested that It gets stuck on welcome screen it will not go forward

rockykv2 said:
I already tested that It gets stuck on welcome screen it will not go forward
Click to expand...
Click to collapse
I'd ask about that in the soldier Rom thread; sounds like it might be a wipe issue (really not sure), but a ton of people love the Rom, so it's probably something random on your end.
I'd stick with a stock-based rom, as they're usually more stable.

That Max Lee tutorial about s9+ root is outdated. He is a ****ing bull****. He did not even cared to update his post that magisk root method always freeze. And also his rmm unlock fix is not updated too. Did you guys have the august 1 security update? I guess that was the cause of this "Only official binaries allowed" after rebooting. Here's hoping somebody here got an answer for that RMM.

jonathan_moreno91 said:
That Max Lee tutorial about s9+ root is outdated. He is a ****ing bull****. He did not even cared to update his post that magisk root method always freeze. And also his rmm unlock fix is not updated too. Did you guys have the august 1 security update? I guess that was the cause of this "Only official binaries allowed" after rebooting. Here's hoping somebody here got an answer for that RMM.
Click to expand...
Click to collapse
That's kinda the general consensus I've gotten about that tutorial.
I was using the August 1 security update, but I was using v1 of Mesa's RMM bypass. I downloaded v2, and downgraded my Rom to like April or March or something and will try it again, once the prenormal clears.
RMM v2 is here:
https://forum.xda-developers.com/sa...nuary-security-patch-sm-t3739225/post75360965

LysolPionex said:
That's kinda the general consensus I've gotten about that tutorial.
I was using the August 1 security update, but I was using v1 of Mesa's RMM bypass. I downloaded v2, and downgraded my Rom to like April or March or something and will try it again, once the prenormal clears.
RMM v2 is here:
https://forum.xda-developers.com/sa...nuary-security-patch-sm-t3739225/post75360965
Click to expand...
Click to collapse
Bro if you are on august 1 security update too then you are in xu2 bootloader... you cannot downgrade to xu1 bootloader which was before august..

jonathan_moreno91 said:
Bro if you are on august 1 security update too then you are in xu2 bootloader... you cannot downgrade to xu1 bootloader which was before august..
Click to expand...
Click to collapse
Really?! This is literally the first I've heard of this. Do you know if there's a thread discussing this?

Having issue flashing with Samsung S9 SM-G960F

Long story short I rooted my phone with Magisk, fully unrooted then me being stupid I went into settings and turned off OEM Unlock it had to wipe the device since then had this FRP lock, Now i was told only way to fix this is to flash with the default software since this i've run into problems with ODIN when loading the files into the phone it gets stuck on recover.img on Odin and on the phone it says sw rev check fail bootloader device 2 binary 2.
If you guys can help fix I would be so happy
Thank you

gilescore said:
Long story short I rooted my phone with Magisk, fully unrooted then me being stupid I went into settings and turned off OEM Unlock it had to wipe the device since then had this FRP lock, Now i was told only way to fix this is to flash with the default software since this i've run into problems with ODIN when loading the files into the phone it gets stuck on recover.img on Odin and on the phone it says sw rev check fail bootloader device 2 binary 2.
If you guys can help fix I would be so happy
Thank you
Click to expand...
Click to collapse
Make sure you're not trying to downgrade the bootloader, has to be the same version or higher that you're flashing
Download mode look for BL:1 or 2 or 3, and pick a firmware with that number or higher as shown below
G960FXXU2BRJ3 << Version 2

Thanks man thats fixed it
*Detection* said:
Make sure you're not trying to downgrade the bootloader, has to be the same version or higher that you're flashing
Download mode look for BL:1 or 2 or 3, and pick a firmware with that number or higher as shown below
G960FXXU2BRJ3 << Version 2
Click to expand...
Click to collapse
Thank you so much

gilescore said:
Thank you so much
Click to expand...
Click to collapse
No probs :good:

Oem unlock security patch november date hack not working

The change date hack to unlock OEM isnt working help me

Wait

*Detection* said:
Wait
Click to expand...
Click to collapse
;(

Lol, I succeeded by setting date to past 1 month, upgrading to pie then setting it back to jan after update

amakuramio said:
Lol, I succeeded by setting date to past 1 month, upgrading to pie then setting it back to jan after update
Click to expand...
Click to collapse
You don't need OEM unlock to update to Pie if it's stock with ODIN

only official released binaries ... nonsense again. I want to flash oreo with root etc.

amakuramio said:
only official released binaries ... nonsense again. I want to flash oreo with root etc.
Click to expand...
Click to collapse
Yea you have to wait 7 days, there is more than just the OEM unlock that needs to time-out, RMM state pre-normal too
Last I heard there was no bypass other than waiting 7 days

*Detection* said:
Yea you have to wait 7 days, there is more than just the OEM unlock that needs to time-out, RMM state pre-normal too
Last I heard there was no bypass other than waiting 7 days
Click to expand...
Click to collapse
downgrading to aug update then trying date hack also impossible?

amakuramio said:
Lol, I succeeded by setting date to past 1 month, upgrading to pie then setting it back to jan after update
Click to expand...
Click to collapse
How what the phone condition before you did the upgrade? you were using it normally, with google, samsung account logged, you had Dev option enabled when OEM appeared? I really need a guide to make this appear for the first time.

scroll-lock said:
How what the phone condition before you did the upgrade? you were using it normally, with google, samsung account logged, you had Dev option enabled when OEM appeared? I really need a guide to make this appear for the first time.
Click to expand...
Click to collapse
I bought it from a second hand shop and tried many times to get oem unlock, from my teenager years I always used xposed so a phone without that is useless. I tried the classical time trick but it didn't work, so in the normal recovery I did factory reset, then didn't login, remove sim, set date one month behind, turn off auto update and time and then connected internet to update, it failed. Then I set date to today and started update it to pie. While it was downloading I put it one month behind, after install I had oem unlock. Before the reboot from oreo it wasn't there in the development options. RMM prenormal prevented me from installing twrp im going to bring this phone back get s8 plus and downgrade to nougat. One week is too long

Error when installing stock OS: SW REV. CHECK FAIL(BOOTLOADER) DEVICE: 7. BINARY: 6

Recently I rooted my S9 and installed Lineage OS but I didnt like it and decided to swap back to the stock OS. I used Frija to get the .tar.md5 files for Odin but once I select all the files and hit start the log in Odin loads up to system.img then stops and I get the SW REV. CHECK FAIL(BOOTLOADER) DEVICE: 7. BINARY: 6 error on my phone. Any idea on how to fix this? I'd really appreciate some help as I'm going to be travelling soon and I need my phone for it and I'd prefer not to use Lineage OS. Thanks in advance.

Do you have an At&t branded phone? SM-G960U?
I am having a very similar problem. A customer came in and was having issues with device. I told them to back up, wipe, and update device. That didn't work so I tried a full flash with ODIN. Now I can't get the phone to boot at all and it says, "Secure Check Fail : Modem" and "Unauthorized software visit nearest AT&T blah, blah,..)
I think it is because AT&T has pushed out the latest update(OCT. 18th), but the Odin files are not out yet. According to:
https://www.att.com/devicehowto/tutorial.html#!/stepbystep/id/stepbystep_KM1253489?make=Samsung&model=SamsungG965U
G960USQS7CSI5 is the latest FW. If you google it, there are only four results.

Yep, the problem was the phone was on the latest FW. Newer firmware was just uploaded a few days ago.
I flashed:
G960USQU7CSJ2_G960UOYN7CSJ2_CHA
and now I'm booting again.
Your problem is that your firmware is too old. Basically, you are trying to downgrade your FW. The phone is basically saying, "Hey, I have bootloader 7, I won't let you install something lower than that."

ma777 said:
Your problem is that your firmware is too old. Basically, you are trying to downgrade your FW. The phone is basically saying, "Hey, I have bootloader 7, I won't let you install something lower than that."
Click to expand...
Click to collapse
^^^^ this ^^^^
the Odin error is telling you that youre trying to flash a revision of the bootloader than was last installed on the phone. to to sammobile.com/fimrwares and get the one with the correct bootloader for your specific phone and flash that.
also download the firmware with the frija tool or samfirm. trust me, its literallt 5x faster than a direct download from the site. The 5 min it takes to get samfirm up and running is worth it, believe me on that.

I may be new to this, But I just Flashed a SM-g960u, That Had Bootloader7 locked on it, When I would go into download mode I would see FRP ON, and this Firmware G960USQU7CSK6. So I downloaded a Combination Firmware file. Used Odin Patched, Flashed it there is a guide out there. Restarted into the Settings, Turned on Developer mode, USB Debugging, and Was able to change OEM-Software install. Then I was able to load this phone after, with G960USQS7CSI5 with ease My first flash and I had to bypass a FRP and a Bootloader lock. Now I should be able to flash this to the U1 version unlocked and be good! If you need any help I did just do this last night I can guide you in the right dirrection. Litterally I had no help from here as in asking questions I am pretty savy. So you need to make sure your Version has the "7" in the Same Place. Also after I enabled those things while in the phone before Flashing it I chose the Factory Reset from within, SO it erashed EVERYTHING except Download Mode and the Combination Firm Loaded. Meaning I should have been able to flash to anything I wanted

Nightfox619 said:
I may be new to this, But I just Flashed a SM-g960u, That Had Bootloader7 locked on it, When I would go into download mode I would see FRP ON, and this Firmware G960USQU7CSK6. So I downloaded a Combination Firmware file. Used Odin Patched, Flashed it there is a guide out there. Restarted into the Settings, Turned on Developer mode, USB Debugging, and Was able to change OEM-Software install. Then I was able to load this phone after, with G960USQS7CSI5 with ease My first flash and I had to bypass a FRP and a Bootloader lock. Now I should be able to flash this to the U1 version unlocked and be good! If you need any help I did just do this last night I can guide you in the right dirrection. Litterally I had no help from here as in asking questions I am pretty savy. So you need to make sure your Version has the "7" in the Same Place. Also after I enabled those things while in the phone before Flashing it I chose the Factory Reset from within, SO it erashed EVERYTHING except Download Mode and the Combination Firm Loaded. Meaning I should have been able to flash to anything I wanted
Click to expand...
Click to collapse
got no help here? how so? I see you got the info you needed to get the phone back up and running properly via asking about it here.
with regard to the bootloader version of 7 in your case, it is a very known thing that whatever bootloader version youre on, you cant go backwards from.
In either event, im very glad that you got it up and running!!

Youdoofus said:
got no help here? how so? I see you got the info you needed to get the phone back up and running properly via asking about it here.
with regard to the bootloader version of 7 in your case, it is a very known thing that whatever bootloader version youre on, you cant go backwards from.
In either event, im very glad that you got it up and running!!
Click to expand...
Click to collapse
Getting no help was meant I hadn't Posted asking Questions, I read everything ya'll put up and I was able to do it on my own without continuing to ask, so Yeah I did get help here but not by asking only reading what is available

downgrade samsung sm-g570m
Nightfox619 said:
I may be new to this, But I just Flashed a SM-g960u, That Had Bootloader7 locked on it, When I would go into download mode I would see FRP ON, and this Firmware G960USQU7CSK6. So I downloaded a Combination Firmware file. Used Odin Patched, Flashed it there is a guide out there. Restarted into the Settings, Turned on Developer mode, USB Debugging, and Was able to change OEM-Software install. Then I was able to load this phone after, with G960USQS7CSI5 with ease My first flash and I had to bypass a FRP and a Bootloader lock. Now I should be able to flash this to the U1 version unlocked and be good! If you need any help I did just do this last night I can guide you in the right dirrection. Litterally I had no help from here as in asking questions I am pretty savy. So you need to make sure your Version has the "7" in the Same Place. Also after I enabled those things while in the phone before Flashing it I chose the Factory Reset from within, SO it erashed EVERYTHING except Download Mode and the Combination Firm Loaded. Meaning I should have been able to flash to anything I wanted
Click to expand...
Click to collapse
hi Nightfox619.! I have a samsung sm-g570m and I trying to downgrade to binary 2 when I flash with odin it give me this error message "sw rev check fail bootloader device 7 binary 3" any idea how can I downgrade .??

pol1345 said:
hi Nightfox619.! I have a samsung sm-g570m and I trying to downgrade to binary 2 when I flash with odin it give me this error message "sw rev check fail bootloader device 7 binary 3" any idea how can I downgrade .??
Click to expand...
Click to collapse
Ok so first you should post I'm your devices threads but that aside. Here's what's up. You can't downgrade the error shown is saying your device is on a bit 7 binary. Your trying to flash a bit 3 binary which isn't even 2 you need to find your respective firmware in a bit 7 or higher.

TheMadScientist said:
Ok so first you should post I'm your devices threads but that aside. Here's what's up. You can't downgrade the error shown is saying your device is on a bit 7 binary. Your trying to flash a bit 3 binary which isn't even 2 you need to find your respective firmware in a bit 7 or higher.
Click to expand...
Click to collapse
thanks 4 answering bro and sorry 4 using this thread.! so definitely I can't downgrade 2 a lower binary than 7..?

pol1345 said:
thanks 4 answering bro and sorry 4 using this thread.! so definitely I can't downgrade 2 a lower binary than 7..?
Click to expand...
Click to collapse
Like 99.9%. That's what that error is. The bootloader is blocking downgrade

pol1345 said:
thanks 4 answering bro and sorry 4 using this thread.! so definitely I can't downgrade 2 a lower binary than 7..?
Click to expand...
Click to collapse
yes, if you get a firmware version matching the one last installed on your device, itll go right thru and boot just fine. Goodlock is finally working on all modules for A10 as well. Maybe we will see more development occur with this shutdown going on. Let us know if you run into any trouble, the error you were getting is totally resolvable!

at the end I give up on it..! my internet 2 slow 4 go downloading & trying rom after rom.! i am from venezuela.

Nightfox619 said:
I may be new to this, But I just Flashed a SM-g960u, That Had Bootloader7 locked on it, When I would go into download mode I would see FRP ON, and this Firmware G960USQU7CSK6. So I downloaded a Combination Firmware file. Used Odin Patched, Flashed it there is a guide out there. Restarted into the Settings, Turned on Developer mode, USB Debugging, and Was able to change OEM-Software install. Then I was able to load this phone after, with G960USQS7CSI5 with ease My first flash and I had to bypass a FRP and a Bootloader lock. Now I should be able to flash this to the U1 version unlocked and be good! If you need any help I did just do this last night I can guide you in the right dirrection. Litterally I had no help from here as in asking questions I am pretty savy. So you need to make sure your Version has the "7" in the Same Place. Also after I enabled those things while in the phone before Flashing it I chose the Factory Reset from within, SO it erashed EVERYTHING except Download Mode and the Combination Firm Loaded. Meaning I should have been able to flash to anything I wanted
Click to expand...
Click to collapse
I have S20+ running Android 11 with U7 Binary. I tried downgrading to Androi 10 which has Binary U5. Now I have downloaded the Binary U5 file. But in some video, he is telling that you should download the Binary File with the same number as it is currently installed in your phone, which in my case is U7. So? Am I supposed to download U7 Combination Binary file and flash it in order to downgrade to Android 10
OR
Should I flash the U5 Combination File and flash the Android 10 AP, CSC, BL, HOME ???

Someone has Combination file to G960F with bootloader SF (Version 15)?