I've rooted my phone a dozen times, flashed TWRP and CWM before via recovery and Odin. Yesterday EVERY aplication started to give me a "Unfortunately, xxxx stopped working" and my phone would enter the system.
I flashed a new rom (5.0 N900XXUEBOA6) and since then, can't root my device.
If i try to use Odin, i have the "Nand write fail" error, if i try the recovery "E: failed to verify whole-file signature" "E: signature verification failed"
I don't think that a factory reset would help my problem, therefore, would you guys have any insight on what seems to be the problem?
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
Can anyone verify this will fix the dm-verity error in recovery on stock SM-935P?
Hello guys, i am trying to fix a bricked S8, i am able to boot into Download Mode and Recovery mode (wiped everything there).
I've already flashed Oreo and Pie Roms but the device wont boot.
When i boot into recovery mode i get this message:
Fail to open recovery_cause ( no such file or directory)
[...]
E: unknown volume for path [/odm]
E: unknown volume for path [/vendor]
dm-verity verification failed.
and stuff like "firmware info was not valid"...
Can anyone help? Don't want to root it at this moment, because the phone has warranty. If i can't fix it by myself i will send it to Samsung
Backstory:
Received the message "Custom binary blocked by FRP lock" when restarting my phone. I had a custom ROM installed so this was probably why, but I had flashed no-verity-opt-encrypt previously so I don't know why I randomly got this message.
Tried to flash the latest Android 8.0.0 stock firmware from sammobile, successfully flashed through Odin but when the phone boots it keeps looping into recovery, followed by "No command".
When I try to access the recovery settings by pressing power+up it comes with:
fail to open recovery_cause(No such file or directory)#
Reboot Recovery Cause is [UNKNOWN]# No Support SINGLE-SKU
Along with a bunch of lines saying failed to mount /system and dm-verity failed.
I've tried flashing many different stock ROMs but only the factory binary combination ROM is able to boot up. Therefore, I cannot turn off FRP lock. I am struggling to find out why, even though Odin successfully flashed the whole stock BL, AP, CP and CSC, the recovery cannot be opened.
Any ideas would be greatly appreciated.
Edit: Managed to fix it through a YouTube video by Mr.Lee
Try downgrading to nougat or marshmallow. That should remove FRP.
Sent from my SM-G935FD using Tapatalk
I've tried but I cannot find any marshmallow/nougat version which does not result in a SW REV CHECK FAIL error, my kernel only accepts Oreo or higher it seems.