If i modify the system partition, the recovery greets me with "dm-verity verification failed".
I do *not* get the message about the DRK being invalid. My phone works fine.
Is there a way to remove this cosmetic error?
sins07 said:
If i modify the system partition, the recovery greets me with "dm-verity verification failed".
I do *not* get the message about the DRK being invalid. My phone works fine.
Is there a way to remove this cosmetic error?
Click to expand...
Click to collapse
No promises...
http://forum.xda-developers.com/s7-edge/how-to/guide-how-to-fix-check-drk-imei-issues-t3379516
I suppose that will work but i want my system partition modified/themed the way it is
I've heard it has something to do with the efs partition inside /efs/prov_data/dmvt or /efs/prov_data/dev_root
Maybe i can recalculate the hash value for the system partition and inject it somewhere?
My DRK is fine. just wish to remove recovery error.
i'm on stock recovery and my unit will always boot because I have the G930P eng kernel with dm-verity disabled. Stock recovery still thinks dm-verity is enabled because it just says "dm-verity verification failed" which is normal when you modify the system partition. I'm only trying to figure out how to remove the dm-verity verification failed error.
i can do such repair remotely
I have a galaxy s7 and rooted my device and some security update, updated my phone now I'm stuck in a bootloop.
I have tried Samsung smart switch and it wont take my model name. What do I do next?
kenny08vt said:
I have a galaxy s7 and rooted my device and some security update, updated my phone now I'm stuck in a bootloop.
I have tried Samsung smart switch and it wont take my model name. What do I do next?
Click to expand...
Click to collapse
Go to recovery mode. factory reset. should boot now.
Hello, Is there any update about how to fix?
Any way to fool your kernel/recovery into thinking dm-verity is just fine?
Samsung s7 says dm-verify verification failed after been reset
Hi everyone! Help! Need help! As titled, i have almost tried everything, frp lock is enabled i can't acces to recovery menu and i'm unable to flash TWRP recovery or boot into normal recovery, frp lock blocked everything, i can just access to download mode
Please, I need some help with my SM-G9350 Hong-Kong Galaxy S7 edge on Binary 4
I got custom binary TWRP recovery/boot blocked by frp lock when the device was working fine running custom rom, and then I flashed stock firmware via Odin and all was just fine and Odin succeed pass, but when installing system updates in recovery it was up to 32% then erasing and then it should boot up system, but it didn't it keeps rebooting to recovery with no options at all, just showing the android guy with no command below and then when I hard it to enter in recovery menu it shows a black screen with some lines that says couldn't open recovery cause unknown and no such file directory, and device is busy, and keep doing the same thing, I did same and flashed again with latest firmware but same thing happened, and then I tried to flash TWRP in order to flash a custom rom to boot up system, but Odin fails and says in download mode custom binary recovery blocked by frp lock, known that my device's bootloader is already unlocked and I flashed before this a whole of stuff, now, I can just access to download mode, otherwise I can't do anything else even no adb , there is no a combination file for the Hong-Kong variant G9350ZH, there is only for the Open-China variant G9350ZC which is not combatible with the device, even there are no adb enabled files, if someone has a solution for this, please kindly take care of this problem?
No menu in stock recovery, it's just saying:
#fait to open recovery_cause(No such file directory)#
#Reboot Recovery Cause is [UNKNOWN]#
No Support SINGLE=SKU
File-Based OTA
Supported API: 3
# MANUAL MODE v1.0.0#
E: [libfs_mgr]Blob verification failed :255
E: Failed setting up dirty target
E:[libfs_mgr] Error creating device mapping: Device or resource busy
E:[libfs_mgr] Couldn't create verity device!
E: Failed setting up dirty target
[omc-app-link] fail to mount /system as rwE:[libfs_mgr]Error creating device mapping: Device or resource busy
E:[libfs_mgr] Couldn't create verity device!
E: Failed setting up dirty target
[omc-permission] fail to mount /system as rwE:[libfs_mgr]Error creating device mapping: Device or resource busy
E:[libfs_mgr] Couldn't create verity device!
E: Failed setting up dirty target
[omc-sysconfig-permission] fail to mount /system as rwE:[libfs_mgr]Error creating device mapping: Device or resource busy
E:[libfs_mgr] Couldn't create verity device!
E: Failed setting up dirty target
[omc-permission-permission] fail to mount /system as rwE:[libfs_mgr]Error creating device mapping: Device or resource busy
E:[libfs_mgr] Couldn't create verity device!
E: Failed setting up dirty target
[omc-res-permission] fail to mount /system as rwE:[libfs_mgr]Error creating device mapping: Device or resource busy
E:[libfs_mgr] Couldn't create verity device!
E: Failed setting up dirty target
[hwr_symlink] fail to mount /system as rw
I'm having the same and exact problem as in this video with same brand device S7e https://youtu.be/l8-ccufk4Q0 the man could save the device by installing TWRP because frp was off. I can't do the same because I got frp on
I used to play with a whole Frp Remover Tools but nothing helped or worked, and also tried some cracked boxes but unfortunately they seem just like interfaces and didn't work as well
If I ended with frp lock turned successfully off then everything will be easy, installing TWRP then flashing through it no_verity_encryption will solve the issue and the device will boot the system successfully, I need to turn it off, if anyone has a solution please help!
TheDevelopper said:
Hi everyone! Help! Need help! As titled, i have almost tried everything, frp lock is enabled i can't acces to recovery menu and i'm unable to flash TWRP recovery or boot into normal recovery, frp lock blocked everything, i can just access to download mode
Please, I need some help with my SM-G9350 Hong-Kong Galaxy S7 edge on Binary 4
I got custom binary TWRP recovery/boot blocked by frp lock when the device was working fine running custom rom, and then I flashed stock firmware via Odin and all was just fine and Odin succeed pass, but when installing system updates in recovery it was up to 32% then erasing and then it should boot up system, but it didn't it keeps rebooting to recovery with no options at all, just showing the android guy with no command below and then when I hard it to enter in recovery menu it shows a black screen with some lines that says couldn't open recovery cause unknown and no such file directory, and device is busy, and keep doing the same thing, I did same and flashed again with latest firmware but same thing happened, and then I tried to flash TWRP in order to flash a custom rom to boot up system, but Odin fails and says in download mode custom binary recovery blocked by frp lock, known that my device's bootloader is already unlocked and I flashed before this a whole of stuff, now, I can just access to download mode, otherwise I can't do anything else even no adb , there is no a combination file for the Hong-Kong variant G9350ZH, there is only for the Open-China variant G9350ZC which is not combatible with the device, even there are no adb enabled files, if someone has a solution for this, please kindly take care of this problem?
No menu in stock recovery, it's just saying:
#fait to open recovery_cause(No such file directory)#
#Reboot Recovery Cause is [UNKNOWN]#
No Support SINGLE=SKU
File-Based OTA
Supported API: 3
# MANUAL MODE v1.0.0#
E: [libfs_mgr]Blob verification failed :255
E: Failed setting up dirty target
E:[libfs_mgr] Error creating device mapping: Device or resource busy
E:[libfs_mgr] Couldn't create verity device!
E: Failed setting up dirty target
[omc-app-link] fail to mount /system as rwE:[libfs_mgr]Error creating device mapping: Device or resource busy
E:[libfs_mgr] Couldn't create verity device!
E: Failed setting up dirty target
[omc-permission] fail to mount /system as rwE:[libfs_mgr]Error creating device mapping: Device or resource busy
E:[libfs_mgr] Couldn't create verity device!
E: Failed setting up dirty target
[omc-sysconfig-permission] fail to mount /system as rwE:[libfs_mgr]Error creating device mapping: Device or resource busy
E:[libfs_mgr] Couldn't create verity device!
E: Failed setting up dirty target
[omc-permission-permission] fail to mount /system as rwE:[libfs_mgr]Error creating device mapping: Device or resource busy
E:[libfs_mgr] Couldn't create verity device!
E: Failed setting up dirty target
[omc-res-permission] fail to mount /system as rwE:[libfs_mgr]Error creating device mapping: Device or resource busy
E:[libfs_mgr] Couldn't create verity device!
E: Failed setting up dirty target
[hwr_symlink] fail to mount /system as rw
Click to expand...
Click to collapse
This isn't good.... Unfortunately I can't help with this matter. I bricked my s7 and ended up exactly like this. I have not been able to recover it. So I gave up. Sorry to be the bearer of bad news.
What happens when you Odin your full firmware package?
Sent from my Pixel 2 XL using Tapatalk
klabit87 said:
This isn't good.... Unfortunately I can't help with this matter. I bricked my s7 and ended up exactly like this. I have not been able to recover it. So I gave up. Sorry to be the bearer of bad news.
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
Thank you man, yea, you're right cause we tried almost everything but unfortunately can't recover it too :/
klabit87 said:
[/HIDE]
This isn't good.... Unfortunately I can't help with this matter. I bricked my s7 and ended up exactly like this. I have not been able to recover it. So I gave up. Sorry to be the bearer of bad news.
What happens when you Odin your full firmware package?
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
Odin success passed the firmware's packages without problems, and it is the right one @klabit87, actually, there is a chance to recover the phone, I have found a video on YouTube having the same and exact problem as me with same brand device S7e, the man could save the device by installing TWRP because frp was off, I can't do the same because I got frp on https://youtu.be/l8-ccufk4Q0
TheDevelopper said:
Odin success passed the firmware's packages without problems, and it is the right one @klabit87, actually, there is a chance to recover the phone, I have found a video on YouTube having the same and exact problem as me with same brand device S7e, the man could save the device by installing TWRP because frp was off, I can't do the same because I got frp on https://youtu.be/l8-ccufk4Q0
Click to expand...
Click to collapse
I think there are ways around frp though... I could be wrong though.
Sent from my Pixel 2 XL using Tapatalk
klabit87 said:
I think there are ways around frp though... I could be wrong though.
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
If only it can be turned off, I'll flash TWRP
TheDevelopper said:
If only it can be turned off, I'll flash TWRP
Click to expand...
Click to collapse
I wonder if you could use a custom kernel with dm-verity removed altogether. You could Odin it. No need for twrp. What firmware version is currently installed? I will compile it for you if you want to try it. Maybe try verity will get you to a point where you could remove frp while booted. Is your bootloader still unlocked? As in OEM unlock I mean.
Sent from my Pixel 2 XL using Tapatalk
q
klabit87 said:
I wonder if you could use a custom kernel with dm-verity removed altogether. You could Odin it. No need for twrp. What firmware version is currently installed? I will compile it for you if you want to try it. Maybe try verity will get you to a point where you could remove frp while booted. Is your bootloader still unlocked? As in OEM unlock I mean.
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
When tried to flash TWRP, it says custom binary recovery block by frp lock
And when tried to flash a custom boot that I took from a custom ROM and I Tared it, it says custom binary boot blocked by frp lock, I don't know if frp is related to OEM unlock or not and I don't know why it failed to Odin the boot that I took, the current firmware is CSC1 ..link for appropriated boot.img https://desktop.firmware.mobi/device:454/firmware:19931 if the device will read it as a custom one I don't think it will bypass it so, I would not disturb u if actually the phone will refuse it
But if crom service still off that means the bootloader is unlocked, once running for the first time on the device no need to use it anymore and the bootloader will be unlocked, but I don't know if OEM is enabled and it says in download mode secure download enabled
TheDevelopper said:
qWhen tried to flash TWRP, it says custom binary recovery block by frp lock
And when tried to flash a custom boot that I took from a custom ROM and I Tared it, it says custom binary boot blocked by frp lock, I don't know if frp is related to OEM unlock or not and I don't know why it failed to Odin the boot that I took, the current firmware is CSC1 ..link for appropriated boot.img https://desktop.firmware.mobi/device:454/firmware:19931 if the device will read it as a custom one I don't think it will bypass it so, I would not disturb u if actually the phone will refuse it
But if crom service still off that means the bootloader is unlocked, once running for the first time on the device no need to use it anymore and the bootloader will be unlocked, but I don't know if OEM is enabled and it says in download mode secure download enabled
Click to expand...
Click to collapse
Ah ok. You're right it won't flash then. Sounding like a qcom CDMA tool might help. I've seen a couple that allow you to remove frp but I believe it requires entering qshusb mode. But it seems like options just get more and more slim now
Sent from my Pixel 2 XL using Tapatalk
klabit87 said:
Ah ok. You're right it won't flash then. Sounding like a qcom CDMA tool might help. I've seen a couple that allow you to remove frp but I believe it requires entering qshusb mode. But it seems like options just get more and more slim now
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
Yes, playing around a right tool can remove it, searching and testing ..
Edit: @klabit87, all the tools failed
I have same model and same problem. Did you find any solution?
hi, do you have any update? I have the same problem and the same model too
Do anyone still need help in fixing this issue?
I would like you to join me in this experiment to fix your device.
how we start it ?
bawsobb said:
how we start it ?
Click to expand...
Click to collapse
Please PM me then we will first try to fix it and then post a tutorial here on XDA.