Database Users

Brick Phone Challenge // dm-verity error... failed code : 0x02

Hello guys,
I bought a soft bricked S7 Edge with a dm-verity error because I thought I could easily fix the issue myself. The previous owner said he went to update the samsung software via android and this happened. But it doesn't seem too easy to fix. I've tried a bunch of different solutions I found on the interwebs but none have worked so far. I would appreciate some help because I don't seem to be making any progress.
EDIT: I've read that some people have reported losing their IMEI after an OTA update. Maybe that is what happened?
NOTE: I do NOT get the "failed to mount /efs" error
When I got the phone, it would boot directly into Android Recovery with a dm-verity error on the bottom. So here is what I tried:
1 . First I did the obvious, facotry reset and wipe partition. No change.
2. Downloaded the firmware with SamFirm (SM-G935F Regin ZTO) and flashed with Odin. It then booted into a screen with a hazard sign and a DRK error. Then returned to Android Recovery. Observation: When I extracted the firmware, I got a strange corrupted error. I downloaded it again, same corruption error. Is that normal? Also, I am not certain the region is ZTO, maybe this phone is from some other region. Does it matter?
3. I flashed the same firmware again. This time the phone booted up to a Samsung error that said to use SmartSwitch's Emergency recovery. I tried but it asks for a recovery code and I don't have one.
4. I tried to flash CF-autoroot but it gave an error in Odin and failed. EDIT: failed because "Blocked by FRP Lock" but I can't unlock the OEM like everyone else because I can't boot normally into android. Any workaround?
5. I downloaded firmware from a different region (UK). I got a DRK error and it booted into Android recovery. The bottom of the phone reads:
No Support SINGLE-SKU​Supported API: 3​dm-verity error...​failed code : 0x02​
6. I flashed the combination file and was able to boot into Factory Binary. I went into Settings to unlock OEM but there isn't that option in the Developer Settings!
That's where I am now. Any ideas?
Thanks!

Are you sure that it is an original 935F?

Pet1981 said:
Are you sure that it is an original 935F?
Click to expand...
Click to collapse
On the back of the phone, its has the model number written like this SM-G935F SAMSUNG YATELEY GU46 6GG UK. Is there someway for this to be wrong?

dleeII said:
On the back of the phone, its has the model number written like this SM-G935F SAMSUNG YATELEY GU46 6GG UK. Is there someway for this to be wrong?
Click to expand...
Click to collapse
Samsung Yateley is Samsung's official UK QA facility, they only receive official products direct from the factories and those sent back for repair and refurbishment. I know this because it's literally just down the road from my house and a couple of friends have worked there over the years.
However, "SAMSUNG YATELEY GU46 6GG UK" has been on literally millions of devices worldwide for years.
It's not a reliable Indication of a genuine product or in fact an indication of anything other than the fact that Samsung have a facility in Yateley.
If the device is a refurb or even a fake it's entirely possible that it only says "SM-G935F SAMSUNG YATELEY GU46 6GG UK" because that's what it's supposed to say.
I'm sorry that I can't be of any more help but, I hope I've helped by stopping you from embarking on a wild goose chase.

X1ras said:
Samsung Yateley is Samsung's official UK QA facility, they only receive official products direct from the factories and those sent back for repair and refurbishment. I know this because it's literally just down the road from my house and a couple of friends have worked there over the years.
However, "SAMSUNG YATELEY GU46 6GG UK" has been on literally millions of devices worldwide for years.
It's not a reliable Indication of a genuine product or in fact an indication of anything other than the fact that Samsung have a facility in Yateley.
If the device is a refurb or even a fake it's entirely possible that it only says "SM-G935F SAMSUNG YATELEY GU46 6GG UK" because that's what it's supposed to say.
I'm sorry that I can't be of any more help but, I hope I've helped by stopping you from embarking on a wild goose chase.
Click to expand...
Click to collapse
I flashed the combination software and in the Factory Binary, it says MODEL: SM-G935F [SS]. Is the information reliable? Is there a possibility that the phone is fake? If so, is there a way to tell for sure?
EDIT: I checked the IMEI I got from the Factory Binary at IMEI.info and it seems to be valid.

I don't know
THIS
can help you or not

Try to use z3x box i read some function of z3x box but i'm not sure if it will fix your phone. Just go to gsm-forum for more details.

