yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] raz123:
I think we should definitely investigate the clock lead.

According to benji22210, the SDHCI driver on our broken devices is trying to set an unusual clock for the internal SD:

s3c-sdhci s3c-sdhci.0: clk 0: rate 133400000, want 400000, got 521093
s3c-sdhci s3c-sdhci.0: clk 1: rate 133400000, want 400000, got 521093
s3c-sdhci s3c-sdhci.0: clk 2: rate 51307692, want 400000, got 200420

Looking at boot logs from other SGS devices (edit: Captivate as well, confirmed!), these should definitely not be 400000, like the above log says the device "wants".

What it should be setting:

Clock 0 = 133400000 Hz

Clock 1 = 133400000 Hz

Clock 2 = 51307692 Hz

Our device is somehow asking for 400000 (seems wrong) for all 3 clocks, and not getting it.

What it is setting:

Clock 0 = 521093 Hz

Clock 1 = 521093 Hz

Clock 2 = 200420 Hz

The question is: what component(s)/file(s) set the clock definitions?

EDIT: Two registers, "Clock Control" (0x002C) and (especially) "Host Control 2" (0x003E) look like valid candidates.

EDIT2: benji22210's log shows that the "Power Control" register (0x0029) has a value of 0, which means that the host controller is not seeing the SD (possibly because of faulty clock/voltage?).

EDIT3: I am fairly certain that the wrong clock that our Captivates are running with is caused by a "1" in the "Preset Value Enable" field of the "Host Control 2" register. As a result, the clock values are extracted from the "Preset Value" registers (0x0060-0x006F), rather than being set by the SDHCI driver.

SD Specs: https://www.sdcard.org/downloads/pl...lified_Specification_Ver3.00_Final_110225.pdf
[Captivate Android Development] jmtheiss:
I'm going to expose my ignorance about the running and building of kernels and just ask the question:

Would it be possible to build a modified kernel for ICS that disables the portion of the kernel that handles encryption?

In other words, if something makes the call to start encryption, it would return an error saying that encryption is not possible and not start any of the processes that are causing this issue.

If Google had it in place but wasn't using it for several versions prior to this one, it would seem to me that disabling this capability would have negligible impact on the functionality of ICS.

Again, I really don't know enough to know if what I'm suggesting makes any sense, but I figured I'd ask since there are a lot of people on here who do understand these things and would be able to chime in either way.
[Captivate Android Development] DaNaRkI:
@raz123 - have you run that idea by the CM9 team? I would think it's their job to fix, as this wrong setting is probably having other side-effects.

It is possible, but you would need to know enough about the encrypting code to find where it is to remove it.

That's not the real issue, encryption has been part of the

Linux Kernel

for a long time (remember Linux is even older then Windows). Google did not add anything to it, but they also had no reason to remove it. By the time honeycomb came about they had figured out a way to have Android do a partial boot (because you need the UI to enter the password on a touch screen device) with rules about who can load and when, plus a way to use the encryption code (the 4 or so parts mentioned on the Google site).

Removing that part of the kernel won't fix the main problem of the phone not being able to mount the partitions like it should. Android will still bring up the screen and users will still get stuck having to reboot.

Removing that part will only cause it to lose respect for encrypted partitions, which at best let's you erase and write over it. We don't want to remove it because there is legitimate use for it (businesses & government, people who are concerned of personal info kept on their phone if stolen).

We want to either find a bypass (my "boot anyways" idea) or a fix (what raz is after, is the preferred solution). The only other problem is that if you falsely let it encrypt the phone it does so with no actual password set to unlock it (Google says this should be your lock screen password, but if you use a slide or pattern unlock it has no values to enter). Sadly Linux does allow for such things, but this "freedom" is what we respect and enjoy about Android being Linux based. You end up stuck, and since it is a natural part of Linux older version of Android still respect it.

leaked from my

ICS

- FUSED SGS I897 contaminating you via XDA app.
[Captivate Android Development] jcjcc:
Anybody tried repeating this procedure, flashing KH3 and accessing internal SD via computer?

