[Q] GT-I9000 nearly dead internal sd card - boot loop - Galaxy S I9000 Q&A, Help & Troubleshooting

Hi,
I have a GT-i9000 with an nearly dead internal sd card. Since 1 week I try to reanimate it. I have root access via adb via CWM Recovery 3.0.0.5. I can flash firmware via Odin (used I9000XXJVU).
Demsg shows io errors when system tries to mount and access mmcblk0. Fdisk and parted can not find partitions or anything else from /dev/block/mmcblk0. I can not mount, partition or format it. But it is listed under /dev/block.
I tried to swap internal and external sd card, but since /dev/block/mmcblk0 is present (but dead), initramfs tries to use it instead of external sd card /dev/block/mmcblk1, which I had partitoned as suggested in different threads. Also the apadtion of /system/etc/vold.fstab does not solve anything. Boot process still looks for /dev/block/mmcblk0, which can not be mounted and is still the internal sd card.
I found one thread which suggests to modify initramfs in zimage before flashing and replace all occurence of mmcblk0 with mmcblk1, which might work, but it requires difficult processes to unpack, change, repack/compiling zimage, which will have a lot of pitfalls for me.
So last idea is finding a ROM, which has already the change mmcblk0 -> mmcblk1 implemented and can be flashed with odin.
1. any further help/idea about what I did up to now?
2. anybody can tell me source for such ROM?
Thanks a lot!
Zenusi

As the device is aging, I see ever more people reporting corrupted internal memory. Check the threads for i9000 (or Google search) as many things were going on last months.
I didn't follow, though.
tetakpatalked from Nexus 7 flo

zenusi56 said:
Hi,
I have a GT-i9000 with an nearly dead internal sd card. Since 1 week I try to reanimate it. I have root access via adb via CWM Recovery 3.0.0.5. I can flash firmware via Odin (used I9000XXJVU).
Demsg shows io errors when system tries to mount and access mmcblk0. Fdisk and parted can not find partitions or anything else from /dev/block/mmcblk0. I can not mount, partition or format it. But it is listed under /dev/block.
I tried to swap internal and external sd card, but since /dev/block/mmcblk0 is present (but dead), initramfs tries to use it instead of external sd card /dev/block/mmcblk1, which I had partitoned as suggested in different threads. Also the apadtion of /system/etc/vold.fstab does not solve anything. Boot process still looks for /dev/block/mmcblk0, which can not be mounted and is still the internal sd card.
I found one thread which suggests to modify initramfs in zimage before flashing and replace all occurence of mmcblk0 with mmcblk1, which might work, but it requires difficult processes to unpack, change, repack/compiling zimage, which will have a lot of pitfalls for me.
So last idea is finding a ROM, which has already the change mmcblk0 -> mmcblk1 implemented and can be flashed with odin.
1. any further help/idea about what I did up to now?
2. anybody can tell me source for such ROM?
Thanks a lot!
Zenusi
Click to expand...
Click to collapse
So after trying all software solutions without success I decided to unsolder the internal sd card chip. I was aware that I would not be able to solder a new one (even some people on youtube could ). But I just wanted to prove that my idea that everything did not work, because the chip was present, but defective, was correct.
And yes, after reassembling and flashing with I9000XXJVU I had a working SGS again. It uses now the external sd card as mmcblk0. As expected camera did not work, but I'm sure there will be a solution for it and with a 32GB card, I will have even more memory than before

Related

SD card problem? cannot read properly

I have been trying this for a day and nothing seem to work so far.
The SD card is working, it can be detected/read/write from phone/pc/mac ,
I can also use the sd card to flash rom onto my phone and all works perfectly,
with disk utility, it confirms the correct partition, 64mb for swap and 1024mb for apps,
(it can be detected but cannot be mounted on my mac so no verify/repair can be done on the partition, but the fat partition can still be verified)
now, when i tried to enable app2sd, my phone says extfs partition cannot be detected under spareParts/data option.
I have tried
repartition the sd card like 20 times
wipe/reflash rom,
wiple/reflash different rom
tried different sd card , the partition works so it's not my phone/partition method
verify/repair sd disk
are there anything else to do to repair? or is it a lost cause?
any help will be appreciated
thanks in advance!
do you have any linux handy? could you do an fdisk -l on the disk and print us the partition table?
perhaps you could also use some windows utility to have a look at the table, perhaps it complains about something, if there is an error.
it may be possible that the sd card has an error in the filesystem area. you could try to plug the sd card into the pc, format it with just one partition and uncheck the quick format option. this way it would check all sectors. you should use the console version of format, i think it should output if there is an error. alternativly i think chkdsk -f prints out the bad bytes and there is another option to make it check for them (but normally a non-quick-format does just that)
thanks for the quick response,
I format with PC and MAC then do the disk check and the first time I did it was with a mac it found 5 cluster file and repaired and have since been error free with only one partition present.
I am gonna try to do the check with terminal see what i can come up with.
fixed
knowing that it's not my phone and not my firmware, I decided to give up on the card even though it's "partly-working".
bought a new card and everything fine now.
However, extensive research showed a lot of people have similar problem and some of them have found the fix by
1. reflash
2. insert the card "correctly"
that's all.