I thought this error message you're getting is because you flashed something on your phone intended for another model. I got the same error when I first got my S7 Edge because I stupidly thought I had the snapdragon variant when in fact the G935F is the Exynos variant. I got exactly the same error message. Have you tried reflashing stock firmware via Odin? Have you checked the Knox trip counter to see if the phone had been tampered with prior to you buying it? I live a stone's throw away from Yateley (5 mins maximum) if you want me to pop in and enquire?
Sent from my SM-G935F using XDA-Developers Legacy app

Sorry for the delayed response. I left my phone with some technicians with a ZX3 and Octopus Box and they were unable to fix the phone. But they didn't seem very interested either so maybe they just blew me off. Not sure. I'll try to find someone else soon.
speedyjay said:
I thought this error message you're getting is because you flashed something on your phone intended for another model. I got the same error when I first got my S7 Edge because I stupidly thought I had the snapdragon variant when in fact the G935F is the Exynos variant. I got exactly the same error message. Have you tried reflashing stock firmware via Odin? Have you checked the Knox trip counter to see if the phone had been tampered with prior to you buying it? I live a stone's throw away from Yateley (5 mins maximum) if you want me to pop in and enquire?
Sent from my SM-G935F using XDA-Developers Legacy app
Click to expand...
Click to collapse
This may be the problem. I have tried flashing the stock firmware with Odin but maybe I'm flashing the snapdragon variant instead of the exynos. How can I tell the difference?
My warranty is 1 (0x0500). That means that Knox was tripped right?

mashardpro said:
I don't know
THIS
can help you or not
Click to expand...
Click to collapse
I've tried this guide and it didn't solve the issue.

I tried flashing a Snapdragon firmware and it failed. So I assume a Exynos firmware is the correct one.

dleeII said:
I tried flashing a Snapdragon firmware and it failed. So I assume a Exynos firmware is the correct one.
Click to expand...
Click to collapse
G935F is exynos yes
Have you tried OEM unlock via adb if possible?
Then flash twrp and https://build.nethunter.com/android-tools/no-verity-opt-encrypt/no-verity-opt-encrypt-5.0.zip ?
Sorry if it's not possible just brainstorming ..

misterashman said:
G935F is exynos yes
Have you tried OEM unlock via adb if possible?
Then flash twrp and https://build.nethunter.com/android-tools/no-verity-opt-encrypt/no-verity-opt-encrypt-5.0.zip ?
Sorry if it's not possible just brainstorming ..
Click to expand...
Click to collapse
No, I haven't tried that yet. How do I access the S7 via adb again? Is it in download mode or in the recovery? Samsungs don't have "fastboot" right?

I'm in the exact same situation, it's FRP locked to me but I can't get passed the DM-Verity to unlock nor root to pass DM-Verity. Hard to believe this could be bricked from a software issue.
---------- Post added at 05:14 PM ---------- Previous post was at 04:44 PM ----------
dleeII said:
No, I haven't tried that yet. How do I access the S7 via adb again? Is it in download mode or in the recovery? Samsungs don't have "fastboot" right?
Click to expand...
Click to collapse
Did you ever find a solution?

Hey, I was able to unbrick the phone. But I had to take it to a technician that used a very interesting technique to reset the phone. Apparently, someone had tried to flash another IMEI on the phone. To reset the device, he switched out one of the memories (there are 3 or 4 slots). Then when you boot up the phone, it is tricked into thinking you are booting up for the first time. At leas that is what I understood. Maybe someone more familiar with phone hardware could explain the solution better.
Rymcbc said:
I'm in the exact same situation, it's FRP locked to me but I can't get passed the DM-Verity to unlock nor root to pass DM-Verity. Hard to believe this could be bricked from a software issue.
---------- Post added at 05:14 PM ---------- Previous post was at 04:44 PM ----------
Did you ever find a solution?
Click to expand...
Click to collapse

Did you ever find a solution?

