Post Reply

[FIX] [UPDATED 2012-12-15] Internal SDCARD Damaged

OP trevd

25th January 2012, 02:21 PM   |  #1  
OP Recognized Developer
Flag Hull
Thanks Meter: 1,176
 
870 posts
Join Date:Joined: Jul 2011
Donate to Me
More
FIRST TIME HERE? - SKIP DOWN AND READ IN FULL THE [ ORIGINAL THREAD CONTENT ]

Quote:

Reference Section:
As this thread as evolved, Folks have contributed various methods they've used to fix/workaround this problem - Credit and Thanks to those members.

Black6spdZ - Information on Physical Removal of the Internal Memory Info - Installing CM9
^_Pepe_^ - Guide: Installing CM10 using Heimdall
TrevD ( Me )Alternative mount point Information for devices with intermittent issues
goofey2012 - External SDCard partitioning information.

Quote:

PROTIP - GET THE LOGCAT:
adb is possible one of the most powerful tools you have at your disposal when diagnosing the source of bootloops. If you are stuck in a bootloop grab a good sized sample of what the device is doing by running.

Code:
adb logcat
PROTIP 2 - DON'T FEAR THE LOGCAT:
During a bootloop the ouput of logcat loops around, Running logcat for a couple of minutes and then read the output, It is written in plain english ( at least on English Language Roms ) and will explain what is causing your bootloop.

PROTIP3 - FIND OUT HARDWARE STATUS
Another useful adb command is dmesg, this is the output from the kernel, the kernel amongst other thing manages the interactation between the software and the hardware, you can normally find out if your sdcard has failed by running
Code:
adb shell dmesg
Run this command early in the boot sequence, if you see a line similar to the one below then there's a good chance you're sdcard has failed
Code:
<3>[    4.802004] mmc0: error -110 whilst initialising MMC card


[ ORIGINAL THREAD CONTENT ]



DISCLAIMER: DON'T TRY THIS IF YOU DON'T HAVE TO - I AM NOT RESPONSIBLE FOR ANYTHING - IF YOU ARE UNSURE ABOUT ANYTHING - ASK


I recently fixed a P1000 with a corrupt internal sdcard - I thought I'd share my experience as unbelievable as It sounds, given the size of the internet
I could not find this procedure /hack anywhere

The Symptoms
  1. When Booting the device got stuck at the Samsung Logo Screen
  2. ODin/Heimdall fails on any rom which include an hidden.rfs and movinand.mst
  3. ODin/Heimdall report success when flashing flashing roms without hidden.rfs and movinand.mst
  4. Recovery Mode reports errors after flashing. The error is different depending on which rom was flashed but are all related to file system functions.

    Internal MMC checksum verify failed.
    E: failed to mount /system (invalid argument)
    E: failed to mount /dbdata (Invalid argument)
    E: /dev/block/mmcblk0p2 on /data failed: No such file or directory
    E: copy_dbdata_media:Can't mount /dbdata

    IMPORTANT: THESE ARE NOT THE ONLY ERRORS AND ARE EXAMPLES. IF YOUR ERROR IS DIFFERENT THEN PLEASE SHARE IT.
    THE MAJOIRITY OF THE TIME THE ERROR WILL MENTION WORDS LIKE:
    mount
    mmcblk
    directiory not existing.


The Problem
The recovery errors alone are not enough to diagnose the problem as they can also occur if flashing has been carried out incorrectly.

The main pointer to an Internal SDCard Failure is the inability to flash hidden.rfs and movinand.mst
You should be able to confirm this to be the case by running dmesg on the device using adb from the command prompt of your computer

If you were luckly enough to have left USB Debbugging on than you should be able the run the following command
while the device is booting loop otherwise run it ) while you are in recovery
Code:
adb shell "dmesg | grep mmc0"
My output contained the following line:
Code:
<3>[    4.802004] mmc0: error -110 whilst initialising MMC card
Another way to check is to use adb to view the devices file system.
Code:
adb shell "ls /dev/block"
Do this WITHOUT an external sdcard.
Any Reference to mmcblk will be missing.

