Is my Phone now rooted or not? - Xiaomi Poco F1 Questions & Answers

I remember how i rooted my phone a month ago to install 4K 60 FPS and it worked. But somehow now the root checker says my phone is not rooted, so i rooted my phone with many Magisk's, twrp and DisableForceEncryption_Treble files and followed many youtube videos that aren't that old, but the phone always says the phone is not rooted. Btw. i was on the MIUI 10.2.2.0 when i rooted my device and i'm still on this version. And i'm sorry when this question was many times asked, but i didn't found anything helpful. And i'm sorry when there is something wrong with my english.

Open magisk manager then open root checker
Add magisk manager to auto-start and remove battery optimizations

It is still saying my phone is not rooted.

Your phone is rooted, man. You probably denied root access for root checker which is why it shows your phone doesn't have root access. An app wouldn't know whether or not your phone has root access unless you allow it.
Tap the 3 dash button on the top left corner in Magisk Manager, then go to Superuser. Check if you've disabled root access for the root checker app.

Root checker has superuser permissions.

You're rooted, i feel some apps didn't work propperly after become super user, and feel like was unrooted, some apps like edpjoyand, usbjoystickcenter, and some others was not working like they supposed to work, then manage to force the selinux to permissive and now everything it's working perfectly

K, but i can't use BuildProp Editor cause it is saying that my device is not rooted.

You tried clearing cache after installing magisk, if not give that a try. Something similar has happened to me last year, after installing magisk in twrp clearing cache/dalvik cache solved it for me
Skickat från min POCOPHONE F1 via Tapatalk

Thank you, but it didn't worked for me

What does it say in magisk manager? Does it show that magisk is installed? Post a screenshot

https://ibb.co/0FGZGsX
https://ibb.co/RjgLfZC

Related

SGS3 re-rooting problem

Hi all,
I've rooted my SGS3 via ODIN with CF-Root-SGS3-v6.3. Everything went good and I had root in seconds. One thing I've noticed that this method is installing SuperSU app instead of SuperUser (which I was using on Motorola Defy). It didn't make any difference for me, however after some time I discovered that not all applications works with SuperSU. For instance xMissedCallPatch for exDialer don't even ask for admin permissions. Permission access window from SuperSU just don't POP UP so I can't give that app a root permissions. There was some more examples but can't remeber which one. TitaniumBackup and few other works good.
And here comes the problem:
I wanted to change from SuperSU to SuperUser, so I've installed SuperUser from market, however that does not make him as default app to handle root requests. So... I went to SuperSU settings and clicked "Switch Superuser application". That deleted SuperSU as default app to handle root, but again it didn't make SuperUser as default also. So, none of SuperSU or SuperUser were default apps to handle root
So, trying to make this out, I've uninstalled SuperUser and made ODIN again with CF-Root-SGS3-v6.3. All procedure went as expected but SuperSU still isn't default app to handle root. Now when I'm launching TitaniumBackup (for instance) it just says that it can't work because it has no root rights. As previously no Permission access window from SuperSU.
Do you have any ideas?
OK, my fault.
I've accidentaly used CF-Root-SGS3-v6.3 instead of v6.4. After ODIN with v6.4 everything works great. Even apps which hadn't popups from SuperSU previously now work. For example xMissedCallPath for exDialer now works somehow.
Sorry to bother you all, topic to close.

Strange problems with my root, could really use seom help

Hey Guys,
I'm having an issue with my root and I cant seem to figure out, the device is the first gen Asus Infinity TF700. So, my root has been a bit wonky for a few months now, hadn't really payed much mind to it as all my apps that need root were working fine but trying to install some new apps that need root would always tell me that I dont have root (even though it passes rootchecker and everything)
The other day I tried installing another app that needs root and it ran extremly slowly, when trying to perform certain things it would tell me I dont have root and at one point it said to install SuperSu and update binaries.
I had Superuser installed, I opened it up and noticed that it hadn't added any new apps to the allow list and the last log entry was months old, it seems like it's being blocked by something else or it just broke.
So fine I uninstalled Superuser and installed SuperSu, ran SUperSu and it asked to update my binaries, I hit continue then selected normal for the update method and it failed, tried several times all with the same result - it fails and exist when I hit OK.
I found some info saying that Busy Box Installer could be used to possibly fix this issue, I downloaded BusyBox Installer, opened up the app and hit Install but it also fails to install, I tried selecting the advanced installer method but that just fails loading the advanced installer.
Another thing I found was people saying that this could be caused by a full system partition, mine is 93% full but withouth properly working root I can't delete any system apps, I tried installing system app remove and it tells me I don't have root.
You guys know way more abut this then I do so maybe this all points to one thing? It kind of seems like it all points to one underlying problem, if anyone could help me figure this out I would really appreciate it.

