messages has stopped - HTC Sensation

Hello,
I seem to be locked out of my native messages application where I can read sms and mms.
When i launch it, it loads up, i see for about a second the messages thread bu then i get fc.
Tried to do a sms backup and i still get an error.
Cleared cache and dalvik in recovery and no luck.
Thanks
Code:
Device: htc_europe HTCSensation (pyramid)
OS: 4.1.2
Kernel: 3.4.10-SebastianFM-1.0.4
Software: ViperS 5.2.1
Description: 3.19.401.101 CL157254 release-keys
Characteristics: default
App: 7.13
7:12:30: An Error has occurred during backup: not an error (code 0)
7:12:30: Releasing cpu wake lock
7:12:30: Count: 0
7:12:30: ERROR! Error Creating Backup File : not an error (code 0): android.database.sqlite.SQLiteException: not an error (code 0)
at android.database.DatabaseUtils.readExceptionFromParcel(DatabaseUtils.java)
at android.database.DatabaseUtils.readExceptionFromParcel(DatabaseUtils.java)
at android.content.ContentProviderProxy.query(ContentProviderNative.java)
at android.content.ContentResolver.query(ContentResolver.java)
at android.content.ContentResolver.query(ContentResolver.java)
at com.riteshsahu.BackupRestoreCommon.BackupProcessor.saveXml(BackupProcessor.java:1322)
at com.riteshsahu.BackupRestoreCommon.BackupProcessor.createBackup(BackupProcessor.java:114)
at com.riteshsahu.BackupRestoreCommon.BackupProcessor.createBackup(BackupProcessor.java:143)
at com.riteshsahu.BackupRestoreCommon.TaskRunner.run(TaskRunner.java:294)
at java.lang.Thread.run(Thread.java)
7:12:30: Could not load Columns from contentUri, creating from mandatory columns : not an error (code 0): android.database.sqlite.SQLiteException: not an error (code 0)
at android.database.DatabaseUtils.readExceptionFromParcel(DatabaseUtils.java)
at android.database.DatabaseUtils.readExceptionFromParcel(DatabaseUtils.java)
at android.content.ContentProviderProxy.query(ContentProviderNative.java)
at android.content.ContentResolver.query(ContentResolver.java)
at android.content.ContentResolver.query(ContentResolver.java)
at com.riteshsahu.BackupRestoreCommon.Common.loadColumnList(Common.java:136)
at com.riteshsahu.BackupRestoreCommon.BackupProcessor.saveXml(BackupProcessor.java:1317)
at com.riteshsahu.BackupRestoreCommon.BackupProcessor.createBackup(BackupProcessor.java:114)
at com.riteshsahu.BackupRestoreCommon.BackupProcessor.createBackup(BackupProcessor.java:143)
at com.riteshsahu.BackupRestoreCommon.TaskRunner.run(TaskRunner.java:294)
at java.lang.Thread.run(Thread.java)
7:12:30: External storage is ready
7:12:30: Trying to getExternalStorageState
7:12:30: Acquiring cpu wake lock
7:12:30: Creating new Backup File:/storage/sdcard0/SMSBackupRestore/sms-20140807071224.xml
7:12:30: Creating New Backup. File: /storage/sdcard0/SMSBackupRestore/sms-20140807071224.xml
7:11:6: AmazonAds failed to load: The configuration was unable to be loadedCODE]

Related

aosp kitkat4.4 nexus 7(deb) not boot

