Database Info

Samsung Galaxy S7 SM-G930F E: Failed to Mount /system (Invalid argument)

Help! I cannot use my phone because while updating to OERO it failed saying :
An error has occurred during update and you have to use emergency firmware recovery on smart switch PC software but smartswitch says it is unsupported device. I have access in download mode but cannot accomplish anything because;
1). Odin fails every time ( gets stuck while flashing system.img (AP)
2). My phone cannot find /system. I have tried restoring my phone to stock, but Odin fails.
The bottom of my recover screen says "dm-verity verification failed ... " And "E: failed to mount /system (Invalid argument)".
Any help or guidance is greatly appreciated.
Thanks.

Mr.Januzi said:
Help! I cannot use my phone because while updating to OERO it failed saying :
An error has occurred during update and you have to use emergency firmware recovery on smart switch PC software but smartswitch says it is unsupported device. I have access in download mode but cannot accomplish anything because;
1). Odin fails every time ( gets stuck while flashing system.img (AP)
2). My phone cannot find /system. I have tried restoring my phone to stock, but Odin fails.
The bottom of my recover screen says "dm-verity verification failed ... " And "E: failed to mount /system (Invalid argument)".
Any help or guidance is greatly appreciated.
Thanks.
Click to expand...
Click to collapse
May be encrypted. Did you installed any TWRP and custom ROM?

zSyntex said:
May be encrypted. Did you installed any TWRP and custom ROM?
Click to expand...
Click to collapse
not rooted, no custom recovery, but while updating to oreo, now in recovery it says system status : custom

Mr.Januzi said:
not rooted, no custom recovery, but while updating to oreo, now in recovery it says system status : custom
Click to expand...
Click to collapse
Are you using ODIN 3.13.1 ?

*Detection* said:
Are you using ODIN 3.13.1 ?
Click to expand...
Click to collapse
I am in swtizerland with CSC VFG and wanted to flash oreo from UK BTU. I flashed it via odin 3.13.1. and couldn't boot into system only into recovery in which i get the message :
No support SINGLE-SKU
Supported API: 3
Dm-verify error…
E:failed to mount /system (invalid argument)
I can see that in recovery I still have the firmware from switzerland G930FXXS2RC3 instead of UK G930FXXU2ERD5.
In download mode I can see Secure download: enabled and FRP lock : ON, I also remember that i didn't toggle the OEM unlock since flashing official firmware you don't need to be OEM unlocked.

This work for me:
Download BTU Oreo stock files.
Download Odin 3.13...
Change AP file format from *.md5 to *.tar
Flash only APxxx.tar file
Wait to reboot
Enjoy
Hope it work. Good luck!
I was on Oreo BTU Stock and try rooting flashing tarp and when boot on TWRP there was lost data partition. I wasn't able to flash anything via twrp and Odin just reboot the phone. Then I did those steps and and boot normally and everything ok, no data loss.

j0shyc0re said:
This work for me:
Download BTU Oreo stock files.
Download Odin 3.13...
Change AP file format from *.md5 to *.tar
Flash only APxxx.tar file
Wait to reboot
Enjoy
Hope it work. Good
Click to expand...
Click to collapse
Nope, it isn't working :/ I only renamed the AP file .md5 to .tar is that correct ?

Mr.Januzi said:
Nope, it isn't working :/ I only renamed the AP file .md5 to .tar is that correct ?
Click to expand...
Click to collapse
That's what i did.

have the same issue hear odin keeps failing flash and in recovery it states the same as you did you come across a fix ??

[email protected] said:
have the same issue hear odin keeps failing flash and in recovery it states the same as you did you come across a fix ??
Click to expand...
Click to collapse
Hello bro.
I did not come around any fix for that, I had to take it to a repair shop and they fixed it for 40 euros.
While searching on internetil I found some guys who said that they could repair it via Teamviewer from their shop but also had to be paid 35 dollars.
After a while, I found a program which is called ; Octopus Box Samsung which seems to repair NVM, write firmware on samsung phones. I haven't tried it but I'm sure it would work if you do a little research on it and watching tutorials on how to use the app.
Best of luck, and let me know if you come to a fix.
Edit: apparently you need this program and a Samsung Micro UART cable with 530k resistor in irder to work.

