Guys, please, help me to find a solution. Very big bug, software or hardware, I don't know!
My HOX after a some time of normal working starts force closing almost all apps.
It happens independently of which apps i run or use.
As I can observe it doesn't depend on a state of radio module or wi-fi or data connection or usb plugging. It can happen at any time and in any case.
Apps that getting crashed are as system as custom but mostly are system apps. The full list of crashing apps you can see below in a logcat with filter "crash".
I tried to solve it myself by doing all possible steps: factory reset, manually formatting all partitions in recovery, formatting SD-card via PC and a device, re-locking bootloader and flashing different custom and stock ROMs, using a phone clean without any custom apps, or disabling radio and data connection. No result.
Now I recorded two logcats, one is when a phone was still normally working, and a second when a phone became force stopping apps.
I am not an advanced user of android OS so hardly i can read a log correctly.
So I need someone who knows how to analyze an information in the logs and find a reason of troubles. I will be very thankful.
One thought when reading logs:
When its OK there is no error messages like "Read-only file system", when it gets bad there are a lot of such warnings. Apps and services cannot operate with /data/ partition because of read-only. What can be a reason that the /data partition gets read-only?
May be this is a clue?
I don't want to believe that this is a hardware problem.
Do you have a custom recovery? If yes, try doing a "Fix Permissions" from the Recovery. I am a noob too, so cant really interpret your logcat. But have read somewhere, that "Fix Permissions" in Clockworkmod Touch Recovery can help solve such FC issues.
If nothing else works, I personally would install RUU (be careful and follow proper instructions) and see if that resolves the issue. If that doesn't send the phone back to HTC.
a.james said:
Do you have a custom recovery? If yes, try doing a "Fix Permissions" from the Recovery. I am a noob too, so cant really interpret your logcat. But have read somewhere, that "Fix Permissions" in Clockworkmod Touch Recovery can help solve such FC issues.
If nothing else works, I personally would install RUU (be careful and follow proper instructions) and see if that resolves the issue. If that doesn't send the phone back to HTC.
Click to expand...
Click to collapse
Fixing permissions doesn't help.
I did install RUU twice on a fully clean device but no trouble had gone away.
Sending back to HTC may be difficult - the phone was unlocked and now is re-locked.
ninelo said:
Fixing permissions doesn't help.
I did install RUU twice on a fully clean device but no trouble had gone away.
Sending back to HTC may be difficult - the phone was unlocked and now is re-locked.
Click to expand...
Click to collapse
That should not be an issue. Relocked with RUU, is basically is same as Stock. As if you unlocked ur phone, and re-locked it without actually doing anything. So, warranty should cover it, if its a Manufacturing Defect. Unfortunately thats all I can think of, unless some senior devs have a look at the logcat and identify the exact issue.
Sorry couldnt be of much help...
a.james said:
unless some senior devs have a look at the logcat and identify the exact issue.
Click to expand...
Click to collapse
Thanks thats what I hope on.
ninelo said:
Thanks thats what I hope on.
Click to expand...
Click to collapse
Try "fastboot erase cache" from your Pc. You will need fastboot files. Look under development section
Sent from my HTC One X using xda premium
eyosen said:
Try "fastboot erase cache" from your Pc. You will need fastboot files. Look under development section
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Did it. It only helps to solve booting into recovery issues. Its not my case.
After some time of testing I came to conclusion that the reason was the error "EROFS (Read-only file system)".
A few examples:
Code:
Line 69: W/ActivityManager( 358): java.io.FileNotFoundException: /data/anr/traces.txt: open failed: EROFS (Read-only file system)
Line 87: W/ActivityManager( 358): Caused by: libcore.io.ErrnoException: open failed: EROFS (Read-only file system)
Line 171: E/DropBoxManagerService( 358): java.io.FileNotFoundException: /data/system/dropbox/drop272.tmp: open failed: EROFS (Read-only file system)
Line 187: E/DropBoxManagerService( 358): Caused by: libcore.io.ErrnoException: open failed: EROFS (Read-only file system)
Line 279: W/ActivityManager( 358): java.io.FileNotFoundException: /data/anr/traces.txt: open failed: EROFS (Read-only file system)
Line 297: W/ActivityManager( 358): Caused by: libcore.io.ErrnoException: open failed: EROFS (Read-only file system)
Line 311: W/ActivityManager( 358): java.io.FileNotFoundException: /data/anr/traces.txt: open failed: EROFS (Read-only file system)
Line 329: W/ActivityManager( 358): Caused by: libcore.io.ErrnoException: open failed: EROFS (Read-only file system)
Line 347: E/DropBoxManagerService( 358): java.io.FileNotFoundException: /data/system/dropbox/drop270.tmp: open failed: EROFS (Read-only file system)
Line 361: E/DropBoxManagerService( 358): Caused by: libcore.io.ErrnoException: open failed: EROFS (Read-only file system)
Line 395: W/BatteryStats( 358): java.io.FileNotFoundException: /data/system/batterystats.bin.tmp: open failed: EROFS (Read-only file system)
Line 407: W/BatteryStats( 358): Caused by: libcore.io.ErrnoException: open failed: EROFS (Read-only file system)
Line 443: W/ActivityManager( 358): java.io.FileNotFoundException: /data/anr/traces.txt: open failed: EROFS (Read-only file system)
Line 461: W/ActivityManager( 358): Caused by: libcore.io.ErrnoException: open failed: EROFS (Read-only file system)
Line 485: E/DropBoxManagerService( 358): java.io.FileNotFoundException: /data/system/dropbox/drop278.tmp: open failed: EROFS (Read-only file system)
Line 499: E/DropBoxManagerService( 358): Caused by: libcore.io.ErrnoException: open failed: EROFS (Read-only file system)
Line 2201: W/ActivityManager( 358): java.io.FileNotFoundException: /data/anr/traces.txt: open failed: EROFS (Read-only file system)
Line 2219: W/ActivityManager( 358): Caused by: libcore.io.ErrnoException: open failed: EROFS (Read-only file system)
Line 2233: W/ActivityManager( 358): java.io.FileNotFoundException: /data/anr/traces.txt: open failed: EROFS (Read-only file system)
Line 2251: W/ActivityManager( 358): Caused by: libcore.io.ErrnoException: open failed: EROFS (Read-only file system)
Line 2413: E/DropBoxManagerService( 358): java.io.FileNotFoundException: /data/system/dropbox/drop285.tmp: open failed: EROFS (Read-only file system)
Line 2429: E/DropBoxManagerService( 358): Caused by: libcore.io.ErrnoException: open failed: EROFS (Read-only file system)
Line 2527: W/ActivityManager( 358): java.io.FileNotFoundException: /data/anr/traces.txt: open failed: EROFS (Read-only file system)
Line 2545: W/ActivityManager( 358): Caused by: libcore.io.ErrnoException: open failed: EROFS (Read-only file system)
Line 2559: W/ActivityManager( 358): java.io.FileNotFoundException: /data/anr/traces.txt: open failed: EROFS (Read-only file system)
Line 2577: W/ActivityManager( 358): Caused by: libcore.io.ErrnoException: open failed: EROFS (Read-only file system)
Line 3039: E/libEGL ( 9262): error creating cache file /data/data/com.htc.Weather/cache/com.android.opengl.shaders_cache: Read-only file system (30)
Line 3195: W/ActivityManager( 358): java.io.FileNotFoundException: /data/anr/traces.txt: open failed: EROFS (Read-only file system)
Line 3213: W/ActivityManager( 358): Caused by: libcore.io.ErrnoException: open failed: EROFS (Read-only file system)
Line 3231: W/SqliteDatabaseCpp( 9327): getJournalMode: errno = 30, error message = Read-only file system
Line 3235: E/SqliteDatabaseCpp( 9327): native_setLocale: errno = 30, error message = Read-only file system
Line 3545: W/ActivityManager( 358): java.io.FileNotFoundException: /data/anr/traces.txt: open failed: EROFS (Read-only file system)
Line 3563: W/ActivityManager( 358): Caused by: libcore.io.ErrnoException: open failed: EROFS (Read-only file system)
Line 3595: W/ActivityManager( 358): java.io.FileNotFoundException: /data/anr/traces.txt: open failed: EROFS (Read-only file system)
Line 3613: W/ActivityManager( 358): Caused by: libcore.io.ErrnoException: open failed: EROFS (Read-only file system)
Line 4039: W/ActivityManager( 358): java.io.FileNotFoundException: /data/anr/traces.txt: open failed: EROFS (Read-only file system)
Line 4057: W/ActivityManager( 358): Caused by: libcore.io.ErrnoException: open failed: EROFS (Read-only file system)
Line 4087: W/ActivityManager( 358): java.io.FileNotFoundException: /data/anr/traces.txt: open failed: EROFS (Read-only file system)
Line 4105: W/ActivityManager( 358): Caused by: libcore.io.ErrnoException: open failed: EROFS (Read-only file system)
Line 5189: E/DropBoxManagerService( 358): java.io.FileNotFoundException: /data/system/dropbox/drop179.tmp: open failed: EROFS (Read-only file system)
Line 5205: E/DropBoxManagerService( 358): Caused by: libcore.io.ErrnoException: open failed: EROFS (Read-only file system)
Line 5729: W/BatteryStats( 358): java.io.FileNotFoundException: /data/system/batterystats.bin.tmp: open failed: EROFS (Read-only file system)
Line 5741: W/BatteryStats( 358): Caused by: libcore.io.ErrnoException: open failed: EROFS (Read-only file system)
Line 7275: W/SqliteDatabaseCpp( 9677): getJournalMode: errno = 30, error message = Read-only file system
Line 7279: E/SqliteDatabaseCpp( 9677): native_setLocale: errno = 30, error message = Read-only file system
It remains to find a solution...
have same problem
in recovery dmesg
dmesg
0
<6>[ 3.891118] mmc0: clock 52000000Hz busmode 2 powermode 2 cs 0 Vdd 7 width 3 timing 1 ddr 0
<6>[ 3.892378] mmc0: clock 52000000Hz busmode 2 powermode 2 cs 0 Vdd 7 width 3 timing 5 ddr 0
<6>[ 3.892488] mmc0: clock 52000000Hz busmode 2 powermode 2 cs 0 Vdd 7 width 3 timing 5 ddr 0
<6>[ 3.892691] mmc0: new high speed DDR MMC card at address 0001
<6>[ 3.893476] mmcblk0: mmc0:0001 K2U00M 29.1 GiB
<4>[ 3.895943] Primary GPT is invalid, using alternate GPT.
I seem to be having the same problem, as outlined in a previous post i made.
I'd love to help and provide more logs but i don't know where to get the logs from.
Also at the moment my phone is stuck on bootloop so i'll need to get that taken care of before anything else. Bootloop happens if my battery is low (<14%) and i reboot the phone or shut it off and back on...
I am also in the process of restoring to stock to see if that helps.
Thank you
smiro2000 said:
I'd love to help and provide more logs but i don't know where to get the logs from.
Click to expand...
Click to collapse
Boot your phone normally, connect to PC, check ADB debugging, run "cmd" on your PC, go to the folder where you have ADB drivers and run:
Code:
adb logcat *:W > C:\logcat.txt
Then look into the logcat.txt and search errors like "EROFS (Read-only file system)"
Had the same errors ... weird fix
Hi,
I had the same errors and found your post.
I tried everything too, installed stock RUU, reflashed, remounted and the errors kept rolling in. All kinds of apps crashed because of the read only filesystem.
But usually when having an error that is illogical, I tend to try **** that is illogical too ... I remembered that my phone fell a couple of weeks ago, cracking the glass (yeah that sucked bigtime!) and the errors started a couple of weeks after that ...
so first I thought it was a hardware thing like memory that was damaged, but since it took a couple of weeks for the errors came I discarded that idea and finally I got the 'dumb' idea to pop out my simcard and re-inserting it ....
and I haven't had a similar error since !!!!
I know it seems weird but maybe Android locks the partitions in case of a sim error or a security risk concerning the sim-card
hope it helps
Hey guys take a look at this post, maybe can help with pur problem http://forum.xda-developers.com/showthread.php?t=895628
Related
I was trying to port a Htc Magic ROM with dsi xda's kitchen ..but its getting stuck in a bootloop at the boot animation. Recovery.log is fine, nothing catastrophic there.But logcat had to say this:-
W/PackageParser( 449): Unknown element under <application>: intent-filter at /system/app/com.htc.MusicWidget.apk Binary XML file line #9
I/PackageManager( 449): /system/app/com.htc.MusicWidget.apk changed; collecting certs
D/installd( 81): DexInv: --- BEGIN '/system/app/com.htc.MusicWidget.apk' ---
D/dalvikvm-sfm( 568): Zip inflate: partial write (will retry): (8152 of 32768)
E/dalvikvm-sfm( 568): Zip inflate: write failed: No space left on device
W/dalvikvm( 568): DexOptZ: extraction of classes.dex from /system/app/com.htc.MusicWidget.apk failed
W/installd( 81): DexInv: --- END '/system/app/com.htc.MusicWidget.apk' --- status=0xff00, process failed
E/installd( 81): dexopt failed on '/cache/dalvik-cache/[email protected]@[email protected]' res = 65280
and this is repeated a lot more times for many other apps.
Complete logcat here: http://pastebin.com/6D7BMqE6
does this mean that the system partition is too small for this rom??
Is it possible to move some of the system apps to data/app folder??
Is there any way to expand it or resize the partitions?(Magic and Wildfire both have the same 512 Mb Roms)
What would be the best course of action?
Did you wiped Dalvik-cache ? This is a Dalvik-cache issue. Does the ROM uses Apps2SD ?
h4oxer said:
Did you wiped Dalvik-cache ? This is a Dalvik-cache issue. Does the ROM uses Apps2SD ?
Click to expand...
Click to collapse
Sorry,
The rom uses Apps2SD(Is this a problem)?.But i did wipe the Dalvik-cache.Will try again.
No Dalvik wipe doesnt help.
I want to be able to install ubuntu to my phone but im having issues trying to do so.
this is the error i get whilst trying to install:
losetup: /dev/block/loop5: No such file or directory
mount: mounting /dev/block/loop5 on /data/local/ubuntu failed: Invalid argument
mount: mounting devpts on /data/local/ubuntu/dev/pts failed: No such file or directory
mount: mounting proc on /data/local/ubuntu/proc failed: No such file or directory
mount: mounting sysfs on /data/local/ubuntu/sys failed: No such file or directory
net.ipv4.ip_forward = 1
Setting /etc/resolv.conf to Google Open DNS 8.8.8.8 and 8.8.4.4
bootlinux: cannot create /data/local/ubuntu/etc/resolv.conf: directory nonexistent
bootlinux: cannot create /data/local/ubuntu/etc/resolv.conf: directory nonexistent
Setting localhost on /etc/hosts
bootlinux: cannot create /data/local/ubuntu/etc/hosts: directory nonexistent
Created by KellyLewis3985 and BThomas22x!
Brought to you by Team BrokeDick!
chroot: can't execute '/bin/bash': No such file or directory
Shutting down Ubuntu
umount: can't umount /data/local/ubuntu/dev/pts: No such file or directory
umount: can't umount /data/local/ubuntu/proc: No such file or directory
umount: can't umount /data/local/ubuntu/sys: No such file or directory
umount: can't umount /data/local/ubuntu: Invalid argument
losetup: /dev/loop5: No such device or address
Click to expand...
Click to collapse
can anyone decipher this and put it into lamens terms for me? does this mean my Desire Z does not have loop device capability with the installed kernel?
im using cyanogen 7.1 at present and according to somoene on their forum thir phone had loop device capability on 7.1.
any help is appreciated
I am trying to get debdroid to start debian squeeze
The linux.img is in /sdcard/debdroid
After deploy from apk, no vnc or ssh so attempt from term
Term output:
Code:
$ export PATH=/data/local/bin:$PATH
$ su
# ash
~ # sh /system/bin/debdroid
Initializing chroot filesystem
mkdir: can't create directory '$/mnt/mnt/android': No such file or directory
mount: Invalid argument
Mounting proc, sysfs, dev, devpts
mount: No such file or directory
mount: No such file or directory
mount: No such file or directory
mount: No such file or directory
/sdcard/debdroid/share/ mounted to /mnt/share
Native Filesystem mounted to /mnt/android
Setting up DNS and Networking
/system/bin/debdroid: line 70: can't create /data/local/debdroid/etc/resolv.conf: nonexistent directory
/system/bin/debdroid: line 70: can't create /data/local/debdroid/etc/resolv.conf: nonexistent directory
/system/bin/debdroid: line 70: can't create /data/local/debdroid/etc/hosts: nonexistent directory
/system/bin/debdroid: line 70: can't create /data/local/debdroid/etc/hostname: nonexistent directory
Debdroid deployed succesfully, opening chroot.
mount: No such file or directory
chroot: can't execute 'bash': No such file or directory
chroot: can't execute '/bin/bash': No such file or directory
failed: No such file or directory
failed: No such file or directory
failed: No such file or directory
failed: No such file or directory
failed: No such file or directory
failed: No such file or directory
failed: Invalid argument
Exiting chroot
Filesystem unmounted
~ #
I dont have bash, is this the problem? Why isnt bash with busybox?
Shouldnt ash work?
BusyBox v1.19.2-cm71 static (2011-10-06 22:09 +0200) multi-call binary.
which zip and image?
You should really post this in the developers debdroid forum.
Which flashable zip and image did you download?
not enough posts
I cant post in dev, im too new.
Here are links to the zip and .gz that I dl'd.
I couldnt even post links. gititbit.ch/ ddba3
I couldnt even post links. gititbit.ch/ ddb4
rename or expand, bash for young
Did you expand the .gz to /sdcard/debdroid and name it linux.img or rename the .gz to linux.img?
not sure how thats supposed to work.
I see that bash is avail for the Young. Not sure why its not in calkulins rom...
Renamed the .gz
First i tried expanding it using estrongs fm. It gave the error "file size mismatch" and the resultant file was only 3.75G. I figured this was not the right way to do it and ended up just renaming the .gz to linux.img. Pretty sure thats how its supposed to go.
Maybe calkulin will include bash in his next rom.
post the output of debshell
post the output of debshell
debshell output
#
#
#
#
#
#
#
#
# sh debshell
init: must be run as PID 1
debshell: line 17: can't create /data/local/debdroid/etc/hostname: nonexistent directory
debshell: line 18: syntax error: unexpected "}"
#
#
#
You cannot simply rename the .gz to .img. Extract it on a computer then move it over to your sdcard as /sdcard/debdroid/linux.img. If ash is not working - bash is required because of the way functions are called in the script, however this should solve your issue once you extract the .img from the compressed download.
i followed this( htt p:/ /androlinux.com/android-ubuntu-development/how-to-install-ubuntu-on-android/ ) tutorial to install ubuntu on my desire z but it doesn't work. i'm using miui rom, does that have anything to do with that?
my kernel is 2.6.35.14-cyanogenmod.
Been planing on trying this myself but it does say it will only work on dual core phones. Haven't confirmed if it can work on g2/dz
Sent from my HTC Vision using xda premium
confirming it worked here
———————————————
i didn't mean to flame you, nor to mock you in any kind of way
^^ what is your kernel?
ILWT CM7
———————————————
i didn't mean to flame you, nor to mock you in any kind of way
i get this errors
Code:
# su
su
# cd sdcard/ubuntu
cd sdcard/ubuntu
# sh ubuntu.sh
sh ubuntu.sh
modprobe: module 'ext2' not found
←[H←[J←[H←[Jrm: can't remove '/system/bin/fsrw': No such file or directory
rm: can't remove '/system/bin/bootubuntu': No such file or directory
rm: can't remove '/system/bin/unionfs': No such file or directory
rm: can't remove '/system/bin/mountonly': No such file or directory
chmod: bootubuntu: Operation not permitted
chmod: fsrw: Operation not permitted
chmod: mountonly: Operation not permitted
chmod: ubuntu.img: Operation not permitted
chmod: ubuntu.sh: Operation not permitted
chmod: unionfs: Operation not permitted
←[H←[J
Ubuntu Chroot Bootloader v0.1
Ubuntu Bootloader is now installed!
This process does NOT damage Android OS!
Original Installer by Charan Singh
Modified for Ubuntu Chroot by Max Lee at AndroLinux.com ,G2Hacks.com and NexusOn
eHacks.net
To enter the Ubuntu Linux console just type 'bootubuntu'
# bootubuntu
bootubuntu
losetup: /dev/block/loop1
mount: mounting /dev/block/loop1 on /data/local/ubuntu failed: Device or resourc
e busy
mount: mounting devpts on /data/local/ubuntu/dev/pts failed: No such file or dir
ectory
mount: mounting proc on /data/local/ubuntu/proc failed: No such file or director
y
mount: mounting sysfs on /data/local/ubuntu/sys failed: No such file or director
y
net.ipv4.ip_forward = 1
Setting /etc/resolv.conf to Google Open DNS 8.8.8.8 and 8.8.4.4
bootubuntu: cannot create /data/local/ubuntu/etc/resolv.conf: directory nonexist
ent
bootubuntu: cannot create /data/local/ubuntu/etc/resolv.conf: directory nonexist
ent
Setting localhost on /etc/hosts
bootubuntu: cannot create /data/local/ubuntu/etc/hosts: directory nonexistent
READY TO ROCK AND ROLL BABY!
Brought to you by NexusOneHacks.net and the open source community!
chroot: can't execute '/bin/bash': No such file or directory
Shutting down Ubuntu
umount: can't umount /data/local/ubuntu/dev/pts: No such file or directory
umount: can't umount /data/local/ubuntu/proc: No such file or directory
umount: can't umount /data/local/ubuntu/sys: No such file or directory
umount: can't umount /data/local/ubuntu: Invalid argument
losetup: /dev/block/loop1: Device or resource busy
Looks like a couple files are missing. I got ubuntu to run quite well really (4GB image file with fluxbox, an office suite, media player, browser, pidgin, and several other apps). I didn't use that guide, I just grabbed the files and read the bash scripts to see what was going on.
Basically the zip you download should have an ubuntu.img file and about 4 other files. Make a folder on your sdcard (I called mine "ubuntu") and place all the files in the zip in that folder. Then use adb shell to connect to your phone and run.
Code:
[B]# sh ubuntu.sh[/B]
That will copy certain files to the system. Once that is done, you can run:
Code:
[B]# bootubuntu[/B]
As far as I know, you have to be using adb shell to run that and not using terminal emulator (though I may be mistaken). Once you run bootubuntu (from adb shell) you don't have to have your phone connected to the computer (until you reboot at least to run it again).
So I have done all the steps to installing Backtrack 5 on my SM-T210 correctly, but when i try to boot it up using "bootbt" i get an error like this:
"[email protected]:/ $
130|[email protected]:/ $ cd /storage/extSdCard/BT5
[email protected]:/storage/extSdCard/BT5 $ su
[email protected]:/storage/extSdCard/BT5 # sh bootbt
Loop device exists
open backing file failed: No such file or directory
mount: No such file or directory
mount: No such file or directory
mount: No such file or directory
net.ipv4.ip_forward = 1
bootbt[23]: can't create /data/local/mnt/etc/resolv.conf: No such file or directory
bootbt[24]: can't create /data/local/mnt/etc/hosts: No such file or directory
chroot: can't execute '/bin/bash': No such file or directory
Shutting down BackTrack ARM For Xoom
failed: No such file or directory
failed: No such file or directory
failed: No such file or directory
failed: Invalid argument
1|[email protected]:/storage/extSdCard/BT5 #"
any suggestions? Im new to android.
http://forum.xda-developers.com/showthread.php?t=1074723
This thread covers installing backtrack on the Xoom tablet. Also implies it can be installed on other devices. Last activity in the thread was in 2012 but there still may be some helpful information.
sent from a buggy xda app by some miracle