Database Info

Galaxy S6 5.1.1 root

Hi,my galaxy s6 is on version 5.1.1 with the G920FXXU2BOGG firmware and I want to root it but don't know the right method.I know that there is already a method on how to root galaxy s6 on 5.1.1 but does it support my firmware?because it is made to root the first 5.1.1 firmware or it supports all galaxy s6 5.1.1 firmwares?

hlm19 said:
Hi,my galaxy s6 is on version 5.1.1 with the G920FXXU2BOGG firmware and I want to root it but don't know the right method.I know that there is already a method on how to root galaxy s6 on 5.1.1 but does it support my firmware?because it is made to root the first 5.1.1 firmware or it supports all galaxy s6 5.1.1 firmwares?
Click to expand...
Click to collapse
Only way to get root on 5.1.1 thus far is by flashing TWRP recovery.
If you are an amateur to this sort of thing I would highly suggest not to do that.
It will void your warranty permanently by tripping KNOX which can't be "un-tripped"
May I ask why you think you need/want root?

I want to root my galaxy s6 as I see some good custom roms and want to try them.I've had some android phones before like the galaxy note 4,galaxy note 3,htc one m8 and galaxy nexus and rooted them.Just curious on how to root my gs6 with the XXU2BOGG firmware.Does the 5.1.1 root method supports my firmware?

hlm19 said:
I wan't to root my galaxy s6 as I see some good custom roms and want to try them.I've had some android phones before like the galaxy note 4,galaxy note 3,htc one m8 and galaxy nexus and rooted them.Just curious on how to root my gs6 with the XXU2BOGG firmware.Does the 5.1.1 root method supports my firmware?
Click to expand...
Click to collapse
Okay then, as long as you aware of the risks..
Rooting isn't device dependent, it's just software. It's supported on any firmware as long as you have TWRP installed. It just installs SuperSU for you into the system files.
http://forum.xda-developers.com/galaxy-s6/orig-development/twrp-t3080940
Pretty sure TWRP is supported on all models of S6/Edge, they all share the same hardware as each other.
Just flash it with Odin version 3.10.6.
Grab it here ZeroFLTE represents all S6 models except Sprint model which require their own special one (no idea why)
You then follow the Odin install method, making sure you're using 3.10.6. Otherwise more than likely will not work.
After installation of TWRP and then booting into TWRP you will be faced with the "SuperSU is not installed, would you like to install it?"
.. And done.
Er, actually I think that appears when when you go to restart via TWRP menu
But yeah.. best of luck, don't blame me if your phone explodes into a fire ball that goes nuclear and destroys the world.. Or simply bricks it
Edit: Wait are you talking about the Chainfire root method? If you are you may as well not even consider that if you're planning on custom firmware installs.. TWRP is your best bet because it isn't device/firmware specific like CF. And you need TWRP for firmware installs anyway..

Stevles said:
Okay then, as long as you aware of the risks..
Rooting isn't device dependent, it's just software. It's supported on any firmware as long as you have TWRP installed. It just installs SuperSU for you into the system files.
http://forum.xda-developers.com/galaxy-s6/orig-development/twrp-t3080940
Pretty sure TWRP is supported on all models of S6/Edge, they all share the same hardware as each other.
Just flash it with Odin version 3.10.6.
Grab it here ZeroFLTE represents all S6 models except Sprint model which require their own special one (no idea why)
You then follow the Odin install method, making sure you're using 3.10.6. Otherwise more than likely will not work.
After installation of TWRP and then booting into TWRP you will be faced with the "SuperSU is not installed, would you like to install it?"
.. And done.
Er, actually I think that appears when when you go to restart via TWRP menu
But yeah.. best of luck, don't blame me if your phone explodes into a fire ball that goes nuclear and destroys the world.. Or simply bricks it
Edit: Wait are you talking about the Chainfire root method? If you are you may as well not even consider that if you're planning on custom firmware installs.. TWRP is your best bet because it isn't device/firmware specific like CF. And you need TWRP for firmware installs anyway..
Click to expand...
Click to collapse
Thanks mate!So twrp now supports 5.1.1?