Whoa, amazing investigation! This is definitely a big lead.

Summary so far: we found where the timeout (error -110) was; unfortunately setting a huge timeout did not fix the problem. The card just doesn't respond. Raz did some work on the clock discrepancy I overlooked, and we both now think it's a clock issue. We might just need to reset some register value that ICS messed up.

For now, could someone with a working internal SDcard running CM7 flash this mmc_debug kernel and post or PM their log?

Install adb if you haven't. Then boot into recovery, mount /sdcard in Mounts and Storage, and on your computer open adb shell (WIN+R "adb shell") and run "cat /proc/kmsg > /sdcard/kmsg.txt" and close the window after 10 seconds. Make sure you do it while the phone is in recovery. Then post the file.

Perfectly safe, it's a freshly-compiled Glitch 13.1 build, and you can flash back to your regular kernel after. We need to see some correct register values :]

Don't flash this on ICS!
[Captivate Android Development] stayintwisted:
well I just got the encryption unsuccessful screen,, have not pushed it's button,I had flashed the glitch kernel and then aokp 23 by vibrant turk,,I pulled the battery,, tried just rebooting but kept returning me to the encryption unsuccessful screen,, I am a user here not a dev but I am willing to follow instructions that might assist in figuring this out,,

ok well thought I might add

first is the I900 screen

then the glitch kernel screen

then the pink unicorn

then it boots directly to the device encryption screen,,

thats where I am at currently,, hope I can be of assistance

ok got bored

odined back to kj3 and everything seems to be available,,hope this helps somebody,,I sure don't understand,,think I will stick to kk4 roms for a while
[Captivate Android Development] raz123:
So I've talked with the person in charge of the kernel on CM.

According to that person, the clocks we're seeing on our defective devices look normal.

Also according to that person, our failures "might" be because he had increased the internal SD's "drive strength" from 2X to 3X (Captivate came with 2X, Fascinate/i9000 with 3X) -- and thus that "might" be why our hardware failed -- a theory.

He reverted the change: http://review.cyanogenmod.com/#change,12847

Nonetheless, I'd like to pursue this debugging till the end.

If someone with a fully working device could follow the instructions benji22210 posted above, we could compare logs between a working vs defective unit.

Also, I tried jmtheiss's suggestion (flashing KH3 and accessing internal SD via computer). Definitely did not work here. KH3 bootloops. KK4 gets you in the OS, but internal SD shows 'unavailable'. So no luck, he must've had a slightly different issue and was presented with the (as I understand it) fairly generic "Encryption unsuccessful" screen.

stayintwisted, there isn't much to do at this point for the internal SD, unfortunately. Read the first post of the thread to see how you could make your phone useful again with the workaround. It involves using an external microSD.
[Captivate Android Development] stayintwisted:
you missed my last edit,, I now have the phone fully functioning,,I odined stock then master cleared and everything works,, I did not push the reset when I had the encryption unsuccessful screen,, just pulled battery used my jig to download mode and flashed Kj3 it worked,,wish I could tell why :)
[Captivate Android Development] killmastern3:
Just got this Encryption Unsuccessful - Reset Android meesage and i did press reset android. It rebooted and now everything is fine.. I can access both my SD cards.
[Captivate Android Development] octavia:
I've been having battery issues
[Captivate Android Development] Red_81:
There was a question earlier about whether leaving the phone without power could possibly clear the state it was stuck in.

Is there anyone who could leave their phone without power for 6/12/24 hours and see if their access to data comes back?
[Captivate Android Development] silvertag:
What Rom/Kernel ?

Was it out of the blue or after a reboot on MTP usb mode ?
[Captivate Android Development] killmastern3:
Facing this for the first time. Happened just after flashing Cyantablet 9, on first boot.
[Captivate Android Development] yosup:
I'm curious about this myself but need my phone on a daily basis. Just to clarify, MP suggested to try leaving it off "a day or two" (with the battery removed) - ie. if anyone is willing & able to attempt this.
[Captivate Android Development] Woody:
I was in meetings all week so I haven't been able to get on but something significant happened somewhere if 2 people in the same day got their internal back and one person actually got the error and was successful in not getting encrypted.

