yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] jmtheiss:
Just to see if hardware is part of this, could anyone who has had this happen post up their build date?

Mine is a 1010.

If you don't know how to get this, take out your battery and look on the label below it. Below the letters "S/N' should be a four-digit code. That's your build number.

I'm wondering if maybe there is a hardware run that is more prone to this error than others.
[Captivate Android Development] ctrclckws:
Build 1010 Refurb.

Had just loaded Dark Knight 3.0

had not really started to reload apps.

Got dreaded message, pulled battery, etc.

Currently have phone set up as Stock KF1 + Cognition 5.2 Kernel (for CWM), It cannot see the internal drive at all.

What did Samsung do when they first manufactured these phones? Is there any way we can do that to reset the memory, so that it can be used?
[Captivate Android Development] bballer182:
A little off topic but:

I got excited this morning when i received an email from Samsung stating that they were going to release an ICS value pack for the i9000. Later my heart was crushed when i read on XDA that its just going to be a re-release of a current GB with ICS features added in... maybe Samsung knows something we don't about the comparability of ICS and our internal storage??? I hope I am wrong.
[Captivate Android Development] chavocarlos:
It's because they cannot include TouchWiz on ICS ROM due to it is a bigger app ... they will never upgrade their phones without TouchWiz.
[Captivate Android Development] raz123:
Anyone with a uart<->usb cable want to test this on a defective* captivate?

*disabled internal mmc
[Captivate Android Development] jcjcc:
Seconded, this would be great.
[Captivate Android Development] RootTheMachine:
We were talking about Nexus S firmware earlier; has anyone read this? http://xdaforums.com/showthread.php?t=1247962&highlight=unbrickable SD and moviNAND get wiped in the progress
[Captivate Android Development] bballer182:
Cough, Adam Outler, cough.
[Captivate Android Development] jmtheiss:
I would agree that Adam would probably be the best choice for this - the question is, how do we get a Captivate with this issue into his hands? I'm going to guess he probably doesn't have one just sitting around at the moment.
[Captivate Android Development] stayintwisted:
hey I would put up 20 dollars towards a project like that
[Captivate Android Development] jeff.leonard:
If Adam is willing and able I would send him the board out of my captivate that has the issue. It would not include the screen; it is cracked. I want this resolved so I can run ICS on my current captivate; and for everyone else of course;)
[Captivate Android Development] swehes:
You know. I know that my phone is not a captivate. However my Vibrant is having the same issue. Sadly it wasn't the Vibrant the Adam already did the mod on. I may just ship my phone off to him for testing though.
[Captivate Android Development] AdamOutler:
I'd really like to see this issue. Send me one. I can probly work out something... I bet it will be pretty quick too.

For these tests I will not gaurantee that your sdcard data, EFS or serial number will remain in tact, but I will try.
[Captivate Android Development] Johnsondr80:
If we knew how to force this error I would be willing to force mine into this state and ship it your way.

i897 on ICS special edition using tapatalk.
[Captivate Android Development] AdamOutler:
From what I gather, changing between different ICS builds does it. I'm running ICSSGS on my captivate but I'm also using it for development purposes so I can't just risk screwing it up.
[Captivate Android Development] bballer182:
I'd mail you my cappy in a heartbeat if it was borked. Hopefully you will have a cappy in your hands shortly.
[Captivate Android Development] swehes:
I sent Adam my Vibrant today. Hopefully it will shed some light on the whole thing. :)
[Captivate Android Development] Johnsondr80:
Flased back and forth between Fusion-sgsics-teamhackaung and back

Follow op instruction aa to how to flash.

No encryption.....

I will keep it up. Run each a day or so.

Maybe I can make it happen.

I would really love it if you could fix this.

Its keeping so many held offish to ics

And edit. If you can fixit it ahould I succeed in encryption....you keep the device.

typed from ICS Collective Base Build. using tapatalk
[Captivate Android Development] jeff.leonard:
No need to ruin your phone; I am sending my captivate as soon as I get his address by PM.
[Captivate Android Development] b-eock:
@OP in the title it says it is an ICS issue, it isn't. It happens on ICS, but only with certain phones. Not every phone has this problem. Mine doesn't as I flash a lot of ICS ROMs because I have to test ROMs and kernels....
[Captivate Android Development] dohboy15:
But only happens on ICS therefore ICS issue ;) I've heard Asus Transformers have this problem as well

Sent from my Rogers Captivate running AOKP
[Captivate Android Development] AdamOutler:
swehes already sent his apparently.
[Captivate Android Development] jeff.leonard:
His is a Vibrant; do you think that will make any difference?
[Captivate Android Development] b-eock:
Well when I see this thread, I think ohh this must be on all ICS and you keep users from experiencing the Greatness of ICS.
[Captivate Android Development] yosup:
Therein lies the dilemma ...

