Problem since rooting - AT&T, Rogers, Bell, Telus Samsung Galaxy S III

I used the method posted in the General sticky thread, followed it and have a rooted phone. I have noticed that since then, Some apps stop responding and I have to pull the battery and reboot. Has anyone experienced similar issues shortly after rooting?

What apps are the problem? At the very least, I would try uninstalling them and reinstalling to see if that helps. Also try a factory reset.
Sent from my SGH-I747 using xda app-developers app

JamesRF said:
I used the method posted in the General sticky thread, followed it and have a rooted phone. I have noticed that since then, Some apps stop responding and I have to pull the battery and reboot. Has anyone experienced similar issues shortly after rooting?
Click to expand...
Click to collapse
Factory reset, wipe cache, wipe dalvik, fix permissions
Sent from my SGH-I747 using xda app-developers app

It seems to be random, and all apps. The app hangs to where all I can do is turn the screen off and on, the other buttons don't work at all.

I ran "fix permissions" both in CWM recovery and RomManager and the issue seems to have been fixed.

Related

Phone rebooting itself, bootloops. Please help

SO I Did a full wipe and wiped cache/dalvik cache twice, and installed Myn's ROM. My phone is rebooting itself anytime I'm browsing the net or doing wireless/wired tether. I can feel my phone getting hot on the back during the process of rebooting. What is causing this? I've tried flashing different kernels but to no avail. Is anyone experiencing or have experienced this problem? If so, can you please point me to how I can fix this? Everything works fine until I begin to browse the net or tether, and then it goes into a boot loop until I remove the battery for several mniutes, then everything is back to normal. Also, ive noticed that when i do full data wipe and reboot, everything is bavk to stock however it seems myns rom isnt coompletely removed. Wiped a few time but same thing happens. Please help! ;(
Sent from my PC36100 using XDA App
Sent from my PC36100 using XDA App
+1
10char
...searching the forums, but no luck.
Mine only reboots using kernels other than stock
Sent from my PC36100 using XDA App
nosfanatic2006 said:
Mine only reboots using kernels other than stock
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
I wonder if my phone somehow ended up with running two kernals, or the remnants of some other kernel still exists and it's causing problems????
Zameus said:
...searching the forums, but no luck.
Click to expand...
Click to collapse
really you did a search and didn't find this http://forum.xda-developers.com/showthread.php?t=818260 its a common problem especially after rooting and flashing something that will run two differnt network signals
Thank you! Much appreciated.

Cyanogen Mod - Camera just started Force Closing...help?

I've used Cyanogen Mod for quite a while without issue. Then, last week my camera started force closing. So far as I knowing didn't change any settings or install an app that would mess with it. Haven't updated radios, etc...it just stopped. I've cleared the cache in apps settings, there is space on the card.
Any suggestions? Thanks!
clear cache and dalvik from recovery, and reboot. If that doesnt work, you will probably have to reflash the rom.
sitlet said:
clear cache and dalvik from recovery, and reboot. If that doesnt work, you will probably have to reflash the rom.
Click to expand...
Click to collapse
Do I need to back anything up before doing this? Thanks.
Sent from my PC36100 using Tapatalk
polkadots said:
Do I need to back anything up before doing this? Thanks.
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
Shouldn't lose anything, as you are just clearing cache files. However, it can never hurt to do a backup first, only takes a couple minutes.
Ugh. I did a full wipe and upgraded to 7.1 (was on 7.0.2)...Camera is still FC'ing...again, it works with other apps (Vignette, Goggles) but not the stock camera. It worked just fine until two weeks ago...and then, nothing. No clue why. :/
Well, now it works...I did one more wipe and it just started working. Thanks!
Try fix permissions, worked for me
Sent from my PC36100 using xda premium

"Android is upgrading:Starting Apps" Every reboot.