hi all:
i download aosp kitkat4.4 source codes from google website. i compiled the code. i got the ROM.but when i flash the ROM to my device nexus 7(deb). it cannot boot.
from the log. i found that following error log. the sentence "couldn't find an OpenGL ES implementation" maybe cause the fatal question.
any advices is welcomed !
thank
brian
02-10 08:37:07.375: E/QCOMKeyMaster(17633): failed to load qseecom library
02-10 08:37:07.375: E/keystore(17633): could not open keymaster device in keystore (Operation not permitted)
02-10 08:37:07.375: E/keystore(17633): keystore keymaster could not be initialized; exiting
02-10 08:37:07.405: A/libEGL(17630): couldn't find an OpenGL ES implementation
02-10 08:37:07.405: A/libc(17630): Fatal signal 6 (SIGABRT) at 0x000044de (code=-6), thread 17630 (surfaceflinger)
02-10 08:37:07.575: E/msm8960_platform(17632): platform_init: DLOPEN failed for libacdbloader.so
02-10 08:37:07.575: E/msm8960_platform(17632): platform_init: DLOPEN failed for libcsd-client.so
02-10 08:37:07.575: E/MonoPipe(17632): Failed to fetch local time frequency when constructing a MonoPipe (res = -32). getNextWriteTimestamp calls will be non-functional

[Q] Juicedefender keeps crashing after update to CM 12 lollipop

