Database Users

Segment Fault error, customized JF 1.51

Hi,
I customized a JF1.51 with my own apps.
The first time everything gone well, but some apps were missing so
i managed to do another one with more apps.
It crashed during first start rebooting over and over.
I suspected an app causing the crash so I removed it and re-update the
phone.
This time everything seemed to working well but the terminal emulator as ls returned a permission denied and the same command in root mode returned a not found
I did a last try with some other apps, and the result was nearly the same as the command ls
returned a segment fault error in the terminal emulator su mode or not.
back to my orginal customized roms everything is working back but the apps are still missing.
So my question is, what could cause these problems?
Is there a size limit for the /system/app folder? (my whole rom is about 40,8Mo compressed)
please help
regards
Herc.

Hi,
So after some tests it really seems that the size matters .
So please can anybody explain me how I could enlarge my rom size without
causing problems after installation.
Bye
Herc. 8)

up
Still searching for an answer

[REF][ICS] Encryption Unsuccessful Reference

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.

[Q] - Why cant I ever seem to catch a useful error message?

Hi. So, I've been doing a lot of troubleshooting on my N10. I started out not even knowing that Jellybean would prevent propper logcatting w/out root, but I've advanced to the point where:
1) I have CatLog writing logcat, every 1 line, to my SD card
2) I have Bootlog Uptime writing log files after a crash
3) I've even looked into trace.txt and the likes, after I found this post:
http://android.stackexchange.com/questions/14430/how-can-i-view-and-examine-the-android-log
But I'll be damned if I ever even see the word "fatal" in any of these logs. And I always see this:
No errors detected
Last reset was software reset (RST_STAT=0x20000000)
So what am I doing wrong? My N10, when on purely stock, seems to have SoD. Im on KTmanta now, and knock-on-wood-dont-see-SoD, but I do still get some reboots.
How does Bootlog Uptime know these are crashes?
Thanks XDA

[Q] Nexus 7 /system corruption?

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

Boot troubleshooting

After working without a glitch for four years, my Nexus 7 (grouper) got stuck in a bootloop after I started it today. Thinking that something is probably wrong with cashe or dalvik cache I've cleared them. Now the bootloop is gone, but the device gets stuck on "Starting apps" after it finishes "optimizing" (filling in the dalvik cache). I would like to see what's going on but I have a problem doing that.
The problem is that I can't get the logcat to do the job. I've tried two "solutions" that seemed obvious, but (for some reason), none of them works.
First "solution": make a simple script and put it in /system/etc/init.d/:
#!/system/bin/sh
logcat > /sdcard/log.txt (set to 755)
I get the file, but even if I leave "Starting apps" to run for some time, when I turn off the tablet and look at the file it only has 65 lines and it still didn't finish initializing the hardware part. No information about started apps or anything. I can retrieve dmesg log from recovery but nothing interesting there as well.
Second "solution": I've tried to make it work trough init.rc, by following this https://stackoverflow.com/questions/17406209/enabling-logcat-in-init-rc (switched /cache/ to /sdcard/). But this also produces no results. Txt file is not generated at all
I don't know what I'm doing wrong.
I don't want to do a factory reset unless absolutely necessary (bunch of games with save files and other apps as well).
I can't do logcat trough adb since device is "unauthorized".
Any help is appreciated.
Thx in advance!
P.S. Using OmniROM (4.4.4)

Boot into TWRP and see if you can create or edit a text file. Reboot back into TWRP again and see if the change you made is still there. If it isn't, your flash memory has gone bad and you are in read only mode. This cant be fixed without a new motherboard. Hopefully this is not your issue.
Sent from my LGLS992 using Tapatalk

Sorry for the late reply, I was on vacation and I left the tablet at home.
The script I've mentioned was inserted trough TWRP so I think this confirms that you can write.
Also there is a log file created, as I've mentioned, it's just super short (I guess if it's in read-only mode there would be no output).