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 .
Well, this is my story. I tried to revive my old Verizon SIII because I really like that model. The problem is I never noticed the 4.4 bootloader lock. I rooted my device after a factory reset, I tried to install the cyanogenmod but at the start the custon recovery wont trigger despite installing the adequate app, first I believed KNOX was the issue so I proceeded to unistall it with TitanimBackup, that made the "custom" Samsung boot screen appear but then a "Unauthorized sofware blah blah blah" message from Verizon appeared so I used download mode to reboot sucessfully, then I remembered that the bootloader wasnt unlocked so I proceeded to unlocked with EZunlocker and the unlock was successful, when the TWRP manager app asked me to reboot to install the custom recovery it never did, just bricked. My questions are, my phone was already running a form of custom rom for region-free SIM card operation, as far I know the device was NOT on 4.4 since it wasn't even on the US anymore and Verizon update services don't operate here, as I remember my sytem version was 4.0.4 why did it bricked? if I buy another device what I must check to avoid another bricking? Is there any way to recover my device? it is a hard brick, noob here.
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.
i have been searching for hours and trying different methods and none seem to be working..
i am trying to root a samsung s6 g920i. it is updated to android 7.0
i have dev options enabled, debugging. the one thing i do not see on the device is OEM unlocking option.
so far ive tried odin3, i selected the cfar_samsung_sm-g920i_zerofltedv_nrd90m.g920idvs4frc9_t0 file, and it shows me successful messages in the odin3 results. but on the device it restarts real quick. once it restarts, its like nothing happened. the device is still rooted and there is no super user app.
ive followed numerous videos and threads all over and cant seem to get this device rooted.
is the oem unlocking option not showing up my issue? also, i noticed when the odin was doing its thing and the phone was restarting, there was a msg showing on the top left that stated "recovery is not seandroid enforcing" then the phone would restart.
any help here would be appreciated. it also looks like all of my samsung devices do not have the oem unlocking option under developer area (3 devices) so i am not sure what happened or what am i suppose to do.
Long Shot, but .....
Similar issues with a G9200 (Hong Kong version, dual SIM). You COULD try downloading Samsung's CROM.APK from the Play Store and see if you can unlock the bootloader that way. Are you by chance running recent Nougat on the device? My suspicion is that the Nougat kernel has been tweaked to disable the known rooting / custom recovery approaches. Areal pain in the butt. My next step with the 9200 is to see if erasing the NAND via Odin will allow me to flash an older MM build (I don't care about the data) root it, TWRP it, and put a decent ROM in place of stock.
Greetings My Brothers. I have a huge Problem. Sometimes ago I got a Samsung Galaxy S7 Verizon Model, thought it will be cool to have such a model, just come to think of it; Snapdragon 820 what else did I wanted again. And the phone started running Berserk. apps downloaded and installed from PlayStore don't work at all even WhatsApp does work properly. The phones freezes all the Time, it overheats all the time. So I made a decision. root, install custom recovery and install Custom Rom like lineage OS. I'm accustom to those stuffs like Odin, download mode, etc. I don't have any problem with a phone stock on boot loop, it's something I have been fixing, so I'm Used to It. My SM-G930V security level is High with its latest android version Oreo, the bootloader is locked. tried to unlock it with ADB and Command Prompt. It was a failure. tried to get some help On YouTube. Failed, all the videos I watched was about SM-G930F none of them talked about SM-G930V, I came across SM-G930V bootloader Unlocking, rooting and custom Rom but, it wasn't compatible with my SM-G930V. So let Me ask You Guys this question. Can I really unlock the bootloader, root the phone and Install a custom recovery, and A custom Rom??? If there is a slight chance or possibility of doing so, please Brothers help me out, because I am unable to use the phone to its full potential. Thanks. Michael.