Hi everyone
I decided to post here because I couldn't resolve my problem with only tutorials.
I have an HTC Legend which was very slow, because of an update from SFR. I tryed a factory reset but it was still slow.
I did a backup with clockworkmod, so I can always go back to the first (bad) configuration.
Today, after many operations, the phone boots until the first screen (when you have to use the slide to unlock the screen). But the screen doesn't respond and the reboot reboot after few minutes. Even after using a RUU...
I know that it is possible to restore it, because it worked once. But because of my enthusiasm, I broke the configuration with cyanogen. (I didn't made backup, so stupid)
If even a RUU cannot restore my HTC Legend, what can I do?
Thank you in advance
Useful information:
HTC Legend branded (Vodafone)
Actual HBOOT version: 1.00
Radio: 7.13.35.05
S-ON
Neferth said:
If even a RUU cannot restore my HTC Legend, what can I do?
Click to expand...
Click to collapse
Hello Neferth,
Switch off your phone. Than switch it on holding the "Vol-" and the "power" button. Then select recovery.
At the red [!] screen. press "Vol+" and the "power" button.
Wait for a blue menu list at the top of the screen. Then select update.zip.
Then you can see the ClockworkMod Recovery menu. You can do a restore now ...
Greetings: alligator-asl
Hi,
If I do that, I can only backup my phone to the first (and bad) configuration. And the phone still boots in loop...
I search for a solution to completely format the system and wipe all things I added. I believed that a RUU could help me, but the problem still remains, as if I forgot something. This is despairing...
Neferth said:
Hi,
If I do that, I can only backup my phone to the first (and bad) configuration. And the phone still boots in loop...
I search for a solution to completely format the system and wipe all things I added. I believed that a RUU could help me, but the problem still remains, as if I forgot something. This is despairing...
Click to expand...
Click to collapse
Here's an idea, you can boot into clock work mod yeah? OK, pick a rom, any rom, but I'd advise you to get one of the froyo based roms like blay0s, these are probably better for you at this stage as they are compleat, and dare I say it bug free
Anyway download the zip file, put it onto your sdcard, boot into recovery, format boot, system, data, cache, and sdext NOT THE SD CARD!
now flash the zip file and reboot, if you still have boot loop then its possible your internal rom space is damaged, I've heard of this issue in other phone threads, however I've not yet heard a story about damaged rom space on legend.
Sent from my Legend using xda app-developers app
Thanks you for your help!
I followed your instructions and I:
-rooted my phone with r4legend.
-formatted boot, system, data and cache partition
-installed Bay0 O.8 and upgraded it to 0.8.4
The bootloop seems to be fixed, but the phone still freeze at first screen. Moreover, the screen dies out after few minutes.
Just in case, I launched
Code:
adb logcat
, and I noticed the following errors and fails:
Code:
--------- beginning of /dev/log/system
I/Vold ( 150): Vold 2.1 (the revenge) firing up
D/Vold ( 150): Volume sdcard state changing -1 (Initializing) -> 0 (No-Media)
I/SystemServer( 189): Entered the Android system server!
I/SystemServer( 189): Entropy Service
W/EntropyService( 189): unable to load initial entropy (first boot?)
[...]
E/ConnectivityService( 189): Error in radioAttributes - ignoring attempt to define type 6
E/ConnectivityService( 189): Error in networkAttributes - ignoring attempt to adopt radio 6
[...]
/SystemServer( 189): HTC Checkin Service.
I/SystemServer( 189): Wallpaper Service
W/WallpaperService( 189): failed parsing /data/system/wallpaper_info.xml java.io.FileNotFoundException: /data/system/wallpaper_info.xml (No such file or directory)
I/SystemServer( 189): Audio Service
[...]
I/WindowManager( 189): SAFE MODE not enabled
W/DevicePolicyManagerService( 189): failed parsing /data/system/device_policies.xml java.io.FileNotFoundException: /data/system/device_policies.xml (No such file or directory)
V/KeyguardViewMediator( 189): password timeout delay 281859ms
[...]
D/KeyguardViewMediator( 189): pokeWakelock(15000)
W/WindowManager( 189): VOLUME button: Unable to find ITelephony interface
D/KeyguardViewMediator( 189): pokeWakelock(15000)
W/WindowManager( 189): VOLUME button: Unable to find ITelephony interface
D/KeyguardViewMediator( 189): pokeWakelock(15000)
W/WindowManager( 189): !!! Unable to find ITelephony interface !!!
And when the screen dies out:
Code:
W/PackageManager( 897): Unknown permission android.permission.ACCESS_LOCATION in package com.htc.android.locationpicker
W/PackageManager( 897): Unknown permission android.permission.ACCESS_GPS in package com.htc.android.locationpicker
W/PackageManager( 897): Unknown permission com.htc.android.mail.permission.READ_ACCOUNT in package com.htc.htccontactwidgets
W/PackageManager( 897): Unknown permission com.htc.android.mail.permission.WRITE_ACCOUNT in package com.htc.htccontactwidgets
W/PackageManager( 897): Unknown permission android.permission.BACKUP_DATA in package com.htc.CustomizationSetup
W/PackageManager( 897): Not granting permission android.permission.CLEAR_APP_USER_DATA to package com.android.packageinstaller (protectionLevel=2 flags=0xbe45)
W/PackageManager( 897): Unknown permission com.android.providers.im.permission.READ_ONLY in package com.google.android.apps.maps
W/PackageManager( 897): Unknown permission android.permission.BACKUP_DATA in package com.htc.android.htcime
W/PackageManager( 897): Unknown permission android.permission.BACKUP_DATA in package com.htc.UpgradeSetup
W/PackageManager( 897): Unknown permission com.android.providers.htccdma.Specific in package com.htc.android.htcsetupwizard
W/PackageManager( 897): Unknown permission com.htc.VzWBackupAssistantClient.PROVISION in package com.htc.android.htcsetupwizard
W/PackageManager( 897): Unknown permission com.google.android.providers.gmail.permission.WRITE_GMAIL in package com.qo.android.htc
W/PackageManager( 897): Unknown permission com.google.android.providers.gmail.permission.READ_GMAIL in package com.qo.android.htc
W/PackageManager( 897): Unknown permission com.android.email.permission.ACCESS_PROVIDER in package com.qo.android.htc
W/PackageManager( 897): Unknown permission com.android.email.permission.READ_ATTACHMENT in package com.qo.android.htc
W/PackageManager( 897): Unknown permission com.google.android.apps.googlevoice.permission.AUTO_SEND in package com.google.android.voicesearch
Perhaps I am wrong but I see nothing that prevent the phone from booting...
You also talked about internal rom space, what is it exactly? Because I only know the partitions:
• /boot
• /cache
• /data
• /misc
• /recovery
• /system
Where can I find this internal rom space and how can I repair it?
Neferth said:
Thanks you for your help!
I followed your instructions and I:
-rooted my phone with r4legend.
-formatted boot, system, data and cache partition
-installed Bay0 O.8 and upgraded it to 0.8.4
The bootloop seems to be fixed, but the phone still freeze at first screen. Moreover, the screen dies out after few minutes.
Just in case, I launched
Code:
adb logcat
, and I noticed the following errors and fails:
Code:
--------- beginning of /dev/log/system
I/Vold ( 150): Vold 2.1 (the revenge) firing up
D/Vold ( 150): Volume sdcard state changing -1 (Initializing) -> 0 (No-Media)
I/SystemServer( 189): Entered the Android system server!
I/SystemServer( 189): Entropy Service
W/EntropyService( 189): unable to load initial entropy (first boot?)
[...]
E/ConnectivityService( 189): Error in radioAttributes - ignoring attempt to define type 6
E/ConnectivityService( 189): Error in networkAttributes - ignoring attempt to adopt radio 6
[...]
/SystemServer( 189): HTC Checkin Service.
I/SystemServer( 189): Wallpaper Service
W/WallpaperService( 189): failed parsing /data/system/wallpaper_info.xml java.io.FileNotFoundException: /data/system/wallpaper_info.xml (No such file or directory)
I/SystemServer( 189): Audio Service
[...]
I/WindowManager( 189): SAFE MODE not enabled
W/DevicePolicyManagerService( 189): failed parsing /data/system/device_policies.xml java.io.FileNotFoundException: /data/system/device_policies.xml (No such file or directory)
V/KeyguardViewMediator( 189): password timeout delay 281859ms
[...]
D/KeyguardViewMediator( 189): pokeWakelock(15000)
W/WindowManager( 189): VOLUME button: Unable to find ITelephony interface
D/KeyguardViewMediator( 189): pokeWakelock(15000)
W/WindowManager( 189): VOLUME button: Unable to find ITelephony interface
D/KeyguardViewMediator( 189): pokeWakelock(15000)
W/WindowManager( 189): !!! Unable to find ITelephony interface !!!
And when the screen dies out:
Code:
W/PackageManager( 897): Unknown permission android.permission.ACCESS_LOCATION in package com.htc.android.locationpicker
W/PackageManager( 897): Unknown permission android.permission.ACCESS_GPS in package com.htc.android.locationpicker
W/PackageManager( 897): Unknown permission com.htc.android.mail.permission.READ_ACCOUNT in package com.htc.htccontactwidgets
W/PackageManager( 897): Unknown permission com.htc.android.mail.permission.WRITE_ACCOUNT in package com.htc.htccontactwidgets
W/PackageManager( 897): Unknown permission android.permission.BACKUP_DATA in package com.htc.CustomizationSetup
W/PackageManager( 897): Not granting permission android.permission.CLEAR_APP_USER_DATA to package com.android.packageinstaller (protectionLevel=2 flags=0xbe45)
W/PackageManager( 897): Unknown permission com.android.providers.im.permission.READ_ONLY in package com.google.android.apps.maps
W/PackageManager( 897): Unknown permission android.permission.BACKUP_DATA in package com.htc.android.htcime
W/PackageManager( 897): Unknown permission android.permission.BACKUP_DATA in package com.htc.UpgradeSetup
W/PackageManager( 897): Unknown permission com.android.providers.htccdma.Specific in package com.htc.android.htcsetupwizard
W/PackageManager( 897): Unknown permission com.htc.VzWBackupAssistantClient.PROVISION in package com.htc.android.htcsetupwizard
W/PackageManager( 897): Unknown permission com.google.android.providers.gmail.permission.WRITE_GMAIL in package com.qo.android.htc
W/PackageManager( 897): Unknown permission com.google.android.providers.gmail.permission.READ_GMAIL in package com.qo.android.htc
W/PackageManager( 897): Unknown permission com.android.email.permission.ACCESS_PROVIDER in package com.qo.android.htc
W/PackageManager( 897): Unknown permission com.android.email.permission.READ_ATTACHMENT in package com.qo.android.htc
W/PackageManager( 897): Unknown permission com.google.android.apps.googlevoice.permission.AUTO_SEND in package com.google.android.voicesearch
Perhaps I am wrong but I see nothing that prevent the phone from booting...
You also talked about internal rom space, what is it exactly? Because I only know the partitions:
• /boot
• /cache
• /data
• /misc
• /recovery
• /system
Where can I find this internal rom space and how can I repair it?
Click to expand...
Click to collapse
Well, rom space (memory storage) is the location of where your rom is flashed to, as far as I know once this is damaged there is no way to fix it.
I'm pretty sure that the boot, system, misc, recovery is all part of rom space. I'm pretty sure that data and cache is part of internal memory?
I haven't actually gotten that deep into internal workings of the hardware so I could be wrong.
Sent from my Legend using xda app-developers app
Found it. It was bad blocks on the system and data partition.
Just THANK to you for your tips and AngelDeath for his marvellous article:
http://forum.xda-developers.com/showthread.php?t=1189544
I will try to move /system and /data partitions to SD card.
edit: I will follow this tutorial => http://petermolnar.eu/linux-tech-coding/how-to-move-dalvik-cache-to-system-partition-in-android/
edit 2: Launching a /system partition on SD card seems to be possible => http://forum.xda-developers.com/showthread.php?t=779274
But it isn't user frienldy enough, so I will probably try "task 29" with MTTY to format the partition. The bad blocks will not disappear, but I hope the system will mark them as "bad".
=> http://forum.xda-developers.com/showthread.php?t=540290
=> http://forum.xda-developers.com/showthread.php?t=644781
Is it working now? I'm also getting problems with bad blocks now
Sent from my Legend using xda premium
Hello xennr3
Sorry for the delay, I had examinations and I forgot this painful problem...
I tried to use MTTY but XP/Seven didn't let me create ActiveSync connection (making a banal connection is too hard for these OS). And without ActiveSync, no mtty.
And obviously no documentation in order to make the same thing with linux.
Sigh.
Anyway, I returned the HTC to its owner. I will try later (~3 month), but I surely will not give up. I will update this post if I found any useful documentation or alternative.
Neferth said:
Hello xennr3
Sorry for the delay, I had examinations and I forgot this painful problem...
I tried to use MTTY but XP/Seven didn't let me create ActiveSync connection (making a banal connection is too hard for these OS). And without ActiveSync, no mtty.
And obviously no documentation in order to make the same thing with linux.
Sigh.
Anyway, I returned the HTC to its owner. I will try later (~3 month), but I surely will not give up. I will update this post if I found any useful documentation or alternative.
Click to expand...
Click to collapse
Isn't active sync for connecting to windows mobile devices like GPS etc?
Sent from my Legend using xda app-developers app
Hello there,
My Samsusng Galaxy S2 (i9100) has recently stopped working as it is supposed to. While I tried debugging the issue in any way I could, I figured out I might get some help over here.
At any time that the device itself isn't connected to a power source (USB cable [adb] or the charger), it randomly crashes (the screen turns black and I have to turn the phone on again). I also must say that this problem doesn't happen while on the recovery screen (CWM based recovery).
At first I thought this may happen because I've installed a pretty old version of Cyanogenmod (the cm11 installer version), so I installed the recent monthly build, but the issue still persists. I've tried debugging the device wirelessly (because when it was connected to a power source it never crashed), so I played a game which makes the CPU work abit, and I thought I'll get a crash log - which I didn't get. The last radio signal I got from the phone was this:
I/LibraryLoader( 2817): Expected native library version number "",actual native
library version number ""
I/chromium( 2817): [INFO:library_loader_hooks.cc(116)] Chromium logging enabled:
level = 0, default verbosity = 0
I/BrowserStartupController( 2817): Initializing chromium process, renderers=0
D/TinyALSA-Audio Hardware( 1855): audio_hw_get_mic_mute(0x4003e938, 0x4126daeb)
D/BluetoothManagerService( 2205): Message: 20
D/BluetoothManagerService( 2205): Added callback: android.bluetooth.IBluetoothMa
[email protected]:true
D/BluetoothAdapter( 2817): 1112752792: getState() : mService = null. Returning
STATE_OFF
D/libEGL ( 2817): loaded /system/lib/egl/libEGL_mali.so
D/libEGL ( 2817): loaded /system/lib/egl/libGLESv1_CM_mali.so
D/libEGL ( 2817): loaded /system/lib/egl/libGLESv2_mali.so
E/ ( 2817): Device driver API match
E/ ( 2817): Device driver API version: 23
E/ ( 2817): User space API version: 23
E/ ( 2817): mali: REVISION=Linux-r3p2-01rel3 BUILD_DATE=Wed Oct 9 21:05:
57 KST 2013
W/chromium( 2817): [WARNINGroxy_service.cc(890)] PAC support disabled because
there is no system implementation
I/chromium( 2817): [INFO:CONSOLE(0)] "Document was loaded from Application Cache
with manifest {URL}
k-core-v40.appcache", source: {URL}
d/sdk/native/sdk-core-v40.html (0)
I/chromium( 2817): [INFO:CONSOLE(0)] "Application Cache Checking event", source:
{URL}
l (0)
I/chromium( 2817): [INFO:CONSOLE(0)] "Application Cache NoUpdate event", source:
{URL}
l (0)
W/chromium( 6284): [WARNINGroxy_service.cc(890)] PAC support disabled because
there is no system implementation
I/chromium( 6284): [INFO:simple_index_file.cc(437)] Simple Cache Index is being
restored from disk.
D/Yamaha-MC1N2-Audio( 1855): yamaha_mc1n2_audio_output_stop()
D/Yamaha-MC1N2-Audio( 1855): yamaha_mc1n2_audio_route_start()
Click to expand...
Click to collapse
I've tried tracing the log files the system automatically creates in the ./system folder, but I couldn't find any useful information except from some deamon crash logs.
I tried resetting the dalvik cache, reinstalling my ROM manually (adb sideload), preforming a complete factory reset and wiping cache partition, and yet it didn't work.
I'm quite sure the issue relates to my phone's battery (which overheated a bit when I used it for a long time), but I'm still not completely sure this is the issue, so I would like to hear your suggestions.
Thanks in advance,
Eden
Eden Campo said:
Hello there,
....
I've tried tracing the log files the system automatically creates in the ./system folder, but I couldn't find any useful information except from some deamon crash logs.
I tried resetting the dalvik cache, reinstalling my ROM manually (adb sideload), preforming a complete factory reset and wiping cache partition, and yet it didn't work.
I'm quite sure the issue relates to my phone's battery (which overheated a bit when I used it for a long time), but I'm still not completely sure this is the issue, so I would like to hear your suggestions.
Thanks in advance,
Eden
Click to expand...
Click to collapse
I also read your logcat or yeah the part of it and it seems all to be fine, normal lines.
I don't own the S2 anymore and I didn't had the issue. But I suggest to try somethings first before buying a new battery.
Try another rom instead of cyanogenmod, Cyanogenmod is supporting Alot of devices and it's not really good specific for devices so I suggest to try one of the roms from the development forums.(Cyanogenmod always have bugs.)
Try to flash back to stock with odin
Try to borrow a battery from a friend and see or you still have the same problem
Remove the battery out of the phone and leave your phone without a battery for like 1-5 minutes.
It could be maybe the battery that it got issues cause the S2 is not the newest phone anymore and hardware also has a lifetime sadly. But your screen goes black and your device goes off right?
Hello,
recently I get my Teclast X89 tablet, but unfortunately it appeares to have a problem. When the battery charging level comes to 100% (at 99% everything is OK) tablet becomes totally unusable. When the screen is switched off it cannot be waken up and when I use the tablet a window pops up telling that "Process com.android.systemui has stopped", like here:
imgur.com/hjWI1lP
After restart everything is OK, but it really grinds my gears. Maybe someone know how to fix this problem?
Please halp!
Bogusz
Go to developer settings and enable android debugging. Now connect to computer set up adb drivers and post a logcat at the time of crash
MasterAwesome said:
Go to developer settings and enable android debugging. Now connect to computer set up adb drivers and post a logcat at the time of crash
Click to expand...
Click to collapse
Hello again,
I've made logcat, here is an interesting part, I think:
I/SecurityManagerService( 671): SMS received security event: App[START/com.android.keyguard]
I/WindowState( 556): WIN DEATH: Window{26a85ad0 u0 Keyguard}
I/ActivityManager( 556): Process com.android.systemui (pid 622) has died.
W/ActivityManager( 556): Scheduling restart of crashed service com.android.systemui/.SystemUIService in 0ms
W/ActivityManager( 556): Scheduling restart of crashed service com.android.keyguard/.KeyguardService in 0ms
D/InputMethodManagerService( 556): --- calledFromForegroundUserOrSystemProcess ? calling uid = 1000 system uid = 1000 calling userId = 0, foreground user id = 0, calling pid = 556dalvik.system.NativeStart.run(Native Method)
W/ActivityManager( 556): Scheduling restart of crashed service com.android.systemui/.ImageWallpaper in 0ms
I/StatusBarManagerService( 556): binder died for pkg=com.android.keyguard
I/WindowState( 556): WIN DEATH: Window{269b48a8 u0 NavigationBar}
W/InputDispatcher( 556): Attempted to unregister already unregistered input channel '268ba8e8 StatusBar (server)'
D/dalvikvm( 3948): Try to disable coredump for pid 3948
D/dalvikvm( 3948): Process 3948 nice name: com.android.systemui
D/dalvikvm( 3948): Extra Options: not specified
Click to expand...
Click to collapse
I discovered also that when the battery level drops to 99% process starts to work properly.
I include also whole log file compressed to .zip.
Still need help!
I have the same problem, even after a factory reset.
me too having the same issue. Is it hardware failure or just android?
I found a solution in an other tread :
http://forum.xda-developers.com/android/general/review-teclast-x89-baytrail-tablet-dual-t3039961
My tasker app keeps getting killed after a while. Keeps closing on it's own. Can't figure it out what causing this. Tasker is running in foreground (Prefs / Monitor / Run In Foreground).
System is Cyanogenmod 11, Lenovo k910, Android 4.4. Any help please?
Here's excerpt from the log with the part when tasker get killed. Maybe this will help with identifying the problem.
Code:
com.google.android.location.fused.LOCATION_REQUESTS
I/Fitness ( 1918): WearableSyncHostService elapsedNanos: 8229
W/bt-btif ( 3206): bta_dm_pm_btm_status stopping timer if activesince sniff mode is enabled
I/ActivityManager( 985): Force stopping net.dinglisch.android.taskerm appid=10033 user=0: pkg changed
I/ActivityManager( 985): Killing 9354:net.dinglisch.android.taskerm/u0a33 (adj 2): stop net.dinglisch.android.taskerm
W/ActivityManager( 985): Scheduling restart of crashed service net.dinglisch.android.taskerm/.MonitorService in 1000ms
I/ActivityManager( 985): Force stopping service ServiceRecord{435bb5e8 u0 net.dinglisch.android.taskerm/.MonitorService}
W/Launcher.Model( 8920): Nobody to tell about the new app. Launcher is probably loading.
W/Launcher( 8920): setApplicationContext called twice! [email protected] [email protected]
I/InputReader( 985): Reconfiguring input devices. changes=0x00000010
I/ActivityManager( 985): Force stopping net.dinglisch.android.taskerm appid=10033 user=0: from pid 28752
I/cm.log.servpro( 5146): [AutoStart]/ AutoBgRepair : net.dinglisch.android.taskerm#net.dinglisch.android.taskerm.ReceiverStaticInternal#action:TIME_SET
D/PackageBroadcastService(28288): Received broadcast action=android.intent.action.PACKAGE_CHANGED and uri=net.dinglisch.android.taskerm
I/PackageManager( 985): Action: "android.intent.action.SENDTO"
I/PackageManager( 985): Category: "android.intent.category.DEFAULT"
I/PackageManager( 985): Scheme: "sms"
I/UpdateIcingCorporaServi( 2145): Updating corpora: APPS=net.dinglisch.android.taskerm, CONTACTS=MAYBE
Hello,
I have recently purchased a refurb Lenovo K6, it came with an Android 6.0 rom.
Off the bat it had some weird reboots and app crashes, updating and system restore solved nothing; the problem worsened, so I ended up using the official Lenovo tools to perform a system recovery, which flashed a stock Nougat rom (K33_USR_S223_1706101140_Q00440_ROW).
This didn't stop sudden app crashes and system restarts however; even at initial system setup, many apps including Google Play Services would stop responding.
Since then I've lost count of re-flashes, data and cache wipes, permission resets etc. that I've performed.
I've attempted to root the phone with KingRoot in order to wipe the Dalvik Cache but could not complete the process.
I got plenty of logs via logcat, wish you could help me understand what's going on using them; here is a small one (Error level treshold) that I got, includes crashes of Firefox, Lenovo Launcher and I think Google Play Services.
pastebin. com/sZkDYPXi
I got other bigger ones, as well.
Mainly I notice a lot of "no such file or directory" errors, such as:
Code:
07-24 14:46:13.852 1447 1667 E QCOM PowerHAL: Error opening sys/devices/system/cpu/cpu0/cpufreq/scaling_governor: No such file or directory
and a lot of SELinux permission denials:
Code:
07-24 14:31:22.373 474 474 E SELinux : avc: denied { find } for service=android.hardware.fingerprint.IFingerprintDaemon pid=2905 uid=10112 scontext=u:r:untrusted_app:s0:c512,c768 tcontext=u:object_r:fingerprintd_service:s0 tclass=service_manager permissive=0
In another log with Warning treshold I was getting a lot of PackageManager warnings such as these:
Code:
07-22 19:34:36.255 5135 5135 W PackageManager: Not granting permission android.permission.ACCESS_FINE_LOCATION to package com.skype.raider because it was previously installed without
Code:
07-22 19:31:12.912 1422 1595 W PackageManager: Permission com.google.android.googleapps.permission.GOOGLE_AUTH from package com.google.android.gsf in an unknown group android.permission-group.ACCOUNTS
I'd rather try to fix the problem myself if at all possible, rather than returning the phone...
Thanks a lot for your help.
I now suspect there has been a failed root attempt on this device, as many errors have to do with denied permissions.
Also I managed to get a new logcat from many Firefox/Google Play Services and a system reboot, and the following line appears:
Code:
07-24 19:12:21.346 10637 10647 F art : art/runtime/gc/collector/mark_sweep.cc:448] Attempting see if it's a bad root
Also firefox crashes report this:
Code:
07-24 19:10:16.979 6598 6954 E InputDispatcher: channel '28475f0 org.mozilla.firefox/org.mozilla.gecko.BrowserApp (server)' ~ Channel is unrecoverably broken and will be disposed!
and apparently can't read session files:
Code:
07-24 19:10:42.340 10412 10426 E GeckoApp: An error occurred during restore, switching to backup file
07-24 19:10:42.340 10412 10426 E GeckoApp: org.mozilla.gecko.GeckoApp$SessionRestoreException: Could not read from session file
and the backtrace reports failure of some sort with async threads...
I really am banging my head against a wall here :crying:
bumpity bump bump