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.
Related
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.
Ok here is the story about a year ago I rooted my AT&T GS3 installing CWM and Cyanogenmod. I hadn't had an issue until mid-september. For some reason one of the updates caused certain phone functions to quit working, specifically my mobile data. I searched around on the internet and found out that it had probably affected my modem files, and was told to flash back to stock and that that should solve it. I found a stock firmware file and flashed it with odin. When my phone rebooted it boots to the point of the samsung emblem with the oscillating blue background and just sits there. I tried flashing different versions of the firmware to the same result. I later learned I probably flashed just the modem which I found while trying to solve the problem. When I boot into stock recovery i receive the following message:
E:failed to mount/data (Invalid argument)
can't mount '/data' (Invalid argument)
# MANUAL MODE #
-- Appling Multi-CSC...
Applied the CSC-code : ATT
Successfully applied multi-CSC
E:failed to mount/data (Invalid argument)
can't mount '/data' (Invalid argument)
E:failed to mount/data (Invalid argument)
Anything will help because I am currently without a phone so.... thanks
Edit 1: The Firmware I attempted to flash came from samsung-updates.com though I am not sure of what build and can't check since it won't boot all the way
What firmware build are you on?
Sent from my SAMSUNG-SGH-I747 using Tapatalk
I cannot tell what build, I got it from samsung-updates.com in a zip titled ATT-I747UCDLK3-201211116120549
I would download it again in case it was somehow corrupted. The build is in the filename, LK3, which appears to be 4.1.1. I would say to try 4.1.2 instead, but it appears that wasn't released by AT&T either.
Or if you want you can try flashing the root66 firmware instead. It's LK3 too, only pre-rooted. It's in this thread: http://forum.xda-developers.com/showthread.php?t=1739426
Either way, redownload and try flashing again. Then boot recovery and factory reset. (Will wipe internal sd)
If it still won't mount /data, try flashing Twrp recovery and factory reset. (Will not wipe internal sd unless you choose advanced > Format /data.)
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Thank you so much! I ended up having to flash twrp but when I did what you said it booted just fine. Now the only question remaining is do I try to go back to cyanogenmod?
Since you have TWRP working, copy CM11 to your phone, boot to twrp, and flash CM11. If CM11 does't boot, try wiping data, cache, and dalvik.
Just remember, anytime you go between different based roms, such as TW and CM, you have to factory reset or it'll hang during boot.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Hi all,
After spending all my morning looking at various solutions I've resulted in opening a new thread.
I was trying to install a stock rom this morning however was stuck in a bootloop on the LG logo.
Trying to go back into recovery resulted in a black screen after the TWRP logo.
I was attempting to re-install TWRP to see if that would fix the problem however I only managed to get into Download Mode (is this the same screen as the Bootloader?) and adb/fastboot couldn't find the device.
Magically, TWRP boots up now however in the log it states the following:
Code:
E: Could not mount /data and unable to find crypto footer.
E: Unable to mount /data
E: Unable to recreate /data/media folder
E: Unable to mount storage
E: Unable to mount /data/media during GUI startup
E: Unable to mount /data/media/TWRP/.twrps when trying to read settings file
If anyone can point me in the right direction in how to resolve this I would be grateful.
Regards,
Ash
AshleyNG2 said:
Hi all,
After spending all my morning looking at various solutions I've resulted in opening a new thread.
I was trying to install a stock rom this morning however was stuck in a bootloop on the LG logo.
Trying to go back into recovery resulted in a black screen after the TWRP logo.
I was attempting to re-install TWRP to see if that would fix the problem however I only managed to get into Download Mode (is this the same screen as the Bootloader?) and adb/fastboot couldn't find the device.
Magically, TWRP boots up now however in the log it states the following:
Code:
E: Could not mount /data and unable to find crypto footer.
E: Unable to mount /data
E: Unable to recreate /data/media folder
E: Unable to mount storage
E: Unable to mount /data/media during GUI startup
E: Unable to mount /data/media/TWRP/.twrps when trying to read settings file
If anyone can point me in the right direction in how to resolve this I would be grateful.
Regards,
Ash
Click to expand...
Click to collapse
Looks like you trying to install stock Rom, Given the account you used a flashable zip. It didnt install all the way. and now your stuck with a messed up unstable device......
If you can get into TWRP, wipe everything at least 2 times.. Then install a Flashable ROM/gapps ect..
If you cant get into TWRP and only into Download mode.. Then you will have to flash stock kdz file...............
you can find all types of guides on that around here............
Eliminater74 said:
Looks like you trying to install stock Rom, Given the account you used a flashable zip. It didnt install all the way. and now your stuck with a messed up unstable device......
Click to expand...
Click to collapse
Thanks for your response, once I got into TWRP I couldn't wipe anything as it couldn't mount any partition nor could I flash anything from the external sd.
When I plugged it in there was no internal memory so I decided to use the TOT restore method to go back to stock which was successful and now I've got my custom stock rom back on.
Hi Guys,
i flashed my phone with Cyanogenmod a few month ago and everything worked
fine. But when i start the phone now, its stuck on cyanogenmod boot logo.
Safestrap 4.01 ( TWRP v2.7.1.0)
I can get into safestrap but i cant install, restore or flash a new rom.
It seems like i cant write on the internal memory anymore.
Error:
E: unable to mount /datamedia
E:unable to mount /data
E:unable to mount internal storage
E: unable to mount datamedia/media/0/ during gui startup
E: unable to mount datamedia/media/0/TRWP/.twrps when trying to read settings file.
Any Idea what i have to do?
I have the same problem
Firephony said:
i flashed my phone with Cyanogenmod a few month ago and everything worked
fine. But when i start the phone now, its stuck on cyanogenmod boot logo.
Click to expand...
Click to collapse
I am not shure, that the root is the same, but I got stuck the same after updating from my original CM from 2016-2 to any newer version.
In my case a swipe (reset to factory defaults) in safestrap helped.
Good luck
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.