Originally Posted by connexion2005
With that said I'm not going to state the ROM flashing experience is to blame here as it would be highly unlikely but at the same time I have seen very odd things happen such as ROM's causing documented digitizer problems on the HD2 when Android or Windows Phone 7 are installed. A while back on the I9000M platform a leaked firmware was causing similar issues to the oneNAND and it was documented as true hardware failure as I could never pull one out of it's partition problems either
To clarify, we are not talking about the act of flashing a rom causing emmc issues, we are talking about partition operations issued from recovery which are interfacing with a new linux 3.0 kernel. This brings into the the picture the possibility these are device driver level issues being exposed.
Imo it is equally hard to believe all these people who combined cwm touch with the ics linux 3.0 kernel are the only ones suddenly having an issue with just the /data partition, and only if they performed a wipe or restore using previously described setup. In addition nobody who has used the previous gb linux 2.6 kernels packed with cwm has ever reported such an issue.
There are too many specifics, imo, for this to just be arbitrary emmc failure. I'm not saying emmc isn't hoarked in some way, clearly it is, as your jtag bit blasting is failing, just imo the previously mentioned actors are somehow involved.
Disclaimer: No touchscreens
were harmed nor injured during the creation of this post. GPS
units were all treated ethically and humanely.
Signed: People against misbehaving Nexus 7 2013s