CWM errors - Samsung Galaxy S (4G Model)

Ok, so first of all, the current firmware on the phone keeps crashing every 5 seconds, and some recovery log process keeps forceclosing, so I NEED to get a new rom. This current one is not functional.
I finally downloaded a ROM, and put it on the root of my SD card.
Now, when I booted to CWM (holding vol up and vol down, and holding power), I get some errors.
It looks something like this:
Android system recovery <3e>
Samsung Recovery Utils
- for BML -
Enter: POWER Key. Select : Vol UP/ Vol Down
reboot system now
reinstall packages
delete all user data
delete cache data
E:Can't mount /dev/block/stl11
(Invalid argument)
E:Can't mount CACHE:recovery/command
# MANUAL MODE #
-- Appling Multi-CSC...
Installing Multi-CSC
E:Can't mount /dev/block/stl11
(Invalid Argument)
E:Can't mount CACHE:log/recovery.log
E:Can't open CACHE:log/recovery.log
E:Can't mount /dev/block/stl11
(Invalid Argument)
And so the CWM is messed up.
Now the menu looks something like this, (Totally different from what I've seen before)
Any idea how to get cwm functioning? By the way, I did not use ROM manager. Heard it messes stuff up.
Thanks.

Use the guide in the second link in my signature.

lumin30 said:
Use the guide in the second link in my signature.
Click to expand...
Click to collapse
Thank you sooooo much :laugh:
I finally fixed my phone!

Related

[Q] Weird Recovery Stuff

I have some weird stuff going on and I was wondering if maybe someone could tell me what it means. My phone is running fine, in fact better than ever. But when I reboot into recovery mode, and before I apply update.zip and I am in stock recovery (blue), I get the follow message below all of the recovery options (error message is in red):
E: Can't mount /dev/block/st111
(Invalid Argument)
E Can't mount /dev/block/mmcblk0p1
(Invalid Argument)
# MANUAL MODE #
E: Can't mount /dev/block/st111
(Invalid Argument)
E: Can't mount /dev/block/st111
(Invalid Argument)
Then, when I do a backup through CWM, everything goes through fine and then I get this message:
Back complete!
E: Can't open /cache/recovery/log
E: Can't open CACHE:recovery/log
When I go into CWM recovery, I do see a backup labeled with the correct date and everything, so I guess it is backing up correctly? Not quite sure what to make of it.
Ignore it.
Sent from my SCH-I500 using XDA App
JayRHamlin said:
I have some weird stuff going on and I was wondering if maybe someone could tell me what it means. My phone is running fine, in fact better than ever. But when I reboot into recovery mode, and before I apply update.zip and I am in stock recovery (blue), I get the follow message below all of the recovery options (error message is in red):
E: Can't mount /dev/block/st111
(Invalid Argument)
E Can't mount /dev/block/mmcblk0p1
(Invalid Argument)
# MANUAL MODE #
E: Can't mount /dev/block/st111
(Invalid Argument)
E: Can't mount /dev/block/st111
(Invalid Argument)
Then, when I do a backup through CWM, everything goes through fine and then I get this message:
Back complete!
E: Can't open /cache/recovery/log
E: Can't open CACHE:recovery/log
When I go into CWM recovery, I do see a backup labeled with the correct date and everything, so I guess it is backing up correctly? Not quite sure what to make of it.
Click to expand...
Click to collapse
I've had this happen and it happens when you have lagfix enabled and try to revert/odin back to a stock kernel (non voodoo) you'll need to follow the manual disabling procedure (of lagfix) by injecting an empty file named "disable lagfix" into the clockwork folder on your SD card then reboot. After that you should be clear to do a clean flash to get everything working properly. If you tried restoring right now it would probably give you an MD5 mismatch, and trying to flash from recovery would probably give you dev/block errors and it would cancel installation until you get your file system back in order.
bdemartino said:
I've had this happen and it happens when you have lagfix enabled and try to revert/odin back to a stock kernel (non voodoo) you'll need to follow the manual disabling procedure (of lagfix) by injecting an empty file named "disable lagfix" into the clockwork folder on your SD card then reboot. After that you should be clear to do a clean flash to get everything working properly. If you tried restoring right now it would probably give you an MD5 mismatch, and trying to flash from recovery would probably give you dev/block errors and it would cancel installation until you get your file system back in order.
Click to expand...
Click to collapse
OK that makes sense. I was flashing all over the place trying to fix that radio issue. Although I liked Add's answer better. Much more convenient
Sent from my SCH-I500 using XDA App
JayRHamlin said:
OK that makes sense. I was flashing all over the place trying to fix that radio issue. Although I liked Add's answer better. Much more convenient
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Lol yea, I tried that too when I buggered mine up, but since I couldn't flash anything in recovery I decided to find out how to fix it

[Q] Showcase boot looping

After trying to update to the Alpha MIUI build for the showcase, I couldn't get past the boot screen. So, I odin flashed back to stock, but in the processes, I believe I accidentally flashed something to the boot loader.
Now, every time I turn on the phone, I get the blue stock recovery. I can get into 2.5 red recovery and access download mode, but doing the correct reflash to stock doesn't seem to fix the problem
Does anyone have any ideas to fix this? Is the stock bootloader available for download?
*edit: Also worth noting. I get the error: "can't mount \dev\block\stl11" in the recovery menu.
The device no longer shows the Samsung Logo on boot. It remains black for a time then proceeds to the recovery menu.
Total error output in stock 2e recovery is as follows:
E:Can't mount /dev/block/stl11
(invalid argument)
E:Can't mount /dev/block/stl11
(invalid argument)
E:Can't mount /dev/block/stl11
(invalid argument)
Once I open recovery 2.5.1x (red) I get the following errors:
E:Missing bitmap progress_empty
(code -1)
E:Missing bitmap progress_fill
(code -1)
E:Can't mount /dev/block/stl11
(file exists)
E:Can't mount /dev/block/stl11
(file exists)
E:Can't mount CACHE:recovery/command
E:Can't mount /dev/block/stl11
(file exists)
E:Can't mount CACHE:recovery/log
E:Can't open CACHE:recovery/log
E:Can't mount /dev/block/stl11
(file exists)
Did you use the PIT file and check Repartition in ODIN when flashing?
Yes, I used the atlas 2.2.1 PIT, and checked repartition.
Had similar error in recovery and only way i found to fix it was to go back to 2.1 then forward to 2.2. Then install custom recovery etc.
Sent from my SCH-I500 using XDA Premium App
This is for the Showcase, not the Mesmerize. There's no 2.1 ODIN files for the Showcase.
Pay attention.
mezster said:
Had similar error in recovery and only way i found to fix it was to go back to 2.1 then forward to 2.2. Then install custom recovery etc.
Sent from my SCH-I500 using XDA Premium App
Click to expand...
Click to collapse
How did you get back to 2.1? I cannot even go into Download Mode and will go back to the recovery menu. Please help me
Milesjones94 said:
How did you get back to 2.1? I cannot even go into Download Mode and will go back to the recovery menu. Please help me
Click to expand...
Click to collapse
did you get this fixed? how? i have the same issue

[Q] samsung fascinate bootloop

hello i have a samsung fascinate and i recently rooted it and sucessfully instaled jt's ics build and was runing smoothly but got bord and installed cyanogynmod 7 and it sucessfully installed but i wanted to goo back to the ics using a backup i previously made it failed and got stuck into bootloop. on first boot after the power being off it boots straight into voodoo lagfix recovery and after i tell it to reboot it boots into cyanogynmod and trys to install ics but fails reboots and then just bootloops. i gave a friend this phone so someone plese help... and on the home recovery screen it gives me this list of errors that look like this...
CwM voodoo lagfix recovery v2.5.1.x
E:cant mount /dev/block/stl11
(file exists)
E:cant mount CACHE:recovery/command
E:cant mount /dev/block/stl11
(file exists)
E:cant mount CACHE: recovery/log
E:cant open CACHE: recovery/log
E:cant mount /dev/block/stl11
(file exists)
plz help i have odin and i CAN get it into download mode i just need the files and a walkthrough thanks...

Nexus 5 crashes and doesn't open

I have waked up and noticed that the phone is stuck on google logo, i tried to restore factory settings but that was not applicable
so i followed that post http://forum.xda-developers.com/showthread.php?t=2513701 to unlock the bootloader and install factory rom
after several tries my mobile phone can't start and when it starts the apps begin to crash one after the other, I noticed that the mobile recognize a memory of 250 MB (although I have a 32 GB storage) and I think thats the problem
Now I can open the recovery mode but the following errors appears:
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/log_log
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/last_install
E:Can't open /cache/recovery/last_install
E:failed to mount /cache (Invalid argument)
So I don't know what to do!!!!! please help
Unfortunately, it looks like the emmc has died. RMA it asap.
vin4yak said:
Unfortunately, it looks like the emmc has died. RMA it asap.
Click to expand...
Click to collapse
what is the emmc???
ahmedaziz555 said:
what is the emmc???
Click to expand...
Click to collapse
The internal flash memory module (32GB) of your phone.
Same thing happened to me. Was stuck in loading screen. Reset to factory settings. My apps would crash and I cant connect to my network. I also followed that same guide but it didn't help.
Yep, phone's internal storage is probably dead. RMA!
Just curious: for how much time did you use your phone before crashing? Was it completely stock?
Simonna said:
Just curious: for how much time did you use your phone before crashing? Was it completely stock?
Click to expand...
Click to collapse
Yes it was completely stock and i used the phone for 2 weeks

[Q] GT-I9128E running into E:failed to mount /data failed to mount /cache

hello guys,
first of all i have read many posts about the problem and have tried most of them:
secondly:- i am sorry maybe it is not the right section but my phone model doesn't exit here
the problem in details : my phone is Galaxy Gt-I9128E
it freezes on Samsung logo , tried recovery boot with power volume up home key , i see the 6 recovery options in blue and
Successfully applied multi-CSC ." in yellow
and in red :
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
E:Can't mount /cache/recovery/last_install
i have tried the 6 recovery system options
1 from ADB : adb shell : connection closed but see the device some times
2 from external storage : downloaded the firmware to external sd card but the phone shut down every time trying to install it.
3 wipe data : wiped
4 wipe cache partition : wiped
download firmware with Odin 3.7 and 3.10 : Pass reboot but the same problem
tried CWM recovery installed by Odin : Pass . device reboot and going to recovery mode but nothing happened the same old system recovery boot
any help will be appreciated
thanks

Categories

Resources