In the overall schema, it's affecting a small percentage of ICS users. However, it's sort of like the risk of getting hit by a car when you cross the street. Do you simply not cross and deny yourself of discovering what's on the other side?

Obviously, there's been a lot of progress made here, but there's still a ways to go.
[Captivate Android Development] b-eock:
I agree, and thank the OP for the fix for people that have the problem. I would just like for it to be edited so that people aren't so scared. I am not scared since my phone is unbrickable.
[Captivate Android Development] AdamOutler:
I don't think so. If I can get it on the vibrant, then it should be the same on every platform. The entire galaxy s (unlike Galaxy S2) is pretty much the same with small variations between each device (CDMA,type of screen, size, physical keyboard, different power management).. however each GS device shares a Hummingbird processor, a OneNand and an internal SD... that's pretty much everything we're dealing with here.

If I am unsucessful with this device, then maybe I will want a Captivate, but i'm 95% sure that if it works on one, then it will work on all GS1's.
[Captivate Android Development] AdamOutler:
It looks like this is a different issue which locks down the sdcard. You can still boot but no internal SD.
[Captivate Android Development] b-eock:
Ohh :/ OK well there is this guide to fix it :P
[Captivate Android Development] Nirmalspeed:
I fixed my vibrant that was having this problem. What I did to fix it Make sure you have an ext sd card thats 4gb or more:

1) install AIO Vibrant Toolbox http://dl.dropbox.com/u/55131570/Install_AIO_Vibrant_Toolbox_2.5.msi

2) Odin Eugene's Rom: http://xdaforums.com/showthread.php?t=833024&page=49

3) Download CWM 2.x, ICS Kiss kernel, and ICS passion 13.1 (newest).

http://sourceforge.net/projects/stockodinjfd/files/update.zip/download

http://dl.dropbox.com/u/33572867/ICS_Passion_v13_cleanup.zip

http://www.mediafire.com/?8y0o1csdrbx8fv3

4) Rename cwm to update.zip and place that and the ics passion cleanup zip (kiss kernel) onto your ext sd card (using a memory card reader). then "reinstall packages" from the stock recovery that you should get right away from eugene's odin flash. you might have to try doign this a few times to get the green screen

5) Install the ICS Kiss kernel and then reboot recovery into CWM 5.x

6) In the CWM 5.x recovery, go to advanced>partition sd card> select 2gb then 0mb(swap) and then hit okay. It SHOULD take a very long time to work, if not, restart from step 1.

7) go to mounts > mount usb storage> place the 3 zip files back onto the external sd card.

8) odin back to eugene's froyo rom

9) reinstall packages to get cwm again and then factory reset and wipe cache (mounts) and then install ics passion 13.1

10) reboot and it should hopefully load up the rom

11) plug in your phone to your computer if its not already and then open up cmd as an administrator. navigate to wherever you installed AIO vibrant toolbox (C:\AIO Vibrant Toolbox\)

12)

Type in the following code into the command window or copy and paste it (easier) Remember to press the enter key after every command:

1) adb devices "This is to check if your device is properly attached"

2) adb remount "This is to check if your device is properly mounted"

3) adb pull /system/etc/vold.fstab "This will copy the vold.fstab file to the platform-tools folder on your PC."

3a) Now open the vold.fstab file you've just copied to your PC located in platform-tools. Right click vold.fstab and open it with notepad for editing.

3b) With the vold.fstab file open in notepad edit the following lines:

(They should be at the very end of the file and look something like this)

Line 1:

internal sdcarddev_mount sdcard /mnt/sdcard 1 /devices/platform/s3c-sdhci.0/mmc_host/mmc0#

Replace both instances of sdcard with emmc

Line 2:

external sdcarddev_mount emmc /mnt/emmc auto /devices/platform/s3c-sdhci.2/mmc_host/mmc2

Replace both instances of emmc with sdcard

Now that you have finished editing vold.fstab save the file close it and proceed to the next step.

3c) Now copy the edited vold.fstab file to your new partition by using the following commands:

adb remount "Followed by"

adb push vold.fstab /system/etc/vold.fstab "The file should now be overwritten."

13) reboot phone and it should work. I'm not a pro at this but this is what i did to get it to work. I had to modify the steps in http://xdaforums.com/showthread.php?p=24466190#post24466190 post to get it to work. Look at that for more detailed steps for some parts.
[Captivate Android Development] minotaur507:
Adam, I can tell you definitively that changing ICS ROM builds is not the culprit here. I've got the issue after installing ICSSGS 4.2 and never modifying the ROM. The only thing I did do is flash a few different versions of the Glitch kernel... Aside from that, this cappy was my daily driver. In my case, I plugged in the phone at night, everything perfect. I woke up in the morning to the encryption message. Several battery pulls, and no joy. Internal SD can not be partitioned, flashed, or reset with anything that I've tried so far...