Normally you should be able to RMA this as it is an hardware failure.
However as warranties expire or you just can't be bothered to wait here is an alternative solution

The Solution is fairly straight forward, However It's not a repair and it is not possible to recover any data from the Internal memory.
So You've lost your Angry Birds Hi-Score forever.

That's the bad news. The Good News is, You've still got what will soon be a working Tablet again and a chance to get an even higher score.

Note: The Following description maybe considered by some as a little heavy on Technical Details.
Unfortunately. we are taking advantage of how the Linux Kernel Interacts with hardware ports and how the linux sysfs Virtual filesystem works, It's the nature of the beast I'm afraid

The Solution

In one sentence. We will use the external SD Card to store and load The Android OS.

How Do You Plan to pull that trick off?
This is made possible because of how the Linux kernel manages and addresses devices of the same type. Linux gives each device a number which increments by 1 each time.
The Hardware can control what Linux Sees. I.E the Internal Memory is always loaded first and given and index of 0 [ remember computers : Start Countong a zero ]
After trying and failing to access from the internal sdcard the Kernel quite sensibly looks for the first functioning SDCard on the System and creates it in the /dev tree with a index of zero for that Class of device. It just so happends that the first (and only) Sdcard on the System is now physically located in the external SDCard Slot.

So What Now?
Now we have to play nice with whatever rom is on the device. which means providing the number of partitions that the rom expects. In my case It was 3.
So go ahead ad format and parition your SDCard.
There is nothing to stop you having more than the base amount with what ever file systems you please as long as the Kernel Can provide a mount point to the device than You're laughing.

This Partition Below table was suitabke for UK Roms. The Fat32 Partition is what will appear when the device is connected to Windows as a disk drive.
From what I recall that is the only reason for having a fat filesystem on the Card. So If you're a Linux Junkie then You should be able to pick what Filesystem is good for you. Format the external sdcard with 3 parititions (you can probably get away with 2) I used a 32 GB card with the follwing

Partition 1: 28 GB Fat 32 (sdcard partition)
Partition 2: 4 GB ext4 (data partition)
Partition 3: 100MB Fat 32 (preload partition)
I Used Heimdall for this and I flashed everything. Odin should do the Job as long you remove hidden.rfs and movinand.mst from the tar balls

Code:
heimdall flash --repartition --pit gt-p1000_mr.pit --primary-boot boot.bin \
--cache cache.rfs \
--factoryfs factoryfs.rfs --modem modem.bin \
--param param.lfs \
--secondary-boot Sbl.bin \
--kernel zImage --recovery zImage
After That I Flash a custom kernel which If memory serves enabled the CWM Recovery. The Kernel I used was
one from Team Overcome Kernel 4 which can be downloaded from the teamovercome download page
The choice of kernel isn't any endorsement........ Actully I will say. Use Team Overcome Kernel. It Works!
Seriously any custom kernel should do the trick and In Theory even a stock kernel could be make to work [See Notes]

Boot To Recovery ( You should now see Clockwork Recovery Mod )
edit /system/etc/vold.fstab on the device to look like the following. You can use the adb pull command if you are unsure how to get at the file.


[WINDOWS USERS]
Linux and Windows use different newline characters. If you are editing the file on windows make sure you are using an editor suitable for the task (i.e UltraEdit or Notepad++)

Code:
# internal sdcard 
{

	ums_path = /sys/devices/platform/usb_mass_storage/lun0/file
	asec = disable
	discard = disable
	format_option = -r 1558
}
dev_mount sdcard /mnt/sdcard 1 /devices/platform/s3c-sdhci.2/mmc_host/mmc1

