Hello,
i have a problem with my Samsung SM-T585. I have rooted it and i will go back to the original Software.
So i downloaded Odin and the newest Software from SamFirm.
I start the download mode and connect my phone to the pc.
Odin says added and i put the 4 files into Odin.
Start the process, all be fine.
The Tablet reboots and starts samsung recovery to erase and then comes a nother reboot.
The tablet is going back to recovery and then comes no command. when i push the power und volum up butten comes the follow window (text)
#fail to open recovery_cause(No such file or directory)#
#Reboot Recovery Cause is [UNKNOWN]#
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 map
ping: 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 m
apping: Device or resource busy
E:[libfs_mgr]Couldn't create verity device!
E:Failed setting up dirty target
[omc-sysconfig-permmission] fail to mount /system as rwE:[libfs_mgr]Error creatin
g device mapping: Device or resource busy
E:[libfs_mgr]Couldn't create verity device!
E:Failed setting up dirty target
[omc-permmission-permmission] fail to mount /system as rwE:[libfs_mgr]Error creat
ing device mapping: Device or resource busy
E:[libfs_mgr]Couldn't create verity device!
E:Failed setting up dirty target
[omc-res-permmission] fail to mount /system as rwE:[libfs_mgr]Error creating devi
ce 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
The tablet is then rebooting and the process starts again.
Can anyone help me to fix the problem? i won't be install twrp again the tablet shold be only run the original software.
Thanks for your help
Try This
Hi there,
Have you tried to download the correct region firmware and then flash it.
Kind Regards,
KIBS2173
T585rick said:
Hello,
i have a problem with my Samsung SM-T585. I have rooted it and i will go back to the original Software.
So i downloaded Odin and the newest Software from SamFirm.
I start the download mode and connect my phone to the pc.
Odin says added and i put the 4 files into Odin.
Start the process, all be fine.
The Tablet reboots and starts samsung recovery to erase and then comes a nother reboot.
The tablet is going back to recovery and then comes no command. when i push the power und volum up butten comes the follow window (text)
#fail to open recovery_cause(No such file or directory)#
#Reboot Recovery Cause is [UNKNOWN]#
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 map
ping: 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 m
apping: Device or resource busy
E:[libfs_mgr]Couldn't create verity device!
E:Failed setting up dirty target
[omc-sysconfig-permmission] fail to mount /system as rwE:[libfs_mgr]Error creatin
g device mapping: Device or resource busy
E:[libfs_mgr]Couldn't create verity device!
E:Failed setting up dirty target
[omc-permmission-permmission] fail to mount /system as rwE:[libfs_mgr]Error creat
ing device mapping: Device or resource busy
E:[libfs_mgr]Couldn't create verity device!
E:Failed setting up dirty target
[omc-res-permmission] fail to mount /system as rwE:[libfs_mgr]Error creating devi
ce 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
The tablet is then rebooting and the process starts again.
Can anyone help me to fix the problem? i won't be install twrp again the tablet shold be only run the original software.
Thanks for your help
Click to expand...
Click to collapse
KIBS2173 said:
Hi there,
Have you tried to download the correct region firmware and then flash it.
Kind Regards,
KIBS2173
Click to expand...
Click to collapse
Hi KIBS2173,
i have the region firmware from my country downloaded. But it fails all the time.
T585rick said:
Hi KIBS2173,
i have the region firmware from my country downloaded. But it fails all the time.
Click to expand...
Click to collapse
Now i tried the newest version from samfirm. The message is:
#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: unknown volume for path [/odm]
E: unknown volume for path [/vendor]
E: unknown volume for path [/odm]
E: unknown volume for path [/vendor]
Manual Mode v 1.0.0#
E:[libfs_mgr]Blob verification failed :255
E:Failed setting up dirty target
failed to mount '/system' (Bad file descriptor)
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 map
ping: 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 m
apping: Device or resource busy
E:[libfs_mgr]Couldn't create verity device!
E:Failed setting up dirty target
[omc-res-permmission] fail to mount /system as rwE:[libfs_mgr]Error creatin
g device mapping: Device or resource busy
E:[libfs_mgr]Couldn't create verity device!
E:Failed setting up dirty target
[omc-res-permmission] fail to mount /system as rwE:[libfs_mgr]Error creat
ing 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 hope everyone can tell me what to do.
Try This
T585rick said:
Now i tried the newest version from samfirm. The message is:
#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: unknown volume for path [/odm]
E: unknown volume for path [/vendor]
E: unknown volume for path [/odm]
E: unknown volume for path [/vendor]
Manual Mode v 1.0.0#
E:[libfs_mgr]Blob verification failed :255
E:Failed setting up dirty target
failed to mount '/system' (Bad file descriptor)
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 map
ping: 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 m
apping: Device or resource busy
E:[libfs_mgr]Couldn't create verity device!
E:Failed setting up dirty target
[omc-res-permmission] fail to mount /system as rwE:[libfs_mgr]Error creatin
g device mapping: Device or resource busy
E:[libfs_mgr]Couldn't create verity device!
E:Failed setting up dirty target
[omc-res-permmission] fail to mount /system as rwE:[libfs_mgr]Error creat
ing 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 hope everyone can tell me what to do.
Click to expand...
Click to collapse
Hi there,
are you able to flash a custom recovery. Just try to flash a custom recovery like twrp.
and then install a custom rom.
i think the flashed failed and causing the problem.
so far i think you are facing a soft brick.
if your still having problems use different versions of odin.
and plus reinstall any samsung usb drivers.
kind regards
KIBS2173
Related
My Z3 Compact tablet was restarting frequently, I did downgrade/change stock FTF but did not help, so I decided to check cm-12.1-20160123 rom. After I followed all their installation instructions, I get stuck at this error:
Code:
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/system at /system: invalid argument of /system failed: no such volume detected filesystem f2fs for /dev/block/platform/msm_sdcc.1/by-name/userdata
Can anyone help please?
hi friends i need a help
sorry for my bad english .
zenfone 2 laser ze550kl(z00ld)
bootloader is not unlocked
Not rooted
when i goto recovery mode gets error
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: failed to mount /cache(no such file or directory)
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
E: failed to mount /cache(no such file or directory)
E: Can't mount /cache/recovery/last_install
E: Can't open /cache/recovery/last_instal
E:Can´t open /dev/block/bootdevice/by-nme/misc
(permission denied)
E:failed to mount /cache (no such file r directory)
Try to apply update from sdcard stock firmware error
install / sdcard/ul z00l ww 21.40.122.1998user zip..
E:Can´t open /dev/block/bootdevice/by-nme/misc
(permission denied)
E:failed to mount /cache (no such file r directory)
E:failed to mount /cache
E:failed to set up expected mounts for install ; abroting
installation abroted.
try to unlock flashable unlock zip for ze550kl error
Failed (remote : cannot flash this partition in locked state)
asus flash tool error
can't open file _frp_request_server_log.txt (error 5 access is denied)
when i delete fastboot mode erase userdata gets error
erasing userdata FAILED (remote: failed to get pt size !!)
when i install twrp phone restarts every 3 seconds, its failed.
try to flash raw firmware phone goes to 9006 mode..
then i use mini partition and get back to 9008 mode .. and starts with qfil ..
what can i do ? how to unlock my bootloader and flash twrp i tried all methods but its not working
how to get my phone back to normal ! please help me someone stuck at boot logo
sunilkumarss said:
hi friends i need a help
sorry for my bad english .
zenfone 2 laser ze550kl(z00ld)
bootloader is not unlocked
Not rooted
when i goto recovery mode gets error
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: failed to mount /cache(no such file or directory)
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
E: failed to mount /cache(no such file or directory)
E: Can't mount /cache/recovery/last_install
E: Can't open /cache/recovery/last_instal
E:Can´t open /dev/block/bootdevice/by-nme/misc
(permission denied)
E:failed to mount /cache (no such file r directory)
Try to apply update from sdcard stock firmware error
install / sdcard/ul z00l ww 21.40.122.1998user zip..
E:Can´t open /dev/block/bootdevice/by-nme/misc
(permission denied)
E:failed to mount /cache (no such file r directory)
E:failed to mount /cache
E:failed to set up expected mounts for install ; abroting
installation abroted.
try to unlock flashable unlock zip for ze550kl error
Failed (remote : cannot flash this partition in locked state)
asus flash tool error
can't open file _frp_request_server_log.txt (error 5 access is denied)
when i delete fastboot mode erase userdata gets error
erasing userdata FAILED (remote: failed to get pt size !!)
when i install twrp phone restarts every 3 seconds, its failed.
try to flash raw firmware phone goes to 9006 mode..
then i use mini partition and get back to 9008 mode .. and starts with qfil ..
what can i do ? how to unlock my bootloader and flash twrp i tried all methods but its not working
how to get my phone back to normal ! please help me someone stuck at boot logo
Click to expand...
Click to collapse
Same problem brother....Tired Every possible way
Hello All,
I have a problem where TWRP is not able to mount /data, although the device still works without any other problems. It has happened when i upgrade the TWRP recovery from 3.2.1-0 to 3.2.1-1
This is preventing me to install Magis modules unfortunately.
I have a OOS Open BETA 1 for the Oneplus 5T.
Here's the log:
Code:
[COLOR="Red"]Could not mount /data and unable to find crypto footer.
Failed to mount '/data' (No such device)
Unable to recreate /data/media folder.[/COLOR]
Updating partition details...
[COLOR="red"]Failed to mount '/data' (No such device)
Failed to mount '/preload' (Invalid argument)[/COLOR]
...done
Full SELinux support is present.
Unfortunately I've updated my Samsung Galaxy S8(SM-G950F). Than tried to root it but not successfully. Therefore I need latest(2020.06.01) EFS file for G950FXXU9DTF1
Please, help me to find the file!
____________________________
Android Recover
Code:
[FONT="System"]#fail to open recovery_cause(No such file or directory)#
#Reboot Recovery Cause is [UNKNOWN]#
Support SINGLE-SKU
File-Based OTA
E: Failed to mount /efsñ Invalid argument
Supported API: 3
E:failed to mount /efs (Invalid argument)
E:unknown volume for path [/odm]
E:unknown volume for path [/vendor]
dm-verity verification failed…
E:[libfs_mgr]is_dt_compatible(): firmware info was not valid : ’/proc/device-
/Firmware/android/compatible’ : No such or directory[/FONT]
_____________________________
Thanks in advance
Best regards
FYI: /efs ( read: Encrypted File System ) is a partition, not a file
I already unrooted and setup custom os on a couple of Motorola G7 play phones. But on this one, I thought I would try a different way to install twrp permanently.
which was to boot into twrp, then "install recovery ramdisk" pointing it to the recovery.img that I know works correctly with this phone.
I got these messages....
I:Switching slots to flash ramdisk to both partitions
I:Setting active slot B
Updating partition details...
Iata backup size is 867MB, free: 14022MB.
I:checking for twrp app
I:Can't probe device /dev/block/bootdevice/by-name/vendor_b
Failed to mount '/vendor' (Invalid argument)
I:Actual block device: '/dev/block/bootdevice/by-name/vendor_b', current file system: 'ext4'
I:Can't probe device /dev/block/bootdevice/by-name/modem_b
Failed to mount '/firmware' (Invalid argument)
I:Actual block device: '/dev/block/bootdevice/by-name/modem_b', current file system: 'ext4'
I:Can't probe device /dev/block/bootdevice/by-name/dsp_b
Failed to mount '/dsp' (Invalid argument)
I:Actual block device: '/dev/block/bootdevice/by-name/dsp_b', current file system: 'ext4'
...done
Backing up Boot...
I:Reading '/dev/block/bootdevice/by-name/boot_b', writing '/tmp/repackorig//boot.emmc.win'
I:Restored default metadata for /tmp/repackorig//boot.emmc.win
I:Error unpacking /tmp/repackorig/boot.img, ret: 256!
Error unpacking image.
I:Set page: 'action_complete'
Iperation_end - status=1
At this point, I realized I didn't previously flash dtbo.img. I suspected if I reboot I would brick the phone. I decided to reboot to bootloader anyway. because to start flashing over the top of this seemed like a bad idea.
Which I in fact bricked the phone.
What should I have done at this point? Gone ahead and flashed dtbo from the PC while in twrp? flashed a copy of the boot.img (from my PC?). before I rebooted?
I actually have found NO info on why I am reflashing dtbo, or whats in these modified dtbo's, or how to tell I need to flash the dtbo. Or if it's even correct "before" commiting to unpacking/repacking the boot image.
And there are multiple links to different modified dtbo's and different instructions sometimes leave out no-verity-opt-encrypt.zip For the record I didn't do this no verity step on the last couple phones and worked fine.
What is the procedure to fix the boot before I reboot out of twrp. And how do I know I have a good copy of a modified dtbo
How can I tell I have (or not) already flashed dtbo?
So since this phone seems to have borked Slot B. Can I unbrick it somehow by going to Slot A? It does not respond to anymore to VolumeDown-Power button so it really bricked for good or not?
Sorry for all the questions, but I think this would save a ton of people wrecking phones.