Mr.Januzi said:
Hello bro.
I did not come around any fix for that, I had to take it to a repair shop and they fixed it for 40 euros.
While searching on internetil I found some guys who said that they could repair it via Teamviewer from their shop but also had to be paid 35 dollars.
After a while, I found a program which is called ; Octopus Box Samsung which seems to repair NVM, write firmware on samsung phones. I haven't tried it but I'm sure it would work if you do a little research on it and watching tutorials on how to use the app.
Best of luck, and let me know if you come to a fix.
Edit: apparently you need this program and a Samsung Micro UART cable with 530k resistor in irder to work.
Click to expand...
Click to collapse
i see its tricky situation that i have never faced and need to fix my phone.. what is NVM ? i do not have Octopus Box but i do have Z3X box but and uart cables dont see that option at anywhere what is NVM what does it do and can you tell me where u seen this post ?

[email protected] said:
have the same issue hear odin keeps failing flash and in recovery it states the same as you did you come across a fix ??
Click to expand...
Click to collapse
[email protected] said:
i see its tricky situation that i have never faced and need to fix my phone.. what is NVM ? i do not have Octopus Box but i do have Z3X box but and uart cables dont see that option at anywhere what is NVM what does it do and can you tell me where u seen this post ?
Click to expand...
Click to collapse
NVM is the memory of the phone on which your firmware operates. I never used the octopus box but I read for it on google.and watched som.youtube videos on which they repair NVM through the octopus box. I never heard about z3x box but I assume it does the same function.

Mr.Januzi said:
Help! I cannot use my phone because while updating to OERO it failed saying :
An error has occurred during update and you have to use emergency firmware recovery on smart switch PC software but smartswitch says it is unsupported device. I have access in download mode but cannot accomplish anything because;
1). Odin fails every time ( gets stuck while flashing system.img (AP)
2). My phone cannot find /system. I have tried restoring my phone to stock, but Odin fails.
The bottom of my recover screen says "dm-verity verification failed ... " And "E: failed to mount /system (Invalid argument)".
Any help or guidance is greatly appreciated.
Thanks.
Click to expand...
Click to collapse
bro did you fix your phone

Installing system update fail after Odin flash. Boot into recovery mode.

Hi,
My phone (S7) got into a boot loop for no apparent reason. I noticed it was a bit hot and it froze a couple of times so I rebooted it and after that it was stuck in a boot loop no matter what. I then tried "flashing" the latest firmware with Odin3 to fix it. Everything was fine in Odin but after the phone rebooted, it couldn't finish installing the patch... It showed an "error!' screen then booted into Android Recovery with these logs:
#fail to open recovery_cause(No such file or directory)#
#Reboot Recovery Cause is UNKNOWN
No Support SINGLE-SKU
File-Based OTA
E:failed to mount /efs (Invalid argument)
supported API: 3
E:failed to mount /efs (Invalid argument)
E:failed to mount /efs (Invalid argument)
dm-verity verification failed...
E:failed to clear BCB message: failed to fin /misc partition
Click to expand...
Click to collapse
At this point I'm not sure what I can do... I would really like to avoid a factory reset as I have a lot of data on my phone I would like to keep.
Thanks!

normsrayn said:
Hi,
My phone (S7) got into a boot loop for no apparent reason. I noticed it was a bit hot and it froze a couple of times so I rebooted it and after that it was stuck in a boot loop no matter what. I then tried "flashing" the latest firmware with Odin3 to fix it. Everything was fine in Odin but after the phone rebooted, it couldn't finish installing the patch... It showed an "error!' screen then booted into Android Recovery with these logs:
At this point I'm not sure what I can do... I would really like to avoid a factory reset as I have a lot of data on my phone I would like to keep.
Thanks!
Click to expand...
Click to collapse
Hello, this problem is very common for people that root their phones if you get drk error then there are 2 methods to solve this
Method one : easy
Just flash cf autoroot with odin download the file for your phone and flash it in ap
You may get stuck or get bootloops in splash screen or red errors just wait patiently until rom boots
Method 2 : for if you want no root (ota still impossible)
Flash twrp with odin, then download the no verity file
And move it to your phone, in twrp tap on install and select the file
https://build.nethunter.com/android-tools/no-verity-opt-encrypt/
Just download the latest version of the file (6.0)
Now wait until rom boots
-----------------------------------------------------------------------------------
Please donate and like if you think i deserved it,
If it didnt work you don't have to do it
Happy flashing and good luck
Dont forget to update me after following the steps

I'm a total newbie when it comes to phone flashing, I have a few questions. If I decide to use autoroot, is there a chance for a brick? What could go wrong? I think there's no turning back from rooting a device, right? I don't want to lose my data.
Also, I can't seem to make TWRP work because when I plug the phone to the pc it doesn't recognize it and I can't access it whatsoever to put the files in there, even after installing the drivers.
Thanks!

