HI!
I have an ATT Note 2 that I'm trying to get to work. It's in a boot loop on the ATT logo. While trying a factory reset and cache clear, I discovered that there was an error code in recovery mode: E: failed to mount / efs (invalid argument).
I looked on the internet and found a few potential solutions, so here's what I have done: flashed stock version 4.4.2 and TWRP version 3.0.2-0 onto the phone using Odin 3. I also rooted it by flashing (CF auto root?) as well. I then installed ADB version 1.4.3 onto my PC.
So I put the phone in recovery (TWRP) mode and went into "Mount," then "Mount/System." --and plugged it into the PC USB port. Next, I opened the Command Prompt and input: "adb devices"--perfect, it found the phone and knew it was in recovery mode.
Here's where I ran into trouble. When I input "adb shell," the next line came up, ~ # (backspace symbol)[6n with the cursor blinking next to the "n". That's as far as I have been able to go in the tutorials I have read/watched. I can find nothing about this code I am getting-- what it is, what it means, or what to do about it.
Now I don't know if where I was supposed to be headed would solve my problem but I would sure like to try. And the only way that will happen is if one of you guys either knows what this code is and what to do about it or has another approach to getting my etf files back.
I would appreciate any input you might offer. I want to finish messing with this phone one way or another--my struggling Note 4 is waiting in the wings!:laugh:
Related
Hey guys,
Yesterday I noticed my My Note 8.0 looping on it's bootscreen. The screen was also flickering...
I haven't been able to reboot the device ever since... I have tried al the conventional ways...
First attempt was through stock recovery... it returned a fail error message when I tried to factory reset, wiping cache,... every option available gave some kind of error:
Code:
E: failed to mount /system (Invalid Argument)
can't mount /system (Invalid Argument)
E: failed to mount /data (Invalid Argument)
can't mount /data (Invalid Argument)
Device has always been rooted. I have done this soo many times so I am 100 % positively sure that I didn't do anything that would explicitly cause this kind of error. So I am sure that I didn't remove or alter any files in system or data directory.
But anyways... How can I fix this...
Device doesn't get recognized anymore by my computers...
3vilrabbit said:
Hey guys,
Yesterday I noticed my My Note 8.0 looping on it's bootscreen. The screen was also flickering...
I haven't been able to reboot the device ever since... I have tried al the conventional ways...
First attempt was through stock recovery... it returned a fail error message when I tried to factory reset, wiping cache,... every option available gave some kind of error:
Code:
E: failed to mount /system (Invalid Argument)
can't mount /system (Invalid Argument)
E: failed to mount /data (Invalid Argument)
can't mount /data (Invalid Argument)
Device has always been rooted. I have done this soo many times so I am 100 % positively sure that I didn't do anything that would explicitly cause this kind of error. So I am sure that I didn't remove or alter any files in system or data directory.
But anyways... How can I fix this...
Device doesn't get recognized anymore by my computers...
Click to expand...
Click to collapse
You are rooted but no custom recovery? I take it you do not have nandroid to restore from? I have only had this tablet for a few days but imagine it being Samsung you can Odin back to factory stock if you don't have a backup or flash a stock image from stock recovery: http://forum.xda-developers.com/showthread.php?t=2289441
CCallahan said:
You are rooted but no custom recovery? I take it you do not have nandroid to restore from? I have only had this tablet for a few days but imagine it being Samsung you can Odin back to factory stock if you don't have a backup or flash a stock image from stock recovery: http://forum.xda-developers.com/showthread.php?t=2289441
Click to expand...
Click to collapse
I did have CWM Touch Recovery installed prior to the showing up of this error...
Device doesn't get recognized any more by any computer I own (different OSes, no success on neither one of them...)
3vilrabbit said:
I did have CWM Touch Recovery installed prior to the showing up of this error...
Device doesn't get recognized any more by any computer I own (different OSes, no success on neither one of them...)
Click to expand...
Click to collapse
I was trying to address your issue with it not booting properly. Have you gotten it to boot up? Did you have a backup to restore from in CWM?
As for recognizing on the PC, I'm sure you probably have the correct drivers installed already. I have had the same issue on my S4 and have not found a solution yet so have been using a cloud service or yanking the card out to transfer. Have not tried it with the Note yet.
**Edit....I might add that most will suggest checking the USB cable and trying different USB ports (to get on a different IRQ) but none of this has worked for me in the past. Might be worth trying at least to make sure.
CCallahan said:
I was trying to address your issue with it not booting properly. Have you gotten it to boot up? Did you have a backup to restore from in CWM?
As for recognizing on the PC, I'm sure you probably have the correct drivers installed already. I have had the same issue on my S4 and have not found a solution yet so have been using a cloud service or yanking the card out to transfer. Have not tried it with the Note yet.
**Edit....I might add that most will suggest checking the USB cable and trying different USB ports (to get on a different IRQ) but none of this has worked for me in the past. Might be worth trying at least to make sure.
Click to expand...
Click to collapse
I'm gonna bring it back to the shop and hopefully, if I put up a poker face if they ask me about rooting my device :angel:, they accept it and treat it with warranty
For some reason, I really don't know what I have being trying...my tablet miraculously is working again!
Thread can be closed...
Back story: OTA update to 4.3 killed USB on this phone, so there is no USB access to it - at all. I don't have a Windows computer, so I never downloaded ODIN to root the phone. It is completely stock, other than the unlock code obtained from T-Mobile.
I just switched from T-Mobile to AT&T, and for some reason had no data connection on the phone, even with the correct APN settings. I decided to try a factory reset. I went through the system settings menu and found the "Reset to factory settings" menu item, selected it, acknowledged the warning, input my PIN and let it go to work.
A few minutes later, it had rebooted into recovery. Sicne it was there, I took the opportunity to use the boot-loader's reset function and wiped the cache while I was at it. That was a mistake.
Now, the phone won't boot past the pulsing Samsung logo. I can get back to the recovery, and it pops up these errors - first, the droid on his back with the red triangle over him flashes "No command", and then it dumps me to the recovery menu with this scrolled at the bottom of the screen:
Code:
# MANUAL MODE #
-- Appling Multi-CSC...
Applied the CSC-code : TMB
Successfully applied multi-CSC
E:failed to mount /data (Invalid argument)
can't mount '/data' (Invalid argument)
E:failed to mount /data (Invalid argument)
E:Can't mount /data/log/recovery_log.txt
It's obviously soft bricked. I can't use ODIN to flash anything. But, since I'm at the recovery screen, it is giving me the option of loading an update from external storage - what should I put on the SD card to load in order to fix it? Can I fix it without ODIN?
edit to add:
I've already tried the stock UVUEMJC firmware from DocHoliday77's thread, but it threw a bunch of errors across the screen that I didn't catch in time and rebooted to the same point.
Try @saranhai's StockMod Rom. Put it on the External SD and flash it. If that fails, please post the error log.
On another note. can you try in Recovery and manually mount /Data Partition ?
Perseus71 said:
Try @saranhai's StockMod Rom. Put it on the External SD and flash it. If that fails, please post the error log.
On another note. can you try in Recovery and manually mount /Data Partition ?
Click to expand...
Click to collapse
Stuck @ work today, and I didn't bring it with me. I'll give that a shot when I get home tonight. I don't recall seeing a "mount" option in recovery - it's the stock Samsung recovery, I'm not sure I made that clear in the OP.
My Nexus 5 arrived last night, so this is becoming a project for me. I just want to know if I can make it work, but without USB access to it, that is probably a non-starter.
If you have Stock Rom, there isn't anything you could flash that way. At the most you could flash a Stock firmware via KIES.
I bought a new never used Tab 3 for the intended purpose of using it as a universal remote. I wanted to strip it down and started right away with installing custom recovery, or at least I tried. No matter what I did I was not able to get Odin to properly load TWRP. It went through all the steps but I was not able to get into recovery other than stock.
Fast forward to the next day, I finally get it to work and somewhere in this process I somehow deleted or unmounted (I really am not sure) my efs folder/partition. If I try to reset deleting all cache and wiping everything including pulling the battery for a few minutes and flashing the stock ROM again I get hung up at the "SAMSUNG' logo. I have tried several ROMs and even tried using Odin to flash a new pit file with I found HERE. When I load both the pit file and my ROM into Odin it eventually says 'FAIL'. I can flash ROMs all day with no issue.
I can only assume that the error I am getting in recovery that says E:failed to mount /efs (Invalid argument) is my issue.
Adb is not really an option for me since I have little to none, more like none at all knowledge of using it. I assume since I have flashed several tries that USB Debugging is not enabled anyway and isn't enabling it key to using ADB anyway?
I have been at this for 2 full days searching everywhere and trying everything I see. I am at a loss and hate to think this new Tab is already junk.
Any help would be greatly appreciated!
The EMCC or something like that requires replacement
andynroid said:
The EMCC or something like that requires replacement
Click to expand...
Click to collapse
So I should junk it then? I only paid $80 for this Tab.
One trial you may try to flash a Cyanogenmod based ROM see if it can write out the partitions else if no luck time to replace that item as mentioned
I have tried flashing CM and still the same issues.
I have since found out what my issue is (or at least 99% sure), I somehow wiped out my efs partition completely. So running a new pit file with Odin does nothing because the partition is gone.
This is fixable and easy for someone who knows shell, but I don't. So now I am trying to figure it out. It's a matter of pushing the 6 following files to the phone using the adb push [file] /sbin/ command using adb which I have done, now I need to figure out the rest.
e2fsck
mke2fs
parted
resize2fs
sdparted
tune2fs
T
you can't do that in the way you think, it requires disassembling the recovery image, making modifications and repacking then reflashing the image.
If you are using an older recovery, namely twrp, install a newer recovery , check @nels83 's thread for a "modern" twrp build.
You can also try one of my philz builds.
Being as you have been abusing Odin, you may actually have damaged your tab.
BUT if you are connecting to wifi without a problem then it's unlikely that you have damaged your efs partition. It's more likely an error with the recovery build you are using, probably in the fstab.
m
I have a Verizon Note 2 that rebooted on its own while charging and is now stuck at the startup logo. When you go into recovery mode, it gives several mount issues including failed to mount /cache / system. When I put it into ADB mode and sideload the stock rom, it will upload to the phone and when the phone starts to install it, it gives the failed to mount /cache and it fails. I have put the rom on the sd card and attempted that way but it fails to mount the /sdcard in recovery and doesn’t find it.
I can’t use the adb shell due to the error: closed message and can’t seem to find a fix that gets around that. I’m thinking that the EMMC chip went bad but if so, where is the rom being stored when sideloading? If the partition is bad, how can I fix that?
I will add that I have tried odin but when I click start, it just goes straight to Failed in the status bar.
Are you using the original Samsung cable to flash the phone? The phone appears as a com port in Odin? Tried different USB cables and USB ports? What is the error in the Odin log?
I wanted to revert my mi 10t pro back to stock miui, but as I wanted to wipe the data, but I got errors like "E:Unable to decrypt FBE device. Code: 1000" or "Failed to mount '/metadata' (invalid argument) and some more. I was told to change the file system to EXT2 but this got me into a bootloop, where I land in fastboot every time I restart. I can navigate to recovery again tho.
Please help me. Im a bit desperate right now.
Edit: My recovery is twrp.
Janxr said:
I wanted to revert my mi 10t pro back to stock miui, but as I wanted to wipe the data, but I got errors like "E:Unable to decrypt FBE device. Code: 1000" or "Failed to mount '/metadata' (invalid argument) and some more. I was told to change the file system to EXT2 but this got me into a bootloop, where I land in fastboot every time I restart. I can navigate to recovery again tho.
Please help me. Im a bit desperate right now.
Edit: My recovery is twrp.
Click to expand...
Click to collapse
Just simply download and flash the Apollo's stock Fastboot ROM in fastboot mode
I tried flashing with with this: "apollo_global_images_V13.0.5.0.SJDMIXM_20220704.0000.00_12.0_global_3391fe8ef8"
is that the right version for my phone (bought in Germany)? I dont get an error while flashing but i just is not finishing. Its running for an hour now and still nothing happended. Ill update this if it finishes.
Edit: False alarm: After restarting the pc, i can connect again. But I still dont know what to do now.
I stopped the process after 2 hours and it got worse. In the recovery, i get the same issues as before, but my fastboot menu got replaced by onother one (I just see orange text that says fastboot). With that new fastboot menu I can not connect to my computer anymore.
Solved: I will never touch these Xiaomi tools again. platform-tools is just better and works
How did you solve the problem with the phone that cant connect to pc?