This is coming to mind right now.

View attachment 1067412

In all seriousness though. There is some good info that can be used here. I'm mobile now but the latest person who was on CM9, did you download the ROM on your PC and then transfer to phone, unplug and then flash it only to find the error at first boot.

I have also read about people leaving there phones off for a long period of time only to find that they swap batteries and BAM they are back to normal.

Could it be some sort of low power built in fail-safe that encrypts your data for your protection? Who knows at this point but some good results need to be pulled from this past day or so to make sure it us still fresh in the users memory.
[Captivate Android Development] octavia:
Maybe it's Skynet messing with us.
[Captivate Android Development] Woody:
Octavia, Killmastern and ReDaved can you all please post as much info that you can recollect in THIS thread that KRock started? Please post all your exact info and anything that can pertain to how you came back from the coma. We can speculated and conjecture in this thread but that other one is for facts.
[Captivate Android Development] yosup:
I just re-inserted my battery after having it removed for 12.5 hours ... and unfortunately still NO access to the internal sdcard. :mad:
[Captivate Android Development] RootTheMachine:
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
[Captivate Android Development] 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.
[Captivate Android Development] Woody:
He was on ICZen with Subzero kernel. Could always try the grip it and rip it philosophy with regards to the battery pull.
[Captivate Android Development] Demetris:
Anyone read this:

http://www.xda-developers.com/android/hard-brick-bug-on-galaxy-s-ii-and-note-leaked-ics-kernels/

I assume this is what is affecting us somehow.
[Captivate Android Development] mr_psycho:
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.
[Captivate Android Development] azunino:
Mine is also 0x0 on a Captivate
[Captivate Android Development] RootTheMachine:
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:

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)?

Post the results in this thread.
[Captivate Android Development] Red_81:
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:

Could they theoretically see their /DATA partition again? Would this explain how some people's data has come back in the last week?
[Captivate Android Development] dougc405:
Unlikely. The structure of the partition is getting overwritten. The kernel can only prevent it from happening in the first place.
[Captivate Android Development] yosup:
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.

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. :mad:
[Captivate Android Development] visionlogic:
Being the dummy that I am, can someone kindly elucidate for me which, if any, current Cappy kernels and/or kernel-rom combos are built from "GT-I9100 ICS leaks, GT-I9100 official releases, GT-I9100 Update4 source base"?
[Captivate Android Development] RootTheMachine:
There aren't any...

Swyped from my ICS Samsung Captivate
[Captivate Android Development] visionlogic:
As I suspected. Thanks.
[Captivate Android Development] matmanchu5:
Borked, Unborked, and Borked Again!

After thinking unbrickablemod would fix this issue and being sorely dissapointed

I came across a Rom that freakin fixed my phone! After using the method in the OP to partition my extSD, i tried flashing CM9 only to get error telling me some build prop files coulnt be accessed (probly cuz they are on the internal inaccessable sd!) SlimRom came to my rescue! For some reason flashing the two-part rom was the trick. Im geussing because the first part doesnt need the buildprop files to install. But it freakin WORKED my phone is running perfect again! Unbelievable! BUT now my USB port is not working! Borked Again!

Thought this might help someone in my situation!

---------- Post added at 10:07 PM ---------- Previous post was at 09:50 PM ----------

I must add that when i encountered the EUnsucc issue I did NOT hit the button but I DID a factory reset vie CWM and after that my SD card was screwed; phone would not boot, I couldnt flash anything except for a Kernel. Then i tried unbrickable mod, then Slim ICS fixed my phone(Mostly)

FREAKIN SWEET! I even edited vold.stab and only thing lost is my internal SD. I would love to have it back, and Im sure there is a way. But for now Im good!

