[Q] S3 stuck at splash screen - Galaxy S III Q&A, Help & Troubleshooting

Was charging my phone yesterday went to unplug and phone stuck at splash screen, pulled battery and left for a while on re-insert splash screen appears straight away. Pulled battery overnight and same thing happened.
Phone has been rooted and has latest (i think) CWM (v6.0.4.7) on it, was running CyanogenMod1! which updated yesterday to latest version (nightly 20140311 i think). I can get into recovery but can't install the rom i have on the phone just get the following messages:
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
E: Can't mount /cache/recovery/last_install
E: Can't open /cache/recovery/last_install
Does anyone have any idea how if i can get a working rom back onto the phone
Thanks in Advance

jedathoss said:
Was charging my phone yesterday went to unplug and phone stuck at splash screen, pulled battery and left for a while on re-insert splash screen appears straight away. Pulled battery overnight and same thing happened.
Phone has been rooted and has latest (i think) CWM (v6.0.4.7) on it, was running CyanogenMod1! which updated yesterday to latest version (nightly 20140311 i think). I can get into recovery but can't install the rom i have on the phone just get the following messages:
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
E: Can't mount /cache/recovery/last_install
E: Can't open /cache/recovery/last_install
Does anyone have any idea how if i can get a working rom back onto the phone
Thanks in Advance
Click to expand...
Click to collapse
I had a similar thing when I was changing between 4.3 and 4.4.2 in which my recovery struggled to mount storage after the system was flashed. In the end I had to flash an old version of Philz CWM, or alternatively flash TWRP and mess about with the settings as where it looked for files (something like that) I also found hat only zips on the internal card flashed for a while...
You may have to either:
1) Push the files to the internal card using ADB
2) Try various recoveries with various ROMS till you get on to sit nicely on your system
3) Or as a last option just reflash your phone with a stock rom through ODIN just to get it up and running, before reflashing a recovery and root using CF-AutoRoot and/or ODIN

pjcarrmole said:
I had a similar thing when I was changing between 4.3 and 4.4.2 in which my recovery struggled to mount storage after the system was flashed. In the end I had to flash an old version of Philz CWM, or alternatively flash TWRP and mess about with the settings as where it looked for files (something like that) I also found hat only zips on the internal card flashed for a while...
You may have to either:
1) Push the files to the internal card using ADB
2) Try various recoveries with various ROMS till you get on to sit nicely on your system
3) Or as a last option just reflash your phone with a stock rom through ODIN just to get it up and running, before reflashing a recovery and root using CF-AutoRoot and/or ODIN
Click to expand...
Click to collapse
Cheers pjc, gives me some idea of where to start. I'd just ogt everything the way i liked it as well, typical isn't it

Related

Phone stuck in boot loop and red text in recovery

