Hey guys, my s5830i bricked. I can't enter in download mod, just stuck in a black window.
In the normal initialization, stuck in the Samsung logo.
I can enter in the recovery mod, but this message appears just at the beginning:
-- Applying Multi-CSC --
E: failed to mount /system (Invalid argument)
E: failed to mount /system (Invalid argument)
or
-- Install /sdcard ...
Finding update package...
Opening update package...
E: Can't open /sdcard/...
(bad)
Installation aborted.
How I can fix it?
I'm getting crazy, please, help me D:
jappandda said:
Hey guys, my s5830i bricked. I can't enter in download mod, just stuck in a black window.
In the normal initialization, stuck in the Samsung logo.
I can enter in the recovery mod, but this message appears just at the beginning:
-- Applying Multi-CSC --
E: failed to mount /system (Invalid argument)
E: failed to mount /system (Invalid argument)
or
-- Install /sdcard ...
Finding update package...
Opening update package...
E: Can't open /sdcard/...
(bad)
Installation aborted.
How I can fix it?
I'm getting crazy, please, help me D:
Click to expand...
Click to collapse
Wow, that's bad. You could try using USBJig (i think that's the name) so that you could boot into download mode and re-install the stock rom.
jappandda said:
Hey guys, my s5830i bricked. I can't enter in download mod, just stuck in a black window.
In the normal initialization, stuck in the Samsung logo.
I can enter in the recovery mod, but this message appears just at the beginning:
-- Applying Multi-CSC --
E: failed to mount /system (Invalid argument)
E: failed to mount /system (Invalid argument)
or
-- Install /sdcard ...
Finding update package...
Opening update package...
E: Can't open /sdcard/...
(bad)
Installation aborted.
How I can fix it?
I'm getting crazy, please, help me D:
Click to expand...
Click to collapse
When you get the black screen after entering download mode, try just pressing volume up,
and plugging phone into the PC just to see if Odin will recognise it. I had a similar problem
and download mode still worked, but the phones screen remained black.
purgy said:
When you get the black screen after entering download mode, try just pressing volume up,
and plugging phone into the PC just to see if Odin will recognise it. I had a similar problem
and download mode still worked, but the phones screen remained black.
Click to expand...
Click to collapse
I was about to suggest the same this probably happens because files are no longer present on the phone, but the logic behind it works anyway
Related
My phone had a black screen and the buttons on the bottom were lit up. I tried to power it off and it wouldn't. So I pulled the battery and restarted and all it did is go as far as saying Galaxy S cyanogen(mod). I did the 3 finger start and wiped the dalvik, cache and data and tried to reboot and still the same. I tried to use Odin to go back to stock and it failed. I did a search but nothing seemed to apply. Any help would be greatly appreciated. I really don't have the money to buy a new phone. Thank you.
I did some more messing around and found 5 errors when doing the 3 finger start.
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
Also I tried re-installing CWM4 modified for CM7.
Is my phone dead, like cant be recovered dead?
I believe the answers you seek can be found in the stickies.
I used a recovery method in the Dev section and part of how to load a MTD and after all is said and done and trying a few more times I got it fixed. If anyone here has any problems like mine PM me a number to call you and I will walk you through what I did.
I have a GSIII for 2 years now. Everything was working great but 3 months ago it started rebooting and boot looping. Long story short I tried everything I could do to solve the issue (custom ROMs, Dalvic cache clean, system cache clean, new battery, new charger). I even sent it to Samsun g official service but after a few weeks the problem reappeared and after some time the phone was practically unusable. So, in my despiration, I tried some things with Odin that messed up things even more.
Anyways, now, everytime I turn on the phone boot loops and when I enter the Recovery Mode the following message appears:
# MANUAL MODE #
-- Appling Multi-CSC...
Applied the CSC-code : CYO
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
Recovery Mode and Download Mode both work.
SO is there any way that I can save my phone and bring it back to life?!
PLEASE HELP IF YOU CAN
The best shot you have is to flash a stock firmware from sammobile.com be sure to use the latest version of Odin.
Sent from my GT-I9300 using Tapatalk
Your emmc chip is corrupt, probably nand is damaged.
Samsung Galaxy S2 SGH-i777 in infinite boot loop.
When I turn on the phone it proceeds past the Samsung logo screen and after a while ends up at the AT&T Rethink Possible screen where it proceeds to reload that screen over and over again in what appears to be an infinite loop.
When I hold down Vol Up & Vol Down and Power, the phone displays the Samsung logo, appears to power cycle and display the Samsung logo again and appears to enter recovery mode. When the phone enters recovery mode, it displays a number of error/status messages as follows:
E:failed to mount /cache (Unknown error: 0)
E:Can't mount /cache/recovery/command
-- Copying media files...
E:failed to mount /cache (Unknown error: 0)
E:copy_cache_media:Can't mount /cache
your storage not prepared yet, please use UI menu for format and reboot actions.
Meida files copy failed.
# MANUAL MODE #
-- Updating application...
E:failed to mount /data (Unknown error: 0)
E:install_application_for_customer:Can't mount /data
your storage not prepared yet, please use UI menu for format and reboot actions.
copy application failed.
-- Appling Multi-CSC...
Installing Multi-CSC
Can't access to '/system/csc/ATT/system/'.
Successfully applied multi-CSC
E:failed to mount /cache (Unknown error: 0)
E:Can't mount /cache/recovery/recovery_kernel_log
E:copy_kernel_file :: Can't open /cache/recovery/recovery_kernel_log
E:failed to mount /cache (Unknow error: 0)
E:Can't mount /cache/reocvery/log
E:Can't open /cache/recovery/log
E:failed to mount /cache (Unknown error: 0)
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
E:failed to mount /cache (Unknown error: 0)
The above messages don't display at once but seem to display after a few presses of the Vol Up button.
After the error messages have all displayed, I see the following at the top of the screen:
Android system recovery <3e>
Enter: Power Key. Select : Vol UP / Vol Down
reboot system now
apply update from sdcard
wipe data/factory reset
wipe cache parition
BUT even though I can use the Vol buttons to navigate the choices, pressing the power button has no affect to select them.
At the moment, I would just like to get back to a working phone. I have attempted to use Odin to flash the UCKH7 stock rom that I found in this post: http://forum.xda-developers.com/showthread.php?t=1286432. It indicates that it does so successfully but it doesn't change my phone situation.
Because I saw the errors about the various partitions I also though maybe I should try re-partitioning with a PIT file. This was probably not a good idea but I was not aware at the time that it may have been a bad decision.
What should I try to fix this situation and get my phone working again?
Thanks!
I'm assuming you are able to boot the phone into download mode, since you flashed Entropy's UCKH7. I suspect that you have memory corruption, and not memory damage. That old UCKH7 from that thread contains only the system and kernel, and not the other files you need to do a full install, so I'm not surprised it didn't boot.
If you flashed the UCKH7 pit file, it probably didn't do any damage, but it would not clear the corruption by itself.
The first thing I would try is to flash a full stock distribution in Odin, without pit, and see if that clears the problem. You can find the files you need in the Download Repository. See the link in my signature. I would suggest flashing the latest stock firmware full distribution, which is I777UCMD8 (Android 4.1.2 Jelly Bean). It's the next to last item at the bottom of the page. The original UCKH7 Full stock distribution is there also under the heading I777UCKH7-CL503881 Stock Binaries.
If the above does not resolve the issue, all is not lost. Post your results back here and I wil post how to clear the corruption. Good luck.
FIXED!
Yes. You assumed correctly. I suspected (or maybe it was hoped) that it was just memory corruption and not damaged but couldn't find what to do.
After following your advice of downloading the latest stock firmware full distribution and using Odin to flash it.
After flashing and booting, I kept getting stuck at the AT&T logo screen. I booted back into recovery mode and saw that it was still unable to mount the /data partition and it didn't seem to let me wipe the /data partition. I then went through a series of reboots and even re-flashed again. Finally, I entered recovery and got distracted. When I came back to the phone, I discovered I was able to get the power button to select the Wipe Data Partition. I wiped data and cache and then I re-flashed one more time.
After this my phone finally booted all the way.
Thank you so much for your help. It is really appreciated.
hi .
I have a Samsung galaxy note 4 . I hold volume up and power button to enter recovery mode and when I click on reboot system now , after few seconds the red error message "e:failed to mount /data (invalid argument) " appears below but the phone reboots successfully and it works fine again . I did a full factory reset and i get this message again . I want to know why i get this message ? does it have any effect on system performance ? because it was slower than other note 4s from the beginning but not noticeable but after a couple of months of using the phone it sometimes gets so slow and lagging sometimes .
here is attached the screenshot of the error i get second before the phone reboots :
I've tried to flash TWRP today and got stuck in a bootloop. First unlocked oem - success. Downloaded corresponding TWRP version (3.0.2, my WIKO is running Marshmallow 6.0) according to instructions from "https://rootmygalaxy.net/root-wiko-fever-4g-and-install-twrp-recovery/" Then went to flashing Wiko with TWRP through "SP Flash Tool", got green tick (hooray)... and during reboot my phone showed WIKO logo for 2 times, then went into TWRP... and looped, looped, looped.
Screen showes such text:
"Could not mount /data and unable to find crypto footer
Failed to mount '/data' (Invalid argument)
Unable to recreate /data/media folder.
Updating partition details...
Failed to mount '/data' (Invalid argument)
... done
Unable to mount storage
Failed to mount '/data' (Invalid argument)
Full SELinux support is present.
Unable to mount /data/media/TWRP/.twrps
Running Recovery Commands
Formatting Cache using make_ext4fs
Failed to mount '/data' (Invalid argument)
Done processing script file
Renamed stock recovery file in /system to prevent the stock ROM from replacing TWRP.
Failed to mount '/data' (Invalid argument)
Failed to mount '/data' (Invalid argument)" then loops
Since then i waited a few minutes/few reboots to look if it ceases to show up, but it persisted. Since usual holding POWER button for a few seconds didn't worked, as phone was not powering down and still booting into TWRP, I decided to unplug battery for 10 minutes. My WIKO has non-removable batt, but these few screws weren't a big problem, and I managed to unplug it. Sadly, after plugging it back, looping came back too.
Tried to power it back (after another 10 mins unplug) with VOL+ and VOL- to put it into download mode, but it just showed " ==> meta mode" info on left bottom part of the WIKO screen, then screen appeared once again without that info, and looping TWRP came back. Tried it few times, with same result.
Seems that nothing works - any help would be really appreciated
EDIT:
Managed to work around it on my own One thing that still worked good was PWR + VOL+, meaning enter boot menu (Recovery, Fastboot, Normal). When in recovery I was able to use TWRP, and since after unlocking oem my data simply vanished, it was only to decide whether to restore Marshmallow or move to madOS 8.1 https://forum.xda-developers.com/android/development/rom-official-mados-wiko-fever-clones-t3762804 Rest is a history....
Since original thread is closed, I will express my deepest thanks to @DerTeufel1980 for a great, great job doing Oreo8.1 compilaton for Wiko Fever. Working like a charm