I bought a Samsung Galaxy S7 Edge from my cousin for $450. I then proceeded to root it and everything was fine for a week or so before my phone went into an infinite boot loop after an OTA update.

In the process of trying to fix it, I accidentally flashed a bootloader, unaware that Samsung has the bootloader locked. As a result, I had a completely bricked phone.

I mean legit bricked. No buttons with work and the screen remained shut and I couldn't flash anything over it again to try to repair it. I couldn't even put the phone into recovery mode. I now had the world's most expensive paperweight.

However, I managed to convince Samsung to repair it for me for free! I told them that the phone just stopped responding after an OTA update from them, which isn't so far from the truth.

I only ever had to flash things on the phone to begin with because of their update. Honestly, I wouldn't has had to deal with this problem, and neither would Samsung, if they just didn't lock the damn bootloader! Why are these companies taking away are independent control of our own devices?

Moral of the story: DON'T flash over a locked bootloader EVER or you will end up with a completely brick device, with no solution other than to open it up and replace the motherboard entirely.

  • 1
    If you could get into fastboot, usually there's a way to fix. On my phone I accidentally wiped the OS and the boot image... All while the bootloader was locked so I had no recovery.

    I learned very quickly to make sure I don't mess parameters up in flash statements ever again... Luckily someone was dumb enough to publicly share a ROM dump that contained a stock boot image (don't ever share a ROM dump, some devices contain unique radio information and you can lock your device out of a network that way).
  • 1
    Which is why I'm considering selling my s7 and getting something that isn't like this.
    Or that at least doesn't come with a shitton of bloatware.
  • 1
    Additionally, there is an OEM unlock option in developer settings in newer Android phones. Never used a Samsung phone, but I have seen it in devices running Lollipop and up. I think enabling that will also unlock the bootloader.
  • 1
    Most locked bootloaders prevent you from flashing full stop. You shouldn't have been able to do this. Shows how messed up Samsung are
  • 3
    @grublle Same here. I'm trying to sell it so that I can get a more techie/dev/hacker friendly phone. Planning on getting the One Plus 3T.
  • 1
    @Neotelos I couldn't get into fast boot. No recovery options available. I messed up the component that interfaces between the hardware and software, so no buttons on the device or screen would do anything because they are now disconnected from the software.
  • 0
    @Koolstr software can't change the predefined hardware actions of buttons. Holding power for 10s will always shut the device off and a combination of buttons will control how the device boots even though the screen will remain blank.

    You can be in fastboot with nothing on the screen and the device seemingly powered off.

    You also need fastboot drivers, adb drivers don't work with fastboot.
  • 0
    @Neotelos this is firmware and hardware level, not software.
  • 1
    OP3t is really a great phone! Coming from nexus 5 then Moto x 2014 pure i really like it
  • 1
    @kamnikaz thanks for the feedback
  • 1
    @Neotelos you're right, it's a firmware issue, not a software issue. My bad. Either way, fastboot wasn't working for me. I hard bricked my device, and it is common knowledge that there is no recovery from a hard bricked device.
  • 0
    Many people use the Samsung S7 edge mobile because it is very beautiful mobile and many people like to use this https://researchpapers.io/we-can-ea... to manage their work. These people must follow the author's post as it may provide them with information.
Add Comment