I own a Samsung Galaxy S6 Edge 32gb, SM-G925F, got it on a contract with Orange France. The phone isn't fake, it is a genuine Samsung unit, I purchased it from an official Orange shop in France, it is network locked as I am on a contract. I rooted it with Ping Pong method, rom was supported and root was successful, knox was not tripped. As I gained access to root, I went and deleted just some bloatware, absolutely nothing critical, and I need to stress on that, from /system/app and system/priv-app. I then rebooted only to see that the phone went into a bootloop. I then went into recovery, wiped cache, that didn't help. I then wiped user data/reset the phone from recovery, no joy after this either. Further more I noticed that in recovery, at the bottom, "dm-verity verification failed..." is written down in yellow. The only way I could revive the phone was by flashing the stock rom again via Odin 3.10. So basically, while ping pong root works just fine, something else prevents it from being useful, as the phone does not like anything at all removed from its system files. Hopefully, all of this makes some sense and I will get some helpful advice here. Apologies if me posting this here breaks any of the forum rules, but I did post the same issue on the ping pong root post and I had no replies basically and also there was no resolution that I could see presented on the other "dm verity verification failed..." posts. So, many thanks in advance indeed for any helpful advice some of you bright minds out there might have for this.
and you flashed correct firmware..?
carionix said:
I own a Samsung Galaxy S6 Edge 32gb, SM-G925F, got it on a contract with Orange France. The phone isn't fake, it is a genuine Samsung unit, I purchased it from an official Orange shop in France, it is network locked as I am on a contract. I rooted it with Ping Pong method, rom was supported and root was successful, knox was not tripped. As I gained access to root, I went and deleted just some bloatware, absolutely nothing critical, and I neestress on that, from /system/app and system/priv-app. I then rebooted only to see that the phone went into a bootloop. I then went into recovery, wiped cache, that didn't help. I then wiped user data/reset the phone from recovery, no joy after this either. Further more I noticed that in recovery, at the bottom, "dm-verity verification failed..." is written down in yellow. The only way I could revive the phone was by flashing the stock rom again via Odin 3.10. So basically, while ping pong root works just fine, something else prevents it from being useful, as the phone does not like anything at all removed from its system files. Hopefully, all of this makes some sense and I will get some helpful advice here. Apologies if me posting this here breaks any of the forum rules, but I did post the same issue on the ping pong root post and I had no replies basically and also there was no resolution that I could see presented on the other "dm verity verification failed..." posts. So, many thanks in advance indeed for any helpful advice some of you bright minds out there might have for this.
Click to expand...
Click to collapse
seems like some of the stuff you got rid of was critical to the os.
I has the same issue as yours. At first, I used the debloater tool and removed all apps listed here: http://forum.xda-developers.com/galaxy-s6/general/safe-to-debloat-s6-threads-t3090383. That caused the bootloops and dm-verity verification fail for me. I then noticed that when I used the tool, not all apps actually get removed even thought I instructed it to. So I used esf file explorer, mounted the system as r/w and then used its system app uninstaller to remove all the apps mentioned in the above thread. Its worked great for me. I think it has to do with some knox apps being left over when I used the first method.
tell me more about flashing stock rom...
hi so for short i have crashed my samsung s6 edge. firstly rooted it with kingroot it was all good. then modified build.prop and after reboot the phone is stuck in boot loop with the same "dm-verity verification failed". no help from factory restore so i suppose i would need to flash my stock rom? but i don't know how to get one.
thanks in advance
rank4 said:
hi so for short i have crashed my samsung s6 edge. firstly rooted it with kingroot it was all good. then modified build.prop and after reboot the phone is stuck in boot loop with the same "dm-verity verification failed". no help from factory restore so i suppose i would need to flash my stock rom? but i don't know how to get one.
thanks in advance
Click to expand...
Click to collapse
try: http://www.sammobile.com/firmwares/
sorry for double post
ok so i found out what is firmware and now i need to find out my SCS or PDA.
is there any way of finding this without working phone?
i know model: SM-G925F SAMSUNG, YATELEY, GU46 6GG. UK
IMEI:359521/06/392799/2 and S/N...?
how can i pick right firmware?
they don't seem to have the sm-g925a for att s6 edge. Does anyone have, or does a rev 3 or 4 version exist in the wild? been looking for 2 days. older versions will not flash, odin fails on AP and BL flashes.
http://click.xda-developers.com/api...amsung Galaxy S6 Edge | XDA Forums&txt=HERE.
found an android firmware for 5.1.1 att stock rom to repair corrupted imei issues.
I have a phone again, yay
Hello everyone
I have found a way to fix dm-verity and DRK issues and it works like official, meaning no errors in stock recovery and OTA works with Official firmware, the problem is related to corrupted/deleted 3 files on /efs partition. I have tested it on SM-N910C so I guess it works on other Exynos variants, perhaps even on snapdragon if the partition layout is similar? Kies won't restore DRK or dm-verity check because it doesn't write to EFS. I can fix yours if someone is interested via Team Viewer, you will need the following:
1. PM contact me for Skype ID
2. Stock rom, rooted (any root method)
3. Adb debugging enabled and drivers installed (Kies or SmartSwitch)
After repair you can enter your stock recovery and confirm there is no DRK/dm-verity red letters error.
Regards,
magix01
Hello magix01
Hello magix01,
Could you kindly please help me?
I have SM-G920F and i have the same issue with it.
Skype ID: adryan_289
phone # : 0040724031461.
I'm scared because I can no longer use my phone. I have teamviwer,drivers, mic and everything that is needed.
Thank you.
magix01 said:
Hello everyone
I have found a way to fix dm-verity and DRK issues and it works like official, meaning no errors in stock recovery and OTA works with Official firmware, the problem is related to corrupted/deleted 3 files on /efs partition. I have tested it on SM-N910C so I guess it works on other Exynos variants, perhaps even on snapdragon if the partition layout is similar? Kies won't restore DRK or dm-verity check because it doesn't write to EFS. I can fix yours if someone is interested via Team Viewer, you will need the following:
1. PM contact me for Skype ID
2. Stock rom, rooted (any root method)
3. Adb debugging enabled and drivers installed (Kies or SmartSwitch)
After repair you can enter your stock recovery and confirm there is no DRK/dm-verity red letters error.
Regards,
magix01
Click to expand...
Click to collapse
magix01 said:
Hello everyone
I have found a way to fix dm-verity and DRK issues and it works like official, meaning no errors in stock recovery and OTA works with Official firmware, the problem is related to corrupted/deleted 3 files on /efs partition. I have tested it on SM-N910C so I guess it works on other Exynos variants, perhaps even on snapdragon if the partition layout is similar? Kies won't restore DRK or dm-verity check because it doesn't write to EFS. I can fix yours if someone is interested via Team Viewer, you will need the following:
1. PM contact me for Skype ID
2. Stock rom, rooted (any root method)
3. Adb debugging enabled and drivers installed (Kies or SmartSwitch)
After repair you can enter your stock recovery and confirm there is no DRK/dm-verity red letters error.
Regards,
magix01
Click to expand...
Click to collapse
Skype is nicolas.allaire
Number 1-450-712-9727
I am looking for help to bypass dm verity on my samsung galaxy s6 5.1.1 **920W8 (canada)
i have the same issue , plz help
skype id : doctor.ayan_isb
suhaibahmad said:
i have the same issue , plz help
skype id : doctor.ayan_isb
Click to expand...
Click to collapse
do you used what'sup?
anwr said:
do you used what'sup?
Click to expand...
Click to collapse
yes please send me message 00923452105231 or send me yours
Hey you all, i'm new on note 3 verizon. Previously i was on note 3 exynos International.
First thing i did was upgraded to android 5 OF1, then rooting, unlock bootloader, and twrp recovery.
For you that want to download in good speed & resumable link, this one is the best. Have a try. And have a happy upgrade
https://www.androidfilehost.com/?fid=24438995911977192
xcal_tau said:
Hey you all, i'm new on note 3 verizon. Previously i was on note 3 exynos International.
First thing i did was upgraded to android 5 OF1, then rooting, unlock bootloader, and twrp recovery.
For you that want to download in good speed & resumable link, this one is the best. Have a try. And have a happy upgrade
https://www.androidfilehost.com/?fid=24438995911977192
Click to expand...
Click to collapse
You are a Minor God. I've been to 35 sites and all fake/dangerous. You rock
Been trying to root, unlock bootloader and install twrp for 2 days solid. Tried several methods with no luck.
I got the phone rooted following this: https://www.youtube.com/watch?v=6x6NUquJl6Y
Using an older version of the Arabic Tool. Confirmes with RootChecker Basic and SuperSU. Could not get twrp installed. Get the Verizon warning. Tried his method but got hung up on the ADB pushing and the final unlock would not work.
I also tried this way: https://wiki.lineageos.org/devices/hltetmo/install
Same... could not get the bootloader undone. I apparently have a CID starting with 11 instead of 15, which is stated in many of the tutorials such as: https://forum.xda-developers.com/ve...guide-ob6-of1-root-bootloader-unlock-t3439010
Does anyone have a good tutorial for my Note 3 Verizon running OF1 ?
Thank you in advance. Sid
I am surprised no one has answered you since February. Hope you have already found a solution by now. If not there is actually a post on this thread that explains quite well how to unlock the bootloader. Here are the steps you may take:
"Originally Posted by jrkruse
I made this for the S5. I modded it with your unlock binary. All it requires is you to answer yes in the samsung unlock binary
I dont have a note 3 so let me know.
Edit: You must have busybox installed
1. Install SamsungUnlockerN3.apk
2. Grant SU access
3. Click On Install SamBootloader Unlocker
4. Grant SU access
5. Type Yes Hit enter wait for device to power off
6. Should be unlocked"
It works. Just follow the steps carefully.
Hi, I am a newbie to rooting and I need some help to unroot my phone. I have a working Samsung Note 5 N920PVPS3DQK1 rooted with Magisk and TWRP following the tutorial on HighOnAndroid's Root Galaxy Note 5 Website (Simple Search should show this)
Unfortunately I seem to come across many issues with this root and as Magisk seems outdated I want to unroot my phone back to stock firmware.
I've got odin downloaded, usb drivers for Note 5 installed, but I cant seem to find the exact stock firmware for my device on sammobile, which gives me options for DQF1 or DQH1. My question is does it matter if I dont choose the exact firmware. And if anyone is familiar with unrooting please reply!
Running Android 7.0
Unroot N920p
go to android file host. Download the factory firmware, unzip and install in odin. Download 3DQC5 and it will factory update about 5 times to 3DQL1 the latest patch.
https : // androidfilehost. com / ?w= search &s =n 920p
cybaphone said:
Hi, I am a newbie to rooting and I need some help to unroot my phone. I have a working Samsung Note 5 N920PVPS3DQK1 rooted with Magisk and TWRP following the tutorial on HighOnAndroid's Root Galaxy Note 5 Website (Simple Search should show this)
Unfortunately I seem to come across many issues with this root and as Magisk seems outdated I want to unroot my phone back to stock firmware.
I've got odin downloaded, usb drivers for Note 5 installed, but I cant seem to find the exact stock firmware for my device on sammobile, which gives me options for DQF1 or DQH1. My question is does it matter if I dont choose the exact firmware. And if anyone is familiar with unrooting please reply!
Running Android 7.0
Click to expand...
Click to collapse
top speed01 said:
go to android file host. Download the factory firmware, unzip and install in odin. Download 3DQC5 and it will factory update about 5 times to 3DQL1 the latest patch.
https : // androidfilehost. com / ?w= search &s =n 920p
Click to expand...
Click to collapse
Super sorry for the late reply, is there any chance you can leave me a step by step instruction with a couple more links just so I dont damage my phone haha thank you!
Background:
So I first suceesfully rooted my device (Samsung S7 SM-G930W8) with Odin, no-verify, and superSU.
I then find out about magisk and decide that I rather use it. (This way I could still use certain apps while rooted)
I did a full unroot and installed TWRP (following multiple guides/tutorials until I found the solution.)
But, I ran into issues...
Problems:
I can no longer enable OEM unlocking in my developer options whether I'm rooted or unrooted
I can't install Magisk as I'm getting "Error 1" and I cannot locate boot.img file. I've searched everywhere and the closest thing I found was boot.ph (it too did not work to resolve error 1.)
Any advice to get a fresh start on this? Or solve these problems? I can be more specific or give more information if required.
Thanks in advance!
ScoobDoob69 said:
Background:
So I first suceesfully rooted my device (Samsung S7 SM-G930W8) with Odin, no-verify, and superSU.
I then find out about magisk and decide that I rather use it. (This way I could still use certain apps while rooted)
I did a full unroot and installed TWRP (following multiple guides/tutorials until I found the solution.)
But, I ran into issues...
Problems:
I can no longer enable OEM unlocking in my developer options whether I'm rooted or unrooted
I can't install Magisk as I'm getting "Error 1" and I cannot locate boot.img file. I've searched everywhere and the closest thing I found was boot.ph (it too did not work to resolve error 1.)
Any advice to get a fresh start on this? Or solve these problems? I can be more specific or give more information if required.
Thanks in advance!
Click to expand...
Click to collapse
UPDATE:
I thought I'd include what my Download Mode says in the event it is helpful:
ODIN MODE
DOWNLOAD SPEED: FAST
PRODUCT NAME: SM-G930W8
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
FRP LOCK: OFF
Secure Download : Enabled
WARRANTY VOID: 1 (0X0500)
RP SWREV: B:7 K:4 S:5
Also, a guy on reddit offered to help, but I wasn't sure whether to trust him as he wanted to use teamviewer (I've heard things about vulnerabilities in RATs) so that kind of sketched me out on whether or not to trust him. But, he did ask if I had a GSPN login, which I do not... Is that needed to fix this or can I fix this with the use of Odin or TWRP?
There may be a chance that in 7 days I could enable OEM unlocking again. But, trying to trick my phones date & time (a method for bypassing RRM/KG locks) did not work.
Thanks in advance to anyone that may reply!
I'm still going to continue researching and will update with any changes :good:
ScoobDoob69 said:
UPDATE:
I thought I'd include what my Download Mode says in the event it is helpful:
ODIN MODE
DOWNLOAD SPEED: FAST
PRODUCT NAME: SM-G930W8
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
FRP LOCK: OFF
Secure Download : Enabled
WARRANTY VOID: 1 (0X0500)
RP SWREV: B:7 K:4 S:5
Also, a guy on reddit offered to help, but I wasn't sure whether to trust him as he wanted to use teamviewer (I've heard things about vulnerabilities in RATs) so that kind of sketched me out on whether or not to trust him. But, he did ask if I had a GSPN login, which I do not... Is that needed to fix this or can I fix this with the use of Odin or TWRP?
There may be a chance that in 7 days I could enable OEM unlocking again. But, trying to trick my phones date & time (a method for bypassing RRM/KG locks) did not work.
Thanks in advance to anyone that may reply!
I'm still going to continue researching and will update with any changes :good:
Click to expand...
Click to collapse
I was told recently that if one has TWRP installed they need not to have OEM unlocking enabled.
Yesterday I attempted to reinstall the stock firmware for my phone, but Odin froze every time. I tried three seperate version of Odin, including the latest version.
I might try again on a different computer and with a different usb cable... we'll see what happens :crying:
I am trying to root my old Galaxy Alpha, but I could not see or make OEM Unlock shown in Developer options. I tried everything suggested from Youtube and googling, but no success.
Would anyone help me out?
My phone is Samsung Galaxy Alpha (SM-G850F) on Android 5.0.2, baseband version G850FXXU1COI3
From what I remember, there is no such option, and you don't need to unlock anything to root that phone. Flash CF-Auto-Root-slte-sltexx-smg850f file using option AP in odin, that's it. Good luck mate.