ok here is the problem i have a telus fascinate and here i tried to install the ics passion rom but i had to flash in an other rom first to get access to clockwork manager since it wasnt possible on my previous one then from there i formated the data and such then instaled this rom :
http://forum.xda-developers.com/showthread.php?t=1362961 so here what it did, first it installed correctly then got it to reboot and see that its stuck in boot loop for 15 min so im saying myself um not good so i decide to restore my backup but here when i flash back to stock i get this:
Code:
[COLOR="Blue"]Android system recovery <3e>
Enter: OK Key, Select: Vol UP / Vol Down
reboot system now
apply update from sdcard
wipe data/factory reset
wipe cache partition
---------------------------------[/COLOR]
[COLOR="Red"]E: copy_dbdata_media:Can'T mount /dbdata
your storage not prepared yet. please use UI men
u for format and reboot action[/COLOR]
[COLOR="SandyBrown"]Media files copy failed
Manual MODE
--Appling Multi-csc....
installing multi-csc
Can'T access to '/system/csc/tls/sys/'.
successfully applied multi-csc[/COLOR]{----this is yellow but was too flashy to put it in that color
[COLOR="Red"]E:failed to mount /cache (invalid argument.)
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 (invalid argument.)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:failed to mount /cache (invalid argument.)
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
E:failed to mount /cache (invalid argument.)[/COLOR]
ok so here i am not knowing what to do i need help im not the best in these things can someone clearly point me to a solution or help plz
You need to flash a better recover than the stock recover, which you will likely need to flash with Odin. I'd try the Vibrant board to see if someone there could be of more assistance, but that's basically what you're looking at, as far as I recall from my TMO Vibrant.
Ok here are the updates of the problem, i did the a complete wipe of the phone then flashed the ice cream sandwich from passion from the phone and i loaded now where it bugs is there is no mobile network so im kinda stuck it detect telus under access point but in network operator it find nothing any idea guys?
You need to go back to eh03 via odin. Then flash as usual through cwm. It happened to me before. Without odin you wont get out of this.
Sent from my SCH-I500 using xda premium

CWM Recovery - E: Can't mount /cache/recovery/command

Last night I decided to install ClockworkMod Touch Recovery 5.8.0.2. I downloaded the image file from this link:
http://download.clockworkmod.com/recoveries/recovery-clockwork-touch-5.8.0.2-shooter.img
I then used Flash Image GUI from the Play store to install the recovery. Everything seemed to work just fine. I was able to boot into recovery and the touch features worked.
Today, I created a backup using ROM Manager and it appeared to complete properly. However, now when I boot into Recovery, I get these errors:
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've tried re-flashing the regular (non-touch) Recovery using ROM Manager and it installs, but I'm still getting the same errors when I boot into Recovery.
I can boot my phone normally and everything works just fine. I just can't do anything with Recovery anymore so I'm stuck on this ROM until I find a solution.
Does anyone know how I can fix this?
Try this
http://forum.xda-developers.com/showpost.php?p=10878511&postcount=8311
And see if it helps.
#Root-Hack_Mod*Always\
So based on that post, you're saying my issues lie on the SD Card, and not the internal memory?
Yup
#Root-Hack_Mod*Always\
I ended up fixing this by following the steps outlined here to return to 100% stock:
http://forum.xda-developers.com/showthread.php?t=1193540
I then ran the Revolutionary tool to get S-OFF and manually flashed ClockworkMod Recovery via Fastboot.
I'm now back in business!
Glad you got back up and running.
#Root-Hack_Mod*Always\
hii
WillJitsu said:
Last night I decided to install ClockworkMod Touch Recovery 5.8.0.2. I downloaded the image file from this link:
http://download.clockworkmod.com/recoveries/recovery-clockwork-touch-5.8.0.2-shooter.img
I then used Flash Image GUI from the Play store to install the recovery. Everything seemed to work just fine. I was able to boot into recovery and the touch features worked.
Today, I created a backup using ROM Manager and it appeared to complete properly. However, now when I boot into Recovery, I get these errors:
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've tried re-flashing the regular (non-touch) Recovery using ROM Manager and it installs, but I'm still getting the same errors when I boot into Recovery.
I can boot my phone normally and everything works just fine. I just can't do anything with Recovery anymore so I'm stuck on this ROM until I find a solution.
Does anyone know how I can fix this?
Click to expand...
Click to collapse
Hi friends
I solved my problem of CWM recovry error, shows same messages given above.
use this link it will help you definetly
http://forum.xda-developers.com/showthread.php?t=1052813
Thankx
errors
I have the same problem with errors but I´m unable to boot normaly it freeze on start logo... All what I can is go to CWM but here I Can´t flash new rom or restore my backup... It is brick
Errors in clockworkmode recovery
hi everyone
i did a terrible thing and bought a china tablet !
anyway, i installed a new clockworkmod v6.0.2.8 on the device and since then every time i turn on the device, i got these Errors :
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 these : wipe data/factory reset, wipe cache patition, backup and restore, install update.zip, install zip from sdcard, flashtools, odin (which doesn't work because phone don't have any home button !), heimdall, wiping and installing multiple roms .
i even tried to open the clockworkmod .img file from the trick i find in xda forum and put the extract files into a update.zip and fix the problem !!!
but unfortunately the .img file can't be extracted with :ext4_unpacker and ext2explore . it says : unknown file format !
i know the tablet is not bricked . because if it was, should not turned on and went to clockworkmod instantly and stuck in the errors i just typed !
if anyone knows how can i fix the problem, please help !
i will be Appreciated !
thank u .
laie1472 said:
Try this
http://forum.xda-developers.com/showpost.php?p=10878511&postcount=8311
And see if it helps.
#Root-Hack_Mod*Always\
Click to expand...
Click to collapse
what do i do if i have this problem with CWM root but its the internal card?
Hi guys, I have this problem too after following this guide: http://www.youtube.com/watch?v=0zdhyDky2MI
I've also read this issue is present on stock roms only, but I'm wondering if this could be a potential issue for mounting the /sdcard and use it.
i cant installl custom rom in my xolo q1010i through cwm recovery. every time its says E: cant open/cache/recovery. plz tell me how to solve this errors?
[email protected] said:
i cant installl custom rom in my xolo q1010i through cwm recovery. every time its says E: cant open/cache/recovery. plz tell me how to solve this errors?
Click to expand...
Click to collapse
follow my thread, maybe it's your problem too.
please help me to fix my phone
my micromax A106 phone is not staring.In cwm recovry mod it's showing the comand below.plz give me a solution.
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
Install TWRP recovery , Select wipe > Advanced Wipe > Select System/Cache/Data (one at a time) > Repair or change file system > select FAT and swipe .
Hi,
am using lenovo a6000 plus. it was stuck at boot logo, so itried to format wit the help of "wipe data"....now its showing up E: cant mount recovery...
could some help to solve the issue?

[Q] Boot loop woes (Possible FS/partition corruption)

Hey there
I have a pretty serious problem with my I9100... I had installed the Paranoid Android 2.52 ROM and I was trying to switch to a different kernel. Which wasn't working for me, I'm guessing due to the Fastboot feature in that ROM.
The last kernel I tried was the Andromeda one. While trying that, I thought I might try to do a factory wipe using its recovery software, hoping that that might get Paranoid Android to boot.
Unfortunately, it would hang while doing the wipe, and I eventually (after about 20 minutes) power-cycled the device. I tried getting back to my working kernel, but Andromeda's recovery would either error out with mount errors, or it would hang altogether.
Eventually, I tried flashing a CF-Root kernel using Odin, and since then I was unable to get past the Samsung boot splash screen. I could no longer access the recovery software, but I could get into download mode and flash stuff via Odin (Kies won't recognize the device).
I've tried a variety of kernels and firmwares (including the stock one for my phone (GT-I9100_XEF_I9100XWKJ2_I9100XXKI4_I9100XEFKJ1, which I've previously flashed successfully to get it back to a non-rooted vanilla state)), but nothing I did would get the phone to boot.
Thinking the partition table might've been damaged somehow, I attempted the stock firmware from the first post here, including the PIT file and re-partitioning. This process would eventually hang when flashing datafs.
Thinking the bootloader might be damaged, I tried partitioning again, flashing the original bootloader from here, and again flashing the stock firmware that I've used successfully in the past.
I can now actually get past the boot splash! However, the phone boots directly into stock recovery, which looks like it's trying to do some post-update maintenance-type stuff, but fails horribly at it. Some of the output from it scrolls past the viewport, but this is the last lines that I can read:
Code:
[COLOR="Orange"]Formatting /cache...
Cache wipe complete[/COLOR]
-- Updating application...
[COLOR="DarkRed"]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.
[/COLOR][COLOR="Orange"]-- Appling Multi-CSC...
Installing Multi-CSC
Can't access to '/system/csc/XEF/system/'.
Successfully applied multi-CSC.[/COLOR]
[COLOR="DarkRed"]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 (Unknown error: 0)
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)[/COLOR]
It definitely looks like a borked filesystem/partitioning to me. I tried doing a factory wipe in this recovery, but it would hang at formatting /cache.
Any ideas of what I can do to get this thing up and running again?
Thanks in advance,
Daniel
I successfully flashed a CF kernel, and can now access CWM.
I get these error messages, however:
Code:
CWM-based Recovery v5.0.2.7
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
Wiping cache partition in CWM takes care of those errors. Trying a factory reset will give me "Formatting /data..." for a bit, and then the device automatically reboots.
I can format /cache and /system alright, but not /data... I'm fearing that NAND corruption bug I've heard of, except I don't see how I would've caught it...
All right, so I've now confirmed that the Andromeda kernel indeed has the hard-brick bug. Why on earth anyone in their right mind would release a kernel based on that broken leak is beyond my comprehension.
And, to add injury to insult, the devs know there's a problem, yet do not warn about it in the OP, but they mention it some thirty pages into the thread. Thanks, guys!
Anyway, I'm currently scanning my internal storage for damaged areas so that I can custom-PIT my way around it.
Useful posts for reference:
http://forum.xda-developers.com/showthread.php?t=1760107
http://forum.xda-developers.com/showthread.php?t=1667886
http://forum.xda-developers.com/showthread.php?t=1823918
http://forum.xda-developers.com/showpost.php?p=26285877&postcount=12
Hopefully I'll see my phone booting tonight.
Using the patched PIT workaround, I now have my phone back up and running 2½ GB lost on the internal storage, though, but hey - beats being a paper weight!

