Hello everyone. I'm a new member here so if I forget to mention crucial information needed to get technical support, please let me know.
Surprisingly it all started when my Galaxy Note Pro 12.2 (SM-P900) was low on battery yesterday. I had to go to college so I took my external battery with me and charged it in my backpack. I didn't need my tablet so I left it in there (was working fine before) and I came back to it this morning to find that it had restarted. It was on the glowing blue Samsung logo, but it wouldn't load past that. I tried restarting it and it wouldn't boot past the logo no matter what. So I tried booting into Android System Recovery (Power + Volume UP) to wipe the cache and still, same results. This is where I can see the error "E: failed to mount /efs (Invalid argument)".
I also did the following:
*Download Samsung Kies (both version 3 and the other since each one says it's not supported and to download the other) and try to resolve the issue. Tablet could not be recognized by either version. No fix.
*Download ADB and the official firmware and flash it (adb gives various errors, ex: can't connect. I may be doing the commands wrong as I'm no expert at this). No fix.
*Download Odin in an attempt to flash it, but the first search result in google was a professional-looking website that actually had a trojan-horse for download; had to shut down my PC and run MalwareBytes, Avast! and McAffee to ensure that nothing remained.
I've been at this since morning. I've also looked at other topics and websites about this problem but I can't seem to find a straight-forward solution. Can anyone please help? I desperately need my tablet for work as soon as possible.
Thanks in advance, and please be precise and clear with your answers (because I'm not so good at Android/Linux commands, or rooting or anything that isn't spoon-fed).
Update: Still not working after I tried to apply TWRP 2.8.6.0 (zip) through System Recovery. After finding, opening and verifying the package it gives the following error message:
E: failed to seek in /tmp/sideload/package.zip (Value too large for defined data type), E: signature verification failed, E: failed to mount /efs (Invalid argument).
I should also note that throughout the entire time I used the official firmware, I haven't used any custom ROMs but I'm now open to it since I have to do all this.
Update 2: Downloaded Cyanogenmod Installer and while it was about to install, it detected the device needed to be repaired. My device was in Android System Recovery under the "apply update from ADB" selection, and these errors came up when Cyanogenmod tried to fix it: "E: footer is wrong, E: signature verification failed".
BIG Update (3): I managed to find the legit Odin application and flashed TWRP v2.8.6.0. However, I'm not sure what to do from this point on out. Help?
Hi.
I am in the same situation. Have you found a solution ?
Thanks in advance.
Related
Hey everyone, today I tried to revert to my original stock rogers firmware via the clockwork recovery backup I made. After booting, it gets passed the i896 page and continues until it says ANDROID in a graphic image. This flashes every once in awhile. But after an hour of just leaving it, it's still in the same cycle. I can boot into recovery but when I try to install a new rom it says:
"E: Can't mount /dev/block/st19
(No such file or directory)
E: Can't mount SYSTEM:
E: Failure at line 2:
copy_dir PACKAGE:system SYSTEM:
Installation aborted"
If I go into the Mounts and Storage Menu it shows that /system isn't mounted and the same error occurs if I try to mount it. If I try to do a restore from either of my clockwork backups it says the MD5 sums don't match.
As I'm fairly knew to android I'm apprehensive to go any further because I think I'll probably make it worse. I'm thinking I'll use Odin, if there aren't any other suggestions, I've just never used it before and don't have windows installed at the moment.
What do you guys think is the best course of action?
Thanks for your help.
Get yourself into download mode and flash to stock using Odin. Then root and install the rom of your choosing (I recomend Assonance)
Hello,
I have Android 2.1(Eclair), when I start my mobile, its show a Android logo with '!' (Recovery Mode)
Its show E:Can't find MiSC:
E:Can't open /cache/recovery/command
E:Can't find MISC:
I am already try to reboot, wide data factory reset option.
please help me - how can I reflash my mobile?
More info please
Before people can help you, you need to give more information.
What is the model for your phone and is it rooted?
If so, what ROM is it running and what custom recovery do you have?
demoneyes905 said:
Before people can help you, you need to give more information.
What is the model for your phone and is it rooted?
If so, what ROM is it running and what custom recovery do you have?
Click to expand...
Click to collapse
Lots of Thanks for reply,
I have Micromax A60, rooted with "SuperOneClick v1.6.5"(http://forum.xda-developers.com/showthread.php?t=803682)
How I know about ROM?
Every time my phone start in recovery mode and show 4 options.
1. Reboot system no
2. Apply sdcard:update.zip (Already try to add update.zip in sdcard but every time show error: Signature )
3. wipe data/factory reset (not useful )
4. wite catche partition..
E:Can't find MISC:
E:Can't open /cache/recovery/command
E:Can't find MISC:
E:Can't find MISC:
Hm....Adb
kunnusingh said:
Lots of Thanks for reply,
I have Micromax A60, rooted with "SuperOneClick v1.6.5"(http://forum.xda-developers.com/showthread.php?t=803682)
How I know about ROM?
Every time my phone start in recovery mode and show 4 options.
1. Reboot system no
2. Apply sdcard:update.zip (Already try to add update.zip in sdcard but every time show error: Signature )
3. wipe data/factory reset (not useful )
4. wite catche partition..
E:Can't find MISC:
E:Can't open /cache/recovery/command
E:Can't find MISC:
E:Can't find MISC:
Click to expand...
Click to collapse
Ok you can't "apply sdcard:update.zip" because even though you rooted your phone, you don't have a custom recovery. You have the stock recovery image that comes with your phone. This means that every zip you try to "apply" or flash will automatically be checked for a signature (to make sure its a valid update from the manufacturer). Since the ROMs usually don't have signatures, it won't work
Never mind about finding out the ROM. since you have a stock recovery, it looks like you haven't put any custom ROM on it. you are running the stock android OS that came with the phone.
It seems your OS got messed up when you tried to root the phone. The One Click root method you used I believe wasn't fully compatible with your phone. You should have used "Universal Root." Anyway, Give me a day or two. I will see If I can find you an official zip belonging to your manufacturer. THAT you can push back onto your phone and get your OS back and in working order.
Cheers!
P.S: Check if there is an option in recovery mode called "Toggle Signature verification" I doubt it but if there is it would DEFINITELY help you.
demoneyes905 said:
Ok you can't "apply sdcard:update.zip" because even though you rooted your phone, you don't have a custom recovery. You have the stock recovery image that comes with your phone. This means that every zip you try to "apply" or flash will automatically be checked for a signature (to make sure its a valid update from the manufacturer). Since the ROMs usually don't have signatures, it won't work
Never mind about finding out the ROM. since you have a stock recovery, it looks like you haven't put any custom ROM on it. you are running the stock android OS that came with the phone.
It seems your OS got messed up when you tried to root the phone. The One Click root method you used I believe wasn't fully compatible with your phone. You should have used "Universal Root." Anyway, Give me a day or two. I will see If I can find you an official zip belonging to your manufacturer. THAT you can push back onto your phone and get your OS back and in working order.
Cheers!
P.S: Check if there is an option in recovery mode called "Toggle Signature verification" I doubt it but if there is it would DEFINITELY help you.
Click to expand...
Click to collapse
I have a Micromax A60 from this company( - http://www.micromaxinfo.com/product.php?cat=Think_Innovative&product=android_A60 )
"Toggle Signature verification" not show in my recovery mode.
If company not release "update.zip" then I can't fix my phone?(dead phone ?)
kunnusingh said:
I have a Micromax A60 from this company( - http://www.micromaxinfo.com/product.php?cat=Think_Innovative&product=android_A60 )
"Toggle Signature verification" not show in my recovery mode.
If company not release "update.zip" then I can't fix my phone?(dead phone ?)
Click to expand...
Click to collapse
I'd recommend changing to CWM recovery via rom manager if you need to toggle verification. Rom manager from the market will flash a recovery for you also.
theimpaler747 said:
I'd recommend changing to CWM recovery via rom manager if you need to toggle verification. Rom manager from the market will flash a recovery for you also.
Click to expand...
Click to collapse
I have no access to USB debugging so I can't use adb command and my phone always start in recovery mode, show only 4 options.
How can I install CWM recovery mode?
It is possible to reinstall whole OS?
Same Problem with HTC Hero, after one click (z4root) root
Hi @ all,
i have the same problem with my hero, and every solution that i can find is using fastboot, but with Eclair i cant´s use it.
So please help.
Here is some dato of my hero:
HERO CVT SHIP S-ON
HBOOT-1.76.0007 (HERO10000)
MICROP-010f
Radio-6.35.15.11
1. If your USB debugging is enable then you can fix your problem.
2. official update.zip can fix your problem.
You can't do anything(but your mobile company can help you)
1. Your mobile company not release any update for your device
2. If USB Debugging is disable
I send my Micromax Mobile on 08 Feb, 2011 and Still no info on my device, Micromax = Poor Quality Support, Wastage of money.
@Micromax - Please close your company.... and move your company to your own country....
I tryed to fix it with every update.zip I found in web by
downloading the zip
rename to update.zip
format sd card
copy update.zip to sd card
start in recovery mode
try to start update
... and get a varification failed error
Has somebody a working update.zip, or can say where can I get it and if my steps are right?
1. If your update.zip is not official(signed) then you can't update your device.
Download this and rename this file to update.zip and retry.
Its a signed update.zip
http://www.filecrop.com/40683206/index.html (Link is valid for 30 minute)
If not work then just find your radio update in this list..
http://www.filecrop.com/update-Hero.html
Thank you very much, I will try it tonight.
Damn, now I get a
"failed to verify whole-file signature" error???
What´s wrong now?
Maybe I need a Certificate to put on my sdcard for the whole file?
HTC Hero Problem Solved
I have solved my Problem.
I downloaded the original RUU from shipped-roms.com, swtiched to Fastboot Mode and installed the RUU. And voilà, Hero is new again.
E:Cant mount/cache/recovery/last_log
any one plzz help me..
i have a micromax a60 brought in 2011
i want to update my ph 2.1 to 2.2(Foryo)
but i get a error on recovery mode..
E: Failed to find cache partition to mount at “/cache”
E:Cant mount/cache/recovery/last_log
E:cant open/cache/recovery/last_log
E:Failed to find cache partition to mount at cache.
Then i try to install zip from sd card, choose zip from sd card select Jet 2.1.zip. It ends up at.
assert failed: write_raw_image(“/tmp/boot.img”,”boot”)
E:Error in sdcard/installations/Jet 2.1.zip (status 7).
Installation aborted.
i flesh my phone throw android download toll but he is still showing this message.. plz help me...
Hi Friends,
I am new to the XDA community and was driven here as a lot of my friends recommended this.
I recently installed the InDroid 4.0 on my Samsung Galaxy I5801 handset. Everything went fine, no problems. After that i wanted to upgrade the version from 4.0 to 4.1, but the upgrade method didn't work.
I would get the following error :- E: Can’t mount /dev/block/mmcblk0 (or NULL) ( No Such file or directory) .
I have searched the forum and trust me, if there was a tool on this website which would tell you how long I have been searching, it would be nothing less than 8 hours straight.
I have read thru the forums about fastbooting and other options.
To begin with, I tried formatting my phone completely, used another SD card but I would get the same error. My phone is rooted but that error seems to keep popping up.
I get the following when I reach my Recovery Screen :-
------------------------------------------------------------------------------------
Android System Recovery
Samsung Recovery Utils – For BML-
Enter : ok key, select
Reboot system now
Apply sdcard:update.zip
Wipe data factory reset
Wipe cache partition
Finding the update package…
E: Can’t mount /dev/block/mmcblk0 (or NULL) ( No Such file or directory)
E: Can’t mount SDCARD:Update.zip. Installation Aborted.
------------------------------------------------------------------------------------
I followed the steps exactly as in the InDroid forum and also, I downloaded the videos off youtube, just in case, but no go.
I am faced with two issues:
1) With this update, my memory card would never show up in the PC.
2) I cannot upgrade the versions.
Is there any way that I can directly go to version 4.4 instead of following the upgrade path?
Is there any way that I can upgrade by resolving this issue.
I am back to my factory Default Installation and the memory card works fine and everything else works fine.
I know that you guys are professionals and busy, but Any help would be Really appreciated. I could just back away to the factory ROM but i don't want my efforts to go waste.
Please Help.
Regards,
Shashank Raj.
Samsung I5801.
Hello, first i have to explain that i tried everything to avoid ask for help here, but i have no more ideas how to try a fix by myself.
I have a huge issue in my S8+ (exynos), the first is that GPS doesn´t working properly, the second (maybe because a nand system error), everytime i go to the original recovery, a error message appears.
#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 for path [/odm]
E: unknown volume for path [/vendor]
E: unknown volume for path [/odm]
E: unknown volume for path [/vendor]
Manual mode v1.0.0
remove failed dir /system/carrier/ATT/priv--app/attIqi_ATT nmo such file or directory
can´t open directory: sup cid permissions
E: [Libsfs_mgr] firmware info was not valid /proc/device-tree no such file or directory.
why i have these errors in my recovery, is the GPS problem related with this issue?
I tried everything that i know: rooted my device, backed up the EFS folder, used this thread and flashed my phone via TWRP, did a fully nand wipe (EFS included) without solving anything.
https://forum.xda-developers.com/ga...1ara2-devbase-v5-0-encryption-t3752964/page61
I did a full nand wipe a lot of times, i also used a PIT file to rebuild the entire partitions, but something else still missing , my knowledge about this specific issue is very basic at this point.
Paulo1024 said:
Hello, first i have to explain that i tried everything to avoid ask for help here, but i have no more ideas how to try a fix by myself.
I have a huge issue in my S8+ (exynos), the first is that GPS doesn´t working properly, the second (maybe because a nand system error), everytime i go to the original recovery, a error message appears.
#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 for path [/odm]
E: unknown volume for path [/vendor]
E: unknown volume for path [/odm]
E: unknown volume for path [/vendor]
Manual mode v1.0.0
remove failed dir /system/carrier/ATT/priv--app/attIqi_ATT nmo such file or directory
can´t open directory: sup cid permissions
E: [Libsfs_mgr] firmware info was not valid /proc/device-tree no such file or directory.
why i have these errors in my recovery, is the GPS problem related with this issue?
I tried everything that i know: rooted my device, backed up the EFS folder, used this thread and flashed my phone via TWRP, did a fully nand wipe (EFS included) without solving anything.
https://forum.xda-developers.com/ga...1ara2-devbase-v5-0-encryption-t3752964/page61
I did a full nand wipe a lot of times, i also used a PIT file to rebuild the entire partitions, but something else still missing , my knowledge about this specific issue is very basic at this point.
Click to expand...
Click to collapse
Those errors are ok. It at least are on us snap dragon models. Some ones flashed as us based csc on it. This is not related to GPS. Do not worry about them leave it be.
I see you say GPS isn't working correctly. Which tells me it is just not good. Is this a correct assumption
TheMadScientist said:
Those errors are ok. It at least are on us snap dragon models. Some ones flashed as us based csc on it. This is not related to GPS. Do not worry about them leave it be.
I see you say GPS isn't working correctly. Which tells me it is just not good. Is this a correct assumption
Click to expand...
Click to collapse
well, it´s a akward situation because the GPS troubles started when i flashed a diferent rom that was not released in my country, mine is TPH, i flashed a unlocked firmware from Germany, but i did mess because put the second CSC file (that is used to keep personal data untouched) in the userdata tab in odin. :/
thanks a lot man
I have a Samsung Galaxy Note 10.1 GT-N8010. One day it suddenly stopped booting Android and wouldn't pass the first screen (it didn't even reach the one with only the Samsung logo, only the one that says "Samsung GALAXY Note 10.1"). I booted into recovery mode and tried to factory reset, but I got this error: "E:failed to mount /efs (invalid argument)." So I followed this guide: https://forum.xda-developers.com/t/how-to-fix-e-failed-to-mount-efs-invalid-argument.2858056/
Here is where the problem begins. When I rooted to remove the factory mode (just following the guide), I did it using CF-Auto Root. But then my tablet stopped booting to Android (again, not passing the first screen), and when I try to boot into recovery mode, the CF-Auto Root screen boots instead (even after flashing stock firmware and TWRP). On this screen, it says the following:
CF-Auto-Root
Copyright (C) 2011-2016 Chainfire
Detecting devices . . .
- Recovery: /dev/block/mmcblk0p6
- System: /dev/block/mmcblk0p9
- Cache: /dev/block/mmcblk0p8
Preparing cache . . .
Mounting . . .
- System
- Cache
Rooting (SuperSU) . . .
Restoring stock recovery . . .
Cleaning up . . .
Rebooting in 10 seconds . . .
Then nothing happens. It still doesn't boot into Android, and if I try to access recovery mode, I get to the same CF-Auto Root screen. I can only access Download Mode, but I don't know what to flash to solve the problem. As I said, I tried flashing the stock firmware and TWRP (when I did that, Odin said PASS!).
I have been using Odin 3.10 and flashing this firmware https://sfirmware.com/es/samsung-gt-n8010/ (ARO). I also tried with a firmware downloaded through Frija (probably the same one).
I think that's everything. If I missed any information, please let me know.
Any help is welcome!
Thanks,
Whilz.
Good afternoon. I cannot guarantee that this will help you, as I have not encountered this problem and have not used these instructions. But maybe this will help you.
I found these instructions on the russian forum of the platform our devices are built on (n80**, i9300, etc.)
I will give the translation in this post and links to the original posts.
Spoiler: E:failed to mount /efs (Invalid argument) and how to deal with it!
Original post: https://4pda.to/forum/index.php?showtopic=514244&st=0#entry26179020
According to the instructions, you need to flash I9300_Repair_efs.tar.zip efs image via Odin3. IMEI and S/N will be lost, so you will have to think about restoring it.
Spoiler: Error "E: unable to mount /efs (Invalid argument)" or "failed to mount /efs..."
Original: https://4pda.to/forum/index.php?showtopic=514244&st=0#entry24433995
Attention! This method will not raise IMEI and S / N without efs backup. If you do not have it, then you can only download your phone, but there will be no network.
Tested on SGS III
1. If you currently do not have root rights, then download them from the link from the topic header, the version for installation via Odin, install.
2. Download Custom recovery. Also versions for Odin (.tar.md5), install.
3. Download AROMA Filemanager
4. Install the File Manager through the recovery as a normal update.
5. Run the built-in terminal File Manager (press menu / select "open console" or "terminal" from the list).
6. We write commands (after each enter - input):
mke2fs /dev/block/mmcblk0p3
mount -w -t ext4 /dev/block/mmcblk0p3 /efs
reboot
The commands are taken here - http://forum.xda-developers.com/showthread.php?t=1896470
7. Reboot into the system (reboot system now).
8. We read the instructions for restoring efs (who did what) and restore.
If during loading we see a translucent pop-up window with yellow inscriptions on the desktop
then we decide like this - Club of Samsung Galaxy S III lovers (Post # 16738476)
Spoiler: Problem Solution: failed to mount /... (Invalid argument)
Original: https://4pda.to/forum/index.php?showtopic=343514&st=8900#entry38837011
There's quite a lot of information here that I'm not moving here. Perhaps you can learn something for yourself by translating the page into the right language.