[Q] How to Root without internal or external SD card mounted?

Like the topic says I need to root my phone without internal or external SD card access.
I would like to do this so I can try to backup my nv_user and related files before I try another partition since I have had no luck finding a solution to being able to mount my external or internal sd cards.
I have the "Mount Point absent or incorrect." error dialog showing up in my status bar.
I tried searching for solutions to both problems but Have been unlucky so far.
For sgs u definitely have a internal sd.
you definitely have an internal sd-card. however if you want to do it without or have problems with it you can flash a kernel+su with odin: thread on samdroid
cheers, jo
yaocheng said:
For sgs u definitely have a internal sd.
Click to expand...
Click to collapse
Phone says neither them are mounted. Same as in the recovery mode. When I check the sd card and memory in the settings menu both are unavailable. It says I am running off 2 gigs of system memory.
So yes I have an internal sd card. It just won't mount and in recovery mode it won't be found.
That's why I said it wouldn't mount. Not that it didn't exist.
I trying not to flash the phone until I can make a back up of thee nvdata files. So I will check the kernel flash and hopefully it won't effect the nvdata. But I'm guessing it does.
I should have stated a different Title for this thread as my real problem is either Int/Ext SD card corruption or something else deeper within the phone.
I will try formatting it with ubuntu like someone else suggested. That will have to wait until I get home and take a bit since I have no linux experience.
Also, the memory *2gb is showing is labelled as Internal Phone Storage.
Thanks
I'm assuming this has to do with the fact that your phone wont flash anyfirmware after JPC right?
Let me know how it goes.
I can flash but it took some messing around. None of the other firmwares even the stock bell one are stable now and I have no access to either the int or ext sd card. Just the 2gb internal non-sd memory. And after JPC my signal is pretty messed up.
My (wifes) phone now also says internal sd card unavailable.
Is there a solution to this? Happened after I upgraded from JH2 to JM6. The same upgraded process worked on my phone (followed the guide exactly).
Guys, just have a look around these forums or use the search button. This is the most common issue with the I9000M and there is no need for another thread about it.

[Q] Problem with External SD and CWM