# externel sdcard
{
	ums_path = /sys/devices/platform/usb_mass_storage/lun0/file
	asec = enable
}
dev_mount sdcard /mnt/sdcard/external_sd auto /devices/platform/s3c-sdhci.2/mmc_host/mmc2 /devices/platform/s3c-sdhci.2/mmc_host/mmc1
One final Reboot should make your Still broken but functioning tablet a little less a bitter pill to swallow (see what I did there)

Note: First boot takes a while. if you are worried or think it is boot looping, you can watch the output using adb logcat
You should now have a working galaxy with the added bonus of a re-sizable data partition.

Tool List:
A Micro SD Card - The Bigger The Better , Size and Speed are everrything as this is where you everything pm your tablet will live. I would definitely pitch for a 32GB Class 10.
A Method of formatting and Partitioning the SDCard. - If your a windows user than you need a method of formatting ext4 partitions. I 'm unsure of the current state if the art regarding that.
A Custom Recovery Image. Clockwork Recovery Mod or something similiar. You can use fasboot from the android sdk to flash it to you device
A Custom Kernel Image. with support for the Ext 4and Fat32 Filesystems.
The Next Step Is To Flash A Rom to the devoce . You Should be able to flash any rom to it as long as Your sdcard Is formatted correctly
I Flash Latest Stock Rom at the time and


[Advanced User and Mashoist's]

You Can use you own custom recovery and kernel if you are so Inclined.

For Extra "Going To Try This Because It's There! an I can" Points
Retain A full Stock Experience. When Booting From SD.

It Should be Possible, If can find a way to format the sdcard partitions to Samsung Proprietary RFS File System.
This was also the reason a custom kernel was used ;

Don't forget to say thanks. It gives me a little warm feeling inside
Last edited by trevd; 15th December 2012 at 02:13 PM. Reason: Got A Bit Wordy
The Following 29 Users Say Thank You to trevd For This Useful Post: [ View ]
11th February 2012, 11:29 PM   |  #2  
Junior Member
Thanks Meter: 0
 
11 posts
Join Date:Joined: Aug 2010
Does this mean that the internal SD Card is no longer fixable?
12th February 2012, 07:33 PM   |  #3  
Junior Member
Thanks Meter: 0
 
7 posts
Join Date:Joined: Feb 2011
Unsucessful
Trying this with latinamerica Galaxy Tab (P1000) but with no success, at least at the moment. I tried humberOS kernel (For Latam) phone but stucked at a permanent boot loop. I was sucessful with odin and a tarball without hidden file. Then zimage (HumberOS).

How did you change the vsftab file? Any specific procedure for this?
16th February 2012, 11:37 AM   |  #4  
Junior Member
Thanks Meter: 0
 
16 posts
Join Date:Joined: Nov 2008
Hi,

Thanks for posting this. Was a great shortcut through my problem.

The ROM i tried it with though wont let me type with the keyboard...i just get "null" for every key...although curiously i can backspace each one of letters in "n-u-l-l".

I did this late last night and i think somehow i have used a ROM from somewhere random in europe by mistake and not got the locals setup or something...i'm just going to try a different ROM though because i'm confused as to where i got it now...
9th April 2012, 05:08 PM   |  #5  
Junior Member
Thanks Meter: 0
 
7 posts
Join Date:Joined: Feb 2011
Succesful
Succesful with LatinAmerica Version Gingerbread from Humberos.

However galaxy tab doesnt recognize sdcard partition, so i cant install anything at all.
download files or take pics.

Any tips?
9th April 2012, 09:42 PM   |  #6  
Account currently disabled
Thanks Meter: 4
 
23 posts
Join Date:Joined: Apr 2012
Oh wow... I can't believe this happens...

Sent from my GT-P6800 using Tapatalk
10th April 2012, 04:51 AM   |  #7  
espionage724's Avatar
Senior Member
Flag Charleroi, PA
Thanks Meter: 513
 
2,512 posts
Join Date:Joined: Feb 2010
Donate to Me
More
Quote:
Originally Posted by fluffmonster

Oh wow... I can't believe this happens...

Sent from my GT-P6800 using Tapatalk

neither can I :/ Hope it doesn't happen to me though (or anyone else for that matter)
16th April 2012, 08:14 AM   |  #8  
Junior Member
Thanks Meter: 1
 
4 posts
Join Date:Joined: Apr 2012
Smile corrupted internal sdcard
Hello guys. I have a problem with my Samsung Galaxy Tab, my internal sdcard is corrupted . I tried to use Odin as well as heimdall to flash my device with any custom firmware, it didn't work (no internal sdcard). Finally I tried the MIUI firmware (I tried CM7 as well but didn't like it) based on CWM Recovery v5.0.2.7. Somehow it recognised my external sdcard as internal one . As a result I have two partitions in my system that correspond to my external sdcard:

