Related
I'm a bit confused. I'm on my Nexus 7 right now which is running a custom ROM. I can boot into bootloader as well as Clockwork Recovery. However when I just tried to run a backup using titanium, it told me my device is not rooted. Superuser is installed. How can this be? How do I gain root access so I can backup my apps before putting on a new ROM?
abdeviation said:
I'm a bit confused. I'm on my Nexus 7 right now which is running a custom ROM. I can boot into bootloader as well as Clockwork Recovery. However when I just tried to run a backup using titanium, it told me my device is not rooted. Superuser is installed. How can this be? How do I gain root access so I can backup my apps before putting on a new ROM?
Click to expand...
Click to collapse
Download to your Nexus 7, Chainfires SU updater package from here...
http://download.chainfire.eu/310/SuperSU/UPDATE-SuperSU-v1.04.zip
Reboot into CWM/TWRP (whichever recovery you're running) and flash it...
(You should find it in the /download folder)
Reboot as normal... you should be rooted.
Rgrds,
Ged.
GedBlake said:
Download to your Nexus 7, Chainfires SU updater package from here...
http://download.chainfire.eu/310/SuperSU/UPDATE-SuperSU-v1.04.zip
Reboot into CWM/TWRP (whichever recovery you're running) and flash it...
(You should find it in the /download folder)
Reboot as normal... you should be rooted.
Rgrds,
Ged.
Click to expand...
Click to collapse
So I followed what you said but I was still getting the no root error when launching titanium. Then I went into settings and uninstalled the SuperSU app and viola! Everything is working now
You probably had root disabled under development settings, as is the default. By installing and uninstalling SuperSU, you may have overridden that security setting. It is important to check whether an app is actually handling such requests; otherwise any app could get root without your knowledge.
Sent from my Nexus 7 using Tapatalk HD
I was updating superSU on my note 3 after root. I tried to use game killer, only to get the message that root wasn't available. I loaded up superSU and was told that the binary couldn't be found... I downloaded a root checker and it said that root access was there... So I unrooted and re rooted. Same deal.
I'm not sure how to fix the issue.
Can anyone please help
(SM-N9005)
BallaratBloke81 said:
I was updating superSU on my note 3 after root. I tried to use game killer, only to get the message that root wasn't available. I loaded up superSU and was told that the binary couldn't be found... I downloaded a root checker and it said that root access was there... So I unrooted and re rooted. Same deal.
I'm not sure how to fix the issue.
Can anyone please help
(SM-N9005)
Click to expand...
Click to collapse
Somethings wrong with your su I think. Have to given privillages to game killer in su?
Sent from Galaxy Note 3 SM-N9005
thahim said:
Somethings wrong with your su I think. Have to given privillages to game killer in su?
Sent from Galaxy Note 3 SM-N9005
Click to expand...
Click to collapse
I have given it privileges. But when I open supersu says there is something wrong with su binary.
BallaratBloke81 said:
I have given it privileges. But when I open supersu says there is something wrong with su binary.
Click to expand...
Click to collapse
Have you deleted then given Super SU privileges back? I find installing a new rom can sometimes screw with them....
ultramag69 said:
Have you deleted then given Super SU privileges back? I find installing a new rom can sometimes screw with them....
Click to expand...
Click to collapse
When I first got the phone it had a rom full of provider bloatware. I flashed another stock Roma to get rid of it. Then I flashed xnote and decided OT wasn't for me, so I went back to stock (without bloats)
BallaratBloke81 said:
When I first got the phone it had a rom full of provider bloatware. I flashed another stock Roma to get rid of it. Then I flashed xnote and decided OT wasn't for me, so I went back to stock (without bloats)
Click to expand...
Click to collapse
Delete the apps from SU then when prompted give them permission again - like normal you will need to re-open them again and get the "Grant root access" prompt from SU...This may work, has for me everytime...
Only other thing I would do if this didn't work would be re-stock and start from scratch...
ultramag69 said:
Delete the apps from SU then when prompted give them permission again - like normal you will need to re-open them again and get the "Grant root access" prompt from SU...This may work, has for me everytime...
Only other thing I would do if this didn't work would be re-stock and start from scratch...
Click to expand...
Click to collapse
Yes hello, can someone please upload the note 3 4.3 touchwiz apk, i accidentally deleted mine, so please.
ultramag69 said:
Delete the apps from SU then when prompted give them permission again - like normal you will need to re-open them again and get the "Grant root access" prompt from SU...This may work, has for me everytime...
Only other thing I would do if this didn't work would be re-stock and start from scratch...
Click to expand...
Click to collapse
I have already reflashed stock back to my phone, re rooted and the problem still exsists
Currently I'm on stock again (downloaded from sammobile)
Every time I open superSU, it tells me there is a problem with the SU BINARY (when I was rooted. I'm not trying to use super SU unrooted lol)
Just rooted again and its still the same...
Reflash stock, full wipe from stock recovery, reroot.
Or u have done a full wipe from stock recovery after flash stock firmware?
Sent from N9005, somewhere on this earth.
antique_sonic said:
Reflash stock, full wipe from stock recovery, reroot.
Or u have done a full wipe from stock recovery after flash stock firmware?
Sent from N9005, somewhere on this earth.
Click to expand...
Click to collapse
Yeah, done all of that. Is there a way to manually wipe the SU binary and reinstall? The root checker app says root access is allowed
Is there another way to see if it's the SU binary or game killer having issues?
BallaratBloke81 said:
Yeah, done all of that. Is there a way to manually wipe the SU binary and reinstall? The root checker app says root access is allowed
Is there another way to see if it's the SU binary or game killer having issues?
Click to expand...
Click to collapse
If you attempts to fix root access denied on game killer then it won't work. Gamekiller/gamecih/gameguardian doesn't work with android 4.3 and above.
I however tried gamecih with cm based rom last week & it worked
Rosli59564 said:
If you attempts to fix root access denied on game killer then it won't work. Gamekiller/gamecih/gameguardian doesn't work with android 4.3 and above.
I however tried gamecih with cm based rom last week & it worked
Click to expand...
Click to collapse
OK, so you're saying those kind of apps will no longer work?
What about the SU binary issue?
BallaratBloke81 said:
OK, so you're saying those kind of apps will no longer work?
What about the SU binary issue?
Click to expand...
Click to collapse
Its not a superSU issue, guess the dev needs to update the gamekiller app. Do you have root privileges with other root apps?
gee2012 said:
Its not a superSU issue, guess the dev needs to update the gamekiller app. Do you have root privileges with other root apps?
Click to expand...
Click to collapse
Not as of yet. The photo of the warning I posted, comes up when I open SuperSU
BallaratBloke81 said:
Not as of yet. The photo of the warning I posted, comes up when I open SuperSU
Click to expand...
Click to collapse
Try unrooting superSU from the app itself and reflash the latest (1.94 i think) superSU.zip in recovery or with Flashify (if compatible ,Playstore) flash CF Root in downloadmode. Hope that helps.
gee2012 said:
Try unrooting superSU from the app itself and reflash the latest (1.94 i think) superSU.zip in recovery or with Flashify (if compatible ,Playstore) flash CF Root in downloadmode. Hope that helps.
Click to expand...
Click to collapse
I can't even get into the app to unroot
BallaratBloke81 said:
OK, so you're saying those kind of apps will no longer work?
What about the SU binary issue?
Click to expand...
Click to collapse
Your SU binary got issue but yes even you solve it those apps won't work.
Try uninstall it from playstore. There is also flashable supersu
http://download.chainfire.eu/204 but I never use it either or maybe reroot
gee2012 said:
Try unrooting superSU from the app itself and reflash the latest (1.94 i think) superSU.zip in recovery or with Flashify (if compatible ,Playstore) flash CF Root in downloadmode. Hope that helps.
Click to expand...
Click to collapse
ES explorer can't get root access either.
Should I flash superSU.zip straight over the top using recovery? Or is that not a good idea?
Rosli59564 said:
Your SU binary got issue but yes even you solve it those apps won't work.
Try uninstall it from playstore. There is also flashable supersu
http://download.chainfire.eu/204 but I never use it either or maybe reroot
Click to expand...
Click to collapse
I have unrooted (flashing stock rom using recovery) and rerooted (using CF auto root... Or whatever it's called) many times.
I currently have the 4.4.2 Google Play edition rom by Danvdh installed. I was performing a backup to flash the new 4.4.3 through CWM.
After the backup, there was a message that root may be lost and if I should fix it. I selected 'Yes'.
After the reboot, I no longer have root access. I have tried to re-root with motochopper and it continues to fail.
Can I restore a backup to regain my root? Or is there another way to regain my root access?
I tried searching for similar issues but could not find one that addressed my problem specifically.
Thanks in advance.
FIXED!!!
Not sure how or why, but SuperSu got messed up. Then I tried to open it, I was receiving an error that no binaries were found. I tried re-installing the apk without success. I then flashed the SuperSu zip in CWM recovery mode. Once it restarted, I was then able to open SuperSu and my root was back.
tuffgong2k3 said:
Not sure how or why, but SuperSu got messed up. Then I tried to open it, I was receiving an error that no binaries were found. I tried re-installing the apk without success. I then flashed the SuperSu zip in CWM recovery mode. Once it restarted, I was then able to open SuperSu and my root was back.
Click to expand...
Click to collapse
If you are using old CWM you would get the message saying "you root may be lost "and asking you to fix it before reboot. Never said "yes" to that questions. That will mess up your super su. If you read through the general section you could see some post about this.
sway8966 said:
If you are using old CWM you would get the message saying "you root may be lost "and asking you to fix it before reboot. Never said "yes" to that questions. That will mess up your super su. If you read through the general section you could see some post about this.
Click to expand...
Click to collapse
Ahhh, thanks sway. I obviously did not find that section. I thought I had the latest CWM, but I guess I didn't. Time to update.
hi people,
i am on firmware 800d20y, just bought the d800 today. i did the 'brute force' method, which initially worked, but after a short while, i lost root access. I literally have no idea what happened, the stump root app still says 'device is rooted', but the root checker app says i don't have root access. I tried a couple of different apps to check for root access, but to no avail.
any help, ANY at all to get root would help immensely! I'm trying to get a custom recovery (prob twrp) so i can flash a cm12 nightly rom...
im still a little new to this, any help would be appreciated!
You could try LGroot
samalamadumalama said:
hi people,
i am on firmware 800d20y, just bought the d800 today. i did the 'brute force' method, which initially worked, but after a short while, i lost root access. I literally have no idea what happened, the stump root app still says 'device is rooted', but the root checker app says i don't have root access. I tried a couple of different apps to check for root access, but to no avail.
any help, ANY at all to get root would help immensely! I'm trying to get a custom recovery (prob twrp) so i can flash a cm12 nightly rom...
im still a little new to this, any help would be appreciated!
Click to expand...
Click to collapse
Did you install SuperSU from playstore after you rooted?
Really now said:
Did you install SuperSU from playstore after you rooted?
Click to expand...
Click to collapse
yup, right after the root checker.
samalamadumalama said:
yup, right after the root checker.
Click to expand...
Click to collapse
look if supersu is perhaps blocking all the apps.
wulsic said:
look if supersu is perhaps blocking all the apps.
Click to expand...
Click to collapse
no, it keeps asking to update the binary, which never works.
samalamadumalama said:
no, it keeps asking to update the binary, which never works.
Click to expand...
Click to collapse
Try to flash supersu through recovery
Do you mean through a custom recovery, or the stock one? I'm only asking because I don't have a custom recovery yet. And if you mean through the stock recovery, I don't know how to do that :/
Hi guys, I have successfully rooted using temporary TWRP + modded magisk method, but now I gain root and checked via Root checker. But the problem is most of the root functions don't work as /system is read-only. Any idea?
Ya i have an idea.. Happened to me as well. I tried almoat everything but system won't be accessible anywhere.. I followed the same tutorial and installed magisk 13.4.
The only solution i could find was flash the latest factory image, and root again using supersu. I used the AIO tool by ghpranav and have got my phone rooted with xposed working without any issues.
zazzy24 said:
Ya i have an idea.. Happened to me as well. I tried almoat everything but system won't be accessible anywhere.. I followed the same tutorial and installed magisk 13.4.
The only solution i could find was flash the latest factory image, and root again using supersu. I used the AIO tool by ghpranav and have got my phone rooted with xposed working without any issues.
Click to expand...
Click to collapse
I also fixed the issue. I flash the modified boot image and I am now gaining proper root access + Xposed. Get it working using Super SU, idk why Magisk keep failing thou. Was wanted to give Magisk a try, but it doesn't work properly on our device.
Cool:good:
Xposed isn't working with magisk? I was planning to install it
amithiel said:
Xposed isn't working with magisk? I was planning to install it
Click to expand...
Click to collapse
Only with SuperSU as I know.
Sent from my Mi A1 using Tapatalk
Guys, this is Magisk from Pixel. You can't expect that it is working. I wrote to MagiskDevs already, they are working on a own Version for Mi A1. Use for that time normal SuperSU (Xposed works normally )
how to??
soralz said:
I also fixed the issue. I flash the modified boot image and I am now gaining proper root access + Xposed. Get it working using Super SU, idk why Magisk keep failing thou. Was wanted to give Magisk a try, but it doesn't work properly on our device.
Click to expand...
Click to collapse
Hay how do you Fix the Read only Issue? can you please share the Modified Boot image and process for same, thanks
maxsan20 said:
Hay how do you Fix the Read only Issue? can you please share the Modified Boot image and process for same, thanks
Click to expand...
Click to collapse
https://desktop.firmware.mobi/device:1748
Just root with replacing the boot image then you are good to go.
soralz said:
https://desktop.firmware.mobi/device:1748
Just root with replacing the boot image then you are good to go.
Click to expand...
Click to collapse
Hi,
I have TWRP installed and unrooted, what I need to do please?
We7dy said:
Hi,
I have TWRP installed and unrooted, what I need to do please?
Click to expand...
Click to collapse
You need flash back stock boot image first, due to some limitations you can't have TWRP and SuperSU root at the same time. If you don't have the stock boot image. I suggest download the ROM from MIUI and then flash it. You can choose "flash_all_except_storage" option, this will keep your data.
http://en.miui.com/download-333.html
After flashing. Reboot back to fastboot and then:
Code:
fastboot oem unlock
After that just run root.bat from the cf-auto root folder you downloaded and wait for it to automatically reboot your phone. You should have root now, if you wish you can download SuperSU from the store.
soralz said:
You need flash back stock boot image first, due to some limitations you can't have TWRP and SuperSU root at the same time. If you don't have the stock boot image. I suggest download the ROM from MIUI and then flash it. You can choose "flash_all_except_storage" option, this will keep your data.
http://en.miui.com/download-333.html
After flashing. Reboot back to fastboot and then:
After that just run root.bat from the cf-auto root folder you downloaded and wait for it to automatically reboot your phone. You should have root now, if you wish you can download SuperSU from the store.
Click to expand...
Click to collapse
Ok, thanks. It's not possible to do that via TWRP? I don't have PC. Currently my bootloader is unlocked, I have TWRP and I'm unrooted.
We7dy said:
Ok, thanks. It's not possible to do that via TWRP? I don't have PC. Currently my bootloader is unlocked, I have TWRP and I'm unrooted.
Click to expand...
Click to collapse
I actually tried before, and I tell you the results:
Option 1 TWRP installed + Rooted with Magisk
= Pretty much useless as /system is read-only. Every root app doesn't function, unless it is system-less. But system-less modules nearly all doesn't work as the Magisk version too old. And this method won't trip safetynet
Option 2 no TWRP + Rooted with SuperSU (cf-root method) -- Currently using this state
= Got proper root access, Xposed works but will trip safetynet
Option 3 TWRP installed + Rooted with SuperSU (cf-root method)
= Don't try this, will cause your phone stuck in boot loop
soralz said:
I actually tried before, and I tell you the results:
Option 1 TWRP installed + Rooted with Magisk
= Pretty much useless as /system is read-only. Every root app doesn't function, unless it is system-less. But system-less modules nearly all doesn't work as the Magisk version too old. And this method won't trip safetynet
Option 2 no TWRP + Rooted with SuperSU (cf-root method) -- Currently using this state
= Got proper root access, Xposed works but will trip safetynet
Option 3 TWRP installed + Rooted with SuperSU (cf-root method)
= Don't try this, will cause your phone stuck in boot loop
Click to expand...
Click to collapse
So not possible via TWRP? Get root access and remove TWRP? I just need that... The root.
We7dy said:
So not possible via TWRP? Get root access and remove TWRP? I just need that... The root.
Click to expand...
Click to collapse
The best bet and possible trouble free is to first download the stock ROM from MIUI, reflash it and then root.
soralz said:
The best bet and possible trouble free is to first download the stock ROM from MIUI, reflash it and then root.
Click to expand...
Click to collapse
:/ Can't root with TWRP without system read only...
We7dy said:
:/ Can't root with TWRP without system read only...
Click to expand...
Click to collapse
It's possible to root without CF-Auto-Root? Why can't flash SuperSu directly with TWRP?
We7dy said:
It's possible to root without CF-Auto-Root? Why can't flash SuperSu directly with TWRP?
Click to expand...
Click to collapse
No, it will cause your phone stuck it boot loop if you try to flash the SuperSU zip directly from the official ChainFire site. I think probably is the AB partitioning problem or some sort (unsure). As I said you need to run CF-Auto root to get proper root access, otherwise flashing Magisk through TWRP will makes most of the root apps does not work properly unless it also uses system-less root function.
soralz said:
No, it will cause your phone stuck it boot loop if you try to flash the SuperSU zip directly from the official ChainFire site. I think probably is the AB partitioning problem or some sort (unsure). As I said you need to run CF-Auto root to get proper root access, otherwise flashing Magisk through TWRP will makes most of the root apps does not work properly unless it also uses system-less root function.
Click to expand...
Click to collapse
Ok I have TWRP installed can I use directly CF auto root?
We7dy said:
Ok I have TWRP installed can I use directly CF auto root?
Click to expand...
Click to collapse
No if you want proper root with CF-auto root you must not have TWRP installed. You either choose TWRP + Magisk (non-working root) or no TWRP but with SuperSU (working root, Xposed works too).
Follow the instruction here to get you on track:
https://forum.xda-developers.com/showpost.php?p=74326169&postcount=2