Since I've switched to a new i727, I'd be willing to ship the Cappy to you if you need one. Wouldn't matter what kind of damage you do to it...
[Captivate Android Development] raz123:
Agreed.
[Captivate Android Development] visionlogic:
A little more risky than that, because at this point the cars are all invisible. ;)

With Adam's help that should soon change.
[Captivate Android Development] swayjd:
There is no actual fix for this yet. Some cases a couple reboots and you are good to go, but others your internal sdcard dies and it is unrecoverable so far. making the phone unusable, and thats why its scary.

What there is, is a work around to have your external sdcard work as if it were internal. But some people report that this also doens't make the phone usable again because the phone reboots whenever you try to install apps.

A user announced that he had found a fix that he made on his fascinate but a couple people reported that it doesn't work and they all got stuck on the same step. Nothing else.

I find it pretty crazy that this isn't in the OP of every ICS rom to be honest. Because right now, as of this moment, any ICS may kill your internal sdcard, for good, and no one seems to give a ****.
[Captivate Android Development] AdamOutler:
My theory is it's likely hardware failure related.... maybe a single bit that went bad or something that causes it to fail when encryption is checked. The thing is, we need to figure out how to get it back to the way it was before the problem happened and figure out if it's fully reproducable (in the case of hardware failure) or a random glitch (in the case of hardware failure or software/firmware problem).
[Captivate Android Development] jcjcc:
I've never used any ICS rom other than THS, but I've changed from build to build.

This is a good summary of the thread, and I'd like to add that some people have a different type of failure where their data partition is just corrupted, and these people can just flash to stock to fix their corrupted partition (or sometimes just a reboot fixes it).

Back when I researched this, I found a few threads (probably less than 5) about Vibrants and Galaxy Tabs having this failure on gingerbread or earlier. The only solution was to replace the motherboard (or do the workaround).

Looking at the sudden mass of people who got it once ICS came out, I assume that the previous failures were just downright hardware issues, while something in the ICS mmc driver or otherwise (voltage/clock) is messing up phones.
[Captivate Android Development] Demetris:
I think is a software problem.

The MBR gets erased like a lagfix gone wrong.

How are you going to proceed adam?

Can you flash Nexus-S bootloader that can format movinand and report back.

Do you have the UART, because i saw in a thread that was broken.

Can you make a linux distro that dont use android to boot so we can format that MCL Nand?
[Captivate Android Development] b-eock:
It is a hardware problem. If it was software, it would be happening to everyone. Not just certain people...
[Captivate Android Development] jmtheiss:
Just my two cents, but it looks like a combination problem.

As I understand it, as ICS is booting up, it checks the /data partition. If it pops up an error in the check, ICS assumes it's encrypted and flags it as such. I believe this wasn't happening in GB and earlier (for the Captivate, anyway) because those versions of Android weren't following that logic of error checking. So software is at least partially at fault here.

If the hardware is throwing up that error, then the issue might be harder to solve. Electronics aren't bulletproof, and with as many of these as Samsung is pushing out, there are bound to be a few chips with some hiccups in the hardware.

Again, just my thoughts on it, but the wide variety of ways people seem to be coming to this same problem indicate to me that something more than just hardware or just software is in play.
[Captivate Android Development] jcjcc:
Has nothing to do with encryption. The encryption screen only shows up because it can't mount /data.

MBR is not corrupt. The device is not accessible at all. Even if the MBR were corrupt we would still be able to access the sdcard as a block device.

From my test kernel logs we have already determined that the chip isn't initializing. Basically, it's as if the internal sdcard was "removed" -- the data is NOT corrupt or encrypted (common misconception on this thread), we can't access it at all.
[Captivate Android Development] ctrclckws:
Agreed +2

Installed Dark Knight V3 on two phones Build 1010 Refurb and Build 1107 Refurb.

