Database Users

[Q] root not working well

Hello, i have a gt-n8010 tablet and just updated it to 4.4.2, from 4.1.2 i had root, worked any method cwm or autoroot, but in this version cant make root work well, i use SuperSU as root app, i do this: (debugging is on)
1 install SuperSU through autoroot (using odin) it installs and everthing goes well, reboots and it says something about disabling knox i just hit yes
2 install pro and configure the SuperSU app,
but at some point after using the app (granting root access), when i access the SuperSU interface it tells me that SuperSU has to update the "su" binary it asks me "normal" or "CWM", i hit normal as always because i didnt install CWM recovery, but this time fails installation and closes the app unlike version 4.1.2 wich didnt have any problem, and doesnt let me to access the app interface because it keeps telling me about updating binary, but when an app asks for root access it still asks me to grant it, and any app previously root granted stays granted.
the apps i use with root are: root explorer, root uninstaller, game killer, triangle away
wich seems strange is that root explorer, root uninstaller and triangle away once i grant root access they work fine, i can access root folders and modify them, uninstall system apps and even reset flash count, but game guardian, game killer and gamecih dont work as they should, they open well but cant use them to read memory and change any ingame value.
gamecih just never shows that has root access even if i granted it and doesnt respond to hotkey
game guardian opens and appears to work but when searching for a value shows 0 results everytime, every game
and game killer opens, but the message saying "Rooted" never shows and after like 20 seconds it closes and opens again in an infinite loop without letting me use it, it also doesnt respond to hotkey.
i have also tried the CWM recovery method and install SuperSU through recovery, it install without problem and just as previous method after some time of use it tells me that SuperSU has to update binary and fails installation and still cant use apps like game killer, i go back to CWM recovery and reinstall it, it reinstalls but this second time, it tells me something about disable recovery flash i just hit yes and after that it warns me about root access loss and ask me to fix it, wich i say yes, then i hit reboot now and everything goes well, but same problem, updating binary problem and no game killer type apps.
i have tried uninstalling every knox app, but still the same. i like to hack games rooting for anything else doesnt matter, any idea what can be causing this? and how to solve it?

do you disable KNOX?

Same Problem without knox.
What can I do? Many apps don't work.
Gesendet von meinem GT-N8000 mit Tapatalk

Weird issue: superuser doesn't work anymore but still have root access

Hi All,
For some reason, just in the past week or so, with no changes to my vs980 except updating twrp to 2.8.1, i've lost all capability of superuser apps but all the apps that have that require root access continue to work. I use Carbon ROM, am on 4.4.4 and do my own builds. It has it's own built in SU but I've been using SuperSU. When a new app tries to get su access via SuperSU, the "grant" button won't press so the app eventually gets denied.
I uninstalled SuperSU and now only using the built in SU app that comes with Carbon ROM. It doesn't seem to be doing anything. No logs are being generated (yes, they are turned on) and I get no toast notifications when apps request root access. But they all still work fine... which seems very odd.
What does all this mean? Can the new twrp be causing it? How can I get SU apps to work again? I've run "root checker" and it says I have root. But when I first run the app, it never asks for root access.
Thanks.

How to troubleshoot logs of a bootloop failure

