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
Related
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
I have a Samsung Galaxy Note 3 (SM-N9005) flashed in Cyanogenmod ages ago. I'd like to reflash it with a new more recent ROM*as right now in CyanogenMod phone is more or less in a bootloop (most of time rebooting just few seconds/minutes after having finished the boot).
Unhappy I'm unable to find out which recovery was installed. I tried to keep physical Vol+ or Vol- butoon pushed while booting but it makes nothing. At boot I just get briefly displayed:
HTML:
Kernel is not SEandroid enforcing
Set Warranty bit: kernel
Is it safe to flash it with TWRP considering it as still a fresh device with original rom ? or danger ?
Thanks
You are booting to download mode try recovery mode.
Vol + Home button and power button
Vol- Home button +power button
As it does not have original firmware .
I would flash latest stock rom through Odin then flash required TWRP.
JJEgan said:
You are booting to download mode try recovery mode.
Vol + Home button and power button
Vol- Home button +power button
Click to expand...
Click to collapse
Thanks a lot, was not sure shortcut to use So I could access the recovery mode !
JJEgan said:
As it does not have original firmware .
I would flash latest stock rom through Odin then flash required TWRP.
Click to expand...
Click to collapse
Well it had at first but as Samsung very quickly stopped any updates I had switched it to CyanogenMod. I have succeeded to install on it the latest TWRP: 2.6.3.7 but each time I try to flash a ROM*(tried with two different ROm just to be sure)*I get the same errors in TWRP. For info files to flash on the SD*Card.
Code:
Updating partition details....
E:Unable to mount '/usbstorage'
Installing '/external_sd/lineage-16.0-20181010-
Checking for MD5*file...
Skipping MD5 check: no MD5*file found
Warning: No file_contexts
E3004: This package is for device: hlte, hltespr
E: unknown command [log]
E:Error executing updater binary in zip '/exter
Error flashing zip '/external_sd/lineage-16.0-2
Updating partition details...
E:Unable to mount '/usbstorage'
I double-checked on original sticker for manufacturer on device and it's well labelled as SM-N9005 so it's the HTLE version no ?
Update: I have tested with a ROM with Android 7.1.2 in it and install in twrp is going fine including gapps but at reboot it get stuck on Samsung Galaxy Note 3 and that's it and it's indicated at top of screen in yellow: Set Warranty bit: kernel
Not sure what's the problem there ?
Thanks for help,
Vincèn
and that's it and it's indicated at top of screen in yellow: Set Warranty bit: kernel
Correct unless its all stock kernel rom and recovery .
:Error executing updater binary in zip '/exter
Error flashing zip
Zip faulty or flashing tool wrong version
JJEgan said:
:Error executing updater binary in zip '/exter
Error flashing zip
Zip faulty or flashing tool wrong version
Click to expand...
Click to collapse
Well in fact the problem was the bootloader that needed update first to accept android so recent
Thanks for help
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
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