Hi
I've been using Juicedefender Ultimate for over a year now, and have never experienced any problems with it. I've just a clean update to Lollipop CM 12 Nightly. Now Juicedefender Ultimate keeps crashing - both when i'm opening the app and wifi isn't activated (instant crash) and when i lock my phone and wifi disconnects (which is a setting i prefer in juicedefender). I can see from the log that they recommend that i reinstall, which i have tried both in play store and in root browser - same problem. I have tried to factory reset the phone, same result. I've come to a point where i don't know how to proceed, which is why i write to you.
I've got the crashlog here:
Code:
JuiceDefender version 3.9.4
Device: A0001
bacon/bacon-userdebug 5.0.2 LRX22G 47d780a5e7 test-keys/5.0.2/oneplus/bacon/A0001:4.4.2/KVT49L/XNPH25R:user/release-keys
Hash: 1523535328
EXCEPTION
java.lang.SecurityException: No permission to write APN settings
No permission to write APN settings
com.latedroid.juicedefender.bf.a(SourceFile:873)
com.latedroid.juicedefender.bj.i(SourceFile:7036)
com.latedroid.juicedefender.bj.e(SourceFile:7077)
com.latedroid.juicedefender.eh.handleMessage(SourceFile:3256)
com.latedroid.juicedefender.bj.run(SourceFile:5118)
Fatal error - JuiceDefender disabled!
The app package might be damaged. Please uninstall JuiceDefender, reboot, then reinstall it
------
Phone type: 1
Profile: 5
[data 3] data 5000ms avg (now: 1/2)
wifi autodisable 8000ms avg (now: 1/2)
sync ping
[bt]
------
battery 15 chrg ac
screen unlock
traffic 10/15(30)
sys: 5
------
00:40 ERROR The app package might be damaged. Please uninstall JuiceDefender, reboot, then reinstall it
00:40 ERROR Fatal error - JuiceDefender disabled!
00:40 ERROR com.latedroid.juicedefender.bj.run(SourceFile:5118)
00:40 ERROR com.latedroid.juicedefender.eh.handleMessage(SourceFile:3256)
00:40 ERROR com.latedroid.juicedefender.bj.e(SourceFile:7077)
00:40 ERROR com.latedroid.juicedefender.bj.i(SourceFile:7036)
00:40 ERROR com.latedroid.juicedefender.bf.a(SourceFile:873)
00:40 ERROR No permission to write APN settings
00:40 ERROR java.lang.SecurityException: No permission to write APN settings
00:40 ERROR EXCEPTION
00:40 Connected: mobile
00:40 Screen on (user present)
00:40 JuiceDefender v3.9.4 enabled: advanced profile - Data m3 WiFi Sync ping - Location training - Schedule Data WiFi 0m/15m, Night, AC Charger, Battery 15%, Traffic 10KB/15s 30s, Screen unlock Data WiFi
00:40 Radio control unavailable
00:40 ROM is not compatible with AOSP helper (band switch control is unavailable) - get CyanogenMod ;)
00:40 ERROR com.latedroid.juicedefender.App.onCreate(SourceFile:356)
00:40 ERROR com.latedroid.juicedefender.bu.a(SourceFile:236)
00:40 ERROR com.latedroid.juicedefender.bu.a(SourceFile:121)
00:40 ERROR open failed: EACCES (Permission denied)
00:40 ERROR com.latedroid.juicedefender.App.onCreate(SourceFile:356)
00:40 ERROR com.latedroid.juicedefender.bu.a(SourceFile:236)
00:40 ERROR com.latedroid.juicedefender.bu.a(SourceFile:121)
00:40 ERROR /data/system/packages.xml: open failed: EACCES (Permission denied)
00:40 ERROR java.io.FileNotFoundException: /data/system/packages.xml: open failed: EACCES (Permission denied)
00:40 ERROR EXCEPTION
00:40 Regular AOSP installation not possible on Android 2.3+
00:40 AOSP helper not found or outdated
00:40 3: Found interface
00:40 WARNING 2:Method not found!
00:40 The device is rooted
00:40 ---------------------------- (initialization)
00:27 ERROR The app package might be damaged. Please uninstall JuiceDefender, reboot, then reinstall it
00:27 ERROR Fatal error - JuiceDefender disabled!
00:27 ERROR com.latedroid.juicedefender.bj.run(SourceFile:5118)
00:27 ERROR com.latedroid.juicedefender.eh.handleMessage(SourceFile:3114)
00:27 ERROR com.latedroid.juicedefender.bj.a(SourceFile:2294)
00:27 ERROR com.latedroid.juicedefender.bj.c(SourceFile:2328)
00:27 ERROR com.latedroid.juicedefender.bj.e(SourceFile:7077)
00:27 ERROR com.latedroid.juicedefender.bj.i(SourceFile:7036)
00:27 ERROR com.latedroid.juicedefender.bf.a(SourceFile:873)
00:27 ERROR No permission to write APN settings
00:27 ERROR java.lang.SecurityException: No permission to write APN settings
00:27 ERROR EXCEPTION
00:27 Training for location "Munkenet-5GHz": 5% complete
00:27 Connected: mobile
00:26 WiFi disabled
00:26 Screen off
00:25 AutoSync ping
00:25 Screen on (user present)
00:25 Screen off
00:24 AutoSync ping
00:24 Screen on (user present)
00:23 Data traffic detected (45KB/45s), delaying disable
00:23 Data traffic detected (58KB/30s), delaying disable
00:22 Screen off
00:17 AutoSync ping
00:17 Schedule stop
00:16 Schedule start
00:13 Charger disconnected
00:09 AutoSync ping
00:08 Screen on (user present)
00:08 Screen off
00:04 Charger connected
00:04 Charger disconnected
00:04 AutoSync ping
00:03 Screen on (user present)
00:03 Screen off
00:03 Charger connected
00:03 Charger disconnected
00:01 Created location for network "Munkenet-5GHz": 20m (0s) - 56.14292,10.20297 - 20m (0s) - 56.14292,10.20297
00:01 AutoSync ping
00:01 Connected: WiFi
00:01 Screen on (user present)
00:01 JuiceDefender v3.9.4 enabled: advanced profile - Data m3 WiFi Sync ping - Location - Schedule Data WiFi 0m/15m, Night, AC Charger, Battery 15%, Traffic 10KB/15s 30s, Screen unlock Data WiFi
00:00 Root access granted
00:00 AutoSync ping
00:00 Connected: WiFi
00:00 Screen on (user present)
00:00 WiFi enabled by user
00:00 Mobile data is back to JD control
00:00 JuiceDefender v3.9.4 enabled: advanced profile - Data m3 WiFi Sync ping - - Schedule Data WiFi 0m/15m, Night, AC Charger, Battery 15%, Traffic 10KB/15s 15s, Screen unlock Data WiFi
00:00 Radio control unavailable
00:00 User had enabled AutoSync
00:00 Data enabled
00:00 User had changed WiFi sleep policy
00:00 User had changed screen brightness mode
00:00 User had changed screen timeout to 30
00:00 User had disabled airplane mode
00:00 JuiceDefender disabled, restoring previous state
00:00 WARNING JuiceDefender wasn't shut down properly!
00:00 Radio control unavailable
00:00 Checking license
00:00 ROM is not compatible with AOSP helper (band switch control is unavailable) - get CyanogenMod ;)
00:00 ERROR com.latedroid.juicedefender.App.onCreate(SourceFile:356)
00:00 ERROR com.latedroid.juicedefender.bu.a(SourceFile:236)
00:00 ERROR com.latedroid.juicedefender.bu.a(SourceFile:121)
00:00 ERROR open failed: EACCES (Permission denied)
00:00 ERROR com.latedroid.juicedefender.App.onCreate(SourceFile:356)
00:00 ERROR com.latedroid.juicedefender.bu.a(SourceFile:236)
00:00 ERROR com.latedroid.juicedefender.bu.a(SourceFile:121)
00:00 ERROR /data/system/packages.xml: open failed: EACCES (Permission denied)
00:00 ERROR java.io.FileNotFoundException: /data/system/packages.xml: open failed: EACCES (Permission denied)
00:00 ERROR EXCEPTION
00:00 Regular AOSP installation not possible on Android 2.3+
00:00 AOSP helper not found or outdated
00:00 3: Found interface
00:00 WARNING 2:Method not found!
Same problem here. Still no solution.
Same here, with a Storex "S'Phone QC 51" with stock Android 5.1.

