Database Info

Is there a fix for this error yet?

S8 plus stuck in recovery with following message:
"Support SINGLE-SKU
Supported API: 3
dm-verity error
failed code : 0x02"
Is there a fix for this yet?
cheers
Matt

...? Elaborate?
What did you flash that lead to this?
dm-verity is what you usually get when you flash something incompatible, or when some insecure fw image is rejected.
Reflash the firmware using ODIN, and the latest FW package for your model / region. (in the AP box)
If you end up with DRK error afterwards, then you're boned. You need Samsung to help you out.
TL;DR: Careful when flashing stuff next time, always verify what you're flashing is for your device's model.

OP, did you found a solution to your problem? i'm asking because now i have the exact same problem as you do so i would really appreciate if you could tell me what you've done.

Comarrid92 said:
OP, did you found a solution to your problem? i'm asking because now i have the exact same problem as you do so i would really appreciate if you could tell me what you've done.
Click to expand...
Click to collapse
Took it back to Samsung and had to pay them £290 to fit a brand new board.
Out of warranty coz i rooted it.
only way out.
Gutted.
Matt

Guess the problem was that you didn't flash dm-verity bypass when u tried to root.

CoreyHUN said:
Guess the problem was that you didn't flash dm-verity bypass when u tried to root.
Click to expand...
Click to collapse
Wrong.
I did flash it, and it was rooted for about a week, but for some reason, i was bored, just potching around with my phone and decided to uncheck 'allow OEM' unlock, but forgot to re-check it before i restarted the phone...too late though...as Samsungs awesome security basically said...NO WAY...he's tinkering about with root triggered the efuse on the board and the ONLY way to fix that was a brand new board.
I'm not a newbie (hence my 371 thanks meter) when it comes to rooting phones....i've been on here since 2011 and rooted stacks of phones....HTC HD2, HTC Sensation, Desire HD, LG G2, LG G3, LG G4, HTC One-X, HTC One-x Plus, HTC Desire eye and a LOT more...Just made a silly mistake a week AFTER I rooted the phone.
I gotta be hnonest, I thought i'd miss root, but can hand on heart say....i'm not missing it one single bit.
My lovely Samsung still has 20 months warranty and i'm keeping it that way by not rooting.
LOVE my S8 Plus and to be honest, with Knox etc....I'd advise everyone not to root this EXPENSIVE beast of a phone!:good:
Matt

In some countries (like the EU ones) it is legal to modify the software on your phone, without voiding HW warranty, so if ur phone dies, and they can't prove that it is because the modification, they have to replace / repair it.

CoreyHUN said:
In some countries (like the EU ones) it is legal to modify the software on your phone, without voiding HW warranty, so if ur phone dies, and they can't prove that it is because the modification, they have to replace / repair it.
Click to expand...
Click to collapse
WRONG!
Hardware problems -> YES
Problems due to wrong use of your phone (i.e. root and phone won't do anything anymore): NO
And I do agree with Samsung: if you temper with the FW, and your phone doesn't do anything anymore -> IT'S YOUR OWN F...... FAULT ! ! !

Here's the nice big fat bill I got for repairing it.

Eeeuuurrreekkaaaaaa!
So after being presented with this error due to my own stupidity (trying to diagnose why MTP wasn't working on windows 10 and disabling Developer Options and not re-enabling OEM Unlock), I managed to get around it quite simply although at the cost of my data... BUT at least its not bricked.
The solution is simple;
1. Use SamFirm and download the latest firmware
2. Using Odin Load all the firmware options (BL, AP, CP and CSC) and in the options tab select all the checkboxes except "Flash Lock" and "T-Flash".
3. Press start and hold your breath.
Upon completion the phone may not reboot automatically so you will have to manually reboot using the Bixby, Volume Down and Power Buttons. Once rebooted you'll see it erasing the remaining userdata and finalising the re-partitioning process but a few minutes later you'll see the samsung logo and the welcome screen.
I hope this helps someone. Good Luck Peeps

I have the same problem guys but my odin isn't working the ID thing specifically the computer isn't recognising the phone.

Can't Downgrade samsung system app

the samsung device maintenance system app worked alright in the past, but I've been seeing a few people not liking the new update since it apparently targets more than what it should; I aimed to not update it at all, but while I was updating apps before I went to sleep yesterday, that app updated as well. I didn't know it did so I've been trying to downgrade it to an earlier version. I downloaded an apk file from apkmirror, made sure to uninstall the updates to it and set it to factory version, but it won't let me install, saying it conflicts with the same app already present. I then used the adb command-line tool to "uninstall" it (pm uninstall -k --user 0 com.samsung.android.lool ), hoping it would work then, but it says "nope, this app doesn't exist on this phone, plus this apk file is corrupted". I can "re-install" it by installing it from the google play store
I'm at a loss on how I can get this done without root (I don't plan on rooting my phone unless the situation is perfect for it), using the adb tool or any tool that won't kill my phone. Any help

LodeUnknown said:
the samsung device maintenance system app worked alright in the past, but I've been seeing a few people not liking the new update since it apparently targets more than what it should; I aimed to not update it at all, but while I was updating apps before I went to sleep yesterday, that app updated as well. I didn't know it did so I've been trying to downgrade it to an earlier version. I downloaded an apk file from apkmirror, made sure to uninstall the updates to it and set it to factory version, but it won't let me install, saying it conflicts with the same app already present. I then used the adb command-line tool to "uninstall" it (pm uninstall -k --user 0 com.samsung.android.lool ), hoping it would work then, but it says "nope, this app doesn't exist on this phone, plus this apk file is corrupted". I can "re-install" it by installing it from the google play store
I'm at a loss on how I can get this done without root (I don't plan on rooting my phone unless the situation is perfect for it), using the adb tool or any tool that won't kill my phone. Any help
Click to expand...
Click to collapse
Uninstalling updates and reverting it back to the factory version is downgrading it as far as it will downgrade, and if it worked before you let it update, then you are running the version (factory) that was working previously, therefore something else is wrong if it still doesn't work