[Q] CleanMaster Root Access Failed

I have already given root access to the app Clean Master. Under the 'Autostart Manager' page, I tried to remove apps that autostart by itself. However, the app pop out a message indicating 'Failed to Grant Root' and reminded me to grant root access.
I went back to the superuser app, it was indicated that root access has been granted.
Any way to solve this problem?
I have been having this same issue on rooted stock gs4. It's temperamental when it comes to root I've noticed. One day I was able to turn it app off of auto start and when I installed a new app it wouldn't let me do it and su says I'm granted
I'm experiencing the same issues. Auto Start Manager is the only feature that has this issue.
Sent from my SPH-L710 using XDA Free mobile app
yoongkc said:
I have already given root access to the app Clean Master. Under the 'Autostart Manager' page, I tried to remove apps that autostart by itself. However, the app pop out a message indicating 'Failed to Grant Root' and reminded me to grant root access.
I went back to the superuser app, it was indicated that root access has been granted.
Any way to solve this problem?
Click to expand...
Click to collapse
I always face this issue also, what I do as a temporary fix is, go to the SuperSU app, then "Forget" Clean Master, open Clean Master and try to disable an app from Auto starting, grant root and the app will be disabled I hope it works for you too
I am glad I am not the only one having this issue. I recently updated an app via the play store and clean master told me it was auto starting. I tried to block it, but it keeps telling me root access failed and to grant it. Well I've granted it root 18 times now and it still says root failed. I have tried everything to get it to work...clear logs, tell superSU to forget clean master, give it global default, etc. Nothing seems to work and it's pissing me off.
Unfortunately this does not work for me.
I have granted root access according to SuperSU Pro however when trying to stop autostarting apps in Clean Master it reminds me to allow access.
I even get a popup massage from SU stating that the app got granted root access.
Whats happening here? Does anyone have a work around?
Deleting Cleanmaster in SuperSU doesnt help. It is always the same unfortunately.
Best Regards
J
I too also have problems with the autostart function in Clean Master on my Optimus Zone II
First of all, if you've root then you shouldn't use clean master. That's so naive.
About the permissions. Even after root your system partition stays in read only mode. I'm guessing this okay. You should check that out first.
Re:Re: [Q] CleanMaster Root Access Failed
Vtrendzzy said:
First of all, if you've root then you shouldn't use clean master. That's so naive.
About the permissions. Even after root your system partition stays in read only mode. I'm guessing this okay. You should check that out first.
Click to expand...
Click to collapse
Ok, (I know Im gunna reget this), but why?, in your option, should Clean Master NOT be used, since it need so many "root" functions in order to work? Ive used it for years. Rooted or no, (mostly rooted), and why do all the "autostart" apks, (ROM Toolbox, Autostarts, Autostart Manager,etc) work just fine. I've tryied it with r-w on system on, sooooo....next...?
DerDoktorEsq said:
Ok, (I know Im gunna reget this), but why?, in your option, should Clean Master NOT be used, since it need so many "root" functions in order to work? Ive used it for years. Rooted or no, (mostly rooted), and why do all the "autostart" apks, (ROM Toolbox, Autostarts, Autostart Manager,etc) work just fine. I've tryied it with r-w on system on, sooooo....next...?
Click to expand...
Click to collapse
I can't argue over this. Best options for you 1. Root Cleaner (high priority) 2. SD Maid Pro (medium priority)
See the difference yourself.
fix?
Has anyone figured out what the issue is here? It worked just fine on cm12 but stock Lilli nope. Root issues for sure it must have something to do with system partition. Has anyone fixed this issue?
dillweedinc said:
Has anyone figured out what the issue is here? It worked just fine on cm12 but stock Lilli nope. Root issues for sure it must have something to do with system partition. Has anyone fixed this issue?
Click to expand...
Click to collapse
Has anyone figured out what the issue is here?²
hey..the main culprit is supersu app
yoongkc said:
I have already given root access to the app Clean Master. Under the 'Autostart Manager' page, I tried to remove apps that autostart by itself. However, the app pop out a message indicating 'Failed to Grant Root' and reminded me to grant root access.
I went back to the superuser app, it was indicated that root access has been granted.
Any way to solve this problem?
Click to expand...
Click to collapse
Clean master is not working on 2.46(I mean the autostart manager) I noticed this yesterday..i flashed a new Rom first it was having Supersu 2.46 version in which CM was not working but after flashing Supersu 2.49 CM is working plus in Google store supersu 2.46 beta is there which won't work...my clean master started working again normally like before after installing SuperSU 2.49...so try flashing or installing supersu 2.49
Link for supersu zip (Flashable zip)
http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Clean master root access
wow. cool...,ill try that,
thanx
it's supersu problem
StoneyJSG said:
I am glad I am not the only one having this issue. I recently updated an app via the play store and clean master told me it was auto starting. I tried to block it, but it keeps telling me root access failed and to grant it. Well I've granted it root 18 times now and it still says root failed. I have tried everything to get it to work...clear logs, tell superSU to forget clean master, give it global default, etc. Nothing seems to work and it's pissing me off.
Click to expand...
Click to collapse
Just go thru my above post..it will definitely work..so give it a try... flashing new supersu 2.49 resolved the problem for me.?
Yep its working again. I tried 2.48 cuz somebody said it worked for them, but i had no luck there. 2.49 did the trick, thx for letting us know in the thread.
tycoon78[stoner] said:
Clean master is not working on 2.46(I mean the autostart manager) I noticed this yesterday..i flashed a new Rom first it was having Supersu 2.46 version in which CM was not working but after flashing Supersu 2.49 CM is working plus in Google store supersu 2.46 beta is there which won't work...my clean master started working again normally like before after installing SuperSU 2.49...so try flashing or installing supersu 2.49
Link for supersu zip (Flashable zip)
http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Click to expand...
Click to collapse
Its working for me too.
Thanks tycoon78 for the tip
RE:RE:RE: [Q] CleanMaster Root Access Failed/SuperUser
The new Super SuperUser Apk 2.49 from chainfire, did not work for my CleanMaster blocking apks from autostarting on my little optimus 2....:crying: any other suggestions?
Ahhh! Thank you so much tycoon! It works for me after updating super user!
QUOTE=Alison.Souza;60674697]Its working for me too.
Thanks tycoon78 for the tip [/QUOTE]
DerDoktorEsq said:
The new Super SuperUser Apk 2.49 from chainfire, did not work for my CleanMaster blocking apks from autostarting on my little optimus 2....:crying: any other suggestions?
Click to expand...
Click to collapse
I just rooted my s6 edge and was having the same issue with 2.46. Luckily when I updated to 2.49, I was unable to block the autostartup apps.

