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 have a Samsung Galaxy Note 3 SM-N900V from Verizon and I have been trying to change it to the DarkLord ROM that is a Modded Mix between Note 7 & Edge ROM.
I at first had problems rooting the phone with Odin (it always failed) so I search and search and found a tool called ArabicTool which took care of it and finally I rooted my phone, after that I tried adding TWRP so I could change the ROM but every time I added the recovery tool I got the message saying that the “System software not authorized by Verizon Wireless has been found on your phone” and then had to do an emergency restoration using Kies3 and the cycle began again with other methods but always the same result.
I would like to know if anyone has a way to change the ROM on a SM-N900V from Verizon, I have seem some guides that claim the process works with the SM-N900V but every time I try to do them I get the message of software not authorized when I install the recovery app TWRP and then I have to do an emergency restore in Kies3.
Please help anyone it would be really appreciated.
anrabaro said:
I have a Samsung Galaxy Note 3 SM-N900V from Verizon and I have been trying to change it to the DarkLord ROM that is a Modded Mix between Note 7 & Edge ROM.
I at first had problems rooting the phone with Odin (it always failed) so I search and search and found a tool called ArabicTool which took care of it and finally I rooted my phone, after that I tried adding TWRP so I could change the ROM but every time I added the recovery tool I got the message saying that the “System software not authorized by Verizon Wireless has been found on your phone†and then had to do an emergency restoration using Kies3 and the cycle began again with other methods but always the same result.
I would like to know if anyone has a way to change the ROM on a SM-N900V from Verizon, I have seem some guides that claim the process works with the SM-N900V but every time I try to do them I get the message of software not authorized when I install the recovery app TWRP and then I have to do an emergency restore in Kies3.
Please help anyone it would be really appreciated.
Click to expand...
Click to collapse
Greetings and welcome to xda. I am not sure the rom you mentioned is compatible with your device and I think your bootloader may also be locked. This thread here
http://forum.xda-developers.com/showthread.php?t=2517610
should help you with a custom recovery and I found this rom which is a s7 port for your device
http://forum.xda-developers.com/ver...ent/rom-aryamod-port-s7edge-portv6-5-t3506144
Good Luck
Sawdoctor
This ROm
sawdoctor said:
Greetings and welcome to xda. I am not sure the rom you mentioned is compatible with your device and I think your bootloader may also be locked. This thread here
http://forum.xda-developers.com/showthread.php?t=2517610
should help you with a custom recovery and I found this rom which is a s7 port for your device
http://forum.xda-developers.com/ver...ent/rom-aryamod-port-s7edge-portv6-5-t3506144
Good Luck
Sawdoctor
Click to expand...
Click to collapse
This is teh ROM i was trying to use but the main problem I'm having is trying to install a recovery tool everytime I do the phone gets stock on the software not authorized screen.
How do I know if teh bootloader is locked and if it is is there a way i can unblocke it?
http://forum.xda-developers.com/galaxy-note-3/development/darklord-s7-edge-port-6-0-1-mm-t3382954
anrabaro said:
This is teh ROM i was trying to use but the main problem I'm having is trying to install a recovery tool everytime I do the phone gets stock on the software not authorized screen.
How do I know if teh bootloader is locked and if it is is there a way i can unblocke it?
http://forum.xda-developers.com/galaxy-note-3/development/darklord-s7-edge-port-6-0-1-mm-t3382954
Click to expand...
Click to collapse
That rom may not be compatible with your device, the verizon variant is different to the other note 3's. I'm pretty sure the verizon note 3 is locked bootloader but if you ask your questions here
http://forum.xda-developers.com/verizon-galaxy-note-3/help
the experts there will be able to confirm this for you
Good Luck
Sawdoctor
Finally found how to install the ROM
So I finally found the solution on how to change the ROM on my SM-900V Verizon Wireless Note 3.
>>>>1) First Step How to Root the phone:
Activate USB debugging, download ArabicTool.exe.
I follow this youtube Vid to do it:
https://www.youtube.com/watch?v=GtuOPhSlymg
>>>>2) Unblock boot loader:
I follow this link:
http://forum.xda-developers.com/ver...l/official-note-3-verizon-bootloader-t3359370
>>>>3) Install TWRP (Using Flashly):
Download Flashly from the Android Play Store then download a recovery img using Flashly I picked TWRP.
>>>>4) Install the ROM:
I follow this link:
http://forum.xda-developers.com/galaxy-note-3/development/darklord-s7-edge-port-6-0-1-mm-t3382954
and
https://www.youtube.com/watch?v=-i6DsGKTsJc
So happy
ok so i bought a phone on eBay..it looked quite cheap for what it was plus it was new (£129) and when i got it it was on OS Version 5.01 and no OTA updates so i discovered the phone was rooted and tried to unroot with SuperSU but the phone restarted and stuck on boot logo ..i installed TWRP and have wiped eveything! i just need some help with trying to instal a new custom or stock ROM onto this device please? dont ask me why i done all this, i have no idea..moments of madness but my problem is i have a phone that i cant use thanks in advance, any help will be very much appreciated
Craig_CFC said:
ok so i bought a phone on eBay..it looked quite cheap for what it was plus it was new (£129) and when i got it it was on OS Version 5.01 and no OTA updates so i discovered the phone was rooted and tried to unroot with SuperSU but the phone restarted and stuck on boot logo ..i installed TWRP and have wiped eveything! i just need some help with trying to instal a new custom or stock ROM onto this device please? dont ask me why i done all this, i have no idea..moments of madness but my problem is i have a phone that i cant use thanks in advance, any help will be very much appreciated
Click to expand...
Click to collapse
I don't have this device but, the following area of the forum is specific to your device.
https://forum.xda-developers.com/galaxy-j5
With that stated...
This is not an easy question to answer because there's a handful of Custom Firmware releases that's specific to your J5 (2015) variant device.
The following is the area where you can locate many of the Custom Firmwares and don't be afraid to ask for some member guidance within the one you choose to install. Just be sure to read that threads OP (OP = Original Post, which means Post #1) first to prevent from asking a question already answered in it.
https://forum.xda-developers.com/galaxy-j5/development
There's other Custom Firmware released in other areas but, that one is, typically, where they all should be for this variant.
I wish you the best of luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
Hi All
I have an S7 Exynos with latest Magisk installed and everything has been working flawlessly till I decided this early morning, for not any particular reason(except my increasing amount of grey hair ), to lock the "developer options". I think I have done the same maybe a couple of years ago though cannot remember how I had solved it.
Obviously my phone was instantly locked.
Would someone be able to link a good working solution with being able to keep data and apps? I am a bit desperate as my work is starting again tomorrow.
Thanks a lot.
look at frp bypass
Costum binary blocked by FRP lock is a protection, whene you do a factory reset from recovery. the only way you get this message is with odin.
this one works for me on s7, s7 edge and s6 tab
Thanks @Dagobert
I will have a look at it now and see if it is not too scary. See my S7 FRP
kiwigi said:
deleted as repeated post
Click to expand...
Click to collapse
Do you have acces to the phone?
kiwigi said:
deleted as repeated post
Click to expand...
Click to collapse
If you have acces to the phone then backup your data do a factory reset. Then you can flash whatever you want. Frp lock is a google protection with a google account. Whene you do a factory reset from settings you wipe the frp.
What is Google FRP?
FAQ for Samsung Mobile Device. Find more about 'What is Google FRP?' with Samsung Support.
www.samsung.com
I have access to the phone via PC/Odin only. No booting as per image above. I wand to keep Data and Apps
I assume I have to flash stock with home csc to be able to enter the phone again? Then root again, if I so wish?
Yup. Maybee a long shot but try Flashing your former firmware with Odin, using HOME_CSC. I think thats the solution
More info on that in this topic
Help! How to flash without losing data?
Good day! My phone got stuck on breathing Samsung logo after my phone updates. Now the only option I have in mind is to restore factory data. But I have some important files in my phone that is very essential in my work. I know I have read that...
forum.xda-developers.com
hmm., done the flashing with the files plus home csc and it asks for password, which I have entered without success. I know the password and it justs does not accept it.
See the factory reset warning and the FRP lock still being on now.
I'm desperately trying to avoid wipping data and apps.
edit: unfortunately I had to format/reinstall as I could not find a workable option.
What I have:
I have a Samsung Galaxy S7 SM-G930W8 device. It has been rooted and unrooted previously, as well as flashed with official samsung stock ROM. I also have just performed a factory reset from recovery mode recently.
What I am trying to do:
I am trying to root it properly and flash LineageOS on it. I am aware as to how to do this based on the guides here, but I run into a problem early on...
Problem:
I cannot seem to enable OEM unlock. It automatically disables right after I try to enable it.
Other potential problem:
When I try reboot to bootloader via adb command ".\adb reboot bootloader", it just restarts my device normally
Question:
If I can connect my device to Odin and attempt to flash LineageOS do I risk bricking my device given it's current circumstance? Or is this all I can try now?
I'll provide any additional information/images if needed. I just feel like I am repeating the same troubleshooting over and over again without any progress.
Thanks
Just ended up doing it assuming that it was unlocked (felt quite risky wiping everything and installing old zips)... Everything seems relatively functional and rooted. I'm a little uncertain whether or not I should update magisk as I don't feel like creating a new problem on it for myself just yet.