Problem boot Efs e: Failed to mount /efs (invalid argument) - Samsung Galaxy S8 Questions and Answers

Hello everybody
How are you ?!
Great community, i love this forum for the ROM & Kernel ^^
Seriously,
I've got serious problem !!!
App via playstore, has erased my phone, and not my SD CARD ....
I flash via ODIN a officially firmware, i haven't error message.
Problem boot, and this message on the recovery : EFS E: FAILED TO MOUNT /EFS (INVALID ARGUMENT)
I want to make the factory binary
for unlock OEM and install the TWRP for my problem, but it's doesn't works, loading, but no boot ...
Sorry for my mistakes, i'm French ^^
Cordially,
Olvers974

Please post in English. Here is a link to the forum rules - https://forum.xda-developers.com/announcement.php?a=81
4. Use the English language.
We understand that with all the different nationalities, not everyone speaks English well, but please try. If you're really unable to post in English, use an online translator. You're free to include your original message in your own language, below the English translation. (This rule covers your posts, profile entries and signature).
Click to expand...
Click to collapse
The purpose of these threads is not only to help the members posting, but also to help anyone searching for an answer to similar problems later as well. Please respect the forum rules, they are there for a reason. Thanks for understanding
Regards
noppy22

Related

i can't install costum rom (deodex rom's)

