[Q] SuperSU issue - T-Mobile, Samsung Galaxy SIII

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.

Related

[q] afraid to do anything now!

I was on Stock T999UVALH2
Rooted and all was fine
A few months later I did the small update to T999UVALH4
Again all was good.
Did the Update to the 4.1.1 OTA and phone went into a boot loop! (for a long time and while I was trying to do
different things to try to recover the phone.) I tried a whole bunch of stuff, and after trying to get into download mode,
and missing it, the phone booted into a screen that was saying it was updating file x of 25x files and counted till the last update file, and rebooted to a screen asking me to choose which launcher to use.
I chose what I was then using, and all the stuff came up, and the NEW rom was running! T999UVDLJA
Build # JRO03L.T999UVDLJA
I began having weird issues, and it was recommended I clean the Dalvic Cache.
Well, I cleared the cache with CWM and the darn thing started counting, and upgrading all over again! WTF?
I don't know what/why it did, but it rebooted and all was like before the cleaning. I have a few more stuff that just do not seem right, but I am afraid to "monkey around" with anything till someone can tell me what was happening (re flashing the rom by itself?) and what I should do to stop this behavior, or if that is a normal thing. I once cleared the cache, on another android HTC, and it just cleared the cache and rebooted.
Maybe some of our "Gurus" can tell me what I should do, if anything.
Thanks to all for any advice that might be forthcoming!
Aloha!
What recovery are you using?
Sent from my SGH-T999 using xda premium
My Recovery
CWM - based Recovery v5.5.0.4
So, you did the jellybean update without the stock recovery, yes? That's the trouble.
Sent from my SGH-T999 using xda premium
---------- Post added at 08:12 AM ---------- Previous post was at 08:09 AM ----------
I'd flash a rooted jellybean Rom; since you have clockwork.
But you could go back to stock and then update
Sent from my SGH-T999 using xda premium
?
I was on a stock rom, and folowed all the "updates" as was said that it was necessary for jelleybean...
Just so I don't grab the wrong thing again,
Would you , per chance, have a link to a rooted JB Rom?
Thanks!
Here is the link to the stock JB rooted rom, it's also safe from triggering the counter if you are worried about that stuff.
http://forum.xda-developers.com/showthread.php?t=1771687
Just flash it from Odin and you will even keep all your apps and such too.
odin flash with the jelly bean .tar image, bone stock.
then root with chains cf auto root (OG dev section)
then download the new clockwork mod touch 6.0.1.2 ..... put it on the root (meaning in no sub-directory, or in no other folders) of your internal sd card, and rename it to cwm6....
download an app called terminal emulator, open it, type "su" without quotes, then grant the app root access, then run these commands, hitting enter after each one:
dd if=/sdcard/cwm6.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery (hit enter...and you will see an output, xxx data transferred in xxx seconds blah blah)
reboot recovery (hit enter again. oops. phone rebooted....... into your new recovery)
good luck
wait, isn't it normal for the "android is upgrading/optimizing x of y apps" to appear after clearing cache? That usually happens when I clean my cache.
As for the other problems with this rom, i guess you should Odin using the method that doesn't trip your flash counter, as stated above
Sent from my SGH-T999 using xda app-developers app
That's normal. It will happen every time it has to rebuild dalvik cache.
Sounds to me like you need to backup, wipe data and start fresh and clean.
Sent from my SGH-T999 using xda premium
I have the same thing happening to me each time I clear cache (optimizing x apps of y), that's completely normal. As to other problems that you said are happening just flash root66, rooted stock 4.1.1 rom, using odin and everything should be good.
Good luck
Sent from my SGH-T999 using xda app-developers app

Problem since rooting

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.

Phone won't boot into recovery?

