Originally Posted by OwenW71

Alex,

Sorry I missed your earlier post. I like your thinking on this, just build it into the ROMs until the problem is fixed. Until that happens, I'm still left wondering...

Is there any drawback to just using OP guide to move /data to the external SD before the EU bug strikes?

OwenW71,

Well, I have not tried because AFAIK mmcblk0p2 is the internal SD ext4 partition with /data on fully working devices. The problem is that in order to change that it is necesary to, AFAIK, modify this file https://github.com/CyanogenMod/andro.../init.aries.rc and recompile? CM9. Not sure...

I'm going to try partitioning a micro SD card, but I suspect that on fully working devices with an external SD partitioned as the OP says, the external ext4 partition would be something different than mmcblk0p2, so /data would be on the internal SD.

Not specically the EU error but this happened running KK4

---

My wife has been running KK4 since it's release and had no issues at all.

She let the phone battery die and plugged it back in only to enter bootloop hell. I entered 3e recovery and got all the mmcblk0p mount errors on /sdcard and /data. 3 sleepless days with no joy using Odin, Heimdall, to internal storage and I was able to get her phone active only with CM9 5-23 nightly on her 2GB extsd but there's alot of photos on the internal that we'd love to save.

Guys...is the data unrecoverable from internal storage?

Originally Posted by millerja01a

My wife has been running KK4 since it's release and had no issues at all.

She let the phone battery die and plugged it back in only to enter bootloop hell. I entered 3e recovery and got all the mmcblk0p mount errors on /sdcard and /data. 3 sleepless days with no joy using Odin, Heimdall, to internal storage and I was able to get her phone active only with CM9 5-23 nightly on her 2GB extsd but there's alot of photos on the internal that we'd love to save.

Guys...is the data unrecoverable from internal storage?

I dont understand totally(my eng is not good) Understand that you want to recover some photos...

There is a pc program named "Recuva"Install it to pc and use it..Maybe it helps...

Not sure if this is the same thing?

---

I have a cappy that was running a KK4 gingerbread ROM. There was no SIM or external SD. Airplane and WIFI turned on. Phone was used for games and surfing.

Today when I turned it on, it went into a boot loop. Pulled battery and rebooted - same thing. Button combo to CWM and data factory reset and reboot - still boot loop.
Tried a heimdall oneclick a KH3 - rebooted - boot loop.
From CWM tried to mount Sd and it failed. Anything having to do with Sd fails.

Looks like there is no way to access it. Is this the same as the encryption issue? On gingerbread?

Anything left to try? This phone has always had problems though. Flashing has always been a challenge, where as my cappy that I use all the time, can flash and run anything without issue. I'm suspecting there may have been issues with this particular phone since the beginning.

Originally Posted by azunino

OwenW71,

Well, I have not tried because AFAIK mmcblk0p2 is the internal SD ext4 partition with /data on fully working devices. The problem is that in order to change that it is necesary to, AFAIK, modify this file https://github.com/CyanogenMod/andro.../init.aries.rc and recompile? CM9. Not sure...

I'm going to try partitioning a micro SD card, but I suspect that on fully working devices with an external SD partitioned as the OP says, the external ext4 partition would be something different than mmcblk0p2, so /data would be on the internal SD.

Alex,

So your thinking is that the procedure in the guide will produce different results if the internal SD is still working? If I understand the logic, even a partitioned external SD will not get the /data directory if the ROM installer is able to write to the internal SD. Only if the internal is completely borked will the installer jump to the external. Does that sum it up?

Has anyone confirmed this?

Originally Posted by brandon_L

I have a cappy that was running a KK4 gingerbread ROM. There was no SIM or external SD. Airplane and WIFI turned on. Phone was used for games and surfing.

Today when I turned it on, it went into a boot loop. Pulled battery and rebooted - same thing. Button combo to CWM and data factory reset and reboot - still boot loop.
Tried a heimdall oneclick a KH3 - rebooted - boot loop.
From CWM tried to mount Sd and it failed. Anything having to do with Sd fails.

Looks like there is no way to access it. Is this the same as the encryption issue? On gingerbread?

Anything left to try? This phone has always had problems though. Flashing has always been a challenge, where as my cappy that I use all the time, can flash and run anything without issue. I'm suspecting there may have been issues with this particular phone since the beginning.

Try this...
http://forum.xda-developers.com/show...12&postcount=3

Originally Posted by jmtheiss

