Question Messed up my root.. How to recover - Google Pixel 7 Pro

So I have root via root checker and root beer is telling me I have root. All my apps that required root are working, but in magisk I can't access the modules.
No new apps are being promoted for root.
When I try to adb flash , it says there's a write error.
Latest everything on a p7p

What do you mean you can't access modules? Are the modules enabled or disabled in magisk? For new apps wanting root, when you look at the permissions in magisk, is root granted/enabled for those apps?
What write error? You need to be more specific with regards to your issues

Related

[Completed] is supersu needed 4 rom install?

all these google play apps say : supersu permission needed, but the root features work 100% ok without supersu on my phone(its like my phone automaticly give them permission)
question is does superuser do anything and is it needed for safestrap install of rom(would it work without it?)
Superuser/SuperSU/etc only manages root access. If your device is already rooted and you don't have a root manager, then every app can get root.
The description for SU in the XDA-University dictionary explains it better than I could.

Change Root Method on Custom ROM [B368 KangVIP]

Everytime I'm rebooting, superSU seem's to be integrated again, but I'd like to root with the magisk version to easily enable /disable root.
Thanks for your support guys.

Busybox and root checker report device not rooted...? Am using root req's apps

Unlocked bootloader. Installed twrp successfully. Flashed majisk successfully yet busybox will not install and root checker reports root not obtained... Huh?
Is this because root checker and busybox look for supersu to be in a certain place and when they can't find it they report no root?
If majisk is essentially root then why does it fail the checks? I am able to install and use apps that require root... What gives? (Sorry for being dumb)
kerryh420 said:
Unlocked bootloader. Installed twrp successfully. Flashed majisk successfully yet busybox will not install and root checker reports root not obtained... Huh?
Is this because root checker and busybox look for supersu to be in a certain place and when they can't find it they report no root?
If majisk is essentially root then why does it fail the checks? I am able to install and use apps that require root... What gives? (Sorry for being dumb)
Click to expand...
Click to collapse
IDK about the root situation, but the way I usually install busybox on the pixel is goto the play store and search busybox and pick the one by meefik. Then open it and change the install location from system/xbin to just system/bin (so remove the x)
kerryh420 said:
Unlocked bootloader. Installed twrp successfully. Flashed majisk successfully yet busybox will not install and root checker reports root not obtained... Huh?
Is this because root checker and busybox look for supersu to be in a certain place and when they can't find it they report no root?
If majisk is essentially root then why does it fail the checks? I am able to install and use apps that require root... What gives? (Sorry for being dumb)
Click to expand...
Click to collapse
This is the best BusyBox installer in my opinion.
From this thread. Works for system or systemless installations.
Flash in TWRP.

Root Kindle Fire HD 10