dleeII said:
Hello guys,
I bought a soft bricked S7 Edge with a dm-verity error because I thought I could easily fix the issue myself. The previous owner said he went to update the samsung software via android and this happened. But it doesn't seem too easy to fix. I've tried a bunch of different solutions I found on the interwebs but none have worked so far. I would appreciate some help because I don't seem to be making any progress.
EDIT: I've read that some people have reported losing their IMEI after an OTA update. Maybe that is what happened?
NOTE: I do NOT get the "failed to mount /efs" error
When I got the phone, it would boot directly into Android Recovery with a dm-verity error on the bottom. So here is what I tried:
1 . First I did the obvious, facotry reset and wipe partition. No change.
2. Downloaded the firmware with SamFirm (SM-G935F Regin ZTO) and flashed with Odin. It then booted into a screen with a hazard sign and a DRK error. Then returned to Android Recovery. Observation: When I extracted the firmware, I got a strange corrupted error. I downloaded it again, same corruption error. Is that normal? Also, I am not certain the region is ZTO, maybe this phone is from some other region. Does it matter?
3. I flashed the same firmware again. This time the phone booted up to a Samsung error that said to use SmartSwitch's Emergency recovery. I tried but it asks for a recovery code and I don't have one.
4. I tried to flash CF-autoroot but it gave an error in Odin and failed. EDIT: failed because "Blocked by FRP Lock" but I can't unlock the OEM like everyone else because I can't boot normally into android. Any workaround?
5. I downloaded firmware from a different region (UK). I got a DRK error and it booted into Android recovery. The bottom of the phone reads:
No Support SINGLE-SKU​Supported API: 3​dm-verity error...​failed code : 0x02​
6. I flashed the combination file and was able to boot into Factory Binary. I went into Settings to unlock OEM but there isn't that option in the Developer Settings!
That's where I am now. Any ideas?
Thanks!
Click to expand...
Click to collapse
You tried smart switch if identify the device and instal stock rom?

bricked S7 Edge with a dm-verity error
dleeII said:
Hello guys,
I bought a soft bricked S7 Edge with a dm-verity error because I thought I could easily fix the issue myself. The previous owner said he went to update the samsung software via android and this happened. But it doesn't seem too easy to fix. I've tried a bunch of different solutions I found on the interwebs but none have worked so far. I would appreciate some help because I don't seem to be making any progress.
EDIT: I've read that some people have reported losing their IMEI after an OTA update. Maybe that is what happened?
NOTE: I do NOT get the "failed to mount /efs" error
When I got the phone, it would boot directly into Android Recovery with a dm-verity error on the bottom. So here is what I tried:
1 . First I did the obvious, facotry reset and wipe partition. No change.
2. Downloaded the firmware with SamFirm (SM-G935F Regin ZTO) and flashed with Odin. It then booted into a screen with a hazard sign and a DRK error. Then returned to Android Recovery. Observation: When I extracted the firmware, I got a strange corrupted error. I downloaded it again, same corruption error. Is that normal? Also, I am not certain the region is ZTO, maybe this phone is from some other region. Does it matter?
3. I flashed the same firmware again. This time the phone booted up to a Samsung error that said to use SmartSwitch's Emergency recovery. I tried but it asks for a recovery code and I don't have one.
4. I tried to flash CF-autoroot but it gave an error in Odin and failed. EDIT: failed because "Blocked by FRP Lock" but I can't unlock the OEM like everyone else because I can't boot normally into android. Any workaround?
5. I downloaded firmware from a different region (UK). I got a DRK error and it booted into Android recovery. The bottom of the phone reads:
No Support SINGLE-SKU​Supported API: 3​dm-verity error...​failed code : 0x02​
6. I flashed the combination file and was able to boot into Factory Binary. I went into Settings to unlock OEM but there isn't that option in the Developer Settings!
That's where I am now. Any ideas?
Thanks!
Click to expand...
Click to collapse
I Also Have this problem with Samsung SM-G935F
I Solved This Problem With Small Trick
1. Flash Phone With Official Firmware
2. Flash Twrp Recovery
3. Wipe All Data Leave System
4. Reboot
Now I got My device back Alive
You Can Try May Be Its Works For You

I tried the same and my fone booted but its very unstable with crashing apps and random restarts...
With smart switch it ends into dm varity verification hash tree error or dm-varity error
Any solutions...

Please check my answer for the S8+ I believe it should be the same process.
https://forum.xda-developers.com/showpost.php?p=75342726&postcount=10
Good Luck

ODIN firmware flash fail - UK EE

Hi there,
Long story short, I purchased a used S8 from someone on FB but when I got home it had the FRP reset lock on it. Instead of asking for the password and email (have since given), which I thought would be too rude, I decided to try and fix it myself.
Decided to follow a tutorial, which told me to flash the 7.0 firmware for the device (running on Android 7, not 8) in order to remove this. Unfortunately, the firmware flash failed on ODIN and I'm unable to recover the device using SmartSwitch. I just get the "an error has occurred while updating" message when trying to boot the phone, but that doesn't prevent me accessing download mode.
DEVICE DETAILS: S8, locked to EE network (UK), G950F. OEM lock and USB debugging were enabled. I've tried the latest Android 7 firmware on Sammobile, would flashing the BTU firmware or Android 8 work? Pretty sure the phone is the SS version, if that helps at all.
Does anyone have any tips on what I could do? Much appreciated.
Thanks.

