FRP Custom binary - Galaxy Grand Prime Q&A, Help & Troubleshooting

Plase help i have grand prime G530H running stock kitkat then i upgraded to 5.0.2 lollipop russian firmware G530XXU2BPB2 to install custom rom, i installed twrp and custom rom with no problems, now running latest RR Rom, since 5.0.2 lollipop i didnt login to any google account, my question is if i login to google account using RR / Custom roms, is there a chance to block custom binary frp after reboot? I read some threads about custom frp, it is said that need to enable oem unlock but after upgrading to lollipop firmware there is no oem unlock on dev options.

test_only said:
Plase help i have grand prime G530H running stock kitkat then i upgraded to 5.0.2 lollipop russian firmware G530XXU2BPB2 to install custom rom, i installed twrp and custom rom with no problems, now running latest RR Rom, since 5.0.2 lollipop i didnt login to any google account, my question is if i login to google account using RR / Custom roms, is there a chance to block custom binary frp after reboot? I read some threads about custom frp, it is said that need to enable oem unlock but after upgrading to lollipop firmware there is no oem unlock on dev options.
Click to expand...
Click to collapse
FRP lock will not trigger if you login to your Google account. If the frp lock was triggered it would ask you to login to your Google account that you had on your stock ROM at the beginning anyway. So it's absolutely safe to login to Google account.
FRP lock only triggers if you tried to wipe data and cache from stock recovery while having a pin or password protected Device. The phone won't let you boot.

tasnim_tamim said:
FRP lock will not trigger if you login to your Google account. If the frp lock was triggered it would ask you to login to your Google account that you had on your stock ROM at the beginning anyway. So it's absolutely safe to login to Google account.
FRP lock only triggers if you tried to wipe data and cache from stock recovery while having a pin or password protected Device. The phone won't let you boot.
Click to expand...
Click to collapse
Thanks for the feedback, i mean custom binary blocked by frp red text on boot screen like bricked and refuses to boot, if installed root or flashed twrp on odin, but nevermind.. sorry for the noob question, my bad... i've found that custom binary error only present in protected or locked bootloader, so it need to enable oem unlock in dev options before installing root/twrp, other GP variants haa protected bootloader, while g530x variant has already unlocked bootloader so no oem unlock in dev options in settings, its safe to install root/twrp/custom.

test_only said:
Thanks for the feedback, i mean custom binary blocked by frp red text on boot screen like bricked and refuses to boot, if installed root or flashed twrp on odin, but nevermind.. sorry for the noob question, my bad... i've found that custom binary error only present in protected or locked bootloader, so it need to enable oem unlock in dev options before installing root/twrp, other GP variants haa protected bootloader, while g530x variant has already unlocked bootloader so no oem unlock in dev options in settings, its safe to install root/twrp/custom.
Click to expand...
Click to collapse
Looks like you found out your answer.
Just to let you know, it's not impossible to get a frp lock in G530H. Yes I know it's a common case in devices like G531H (Value Edition) or some carrier phones which has locked bootloaders. But I even heard some cases of frp lock in g530h due to some failure while flashing firmware from Odin. But it still should not effect you. As you were able to install custom ROM.. so your safe .

Related

My experience with "Custom Binary Blocked By FRP / FAP Lock"