Error 1001

How to fix [Error 1001, twrp error 7] while porting ROMs?

How To Guide Bypass "System update failed" - Update w/ Fastboot

Update notifications appeared, the update was recognized, but it failed instantly.
Spoiler: Error Stacktrace
Code:
06-26 06:38:27.804 1510 1510 E update_engine: DM_DEV_REMOVE failed for [vendor_b]: Device or resource busy
06-26 06:38:27.806 1510 1510 E update_engine: Could not delete snapshot device: vendor_b
06-26 06:38:27.807 1510 1510 E update_engine: DM_DEV_REMOVE failed for [product_b]: Device or resource busy
06-26 06:38:27.808 1510 1510 E update_engine: Could not delete snapshot device: product_b
06-26 06:38:27.809 1510 1510 E update_engine: DM_DEV_REMOVE failed for [system_ext_b]: Device or resource busy
06-26 06:38:27.810 1510 1510 E update_engine: Could not delete snapshot device: system_ext_b
06-26 06:38:27.811 1510 1510 E update_engine: DM_DEV_REMOVE failed for [odm_b]: Device or resource busy
06-26 06:38:27.812 1510 1510 E update_engine: Could not delete snapshot device: odm_b
06-26 06:38:27.813 1510 1510 E update_engine: Could not remove all snapshots
06-26 06:38:27.814 1510 1510 E update_engine: [ERROR:dynamic_partition_control_android.cc(759)] Cannot begin new update.
06-26 06:38:27.815 1510 1510 E update_engine: [ERROR:dynamic_partition_control_android.cc(463)] PrepareSnapshotPartitionsForUpdate failed in Android mode
06-26 06:38:27.816 1510 1510 E update_engine: [ERROR:delta_performer.cc(1411)] Unable to initialize partition metadata for slot A
06-26 06:38:27.816 1510 1510 I update_engine: [INFO:delta_performer.cc(1325)] [UpdateEngine] ParseManifestPartitions : Orignal required_size = 0
06-26 06:38:27.817 1510 1510 E update_engine: [ERROR:download_action.cc(336)] Error ErrorCode::kInstallDeviceOpenError (7) in DeltaPerformer's Write method when processing the received payload -- Terminating processing
06-26 06:38:27.817 1510 1510 I update_engine: [INFO:multi_range_http_fetcher.cc(177)] Received transfer terminated.
06-26 06:38:27.818 1510 1510 I update_engine: [INFO:multi_range_http_fetcher.cc(129)] TransferEnded w/ code 200
06-26 06:38:27.818 1510 1510 I update_engine: [INFO:multi_range_http_fetcher.cc(131)] Terminating.
06-26 06:38:27.822 1510 1510 I update_engine: [INFO:action_processor.cc(116)] ActionProcessor: finished DownloadAction with code ErrorCode::kInstallDeviceOpenError
06-26 06:38:27.822 1510 1510 I update_engine: [INFO:action_processor.cc(121)] ActionProcessor: Aborting processing due to failure.
06-26 06:38:27.823 1510 1510 I update_engine: [INFO:update_attempter_android.cc(523)] Processing Done.
06-26 06:38:27.824 2954 3366 I UpdateLauncher: status: 0, percent:0.0
06-26 06:38:27.826 2954 3366 I SeamlessUpdateNotifier: percent:0
06-26 06:38:27.826 1510 1510 I update_engine: [INFO:metrics_reporter_android.cc(131)] Current update attempt downloads 0 bytes data
06-26 06:38:27.828 2954 3366 I UpdateLauncher: errorCode: 7
06-26 06:38:27.830 2954 3366 I SeamlessUpdateNotifier: percent:-1
06-26 06:38:27.831 2954 3366 I SeamlessUpdateNotifier: show update fail dialog
I have since resolved the error by flashing a raw firmware without a wipe.
This post is for archival purposes or simply an alternative installation method
Manual Update w/ Fastboot
This process does not include a data wipe.
Wiping data should be done at your own discretion.
Grab payload_dumper (https://github.com/vm03/payload_dumper)
Download update from the Asus site (ie. WW-18.0840.2104.56)
Extract the payload.bin from update to the payload_dumper folder
Follow the instructions to run payload_dumper on the payload.bin
If you have fastboot installed (ie. Android SDK), skip this section
ASUS_Fastboot-Portable.zip | by twistedumbrella for ROG Phone 5
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
Extract the contents to the output folder of payload_dumper
This is the same fastboot included in the raw firmware files
Once fastboot is available, you may continue the update process
Download the flash_all.sh.zip file attached to this post
Extract the script to the output folder of payload_dumper
Reboot your phone into bootloader (volume up + power)
Connect your phone and run the script (Mac / Linux)
The following errors are perfectly normal and can be ignored:
(Script updated. Flashing non-hlos image should be resolved)
Code:
FAILED (remote: 'Flashing non-hlos image is not allowed in lock state')
Code:
Invalid sparse file format at header magic
Once the phone reboots, launch settings to verify the version number
Restoring Magisk
Copy the boot.img from payload_dumper output to the phone
Run Magisk and patch the file
Copy the patched file back to the computer
Flash the boot.img with "fastboot flash boot [file name]"
Your rog flashed 5 times with the edl repair and then tried the update, maybe something was shot by the custom kernel that you tried to flash / boot
ChrisFeiveel said:
Your rog flashed 5 times with the edl repair and then tried the update, maybe something was shot by the custom kernel that you tried to flash / boot
Click to expand...
Click to collapse
No idea how that is possible. I've only flashed the repair once and the kernel was stock. Possibly something I wasn't supposed to uninstall to perform updates.
Edit: updated manually so we'll see what happens next time.
Asus took 2 days just sending the form to "officially" investigate the issue. Nobody has time for their TPS Reports, so I found a way to install the update myself.
Updating to WW-18.0840.2104.56 with this method did not restore standard installation for WW18.0840.2106.86, but the scripts have been updated to fix the non-hlos image errors, which may fix updating for future versions.
We should unlock bootloader for this ?
jaleel (jelly) said:
We should unlock bootloader for this ?
Click to expand...
Click to collapse
No. You should not be using this method unless you are getting the specific error that the update fails. If your update is not failing, this may break it.
I'm having wifi problem I'm thinking to update but is not showing me I had changed to data in update but also it's was not recognise .. it seems like same version update will not show in update notification ..
If you already updated, the update is complete. Installing it a second time will not change anything in it.
I had download ota file from asus website keep in root storage then also not showing update .. oneplus will show update but asus seems not show
Make sure to reboot
twistedumbrella said:
Make sure to reboot
Click to expand...
Click to collapse
Some many times I had rebooted
jaleel (jelly) said:
Some many times I had rebooted
Click to expand...
Click to collapse
Someone on zentalk stated that rolling the last number one number higher will prompt the install as well. The downside is if the next official comes in with that number you have to manual update again using the same method.
I have not tried this myself and have not seen any proof of work. Proceed at your own risk here.
BILLYB187 said:
Someone on zentalk stated that rolling the last number one number higher will prompt the install as well. The downside is if the next official comes in with that number you have to manual update again using the same method.
I have not tried this myself and have not seen any proof of work. Proceed at your own risk here.
Click to expand...
Click to collapse
They usually skip a few incremental version numbers, so it may even work without causing issues for future updates.
System update fails if the device fingerprint doesn't match the firmware fingerprint. By Fingerprint I mean Device ID embedded in Vendor Partition.
Eg: If you have Tencent Hardware with a WW Rom installed on it, and if you haven't edited the fingerprint (Device ID) of the device to WW, It will never accept WW OTA Files automatically, you will always have to use fastboot.
This file is located in the Vendor image, and you can edit it using root explorer.
You can read more here - Changing Fingerprint from CN to WW
Doing this once fixes it for good, and never again you'll have to use manual updates.
JazonX said:
System update fails if the device fingerprint doesn't match the firmware fingerprint. By Fingerprint I mean Device ID embedded in Vendor Partition.
Eg: If you have Tencent Hardware with a WW Rom installed on it, and if you haven't edited the fingerprint (Device ID) of the device to WW, It will never accept WW OTA Files automatically, you will always have to use fastboot.
This file is located in the Vendor image, and you can edit it using root explorer.
You can read more here - Changing Fingerprint from CN to WW
Doing this once fixes it for good, and never again you'll have to use manual updates.
Click to expand...
Click to collapse
Actually, the manual updates will always be required if you unlock the bootloader. The Asus app may or may not be to blame for that.
Fingerprint issues are most often found on devices with the notification about mismatched firmware. This one was something with the active partition or the installer itself. Flashing raw firmware fixed it and restored regular installation.
I'm sure the info will be useful for anyone that thinks they would be able to fix a fingerprint issue by flashing firmware, though, since it won't solve it.
The more I think about it, this issue may have started when I did an update using the Magisk feature to preserve root using an inactive partition.
I wonder if there was some sort of corruption with the partition it selected after doing it a few times. Something to keep in mind when you update, I guess.

[GKI] [android13-5.10] [Bazel] build failed Differences between ksymtab and symbol list detected!

I following this instruction:https://source.android.com/docs/setup/build/building-kernels
I initialized repo and synced
Using Bazel to build (with build/build.sh same error)
Using this command:tools/bazel run --lto=none //common:kernel_aarch64_dist -- --dist_dir=out/android13-5.10/dist
And get this error:
ERROR: /home/aaron/Builds/android-kernel/common/BUILD.bazel:26:22: Checking for kmi_symbol_list_
strict_mode //common:kernel_aarch64 failed: (Exit 1): bash failed: error executing command (from
target //common:kernel_aarch64) /bin/bash -c ... (remaining 1 argument skipped)
Use --sandbox_debug to see verbose messages from the sandbox and retain the sandbox build root f
or debugging
ERROR: Differences between ksymtab and symbol list detected!
Symbols missing from ksymtab:
- __cfi_slowpath
Symbols missing from symbol list:
Target //common:kernel_aarch64_dist failed to build
Use --verbose_failures to see the command lines of failed build steps.
INFO: Elapsed time: 3572,647s, Critical Path: 3535,69s
INFO: 7 processes: 3 internal, 4 linux-sandbox.
FAILED: Build did NOT complete successfully
FAILED: Build did NOT complete successfully
Hello, I also encountered this problem, how did you solve it?

Categories

Resources