Please keep all discussion/theories/questions/general complaints in the original "Encryption Unsuccessful" thread! We need to keep this one clean so we can get to the bottom of this. Meaning, do not post here unless you have facts or something with repeatable results!
This thread is to contain all relevant reference information in regard to the "Encryption Unsuccessful" error seen in this thread. There were many users who encountered this error, and there were also many potential fixes posted in that thread, but most of the usefulness is buried within the clutter and confusion. We decided to create this thread in order to keep track of the important details and things that can be proven as fact.
If you do have something to post here, you must report the following information:
ROM:
Kernel:
When the error happened:
How the error happened:
The steps taken to reproduce/resolve the issue:
or if you need to make a different kind of report, just make sure it belongs here and not in the other thread.
See second post for references.
Work in progress... More to come later
Things to try first after getting the error (try not to press "reset phone"):
-Reboot
-Reboot w/o external SD
-Reboot recovery, factory reset, reboot
-Flash CM7
-Flash to stock
Things we know so far:
-The error can result in loss of access to the internal SD card and /data, no matter what is done to the phone.
-The error happens when the Android system cannot mount /data, therefore assuming it is encrypted and throwing the error. We don't know exactly why it results in the data lockout.
-Pressing "Reset Phone" may or may not affect this
-This error is happening across a wide range of devices and ICS ROMs, not limited to the Galaxy S series
-Sometimes, the lockout can be avoided
-The error can happen when the phone is first booted, or may be on the screen when pulled out of your pocket (most common). Often, a user finds the phone stuck on the bootanimation, but it is very dark. A reboot will then bring up the error.
-Data can be recovered, but currently only in isolated cases without repeatable results.
-Data recovery seems to be random
-Users who get this have had battery issues in some cases. Investigation underway... I don't think this is important
-Users who got a random fix seem to be using Glitch kernel... may or may not be important... Kernel may play a role
-Removing/switching external sd can trigger EU again
Possible causes:
-MTP not unmounting properly (strong arguments for and against this)
-Hardware
-eMMC firmware bug, or similar issue
Possible solutions (after losing access to sdcard and /data):
-Glitch kernel flash Link
ROM: Slim 3.0
Kernel: Semaphore 1.0 scbm
Before the error: Phone was OC'd
Solution: 1-2 months after recieving the error, the user flashed an extracted boot.img of Glitch kernel from Doc's ROM. A week later, all of the original files showed up in recovery. The user rebooted and saw "android is upgrading" and all files from /data and /sdcard were back in their original place, but applications and wifi were having issues. User wiped data and all went back to normal. Since it wasn't an immediate result, it's unclear whether the kernel flash is directly related.
Other: User had external sd fix applied on 32GB sd
-Battery Death
ROM: Infinitum 2.2
Kernel: Glitch B6
Before the Error: User flashed Infinitum, and got the error. They pressed "reset phone" and lost access to their data.
Solution: The battery died, and phone was dead for 8-12 hours. Upon turning on the phone, user saw both sd cards and could access /data.
Other: User had external sd fix applied
eMMC Bug (on other devices):
http://www.xda-developers.com/android/hard-brick-bug-on-galaxy-s-ii-and-note-leaked-ics-kernels/
and http://forum.xda-developers.com/showthread.php?t=1644364&page=1
Based on this^ (if it is indeed the cause (which it isn't...)):
-A bug in eMMC firmware causes it to corrupt and fail, usually unrecoverable by any means
-The data partition fails because it is the most accessed
-Certain kernel setups can trigger/prevent this
-Caused by wiping data (or perhaps large operations)
-This explains losing /data, but not the sdcard. Perhaps triggered by the synthetic encryption?
-While parts of the eMMC are gone, it is possible to resize the partitions around the bad area. Works on Galaxy Note, may work for us. Not a solution, but a temporary fix.
-This entire theory could be made invalid by the differences between Galaxy S and the phones in those threads.
From my data so far: There really doesn't seem to be any kind of pattern (I could be overlooking something)
^Don't rely on this theory. Our devices are different, and are facing a slightly different issue. Our issue also involves non-Samsung devices, while the above issue is because of Samsung software. I am still collecting data from users on this because it's possible that there is some kind of remote connection.
Well it seems we don't have the same issue. But the similarity of the outcome of these issues could still mean we have a similar issue where hardware ends up failing.
Incident threads:
-[Guide] Encryption Unsuccessful - Reset Android [ICS Issue]
-Encryption Unsuccessful - Fixed
Resources:
-Notes on the implementation of encryption in Android
-Cyanogen's Post
-eMMC Corruption bug discussion
Effected Devices:
Samsung Captivate~~~(Roms->Infinitum 2.2 (CM9) with 3.1.10_IcyGlitch, Slim ICS 3.6 w/ Semaphore 1.1.1sc, Cyantablet 9)
Samsung Vibrant ~~~~ (ROMs-> CM9, AOKP, Zenwich, Passion, Euphoria, Doc's)
Asus Transformer TF101 ~~~~ (ROMs ->CM9)
Asus Transformer TF101g [3g version] ~~~~ (ROMs ->CM9)
Nook Color [not Nook Tablet] ~~~~ (ROMs ->Rack's Dual Boot Cm7/CM9)
Samsung Galaxy SII <--This seems to hark that something is wrong with the EFS but Adam Outler tried something along the similar lines and it didn't pan out.
Will update with more information when something new comes available.
Change Log:
5/20/12 - Put in Hyperlinks to threads/posts where the error was reported or "fixed"
A link that may play a part...
korockinout13 said:
Work in progress... More to come later
Things to try first after getting the error (and not pressing "Reset Phone"):
-Reboot
-Reboot w/o external SD
-Reboot recovery, factory reset, reboot
-Flash CM7
-Flash to stock
Things we know so far:
-The error can result in loss of access to the internal SD card and /data, no matter what is done to the phone.
-The error happens when the Android system cannot mount /data, therefore assuming it is encrypted and throwing the error. We don't know exactly why it results in the data lockout.
-This error is happening across a wide range of devices and ICS ROMs, not limited to the Galaxy S series
-Sometimes, the lockout can be avoided
-The error can happen when the phone is first booted, or may be on the screen when pulled out of your pocket. Seems random.
-Data can be recovered, but currently only in isolated cases without repeatable results.
Possible causes:
-MTP not unmounting properly
Possible solutions (after losing access to sdcard and /data):
-Glitch kernel flash Link
ROM: Slim 3.0
Kernel: Semaphore 1.0 scbm
Before the error: Phone was OC'd
Solution: 1-2 months after recieving the error, the user flashed an extracted boot.img of Glitch kernel from Doc's ROM, and all files were back in their original place. Happened after a week of being on the kernel, so it is unclear whether that is directly related. More info to come...
Other: User had external sd fix applied.
-
Incident threads:
-[Guide] Encryption Unsuccessful - Reset Android [ICS Issue]
-Encryption Unsuccessful - Fixed
Resources:
Notes on the implementation of encryption in Android
Click to expand...
Click to collapse
Hi, I'm the guy who posted that glitch kernel possible fix post. I was reading what Barney Fyfe posted as his fix, and found something in common. I used a 32gb sd card when I applied the work around. I have no idea if that can play a part in accessing the internal sdcard. I'm just trying to make a connection with why both of us were able to recover our data.
My encryption issue has not reproduced (yet, and hopefully never again), but have since changed my kernel to Devil's Beta and still have access. Hope this can help...
* I was using a 16gb external sdcard before the encryption error came. Changed to 32gb to compensate for lost space.
* After applying work around, access was still restricted to internal for 1-2 months
SMH, even after posting all that stuff in big bold letters, I still posted here..... Sorry.
Bump TTT
There has been 3 people as of the past 2 days that have either come back from the Error or got it, hit Reset and did not get Encrypted.
My Captivate got the reset problem and lost the internal card, a couple of weeks later, the battery died and when I turned it on, the internal card was there again. I didn't do anything but here's what happened.
I started from a CM7 Mubi ROM (don't remember the kernel) and I flashed Infinitum 2.2 (CM9) with 3.1.10_IcyGlitchv14-b6-I896-I897. Then I pressed Reset and lost the card. I flashed Mubi again before realizing it wasn't gonna do anything so I flashed Infinitum 2.2 again.
I applied the solution from the Encryption Guide:
# internal sdcard
dev_mount sdcard /mnt/emmc 1 /devices/platform/s3c-sdhci.0/mmc_host/mmc0
# external sdcard
dev_mount emmc /mnt/sdcard auto /devices/platform/s3c-sdhci.2/mmc_host/mmc2
Click to expand...
Click to collapse
I used my phone relatively normal for a few days. At this point, I'd been using 2 Chinese extended batteries that kept dying sometimes after a couple of hours of use, sometimes if the phone was shaken. So a few days ago, the phone died the same way as always, it was dead for several hours, maybe 8-12 but less than 24.
When I turned on the phone, I kept getting 'Unfortunately X program has stopped' for many apps and half my widgets weren't there. So I decided to flash Infinitum LBR (but didn't yet). When I connected the phone to the computer, I saw both cards so I disconnected the phone and realized that both cards were now available, that would be the 3 partitions:
1) Internal Storage 1.85GB
2) USB Storage 13.03GB
3) SD Card 12.92 GB
From the File manager I see:
1) Home>mnt>emmc (which is also shown as Home>emmc, the files are the same)
2) Home>sdcard
I flashed Infinitum LBR and both cards were still there.
SOME of the new apps are installed on mnt/sdcard/android/data
On mnt/emmc I see some of the same folders with older dates (I assumed they're from their previous installation before the reset problem occurred) but I also see newer folders (from today and yesterday).
I don't know which folders are installation files and which are just data. korockinout13 asked if I could access /data, I can but it's empty.
Sorry if I'm not clear enough, I'm still confused.
Edit 1: Dunno if this is relevant but I'll post it just in case.
It seems that both the OP in Encryption Unsuccessful - Fixed and me had battery issues. In my case, my batteries just died randomly but I was able to charge them. My batteries are still crapping out but they last longer.
Edit 2: One thing I forgot to mention is that the vold file doesn't look like above, it looks like this:
# internal sdcard
dev_mount sdcard /mnt/sdcard 1 /devices/platform/s3c-sdhci.0/mmc_host/mmc0
# external sdcard
dev_mount emmc /mnt/emmc auto /devices/platform/s3c-sdhci.2/mmc_host/mmc2
Click to expand...
Click to collapse
Update 2012-05-30: I noticed that with an app like Headset Button Controller, my profiles aren't saved for good. I mean, they are for a few days (even after removing the battery) and all of sudden, the profiles are gone. I'd used the app for months without any problem until the cards issue so it might be related. I'll email the dev just in case.
Thank you for sorting out all the info, the original thread is now way too lengthy to read.
Although I have a new phone now, I do want to get all the photos and messages in my internal SD back
korockinout13 said:
If you do have something to post here, you must report the following information:
Click to expand...
Click to collapse
ROM: Slim ICS 3.6
Kernel: Semaphore 1.1.1sc
When the error happened: 7pm central, 05/18/12. A few minutes prior, I was running a game called Word Off. That was the only new app I'd installed that day. I'd been on SlimICS/Semaphore for about a month prior.
How the error happened: Pulled phone out of my pocket, saw an unfamiliar animation on the screen (it looked like a horizontal gray bar, cycling -- possibly a dark Slim ICS boot screen). Phone was unresponsive. Pulled the battery and rebooted. Got the Encryption Unsuccessful screen on reboot, and I pushed the Reset Phone button (sorry -- hadn't seen this thread yet).
The steps taken to reproduce/resolve the issue: It appears CWM is mounting my external SD card as /sdcard, and can't mount anything as /emmc. I'm 90% sure that's backwards, but don't know why it would be happening. (Or maybe that's normal in this situation and I just haven't seen it yet.)
I can mount the external SD card just fine on USB using CWM and transfer files to it.
Now I'm rebooting without the external SD several times to see if that fixes it. Assuming it doesn't, I'm going to do a Heimdall or Odin flash to CM7 or stock and go from there.
Any suggestions or other things I should try in the name of science?
UPDATE: Formatted my (external) SD card using CWM. Installed Slim 3.7 and we're back in business. Using the vold.fstab hack from here to remap. This seemed much faster than doing a full Heimdall or Odin wipe, and I don't really need both internal and external SD cards anyway.
ROM: Cyantablet 9
Kernel: The one that comes with the ROM
When the error happened: 18/5. Had been using GB MIUI.
How the error happened:Flashed to Cyantablet 9 and in the first boot i got the encryption message. I pressed the reset button. It rebooted into that android symbol and after like 10 seconds it rebooted again into the ROM. I immediately tried accessing my SD cards and both internal and external are working fine.
Samsung Vibrant
C:\1>adb shell
~ $ su
su
[email protected]:/ # cd /sys/class/block/mmcblk0/device
cd /sys/class/block/mmcblk0/device
[email protected]:/sys/class/block/mmcblk0/device # cat name hwrev fwrev manfid oemid
date type serial cid
wrev manfid oemid date type serial cid <
0x1
0x0
0x000028
0x4245
02/2012
SD
0xbf06287b
284245202020202010bf06287b00c200
[email protected]:/sys/class/block/mmcblk0/device #
Samsung Vibrant
ROM: AOKP B36
Kernel: Glitch kernel which comes with AOKP
When the error happened: 5/19
How the error happened: Phone was just sitting and saw dimmed boot animation. Reboot took me to EU error screen. I didn't press reset. Did a few battery pulls, reboots but nothing. Internal SD was not accessible. A few hours prior to the error, i had the phone connected to PC (NO MTP, rom had mass storage mode but it was not mounted at the time), i applied a theme chooser theme and rebooted while phone was still plugged in (have done it 100s of time before). After the reboot i unplugged the phone and i saw USB icons were still there in status bar. I plugged the cable and then unplugged it again and they went away. EU error happened a little bit later. Another thing to note, i was not using any external card for a while.
The steps taken to reproduce/resolve the issue: I reflashed the rom but same error. I then odin'd back to jfd eclair 2.1 (common way on our vibrant to back to stock) but it did not boot. It would show vibrant logo and would then turn off. I flash Eugene's froyo JK2 i think and it booted into OS. Wifi and all the apps were there as they should be in that rom but no internal SDcard accessible. I tried jfd again but nothing. After that all sorts of rom with same result. Also tried to let battery die by playing youtube videos when i flashed froyo and then i left it untouched for about 20 hours but no change.
Well, my results (Vibrant):
fwrev manfid oemid date type serial cid
SU16G
0x8
0x0
0x000003
0x5344
12/2010
SD
0x0c2b6df0
0353445355313647800c2b6df000ac00
And when I connect phone into PC through USB (I'm supposed to doing this yet?) I can see two drives on My Computer (like H: & I: ) but only the I: is acessible (the external SD card working as internal). The other is with no access (right click > format gives me that there's no device connected at all)
Here are the results from my Vibrant
wrev manfid oemid date type serial cid
SD16G
0x3
0x0
0x000027
0x5048
02/2012
SD
0x7c88d6fe
2750485344313647307c88d6fe00c200
[UPDATE]
[email protected]:/sys/class/block/mmcblk0/device # cat name hwrev fwrev manfid oemid
date type serial cid
wrev manfid oemid date type serial cid <
SD16G
0x3
0x0
0x000027
0x5048
02/2012
SD
0x7c88d6fe
2750485344313647307c88d6fe00c200
Captivate (i896) EDIT: Posted as reference, i'm running under UMS and have not had the EU error (yet).
wrev manfid oemid date type serial cid <
MAG8DE
0x0
0x0
0x000015
0x0100
09/2010
MMC
0xa51212a9
1501004d414738444516a51212a99d00
Alex9090 said:
Samsung Vibrant
ROM: AOKP B36
Kernel: Glitch kernel which comes with AOKP
When the error happened: 5/19
How the error happened: Phone was just sitting and saw dimmed boot animation. Reboot took me to EU error screen. I didn't press reset. Did a few battery pulls, reboots but nothing. Internal SD was not accessible. A few hours prior to the error, i had the phone connected to PC (NO MTP, rom had mass storage mode but it was not mounted at the time), i applied a theme chooser theme and rebooted while phone was still plugged in (have done it 100s of time before). After the reboot i unplugged the phone and i saw USB icons were still there in status bar. I plugged the cable and then unplugged it again and they went away. EU error happened a little bit later. Another thing to note, i was not using any external card for a while.
The steps taken to reproduce/resolve the issue: I reflashed the rom but same error. I then odin'd back to jfd eclair 2.1 (common way on our vibrant to back to stock) but it did not boot. It would show vibrant logo and would then turn off. I flash Eugene's froyo JK2 i think and it booted into OS. Wifi and all the apps were there as they should be in that rom but no internal SDcard accessible. I tried jfd again but nothing. After that all sorts of rom with same result. Also tried to let battery die by playing youtube videos when i flashed froyo and then i left it untouched for about 20 hours but no change.
Click to expand...
Click to collapse
Very similar situation as above, had just flashed to b36 from milestone 5.
Haven't had a chance to repartition through Odin as I am away from home and only have my netbook. A viable workatound may be an a2sd init.d hack or complete initram change for affected devices.
Captivate (i896) (Posted as reference, since I have not suffered the EU bug... still on CM7).
wrev manfid oemid date type serial cid
MAG8DE
0x0
0x0
0x000015
0x0100
07/2010
MMC
0x4112fa73
1501004d4147384445154112fa737d00
I'd really like to see the values for a Captivate affected by the bug.
Galaxy S II (GT-I9100)
Was on recent CM9 nightly
ADB output:
Code:
[email protected]:/sys/class/block/mmcblk0/device $ cat name hwrev fwrev manfid oemi
d date type serial cid
fwrev manfid oemid date type serial cid <
VYL00M
0x0
0x0
0x000015
0x0100
05/2011
MMC
0xe8595874
15010056594c30304d19e85958745ef7
Update 2012-05-30: I noticed that with an app like Headset Button Controller, my profiles aren't saved for good. I mean, they are for a few days (even after removing the battery) and all of sudden, the profiles are gone. I'd used the app for months without any problem until the cards issue so it might be related. I'll email the dev just in case.
I found 2 links today they are very useful and they might be our solution to our problem
http://forum.xda-developers.com/showthread.php?t=1621835 READ THE FIRST LINK FIRST IT HAS OUR PROBLEM http://forum.xda-developers.com/showthread.php?t=1611796 THIS IS OUR SOLUTION
manu_ha2001 said:
I found 2 links today they are very useful and they might be our solution to our problem
http://forum.xda-developers.com/showthread.php?t=1621835 READ THE FIRST LINK FIRST IT HAS OUR PROBLEM http://forum.xda-developers.com/showthread.php?t=1611796 THIS IS OUR SOLUTION
Click to expand...
Click to collapse
Not quite the same, the problem I mean, that user saw himself unable to use ICS roms. Captivate phones stop having a functional sdcard altogether.
Still worth the shot though, no doubt.
Related
Hi.
I'm running SyndicateROM Frozen 1.1.1, and I've observed several bugs. I need to know if the bugs are the fault of the ROM (and thus something I should take up with the ACS developers) or if they're my fault due to something I'm doing wrong.
1) I use folders on my LauncherPro* homescreens to organize apps. For this example, I'll use my Games folder. In it, all the games except 1 are installed onto my microSD card. After I drag the icons to the folder the first time, they are fine. However, after a reboot, the icons of the apps installed to my microSD card that are in folders change to the generic Android green/white icon. The apps still load properly, and the icons appear fine in the App drawer.
*LauncherPro is included as the only homescreen in this ROM.
2) I'm having an odd issue with Plants vs. Zombies. It loads to the main screen, and I can manage the player names, but after I click to start the adventure, it locks up with the Adventure button depressed. The main screen music also dies. No FC/wait dialog appears. I have to press the Home button to get out of it. PvZ is unplayable in this condition. Rebooting does not help, nor does formatting /cache or Dalvik-cache in custom recovery.
3) JuiceDefender Ultimate tells me in the log that it cannot toggle 2G/3G data, and that this is likely to be a kernel issue. As far as I know, this reduces the effectiveness of JD.
4) In ClockwodMod Recovery 3.0.0.6, I cannot mount my microSD card for the PC to read/write it. I get "E:Unable to open ums lunfile (no such file or directory)". I've seen posts that indicate this is a bug that was corrected in later versions, but I don't know if the custom ROM I am running is compatible with later versions,or where to find later versions. EDIT: I found CWM 3.0.2.5, and flashed it. It still reports the same error when attempting mount my microSD card for my PC to work with.
5) When I connect the phone's cable to my PC and get the the "Charging/Mass Storage/Tethered" popup and click Mass Storage, and then click "Turn On" at the next screen, it appears to work fine, except that my PC shows no new removable media drives. Sometimes, even though I touched the "Turn On" button, nothing happens. The button does not turn into a spinning wait indicator, nothing.
6) I found a post (that I've since lost track of) that purported to provide instructions to see if journaling was enabled. (I'm already formatted as EXT4). The instructions errored out, apparently because I have the wrong version of tune2fs. I'm not sure how to copy the correct version over, so I flashed the "Journaling On" zip shortly after I re-flashed this ROM. Does EXT4 and journaling stick between ROM re-flashes?
SweetBearCub said:
Hi.
I'm running SyndicateROM Frozen 1.1.1, and I've observed several bugs. I need to know if the bugs are the fault of the ROM (and thus something I should take up with the ACS developers) or if they're my fault due to something I'm doing wrong.
1) I use folders on my LauncherPro* homescreens to organize apps. For this example, I'll use my Games folder. In it, all the games except 1 are installed onto my microSD card. After I drag the icons to the folder the first time, they are fine. However, after a reboot, the icons of the apps installed to my microSD card that are in folders change to the generic Android green/white icon. The apps still load properly, and the icons appear fine in the App drawer.
*LauncherPro is included as the only homescreen in this ROM.
2) I'm having an odd issue with Plants vs. Zombies. It loads to the main screen, and I can manage the player names, but after I click to start the adventure, it locks up with the Adventure button depressed. The main screen music also dies. No FC/wait dialog appears. I have to press the Home button to get out of it. PvZ is unplayable in this condition. Rebooting does not help, nor does formatting /cache or Dalvik-cache in custom recovery.
3) JuiceDefender Ultimate tells me in the log that it cannot toggle 2G/3G data, and that this is likely to be a kernel issue. As far as I know, this reduces the effectiveness of JD.
4) In ClockwodMod Recovery 3.0.0.6, I cannot mount my microSD card for the PC to read/write it. I get "E:Unable to open ums lunfile (no such file or directory)". I've seen posts that indicate this is a bug that was corrected in later versions, but I don't know if the custom ROM I am running is compatible with later versions,or where to find later versions. EDIT: I found CWM 3.0.2.5, and flashed it. It still reports the same error when attempting mount my microSD card for my PC to work with.
5) When I connect the phone's cable to my PC and get the the "Charging/Mass Storage/Tethered" popup and click Mass Storage, and then click "Turn On" at the next screen, it appears to work fine, except that my PC shows no new removable media drives. Sometimes, even though I touched the "Turn On" button, nothing happens. The button does not turn into a spinning wait indicator, nothing.
6) I found a post (that I've since lost track of) that purported to provide instructions to see if journaling was enabled. (I'm already formatted as EXT4). The instructions errored out, apparently because I have the wrong version of tune2fs. I'm not sure how to copy the correct version over, so I flashed the "Journaling On" zip shortly after I re-flashed this ROM. Does EXT4 and journaling stick between ROM re-flashes?
Click to expand...
Click to collapse
OK can only answer some of these. I heard Launcher Pro can take a little while to read icons from the sd card. You may want to download and try Zeam launcher.
The Plants v Zombies may be a result of overclocking/undervolting. Try it again with no undervolting and your speed set to 1Ghz max and 200 Mhz min.
Not sure why you are mounting the sd card in clockwork. Sounds like either your cable is flaky or you need to reinstall the Samsung drivers to connect your USB. Also try different USB ports and turn USB debugging on. I had to reinstall the drivers for each port on my laptop as it would only recognize my phone in one of them originally.
No, journaling does not carry through other ROM flashes. If you flash a no-journaling ROM, you will have no journal unless you turn it back on. Some can be turned on simply be making a nand backup then immediately restoring it. Others work fine with the journal on flash. And some are more special and need a specific script like Bonsai.
Hope some of this helps.
SweetBearCub said:
Hi.
I'm running SyndicateROM Frozen 1.1.1, and I've observed several bugs. I need to know if the bugs are the fault of the ROM (and thus something I should take up with the ACS developers) or if they're my fault due to something I'm doing wrong.
1) I use folders on my LauncherPro* homescreens to organize apps. For this example, I'll use my Games folder. In it, all the games except 1 are installed onto my microSD card. After I drag the icons to the folder the first time, they are fine. However, after a reboot, the icons of the apps installed to my microSD card that are in folders change to the generic Android green/white icon. The apps still load properly, and the icons appear fine in the App drawer.
*LauncherPro is included as the only homescreen in this ROM.
2) I'm having an odd issue with Plants vs. Zombies. It loads to the main screen, and I can manage the player names, but after I click to start the adventure, it locks up with the Adventure button depressed. The main screen music also dies. No FC/wait dialog appears. I have to press the Home button to get out of it. PvZ is unplayable in this condition. Rebooting does not help, nor does formatting /cache or Dalvik-cache in custom recovery.
3) JuiceDefender Ultimate tells me in the log that it cannot toggle 2G/3G data, and that this is likely to be a kernel issue. As far as I know, this reduces the effectiveness of JD.
4) In ClockwodMod Recovery 3.0.0.6, I cannot mount my microSD card for the PC to read/write it. I get "E:Unable to open ums lunfile (no such file or directory)". I've seen posts that indicate this is a bug that was corrected in later versions, but I don't know if the custom ROM I am running is compatible with later versions,or where to find later versions. EDIT: I found CWM 3.0.2.5, and flashed it. It still reports the same error when attempting mount my microSD card for my PC to work with.
5) When I connect the phone's cable to my PC and get the the "Charging/Mass Storage/Tethered" popup and click Mass Storage, and then click "Turn On" at the next screen, it appears to work fine, except that my PC shows no new removable media drives. Sometimes, even though I touched the "Turn On" button, nothing happens. The button does not turn into a spinning wait indicator, nothing.
6) I found a post (that I've since lost track of) that purported to provide instructions to see if journaling was enabled. (I'm already formatted as EXT4). The instructions errored out, apparently because I have the wrong version of tune2fs. I'm not sure how to copy the correct version over, so I flashed the "Journaling On" zip shortly after I re-flashed this ROM. Does EXT4 and journaling stick between ROM re-flashes?
Click to expand...
Click to collapse
1) you can get a different launcher from the market. I've never had any luck with pushing apps to sd.
2) that's a issue with the game. Try changing your max and min cpu.clocks. If you uved you may be to low.
3)jd is a pos and you don't need it. I go on average of 12-16hrs a day with 3+ hours of screen on. And a synce interval of every hour
4) no versions of cwm on the epic has allowed you to mount your sd to pc for the epic. Cwm was ported to the epic and not created by koush him self so some things are broken.
5) try a different cable and usb ports. This is a known problem even while on a stock rom
6) yes it sticks unless the rom your flashing changes it.
Sent from my SPH-D700 using Tapatalk
Thanks Mystery for validating my advice...LOL. Would like to see you around here more.
cwm 3.1.0.1 allows mounting the sd card to pc in recovery..
chris41g said:
cwm 3.1.0.1 allows mounting the sd card to pc in recovery..
Click to expand...
Click to collapse
I forgot they fixed that. But anything before that don't allow this
Sent from my SPH-D700 using Tapatalk
kennyglass123 said:
Thanks Mystery for validating my advice...LOL. Would like to see you around here more.
Click to expand...
Click to collapse
I'm knee deep on working on sfr1.2
Sent from my SPH-D700 using Tapatalk
After rooted the official gingerbread my device was never the same.
Let me try to explain what is happening to see if someone can help.
Official roms:
When I turn my device to PC via USB and then choose the option Mount USB Storage what happens is in the device the Android stays Green with the option below to mount storage, the SD card is apparently un-mounted from device but in the PC I can see the SD card content normally and see it as a removable storage drive
Custom roms:
When I turn my device to PC via USB and then choose the option Mount USB Storage what happens is in the device the Android stays Green with the option below to mount storage, the SD card is apparently un-mounted from device but in the PC I can see the SD card content but can’t make any changes as it opens up as a CD drive. Imagine you put a CD/DVD in your drive you can see all the files but you cannot write on it.
What can I do as seems to be a deep system alteration that won’t change by doing anything at all such as flashing new roms, changing complete content of pink screen, factory resets, etc, etc.
Can someone plz help me with this?
try this with cm7
settings->about phone->project menu->USE GOOGLE USB
I stuck with 2.3 official again!!!
I think I going to deliver my phone to TMN and say that got ****ed up after official upgrade instalation
I've read somewhere that the TMN ones (or some of them) are called "black sheep" since they have some problems (installing other roms I think), maybe your problems where there all along and the updates brought them to the surface...
Yeah, send it back
Yes I know, but I got lucky as my device is like a Hummer.Mine is not.
Goes over of it all, until I messed up... lolol
druida did you format the sd card on the pc and chnage the partition size?
I have the device partitions resized months ago.
yes card was formated and formated and formated.
priestx said:
I've read somewhere that the TMN ones (or some of them) are called "black sheep" since they have some problems (installing other roms I think), maybe your problems where there all along and the updates brought them to the surface...
Yeah, send it back
Click to expand...
Click to collapse
I have a so called "black sheep" and official 2.3.5 is rooted and runnin' flawlessly.
try revert to 2.2.2 using internal sd card.
I got it at last doing this:
Dial * # * # 2846579 # * # *
Background Setting > USB ports setting > choose "Normal Mode" and then rebooted.
The option that was by default and was giving me all this trouble was "Manufacture mode".
Tried to choose "Google Mode" but after reboot revert back to "Manufacture mode" again.
This way every time I connect the USB and choose the option Mount Usb Storage the SD was getting unmounted in the device but in the PC was showing as removable disk giving me full access.
When I unplug the cable I had to mount the card again.
****ing weird!!!!
priestx said:
I've read somewhere that the TMN ones (or some of them) are called "black sheep" since they have some problems (installing other roms I think), maybe your problems where there all along and the updates brought them to the surface...
Yeah, send it back
Click to expand...
Click to collapse
no they are not (me +2other friends have such phones). it's hapenning the same as before: people messing up.
Well, this problem is not related to 2.3.5 update, but with updates in general, 'cause i have it about a month ago. Same thing as you, but if U use a 2.2 custom ROM (flb or void) you should mount usb properly. If U go to device manager you will see that the drivers aren't properly installed.
Altough I don´t know the exact time, i think my probelm begins when after flashing a ROM I got the blue screen and needed to install b138 elisa. I guess after we get a blue screen the phone never is the same.
BTW i got 0 imei. And have an theory to this to. The IMEI are related to an operator, so when flashing a official rom not from operator, maybe the phone goes crazy and the IMEI begins to shown 0, it's not a big deal, since we can communicate normally with people.
so how do I install the drivers correctly?
I found a way to revert from 2.3 and I'm in MIUI again but USB issue still there shiiiiiiit
Druida69 said:
so how do I install the drivers correctly?
I found a way to revert from 2.3 and I'm in MIUI again but USB issue still there shiiiiiiit
Click to expand...
Click to collapse
I d0n't lnow, i don't have an solution, I install some drivers that are in huawei server, but with no luck.
The main point is: using a 2.2 rom, all ok, upgrade to a 2.3 rom, and U have problems, so the problem it's not on pc and in hardware, the problem somehow is software.
What I'm wondering it's that the official 2.3.5 help with this problem, but with your report the hope dissapear...
yes the problem is in the device nt in PC.
I think its missing the adb USB drivers inside the device.
and yes its software problem not hardware
Druida69,
Is your IMEI 0 ?
Do you have wifi ERROR in 2.3 Custom Roms ?
I have that USB problem since I tried to format SD Card directly from the mobile, with CM7... all problems started there... and there is another user over here that made the same with MIUI.
nrdl said:
Druida69,
Is your IMEI 0 ?
Do you have wifi ERROR in 2.3 Custom Roms ?
I have that USB problem since I tried to format SD Card directly from the mobile, with CM7... all problems started there... and there is another user over here that made the same with MIUI.
Click to expand...
Click to collapse
ME! Me Me! lol
I have this problem, but don't have problems with wi-fi, my imei is 0 also, but if you use custom or stock 2.2 the usb works fine, so don't think that the problem is caused by formating the sd... I guess is that the libraries in 2.3 somehow changed, i guess the libraries from geno changed a while ago, and therefore this bug appears. It's not for everyone 'cause we all know that x5 have personnality, so...
regarding IMEI yes its 0.
I don't know when it happen and how it was before as I never look for it, up to this moment.
Regarding the USB, I think start to happen when I tried to root the official 2.3.
All drivers in computer are fine as I uninstall them and install all again just to make sure.
Something change something deep inside the phone software and mess all of it.
I manage to do a shortcut though. In official 2.3 you can mount usb storage again if you do this:
dial *#*#2846579#*#*
then you will be inside Project Menu.
Go to Background setting > USB ports setting and you will see these options:
Normal Mode
Google Mode
CTS test mode
Manufacture mode
Authentication mode
Other Mode
By default all systems are with Google Mode activated.
Change to Normal Mode and it solve the problem.
If you try to change this option in CM7 for example, won't work, odd but I don't know why...
Hello !
This USB issue happens to me since CM7 (imei 0, wifi error...). And it happens with all roms (even 2.2.2 stock rom)
I can use usb storage, but in the end I have to manualy mount card again.
With 2.3.5 Official I went into Project Menu and was already in Manufacture Mode, if I change it to Google Mode everything works normally... but after a reset setup returns back to Manufacture Mode.
It is a solution... temporary... but it is
why dont u switch back to cm7 or oxygen and give it a try . surely there is some problem with official 2.3 , mine sometimes says " sd card damaged and stuff .format ... " . am switching back to cm7 . dont want this waste of time rom . ( u know how long we have waited 4 this official update . cant even manage power widgets n LED without external app . f**kin huawie )
mkr17 said:
why dont u switch back to cm7 or oxygen and give it a try . surely there is some problem with official 2.3 , mine sometimes says " sd card damaged and stuff .format ... " . am switching back to cm7 . dont want this waste of time rom . ( u know how long we have waited 4 this official update . cant even manage power widgets n LED without external app . f**kin huawie )
Click to expand...
Click to collapse
As I said before, this problem, regardeless appears more often now, it's not related with the update to official 2.3.5 since I and at least to people more, have this problem before official beta rom appears... It is related to the process of upgrading any rom, and I think it happens when we get a pink screen...
Well, my Nook appears to be in trouble.
The long and the short of it is that it got wet. Not too wet, but wet.
It boots but whatever I boot to crashes. This includes sdcard installs. The ROM completes the boot, and I can sometimes even open the app drawer, but it crashes before I can interact with it in any meaningful way.
All ROMs complain of "System process" and Wireless issues, with FCs.
I cannot get adb to recognize the device anymore. lsusb does find the Google Inc. entry, though. When I try and run adb devices (ubuntu), it returns ?????? and says insufficient permissions. I have, in response, set up the 99-android.rules in etc/udev/rules.d but it still cannot connect. I have also tried to quickly access the android terminal in the brief period I am allowed before the device crashes with no luck. My goal with this was to try fdisk -l.
The sdcard never mounts while in the ROM, and the emmc storage appears completely wiped.
However, I was able to see I had the correct files in /rom once, so those are there.
Thinking that the wireless chip might be the problem (as when even when I return to stock the set-up fails there, well, until it crashes again...) I tried to just turn off Wifi in 7.2. But as I unchecked the box, right under the setting just displayed "error"
CWM appears to be working EXACTLY as it should, including mounting the sdcard and allowing me to choose update zips.
The uboot and the uboot menu work as well.
I have tried flashing CM7, 9 and stock, as well as booting from sdcard in CM9. All flash and boot normally, but crash.
I have done the 8x reboots, succesully, but when the B&N set-up begins, I cannot connect to wireless. Which would be okay, in the long run, but it then crashes, which is not okay.
I was hesitant to reveal that it got wet, because I can see this being written off as a hardware issue (which it may be, don't get me wrong). But the fact that CWM works and the ROMs boot sure look like software problems to me.
I have tried flashing just about everything that looked promising. I have not dd any images, because I cannot get adb to work, and don't have any idea which partitions are in what shape.
Any suggestions?
Position the unit upside down with the SD flap open. Blowdry it from the bottom up on medium several times over a couple of days. If it's still doing it after that you can probably eliminate moisture as a cause.
old cell phone trick
Fill a bowl with rice (uncooked).....the rice will draw the moisture out.
you can also submerge it in ispropol rubbing alcohol... is what we use to clean electronic components... it will combine with the water... also used for water in gas on a car
Whoa, isopropyl alcohol. I feel like that would take some stones...
I have already put it through a 30 or so hour rice regimen (if that is true, even. It makes some kind of weird intuitive sense, which is usually the kiss of death...)
I have it standing up now and will see about a little air dry method while I investigate where to find the alcohol.
It didn't get submerged, it was lying on a counter and a glass got knocked over. I grabbed it right up, and then left it off like I said.
It boots, CWM works, but since it has been set all the way back to stock and all iterations have the same issue I am fearing the worst...
Thanks for the ideas...any and all welcome!
You can take the back off. I have not done it, but somebody just said they did it to disconnect the battery to reset. Look at that recent thread in q/a. Maybe he can tell you how he did it.
Attempt at your own risk, no support will be provided.
I'm not the battery guy leapinlar was talking about but,
Open the battery flap, remove SD card, remove the tape dots from the T-5 torque screws then remove the screws. Slowly and carefully so as not to break any of the hooky thingies that are holding the back on pry the cover up from that point moving slowly around the unit.
I've only done this once, it was a while back and I ended up breaking two of the little hooky thingies. That's why I suggested providing points for evaporation to escape and attempting to accelerate evaporation. Heck we don't even know if moisture is the issue anymore.
Thanks for the extra suggestions.
I tend to think at this point that whatever water got in there is gone. It's been four days, and it wasn't soaking. I may just go ahead and try and take out the battery, I don't know exactly why that would help, but what have I got to lose?
If I had to guess, I would think that the wifi chip might be shorted, as that is the only thing that doesn't seem to work at least for some period of time.
The FC's sure do look software related though. I fail to see how CWM could read and mount the sdcard while the ROM cannot as being anything other than sotware. Unless they use wildly different methods to do the same thing.
This nagging feeling that I should be able to at least fix that with some software methods keeps me thinking the same or the other problems. I'd be okay with an non-networked tablet, if it came to that. But maybe the thing has to have wifi as an option to work right. I don't know...
Two weeks ago my daughter managed to completely soak her nook.The nook would just constantly reboot with the stock os and system process would repeatedly fc with the cm7 sdcard. I pulled the back cover off and let it stand for a week. Today I pulled the battery and power button cable and it booted up just fine so far. So there is hope.
Malave said:
Two weeks ago my daughter managed to completely soak her nook.The nook would just constantly reboot with the stock os and system process would repeatedly fc with the cm7 sdcard. I pulled the back cover off and let it stand for a week. Today I pulled the battery and power button cable and it booted up just fine so far. So there is hope.
Click to expand...
Click to collapse
Considering that this is basically what is happening to me (but with some additional Wifi setting crashes) this gives me hope.
I had burned a bootable CWM card, from Leapinlar, which was a higher version than I usually used. I think 5.5.0.4 (?)
Anyway, of interest (before I shut it down 2 days ago):
internal sd card is not wiped, it can be explored in CWM.
The /ROM partition is at least somewhat functional, as battery stats can be wiped
When I request a log, I get:
Code:
Battery Stats
Block Groups: 3
reserved block group size: 23
Created filesystem with 11/22608 inodes
and 2883/90357 blocks
warning: wipe_block_device: Discard Failed
W: failed to mount /dev/block/mmcblk1p2 (no such file or dir)
also at one point:
Code:
make_ext4fs failed on /dev/block/mmcblk1p2
(note: both of the above from hastily scrawled notes)
It looks like mmcblk1p2 is related to system mounting, although I am not sure. Maybe that is why I am having trouble with ADB. It just kept saying insufficient permissions and ???????????. I tried setting up android-rules for udev with no luck.
Unless I hear anything else promising, I will go get the proper screwdriver and try the battery thing. It has been sitting off for a couple days now...
Thanks for all the ideas, people.
I'm confused... but trying to help you out... why are you trying that stuff on /dev/block/mmcblk1p2 when /dev/block/mmcblk0p2 is the ROM partition?
Try your edits to /rom... and if you have to try: mount /dev/block/mmcblk0p2 /rom
DizzyDen said:
I'm confused... but trying to help you out... why are you trying that stuff on /dev/block/mmcblk1p2 when /dev/block/mmcblk0p2 is the ROM partition?
Click to expand...
Click to collapse
I actually didn't try to do anything. I just wiped system, cache, davlik, battery stats and asked for a log prior to flashing a new zip in the hopes that the rom would work if provided a blank slate.
I wiped battery stats since the .bin that holds them is in /rom. The log was something I had never done before.
The notes from above were just the CWM output from the log.
edit: I just saw your second paragraph. Don't know how I missed it.
But I don't know what you mean by edits. I haven't been able to get ADB working. I have been able to mount and unmount through CWM that's it. Unless you might know anther way to resolve insufficient permissions with beaucoup question marks instead of device number?
Ok... sorry about my confusion on that... It appears that you are using a CWM that is modifid to work on SD... since it is trying to access /dev/block/mmcblk1p2 since the rom partition is on /dev/mmcblk0.
I would try a different version of recovery.
DizzyDen said:
Ok... sorry about my confusion on that... It appears that you are using a CWM that is modifid to work on SD... since it is trying to access /dev/block/mmcblk1p2 since the rom partition is on /dev/mmcblk0.
I would try a different version of recovery.
Click to expand...
Click to collapse
Which I was. I got it from Leapinlar, and was under the impression, since I had seen him warn that roms flashed from that recovery would go to emmc, that it would work.
I did make a regular 3.2.0.1 bootable, and tried again, but with the same result, so I don't know if that made a difference. But it did seem hopeful, so thanks for the response.
I am going to finally go get the torque screwdriver and take this battery off and give it some days. It's been almost a week already, but you never know.
Thanks a bunch for the reponses, Diz.
mateorod said:
I had burned a bootable CWM card, from Leapinlar, which was a higher version than I usually used. I think 5.5.0.4 (?)
warning: wipe_block_device: Discard Failed
W: failed to mount /dev/block/mmcblk1p2 (no such file or dir)[/CODE]
also at one point:
Code:
make_ext4fs failed on /dev/block/mmcblk1p2
(note: both of the above from hastily scrawled notes)
It looks like mmcblk1p2 is related to system mounting, although I am not sure.
Click to expand...
Click to collapse
Mateorod, if you got that log using my CWM boot SD version 5.5.0.4, the recovery.fstab lists /dev/block/mmcblk1p2 as SD-EXT, which for some devices is the extended partition on SD for storing additional apps to supplement /data. Our implementation of CM does not use that. So when recovery tries to do some wiping, formating, backing up, etc, it always fails when it looks for that partition. It has nothing to do with /system or /rom.
If you told it to do a factory reset, it tries to wipe /SD-EXT as part of that and it fails to wipe that because it cannot find that partition.
Edit: That CWM SD does do its modifications to emmc. It only referenced mmcblk1p2 because of sd-ext.
Here is the filesystem table from my log using it on SD:
0 /tmp ramdisk (null) (null) 0
1 /boot vfat /dev/block/mmcblk0p1 (null) 0
2 /system ext4 /dev/block/mmcblk0p5 (null) 0
3 /data ext4 /dev/block/mmcblk0p6 (null) 0
4 /cache ext4 /dev/block/mmcblk0p7 (null) 0
5 /emmc vfat /dev/block/mmcblk0p8 (null) 0
6 /sdcard vfat /dev/block/mmcblk1p1 (null) 0
7 /sd-ext ext4 /dev/block/mmcblk1p2 (null) 0
The alcohol trick does work, I did it on my old HTC Kaiser. I disassemble it as much as I was comfortable, and then completely submerged it in alcohol until It stopped throwing up air bubbles; Thus showing there was no air left in the unit. I then removed the pieces from the alcohol and put them in a bowl of rice. I let it stand for about a week. Once the time was up a reassembled and turned it on like nothing had happened.
Little note: I was in the possession of a AT&T Go Phone for use as a back up in case this destroyed the unit. If you feel that there might be another way to repair it, I would suggest you explore that option first as I do not know what a significant time in alcohol will do to the inner workings of the Nook. However if you are at the point of already replacing or upgrading to a different tablet, than you have nothing to lose and can only gain a working Tablet or fancy Paper-weight from this.
Okay, a little update.
I had taken apart the Nook and let it sit for almost a week. But upon reconnecting the battery and clearing system/cache/davlik and reflashing anything, it still wouldn't allow in-ROM mounting of sdcard or adb or wireless and I would still get some version of "process System not responding" and "Setting Wireless not responding" toasts and then a crash, either in CM7, CM9 or Stock. Unusable.
What I think I have is a totally borked wifi chip. Which is okay, in the long run, but the Nook kept crashing and I would have liked to use it in some capacity.
What I decided (which was difficult to diagnose with no terminal or no ADB) was that the Nook was crashing upon trying to access the network and the saved network info. (which I know is mad persistent, as the wifi network I used to originally register the device still shows up in the stats, even after many many system wipes and 8x reboots and so forth.)
I had never reset to factory from stock settings and I couldn't now completely erase and deregister because you need wifi to do so.
However, I found this (which I had never heard of, sounds like a boon to thieves everywhere). After skipping out-of-box experience I could boot into stock recovery and finally erase the wireless settings.
Now I have a stable (albeit un-registered) stock nook, where I can at least read the books I have on sdcard.
I will eventually reflash a CM build now that the network settings have been forgotten and see if that is usable, even if there is no wifi.
But I am pretty happy to have some semblance of the Nook back, even if it is just a neutered (literally) stock.
I'll let you know how CM goes one day soon.
Thanks for the help!
Excellent, (and powerful), link.
And by virtue of that link I will find a way to proclaim my absolute geekitude within the company by dropping Kate's name. :good:
Well, I finally tried flashing Cyanogen 7 and 9 to the thing, but as it crashes when it tries to access wifi, I can't get it stable.
Unless anyone knows a code edit (smali maybe? I know there are a bunch of boolean settings in the SystemUI.apk, maybe there) where I can change the default wifi setting, I may just be stuck with stock.
Which is way better than nothing, at least it has use. Skipping OOBE was a life-saver for getting to a place where I could erase the WiFi info.
Okay, here's another shot in the dark, still trying to get this thing to successfully boot in CM...
I am working on a little project for the Nook, which will be infinitely easier to debug if I can actually boot into CM.
Does anyone familiar with the source code know how to modify it so that WiFi is set to off by default? I am thinking about changing the 'true' to 'false' in the /device/bn/encore/overlay/frameworks/base/core/res/res/values/config.xml entry for wifi found here...
Code:
<!-- This string array should be overridden by the device to present a list of network
attributes. This is used by the connectivity manager to decide which networks can coexist
based on the hardware -->
<!-- An Array of "[Connection name],[ConnectivityManager connection type],
[associated radio-type],[priority],[restoral-timer(ms)],[dependencyMet] -->
<!-- the 5th element "resore-time" indicates the number of milliseconds to delay
before automatically restore the default connection. Set -1 if the connection
does not require auto-restore. -->
<!-- the 6th element indicates boot-time dependency-met value. -->
<string-array translatable="false" name="networkAttributes">
<item>"wifi,1,1,1,-1,true"</item>
<item>"bluetooth,7,7,0,-1,true"</item>
<!-- item>"ethernet,9,9,2,-1,true"</item -->
</string-array>
This looks like I am on the right track (this will eventually end up being compiled into the res folder of framework-res.apk) but I may need to track down the ConnectivityManager. Although the cursory look I have given this seems like I may be close to on the right track...
(The wifi being on at boot always crashes my CM installs due to shorted wifi chip, for those of you who may be new to the thread.)
I am asking here just in case someone knows, I may just go ahead and try it if no one chimes in. But better to ask than to blindly shoot in the dark, I figure...
Update: Success. I am back on CM9 (well, a hybrid, actually...HINT), without wifi.
Update 2: Due to the fact that this nook is now in a Cyanogen-usable state, a new rom will be posted in development tomorrow from eyeballer and I. Thanks for the suggestions, everyone. I wish I had dipped it in isopropyl alcohol, just so I could say I did it...
First of all, a huge thanks to the creators and maintainers of touchnooter and noogie, and all the helpful people on the forums (like this one)
My rooted NST has been incredibly useful and reliable up till now, It contains tons of books and articles waiting for a few sunny days....
However, lately it has been acting a little flaky (segfaults from busybox, notifications not opening, nothing really serious). And then one day it remained stuck on the "rooted forever" screen. I did try a few remedies, but nothing helped (I never made a full backup of the machine ) and I finally ordered a new machine (the glowing version, this time)
Out of sheer curiosity I flashed my SD card with noogie.img, booted from the card, connected the Nook via USB and had a look at the internal storage, in the hope of seeing something that I could correct. The partition table looked fine, but when mounting /system (partition #5) and then listing its contents I got an error message :
# mount /dev/sdb5 /mnt/test
# ls -lR /mnt/test
/mnt/test/xbin/blah: I/O error
(.... rest of listing)
Click to expand...
Click to collapse
This suggested that the internal storage got corrupted somehow. And sure enough,
# fsck /dev/sdb5
Click to expand...
Click to collapse
turned up a lot of errors. After letting fsck do its thing, the Nook now booted normally! I will keep my fingers crossed: there may be a hardware problem that has caused the corruption, and then it will re-occur...
Google didn't turn up this scenario, so I post my story here for the benefit of others who might find it useful. In my case, a full restore of a previous backup (which I didn't have...) would have worked, but would have cost me all the changes I made since that backup.
I am a linux user, but I would be surprised if cygwin and the windows Ext2fs driver couldn't do the job under windows, using approximately the same commands.
So, in a few days, I will be the owner of two working nooks
Hi all,
Has anyone else experienced data corruption on the /system partition? I'll probably have to return my tablet for replacement, but am wondering if it's happened to anyone else, or if it's just me.
Background:
A few weeks ago my Nexus 7 rebooted itself and became stuck at the 'X' logo - recovered by doing a full system re-image. It then worked for a week or so, then suddenly everything started force-closing, and after reboot I was back at the 'X' logo hang. This time fortunately I had debugging enabled and was able to dig a little further - turned out that several files in /system/framework differed from the ones in the original system image, even though they'd only just been reflashed - restoring those files from the image was sufficient to repair the system.
Just tonight it started happening again, and yet again one of the /system/framework files had changed. Comparing against the originals, it looks like a small number of bit errors, rather than any deliberate attack. In this case, framework.odex had a little over 1000 bytes with 1- or 2-bit errors, mostly (~80%) changes from 0 to 1. At this stage, I'm presuming that some kind of hardware corruption is going on here (considering it's normally a read-only partition).
Regards,
Nathan
I have experienced significant filesystem (ext4) corruption in /system (cross-linked block allocations), but I haven't observe "bit rot" in individual files afaik. I suppose bit-rot in filesystem metadata could produce the symptoms I observed, so I can't rule it out.
I thought I had a working hypothesis about why it was happening, and attributed it to something I was doing in TWRP, but I haven't run that hypothesis down yet. I am using lightly-rooted stock, so when this happened to me, I had only done a few things in /system such as the SuperSU kit and adding in the AOSP stock browser.
Anyhow - for the moment - the bit rot you describe does sound like media read errors & probably different than what I experienced. In either case, I certainly sympathize - it doesn't exactly instill a sense of confidence.
I thought that eMMC flash was supposed to be a lot more robust than MTD flash - things like automatic block remapping & wear leveling inside the controller allowing ext3/4 to be safe to use without causing premature failure... and even more so (you would think) with filesystems which are mostly used with read-only mounts.
Anyhow - because it keeps happening to you - you might want to revert to pure stock & relock your bootloader if your tablet is still under warranty. The next time it happens, set up an RMA, factory reset (using the stock recovery...) and send it in. (Even though it is a legitimate warranty defect situation, you can't really describe your diligence in tracking the problem down.)
good luck