I have SM-G925F with DRK problem, after ODIN upgrade of 6.0.1 and 7.0 stuck in boot loop on recovery mode (dm-verity verification failed/need to check drk first).
I found solution only for 6.0.1 with custom kernel and the phone is working perfectly.
(drive.google.com/file/d/0B7MNcHK68wHZaDdqRUY4c0xCM00/view)
Does anyone has a solution for Nougat 7.0 SM-G925F etc Custom Kernel 7.0 Fix, Skip/Patch DRK, Fix Error DRK - bootloop recovery!, FIx Check Dm-fail .....
hey man can you help me??? i need the file to fix (dm-verity verification failed/need to check drk first) that you have use on 6.0.1 plss i rreally need it thanks
Ben Z said:
hey man can you help me??? i need the file to fix (dm-verity verification failed/need to check drk first) that you have use on 6.0.1 plss i rreally need it thanks
Click to expand...
Click to collapse
Sure, here is Kernel_G925F_fix_DRK_error.tar
vesel79 said:
Shure, here is Kernel_G925F_fix_DRK_error.tar
Click to expand...
Click to collapse
can you tell me how to use this? I have the exact same error
crukx said:
can you tell me how to use this? I have the exact same error
Click to expand...
Click to collapse
Flash the zip through TWRP
crukx said:
can you tell me how to use this? I have the exact same error
Click to expand...
Click to collapse
For 6.0.1 - Put your S6 Edge in download mode, flash with Odin with Stock FW, then if you have bootloop and error like "dm-verity verification failed / need to check drk first" put again in download mode, again flash with Odin Kernel_G925F_fix_DRK_error.tar which will skip / bypass "dm-verity verification failed / need to check drk first"
For 7.0 - Flash stock 7.0 with Odin, instal TWRP for correct model and Instal Magisk which will root and skip "dm-verity verification failed / need to check drk first"
I hope will help.
I never installed any custom Rom. just rooted it for Linux purposes. now I didn't get ota updates hence uprooted using super su. so can I directly flash the file with Odin?
crukx said:
I never installed any custom Rom. just rooted it for Linux purposes. now I didn't get ota updates hence uprooted using super su. so can I directly flash the file with Odin?
Click to expand...
Click to collapse
Yes Odin, It's work for stock FW (tested), but after flashing Kernel_G925F_fix_DRK_error.tar the phone will be rooted without superuser and you won't receive OTA updates anymore.
I inatalled android 7.0 on my g925f and soon after he process, it asked me to install the DRK. How can I bypass his problem?
Florencio Mamhica said:
I inatalled android 7.0 on my g925f and soon after he process, it asked me to install the DRK. How can I bypass his problem?
Click to expand...
Click to collapse
Sorry, I don't know, so far for 7.0 i was not found any patch .. fix ... bypass for DRK problem.
Worked like a Charm
vesel79 said:
For 6.0.1 - Put your S6 Edge in download mode, flash with Odin with Stock FW, then if you have bootloop and error like "dm-verity verification failed / need to check drk first" put again in download mode, again flash with Odin Kernel_G925F_fix_DRK_error.tar which will skip / bypass "dm-verity verification failed / need to check drk first"
For 7.0 - Flash stock 7.0 with Odin, instal TWRP for correct model and Instal Magisk which will root and skip "dm-verity verification failed / need to check drk first"
I hope will help.
Click to expand...
Click to collapse
Thank you sooo much, even though i still have imei issues, this helped me bypass drk issues for 7.0. Im not giving up now.
Katinc said:
Thank you sooo much, even though i still have imei issues, this helped me bypass drk issues for 7.0. Im not giving up now.
Click to expand...
Click to collapse
To fix imei issues you need to find the combination firmware, this can fix imei
Years ago my dad bought an used s6 edge, the phone suddenly died and the mainboard was replaced (and the imei of the ""new"" mainboard had to be repaired ).
I'm currently using that s6 edge and i wanted to install a custom rom or installing the stock Nougat update (currently using 6.0.1) my question.... If I upgrade or install custom rom (or custom kernel).... will my "fixed imei" dissapear?
Thanks for your answers!
**Note: It seems that the phone was rooted when the imei was fixed
vesel79 said:
Sorry, I don't know, so far for 7.0 i was not found any patch .. fix ... bypass for DRK problem.
Click to expand...
Click to collapse
Hi dear!
Im facing problems to install CM12 on my Note 2 N7100.
It takes long to logon and somethimes if it happens to install, brings up information like: Android is upgrading... Starting apps. This process takes long, something about 1hr and then it opens full of difficulties. There are a lot of services not available.
How can I solve it?
If you have a good Rom, may you please send me the link!
Related
Hi!
Phone finds the update, downloads the 600+ mb then restarts for installation then the Update Failed thingy comes up. And after this, while searching for updates it says " You have the latest version". Went to recovery more, reset the phone, then the same thing happens.
Any suggestions?
Or do I just download the 5.1.1 firmware and flash it with Odin?
Any help would be appreciated!
Halfbaked156 said:
Hi!
Phone finds the update, downloads the 600+ mb then restarts for installation then the Update Failed thingy comes up. And after this, while searching for updates it says " You have the latest version". Went to recovery more, reset the phone, then the same thing happens.
Any suggestions?
Or do I just download the 5.1.1 firmware and flash it with Odin?
Any help would be appreciated!
Click to expand...
Click to collapse
Download the latest stock firmware, and flash it with Odin.
Uzair40 said:
Download the latest stock firmware, and flash it with Odin.
Click to expand...
Click to collapse
Thanks for the reply. I guess that's the only alternative before I root. But there's this message in recovery mode "dm-verity verification failed....Need to check DRK first"
No idea what this is, have googled and it is not related to the problems shown on the web. Phone is not rooted, still official firmware.
So, is it safe to flash the latest firmware through Odin or will it brick my phone?
Halfbaked156 said:
Thanks for the reply. I guess that's the only alternative before I root. But there's this message in recovery mode "dm-verity verification failed....Need to check DRK first"
No idea what this is, have googled and it is not related to the problems shown on the web. Phone is not rooted, still official firmware.
So, is it safe to flash the latest firmware through Odin or will it brick my phone?
Click to expand...
Click to collapse
It's safe.
Uzair40 said:
It's safe.
Click to expand...
Click to collapse
Another obstacle. Odin or Win 10 doesn't recognize my phone in Download Mode. Have tried everything that I know of.....maybe it is win 10?
Halfbaked156 said:
Another obstacle. Odin or Win 10 doesn't recognize my phone in Download Mode. Have tried everything that I know of.....maybe it is win 10?
Click to expand...
Click to collapse
Got it working. Flashed the file..now it's stuck on the Samsung Galaxy S6 edge powered by Android screen.
Have tried factory reset, wipe cache, re-flashed....still stuck on it. Any help please?
Hello. Unfortunately i bricked my phone. Here is the story.
I root the phone with cf auto root. Install recovery, but i forget to make EFS backup. Then install Bootloader and Modem PF1 for G925F - TWRP from carhd thread and then the rom itself. After that i lose mobile network. I can't use my sim card, no IMEI, baseband unknown. Since i don't have EFS backup i tried to flash every stock firmware that i can and nothing fixed the efs. Everytime when i flash stock firmware and reboot the device after flash, the phone boot in stock recovery and it says: "dm-verity verification failed...need to check drk first . The only way to boot the phone is to install twrp and install no-verity-opt-encrypt-2.1 but still no sim detection and no IMEI.. Smart Switch is not working for my phone. How can i fix it?
Lately I've seen so many bricked s6 due to not backing up efs. The most important thing is always make backup.
I had the same error and problems as you and all i did was flash stock to fix it. Try to flash a stock with a newer bl and modem. If stock doesn't fix it im not sure of another way
Sent from my SM-G925F using Tapatalk
From where to get the newest botloader and modem?
FakeSmile said:
From where to get the newest botloader and modem?
Click to expand...
Click to collapse
Theres a thread on here somewhere.
Try to flash a new firmware build. Like 4xxxx
FakeSmile said:
From where to get the newest botloader and modem?
Click to expand...
Click to collapse
This guy had exactly the same as you and flashing stock fixed it. Read the posts and flash the fw and pit from there.
http://forum.xda-developers.com/galaxy-s6-edge/help/bricked-samsung-s6-g925f-t3457433/page2
Hi everyone, please help me with this problem. My phone is a J5 Sm J500m, with 6.0.1 andrioid and root with Odin and CF Autoroot.
The phone was working great (root and system all working smoothly) until I F***ed Up by deactivate in the menu de feature "OEM UNLOCK" and restarted the phone and i got a message saying "Custom binary blocked by FRP".
I have tried to re-root with odin and of course i cant do it beacause of the FRP block, my question is: how can i bypass this block because the system works well i just cant fix this issue.
Thanks to everyone
tryser said:
Hi everyone, please help me with this problem. My phone is a J5 Sm J500m, with 6.0.1 andrioid and root with Odin and CF Autoroot.
The phone was working great (root and system all working smoothly) until I F***ed Up by deactivate in the menu de feature "OEM UNLOCK" and restarted the phone and i got a message saying "Custom binary blocked by FRP".
I have tried to re-root with odin and of course i cant do it beacause of the FRP block, my question is: how can i bypass this block because the system works well i just cant fix this issue.
Thanks to everyone
Click to expand...
Click to collapse
Go to SamMobile download the firmware for your device and flash it with Odin.
After that just check OEM unlocking and re root.
PalmCentro said:
Go to SamMobile download the firmware for your device and flash it with Odin.
After that just check OEM unlocking and re root.
Click to expand...
Click to collapse
Hello there, i follow your directions, went to sammobile and download the firmware (choose de correct country) and i flash it with Odin,everithing went as it should and got the "PASS" on odin, but at the restart of the phone it got stuck in he samsung logo forever, i restarted the phone but it keeps getting stuck in the samsung logo.
¿What should i do? thank you for your help men
tryser said:
Hello there, i follow your directions, went to sammobile and download the firmware (choose de correct country) and i flash it with Odin,everithing went as it should and got the "PASS" on odin, but at the restart of the phone it got stuck in he samsung logo forever, i restarted the phone but it keeps getting stuck in the samsung logo.
¿What should i do? thank you for your help men
Click to expand...
Click to collapse
I would say you should boot into recovery and wipe cache, if it doesn't help make a full wipe.
It can sometimes take time till it boots....
PalmCentro said:
I would say you should boot into recovery and wipe cache, if it doesn't help make a full wipe.
It can sometimes take time till it boots....
Click to expand...
Click to collapse
I did everything you said and it work! thank you so mucho.
ONE last question, the firmware is running andrioid 5.1.1, so i tried to update the the software. when i click, on "software update" it says "registering device" and then it pops out processing failed.
I teliminated the data of "software update" from application manager but i still cant update the software.
thanks a LOT men :good:
tryser said:
I did everything you said and it work! thank you so mucho.
ONE last question, the firmware is running andrioid 5.1.1, so i tried to update the the software. when i click, on "software update" it says "registering device" and then it pops out processing failed.
I teliminated the data of "software update" from application manager but i still cant update the software.
Click to expand...
Click to collapse
You can manually do it via sammobile or via Samsung Kies.
PalmCentro said:
You can manually do it via sammobile or via Samsung Kies.
Click to expand...
Click to collapse
I fix everything! Thanks men:good::good::good::good::good:
PROBLEM SOLVED, THANK YOU !
Hi.
I just recently rooted my Honor 5X (KIW-UL00 , it's the chinese model)
I then tried installing a custom ROM, the LineageOS. Problem being that I was stuck in a weird BootLoot. When I rebooted the system, it showed me the usual Honor page for like 4-5 seconds, then the loading screen for LineageOS. After like 10 seconds, the animation stopped, the thing crashed and my phone restarted to the Honor page, then Lineage, then crash ... So I booted my phone with TWRP, tried Wiping the Cache and System and started over again with installing Lineage. The same thing happened. I then tried with 3 other custom ROM'S and the same thing happened. I don't know what I did wrong, I am wiping my cache and Dalvic each time, but I can't figure out what to do.
I'm looking for someone who could help me fix this. I am thinking about flashing the stock ROM, I just don't know how to do it, because it seems different than the custom ROM'S
PS: I'm looking for a kick fix, because I kinda really need my phone xD
Thank you!
Ok so, quick update, I got rid of TWRP by flashing the stock recovery over it. I tried to follow this:
https://forum.xda-developers.com/honor-5x/help/honor-5x-kiw-ul00-boot-loop-t3449554
(DigiGoon's first answer) but it told me that the installation failed.
So in short, my phone is actually in a endless bootloob, trying to boot no ROM, because the're none.
what's the stock system version you were running before you flashed the custom rom? B418 is the latest non VoLTE firmware.
It was Marshmallow 6.0.1... I found my mistake
We can't downgrade using the SD card method and I was trying to install 5.0
Now I need to find the stock version for the KIW-UL00 6.0.1
you can downgrade with the help of hisuite by huawei.
if your stock system was above B422, you can use this patch to stop the bootloop,
just flash the file in twrp after you flash the rom. https://mega.nz/#!tK51gDRL!S9oYLBTeFDbN0hOCzt5jQ5DYECObFC08YMr-Kml6scc
Problem is that I dont have any ROM or custom recovery running on my phone. I can only acess the bootloader, the eRecovery (that for some magical reasons, doesn't work for me) and the SD card installer, that also doesnt work because the only thing I can find is a UPDATE.APP that is on 5.0, when my phone was on 6.0.1, which doesn't work.
HiSuite doesn't even connect and I don't know what VolTE is, can you explain?
Can someone can help me in finding the Stock ROM for KIW-UL00 (the chinese version of Honor 5x) on android 6.0.1. I can find those for every country except china...
EDIT, I was able to get back on TWRP, so I can add files in my phone
haubudam, i freaking love you dude, you saved me
Thank you SOOOOOOO much
haubudam said:
you can downgrade with the help of hisuite by huawei.
if your stock system was above B422, you can use this patch to stop the bootloop,
just flash the file in twrp after you flash the rom. https://mega.nz/#!tK51gDRL!S9oYLBTeFDbN0hOCzt5jQ5DYECObFC08YMr-Kml6scc
Click to expand...
Click to collapse
Thanks man. I was also stuck up in the same problem for a day and flashing BaPatch.zip solved the issue.
Uvneshkumar said:
Thanks man. I was also stuck up in the same problem for a day and flashing BaPatch.zip solved the issue.
Click to expand...
Click to collapse
Can u send me the screenshot of files in zip?
gopinaidu77 said:
Can u send me the screenshot of files in zip?
Click to expand...
Click to collapse
https://mega.nz/#!tK51gDRL!S9oYLBTeFDbN0hOCzt5jQ5DYECObFC08YMr-Kml6scc
Uvneshkumar said:
https://mega.nz/#!tK51gDRL!S9oYLBTeFDbN0hOCzt5jQ5DYECObFC08YMr-Kml6scc
Click to expand...
Click to collapse
Thank you
haubudam said:
you can downgrade with the help of hisuite by huawei.
if your stock system was above B422, you can use this patch to stop the bootloop,
just flash the file in twrp after you flash the rom.
Click to expand...
Click to collapse
My version of the firmware is B245. Your patch did not help me, there is no newer version of firmware for KISH-UL00 than 245. What should I do?
Sodomit666 said:
My version of the firmware is B245. Your patch did not help me, there is no newer version of firmware for KISH-UL00 than 245. What should I do?
Click to expand...
Click to collapse
It was necessary to update the stock firmware to the latest version and then flash custom.
I tried to root my Samsung Galaxy S6 Edge, installed TWRP & tried to install SuperSU 2.79 and it got stuck on creating image, so I rebooted my phone and it didn't boot.
At this point i could only access TWRP and Donwload mode, I got worried and decided to flash stock recovery via ODIN but I think i forgot to uncheck auto-reboot box (Don't know if this step could cause the problem but I think they are related), and I know it's trying to open recovery mode because when I flash TWRP again, some red letters appear on the top-left corner of the screen, same as when I opened TWRP custom recovery, so at the moment I can only open Download mode.
The things I've tried:
ADB reboot recovery: It won't recognise the device anymore
Flash Stock Firmware/Recovery: After sboot.bin it fails (I have the Firmware for my specific model and region)
Also, I'm new to the forums stuff so forgive me if I do something wrong
I hope someone could help me,as I've searched all over the internet and found close to nothing about this thread
Afganito said:
I tried to root my Samsung Galaxy S6 Edge, installed TWRP & tried to install SuperSU 2.79 and it got stuck on creating image, so I rebooted my phone and it didn't boot.
At this point i could only access TWRP and Donwload mode, I got worried and decided to flash stock recovery via ODIN but I think i forgot to uncheck auto-reboot box (Don't know if this step could cause the problem but I think they are related), and I know it's trying to open recovery mode because when I flash TWRP again, some red letters appear on the top-left corner of the screen, same as when I opened TWRP custom recovery, so at the moment I can only open Download mode.
The things I've tried:
ADB reboot recovery: It won't recognise the device anymore
Flash Stock Firmware/Recovery: After sboot.bin it fails (I have the Firmware for my specific model and region)
Also, I'm new to the forums stuff so forgive me if I do something wrong
I hope someone could help me,as I've searched all over the internet and found close to nothing about this thread
Click to expand...
Click to collapse
Flash stock firmware it will work.
The reason it fails at sboot.bin is because your flashing a firmware with an older bootloader than you currently have.
Flash a newer/newest firmware and it will work.
callumbr1 said:
Flash stock firmware it will work.
The reason it fails at sboot.bin is because your flashing a firmware with an older bootloader than you currently have.
Flash a newer/newest firmware and it will work.
Click to expand...
Click to collapse
I tried with Nougat 7.0, still have the same problem, it keeps failing at sboot.bin
Afganito said:
I tried with Nougat 7.0, still have the same problem, it keeps failing at sboot.bin
Click to expand...
Click to collapse
Needs to be a newer firmware with a newer BL. Your still trying to downgrade BL.
callumbr1 said:
Needs to be a newer firmware with a newer BL. Your still trying to downgrade BL.
Click to expand...
Click to collapse
When I last checked my Android versión was 7.0 and I think that was the last update the galaxy s6 had, but if you can tell me where can I get a newer firmware that would be great, also thanks for the help you have given me until now.
Afganito said:
When I last checked my Android versión was 7.0 and I think that was the last update the galaxy s6 had, but if you can tell me where can I get a newer firmware that would be great, also thanks for the help you have given me until now.
Click to expand...
Click to collapse
So the BL is like G925FXXU-S4.... G925FXXU-S5.... flash one which is higher.
https://updato.com/firmware-archive-select-model?record=FE9175C4876911E89F15FA163EE8F90B
Try this one.
Sorry for late reply