*Detection* said:
Uninstalling updates and reverting it back to the factory version is downgrading it as far as it will downgrade, and if it worked before you let it update, then you are running the version (factory) that was working previously, therefore something else is wrong if it still doesn't work
Click to expand...
Click to collapse
what would I have to do to diagnose this if possible, and if it can't be, am I pretty much at a dead end?

LodeUnknown said:
what would I have to do to diagnose this if possible, and if it can't be, am I pretty much at a dead end?
Click to expand...
Click to collapse
Flash the same ROM over the top using HOME_CSC instead of CSC so not to lose data
If that fails, bite the bullet and factory reset

*Detection* said:
Flash the same ROM over the top using HOME_CSC instead of CSC so not to lose data
If that fails, bite the bullet and factory reset
Click to expand...
Click to collapse
im using the default Android OS (7.1 nougat), no custom ROMs, and this android phone was bought at an AT&T retailer; if the right chance comes, I would be willing to flash a custom rom (probably LineageOS) after I get it unlocked (doubt ill be updating to a newer phone unless there's an actual difference) and the money situation is good, but until then, sticking with what I got
I did remember about an application called odin that can (maybe?) flash stock rom of android without tripping the knox counter, that true? and if I do, will I lose all my installed stuff, apps, contact info, etc...

LodeUnknown said:
im using the default Android OS (7.1 nougat), no custom ROMs, and this android phone was bought at an AT&T retailer; if the right chance comes, I would be willing to flash a custom rom (probably LineageOS) after I get it unlocked (doubt ill be updating to a newer phone unless there's an actual difference) and the money situation is good, but until then, sticking with what I got
I did remember about an application called odin that can (maybe?) flash stock rom of android without tripping the knox counter, that true? and if I do, will I lose all my installed stuff, apps, contact info, etc...
Click to expand...
Click to collapse
If your phone is a US model S7 (snapdragon) you cannot flash custom ROMs
My instructions are for ODIN (version 3.12.7 for Nougat)

So at this point, my only option is to switch to a new phone that can be used by Odin, or just standard root my phone and flash a custom rom of a different type, right?

LodeUnknown said:
So at this point, my only option is to switch to a new phone that can be used by Odin, or just standard root my phone and flash a custom rom of a different type, right?
Click to expand...
Click to collapse
You cannot flash a custom ROM to a snapdragon phone using any method, it has a locked bootloader
ODIN is for stock ROMs only (and TWRP recovery which you cannot use on snapdragon either)
You can use ODIN on any S7 for stock ROMs

To sum it all up, you're saying that I have to get an exynos/international version of any Android phone if I want to root and or flash a custom ROM, correct? And if I do, could I still use it with a US phone carrier, like AT&T or MetroPCS afterwards?
And even if I could use it with a US phone carrier, would I still be eligible for any technical support / repair service they would offer, or would I have to use a non-affiliated repair service?

LodeUnknown said:
To sum it all up, you're saying that I have to get an exynos/international version of any Android phone if I want to root and or flash a custom ROM, correct? And if I do, could I still use it with a US phone carrier, like AT&T or MetroPCS afterwards?
And even if I could use it with a US phone carrier, would I still be eligible for any technical support / repair service they would offer, or would I have to use a non-affiliated repair service?
Click to expand...
Click to collapse
Yes, only Exynos has an unlocked bootloader (See the snapdragon vs exynos custom ROM dev forums)
Yes you could still use a US carrier as long as the phone is SIM unlocked (carphone warehouse phones are all unlocked), I have no idea of the limitations / implications, but some people here already do that, and the G930W8 (Canada) is Exynos
No idea about warranty, but if you bought it from say the UK and had it shipped, you'd have to discuss with Samsung if they would accept it into a US service centre or if you'd have to ship it back to the UK, no idea about that, no doubt there are places in the US that you could buy a Exynos from
Hit Samsung up on twitter and ask them

SM-G965U G965USQS4CSC8 & SM-G965U1 G965U1UEU4CSC7 Apr-21-19 Official PIE Firmware

Introduction:
Download official G965USQS4CSC8 (carrier) and G965U1UEU4CSC7 (unlocked) firmware for the SM-G965U and SM-G965U1 here. You can flash either onto a SM-G965U or SM-G965U1 using the patched Odin linked below. Flashing back and forth is safe because they are both on bootloader version 4.
Click to expand...
Click to collapse
Patch Level:
Carrier SM-G965U 04-01-19 (CSC8)
Unlocked SM-G965U1 03-01-19 (CSC7)
Click to expand...
Click to collapse
So, what is userdata?
A lot of people think this is carrier bloat only. However, userdata also contains the files necessary to activate carrier specific features. Without it, you may not be able utilize all of the carrier features that the phone is capable of providing. Please note that carrier userdata may not be available for your carrier.
Click to expand...
Click to collapse
SM-G965U1 (unlocked version) users read here:
Drawbacks of flashing carrier version G965USQS4CSC8 firmware on the unlocked phone (SM-G965U1):
CallerID no longer works unless you subscribe to carriers CallerID service.
Installs carrier bloat.
Benefits of flashing carrier version G965USQS4CSC8 firmware on the unlocked version phone (SM-G965U1):
Will enable all carrier specific features (video calling, etc, etc).
Click to expand...
Click to collapse
SM-G965U (carrier version) users read here:
Drawbacks of flashing unlocked version G965U1UEU4CSC7 firmware on the carrier version phone (SM-G965U):
Will disable all carrier specific features (video calling, etc, etc).
Benefits of flashing unlocked version G965U1UEU4CSC7 firmware on the carrier version phone (SM-G965U):
CallerID works without subscribing to carriers CallerID service.
Eliminates carrier bloat.
Click to expand...
Click to collapse
Installation Instructions:
Reboot to download mode:
Power off your Galaxy S9 Plus completely until it vibrates.
Press and hold the Volume Down + Bixby + Power buttons simultaneously. Release the buttons when you see the warning message.
Now just press Volume up button to continue.
Congratulations, you're now in download mode.
Connect your phone to your PC:
Start the patched Odin 3.13.1 that you downloaded from the provided link.
Plug the cord your phone came with into your phone and PC. Other cords may not work.
The Odin log will display a <ID:0/005> Added!! message once it connects.
Flash the firmware:
First, extract the compressed firmware to a folder on your PC.
In Odin, begin with the BL (bootloader) box, navigate to the firmware folder and select the file beginning with BL_.
Wait for each file to initialize and appear to the right of its corresponding box before attempting to proceed to the next step.
Now select the AP (Application Processor aka System) box, it should open the correct folder, then select the file beginning with AP_.
AP takes a while to initialize, don't worry.
Now select the CP (Core Processor aka modem) box, then select the file beginning with CP_.
Now select the CSC (Consumer Software Customization aka Carrier Settings) box, then select the file beginning with CSC_.
Choose HOME_CSC to not wipe your phone, or CSC_ (preferred option when switching between unlocked and carrier versions) to wipe your phone .
Optionally, select the userdata (User Data) box, then select the file beginning with USERDATA_.
Now, click start and wait for the magic.
Disconnect the cord when the phone reboots.
The phone should boot to recovery to automatically cleanup, then reboot again.
Click to expand...
Click to collapse
Downloads:
Download SM-G965U Firmware Here
Download SM-G965U1 Firmware Here
Download patched Odin Here
Click to expand...
Click to collapse

I v just one question. How do I restore a tripped knox after flashing or restore my flash count to zero?
Sent from my SM-G965F using Tapatalk

Got a non-Android File host mirror? They're slow or not working for me at all no matter what mirror of theirs I choose.

samson007 said:
I v just one question. How do I restore a tripped knox after flashing or restore my flash count to zero?
Sent from my SM-G965F using Tapatalk
Click to expand...
Click to collapse
Tripped knox is forever. There is a fuse that blows on the phone. That said, there are workarounds on rooted phones (you might as well stay rooted). Try looking for edits for the build.prop to restore functionality to Samsung Health and other affected apps. Dr Ketan still makes ROMs I believe and should have something for you.

NLA

NLA

Then I won't root. The only reason I want to root is because I need to use mod apps like Spotify but sadly all the ones v been downloading never worked. Can you help me out please. Thank you
rmarinella said:
Tripped knox is forever. There is a fuse that blows on the phone. That said, there are workarounds on rooted phones (you might as well stay rooted). Try looking for edits for the build.prop to restore functionality to Samsung Health and other affected apps. Dr Ketan still makes ROMs I believe and should have something for you.
Click to expand...
Click to collapse
Sent from my SM-G965F using Tapatalk

samson007 said:
Then I won't root. The only reason I want to root is because I need to use mod apps like Spotify but sadly all the ones v been downloading never worked. Can you help me out please. Thank you
Click to expand...
Click to collapse
I don't want to be rude, but your question was answered already. You can't untrip the know counter. It's an actual fuse, that physically becomes blown. This isn't a software setting, but an actual, physical fuse.
It goes back to the days of people using exploits, and in rare cases would damage their phone in the process, but the phone worked enough to relock the bootloader. Then the person would send their phone back and blame it on the manufacturer. So now Samsung decided to put in an actual fuse so that if you decide to unlock it, your warrenty is permanently void.
Bottom line, your out of luck. I know any unlock would have given a warning that it is PERMANENT and that it would VOID YOUR WARRENTY. Wether you read it and ignored the warning, or didn't bother to read it, it's on you for unlocking your bootloader.

todd3835 said:
I don't want to be rude, but your question was answered already. You can't untrip the know counter. It's an actual fuse, that physically becomes blown. This isn't a software setting, but an actual, physical fuse.
It goes back to the days of people using exploits, and in rare cases would damage their phone in the process, but the phone worked enough to relock the bootloader. Then the person would send their phone back and blame it on the manufacturer. So now Samsung decided to put in an actual fuse so that if you decide to unlock it, your warrenty is permanently void.
Bottom line, your out of luck. I know any unlock would have given a warning that it is PERMANENT and that it would VOID YOUR WARRENTY. Wether you read it and ignored the warning, or didn't bother to read it, it's on you for unlocking your bootloader.
Click to expand...
Click to collapse
Yea I remember those days... Well truth is I haven't rooted.. I was considering it until I read the warranty part... My point is, the reason I want it rooted is because I want to use some modded applications. I researched further and found out I could use some without even rooting. So i tried downloading Spotify mod app, but unfortunately it didn't work. I couldn't get recent application for it, what I kept getting was an outdated mod app. In all it didn't work. So am asking if there's a way to use mod apps without rooting the phone. Thank you
Sent from my SM-G965F using Tapatalk

samson007 said:
Yea I remember those days... Well truth is I haven't rooted.. I was considering it until I read the warranty part... My point is, the reason I want it rooted is because I want to use some modded applications. I researched further and found out I could use some without even rooting. So i tried downloading Spotify mod app, but unfortunately it didn't work. I couldn't get recent application for it, what I kept getting was an outdated mod app. In all it didn't work. So am asking if there's a way to use mod apps without rooting the phone. Thank you
Click to expand...
Click to collapse
You'll have to wait until someone mods the latest app. Or, you could just pay for Spotify. For the record, I used to use a modded Spotify, and they typically patch within a day or two of a modded apk being released. They may have finally switched to server side authentication which is why your likely not seeing an updated version. I stopped bothering because it's just a cat and mouse game. I didn't feel like Spotify was worth it, so I moved on.
I find Google Play Music is a better deal. I get add-free YouTube, and all the same music as Spotify, for the same price.
On a side note, I don't believe Xda allows modded apks that bypass paid features. There are sites that cater to such things, but I'm pretty sure it's a no-no here. They tend to support devs / companies as opposed to cheating them out of money.

Hi dude, I have 2 questions, I just buy S9+ 965U sprint unlock running U3ARH7 can I flash this 965U1's fw? and What is CSC in U1 fw? thanks

optimus207 said:
Hi dude, I have 2 questions, I just buy S9+ 965U sprint unlock running U3ARH7 can I flash this 965U1's fw? and What is CSC in U1 fw? thanks
Click to expand...
Click to collapse
Hi, you can flash the U1 firmware on the Sprint 965U. You need to use the patched Odin linked in the OP. The CSC file included is for multiple carriers. When flashing it will read your sim and setup accordingly.

Umm what's new? The "I" September patch Odin's have been out since mid September.
rmarinella said:
Introduction:
SM-G965U1 (unlocked version) users read here:
SM-G965U (carrier version) users read here:
Installation Instructions:
Downloads:
Click to expand...
Click to collapse

The thread provides detailed instructions and the most current firmware. The instructions are new to the thread and so are the links. Didn't realize I was required to explain what was new to you.

Uploading G965USQS3ARIB firmware now.

Hi, Q. If I install the ARIB version in my U1 under att, I still can use another carrier sim right?
I'm traveling to Argentina soon and I want to know that.
Thanks

Should be fine , your U1 is unlocked. The sim card in Argentina might not set up the APN for you regardless of what firmware you're on. Personally, I would use the U1 firmware though.

juannicolas said:
Hi, Q. If I install the ARIB version in my U1 under att, I still can use another carrier sim right?
I'm traveling to Argentina soon and I want to know that.
Thanks
Click to expand...
Click to collapse
I don't use the "B" revision firmwares, but there was at least one listed as a BOYD firmware. Since your already on U1 and loosing wifi-calling, HD voice, volte, etc, that might give you the best luck. Might be something to look into.

todd3835 said:
I don't use the "B" revision firmwares, but there was at least one listed as a BOYD firmware. Since your already on U1 and loosing wifi-calling, HD voice, volte, etc, that might give you the best luck. Might be something to look into.
Click to expand...
Click to collapse
Sorry, didn't understood your response. Is that an yes besides regaining the features of HDVoice, volte and Wifi Calling?
Thanks

juannicolas said:
Sorry, didn't understood your response. Is that an yes besides regaining the features of HDVoice, volte and Wifi Calling?
Thanks
Click to expand...
Click to collapse
You asked about sim swapping for traveling. The BYOD firmware makes for easier sim swapping. It's designed to populate the carrier settings when you insert a sim instead of needing to wipe your device.
As for ATT features, I believe those firmware are for the U firmware, so yes, you'd regain those features, but you'd get the ATT bloat. I don't mind the bloat personally. I just remove the junk I don't need.

samsung galaxy s7 custom binary blocked by frp lock

Greetings, ever since i tried rooting my phone, i knew something went wrong (i used cf autoroot).
So the first thing i noticed, i was asked to reset the phone or something similar to that, meaning i would lose all my data.
I tried to find a workaround as this had never happened to me before while rooting a phone, and someone had said that i was supposed to download twrp
and change some partition and then change it back. I dont remember what else he mentioned and what exactly i tried doing, i realised it was formatted either way and i had to start fresh. As i setup my phone i went and switched the oem unlock back to "off", as i did not wanna attempt to root again, but i hadn't realised that my phone was infact rooted sucessfully, leading me to my first error after restarting. "Custom binary blocked by frp lock", with absolutely no access to recovery mode at all anymore. Again, trying to find a workaround, i download some stockfirmware that i atleast had hoped was the right one for my phone, after a couple failed attempts of flashing with odin, ( i had gotten various different error messeges on download mode screen such as (REV Check fail device 7 binary 0 and others witch i cannot remember), now im getting a new error screen, stating that an error has occured while updating the device software. I cant flash twrp recovery as the frp lock is on, and the only thing i can guess is that im flashing the wrong firmware, but i cant find a matching code at all.
Its the following: sm-g930fzkadbt
IMEI: 35214310282955
on the back of the phone it says uk yateley, although the phone was purchased in germany.
Im not sure what to do anymore, any advice would be greatly appreciated.
PS: I have managed to get back to the old error screen with the custom binary info, this time with bootloop, by checking the deviceinfo box on odin

Yep you've now learned the hard way not to mess about and read the proper guides.
Anyway "dbt" is just unbranded german firmware. Download UK "BTU" and flash with Odin, it's UK unbranded.
FRP lock means you'll need to unlock the phone with the google account and password that was on it before you started messing about with it.
If you don't know the google email and password you need to read up on how to bypass FRP lock and it's a nightmare.

cooltt said:
Yep you've now learned the hard way not to mess about and read the proper guides.
Anyway "dbt" is just unbranded german firmware. Download UK "BTU" and flash with Odin, it's UK unbranded.
FRP lock means you'll need to unlock the phone with the google account and password that was on it before you started messing about with it.
If you don't know the google email and password you need to read up on how to bypass FRP lock and it's a nightmare.
Click to expand...
Click to collapse
Thanks for your reply, just a question, will any btu update work? Should i download latest android version btu firmware?
(Also yes, it was stupid of me to try and do it quick but i had rooted 3 different samsung galaxy phones in the past without issues, either i did something wrong or it took something way too specific to do the job, perhaps the phone's unrootable, but thank you either way) :fingers-crossed:

Elef244 said:
Thanks for your reply, just a question, will any btu update work? Should i download latest android version btu firmware?
(Also yes, it was stupid of me to try and do it quick but i had rooted 3 different samsung galaxy phones in the past without issues, either i did something wrong or it took something way too specific to do the job, perhaps the phone's unrootable, but thank you either way) :fingers-crossed:
Click to expand...
Click to collapse
You'll likely only find the last version of BTU think it was August 2019. It isn't updated officially anymore but it'll be fine to use.

cooltt said:
You'll likely only find the last version of BTU think it was August 2019. It isn't updated officially anymore but it'll be fine to use.
Click to expand...
Click to collapse
I've found android 6 to android 8 with all the monthly updates, im just trying the latest of the latest though i dont remember my android version, ill try android 7 and 6 if that doesn't work, thanks again. I'll make sure to reply if this works or doesn't.

cooltt said:
Yep you've now learned the hard way not to mess about and read the proper guides.
Anyway "dbt" is just unbranded german firmware. Download UK "BTU" and flash with Odin, it's UK unbranded.
FRP lock means you'll need to unlock the phone with the google account and password that was on it before you started messing about with it.
If you don't know the google email and password you need to read up on how to bypass FRP lock and it's a nightmare.
Click to expand...
Click to collapse
OK so i thought it worked but i can only enter recovery mode now and download mode, but cant actually boot the system, it just boots up the battery screen whenever i plug the charger, and never shows the actual battery info, just the thunder icon. Formatting from recovery mode doesn't help either (Note whenever i launch recovery mode it says installing update, then says no command and brings me to the recovery menu) Any ideas?
PS: It fixed itself. Sorry for the pointless edit.

Samsung S7 edge sm-G930V android version 8.0 Unlock Bootloader

Hello Guys i have been searching all over the internet for a few month, where do i find the boot unlock for this particular phone? I need this in order to root and install lineage OS custom rom
I really appreciate if someone has the information.

CAN ANYONE HELP PLEASE? I need to unlock bootloader for Verizon SM-G930V

ibex333 said:
CAN ANYONE HELP PLEASE? I need to unlock bootloader for Verizon SM-G930V
Click to expand...
Click to collapse
I just picked up this model myself and find myself in the same boat. My developer options do list an "OEM unlock" option. Does yours?

ibex333 said:
CAN ANYONE HELP PLEASE? I need to unlock bootloader for Verizon SM-G930V
Click to expand...
Click to collapse
Emmalfal said:
I just picked up this model myself and find myself in the same boat. My developer options do list an "OEM unlock" option. Does yours?
Click to expand...
Click to collapse
It doesn't matter, Verizon devices have locked bootloaders that can't be unlocked, don't waste your time trying, it isn't going to happen. Verizon devices have been this way for years now, I don't forsee that changing at any time in the future.

Droidriven said:
It doesn't matter, Verizon devices have locked bootloaders that can't be unlocked, don't waste your time trying, it isn't going to happen. Verizon devices have been this way for years now, I don't forsee that changing at any time in the future.
Click to expand...
Click to collapse
My device has the "oem unlock" button. Does that not matter? I was surprised as hell to find that.

Emmalfal said:
My device has the "oem unlock" button. Does that not matter? I was surprised as hell to find that.
Click to expand...
Click to collapse
You can try it but I'm pretty certain that Verizon has it locked down. There is a root method for Verizon S7 and S7 edge but no TWRP or custom ROMs that I know of.
Verizon S7 / S7 Edge [Root Guide] SM-G930V SM-G935V [NO KNOX TRIP]
Hi, I am compiling this guide for rooting the verizon variant. I also hope to fill in some gaps in the other guides. I AM NOT RESPONSIBLE FOR ANY PROBLEMS YOU MAY CAUSE OR ENCOUNTER I did not develop this, I'm only telling you how to do it...
forum.xda-developers.com

Droidriven said:
You can try it but I'm pretty certain that Verizon has it locked down. There is a root method for Verizon S7 and S7 edge but no TWRP or custom ROMs that I know of.
Verizon S7 / S7 Edge [Root Guide] SM-G930V SM-G935V [NO KNOX TRIP]
Hi, I am compiling this guide for rooting the verizon variant. I also hope to fill in some gaps in the other guides. I AM NOT RESPONSIBLE FOR ANY PROBLEMS YOU MAY CAUSE OR ENCOUNTER I did not develop this, I'm only telling you how to do it...
forum.xda-developers.com
Click to expand...
Click to collapse
Figured I'd give it the old college try. Got Odin to recognize the phone and went through the root process. All looked well until the very end. "Complete (write) operation failed."

Emmalfal said:
Figured I'd give it the old college try. Got Odin to recognize the phone and went through the root process. All looked well until the very end. "Complete (write) operation failed."
Click to expand...
Click to collapse
And now, using the latest version of Odin (I somehow downloaded an older one the first time around) it got to recovery.img and just stuck there. An exercise in frustration as you had warned. I need a Verizon phone that can 100 percent be rooted. I'm using a rooted original Pixel now but that sucker is getting worn out.

Emmalfal said:
Figured I'd give it the old college try. Got Odin to recognize the phone and went through the root process. All looked well until the very end. "Complete (write) operation failed."
Click to expand...
Click to collapse
It might depend on what version/build number of stock firmware is installed on the device. That guide might be for an older version of a specific version. If what you have is newer than what the guide was written for, that might be why it failed.
Does it say anything in the guide thread about it requiring a specific stock firmware or specific bootloader version?

Emmalfal said:
And now, using the latest version of Odin (I somehow downloaded an older one the first time around) it got to recovery.img and just stuck there. An exercise in frustration as you had warned. I need a Verizon phone that can 100 percent be rooted. I'm using a rooted original Pixel now but that sucker is getting worn out.
Click to expand...
Click to collapse
How about an unlocked device that can be used on Verizon's network?

Droidriven said:
It might depend on what version/build number of stock firmware is installed on the device. That guide might be for an older version of a specific version. If what you have is newer than what the guide was written for, that might be why it failed.
Does it say anything in the guide thread about it requiring a specific stock firmware or specific bootloader version?
Click to expand...
Click to collapse
I've gone through a couple different tutorials and they all seem to link to the same files that I need to download. It's been frustrating because looking for proper files for a phone this old leads to a lot of dead links. I'm probably going to give it up soon, but you know how it is. There's always "one more thing" to try. I tell you, I'm going to research like hell before I buy another phone. I need to know for sure that it can be rooted. In this case, I inherited my wife's old phone and a quick search revealed that it ought to be a piece of cake to root. There's always some little detail that trips me up. I appreciate your help with this.

Emmalfal said:
And now, using the latest version of Odin (I somehow downloaded an older one the first time around) it got to recovery.img and just stuck there. An exercise in frustration as you had warned. I need a Verizon phone that can 100 percent be rooted. I'm using a rooted original Pixel now but that sucker is getting worn out.
Click to expand...
Click to collapse
Try a version of Odin from around the same time the S7/S7 edge was released onto the market. Some versions work better with certain devices, as android evolved and as Odin gets updated to newer versions for newer devices, there are slight differences along the way that can effect how it works on older devices.
If the stock firmware that you are trying to flash is older than what was already installed on the device, it will probably fail due to not allowing the device to be degraded to an older version, it's a "security" measure put there to prevent you from installing a less "secure" operating system.

Droidriven said:
How about an unlocked device that can be used on Verizon's network?
Click to expand...
Click to collapse
Yeah, that would work. It's been so long since I messed around with this stuff -- I've had the pixel for six or seven years I think -- that I've forgotten everything I once knew.
Droidriven said:
Try a version of Odin from around the same time the S7/S7 edge was released onto the market. Some versions work better with certain devices, as android evolved and as Odin gets updated to newer versions for newer devices, there are slight differences along the way that can effect how it works on older devices.
If the stock firmware that you are trying to flash is older than what was already installed on the device, it will probably fail due to not allowing the device to be degraded to an older version, it's a "security" measure put there to prevent you from installing a less "secure" operating system.
Click to expand...
Click to collapse
I'll look that up and try it out. Nothing to lose at this point. All I'm trying to flash at this point is the CF Auto Root Tar.md5, as per the instructions.

Emmalfal said:
I've gone through a couple different tutorials and they all seem to link to the same files that I need to download. It's been frustrating because looking for proper files for a phone this old leads to a lot of dead links. I'm probably going to give it up soon, but you know how it is. There's always "one more thing" to try. I tell you, I'm going to research like hell before I buy another phone. I need to know for sure that it can be rooted. In this case, I inherited my wife's old phone and a quick search revealed that it ought to be a piece of cake to root. There's always some little detail that trips me up. I appreciate your help with this.
Click to expand...
Click to collapse
No, I mean does it say anything about it requiring a specific version of stock firmware or specific version of bootloader to be already installed on the device "before" you do the rooting process described in the guide?
Sometimes these kinds of things require your device to have a certain stock software version as a starting point before the device is modified. Most of the time, if the device is ever updated to a newer version, the specific exploit that was being used to root gets patched in the update, killing the effectiveness of the exploit used to root. From that point on, chances of rooting are nil.

Emmalfal said:
Yeah, that would work. It's been so long since I messed around with this stuff -- I've had the pixel for six or seven years I think -- that I've forgotten everything I once knew.
I'll look that up and try it out. Nothing to lose at this point. All I'm trying to flash at this point is the CF Auto Root Tar.md5, as per the instructions.
Click to expand...
Click to collapse
The vulnerability that CF autoroot takes advantage of may have been patched in newer versions of firmware.
I haven't been able to root any of my devices for last 4-5 years.

Droidriven said:
No, I mean does it say anything about it requiring a specific version of stock firmware or specific version of bootloader to be already installed on the device "before" you do the rooting process described in the guide?
Sometimes these kinds of things require your device to have a certain stock software version as a starting point before the device is modified. Most of the time, if the device is ever updated to a newer version, the specific exploit that was being used to root gets patched in the update, killing the effectiveness of the exploit used to root. From that point on, chances of rooting are nil.
Click to expand...
Click to collapse
Yeah, I've been careful to download files in keeping with my specific phone, not just the G930V but the longer version of that model number, which seems super specific. Nothing works. I've tried three or four different versions of Odin at this point, but they all either fail or get stuck somewhere in the process. Probably time to start searching for a new phone. I looked around for other ways to root this s7 but i'm not finding much. I rooted the PIxel with Magisk.

Emmalfal said:
Yeah, I've been careful to download files in keeping with my specific phone, not just the G930V but the longer version of that model number, which seems super specific. Nothing works. I've tried three or four different versions of Odin at this point, but they all either fail or get stuck somewhere in the process. Probably time to start searching for a new phone. I looked around for other ways to root this s7 but i'm not finding much. I rooted the PIxel with Magisk.
Click to expand...
Click to collapse
I'm not talking about model number version, I mean the specific build number of the firmware that is installed on the device. Some guides/methods only work on specific build numbers of stock firmware or only work if a specific version of bootloader is installed on the device.

Droidriven said:
I'm not talking about model number version, I mean the specific build number of the firmware that is installed on the device.
Click to expand...
Click to collapse
Ah. I'll check that.

Emmalfal said:
And now, using the latest version of Odin (I somehow downloaded an older one the first time around) it got to recovery.img and just stuck there. An exercise in frustration as you had warned. I need a Verizon phone that can 100 percent be rooted. I'm using a rooted original Pixel now but that sucker is getting worn out.
Click to expand...
Click to collapse
The S7 *can* be rooted, with lots of limitations afterwards. It just can't be BL unlocked

It could be failing due to the usb port or cable. I have an S8 that i can no longer flash only because I don't have a usb port in my pc old enough to flash it. I assume the S7 is the same way