I've had my Note 4 for a while and after a few Lollipop update incidents I finally after a lot of hesitation decided to root my phone (with the TWRP bootloader) and disable the update notifier. Since then, I've always stuck to the latest stock version of KitKat 4.4.4.
Since I've rooted my phone, I made the following modifications that require root priviliges: I installed XPrivacy mod, YouTube AdAway mod, NoSafeVolumeWarning mod, PlayPermissionsExposed mod, and CrappaLinks mod for the Xposed framework. I also installed Titanium backup to freeze/uninstall the updater and AdAway. After XPosed was installed I had to change a line in /system/build.prop to 'ro.securestorage.support=false' to make 'S Health' work again. I did that with the 'FX' app.
That's it, I had made no more modifications and the phone seemed to work quite well for a month or so.
Two days ago I decided to try out Instagram, I've been quite wary with social apps but figured Instagram shouldn't hurt and everything was fine. Then I installed a bunch of dating apps, I started with Match.com and Tinder. Tinder didn't work because it required FB and Match didn't work because it refused to, probably because of denied permissions with XPrivacy so I gave up on them and uninstalled them.
But I also installed OkCupid and Motesplatsen and enjoyed playing around with these apps. They didn't seem to interfere with XPrivacy and worked rather fine. Motesplatsen was rather intense with sending me notifications of girls who watched my profile and sent me (rather strange) messages whereas OkCupid was rather calm.
Then something strange happened.
Yesterday I started noticing that the battery was draining considerably faster than normal during normal day. It was almost empty whereas it usually is half full after a full day, I also noticed that the phone was unusually warm. I forgot to put it on the charger and woke up today with a dead phone. I put it on charge and after about an hour the battery was full again.
When I tried to turn on the phone it was stuck on boot loop. I first tried disabling XPosed by "touch /data/data/de.robv.android.xposed.installer/conf/disabled" using the 'terminal' tool in the TWRP bootloader. It didn't help. I tried flushing the cache/dalvik cache but it didn't work either. Then I did a total factory reset, but that didn't work. I noticed that during boot, the phone froze so hard that it doesn't even respond to button pushes. I had to take out the battery to reboot (that's one reason why I never will buy S6).
So then I decided to flash the phone with stock KitKat once again using Odin and that finally restored the phone.
Now, here's one of my questions, how can things go so bad with a phone that not even a factory reset will fix it? We're talking stock firmware here, albeit it is rooted.
What boot logs could be worth looking into when such a thing occurs and what is the easiest way to extract them? The terminal tool in the bootloader seems promising, plus I saw a 'copy log to SD' option which I neglected this time.
I'm puzzled, does anyone know what happened? I made no root modifications in the process of installing these apps and they don't advertise themselves as needing root privileges. How can a seemingly inconspicuous app directly from Google play **** a phone up like that?

After restart, some apps stuck

Hello, I have a strange problem, after every reboot of the phone, some apps are not working anymore, they either stuck at the loading screen or force close. For example, Genshin Impact (game) gets stuck, Faceapp force closes, other apps like a banking app and a local provider app are also affected. Clearing cache/data does't help, only reinstalling fixes this.
Open bootloader, rooted, stock rom 11.0.2.2IN11BA, stock kernel, no magisk modules, upgrade from 11.0.1.1 didn't fixed it. Model IN2023, when I got the phone it had the global rom and I installed the eu after rooting. Any ideas what the problem could be?

Perpatoura said:
Hello, I have a strange problem, after every reboot of the phone, some apps are not working anymore, they either stuck at the loading screen or force close. For example, Genshin Impact (game) gets stuck, Faceapp force closes, other apps like a banking app and a local provider app are also affected. Clearing cache/data does't help, only reinstalling fixes this.
Open bootloader, rooted, stock rom 11.0.2.2IN11BA, stock kernel, no magisk modules, upgrade from 11.0.1.1 didn't fixed it. Model IN2023, when I got the phone it had the global rom and I installed the eu after rooting. Any ideas what the problem could be?
Click to expand...
Click to collapse
Are you indeed still rooted? I get this issue if I turn on systemless and then don't reboot.
Or if I lose root if I haven't actually installed the patched image after booting the patched image.
Check to see if you're actually still rooted.
If you are then turn on systemless.

dladz said:
Are you indeed still rooted? I get this issue if I turn on systemless and then don't reboot.
Or if I lose root if I haven't actually installed the patched image after booting the patched image.
Check to see if you're actually still rooted.
If you are then turn on systemless.
Click to expand...
Click to collapse
Hello, thank you for your answer, I still have root, just checked. What do I have to do to turn on systemless? Just press on "systemless hosts" in magisk settings?

Root System Access Issues Resolved

A while back I was able to achieve root on my ZTE 2050 (which also goes by about 20 other names.) I was continuously having issues with the phone locking up, I couldn't access the root files, as well as many other issues. I tried installing BusyBox to see if that helped. I was able to access the root files, but if I moved or deleted anything, the phone would begin to freeze up again. Every time it froze and I would restart it, I would lose cell service until I rebooted the phone between 4 - 6 times. Finally what I figured out is that the folder BusyBox was installing the applets in, /system/sbin, were fighting against Magisk and it's BusyBox. After deleting BusyBox and reinstalling it in /system/bin and applying the option to have it reinstalled upon every boot, I have no issues accessing and modifying the root system. Don't know if anyone else has had trouble with that, but if so I hope this helps. Now if I could only figure out why I lose stock recovery once the phone is rooted or could even install TWRP I'd be doing pretty good.