[Q] YP-G1CWY/XAA Mysterious Bootloop - Samsung Galaxy Player 4.0, 5.0

Hello, currently, one of our Galaxy 4.0 Players is stuck in a boot loop. I have been searching this site and a few others for over a month now for solutions and am stumped.
I have tried flashing several different US YP-G1 stock ROMs using both Heimdall and Odin, Terrasilent kernel, Steve's kernel, Icyfusion ROM, factory reset, wiping cache/dalvik.
Over a month ago, the device started randomly rebooting and showing the first time startup screen each time it rebooted like this. When it would have a random reboot however, it would get stuck in a boot loop and have to be restarted by holding the power button or pulling battery. Then after a couple weeks of that, it has since been stuck in a boot loop.
Interesting "dmesg" information that may or may not have anything to do with this are:
7.347889] init: SEC_DEVENC ***[/dev/block/mmcblk0p2][0]
7.352046] init: failed that mount s:'/dev/block/mmcblk0p2', t:'/data', f
7.362574] init: SEC_DEVENC ***[/dev/block/mmcblk0p2][0]
7.368081] init: failed that mount s:'/dev/block/mmcblk0p2', t:'/data', f
8.585066] mmc0: error -110 whilst initialising MMC card
8.655510] mmc1: new high speed SDHC card at address b368
I believe that the internal sdcard has died and have formatted the external one with the vfat and rfs partitions to act as the internal sdcard. But according to dmesg, it appears that perhaps mmcblk0p2 is trying to be mounted in the boot procedure before MMC1 is detected?
Any help is greatly appreciated and I will provide any more information as needed.
-Tony

"FATAL EXCEPTION IN SYSTEM PROCESS: ConnectivityThread"
update
Between flashing the international verions's bootloader, reflashing recovery rom, Terrasilent kernel and restoring a Nandroid backup from our other YP-G1, the mounting problems seem to be gone now.
However, there is still a bootloop problem which I believe has something to do with these logcat entries:
D/NativeDaemonConnector( 246): NativeDaemonConnector ::
D/NetdConnector( 246): run ::
D/NetdConnector( 246): listenToSocket ::
I/SystemServer( 246): Connectivity Service
W/dalvikvm( 246): threadid=17: thread exiting with uncaught exception (group=0x
40015578)
E/ ( 246): Dumpstate > /data/log/dumpstate_sys_error
V/ConnectivityService( 246): ConnectivityService starting up
E/ActivityThread( 246): Failed to find provider info for settings
E/AndroidRuntime( 246): *** FATAL EXCEPTION IN SYSTEM PROCESS: ConnectivityThre
ad
E/AndroidRuntime( 246): java.lang.NullPointerException
E/AndroidRuntime( 246): at android.provider.Settings$NameValueCache.getS
tring(Settings.java:664)
E/AndroidRuntime( 246): at android.provider.Settings$Secure.getString(Se
ttings.java:2209)
E/AndroidRuntime( 246): at com.android.server.ConnectivityService.<init>
(ConnectivityService.java:264)
E/AndroidRuntime( 246): at com.android.server.ConnectivityService.<init>
(ConnectivityService.java:61)
E/AndroidRuntime( 246): at com.android.server.ConnectivityService$Connec
tivityThread.run(ConnectivityService.java:229)
I/dumpstate( 277): begin
E/dumpstate( 277): Cannot get free space size. So, skip dumpstate.
When the problems first started before all the flashing, logcat also showed this fatal exception in ConnectivityThread

Related

[Q] Official Froyo Camera on 720p forced close issues

Hi everyone,
I am new here on the forum, and the Streak is my very first Android phone. Just wanted to quickly say I really enjoy the community here and I like how everyone tries to help each other.
I noticed that a lot of people have been having problems with Camera forced close issues, which is what I've been experiencing as well. Please mind that this is my first Android phone, and my understanding of Linux is very limited.
I thought I'd post my findings so far in the forced close issues I've been experiencing. Here are some of what I think are the culprits behind the forced close:
Main Log:
1. First it tries to set unsupported parameters for the audio input, followed by more failed attempts to set other parameters
Code:
11-21 02:00:11.475 E/audio_input( 91): unsupported parameter:
x-pvmf/media-input-node/cap-config-interface;valtype=key_specific_value
11-21 02:00:11.475 E/audio_input( 91): VerifyAndSetParameter failed
2. Big Fail! It tries to load what looks to be a video encoder, and can't find it:
Code:
11-21 02:00:11.525 E/PVOMXEncNode( 91): PVMFOMXEncNode-Video_M4V::DoPrepare(): Cannot get component OMX.qcom.video.encoder.mpeg4 handle, try another component if available
11-21 02:00:11.525 E/PVOMXEncNode( 91): PVMFOMXEncNode-Video_M4V::DoPrepare(): Cannot get component OMX.PV.mpeg4enc handle, try another component if available
11-21 02:00:11.525 E/AuthorDriver( 91): Command 13 completed with error -17
11-21 02:00:11.535 E/MediaRecorder( 754): prepare failed: -17
11-21 02:00:11.535 E/videocamera( 754): prepare failed for /mnt/sdcard/DCIM/Camera/VID_20101121_020011.3gp
3. Dalvik Virtual Machine pops up an error, and throws it at Android for error handling:
Code:
11-21 02:00:11.545 F/dalvikvm( 754): Exception!!! threadid=1: thread exiting with uncaught exception (group=0x4001d7d8)
11-21 02:00:11.565 E/AndroidRuntime( 754): FATAL EXCEPTION: main
11-21 02:00:11.565 E/AndroidRuntime( 754): java.lang.RuntimeException: java.io.IOException: prepare failed.
11-21 02:00:11.565 E/AndroidRuntime( 754): at com.android.camera.VideoCamera.initializeRecorder(VideoCamera.java:1297)
11-21 02:00:11.565 E/AndroidRuntime( 754): at com.android.camera.VideoCamera.access$300(VideoCamera.java:99)
11-21 02:00:11.565 E/AndroidRuntime( 754): at com.android.camera.VideoCamera$MainHandler.handleMessage(VideoCamera.java:300)
Events Log:
1. Pretty straightforward -- video camera -- problem returns to android for handling during use of Media Recorder?
Code:
11-21 02:00:11.575 I/am_crash( 148): [754,com.android.camera,48709,java.io.IOException,prepare failed.,MediaRecorder.java,-2]
11-21 02:00:11.585 I/am_finish_activity( 148): [1193151496,8,com.android.camera/.VideoCamera,crashed]
11-21 02:00:11.585 I/am_pause_activity( 148): [1193151496,com.android.camera/.VideoCamera]
11-21 02:00:12.095 I/am_resume_activity( 148): [1190436808,2,com.dell.launcher/.Launcher]
System Log:
1. Same below -- start video camera, crash, Android handles the "oh no"s...
Code:
cat=[android.intent.category.LAUNCHER] flg=0x14000000 cmp=com.android.camera/.Camera }
11-21 02:00:10.445 I/ActivityManager( 148): Starting activity: Intent { flg=0x4000000 cmp=com.android.camera/.VideoCamera (has extras) }
11-21 02:00:11.565 E/AndroidRuntime( 754): FATAL EXCEPTION: main
11-21 02:00:11.565 E/AndroidRuntime( 754): java.lang.RuntimeException: java.io.IOException: prepare failed.
I've also attached the processes log, processesthread log, and system.prop files for reference (I removed all wifi and carrier information at the bottom of the system.prop, but I don't think it's relevant)
I think the main cause of the crash is the media recorder trying to set unsupported parameters and missing video encoder. Not sure though. Any assistance would be greatly appreciated -- I am still looking into the problems, and will get back to everyone on my findings.
Good job...Guess the codec might also be dealing with audio and the bad parm is caused by the unregistered/missing codec? [noob]
Yes - I think definitely there were some serious problems with updating it from a non-00 baseband version.
I think dependencies are missing/broken from either updating from a non 00 baseband version or the flashboot method itself. Those with 00 baseband have it easier, as they already have all the dependencies and can upgrade using the
"copy package to /sdcard/update.pkg" method.
I gave up trying to find the dependencies that were broken, instead went the "downgrading, converting to baseband 00 version and upgrading back to Froyo" method.
I've finally got everything working (including 720p recording) with a combination of Homeiss' "How To Install Official Dell 2.2 Upgrade.pkg" and Geek78's "How to go back from 21 to 00 builds" guide with a little alteration suggested by llecaroz (from modaco forum).
I think this downgrade first to Baseband 00 first than upgrade should fix all problems. The trick is to downgrade to downgrade to 1.6 that matches your baseband (21,31) first! In my case, I had a baseband 21 version.
Suggestions:
- I suggest to downgrade using Geek78's guide first (because, based on my experience, downgrading from 21 2.1 -> 00 1.6 ends up with DELL forever logo).
- If you end up with a "FOTA version error" thingy, you need to flash with a different recovery file (it changes the recovery version from 21 to 00)
- If getting "flash_image: not found" error, it means you are missing the binary. Get it from cyanogen.
Good luck with Homeiss' and Geek78's guide.
I can re-compile a more comprehensive guide, but I think I am unable to place links in here.
If you have upgraded the fastboot way (with the 3 files Stephen provided) You will have FCs on 720p recording! I have downgraded mine to 6267 and then upgraded with the pkg file! Now 720p works perfect!

[Q] Connectivity Services exception causes boot loop

Hi.
Summary: the AndroidRuntime process fails when starting the Connectivity Service, causing my phone into a boot loop.
Sorry for the very verbose post.
Background: I've spent quite a bit of time trying to resolve a problem that causes my Sony Ericsson Xperia X10 Mini (from O2) to go into a boot loop. I've rooted the phone some time ago using this process: (sorry the forum prevents me from posting link, please copy and paste this: android.doshaska.net/x10miniroot).
I then proceeded to remove some of the redundant programs from /system/app.
Everything worked fine for several weeks until the phone started complaining about the storage being filled up. I could see that /data was getting full and I suspected that the K9 email client I had installed was using lots f space to keep the IMAP folders synced.
I can't remember if the phone rebooted itself or if I did it manually, but it never managed to boot up again, and is ever since stuck at the Sony Ericsson logo.
adb logcat tells me that the AndroidRuntime process fails when starting the Connectivity Service. It's stuck in this loop, but I've isolated one single loop in the attachment logcat.txt. The crash file references has been attached as 1279210811.txt.
The final fatal crash is:
I/SystemServer( 1297): Starting Connectivity Service.
W/dalvikvm( 1297): threadid=51: thread exiting with uncaught exception (group=0x2aac9a28)
E/AndroidRuntime( 1297): Uncaught handler: thread ConnectivityThread exiting due to uncaught exception
E/AndroidRuntime( 1297): *** EXCEPTION IN SYSTEM PROCESS. System will crash.
E/AndroidRuntime( 1297): java.lang.NullPointerException
E/AndroidRuntime( 1297): at android.app.ActivityThread.getProvider(ActivityThread.java:3938)
E/AndroidRuntime( 1297): at android.app.ActivityThread.acquireProvider(ActivityThread.java:3967)
E/AndroidRuntime( 1297): at android.app.ApplicationContext$ApplicationContentResolver.acquireProvider(ApplicationContext.java:1527)
E/AndroidRuntime( 1297): at android.content.ContentResolver.acquireProvider(ContentResolver.java:579)
E/AndroidRuntime( 1297): at android.content.ContentResolver.query(ContentResolver.java:147)
E/AndroidRuntime( 1297): at android.provider.Settings$NameValueCache.getString(Settings.java:476)
E/AndroidRuntime( 1297): at android.provider.Settings$Secure.getString(Settings.java:1701)
E/AndroidRuntime( 1297): at android.provider.Settings$Secure.getInt(Settings.java:1741)
E/AndroidRuntime( 1297): at com.android.server.ConnectivityService.getPersistedNetworkPreference(ConnectivityService.java:182)
E/AndroidRuntime( 1297): at com.android.server.ConnectivityService.<init>(ConnectivityService.java:123)
E/AndroidRuntime( 1297): at com.android.server.ConnectivityService.<init>(ConnectivityService.java:47)
E/AndroidRuntime( 1297): at com.android.server.ConnectivityService$ConnectivityThread.run(ConnectivityService.java:87)
I've had a look at the JavDoc for android.app.ActivityThread.getProvider, but I've not been able to find any useful information. I have to guess that the start-up process fails to read the provider (network) specific settings for some reason. I don't have a clue whether the source is a file, database or something else.
A wild guess is that something got corrupted when the data partition filled up. There are some upset earlier in the log (line 180) when the PackageManager is reading an XML file that relates to the PackageManager settings that seems to have been corrupted:
E/PackageManager( 1297): Error reading package manager settings E/PackageManager( 1297): org.xmlpull.v1.XmlPullParserException:
Premature end of document. (position:line -1, column -1) caused by:
org.apache.harmony.xml.ExpatParser$ParseException: At line 1, column 0: no element found
I've seen a few similar posts, but nothing exactly like this nor anything that I could use to resolve it.
Stupid section
I've got myself into this through a combination of stupidity and bad luck. I've backed up all .APK that I've removed and created a log of what I removed (that I'm still looking for). I thought this was all that I needed and I don't have a full backup.
Unfortunately, the root access now gives me a segmentation fault and the root process requires the GUI to work, so I can't repeat the process. I don't want to try another root process before I've tried what I can to get the phone back in a reasonable state.
Fortunately, I still have full adb access, so I have visibility and some control over the phone.
Any help on this would be much appreciated. At least I've saved you the time pointing out that I'm an idiot not doing a full backup
Regards,
Dan

[Request] LG Optimus One - Orange UK Original ROM

Request is in the title - the LG Optimus One from Orange UK contains the Orange Signal Boost (UMA) software that would be useful to get working on other android phones with networks which support UMA. The topic is here but I've cross-posted here in case the topic gets lost in the general forum.
Here you go, This should be the original Orange V10C_00 firmware for your phone:
Code:
csmg.lgmobile.com:9002/swdata/WEBSW/LGP500/AORUBK/V10c_00/V10C_00.kdz
I was thinking maybe someone with the Optimus One could just backup the apk for Orange Signal Boost and post that. I have tried expanding the rom posted in the link and have got as far as the mbn files and boot.img etc but I don't know how to get at the apk's...
Bump
Could any owner of optimus one share that app with us ?
please
Again, please anyone! We just need a backup of the apk to get started!
Sent from my HTC Desire using XDA App
Ok, I managed to unpack the KDZ file but still couldn't find a way extract the Orange Signal Booster apk from boot.img file; so if anyone has backup of the apk it would be greatly appreciated.
I tried the same thing but had no luck. If you had the handset you could use a number of different apps (astro, titanium backup) to make a backup of the .apk file with very little technical knowledge.
It would be god send if we could get this app running on other handsets...
Here is the APK!
OK here is the APK which I have extracted from the ROM image. I tried installing it on my desire and it FCs as soon as I attempt to run it. If anyone else wants to get onboard with this please do!
Hi ballandbiscuit, many thanks for the APK. Tried it on my HTC DHD and had the same FC result as you. As far as I can tell, this is not a hardware restriction but possibly the result of other system services required by the app not installed on the handset.
I really wish someone from Orange with a bit of technical knowhow would get involved and assist us with this much needed feature.
what about some kind of logging? maybe it say something...
Sent from my LG-P500 using XDA App
Here is some data from logcat
Code:
I/ActivityManager( 167): Starting activity: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.android.kineto/.kineto }
I/ActivityManager( 167): Start proc com.android.kineto for activity com.android.kineto/.kineto: pid=1695 uid=10103 gids={3003, 3002, 3001, 1015}
W/dalvikvm( 1695): Exception Ljava/lang/UnsatisfiedLinkError; thrown during Lcom/android/kineto/kineto;.<clinit>
W/dalvikvm( 1695): Class init failed in newInstance call (Lcom/android/kineto/kineto;)
D/AndroidRuntime( 1695): Shutting down VM
W/dalvikvm( 1695): threadid=1: thread exiting with uncaught exception (group=0x4001d7e8)
E/AndroidRuntime( 1695): FATAL EXCEPTION: main
E/AndroidRuntime( 1695): java.lang.ExceptionInInitializerError
E/AndroidRuntime( 1695): at java.lang.Class.newInstanceImpl(Native Method)
E/AndroidRuntime( 1695): at java.lang.Class.newInstance(Class.java:1429)
E/AndroidRuntime( 1695): at android.app.Instrumentation.newActivity(Instrumentation.java:1021)
E/AndroidRuntime( 1695): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2577)
E/AndroidRuntime( 1695): at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2679)
E/AndroidRuntime( 1695): at android.app.ActivityThread.access$2300(ActivityThread.java:125)
E/AndroidRuntime( 1695): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2033)
E/AndroidRuntime( 1695): at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime( 1695): at android.os.Looper.loop(Looper.java:123)
E/AndroidRuntime( 1695): at android.app.ActivityThread.main(ActivityThread.java:4627)
E/AndroidRuntime( 1695): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime( 1695): at java.lang.reflect.Method.invoke(Method.java:521)
E/AndroidRuntime( 1695): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:868)
E/AndroidRuntime( 1695): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:626)
E/AndroidRuntime( 1695): at dalvik.system.NativeStart.main(Native Method)
E/AndroidRuntime( 1695): Caused by: java.lang.UnsatisfiedLinkError: Library kineto not found
E/AndroidRuntime( 1695): at java.lang.Runtime.loadLibrary(Runtime.java:461)
E/AndroidRuntime( 1695): at java.lang.System.loadLibrary(System.java:557)
E/AndroidRuntime( 1695): at com.android.kineto.kineto.<clinit>(kineto.java:1552)
E/AndroidRuntime( 1695): ... 15 more
W/ActivityManager( 167): Force finishing activity com.android.kineto/.kineto
W/ActivityManager( 167): Activity pause timeout for HistoryRecord{46506b50 com.android.kineto/.kineto}
I/ActivityManager( 167): No longer want com.google.android.apps.uploader (pid 653): hidden #16
I/Process ( 1695): Sending signal. PID: 1695 SIG: 9
W/InputManagerService( 167): Window already focused, ignoring focus gain of: [email protected]
I/ActivityManager( 167): Process com.android.kineto (pid 1695) has died.
Not sure if this is relevant but earlier in the logcat...
Code:
W/PackageManager( 167): Not granting permission android.permission.DEVICE_POWER to package com.android.kineto (protectionLevel=2 flags=0x48444)
W/PackageManager( 167): Not granting permission android.permission.UPDATE_DEVICE_STATS to package com.android.kineto (protectionLevel=2 flags=0x48444)
W/PackageManager( 167): Unknown permission android.permission.INJECT_EVENT in package com.android.kineto
Having looked at some other posts regarding the T-Mobile US UMA app, which is also Kineto based I think it will take a lot of work to get this functioning. It appears to need some libraries such as...
libkento
linganril
librilswitch
and also some changes to the kernel as per this thread
http://forum.xda-developers.com/showthread.php?t=807116
I don't know if this was ever ported to devices other than the N1. It is shame that it requires more than just an app. Orange should be pushing this to all Android handsets. I don't use my phone at home for calls or texts because the signal is too weak, this is a loss for both myself and Orange because they don't get to charge me for calls I don't make. My wife has a Vodafone Sure Signal box which is brilliant but Orange don't offer such a device...
Okay, I just had a little luck with the UMA application.
Not quite there yet though.
BASICALLY, I have come to understand that the application extracted from various Roms FC cuz they are missing other files they depend on from the ROM.
I was using Orange Signal Boost apk from the Orange Desire S rom (am attaching it) on my HTC Legend.
Then I came across stories of someone in US who had extracted an apk from so Tmobile Rom for wifi calling and made it to work on a Nexus 1. I downloaded that files (also attached). This file was a modded version of original apk and had all the dependant files. (and consequently was 3mb vs 600kb of Orange signal boost)
So what I tried was
1. Install tmobile wifi app
2. Install Orange signal boost on TOP of it. It will ask you that this progam will replace another older program on your phone. Clcik okay.
3. What this does is leave old installed files needed from tmobile app and this time LO AND BEHOLD, signal boost app launches without FC
Here comes the problem though, it doesnt work, cuz somewhere hardcoded in the files that the tmobile app installs is the network info and naturally, our sims being orange are recognized as invalid sim.
Me and a LOT of other people would REALLY appreciate it if someone with any knowhow can look at this and figure it out for us