Welcome! TWRP has supported 5.1.1 since the latest version: 2.8.7.1. Change log is in the second post here. Take care and have fun

Stevles said:
Welcome! TWRP has supported 5.1.1 since the latest version: 2.8.7.1. Change log is in the second post here. Take care and have fun
Click to expand...
Click to collapse
Thanks again!But I thought the only way to root the gs6 with 5.1.1 is by using the unikernel something?as 5.1.1 is different than 5.0.2.

hlm19 said:
Thanks again!But I thought the only way to root the gs6 with 5.1.1 is by using the unikernel something?as 5.1.1 is different than 5.0.2.
Click to expand...
Click to collapse
Not sure about that.. Perhaps install unikernal first just to be sure
Okay so go to the last page or two of the TWRP thread and start reading

Stevles said:
Not sure about that.. Perhaps install unikernal first just to be sure
Click to expand...
Click to collapse
Yeah,just checked and have to flash unikernel first and then the twrp via odin.If I root using this twrp method,it supports my 5.1.1 firmware right?Sorry for lots of asking.

hlm19 said:
Yeah,just checked and have to flash unikernel first and then the twrp via odin.If I root using this twrp method,it supports my 5.1.1 firmware right?Sorry for lots of asking.
Click to expand...
Click to collapse
Assuming it doesn't boot loop with unikernel (all reports say it's fine) then yeah you won't have any dramas with root via TWRP.. Like I said it's just software, the boot loop comes from Samsung being slippery Gypsies and modifying their kernels to basically stop people from modifying system partitions. Hence the need for a custom kernel to bypass that crap. You'll be fine

Stevles said:
Assuming it doesn't boot loop with unikernel (all reports say it's fine) then yeah you won't have any dramas with root via TWRP.. Like I said it's just software, the boot loop comes from Samsung being slippery Gypsies and modifying their kernels to basically stop people from modifying system partitions. Hence the need for a custom kernel to bypass that crap. You'll be fine
Click to expand...
Click to collapse
Yeah,and if I need to unroot it,I do just flash the official firmware via odin?

hlm19 said:
Yeah,and if I need to unroot it,I do just flash the official firmware via odin?
Click to expand...
Click to collapse
Sorry for delayed response.. Yes flashing a firmware tar. md5 will reset the system partition back to full stock and replace the recovery, kernel, modem etc.
Just download one corresponding to your device ie.. SM-G92XX where the first X is either a 5 or 0 and the second is the country or region the phone was intended for. I keep the latest firmware for my device and country (not carrier because it has too much bloatware) around at all times to undo any screw ups and start again

Stevles said:
Sorry for delayed response.. Yes flashing a firmware tar. md5 will reset the system partition back to full stock and replace the recovery, kernel, modem etc.
Just download one corresponding to your device ie.. SM-G92XX where the first X is either a 5 or 0 and the second is the country or region the phone was intended for. I keep the latest firmware for my device and country (not carrier because it has too much bloatware) around at all times to undo any screw ups and start again
Click to expand...
Click to collapse
Thanks for the help!Will try it

Try this:
http://forum.xda-developers.com/galaxy-s6/samsung-galaxy-s-6--s-6-edge-unified-development/kernel-stockmod-kernel-t3100395

roydok said:
Try this:
http://forum.xda-developers.com/galaxy-s6/samsung-galaxy-s-6--s-6-edge-unified-development/kernel-stockmod-kernel-t3100395
Click to expand...
Click to collapse
I think he may have already actually, thanks for your input. It was certainly mentioned earlier but now there's a link which is always nice

What does tripping KNOX do? I like and would like to continue using the Tap & Pay feature from my bank. Is KNOX separate from the secure element the bank uses?
Other than providing a separate environment for work, what else does KNOX provide?

To Root or Not to Root

Hello Community!!
I have owned many androids over the years, and have recently got an S6, hoping to dive back into the game of rooting, modding and messing around until my phones works the way i want it to. There are MANY things that really Piss me off about my T-MObile variant of the S6, including the horrible battery life, bloatware, and lack of personality. I Really would love to root my device, but KNOX. OMG what is this?! If i Root, no Samsung pay? What other downsides are there to rooting? But recently, my phone installed "ANdroid Pay" SO I am thinking, I should just root, forget Samsung pay and just use Google pay or whatever they call it.
As you guys can tell from my sig, I have been very inactive on these forums. I am hoping someone can give me some advice here---
Thanks So much
EMilio