[Q] Need Help fixing CWM on HTC Hero S (kingdom)

Hello,
I recently rooted&unlocked my bootloader on my HTC Hero S (basically same phone as the Evo Design 4G), and installed Evervolv (4.2.2, 4-7-13 nightly) and my phone is running the ROM fine for the most part, except for a random reboot about once or twice daily. Anyway, when I reboot into recovery (2FS kingdom CWM Recovery v5.0.2.8) I get a series of errors. These errors started appearing after I made a backup with ROM manager:
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 can't do anything in CWM such as install packages, flash roms, factory reset, etc. As of now my phone boots into Android 4.2.2 just fine. I manually installed all the gapps to the system folder, so I have all the Google services. I've also tried re-installing CWM with H-boot and re-naming the file PH44IMG, but when H-boot reads the file it says "CID incorrect! Press power to reboot." I have also tried a clean micro SD card as suggested in a different post.
So basically I have a working phone, but if I need to re-flash or restore a backup I am screwed. Any ideas how to fix this?
I also have everything important backed up in a safe place, so data loss is not a concern.
I looked in my CWM zip, and I found the CID was actually for Sprint phones(my bad haha), so I changed it to US Cellular's CID and I was able to re-install CWM again. Then apon reboot, the errors were still there. I was able to clear the cache in CWM and once I rebooted the errors were gone! Now I can install .zip files without a problem.
Problem Solved.

Wiko Getawya with MIUI8 Rom stoped working after battery deplyted

Hello there,
I should start by saying that i installed the ROM on my device trought this site ("getdroidtips.com/install-miui-8-wiko-getaway"), in the first two days worked very well.
Yesterday my phone depleted his battery and when i turned it on it got stuck on the boot menu, i tryed to enter the recovery mode to try and reboot, the same thing happened.
When i trye to flash the Operating System againt it gave me the error of:
E: Can't mount sd card.
I tryed to format the SD partition and nothing worked, now everytime i enter the safe mode it comes with this:
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
Before this ROM i had cyanogenmod. Those anyone has any idea on how to solve this. Thanks for the help in advance.
More probably usefull information
In the device manager the phones appears like this: YunOS ACB interface
Hope this detail help you helping me.
Once again thanks in advance.

Categories

Resources