How to Unroot Android Device (Samsung Galaxy Avant)

This question has probably been asked a million times before, but my circumstances are a little different. On my first attempt, I used the "unroot" option on Superuser, and it claimed my device had been cleared of root access after booting back up. However, after realizing my root apps still worked, I downloaded a root checker and confirmed my suspicion that my phone hadn't changed. Afterwards, I followed a Youtube tutorial and deleted various SU files in my system's directory, but partial root access remains. No unroot app works because Superuser can't grant full root access, and SU itself crashes upon booting when I re-download it. I've attempted re-rooting my phone so I had full root access, but that won't work either. Any suggestions?

never asks for root

Newest stable version works but doesn't ask for root privilege. Rooted using Chainfire's supersu.
Also happened to me, but here's the deal, just follow the new setup wizard without root access anyways, then when you have access to the app settings you can change to root mode and force to greenify anything, or try to activate any settings that require root, super su should prompt, then you can grant root access, it's working fine for me now
Best of luck
Sent from my Sony Xperia SP using XDA Labs
Which settings require root? I've toggled all the settings and none of them made it ask for root.
olliebean said:
Which settings require root? I've toggled all the settings and none of them made it ask for root.
Click to expand...
Click to collapse
For me it asked for root when I changed settings under "wake up tracking and cut off".
If nothing happens to you reboot your phone and try again, you could also check to see if there is any denied requests of greenery in super su app and manually grant it.
Sent from my Sony Xperia SP using XDA Labs
ghst7 said:
Also happened to me, but here's the deal, just follow the new setup wizard without root access anyways, then when you have access to the app settings you can change to root mode and force to greenify anything, or try to activate any settings that require root, super su should prompt, then you can grant root access, it's working fine for me now
Best of luck
Click to expand...
Click to collapse
Oh it works just fine. It's just not showing up in Supersu as having root access.
I have the same problem.
After I updated from the market today I can't get greenify to properly request root access.
When I run it I tell it I'll rooted, see it saying it's requesting root access but supersu doesn't prompt then says it can't get root. Same results with rebooting.
In supersu there are no request prompts from greenify. I deleted the greenify access to see if that would get it to reprompt but it still says can't get root and supersu shows no requests in logs.
Other apps still work fine in supersu.
Edit --
Interesting, I disabled the module in xposed and when it prompts for root supersu pops right up. So I gave it access that way but logs show that once the module is reenabled it never asks for root.
Weird
Can't get root privilege
I've updated it trough the market and followed the wizard. When its given the choice i selected root but response is> there is no root<, so i decided to recheck it manual as suggested in the app)Same problem, no root request popup, not showing in su(chainfire). Also wake up tracker does not remember it's setting.
What i did so far:
Reinstall greenify, reinstall SU, deselect Geenify module and select again in xposed.
Reboot
Never it shows up in SU or get root request permission popup.
On a samsung s4 gt 505 root xposed greenify donate pack. kitkat 4.4.2
rockah said:
I've updated it trough the market and followed the wizard. When its given the choice i selected root but response is> there is no root<, so i decided to recheck it manual as suggested in the app)Same problem, no root request popup, not showing in su(chainfire). Also wake up tracker does not remember it's setting.
What i did so far:
Reinstall greenify, reinstall SU, deselect Geenify module and select again in xposed.
Reboot
Never it shows up in SU or get root request permission popup.
On a samsung s4 gt 505 root xposed greenify donate pack. kitkat 4.4.2
Click to expand...
Click to collapse
Got mine to work by deselecting Greenify module in Xposed and rebooting. Started Greenify app and it said to either to activate the Xposed module or select non-root mode. I clicked on Greenify settings and tried to change Xposed settings and a popup window asked if I wanted to activate Xposed module. I selected yes, Xposed started, I selected Greenify module and rebooted. During the bootup process, Greenify asked for root permissions.
A similar process worked for me: deactivated the Xposed module, rebooted, started the Greenify app, then I went into the Greenify settings and turned on the enhanced wake up tracker, which caused Greenify to request root. Granted permission, then reactivated the Xposed module and rebooted again. Checked in SuperSU that Greenify had permissions, then I just had to re-enable the Xposed based features in the Greenify settings.
Having done that, however, I see from the SuperSU logs that Greenify isn't actually requesting any root permissions since I re-enabled the Xposed module. I suspect the new version is using Xposed for all its root access and no longer needs root permissions for the app in Boost (Xposed) mode.
Lots of guessing here.
I tried doing a plain re-install. Greenify comes up with the new setup process, tells me it's going to request root access and then does... nothing. Then it complains it can't get root access and stays there so can't install anymore. Completely broken. Unless I want to go without root which is not my intention as I don't want to use it with a reduced feature set.
dreinulldrei said:
Lots of guessing here.
I tried doing a plain re-install. Greenify comes up with the new setup process, tells me it's going to request root access and then does... nothing. Then it complains it can't get root access and stays there so can't install anymore. Completely broken. Unless I want to go without root which is not my intention as I don't want to use it with a reduced feature set.
Click to expand...
Click to collapse
Read prior posts for further guidance. Seems others have got it to work. I had zero/nada/no problems on latest betas w/Xposed and SuperSU 2.76. YMMV.
What can I say.... I do a clean install, the app says it's going to acquire root and then fails. I'd call this a bug... Honestly.
dreinulldrei said:
What can I say.... I do a clean install, the app says it's going to acquire root and then fails. I'd call this a bug... Honestly.
Click to expand...
Click to collapse
Using SuperSU? If ≥ 2.77 try 2.76 (terminal build by ChainFire).
BTW - I tend to agree there's a glitch somewhere given complaints; Q&A will hopefully allow dev to isolate/rectify.
I'm using SuperSU v2.78 with the latest Greenify v3.0 build 5 beta and it working fine.
Wonder if I should drop back to v2.76 and how to even do that without losing root?
Davey126 said:
Using SuperSU? If ≥ 2.77 try 2.76 (terminal build by ChainFire).
BTW - I tend to agree there's a glitch somewhere given complaints; Q&A will hopefully allow dev to isolate/rectify.
Click to expand...
Click to collapse
---------- Post added at 03:55 PM ---------- Previous post was at 03:43 PM ----------
This page has a link to the SuperSU v2.76 zip on ChainFire's site, which can be flashed with TWRP, etc depending on your phone.
https://www.progeeksblog.com/download-supersu-for-android/
I have not tried to flash it myself.
divineBliss said:
I'm using SuperSU v2.78 with the latest Greenify v3.0 build 5 beta and it working fine.
Wonder if I should drop back to v2.76 and how to even do that without losing root?
Click to expand...
Click to collapse
If life is good don't change anything! I'm not out to skewer SuperSU v2.78; the problems I and a few others experienced are likely outliers with various contributing factors. That said, SuperSU 2.76 has been rock solid on my devices as have most of ChainFire's previous releases. Sticking with what works for now.
rockah said:
I've updated it trough the market and followed the wizard. When its given the choice i selected root but response is> there is no root<, so i decided to recheck it manual as suggested in the app)Same problem, no root request popup, not showing in su(chainfire). Also wake up tracker does not remember it's setting.
What i did so far:
Reinstall greenify, reinstall SU, deselect Geenify module and select again in xposed.
Reboot
Never it shows up in SU or get root request permission popup.
On a samsung s4 gt 505 root xposed greenify donate pack. kitkat 4.4.2
Click to expand...
Click to collapse
Did all of the above and it doesn't show in supersu. Strange thing is Greenify works with root+boost selected just fine. Doesn't show in su logs either.
If you moved Greenify apk to
"/system/priv-app", it won't need to ask SuperSU for root and won't be in the SuperSU log. Is that the case here?
craigevil said:
Did all of the above and it doesn't show in supersu. Strange thing is Greenify works with root+boost selected just fine. Doesn't show in su logs either.
Click to expand...
Click to collapse
divineBliss said:
If you moved Greenify apk to
"/system/priv-app", it won't need to ask SuperSU for root and won't be in the SuperSU log. Is that the case here?
Click to expand...
Click to collapse
Hum - assumed those with Xposed framework left Greenify as a user app. Perhaps not the case for all. As you pointed out one would not necessarily expect a prompt for privileged access if the app resides in "/system/priv-app" depending on how the active SU manager (typically SuperSU) is configured.
I don't think you can do anything to the SuperSU configuration to make it so apps in priv-app have to ask for SU permission. I have other apps in there and have never seen them ask and they are not in SuperSU log either.
I moved my Greenify apk into priv-app because it wasn't clear to me that there was nothing to gain by doing that as I already had Xposed installed and working. Have since moved it back to original folder in /data/app/.
Davey126 said:
Hum - assumed those with Xposed framework left Greenify as a user app. Perhaps not the case for all. As you pointed out one would not necessarily expect a prompt for privileged access if the app resides in "/system/priv-app" depending on how the active SU manager (typically SuperSU) is configured.
Click to expand...
Click to collapse
- Android 6.0.1
- SuperSU 2.78 (systemless root)
- Xposed
- latest Greenify Beta from PlayStore (in Root+Boost mode)
- NOT installed as system app or anything.
Same problem here -- Greenify never asks for root, is not listed in SuperSU logs. Greenify initially had root access iirc, but one of the updates from PlayStore removed it.
Nevertheless Greenify seems to be working fine though.
EDIT: All other root apps on my phone (OnePlus 2, stock OxygenOS 3.1) don't have any issues with root access.
Sent from my OnePlus 2 using Tapatalk

Categories

Resources