yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] dawei213:
I've been trying to swap the internal SD and external SD card in the vold.fstab with no success. After making the edits in the file, upon a reboot, the phone would just stay on the boot animation. I've done this with Slim ICS and Dark Knight with same results. Anyone else came to this issue?

I'm using a 32gb G.Skill class 10 card.
[Captivate Android Development] Big Dog KMc:
I took the link and added it to a google search and then in the results clicked on "Translate" and brought me this translated page.

http://translate.google.com/transla...ml&hl=en&safe=off&biw=1107&bih=814&prmd=imvns

maybe the smarter ones here can use any information found.
[Captivate Android Development] Woody:
I read all 23 pages of that forum and it seems that it is just a carbon copy of this thread. FYI-when Google Translate says "Brush", it really means "flash". Might register and see if we can get some global support for this maybe.
[Captivate Android Development] Espaa Valorum:
I'm a victim of this bug as well.

Captivate, Slim ICS 3.1 (i think?), Semaphore 1.0.0sc (i think?).

Last week when i pulled my phone out of my pocket i was greeted by the Slim boot animation playing, but all dark (just the blue was visible, white was not?). I did not know what was going on (had not read about this issue yet.) I don't remember what exactly my next step was, but i think i ended up doing a battery pull.

On reboot, was greeted by the Encryption Unsuccessful message. I remembered seeing that mentioned in threads here, so came and read up before i did anything else.

As recommended, pulled my external SD and tried rebooting several times. No change.

Left the phone alone until today, too busy with new baby to sit down and work on this. Today, downloaded the KK4 Odin One Click package and ran it.

After the flashing, the phone booted into the recovery prompt where it proceeded to finish the install. This failed when it tried to access /sdcard. It cannot access it, cannot format it, cannot copy files to it (duh).

ETA: This is what i see on the phone:

Then the recovery menu appears at the top, where i can reboot or wipe data/factory reset etc. I tried doing the wipe data/factory reset, but get the same errors as mention above under the "Wiping data...".

When selecting the 'reboot' option from the recovery menu, it boot loops (AT&T animation to SGS animation, repeat).

So now i'm stuck?

What i'm not entirely clear on is - Does this mean my internal SD is basically broken and cannot be used anymore? As in, either do the workaround of making Android use the external SD instead, or otherwise it's a new phone??
[Captivate Android Development] visionlogic:
Yes. Broken.

There have been reports that some phones have seemingly resurrected themselves from the dead after a length of unpowered time.

As S. Holmes said... "when you have eliminated the impossible, whatever remains, however improbable, must be the truth".
[Captivate Android Development] Espaa Valorum:
Well crap :(

I guess i'll give that a shot then...

I tried flashing KH3, but no dice there either. Still cannot access /data, cannot mount /sdcard etc...
[Captivate Android Development] manolis:
100% of the system on the external card

guys who are versed in this matter may do so to make it work with an external system maps with live memory? Thank you for your attention!

PS sorry for my english;)
[Captivate Android Development] visionlogic:
In searching around I ran across the following... don't know what, if anything, this could add to our discussion of the EU problem. Just posting as FYI:

1. Google+ post by Daniel Hillenbrand re: "We've contacted Samsung about the problem where performing a mmc erase could hardbrick your phone (i9100, i9100g, n7000, m250 - MAG4FA, VYL00M, and KYL00M with firmware revision 0x19 // T989 and I727 with fw rev 0x12) if it's having a faulty emmc chip." --> https://plus.google.com/111398485184813224730/posts/21pTYfTsCkB

2. [08.06.2012] Got Brickbug ? v1.1 - xda thread (Galaxy Note subforum) with small apk attachment that will show the type, CID, and fwRev of your eMMC chip --> http://xdaforums.com/showpost.php?p=27014974&postcount=1

Noted in the above post is: 'News - 08.06.2012

Samsung: "Patches will be out in form of new official ROMs and also sourcecode releases after testing, which might take some time."'

Running the Got Brickbug? apk on my phone it yielded:

eMMC chip type: MAG8DE

Revision: 0x16

Under "Verdict": 'Unknown chip, don't know if dangerous. At least it isn't one of the chips known to be bad.'

