Related
Ok so my phone is continuously checking the SD card for errors. THis means that i cant use the sd card. i donno wat happened, or where it went wrong but wen i go in reccovery and mount it, it mounts fine and i can copy files over, but while in the rom it doesnt let me mount (option does not appear). This is happening on Cyan's latest rom and i have tried wiping and reflashing, and just reflashing to no avail.
I think thats abt it, if you need any other info let me know. Any help will be appreciated, thanks!
Have you re-formatted the sdcard?
Sounds like you may have errors on your sdcard. Do a chkdsk while mounting the sdcard in recovery. And/or back everything up and format your sdcard.
I have a Droid running Peter Alfonso's Gingerbread release (GPA15) and it will not show USB storage. I have tried wiping the cache, Dalvik cache, rebooting, etc. i have the same problem with almost every ROM I've tried. The option to mount USB storage simply doesn't appear in the notifications. It appears when the ROM is freshly installed, and then just stops appearing, so it seems to be a device problem. However, I can mount the SD card from CWMRecovery. Ideas?
Hi guys,
This is my first post here, because this is the first time I’ve encountered a problem where I can’t find a solution for on the forums and or random google searches. So I decided to make this thread for myself and others that can’t find the solution to this problem.
So basically this is (I think) the main problem
The internal sd card of my Galaxy S GTI9000 is corrupt.
I can only read the files that are stored, when I try to write (copy a file, delete files or format the whole internal storage) the changes only have effect until the internal sd card is remounted.
This does let me think the internal sd card suddenly became write-protected.
The tricky thing is to know if this can be resolved or if this is truly a hardware problem.
I personally think making the external sd card the internal sd card could work.
What I’ve done so far
Running fine on Slimbean 2.2 until one day it suddenly was in Recovery mode; bootloop
- Reflashed with Slimbean 2.2; bootloop
- Wiped and reflashed; bootloop
- Wiped and flashed CyanogenMod 9.1.0; starting but encryption unsuccessful
- Wiped and flashed CyanogenMod 10 Build 20120920; bootloop
- Flashed 2.3.4_I9000XXJVP; starts fine but apps are crashing all the time
Here I discovered the internal SD Card writing problem
Flashed several official firmware versions with same outcome as the point above
Errors encountered while flashing these firmwares (not always):
- E:format_volume: rfs format failed on /dev/block/mmcblk0p2
- E:format_volume: rfs format failed on /dev/block/stl10
- E:format_volume: rfs format failed on /dev/block/stl11
Firmwares flashed
- I9000XWJS5 (JS5_JS3_JPY_ tar)
- I9000XWJW5_I9000XENJV6_XEN (JW5_JV6_JW4 tar)
- JW6_JW5_JW4 tar
- I9000XXJVT
Also tried
- Hard reset in JVP (gave errors mentioned above)
- Use external sd as internal sd (didn’t succeed in doing this)
- http://forum.xda-developers.com/showthread.php?t=1188482
(got stuck at repacking kernel, same as OP of that thread)
Best I could do
What works the best for me right now is flashing JVP, but:
:good: Can make calls
:good: Can send text messages
Apps are crashing often
No Wi-Fi
No mobile internet
Can’t get root access (with CF-Root)
I hope you can help me, thanks in advance.
-UPDATE-
I did this workaround: http://forum.xda-developers.com/showthread.php?t=1906089
Now I have a fully working phone again, but still the same problems with the internal sd card. (can still be accessed)
If you have the same problem and also have a external sd card the workaround mentioned above would definitely work!
Thanks to reganstott
Hi all, this is my first post on XDA. I'm having big troubles with my device, a Samsung Galaxy S Plus i 9001 and I'm looking for some advice.
After a clean installation of the rom i had been using for some time I started to get messages of force close for most of the apps installed at every boot. The ROM in question is SmoothieICS v2. I believe that the reason of this issue is the fact that I restored all the apps and the data with Titanium backup. To solve the problem I tried to restore a nandroid backup via CWM (version 6.0.1.0), but when a rebooted, the backup was not installed at all and the force close messages continued. After that I tried to wipe data and cache, reinstall the ROM via CWM and Odin, install the stock ROM, fix permissions, format the partition, but nothing worked. Every time I reboot the device, the old ROM boot up with the same force close messages.
I've read several posts on XDA with similar issues, but usually a clean reinstall worked fine. At the moment I'm out of option.
Find attache a copy of the logcat recorded after rebooting the device.
Any suggestion to save my phone is really appreciated.
Thnaks in advance.
Some tips here:
1: Flash BroodROM RC5 (this is an Gingerbread ROM with all the partitions of our device) via odin
2: flash CWM 5.5.0.4 (this is in my eyes the most stable recovery) and wipe all (system, data, cache,dalvic etc)
ibacco said:
Hi all, this is my first post on XDA. I'm having big troubles with my device, a Samsung Galaxy S Plus i 9001 and I'm looking for some advice.
After a clean installation of the rom i had been using for some time I started to get messages of force close for most of the apps installed at every boot. The ROM in question is SmoothieICS v2. I believe that the reason of this issue is the fact that I restored all the apps and the data with Titanium backup. To solve the problem I tried to restore a nandroid backup via CWM (version 6.0.1.0), but when a rebooted, the backup was not installed at all and the force close messages continued. After that I tried to wipe data and cache, reinstall the ROM via CWM and Odin, install the stock ROM, fix permissions, format the partition, but nothing worked. Every time I reboot the device, the old ROM boot up with the same force close messages.
I've read several posts on XDA with similar issues, but usually a clean reinstall worked fine. At the moment I'm out of option.
Find attache a copy of the logcat recorded after rebooting the device.
Any suggestion to save my phone is really appreciated.
Thnaks in advance.
Click to expand...
Click to collapse
First solution,
SmoothieICS is an outdated ROM. Currently there are more stable and bug free releases are available for our device. You can try that.
But, the choice is yours, if you want to continue with it,
Access download mode, install a stable and safe recoveries like CWM 5.5.04, TWRP 2.2.1, or CWM 6.0.3.2 via odin or you can try to flash it via current recovery.
Then do a full data wipe, wipe cache, wipe dalvic cache. If necessary, delete the partition and do a full format
Restore the nandroid backup or do a fresh install
Edit: @mrjraider Haven't seen your reply. Silly me, repeated the same thing you said..
jabrif said:
First solution,
SmoothieICS is an outdated ROM. Currently there are more stable and bug free releases are available for our device. You can try that.
But, the choice is yours, if you want to continue with it,
Access download mode, install a stable and safe recoveries like CWM 5.5.04, TWRP 2.2.1, or CWM 6.0.3.2 via odin or you can try to flash it via current recovery.
Then do a full data wipe, wipe cache, wipe dalvic cache. If necessary, delete the partition and do a full format
Restore the nandroid backup or do a fresh install
Edit: @mrjraider Haven't seen your reply. Silly me, repeated the same thing you said..
Click to expand...
Click to collapse
No problem mate
Things happen
Thank you both, but your solutions didn't work. After installing BroodROM via Odin my phone rebooted in SmoothieICS just like nothing happened. Also a new recovery can't be installed, Tried with TWRP and CWM with no luck :crying:
ibacco said:
Thank you both, but your solutions didn't work. After installing BroodROM via Odin my phone rebooted in SmoothieICS just like nothing happened. Also a new recovery can't be installed, Tried with TWRP and CWM with no luck :crying:
Click to expand...
Click to collapse
That's strange. How is it possible to show up again after deleting and formatting the partition completely.. Are you sure you formatted the data and system in mounts and storage menu of cwm recovery.?
Anyway, Remove your external sd card, and try all the methods again..
Tried again. Did the following:
- removed the external sd card
- rebooted in recovery
- format system and data
- installed CWM 5.5.0.4
- rebooted in recovery
The recovery version installed is still the 6.0.1.0!!!!
It is like the internal SD card can't be written any more.
One thing I maybe didn't mention is that if I delete a file in the internal SD card and the reboot, the file is still there. it is not deleted.
This is really frustrating.
ibacco said:
Tried again. Did the following:
- removed the external sd card
- rebooted in recovery
- format system and data
- installed CWM 5.5.0.4
- rebooted in recovery
The recovery version installed is still the 6.0.1.0!!!!
It is like the internal SD card can't be written any more.
One thing I maybe didn't mention is that if I delete a file in the internal SD card and the reboot, the file is still there. it is not deleted.
This is really frustrating.
Click to expand...
Click to collapse
That's strange and weird. Haven't heard about such a problem before. I will look in to it and will reply you if i get something..
ibacco said:
Tried again. Did the following:
- removed the external sd card
- rebooted in recovery
- format system and data
- installed CWM 5.5.0.4
- rebooted in recovery
The recovery version installed is still the 6.0.1.0!!!!
It is like the internal SD card can't be written any more.
One thing I maybe didn't mention is that if I delete a file in the internal SD card and the reboot, the file is still there. it is not deleted.
This is really frustrating.
Click to expand...
Click to collapse
I recognize those symptoms. The i/o of the sdcard is defect.
What happens is that when you want to format random 0 and 1 are being written to remove the data on the card. If your card is broken and cant be written to you will be unable to format or flash anything. And thus the data on the card remains.
Verstuurd van mijn GT-I9001 met Tapatalk
mrjraider said:
I recognize those symptoms. The i/o of the sdcard is defect.
What happens is that when you want to format random 0 and 1 are being written to remove the data on the card. If your card is broken and cant be written to you will be unable to format or flash anything. And thus the data on the card remains.
Verstuurd van mijn GT-I9001 met Tapatalk
Click to expand...
Click to collapse
Does this mean that the only way to solve the issue is to replace the internal SD card?
Same Issue, but with SGS GT-I9000
I have pretty much the same problem!
Ive been reading a lot and it really seems to be a problem of the internal SD card!
I tried many times to delete all the files on the internal SD card via USB and via Recovery Mode, installed different OS ...nothing worked and most of my apps crash the whole time, so force close to all!
Im now about to decide to use my external SD as internal!
What do you say?
Any ideas
Thanks
Hi guys!
Here's my situation:
- P990, tonyp's PA 2.6 v.13, old bootloader, Kowalski kernel exp. version 12x
- Phone started boot looping (no obvious cause)
- Tried deleting cache. Didn't help.
- Tried flashing the same ROM from external SD. Didn't help.
- Tried restoring working backup (boot and system only, not complete restore) from CWM. Didn't help.
So then I guess I have to do a complete factory reset, but that means I'll lose everything on my internal SD card, right? I want to make a copy first so that I can keep my files. My nandroid backups are only 2.x GB, so I guess they don't include everything on the internal SD card.
I tried to connect the phone to my laptop, but nothing happened, so I deleted/reinstalled drivers from the LG website. That didn't work, but then I found this post which got me a little further. It said the installation was successful, but when I was in CWM, the disks (int. and ext. SD) wasn't being recognized. When I rebooted recovery (from CWM) or just rebooted the device, the computer recognized the discs and started installing four drivers, but as the phone either gets into CWM or just boot loops, it seems like Windows isn't able to finalize the installation of the drivers. This results in the SD cards not being functional in Windows. I can't even see disk labels or storage used/available.
Does someone have an idea of how I might be able to access the internal SD from Windows? Either by fixing the driver issue, or some other method?
I guess I have to fix this USB issue to be able to try to use adb pull to get all the stuff off the internal memory as well, right? Or is the connection between phone and computer not required to be "complete" to be able to do that? I do not remember for sure, but I believe I had turned on USB debugging before all this mess started. However, I have never used adb before.
I'm massively thankful for any help!
Sammy321 said:
Hi guys!
Here's my situation:
- P990, tonyp's PA 2.6 v.13, old bootloader, Kowalski kernel exp. version 12x
- Phone started boot looping (no obvious cause)
- Tried deleting cache. Didn't help.
- Tried flashing the same ROM from external SD. Didn't help.
- Tried restoring working backup (boot and system only, not complete restore) from CWM. Didn't help.
So then I guess I have to do a complete factory reset, but that means I'll lose everything on my internal SD card, right? I want to make a copy first so that I can keep my files. My nandroid backups are only 2.x GB, so I guess they don't include everything on the internal SD card.
I tried to connect the phone to my laptop, but nothing happened, so I deleted/reinstalled drivers from the LG website. That didn't work, but then I found this post which got me a little further. It said the installation was successful, but when I was in CWM, the disks (int. and ext. SD) wasn't being recognized. When I rebooted recovery (from CWM) or just rebooted the device, the computer recognized the discs and started installing four drivers, but as the phone either gets into CWM or just boot loops, it seems like Windows isn't able to finalize the installation of the drivers. This results in the SD cards not being functional in Windows. I can't even see disk labels or storage used/available.
Does someone have an idea of how I might be able to access the internal SD from Windows? Either by fixing the driver issue, or some other method?
I guess I have to fix this USB issue to be able to try to use adb pull to get all the stuff off the internal memory as well, right? Or is the connection between phone and computer not required to be "complete" to be able to do that? I do not remember for sure, but I believe I had turned on USB debugging before all this mess started. However, I have never used adb before.
I'm massively thankful for any help!
Click to expand...
Click to collapse
Can you tell me version of the recovery you use?
Did you tried wipe dalvik-cache? (Advance-->Wipe dalvik-cache)
bitdomo said:
Can you tell me version of the recovery you use?
Did you tried wipe dalvik-cache? (Advance-->Wipe dalvik-cache)
Click to expand...
Click to collapse
I'm using ClockworkMod Recovery v6.0.3.1.
Yes, I tried wiping dalvik cache as well, but that didn't fix it either.
Are there some other ways of getting out of the bootloop? I don't mind flashing stock rom or whatever else, as long as I can recover my internal SD.
Sammy321 said:
I'm using ClockworkMod Recovery v6.0.3.1.
Yes, I tried wiping dalvik cache as well, but that didn't fix it either.
Are there some other ways of getting out of the bootloop? I don't mind flashing stock rom or whatever else, as long as I can recover my internal SD.
Click to expand...
Click to collapse
Download AIO-toolkit from the developement forum. Install itt, and install nvflash drivers with it.
At the main screen select option 2, and then select option 2 again. Follow teh instructions on the screen, and select TWRP 2.5.0.0 to be installed, or cwm 5.0.2.8, both have working mass storage.
(6.0.3.1 has broken massstorage and adb interface. I think you installed cwm 6.0.3.1 through rom manager, if it that true you are on old bootloader.)
bitdomo said:
(6.0.3.1 has broken massstorage and adb interface.
Click to expand...
Click to collapse
Aha, that explains it!
I installed CWM 5.0.2.8 and I got a little further than before. When I mount USB storage in CWM, my external SD card shows up on my computer, but not my internal SD card. What can be the reason for this? Could the card be corrupted, or are there other ways of getting the internal SD to appear?
I tried mounting everything I could mount from the Mounts and storage menu in CWM, but the external SD was still the only thing that showed up on my laptop.
Thank you so much for helping with this!
Sammy321 said:
Aha, that explains it!
I installed CWM 5.0.2.8 and I got a little further than before. When I mount USB storage in CWM, my external SD card shows up on my computer, but not my internal SD card. What can be the reason for this? Could the card be corrupted, or are there other ways of getting the internal SD to appear?
I tried mounting everything I could mount from the Mounts and storage menu in CWM, but the external SD was still the only thing that showed up on my laptop.
Thank you so much for helping with this!
Click to expand...
Click to collapse
Can you try twrp 2.5.0.0?
bitdomo said:
Can you try twrp 2.5.0.0?
Click to expand...
Click to collapse
I've been trying, but I'm not even able to boot into recovery with TWRP installed.
Any other ideas? :fingers-crossed:
Sammy321 said:
I've been trying, but I'm not even able to boot into recovery with TWRP installed.
Any other ideas? :fingers-crossed:
Click to expand...
Click to collapse
Do a factory reset with a working cwm. You will lose all your installed apps and their data, but it will keep data on internal sdcard. After the factory reset you can boot up into andorid
bitdomo said:
Do a factory reset with a working cwm. You will lose all your installed apps and their data, but it will keep data on internal sdcard. After the factory reset you can boot up into andorid
Click to expand...
Click to collapse
YES! I thought factory reset would delete the internal SD, so I didn't even consider that, but it worked like a charm! Thank you so much for caring and helping! You just made my week! :highfive: