Database Info

FRP Lock - unable to boot and flash

I recently bought an S7 and wanted to root. It's my first Samsung phone so the software is new to me so apologies if there is an easy answer. I (extremely stupidly) re-enabled FRP lock within Android after rooting (hoping that it was stop the unauthorised actions warning). This now means when i start the phone it states "Custom Binary Blocked by FRP lock" and would not boot in to Android. I've read some threads but the current situation is:
1) When i tried to boot it would not boot to Android and stuck at the first splash screen and warning. Whilst i had rooted i did not flash twrp so only have the stock recovery.
2) I went in to the stock recovery and did a factory reset and cache clear. No change.
3) I tried Smart switch and kies - no luck - both said un-supported device or hung on connecting
4) I went to the thread with the most recent stock download (Netherlands) and downloaded that. I tried to install that and it hung for about an hour. I disconnected and it now says "An error has occurred whilst updating the device software" and does not boot.
So i cannot boot in to Android, have no custom recovery and KIES/SmartSwap do not work.
Any ideas????!?!?

Download the latest MM stock rom and try to bypass the frp lock.

lord_melchett said:
I recently bought an S7 and wanted to root. It's my first Samsung phone so the software is new to me so apologies if there is an easy answer. I (extremely stupidly) re-enabled FRP lock within Android after rooting (hoping that it was stop the unauthorised actions warning). This now means when i start the phone it states "Custom Binary Blocked by FRP lock" and would not boot in to Android. I've read some threads but the current situation is:
1) When i tried to boot it would not boot to Android and stuck at the first splash screen and warning. Whilst i had rooted i did not flash twrp so only have the stock recovery.
2) I went in to the stock recovery and did a factory reset and cache clear. No change.
3) I tried Smart switch and kies - no luck - both said un-supported device or hung on connecting
4) I went to the thread with the most recent stock download (Netherlands) and downloaded that. I tried to install that and it hung for about an hour. I disconnected and it now says "An error has occurred whilst updating the device software" and does not boot.
So i cannot boot in to Android, have no custom recovery and KIES/SmartSwap do not work.
Any ideas????!?!?
Click to expand...
Click to collapse
Flash latest nougat Stock rom from sammobile using The latest ODIN software. You shouldnt disable OEM unlock next time you root/install custom recovery to your phone or else this will happen again, and you'll have to flash stock firmware again.

Stuck on Boot screen after flashing TWRP

Hello,
I just flashed the latest ROM for the S8+ (AQL5) and that went well.
Afterwards I tried to flash TWRP, but now the phone is stuck on the Samsung screen.
I then followed the guide I found here to use the BL file of AQF7 in Odin and spam the Start button so I managed to get into TWRP.
Question is, what do I do next? I restart the system it's the same problem all over again.
No one explains anywhere what to do in TWRP to save the phone.
Can I remove TWRP or somehow save the phone (without wiping my data)
Please help

Can you get to download mode? Then go to ODIN and redo your flashing of the OS and then TWRP. After the flash of TWRP, immediately boot into TWRP, and do Verity if you want that, and your root, if not already done. Clear Dalvik/cache and reboot to system.
It is not uncommon for folks, following TWRP flash, to get stuck in boot loop, unfortunately. Can take a little time, but you will get through it and finally to System.

