Related
I get these annoying pop up notifications about nfc not working and other stuff and certain apps freeze for a sec then start up again. I have the screen shots that i will attach. I used the new method on this site after i got the stock JB update from VZ OTA.
Also, im a noob even though i got this done using VM and a cracked version of windows xp.
Please help!!!
FingerBlastJ said:
I get these annoying pop up notifications about nfc not working and other stuff and certain apps freeze for a sec then start up again. I have the screen shots that i will attach. I used the new method on this site after i got the stock JB update from VZ OTA.
Also, im a noob even though i got this done using VM and a cracked version of windows xp.
Please help!!!
Click to expand...
Click to collapse
I take it you are running a custom recovery? Boot into it and clear your cache and dalvik cache and then fix permissions. Usually force closes are permission issues. If it doesn't fix it maybe a factory reset? If that don't do anything either then just flash the JB rooted image with odin from here
x714x said:
I take it you are running a custom recovery? Boot into it and clear your cache and dalvik cache and then fix permissions. Usually force closes are permission issues. If it doesn't fix it maybe a factory reset? If that don't do anything either then just flash the JB rooted image with odin from here
Click to expand...
Click to collapse
how long does it normally take to fix permissions? its been doing it for 5 mins and it almost seems frozen and this is my 2nd attempt. i took out the battery and tried again. what should i do now?
FingerBlastJ said:
how long does it normally take to fix permissions? its been doing it for 5 mins and it almost seems frozen and this is my 2nd attempt. i took out the battery and tried again. what should i do now?
Click to expand...
Click to collapse
ok now i have a bigger problem, "unfortunately, touchwiz hom has stopped" flashes every5 secs and i cant even use my phone. what do i do?
FingerBlastJ said:
ok now i have a bigger problem, "unfortunately, touchwiz hom has stopped" flashes every5 secs and i cant even use my phone. what do i do?
Click to expand...
Click to collapse
Download that stock rooted JB image I linked to and flash it with odin. If you don't know how to use odin follow step 5 in this guide. Fixing permissions should only take a couple mins tops on a stock rom so something is probably corrupted and causing issues.
x714x said:
Download that stock rooted JB image I linked to and flash it with odin. If you don't know how to use odin follow step 5 in this guide. Fixing permissions should only take a couple mins tops on a stock rom so something is probably corrupted and causing issues.
Click to expand...
Click to collapse
yea i know how to flash with odin, im gonna try it right now with the non wipe version of the latest JB
FingerBlastJ said:
yea i know how to flash with odin, im gonna try it right now with the non wipe version of the latest JB
Click to expand...
Click to collapse
odin isnt allowing me to flash that image, attached is a screen shot
What does the error say? I can't read it that small.
x714x said:
What does the error say? I can't read it that small.
Click to expand...
Click to collapse
it says vmware-host\shared folders\desktop\root files\root66 file ..... then all these special characters that look like boxes
i tried running a different launcher, and they work a lil better but touchwiz is by far superior but i still get the nfc stopped message and everything is much slower
Ya i dont know what what that refers too either, you have a windows computer you can run it on then inside a VM?
x714x said:
Ya i dont know what what that refers too either, you have a windows computer you can run it on then inside a VM?
Click to expand...
Click to collapse
im using a mac so im forced to use windows xp on VM
FingerBlastJ said:
im using a mac so im forced to use windows xp on VM
Click to expand...
Click to collapse
ok i just did a factory reset and i still have the nfc issue along with the com.android.phone issue and i cant get into the mobile networks, any ideas of what i can do?
this thread here says its an nfc fix i just dont know if it will ruin my nfc capabilities
http://forum.xda-developers.com/showpost.php?p=32029713&postcount=8367
please help.
Something is corrupt on the system is my guess. Im thinking your only option is to flash the os again.
x714x said:
Something is corrupt on the system is my guess. Im thinking your only option is to flash the os again.
Click to expand...
Click to collapse
by flashing you mean formatting? why would that do anything when it didnt do much the first time?
Hi, Guys,
I'm using P5110, with CM 9.
Everything was fine at the beginning, but din't know since when, it takes forever to uninstall any app, taking more than 10 minutes in many cases.
Sometimes, rebooting the tab would help to get the app uninstalled, but it is ridiculous to do so every time before uninstalling apps.
Any idea how to solve this?
Thanks!
Jxt. said:
Hello there, even though i don't your same tablet i may be able to help. What rom are you currently on, and are you rooted?
Click to expand...
Click to collapse
Hi, Jxt,
Thanks for your attention.
The rom I am on is: [4.0.4] CyanogenMod 9, downloaded from:
http://forum.xda-developers.com/showthread.php?t=1722099
Yes, my tab is rooted.
Hope it won't require complete system re-flashing rom, 'cause when thinking of flashing rom and installing, setting all the apps, it drives me mad.
Jxt. said:
Hello, your welcome i was just wonder, did you restore apps with titanium backups?
Are you running out of space?
Try going into recovery and wiping cache? NOT Factory !!
Click to expand...
Click to collapse
Hi,
1. I didn't use titanium;
2, space is enough,
3, Thx for your suggestion, gonna try it now.
Jxt. said:
Tell me if it works for you!
Click to expand...
Click to collapse
I've just wiped cache, but sorry it doesn't work, problem remains.
Anything else to try?
P.S.
I've installed FREE MY APPS before, and therefore, have install/uninstall many apps on this tab, but months ago, I've stopping doing this and removed all the staff, including FREE MY APPS.
Maybe during that period, some mess was done to the system?
Jxt. said:
The only thing i would say to try now is flashing a different rom, i recommend Pacman roms.
Click to expand...
Click to collapse
Will check it out when I'm ready to go through the pain of flashing rom.
Thx.
Jxt. said:
Lol best of luck to you tell me if it works whenever you do try it
If i helped you please thank me with the button
Click to expand...
Click to collapse
Have cliked on it.
viaj said:
Hi, Guys,
I'm using P5110, with CM 9.
Everything was fine at the beginning, but din't know since when, it takes forever to uninstall any app, taking more than 10 minutes in many cases.
Sometimes, rebooting the tab would help to get the app uninstalled, but it is ridiculous to do so every time before uninstalling apps.
Any idea how to solve this?
Thanks!
Click to expand...
Click to collapse
I assume you are trying to uninstall from your Setting/Apps.
What happens if you log into the Playstore App and try to uninstall apps from there?
hcfte said:
I assume you are trying to uninstall from your Setting/Apps.
What happens if you log into the Playstore App and try to uninstall apps from there?
Click to expand...
Click to collapse
Both the same.
Have you tried to go into recovery and clear cache?
Sent from my GT-P3113 relaxing at the beach using Xperant Blue Tapatalk 4
Problem finaly solved wihout having to reflash rom, or even switch rom!
All credit goes to a miracle app: SDmaid !
After trying wiping cache, and using several apps to clean the trash files (some tools did clean hundred MB of trash files) without any help, I tried SDmaid.
It further cleaned out tons of trash files, and right after that, it takes only few seconds to uninstall apps, work like charm!
Problem finaly solved wihout having to reflash rom, or even switch rom!
All credit goes to a miracle app: SDmaid ! :good:
After trying wiping cache, and using several apps to clean the trash files (some tools did clean hundred MB of trash files) without any help, I tried SDmaid.
It further cleaned out tons of trash files, and right after that, it takes only few seconds to uninstall apps, work like charm!
[Q] Please help! "unfortunately the process com.android.systemui has stopped"
I have a rooted nexus 5 running CM11. I kept getting this message before and I didn't know why so I posted here and someone told me to wipe my data so I did. That fixed the problem for about 2 weeks but it's back again. It happens so frequently now its very frustrating. It happens when I open an app, update an app or uninstall an app. Not every time but most frequently when updating. Why is this happening?! Please help and thanks in advance!
Just reflash your ROM or flash a different ROM and your problem should be fixed
Sent from my Nexus 5 using Tapatalk
Do you use Xposed or any theme mods? Probably something like that causing it.
As spinninbsod said, just dirty flash your ROM again or clean flash a new one.
CitizenLee said:
Do you use Xposed or any theme mods? Probably something like that causing it.
As spinninbsod said, just dirty flash your ROM again or clean flash a new one.
Click to expand...
Click to collapse
Ok I'll try reflashing. And yes I have xposed and around 10 mods.
lilfil3 said:
Ok I'll try reflashing. And yes I have xposed and around 10 mods.
Click to expand...
Click to collapse
Cool, just make sure none of the mods are trying to do the same thing, like change battery icon etc.
If you're reflashing ROM it also might be worth taking a fresh back up before reactivating Xposed, just to save reflashing if something ***** up again
CitizenLee said:
Cool, just make sure none of the mods are trying to do the same thing, like change battery icon etc.
If you're reflashing ROM it also might be worth taking a fresh back up before reactivating Xposed, just to save reflashing if something ***** up again
Click to expand...
Click to collapse
I think its XBLAST TOOLS that's giving me the problems. I don't get that error until I open the app.
lilfil3 said:
I think its XBLAST TOOLS that's giving me the problems. I don't get that error until I open the app.
Click to expand...
Click to collapse
Ok that's a good start. Can you remember what you were using it to do? There's probably a similar settings in XGEL or Gravity Box.
CitizenLee said:
Ok that's a good start. Can you remember what you were using it to do? There's probably a similar settings in XGEL or Gravity Box.
Click to expand...
Click to collapse
As soon as I open xblast I get the error. I just uninstalled it and I'm trying gravity box now to see if it was just xblast. And what do you mean what I was using?
lilfil3 said:
As soon as I open xblast I get the error. I just uninstalled it and I'm trying gravity box now to see if it was just xblast. And what do you mean what I was using?
Click to expand...
Click to collapse
Prior to your problems, were you using XBlast to do anything specific like changing statusbar or something like that?
CitizenLee said:
Prior to your problems, were you using XBlast to do anything specific like changing statusbar or something like that?
Click to expand...
Click to collapse
Yes. I had like everything enabled. I changed things in the status and notification bar and I also did stuff to my lock screen and a few other tweaks.
lilfil3 said:
Yes. I had like everything enabled. I changed things in the status and notification bar and I also did stuff to my lock screen and a few other tweaks.
Click to expand...
Click to collapse
You can change all that stuff in GravityBox and XGEL so might be best to just use those instead
Due to an update of an Xposed module, I had badly corrupted my systemui. The phone was totally unusable, and I could only press the OK button notifying the stopped event at startup.
Lucky me, I still had not updated to 4.4.3. Via Skipsoft Android Toolkit I updated to the last Android release, and my systemui got fixed. I did not choose to perform a complete wipe, so I actually maintained my previous apps. In relation to root, I did not loose it, but I had to reinstall SuperSU to get the non-official apps working again.
I hope this helps somebody else in my same condition, with no need to do a system wipe!
thank you. this helped me today.
woke up with the error. assuming its gravitybox and xblast causing an issue. will remove xblast.
i9o said:
Due to an update of an Xposed module, I had badly corrupted my systemui. The phone was totally unusable, and I could only press the OK button notifying the stopped event at startup.
Lucky me, I still had not updated to 4.4.3. Via Skipsoft Android Toolkit I updated to the last Android release, and my systemui got fixed. I did not choose to perform a complete wipe, so I actually maintained my previous apps. In relation to root, I did not loose it, but I had to reinstall SuperSU to get the non-official apps working again.
I hope this helps somebody else in my same condition, with no need to do a system wipe!
Click to expand...
Click to collapse
Xposed does not actually "touch" or change SystemUI in any way. Xposed puts a couple of "files" in system which allows intercepted commands to be changed, without changing the actual code.
When you updated the ROM via a toolkit (PLEASE don't use toolkits by the way) you would have overwritten these Xposed files.
The simplest fix is to just remove the Xposed files
Sent from my Nexus 5 using Tapatalk
Hi Guys! Really hope you can help.
My Nexus 5 when I turned it on this morning booted up into 4.4.4 and suddenly showed that the process "com.android.systemui" has stopped. I rebooted several times and even cleared the cache through stock recovery and I still get the message. I have no idea what caused it. It was fine last night when I turned it off.
My phone is rooted and I do have a nandroid that is about two months old and I could boot TWRP using the Nexus Root Toolkit, but I was wondering if there is any other options? I would prefer not to lose anything up to this point.
I could kick myself for not making a more current nandroid. I've just been busy.
If the nandroid restore is the best approach could you refresh me on the exact options needed for both a clean restore with a nandroid and a dirty flash? I would probably dirty flash it first.
Hope you can help! Thanks so much!
Matthewlawson3 said:
Hi Guys! Really hope you can help.
My Nexus 5 when I turned it on this morning booted up into 4.4.4 and suddenly showed that the process "com.android.systemui" has stopped. I rebooted several times and even cleared the cache through stock recovery and I still get the message. I have no idea what caused it. It was fine last night when I turned it off.
My phone is rooted and I do have a nandroid that is about two months old and I could boot TWRP using the Nexus Root Toolkit, but I was wondering if there is any other options? I would prefer not to lose anything up to this point.
I could kick myself for not making a more current nandroid. I've just been busy.
If the nandroid restore is the best approach could you refresh me on the exact options needed for both a clean restore with a nandroid and a dirty flash? I would probably dirty flash it first.
Hope you can help! Thanks so much!
Click to expand...
Click to collapse
First of all, stop using the stock recovery.
Since you had root access, were you using any modifications such as Xposed?
You can pull your internal storage with adb pull /sdcard/, and your app data with adb pull /data/data/ while in custom recovery.
You can also try pushing a stock ROM .zip downloaded from here to your device with ADB push, then dirty flashing it in recovery (obviously after flashing a custom recovery, also assuming you're on stock ROM).
Also, don't use toolkits. Click the first link of my signature and read some threads if you don't know how to use ADB/fastboot.
On a sidenote I do have xposed framework installed. However, I've never had any problems out of it and I have not modified anything in months.
Matthewlawson3 said:
Hi Guys! Really hope you can help.
My Nexus 5 when I turned it on this morning booted up into 4.4.4 and suddenly showed that the process "com.android.systemui" has stopped. I rebooted several times and even cleared the cache through stock recovery and I still get the message. I have no idea what caused it. It was fine last night when I turned it off.
My phone is rooted and I do have a nandroid that is about two months old and I could boot TWRP using the Nexus Root Toolkit, but I was wondering if there is any other options? I would prefer not to lose anything up to this point.
I could kick myself for not making a more current nandroid. I've just been busy.
If the nandroid restore is the best approach could you refresh me on the exact options needed for both a clean restore with a nandroid and a dirty flash? I would probably dirty flash it first.
Hope you can help! Thanks so much!
Click to expand...
Click to collapse
Matthewlawson3 said:
On a sidenote I do have xposed framework installed. However, I've never had any problems out of it and I have not modified anything in months.
Click to expand...
Click to collapse
Read my previous post, and since you're running Xposed try using it's safemode disable feature, explanation on how that works here: http://forum.xda-developers.com/showpost.php?p=51306764&postcount=9879
Do you think this is caused by Xposed? You want me to disable it to see I assume?
Matthewlawson3 said:
Do you think this is caused by Xposed? You want me to disable it to see I assume?
Click to expand...
Click to collapse
It's entirely possible that a module/Xposed itself is causing a SystemUI crash, it's happened to me before. I'd do it just to be sure, then proceed to what I said in my previous post if it still happens.
Ok its been awhile since I dirty flashed. If I have to do that, what are the exact things that need to be cleared to maintain data after recovery?
Lethargy said:
It's entirely possible that a module/Xposed itself is causing a SystemUI crash, it's happened to me before. I'd do it just to be sure, then proceed to what I said in my previous post if it still happens.
Click to expand...
Click to collapse
Matthewlawson3 said:
Ok its been awhile since I dirty flashed. If I have to do that, what are the exact things that need to be cleared to maintain data after recovery?
Click to expand...
Click to collapse
What do you mean? No data is lost if you dirty flash a ROM, it only reformats /system.
Custom recovery, download stock ROM flashable zip, ADB push zip to your device while it's in recovery, then flash it.
It looks like I may not have to flash anything. The Xposed Disable worked. But how do I proceed if I want to use Xposed still?
Lethargy said:
What do you mean? No data is lost if you dirty flash a ROM, it only reformats /system.
Custom recovery, download stock ROM flashable zip, ADB push zip to your device while it's in recovery, then flash it.
Click to expand...
Click to collapse
Matthewlawson3 said:
It looks like I may not have to flash anything. The Xposed Disable worked. But how do I proceed if I want to use Xposed still?
Click to expand...
Click to collapse
First of all we have to see if it's an individual module or Xposed itself causing the issue. List your modules?
Disable all your modules, and delete /data/data/de.robv.android.xposed.installer/conf/disabled using a file explorer (to re-enable Xposed like the post says).
Reboot with no modules active, and see if it happens again.
If it doesn't, enable one module, reboot.
If it still doesn't happen, disable the module and enable a different one, reboot again. Keep doing it until you find the culprit.
OK.
My modules are AC Display, Bootmanager, DS Battery Saver, Google Search API, Gravity Box (KK), Greenify, Immerse Me, Notify Clean, Swype Tweaks, Xblast Tools, and Youtube Adaway.
Lethargy said:
First of all we have to see if it's an individual module or Xposed itself causing the issue. List your modules?
Disable all your modules, and delete /data/data/de.robv.android.xposed.installer/conf/disabled using a file explorer (to re-enable Xposed like the post says).
Reboot with no modules active, and see if it happens again.
If it doesn't, enable one module, reboot.
If it still doesn't happen, disable the module and enable a different one, reboot again. Keep doing it until you find the culprit.
Click to expand...
Click to collapse
Matthewlawson3 said:
OK.
My modules are AC Display, Bootmanager, DS Battery Saver, Google Search API, Gravity Box (KK), Greenify, Immerse Me, Notify Clean, Swype Tweaks, Xblast Tools, and Youtube Adaway.
Click to expand...
Click to collapse
Continue with what I've said to try, a few of your modules modify the system and could be causing it.
Go to the xposed module repository and find which of those modules updated recently. I'd bet that's the culprit. Or at least it's a good place to start looking.
Ok before I proceed. I have went into Xposed and disabled all modules. I am now in Root Explorer and have dug down to the "disabled" file following the path indicated. Do I just delete "disabled" and then reboot?
Lethargy said:
Continue with what I've said to try, a few of your modules modify the system and could be causing it.
Click to expand...
Click to collapse
Matthewlawson3 said:
Ok before I proceed. I have went into Xposed and disabled all modules. I am now in Root Explorer and have dug down to the "disabled" file following the path indicated. Do I just delete "disabled" and then reboot?
Click to expand...
Click to collapse
Yep, delete the folder named "disabled"
It may be faster to see which module updated recently and see if that fixes the problem first before going one by one. What do you think?
Lethargy said:
Yep, delete the folder named "disabled"
Click to expand...
Click to collapse
Matthewlawson3 said:
It may be faster to see which module updated recently and see if that fixes the problem first before going one by one. What do you think?
Click to expand...
Click to collapse
Worth a shot. In the end it's probably a single module, or a combination of conflicting modules, that's causing the issue.
Looks like the latest updated was Bootmanager on July 26.
Lethargy said:
First of all we have to see if it's an individual module or Xposed itself causing the issue. List your modules?
Disable all your modules, and delete /data/data/de.robv.android.xposed.installer/conf/disabled using a file explorer (to re-enable Xposed like the post says).
Reboot with no modules active, and see if it happens again.
If it doesn't, enable one module, reboot.
If it still doesn't happen, disable the module and enable a different one, reboot again. Keep doing it until you find the culprit.
Click to expand...
Click to collapse
Matthewlawson3 said:
Looks like the latest updated was Bootmanager on July 26.
Click to expand...
Click to collapse
Try enabling them one by one by update date.
I'll reboot with all modules off first. Ok, I no longer am getting the error message. At least it's not Xposed itself!
Matthewlawson3 said:
Looks like the latest updated was Bootmanager on July 26.
Click to expand...
Click to collapse
I'm trying to flash a new build of Lineage OS on my OnePlus One, but upon flashing the ROM in TWRP I get the error "Error exectuing updater binary in zip sdcard".
I'm currently running CM13 on Android version 6.0.1, however it's a pretty old build since I flashed this in February 2016 and never bothered to update..
The process of what I did was, I backed up my current ROM, I wiped system, dalvik and normal cache.
The exact error is:
Code:
"Can't install this package on top of incompatible data.
Please try another package or run a factory rset.
E: Error executing updater binary in zip '/sdcard/lineage-14.1-20170206-nightly-bacon-signed.zip'
Error flashing zip '/sdcard/lineage-14.1-20170206-nightly-bacon-signed.zip'"
Help would be appreciated!
Since you have nothing to lose flash the stock COS 13.1 ROM from fastboot.
Then flash TWRP from fastboot and make sure it's the last version. Also download again the zip of Lineage to be sure it's not corrupted.
I'm currently running on that ROM, very stable and enjoyable like a COS stock N ROM.
AndroidFan2 said:
I'm trying to flash a new build of Lineage OS on my OnePlus One, but upon flashing the ROM in TWRP I get the error "Error exectuing updater binary in zip sdcard".
I'm currently running CM13 on Android version 6.0.1, however it's a pretty old build since I flashed this in February 2016 and never bothered to update..
The process of what I did was, I backed up my current ROM, I wiped system, dalvik and normal cache.
The exact error is:
Code:
"Can't install this package on top of incompatible data.
Please try another package or run a factory rset.
E: Error executing updater binary in zip '/sdcard/lineage-14.1-20170206-nightly-bacon-signed.zip'
Error flashing zip '/sdcard/lineage-14.1-20170206-nightly-bacon-signed.zip'"
Help would be appreciated!
Click to expand...
Click to collapse
Make sure zip isn't corrupted.
And don't forget to do wipe data/factory reset next time.
Guys, I have recently installed lineage OS, rooted and installed adaway. Yet I am getting annoying ads on my caller! I installed google caller, disabled default caller, yet I am getting ads on google dialler, whenever I get incoming calls. What the hell? Anyone facing this problem? Can anyone help?
coolcmc said:
Guys, I have recently installed lineage OS, rooted and installed adaway. Yet I am getting annoying ads on my caller! I installed google caller, disabled default caller, yet I am getting ads on google dialler, whenever I get incoming calls. What the hell? Anyone facing this problem? Can anyone help?
Click to expand...
Click to collapse
It might be some app you have installed
Because I don't get any ads in the dailer
coolcmc said:
Guys, I have recently installed lineage OS, rooted and installed adaway. Yet I am getting annoying ads on my caller! I installed google caller, disabled default caller, yet I am getting ads on google dialler, whenever I get incoming calls. What the hell? Anyone facing this problem? Can anyone help?
Click to expand...
Click to collapse
It might be some 3rd party apps that you probably gave root permission. can you provide a screen shot of your supersu front page?
piez97 said:
It might be some 3rd party apps that you probably gave root permission. can you provide a screen shot of your supersu front page?
Click to expand...
Click to collapse
Here it is
coolcmc said:
Here it is
Click to expand...
Click to collapse
Uninstall AdBlockPlus and Root checker. Then try rebooting your device. If the ads are still there try wiping your cache.
Adaway alone will give you best experience.
piez97 said:
Uninstall AdBlockPlus and Root checker. Then try rebooting your device. If the ads are still there try wiping your cache.
Adaway alone will give you best experience.
Click to expand...
Click to collapse
Sure, I will give it a try
coolcmc said:
Sure, I will give it a try
Click to expand...
Click to collapse
did it work?
piez97 said:
did it work?
Click to expand...
Click to collapse
I tried it, nothing happened. I did not get ads yesterday but today I got one ?
I did not clear the cache but did the rest
coolcmc said:
Sure, I will give it a try
Click to expand...
Click to collapse
I uninstalled and did a reboot, there were no ads yesterday but appeared today? (sorry did not clear the cache)
But now I know from which app its appearing, but this is sad, can someone fix it?
coolcmc said:
I uninstalled and did a reboot, there were no ads yesterday but appeared today (sorry did not clear the cache)
But now I know from which app its appearing, but this is sad, can someone fix it?
Click to expand...
Click to collapse
I think it's because you are using a third party dialer. Use google dialer. It is clean,simple and won't show ads.
piez97 said:
I think it's because you are using a third party dialer. Use google dialer. It is clean,simple and won't show ads.
Click to expand...
Click to collapse
I am not using a third party dialer/caller. The stock version also showed ads and google version did too. Now that I uninstalled an app, I am not getting ads on the caller