But, this may just be all off target and false output... I thought the Cappy (and other GalaxyS series) used a oneNAND and not eMMC as the Exynos devices do. (???)
[Captivate Android Development] silvertag:
It's a firmware bug that is not present in the cappy.
[Captivate Android Development] hagayg:
Well, I've had a similar problem with my SGS II. I've encrypted it and then preformed a Factory Reset on my phone... which ended up without its internal SD Card. Tried fixing it for 3 days and ended up installing the original Samsung ROM so I'll have GApps. Lo and Behold, once the device booted up... A request to format the internal SD Card came up!

I really don't know what to make of it, but it solved my problem, perhaps it could help you guys too.
[Captivate Android Development] Demetris:
Sure give us a way to flash sgs 2 ROM on sgs1. :P
[Captivate Android Development] visionlogic:
Hell, just give us the way to run ICS without the sword of Damocles hanging over our internal memory chip.
[Captivate Android Development] takeoutttt:
This sure is some trouble if experienced. Hope I will not encounter this in the future. #fingers.crossed :D
[Captivate Android Development] fagnerkof:
I wonder if a porting would possibly work...
[Captivate Android Development] manu_ha2001:
my CWM partitions the mem card in just a few seconds what does that mean? have i done that step successfully?
[Captivate Android Development] jvc73:
I don't know if this is really the same thing, however seems quite relevant:

I had downgraded from slim to cm7, ran or for many days, install was fine.

One day I was playing around with the market app because of dpi etc, at one point I had not realized that I had also extracted the market app to the sd ext with the full path (wanted to copy from another ROM).

So at a certain point I think I deleted the app from the internal sd and the sd int became inaccessible (but was present from cwm).

I had to reinstall cm7 to get it back.

I know this is crazy, just thought it was worth sharing.
[Captivate Android Development] manu_ha2001:
I faced this encounter when my phone overcharged

It was very hot and my phone was on overcharging at that time
[Captivate Android Development] Demetris:
Got brickbug?v1.1 from chainfire reports my emmc as:

Type: SU02G

Revision 0x0
[Captivate Android Development] azunino:
CM9 with /data on the external SD working!

Hi,

finally got the time to modify and compile CM9 to use /data on the external SD. I've just installed my modified CM9 running with /data on a partitioned SanDisk class 4 SD card with good performance (off course slower than from the internal SD...)

To those of you that have not been following this very long thread I proposed a workaround to avoid crippling our phones with ICS: forcing CM9 to use /data on the external SD instead of the internal. In this way I hope the EU bug will corrupt/break the external SD instead of the internal. Considering that my patched CM9 does not even mount /data on the internal SD and mounts the external SD FAT partition as /sdcard, it does not even require the internal 16GB FAT partition... well in theory it is less likely that the EU will kill the internal SD...

Tomorrow I will post a new thread with the hacked CM9 and some short instructions to make it work. Keep in mind that I have no idea what I'm doing since I'm not a developer and I've asked around, but I did not receive any technical feedback so far.

The sad news... it is not possible to use any other kernel with my modified CM9 because AFAIK the mapping of /data -> external SD is part of the kernel boot.img... In theory it is possible to extract from a boot.img file the init.rc file with the mappings and modify it, but I have not idea how (some help devs?). Well, if we can solve that, I can write a shell script to convert any(?) ICS based rom or kernel and modify it to use /data on the external sd.

Going to sleep now
[Captivate Android Development] cas0404:
Great !!!
[Captivate Android Development] swayjd:
I think I'm in love with you. Not even kidding.
[Captivate Android Development] azunino:
CM9 with /data on the external SD working

Hi,

I need some advanced captivate users for testing the modified CM9 with /data on the external SD. PM me and I'll send you the instructions and download link.

thanks!

BTW: here is the new /data mount point:
[Captivate Android Development] gelgel133:
i`m stuck

this message show in recovery :

-- Copying media files...

E:failed to mount/sdcard (No such file or directory)

E:copy_dbdata_media:Can't mount /sdcard

your storage not prepared yet. please use UI menu for format and reboot actions.

Media files copy failed.

-- Wiping data...

Formatting /data...

E:format_volume: rfs format failed on /dev/block/mmcblk0p2

Formatting /dbdata...

Formatting /cache...

Data wipe failed

i can`t do any thing, always failed !!!

