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
Related
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
Hello everybody
my I8160 is stuck in recovery mode. I have flashed ROM with CyanogenMod 12 but my SIM card wasn't recognized anymore. I then decided to downgrade to 2.3.6 with Odin 3.12.4 and I8160XXLL2_DBTLL1.zip in AP field (XXLL was the original baseband version -- does baseband version matter?)
Odin finished and the phone was rebooted telling me the following
Deleting Cryption Meta Data
-- Copying media files...
Successfully copied media files...
#MANUAL MODE#
-- Updating applications...
Copying Contents.
Successfully updated application.
- Applying Multi-CSC
Installing Multi-CSC
Can't access to '/system/csc/EPL/system/'.
Successfully applied multi-CSC
Then recovery is started (Android system recovery <3e>. When I restart the phone its coming to the recovery mode again. But how to continue now? How do I get android started?
I greatly appreciate any help, Andreas
EDIT: Thanks for the replies. I found a solution, just in case anyone encounters the same problem: Flashing the phone with Odin 3.2.1.4 and i8160XXNB1_OXXNB4_Android_4.1.2_service.zip from https://service-gsm.net/Samsung/I8160/i8160XXNB1_OXXNB4_Android_4.1.2_service.zip/ (all the others I have tried did not work).
Just an idea, have you tried doing a factory reset from the recovery?
I recently downgrade my I8160 from Cynagen to Gingerbread, as I just want to use it as a spare dumb phone with no apps or google account.
I used Odin v3.07 and GT-I8160_I8160XXLK6 which has 3 files. When Coming back to Gingerbread you need the 3 files to be able to repartition.
See screenshot.
Hello friends, when I flash Combination file, or stock file , my phone boots and hang at start up logo, while I restart to recovery I see this error (E:Failed to mount efs, Invalid Argument)?
Can anyone help?
What have you done ? Trying to root and lost your IMEI ?
If so, then go to recovery and do all of the wipes and format Data. Once done, then just flash the exact same ROM as the one which is already installed on your phone.
TheRealKeyserSoze said:
What have you done ? Trying to root and lost your IMEI ?
If so, then go to recovery and do all of the wipes and format Data. Once done, then just flash the exact same ROM as the one which is already installed on your phone.
Click to expand...
Click to collapse
This steps does not work, I need EFS for A8 2018.
I'm having the same problem, I've tried everything. z3x, Odin , won't even let me flash from sd card. Won't load into Oreo just keeps rebooting. I can get into recovery but does nothing as well as boot loader. I did have a utility im pretty sure was made by FACTORY BINARY that was it's own little OS with a bunch of little tools. I have a sm-a530w flashed with boot loader 4 ugggg. If anyone can help find that utility that will wipe the whole thing and let me flash from scratch that would be awesome. I've tryed miracle, Uni-Android, samsung tools 29.5 and flashing with odin. Lets me flash factory FIRMWARE but still error's out on the "Failed to mount EFS" HELPPLEASE
A quick suggestion you probably tried, but i've had failure at boot in the past after returning to stock via odin if i used home_csc. So, if you haven't already tried, use just csc. No home. On home it does system.img until the end, no user_data . Not sure at all what the deal is but it's all i can suggest. Get 'er goin'!
:Failed to mount EFS
Yes I think I tried that, but at this point, I try again. Any more suggestions would be greatly appreciated. An A8 in mint shape just hurts LOL.
i have sm g955f, flashed on pie, everything is ok, works fine, no memory lost, but when in recovery i get:
E: unknown volume for path [/ odm]
E: unknown volume for path [/ vendor]
E: unknown volume for path [/ odm]
E: unknown volume for path [/ vendor]
anybody knows what this is about? i installed stock firmware, knox has not been triggered, status official. during odin update, no vendor or odm have been flashed to phone (in odlin steops / actions)...
thanks
No one has the same issue?
I too have the same issue. Also to add to that my phone is currently stuck booting into safe mode. I did root my s8+ many moons ago and completely forgot.. not sure what I can do to fix this or if I should try flashing the stock firmware back onto it, completely erase.
Senex03 said:
I too have the same issue. Also to add to that my phone is currently stuck booting into safe mode. I did root my s8+ many moons ago and completely forgot.. not sure what I can do to fix this or if I should try flashing the stock firmware back onto it, completely erase.
Click to expand...
Click to collapse
I didn't root, nor ever flashed anything but stock firmware. Didn't find any solution on the net. Also, tried to flash with full erase, no success.
Quite annoying.
Note Fe N935F
I have same issues and i didn't root my device before
jba.33a said:
i have sm g955f, flashed on pie, everything is ok, works fine, no memory lost, but when in recovery i get:
E: unknown volume for path [/ odm]
E: unknown volume for path [/ vendor]
E: unknown volume for path [/ odm]
E: unknown volume for path [/ vendor]
anybody knows what this is about? i installed stock firmware, knox has not been triggered, status official. during odin update, no vendor or odm have been flashed to phone (in odlin steops / actions)...
thanks
Click to expand...
Click to collapse
It's not an issue if it doesn't affect the functionality of your phone.
It's just a bug in the stock recovery.
same issue
SM-G950U here 100% stock from verizon. Went to bed night before last with low battery woke up to plug it in and boots into the Android Recovery with:
#Reboot Recovery Cause is [[Bootchecker]RebootRecoveryWithKey]#
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
i've cleared cache , factory reset ... pretty much every option in this menu. Can't boot to safe mode because you never get the "Samsung" just the initial galaxy screen or the recovery.
Brought to a store they could give a **** less they just want to sell me a new phone , big surprise.
I downloaded Odin and Drivers but can't find a non-paywall firmware and the 15k/sec download has failed multiple times (never rooted before)
So just looking for some help here.....
Did anyone fine a solution for this? I started a thread on the same thing did not see this old one.
I was stock att then tried unbranded firmware for a while then recently decided to go back to att and upgrade to Pie at the same time. All seemed to be success besides the recovery showing same error as op.
I have not done a factory reset I was afraid to brick it with the errors going on. After reading here I see reset didn't help. My data and everything was still intact after flashing which was a surprise after changing from U1 to U, and upgrading. I sure would like to find a solution to the errors on recovery. I'm afraid it will be a problem in the future.
On a side note, I noticed I have 5G signal on att. On the unbranded firmware it was LTE tops.
I found the following solution on Samsung J5:
-Download Stock Firmware
- Extract AP with 7zip
- Copy boot.img somewhere else so you can rename it to recovery.img
- Replace old with new recovery.img in extracted AP folder
- Compress AP again to tar file
- Flash new AP archive with everything else in Odin ( I used the PIT file as well nanderase and repartion
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.