I was able to use Kingoroot for PC to root my Fire HD 10. Updated to the newest Firmware. It would say it was rooted. But, Trying to give permissions and checking with root checker was not successful and said there was no root. I installed SuperSU apk it says the binary is occupied. So I Uninstalled the superuser apk. that was installed by Kingoroot and tried to change the build prop with a root browser text editor and it was successful so apparently it roots but superuser is not working to grant or deny permissions. It automatically grants permissions does not even open up superuser so its kinda dangerous but it is rooted and working. My experience is that kingoroot superuser must be Uninstalled for root to work. I used twrp manager to backup my recovery img., and boot img. I am going to try to build a recovery for it but I'm not In a hurry plus I'm not sure if it will flash afterwards anyways but if you want root, Kingoroot for pc and Uninstalled the kingoroot superuser apk it installs and you will have it
Installed magisk manager installed zip direct (recommended) it bricked the fire. And then I adb sideloaded the update and now I'm back in business reasonably easy to do but I do not recommend magisk at this time .
Going to try xposed next
Couldn't get it to install says it's arm device tries to install and says it's an arm64 device. Plus has to be flashed in recovery and one hasn't been built yet
You can't manage Kingoroot su binary using SuperSU.
If you not install SuperSU su binary, SuperSU apk does not working.
Try this method to install SuperSU su binary.
https://forum.xda-developers.com/showpost.php?p=75242414&postcount=99
erono said:
You can't manage Kingoroot su binary using SuperSU.
If you not install SuperSU su binary, SuperSU apk does not working.
Try this method to install SuperSU su binary.
https://forum.xda-developers.com/showpost.php?p=75242414&postcount=99
Click to expand...
Click to collapse
I installed supersu to find out if it was rooted since the root checker said it was not. the binary error was a confirmation that it was in fact rooted and it doesn't matter what superuser is used it will not allow pop up or apps to draw over other apps so when it's rooted with kingoroot it automatically grants root without a confirmation,as long as the kingoroot super user app is not installed and if SuperSU is kept installed default permission has to be set to grant for root to work. I in fact installed the SuperSU binary through an older version of the apk and it installed but still has no control over denying or granting permissions. Thanks for the advice though. I appreciate your willingness to help me
Joker1716 said:
I was able to use Kingoroot for PC to root my Fire HD 10. Updated to the newest Firmware. It would say it was rooted. But, Trying to give permissions and checking with root checker was not successful and said there was no root. I installed SuperSU apk it says the binary is occupied. So I Uninstalled the superuser apk. that was installed by Kingoroot and tried to change the build prop with a root browser text editor and it was successful so apparently it roots but superuser is not working to grant or deny permissions. It automatically grants permissions does not even open up superuser so its kinda dangerous but it is rooted and working. My experience is that superuser must be Uninstalled for root to work. I used twrp manager to backup my recovery img., and boot img. I am going to try to build a recovery for it but I'm not In a hurry plus I'm not sure if it will flash afterwards anyways but if you want root, Kingoroot for pc and Uninstalled the superuser apk it installs and you will have it
Installed magisk manager installed zip direct (recommended) it bricked the fire. And then I adb sideloaded the update and now I'm back in business reasonably easy to do but I do not recommend magisk at this time .
Going to try xposed next
Click to expand...
Click to collapse
Not trying to insult your intelligence or anything here, but you said newest firmware? Newest Fire firmware? Newest firmware isn't rootable from my understanding.
What firmware were you on when you started the root process?
Also, are you making sure that the Kingoroot "install our extra junk" box isn't checked (not sure that would prevent root success)?
It wouldn't open superuser. superuser should be set to "grant" because of how the Fire works, which it sounds like you are aware of based on your last post. I wouldn't say it's dangerous, per se.
I've followed this guide nearly a dozen times now and I've not run into the issue(s) you're having.
smam1338 said:
Not trying to insult your intelligence or anything here, but you said newest firmware? Newest Fire firmware? Newest firmware isn't rootable from my understanding.
What firmware were you on when you started the root process?
Also, are you making sure that the Kingoroot "install our extra junk" box isn't checked (not sure that would prevent root success)?
It wouldn't open superuser. superuser should be set to "grant" because of how the Fire works, which it sounds like you are aware of based on your last post. I wouldn't say it's dangerous, per se.
I've followed this guide nearly a dozen times now and I've not run into the issue(s) you're having.
Click to expand...
Click to collapse
Prompt dialog not working in amazon fire devices.
erono said:
Prompt dialog not working in amazon fire devices.
Click to expand...
Click to collapse
Set prompt to grant and fixed.
yes. mind doesnt pop up supersu granting notification too
my fire hd 10 is on 5.6.1.0
someone told me it's amazon's own security measure
stevenchun said:
yes. mind doesnt pop up supersu granting notification too
my fire hd 10 is on 5.6.1.0
someone told me it's amazon's own security measure
Click to expand...
Click to collapse
One can try this improvement :
SuperSU access workaround for Fire devices
https://forum.xda-developers.com/hd8-hd10/general/supersu-access-workaround-fire-devices-t3738269

[Q] Manually give root access to an app via terminal or any other method (SOLVED)

There's this app that needs root access but magisk wont prompt or show anything, Any help is appreciated
Hello people, i solved this issue by installing "sui", its a magisk module. Search it up on the magisk module section, Also make sure u have riru, a magisk module aswell installed

Categories

Resources