Related
Hi
I have been using clockworkmod superuser on stock 4.3 with no problems. However I have just flashed a new kernel and am now getting the message that the SU binaries are out of date. I have tried re-flshing the superuser.zip with CWM but still have the same message and of course no root. Is it possible to replace superuser with the latest supersu and see if that gets my root back. If so how I do it and will I then be able to unistall the clockwork superuser app once supersu is up and running.
Thanks
Andy.
g1dtf said:
Hi
I have been using clockworkmod superuser on stock 4.3 with no problems. However I have just flashed a new kernel and am now getting the message that the SU binaries are out of date. I have tried re-flshing the superuser.zip with CWM but still have the same message and of course no root. Is it possible to replace superuser with the latest supersu and see if that gets my root back. If so how I do it and will I then be able to unistall the clockwork superuser app once supersu is up and running.
Thanks
Andy.
Click to expand...
Click to collapse
just flash the latest supersu flashable. search google for supersu, youll find it asap. its better than the latest superuser.
simms22 said:
just flash the latest supersu flashable. search google for supersu, youll find it asap. its better than the latest superuser.
Click to expand...
Click to collapse
cool wikll give it a try once flashed will it replace the current superuser app or will i have to uninstall remove it manually?
g1dtf said:
cool wikll give it a try once flashed will it replace the current superuser app or will i have to uninstall remove it manually?
Click to expand...
Click to collapse
itll add the supersu app
simms22 said:
itll add the supersu app
Click to expand...
Click to collapse
By that do you mean it replaces the superuser that is currently installed or adds it as an additional app. Sorry for the confusion but still a little confused with the various methods of obtaining root with the various superusers etc.
g1dtf said:
By that do you mean it replaces the superuser that is currently installed or adds it as an additional app. Sorry for the confusion but still a little confused with the various methods of obtaining root with the various superusers etc.
Click to expand...
Click to collapse
itll add the supersu app, youll probably have to uninstall the superuser app by yourself.
simms22 said:
itll add the supersu app, youll probably have to uninstall the superuser app by yourself.
Click to expand...
Click to collapse
Thanks for the help and will let you know how I get on once I get it downloaded and installed.
Installed the zip and everything is now working ok and I have root back. The supersu app replaced the origional superuser app so nothing to uninstall/delete.
Thanks Again
Andy.
g1dtf said:
Installed the zip and everything is now working ok and I have root back. The supersu app replaced the origional superuser app so nothing to uninstall/delete.
Thanks Again
Andy.
Click to expand...
Click to collapse
sweet
Had to flash back to SuperSU v2.79.
Anyone else facing the issue??
DUDE!!!, wrong section
did you even check supersu threads before posting in here ?, check out this
AL_IRAQI said:
DUDE!!!, wrong section
did you even check supersu threads before posting in here ?, check out this
Click to expand...
Click to collapse
1. Both 2.8 and 2.81 won't work on our device, mostly 2.81
2. I had it semi working on 2.8 but when I have updated to 2.81 I've lost root and couldn't re-install it
3. you can either revert back to 2.79 SR3 which work just fine or try Magisk v 12.0
4. I moved to magisk and so far so good, at least until chainfire will get his bugs rooted
SuperSu 2.81 running just fine on my device
Sent from my Nexus 6P using XDA-Developers Legacy app
akashkyh said:
Had to flash back to SuperSU v2.79.
Anyone else facing the issue??
Click to expand...
Click to collapse
Same thing happened to me. Flashed 2.79 SR3 to get root back. 2.82 has been released but I haven't tried it.
Edit: Updated to 2.82 and it works fine on all my devices - Nexus 6P, Nexus 2013, GS4 & Acer A500 tab.
newkydawg said:
Same thing happened to me. Flashed 2.79 SR3 to get root back. 2.82 has been released but I haven't tried it.
Click to expand...
Click to collapse
Installed 2.82 today morning.. think seems fine now.. no unroot problem.
wizardwiz said:
1. Both 2.8 and 2.81 won't work on our device, mostly 2.81
2. I had it semi working on 2.8 but when I have updated to 2.81 I've lost root and couldn't re-install it
3. you can either revert back to 2.79 SR3 which work just fine or try Magisk v 12.0
4. I moved to magisk and so far so good, at least until chainfire will get his bugs rooted
Click to expand...
Click to collapse
Could you write a short tutorial about magisk installation. Tried 3 times to install it, but nothing happened "no root".
N2G47O
IOne_Rus said:
Could you write a short tutorial about magisk installation. Tried 3 times to install it, but nothing happened "no root".
N2G47O
Click to expand...
Click to collapse
Actually a tutorial would be very short one.
* I have downloaded the zip installation file version 12.0
* copy it to your sdcard in your phone
* boot into custom recovery mode
* flash the zip file via the recovery
That's it.
It's the same as flashing chainfire supersu zip file.
wizardwiz said:
Actually a tutorial would be very short one.
* I have downloaded the zip installation file version 12.0
* copy it to your sdcard in your phone
* boot into custom recovery mode
* flash the zip file via the recovery
That's it.
It's the same as flashing chainfire supersu zip file.
Click to expand...
Click to collapse
Did the same but no results.
Will try again.
Thanks
IOne_Rus said:
Did the same but no results.
Will try again.
Thanks
Click to expand...
Click to collapse
That's the only thing i've done.
You can also download the magisk utility from the play and use it to root your device.
https://play.google.com/store/apps/details?id=com.topjohnwu.magisk
IOne_Rus said:
Did the same but no results.
Will try again.
Thanks
Click to expand...
Click to collapse
Extract the boot.img from your ROM and flash before magisk zip. It always clears up any issues I'm having. If your using custom kernel will need to flash again.
I have the same problème so I just flashed magisk but seems like I can't change the permissions
blop135 said:
I have the same problème so I just flashed magisk but seems like I can't change the permissions
Click to expand...
Click to collapse
As suggested before, flash your boot.img and the re-apply the root of your choice.
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
Hi, just as the title says everytime i reboot my devices after successfully installing magisk through a patched boot image file i lose root. Root works i also checked with the root checker when i don't reboot my device. What is causing this ?
Try boot to twrp [yes, just boot if you don't want to flash it] and flash magisk thru it.
tanapak1 said:
Try boot to twrp [yes, just boot if you don't want to flash it] and flash magisk thru it.
Click to expand...
Click to collapse
thanks i'll give it a try
emiljano539 said:
thanks i'll give it a try
Click to expand...
Click to collapse
Flash magisk 16.7
tanapak1 said:
Try boot to twrp [yes, just boot if you don't want to flash it] and flash magisk thru it.
Click to expand...
Click to collapse
now its working after i flashed the magisk by twrp thanks
ProchyGaming said:
Flash magisk 16.7
Click to expand...
Click to collapse
i just flashed by twrp and its working now
Doesn't twrp unable ota updates?
so, i had my op 6t bricked and in a bootloop to fastboot
i managed to recover my data through twrp, but couldnt get lineage to run again, so i used the msm tool to downgrade to android 9 oos
now when i try to install a custom recovery i the phone freezes in this "the bootloader is unlocked warning"-screen
no idea why i cant boot into a custom recovery, with a unlocked oem
my plan is to get it back to run lineage os with twrp recovery
can u maybe help me?
I wasn't able to boot into twrp since a11. Had to install from magisk in booted oos using twrp installer. Not sure why it wouldn't work if you downgraded but maybe not using the correct twrp? Sounds like things are messed up. I would start from scratch and get a clean oos on both slots. If you can't boot into twrp then root with magisk and install directly from magisk manager with the installer.
So I am on 11.1.2.2, how do I get twrp installed on this. I cannot get twrp to boot past the logo. I have been trying to Flash HAVOC but have been stuck
Easiest way is to get the newest twrp that just came out. Root with magisk. And using the twrp installer not the image just install directly from magisk.
Brettroth said:
Easiest way is to get the newest twrp that just came out. Root with magisk. And using the twrp installer not the image just install directly from magisk.
Click to expand...
Click to collapse
Which magisk? latest or canary
Gytole said:
Which magisk? latest or canary
Click to expand...
Click to collapse
I use the latest
and are we talking 3.6.0_9? orr...
Gytole said:
and are we talking 3.6.0_9? orr...
Click to expand...
Click to collapse
Yeah that's the newest. Older ones work but that one has a lot of good changes
Okay. I am familiar witht that I am just currently unrooted. So I have downloaded the latest magisk apk and twrp zip, just gotta figure out how to root.
Gytole said:
Okay. I am familiar witht that I am just currently unrooted. So I have downloaded the latest magisk apk and twrp zip, just gotta figure out how to root.
Click to expand...
Click to collapse
You need to flash a magisk modded boot in fastboot from your oos. Someone has a post somewhere in here hosting them I'll try to get a link for you.
so fastboot flash boot_a and b like usual for the patched boot image and then once in android just open magisk, then install the latest twrp from there? I think that's what put me in crash dump mode before
Gytole said:
Okay. I am familiar witht that I am just currently unrooted. So I have downloaded the latest magisk apk and twrp zip, just gotta figure out how to root.
Click to expand...
Click to collapse
Are you on 11.2.1.1?
Brettroth said:
Are you on 11.2.1.1?
Click to expand...
Click to collapse
11.1.2.2 I believe?
Gytole said:
11.1.2.2 I believe?
Click to expand...
Click to collapse
Sorry that's what I meant. Here is modded boot. Flash in fastboot.
Brettroth said:
Sorry that's what I meant. Here is modded boot. Flash in fastboot.
Click to expand...
Click to collapse
Done. Now I boot into android, open magisk, and install the recovery?
Gytole said:
Done. Now I boot into android, open magisk, and install the recovery?
Click to expand...
Click to collapse
Yessir
Brettroth said:
Yessir
Click to expand...
Click to collapse
Work out for ya?
Wow. Alright. You all need to remember this. Msm only flashes to slot a. NOT slot b. So, if you were previously in A10 or A11 and flash msm OOS 9, there will be issues unless you local update the same android version to slot b. You can't have 2 different android version on your slots unless you're using dualboot mod. Like on 8 pro, crashdump happens when twrp is installed if both slots aren't using the same android version