I am running a SM-P600 with Hyperdrive 4.1 and Xluco V3 kernel. I wanted to try out the new V4b3 kernel so i flashed it without any problems. Next i installed Xposed without a problem and flashed Xblast again without a problem. I went into Xblast and enabled the Visual Tweaks/Dark Halo Background. after rebooting the tablet, it started randomly rebooting (alot). so I uninstalled Xblast and rebooted then uninstalled Xposed and rebooted. This time after rebooting i am now stuck on the Hyperdrive bootscreen which i believed was a simple fix.
Boot to TWRP restored my current nandroid, still in bootloop. To make a long story short, i tried all my nandriods without success, fired up Odin v3.09 and flashed back to Stock NK1. Still stuck, but now of coarse stuck in the "Samsung" logo. so i rebooted in to Stock Recovery and "Low & Behold":
E: failed to mount /efs (Invalid argument)
I have been researching and trying to clear this error for about 3 days now. I really thought that flashing stock firmware (NK1 & NK2) made the most sense but i was wrong. Then I found something about using "Fastboot" but it seems that this samsung tablet does not support fastboot (please correct me if i am wrong).
Anyway i am at the point where my options are a complete destruction of the tablet (erase, wipe, format, mount, remount and/or flash) which i am not convinced that it would fix it and i would have an even larger problem.
My thoughts at this point are: this whole thing began with uninstalling Xposed so i would like to think my /EFS folder is probably still there and it just needs to be remounted. After all the googling (mostly smartphones affected by this issue) I have no idea where the SM-P600 /EFS folder should be mounted to (ie mmcblk0p3).
I would really, really appreciate any help, BTW: i do not have a backup of /EFS
I am sorry that this post turned into a novel but it is actually the short version of a 3 day trek of googling for an answer.
I had a similar problem with TWRP not being able to mount partitions, specifically the /data partition. It kept getting stuck at the boot animation. Looking at the partition in TWRP it showed the size of the partition as 0 MB.
Long story short I did about 7 factory resets before I started to get my partitions back. I think I read somewhere that it is a bug in TWRP 2.8.1.0 or something along those lines.
Try using older versions of TWRP.
---------- Post added at 06:16 AM ---------- Previous post was at 06:11 AM ----------
http://www.android.gs/backup-restore-efs-from-any-android-samsung-device/
On the website it said something about downgrading and adding the efs through your computer. Hope is not lost.
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...
Hey guys, I seem to have soft-bricked my AT&T S3.
I was running Paranoidkangdroid 2.32 (based on CM10.1, 4.2.2), but started having some stability issues. Thinking it was time to start fresh with a new ROM, I downloaded SlimKat 4.1 and tried to install it following these instructions.
Upon rebooting, my phone hit the SlimKat loading screen and never finished booting. I rebooted to recovery, and saw errors saying it was unable to mount /cache, /data, and /system. I still have access to recovery and download, and have tried flashing and reflashing a variety of different ROMs, both custom and stock, but haven't been able to get past those errors.
When flashing from recovery, I get errors saying the partitions aren't able to be mounted. I can flash ROMs from Odin, and they do seem to be installing (no errors in Odin, and the Current Binary setting does change depending on whether it is a stock or custom ROM).
Best I can tell, my partitions are screwed up. Any advice on what I did wrong and the best way to proceed? If the partitions are screwed up, is there a way I can rebuild the partitions through the shell?
ericmerl said:
Hey guys, I seem to have soft-bricked my AT&T S3.
I was running Paranoidkangdroid 2.32 (based on CM10.1, 4.2.2), but started having some stability issues. Thinking it was time to start fresh with a new ROM, I downloaded SlimKat 4.1 and tried to install it following these instructions.
Upon rebooting, my phone hit the SlimKat loading screen and never finished booting. I rebooted to recovery, and saw errors saying it was unable to mount /cache, /data, and /system. I still have access to recovery and download, and have tried flashing and reflashing a variety of different ROMs, both custom and stock, but haven't been able to get past those errors.
When flashing from recovery, I get errors saying the partitions aren't able to be mounted. I can flash ROMs from Odin, and they do seem to be installing (no errors in Odin, and the Current Binary setting does change depending on whether it is a stock or custom ROM).
Best I can tell, my partitions are screwed up. Any advice on what I did wrong and the best way to proceed? If the partitions are screwed up, is there a way I can rebuild the partitions through the shell?
Click to expand...
Click to collapse
What stock ROM did you try to flash via Odin and did you get the <PASS> message? If you did, then it would seem the flash was successful. Can you try booting into recovery and doing a hard wipe/reset? Unless your phone has hardware issues, flashing a complete stock image should update all partitions.
Finally, if you were already on Android 4.3, you may try doing a stock restore using the instructions in the following thread ...
http://forum.xda-developers.com/showthread.php?t=2658486
Stock ROMs
Larry2999 said:
What stock ROM did you try to flash via Odin and did you get the <PASS> message? If you did, then it would seem the flash was successful. Can you try booting into recovery and doing a hard wipe/reset? Unless your phone has hardware issues, flashing a complete stock image should update all partitions.
Finally, if you were already on Android 4.3, you may try doing a stock restore using the instructions in the following thread ...
http://forum.xda-developers.com/showthread.php?t=2658486
Click to expand...
Click to collapse
The ROM I had previously installed was based on 4.2.2, so I'm not sure the instructions in that thread will apply...
I have tried installing the UCDLK3 ROM, as well as a couple of custom ROMs. I'm about to try another stock ROM (UCALEM), and will report back with the results in a few minutes.
ericmerl said:
The ROM I had previously installed was based on 4.2.2, so I'm not sure the instructions in that thread will apply...
I have tried installing the UCDLK3 ROM, as well as a couple of custom ROMs. I'm about to try another stock ROM (UCALEM), and will report back with the results in a few minutes.
Click to expand...
Click to collapse
Sad times.
I just tried installing the UCALEM stock ROM with Odin. Everything seemed to go well, and it finished with no errors and a "PASS!" result.
When my phone rebooted, a screen briefly popped up with red text. It didn't stay up long, but the errors I saw were similar to what I had seen before (unable to mount, etc.). The background was the red exclamation with the android robot lying down. The phone quickly rebooted, and sat with a black screen. When I pulled the battery out and powered it back on, it tried to enter recovery mode on its own, but only flashed the Samsung Galaxy S3 screen and remained on a black screen.
I can still access download mode, and the Current Binary now reads "Samsung Official." My phone did this same thing earlier when I flashed another stock ROM, and I was able to get back to recovery mode by flashing a fresh instance of CWM.
ericmerl said:
Sad times.
I just tried installing the UCALEM stock ROM with Odin. Everything seemed to go well, and it finished with no errors and a "PASS!" result.
When my phone rebooted, a screen briefly popped up with red text. It didn't stay up long, but the errors I saw were similar to what I had seen before (unable to mount, etc.). The background was the red exclamation with the android robot lying down. The phone quickly rebooted, and sat with a black screen. When I pulled the battery out and powered it back on, it tried to enter recovery mode on its own, but only flashed the Samsung Galaxy S3 screen and remained on a black screen.
I can still access download mode, and the Current Binary now reads "Samsung Official." My phone did this same thing earlier when I flashed another stock ROM, and I was able to get back to recovery mode by flashing a fresh instance of CWM.
Click to expand...
Click to collapse
To follow up again, I was able to re-flash TWRP using Odin. Once that was done, the phone no longer tried to boot straight to recovery. I was able to three finger into TWRP, though it took a super long time for it to boot.
Here's the console log taken from TWRP once it boots:
Code:
E:Could not mount /data and unable to find crypto folder.
E:Unable to mount '/data'
E:Unable to recreate /data/media folder.
Updating partition details...
E:Unable to mount '/system'
E:Unable to mount '/data'
E:Unable to mount '/cache'
E:Unable to mount internal storage.
E:Unable to mount /data/media during GUI startup.
E:Unable to mount '/cache'
Full SELinux support is present.
E:Unable to mount '/cache'
Running boot script...
Finished running boot script.
E:Unable to mount '/cache'
E:Unable to mount /data/media/TWRP/.twrps when trying to read settings file
E:Unable to mount '/data'
This happened a few days ago. So first of all what happened was before I went to sleep my phone rebooted by itself for no reason which I thought that maybe my phone died,But the next morning i woke up to a samsung logo on my phone (not blinking) which I thought was rebooting again, but it wasnt booting into the OS. Im running dirty unicorn 4.4.4 (final ver) and the unicorn booting animation wasnt showing up. Before I try to boot/go into recovery/bootloader there is a red blink ( not too sure if that was always there) and I am able to access my recovery and bootloader. I checked my recovery log and it says the following:
E:unable to find partition size for '/boot' '/recovery' '/modem'
E:unable to mount '/efs' '/cache' '/system' '/data' storage /data/media during GUI startup
E:Failed to get default contexts and file mode for storage files
So seeing this I tried going into my bootloader which I was successfully able to go. Therefore I tried flashing stock through odin and resulted in failing or just freezing. *Had notes about being unable to write
I had this phone for 2 years without any problems and I'm with Rogers. Has anyone else gone through this or know a solution?
A similar thing happened to me recently. The battery was part of the problem I believe (for 2 of my Note 2s), as it wasn't holding a charge properly (this was causing problems from charging, to regular freezes, reboots). Finally, the last time the phone just got stuck on the samsung boot logo. By then, I had my new battery, so I swapped that in - but that didn't fix the problem. I booted into Philz recovery and saw the same error messages as you. I wiped dalvik cache 3 times, factory reset, and reset for installation of new rom (which still gave me the same error messages and something about unable to format E. Despite the error message, I proceeded to reinstall the custom Rom (Ditto Note 3) again from an external SD card. Everything loaded up like normal. SMS, chat records, contacts were all in tact (like a dirty flash). That said my wifi was having issues - so I ended up redoing the aforementioned process (clear cache, factory reset, reset for installation of new rom). This time no messages about the E: location. Installation was fresh and all content was wiped clean. The wifi issue was still occurring - but it turned out I just needed to install the AGNI kernal again.
Good luck
Note2Hunter said:
This happened a few days ago. So first of all what happened was before I went to sleep my phone rebooted by itself for no reason which I thought that maybe my phone died,But the next morning i woke up to a samsung logo on my phone (not blinking) which I thought was rebooting again, but it wasnt booting into the OS. Im running dirty unicorn 4.4.4 (final ver) and the unicorn booting animation wasnt showing up. Before I try to boot/go into recovery/bootloader there is a red blink ( not too sure if that was always there) and I am able to access my recovery and bootloader. I checked my recovery log and it says the following:
E:unable to find partition size for '/boot' '/recovery' '/modem'
E:unable to mount '/efs' '/cache' '/system' '/data' storage /data/media during GUI startup
E:Failed to get default contexts and file mode for storage files
So seeing this I tried going into my bootloader which I was successfully able to go. Therefore I tried flashing stock through odin and resulted in failing or just freezing. *Had notes about being unable to write
I had this phone for 2 years without any problems and I'm with Rogers. Has anyone else gone through this or know a solution?
Click to expand...
Click to collapse
jun3280 said:
A similar thing happened to me recently. The battery was part of the problem I believe (for 2 of my Note 2s), as it wasn't holding a charge properly (this was causing problems from charging, to regular freezes, reboots). Finally, the last time the phone just got stuck on the samsung boot logo. By then, I had my new battery, so I swapped that in - but that didn't fix the problem. I booted into Philz recovery and saw the same error messages as you. I wiped dalvik cache 3 times, factory reset, and reset for installation of new rom (which still gave me the same error messages and something about unable to format E. Despite the error message, I proceeded to reinstall the custom Rom (Ditto Note 3) again from an external SD card. Everything loaded up like normal. SMS, chat records, contacts were all in tact (like a dirty flash). That said my wifi was having issues - so I ended up redoing the aforementioned process (clear cache, factory reset, reset for installation of new rom). This time no messages about the E: location. Installation was fresh and all content was wiped clean. The wifi issue was still occurring - but it turned out I just needed to install the AGNI kernal again.
Good luck
Click to expand...
Click to collapse
So did you install it using an external sdcard?
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
Hi there, so I'm having a bit of a problem. I tried to revive my old M9. I remember flashing it with a custom ROM (Android HD Revolution) and everything was fine. I left it since I got a new phone and today wanted to play around with my M9 again.
However, it would be stuck with the HTC Logo while loading, and my TWRP was gone, could no longer boot into it and my download mode was also screwed, as it gave me the error (failed to boot to download mode).
Anyway so I tried restoring to one of my TWRP backups, by mounting a TWRP img file first using my PC. It went fine, after that I booted into system and the HTC logo would be on white background and preventing me from using the screen, although funnily enough the system was functionally normally i.e. the volume keys worked and I could see it change on screen but, it was just as if I had a some kind of overlay and couldn't use the screen itself by touching.
I then tried to flash with the same custom ROM, but after installing it and rebooting the phone it was stuck in a boot loop, where it would shutdown and try to boot again.
So I turned it off using power up and home button, and tried to wipe the partition to install another ROM, using the same TWRP method I did above.
Only this time, I can't do anything: wipe, install, format etc. I get the error "Failed to mount '/data' (Invalid Argument)" "Failed to mount '/cache' (Invalid Argument)" whenever I try doing anything within TWRP. I can't even mount cache, system or Data. It is if they're not there.
And now my phone is back to where it started, i.e. infinite boot screen with HTC Logo and "This build is for etc..." text.
Note: Trying to change file system from ext4 to ext2/3 and back to ext4 does not fix the problem ,as the same errors pop up when trying to change file system.
90% chance the nand is goosed. 10% chance of recovering by flashing a stock firmware in download mode (same version as currently installed, external sd card method).
Twrp has a known issue for bricking devices at random.