Hello, so after rooting my S7 and finding out that there was the annoying volte and hurricane issue, I patched in a fix to get rid of them. Unfortunately, it was a patch for the marshmallow build, which caused that process to go into a force close loop. I found the proper nougat fix and patched it, but it seemed to only affect settings and not the apk itself. In a bit of desperation, I removed the apk entirely, but that has caused a few minor issues. I was wondering if anyone would be kind enough to post the stock imsservice.apk so that I can see if that will fix the issue, and hopefully, there will be no more force closes.
Related
I have an XT 1034 that I rooted and foolishly updated to 4.4 shortly after turning it on. My phone was basically unusable thanks to the laundry list of bugs the moto g suffered from with 4.4. So after seeing that there wasn't much help from Motorola I flashed back to 4.3 which leads me to now.
It seems the latest OTA does indeed fix most if not all of the 4.4 bugs so I'm trying to update. I removed fotakill, all the xposed framework apps and any other system tweaks I could think of, but is still falling. My best guess is that adblock effed up when I tried to disable it and is causing the update to fail.
Does anyone have a stock copy of the 4.3 hosts file that I could use to get the updates to go through? I'd rather avoid reflashing to stock if possible.
You might have to chmod 644 it.
eastdata said:
You might have to chmod 644 it.
Click to expand...
Click to collapse
Many thanks
I am posting this here, since I do not have access to the KatKiss thread itself, due to new user.
After having a hard time trying to install KatKiss-4.4.3_028 (+fsync+rightclick+gapps) on an fully functional 4.4.2_024. I did everything by the book, and when didn't work I did a full factory and still problems. I think I have isolated the culprit though.
What happens is that I get stuck on the KatKiss boot animation, seemingly going nowhere. Means I need to force reset and reflash. If I flash without it works, if I flash the rightclick package onto a working 028 setup, it stops working.
So onto my question, anyone else seen this fault, and does anyone have fix to get rightclick fix to work?
Try this one and report:
4.4.3_RightClick.zip
(The previous one was made for 4.4.2, code has changed in 4.4.3 so you should not use the 4.4.2 one.)
Thanks. That seems to fix it for me.
Hi all,
I recently updated to 5.0.1 using the RUU, ever since I do not get push notifications. I am hoping it is something simple and not related to the 5.0.1 firmware.
I tried turning off the sleep mode to see if that fixed the problem, but it doesn't seem like that is the issue because I still don't get push notifications. I also checked all my in-app notification settings and they seem fine.
Does anyone have any ideas what the problem is?
Your help would be greatly appreciated.
It is most likely a ROM issue, firmware shouldn't effect is. Maybe make a backup of your current ROM and do a factory reset to see if that fixes the problem
Hi, I have a Z3 on 5.0.2 (Locked BL) and the device reboots after every app install/uninstall.
I do have xposed installed but have flashed the appropriate zips to make xposed function correctly.
What is the most likely cause of this?
Thanks
EDIT: i have done my research and noticed similar people have experienced this issue and resolved it by clearing the /data/system/netstats folder based on providing the crash text. Is anyone able to read a crash file to identify my problem?
I have also tried reflashing lollipop etc. I don't really want to move back to KK someone please help!!!!!
I hope someone can help. I am using LineageOS 18.1 with Open Gapps Pico. The custom ROM has been installed for a couple of weeks and hasn’t had too many issues - until now. (I have installed the latest patch in the past couple of days, so not sure if this is the cause of the problem, and if it is I wouldn’t know how to remove it).
I am now experiencing a problem, where the screen is freezing (see attached photo), and the only way I can find to resolve it is to physically remove the battery - although this can only be a temporary measure.
Has anyone experienced this before and is there a permanent fix / patch backout that could resolve it?
Thanks in advance.