Hi just update my G530H to lollipop via Odin and everything was fine and when I trie to wipe data this problem appears about E:unknown volume "/sbfs"
There is the log :
|<1 MANUAL MODE*
Appling Multi-CSC…
I Applied_the CSC-code : XEF
Successfully applied multi-CSC.
— Wiping cache…
Formatting /cache…
Cache wipe complete.
— Wiping data…
Formatting /data…
Formatting /cache…
Formatting /sbfs…
E:unknown"volume for path [/sbfs]
E:unknown volume "/sbfs"
Data wipe complete.
I don't know what wrong.
Anyone know it, tell me please.
::BUMP::
Really no one knows about this error?
In KitKat this error dont exist BUT in Lollipop appears on hard reset. I dont know if is an bug on Lollipop FW or what.
I already trie 5 different Lollipop Firmwares fron different countries and every single one give that error no matter if is OTA, KIES or ODIN.
I really appreciate any help or is something that dont affect at all the daily use of my phone.
e:unknown volume for path [/sbfs]
same problem need help
same probleme help plz
same problem on an Alpha G850M. No one knows how to solve this untill now ???????????
I get the same error message! And n one knows what it means?!
e: table length: 170
e: verify signature ...
e: signature verfication is successful.
--wiping data ..
Formatting / data
Formatting / cache
formatting / sbfs ..
e: unknown volume for path [/ sbfs]
e: unknwn volume "/ sbfs"
on marshmellow
got this error
no support single-sku
i try to flash cm12
msg appears
this pacage is for device: j53g; this device is j5lte.
E: Error executing updater binary in zip '/ xxxxxxxxxxx
i flashed all these firmwares
J500H_DS_XXU1AOFB_OXE1AOFB_v5.1.1_Repair_Firmware
J500HXXU1BPJ3_J500HOJV1BPJ2_LYS
J500HXXU1AOG4_OXE1AOG4_J500HXXU1AOG4
some one please tell me how can i solve this
Reflash the stock rom to get the phone back on
john-ammu said:
e: table length: 170
e: verify signature ...
e: signature verfication is successful.
--wiping data ..
Formatting / data
Formatting / cache
formatting / sbfs ..
e: unknown volume for path [/ sbfs]
e: unknwn volume "/ sbfs"
on marshmellow
got this error
no support single-sku
i try to flash cm12
msg appears
this pacage is for device: j53g; this device is j5lte.
E: Error executing updater binary in zip '/ xxxxxxxxxxx
i flashed all these firmwares
J500H_DS_XXU1AOFB_OXE1AOFB_v5.1.1_Repair_Firmware
J500HXXU1BPJ3_J500HOJV1BPJ2_LYS
J500HXXU1AOG4_OXE1AOG4_J500HXXU1AOG4
some one please tell me how can i solve this
Click to expand...
Click to collapse
Connect your phone to computer. Install Samsung Smart Switch on the computer and initiate a firnware reflash trough it. It is official samsung service so it will automatically download the latest official firmware for your device and after that it will flash it no matter what you have done to your phone as long as you can boot it into Download Mode.
Flash stock lollipop sock ROM form SamMobile . After flashing clear ur cache and factory reset . Your device will boot . Ignore the error . After dirty flash stock mm ROM and enjoy
flash failed - got SAMSUNG Logo stack
s10gopal said:
Flash stock lollipop sock ROM form SamMobile . After flashing clear ur cache and factory reset . Your device will boot . Ignore the error . After dirty flash stock mm ROM and enjoy
Click to expand...
Click to collapse
Need your held as download mode doesn't work after flashing with odin failed.
Phone (SM-J500FN) stacks in SAMSUNG Logo!
Hey guys ,
I accidentally done an Full format via TWPR before i could make a Backup of the EFS folder...
Obviously i dont have an IMEI now and cant use Mobile services ...
I Tryed Flashing the newest stock rom again and got the error:
SW REV. CHECK FAIL (BOOTLOADER) DEVICE:4 BINARY:3
so uhm ... that wont work at all
I saw some tutorials with an Combination Rom flash but i will still got the BL error and nothing happens..
Are there any ways to Recover my phone?
Could i use the EFS's files of my old A5 2016 SM-510F?
Hitaku said:
Hey guys ,
I accidentally done an Full format via TWPR before i could make a Backup of the EFS folder...
Obviously i dont have an IMEI now and cant use Mobile services ...
I Tryed Flashing the newest stock rom again and got the error:
SW REV. CHECK FAIL (BOOTLOADER) DEVICE:4 BINARY:3
so uhm ... that wont work at all
I saw some tutorials with an Combination Rom flash but i will still got the BL error and nothing happens..
Are there any ways to Recover my phone?
Could i use the EFS's files of my old A5 2016 SM-510F?
Click to expand...
Click to collapse
Device 4 Binary 3 means you are flashing older firmware than what is currently on your phone. You will need to get latest firmware with bootloader 4.
Bootloader version number is the 5th number from the right of the firmware name. The same error will happen if you use combination firmware as well.
spawnlives said:
Device 4 Binary 3 means you are flashing older firmware than what is currently on your phone. You will need to get latest firmware with bootloader 4.
Bootloader version number is the 5th number from the right of the firmware name. The same error will happen if you use combination firmware as well.
Click to expand...
Click to collapse
Hey
so the
G950FXXU4CRI5/G950FOXM4CRI5/G950FXXU4CRI1/G950FXXU4CRI5 firmware should technically work?
Hitaku said:
Hey
so the
G950FXXU4CRI5/G950FOXM4CRI5/G950FXXU4CRI1/G950FXXU4CRI5 firmware should technically work?
Click to expand...
Click to collapse
Yes it should as it is the latest firmware available.
Hitaku said:
Hey guys ,
I accidentally done an Full format via TWPR before i could make a Backup of the EFS folder...
Obviously i dont have an IMEI now and cant use Mobile services ...
I Tryed Flashing the newest stock rom again and got the error:
SW REV. CHECK FAIL (BOOTLOADER) DEVICE:4 BINARY:3
so uhm ... that wont work at all
I saw some tutorials with an Combination Rom flash but i will still got the BL error and nothing happens..
Are there any ways to Recover my phone?
Could i use the EFS's files of my old A5 2016 SM-510F?
Click to expand...
Click to collapse
Did you manage to fix the problem? I have an S7 with a deleted EFS partition and can't use mobile services either
sirs2k said:
Did you manage to fix the problem? I have an S7 with a deleted EFS partition and can't use mobile services either
Click to expand...
Click to collapse
Same.. i have an A520F/DS, deleted EFS, no mobile services and null imei..any ideas on how to solve this?
I have a problem sm-g950f- u12 saying fail to open recovery cause(no such fail 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 please anyone to help me
I have a problem sm-g950f- u12 saying fail to open recovery cause(no such fail 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 please anyone to help me
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
When i boot into stock android recovery it says cant load android system your data may be corrupt but when try factory data reset it doesnt fix anything and i see a error in bottom too it says
#reboot recovery cause is unknown#
e: libfs_mgr failed to mount /efs: invalid argument
e: failed to mount /.system invalid argument 5 times
#reason is enablefilecrypto_failed
and e: failed to mount /.system invalid argument again
Supported api: 3
You tried to install TWRP recovery?
Cengizhan55 said:
When i boot into stock android recovery it says cant load android system your data may be corrupt but when try factory data reset it doesnt fix anything and i see a error in bottom too it says
#reboot recovery cause is unknown#
e: libfs_mgr failed to mount /efs: invalid argument
e: failed to mount /.system invalid argument 5 times
#reason is enablefilecrypto_failed
and e: failed to mount /.system invalid argument again
Supported api: 3
Click to expand...
Click to collapse
Please install back stock rom using odin.
cmfCyangenModteam said:
You tried to install TWRP recovery?
Click to expand...
Click to collapse
my oem and bootloader locked somehow i guess the guests will changed it when im not in home
mvikrant97 said:
Please install back stock rom using odin.
Click to expand...
Click to collapse
i said im on stock android recovery in first message im on correct stock rom