normsrayn said:
I'm a total newbie when it comes to phone flashing, I have a few questions. If I decide to use autoroot, is there a chance for a brick? What could go wrong? I think there's no turning back from rooting a device, right? I don't want to lose my data.
Also, I can't seem to make TWRP work because when I plug the phone to the pc it doesn't recognize it and I can't access it whatsoever to put the files in there, even after installing the drivers.
Thanks!
Click to expand...
Click to collapse
Flash the stock firmware again but from download the firmware from Samfirm application. Please use the HOME_CSC too or your device is wiped. If you need the firmware just post modelnumber or name idk and CSC code and i can post a link with the firmware for you. TWRP can't mount /data and you will need to format your phone with means you lose everything.

getting dark error in galaxy j4 smj400F after system update failing
Picklewickle said:
Hello, this problem is very common for people that root their phones if you get drk error then there are 2 methods to solve this
Method one : easy
Just flash cf autoroot with odin download the file for your phone and flash it in ap
You may get stuck or get bootloops in splash screen or red errors just wait patiently until rom boots
Method 2 : for if you want no root (ota still impossible)
Flash twrp with odin, then download the no verity file
And move it to your phone, in twrp tap on install and select the file
but i have done factory reset so how to enable oem /unlock bootloader to flash via odin
HELP
-----------------------------------------------------------------------------------
Click to expand...
Click to collapse

Same issue
I have the same issue. I cant boot into download mode at all to even attempt to flash anything

Error flashing back to stock from unbranded firmware

I put this in the wrong forum twice. Finally in the right place
I read for hours looking for a solution.
G955USQU5DSD3 Patch April 1, 2019
I had an error on S8+ screen when flashing back to att firmware from unbranded using Comsy. There's still an error on recovery screen.
I was running unbranded firmware G955U1 for a while. I had used Comsy Odin to flash ubranded and worked great. I decided to go back to stock att G955U & upgrade from 8.0 to 9.0.
I used the same Comsy Odin I had used to flash ubranded U1 firmware. I used stock Firmware with same binary 5. I used CSC and not CSC Home.
Odin Passed but on the handset itself, while handset was installing, showed an error on the screen at 32%. The install did complete but
had errors on the stock recovery screen (photo attached). I have not done a factory reset at all during process. I have a backup but did not want reset chancing bricking with these errors showing. I thought the CSC would wipe the data anyway but was left intact.
The phone boots and works fine. I'm on 9.0 now and all my data & settings were untouched.. as if I received OTA. Wifi calling works so for the most part was success. All seems fine except the Recovery still shows the errors, the phone will never be able to receive updates like this (not good if I want to sell it) and I don't know what other problems it could cause.
As a side note, now when I try to flash a different firmware, stock, same binary it will fail with any Odin except for the Comsy. I assume only Comsy can only be used now, even if flashing another stock with same binary, because it never wiped data and some remnants of Oreo are left behind?
I'd like to fix this and get it back to normal without errors. Should I do Factory Reset?
Is there a chance of brick with these errors?
Would it make sense to extract pit file from firmware, use Pit option and repartion with Odin along with flashing BL, AP, CP, and CSC at same time?
Any help greatly appreciated
Thanks
File-Based OTA
Supported API:3
E:unknown volume for path [/odm]
E:unknwon volume for path [/vendor]
"
E:vendor or odm partition won't be used
"
E:failed to mount /data (Invalid argument)
failed to mount '/data'(invalid argument)