Hi guys, so I was using wicked ROM, whenever I tried to boot into recovery, it just rebooted back to system. Odin'ed back to stock, flashed twrp through goo manager app, but still no use. Any help greatly appreciated
Sent from my Nexus 7 using xda premium
eggydrums said:
Hi guys, so I was using wicked ROM, whenever I tried to boot into recovery, it just rebooted back to system. Odin'ed back to stock, flashed twrp through goo manager app, but still no use. Any help greatly appreciated
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
What methods have you tried?
adb reboot recovery is the easiest way to get to recovery
Maybe try flashing CWM, seeing if that works, and then flashing TWRP (I've never flashed TWRP through Goo Manager so I don't know how that works)?
If you don't have adb set up, get quick boot from market and try recovery through that.
If that doesn't work, I honestly don't know. I'm assuming you've done the power off then volume up+home+power at the same time trick already.
EtherealRemnant said:
What methods have you tried?
adb reboot recovery is the easiest way to get to recovery
Maybe try flashing CWM, seeing if that works, and then flashing TWRP (I've never flashed TWRP through Goo Manager so I don't know how that works)?
If you don't have adb set up, get quick boot from market and try recovery through that.
If that doesn't work, I honestly don't know. I'm assuming you've done the power off then volume up+home+power at the same time trick already.
Click to expand...
Click to collapse
With the goo app, I can boot directly into recovery, but my issue is that I get to the Recovery's splash screen, it hangs there for a second and immediately reboots back to system. I'm thinking to get the stock recovery back and try again I'm really not sure what the Hecks going on
Sent from my Nexus 7 using xda premium
Mhm OK, got cwm working, guess I'll just use that one for the time being
Sent from my Nexus 7 using xda premium
eggydrums said:
Mhm OK, got cwm working, guess I'll just use that one for the time being
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
I would highly recommend putting TWRP back on there. The CWM was more for testing... people have reported issues using CWM with certain ROMs. Glad you were able to get CWM on though.
Nothing wrong with CWM.
Aerowinder said:
Nothing wrong with CWM.
Click to expand...
Click to collapse
There are a number of ROMs that do not support CWM so that statement is false. FreeGS3 loses update functionality, for example.
Also, there have been complaints in the case of CWM touch of it being too easy to wipe your entire device.
Not to mention there is no Goo Manager functionality without TWRP as well.
Lots of benefits of TWRP versus CWM. I used CWM for years then had to switch to a modified TWRP for my MAXX and was more than happy when I found out the SGS3 used TWRP as well (although I wish we had the ROM slots like the MAXX though - that was actually cool)
The statement is not false. I think FreeGS3 hasn't been updated for 4.5 months? Maybe not the best example. And I still think you should use as few automated tools as possible where flashing is concerned (Goo/ROM Manager).
It can be easy to wipe the wrong partition in CWM, if you are careless or illiterate. In the 6 months that I've used it (nearly every day), I have never once wiped the wrong partition, or my entire device. Never had a backup that wouldn't restore.
I like some of what TWRP offers. But I still experience showstopping bugs with it on my device. At this time, the devs are unable to track down the cause of the problems.
Aerowinder said:
The statement is not false. I think FreeGS3 hasn't been updated for 4.5 months? Maybe not the best example. And I still think you should use as few automated tools as possible where flashing is concerned (Goo/ROM Manager).
It can be easy to wipe the wrong partition in CWM, if you are careless or illiterate. In the 6 months that I've used it (nearly every day), I have never once wiped the wrong partition, or my entire device. Never had a backup that wouldn't restore.
I like some of what TWRP offers. But I still experience showstopping bugs with it on my device. At this time, the devs are unable to track down the cause of the problems.
Click to expand...
Click to collapse
Don't get me wrong, I've used CWM on many devices for years and even have a premium license for ROM Manager but I've seen a number of ROMs explicitly say not to use CWM, FreeGS3 was just the first that came to mind. I don't flash often because quite frankly, I have no problems with Wicked v8 and see no reason to switch to anything else.
And I am neither careless nor illiterate but I have accidentally borked things using CWM before in the past (it was a modified CWM Touch recovery) and I was not happy.
I think most of the complaints about CWM these days though come from CWM Touch, not regular CWM. Sorry TWRP has issues for you.
OK, so I'm getting a new issue, I changed to AOKP and I had problems with the ROM saying I needed to wipe data, I did, the issue persisted for few reboots, now apps won't install, and for some reason the /data folder still displays apps from my previous ROM ugh I don't know what's happening
Oh and for some reason the app exchange service kept force closing
Sent from my Nexus 7 using xda premium
eggydrums said:
OK, so I'm getting a new issue, I changed to AOKP and I had problems with the ROM saying I needed to wipe data, I did, the issue persisted for few reboots, now apps won't install, and for some reason the /data folder still displays apps from my previous ROM ugh I don't know what's happening
Oh and for some reason the app exchange service kept force closing
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Which recovery? Try erasing data, cache, and system three times each and reinstalling the ROM... If that doesn't work you might consider doing a back up of everything internally stored on your phone and then wiping the internal storage entirely and starting over.
EtherealRemnant said:
Which recovery? Try erasing data, cache, and system three times each and reinstalling the ROM... If that doesn't work you might consider doing a back up of everything internally stored on your phone and then wiping the internal storage entirely and starting over.
Click to expand...
Click to collapse
I tried. I think for some reason, the recovery isn't wiping data, even though it says so. I'm using twrp
Managed to install apps through the play website, still no go with the play store app though
Sent from my Nexus 7 using xda premium
eggydrums said:
I tried. I think for some reason, the recovery isn't wiping data, even though it says so. I'm using twrp
Managed to install apps through the play website, still no go with the play store app though
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Hmmm... Have you tried doing it through CWM? Its starting to sound like your partitions are messed up.
EtherealRemnant said:
Hmmm... Have you tried doing it through CWM? Its starting to sound like your partitions are messed up.
Click to expand...
Click to collapse
I think that's a possibility I just tried through clockwork, and it's all good now but exchange service fcs here and there
Sent from my Nexus 7 using xda premium
eggydrums said:
I think that's a possibility I just tried through clockwork, and it's all good now but exchange service fcs here and there
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Did you fix permissions?
EtherealRemnant said:
Did you fix permissions?
Click to expand...
Click to collapse
I tried while I was in twrp, it failed, something about a an error "failed to chmod data/data/ email.apk" (not exactly like that)
Sent from my Nexus 7 using xda premium