The 1107 didn't have a problem, however after the Build 1010 got the problem within an hour or so of flashing, I took it back to Legend. Since then I went even further back to Cognition 4.5.3 a Froyo Build.
[Captivate Android Development] simple man:
It seems as if the 1010 build is a common thread, from what I've observed.
[Captivate Android Development] simple man:
If I recall correctly, the 1010 builds don't do well flashing the Stock JF6 One click either. May/maynot be related. Just wondering?
[Captivate Android Development] jmtheiss:
Could be - I only received one reply about the build number, and it just happened to be it was a 1010 build. Anyone else who had this happen want to chime in with their build number?
[Captivate Android Development] shaker2k:
I read that captivates produced on Nov 2010 or earlier (sorry don't have the link) were having sleep death issues on stock. There was a recall and you could exchange your phone.

Could this have something to do with it? Obviously that was a hardware issue. So something was changed post Nov 2010.
[Captivate Android Development] jcjcc:
I have a 1007. It indeed could be something like 1010 and earlier.
[Captivate Android Development] raz123:
+1.

This has been mentioned on at least 5 different occasions in this thread, as late as two pages ago.

The Movinand device is still detected. It is, however, constantly answering as busy.

Allow me to simplify it even more.

This is how a good Captivate works:

Kernel: YO MOVINAND, READY TO TALK?

Movinand: NOPE, BUSY!

[...~1 second and a few tries later...]

Kernel: YO MOVINAND, READY TO TALK?

Movinand: YUP, READY

Kernel: AIGHT, LET'S TALK AND EXCHANGE DATA!

This is how a defective Captivate works:

Kernel: YO MOVINAND, READY TO TALK?

Movinand: NOPE, BUSY!

[...plenty of time and many tries later...]

Kernel: YO MOVINAND, READY TO TALK?

Movinand: NOPE, [still] BUSY!

Kernel: JEEZ. SCREW THAT, BOOTING WITHOUT YA.

I can't be any more clear than that :)

*Build 1008 here.
[Captivate Android Development] simple man:
I have a 1008 build, and thank GOD, I haven't got this message. I hope we can find a fix and prevention for this soon.
[Captivate Android Development] visionlogic:
1012 build. 3 different ICS ROMs (various versions of each), several different kernels. No problem. Yet.
[Captivate Android Development] swayjd:
question, people who did get the problem, did you get it in the first ICS you tried or it just happened randomly after a couple weeks?

On a side note, I am also 1010, used cm9, dark knight, icssgs, slim, a lot of them really. No problem yet. Am now on GB cause I can't stand the anxiety of bricking the phone on a reboot.
[Captivate Android Development] jcjcc:
Hahaha, excellent illustration :D
[Captivate Android Development] ctrclckws:
ICS had not even been on the phone for 2 hours.

Dark Knight 3.0 Freshly installed.

1010 Refurb, as stated before.
[Captivate Android Development] minotaur507:
ICSSGS had been on for about 3 weeks. Phone was plugged in to charge overnight. Took it off the charger and had the encryption error. To the best of my knowledge, the phone didn't reboot, and this wasn't exacerbated by constant ROM changing...

I'll look at my build number this evening when I get home.
[Captivate Android Development] amtrakcn:
I encountered this after using ICS daily for several weeks.
[Captivate Android Development] visionlogic:
Just a personal request reiterating a suggestion in a prior post:

when posting in this thread that you've suffered this problem or not

please include your phone's build number

. It may or may not be meaningful in trying to find a cause and solution, but more info is better than less.
[Captivate Android Development] matrixfan321:
Phone got bricked because of this. I was on ICGSGS RC2 when I got the unsuccessful encryption message. Didn't know so I tried to reset it.

It can boot into download mode and I tried to restore it with Odin but it gets stuck in a reboot loop. Must mean that my internal sd is ****ed since it can't mount /data or /mmc.

Not sure how to find my build number

edit: sticker on the phone says 10.10 so I guess Build 1010?
[Captivate Android Development] DaNaRkI:
1012, been on ICS since CM9 went alpha; no problems yet.

leaked from my

ICS

- FUSED SGS I897 contaminating you via XDA app.
[Captivate Android Development] b-eock:
Same here but I flash a lot of Glitch beta test kernels and ROMs.
[Captivate Android Development] minotaur507:
Build 1008 for me experiencing this problem.
[Captivate Android Development] The Communicator:
Started using CM9 teamhacksung builds from october 2011 to february 2012. back on CM7 right now because of this possibility. mine is build 1101. I think the November 2010 pullout is a huge factor in this, with the units on stock that are experiencing sleep deaths.
[Captivate Android Development] AdamOutler:
Well, the device boots, but it does not mount SDCard.. It's odd that it wouldn't boot before and now it boots after an eraseall command.
[Captivate Android Development] iperezru:
So, work in progress, no?

Thanx for your effort! all are with you
[Captivate Android Development] raz123:
That particular phone might have had two separate issues:

1. Un-mountable internal SD

2. Bootlooped, caused by the owner applying various bootloaders/kernels/roms in trying to fix #1

It sounds like you have fixed #2.

What do you think about trying the "mmctest" command, present in SBL?
[Captivate Android Development] Wdustin1:
lol he could have sent you a phone that boots at least :D thank you for all your efforts! i hope something gets figured out.
[Captivate Android Development] Demetris:
Also showpart would be interesting.