[Samsung Galaxy J7 ROMs, Kernels, Recoveries, & Oth] dbreed53:
Bricked my J7 (2017) Perx Boost

I screwed Up, BIG TIME!

I applied your recovery several weeks ago, and all was well.

Then I looked for and found a few other variations of modified, STOCK recoveries from links offered by [MENTION=4389243]peter couniaz[/MENTION] and tried them all. All worked, some more pleasing than others. Then I re-applied your original recovery and each of your updates to it.

About a week or ten days passed and I wanted restore to stock, as I had acquired the Samsung firmware to do so.

Then, I wanted to learn how to extract the STOCK FIRMWARE from the phone so I could apply that knowledge to other devices in the future.

Before doing so, I ventured into configuration settings revealed by

Phone INFO ★Samsung★ from vndnguyen

Short story, I ventured too far and made changes related to USB that prevented me from accessing the phone, but could not determine how to correct that.

As a consequence, I could no longer get ADB or Odin to see the COM3 connection on the phone, even though I know for a fact the Developer option to turn the OEM Lock OFF was ON, and USB Debugging was ON.

I struggled overnight, obviously too tired to have been doing this and had consumed some adult beverages as well.

Near sunrise, I thought perhaps the PC and the phone were as confused as I was, and decided we all needed to be rebooted.

Sadly, I forgot that in my many iterations of altering the current state of each device, I had MOST recently turned OFF the switch that turns OFF the OEM Lock, and turned OFF USB debugging.

When the phone rebooted, I realized what I had done, and was presented with a rather chilling message (in a crude, large ANSI style text and pic.

Custom binary blocked by FRP Lock (boot.img)

SECURE FAIL: Boot

with a large yellow triangle with an ! below the text.

The message continues to appear if connected to power or the PC, with this variation;

SECURE FAIL: Kernel

I can no longer enter RECOVERY MODE (VolUp + Home + Power).

I can enter the DOWNLOAD MENU, (VolDown + Home + Power),

BUT the VolUp / VolDown keys no longer work, so I CANNOT start the DOWNLOAD, nor can I cancel.

I can make it reboot by holding the same keys, or the Home + Power key, or the Power key.

I can even enter the DOWNLOAD MENU holding ONLY the Home + Power keys, but the VolUp / VolDown keys still don't work.

There is no longer a Samsung Tech at my local Best Buy/Boost Mobile store, who could have salvaged this BRICKED device.

I have looked here and elsewhere, but haven't yet found a solution I can apply.

I am seeking any suggestions OTHER THAN shipping it to Samsung. At $150 to replace it with a new device at Best Buy/Boost Mobile, the shipping TO Samsung, PLUS cost to repair charged by Samsung (I'm guessing it to easily be $100) plus return shipping they'll charge makes that option untenable.

Plus, I'd rather they DID NOT discover what I put on the device so there are no repercussions for the parties who crafted the recoveries, if that is possible. I don't know if they could but I suspect it's possible, and if they could, in my opinion, they probably would use that knowledge to make flashing even more difficult, or legally risky for those who develop the methods.

I'll even venture so far as to disassembling it to connect to the motherboard, IF it is even possible to do so using a PC and some wiring rig. I have no idea what that entails, but at this point, I'll try anything since it is a total loss otherwise. I've more than 50 years of electronics repair experience, so I'm sure I could do it with the correct tools at hand, I just don't know what they are yet.

I currently have NO PHONE at all, my bill is due tomorrow and I'm about to call Boost to cancel my account until such time as I can purchase a new device. I am on Social Security, so I won't have funds to do so until August 8th. I've been without for a full week today and have no idea what or whom I've missed in the meantime.

I've no one to blame, it's my own fault.

I've since wiped the PC clean and re-installed Win 7 Pro from scratch to ensure I've not diddled the stock connectivity settings, just as it was when I WAS successful attaching using Odin before. However, not having a device to test the connection, I don't know yet if I have corrected the issue. I used the same cable as before, so I still don't know why it wouldn't work this last time around. I had hoped flashing the stock recovery or the original stock firmware would correct the changes I had made to the USB config, but could not connect to flash either one.

Three cautions to the general population:

1) READ all directions thoroughly and follow them to the letter.

2) Don't screw with things you don't FULLY understand.

3) Be prudent. Don't rush. Avoid rash choices. Avoid fatigue. Don't drink & Flash. If you don't know, don't go. Ask lots of questions.

David