Code:
C:\tools>adb shell
~ # fdisk -l /dev/block/mmcblk0
fdisk -l /dev/block/mmcblk0
Disk /dev/block/mmcblk0: 16.0 GB, 16021192704 bytes
255 heads, 63 sectors/track, 1947 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
              Device Boot      Start         End      Blocks  Id System
/dev/block/mmcblk0p1               1        1818    14597656   c Win95 FAT32 (LBA)
/dev/block/mmcblk0p2            1818        1948     1048039+ 83 Linux
~ # parted /dev/block/mmcblk0
parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
print
print
Model: SD NCard (sd/mmc)
Disk /dev/block/mmcblk0: 16.0GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number  Start   End     Size    Type     File system  Flags
 1      512B    14.9GB  14.9GB  primary  fat32        lba
 2      14.9GB  16.0GB  1073MB  primary  ext4
But the system see only partition 2 (ext4) as an internal memory. Partition 1 is missed although I can see it in recovery mod and install firmware from it. sdcard is unavailable in the android system. So I can download and use only small aplications that don't require sdcard. But I can't deal with apps, that asks for sdcard. I need to make MIUI see my partition 1 as an sdcard, but I don't know how to do that. I suppose the solution is in editing
"/system/build.prop"

Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=MIUI-XJ
ro.build.display.id=MIUI.2.3.10
ro.build.version.incremental=2.3.10
ro.build.version.sdk=10
ro.build.version.codename=REL
ro.build.version.release=2.3.7
ro.build.date=Fri Mar 10 11:56:49 CST 2012
ro.build.date.utc=1331265409
ro.build.type=userdebug
ro.build.user=xjmod
ro.build.host=builder
ro.build.tags=test-keys
ro.product.model=GT-P1000
ro.product.brand=samsung
ro.product.name=P1000
ro.product.device=galaxytab
ro.product.board=GT-P1000
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=Samsung
ro.product.locale.language=en_us
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=s5pc110
# ro.build.product is obsolete; use ro.product.device
ro.build.product=galaxytab
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=galaxytab-userdebug 2.3.7 MIUI 2.3.10 test-keys
ro.build.fingerprint=samsung/galaxytab/galaxytab:2.3.7/MIUI/2.3.10:userdebug/test-keys
# end build properties
#
# system.prop for smdkc110
#
rild.libpath=/system/lib/libsec-ril.so
rild.libargs=-d[SPACE]/dev/s3c2410_serial3
ro.sf.lcd_density=240
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.opengles.version=131072
wifi.interface=eth0
wifi.supplicant_scan_interval=20
ro.telephony.ril_class=samsung
# mobiledata.interfaces=eth0,pdp0
mobiledata.interfaces=pdp0,eth0,gprs,ppp0
dalvik.vm.heapsize=48m
ro.com.google.locationfeatures=1
ro.com.google.networklocation=1
ro.kernel.android.checkjni=0
dalvik.vm.checkjni=false
ro.removablemounts=/mnt/sdcard/external_sd
keyguard.no_require_sim=true
ro.com.android.dateformat=MM-dd-yyyy
ro.com.android.dataroaming=false
ro.ril.hsxpa=1
ro.ril.gprsclass=10
ro.url.legal=
ro.url.legal.android_privacy=
ro.com.google.clientidbase=android-google
ro.com.android.wifi-watchlist=GoogleGuest
ro.setupwizard.enterprise_mode=1
ro.setupwizard.mode=OPTIONAL
ro.com.android.dataroaming=false
ro.ril.enable.managed.roaming=1
ro.ril.oem.nosim.ecclist=911,112,999,000,08,118,120,122,110,119,995
ro.ril.emc.mode=2
persist.sys.mitalk.enable=false
ro.moddevice=P1000
ro.config.ringtone=MI.ogg
ro.config.notification_sound=FadeIn.ogg
ro.config.alarm_alert=ClassicAlarm.ogg
ro.config.sms_received_sound=FadeIn.ogg
ro.config.sms_delivered_sound=MessageComplete.ogg
dalvik.vm.lockprof.threshold=500
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
#
# XJ ADDED BUILD PROPERTIES
#
ro.telephony.call_ring.multiple=false
ro.telephony.call_ring.delay=1000
ro.additionalmounts=/mnt/emmc
ro.phone_storage=1
ro.gps.soket=/data/gpspipe
ro.sf.hwrotation=90
ro.modversion=MIUI-XJ-GT-P1000
ro.setupwizard.enable_bypass=1
media.stagefright.enable-meta=false
media.stagefright.enable-scan=false
media.stagefright.enable-http=true
media.stagefright.enable-rtsp=false
stagefright.enable-player=false
phone.ril.classname=com.android.internal.telephony.SamsungRIL
dev.sfbootcomplete=0
# LTTLDVL
video.accelerate.hw=1
ro.media.enc.jpeg.quality=100
ro.HOME_APP_ADJ=1
debug.performance.tuning=1
and "/system/etc/vold.fstab"
Code:
## Vold 2.0 Generic fstab
## - San Mehat (san@android.com)
## 
#######################
## Regular device mount
##
## Format: dev_mount <label> <mount_point> <part> <sysfs_path1...> 
## label        - Label for the volume
## mount_point  - Where the volume will be mounted
## part         - Partition # (1 based), or 'auto' for first usable partition.
## <sysfs_path> - List of sysfs paths to source devices
######################
# internal sdcard
dev_mount sdcard /mnt/sdcard 1 /devices/platform/s3c-sdhci.0/mmc_host/mmc3
# external sdcard
dev_mount sdcard/external_sd /mnt/sdcard/external_sd auto /devices/platform/s3c-sdhci.2/mmc_host/mmc1 /devices/platform/s3c-sdhci.2/mmc_host/mmc2
#end line ## keep this line
I tried to correct these two files in different ways but no result at all. I know that the solution of my problem is very close and I suppose it is simple. I'll be glad to get any sugestion in solving my problem.
The Following User Says Thank You to crayo For This Useful Post: [ View ]
30th April 2012, 04:01 AM   |  #9  
waqasshahzad1986's Avatar
Senior Member
Flag Lahore
Thanks Meter: 399
 
460 posts
Join Date:Joined: Jun 2011
More
Facing same kind of problem , but tab isn't p1000 , its Spirint SPH-P100 , its got 2GB.

Above Method will only work if you have modified kernel.
1st May 2012, 06:08 AM   |  #10  
Junior Member
Thanks Meter: 0
 
7 posts
Join Date:Joined: Feb 2011
what is the solution?
So, what is the solution or a 100% valid workaround for this? Maybe it is necessary to replace motherboard or something. Anyway this is for gingerbread and i need ics. Any ideas? Or maybe some examples files for ics? I Really appreciate your help.

Post Reply Subscribe to Thread

Tags
bootloop brick galaxy tab fix
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes