After the most recent update (plus rooting), when I open Snote, the app freezes, closes, and then I get the mssage "unfortunate, S note has stopped".
Not too sure what is happening. If I use the Spen and double tap, I can still get the mini-memo pad; when I go and try to read them, the app crashes.
Any suggestions? I haven't heard of this issue before...
Have you cleared s note app data?
Sent from my SGH-T889 using xda app-developers app
kintwofan said:
Have you cleared s note app data?
Sent from my SGH-T889 using xda app-developers app
Click to expand...
Click to collapse
Yes. I've forced-stop and then cleared the data and cache.
I have two "S note" apps in the App manager; I've done this for both of them.
anderroid said:
Yes. I've forced-stop and then cleared the data and cache.
I have two "S note" apps in the App manager; I've done this for both of them.
Click to expand...
Click to collapse
I would delete one. But it will probably be the most helpful if you pull a logcat
Sent from my SGH-T889 using xda app-developers app
kintwofan said:
I would delete one. But it will probably be the most helpful if you pull a logcat
Sent from my SGH-T889 using xda app-developers app
Click to expand...
Click to collapse
Hopefully this is what you wanted?:
04-15 16:49:18.880 D/IPPolicy(1879): updateImsNotification. ComponentName: ComponentInfo{com.sec.android.app.snotebook/com.infraware.filemanager.FmFileTreeListActivity} tickerText null
04-15 16:49:19.425 I/ActivityThread(22675): Pub com.infraware.provider.SNoteProvider: com.infraware.provider.SNoteProvider
04-15 16:49:19.850 D/IPPolicy(1879): updateImsNotification. ComponentName: ComponentInfo{com.sec.android.app.snotebook/com.infraware.filemanager.FmFileTreeListActivity} tickerText null
04-15 16:49:28.295 D/IPPolicy(1879): updateImsNotification. ComponentName: ComponentInfo{com.sec.android.app.snotebook/com.infraware.filemanager.FmFileTreeListActivity} tickerText null
04-15 16:49:28.305 D/IPPolicy(1879): updateImsNotification. ComponentName: ComponentInfo{com.sec.android.app.snotebook/com.infraware.filemanager.FmFileTreeListActivity} tickerText null
04-15 16:49:29.375 I/SNoteProvider(22675): checkSyncComplete
04-15 16:49:29.415 I/SNoteProvider(22675): checkSyncComplete
04-15 16:49:29.465 I/SNoteProvider(22675): checkSyncComplete
04-15 16:49:30.565 I/ActivityManager(876): Process com.sec.android.app.snotebook (pid 1522) (adj -12) has died.
04-15 16:49:33.130 D/SNoteWidgetProvider(22970): android.appwidget.action.APPWIDGET_UPDATE
04-15 16:49:33.130 E/SNoteDirectWidgetProvider(22970): android.appwidget.action.APPWIDGET_UPDATE
04-15 16:49:59.525 I/ActivityThread(25051): Pub com.infraware.provider.SNoteProvider: com.infraware.provider.SNoteProvider
04-15 16:49:59.560 I/SyncAdapter-SNote-Proxy(25038): onServiceConnected : Binded.
04-15 16:49:59.560 I/SNoteSyncAdapter(25038): PERFORM SYNC : 2.4.0
04-15 16:50:04.670 I/SNoteSyncAdapter(25038): PERFORM SYNC : START
04-15 16:50:07.195 I/SNoteSyncAdapter(25038): PERFORM SYNC : END
04-15 16:50:07.195 I/SNOTE-SYNC(25038): SYNC SERVICE END
04-15 16:50:21.430 D/IPPolicy(1879): updateImsNotification. ComponentName: ComponentInfo{com.sec.android.app.snotebook/com.infraware.filemanager.FmFileTreeListActivity} tickerText null
04-15 16:50:22.315 D/IPPolicy(1879): updateImsNotification. ComponentName: ComponentInfo{com.sec.android.app.snotebook/com.infraware.filemanager.FmFileTreeListActivity} tickerText null
04-15 16:50:22.570 W/ActivityManager(876): Process com.sec.android.app.snotebook has crashed too many times: killing!
04-15 16:50:31.300 D/IPPolicy(1879): updateImsNotification. ComponentName: ComponentInfo{com.sec.android.app.snotebook/com.infraware.filemanager.FmFileTreeListActivity} tickerText null
04-15 16:50:31.320 D/IPPolicy(1879): updateImsNotification. ComponentName: ComponentInfo{com.sec.android.app.snotebook/com.infraware.filemanager.FmFileTreeListActivity} tickerText null
04-15 16:50:32.320 D/IPPolicy(1879): updateImsNotification. ComponentName: ComponentInfo{com.sec.android.app.snotebook/com.infraware.filemanager.FmFileTreeListActivity} tickerText null
04-15 16:50:32.655 I/ActivityManager(876): Process com.sec.android.app.snotebook (pid 22970) (adj -12) has died.
04-15 16:50:33.320 D/IPPolicy(1879): updateImsNotification. ComponentName: ComponentInfo{com.sec.android.app.snotebook/com.infraware.filemanager.FmFileTreeListActivity} tickerText null
04-15 16:51:40.335 D/IPPolicy(1879): updateImsNotification. ComponentName: ComponentInfo{com.sec.android.app.snotebook/com.infraware.filemanager.FmFileTreeListActivity} tickerText null
04-15 16:51:49.090 D/IPPolicy(1879): updateImsNotification. ComponentName: ComponentInfo{com.sec.android.app.snotebook/com.infraware.filemanager.FmFileTreeListActivity} tickerText null
04-15 16:51:49.145 D/IPPolicy(1879): updateImsNotification. ComponentName: ComponentInfo{com.sec.android.app.snotebook/com.infraware.filemanager.FmFileTreeListActivity} tickerText null
04-15 16:51:50.135 D/IPPolicy(1879): updateImsNotification. ComponentName: ComponentInfo{com.sec.android.app.snotebook/com.infraware.filemanager.FmFileTreeListActivity} tickerText null
04-15 16:51:50.410 I/ActivityManager(876): Process com.sec.android.app.snotebook (pid 26421) (adj -12) has died.
I'm thinking of simply reinstalling the app....
Does anyone have the original apk(s).
Anyone?
anderroid said:
Anyone?
Click to expand...
Click to collapse
Try this. Clear data and cache again. Then use a file Explorer to navigate to your internal SD card and delete the entire snote folder. Obviously save a copy of the folder to your computer or externalsd of you have notes you want to keep before deleting.
Then reboot and see if it will open then.
Sent from my SGH-T889 using xda app-developers app
kintwofan said:
Try this. Clear data and cache again. Then use a file Explorer to navigate to your internal SD card and delete the entire snote folder. Obviously save a copy of the folder to your computer or externalsd of you have notes you want to keep before deleting.
Then reboot and see if it will open then.
Sent from my SGH-T889 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the advice, but no luck. Still crashes on open.
anderroid said:
Thanks for the advice, but no luck. Still crashes on open.
Click to expand...
Click to collapse
Crazy, are you in a stock ROM? As a last resort I say factory reset. While you're at it you may as well look into a custom ROM
Sent from my SGH-T889 using xda app-developers app
kintwofan said:
Crazy, are you in a stock ROM? As a last resort I say factory reset. While you're at it you may as well look into a custom ROM
Sent from my SGH-T889 using xda app-developers app
Click to expand...
Click to collapse
Yeah, it is Stock rom. I was hoping someone could link/post the Snote APK for installation...
I'm having the SAME issue, main reason I went on the board today was for this haha.
I've done all the same steps, no luck.
what kind of update have u done except for root?
Sent from my GT-N7108 using xda app-developers app
I just flashed a few apps/roms from S4 apps thread, S voice, etc. Nothing worked and I have deleted them all.
I have your key to s-note working again cause i had the same problem
Hey are you still having this problem. Its hard to ask in the rom threads also cause people just don't understand what we are saying. I had this same exact problem 2 months ago. You can even go through my posts under my screen name and see how frustrated i was getting with people trying to tell me there was no problem that existed like this. With me though, i had clockwork recovery mod installed, and s-note would always work, but anytime i would fix permissions besides after the first time installing any rom, even a stock rooted rom, it would say unfortunately s-note is not responding. Id click on it, it would hang, then slowly turn to a black screen they say exactly what you said it would. What i had to do, with help from another user, was download the latest version of odin, and do the whole rooting process all over again, once i did that s-note worked perfectly, and when i'd fix permissions, it would work still, unlike before. What happened is we came to find out some files ended up not flashing right when i 1st rooted my phone. I used the method on the page that was called something simply like, galaxy note 2 root, and the version of odin would always say not responding, yet still root my phone. So, yeah, if you'd like go through my thread to see that i had the same exact problem you did before doing what i tell tell you feel free . But heres what i had to do. Uninstall the version of Samsung galaxy drivers you have on your pc, then reboot, install the latest samsung galaxy drivers then reboot again, also, get the latest version of odin, just one sec i'll look to see what version it is that i have,.. Ok, the version is odin3 v1.85, if you already have that then great, unroot, then reroot your phone again with that version, i guarantee this will work for you. Sorry for the huge post i just know how much this pissed me off when it happened to me cause it went on for almost 2 months with everyone telling me i had a problem and getting pissed at me like it was my fault or something telling me to move on to another rom and everything else rude people would say under the sun. I really hope i helped you out here, cause i know i was happy as h e double hockey sticks when i re rooted and my s-note worked and worked also after fixing permissions. Not saying im happy but im glad to see someone else had the same problem as me at some point cause everyone tried just telling me i was stupid and im very smart at what i do one here.
Hey, so unrooted, rerooted and now everything is back to normal!
Thanks for the help!
No prob.
Sent from my SGH-T889 using xda premium
hi, I'm having the same problem except I'm not rooted. started after my phone [H3 UK] OTA update to support LTE which is new to my network. any suggestions? tried a recovery cache wipe, factory reset [such a hassle] and also deleteing the info from app manager. will try delete from internal sd.. aaaand no luck
Hi ,
same problem here after the 4.3 jellybean update. S Note crashes. stock rom ...not rooted
It happened to me, what I did was pulled out the spen, s note auto popped up, and I expand the snote, write something and saved.
After that I don't see the error when I manually open up the snote app.
Hope this help.
David
Related
Hi,
I'm trying to root my wife's Desire as she's constantly running low on space despite having very few apps and moving the apps to sdcard whenever possible. I thought I'd root and then get rid of all the bloatware with Titanium backup, but while I'm at it, I thought perhaps I should look at a custom ROM. What are some of the best choices that fit these criteria?
- Sense based, looks like a stock Desire
- Stable and fast
- Lean, no bloatware, lots of free space to install apps
- Gingerbread is nice but not necessary
Thanks!
goister said:
Hi,
I'm trying to root my wife's Desire as she's constantly running low on space despite having very few apps and moving the apps to sdcard whenever possible. I thought I'd root and then get rid of all the bloatware with Titanium backup, but while I'm at it, I thought perhaps I should look at a custom ROM. What are some of the best choices that fit these criteria?
- Sense based, looks like a stock Desire
- Stable and fast
- Lean, no bloatware, lots of free space to install apps
- Gingerbread is nice but not necessary
Thanks!
Click to expand...
Click to collapse
If you want it to be as stocklike as possible, you can try the rooted stock roms. If you want Sense 2.1 you can try some of the AceS/SagaS based roms like LeeDroid HD v3.3.3. Finally, if you want Sense 3.0 you can try Cool3D AceS http://forum.xda-developers.com/showthread.php?t=1040121. All of them are smooth and stable and you can remove bloatware if the Rom developer did not remove enough bloatware. Also, if you want more space, you can get roms with A2SD+, Data2EXT, or change your Hboot. In the end, it comes down to your preference. But be warned that some of these roms require at least 1 EXT partition on your sdcard.
Sent from my HTC Original Desire using Tapatalk
goister said:
Hi,
I'm trying to root my wife's Desire as she's constantly running low on space despite having very few apps and moving the apps to sdcard whenever possible. I thought I'd root and then get rid of all the bloatware with Titanium backup, but while I'm at it, I thought perhaps I should look at a custom ROM. What are some of the best choices that fit these criteria?
- Sense based, looks like a stock Desire
- Stable and fast
- Lean, no bloatware, lots of free space to install apps
- Gingerbread is nice but not necessary
Thanks!
Click to expand...
Click to collapse
There are plenty of roms out there, but i recommend supernova.
http://forum.xda-developers.com/showthread.php?t=1045824
all you have to do is install an ext4 partition on your sd card. and away you go. it's fast bloatware free and is the same as the desire in every way without the lagyness and bugs of the sense 2.5's or 3's. and you don't have to mess around with hboots.
But the AOSP's are also very good. Try out redux, oxygen, cm7 or gingervillain. you'll be surprised.
I think many good ROM are out there, just try flash couple of them and see which fit you. For SENSE obviously you need ext4 and a good hboot, recommend CM7r2, compatible with many
I tried and ended up with AURORA v3 http://forum.xda-developers.com/showthread.php?t=1268279, so far smoothest for SENSE 3.0 ROM
Remember to update other part of your phone i.e. kernel, radio as well so that you wont run into any bug.
ikidntu said:
I think many good ROM are out there, just try flash couple of them and see which fit you. For SENSE obviously you need ext4 and a good hboot, recommend CM7r2, compatible with many
I tried and ended up with AURORA v3 http://forum.xda-developers.com/showthread.php?t=1268279, so far smoothest for SENSE 3.0 ROM
Remember to update other part of your phone i.e. kernel, radio as well so that you wont run into any bug.
Click to expand...
Click to collapse
Further to this, the ROM MUST state it is compatible with CM7 hboot, otherwise it will not fit.
OK, she actually wants something radically different, haha. Any recommendations there? The rest of the requirements(stable/fast/lotsa space) still stand.
MIUI is completely different from stock.
Sent from my HTC Desire using XDA App
Try miui if you want an iPhoneish like style of launcher. Oxygen or cyanogenmod are aosp roms which is also a great option.
Sent from my HTC Original Desire using Tapatalk
Will check Oxygen out. Showed her MIUI and she doesn't like it coz it's too iphone-ish. She liked Cyanogenmod though. How are all of these choices in terms of speed, stability, and amount of memory left for apps?
goister said:
Will check Oxygen out. Showed her MIUI and she doesn't like it coz it's too iphone-ish. She liked Cyanogenmod though. How are all of these choices in terms of speed, stability, and amount of memory left for apps?
Click to expand...
Click to collapse
Both oxygen and cyanogen, being aosp roms are fast and very stable. As for the amount of memory left, it depends on whether you use A2SD+ or change into another hboot that fits them perfectly like the CM7r2 hBOOT for cyanogen and the Oxygen hBOOT for Oxygen roms.
Sent from my HTC Original Desire using Tapatalk
Thanks. I'm quite unfamiliar with a2sd and a2sd+. AFAIK a2sd+ allows more stuff, such as the dalvik cache, to be moved to the sdcard, in expense of speed (should the sdcard card not be as fast as internal flash memory). May I know what other pros and cons I should be aware of?
Currently I've rooted and obtained s-off as per this guide. I've done up to step 4. Step 5 explains how to use gparted to repartition my sdcard, and step 6 explains how to do a nandroid backup. Is it really necessary to repartition my existing sdcard? Is this required for a2sd/a2sd+? If so, is the process destructive, i.e. will I lose all data on the sdcard?
I ask because this step isn't mentioned in the Cyanogenmod v7 thread. It just says root/install cwm recovery, do a nandroid backup, wipe, and install the ROM.
Thanks.
Best thing to do so as to not lose all the stuff on your sd card is simply to copy the sd card onto your pc first, then run the GParted partitioning to create a first partition of fat32, then a (recommended) 1gb second partition of ext4. Then you can simply copy the stuff back onto your sd card (or just your pics/documents etc).
Nandroid backup before trying to flash a new ROM is a MUST I would say, just in case something goes wrong with the flash you can simply restore the nandroid and it'll restore your phone to the exact way it was when you made the backup (text messages, settings and all).
If you want the phone to look a bit different I'd suggest using a launcher (downloadable from the market). There are a few to choose from. "Go Launcher Ex" is a good one, which has loads of options to customize the look and feel of the phone (I personally use this one). But there are others that can completely change the look of the phone ("Launcher7" looks interesting as it makes the phone look like a WM7 phone). Experiment and see what you like.
Personally I'd recommend "Redux2" (don't worry about its test status, it's one of the most stable aosp ROM's on here), and GingerVillain (I'm using this now).
Being aosp ROM's they both leave you loads of room for apps, but if it starts to get low you can move the dalvik cache to the sd card freeing you up a load more space (how to do this is included on the op of their threads).
Or flash a different HBoot like another poster said. Easy enough to do using "Android Flasher" (found here on XDA). Changing to a HBoot like CM7r2 will give you a different amount of app data space.
I've never noticed a drop in speed when I've moved my dalvik cache to my sd card when I was using an 8gb class4 card (or now when I'm using a 16gb class10 card).
Rules to remember before flashing anything...
1) Check the op of the ROM you want to flash to make sure it is compatible with your setup (HBoot etc)
2) Nandroid (just in case)
3) Wipe,wipe,wipe
4)Flash
If you get stuck just post any issues or problems and the guys on here will help.
Thanks. I've downloaded the Cyanogenmod v7 ROM, and I've done the gparted. When the phone detected the sdcard though, I lost many of my apps, including Google Maps, and I'm now lower than ever on space. Even after copying back my backed up sdcard contents, those apps were still missing - weird.
Does Cyanogenmod come with A2SD+ to move system stuff to my sdcard?
goister said:
Thanks. I've downloaded the Cyanogenmod v7 ROM, and I've done the gparted. When the phone detected the sdcard though, I lost many of my apps, including Google Maps, and I'm now lower than ever on space. Even after copying back my backed up sdcard contents, those apps were still missing - weird.
Does Cyanogenmod come with A2SD+ to move system stuff to my sdcard?
Click to expand...
Click to collapse
Did you use Titanium Backup? It's the best way to keep all of your apps safe when switching between ROM's.
goister said:
Thanks. I've downloaded the Cyanogenmod v7 ROM, and I've done the gparted. When the phone detected the sdcard though, I lost many of my apps, including Google Maps, and I'm now lower than ever on space. Even after copying back my backed up sdcard contents, those apps were still missing - weird.
Does Cyanogenmod come with A2SD+ to move system stuff to my sdcard?
Click to expand...
Click to collapse
Hmm... Cyanogenmod shouldn't move your system apps to the sdcard, it has no reason to do that as the system apps can be fitted perfectly on the system partition. Try doing a full wipe and flash again.
Sent from my HTC Original Desire using Tapatalk
I haven't installed Cyanogenmod v7 yet. I'm assuming flashing the Cyanogenmod ROM will, it will come with all the normal Google apps?
Edit: Just read the Cyanogenmod thread that Google apps are not part of the ROM, and a separate Google addon should be installed if required. Can I find out if Cyanogenmod supports A2SD+? Is there a guide for flashing Cyanogenmod, Google addon and A2SD+?
Thanks.
goister said:
I haven't installed Cyanogenmod v7 yet. I'm assuming flashing the Cyanogenmod ROM will, it will come with all the normal Google apps?
Edit: Just read the Cyanogenmod thread that Google apps are not part of the ROM, and a separate Google addon should be installed if required. Can I find out if Cyanogenmod supports A2SD+? Is there a guide for flashing Cyanogenmod, Google addon and A2SD+?
Thanks.
Click to expand...
Click to collapse
If I'm not wrong cm7 comes with a2sd+ but I'm not sure if its enabled by default or not. To flash cyanogenmod follow step 7 here. http://forum.xda-developers.com/showthread.php?t=1016084. To flash Google Apps just click choose zip from sdcard from the recovery after flashing cm7, go to the Google Apps zip file and click it, then click yes.
Sent from my HTC Original Desire using Tapatalk
OK, thanks. I've successfully installed Cyanogenmod v7, but when I try to install the Google apps via "install from zip file", after rebooting it keeps hanging at the " Why So Serious" boot up screen. adb logcat shows the following output over and over again:
Code:
D/AndroidRuntime( 326):
D/AndroidRuntime( 326): >>>>>> AndroidRuntime START com.android.internal.os.Zyg
oteInit <<<<<<
I/AndroidRuntime( 326): Heap size: -Xmx32m
D/AndroidRuntime( 326): CheckJNI is OFF
D/dalvikvm( 326): creating instr width table
W/dalvikvm( 326): ERROR: Unable to find decl for native Landroid/os/BinderProxy
;.pingBinder:()Z
E/JNIHelp ( 326): RegisterNatives failed for 'android/os/BinderProxy'
E/AndroidRuntime( 326): Unable to register all android natives
I/ServiceManager( 127): service 'media.audio_flinger' died
I/ServiceManager( 127): service 'media.player' died
I/ServiceManager( 127): service 'media.camera' died
I/ServiceManager( 127): service 'media.audio_policy' died
I/Netd ( 328): Netd 1.0 starting
I/ ( 327): ServiceManager: 0xad50
E/AudioHardwareQSD( 327): Cannot open /dev/audience_a1026 -1
I/HTC Acoustic( 327): libhtc_acoustic.so version 2.0.1.5
E/HTC Acoustic( 327): Fail to open /system/etc/AdieHWCodecSetting.csv -1.
E/HTC Acoustic( 327): read ADIE para from file failed -1
E/HTC Acoustic( 327): ioctl ACOUSTIC_UPDATE_ADIE failed -1
I/HTC Acoustic( 327): open /system/etc/AudioBTID.csv success.
I/HTC Acoustic( 327): BT ID table version: PASSION_HTC_20091105
E/HTC Acoustic( 327): Fail to open /system/etc/TPA2018.csv -1.
D/AudioHardwareQSD( 327): speaker amplifier tpa2018 is not supported
D/AudioHardwareInterface( 327): setMode(NORMAL)
I/AudioHardwareQSD( 327): Set master volume to 1.000000
I/CameraService( 327): CameraService started (pid=327)
D/AudioFlinger( 327): setParameters(): io 1, keyvalue routing=2, tid 332, calli
ng tid 327
I/AudioFlinger( 327): AudioFlinger's thread 0xea80 ready to run
I/AudioHardwareQSD( 327): Routing audio to Speakerphone
D/AudioHardwareQSD( 327): Switching audio device to
D/AudioHardwareQSD( 327): Speakerphone
I/AudioHardwareQSD( 327): voice volume 5 (range is 0 to 5)
D/AudioHardwareQSD( 327): Setting in-call volume to 100
Anyone knows what's wrong? I've rewiped and reflashed Cyanogenmod v7 and it boots up correctly now. Should I try flashing the Google Apps zip again?
Thanks.
goister said:
OK, thanks. I've successfully installed Cyanogenmod v7, but when I try to install the Google apps via "install from zip file", after rebooting it keeps hanging at the " Why So Serious" boot up screen. adb logcat shows the following output over and over again:
Code:
D/AndroidRuntime( 326):
D/AndroidRuntime( 326): >>>>>> AndroidRuntime START com.android.internal.os.Zyg
oteInit <<<<<<
I/AndroidRuntime( 326): Heap size: -Xmx32m
D/AndroidRuntime( 326): CheckJNI is OFF
D/dalvikvm( 326): creating instr width table
W/dalvikvm( 326): ERROR: Unable to find decl for native Landroid/os/BinderProxy
;.pingBinder:()Z
E/JNIHelp ( 326): RegisterNatives failed for 'android/os/BinderProxy'
E/AndroidRuntime( 326): Unable to register all android natives
I/ServiceManager( 127): service 'media.audio_flinger' died
I/ServiceManager( 127): service 'media.player' died
I/ServiceManager( 127): service 'media.camera' died
I/ServiceManager( 127): service 'media.audio_policy' died
I/Netd ( 328): Netd 1.0 starting
I/ ( 327): ServiceManager: 0xad50
E/AudioHardwareQSD( 327): Cannot open /dev/audience_a1026 -1
I/HTC Acoustic( 327): libhtc_acoustic.so version 2.0.1.5
E/HTC Acoustic( 327): Fail to open /system/etc/AdieHWCodecSetting.csv -1.
E/HTC Acoustic( 327): read ADIE para from file failed -1
E/HTC Acoustic( 327): ioctl ACOUSTIC_UPDATE_ADIE failed -1
I/HTC Acoustic( 327): open /system/etc/AudioBTID.csv success.
I/HTC Acoustic( 327): BT ID table version: PASSION_HTC_20091105
E/HTC Acoustic( 327): Fail to open /system/etc/TPA2018.csv -1.
D/AudioHardwareQSD( 327): speaker amplifier tpa2018 is not supported
D/AudioHardwareInterface( 327): setMode(NORMAL)
I/AudioHardwareQSD( 327): Set master volume to 1.000000
I/CameraService( 327): CameraService started (pid=327)
D/AudioFlinger( 327): setParameters(): io 1, keyvalue routing=2, tid 332, calli
ng tid 327
I/AudioFlinger( 327): AudioFlinger's thread 0xea80 ready to run
I/AudioHardwareQSD( 327): Routing audio to Speakerphone
D/AudioHardwareQSD( 327): Switching audio device to
D/AudioHardwareQSD( 327): Speakerphone
I/AudioHardwareQSD( 327): voice volume 5 (range is 0 to 5)
D/AudioHardwareQSD( 327): Setting in-call volume to 100
Anyone knows what's wrong? I've rewiped and reflashed Cyanogenmod v7 and it boots up correctly now. Should I try flashing the Google Apps zip again?
Thanks.
Click to expand...
Click to collapse
Did u first let your phone boot once before installing the google apps?
Greetz
Sent from my HTC Desire runnin Cool VisionS v1.2
Edit: yes you should flash it again
Sent from my HTC Desire runnin Cool VisionS v1.2
Everytime I try to purchase an app or song or book from the market I get "An error has occurred. Please try again." Its been happening since about October. I've tried clearing the cache on the market, I tried factory resetting, I even tried wiping everything (sd and emmc included.) The log mentions something about mismatched uids.
HTML:
12-11 10:28:01.601 I/ActivityManager( 461): Starting activity: Intent { flg=0x20010000 cmp=com.android.vending/com.google.android.finsky.activities.PurchaseDialog (has extras) } from pid 1242
12-11 10:28:01.701 D/Finsky ( 1242): [1] SelfUpdateScheduler.checkForSelfUpdate: Skipping self-update. Local Version [8009011] >= Server Version [0]
12-11 10:28:01.741 I/ActivityManager( 461): Displayed com.android.vending/com.google.android.finsky.activities.PurchaseDialog: +123ms
12-11 10:28:01.831 D/Finsky ( 1242): [1] PageFragment.rebindViews: Page [class=PurchaseFragment] loaded in [89 ms]
12-11 10:28:01.841 E/Finsky ( 1242): [1] AppPermissionAdapter.<init>: Invalid group name:null
12-11 10:28:01.871 W/Finsky ( 1242): [1] CarrierParamsAction.run: Saving carrier billing params failed.
12-11 10:28:01.881 D/Finsky ( 1242): [1] CarrierProvisioningAction.shouldFetchProvisioning: Required CarrierBillingParams missing. Shouldn't fetch provisioning.
12-11 10:28:01.881 D/Finsky ( 1242): [1] CarrierProvisioningAction.run: No need to fetch provisioning from carrier.
12-11 10:28:01.881 D/Finsky ( 1242): [1] GetBillingCountriesAction.run: Skip getting fresh list of billing countries.
12-11 10:28:01.881 W/AccountManagerService( 461): caller uid 10051 is different than the authenticator's uid
12-11 10:28:01.881 E/Finsky ( 1242): [57] 1.run: Caught SecurityException: caller uid 10051 is different than the authenticator's uid
12-11 10:28:01.901 D/Finsky ( 1242): [1] CheckoutPurchase.onErrorReceived: Could not retrieve Checkout auth token: caller uid 10051 is different than the authenticator's uid
12-11 10:28:01.901 E/Finsky ( 1242): [1] CheckoutPurchase.setError: type=UNKNOWN, code=-1, message=An error occurred. Please try again.
Reposted to QandA, sorry for the mix up. Mods feel free to delete.
I was getting the authentication error and wouldn't log me in....I reflashed Gapps and I could get into Market again but when I try to download or update an app, it just sits there and says, "downloading......"
But my buddy who is on Sprint is able to download apps just fine.
Have you tried contacting Google via email. It might be on their end.
Sent from my ADR6300 Incredible
I believe this can be fix like so:
Go to: settings/applications/manage applications/running app./tap:download manager,then tap clear data,and force to stop,after that go back to home,restart your phone,also clear cache/data on market,I hope this will fix your problem...let me know.
Sent from my PC36100 using XDA App
Thanks for the suggestion, but I am still having the problem. I'll just use the web interface for now.
I just downloaded the MarketFix app from the Android Market. It moves the market cache to the SD card. Problem solved...give it a shot.
I had that same problem when the credit card information for Google Wallet had to be updated.
Try entering or updating your Wallet info online via your computer.
Sent from my NookColor
gadzooks64 said:
I had that same problem when the credit card information for Google Wallet had to be updated.
Try entering or updating your Wallet info online via your computer.
Sent from my NookColor
Click to expand...
Click to collapse
Thanks for the tip, but still a no go.
wrong thread, sorry
I'm having the same exact problem as the OP, anyone know of any other possible solution or tricks?
By the way I have a different device than OP, mine is a cheap chinese tablet called teclast p75.
android market place error
unfortunately i also have the issue with the android market place on my kindle fire. i installed the market place, google wallet is actual, but i am even not able to download free apps. after accepting and clicking on "download" i always get the message
"appname" could not be downloaded due to an error. does anybody have an idea? I am really lost.
have you been updated to the 3.4.7 version of the market yet? that's to anyonehaving this issue
I got same proplem. i'v update market, clear cache, clear everything and stil can't buy anythings from google play
so?
I am having this problem now. on og droid steel droid rom.
I had a similar problem once on my kindle and eventually what i wound up doing was going into recovery and flashing the ROM from scratch like it was brand new. Wipe System/Data/DataData/Cache/Dalvik/anything else you like to wipe and reflash the ROM (and the newest applicable gapps) and see if that helps. It did the trick for me, it is an odd error and I feel like the easiest thing is to start from the beginning when something like that happens and hope that you don't run into it again.
EDIT: of course make a nandroid first, in case it doesn't work
I had the mismatced UIDs issue when I installed a stock 2.3.4 Rom. It alerted me on the first boot up, then never alerted me again. I had to install a different Rom because many features didn't work. Hope this helps!
I did try reflashing the stock ROM (provided by the producer) without success, still having the same problem.
You mention reflashing the gapps, would that only work if you got the Cynogenmod installed or will they work with any ROM?
I did try reflashing the stock ROM (provided by the producer) without success, still having the same problem.
You mention reflashing the gapps, would that only work if you got the Cynogenmod installed or will they work with any ROM?
Click to expand...
Click to collapse
Were you able to root/flash this through recovery? With stock ROMs the GAPPS are typically included (unless the company making the tablet wishes to use a different market so they don't have to pay royalties to google).
Yes it does ship with gapps but the user mentioned re-installing them (maybe even upgrading). I wondered that if you can find different gapps it could make it work but I don't know how you would go about it. The gapps for Cynogen are in a zip that has to be installed using Cynogen recovery console, not sure how to install them manually.
kulhat said:
Yes it does ship with gapps but the user mentioned re-installing them (maybe even upgrading). I wondered that if you can find different gapps it could make it work but I don't know how you would go about it. The gapps for Cynogen are in a zip that has to be installed using Cynogen recovery console, not sure how to install them manually.
Click to expand...
Click to collapse
If you want to install a newer market you can do it as long as you're rooted. That being said, so long as you're not on an ancient device (maybe you're that lucky with the chinese tablet) it is supposed to update automatically. At any rate, if you have SU then you just need to drop the vending.apk into /system/app and give it the following permissions:
[X][X][ ]
[X][ ][ ]
[X][ ][ ]
EDIT: You might only need marketupdater.apk things have changed since they changed the market to googleplay so I am not as familiar with it as I used to be when I originally rooted/ added the market to my Kindle Fire
All I do anymore to get gapps is flash the gapps.zip through recovery but I don't know a whole lot about your chinese tablet so I can't really give input on its recovery setup haha
i just bought a used Galaxy nexus Gsm. but every time it boots this error comes up "Unfortunately, the process com.android.phone has stopped"
when i press ok it goes away and phone seems to work fine.
i have tried flashing the stock rom thorough ODIN and also tried couple of custom Roms but the error still persists. i'll be grateful if someone could help me out. cheers
coolshan said:
i just bought a used Galaxy nexus Gsm. but every time it boots this error comes up "Unfortunately, the process com.android.phone has stopped"
when i press ok it goes away and phone seems to work fine.
i have tried flashing the stock rom thorough ODIN and also tried couple of custom Roms but the error still persists. i'll be grateful if someone could help me out. cheers
Click to expand...
Click to collapse
Flash the factory images available on Google's servers using this guide: http://forum.xda-developers.com/showthread.php?t=1626895. Don't use Odin unless you have to, fastboot is the preferred method for flashing a Nexus.
If that doesn't help, post a logcat (use adb to get it). We can try finding the cause with that.
Petrovski80 said:
Flash the factory images available on Google's servers using this guide: http://forum.xda-developers.com/showthread.php?t=1626895. Don't use Odin unless you have to, fastboot is the preferred method for flashing a Nexus.
If that doesn't help, post a logcat (use adb to get it). We can try finding the cause with that.
Click to expand...
Click to collapse
how to get the logcat ? can you tell me the procedure? i have adb and all the drivers installed already
coolshan said:
how to get the logcat ? can you tell me the procedure? i have adb and all the drivers installed already
Click to expand...
Click to collapse
- enable usb debugging via developer options
- reboot phone
- wait for error to display
- connect phone via USB to computer
- open a command prompt where the adb executable is located
- type: abd logcat > c:\MyLogcat\logcat.txt
Petrovski80 said:
Flash the factory images available on Google's servers using this guide: http://forum.xda-developers.com/showthread.php?t=1626895. Don't use Odin unless you have to, fastboot is the preferred method for flashing a Nexus.
If that doesn't help, post a logcat (use adb to get it). We can try finding the cause with that.
Click to expand...
Click to collapse
Petrovski80 said:
- enable usb debugging via developer options
- reboot phone
- wait for error to display
- connect phone via USB to computer
- open a command prompt where the adb executable is located
- type: abd logcat > c:\MyLogcat\logcat.txt
Click to expand...
Click to collapse
i have attached the logcat.txt file. have a look at it. i personally dont understand a thing lol
coolshan said:
i have attached the logcat.txt file. have a look at it. i personally dont understand a thing lol
Click to expand...
Click to collapse
Looking through your logcat, I see several exceptions, one of them concerns the RIL (radio interface layer). I'm thinking this causes your error after each boot:
Code:
D/CAT ( 584): RilMessageDecoder: decodeMessageParams: caught ResultException e=result=CMD_DATA_NOT_UNDERSTOOD additionalInfo=-1 explantion=length < 0x80 length=0 curIndex=3 endIndex=113
W/dalvikvm( 584): threadid=1: thread exiting with uncaught exception (group=0x41a30300)
E/AndroidRuntime( 584): FATAL EXCEPTION: main
E/AndroidRuntime( 584): java.lang.NullPointerException
E/AndroidRuntime( 584): at com.android.internal.telephony.cat.CatService.handleRilMsg(CatService.java:172)
E/AndroidRuntime( 584): at com.android.internal.telephony.cat.CatService.handleMessage(CatService.java:619)
E/AndroidRuntime( 584): at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime( 584): at android.os.Looper.loop(Looper.java:137)
E/AndroidRuntime( 584): at android.app.ActivityThread.main(ActivityThread.java:4896)
E/AndroidRuntime( 584): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime( 584): at java.lang.reflect.Method.invoke(Method.java:511)
E/AndroidRuntime( 584): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:791)
E/AndroidRuntime( 584): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:558)
E/AndroidRuntime( 584): at dalvik.system.NativeStart.main(Native Method)
However, I have no idea what causes the exception. I would try flashing the appropriate RIL for you device, look here: http://forum.xda-developers.com/showpost.php?p=27441945
As for the rest of your logcat, the following apps cause exceptions as well:
- geniewidget: file not found exception. Probably nothing to worry about if it's working OK.
- SuperSU: java IO exception when executing /system/.bash/.ssu, -v. Not sure what's going on there, are SuperSU and its su binary up to date? Worth checking out imho.
- Go SMS sinaweibo plugin: illegal argument exception. Again, if this is working OK don't worry about it.
- Plume: arrayindex out of bounds exception. If this is working OK don't worry about it.
Petrovski80 said:
Looking through your logcat, I see several exceptions, one of them concerns the RIL (radio interface layer). I'm thinking this causes your error after each boot:
Code:
D/CAT ( 584): RilMessageDecoder: decodeMessageParams: caught ResultException e=result=CMD_DATA_NOT_UNDERSTOOD additionalInfo=-1 explantion=length < 0x80 length=0 curIndex=3 endIndex=113
W/dalvikvm( 584): threadid=1: thread exiting with uncaught exception (group=0x41a30300)
E/AndroidRuntime( 584): FATAL EXCEPTION: main
E/AndroidRuntime( 584): java.lang.NullPointerException
E/AndroidRuntime( 584): at com.android.internal.telephony.cat.CatService.handleRilMsg(CatService.java:172)
E/AndroidRuntime( 584): at com.android.internal.telephony.cat.CatService.handleMessage(CatService.java:619)
E/AndroidRuntime( 584): at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime( 584): at android.os.Looper.loop(Looper.java:137)
E/AndroidRuntime( 584): at android.app.ActivityThread.main(ActivityThread.java:4896)
E/AndroidRuntime( 584): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime( 584): at java.lang.reflect.Method.invoke(Method.java:511)
E/AndroidRuntime( 584): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:791)
E/AndroidRuntime( 584): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:558)
E/AndroidRuntime( 584): at dalvik.system.NativeStart.main(Native Method)
However, I have no idea what causes the exception. I would try flashing the appropriate RIL for you device, look here: http://forum.xda-developers.com/showpost.php?p=27441945
As for the rest of your logcat, the following apps cause exceptions as well:
- geniewidget: file not found exception. Probably nothing to worry about if it's working OK.
- SuperSU: java IO exception when executing /system/.bash/.ssu, -v. Not sure what's going on there, are SuperSU and its su binary up to date? Worth checking out imho.
- Go SMS sinaweibo plugin: illegal argument exception. Again, if this is working OK don't worry about it.
- Plume: arrayindex out of bounds exception. If this is working OK don't worry about it.
Click to expand...
Click to collapse
its not working... i flashed the RIL with GETRIL app. and it says it a matching one. i even tried an other one for JB but in vain. its really irritating me now.. what is the problem :/
coolshan said:
its not working... i flashed the RIL with GETRIL app. and it says it a matching one. i even tried an other one for JB but in vain. its really irritating me now.. what is the problem :/
Click to expand...
Click to collapse
Have you tried going completely back to stock using this guide: http://forum.xda-developers.com/showthread.php?t=1626895
Petrovski80 said:
Have you tried going completely back to stock using this guide: http://forum.xda-developers.com/showthread.php?t=1626895
Click to expand...
Click to collapse
i did. i even flashed other radios but nothing seems to work. could you tell me what is the purpose of this process ? "com.android.phone"
coolshan said:
i did. i even flashed other radios but nothing seems to work. could you tell me what is the purpose of this process ? "com.android.phone"
Click to expand...
Click to collapse
That's the phone app in /system/app.
I'm beginning to think your problem might be related to hardware. I'm out of suggestions I'm afraid.
Sent from my Galaxy Nexus using Tapatalk 2
Petrovski80 said:
That's the phone app in /system/app.
I'm beginning to think your problem might be related to hardware. I'm out of suggestions I'm afraid.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
yeah me too.. thanks for the help though. but still i dont understand why is they phone functioning properly? what disfunction this process can cause ? it seems to make and receive calls and sms without any probelm
Petrovski80 said:
That's the phone app in /system/app.
I'm beginning to think your problem might be related to hardware. I'm out of suggestions I'm afraid.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
i found the problem !! its neither software nor hardware infact its my sim card thats causing it. changed the sim card and it booted normally my sim card is quite old so may be that could be a reason. but its a relief.. thanks man u really helped me out alot. learned alot from you. :good:
coolshan said:
i found the problem !! its neither software nor hardware infact its my sim card thats causing it. changed the sim card and it booted normally my sim card is quite old so may be that could be a reason. but its a relief.. thanks man u really helped me out alot. learned alot from you. :good:
Click to expand...
Click to collapse
Great you fixed it. Thanks for posting the solution here.
Sent from my Galaxy Nexus using Tapatalk 2
Hello. I've searched the forums and looked at guides and people with similar problems previously.
I've soft bricked my phone, stuck at:
Secure booting Error!
Cause : boot certification verify.
I rooted it using the E980 universal rooting tool from giantpune from ballshanglow's post. I then unlocked it using FreeGee 1.10, installed TWRP 2.6.1.0.
Upon reboot, the phone was stuck with the above error. I have downloaded the relevant .kdz for my phone, installed the USB drivers and the LG flashing tool. I have uninstalled and reinstalled the drivers (trying out different versions) and also tried various versions of the LG flashing tool (KDZ_FW_UPD_EN & FlashTool.1.0.54). I have also tried to use LG's provided software to recover my phone.
The furthest I've been able to go in the recovery/stock-firmware-flashing process, is the device check. Despite have 99%+ battery according to TWRP, I still get the error that my phone (in download mode) has low battery. Other times, the flashing tool freezes up and becomes not-responding after I get an extract error, or after I click 'Reading phone information'.
I've tried everything I could find. I've also attempted to flash a custom rom, but I get:
Assert failed: getpropr("ro.product.device") == "geefhd_att_us" ||
getprop("ro.build.product") == "geefhd_att_us"
E:Error executing updater binary in zip.
I'M F***ING STUCK. I'VE TRIED POSITIVELY EVERYTHING I COULD FIND.
Is there anything you guys can suggest I try before I send it to LG to have it returned to stock?
Thank you very much, and sorry I'm a noob. I tried.
My phone's model name is E988, firmware version E98810A_00
BauhausPen said:
My phone's model name is E988, firmware version E98810A_00
Click to expand...
Click to collapse
I experienced exactly the same with my E986::crying: bootloader unlock+installing CWM recovery with "freeGee".
It seems their bootloader unlock is not good.
Flahing with r&D tool is interrupted with this "low battery" message.
help!
xifizurk said:
I experienced exactly the same with my E986::crying: bootloader unlock+installing CWM recovery with "freeGee".
It seems their bootloader unlock is not good.
Flahing with r&D tool is interrupted with this "low battery" message.
help!
Click to expand...
Click to collapse
Dude. I fixed it. Apparently, I just didn't leave my phone to be connected to the computer long enough before beginning the recovery/restoration process. Connect your phone to your computer in download mode for 3 minutes and LEAVE IT.
You can check Printers and Devices to see if your computer has recognised your phone. That's all I can say.
GOOD LUCK.
still problem with "UpTestEX.exe" r&d test tool
still no luck for me.
In download mode the phone appears to be properly recognised by my win7 pc.
waited more than 3 minutes before proceeding
all the same the flashing process exits with the "unsufficient battery level" message.
here the last lines of the "R&D test tool"log before it exits:
23:53:50 : *****Get ESN / IMEI / MEID Start*****
23:53:50 : ESN/IMEI/MEID : xxxxxxxxxxxxxxx
23:53:53 : Check Backup and Restore model
23:53:53 : Phone type Compare start
23:53:53 : *****Start _GetBatteryLevel*****
23:53:53 : ******************************
23:53:53 : Battery(1)
23:53:53 : You can't continue the process due to lack of battery power.\nRecharge the phone battery fully and retry.
23:53:56 : ~~~~~~~~~~~~~~~~~~~~
23:53:56 : !pUpgrade->StartProcessing ... PostMsg STEP_TYPE_ENV_ERROR
23:53:56 : Page_Error ºÎºÐÀÔ´Ï´Ù
23:53:56 : OnStepMsg STEP_TYPE_ENV_ERROR delete m_pLGCyonUpdate
(being quite sure there is enough charge in the battery)
very thankful for any hints
xifizurk said:
still no luck for me.
In download mode the phone appears to be properly recognised by my win7 pc.
waited more than 3 minutes before proceeding
all the same the flashing process exits with the "unsufficient battery level" message.
here the last lines of the "R&D test tool"log before it exits:
23:53:50 : *****Get ESN / IMEI / MEID Start*****
23:53:50 : ESN/IMEI/MEID : xxxxxxxxxxxxxxx
23:53:53 : Check Backup and Restore model
23:53:53 : Phone type Compare start
23:53:53 : *****Start _GetBatteryLevel*****
23:53:53 : ******************************
23:53:53 : Battery(1)
23:53:53 : You can't continue the process due to lack of battery power.\nRecharge the phone battery fully and retry.
23:53:56 : ~~~~~~~~~~~~~~~~~~~~
23:53:56 : !pUpgrade->StartProcessing ... PostMsg STEP_TYPE_ENV_ERROR
23:53:56 : Page_Error ºÎºÐÀÔ´Ï´Ù
23:53:56 : OnStepMsg STEP_TYPE_ENV_ERROR delete m_pLGCyonUpdate
(being quite sure there is enough charge in the battery)
very thankful for any hints
Click to expand...
Click to collapse
If you run it on windows 7, just right click on "UpTestEX.exe", choose "properties", choose "Compatibility", on tab "Compatibility mode" tick "Run this Program in compatibility mode for" and choose " Windows 7", after that, Apply and Ok.
So the issue is gone.
Goodluck.
Sorry Guys,
(It was indeed a battery problem)
sorry this was a premature conclusion
but please take care with "uptest.exe"...
xifizurk said:
It was indeed a battery problem
Click to expand...
Click to collapse
tried again to flash the original .kdz with a running cyanogen mod 4.3 on the phone and with more than enough battery ...and i couldn't.
Again interrupted with the "low-battery" warning.
hm...
would be nice to have something easier and less tricky!
xifizurk said:
tried again to flash the original .kdz with a running cyanogen mod 4.3 on the phone and with more than enough battery ...and i couldn't.
Again interrupted with the "low-battery" warning.
hm...
would be nice to have something easier and less tricky!
Click to expand...
Click to collapse
If you are running Windows 7, right click on Up TestEX.exe in flash tool 1.0.5.4 folder, choose Properties, choose Compatibility, tick "Run this program in compatibility mode for" and choose "Windows 7", choose "Apply" and choose "OK".
After all, run "Up TestEX.exe" again, it doesn't ask about your battery.
Googluck.
Charge the phone all the way, then it'll work.
Sent from my LG-E980 using XDA Premium 4 mobile app
xifizurk said:
tried again to flash the original .kdz with a running cyanogen mod 4.3 on the phone and with more than enough battery ...and i couldn't.
Again interrupted with the "low-battery" warning.
hm...
would be nice to have something easier and less tricky!
Click to expand...
Click to collapse
Has anyone solved this problem?
I tried with Win XP,Win7,Win 8.1 on two different laptop,different usb port,as administrator,compatibility mode for Win7/battery is full. ..:crying:
The phone is E988 currently CM11 and TWRP, last month Flash Tool worked smoothly but now...?!?!?!?
Please help!?
23:30:49 : ******************************************
23:30:50 : [C:\Documents and Settings\All Users\Application Data\LGMOBILEAX\Phone] Try to delete folder
23:30:50 : SetEmerModeAT()
23:30:50 : _IsConnectedPhone Call
23:30:56 : _IsConnectedPhone(1)
23:30:56 : 0 - NotConnected.
23:30:56 : 1 - Normal connect success
23:30:56 : 2 - Emergency connect success
23:30:56 : *****CheckOS Start********
23:30:56 : Microsoft_Windows_XP_Professional_Service Pack 2
23:30:56 : *****CheckPCSyncPrograms Start*****
23:30:56 : PCSyncPrograms Not Found - OK and ready to upgrade
23:30:56 : Verifying phone connection...
23:30:56 : dwWaitResetTime(40000 ms)
23:30:57 : Phone Mode(1)
23:30:57 : *****GetPhoneType Start*****
23:30:57 : Phone Type : CDMA_2CHIP
23:30:57 : *****GetPhoneModel Start*****
23:30:57 : Phone read Model : LGE988AT
23:30:57 : Server param Model :
23:30:57 : *****GetPhoneBinaryVersion Start*****
23:30:57 : Phone Bin Version : E98810D_00
23:30:57 : *****Get ESN / IMEI / MEID Start*****
23:30:57 : ESN/IMEI/MEID : 357486050300391
23:30:59 : Check Backup and Restore model
23:30:59 : Phone type Compare start
23:30:59 : *****Start _GetBatteryLevel*****
23:30:59 : ******************************
23:30:59 : Battery(3)
23:30:59 : You can't continue the process due to lack of battery power.\nRecharge the phone battery fully and retry.
23:31:03 : ~~~~~~~~~~~~~~~~~~~~
23:31:03 : !pUpgrade->StartProcessing ... PostMsg STEP_TYPE_ENV_ERROR
23:31:03 : Page_Error ºÎºÐÀÔ´Ï´Ù
23:31:03 : OnStepMsg STEP_TYPE_ENV_ERROR delete m_pLGCyonUpdate
Someone please
Sent from my LG-E980 using xda app-developers app
lakir said:
Someone please
Sent from my LG-E980 using xda app-developers app
Click to expand...
Click to collapse
I don't know if this will be of any help to you or not... It might give you some ideas as to what to try:
http://forum.xda-developers.com/showthread.php?p=48246529#post48246529
how i solved the problem
lakir said:
Someone please
Sent from my LG-E980 using xda app-developers app
Click to expand...
Click to collapse
"uptest.exe" didn´t work with my device (E-986) after the bad "freegee" unlock.
Since I could finally access cwm-recovery from my soft broken phone and restored a E-988 stock-backup that I found while browsing this site, I didn´t need to flash anymore at that time.
Later with an unstable cyanogenmod on the phone it didn't work neither.
Only after restoring the mentionned stock-backup the flashing process was successful.
visionlogic said:
I don't know if this will be of any help to you or not... It might give you some ideas as to what to try:
http://forum.xda-developers.com/showthread.php?p=48246529#post48246529
Click to expand...
Click to collapse
I've tried everything in this post but failed. Thanks anyway!
It is possible that the problem with Fregee unlocking. Can I install PhilZ CWM, is it possible with CM 11?
I tried to install G2 V5 but still get the CWM boot loop. I can only CM11 with TWRP nothing else...
Sent from my LG-E980 using xda app-developers app
Problem solved!
Problem solved!
I installed PhilZ CVM
http://forum.xda-developers.com/showthread.php?t=2201860
then g2 v5
http://forum.xda-developers.com/showthread.php?t=2462453
and after that the process in this post
http://forum.xda-developers.com/showthread.php?t=2420219
Factory reset (volume down-home-power )
Root
http://forum.xda-developers.com/showthread.php?t=2362657
If anyone had the same problem now know what the solution was.
Thank you all for your responses and ideas!
lakir said:
Problem solved!
I installed PhilZ CVM
http://forum.xda-developers.com/showthread.php?t=2201860
then g2 v5
http://forum.xda-developers.com/showthread.php?t=2462453
and after that the process in this post
http://forum.xda-developers.com/showthread.php?t=2420219
Factory reset (volume down-home-power )
Root
http://forum.xda-developers.com/showthread.php?t=2362657
If anyone had the same problem now know what the solution was.
Thank you all for your responses and ideas!
Click to expand...
Click to collapse
when the phone is not able to boot at all how did u install cwm>?
lakir said:
Problem solved!
I installed PhilZ CVM
http://forum.xda-developers.com/showthread.php?t=2201860
then g2 v5
http://forum.xda-developers.com/showthread.php?t=2462453
and after that the process in this post
http://forum.xda-developers.com/showthread.php?t=2420219
Factory reset (volume down-home-power )
Root
http://forum.xda-developers.com/showthread.php?t=2362657
If anyone had the same problem now know what the solution was.
Thank you all for your responses and ideas!
Click to expand...
Click to collapse
manhktqd said:
If you are running Windows 7, right click on Up TestEX.exe in flash tool 1.0.5.4 folder, choose Properties, choose Compatibility, tick "Run this program in compatibility mode for" and choose "Windows 7", choose "Apply" and choose "OK".
After all, run "Up TestEX.exe" again, it doesn't ask about your battery.
Googluck.
Click to expand...
Click to collapse
Hey I used both your suggestions and it worked perfectly,
Thank you very much
anirudhks said:
when the phone is not able to boot at all how did u install cwm>?
Click to expand...
Click to collapse
Phone worked on CM11. when installed G2 V5 going to boot loop into CWM
Sent from my LG-E988 using xda app-developers app
---------- Post added at 07:09 PM ---------- Previous post was at 07:08 PM ----------
Cewar said:
Hey I used both your suggestions and it worked perfectly,
Thank you very much
Click to expand...
Click to collapse
:beer:
Sent from my LG-E988 using xda app-developers app
Problem with battery after update the new rom
Jammol said:
Charge the phone all the way, then it'll work.
Sent from my LG-E980 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
LG optimus g e980
I live in Italy, I bought LG E980 on ebay. To localize the menu in Italian, I did upgrade to the rom Panama. and I also did the root
The phone works fine, but only on 3G I DO NOT HAVE THE MENU 4G (LTE).
I wanted to put another Rom, but now the program tells me battery problems (really weird)
Do you have any solutions for solve this problem?
Oh well..
Upgraded from 10.0.4 to 10.0.6 via ota and boom my mobiledata is gone.
I do NOT want to factory reset. Lets try it if nothing else helps.
Can someone put somewhere where I can download files from 10.0.4 eu rom:
/system/priv-app/TeleService/*
My logcat shows:
FATAL EXCEPTION: main
Process: com.android.phone, PID: 10338
java.lang.RuntimeException: Unable to instantiate application com.android.phone.PhoneApp: java.lang.ClassNotFoundException: Didn't find class "com.android.phone.PhoneApp" on path: DexPathList[[zip file "/system/priv-app/TeleService/TeleService.apk"],nativeLibraryDirectories=[/system/priv-app/TeleService/lib/arm64, /system/priv-app/TeleService/TeleService.apk!/lib/arm64-v8a, /system/lib64, /product/lib64, /system/lib64, /product/lib64]]
at android.app.LoadedApk.makeApplication(LoadedApk.java:1226)
at android.app.ActivityThread.handleBindApplication(ActivityThread.java:6594)
at android.app.ActivityThread.access$1600(ActivityThread.java:231)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1952)
at android.os.Handler.dispatchMessage(Handler.java:107)
at android.os.Looper.loop(Looper.java:214)
at android.app.ActivityThread.main(ActivityThread.java:7682)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:516)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:950)
Caused by: java.lang.ClassNotFoundException: Didn't find class "com.android.phone.PhoneApp" on path: DexPathList[[zip file "/system/priv-app/TeleService/TeleService.apk"],nativeLibraryDirectories=[/system/priv-app/TeleService/lib/arm64, /system/priv-app/TeleService/TeleService.apk!/lib/arm64-v8a, /system/lib64, /product/lib64, /system/lib64, /product/lib64]]
at dalvik.system.BaseDexClassLoader.findClass(BaseDexClassLoader.java:196)
at java.lang.ClassLoader.loadClass(ClassLoader.java:379)
at java.lang.ClassLoader.loadClass(ClassLoader.java:312)
at android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
at android.app.Instrumentation.newApplication(Instrumentation.java:1153)
at android.app.LoadedApk.makeApplication(LoadedApk.java:1218)
... 9 more
Suppressed: java.io.IOException: Failed to open dex files from /system/priv-app/TeleService/TeleService.apk because: Failure to verify dex file '/system/priv-app/TeleService/TeleService.apk': Bad checksum (c0c2207c, expected 277e206c)
at dalvik.system.DexFile.openDexFileNative(Native Method)
at dalvik.system.DexFile.openDexFile(DexFile.java:365)
at dalvik.system.DexFile.<init>(DexFile.java:107)
at dalvik.system.DexFile.<init>(DexFile.java:80)
at dalvik.system.DexPathList.loadDexFile(DexPathList.java:444)
at dalvik.system.DexPathList.makeDexElements(DexPathList.java:403)
at dalvik.system.DexPathList.<init>(DexPathList.java:164)
at dalvik.system.BaseDexClassLoader.<init>(BaseDexClassLoader.java:126)
at dalvik.system.BaseDexClassLoader.<init>(BaseDexClassLoader.java:101)
at dalvik.system.PathClassLoader.<init>(PathClassLoader.java:74)
at com.android.internal.os.ClassLoaderFactory.createClassLoader(ClassLoaderFactory.java:87)
at com.android.internal.os.ClassLoaderFactory.createClassLoader(ClassLoaderFactory.java:116)
at android.app.ApplicationLoaders.getClassLoader(ApplicationLoaders.java:114)
at android.app.ApplicationLoaders.getClassLoaderWithSharedLibraries(ApplicationLoaders.java:60)
at android.app.LoadedApk.createOrUpdateClassLoaderLocked(LoadedApk.java:851)
at android.app.LoadedApk.getClassLoader(LoadedApk.java:950)
at android.app.LoadedApk.getResources(LoadedApk.java:1188)
at android.app.ContextImpl.createAppContext(ContextImpl.java:2499)
at android.app.ContextImpl.createAppContext(ContextImpl.java:2491)
at android.app.ActivityThread.handleBindApplication(ActivityThread.java:6497)
... 8 more
Here you go.
Thanks mate. Did not help. Was weird cache problem and only factory reset solved it.
tohtorin said:
Thanks mate. Did not help. Was weird cache problem and only factory reset solved it.
Click to expand...
Click to collapse
By what means did you do factory reset? Did you lose root?
Cowbell_Guy said:
By what means did you do factory reset? Did you lose root?
Click to expand...
Click to collapse
Nothing else helped out. Factory reset does not lose root because it keeps magisk modded boot image. You just need to install it again from magisk manager.
i had the same, and after monster process of rooting and 1:1 backup restoration (3 days), the last thing was to insert the SIM card (only after phone is secure), bang. Factory reset is something i never do unless i'm switching phone so i started checking files (same vs backup), log tracing, reverse engineering but then i quickly realized why bother if we have a patch boy - OOS Native Call Recording - here, so i just removed and installed the magisk plugin and it's fixed the problem.