When i go recovery see this massage :
E: Can't find misc
E: Can't mount cache: Recovery/command
E: Can't find misc
E: Can't mount cache: Recovery/log
E: Can't find misc
What is the problem?
Does not anyone answer me ?
Clearvoyant
Dude, do you expect us to know everything you did, what kind of phone you have, what procedure you followed, where you messed up, etc. etc. just by showing a few Errors?
If you're serious about getting answers, you better start getting serious about providing usefull information that can help members better understand what part of the procedure eventually led to these errors. We do not have a crystal ball nor can we look in your head from here.
So please retry your topic by:
- First watching the n00b-clip (You've come across the link a few times now, a quick search will provide you the video again, please watch it.)
- Reconsider what you have done, what you should have done and what you'd better not do.
- Use the f*** Search!
- Though it's a long shot, maybe if you actually read other posts on these forums, you'd actually learn stuff from it.
- If you still feel we should tell you where you made a mistake we need info:
+ Detailed step by step description of what you have done thusfar to arrive to this error, what you've been reading to help you guide through it, what questions you might have about the guides and please share any assumption you have made. (Since assumption is the mother of all fckups )
+ Including, but not limited to, the version numbers of the firmwares, roms and bootloaders you started with and the ROM('s) version you'd like to have installed. Supply rich/detailed comments about how exactly you think it should work and how it differs from what you're experiencing.
+ Do not expect anyone responding AD HOC. You want help, you better give people a reason to provide you help. Bumping a thread within a few hours with little or no usefull information is pointless. You only accomplish people to be annoyed by your nagging.
Users behaving like You do here, and threads like this one, are THE SOLE REASON most more experienced members do not respond to n00bs and limitations are applied to new member accounts.
If you do not want to go through this trouble, you should not have come to this website. It's really important you do your own research first and only after you've tried (almost) everything and read most manuals concerning your attempted ROM-setup; then you can try to ask others to look into it.
Memorize what I've said here, it's the basic code of conduct to this tech forum - and many other tech forums on the internet.
I have been browsing here for a couple of months now, I did not have to ask a single question about flashing or upgrading my devices since everything was already explained in detail. Personally I'd rather search than that I waste anyone's time asking for that what has already been answered.

[Q] Fail to mount from E:

Hi All of you
I am having problem with my Galaxy Y mobile.
Don't know why it start rebooting again and again. I tried "Power + Up Volume + center" button to restore it from memory card. But it always reply E:failed to mount <invalid argument>.
There are lot of thread about this issue. But none of these thread explained how to do it.
Can someone explain me how to fix my mobile?
which file to download?
which file to install in PC ?
which file to download in memory card?
everything!!!!
i am new in forum and i don't know how to fix mobiles. Don't know about oid etc etc.
Please explain everything. which file to download in pc and which one to mobile (memory card)!
Thanks
Dev Prakash
India
first did u flash something maybe rom or kernel?? or changing something in build.prop..
☆★☆★☆★☆★☆★☆★☆★☆★
devprakash said:
Hi All of you
I am having problem with my Galaxy Y mobile.
Don't know why it start rebooting again and again. I tried "Power + Up Volume + center" button to restore it from memory card. But it always reply E:failed to mount <invalid argument>.
There are lot of thread about this issue. But none of these thread explained how to do it.
Can someone explain me how to fix my mobile?
which file to download?
which file to install in PC ?
which file to download in memory card?
everything!!!!
i am new in forum and i don't know how to fix mobiles. Don't know about oid etc etc.
Please explain everything. which file to download in pc and which one to mobile (memory card)!
Thanks
Dev Prakash
India
Click to expand...
Click to collapse
first of all since u r new to xda u should read this guide-http://forum.xda-developers.com/showthread.php?t=1974338
do read it.....it will help u to understand basics of flashing rooting and some other things used in xda....
now to solve ur issue.....u must flash a stock rom.....
go to sir doky's thread-http://forum.xda-developers.com/showthread.php?t=1465800.....download the latest stock rom of ur region(for india download ddlk1)....than see the 2nd post in that thread on how to flash stock rom via odin......everything is explained their in the post.....just read it and follow the guide wisely....
Thankyo
anmolsharma1293 said:
first of all since u r new to xda u should read this guide-http://forum.xda-developers.com/showthread.php?t=1974338
do read it.....it will help u to understand basics of flashing rooting and some other things used in xda....
now to solve ur issue.....u must flash a stock rom.....
go to sir doky's thread-http://forum.xda-developers.com/showthread.php?t=1465800.....download the latest stock rom of ur region(for india download ddlk1)....than see the 2nd post in that thread on how to flash stock rom via odin......everything is explained their in the post.....just read it and follow the guide wisely....
Click to expand...
Click to collapse
Thanks Bro.
really helpful. My mobile is working fine.
Thankyou.

E footer is wrong, e signature verification failed when installing OTA update?

Hi folks!
Just bought myself an S5, have successfully rooted the phone, and decide to install the Alliance Rom with no issues.
I then downloaded the Black Glass OTA Theme, went into recovery mode and tried to unzip the file (Using Philz touch) - I received the following two error messages: "e footer is wrong, e signature verification failed"
I'm on android v4.4.2 - I backed up prior to this so I've just restored back to factory settings for the meantime, but I'd like to know why I'm getting those two errors if possible?
Many thanks!
ggiiaann91 said:
decide to install the Alliance Rom with no issues.
I then downloaded the Black Glass OTA Theme, went into recovery mode and tried to unzip the file (Using Philz touch) - I received the following two error messages: "e footer is wrong, e signature verification failed"
Click to expand...
Click to collapse
Could be many reasons, you don't have enough information yet to know. Crucially, you failed to paste the verbatim error and the context surrounding it here. Or even link to the theme you refer to. So we don't have much to go on.
As it is labeled as an OTA theme, it will be specifically formatted for that custom ROM. So wouldn't it make more sense to seek help in the custom ROM support thread?
The actual error could be anything from a corrupt download (did you verify the md5 checksum or try downloading the theme again?) to a marginal USB cable (did you try a different USB cable and port?). Or many other things. Did you search the support thread to see if anyone else was troubleshooting similar issues?
.
Sorry, I'm completely new to the forum so don't know my way about.
How would I go about obtaining/providing the verbatim error?
ggiiaann91 said:
How would I go about obtaining/providing the verbatim error?
Click to expand...
Click to collapse
You can copy and what you see on screen from the log that Odin or Kies makes. Or alternately make a screenshot.
Most questions could be expediently answered by a search of the forum too. But for some reason, most people don't try that.
.
fffft said:
You can copy and what you see on screen from the log that Odin or Kies makes. Or alternately make a screenshot.
Most questions could be expediently answered by a search of the forum too. But for some reason, most people don't try that.
.
Click to expand...
Click to collapse
I appreciate that, I did try looking via the forum before asking but didn't find any mention of 'verbatim'...
I also searched for the errors I am experiencing and whilst I found several other threads, none are a similar scenario to mine.
I am not using Odin or Kies, I was able to root my phone successfully, and installed the Alliance Rom with no issues.
My issue occurs after downloading an the OTA update/theme and then going into recovery mode > Install Zip > Choose zip from /sdcard > OtaDownloads/ > Install Black_Glass_S5
I ticked to check the MD5 sum, it came back with with 'MD5 check: error'
Signature verification causes the 'E: footer is wrong and E: signature verification failed' errors.
ggiiaann91 said:
I did try looking via the forum before asking but didn't find any mention of 'verbatim'...
Click to expand...
Click to collapse
Your search technique needs polishing. If some particular keyword doesn't work in a search, then use a synonym or reword your search query.
ggiiaann91 said:
I ticked to check the MD5 sum, it came back with with 'MD5 check: error'
Signature verification causes the 'E: footer is wrong and E: signature verification failed' errors.
Click to expand...
Click to collapse
And there is crucial information that you didn't provide earlier. The very reason why I wanted the verbatim context. We are't psychic and can't help you effectively if you don't provide a detailed account.
Adding those details is a huge improvement. You selected a feature (check md5) without understanding how it worked. That caused an error. You then asked us what the error meant without telling us that you had done that and not providing any context or details for us to work with.
The error message, in context, tells us that you either tried to check md5 on a file that doesn't have a md5 - therefore a spurious error. Or the file was profoundly corrupt.
.
It's not my intention to be vague, I simply do not know what information is relevant/beneficial to you.
I deleted the file and then re-downloaded a new copy but it still won't unzip the file, the issue also occurs for another OTA file.
If there's specific info I can provide then by all means let me know and I'll provide it.
Appreciate the help and patience - evidently I'm still a noob when it comes to all the features/tools.
ggiiaann91 said:
If there's specific info I can provide then by all means let me know and I'll provide it.
Click to expand...
Click to collapse
If you were already an expert, you could pare down the details in your post to the minimum amount needed. But when seeking help in an area that is new to you, you should provide the maximum amount of information. If in doubt post more, rather than exclude something when troubleshooting.
Nothing impairs someone from providing effective help as much as missing crucial details. The only things you should withhold are personally identifying info e.g. serial numbers.
Someone knowledgeable trying to help you can easily sift through too much info. Not the reverse.
.
fffft said:
If you were already an expert, you could pare down the details in your post to the minimum amount needed. But when seeking help in an area that is new to you, you should provide the maximum amount of information. If in doubt post more, rather than exclude something when troubleshooting.
Nothing impairs someone from providing effective help as much as missing crucial details. The only things you should withhold are personally identifying info e.g. serial numbers.
Someone knowledgeable trying to help you can easily sift through too much info. Not the reverse.
.
Click to expand...
Click to collapse
I wasn't disagreeing - I've not got any other information to provide currently.
Will try searching the forum more to see if I can find anything else in the meantime.
g935f stuck on logo
hi i tried to remove pattern lock of my s7 edge with z3x but phone just stuck on logo now im trying to take it to download mode but can not boot , just i can go to recovery mode , can anyone help me , is this possible i can flash by sd card.
fffft said:
Your search technique needs polishing. If some particular keyword doesn't work in a search, then use a synonym or reword your search query.
And there is crucial information that you didn't provide earlier. The very reason why I wanted the verbatim context. We are't psychic and can't help you effectively if you don't provide a detailed account.
Adding those details is a huge improvement. You selected a feature (check md5) without understanding how it worked. That caused an error. You then asked us what the error meant without telling us that you had done that and not providing any context or details for us to work with.
The error message, in context, tells us that you either tried to check md5 on a file that doesn't have a md5 - therefore a spurious error. Or the file was profoundly corrupt.
.
Click to expand...
Click to collapse
You should be nicer. That was just plain rude.
guau pues buscais el update.img lo meteis y listo
"read only"?
ggiiaann91 said:
Hi folks!
Just bought myself an S5, have successfully rooted the phone, and decide to install the Alliance Rom with no issues.
I then downloaded the Black Glass OTA Theme, went into recovery mode and tried to unzip the file (Using Philz touch) - I received the following two error messages: "e footer is wrong, e signature verification failed"
I'm on android v4.4.2 - I backed up prior to this so I've just restored back to factory settings for the meantime, but I'd like to know why I'm getting those two errors if possible?
Many thanks!
Click to expand...
Click to collapse
Do you mount your SD card into a USB card reader and then use in a USB port on your desktop or laptop?
because if you accidentally made the "E" port into "read only" on one file, or anything on the drive it could have locked the entire drive down, which to me is exactly
what it sounds like,
put the card back into your desktop, right click as if you were ejecting drive. select properties> preferences> share file settings and set to "Everyone"
yes i know its old, but its not a bad thing to bring up to answer for other newbies right on front page.
thanks this helped me a lot
Greggofaster said:
Do you mount your SD card into a USB card reader and then use in a USB port on your desktop or laptop?
because if you accidentally made the "E" port into "read only" on one file, or anything on the drive it could have locked the entire drive down, which to me is exactly
what it sounds like,
put the card back into your desktop, right click as if you were ejecting drive. select properties> preferences> share file settings and set to "Everyone"
yes i know its old, but its not a bad thing to bring up to answer for other newbies right on front page.
Click to expand...
Click to collapse
I realised I couldn't boot from sd card because I was creating the boot card through a card reader from this post so that really helped me thanks
"Hey i'd rather you do the work for me" kinda thang is a bit annoying. People are so silly sometimes.

Repartition zenfone with terminal/shell via linux tools to fix any trouble

Dears, the purpose of this thread is to find a way to repartition internal storage with linux (like 'parted') tools.
who could be interested in finding the solution? -
anyone, who has debrick problems and currently has no solution to restore oem partitions.
the most often you come up to the final error when oem partitinoing with partition.tbl command produces 'gpt command failed' error.
and no repartitioning.
at this stage any unbrick and reflash of the stock rom fails.
my service says there is no way to repartition zenfone 5/6 internal storage due to its architecture (? I'm not sure in definitions, but the idea is clear).
they say if that would be samsung chip, then it is possible to repartition.
my experience says things very close to this: I cannot run 'parted' because it looks like there is no 'parted' for x86 architecture.
so, if somebody can add more knowledge to the problem, then, perhaps, we could reanimate all those bricks we have in our hands
mine looks just fine and can run bootloader and recovery, but can't mount any partition and the rest I mentioned.
Wave
I have a problem with my phone and an asus zenfone 5 (a501cg). I have not been able to find a way to solve this problem. I read in certain forums, there are people trying to write the android pardos by adb or fastboot
---------- Post added at 07:42 AM ---------- Previous post was at 07:33 AM ----------
I have tried all the methods to try to resurrect my a501cg, posted in this forum, all show in the end "E: can not mount / cache / recovery / log"
"E: can not open / cache / recovery / las_update-log"
"E: failed to mount / cache (invalid argument)"
. And a huge error list like the three I
:rolar os olhos:
Thdogz said:
Wave
I have a problem with my phone and an asus zenfone 5 (a501cg). I have not been able to find a way to solve this problem. I read in certain forums, there are people trying to write the android pardos by adb or fastboot
---------- Post added at 07:42 AM ---------- Previous post was at 07:33 AM ----------
I have tried all the methods to try to resurrect my a501cg, posted in this forum, all show in the end "E: can not mount / cache / recovery / log"
"E: can not open / cache / recovery / las_update-log"
"E: failed to mount / cache (invalid argument)"
. And a huge error list like the three I
:rolar os olhos:
Click to expand...
Click to collapse
Yes, if you see it can't mount partitions and did try oem repartition command with no luck, then you have the same type of the problem.
Unfortunately, as I said above, we can (if it's possible) solve it with an expert help only, which is this thread for
Yes, I tried to mount "oem partitions" in fastboot mode, without success. I researched and ended up seeing another forum, said that the reason for this error is not more software, but Hardware said there is a bug in smatphone, a piece called EMMC, I read a bit about this central board of Asus zenfone. ... the error occurred by corronper in that area of ​​smaphone.
---------- Post added at 06:12 AM ---------- Previous post was at 06:05 AM ----------
Hey, dude, since when did you find this error? I'm going to make a month for my device to have this damn error ... I do not know what to do, any time?
Facing the same problem... Remote gpt command failed.. can't mount /cache

Your device is corrupt and cannot be trusted and may not work - ZB601KL

Hello, anyone can help me with this error? "your device is corrupt and cannot be trusted and may not work properly." This is after I updated my phone from Oreo to Pie.
I tried to follow the steps from an XDA forum (https://forum.xda-developers.com/asu...upted-t3937991), When I checked the Verity Mode settings using the command fastboot oem device-info I see that it is set to FALSE.
But when I tried to run the command : adb reboot "dm-verity enforcing" or fastboot reboot "dm-verity enforcing" I am getting an error message saying : fastboot: usage: unknown reboot target dm-verity enforcing
I attached a screenshot of the error message.. I am not sure what are the next steps for me.. I need some help please...
[email protected] said:
Hello, anyone can help me with this error? "your device is corrupt and cannot be trusted and may not work properly." This is after I updated my phone from Oreo to Pie.
I tried to follow the steps from an XDA forum (https://forum.xda-developers.com/asu...upted-t3937991), When I checked the Verity Mode settings using the command fastboot oem device-info I see that it is set to FALSE.
But when I tried to run the command : adb reboot "dm-verity enforcing" or fastboot reboot "dm-verity enforcing" I am getting an error message saying : fastboot: usage: unknown reboot target dm-verity enforcing
I attached a screenshot of the error message.. I am not sure what are the next steps for me.. I need some help please...
Click to expand...
Click to collapse
Instead of opening another thread you should've posted this in the thread you followed. It'll be much more helpful. Also try using USB 2.0 port instead of 3.0 and with the latest drivers.
@[email protected] THREAD CLOSED! @ all interested in the subject, please follow this already existing thread, where the OP posted before this thread was created and where the OP got his problem solved.
XDA Forum Rules (excerpt):
...
5. Create a thread topic or post a message only once, this includes external links & streaming media.
As a large forum, we don't need unnecessary clutter. You're free to edit your message as you like, so if you do not receive an answer, revisit your message and see if you can describe your problem better. Not everyone is online at the same time so it might take a while before you receive an answer.
You can bump your unanswered question once every 24 hours
Duplicate threads and posts will be removed
Always post in an existing thread if a topic already exists, before creating a new thread.
Use our search function to find the best forum for your device.
Links to an external source are only allowed if relevant to the topic in hand. A description must be included, no copy & pasting from the original source.
Self-promotion is forbidden, this includes blogs, social media and video channels etc. Random links will be removed.
...
Click to expand...
Click to collapse

Categories

Resources