Hi, yesterday I was using my S2 and I turned it off, then when I turned back I had a bootloop, and restarting in recovery I have error "E: / Failed to mount / efs (invalid argument)." I saw other topics with the same error, but my problem is that it needs adb, but my S2 has a problem with the USB port, so every time I connect it to the PC I have "Unknown USB device" and adb does not recognize it. I flashed a TWRP signed, and I have also file a CWM, then I have two recovery. There is no way to solve only by recovery? I have backup of my EFS folder.
If you have a backup of your efs folder flash aroma file manager and copy the backup of efs folder to /efs
Related
Hello,
I ran into some issues after installing the Classic Jewel V0.0.4 Rom that ultimately led to my internal SD card not being recognized or not mounted properly. For the record, I am not blaming the ROM nor am I suggesting that there is anything wrong with the ROM.
Below is the sequence of events:
1. Full wipe of everything except SD card.
2. Flashed the ROM.
3. The Phone booted all the way to the setup wizard but then rebooted.
4. Phone went into a bootloop.
5. Re-flashed the ROM without wiping.
6. The Phone won't get pass the HTC logo screen.
7. I went in recovery and wiped everything and Flashed Fresh's rom / this did not work.
8. I flashed maybe two other ROMS and still not working.
9. I went into bootloader and did a factory reset (I think this may have been my downfall)
10. The internal SD card is not mounted (or not mounted properly) in Recovery. (I can see the SD card, and see the TWRP folder but nothing else.)
11. Flashing any ROM fails. I see several lines of this error: "E:failed to mount /sdcard (invalid argument)"
12. I tried to do a restore but the file is not there (I guess it's because the internal SD card is acting up?)
Any ideas on how I can fix this?
----------------
Edit:
Here are some more errors that I see while in Recovery
E:failed to mount /sdcard (invalid argument)
E:failed to mount /sdcard (invalid argument)
E:failed to mount /sdcard (invalid argument)
E:failed to mount /sdcard (invalid argument)
E:failed to mount /sdcard (invalid argument)
E:unable to mount /sdcard during GUI startup.
*Verifying filesystems...
*Verifying partition sizes...
E:unable to mount /sdcard
E:unable to mount /sdcard
Running boot script...
Finished running boot script.
E:failed to mount /sdcard (invalid argument)
E:failed to mount /sdcard (invalid argument)
E:unable to mount /sdcard
E:failed to mount /sdcard (invalid argument)
-----------------
Thanks,
Aloupha
I think my problem could be fixed by doing something similar to what's discussed in this thread... but I have no clue on what to do.
http://forum.xda-developers.com/showthread.php?t=1526912
Stab in the dark but can you get Windows to recognize the sd while in recovery? If so open cmd prompt and type chkdsk /X /F <SD card drive letter> and see if it repairs it......just a thought
Sent from my Transformer Prime TF201 using Tapatalk 2
The problem is gone!
The strangest thing happened. I kept flashing roms and they kept failing. Eventually, I tried flashing the MeanRom and it flashed successfully.
I am not sure how that was possible but I am happy! I lost some most of files I had in the Internal SD card though but that's okay!
I am going to install the Classic Jewel rom again and see if the same thing happen again.
I know this thread is a little old but i didn't find much else on this issue. I followed these steps to get a ROM loaded back on my phone
ROM update without SDcard
If you don't have an sd card, or your slot is broken you can try this trick, but you will need a custom recovery like Clockwork.
Boot up your phone to recovery. And move your rom file to the adb directory, and start a command line ( cmd )
adb shell
mount data
adb push D:\custom_rom.zip /data/
Wait until the push finised, and restart your device to recovery again with "adb reboot-bootloader"
mount data
mount /data /sdcard ( mount the data folder into your sdcard folder, so your recovery will think that you have an sdcard installed )
Locate the ROM .Zip file you wish to flash.
Confirm the flash by following the on-screen instructions (ie: pressing the trackball, pressing the call button, etc.)
If no errors arise during the flashing process then the ROM flash was successful, Reboot the device.
With some root file explorer, remove the rom file if you don't need it anymore, to free up space.
Or use adb to remove the custom recovery
adb shell rm data/custom_rom.zip
I am still trying to figure out whats going on with my internal SD I will post if i find a solution.
Do not use clockwork recovery.
Sent from my EVO using xda premium
Okay so last night I attempted to root my nook tablet 1.4.3 using this guide http://forum.xda-developers.com/showthread.php?t=2037368. I downloaded all the files that were pointed to in that thread, and followed the instructions. Everything went perfect and soon I was setting up my google account, then following the final steps which involved downloading rom manager, and goo manager. All was well, until I decided to reboot the tablet.
After I rebooted the initial loading seemed fine (got the "n" screen"), then cyanobootloader popped up, then the Team B presents XDA logo popped up and then nothing. The tablet stayed frozen on the Team B logo, and rebooting did nothing.
So being the idiot that I am, I tried going into recovery from the cyanobootloder. This took me to TWRP where my dumbass ended up going to advanced and Wiping the system. After that I tried installing Cm-7-Team-B-Beata1-signed.zip and gapps-gb-20110828-signed.zip from TWRP. The log gives several messages that read:
E: Unable to mount /system
E: Unable to mount /data
E: Unable to mount /cache
E: Unable to mount /emmc
E: Unable to mount /emmc
E: failed to mount /emmc (No such File or directory exist)
E: failed to mount /emmc (No such File or directory exist)
E: failed to mount /emmc (No such File or directory exist)
At this point I was freaking out, stopped using my head, and began trying desperately to go back to stock. I tried using this method http://raywaldo.com/2012/06/how-to-un-brick-a-nook-tablet-8gb-or-16gb/, but it didn't change anything.
I decided then to try redoing the rooting guide again to see if that could solve the problem. It did not.
So now the tablet boots into TWRP when I turn it on. I can also enter CWM-based Recovery using the SD card I made from the guide. However, when I enter CWM-based-recovery I get these messages at the bottom:
E: Can't Mount /cache/recovery/command
E: Can't Mount /cache/recovery/log
E: Can't Open /cache/recovery/log
E: Can't Mount /cache/recovery/last_log
E: Can't Open /cache/recovery/last_log
That's pretty much where I'm stuck on at the moment. I figured I should probably stop messing with this tablet before I made a bigger mess.
Any help would be greatly appreciated.
I'd suggest that you try flashing afresh a CM10 or CM10.1 build using SDcard based CWM recovery, using a method such as described at http://forum.xda-developers.com/showthread.php?t=2056626.
In case you're considering using one of the so-called "unbricking" tools, read this post http://forum.xda-developers.com/showpost.php?p=37515697&postcount=31 first before you pick the wrong tool that would permanently wipe out your NT's individual device specific data like WiFi MAC address, security certificate, serial number, etc.
Nook needs a /recovery folder in /cache partition like /cache/recovery.
Somehow that folder is missing
Is so easy to fix that you will laugh
dd zero the cache partition after you make sure cwm/twrp is not have it mounted check by reading mount /cache if it says unmount cache select it first.
Then format cache in cwm/twrp and that's it. Folder will be created by it self and that error print out will stop.
Here it is
http://forum.xda-developers.com/showthread.php?t=2179403
My i9300 got stuck in boot screen after I activated Link2sd with a newly repartitioned extsd. I made the first partition FAT32, the second EXT4.
I've got a cwm backup from before I repartitioned ext.sd
I've also got a 'efs.tar.gz file', which I found in the copy of my ext.sd. I assume this is a backup of efs/imei?
Before each operation I've done since I've wiped dalvic cache, wiped cache partition and factory reset.
I repartitioned my ext.sd to one FAT32 partition.
I have tried to restore my cwm backup, everything looked good, but when rebooting the problem was still there.
I flashed a couple of different roms and kernels, they seemed successful, the boot screen changed as expected, problem still there.
Then flashed 'CF-Auto-Root-m0-m0xx-gti9300' with Odin downloader, got a "PASS", problem not solved.
I can still boot into recovery, which changed to stock as expected, and I can boot into download mode.
I've also tried to boot without any ext.sd or SIM inserted, nothing changed.
The recovery gives me this message:
E:failed to mount /efs (invalid argument)
E:failed to mount /efs (invalid argument)
# MANUAL MODE #
---Appling Multi-CSC…
Applied the CSC-code : unknown
Successfully applied multi-CSC.
I take it my /efs is damaged and needs to be restored? Can I restore it from 'efs.tar.gz file' while only being able to enter recovery and download mode? With Odin, or some other software?
I've read someone managed to fix their efs-folder by extracting their efs.tar.gz, and then manually paste the files in place of the efs-folders contents, but then I would need to access my phones internal sd. Is that doable without booting the system?
Couldn't find a solution anywhere, any help is much appreciated!
UNDERSTAND FIRST
http://forum.xda-developers.com/showthread.php?t=2362743
Network IMEI EFS
http://forum.xda-developers.com/showthread.php?t=2393289
Downgrade and network problems .
http://forum.xda-developers.com/showthread.php?t=2531221
Mod Edit
Check the links in the above post.
Thread closed
malybru
Forum Moderator
Hello,
First of all, my english isn't very good.
Ok, I have a huge problem with my lenovo k3 note, I was listening to music yesterday and suddenly it stopped. I tried to unlock, restart itp but nothing. Finally I took off the battery and they restarted the phone, it stopped on Lenovo bootloader, so again battery, restart and this time I went to TWRP recovery. I wanted to restore one of my backups, but there is no backups, internal storage is 0mb, I can't do factory reset, I can't install any zip, nothing. Windows 10 sees just external SD card, no intenal memory.
Entering TWRP makes errors in console like this:
E: Could not mount /data and unable to find crypto footer.
E: Unable to mount '/data'
E: Unable to recreate /data/media folder.
Updating partition details...
E: Unable to mount '/protect_f'
E: Unable to mount '/protect_s'
E: Unable to mount '/cache'
E: Unable to mount '/data'
...done
E: Unable to mount storage.
E: Unable to mount /data/media during GUI startup.
and some more "unable to mount /data".
So I tried to flash original rom with sp flash tool, but on my last rom (MIUI 7 custom) I didn't enable USB debbuging. Every stable ROM or flash tool version I try, every time and the end there is BROM ERROR: S_CHCKSUM_ERROR (1041) and if I boot my phone after such flash it stops on bootloader and in TWRP still internal storage 0mb. I've tried do sth with adb but it doesn't detect my phone, flash tool works though.
I don't know what to do, please guys help me! It's my first android phone and rooting a phone and recovery was a challenge (just installing roms from twrp is very easy) and I really need your help, so please help me.
Thanks in advance and have a good day!
lenovo k3 error 1041
did you solved the problem with lenovo k3? i have the same problem
So I tried playing around with permissions and accidently removed execute permission in the data folder.. The phone is an unlocked verizon and locks up when turned on and stays stuck on the red verizon logo screen. Now I get this error when I tried using android recovery:
E: failed to mount /data (Invalid argument)
can't mount '/data' (Invalid argument)
Odin failed me and so has trying to "apply update from internal storage"
No my dumb but did not put recovery software on my phone.. Ummm Duuuuuh. Well, I am guessing that I need a script to apply from ADB that will fix the permission in the data file to be able to execute. Hoping one of you genius' has the answer. Have never used ADB before but I think it is the only way to fix my phone. Thank you in advance.