RESOLVED
Thanks to @instrumentaly, this issue was resolved!!
This guy was helpful at every step of the way, well done and thanks again. Honestly, at first glance I thought it was too good to be true but I can now use my new phone again thanks to him. Professionally done.

SM-T590 frp bypass help

Sm-t590 on android 9 bought online and it's Google locked tried a few methods but cant seem to get around it...any help would be great.

https://drive.google.com/file/d/1XpSZC865lOFpf-7ClmUBu59XhWns-kQN/view?usp=sharing

mindlery said:
https://drive.google.com/file/d/1XpSZC865lOFpf-7ClmUBu59XhWns-kQN/view?usp=sharing
Click to expand...
Click to collapse
Hi! I've inherited a SM-T590 (among various other devices) from a deceased relative and try to figure out how to unblock them. I flashed the engineering image and turned on ADB but I don't see how to get rid of the FRP from there. What would be the next steps to disable the FRP entirely?
Thanks!

Once you flash the eng ROM, which you have, go into developer options and enable OEM unlock. Then factory reset within the settings. After that you can flash stock and frp will be disabled.

That worked! Thanks a lot!

Hello,
I know this thread is old. I have almost the same problem, except this is a familly kid who forget his lock screen password, and he used a dummy email adresse to create google account... And android version is 10, not 9.
So we did a factory reset from the recovery menu. But, now, we have to enter the google account, and of course, he doesn't remember.
I tried some (non trusted) tools as samsung frp tool, but not working. I tried a combination rom (i don't know if this is the good one), but in the download mode, the device tells me that :
frp is enabled, ignore pit download.
I tried to flash latest version 10 stock rom, but no change.
Is it worth to try to flash with a stock rom version 8 or 9 ? But to get these roms, i have to pay, but no garantie that this will work...
The device is not in debug mode, of course, and oem locked.
In the second post of this thread, there was a google drive link, but it's dead.
Do i have to put this galaxy tab a tm-t590 to the trash, or is there some hope to unlock it?

Finally did it.
I downgraded using odin in Android 9 using a stock rom, for 2.99$.
https://samfrew.com/fr/download/Galaxy__Tab__A__/gi1r/XEF/T590XXU3BSG3/T590OXM3BSG3/
I tried again samsung frp tool that I trust now .
I followed this video:
But the step *#0*# didn't work. So i tried to launch some apps from the web launcher.
I didn't remember exactly how I did it, but I succeded to create a new google account.
I restarted the device, and and i'm now in android. I activated debug mode and disabled oem mode.
I will try to flash something new and maybe alternative firmware.
I don't know which, but I will search here

SM-935A FRP Lock, am I screwed? (accidentally upgraded to Binary A)

Purchased the phone off guy on Facebook. It appears that he wiped it without realizing about the FRP lock. It had 7.0 on it. I tried all the tricks you see on the youtube videos to bypass FRP but none of them worked. I know how to use ODIN and Z3X, so I flashed an 8.0 firmware thinking I would try some of the bypass methods for 8.0. Those didn't work so then I tried to move back to 7.0.....and then I learned that you can't downgrade bootloaders. In odin it would say Fused 10 > Binary 4, for example. To be clear, the firmware that I am on is G935UUESACSF1.
The next thing I tried was to load a combination firmware. I used G935AUCUAASF1. That allowed me to load up "Factory Binary" and within that firmware I have access to the settings menu and IMEI dialer. I went into the menu, enabled developer options, and made sure that USB debugging was enabled. There was no option for "OEM Unlock". I used the dialer to bring up USB settings and set it to MTP+ADB. Then I brought up Z3X 29.5 thinking I would use the FRP unlock feature there. The SM-935A does not have a feature for that, but the SM-935T and F models do. So I took a risk and pulled up the T model and I selected FRP Reset. It did it's thing and it said that it was successful. I followed the instructions to do a factory data wipe directly after.
I wasn't sure what to do next, so I put the phone back into download mode and used ODIN to flash the 8.0 firmware back on. When that booted up, nothing had changed..it was still FRP locked. I'm not sure if I'm missing something in the process or what I should do next, if anything can be done. It seems I'm very limited in what I can do because from what it seems, I can't downgrade to a lower bootloader binary so I can't, for example, go back to 7.0 or 6.0.1. I can't even go back to earlier versions of 8.0 and try some of the tricks for those (like the S Voice Terms and Conditions trick..S Voice isn't listed during startup on my firmware)...
Anything that I can do? Any help is appreciated.

