Originally Posted by yosup

I just re-inserted my battery after having it removed for 12.5 hours ... and unfortunately still NO access to the internal sdcard.

The only difference is that their battery died and was left in the phone... Not sure if that affects anything

Swyped from my ICS Samsung Captivate

Originally Posted by yosup

I just re-inserted my battery after having it removed for 12.5 hours ... and unfortunately still NO access to the internal sdcard.

What ROM/kernel are you running? Perhaps we need to just yank the battery while it is still on rather than a graceful shutdown.

Sent from my SAMSUNG-SGH-I897 using XDA

Originally Posted by Red_81

What ROM/kernel are you running? Perhaps we need to just yank the battery while it is still on rather than a graceful shutdown.

Sent from my SAMSUNG-SGH-I897 using XDA

He was on ICZen with Subzero kernel. Could always try the grip it and rip it philosophy with regards to the battery pull.

Anyone read this:

http://www.xda-developers.com/androi...d-ics-kernels/

I assume this is what is affecting us somehow.

Originally Posted by demetris_I

Anyone read this:

http://www.xda-developers.com/androi...d-ics-kernels/

I assume this is what is affecting us somehow.

Firstly, thanks for the link. That was a VERY informative and enlightening link.

So, the question is what is the eMMC revision ids of the affected platforms we have (Captivate, Vibrant, etc), and what version/platform source are the CM kernels based on?

MP

EDIT: Looks like we probably are affected.

root@android:/ # cat /sys/class/block/mmcblk0/device/fwrev
0x0

That was from my Vibrant.

Originally Posted by Ken Sumrall
The patch includes a line in mmc.c setting fwrev to the rights bits from the cid register. Before this patch, the file /sys/class/block/mmcblk0/device/fwrev was not initialized from the CID for emmc devices rev 4 and greater, and thus showed zero.(On second inquiry)
fwrev is zero until the patch is applied.

Originally Posted by mr_psycho

EDIT: Looks like we probably are affected.

root@android:/ # cat /sys/class/block/mmcblk0/device/fwrev
0x0

That was from my Vibrant.

Mine is also 0x0 on a Captivate

Originally Posted by azunino

Mine is also 0x0 on a Captivate

Same, however it is unclear whether this actually affects us, since we aren't using a leaked kernel (or any kind of official Samsung ICS kernel). It does make a lot of sense though, and it probably is a cause.

I found this in a thread where they seem to know what's going on:

That's correct. To get nailed, you need BOTH:
1) A flash chip with the affected firmware. This appears to be the case for nearly all Samsung Exynos devices. There is currently no known way to change the firmware - what you have now is what the factory put in.
2) A kernel that triggers the firmware bug. I9100 update4 sources don't, Gingerbread kernels don't, nearly all other ICS releases do

According to that, we would have to fix the kernel.

Edit: Okay, anybody affected by the error, would you mind posting the results of the following (use terminal or ADB)?

shell@android:/ $ su
shell@android:/ # cd /sys/class/block/mmcblk0/device
shell@android:/sys/class/block/mmcblk0/device # cat name hwrev fwrev manfid oemid date type serial cid

Post the results in this thread.

I have a question now that this new info has come to light. Forgive me if this is a stupid question because I don't develop kernels.

If a user who has this issue flashes a kernel made from:

GT-I9100 ICS leaks, GT-I9100 official releases, GT-I9100 Update4 source base

Could they theoretically see their /DATA partition again? Would this explain how some people's data has come back in the last week?

Unlikely. The structure of the partition is getting overwritten. The kernel can only prevent it from happening in the first place.

Sent from my SGH-T959 using Tapatalk 2

Originally Posted by Red_81

What ROM/kernel are you running?

Originally Posted by Woodrube

He was on ICZen with Subzero kernel.

Woodman ... thanks for covering for me. Life's been a bit crazy lately.

When I had the battery pulled (and left removed for 12.5 hours) on my Vibrant, I was running ICZen_rc1.7.1 (AOKP Build #35) + subZero #80-VC kernel.

Originally Posted by Red_81

Perhaps we need to just yank the battery while it is still on rather than a graceful shutdown.

Originally Posted by Woodrube

Could always try the grip it and rip it philosophy with regards to the battery pull.

I just tried the un-graceful battery pull while the phone was on (running same rom/kernel as mentioned above), and the results are the same. Still no access to the internal sdcard.