But I thought all new firmware versions are incompatible with TWRP and cause this error.
I might try to install TWRP again if I flash the latest compatible version (I think it's the F7 one).
Does "Verify" in TWRP make that annoying "Your phone is not verified" message go away? The only option is to Reset phone when that thing comes up and I don't want to do that.
I managed to get out of that by reflashing the AQL5 version and just not installing TWPR.
Kind of scared to retry because everything goes wrong when I try to follow the guides on here or youtube

nkomp18 said:
But I thought all new firmware versions are incompatible with TWRP and cause this error.
I might try to install TWRP again if I flash the latest compatible version (I think it's the F7 one).
Does "Verify" in TWRP make that annoying "Your phone is not verified" message go away? The only option is to Reset phone when that thing comes up and I don't want to do that.
I managed to get out of that by reflashing the AQL5 version and just not installing TWPR.
Kind of scared to retry because everything goes wrong when I try to follow the guides on here or youtube
Click to expand...
Click to collapse
Would you please provide the info from my first post? and Exynos of Snapdragon?

JeffDC said:
Would you please provide the info from my first post? and Exynos of Snapdragon?
Click to expand...
Click to collapse
I have Exynos - model SM-G955F
Yes I can go to download mode but I won't do the things you ask because they're guaranteed to soft-brick the phone again and I have it working now

i have the same problem, followed this guide https://forum.xda-developers.com/galaxy-s8/how-to/guide-how-to-root-galaxy-s8-crgh-rom-t3846009 managed to get to TWRP no problems, once i reset the device though im stuck at the samung galaxy s8+ boot screen and can't get it off
any suggestions ? i did try to search but this old thread was the only relevant one i could find

stuck on boot screen after flashing twrp for magisk manager
i flashed magisk manager in twrp youtube.com/watch?v=r3R9kiBIx34 by this and now not booting to android . before i had this i reflashed miui 11 using official software and coulnt be sucess this time also please help me any one . my mobile is redmi 6 pro.:crying::crying::crying::crying:

Oem locked, frp block, and drk help

Hey guys. I'm in a hell of a bind and could use some help.
My Galaxy Note 5 (N920T, rooted) was running fine on this ROM: https://forum.xda-developers.com/tm...m-qc6-lite-rom-bloated-knoxed-odexed-t3598686 ; however, I had disabled OEM unlock at one point to try and fix a random app I was playing with. The battery died not long after, causing the phone to reboot. On power, it failed to boot due to custom binary block from FRP, so I decided to try and run the usual troubleshooting of flashing a stock ROM via Odin. Stock images will flash (tried 5.1.1, 6.1, and 7); however, when they try to install I get the error for no DRK. Sometimes I'll also get a dm-verity error as well... So I then tried to flash TWRP or any recovery via Odin to let me fix this issue; however, any custom recoveries I try to flash are being blocked by FRP.
So, I'm in a loop. I can't use my initial ROM because FRP, however I also can't install a stock ROM because of missing DRK, AND I can't fix the DRK or verity errors because I can't install a recovery capable of doing so because of FRP.
IMEI is intact when I look into Download mode, but I can't seem to get anything to work. I've tried the FRP Tool and crack, but that gives me FRP blocks as well (USERDATA).
Am I boned?

B U M P
Anyone?

same situation, going to try flashing it to stock. Can we just flash a stock bootloader or do we need to start over?
Got it working by flashing stock rom with odin so maybe not exact same situation as you. Hard to find a filehosting site with good download speeds and spent all day trying to get latest stock note 5 firmware. Well good for now.. All started because of a wrong flip of a switch *bangs head on desk*

You need to do a few things. First you need to wipe everything in TWRP including format data, so love your files to some other storage. In Odin go to options and turn off auto reboot. Turn on f reset time, phone bootloader update and Nand Erase All. You need to know that this doesn't always work, if you can't unlock it this way try disabling encryption after flashing stock and TWRP and flash Magisk. Let me know how it goes.

Metabolic12 said:
You need to do a few things. First you need to wipe everything in TWRP including format data, so love your files to some other storage. In Odin go to options and turn off auto reboot. Turn on f reset time, phone bootloader update and Nand Erase All. You need to know that this doesn't always work, if you can't unlock it this way try disabling encryption after flashing stock and TWRP and flash Magisk. Let me know how it goes.
Click to expand...
Click to collapse
Got as far as getting the firmware flashed via Odin, but when I first boot I get "Device does not have DRK" error. I cannot install TWRP or any custom recovery through Odin due to FRP lock.

x24veggie said:
Got as far as getting the firmware flashed via Odin, but when I first boot I get "Device does not have DRK" error. I cannot install TWRP or any custom recovery through Odin due to FRP lock.
Click to expand...
Click to collapse
if all you are getting is frp lock just flash back to stock like I did and start over rooting etc.

craig198 said:
if all you are getting is frp lock just flash back to stock like I did and start over rooting etc.
Click to expand...
Click to collapse
That's not all. Basically, it goes,
Flash back to stock
Reboot
Can't finish ROM install because DRK is unavailable
Can't install anything in locked, stock android recovery
TWRP, autoroot, etc. is blocked from Odin by FRP

craig198 said:
same situation, going to try flashing it to stock. Can we just flash a stock bootloader or do we need to start over?
Got it working by flashing stock rom with odin so maybe not exact same situation as you. Hard to find a filehosting site with good download speeds and spent all day trying to get latest stock note 5 firmware. Well good for now.. All started because of a wrong flip of a switch *bangs head on desk*
Click to expand...
Click to collapse
No. It started because you didn't back up your phone properly with twrp before going flash crazy
---------- Post added at 08:52 AM ---------- Previous post was at 08:47 AM ----------
x24veggie said:
That's not all. Basically, it goes,
Flash back to stock
Reboot
Can't finish ROM install because DRK is unavailable
Can't install anything in locked, stock android recovery
TWRP, autoroot, etc. is blocked from Odin by FRP
Click to expand...
Click to collapse
https://www.google.ca/amp/s/forum.x...to-solve-dm-verity-verification-t3293306/amp/ have you tried this? If we can figure this out please don't ever play with oem or have a stock recovery ? that's your security blanket

[Bricked] One of the harder ones =|

I'm gonna keep it simple, here is the scenario:
ROM is corrupted.
Bootloader is unlocked.
FRP lock is on. (fastboot can't do much)
TWRP was flashed back to stock.
Stock hard-reset fails. (even wipe option)
Force upgrade stops at 5% (swear I am using the same one)
eRecovery does not work.
Can't flash. Can't push files.
Wat do.
Model: BLN-L24C567B369 (pretty sure this was it)
Whole story:
This whole episode began when I wanted to install Magisk to use MagiskManager's HideMe feature. This required me to install TWRP recovery which inturn lead me to unlock my bootloader in the process, straightforward and went off nicely. Now it was time to gain superuser which I already had done before on another device, installing SuperSU through TWRP recovery was painless but after booting found out MagiskManager needs Magisk Root to work. I then followed Android Exlpained's article to do so. Running unSU through recovery went smoothly but running Magisk didn't, on the initial run I was prompted to use Adrian DC's BootBridge which after removing a few Assert lines ran nicely. However there was no root install, SuperSU was removed though.
At the time I wasn't sure what exactly I was doing and ended up soft-bricking by flash boot through TWRP, at this time FRP was unlocked. After many many hours I restored to stock firmware by using YMNDLZ's guide. I used BLN-L24C567B370(OTA-MF-FULL) for the img files then proceed to flash the vendor.img using TWRP and the rest (boot.img, recovery.img, system.img) using fastboot in that order as instructed. The only part which didn't work was the forced update, it always failed at 5% however after more hours going recovery mode (now stock) wiping the cache and data/factory reset did the trick (Note: my model showed BLN-L24C567B369). I proceeded to reinstall TWRP, installed MagiskManager, tried to install Magisk 16.0 which ran but didn't root me but was fine because MagiskManager's download worked. I then thought since I went through all this trouble might as well install a custom rom, EliteRom was my ROM of choice. At this point I had logged in with my gmail credentials FRP was now locked.
*Before further action was taken I took the precaution to backup my current stable stock ROM after installing EliteROM but before booting*
The steps to install EliteROM went by flawlessly, installed EliteTWRP reboot into it, ran EliteROM
went through the setup without any hiccups. However up system restart I the ROM wouldn't boot leading me to boot into my recovery only to be prompted for an encryption password (???). Since I didn't recall setting one, couldn't boot into the OS, and FRP was locked I couldn't read my own internal storage. So I reformatted the internal storage and tried what had worked before, flashing the img files using TWRP then booting into stock recovery wiping cache and data/hard reset. . . this did not work. And here I am FRP locked so fastboot isn't useful (I think?), stock recovery doesn't work, eRecovery fails connection, and force update still fails at 5% with "Software install failed!".
Click to expand...
Click to collapse
Lemme know if there is any insight anyone can provide and thanks in advance.

This problem has been solved?

MisterRee said:
I'm gonna keep it simple, here is the scenario:
ROM is corrupted.
Bootloader is unlocked.
FRP lock is on. (fastboot can't do much)
TWRP was flashed back to stock.
Stock hard-reset fails. (even wipe option)
Force upgrade stops at 5% (swear I am using the same one)
eRecovery does not work.
Can't flash. Can't push files.
Wat do.
Model: BLN-L24C567B369 (pretty sure this was it)
Lemme know if there is any insight anyone can provide and thanks in advance.
Click to expand...
Click to collapse
you have to follow only xda methods to root or change to custom rom. i have never heard about flashing stock images from twrp. i think u didn't followed elite rom instructions clearly. you need to formate data then reboot to recovery then wipe everything then flash the os in this way you won't get encription error. anyway now your frp is locked so there is no way to flash twrp so download all the available firmwares for your phone oeminfo then do flashing via dload you will get it worked.
even i was also once stuck with elite rom. i didn't liked it because missing apps icon and forgetting permission. i tried to go back to stock but stuck at 5% error. then went to google searched stock rom for honor 6x india and downloaded nearly 3 roms last one worked helped me to get back to stock.
never flash system images boot,vendor etc from fastboot and twrp unless you are on emui8 and going to try gsi roms.

hey i cant revert back to stock rom. it fails to get package from server. does jio voice calling works on this device?? if no then plz guide me how to go back to stock rom..

MisterRee said:
I'm gonna keep it simple, here is the scenario:
ROM is corrupted.
Bootloader is unlocked.
FRP lock is on. (fastboot can't do much)
TWRP was flashed back to stock.
Stock hard-reset fails. (even wipe option)
Force upgrade stops at 5% (swear I am using the same one)
eRecovery does not work.
Can't flash. Can't push files.
Wat do.
Model: BLN-L24C567B369 (pretty sure this was it)
Lemme know if there is any insight anyone can provide and thanks in advance.
Click to expand...
Click to collapse
Register for update using firmware finder and Puts dns address in the router settings and then use erecovery

Frp lock, stock rom doesn't boot

I used lineage 16 on Galaxy A3 2017 for several weeks without problems. Suddenly when trying to connect to a stored WiFi, nothing happened. Hit reboot to try reconnecting and got into bootloop due to FRP lock. No access to system or recovery possible.
After flashing stock firmware with Odin, stuck at the blinking Samsung logo, so still no access to system. Flashing TWRP fails too due to FRP lock.
An ideas how I can restore the OS, or any OS whatsoever?

Additional info after some more experimenting: Even fastboot is not working at all.
- In recovery, adb finds the device (however, only sideload mode, which is no help here). Fastboot does not.
- In bootloader, neither adb nor fastboot list the device. (Flashing with Odin works, obviously, but is no help since original firmware doesn't boot and TWRP fails due to FRP lock.)
- When stuck at the flashing Samsung logo on system reboot, the phone is recognized by the computer. But again, neither adb nor fastboot list the device.
A lot of dead ends and no more options for me to explore after hours of unsuccessful web-searching. Any help is appreciated, as I am this close to buying an iphone, which is something I promised myself I would never do

bart753 said:
Additional info after some more experimenting: Even fastboot is not working at all.
- In recovery, adb finds the device (however, only sideload mode, which is no help here). Fastboot does not.
- In bootloader, neither adb nor fastboot list the device. (Flashing with Odin works, obviously, but is no help since original firmware doesn't boot and TWRP fails due to FRP lock.)
- When stuck at the flashing Samsung logo on system reboot, the phone is recognized by the computer. But again, neither adb nor fastboot list the device.
A lot of dead ends and no more options for me to explore after hours of unsuccessful web-searching. Any help is appreciated, as I am this close to buying an iphone, which is something I promised myself I would never do
Click to expand...
Click to collapse
Fastboot isn't working because Samsung does not support fastboot.
The XDA rules prevent us from helping you or anyone else in finding a way to bypass FRP lock. It is pointless to ask your question here.
I wish you luck, but we can't help you. Your only options are:
1) remember the original Google email and password.
2) keep searching the internet to find your own method.
Sent from my SM-S767VL using Tapatalk

Droidriven said:
Fastboot isn't working because Samsung does not support fastboot.
The XDA rules prevent us from helping you or anyone else in finding a way to bypass FRP lock. It is pointless to ask your question here.
I wish you luck, but we can't help you. Your only options are:
1) remember the original Google email and password.
2) keep searching the internet to find your own method.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
I would not need to bypass the FRP lock, if I could just boot into system. I know the email and password for the Google account. I just have no means of entering it. The main problem is my phone stuck in bootloop even after flashing the original firmware.

Did some more experimenting and it's getting weirder by the hour.
- Newer versions of the original firmware (downloaded from Sammobile) all fail at flashing "hidden.img". Reverting to older versions is now blocked.
- Tried the newest versions of all available vendors, every single one fails at hidden.img.
- Many reports of other users having this problem, all seem to be solved by removing hidden.img from the CSC archive and packing it again.
- I can flash the firmwares without hidden.img, but again get stuck in the same bootloop at the flashing Samsung logo.
- Flashing the hidden.img alone in AP slot after the rest of the firmware also fails.
- Found no more help online as all threads end after removing the hidden.img.

bart753 said:
Did some more experimenting and it's getting weirder by the hour.
- Newer versions of the original firmware (downloaded from Sammobile) all fail at flashing "hidden.img". Reverting to older versions is now blocked.
- Tried the newest versions of all available vendors, every single one fails at hidden.img.
- Many reports of other users having this problem, all seem to be solved by removing hidden.img from the CSC archive and packing it again.
- I can flash the firmwares without hidden.img, but again get stuck in the same bootloop at the flashing Samsung logo.
- Flashing the hidden.img alone in AP slot after the rest of the firmware also fails.
- Found no more help online as all threads end after removing the hidden.img.
Click to expand...
Click to collapse
After flashing the stock firmware, if it bootloop, boot into stock recovery and factory reset the device then wipe the cache partition then reboot and see if you still bootloop.
Sent from my SM-S767VL using Tapatalk

Droidriven said:
After flashing the stock firmware, if it bootloop, boot into stock recovery and factory reset the device then wipe the cache partition then reboot and see if you still bootloop.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
I just performed those exact steps, bootloop still continues...
Edit: It actually did finally boot after waiting quite some more. (I was just so used to seeing the flashing logo that I didn't believe it possible.)
Not sure which part I was missing before, but somehow it worked now. Thanks man!

bart753 said:
I just performed those exact steps, bootloop still continues...
Edit: It actually did finally boot after waiting quite some more. (I was just so used to seeing the flashing logo that I didn't believe it possible.)
Not sure which part I was missing before, but somehow it worked now. Thanks man!
Click to expand...
Click to collapse
It can take up to an hour when booting for the first time after flashing a new system.
You were probably getting a bootloop due to the user data stored on the device conflicting with the new system. Factory resetting and wiping cache removes the conflicting data and allows the device to boot. Flashing via Odin does not wipe the data from the device during the flashing process unless the firmware being flashed has an upgraded/downgraded bootloader. If the bootloader is the same as the bootloader already on the device, it does not wipe the device during flashing.
Sent from my SM-S767VL using Tapatalk