So everything was working well with my S7 (Helios 7 Rom), but I wanted to try the S8 AOD apk.
After flashing the zip some wierd graphical glitches started appearing on my phone, so I tried to fix them by disabling done options.
Well the issue is, I didn't know that If you disabled​ developer options (or the OEM unlock option specifically) then your phone won't boot as long as you have a custom recovery.
The error you'll get is: "Custom binary vlocked by FRP lock"
(top left corner in red when you're on the samsung text while booting)
The only thing you're​ able to boot into is download mode.
(btw and to quit download mode you'll have to hold vol down home power)
Many people were saying that wiping is the only way to fix this, but i can't wipe as I have important data on the internal storage.
But luckily I was using a stock rom, so I downloaded​ a recent S7 nougat firmware from the general forum here and flashed it with Odin, and what do you know! I was able to boot normally and my internal storage files are all there.
Now to go back to TWRP and custom roms, I have to wipe my internal storage but at least I can backup everything and flash cfroot to get root then backup all my apps with titanium backup (to external storage).
After that just follow this thread:
[ROOT] (Updated) Official Stock Nougat 7.0 (100% Working) - All Exynos Models
https://forum.xda-developers.com/galaxy-s7/how-to/root-official-stock-nougat-7-0-100-t3540765
then you'll be back to twrp and can flash custom roms. (but that procedure will wipe your internal storage.
good luck to everyone, just wanted to share this in case anyone faced the same situation as me.
When flash autoroot by chainfire with odin it doesn't flash.
It says blocked by frp.
How do I flash root on 6.0.1?
3omar7 said:
When flash autoroot by chainfire with odin it doesn't flash.
It says blocked by frp.
How do I flash root on 6.0.1?
Click to expand...
Click to collapse
Before flashing root remove your google account, after root enable OEM unlock then log to account back

SM-G531M - FRP can't be disabled when logged into Google

Hi! I have flashed successfully a stock rom of Android 5.1.1 on this device (SM-G531M) using the latest Odin. I enabled the developer options and then OEM Unlock and USB Debugging. Flashed TWRP, everything great. Once TWRP was on my device I installed Magisk following the instructions and no problem. So having root access and TWRP on my phone, really happy that no problems came up on the way, I decide to log into my Google account to update and get some apps and here is when the problems appear. I checked that OEM Unlock is still on and reboot my phone to find that FRP is on and can't boot because of root (can't get in recovery either because TWRP is not the stock recovery), so I flash the device again with the stock rom and find out that I can't remove FRP lock to flash TWRP again. I try removing my google account and FRP is off, so I have to choose:
a) root access and TWRP recovery or
b) Google Account and get new apps or update the ones I have.
Nowhere I looked I could find any answer or anyone having this issue. Can someone tell me what am I doing wrong? I really have no idea why this happens, is a Google update that does this to everyone or what's going on?
Thanks in advance!

Root SM-G361F without triggering FRP lock!! Enable OEM unlock does not work!!

Hi there.
I have a problem with a smartphone of a family member that needs to be cleaned by bloatware and then has to st back unrooted.
Smartphone model: Samsung Galaxy Core SM-G361F
I have used Magisk for root and install it with TWRP and done all the cleaning... and for doing it correctly I hat also to delete all the Google accounts in the phone as the TWRP recovery was keeping to be triggering the FRP lock, so I was not able to access it anymore if having the Google accounts installed!!
And in all this, Enable OEM unlock is checked in the Dev options!!!!!!!!
Speaking about the exact problem I have, after having done all the cleaning, I restarted...and I could not boot into the os anymore as the load was triggered by the FRP lock!!
The os was still rooted, and then I thought that maybe I should have not added back the Google account before removing Magisk before restarting!!
I had to flash stock firmware without wiping so to restore os without loosing my data and apps (fortunately...)
How to root and then remove bloatware and then un-root this device it without triggering the FRP lock?
Thanks!!

How to root SM-G531F (with either Magisk or SuperSU) without being blocked by FRP?

Hello, I need some help. It's about rooting SM-G531F with either Magisk or SuperSU without being blocked by FRP. I know how to disable FRP, I just need to remove my Google Account in my device, the problem is, how can I prevent it from blocking my device (with a Google Account) to boot when I root it with Magisk?
I can say I'm partially successful at rooting it with Magisk, but whenever my device reboots with a Google Account, I get blocked by FRP with this message "Custom Binary blocked by FRP" (I have a faulty battery so sometimes it reboots or shut downs by itself). With this blocking me, I have to flash the stock firmware again. And sometimes, although I had removed all my accounts in my device, I still get blocked. (It's too late for me to boot to Download Mode or just reboot directly, my device gets block either way)
I once fully successfully rooted my SM-G531F with a Beta Version of SuperSU without FRP blocking problems, however, I.... lost the .zip file of it (XO XTUPID (-‸ლ) ). Now, when I flash SuperSU, it fails to root it.
I also stopped by another thread stating that there is a boot.img file that doesn't contain FRP in it. Is it true? Is it true that there is a boot.img that doesn't have FRP for SM-G531F
That's all, thanks.
​

Stuck with upgrading FRPed G900V