if i change the mainboard the phone will work ?

and where to buy it ? because i didn`t find it on ebay .
[Captivate Android Development] NightHawk877:
Is this whole encryption bug a hardware issue or is it software related? I fear my Captivate being my only phone might end up without working internal storage.
[Captivate Android Development] creeve4:
So we all know there is no fix for when encryption is unsuccessful, but do we know what to do (our not to do) to prevent it from happening in the first place? Or is this also what is unknown and being looked into?
[Captivate Android Development] azunino:
There is no way to prevent it so far because the bug seems random. Being looked into... I've asked before: http://xdaforums.com/showpost.php?p=26648921&postcount=6384

Anyway, I'm working on a workaround based on a *theory* (take a look at this thread some pages back) to prevent it and so far its been working with the testers who have spent time and risked their cappys trying my "hack". Thanks to them!!!!!!!!!!!! BTW, by *theory* I mean it can probe right... or wrong... :(
[Captivate Android Development] billyjed:
Seriously, there are 700+ posts about this. . .

Sent from my Apple IIe
[Captivate Android Development] NightHawk877:
I apologize for not searching. I was really scatterbrained yesterday.
[Captivate Android Development] Woody:
Test

---------- Post added at 01:58 AM ---------- Previous post was at 01:49 AM ----------

Software. The only 100%way to avoid the Encryption Error is to stay on Froyo or GB (unfortunately) .

You are a man among men (unless you are female). I am actively watching this to see how it turns out. Keep up the good work and I appreciate your self sacrifice, if that becomes the case.

It happens.

******

I am compiling a "Calling all 'Samsung' Cars" type post to put in the Recognized Contributors forum (4-2ndtwin is part of this group btw) to see if we can get any other help. It is a PITA to get all the info from this massively, noisy thread but it is a wip right now. Will post it when i am done just for reference since the forum is restricted.
[Captivate Android Development] azunino:
As promised: http://xdaforums.com/showthread.php?t=1711150
[Captivate Android Development] takeoutttt:
So one way to prevent experiencing this is to stay on GB?
[Captivate Android Development] 11sword11:
On the card is moved only to the section / data?

System and the cache is still on the internal memory?
[Captivate Android Development] visionlogic:
Yes.
[Captivate Android Development] azunino:
yes:

http://xdaforums.com/showpost.php?p=27327814&postcount=700

because the UE bug does not affect these partitions.
[Captivate Android Development] gelgel133:
any help ?
[Captivate Android Development] takeoutttt:
Are you using the CWM recovery?
[Captivate Android Development] RootTheMachine:
Looks like stock
[Captivate Android Development] sa1yan:
I hope this hasn't been asked before. This bug will not occur if there is no external sd card right? Cause I don't use one, but am I still at risk?
[Captivate Android Development] yosup:
It has hit people who were not using external cards as well. Sorry not the answer you wanted. :D
[Captivate Android Development] azunino:
You can try my "safe ICS" http://xdaforums.com/showthread.php?p=27421128
[Captivate Android Development] Woody:
Just an FYI, someone on our side got the bug and was able to get out of it. Sheer luck? Not sure but he posted a very detailed description of what he did. Here is the post.

It did spark something to me though. Remember not too long ago when Adam Outler posted his EFS folder bc we thought it was corrupting and causeing the bug? Turns out it didn't work and we moved on.

*I am wondering how many people with this bug are using unlocked phones and how were they unlocked?

*Also, since I don't frequent your Dev section other than these threads, does anyone remember anybody posting about after they flashed and losing their data or their IMIE got corrupted?
[Captivate Android Development] visionlogic:
[Musing ON]

More and more I get the feeling that this problem and possible/probable solultion(s) is much like genome research. You know the typical statement... "Researchers announced today that they have identified the gene that causes [insert terrible disease]". Then, upon further research, they find that changing that gene not only affects the terrible disease, but may induce another disease or condition, and that there are in fact other genes, not just the single one identified, involved in the causation/cure process.

[Musing OFF]
[Captivate Android Development] Thunder22:
I have the EU bug on my i897. I have tried everything to recover from it. since getting the bug I have been unable to see internal card. I got the phone booting again with an external card. When I take out my external card then the system will go to the EU screen once booted. Nothing new...then I took out my external card. I went into aroma file manager using devil kernel and I couldn't mount sd card but could see all root files like /system /data /sys /Dev...etc..

Could I copy cm7 root files using aroma file manager and potentially recover card using this method?
[Captivate Android Development] Entropy512:
OK, odd question:

Those that experienced this issue, did it seem to trigger after performing a data wipe in recovery?

Since it turns out that /data and /sdcard are on eMMC and not moviNAND or oneNAND like everything else, a few people are wondering if the internal eMMC is getting damaged by a variant of the "superbrick" bug that has been plaguing Exynos-based devices. (the eMMC chip is unable to handle secure erase commands if one is fired at it, and suffers what is currently unrecoverable damage if it does receive such a command.)

However some of the descriptions people have given makes it sound like another issue... For example a few have indicated that the eMMC chip completely disappears. That doesn't happen with Superbrick - in our case it is still detectable by the system but locks up when you try to access damaged parts of the chip.
[Captivate Android Development] Demetris:
Yes after performing data wipe in recovery, then flash new ICS rom then reboot and EU.

Yes eMMC chip completely disappears, nowhere to be found but in XP i have it in computer just reports 0 as space left, you cant format,erase,partition it.
[Captivate Android Development] Entropy512:
Hmm... It would be useful to see if the eMMC is alive until someone tries to access the "wrong" part of it.

If it is the same issue some other devices are having - Certain methods of wiping corrupt the chip's internal data structures. Once this happens, if you touch affected parts of the chip, it locks up and you can't talk to it again without a power cycle. This usually affects only parts of the chip though.

However, prior to this most people have had experience with eMMC corruption on devices that have "other" stuff in the eMMC prior to /data (including /system) - GalaxyS devices only have /data and /sdcard. It might be that wiping /data on such devices causes damage to even the eMMC partition table, such that it immediately dies when you try and do anything with it... Not sure though.
[Captivate Android Development] xtmp:
Recently on one of my cappy started having problems described here:

http://xdaforums.com/showpost.php?p=27819533&postcount=2374

Running on SlimICS 4.0, flash devil Kernel 0.81, and went to ASS - StartUp tweaks, screen was black ~ 5 sec. Then slimICS got root permissions, screen was black again but ~ 15-20 sec. Then I seen only first checkbutton activated (Enable start-up tweaks).

After this operation, and rebooting, phone starting showing devil screen, then slim logo infinitely(waited more than 20 minitus), not booting to desktop.
init.d has only
S30datafix**
S90volume**

Tried 3 times with stock flashing.
Without devil kernel booting fine.
Tried devil 0.85, semaphore 1.2.5 - result the same.

Then I decided not to go into this evil menu. But by setting the wrong overclocking settings in Nstools the phone hung up, and I decided to reset to default nstools settings through the menus in the cwm. The result of the phone hanging on the Slim logo, again.
Flashing Slim with a wipe and without, running the kernel cleaning script from lippol not solving the problem.

Only flashing CM9 with formatting, and then slim is resolving 4 me.

I thought it was a firmware bug, or kernel, but opening the boot.txt file, I saw the following:

look attach from "Bad block... 43..."

It seems that the memory is beginning to break down? :crying:

my eMMC chip

Type: MAG8DE

Revision:0x15
[Captivate Android Development] RootTheMachine:
This doesn't seem to be related to this thread at all. Also, I'm pretty sure my boot.txt has always said that... even down to block 43
[Captivate Android Development] garwynn:
Sorry for jumping into this thread late but in just curious - can someone copy/paste the current partition settings off of a working Captivate? This may help if it is the same bug; and I'm leaning towards Entropy's thoughts that this may be the same thing, just a different effect. A different layout of the partitions could easily explain this; hence the request for the partition list.

Thanks in advance!
[Captivate Android Development] Espaa Valorum:
Samsung says it's a hardware issue

I had the Encryption Unsuccessful issue, and was unable to recover from it. (I did not try to "use the external SD instead" work-around.) I called Samsung and explained the problem. They said they'd take a look and gave me a UPS label to send it to them for free. They would try to software flash to see if that would reinitialize things.

I got a voice mail from them to let me know that the software flash was unsuccessful and that it'll require a hardware replacement. (Did not yet call back for details.) If i want them to do that, it's going to cost me $70 since i'm out of warranty. Debating if I want to go that route, or go for the S3, since i'm eligible for an upgrade...

Figured it might be of interest to all of you to know that Samsung themselves was not able to fix it through software, and that it seems to indeed be a hardware failure.

My thought is that if Android was indeed able to cause a hardware failure, i'm hesitant to pay the $70, only to risk having ICS kill my HW again perhaps....
[Captivate Android Development] garwynn:
In the case of the Epic 4G Touch they said the same thing until it was confirmed by Google to be a different cause and then now confirmed by Samsung. It's part of the reason we've been trying to verify that the scope is correct because we simply don't know what eMMCs shared the offending controller and firmware commands causing the lockup.

As for your question - $149 for the 16 GB GS3 if I remember correctly, $199 for the 32... if you're going to shell out $70 you might as well get the updated hardware IMHO. Others are certainly welcome to disagree with that opinion if desired.
[Captivate Android Development] melvinaury:
I have one question, but I want to share good news.

My cappy was hit with the encrytion error, two months ago. I begin to use the external sd as my sdcard and continue to use my phone. The card that I use are only 2GB. I partition 1gb for data and 1gb for the regular data or sdcard in the phone. I was using AOKP 39 with devil kernel, last test release. Yesterday I install AOKP40 and configure the internal and external sd as per the instructions in the first post. Then I clear battery stats and let the phone die to 0% battery. Today in the morning I connect my phone and turn it on and begin to received a lot of weird errors.

I said forget it and go to recovery and made a factory reset plus format all the data, system, cache, sdcard and emmc.

And install AOKP from scratch, google apps, ukgb3 modem and of course devil kernel in that order. Then restart the phone and when finish configure my google account. Then connect my phone to my pc to copy my TIBU folder in my sdcard and restore my apps. And then ta tan :confused: the pc show my external sdcard and my dear and forgoten internal sdcard directly from heaven. Why or How is the same question of the past two monts, Why or How I have the problem.

In other words my internal sd is back from dead and I don't know why.:D:D:D

And my question is how I partition again my 2gd external sdcard for use. Right now only 1gb is usable. I try to partition again in recovery but received errors.
[Captivate Android Development] swayjd:
Always glad to hear good news.

You can use a partition tool for Windows. Google some free app, there are plenty!

Meanwhile you would do good to use azunino's Roms with data on the external!

Better safe than sorry.
[Captivate Android Development] Woody:
Long time no post. Sorry about that but life happened and I was getting burnt out running in circles on this thing. I decided to take a break for a bit. I'm back and it seems in the nick of time. It seems that someone working on Jelly Bean solved the EU bug but no details yet. PMs have been sent and I will update you with any info I get.

@Americans - have a nice holiday tomorrow.

@Everyone else - happy Wednesday.
[Captivate Android Development] M973:
Thanks to everyone working on this. Luckily I haven't been hit with it, but naturally have been worried, have even been debating reverting to GB. Glad there is at least the workaround, as well as the "preventative" but will be very eager to hear if it truly has been solved :fingers-crossed:
[Captivate Android Development] azunino:
WOW! that is so good news!

Googling right now like crazy for more info
[Captivate Android Development] Woody:
Here is a post from our side with some of the info. Sorry I didn't link it last night, I had about 8 pages and convos going on my tablet both on XDA and RW and linking YouTube videos and I must have reached its threshold so it crashed on me.

The second link in that post is where the goodies are, sort of. They say that they solve the encryption bug but details are slim, hence some PMs sent. I went back a few pages to get some background info and the read it to the end.

Still might be enough to trigger someone over here into something that they never really looked at before.
[Captivate Android Development] cas0404:
hi Woodrube,

maybe we can just take the jelly bean kernel they did and see what are the diferences?
[Captivate Android Development] Woody:
I think that is what a few of us are doing. We first need to make sure that it is in fact the same error and diagnose it accordingly.

The term Encryption was used and there are many similar symptoms but we are still waiting for the solver to respond to some PMs. He's porting JB so i am betting he is getting inundated with problems/solutions for that. Will just have to wait for his particulars but a few of us are already working on it since last night.