[Q] my galaxy sl i9003 stuck at the boot logo after rooting - Samsung Galaxy SL i9003

i've roooted my galaxy sl for the first time and after rooting my mobile is stuck at the boot menu....
i can't wipe data/factory reset and wipe cache partition
i can't install my remicsv1.7 too....
it displays the same error in recovery mode is:
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
plz give me a solution to install remics1.7...

Flash through odin:thumbup:

Related

[Q] CWM problem, please help!

Whenever I go into recovery mode I get these errors right away:
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
This hasn't seemed to affect my device at all in fact my device is working better than normal, so my question to you is is this a problem worth fixing as I don't want to reflash anything or should I just not worry about it.
Thanks,
P2K

[Q] Save dead ZTE V985

Hi,
After attempt to update my ZTE V985 from Android 4.0.4 to 4.1.2 I ended with device that goes only to recovery and prints the following:
"E:Can't mount /cache/recovery/command
E:Can't open /dev/block/platform/sdhci-tegra.3/by-name/MSC
(No such file or directory)
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
E:Can't open /dev/block/platform/sdhci-tegra.3/by-name/MSC
(No such file or directory)"
I tried with "adb sideload" but can't succeed with the ROM that I have. Does it have to be special recovery image ?
Is there any chance to bring it back to life the phone ?
Freezes at boot
LamqtaSpas said:
Hi,
After attempt to update my ZTE V985 from Android 4.0.4 to 4.1.2 I ended with device that goes only to recovery and prints the following:
"E:Can't mount /cache/recovery/command
E:Can't open /dev/block/platform/sdhci-tegra.3/by-name/MSC
(No such file or directory)
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
E:Can't open /dev/block/platform/sdhci-tegra.3/by-name/MSC
(No such file or directory)"
I tried with "adb sideload" but can't succeed with the ROM that I have. Does it have to be special recovery image ?
Is there any chance to bring it back to life the phone ?
Click to expand...
Click to collapse
I have a zte v985 phone that freezes at boot time, the start animation runs and suddenly stops there.
My mistake was to flash a rom without erasing the user data. I want to repair it but I don't know a
procedure for my specific situation, I'm curious about "adb sideload", is there a way to use it with my phone?
or is there any other way to set it into recovery mode manually?
Any help will be appreciated. Thank you.
your phone's recovery is not the correct version,you can use the tool called "v985flash" to flash a correct recovery.

[Q] E: Can't mount/open cache...

Using Galaxy Tab 2 P5100. What is that???
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
I have stock kernel and CWM recovery.
Tried to restore stock Rom with Odin and it always Fail to write cache. Tryed CyanogenMod too. Someone can helpme?
EDIT: While formating data or cache it just stuck formating cache.
Nobody can helpme?
isaacbf said:
Nobody can helpme?
Click to expand...
Click to collapse
Try this:
Boot into recovery.
> Wipe and Format Options > Custom Format Options > format /cache

[q] android stuck at boot logo

my android is stuck at boot logo ,its also shows this when i boot into recovery , it shows these messages when i boot into recovery it shows these messages the screen stuck on boot logo....
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
Cooperamiski said:
my android is stuck at boot logo ,its also shows this when i boot into recovery , it shows these messages when i boot into recovery it shows these messages the screen stuck on boot logo....
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
Click to expand...
Click to collapse
What phone are you using?
Flash a new stock rom in your phone.
Press thanks if help.
AzrulHisyam said:
What phone are you using?
Click to expand...
Click to collapse
my phone is a chinese mobile called tecno n7 which have same builds as iris lava 501
Just downlaod a stock rom of your phone and flash it
KAUSHDROID said:
Flash a new stock rom in your phone.
Press thanks if help.
Click to expand...
Click to collapse
My phone wont boot , its stuck at the boot logo ,when i boot into cwm recovery too these errors pup up
cwm automade 21.09.2013 23:20:59
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
I tried restoring my stock backup but these showed up
""checking MD5 sums...
Erasing boot before restore ...
Restoring boot image ...
Restoring system...
E:format _volume: make _extf4fs failed on /dev/block/mmcblk0p3
Error While formatting/system!""
mates pls help ...am at newbie with these stuffs.
Deleted

[q] android stuck at boot logo

My android is stuck at the boot logo.... and when i boot into recovery it shows these errors , i cant restore my Rom .
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... i need help asap
Go to fastboot mode, flash a custom recovery then try to reflash your rom or restore it, i don't know which phone are you using but i can help you
I suggest you try flashing a custom rom using your device's specific fastboot mode

Categories

Resources