Hello everyone:
Making big hands on my bike G I deleted the partitions and then when trying to mount a stock I throw several errors and does not allow installing any version of android. I get a "Failed to mount ..." message in the cache folders, data, system; I also get a message of "Failed to write / dev / block / ....: I / O error"
Can someone tell me "step by step" how to recreate all the partitions (or if they have a much better script) to then be able to mount android lollipop?
I have installed TWRP 3.1.0-0
cealzateg said:
Hello everyone:
Making big hands on my bike G I deleted the partitions and then when trying to mount a stock I throw several errors and does not allow installing any version of android. I get a "Failed to mount ..." message in the cache folders, data, system; I also get a message of "Failed to write / dev / block / ....: I / O error"
Can someone tell me "step by step" how to recreate all the partitions (or if they have a much better script) to then be able to mount android lollipop?
I have installed TWRP 3.1.0-0
Click to expand...
Click to collapse
reflash the stock firmware.
probably your emmc is dead, same thing happened to me
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)
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 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.
Hello guys,
Today I wanted to update my Honor 8 (FDR-L09) because it was showing me, that there is a new update ready to install (FRD-L09C432B405) and I was on a very old firmware (something from mid 2017). So it was time for me to update.
I downloaded the latest update (FRD-L09C432B405) and tried to wipe the cache, dalvik, and Data, but for some reason it "couldn't mount /data" and the wipe failed.
After an advanced wipe it worked and I tried to flash the stock image (the update which was shown to me (FRD-L09C432B405) with TWRP (3.1.1.1.)).
Now my hassle starts:
1. The Rom couldn't get flashed because of "Error: 7" --> I fixed it with the common "Error 7 fix --> editing the update-script and removing the assert line. (And yes, I'm 100% sure that it was the right ROM.
2. Now TWRP seemingly starts to flash the rom but inbetween the lines there is "mountencrypt: failed to mount /data: no such file or directory and it ends with "unknown command [[]" and it takes just two seconds, so the flash obviously isn't succsessfull.
I tried the "failed to mount /data" fix, where I change the data system to ext3 and then back to f2fs and change it back, but it won't work.
In my frustration I did another pretty bad thing and made another advanced wipe and wiped the system too, so now I don't have an OS on my system.
Maybe it's also important to note that there was a window showing up for a very short amount of time, with something like "encryption/encrypted" showed up.
What should I do now? Is there a way to fix the "/data couldn't be mounted" problem? Or am I missing a vital step in flashing the stock rom?
Thanks for your kind help!
You can not flash an update with twrp unless you use hurupdater. You essentially bricked your phone. Look for hurupdater here on xda and follow the instructions and you'll be fine
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.