[Q] Phone Locking Up

I'm running LiquidSmooth ROM and even with a complete wipe and re-install of the ROM my phone will randomly lock up. Can't replicate it on demand and it could take a few days before it does it. Sometimes it happens a couple times a day, and sometimes it'll go a week without locking up. It always when the screen is off so I can't wake the phone up and have to pull the battery to get it back in a working state. Any ideas on what it could be? I'm open to any suggestions and will provide any info needed.
Open terminal emulator (get from store if you haven't already) and type this:
Getprop ro.bootloader
Tell us what it says.
It could be an app you are using causing issues.
Do you restore anything from backups? Titanium, nandroid or otherwise?
Sent from my SGH-T999 using xda premium
Is this the first custom ROM you've flashed? How about the first 4.2 ROM? Did the others run fine?
DocHoliday77 said:
Open terminal emulator (get from store if you haven't already) and type this:
Getprop ro.bootloader
Tell us what it says.
It could be an app you are using causing issues.
Do you restore anything from backups? Titanium, nandroid or otherwise?
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
T999UVDLJC - I restored some apps via titanium backup like google music and some other various apps, but I didn't restore the data with it; just the app. I thought it was due to using autostarts and maybe had an app/service stopped and was causing the issue, but after the wipe and reinstall of the ROM, I didn't re-install autostarts and it still happened.
zeekx4 said:
Is this the first custom ROM you've flashed? How about the first 4.2 ROM? Did the others run fine?
Click to expand...
Click to collapse
I don't recall if it happened on the stock ROM as I didn't have it long enough for it to lock up. Actually, I take that back. It did lock up with the stock ROM, but was rooted. I've flash ROMs on previous phones I've owned, but this is the first custom ROM on this phone specifically. The stock ROM was 4.1 so yeah, this is the first 4.2.x ROM.
Sounds like you're restoring an incompatible app, or you didn't wipe data prior to changing roms.
Try flashing, but do not restore the apps. Reinstall them clean via the play store.
We're you restoring them as system apps, or user apps?
Sent from my SGH-T999 using xda premium
Sorry for the long delay. I tried another ROM, pac man, and it locked up within 2 hours of using it and no apps installed yet (except for google apps). I was watching logcat today and I see a ton of messages saying "unknown permissions". I tried the fix permissions option from CWM, but I'm still seeing those messages in logcat. I'm going to leave my phone hooked up to my PC and logcat running hoping maybe I can catch the issue via logcat when it happens. If need be, I can save logcat to a file for review.
DocHoliday77 said:
Sounds like you're restoring an incompatible app, or you didn't wipe data prior to changing roms.
Try flashing, but do not restore the apps. Reinstall them clean via the play store.
We're you restoring them as system apps, or user apps?
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
If you're still having problems with it, and especially if it happens on different roms, you should Odin flash the latest stock firmware (root66 ok), and wipe everything. Run clean and stock for a while. If it continues after this it's probably a hardware issue.
Sent from my SCH-I535 using Tapatalk 4
It only happens when the phone is idle/sleeping (screen off, not being used). While actually using it, it never locks up. Do you happen to have a link to the stock rom/firmware handy? If not, I can search for it. Could I have rooted the phone incorrectly? Could it be an issue with the partitions? Any ideas on how to track down the hardware problem?
Also, I see what seems to be a lot of errors in logcat, but I don't know if these are legit or not.
DocHoliday77 said:
If you're still having problems with it, and especially if it happens on different roms, you should Odin flash the latest stock firmware (root66 ok), and wipe everything. Run clean and stock for a while. If it continues after this it's probably a hardware issue.
Sent from my SCH-I535 using Tapatalk 4
Click to expand...
Click to collapse
bloodfilledwater said:
It only happens when the phone is idle/sleeping (screen off, not being used). While actually using it, it never locks up. Do you happen to have a link to the stock rom/firmware handy? If not, I can search for it. Could I have rooted the phone incorrectly? Could it be an issue with the partitions? Any ideas on how to track down the hardware problem?
Also, I see what seems to be a lot of errors in logcat, but I don't know if these are legit or not.
Click to expand...
Click to collapse
I honestly don't know a lot about non-touchwiz roms, but from all the bugs people mention it wouldn't surprise me at all to see a lot of errors in your logical.
You can find my firmware thread linked in my Sig, and stickied in development. It's probably not anything specific you did. It's hard to say for sure. If it's only happening while asleep, it may be the kernel. But still, I think flashing stock to test is the best option. If it stops happening you will know for sure it's not the hardware. Before trying to track it down, first determine if it's even likely.
Sent from my SCH-I535 using Tapatalk 4
DocHoliday77 said:
I honestly don't know a lot about non-touchwiz roms, but from all the bugs people mention it wouldn't surprise me at all to see a lot of errors in your logical.
You can find my firmware thread linked in my Sig, and stickied in development. It's probably not anything specific you did. It's hard to say for sure. If it's only happening while asleep, it may be the kernel. But still, I think flashing stock to test is the best option. If it stops happening you will know for sure it's not the hardware. Before trying to track it down, first determine if it's even likely.
Sent from my SCH-I535 using Tapatalk 4
Click to expand...
Click to collapse
So, I downloaded the stock 4.3 OTA ROM and flashed it. All problems are solved. No issues, but now I'd like to try to re-root the phone and try again, but from what I've read you can't downgrade from 4.3.

Twrp error

I tried to update my rom with Twrp and after I flashed I got a message saying, it appears your phone is not rooted, do you want to install superuser. I've been using Twrp on this phone for over a month and never had any issues. This however was the first time I just flashed a rom update as opposed to a new rom, so I didn't wipe anything.???? Any ideas why? Also after that happened I opened super su and it asked to update binaries. I haven't seen that since I originally installed super su. Thanks for any input I can get.
Sent from my SPH-L710 using xda app-developers app
Updating binaries is very common. If your using one of the new CM style aosp roms they have superuser built in and you have to go in settings and turn it on.you don't need to download a super user app.
Remember search is your best friend, Have a great day!

Categories

Resources