This is something that's bothered me since upgrading to 4.1.1. Doing just what the title says. So far, I've tried clearing the dalvik cache, wiping the cache partition, uninstalling titanium backup and restarting, as well as uninstalling ROM toolbox and lucky patcher. I'm rooted with chainfire's "quick" method but I also had root before upgrading from ICS. I also tried bin4ry's universal ICS/Jellybean method after upgrading before finding chainfire's, witch, I am suspicious of bin4ry's causing the bug in the first place. The message shows briefly after the glowing "Samsung" boot animation. I have scoured to the bottom of the internet looking for an answer, but I really, really do not want to re-flash the stock rom again. Any reason why this happens? Any way to fix it without wiping my phone; if that works?
Sent from my SAMSUNG-SGH-I747
Sounds like it's wiping dalvik on each reboot. Wipe and re flash.
Sent from my SGH-I747 using Tapatalk 2
peneoark said:
Sounds like it's wiping dalvik on each reboot. Wipe and re flash.
Sent from my SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
Any reasons why this happens?
Mine is doing the same thing.
peneoark said:
Sounds like it's wiping dalvik on each reboot. Wipe and re flash.
Sent from my SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
It's not wiping the dalvik cache. The system displays the message briefly with no application count. I just assumed it was normal on 4.1.1
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Several people seem to claim otherwise, Google shows. My tenant's and several of my friend's phones don't do it. I'll try reverting to factory and upgrading again in a few days if there are no other solutions.
Sent from my SAMSUNG-SGH-I747
Mine showed up after the Google wallet mod. Also had it happen after removing some stock apps although I'm not sure which caused it.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
I've removed a lot of at&t's bloatware, along with S-Suggest, "help" and ypmobile. I've also frozen s-voice and the samsung keyboard in favor of SwiftKey. I've removed bloatware in both so far. Maybe once I revert, I'll try to find out more about the problem. Until my phone is sick of the cache partition wipes and ruthless dalvik cache destruction, I will continue to try in vain. For the good of my OCD.
Sent from my SAMSUNG-SGH-I747
Many ROMs and Kernels are set to ziplalign apps on boot to improve performance.
I want to say this was also implemented in stock JB, or its set in CWM's init.d script for the newer versions.
This also happens each time you wipe dalvik and/or if you have Titanium Backup set to intergrate sys dalvik into ROM
I just did the HOWTO root after upgrading to stock JB, and after reading this post I did a quick reboot and yeh, the message appears for me as well.
Never integrated sysdalvik w/ titanium backup. I've also rebooted the phone without clearing dalvik, and never had cwm. Probably a few things I should have mentioned earlier, but they never crossed my mind.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Fixed the problem. Turns out you do need to re flash the whole phone. Reset to factory in recovery, then wipe the cache AND the dalvik, then reset to stock using ODIN. IT IS IMPERATIVE THAT YOU RESET TO FACTORY. The phone will remain soft bricked otherwise. A tutorial can be found here: http://galaxys3root.com/galaxy-s3-unroot/how-to-unroot-att-galaxy-s3-sgh-i747/. The only tried and true way to get the bug out. As far as I know. If anyone has any more ideas as to how this problem occurs, I'd still like to hear them.
Sent from my rooted SAMSUNG SGH-I747. THANKS CHAINFIRE!!
I rarely reboot these days. I do my CWM backups online.
But when I do reboot, I do get that updating message and have been seening that from as far back as I can remember. It bugged me at first but not now. For me, it only does it for about 2-4secs so I don't bother trying to fix it.
I have the cause in my case but I don't have the solution. I flashed a mod I found here http://forum.xda-developers.com/showthread.php?t=2044449, apn_editor_1.1.zip. Now every reboot I get Android Is Upgrading.... Starting apps.
How do I stop the phone from trying to add this mod?
Just got the same problem. Had super SU on the phone (soft root), so i tried to fully root (i installed xblasttools, and had to flash pa-icons, so i could change the color of the battery, but i couldn't because it said signature failed). Downloaded philz kernel/root, flashed with recovery. Then i uninstalled the Super su rebooted and there it was; Andriod is upgrading ...
I'm on 4.1.2, Samsung GT-i9100. Help !
P.S Uninstalled the superuser that i got with the phil kernel and installed Super SU. Also i did wipe the davlik and cache. Same stuff.
I got the Android is upgrading message before. It was because I tried to convert a user app to a system app. Converted it back to a user app and it went away. I think it had something to do with having an apk file but no corresponding odex file for that app in /system/app
Sent from my SGH-I747M using xda app-developers app
I have found why this happens, issue is with lucky patcher, when you patch application it creates <appname.odex> this odex file is somehow diffrent than real odex, so when you wipe dalvik cache it caches all your apps and then you have Android is starting apps on each boot. The solution is to delete all apps odexes wich you patched, reboot phone, this time it will not display "android is starting apps" and will work until you delete dalvik again. It is possible to apply patch with Lucky Patcher to dalvih cache instead of creating odex, but you loose your crack when you wipe dalvik again.
This is the solution, if someone have better way of doing it post here, also sorry if thread is old.
magix01 said:
I have found why this happens, issue is with lucky patcher, when you patch application it creates <appname.odex> this odex file is somehow diffrent than real odex, so when you wipe dalvik cache it caches all your apps and then you have Android is starting apps on each boot. The solution is to delete all apps odexes wich you patched, reboot phone, this time it will not display "android is starting apps" and will work until you delete dalvik again. It is possible to apply patch with Lucky Patcher to dalvih cache instead of creating odex, but you loose your crack when you wipe dalvik again.
This is the solution, if someone have better way of doing it post here, also sorry if thread is old.
Click to expand...
Click to collapse
Thank you for pointing out Lucky Patcher. The "android is starting apps" notification started when I deodexed my rom. I uninstalled those patched apps, reinstalled and re-patched normally with Lucky Patcher 3.9.9.1 and that notification is gone.
:good:
coffee black said:
Thank you for pointing out Lucky Patcher. The "android is starting apps" notification started when I deodexed my rom. I uninstalled those patched apps, reinstalled and re-patched normally with Lucky Patcher 3.9.9.1 and that notification is gone.
:good:
Click to expand...
Click to collapse
Next time just cut odex files to other location, reboot phone and copy odexes back, this should be alot easyer
Try to reflash your rom that may help some how
Sent from my GT-I9500 using xda app-developers app

GS3 Reboots In Clockworkmod

running PAC ROM for the last few months, very few issues. yesterday, phone randomly reboots & stays in bootloop. I manually reboot into recovery, do a clean wipe & re-flash ROM. phone works fine until i try to restore apps/data via Titanium, the phone goes back into bootloop. figured i possibly waited too soon to restore my phone, so i held out until this morning. go to run Titanium & phone bootloops again. but this time when i reboot into recovery & try to do a factory reset, the phone reboots as soon as i select "Yes" & goes back into bootloop. Google produced nothing, help!!!! Thanks.
Reflash rom and try to determine which app youre restoring that may be causing the problem. Do you let apps auto update? Do you have backups set to rerun on a schedule?
You could also odin flash the official firmware and start over that way.
Sent from my SGH-T999 using xda premium
DocHoliday77 said:
Reflash rom and try to determine which app youre restoring that may be causing the problem. Do you let apps auto update? Do you have backups set to rerun on a schedule?
You could also odin flash the official firmware and start over that way.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
thanks for your response! I believe I found the culprint; a theme I downloaded yesterday. I was able to wipe everything except data & reboot, which caused the phone to "optomize" all of my apps. So far so good, but I'm not so sure if this is a temporary or permanent fix.
I dont auto update anything on my phone. Should I?
EDIT: spoke too soon, phone worked for about 2 hours & went into bootloop while idle. froze while deleting dalvik cache but rebooted & is back "optomizing apps". Looks like I may have to odin flash.
armondwakeup said:
thanks for your response! I believe I found the culprint; a theme I downloaded yesterday. I was able to wipe everything except data & reboot, which caused the phone to "optomize" all of my apps. So far so good, but I'm not so sure if this is a temporary or permanent fix.
I dont auto update anything on my phone. Should I?
EDIT: spoke too soon, phone worked for about 2 hours & went into bootloop while idle. froze while deleting dalvik cache but rebooted & is back "optomizing apps". Looks like I may have to odin flash.
Click to expand...
Click to collapse
Dont auto update, I was just asking because if you did, it could point to a recently updated app as the problem.
It does sound to me like odin is your best option though.
Sent from my SGH-T999 using xda premium
Wow armond, the EXACT same thing happened to be while running Illusion. I couldn't factory reset in recovery, b/c that led to a bootloop when i pressed "yes". I wiped, cache/dalvik and phone worked for a little, had a hot reboot, and bootlooped again. By any chance are you running Ktoonsez kt747 kernel? And i eventually got it fixed thanks to Doc through ODIN. Best of luck!

[Q] SuperSU issue

Every once in a while when a new app needs root permission, i open the app waiting for the superSU popup, and it never comes. my phone ends up freezing and i have to restart it via a battery pull or long press of the power key. Once i reboot and enter the app, the superSU popup comes right away and i can grant it root permission.
Any ideas why it would be doing this?
Replace your Superuser app. Or update it.
I've done that. A few times. Still giving me that issue. It seems pretty random. And it's only the first time an app asks for permission. Seems to happen only to apps that use deep root too, like busybox etc... I think lol
Sent from my SGH-T999 using xda app-developers app
I've never had a problem with superSU, do all superuser apps do this?
Sent from my SGH-T999 using Tapatalk
No. And I've never had a superSU issue till now either. Here's the last thing I did before I noticed the issues.
I was having power button issues, but it wasn't constant, so I thought it might be a rom based issue, so I went back to the root66 version of stock 4.3
I realized that it was a hardware button, so I switched back to saranhai's stockmod slim rom. I also updated my CWM to the latest version. Those are the only things I've done between it working fine and me having these issues now. Not sure what it could be.
Sent from my SGH-T999 using xda app-developers app
Please do a Factory Reset and then try one of the apps that previously gave you trouble with Root Access.
I did a factory reset before I flashed the last rom. Think I still need to do another one?
Sent from my SGH-T999 using xda app-developers app
Given your current Problem, I'd say yes. Do it in Recovery so it will format Dalvik & Cache as well. Needless to say don't restore anything unless you have tested that the problem is indeed gone.

Categories

Resources