Thanks SLIM ICS!!!
[Captivate Android Development] Woody:
Just so we are clear. Your phone is 100% back or you are now able to boot up completely but still running Slim off your externalSD?
[Captivate Android Development] RootTheMachine:
I asked the smart people in one of their threads a few days ago, and they said it doesn't apply to us because our devices are completely different.

The hwrev and fwrev data I collected this week are in my thread, and I'm not really sure what can be deducted from them, so if you could help, that'd be great.

Swyped from my ICS Samsung Captivate
[Captivate Android Development] manolis:
specify who can please my cid = 1501004d4147384445153e1453d07d00

that is, 0x15, safe flash ICS?
[Captivate Android Development] RootTheMachine:
We don't know what this means yet...

Swyped from my ICS Samsung Captivate
[Captivate Android Development] melvinaury:
Oh men, I was using AOKP Milestone 5 and install today the new semaphore kernel. After just two hours my phone freeze and when the phone was booting. Ta, tan, it apper our love message, encrytion unsuccessful.

Now I'm just looking where to put my new paper weight.

It's there's any Glitch kernel to flash using oding?

For I think was whenb I install Semaphore, by the way I don't connect my phone to the computer, I always download directly to my phone and flash.
[Captivate Android Development] Demetris:
wellcome to the club :)
[Captivate Android Development] Wdustin1:
Not a paper weight if you use the work around
[Captivate Android Development] melvinaury:
I know the problem that I don't use te external card.

But I found a 2GB micro SD card, I hope that it Work.

I update later.:eek::eek::eek:
[Captivate Android Development] Woody:
Ugh. That sucks. Someone else got hit on our side going laterally from Infinitum 4.0.4 to AOKP latest build.

This is getting out of hand. Either more and more people are getting hit or more people are now aware of what is/has hit them. Either way it is getting to be.....epidemic.
[Captivate Android Development] s0ul_ali:
Hmmmmmmmmmm.. ! rabbit hole is getting deeper & deeper. So this is a core ICS baby, and Samsung was mostly blamed. Now it will grab more attention. Lets see where this road leads.
[Captivate Android Development] swayjd:
I think we should find a way to raise awareness for this issue. tons of people running around completely oblivious of how serious this is.

I used ics for a couple months before learning about this, quickly rolled back cause I'm not one to play with fire.

ROM threads have the responsibility dump in big bold letters as we all know, but they all know about this and it seems they chose to close their eyes to it hoping it goes away. A simple warning would hurt their downloads but would do wonders fire their character.
[Captivate Android Development] AtoZ0to9:
I knew this bug had something to do with having an external SD in the phone!!
[Captivate Android Development] RootTheMachine:
But it doesn't...

Swyped from my ICS Samsung Captivate
[Captivate Android Development] silvertag:
Nobody said externals are the source. Many got hit without using the external sd! You should read the threads before assuming things like this.
[Captivate Android Development] Woody:
I cannot agree more with this post and many levels.

Once the

gravity

of this thing hit yours and our sides, I put a BIG FAT WARNING in my ICS install guide about it and links to this thread and on on our side. There are only a handful of ROM threads that have it acknowledged in their OPs in the Vibrant fora.

I was thinking about compiling all our data and the stuff recently found out about TRIM,...and the things in KRock's [REF] thread and putting it together and submitting it to an XDA news writer to see if we can get something on the front page. Maybe someone out there who hardly ever reads the Cappy/Vibrant General/Q&A threads will see it and something wil go off. We have so many bright people working on this but we just can't get past the one thing that is eluding us. If we could catch a break somewhere, I have no doubt that it could be fixed. I mean isn't that what XDA is all about?

What do you guys think about something like that? We could take all our info and dump it on them and they could write about it or we could write it and show our references (flashback to my college days :eek::eek::mad::eek::cool:).

