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
Hello all.
Although I have read a LOT of xda before, while and after my problems, this is my first post here.
I registered because I wanted to share my solution with the community.
Maybe somebody will find it useful at some point of their mobile adventures.
Primary symptoms:
- a lot of freezing for 5-60 seconds (sometimes longer)
What got me into the primary symptoms
- rooted 4.1.2 stock upgraded via odin to 4.3 stock
Primary ideas that failed
- Dummy File Generator - resulted in freezes, hangs and reboots
- LagFix (fstrim) - no palpable effect
- e2fsck -f -c -v -p every partition (data, system, efs, cache) - no erros & no palpable effect
- Flashing CM11 - primary symptoms remained
What got me into the secondary symptoms
1. Gave up (at that point I was convinced that the problem was hardware related and began to worry about the tripped knox warranty )
2. TWRP format data + wipe every partition (important step it seems)
3. Nandroid restore to 4.3 stock
Nandroid restore was successful BUT:
Secondary symptoms:
- apps were unable to write to internal sdcard0 I could however paste files from my pc via USB or sambadroid so all was not that bad
- titaniumbackup said that any location under /sdcard0/ was "not writable"
- swiftkey was not able to download language packs etc.
- despite the fact that apps could not write to the internal storage the phone seemed not to freeze and became snappier so you could say that the primary issue was resolved (probably by the 'TWRP format data + wipe every partition' step)
Now what about that read-only issue?
Secondary ideas that failed
- chmod 777 for data/media, mnt, storage etc.
- remounting
- retried nandroid restore
Solution that worked
- because only apps had problems I thought that I could mount the /Android folder from internal SD to external SD (apps had no problems with writing to external) and so I downloaded FolderMount. Upon launching it informed me that I have a faulty sdcard module and it will try to repair it (hell yeah! please do!). I rebooted and... sd worked + no more freezes!
phew! that is a lot! all in all I believe that the odin upgrade messed up my internal SD and the freezing was a sign of the phone struggling to write to the storage.
Needless to say - from that moment on I am a happy FolderMount premium user
TL;DR
If you have problems with S3 freezes and/or with read-only internal SD - install FolderMount and let it repair your sdcard module.
I wondered what happened in the background so I asked the dev himself:
madmack said:
The repair simply replaces /system/bin/sdcard with a proprietary one that changed the sdcardfs filesystem that samsung uses to the fuse filesystem that Android AOSP uses which supports binding.
Click to expand...
Click to collapse
And lastly - thank you madmack!
Hello All,
Long time lurker, first time poster (and, as usual, asking for help)
I have a Samsung Galaxy Tab GT-P1000, stock, rooted. Was installing an app yesterday from the play store, when the device rebooted and now it seems to be stuck in a boot loop.
At first I was afraid that it was the dreaded internal SD card corruption issue mentioned here: http://forum.xda-developers.com/showthread.php?t=1463756
However, when connecting with adb, I was unable to locate any references to the error mentioned in the post above :
Code:
<3>[ 4.802004] mmc0: error -110 whilst initialising MMC card
(Also tried the alternative option to list contents of /dev/block and was able to see several references to mmcblk)
Having said that, I haven't yet tried a wipe data/factory reset from the stock recovery because I am not sure if this will wipe my internal SD card contents. I do want to try to save/ copy out my pics etc. if there is a way to do this at all prior to wiping it. (And yes, I am kicking myself hard for not having backed this stuff up.)
I guess what I am asking for is:
a) Is there a way to recover from this without a complete device wipe?
b) If I do need to wipe from recovery, will I lose media/user data on the interal sd card?; and
c) If so, is there a way to retrieve all this data to a PC prior to wiping?
I have also attached the adb logcat file recorded during the bootloop.
Thanks All!!
Resolved
I guess this forum is not quite as alive as some of the others, which makes sense considering the age of this device.
In any case here is a quick summary of what I went thru to successfully get the device working again. (and I still have all my pics/videos )
a) Answer to my first question below - After a loooot of googling, I couldn't figure out a way to recover without a wipe.
b) Answer to my second question - You will NOT lose data on your internal SD card when you do a wipe from (stock) recovery.
c) Answer to third question - There may be, but I was unable to figure it out. I'm fairly certain you can mount the internal SD manually from ADB if you have root and attempt to pull your files to your PC, but my device didn't have a rooted kernel, so I couldn't quite get this done.
Anyway, my other issue was that my Stock recovery was unresponsive as well. On selecting the wipe option for example, the screen would clear itself of all text and just display the Android w/ Exclamation background. I attempted to flash CWM recovery based on the steps in this thread: http://forum.xda-developers.com/showthread.php?t=2430190
However, I ended up with a corrupt screen when attempting to access this new recovery. (Don't know - May be because of improper rooting?)
I was able to successfully restore the device by flashing the stock recovery and ROM based on this thread http://forum.xda-developers.com/showthread.php?t=1133590 ,following the instructions for un-softbricking .
When I booted into recovery and attempted to wipe/factory reset, I got an error.
Code:
rfs format failed on /dev/block/stl10
There was an additional step I had to take, which is clarified further below in the same thread. http://forum.xda-developers.com/showthread.php?p=27979493#post27979493 , which is to flash dbdata as well.
Doing this let me successfully wipe the device, which in turn let me finally get out of the damn bootloop.
Anyway, I hope all this helps someone. Thanks for being a great resource as usual XDA! :good:
Dagrat3One said:
Hello All,
Long time lurker, first time poster (and, as usual, asking for help)
I have a Samsung Galaxy Tab GT-P1000, stock, rooted. Was installing an app yesterday from the play store, when the device rebooted and now it seems to be stuck in a boot loop.
At first I was afraid that it was the dreaded internal SD card corruption issue mentioned here: http://forum.xda-developers.com/showthread.php?t=1463756
However, when connecting with adb, I was unable to locate any references to the error mentioned in the post above :
Code:
<3>[ 4.802004] mmc0: error -110 whilst initialising MMC card
(Also tried the alternative option to list contents of /dev/block and was able to see several references to mmcblk)
Having said that, I haven't yet tried a wipe data/factory reset from the stock recovery because I am not sure if this will wipe my internal SD card contents. I do want to try to save/ copy out my pics etc. if there is a way to do this at all prior to wiping it. (And yes, I am kicking myself hard for not having backed this stuff up.)
I guess what I am asking for is:
a) Is there a way to recover from this without a complete device wipe?
b) If I do need to wipe from recovery, will I lose media/user data on the interal sd card?; and
c) If so, is there a way to retrieve all this data to a PC prior to wiping?
I have also attached the adb logcat file recorded during the bootloop.
Thanks All!!
Click to expand...
Click to collapse
Hi, guys.......new to the process....rooted my galaxy tab p1000 2.2 froyo with z4mod.
Then initially I installed cwm with ROM manager for galaxy tab T because there wasn't any specific model of cwm for p1000.
But but when I switched off and booted recovery, stock recovery always came......I could access cwm only through the ROM manager ("boot into recovery")....and that too if i choose any function it starts to load and when I press home twice it says "replacing stock with cwm" and that goes on forever...
So I installed cwm with Odin as I couldn't access functions like "install" in cwm without going into the loading phase.....but as the process in Odin finished, my tab started to boot and at "galaxy", the sceen got all pixalated and it went till " samsung " and the whole process looped........ Help!
Hello everybody,
I am in desperate need for help.
Received my OP3T yesterday and followed the instructions to flash Sultan's CM13 ROM, unlocking bootloader, running "fastboot OEM unlock", deleting data and system partitions, attempting to flash TWRP and even using the SuperSu root afterwards.
I now have an issue where the internal memory of the phone does not show up on PC. It does not show when I am running CM13, and does not show when I'm in the TWRP recovery menu.
- Using the mount feature in TWRP does not work.
- All my file systems are currently set to ext4.
- USB debugging is on, off course.
- Tried accessing internal memory on a different PC, and still doesn't show.
I've tried completely deleting all the partitions, re-flashed TWRP and re-flashed CM13. Also tried re-flashing the original recovery and the original OxygenOS rom.
As a result, I can only access the TWRP recovery now. I have no way to copy the CM13 zip file or any other file to the internal memory.
Anyone know what's going on?
to see internal storage in TWRP you need to enter the password you definied as android login.
to see internal storage on pc go to "Settings/developer options/usb configuration and use again "file transfer" (i hope this is the english word for "dateiübertragung")
ISSUES :
You get error message when you try to update apps in Play Store or unable to install an apk saying "Out of storage space".
Requirement :
Your phone must be an bootloader unlocked phone and flash and use OrangeFox recovery (I prefer OrangeFox this time).
^^^^^^^^^^WARNING! ALL YOUR DATA WILL BE GONE^^^^^^^^^^ Back up your data to other device or using cloud-based backup.
SOLUTION :
Boot your phone in to Orange Fox Recovery. Mount all partitions available and shown there. Erase these partitions "Data" (NOT Data Format), "Dalvik-cache" & "Cache".
Mount / Enable MTP (can't get connected? Turn it off and back on).
Copy your MIUI14 firmware in to internal storage.
After copying, go to \data\media. Click the flashable miui14 zip and install it as Flashable zip. Wait till it's finished. After that, clear "Dalvik-cache & cache".
I recommend a full reset after phone is booted completely. Your external memory card will be erased too.
Go to \data\media and delete the flash zip file to gain some storage space.
Thank you.