I have an old G900V in great condition but trouble is that it is locked under Samsung FRP. It originally had 6.0.1.
I was trying to remove lock, but it did not work, so I decided to just upgrade to Lineage OS 18.1.
My EMMC is 15.
I followed the guide
2022_VZW_EMMC_15_ AIO_Tool To Unlock_Bootloader+Install_TWRP And MM_QL1_Rooted_Rom Works On Any Version Bootloaders_MM_LL_KK-Reactivation Lock Remover
This Process Will Root Phone Unlock Your VZW EMMC 15 Chipset Bootloader Install TWRP Recobery And Imstall Latest QL1 Stock Rom . Downloads S5_Root_Tools_2023.7z EMMC_15_Rom.zip -- Stock QL1 6.0 Directions For Unlocking Stock Phone I would...
forum.xda-developers.com
on how to root the device and I am able to install 4.4, root it and boot into TWRP, do advanced wipe and install the latest Lineage 18.1 image.
Once the phone reboots, it is stuck on Samsung logo.
I also tried installing 6.0.1 flash from the same forum post, but it immediately shows error, indicating that the phone is locked.
Please suggest how to proceed. Ideally, I want to upgrade to lineage, but if that is not possible, I am ok with 6.0.1, but trouble is that with the stock firmware I am not able to proceed because of FRP.
Is there a simple method to bypass the FRP, given that I have root on 4.4 and potentially can make changes in the system, while still in TWRP, after installing stock?
I figured out the reason for my issues.
This process did not work properly for me:
2022_VZW_EMMC_15_ AIO_Tool To Unlock_Bootloader+Install_TWRP And MM_QL1_Rooted_Rom Works On Any Version Bootloaders_MM_LL_KK-Reactivation Lock Remover
This Process Will Root Phone Unlock Your VZW EMMC 15 Chipset Bootloader Install TWRP Recobery And Imstall Latest QL1 Stock Rom . Downloads S5_Root_Tools_2023.7z EMMC_15_Rom.zip -- Stock QL1 6.0 Directions For Unlocking Stock Phone I would...
forum.xda-developers.com
So I used the process described here to root and install safestrap and then remove Samsung FRP
[HOW TO] [GUIDE] - How to completely disable Reactivation Lock on SM-G900V
This is a guide how to completely disable Reactivation Lock on SM-G900V in simple steps. Schematically, we will install Android 4.4.2, bypass Samsung Account login, register a new one and then turn Reactivation Lock OFF. The phone will be clear...
forum.xda-developers.com
After that was done, I switched back to step 11 of
2022_VZW_EMMC_15_ AIO_Tool To Unlock_Bootloader+Install_TWRP And MM_QL1_Rooted_Rom Works On Any Version Bootloaders_MM_LL_KK-Reactivation Lock Remover
This Process Will Root Phone Unlock Your VZW EMMC 15 Chipset Bootloader Install TWRP Recobery And Imstall Latest QL1 Stock Rom . Downloads S5_Root_Tools_2023.7z EMMC_15_Rom.zip -- Stock QL1 6.0 Directions For Unlocking Stock Phone I would...
forum.xda-developers.com
to unlock bootloader.
I did not boot into 6.0.1 but immediately installed Lineage 18.1 and all worked.
alexv12 said:
I figured out the reason for my issues.
This process did not work properly for me:
2022_VZW_EMMC_15_ AIO_Tool To Unlock_Bootloader+Install_TWRP And MM_QL1_Rooted_Rom Works On Any Version Bootloaders_MM_LL_KK-Reactivation Lock Remover
This Process Will Root Phone Unlock Your VZW EMMC 15 Chipset Bootloader Install TWRP Recobery And Imstall Latest QL1 Stock Rom . Downloads S5_Root_Tools_2023.7z EMMC_15_Rom.zip -- Stock QL1 6.0 Directions For Unlocking Stock Phone I would...
forum.xda-developers.com
So I used the process described here to root and install safestrap and then remove Samsung FRP
[HOW TO] [GUIDE] - How to completely disable Reactivation Lock on SM-G900V
This is a guide how to completely disable Reactivation Lock on SM-G900V in simple steps. Schematically, we will install Android 4.4.2, bypass Samsung Account login, register a new one and then turn Reactivation Lock OFF. The phone will be clear...
forum.xda-developers.com
After that was done, I switched back to step 11 of
2022_VZW_EMMC_15_ AIO_Tool To Unlock_Bootloader+Install_TWRP And MM_QL1_Rooted_Rom Works On Any Version Bootloaders_MM_LL_KK-Reactivation Lock Remover
This Process Will Root Phone Unlock Your VZW EMMC 15 Chipset Bootloader Install TWRP Recobery And Imstall Latest QL1 Stock Rom . Downloads S5_Root_Tools_2023.7z EMMC_15_Rom.zip -- Stock QL1 6.0 Directions For Unlocking Stock Phone I would...
forum.xda-developers.com
to unlock bootloader.
I did not boot into 6.0.1 but immediately installed Lineage 18.1 and all worked.
Click to expand...
Click to collapse
If you would have scrolled down a little farther on the my thread there was instruction and rom needed to remove reactivation lock

Categories

Resources