[Q] Account corruption after reset

Hey,
Ive got a Galaxy Tab 10.1 running stock 3.2. I encountered a strange problem with my tab today.
An app froze(google maps) - I could click the clock and the menu would roll up, it had a black screen and did nothing, so I reset the tab by long pressing power.
After this the tab got stuck at the SAMSUNG logo for a long time, so I tried another reset and then another after cleaning the connectors - the slot wasnt dirty but just in case. After I gave up and left the tab with the SAMSUNG logo for about 10 minutes it finally booted. But the weird part is that it booted like I have just performed a factory reset, but all my data is still there, all apps, heck even my background is the same.
Only thing is, that any app that has some connection to any account stored in on the tab is force closing. Its as if the accounts got corrupted.
Now this happened twice, first time I factory reset the tab and it was then ok, but a second time? I dont want to lose saved games, and stuff...
My question is, has this ever happened to anybody else? Can it be solved without data loss?
radqooo said:
Hey,
Ive got a Galaxy Tab 10.1 running stock 3.2. I encountered a strange problem with my tab today.
An app froze(google maps) - I could click the clock and the menu would roll up, it had a black screen and did nothing, so I reset the tab by long pressing power.
After this the tab got stuck at the SAMSUNG logo for a long time, so I tried another reset and then another after cleaning the connectors - the slot wasnt dirty but just in case. After I gave up and left the tab with the SAMSUNG logo for about 10 minutes it finally booted. But the weird part is that it booted like I have just performed a factory reset, but all my data is still there, all apps, heck even my background is the same.
Only thing is, that any app that has some connection to any account stored in on the tab is force closing. Its as if the accounts got corrupted.
Now this happened twice, first time I factory reset the tab and it was then ok, but a second time? I dont want to lose saved games, and stuff...
My question is, has this ever happened to anybody else? Can it be solved without data loss?
Click to expand...
Click to collapse
It happened to me 3 weeks ago, and all the applications were force closing. I had to uninstall them all, and then reinstall. I did not lose any document though.
Now, I feel that the default browser seems corrupted; Everytime I log in to Facebook, it asks me to to identify the current device.
ace81 said:
It happened to me 3 weeks ago, and all the applications were force closing. I had to uninstall them all, and then reinstall. I did not lose any document though.
Now, I feel that the default browser seems corrupted; Everytime I log in to Facebook, it asks me to to identify the current device.
Click to expand...
Click to collapse
That would make sense, the first time it happened I had the browser opened. I opened logcat to see what are the reasons of force closing, and its talking something about a corrupted database.
Here is an extract what happens when I want to run dropbox.
E/AndroidRuntime( 3182): FATAL EXCEPTION: main
E/AndroidRuntime( 3182): java.lang.RuntimeException: Unable to create application com.dropbox.android.DropboxApplication: android.database.sqlite.SQLiteCantOpenDatabaseException: unable to open database file
E/AndroidRuntime( 3182): at android.app.ActivityThread.handleBindApplication(ActivityThread.java:3702)
E/AndroidRuntime( 3182): at android.app.ActivityThread.access$1200(ActivityThread.java:122)
E/AndroidRuntime( 3182): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1065)
E/AndroidRuntime( 3182): at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime( 3182): at android.os.Looper.loop(Looper.java:132)
E/AndroidRuntime( 3182): at android.app.ActivityThread.main(ActivityThread.java:4126)
E/AndroidRuntime( 3182): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime( 3182): at java.lang.reflect.Method.invoke(Method.java:491)
E/AndroidRuntime( 3182): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:844)
E/AndroidRuntime( 3182): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:602)
E/AndroidRuntime( 3182): at dalvik.system.NativeStart.main(Native Method)
E/AndroidRuntime( 3182): Caused by: android.database.sqlite.SQLiteCantOpenDatabaseException: unable to open database file
E/AndroidRuntime( 3182): at android.database.sqlite.SQLiteDatabase.dbopen(Native Method)
E/AndroidRuntime( 3182): at android.database.sqlite.SQLiteDatabase.openDatabase(SQLiteDatabase.java:983)
E/AndroidRuntime( 3182): at android.database.sqlite.SQLiteDatabase.openDatabase(SQLiteDatabase.java:956)
E/AndroidRuntime( 3182): at android.database.sqlite.SQLiteDatabase.openOrCreateDatabase(SQLiteDatabase.java:1021)
E/AndroidRuntime( 3182): at android.app.ContextImpl.openOrCreateDatabase(ContextImpl.java:772)
E/AndroidRuntime( 3182): at android.content.ContextWrapper.openOrCreateDatabase(ContextWrapper.java:221)
E/AndroidRuntime( 3182): at android.database.sqlite.SQLiteOpenHelper.getWritableDatabase(SQLiteOpenHelper.java:149)
E/AndroidRuntime( 3182): at com.dropbox.android.provider.g.b(panda.py:185)
E/AndroidRuntime( 3182): at com.dropbox.android.DropboxApplication.onCreate(panda.py:59)
E/AndroidRuntime( 3182): at android.app.Instrumentation.callApplicationOnCreate(Instrumentation.java:968)
E/AndroidRuntime( 3182): at android.app.Ac...
Questions go in the Q&A section