beforedenied said:
Hello Community!!
I have owned many androids over the years, and have recently got an S6, hoping to dive back into the game of rooting, modding and messing around until my phones works the way i want it to. There are MANY things that really Piss me off about my T-MObile variant of the S6, including the horrible battery life, bloatware, and lack of personality. I Really would love to root my device, but KNOX. OMG what is this?! If i Root, no Samsung pay? What other downsides are there to rooting? But recently, my phone installed "ANdroid Pay" SO I am thinking, I should just root, forget Samsung pay and just use Google pay or whatever they call it.
As you guys can tell from my sig, I have been very inactive on these forums. I am hoping someone can give me some advice here---
Thanks So much
EMilio
Click to expand...
Click to collapse
There are pros and cons to root.
The first pro is limitless customizations and personalizations.
The first con is OTA updates get disabled.
Another pro is you are able to dramatically improve battery and overall performance using various apps.
Another con is your warranty will be void, assuming you tripped KNOX.
If you trip KNOX, Samsung Pay no longer works; if you have root (even without touching KNOX) Android Pay does not work.
I obtained root just to prove to myself it could be done.
Since then there have been dramatic improvements with speed and battery life.

Package Disabler Pro can freeze a lot of the bloatware without root: https://play.google.com/store/apps/details?id=com.ospolice.packagedisablerpro&hl=en

Hi,
It's a highly personal decision. I myself for the first time am holding on rooting - I was the one who made the most famous Xoom rooting tool and also S4 Linux Root Script, so that tells a lot. The thing is, meanwhile my device is satisfying my needs, and I'm really curious about Samsung Pay, as it has a way wider support than Android Pay and other systems.
The best thing about rooting in my opinion was the endless system customization - specially after Xposed was released. The way better data management I had, better system control and some exclusive apps that require root or works better with root. If you are really pissed about Samsung TouchWiz apps and system "features", rooting would be a nice idea. Just keep in mind that after rooting Knox will be tripped and there's no turning back with Knox. Depending on your country, Knox trip also means warranty void, because once rooted you can unroot and make it looks like nothing happened.
Just adding what was already said, but Android Pay doesn't work with root.
All the best,
~Lord
Sent from my SM-G920I using Tapatalk

XxLordxX said:
Hi,
It's a highly personal decision. I myself for the first time am holding on rooting - I was the one who made the most famous Xoom rooting tool and also S4 Linux Root Script, so that tells a lot. The thing is, meanwhile my device is satisfying my needs, and I'm really curious about Samsung Pay, as it has a way wider support than Android Pay and other systems.
The best thing about rooting in my opinion was the endless system customization - specially after Xposed was released. The way better data management I had, better system control and some exclusive apps that require root or works better with root. If you are really pissed about Samsung TouchWiz apps and system "features", rooting would be a nice idea. Just keep in mind that after rooting Knox will be tripped and there's no turning back with Knox. Depending on your country, Knox trip also means warranty void, because once rooted you can unroot and make it looks like nothing happened.
Just adding what was already said, but Android Pay doesn't work with root.
All the best,
~Lord
Sent from my SM-G920I using Tapatalk
Click to expand...
Click to collapse
Rooting doesn't allways mean tripped knox. I have my G920F rooted and knox intact. This can be done even after updrade to 5.1.1 stok firmware.

An android phone for me is worthless without root permissions. I need it for:
adaway adds
iptables (firewall)
better battery life (debloat)
titanium backup

JuanRamiro said:
Rooting doesn't allways mean tripped knox. I have my G920F rooted and knox intact. This can be done even after updrade to 5.1.1 stok firmware.
Click to expand...
Click to collapse
I was only aware of root that can be applied before upgrade to 5.1.1.
Can you advise how you applied root after 5.1.1? Thanks.

