Hi All
am a new user and i need help ,My GT-N5100 Galaxy Note 8.0 hanging in Samsung logo when i was updating to kitkat and in recovery mode give me E: failed to mount /efs (invalid argument) !!! the problem is that i don't have a backup fro my EFS files
i flashed the last software from samemobile with odin and using firmware upgrade and initialization in kies but still not fixed
do i have any other solutions to try !!
don.sarajevo said:
Hi All
am a new user and i need help ,My GT-N5100 Galaxy Note 8.0 hanging in Samsung logo when i was updating to kitkat and in recovery mode give me E: failed to mount /efs (invalid argument) !!! the problem is that i don't have a backup fro my EFS files
i flashed the last software from samemobile with odin and using firmware upgrade and initialization in kies but still not fixed
do i have any other solutions to try !!
Click to expand...
Click to collapse
you're not alone dude...... i was shoot on my head for 2 weeks ago bout this mess
and the other bad news...i didn't backup my efs.... Lol
I was trying many ways.....and all of nothing in the end !!
even you cannot downgrade or restore your nandroid
I thing the big problem is.... we cannot go anywhere with 4.4.2 bootloader
hope...somebody telling us what we should to do.....something to make our note can make a data connection again.....
plz...help to solving this screw up
Thanx in Advance
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...
Hello all
I was updating my gf phone from rooted UVALJ4 or UVALH2 (Cant remember now, but it was an old Firmware) to root66 T999_UVUENC2 via Odin 3.09 on my Win 7 pc but after the odin install (which passed) I rebooted the phone and I got stuck on the Samsung logo on the start up screen. After about 10 mins I pulled the battery and tried to enter the Recovery mode, but nothing appears. Just a black screen.
So i Odin flashed the TWRP 2.6.3.1 to try to get to a recovery, but that didnt work. Still no Recovery.
I then used odin to flash the stock tmobile UVUENC2 4.3 firmware and it still gets stuck on the Samsung screen.
Next I tried to unbrick it via http://forum.xda-developers.com/showthread.php?t=2439367 using "SGH-T999 4.3 only Debrick Image" and reflashed the stock 4.3 rom, but that didnt work. :crying:
What can I try next? WHat should I do? I can still access download mode, thats about it.
Please help if you can.
Thx
I dont know how but I got the stock recovery to finally appear and now I get these errors (see Pic) what do these mean?
The recovery errors read: E:failed to mount /data ( Invalid argument) can't mount "/data" (invalid argument)
E: Can't mount /data/log/recovery_log.txt
again thx
synplex said:
I dont know how but I got the stock recovery to finally appear and now I get these errors (see Pic) what do these mean?
The recovery errors read: E:failed to mount /data ( Invalid argument) can't mount "/data" (invalid argument)
E: Can't mount /data/log/recovery_log.txt
again thx
Click to expand...
Click to collapse
Never Mind Used Unified Android Toolkit to fix recovery and flash stock rom.
Thank god for that toolkit.
...time to donate
:victory:
Mod Please delete Thread.
Thx
In the future, try a factory reset, almost all boot hangs are solved with this. Happens because of incompatible data between versions, which would make sense condidering the jump you made. Kind of makes sense with the error message too, but I'm not 100% certain there.
Be careful with the toolkit. There is no support for it and it has bricked phones in the past.
Im desperate at this point. when i go into factory recovery i got this message E:FAILED TO MOUNT /EFS (INVALID ARGUMENT). i dont have a back up folder, but my phone reboots fine. but when i connect to wifi it does a fast reboot and turns off the wifi. everything starts when i was running on ROM ViSiON-X N3 INTL. Android L 5.0, and i try to flash dompop v4.3 and i got a failed to flash message.
Hey everyone. My name is antonie and i have a question maybe you can help me with.
When i woke up today my galaxy note 2 was stuck in the boot logo. Now i cant seem to make it work again and when i enter recovery mode it gives lots of errors.
E:failed to mount /cache
E:failed to mount / data
E:failed to mount / cache/ recovery/last recovery
And a few more of those
I took a picture of it with my other phone but cant seem to upload it here.
I will attach my email if you want to have a look at the picture.
Hope you guys can help me cause i really want to keep some of the data on the phone
Thanks
Antonie
[email protected]
Have you tried flashing a stock rom, with and without a pit file?
Antoniekooij said:
Hey everyone. My name is antonie and i have a question maybe you can help me with.
When i woke up today my galaxy note 2 was stuck in the boot logo. Now i cant seem to make it work again and when i enter recovery mode it gives lots of errors.
E:failed to mount /cache
E:failed to mount / data
E:failed to mount / cache/ recovery/last recovery
And a few more of those
I took a picture of it with my other phone but cant seem to upload it here.
I will attach my email if you want to have a look at the picture.
Hope you guys can help me cause i really want to keep some of the data on the phone
Thanks
Antonie
[email protected]
Click to expand...
Click to collapse
visit sammobile.com and dowload firmware related to your model numbe and flash it to your phone via odin
Hello everyone.
I'm not sure what to title this post, as I'm not entirely sure what the problem is.
My S4 Mini (GT-I9190) froze last night while using an app. I pulled the battery out then put it back in. For a few hours, it wouldn't power up at all. It eventually managed to power up, but that's when the real problems started... I cannot remember the exact steps I took towards probably nuking my phone, but right now, the situation is as follows:
I come across the following errors when attempting to do anything:
Failed to mount /cache (Invalid argument)
Failed to mount /data (Invalid argument)
Failed to mount /efs (Invalid argument)
Failed to mount /persist (Invalid argument)
Unable to mount storage
I occasionally get the following error:
E: failed to write /dev/block/mmcblk0p15: I/O error
I was running LineageOS 15.1 before everything blew up, with the latest TWRP recovery, and I have a stock ROM from SamMobile (4.4.2, I believe). I've tried flashing it to my phone, but that doesn't work. No amount of wiping works (though, admittedly, I may be doing it all wrong). I've read around, and my problem is that I don't know where to start, if there is a fix at all. This is my only phone, and I'd like to get it back ASAP.
Thanks.
DolfWick said:
Hello everyone.
I'm not sure what to title this post, as I'm not entirely sure what the problem is.
My S4 Mini (GT-I9190) froze last night while using an app. I pulled the battery out then put it back in. For a few hours, it wouldn't power up at all. It eventually managed to power up, but that's when the real problems started... I cannot remember the exact steps I took towards probably nuking my phone, but right now, the situation is as follows:
I come across the following errors when attempting to do anything:
Failed to mount /cache (Invalid argument)
Failed to mount /data (Invalid argument)
Failed to mount /efs (Invalid argument)
Failed to mount /persist (Invalid argument)
Unable to mount storage
I occasionally get the following error:
E: failed to write /dev/block/mmcblk0p15: I/O error
I was running LineageOS 15.1 before everything blew up, with the latest TWRP recovery, and I have a stock ROM from SamMobile (4.4.2, I believe). I've tried flashing it to my phone, but that doesn't work. No amount of wiping works (though, admittedly, I may be doing it all wrong). I've read around, and my problem is that I don't know where to start, if there is a fix at all. This is my only phone, and I'd like to get it back ASAP.
Thanks.
Click to expand...
Click to collapse
unusual to get all those error messages.
What msg do you get when you try to flash stock?
(edit; suppose you mean same msg when flashing stock also, have you tried with pit file (unseeing full stock rom aka repair)
IronRoo said:
unusual to get all those error messages.
What msg do you get when you try to flash stock?
(edit; suppose you mean same msg when flashing stock also, have you tried with pit file (unseeing full stock rom aka repair)
Click to expand...
Click to collapse
I have not used a pit file. In fact, I know neither what it is nor how to use it. Would you be so kind as to either explain it to me or direct me to a post that discusses it? I believe I have every other file needed to get things going, but nothing I've done works, so this suggestion may help. Thanks.
DolfWick said:
I have not used a pit file. In fact, I know neither what it is nor how to use it. Would you be so kind as to either explain it to me or direct me to a post that discusses it? I believe I have every other file needed to get things going, but nothing I've done works, so this suggestion may help. Thanks.
Click to expand...
Click to collapse
PIT stands for Partition Infrmation Table, flashing with this file (.pit) will repartition your phone. It must be for your exact phone model.