after towel was released at&t released a update which fixed the patch that was used to root in towelroot. I have heard that there are alternative rooting methods which I have tried that involve Odin. For some reason though when I try to use Odin it always told me fail and after a certain amount of tries in bricked my phone which is now in a boot loop. can someone help get me out of that bootloop?
I also have another question. Can't you just flash a older version of android to your Galaxy s5 and then use towelroot to root it?
(I am very new to this rooting experience and I would appreciate step by step guide):laugh:
Than you
You probably had "fail" message because you hadn't disabled the option "Reactivation Lock" in Security settings before using Odin.
To fix your phone, just boot in Download Mode, then flash a working firmware for your S5. Do you how to do that ? Can help you if needed
I also have another question. Can't you just flash a older version of android to your Galaxy s5 and then use towelroot to root it?
Yes you can, but prefer using newer version for you'll have better performance and security updates.
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 .
So i think i have completely ****ed up, hopefully you guys can give me some insight
I was on the process of properly rooting a samsung s7 that i got since the root checker said that it was not properly root.
i decide to fallow this guide
https://forum.xda-developers.com/ve...ot-guide-verizon-s7-s7-edge-sm-g930v-t3411015
But i after flashing the ENG using Odin
the phone just keep restarting, over and over, it also does the samething in recovery mode.
Notes:
The phone was displaying Custom unlock login screen (Before Flash)
Also it was 6.0.1 update
and I got the the 7.0 update, to flash the ENG
If there is anything you guys can advice, ill appreciate.
If it can go in downloading mode you can flash stock firmware and try rooting again.
Hi there I've been away from rooting for a bit and i have been trying to root a broken s7 edge more recently. Its got 6.0.1 stock on it. It all works except the volume up button. I seem to be able to access the phones files and sd card in windows. I can also flash 6.0.1 it seems by forcing it into download mode. But its still stuck on FRP and i can't find any way to unlock the bootloader to install custom software. I've been trying all the tutorials i can find but none work. Is this Samsung patching these security holes and so they no longer work? The password Is unknown for the Google account and it's not blacklisted or anything like that I've not used the SIM in any tutorial though. So is this doable or is it impossible at present? It all seems a lot more secure since my last root :s Thanks
Mumraa said:
Hi there I've been away from rooting for a bit and i have been trying to root a broken s7 edge more recently. Its got 6.0.1 stock on it. It all works except the volume up button. I seem to be able to access the phones files and sd card in windows. I can also flash 6.0.1 it seems by forcing it into download mode. But its still stuck on FRP and i can't find any way to unlock the bootloader to install custom software. I've been trying all the tutorials i can find but none work. Is this Samsung patching these security holes and so they no longer work? The password Is unknown for the Google account and it's not blacklisted or anything like that I've not used the SIM in any tutorial though. So is this doable or is it impossible at present? It all seems a lot more secure since my last root :s Thanks
Click to expand...
Click to collapse
Try this for bypassing Factory Reset Protection(FRP)
https://www.progeeksblog.com/bypass-factory-reset-protection-on-samsung-devices/
Or this
https://www.xda-developers.com/rootjunky/
As for rooting the device, there aren't many methods that work on lollipop and newer firmwares other than maybe trying Kingroot and Kingoroot or flashing TWRP(not an option for you since you have a locked bootloader) for your model number then flashing Super or Magisk.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
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.