so i rooted my first android device about 6 hours ago went great. how ever i made a rookie mistake and turned off the oem unlock after I was finished now I'm stuck and fear i may have hard bricked my device, i used odin 3 with twrp 3.0.2 and installed the supersu even made backups using both twrp recovery and titanium backup. but when i rebooted my device im stuck in the boot loop with a red message stating custom binary blocked by frp lock. and recovery mode is not accessable, only option is download mode. ok so i tried to go back to the stock rom but i get custom binary(recover) blocked by frp lock. is there a solution here or did i prema brick my phone.
im not new to the modding process i have done a few other devices just never rooted a phone before today.
any ideas on what i should try next
FISBANREGNER said:
so i rooted my first android device about 6 hours ago went great. how ever i made a rookie mistake and turned off the oem unlock after I was finished now I'm stuck and fear i may have hard bricked my device, i used odin 3 with twrp 3.0.2 and installed the supersu even made backups using both twrp recovery and titanium backup. but when i rebooted my device im stuck in the boot loop with a red message stating custom binary blocked by frp lock. and recovery mode is not accessable, only option is download mode. ok so i tried to go back to the stock rom but i get custom binary(recover) blocked by frp lock. is there a solution here or did i prema brick my phone.
im not new to the modding process i have done a few other devices just never rooted a phone before today.
any ideas on what i should try next
Click to expand...
Click to collapse
any help with this would be great im looking for the latest firmware for the sm-g550t1 the rev00 doesnt work because of version mismatch
FISBANREGNER said:
so i rooted my first android device about 6 hours ago went great. how ever i made a rookie mistake and turned off the oem unlock after I was finished now I'm stuck and fear i may have hard bricked my device, i used odin 3 with twrp 3.0.2 and installed the supersu even made backups using both twrp recovery and titanium backup. but when i rebooted my device im stuck in the boot loop with a red message stating custom binary blocked by frp lock. and recovery mode is not accessable, only option is download mode. ok so i tried to go back to the stock rom but i get custom binary(recover) blocked by frp lock. is there a solution here or did i prema brick my phone.
im not new to the modding process i have done a few other devices just never rooted a phone before today.
any ideas on what i should try next
Click to expand...
Click to collapse
ok so i was having an issue where i bricked my metropcs sm-g550t1 (galaxy on5) when i downloaded the stock rom for my phone i would get a sw mismatch D2 B1 error. the reason for this error is the update that came out in the beginning of 2017 changed the firmware version from PF1 to PL1. so if you are also having this problem when trying to unbrick your phone use the firmware for phone SM-G550T2 then use your twrp backup to unbrick but remember to turn the oem unlock on or you will brick your phone again
I was trying to root my phone
odin failed and my phone showed "Custom Binary (Recovery): Blocked By FRP Lock"
I was following this video
https://www.youtube.com/watch?v=M8ji0yjf7IY
What went wrong ?
johngr77 said:
Probably you forgot to enable OEM unlock in developer options menu
Click to expand...
Click to collapse
I did that and I successfully installed the twrp file
Then the phone rebooted and now it is stuck in the Samsung logo !!
What should I do ?
look through this forum - i only put the answer on here yesterday
JUST FLASH with latest stock firmware.. 1st of all to get phone into main screen/ activation lock screeen
asadnow2k said:
JUST FLASH with latest stock firmware.. 1st of all to get phone into main screen/ activation lock screeen
Click to expand...
Click to collapse
I did that and its working again
But How can I root it now ?
I tried rooting it again the same way but it got stuck on logo screen again !
is there any alternative way to root it ?
HussainJH said:
I did that and its working again
But How can I root it now ?
I tried rooting it again the same way but it got stuck on logo screen again !
is there any alternative way to root it ?
Click to expand...
Click to collapse
you just install frimware latest one and activate it with ur google account. than oem unlock than flash with root via odin
Im having this issue with my phone i accidently ticked off the oem unlock in development settings I put the phone in download mode because thats the only mode i can get into (recovery and regular boot does not work) when I connect to pc now it shows up as usb serial device in ports or it shows up as samsung modem and odin wont flash the firmware
I never had any issue. You get a single recovery.IMG and flash it. The s6e+ is tricky. You should have a custom ROM or what you want to flash ready and just flash twrp, boot immediately into it. Backup phone via twrp then wipe it and flash custom ROM. This will ensure you don't get any real issues or fpr blocked. Also use XDA tuts or get help here, YouTube can go good or bad. Recovery images are device specific. If you have f and flash t it won't work. You have to really look at what you are flashing and match model information. I'm seeing a lot of people fpr blocked and in trouble. I might go make a little walkthrough
soooo.. full FRP lock
SM-G550T1 (metropcs)
limited odin
BL/AP Fail.
CP and CSC Write
Promts during boot to go to smart switch can not get S/N from sticker
Cannot boot into recovery FRP locked
Bootloader cant boot FRP Locked
Ideas?
Codebreaker32 said:
soooo.. full FRP lock
SM-G550T1 (metropcs)
limited odin
BL/AP Fail.
CP and CSC Write
Promts during boot to go to smart switch can not get S/N from sticker
Cannot boot into recovery FRP locked
Bootloader cant boot FRP Locked
Ideas?
Click to expand...
Click to collapse
What firmware are you on? You can't boot into recovery, but does your phone boot into the OS and through to the Google verification screen?
Drunkpilot said:
What firmware are you on? You can't boot into recovery, but does your phone boot into the OS and through to the Google verification screen?
Click to expand...
Click to collapse
Nope
Samsung On5 Screen with strictly in text upper left Custom Binary Blocked by [FRP] then it loops boot
Codebreaker32 said:
Nope
Samsung On5 Screen with strictly in text upper left Custom Binary Blocked by [FRP] then it loops boot
Click to expand...
Click to collapse
Funny enough, the exact same thing happened to me this afternoon. I had turned off "OEM unlock" and "USB debugging" in developer options and rebooted. I know exactly what you're talking about and I fixed it. I used Odin and flashed the 4 files with "nand erase all" checked in options. I flashed the G550TUVS2APL1 firmware. That is the rom I was on. I had previously tried flashing the G550TUVU1APF1 firmware for another issue and like you, I could only get the CP and CSC to pass, everything else was fail and it broke the modem and left me with no reception until I flashed the correct modem once again. The firmware you flashed was not the correct one. Flash the correct one and you will see your phone reboot into the startup wizard once again. Two minutes and my phone was up and running once again.
Recently, I turned off developer options in my rooted S7 Edge (SM-G935FD). Idk if that is the cause, but after rebooting I got the error "Custom Binary Blocked by FRP Lock". I couldnt boot into my recovery (TWRP) either. I was running on Oreo btw. I watched some Youtube guides and apparently the solution was to flash stock rom. So... I flashed an Oreo Stock Rom on my phone via Odin. I thought that would solve my problem, but instead it made it worse. It didnt give me the Custom Binary Blocked by FRP lock error but my boot screen is stuck at the boot animation (not a bootloop). I could boot into the stock recovery tho. I tried a factory reset, that didnt make things better. I could also boot into download mode. I thought I made a mistake, so I flashed like 5-8 times with both CSC an Home_CSC. The result was the same, it would get stuck at the boot animation. I tried flashing TWRP via Odin too, but it said "Custom Binary (Recovery) blocked by FRP Lock". I tried sideloading that TWRP file to my device via ADB. It gave me an error too (I think "Cannot flash from external devices" or something like that) I thought flashing with Re-partition and Nand Erase On would solve my problem, so I tried that, but it didnt work. Im running on Binary 3 apparently. Is there anything I can do?
Rapidfayaround said:
Recently, I turned off developer options in my rooted S7 Edge (SM-G935FD). Idk if that is the cause, but after rebooting I got the error "Custom Binary Blocked by FRP Lock". I couldnt boot into my recovery (TWRP) either. I was running on Oreo btw. I watched some Youtube guides and apparently the solution was to flash stock rom. So... I flashed an Oreo Stock Rom on my phone via Odin. I thought that would solve my problem, but instead it made it worse. It didnt give me the Custom Binary Blocked by FRP lock error but my boot screen is stuck at the boot animation (not a bootloop). I could boot into the stock recovery tho. I tried a factory reset, that didnt make things better. I could also boot into download mode. I thought I made a mistake, so I flashed like 5-8 times with both CSC an Home_CSC. The result was the same, it would get stuck at the boot animation. I tried flashing TWRP via Odin too, but it said "Custom Binary (Recovery) blocked by FRP Lock". I tried sideloading that TWRP file to my device via ADB. It gave me an error too (I think "Cannot flash from external devices" or something like that) I thought flashing with Re-partition and Nand Erase On would solve my problem, so I tried that, but it didnt work. Im running on Binary 3 apparently. Is there anything I can do?
Click to expand...
Click to collapse
I still have the "FRP Lock: On" on download mode, so I tried bypassing FRP lock via binary 5 combination firmware and flashing a binary 7 stock firmware. This time, it doesnt get stuck at the boot animation, instead it redirects to a screen with an android face saying "Installing System updates". A few seconds later, it says "No command" with a dead android face. Then it reboots and the same thing happens. Basically a boot loop, but in a different way. I cant seem to boot to stock recovery either. The worst thing is that I cant even turn off the thing. I have to leave it loop for the entire day until its battery dies
Rapidfayaround said:
I still have the "FRP Lock: On" on download mode, so I tried bypassing FRP lock via binary 5 combination firmware and flashing a binary 7 stock firmware. This time, it doesnt get stuck at the boot animation, instead it redirects to a screen with an android face saying "Installing System updates". A few seconds later, it says "No command" with a dead android face. Then it reboots and the same thing happens. Basically a boot loop, but in a different way. I cant seem to boot to stock recovery either. The worst thing is that I cant even turn off the thing. I have to leave it loop for the entire day until its battery dies
Click to expand...
Click to collapse
after flashing the combination firmware, flash the stock firmware and go thru the boot process
Youdoofus said:
after flashing the combination firmware, flash the stock firmware and go thru the boot process
Click to expand...
Click to collapse
That is what I literally did. I flashed a combination firmware, factory rested my entire phone, turned on developer options as well as allow usb debugging, attempted to reset FRP via Z3X Samsung Tool Pro and finally flashed a stock rom. And, the result is this. A bootloop with an android face dying. I did manage to enter a different screen by pressing volume up once along with pressing volume down and power button. It said "could not open recovery_because_no file directory" and had some more errors. The thing is....I made it worse at the first place. I could have flashed a room with binary 6 or lower, cuz at least the combination firmware would have been available to flash, but my stupid brain did not think of that. I flashed a binary 7 stock rom and there is no combination firmware with a binary of 7 or more. Which means, I will most likely get the "SW check fail Device: 7 Binary: 6 " error while flashing.
Rapidfayaround said:
That is what I literally did. I flashed a combination firmware, factory rested my entire phone, turned on developer options as well as allow usb debugging, attempted to reset FRP via Z3X Samsung Tool Pro and finally flashed a stock rom. And, the result is this. A bootloop with an android face dying. I did manage to enter a different screen by pressing volume up once along with pressing volume down and power button. It said "could not open recovery_because_no file directory" and had some more errors. The thing is....I made it worse at the first place. I could have flashed a room with binary 6 or lower, cuz at least the combination firmware would have been available to flash, but my stupid brain did not think of that. I flashed a binary 7 stock rom and there is no combination firmware with a binary of 7 or more. Which means, I will most likely get the "SW check fail Device: 7 Binary: 6 " error while flashing.
Click to expand...
Click to collapse
If the device is still entering download mode, install the recent version of stock for your device. Maybe that will solve your problem.
Rapidfayaround said:
That is what I literally did. I flashed a combination firmware, factory rested my entire phone, turned on developer options as well as allow usb debugging, attempted to reset FRP via Z3X Samsung Tool Pro and finally flashed a stock rom. And, the result is this. A bootloop with an android face dying. I did manage to enter a different screen by pressing volume up once along with pressing volume down and power button. It said "could not open recovery_because_no file directory" and had some more errors. The thing is....I made it worse at the first place. I could have flashed a room with binary 6 or lower, cuz at least the combination firmware would have been available to flash, but my stupid brain did not think of that. I flashed a binary 7 stock rom and there is no combination firmware with a binary of 7 or more. Which means, I will most likely get the "SW check fail Device: 7 Binary: 6 " error while flashing.
Click to expand...
Click to collapse
the "no such file or directory" error is due to either having had removed stock recovery in flashing the firmwares or the factory recovery corrupted due to likely the same reason. Just flash a revision 7 firmware for your phone and it will at least boot
Dark Stranger said:
If the device is still entering download mode, install the recent version of stock for your device. Maybe that will solve your problem.
Click to expand...
Click to collapse
^^^ this ^^^
Dark Stranger said:
If the device is still entering download mode, install the recent version of stock for your device. Maybe that will solve your problem.
Click to expand...
Click to collapse
I have literally flashed the latest stock rom for my device and my country which is G935FXXS7ESK8.
I am a bit confused tho...I am not sure if my device is SM-G935FD or SM-G935F. The download mode says SM-G935F...but this phone used to work with a SM-G935FD rom back in the days. Is this causing the problem most likely? And btw the repair shop said they cant fix it too
Rapidfayaround said:
I have literally flashed the latest stock rom for my device and my country which is G935FXXS7ESK8.
I am a bit confused tho...I am not sure if my device is SM-G935FD or SM-G935F. The download mode says SM-G935F...but this phone used to work with a SM-G935FD rom back in the days. Is this causing the problem most likely? And btw the repair shop said they cant fix it too
Click to expand...
Click to collapse
I am somehow relieved to know that someone else on this planet is on the same (EXACT) boat as me....this is what we get for messing around too much with our phone hum?
1 - After booting up my phone I get the blue background with a dead Android and "No Command" message
2 - I tried accessing recovery by pressing Power+Home+VolumeUp, but all I get is a black screen with a wall of code lines with "fail to open recovery_cause(No such file or directory)" at the beggining of the text.
3 - "No problem! I'll just flash TWRP with ODIN and install a custom ROM and be done with it!".
..NOPE! FRP(factory reset protection) is ON!!! I cannot install TWRP
4- I've tried to find a combination file with binary version 7...but looks like the internet doesn't seem to care about the good ol' number 7...All I can find is binary version 6.
What Im trying to do now is creating my own combination file binary version 7 (if that's even a thing...) from a stock firmware. But I'm not getting any luckier down this path.
Looks like we need a hero...:crying:
PseudoNoob said:
I am somehow relieved to know that someone else on this planet is on the same (EXACT) boat as me....this is what we get for messing around too much with our phone hum?
1 - After booting up my phone I get the blue background with a dead Android and "No Command" message
2 - I tried accessing recovery by pressing Power+Home+VolumeUp, but all I get is a black screen with a wall of code lines with "fail to open recovery_cause(No such file or directory)" at the beggining of the text.
3 - "No problem! I'll just flash TWRP with ODIN and install a custom ROM and be done with it!".
..NOPE! FRP(factory reset protection) is ON!!! I cannot install TWRP
4- I've tried to find a combination file with binary version 7...but looks like the internet doesn't seem to care about the good ol' number 7...All I can find is binary version 6.
What Im trying to do now is creating my own combination file binary version 7 (if that's even a thing...) from a stock firmware. But I'm not getting any luckier down this path.
Looks like we need a hero...:crying:
Click to expand...
Click to collapse
OMGGGGGGGG....Looks like I am not the only one. DAMN. Bro...tell me if you find a solution ok? Hopefully there is a way to solve this problem...there has to be one. And share your combination firmware after you finish it. Thank you very much
Rapidfayaround said:
OMGGGGGGGG....Looks like I am not the only one. DAMN. Bro...tell me if you find a solution ok? Hopefully there is a way to solve this problem...there has to be one. And share your combination firmware after you finish it. Thank you very much
Click to expand...
Click to collapse
No luck over here friend...
Desperate times require desperate measures. Have you ever tried flashing combination files from different S7 Edge versions?
I can find files for the G935A with a revision 7 of the binary...Im thinking flashing it into my G935F and see what happens. I've read the risks associated with installing firmwares from other phone versions, but I'll have a paperweight either way.
I'll keep this thread updated.
Rapidfayaround said:
I have literally flashed the latest stock rom for my device and my country which is G935FXXS7ESK8.
I am a bit confused tho...I am not sure if my device is SM-G935FD or SM-G935F. The download mode says SM-G935F...but this phone used to work with a SM-G935FD rom back in the days. Is this causing the problem most likely? And btw the repair shop said they cant fix it too
Click to expand...
Click to collapse
Doesn't really matter if you have a F or FD. I'd say you flash the latest stock rom for G935F or FD(which ever is latest) for any country regardless. By this you should be able to boot and won't get any odin errors.
UsmaniMustafa said:
Doesn't really matter if you have a F or FD. I'd say you flash the latest stock rom for G935F or FD(which ever is latest) for any country regardless. By this you should be able to boot and won't get any odin errors.
Click to expand...
Click to collapse
Can you provide me the link plz.
Turns out, its a hardware problem with the storage. Replacing the motherboard might be the solution I think. :/
I had solved my phone last day
At first u can flash ur phone to leatest stock rom. Then u have to turn of frp lock. Then u will able to boot up your phone. If u cant fix u can knock me on facebook. (If u r a z3x user). Bcoz u need z3x for bypass frp with ufs cable.
Im also using s7 edge.
hazratboss said:
At first u can flash ur phone to leatest stock rom. Then u have to turn of frp lock. Then u will able to boot up your phone. If u cant fix u can knock me on facebook. (If u r a z3x user). Bcoz u need z3x for bypass frp with ufs cable.
Im also using s7 edge.
Click to expand...
Click to collapse
Oh ok I will contact you
hazratboss said:
At first u can flash ur phone to leatest stock rom. Then u have to turn of frp lock. Then u will able to boot up your phone. If u cant fix u can knock me on facebook. (If u r a z3x user). Bcoz u need z3x for bypass frp with ufs cable.
Im also using s7 edge.
Click to expand...
Click to collapse
Does it matter if I use the cracked version without box. And no, I dont have the ufs cable. Is there anything else I can do?
Hi guys, I have the exact same problem with my S7 edge from T-mobile (g935t). Odin will only accept for flash the latest rom and after flash it reboots but I get BSOD. I tried a pit file also from an old g935T rom which was android 6.0 and I managed to get into recovery for a moment and I did a factory reset/wipe cache but after reboot entered again in a black screen and the blue led was lit. I finally removed the battery to turn the phone off. I can still enter download mode but is there anything else I can do to resurrect the phone?
Samsung s7 edge (g935f)
Hi everyone , please am having issue of NO COMMAND and i cant boot into recovery. My oem is on so i cant install twpr neither. Am on binary u8. Please any solution to recover my phone?
Very very good new guys...yep you guessed it right. I was able to fix this problem.
How you may ask? Follow these steps
Note: Make sure you have enough battery. Lack of battery charge in my case caused alot of problems.
1. Download a U7 Rom for your SM-G935F or SM-G935FD
2. Extract the Rom as well as the AP
3. After you extract the AP, you will be greeted with boot.lz4.img , recovery.lz4.img , system.lz4.img & meta-data
4. Make a backup of recovery.lz4.img and meta-data just in case. Also, make a copy of boot.lz4.img and rename the copied one to recovery.lz4.img. Don't forget to delete the original recovery and meta-data
5. Now, you should be left with boot.lz4.img , (modified) recovery.lz4.img and system.lz4.img.
6. Now, download this https://www.mediafire.com/file/ah20ha869prdkkc/Autotar2.0_By_FixFirmwares.com.rar/file
7. Now, make a .md5 file that contains (modified) recovery.lz4.img and system.lz4.img
8. After you are done making that .md5, flash it along with CSC, CP and BL.
9. You should directly boot into your device, (if you do), charge your phone for a while if the battery is lower than 20%.
10. Then, go to the settings and enable OEM Unlock before doing ANYTHING
11. Then, reboot to download mode and flash TWRP
12. Download the no-verity-encryption.zip
https://zackptg5.com/android.php#disverfe
13. Allow system modifications and format data (NOT WIPE)
14. If that doesn't work, go to TWRP, connect it to your PC and copy the no-verity-encryption.zip file and install it
15. If that still doesn't work then, follow this tutorial
https://www.google.com/amp/s/forum....niversal-dm-verity-forceencrypt-t3817389/amp/
16. Then, you should boot and yea...enjoy ?
If this method doesn't work then, you need to try different combinations.
Try packing these files in AP
1. Boot.lz4.img, (Modified) Recovery.lz4.img & system.lz4.img
2. (Modified) Recovery.lz4.img & system.lz4.img
3. Meta-data, Boot.lz4.img, (Modified) Recovery.lz4.img & system.lz4.img
If that doesn't work, I'm sorry this is how I fixed it. ?*
For anyone wondering how I fixed it well, firstly a HUGE THANKS TO @shah22 & @Tapas27sTapas2. This would have been LITERALLY IMPOSSIBLE WITHOUT THEM. So, basically I tried an AP with renamed recovery.lz4.img and system.lz4.img only along with CP, CSC and BL. Due to my phone having literally 0%, this journey was very difficult.
Feel free to ask any question
Very very good new guys...yep you guessed it right. I was able to fix this problem.
How you may ask? Follow these steps
Note: Make sure you have enough battery. Lack of battery charge in my case caused alot of problems.
1. Download a U7 Rom for your SM-G935F or SM-G935FD
2. Extract the Rom as well as the AP
3. After you extract the AP, you will be greeted with boot.lz4.img , recovery.lz4.img , system.lz4.img & meta-data
4. Make a backup of recovery.lz4.img and meta-data just in case. Also, make a copy of boot.lz4.img and rename the copied one to recovery.lz4.img. Don't forget to delete the original recovery and meta-data
5. Now, you should be left with boot.lz4.img , (modified) recovery.lz4.img and system.lz4.img.
6. Now, download this https://www.mediafire.com/file/ah20ha869prdkkc/Autotar2.0_By_FixFirmwares.com.rar/file
7. Now, make a .md5 file that contains (modified) recovery.lz4.img and system.lz4.img
8. After you are done making that .md5, flash it along with CSC, CP and BL.
9. You should directly boot into your device, (if you do), charge your phone for a while if the battery is lower than 20%.
10. Then, go to the settings and enable OEM Unlock before doing ANYTHING
11. Then, reboot to download mode and flash TWRP
12. Download the no-verity-encryption.zip
https://zackptg5.com/android.php#disverfe
13. Allow system modifications and format data (NOT WIPE)
14. If that doesn't work, go to TWRP, connect it to your PC and copy the no-verity-encryption.zip file and install it
15. If that still doesn't work then, follow this tutorial
https://www.google.com/amp/s/forum....niversal-dm-verity-forceencrypt-t3817389/amp/
16. Then, you should boot and yea...enjoy ?
If this method doesn't work then, you need to try different combinations.
Try packing these files in AP
1. Boot.lz4.img, (Modified) Recovery.lz4.img & system.lz4.img
2. (Modified) Recovery.lz4.img & system.lz4.img
3. Meta-data, Boot.lz4.img, (Modified) Recovery.lz4.img & system.lz4.img
If that doesn't work, I'm sorry this is how I fixed it. ?*
For anyone wondering how I fixed it well, firstly a HUGE THANKS TO @shah22 & @Tapas27s. This would have been LITERALLY IMPOSSIBLE WITHOUT THEM. So, basically I tried an AP with renamed recovery.lz4.img and system.lz4.img only along with CP, CSC and BL. Due to my phone having literally 0%, this journey was very difficult.
Feel free to ask any question
Hi there,
I have a Samsung Galaxy Tab A6 (SM-T285) which I bought today. I followed this tutorial to install twrp, ultimately to root the device:
I can't even post links so sad. But the link was of **********.
Everything worked fine and I was able to boot and reboot fine. Until I signed in with my Google Account. After trying to reboot, I get a black screen with the Samsung logo and a text in red saying: Custom binary blocked by FRP Lock. I went back to the store and they advised me to install Samsung Smart Switch to try and restore. In the Smart Switch program I get an error saying that the device is not supported by Smart Switch.
I can get into download mode, not into any other mode. I can't get into recovery mode. The tablet doesn't start up at all. On the download mode it also says FRP Lock ON.
When I go back into ODIN and retry to install the from above TWRP image, it says operation failed.
Can anybody please advice? I am at a complete loss. Am I supposed to flash the original boot file? Where can I find that for my device? Will my tablet accept that, since ODIN didn't even want to flash my current TWRP image a second time?
P.S. I only read later that you are supposed to change the OEM setting. I didn't. Is that the cause of this issue, and if so, can I do something about it?
Thanks
Pro_Gamer368 said:
Hi there,
I have a Samsung Galaxy Tab A6 (SM-T285) which I bought today. I followed this tutorial to install twrp, ultimately to root the device:
I can't even post links so sad. But the link was of **********.
Everything worked fine and I was able to boot and reboot fine. Until I signed in with my Google Account. After trying to reboot, I get a black screen with the Samsung logo and a text in red saying: Custom binary blocked by FRP Lock. I went back to the store and they advised me to install Samsung Smart Switch to try and restore. In the Smart Switch program I get an error saying that the device is not supported by Smart Switch.
I can get into download mode, not into any other mode. I can't get into recovery mode. The tablet doesn't start up at all. On the download mode it also says FRP Lock ON.
When I go back into ODIN and retry to install the from above TWRP image, it says operation failed.
Can anybody please advice? I am at a complete loss. Am I supposed to flash the original boot file? Where can I find that for my device? Will my tablet accept that, since ODIN didn't even want to flash my current TWRP image a second time?
P.S. I only read later that you are supposed to change the OEM setting. I didn't. Is that the cause of this issue, and if so, can I do something about it?
Thanks
Click to expand...
Click to collapse
Reinstall stock rom
Change OEM setting in Developer Options
Then you install TWRP - Turn off auto reboot in TWRP
After ODIN install, manually reboot to recovery.
gcrutchr said:
Reinstall stock rom
Change OEM setting in Developer Options
Then you install TWRP - Turn off auto reboot in TWRP
After ODIN install, manually reboot to recovery.
Click to expand...
Click to collapse
wait......... do i off oem unlock or on it
Pro_Gamer368 said:
wait......... do i off oem unlock or on it
Click to expand...
Click to collapse
slide the button to the right
gcrutchr said:
slide the button to the right
Click to expand...
Click to collapse
thanks, you're a legend :good::good::good: