Similarly if you try and wipe data/factory reset, it will hang or timeout after a while. Once it reaches the /data partition, ODIN will hang. You can try and ODIN a stock ROM on top which will basically work for all the components except the /data partition. However later we found it wasn't limited to just CWM Touch and temporary flashing as CWM repacks with the ICS-based kernel also exhibited that behavior, albeit not as often.Įven more frustrating is that this bug is not always deterministic, in that you could do some operation 3 times and have it work fine, then on the 4th, trigger the /data EMMC corruption.Ĭomplicating the testing/debugging is the issue that once the problem is triggered, your phone is basically not recoverable. In particular wipe data/factory reset seemed to often trigger the /data EMMC corruption.
The problem first cropped up when people used ROM Manager to temporary "fake" flash CWM Touch onto an ICS-based kernel to do their flashing needs. Other GS2 models as well as Galaxy Note are experiencing the same thing as can be seen by this Public Service Announcement in the Galaxy Note section. This problem is NOT limited to the Epic 4G Touch. This EMMC corruption is so far non-recoverable, even with JTAG bit blasting, which should bypass all but hardware issues. It is TOO EARLY to make that claim.Īs many of you are aware since ICS has come out, there has been a nagging issue where in some situations flashing ROMs with an ICS-based kernel and custom recovery has left the phone with EMMC corruption. Please do NOT jump ahead and think it is fixed. Even if the fix doesn't address the issue, it is hoped in the process we are able to gather more info into specific "safe" and "unsafe" scenarios. This thread's purpose is to foster discussion on the issue and to determine if the potential fix actually does fix our issue. There has been some communication with the developers in charge of that area to gather further info.
Corruption time android code#
The first release to include that checked in code is FE07. It is possible this might fix the /data EMMC corruption we have been seeing, but we aren't sure if it is fixing the same problem. Garwynn has found a recent checkin from Samsung in the kernel code handling EMMC memory that fixes a data corruption problem. We want to isolate just the FE07 kernel and unlocked stock recovery before introducing new variables. Even if it doesn't apply, the hope is the data we get from testing will help us produce more flexible "safe" flashing practices. Separately we are still discussing whether the fix Samsung checked in will get applied to our phone. We all owe them our thanks for risking their phones to help the community (taking one for the team) No bricks so far. It is the main difference between first and 2nd round of testing and is the current suspectĮsoteric68, azyouthinkeyeiz, and robertm2011 are testing flashing different ROMs with FE07/FE10 repacked with unlocked recovery. Please do NOT use Wipe Data/Factory Reset. Please do NOT do any more testing until further notice. It isn't clear whether the fix would resolve our /data EMMC brick issues, but the point is moot right now because we don't have the fix. It appears after looking at the code more closely and examining the results of the card info dumps, we do not have this fix in our kernel. It appears Sprint/Samsung tested the EMMC brick issue, confirmed the problem, and tested a fix that appears to resolve the problem: Sumrall, Garwynn, Entropy, and everyone else who pitched in!
Corruption time android update#
Why do CM9/AOKP installs often brick in ICS but not in GB?ĥ/24 Update pretty much ties up all the loose ends - Thanks Mr. Pros/Cons of placing workaround in kernel vs libext4_utils.a MD5s of various update-binary executables Section of update-binary afflicted by same issue as wipe data/factory reset
Less technical summary and preparation for new round of testingĥ/31 Lots of discussion on the code path detailing how the problem occurs and where to put the workaround, select posts belowĬall trace for CWM Recovery - wipe data/factory reset We are getting more confident the code analysis was correct. We are ready to have more testers try out the test ROM installs. 6 flashes of CM9, 3 flashes of AOKP, 3 wipe data/factory resets, and 3 nandroid restores, 1 stock FF02 flash, all successful. She has completed the test plan and more. Test plan posted - see bottom of post for results so far (esoteric68, krazy_smokezalot report success)īIG THANKS to Esoteric68 (and robertm2011 before her) who took the plunge to benefit everyone else.
0 kommentar(er)
