[Samsung Galaxy S7 Questions and Answers] ukero:
[Problem solved] If anybody faces this kind of problem please notice it is not the problem of Nand-erase but DRK error and flashing with .pit file won't fix your problem. Just go to this discord group, https://discord.gg/Z4UZheJ [permanent] and ask for #Augustin. He will solve your problem 100%. He did for me. Full working network + rooted.

---------------------------------------------------------------------------------------------------

Hello, I was trying to update my s7 edge (SM-G935FD) with Oreo 8.0 from Nougat 7.0 with a custom firmware from sammobile.com.

The used file is: sammobile.com/firmwares/galaxy-s7-edge/SM-G935FD/BNG/download/G935FXXS3ERHD/236500/

But when flashing with Odin I accidentally selected "Nand Erase" option. After the operation completed my phone tried to boot up, showed installing updates, then tried to boot again and now permanently stuck on "SAMSUNG Galaxy S7 edge POWERED BY android".

Still, I can access "download mode" by using "Power + down + home" button and "android recovery" by using "Power + up + home" button.

While loading android recovery screen it shows, "Installing update..." then "Error" with an icon of android eyes crossed.

In my recovery menu, these lines are shown:

#fail to open recovery_cause(No such file or directory)#

#Reboot Recovery Cause is [UNKNOWN]#

No Support SINGLE-SKU

File-Based OTA

Supported API : 3

E: [libfs_mgr]Blob verification failed :255

E: Failed setting up dirty target

dm-verity verification failed...

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 flashed with this same firmware to no avail. I have also tired "Wipe data / Factory reset" and "Wipe cache partition". Nothing worked.

Now, other people who have tired this firmware faced the same problem for #fail to open recovery_cause

But, in my case, as bold lines indicates, this is may be due to using "Nand Erase" in Odin.

I do have :

Nougat 7.0 firmware for my device [Please notice that its baseband is U2 - so I can't downgrade bootloader from S3 to U2 hence can't flash with Nougat]

.pit file for my device [not sure about this one - I actually need a valid pit file from the above firmware, others don't seem to work.]

I have tried Z3box / octopus / smart switch samsung software to recognize my device, but they always reply with "Card not found". My Windows treats my device as unrecognized in this situation.

Please help me fix this issue. I just have bought this phone - second hand. :(

-----------------------------------

Update - I tried to use stock recovery files to flash with TPRW stock recovery. After I did that It started the tprw recovery and I installled two files

1. twrp-3.1.0-0

2.SR3-superuser

It completed and when I selected to reboot my phone, it just won't turn on anymore. I guess it is due to my partition is all messed up. I forced it to start up using my charger cable and plugging it to charging. Using "Download mode" then I tried to uninstall this TPRW and flashed only "AP" with "G935FXXU2ERD5" with odin as I was unable to find any stock recovery for "G935FXXS3ERHD".

Now, I am stuck with U2 bootloader whereas I need S3 bootloader. My phone still doesn't turn on normally. I have to plug it in charging port / USB cable to pc, then it goes straight up to "Android Recovery" and Now shows this:

File-Based OTA

Supported API : 3

E: [libfs_mgr]Blob verification failed :255

E: Failed setting up dirty target

dm-verity verification failed...

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

Successfully verified dmverity hash tree

E: Failed to clear BCB message: failed to find /misc partition

Please help me. I know I messed up, I shouldn't have used the TPRW recovery. Now I can't even flash with previous G935FXXS3ERHD or any U2 firmware. Please help me. I feel like crying. :(