trinityracing said:
I put this in the wrong forum twice. Finally in the right place
I read for hours looking for a solution.
G955USQU5DSD3 Patch April 1, 2019
I had an error on S8+ screen when flashing back to att firmware from unbranded using Comsy. There's still an error on recovery screen.
I was running unbranded firmware G955U1 for a while. I had used Comsy Odin to flash ubranded and worked great. I decided to go back to stock att G955U & upgrade from 8.0 to 9.0.
I used the same Comsy Odin I had used to flash ubranded U1 firmware. I used stock Firmware with same binary 5. I used CSC and not CSC Home.
Odin Passed but on the handset itself, while handset was installing, showed an error on the screen at 32%. The install did complete but
had errors on the stock recovery screen (photo attached). I have not done a factory reset at all during process. I have a backup but did not want reset chancing bricking with these errors showing. I thought the CSC would wipe the data anyway but was left intact.
The phone boots and works fine. I'm on 9.0 now and all my data & settings were untouched.. as if I received OTA. Wifi calling works so for the most part was success. All seems fine except the Recovery still shows the errors, the phone will never be able to receive updates like this (not good if I want to sell it) and I don't know what other problems it could cause.
As a side note, now when I try to flash a different firmware, stock, same binary it will fail with any Odin except for the Comsy. I assume only Comsy can only be used now, even if flashing another stock with same binary, because it never wiped data and some remnants of Oreo are left behind?
I'd like to fix this and get it back to normal without errors. Should I do Factory Reset?
Is there a chance of brick with these errors?
Would it make sense to extract pit file from firmware, use Pit option and repartion with Odin along with flashing BL, AP, CP, and CSC at same time?
Any help greatly appreciated
Thanks
File-Based OTA
Supported API:3
E:unknown volume for path [/odm]
E:unknwon volume for path [/vendor]
"
E:vendor or odm partition won't be used
"
E:failed to mount /data (Invalid argument)
failed to mount '/data'(invalid argument)
Click to expand...
Click to collapse
I know this is old but the 32% failure is normal. Happens anytime you flash a firmware with csc. That's just how it is. No more no less
I also have the same errors with odm and such. Should be just fine. Also comsy is old and outdated. Shouldn't work for pie oreo or pie at all. Due to the lz4 and non tar formats now used

S8 (sm-g950f) wont boot, reset, wipe and is stuck

Hello,
My phone(Samsung galaxy s8) just had a crash and is stuck on the blue screen with "Installing update". After several seconds the screen goes away and boots straight into the recovery mode.
The log that i see in the recovery is :
Fail to open recovery_cause(No such file or directory)
Failed to mount /efs
Unknown volume for path /odm
dm-verity verification failed
I tried to install the stock firmware (I cant link to the webpage but im 100% sure its the correct one) but it wont boot and goes to the "Installing update" again and after that to the recovery.
I tried installing twrp but it wont install due a FRP lock. i read that you should wipe your data and factory reset. Also tried that but again no succes.
Can someone please help me.
Thanks in advance

nickglas said:
Hello,
My phone(Samsung galaxy s8) just had a crash and is stuck on the blue screen with "Installing update". After several seconds the screen goes away and boots straight into the recovery mode.
The log that i see in the recovery is :
Fail to open recovery_cause(No such file or directory)
Failed to mount /efs
Unknown volume for path /odm
dm-verity verification failed
I tried to install the stock firmware (I cant link to the webpage but im 100% sure its the correct one) but it wont boot and goes to the "Installing update" again and after that to the recovery.
I tried installing twrp but it wont install due a FRP lock. i read that you should wipe your data and factory reset. Also tried that but again no succes.
Can someone please help me.
Thanks in advance
Click to expand...
Click to collapse
I'm going to take a guess here, you had the device rooted and then you tried to apply an OTA stock update while the device was rooted? Tyically, stock OTA updates can't be applied to devices that have been rooted because the updates require the device to have an unmodified system partition(no root) and they require stock recovery instead of custom recovery. There are "some" devices that can apply stock updates while rooted, but those are few and far between.
If that is what you did, you need to do some searching for repairing failed OTA updates on rooted devices.
Sent from my SM-S767VL using Tapatalk

S7 lost /efs and with it imei on bootloader v8 - chances of repair?

I have a s7 G930F here in Germany were i lost /efs due to a wrong backup overwrite.
The phone was on stock oreo with bootloader 8 now is on lineage but ofcourse mobile data / calling wont work without propper imei or efs.
I tried to flash a factory image / combined image but that does not go through with odin as the phone checks boot loader versions and i havent found an image with b8 as a bootloader version which would restore my/efs.
What are my options?

pr10dr said:
I have a s7 G930F here in Germany were i lost /efs due to a wrong backup overwrite.
The phone was on stock oreo with bootloader 8 now is on lineage but ofcourse mobile data / calling wont work without propper imei or efs.
I tried to flash a factory image / combined image but that does not go through with odin as the phone checks boot loader versions and i havent found an image with b8 as a bootloader version which would restore my/efs.
What are my options?
Click to expand...
Click to collapse
You just need to flash the latest G930F for Germany. The firmware code is DBT, it's unbranded so no netweork provider bloatware.
I've attached Samfirm tool. It gets the latest firmware straight from samsung servers version 8.
1. Unzip
2. Run application as admin
3. Check auto box
4. SM-G930F in Model box
4. DBT in Region box
5. Check Update
6. Wait to finish
7. Flash files with Odin
8. New Phone.