Any other fix than reflash for "Unable to find android system package"

After trying to boot my phone several times with an almost empty battery the phone won't boot any more. The boot process hangs in the Jiayu logo (the phone is a Jiayu S3). The phone gets hot, so maybe it is doing something CPU intensive??? I can connect to the phone via adb. Command "adb logcat" shows several messages flowing constantly. The most severe message as far as I can tell is the following:
Code:
E/AndroidRuntime( 841): *** FATAL EXCEPTION IN SYSTEM PROCESS: main
E/AndroidRuntime( 841): java.lang.RuntimeException: Unable to find android system package
E/AndroidRuntime( 841): at com.android.server.am.ActivityManagerService.setSystemProcess(ActivityManagerService.java:2069)
E/AndroidRuntime( 841): at com.android.server.SystemServer.startBootstrapServices(SystemServer.java:500)
E/AndroidRuntime( 841): at com.android.server.SystemServer.run(SystemServer.java:338)
E/AndroidRuntime( 841): at com.android.server.SystemServer.main(SystemServer.java:241)
E/AndroidRuntime( 841): at java.lang.reflect.Method.invoke(Native Method)
E/AndroidRuntime( 841): at java.lang.reflect.Method.invoke(Method.java:372)
E/AndroidRuntime( 841): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:959)
E/AndroidRuntime( 841): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:754)
E/AndroidRuntime( 841): Caused by: android.content.pm.PackageManager$NameNotFoundException: android
E/AndroidRuntime( 841): at android.app.ApplicationPackageManager.getApplicationInfo(ApplicationPackageManager.java:286)
E/AndroidRuntime( 841): at com.android.server.am.ActivityManagerService.setSystemProcess(ActivityManagerService.java:2051)
E/AndroidRuntime( 841): ... 7 more
I think that the error comes from this line in com.android.server.am.ActivityManagerService.setSystemProcess(ActivityManagerService.java):
Code:
ApplicationInfo info =
mSelf.mContext.getPackageManager().getApplicationInfo(
"android", STOCK_PM_FLAGS);
Is there a fix for the message "Unable to find android system package" (package "android")? For example, would re-installing an .apk (which one?) fix this?
I would rather not reflash the ROM. I would like to preserve the data I have, such as text messages, WiFi passwords and WhatsApp contents.
I have already tried twice wiping cache and Dalvik cache.
My phone is Jiayu S3 with stock Android 5.1. It is rooted and has TWRP.
Now only fastboot, adb and TWRP Terminal work for my phone (Jiayu S3). Android user interface won't start, it just shows the Jiayu logo. Is there any command (in fastboot, adb or TWRP Terminal) which would reset the Android user interface so that I could boot into the graphical user interface again?
The phone is the "Jiayu Deutschland" version and it has TWRP 2.8.7.0 and Android 5.1.1. I do not have the original ROM files so I can't just reflash it.
I still haven't made any progress. Android boot just shows the logo and does not open the normal UI. adb logcat displays repeated error "Unable to find android system package". The only things that work are fastboot, adb and TWRP. So basically I have the command line, but not the graphical user interface.
How could I debug error "Unable to find android system package"? Are there any helpful logs? So far I have looked at adb logcat, dmesg and files in /data/anr.
How can I verify that CLASSPATH is OK during boot? What file contains the android system package, how can I verify it? Should I try regenerating dex files? I have already wiped cache and Dalvik cache.

Categories

Resources