I wrote in separate thread 10 days ago.
I got the rooted Galaxy S7 (SM-G930F) which if I try to boot to recovery gives an error: dm-verity verification need to check drk first.
Then following step by step instructions I installed TWRP.
And flashed custom rom SuperMan-Rom V1.6.5
Rom worked fine until I rebooted the device for the first time. Then I got message:
Code:
Custom Binary Blocked By FRP
Maybe I accidentally turned off OEM unlock in Developer settings, but I honestly don't remember I did that.
And after that I got the hard brick. This is confirmed by @CuBz90 in this thread
So my question is:
1. After the Galaxy S7 is rooted/custom recovery is installed, the DRK is damaged and dm-verity verification will fail if stock rom is installed, right?
2. If user accidentally turn off OEM Unlock the device will be hard bricked, right?
Is that two steps one way ultimate bricking?
I'm asking that because I'm thinking of buying new Galaxy S7 to replace the bricked one, but if hard bricking is that easy, than I'm not really sure I will buy it again.
Dude, try to kill him completly ( nothing on screen ) then send him to warranty, you got nothing to lose.
NeoDJW said:
Dude, try to kill him completly ( nothing on screen ) then send him to warranty, you got nothing to lose.
Click to expand...
Click to collapse
It's not possible since I bought it second hand.
Even if I had a warranty, in my country (Serbia) warranty for smartphones doesn't mean much, I think I could write PhD thesis easier than to make seller replace/fix smartphone with warranty
mss1988 said:
I wrote in separate thread 10 days ago.
I got the rooted Galaxy S7 (SM-G930F) which if I try to boot to recovery gives an error: dm-verity verification need to check drk first.
Then following step by step instructions I installed TWRP.
And flashed custom rom SuperMan-Rom V1.6.5
Rom worked fine until I rebooted the device for the first time. Then I got message:
Code:
Custom Binary Blocked By FRP
Maybe I accidentally turned off OEM unlock in Developer settings, but I honestly don't remember I did that.
And after that I got the hard brick. This is confirmed by @CuBz90 in this thread
So my question is:
1. After the Galaxy S7 is rooted/custom recovery is installed, the DRK is damaged and dm-verity verification will fail if stock rom is installed, right?
2. If user accidentally turn off OEM Unlock the device will be hard bricked, right?
Is that two steps one way ultimate bricking?
I'm asking that because I'm thinking of buying new Galaxy S7 to replace the bricked one, but if hard bricking is that easy, than I'm not really sure I will buy it again.
Click to expand...
Click to collapse
Maybe you can find the solution here:
http://androidforums.com/threads/custom-binary-block-by-frp-lock.977734/
Erik1805 said:
Maybe you can find the solution here:
http://androidforums.com/threads/custom-binary-block-by-frp-lock.977734/
Click to expand...
Click to collapse
Thanks but this will not fix my problem.
Have you tried this: http://pangu.in/frp.error.html
Bright.Light said:
Have you tried this: http://pangu.in/frp.error.html
Click to expand...
Click to collapse
No I didn't but the fact is it will not work.
There is currently no way to fix that. The only way would be to unlock FRP by some box, but it isn't released yet.
What I am asking here is true that Galaxy S7 could be hard bricked that easy? By steps I wrote in my first post.
My questions are partially answered in this article
But I still don't understand what's the problem with dm-variety if I flashed stock rom?
Is there are any other parts of the NAND that are not original/signed and that's why dm-verity fails?
If that's the case can they be backed up then reflashed with the Odin if I get into same problem with new phone?
Thanks
@mss1988 Even if you get message as locked because of FRP, just use Smart switch with Emergency recovery mode and you will get the device back to its original state. This works even if the device is rooted or Twrp'd
harshang2007 said:
@mss1988 Even if you get message as locked because of FRP, just use Smart switch with Emergency recovery mode and you will get the device back to its original state. This works even if the device is rooted or Twrp'd
Click to expand...
Click to collapse
Thanks, but Smart Switch Emergency Recovery is basically the same thing as Kies Firmware update. Which I already tried and that didn't fixed my problem.
mss1988 said:
Thanks, but Smart Switch Emergency Recovery is basically the same thing as Kies Firmware update. Which I already tried and that didn't fixed my problem.
Click to expand...
Click to collapse
@mss1988 I have personally faced this issue on Samsung J7 and J5 and later I had to use Smart Switch's Emergency recovery functionality by enter my Serial number and Device Model Number and Successfully finished flashing the stock ROM. Yes, This works.
harshang2007 said:
@mss1988 I have personally faced this issue on Samsung J7 and J5 and later I had to use Smart Switch's Emergency recovery functionality by enter my Serial number and Device Model Number and Successfully finished flashing the stock ROM. Yes, This works.
Click to expand...
Click to collapse
I don't have the phone anymore to confirm or to deny this. But the whole procedure in Kies and Smart Switch is the same. There are other people with the same problem too in this thread too, and they still didn't found the way to unbrick their devices.
mss1988 said:
I wrote in separate thread 10 days ago.
I got the rooted Galaxy S7 (SM-G930F) which if I try to boot to recovery gives an error: dm-verity verification need to check drk first.
Then following step by step instructions I installed TWRP.
And flashed custom rom SuperMan-Rom V1.6.5
Rom worked fine until I rebooted the device for the first time. Then I got message:
Code:
Custom Binary Blocked By FRP
Maybe I accidentally turned off OEM unlock in Developer settings, but I honestly don't remember I did that.
And after that I got the hard brick. This is confirmed by @CuBz90 in this thread
So my question is:
1. After the Galaxy S7 is rooted/custom recovery is installed, the DRK is damaged and dm-verity verification will fail if stock rom is installed, right?
2. If user accidentally turn off OEM Unlock the device will be hard bricked, right?
Is that two steps one way ultimate bricking?
I'm asking that because I'm thinking of buying new Galaxy S7 to replace the bricked one, but if hard bricking is that easy, than I'm not really sure I will buy it again.
Click to expand...
Click to collapse
I went through this procedure: http://forum.xda-developers.com/s7-edge/how-to/guide-how-to-fix-check-drk-imei-issues-t3379516 which gives a link to downloading the factory binary (of either version). It reinstated my IMEI which had been turned to a string of zeroes. I will say that when you reboot after flashing the factory binary it's pretty different looking so be prepared for that. I then went to Sammobile and downloaded the appropriate stock ROM for my s7 and flashed that with Odin. I flashed TWRP, formatted internal data when given the opportunity, flashed the no-verity-opt-encrypt.zip, and I was able to use my s7 again. At any rate, you might follow the guide at the link I gave you and see if it helps. As always, no guarantee is given or implied. It's just what I did.
Thanks man, but I can't flash the Factory binary, my FRP is unfortunately ON.
E pa brate nemoj se više onda igrati sa telefonom, nije to za svakoga,...
Mod Edit: Please post in English only:
Well, the brothers do not come then play with the phone, it's not for everyone
now phone detect usb ? i mean adb devices
mss1988 said:
I wrote in separate thread 10 days ago.
I got the rooted Galaxy S7 (SM-G930F) which if I try to boot to recovery gives an error: dm-verity verification need to check drk first.
Then following step by step instructions I installed TWRP.
And flashed custom rom SuperMan-Rom V1.6.5
Rom worked fine until I rebooted the device for the first time. Then I got message:
Code:
Custom Binary Blocked By FRP
Maybe I accidentally turned off OEM unlock in Developer settings, but I honestly don't remember I did that.
And after that I got the hard brick. This is confirmed by @CuBz90 in this thread
So my question is:
1. After the Galaxy S7 is rooted/custom recovery is installed, the DRK is damaged and dm-verity verification will fail if stock rom is installed, right?
2. If user accidentally turn off OEM Unlock the device will be hard bricked, right?
Is that two steps one way ultimate bricking?
I'm asking that because I'm thinking of buying new Galaxy S7 to replace the bricked one, but if hard bricking is that easy, than I'm not really sure I will buy it again.
Click to expand...
Click to collapse
wild guess....
Install dm-verity and force encryption disabler
Wipe Cache
install custom kernel
chandarakk said:
now phone detect usb ? i mean adb devices
Click to expand...
Click to collapse
There's no adb/fastboot access from Samsung recovery or Samsung download mode, as far as I know.
Just get your phone into downloadmode and then flash the stock firmware witch you can find on sammobile. I got also this problem, and then everything will be fine ?
did you try use Kies or Smart swticher to factory restore the phone ?
because as far as i know , even FRP is on , you can still flash stock firmware.
and , try local shop to find any place have z3x box or Octopus box .
I recently buy Samsung Galaxy J7 (2015) from a untrusted source, and when i wipe data, it need to enter the google account, i don't have the account, i've try all solutions on the internet but it don't help me, because OTG cable and SideSync solution are blocked on the new 5.1+ firmware, and i have to install the old 5.1 firmware but my phone is on 6.0, when install the old 5.1 firmware using odin and it said failed and stopped at cm.bin, i read on some forum, blog that because of the update has block downgrade, please help!
flash Custom recovery and stock flasheable man
so fine
seven4grindBR said:
so fine
Click to expand...
Click to collapse
Use Odin ?
Im new to android
p/s: Samsung don't have .zip stock rom, or if it have, please give me the link
~not really good at English
dangquoctrung123 said:
I recently buy Samsung Galaxy J7 (2015) from a untrusted source, and when i wipe data, it need to enter the google account, i don't have the account, i've try all solutions on the internet but it don't me, because OTG cable and SideSync solution are blocked on the new 5.1+ firmware, and i have to install the old 5.1 firmware but my phone is on 6.0, when install the old 5.1 firmware using odin and it said failed and stopped at cm.bin, i read on some , blog that because of the update has block downgrade, please !
Click to expand...
Click to collapse
Brother I have same problem, when I try to install Twrp by Odin it says FRP lock, but I fix this by simply formate mobile without setup google account then I am able to Install TWRP on it.
After that I flash 5.1(Lollipop) by TWRP.
It install successfully but when I sign in again in my google account from my device it gonna turned off.
And when I tried to turn on only model no is display (Not samsung logo) and at the top of the screen there is something like- "custom frp lock" display.
TWRP also not open, I already try some methods but Not working.
Please help me how to fix it?
I'm using J700F/DD I'm not able to bypass FRP lock. Using 6.0.1/MMB29K/J700FXXU2BPH4
I'm using J700F/DD I'm not able to bypass FRP lock. Using 6.0.1/MMB29K/J700FXXU2BPH4
Hey i have a Canadian Samsung Galaxy S7 SM-G930W8 model and when i bought it second hand buddy did not remove his google& Samsung account which is preventing me from having my OWN phone and i want to factory reset it and cannot do it through the setting (powered on) and in recovery it says that it will require the Google account that is currently on the phone be signed into once the reset is complete stupid FRP protection. I found the Samsung master reset code online and im hoping that will work but wanted to ask the community before i tried just to be safe. Please any helped is greatly appreciated thanks.
ALSO its running the july 1 2018 security patch and android 8.0 ored
The only way to get past FRP is the google account or an FRP bypass exploit which are all patched in Oreo.
Take it back to the seller and get them to unlock it for you.
Its not lock i have full access i am trying to get rid of his Samsung & google account if i could root it i could get it but cant seem to find a rooting method for this phone ..... Im not locked out of it i have 100% access just need his account removed
G930W8 is Exynos, so you should just be able to flash TWRP and then flash a root zip. But if you factory reset its going to lock down. https://forum.xda-developers.com/galaxy-s7/development/recovery-official-twrp-herolte-t3333770
Downgrading to marshmallow and using a bypass method (even though it's not locked, bypass lets you change the google account) may be your best bet.
Ok so downgrade to 6.0? And then find a frp unlock for marshmallow and then i dont kno how to run the bypass never had a phone with this nonsense ..... As for the root method which root file would i have to get i could then have my brother write a snippet like the old "remove gapps\knox\samsung apps" i doubt the old one i have would even work lol
Lookup FRP bypasses on youtube, there's many methods and at least once will work - it's not a simple process however.
In that TWRP thread I linked is the Super SU flashable zip, or Magisk would be the best root methods.
I have been trying for about a month to root and atleast boot this SM-G920V to a rom I dont even care if it's rooted but anytime i try to follow a youtube video exactly it still ends up failing i have used adb to boot to bootloader then turned off phone booted into download mode to bypass the secure download but it still says SECURE CHECK FAIL : (RECOVERY) I don't quite understand why Verizon just has to be so difficult but this may be a dumb question is there anyway to actually switch the model of this phone without just changing that file that displays it to thus switch it to a root compatible version or will changing that actually make the phone compatible I don't know if anyone has any tips as to booting this verizon galaxy s6 nougat 7 to a custom rom or even rooting though I was told that the verizon models are incompatible for unlocking bootloader but I know theres ways of booting to roms without unlocking bootloader though you need root is there anyone that doesnt need root or unlocking bootloader I have also tryed the old ping pong method and that still failed. please let me know if you have any knowledge of any of this thank you in advance
No way for custom rom.
Flash the latest official, install Package Disabler app and get rid of the bloatware.
Then enjoy the phone.
Hi. I accidently updated my J3 to android 9 and since then, the phone works like my old Samsung S4 mini. Everything is lagging, in short phone is just unusable. I know that trying to downgrade via odin you get anti rollback protection because of the bootloader so is there any other way how to downgrade it to older version? I don't care if it's easy or hard way, i just want to make this phone usable. Maybe flashing older rom with keeping new bootloader? I heard someone did that once to A7 2018 but never published this rom.
I downgraded my SM-J330F (with unlocked bootloader) from Pie (9) to Nougat (7) using Odin.
To unlock the bootloader on a J3 is very easy. Go to Developer Options and activate OEM unlocking. That's it.
If it's somehow missing, use this:
[OFFICIAL][TOOL][WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.4.3
15 seconds ADB Installer v1.4.3 ADB, Fastboot and Drivers What is this? This is All-in-One installer for 3 most needed PC tools for Android. No need to download big SDK for 3 small things. I originaly made it for my Kurdish friend AnGrY DuDe in...
forum.xda-developers.com
You can find a how-to here:
Unlock Bootloader on Samsung Galaxy J3 2018? OEM Unlock!
Hey, there in this guide, I will show you the easiest method to Unlock Bootloader on Samsung Galaxy J3 2018. This smartphone was recently launched, and in
www.rootingsteps.com
my thread may help you
[A320FL] Downgrade Android 8 to 6.0.1
So i just succeded in downgrading my A3 by flashing boot.img and system.img through OrangeFox recovery, theres not much more to it(and magic probably). The phone initially didn't boot and just bootlooped not even showing the boot animation only...
forum.xda-developers.com