I've had the Captivate for a couple of months now and am on xda reading everyday (my wife says I'm obsessed) -- I have yet to find the cause/solution for my problem. I've searched and found similar topics, but I'm not sure if they really apply to my issue.
This problem has followed me to a couple of different ROMs. I started with stock Eclair, Serendipity 5.xx, Cognition 4.1, stock Froyo, and then back to Cognition 4.1.1. I don't recall exactly when the issue started, but I think it was around Cog4.1/stock Froyo.
In Android, I can see it just fine as /sdcard/external_SD (normally use Linda manager). I can copy/move files to/from without any issues. If I plug the phone into the computer, I can access both internal and external SD cards with no problems.
Anyway, CWM 2.5.1.3 -Voodoo Lagfix will not see/mount my external SD card. Attempting to mount /sd-ext produces the error:
E:Can't mount /dev/block/mmcblk1p2 (*NOTE: I've seen posts with this message, but under slightly different circumstances)
(File Exists)
Error mounting SDEXT:!
If, however, I go to "choose zip from sdcard" and then navigate to "external_SD" it will "go" -- however this is **NOT** my external SD card, it appears to be a separate partition. My actual external SD has lots of folders and files, but the CWM "external_SD" has two files that I copied to it attempting to troubleshoot the issue.
A few minutes ago, within Android, I found that if I unmount my external SD, when I navigate to "external_SD", I don't see the files on my true external SD (as expected), but instead I see the partition with my two test files.
I apologize for this lengthy post, but I am at a loss and don't know what else to try. If this has been covered somewhere else, again, I apologize and would greatly appreciate pointing my in the right direction.
Thanks much!
jsbac
how big is this partition?
**i think** somewhere along the road you clicked "partition sd card" in clockwork recovery.
use windows: Start> Administrative tools > "computer management" > "disk management" tree > edit/delete/expand/shrink partitions manually.
Checked partitions in Windows. The mystery "external_SD" wasn't a partition. it was a plain folder named external_SD (don't remember creating that folder, but probably did). I deleted the folder. I still get the same message in CWM.
When connected to the computer, the internal storage shows as FAT32, capacity 13.03GB (single partition); the external storage shows as FAT32, capacity 7.6GB (which is correct - also single partition).
Just for the record, this issue doesn't appear to be creating any stability or performance problems. I want to figure this out just because...
I appreciate the help thus far.
jsbac
Anyone have any other ideas of how to get my external SD card to mount in CWM?
jsbac said:
Error mounting SDEXT:!
Click to expand...
Click to collapse
i have this trouble too on speedmod_k13c kernel.
i want to place and store all my roms and patches on external sd, but now I'm afraid to do it
maybe it's need to create folder with special name on internal SD (ext-sd for example), which will be point of mount.
unfortunately, CWM don't echo detailed information about error even
jsbac said:
Anyone have any other ideas of how to get my external SD card to mount in CWM?
Click to expand...
Click to collapse
Flashing different ROMs can lead to this. It's always a good idea to remove your external SD when flashing.
Try dumping the contents of the card to your PC with a card adapter, then reformat using this:
http://panasonic.jp/support/global/cs/sd/download/sd_formatter20.html
Use the FULL (ERASE ON) setting and leave FORMAT SIZE ADJUSTMENT off.
When you put the files back on, only put the data, don't put any system settings etc back on.
Ok -- I will try this when I get home tonight.
Thanks,
jsbac
clemmie said:
Flashing different ROMs can lead to this. It's always a good idea to remove your external SD when flashing.
Try dumping the contents of the card to your PC with a card adapter, then reformat using this:
http://panasonic.jp/support/global/cs/sd/download/sd_formatter20.html
Use the FULL (ERASE ON) setting and leave FORMAT SIZE ADJUSTMENT off.
When you put the files back on, only put the data, don't put any system settings etc back on.
Click to expand...
Click to collapse

SD card Blank or has unsupported filesystem.

hello every one,
today i had fased a strange prob. which i want to share with u all.
i am having google nexus 1 with cynogenmod 7 installed.
and having sandisk 8gb microsd card. and suddenly today morning it says that "SD card Blank or has unsupported filesystem." i took out my card and mount on my computer and take the entire backup of the data and format it. and incert it but still having the same prob. nothing happen, then i search on net i found on other threads that download the sd card formater and try it. i also tried the same but nothing happen, then on other thread it was mention that try to run chkdsk on computer, with /x comment.. i also done same but still prob. is same.
i am having 3 more micro sd cards of different brands and of different size i also tried them but giving same prob.
nothing happening.
i also open the terminal emulition in my phone and type the commmand mount -a but it says that /etc/fstab not exist.
tell me what i do ? even i am not able to do anything ...
Wow--that is tough to figure out and i am not good at this level of TS.
Sounds like you lost the mount point. It is in etc/fstab
Do you have a backup rom on pc that you can extract etc/fstab from or can you install that rom thru adb with no sd card--
http://www.addictivetips.com/mobile/how-to-install-a-rom-to-an-android-phone-device-without-sd-card/
Can you mount card thru adb--
adb shell
mount /sdcard
exit
Did you use full ersase on and size adj on when you formatted card.
Can you format and partition card outside of phone.
Also, when formatting and wiping for flashing new rom you may want to get Temasek's Format zips that include boot and system wipes.
http://www.mediafire.com/?bxfijcp6f6bf1me#1
Someone will have a better and more accurate answer soon--
Ken

SD Card Basics and rooting/CM

