12/16/2012, 01:20 PM
|
#1 (permalink) |
|
Member
![]()
Posts: 1
|
After installing cm-9-20121209-NIGHTLY-tenderloin.zip and camera patch my iNand has decided that he's readonly from now on. (The filesystem is stuck - Format via xp - filesystem returns to previous state on reboot / Delete apps in android, the come back on reboot). Webos secure erase does't erase.
I think I have tried all the fixes previously mentioned at this stage. These posts describe similar problem: null0pointer post #147 AniWarlock #164 Daiper5 #170 http://forum.xda-developers.com/show...426244&page=15 Sending back to HP isn't an option because I live in Ireland & I have 3rd party os installed. So I am wondering what are the options. From reading other posts it seems RO is caused by a filesystem problem. Some folks have said the only way to fix is to send back to HP. Since this isn't an option for me I consider what the alternatives are? Given the iNand is designed to go into RO mode when a filesystem problem occurs (to prevent further damage?), then there is a good chance there must be a way for the iNand get out of RO mode. Here are some links on the subject Datasheet http://omapworld.com/iNAND_e_MMC_4_4...1_0[1].pdf JESD84-A441 pdf google SD/MMC Programming Introduction http://nawattlabs.com/index.php/corp...mc-programming ELM - How to Use MMC/SDC Also interesting, dell streak has similar RO iNand problems http://forum.xda-developers.com/show....php?t=1290097 UPDATE: Touchpad eventually died (wouldn't boot at all). Tried debricking with JCSullins method. http://rootzwiki.com/topic/36658-tpdebrick-v01/ It resulted in: "Image Download Failed. Cookie(if present) not received" = iNand failure. Last edited by cofster; 12/17/2012 at 06:26 PM. Reason: spelling |
![]() |
|
| Tags |
| inand touchpad emmc |
| Thread Tools | |
| Display Modes | |
|
|