I would like to propose option #2: A AOKP/AOSP build that has the portion of ICS that allows a partition to be marked as encrypted removed from the code. As I understand it, it's a few lines of code that say, "if the drive doesn't respond in x amount of time, mark it as encrypted". I would like to see it say, "if the drive doesn't respond in x amount of time, mark it as needing fsck and move on" or something like that. If completely removing encryption capabilities would be easier, so be it.

Mark it and move on, to what? An empty phone. You'll still need to see an error screen. Else we'll get a lot of "HELP! My phone boots up but all the apps are gone and I can't install anything!" The actual EU screen is nothing more then an image and a button. Changing it or adding another is not a simple task, because it's in bits and pieces throughout the framework.

Breaking encryption, would only succeed in removing the one and only way for us to know something is wrong.

Which would you rather a boot-loop or a screen telling you there is a problem with the memory. Thanks to encryption we have been able to narrow down the issue to the memory chip, and that it's not initializing. Think of how many causes exist that make a phone boot-loop...

-xda app, too lazy for something interesting to say-

Originally Posted by crt60

Try this...
http://forum.xda-developers.com/show...12&postcount=3

Thanks for the suggestion, but still can't mount sd

Originally Posted by DaNaRkI

Mark it and move on, to what? An empty phone. You'll still need to see an error screen. Else we'll get a lot of "HELP! My phone boots up but all the apps are gone and I can't install anything!" The actual EU screen is nothing more then an image and a button. Changing it or adding another is not a simple task, because it's in bits and pieces throughout the framework.

Breaking encryption, would only succeed in removing the one and only way for us to know something is wrong.

Which would you rather a boot-loop or a screen telling you there is a problem with the memory. Thanks to encryption we have been able to narrow down the issue to the memory chip, and that it's not initializing. Think of how many causes exist that make a phone boot-loop...

-xda app, too lazy for something interesting to say-

That's a good point, and I hadn't considered that aspect of the issue. I know I'm not well versed in the hardware-software relationships used in Android devices, but it just seems excessive to me that the default action when a hardware issue is detected is to completely and permanently deny access to the device, even if the issue could be intermittent.

Here's an analogy for how I was seeing this whole issue: You own a shed full of your personal belongings, and you've hired a company (Andy, Inc.) to send out someone to watch your stuff and let you put in and take stuff out whenever you want/need to. The shed can only be accessed via one door, and that's the door that the Andy rep is guarding.

In the past, the Andy employees haven't really paid attention to the shed. If one of the roof beams in the shed gave out, they'd notice and tell you (as anyone would be able to see that), but it would take a pretty massive failure of the shed before they would do anything.

This new employee from Andy (Ichabod Sandovich), though, has a background in building design and maintenance, and knows some things about construction.

One day, you come to your shed, and find you can't open the door. You ask the Andy rep what's going on, and he says, "Oh, I noticed that you were using three lag bolts in your main support rafters instead of four, which would likely make the shed collapse. As a courtesy to you, I welded the door shut."

In the past, if the reps thought something was a little wrong, they would just put a note on the door that said that something wasn't right. You could still come in with a repair crew and see if something could be done, possibly getting your stuff out, but not any more.

To wrap this long post up, my point is that I'd like to see if there was a way to get an employee of Andy that doesn't weld the door shut, but puts a note on the door instead so the possibility of getting inside again exists.

I hope that wasn't a completely moronic post.

(Oh, and I'm going to do a thanks for you Danarki as soon as my 8 per day limit is over.)

Originally Posted by jmtheiss

To wrap this long post up, my point is that I'd like to see if there was a way to get an employee of Andy that doesn't weld the door shut, but puts a note on the door instead so the possibility of getting inside again exists.

You've still got it backwards. The door gets jammed all on its own. Think of it more in terms of the lock on the shed, and that different OS versions are different keys. The ICS version of the key is shaped a little different and that causes the lock to get jammed. Once the locked is jammed no other key seems to turn it. Your employee is simply letting you know "something happened and I can't get the key to fit."

For a while everyone has been looking at all the different ways to force the lock back open. Others have been looking at the key to try and see what's different, but it's nothing so obvious. Until we can get the lock back open or can intentionally jam it we can't troubleshoot. In the interim we have had two of the locks free up (again all on it's own). We still don't know what exactly is getting stuck, and we don't have the proper tools to open the lock. xda only has the tools to make keys.

Your company and the guard are getting a bad name, but they aren't doing a thing good or bad.

Note: if you want to get more technical then the system is of key-cards that you swipe, thus the lock is all internal moving parts we can't get to.

-xda app, too lazy for something interesting to say-