Iceman_jkh said:
I was only aware of root that can be applied before upgrade to 5.1.1.
Can you advise how you applied root after 5.1.1? Thanks.
Click to expand...
Click to collapse
Just install de 5.0.2 engineering bootloader via ODIN. Then instal TRWP via ODIN.
After this two steps you can flash whatever you want via TRWP.
Edit: with the 5.0.2 bootloader you will loose fingerprint scanner, the rest works great, at least with the custom rom I am using.

JuanRamiro said:
Just install de 5.0.2 engineering bootloader via ODIN. Then instal TRWP via ODIN.
After this two steps you can flash whatever you want via TRWP.
Edit: with the 5.0.2 bootloader you will loose fingerprint scanner, the rest works great, at least with the custom rom I am using.
Click to expand...
Click to collapse
Keep in mind this engineering bootloader does not work with all variants. For example there is no Eng Bootloader for the Canadian phones.

Thank you both. I have the international SM-G920F (technically it's the dual Sim version, SM-G920FD, (from United Arab Emirates)).
So, to confirm, would the eng boot loader still work on my device variant, and allow root without tripping KNOX?
Sent from my SM-G920F using Tapatalk

Iceman_jkh said:
Thank you both. I have the international SM-G920F (technically it's the dual Sim version, SM-G920FD, (from United Arab Emirates)).
So, to confirm, would the eng boot loader still work on my device variant, and allow root without tripping KNOX?
Sent from my SM-G920F using Tapatalk
Click to expand...
Click to collapse
I have the single sim version of the G920F, so I don't know if it will work with the dual sim.
I don't think that it will strip you knox...
... and I think that if your phone doesn't work with this bootloader, you can just flash the correct one and make it work again.
But these are just guesses... you decide if you want to take the risk.
Good luck.

JuanRamiro said:
I have the single sim version of the G920F, so I don't know if it will work with the dual sim.
I don't think that it will strip you knox...
... and I think that if your phone doesn't work with this bootloader, you can just flash the correct one and make it work again.
But these are just guesses... you decide if you want to take the risk.
Good luck.
Click to expand...
Click to collapse
Thanks. I did some additional research, thanks to your advice about eng boot loader, and seems like it will work ☺
Sent from my SM-G920F using Tapatalk

JuanRamiro said:
I have the single sim version of the G920F, so I don't know if it will work with the dual sim.
I don't think that it will strip you knox...
... and I think that if your phone doesn't work with this bootloader, you can just flash the correct one and make it work again.
But these are just guesses... you decide if you want to take the risk.
Good luck.
Click to expand...
Click to collapse
Hi,
I wouldn't risk that "you can just flash the correct one and make it work again". If you know how a bootloader work, if it gets broken there is no way to get to Download Mode and flash a new firmware/bootloader.
For information sake, a bootloader is a piece of software that is the first thing loaded when you boot your device, it comes before anything, be it kernel, be it recovery or anything else, that means, if you have a broken bootloader, the moment you try to boot your device up, it will try loading BL and it will fail, so it will shut down back again. I've had a broken BL once before on S4, the only way to recover was a direct flash of software in system chip using a tool called JTAG.
So, all I can say to users who still didn't get it: beware with this. It seems that many people are getting successful results, but it's an extremely risk procedure, make sure you read every single instruction and follow it, the possibility of a hard brick is high.
Even still, it's a great find, thanks for sharing with me, I didn't know of this until early today .
All the best,
~Lord

I wonder whether Samsung pay will work again after reflash stock rom after root? Is it like knox, once rooted you will never have it no mater what you do including going back to pure stock?

XxLordxX said:
Depending on your country, Knox trip also means warranty void, because once rooted you can unroot and make it looks like nothing happened.
Click to expand...
Click to collapse
Did you mean, once rooted we can unroot and install the stock firmware and hence tripped Knox will be restored as well?
Or the unrooting will only help to restore the stock but the knox will continue to remain tripped. I would like to know this as I am considering purchasing S6. The last samsung phone I owned was S2 and used that for 3 full years with out any problems.
Thanks.

coolmalayalee said:
Did you mean, once rooted we can unroot and install the stock firmware and hence tripped Knox will be restored as well?
Or the unrooting will only help to restore the stock but the knox will continue to remain tripped. I would like to know this as I am considering purchasing S6. The last samsung phone I owned was S2 and used that for 3 full years with out any problems.
Thanks.
Click to expand...
Click to collapse
Once Knox is tripped its tripped but, yes you can flash original firmware and as long as you factory reset it, it will be unrooted and ready for official updates.

jetbruceli said:
Once Knox is tripped its tripped but, yes you can flash original firmware and as long as you factory reset it, it will be unrooted and ready for official updates.
Click to expand...
Click to collapse
Thanks. But can you be a bit more specific of if the unrooting, flashing stock, and factory resting will finally untrip the tripped Knox as well? My question in the event I need to take this back to a service center to claim warranty for whatever reason, is there any way for them to know that I have voided warranty if I unroot, flash back the stock and factory reset?

coolmalayalee said:
Thanks. But can you be a bit more specific of if the unrooting, flashing stock, and factory resting will finally untrip the tripped Knox as well? My question in the event I need to take this back to a service center to claim warranty for whatever reason, is there any way for them to know that I have voided warranty if I unroot, flash back the stock and factory reset?
Click to expand...
Click to collapse
Once tripped there is no going back. Voided warranty depends on laws of your country and your retailers policy.

coolmalayalee said:
Thanks. But can you be a bit more specific of if the unrooting, flashing stock, and factory resting will finally untrip the tripped Knox as well? My question in the event I need to take this back to a service center to claim warranty for whatever reason, is there any way for them to know that I have voided warranty if I unroot, flash back the stock and factory reset?
Click to expand...
Click to collapse
YOU CAN NOT UNTRIP KNOX, you can reflash your firmware from Sammobile, http://www.sammobile.com/firmwares/database/SM-G920F/
use odin and then after you flash, go into recovery or use system settings and conduct a factory reset. It will say Official in the status but, since they will reflash your rom anyways, they will see the knox trip.
It depends on where you purschased your device whether or not they will warranty it with Knox tripped.
Honestly, anyone who roots should understand this information before hand. You should always know how to return to stock unroot.

Jameslwoodward said:
I wonder whether Samsung pay will work again after reflash stock rom after root? Is it like knox, once rooted you will never have it no mater what you do including going back to pure stock?
Click to expand...
Click to collapse
After rooting my 5.1.1 without tripping Knox, with the 5.0.2 engineering bootloader (as as described a few posts ago) I have flashed a stok rom with odin and then everything went back as it was before the rooting procedure.
1. I was on stok oficial rom with oficial bootloader.
2. I lost root.
3. Knox was still intact: 0.
4. Fingerprint scanner and MyKnox worked again.
So: after upgrade to 5.1.1, rooting with the 5.0.2 engineering bootloader seems to be safe and also easy to bo back to stock... at least for my model (G920F)

Dm-Vertify Bootloop

Hello today i come to you with the dm-vertify bootloop issue. I got stuck in this dilemma by attempting to SIM unlock to be able to use my Sprint Variant on T-Mobile and my stupid self was messing with settings i should have resulting in this. After research i have found that i need to flash with Odin using the stock Firmware firmware but i cant seem to find the exact firmware i need to un-brick my phone.
In the system recovery it lists "LMY47X.G925PVPU3BOL1" as the version of firmware my phone is currently running on. If anyone could help me Locate the appropriate download that would be much appreciated!

MeoWDeVoX said:
Hello today i come to you with the dm-vertify bootloop issue. I got stuck in this dilemma by attempting to SIM unlock to be able to use my Sprint Variant on T-Mobile and my stupid self was messing with settings i should have resulting in this. After research i have found that i need to flash with Odin using the stock Firmware firmware but i cant seem to find the exact firmware i need to un-brick my phone.
In the system recovery it lists "LMY47X.G925PVPU3BOL1" as the version of firmware my phone is currently running on. If anyone could help me Locate the appropriate download that would be much appreciated!
Click to expand...
Click to collapse
You wouldn't mind sharing me your EFS, I went into deeper crap with an error saying device does not have drk please install drk first and the only way to bypass it is to root which I don't want to keep. Would really appreciate it if you could help me out :good:

TheNextGenNation said:
You wouldn't mind sharing me your EFS, I went into deeper crap with an error saying device does not have drk please install drk first and the only way to bypass it is to root which I don't want to keep. Would really appreciate it if you could help me out :good:
Click to expand...
Click to collapse
I no longer own the phone. So i couldn't tell you.

MeoWDeVoX said:
I no longer own the phone. So i couldn't tell you.
Click to expand...
Click to collapse
Ah well thanks for the reply

Hard bricking Galaxy S7

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 .

Root for Verizon Prepaid Galaxy j7?

Hi,
I was wondering if there is a root method for the Samsung Galaxy j7 Verizon's 2017 edition (SM-J727VPP). Is it even possible? I read that the bootloader for verizon phones are locked so you can't root them. Is this correct?
Thanks.

I'm on the same boat. I love the phone but not sure how to root it. Anyone know if the other root methods work for this phone?

I just bought this phone as well. Anyone dedicated into developing an unlock method for the bootloader and custom recovery would greatly be appreciated.

YanniFan said:
Hi,
I was wondering if there is a root method for the Samsung Galaxy j7 Verizon's 2017 edition (SM-J727VPP). Is it even possible? I read that the bootloader for verizon phones are locked so you can't root them. Is this correct?
Thanks.
Click to expand...
Click to collapse
I haven't tried on this one yet (scared) but with Verizon's bootloader I know that its pretty much permanently locked.
... at the very least for now,
Meaning, it MAY be possible to get root BUT that would b where the road ended... no custom roms.... etc.

Root better than nothing.
Sent from my SM-J700P using Tapatalk

Maybe you can try the app in this video for Windows looks like it has a big list of various Samsung models
I tried the link in the video but it takes you to a 4shared link that seems kind of spammy so I searched for the file on Google and found it eventually about to try it on the PC right now..
Tried it its a jtag app that need a box to flash firmware
We need to find a 7.1 n root exploits that work or find a way to dump the firmware I can't find any restore firmwares online yet

J727VPP Firmwares
artist.skywarp said:
Maybe you can try the app in this video for Windows looks like it has a big list of various Samsung models
I tried the link in the video but it takes you to a 4shared link that seems kind of spammy so I searched for the file on Google and found it eventually about to try it on the PC right now..
Tried it its a jtag app that need a box to flash firmware
We need to find a 7.1 n root exploits that work or find a way to dump the firmware I can't find any restore firmwares online yet
Click to expand...
Click to collapse
I have the stock firmware for j727VPP, the QB2 bootloader version to be exact, which is stock. It's Odin flushable , if u need it for any reason restore or w.e let me know n send me an email @ [email protected] . Also, Verizon just came out with a update for j727vpp which changed the bootloader to QF3. Do not update, otherwise going back to QB2 will be near impossible and if anyone does come out with a root then it will be for the QB2, not EF3 bootloader. But, if u already did update and need the EF3 firmware for restore purposes I have that as well, except it is in a ENC4 format, which is a RAW format for firmware. U will need to decrypt it with 7Zip to Tar or Md5 in order to be able to flash it. Like i said email me - [email protected] and I'll provide u with whatever files u need.

Oem unlock
Hello all.
Is there a way to unlock the bootloader for VZW sm-j727v yet?

Is it same for both phones?
Is the root you guys worked on and completed is it what works for this phone versions too?:
samsung
Model: sm-j727vpp
Android Version: 7.0 (nrd90m.j727vppvru1aqk4)
Please let me know. Anyone please email me at blakecollins009 at gmail dot
Thanks!

bilyjck said:
Hello all.
Is there a way to unlock the bootloader for VZW sm-j727v yet?
Click to expand...
Click to collapse
Having the same problem. Can't find anything yet. Any luck for you?

J727VPP
Sara.Gillentine said:
Having the same problem. Can't find anything yet. Any luck for you?
Click to expand...
Click to collapse
Here is a firmware link for you but the problem is it 8.1.0 for your phone !
https://www.androidfilehost.com/?fid=1322778262904007456

Any root yet?
Is there a working root method available for this phone yet? There are a few websites that claim to be able to root it, but I don't want to take a chance and brick my phone. Thanks.