Hi guys I own an S8, SM-G950F. The previous software I was on was Android 8 U2 (can't remember exact one). I flashed the new DBT Android 9 software via ODIN (using CSC, not home CSC). However the phone stays in the "Powered by Android" screen and does not go any further.
I can go into the Samsung recovery mode and have tried wiping both the cache and data/factory reset but this seems to make no difference. As an alternative I have tried flashing the Android 8 files (with bootloader U4), which is successful in ODIN but shows "No command" when booting.
USB debugging was also turned on before applying this update.
Other info:
FRP Lock: Off
OEM Lock: Off
RP SWREV: B:4 K:3 S:3
Any ideas what I could do?
Thanks.
Try Flash Same Firmware Reigon You have own in prev Version
MA7MOD_GSM said:
Try Flash Same Firmware Reigon You have own in prev Version
Click to expand...
Click to collapse
Thanks for your reply. I have tried this although it does not work as the boot loader version is now at V4, whereas the previous software I had was V2. I have tried flashing other Android 8 software with boot loader V4 but it goes into the “No command” state where I can’t access the recovery, only download mode is available.
hs102 said:
Thanks for your reply. I have tried this although it does not work as the boot loader version is now at V4, whereas the previous software I had was V2. I have tried flashing other Android 8 software with boot loader V4 but it goes into the “No command” state where I can’t access the recovery, only download mode is available.
Click to expand...
Click to collapse
Also a little more info. When the ODIN flash is successful it restarts to the "Install Software Update" blue screen. It reaches 32% but then begins erasing.
The following error message is also present in the recovery:
#fail to open recovery_cause (No such file or directory) #
#report recovery cause is [unknown] #
Support single-sku
File-Based OTA
Supported API: 3
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-tree / firmware / android / compatible': No such file or directory
I think you Flash worng Firmware send download mode photo
MA7MOD_GSM said:
I think you Flash worng Firmware send download mode photo
Click to expand...
Click to collapse
Firmware was fine not sure what the issue was.
Got around it by flashing latest TWRP and no verity and it loaded successfully.
Thanks
same as me. loaded twrp and no ver opt and magestic but thats all cool but all i want is official with no root or anything. why wont my damn phone boot without all the crap. this method will not allow any kind of ota. same issue when i flas pie via odin except it even worse. cant get to boot
hs102 said:
Firmware was fine not sure what the issue was.
Got around it by flashing latest TWRP and no verity and it loaded successfully.
Thanks
Click to expand...
Click to collapse
after TWRP your fone boot working ... because I have the same issue Samsung warranty center told me to replace the motherboard
hs102 said:
Also a little more info. When the ODIN flash is successful it restarts to the "Install Software Update" blue screen. It reaches 32% but then begins erasing.
The following error message is also present in the recovery:
#fail to open recovery_cause (No such file or directory) #
#report recovery cause is [unknown] #
Support single-sku
File-Based OTA
Supported API: 3
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-tree / firmware / android / compatible': No such file or directory
Click to expand...
Click to collapse
I also am seeing the same message in recovery mode. Also in odin mode(download mode) there is extra lines of text. Although in saying this the s8 boots and seems to function as per usual. The storage used from stock firmware is 12.4 GB... Is this normal??
All I am wanting to know is "is this normal for the exynos galaxy s8 running One UI, android 9" ?
or Did I Download a dodgy Rom?
Kdom81 said:
I also am seeing the same message in recovery mode. Also in odin mode(download mode) there is extra lines of text. Although in saying this the s8 boots and seems to function as per usual. The storage used from stock firmware is 12.4 GB... Is this normal??
All I am wanting to know is "is this normal for the exynos galaxy s8 running One UI, android 9" ?
or Did I Download a dodgy Rom?
Click to expand...
Click to collapse
Same here.
https://forum.xda-developers.com/galaxy-note-8/help/weird-message-recovery-e-libfsmgr-t3936625
Did you arrive to any conclusion?
Hey I have the same problem as well... I can't flash twrp because I have oem locked and I can't boot into my because it keeps restarting and getting stuck at some point, and the recovery is saying:
#fail to open recovery_cause (No such file or directory) #
#report recovery cause is [unknown] #
Support single-sku
File-Based OTA
Supported API: 3
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-tree / firmware / android / compatible': No such file or directory
How can I fix this?
Is there any update on this? I have the same issue as post #11 on a Samsung A8 sm-a530w.
Any help would be much appreciated.
I've got the same issue on a G950F.
I bought new (sealed, G950FXXU5DSFB), and tried to flash combination file G950FXXU5ASF1 . This did not work. (no boot).
So I flashed what I thought was stock rom matching CSC.
(AP_G950FXXU5DSFB_CL16290088_QB24491245_REV00_user_low_ship_meta_OS9.tar )
The phone boots and operates fine, except for the same message you guys are getting in recovery, as well as a message about no OTA updates.
---------- Post added at 05:54 PM ---------- Previous post was at 05:54 PM ----------
I've got the same issue on a G950F.
I bought new (sealed, G950FXXU5DSFB), and tried to flash combination file G950FXXU5ASF1 . This did not work. (no boot).
So I flashed what I thought was stock rom matching CSC.
(AP_G950FXXU5DSFB_CL16290088_QB24491245_REV00_user_low_ship_meta_OS9.tar )
The phone boots and operates fine, except for the same message you guys are getting in recovery, as well as a message about no OTA updates.
Any news about this? for me I bought used Galaxy Note 8 it was Korean N950N Converted to N950FD, I wanted to Install TWRP and ROOT but I kept getting Failed to Mount Preload error in TWRP and read smwhere its because of messed up partition so not knowing what official firmware it came with I flashed the carrier firmware which phone's IMEI info got me also it was closest to old converted FD baseband now I bypassed this nonsense via twrp but there is not even proper root to install any other custom ROM help me solve this or kindly help me find solution to Failed to mount /preload in twrp
techyrock said:
Any news about this? for me I bought used Galaxy Note 8 it was Korean N950N Converted to N950FD, I wanted to Install TWRP and ROOT but I kept getting Failed to Mount Preload error in TWRP and read smwhere its because of messed up partition so not knowing what official firmware it came with I flashed the carrier firmware which phone's IMEI info got me also it was closest to old converted FD baseband now I bypassed this nonsense via twrp but there is not even proper root to install any other custom ROM help me solve this or kindly help me find solution to Failed to mount /preload in twrp
Click to expand...
Click to collapse
Same problem but my phone s8 g950n korean, Failed to mount /preload, heres what i did to solve my problem:
- MOUNT everything in TWRP Without SDCard
- WIPE everything but NOT SDCard
- FORMAT DATA
- FACTORY RESET
- Reboot Recovery
after that no more Failed to mount /preload in twrp
- Flash Custom ROM
- Rooted my device by Flashing Magisk v20.4
nmx87 said:
Same problem but my phone s8 g950n korean, Failed to mount /preload, heres what i did to solve my problem:
- MOUNT everything in TWRP Without SDCard
- WIPE everything but NOT SDCard
- FORMAT DATA
- FACTORY RESET
- Reboot Recovery
after that no more Failed to mount /preload in twrp
- Flash Custom ROM
- Rooted my device by Flashing Magisk v20.4
Click to expand...
Click to collapse
There was some very simple fix for this mate I don't recall what worked for me, ever since I have change several phones I am on S10 5G right now, so It was just once a faced it and now I dont even remember lol what was it that fixed it for me, I think maybe different TWRP or I flashed Stock Rom the full rom with CSC and everything, just remember don't touch the partitions it was a simple fix of some sorts
hs102 said:
Also a little more info. When the ODIN flash is successful it restarts to the "Install Software Update" blue screen. It reaches 32% but then begins erasing.
The following error message is also present in the recovery:
#fail to open recovery_cause (No such file or directory) #
#report recovery cause is [unknown] #
Support single-sku
File-Based OTA
Supported API: 3
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-tree / firmware / android / compatible': No such file or directory
Click to expand...
Click to collapse
Hello Everyone!
I have the same problem with Galaxy Note 8 / SM-N950F
Is there a solution for this??
Please need help, please please.
Thank you
I have a samsung S8 that stayed in the samsung logo and restarts, reinstall the operating system but I get the following error:
#fail to open recovery_cause(No such file or directory)#
#reboot Recovery Cause is [ UNKNOWN]#
Support SINGLE-SKU
File-Based OTA
Supported API:3
E:unknown volume fot path [ /odm]
E:unknown volume fot path [ /vendor]
dm-verity verification failed...
E:[libfs_mgr]is_dt_compatible(): firmware info was not valid : ´/porc/device-tre/firmaware/android/compatible´: No such file or directory
did anyone have this problem? How could you fix it?
thanks U very much
ApoloDesign said:
I have a samsung S8 that stayed in the samsung logo and restarts, reinstall the operating system but I get the following error:
#fail to open recovery_cause(No such file or directory)#
#reboot Recovery Cause is [ UNKNOWN]#
Support SINGLE-SKU
File-Based OTA
Supported API:3
E:unknown volume fot path [ /odm]
E:unknown volume fot path [ /vendor]
dm-verity verification failed...
E:[libfs_mgr]is_dt_compatible(): firmware info was not valid : ´/porc/device-tre/firmaware/android/compatible´: No such file or directory
did anyone have this problem? How could you fix it?
thanks U very much
Click to expand...
Click to collapse
we need more info man. what firmware was it on before the crash (if that info is available) and what firmware did you flash before this error happened?
Youdoofus said:
we need more info man. what firmware was it on before the crash (if that info is available) and what firmware did you flash before this error happened?
Click to expand...
Click to collapse
I have same issues with my samsung s8
I got it from a customer said efs invalid argument and now iam flashed twrp and enter into terminal and used commands to mount the efs partition then it is mounted and now iam flashed the dm verity disabler and Rmm state bypass then reboot my device stuck in samsung logo and then i flashed exact stock firmware with u12 bootloader and now it stuck in boot logo when i enter into stock recovery it is showing dm verification failed
Odm/failed
Vendor/failed
E:libs_mgr is dt compatible
See attached files more info
Plz help i got stuck help me pls
well first i want to say hello, i will explain my problem how started i wipe efs from my phone via z3x box because I was trying to fix imei, baseband, and no service sim problems. I have an unknown and i'm failed the idea was stupid and i did a reboot and i faced some problems in frp has locked bootloader i think its text is red i downloaded firmware rom stock from sam mobile and did flash on odi, but I downloaded the last version and binary U2, this is the file name G570FXXS2CSH1_G570FOJV2CSI2_TUN then the phone turned on and entered me on the recovery mode and showed me " installing system update " and then the "Erasing" and then he restarted alone and it appeared after him "No Command" I pressed the volume up button and the button power so that I see what I'm wrong, I tried to find my combination binary u2 and i didn't find only binary u1 and i have frp lock ON so i can't install root or TWRP on my phone and also i could not to boot into the system so I searched on google and found a file named "SM-G570F U2 Android 8.0 FIX DRK - dm-verity Failed Frp ON RMM ON.tar"
I knew that this file would fix my problem is " E:[libfs_mgr] Couldn't create verity device!" I'm flash my phone and put this file in the place of BL and also put the AP file system which I think is 2 GB and when he succeeded in the flash process my phone did a restart and showed me the SAMSUNG logo and entered me to the system, but another problem appeared to me, that the touch does not work, I cannot press anything if I hold on the power button, and i'm see RESTART and SHUTDOWN appears to me, but I cannot even click on them. I thought that this problem is from the file that I flashed to the location of BL, perhaps, also I am unable to enter recovery mode unless I flash 4 files again but my question is there is another solution To fix my phone? I want it to come back :crying:
Question: did u download the firmware stock and the same model phone?
Answer: yes, i did
these errors are seen by me when i'm flash firmware stock and then enter me into recovery mode. alone:
BLOB 255 DM VERITY FAILED
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
WHAT SHOULD I DO?? TO GET BACK ON STOCK?
any admis's or moderator here change my topic to SAMSUNG J5 PRIME?, I did not see it
anyone? HELLO ?
liwahadri1 said:
anyone? HELLO ?
Click to expand...
Click to collapse
Try reflash stock, then TWRP if possible. Otherwise no hope, also stop spamming in your threads, no one will help you with this attitude. Try to maje the thread as short as possible cause no one will want to stay and read all this stuff.
NecromancerViper said:
Try reflash stock, then TWRP if possible. Otherwise no hope, also stop spamming in your threads, no one will help you with this attitude. Try to maje the thread as short as possible cause no one will want to stay and read all this stuff.
Click to expand...
Click to collapse
i have tried before and it will not work
also I did not spam because I saw the topic is dead
liwahadri1 said:
i have tried before and it will not work
also I did not spam because I saw the topic is dead
Click to expand...
Click to collapse
Then your phone is pretty much dead
NecromancerViper said:
Then your phone is pretty much dead
Click to expand...
Click to collapse
what about combination for binary u2?
btw if i flash only system.img on AP and BL file "SM-G570F U2 Android 8.0 FIX DRK - dm-verity Failed Frp ON RMM ON"
i can boot into android but touch not work my question is combination soon out for binary u2?
liwahadri1 said:
what about combination for binary u2?
btw if i flash only system.img on AP and BL file "SM-G570F U2 Android 8.0 FIX DRK - dm-verity Failed Frp ON RMM ON"
i can boot into android but touch not work my question is combination soon out for binary u2?
Click to expand...
Click to collapse
I dont own the phone so... I can't help you past this... sorry
Hello. I have problem with my SM-530F (2017). Lately, I've tried to flash TWRP in ODIN, but failed. Phone went in some sort in loop, where Samsung logo is visible, then everything is black, and Samsung logo again. I have installed new BL, AP, CP and CSC, but it didn't resolve that problem. In recovery there are lines with this messages:
#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]
dm-verity verification failed...
E:Failed to clear BCB message: failed to open /dev/block/platform/13540000.dwmmc0/by-name/MISC: No such file or directory
Is there any way to fix it?
Thanks in advance.
hi guys, I used odin since 2010 so I have some experience with it
but now after flashing the official firmware , then flashing TWRP
the phone is now stuck in recovery
#fail to open recovery_cause (No such file or directory) #
#report recovery cause is [unknown] #
Support single-SKU
File-Based OTA
Supported API: 3
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-tree
/firmware/android/compatible : no such file or directory"
it's either stuck in recovery mode
What I tried
fashing stock firmware
tried to install TWRP , fail ( only official binaries are allowed)
Any idea ?
Ba89ar said:
hi guys, I used odin since 2010 so I have some experience with it
but now after flashing the official firmware , then flashing TWRP
the phone is now stuck in recovery
#fail to open recovery_cause (No such file or directory) #
#report recovery cause is [unknown] #
Support single-SKU
File-Based OTA
Supported API: 3
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-tree
/firmware/android/compatible : no such file or directory"
it's either stuck in recovery mode
What I tried
fashing stock firmware
tried to install TWRP , fail ( only official binaries are allowed)
Any idea ?
Click to expand...
Click to collapse
Try to flash TWRP again. And stick to the installation instructions on post number 3 of this thread:
[RECOVERY][OFFICIAL] TWRP for Galaxy S8 and S8+ (Exynos)
Team Win Recovery Project 3.1.1 Exynos ONLY. In NO way it is compatible with Snapdragon variants including but not limited to American(U/A/T/P/V), Chinese(0/8/6), Hong Kong(0), Japanese(SC-*), Canadian(W) variants. #include...
forum.xda-developers.com