I have no problem writing it if you want but it is going to take some time to compile and I am sure I will miss something here or there. You could PM me post links and a *short* reason why you are sending it and then I'll put it all together and PM out for proof-reading. Will/could take a few weeks or so bc of my schedule but at this point we need more exposure. if anyone else wants to do it by all means but I agree with swayjd, it is time to get it more out there.
[Captivate Android Development] AtoZ0to9:
@silvertag

Excuse me buddy but I do read the threads, and am just informed about the issue as anyone else... maybe I missed it, but I havent seen anyone experience this with a phone that never has an external SD installed... I even asked, in this thread, has anyone not using an external SD experienced this with NO response... So maybe you should read the threads before assuming about my knowledge, or lack of expertise... possibly I missed it, and if I'm incorrect, then I'm sorry on behalf of the other users who read my post, not you... Quit jumpin on folks man.... I'm not some noob...
[Captivate Android Development] yosup:
Here are a couple (from this thread):

Also, Alex9090 got hit on her Vibrant ... also did not have an external card inserted. From korockinout13's Reference thread:
[Captivate Android Development] AtoZ0to9:
I do appreciate the clarification, thanks button hit...
[Captivate Android Development] Woody:
Thank you for keeping it civil. My Transformer forums are full of jump-down-your-throat-types and to be honest, it gets old REAL quick.

I appreciate it, as I am sure others do.

Now back to your regularly scheduled programming.

Haha, I was thinking the exact same thing earlier today. With all the people either ditching ICS or fearful, we should see a large influx in the Froyo/GB ROMs.
[Captivate Android Development] BxingFetus:
So, seeing as this issue seems to be a big one to fix, maybe some gingerbread work could be resurrected?

From the land of defrag
[Captivate Android Development] AtoZ0to9:
Has it ever been reported on a phone that was launched with ICS on it? Does it seem like it only happens to phones which require BML to MTD conversion for ICS?
[Captivate Android Development] melvinaury:
Count me too, I was hit yesterday without using any external card. AOKP milestone 5 and semaphore latest build.
[Captivate Android Development] RootTheMachine:
I think we need to do this... I'm sure there is somebody out there that will have an idea that will help us. The front page would definitely give us that kind of needed attention.

On another note, I haven't been updating my thread recently because there is so much new information being presented to me and it's taking me awhile to process and filter it all. I haven't yet determined the relevance of the eMMC firmware bug people were posting about. The problem with that theory is, it only regards Samsung phones with certain hardware, while other devices (Samsung and non-Samsung) are getting EU also. And that bug doesn't even involve EU or loss of the sd card. Also, we have had phones come back from the dead, while they seem to be stuck unless they manually go around the bad blocks. Apparently we don't even use mmc?

I'll eventually try to update my thread with straightforward details.

I don't think EU has happened on any official builds (the eMMC bug has, of course), but I can't say all of the devices run on BML (I don't really have any knowledge of the other devices that Woodrube posted, but I don't think they all use BML)
[Captivate Android Development] Big Dog KMc:
I have not heard a Peep about this on the Nexus S forums yet.

Owning a NS on T-Mobile for 2 months now I received the OTA 4.0.4 IMM76D about a month ago and no hiccups yet.

An observation though, I read earlier that the possible cause might be the MTB usb mounting on the custom ICS/CM9 roms being used.

My Nexus S has no such MTB on it. only the standard mass storage device mounting.

If the Custom roms that we use for our Vibes/Cappys are from the Nexus S, Where did MTB come from?

Has there been any EU reports from anyone running 4.0.3 ?

Also, CyanogenMod 7 is MTB. Why does this rom have no Internal SD errors or EU Bug.

I know that Encryption was add on Honeycomb on up but the MTB connection Mounting/Un-mounting Issue that might be causing this internal SD problem and thus the EU bug should also be there on the CM7 builds as well I would think.

I have run almost every ICS on My Vibrant + different Kernels but never used the MTB mounting connection and when I ever used the USB to transfer anything I always Un-Mount the USB from Windows first (using the Icon in tray) then Un-Mount from the phone before unplugging anything.

Maybe the custom roms should remove the MTB and see what happens

Just my thoughts on this thus far.