Can you get into custom recovery? If you can, flash no verity opt encrypt and it will be fixed or if not, also flash RMM bypass

freakwithracket said:
Purchased the phone off guy on Facebook. It appears that he wiped it without realizing about the FRP lock. It had 7.0 on it. I tried all the tricks you see on the youtube videos to bypass FRP but none of them worked. I know how to use ODIN and Z3X, so I flashed an 8.0 firmware thinking I would try some of the bypass methods for 8.0. Those didn't work so then I tried to move back to 7.0.....and then I learned that you can't downgrade bootloaders. In odin it would say Fused 10 > Binary 4, for example. To be clear, the firmware that I am on is G935UUESACSF1.
The next thing I tried was to load a combination firmware. I used G935AUCUAASF1. That allowed me to load up "Factory Binary" and within that firmware I have access to the settings menu and IMEI dialer. I went into the menu, enabled developer options, and made sure that USB debugging was enabled. There was no option for "OEM Unlock". I used the dialer to bring up USB settings and set it to MTP+ADB. Then I brought up Z3X 29.5 thinking I would use the FRP unlock feature there. The SM-935A does not have a feature for that, but the SM-935T and F models do. So I took a risk and pulled up the T model and I selected FRP Reset. It did it's thing and it said that it was successful. I followed the instructions to do a factory data wipe directly after.
I wasn't sure what to do next, so I put the phone back into download mode and used ODIN to flash the 8.0 firmware back on. When that booted up, nothing had changed..it was still FRP locked. I'm not sure if I'm missing something in the process or what I should do next, if anything can be done. It seems I'm very limited in what I can do because from what it seems, I can't downgrade to a lower bootloader binary so I can't, for example, go back to 7.0 or 6.0.1. I can't even go back to earlier versions of 8.0 and try some of the tricks for those (like the S Voice Terms and Conditions trick..S Voice isn't listed during startup on my firmware)...
Anything that I can do? Any help is appreciated.
Click to expand...
Click to collapse
can you Kindly Share the stock rom you used. i am having the Same issues. Thank you in advance .

[issue found][archived] FRP / OEM locked device that won't start OS

Edit 3: TL;DR: This is appears to be an S8 exclusive error, it's shown in the recovery:
"Product device tree not found, couldn't verify firmware" or something like that. For solutions, please look that up.
So, I bought a bootlooping S8 in the hopes of fixing it.
Since OEM and FRP lock are on, I went with installing Samsung firmware on it, as installing a custom recovery at this point is not possible.
The default recovery wouldn't work, so I wasn't able to know which firmware exactly to flash, because I couldn't find out which model exactly I have bought.
I do not know the carrier of the device either, but it should be from some german provider.
All of the firmwares I tried just bootlooped, but the recovery works again, except for ADB, which is quite unfortunate, and I have no idea why it fails, the device shows up when I'm in the recovery menu, but as soon as I activate ADB, it's gone from the list of connected devices.
Combination firmwares sometimes show some turning gears animations, but then crash with some, thought often memory related, pretty random crash issue.
Another problem I am now facing is that in the process of trying to find a working firmware I now upgraded the devices "binary level"? (forgot what exactly it was called) to 6, so I can't flash any older firmware or combination firmware than 6, since downgrading isn't allowed.
I received the device with either binary level 1 oder 2.
My theory is that I don't have the right firmware, since I keep seeing dm-verity and license errors...
I am happy to provide logs if necessary.
The goal is to have an unlocked bootloader/ custom recovery.
I literally am going INSANE over this FRP blocking me from flashing TWRP and being done with this in under 10 minutes, please help :c
PS: Some random info attached
Edit 1: With the IMEI code i found while opening the phone I now know my model number: SM-G950FZKADBT.
Any tips for finding the PDA code of the originally installed system? Or finding a matching firmware?
Is this even neccesary? Why do official firmwares not work for me? :c
Edit 2: Somewhat solution: I think the only way to recover this device would be to find it's firmware, which is just NOT to be found...
So, until a miracle happens I'm gonna keep reading "Firmware is not valid" errors in the log

Did you look in samfrew.com ? ? ? I just grabbed a fw from there.
The dnld was loooong so I purchased a privilege for faster speed . . .