Introduction I wanted to put this into a thread since there are multiple questions about the same topics here. I'm simplifying here, Verygreen and others could give you a lot better detail. But if you are confused about some of the directions in other threads, this may help.
For most purposes, the SD card is treated as a simulated hard disk. So much of the control and terminology used is the same as HD.
For the Nook HD/HD+, the easiest (and so far only) way to access control of the machine is through an SD card. This is because the bootloader will check the SD card and boot an acceptable OS it finds there. So for now at least, ALL CM versions for these Nooks will be booted off the SD card. For those familiar with flashing their phones, it is no different except all ROMs will reside on the SD card. The internal memory, called EMMC (or internal SD) is available for use with these ROMs as of 12/28 releases so it isn't wasted, and data (not programs) you want available from both Stock and CM can be placed there.
ROMs are placed into memory with a program generically called Recovery. This is a small OS which can provide access to memory, update ROMs, wipe memory partitions, make backups of your ROM, provide access to partitions from your computer via ADB, etc. The version that we are using here is called Clockwork Mod (CWM). You will need to load this into the boot sectors of your SD card.
Burning CWM In order for the bootloader to load this program, the exact placement of bits in the SD memory is critical. So instead of copying this program over to the SD card, you must burn an 'image'. This is an exact replica of the specific bits mapped to correct sectors of the SD card. The term is usually 'burn' an image. To burn an image from Windows, the recommended program is Win32DiskImage (http://sourceforge.net/projects/win32diskimager/) but other "image writing" software will work.
When you write an image, your SD card will contain a partition exactly the size of the image you just wrote. A partition is a formatted and ready to use portion of a hard disk or something simulating a hard disk like your SD card. In windows, you might have seen instances where multiple partitions are allocated to different drive letters (e.g. C: and D: ) both on the same physical device. In Unix or Android, partitions are often known by names such as /system or /sdcard. However, native Windows installs are only able to see the first partition of a SD card. Therefore, if you write a 500MB image to a 32 GB card, at that point in time only 500MB is usable and 31.5GB is no longer available. For the CM10 installs on this thread, the rest of the card is automatically partitioned as new drives for the ROM and DATA and so becomes available (linux/android don't have the partition disabilities of Windows).
If you are using Leapinlars' CWM zips to root, etc, you can simply copy the files over after writing the image. There is room in the imaged partition for these files. IF you are using Verygreen's CM10, and possibly others, you can't copy the files over as the CWM partition is too small to start with. After the CM10 SD boots in the Nook, it will create partitions to use the rest of memory. But these new partitions are not easily accessible with Windows. This is why Verygreen's instructions include using ADB to push the zip file to the /sdcard partition.
Partitions For those writing CWM images for update zips (e.g. http://forum.xda-developers.com/showthread.php?t=2062613), you will either want to use a smallish (e.g. 4G) SD card or repartition the card after you are done. The images by Leapinlar are large enough to load a few zip files for flashing in addition to the CWM program and a couple of backups (sometimes called 'nandroids'). But if you want to access the rest of the card, you'll need to repartition. The main reason you would want to do this is to return your 32GB card to full size, either with or without CWM on it; simply reformating on windows will not restore the unused data. For this, you will need to use a partitioning tool like Easeus (http://download.cnet.com/Easeus-Partition-Master-Home-Edition/3000-2248_4-10863346.html) or Minitool (http://www.partitionwizard.com/download.html). Note, this is generally NOT needed by the instruction sets on these fora, but is just provided as information, or if you wish to return to SC card to an initial state.
Copying files to partitions For the Nook HD/HD+, you must have the boot partition in the first partition of the SD card. This will NOT be the /data partition or the /sdcard partition. Therefore, you need a way to write to these partions on the CM builds. The easiest way is to boot CWM and use your computer to write to the these partitions via Android Debug Bridge (ADB). The process is boot to CWM, then go to mounts and storage, mount the /sdcard, THEN adb with CWM running and copy the zip over. ADB is a command shell that can execute commands on a remote android machine. Leapinlar's tips thread http://forum.xda-developers.com/showthread.php?p=34168454#post34168454 gives a lot of detail about setting it up and getting it to run. If you are using Windows, there is a way (Update: this does work to see the sd card partition on CM10 SDs) to see all partitions on a SD card. See this tutorial: http://forum.xda-developers.com/showthread.php?t=1585572. When done properly, you should be able to write your zips directly to the /sdcard partiton of the sd card (if that sounds confusing, please reread all that stuff above.) Note, there are partitions formated in unrecognized formats which are NOT seen with this method.
SD Formats SD cards are 'formatted' in different ways, just like hard disks. Formatting refers to data structures and directory structures used to keep track of files on a hard disk. In fact, any hd format can be used, but the typical format (data/directory structure) on smaller SD cards is FAT32. These are limited to a max filesize of 4GB and are fully compatible with Windows XP. For the larger cards, they often come formatted to a new format called exFAT (extended FAT). These allow larger files but are not native to Windows XP. However, a driver is available from M$ that will support exFAT. Because it is unexpected, you will get an error talking about the likely damage to your hardware if you proceed when writing an image to the exfat formatted SD card. You can ignore the error, the image is written bit for bit correctly.
Lastly to completely reboot the Nook HD/+, you need to hold the power button down for 10 seconds ignoring all prompts. Then hold it down again until it turns on.
I hope this is helpful. Please feel free to post comments and corrections below if I've made any mistakes and I'll update the op. I'll also try to answer questions if you have them.

Categories

Resources