I followed your instructions and downloaded Firmware.
After flashing the phone reboots, displays that its erasing and after another reboot stops at the screen with the yellow exclamation mark and displaying "no command".
From there it only loops: reboot -> installing system recovery displayed for a very short time -> no command.
I since flashed multiple times and got the same result everytime. I flashed BL AP CP CSC (both CSC and home CSC yield same result) . Odin shows no errors.
Firmware is G930FXXS8ETC6

Alright i think i resolved part of the issue as follows:
* i flashed the complete stock firmware as described above
* After flash was done i rebooted again into download mode and installed TWRP as recovery via odin
* I then booted into TWRP and copied the "no-verity-opt-encrypt" in the latest version to the phone
* The zip of "no-verity-opt-encrypt" i then installed with TWRP.
The phone booted up. Factory Samsung Android works but the imei is still shown as empty / unknown.
Some guides suggest to flash a factory combination image but i can not find one for bootloader version 8 which is on my phone.

pr10dr said:
I followed your instructions and downloaded Firmware.
After flashing the phone reboots, displays that its erasing and after another reboot stops at the screen with the yellow exclamation mark and displaying "no command".
From there it only loops: reboot -> installing system recovery displayed for a very short time -> no command.
I since flashed multiple times and got the same result everytime. I flashed BL AP CP CSC (both CSC and home CSC yield same result) . Odin shows no errors.
Firmware is G930FXXS8ETC6
Click to expand...
Click to collapse
Yes sometimes this happens, try a different firmware like United Kingdom BTU.
Does Odin say Pass?
The updating and erasing screen is normal after flash just leave it.
Once the phone boots on BTU you can either change language to German or flash DBT again.
It's worth checking / reinstalling Samsung drivers. Use different USB port. Odin should be version 13.
As long as you can boot into download mode the problem is fixable.

Thanks for your advice.
I will try the BTU firmware later. Just to check we are on the right track: If i understand you correctly you are saying the lost imei will be "fixed" by installing either the BTU or DBT stock firmware via odin?

Installed the BTU version. Same behaviour. The System does not start and hangs on the same position.

pr10dr said:
Installed the BTU version. Same behaviour. The System does not start and hangs on the same position.
Click to expand...
Click to collapse
OK it sounds like the BL info on the EFS is missing or corrupt.
Just try one more thing before trying to repair the EFS.
Flash firmware again with Odin but uncheck "auto reboot"
When passed in Odin disconnect phone.
Hold volume down+home+power. As soon as the screen goes back move your finger to volume up while still pressing home +power. You want to boot into system recovery. It may take a few attempts.
Once in system recovery, wipe data/factory reset and reboot phone.

Managed to get into Recovery directly after flash. But recovery is not loading fully and is outputting some text like :
HTML:
failed to open recovery_cause /No such file or directly)
Blob verificatio failed 255
failed setting up dirty targets
failed to mount /system (bad file descriptor)
...
Any chance of reparing the efs? Someone here messaged my and told me i would in PM that i might need to connect to some server software to get efs back.
Any idea is appreciated

pr10dr said:
Managed to get into Recovery directly after flash. But recovery is not loading fully and is outputting some text like :
HTML:
failed to open recovery_cause /No such file or directly)
Blob verificatio failed 255
failed setting up dirty targets
failed to mount /system (bad file descriptor)
...
Any chance of reparing the efs? Someone here messaged my and told me i would in PM that i might need to connect to some server software to get efs back.
Any idea is appreciated
Click to expand...
Click to collapse
Anyone offering money to fix or connect to a server is a scammer, stay clear.
To repair the EFS you have to get the stock firmware back on there or flash someone esle's EFS back up file. You can buy a damaged S7, install TWRP, back up the EFS to the SD card, put that sd card in your phone then restore the efs. Your phone will then take on the identity of the phone the EFS file came from. Effectively you will have a new IMEI number and mac address. As long as the donor phone is not registered on the network your phone will work fine. You cannot have two phones with the same IMEI registered on the network, both will be blocked and black listed. Obviously the donor phone must be exactly the same model as yours.
However the method below should be tried first.
The error with the text "failed to open recovery" means the phone cannot find the partition where the stock recovery file is located.
Now to solve this we can install TWRP with ODIN and that will provide a way to install the stock firmware in .zip format direct from the sd card using TWRP as the recovery method instead of the inbuilt stock recovery which cannot be found.
You should then be left with a phone which has a restored EFS with your original IMEI and other data with TWRP as the recovery tool.
Which ever method you choose TWRP must be installed first.