Database Users

Unroot G4 PLUS XT1643 running on custom ROM to flash magisk

Hi! Is there any way to unroot,so that I can have magisk flashed on MOTO G4 PLUS XT1643 (currently running on AOKP ROM)

UdayaKudulla said:
Hi! Is there any way to unroot,so that I can have magisk flashed on MOTO G4 PLUS XT1643 (currently running on AOKP ROM)
Click to expand...
Click to collapse
Download SuperSU app from play store. Grant root access. Do full unroot. Disable root from development reboot. Now you can flash magisk.

How can u get into the development reboot? Btw the the su app says su binary is missing.

UdayaKudulla said:
How can u get into the development reboot? Btw the the su app says su binary is missing.
Click to expand...
Click to collapse
He meant to say,
Disable Root access from Development settings,
Flash SuperSU latest ZIP 2.78 SR5,
Turn on device,
Open SuperSU ->settings -> full unroot
Reboot,
Then you can install magisk,
Always take backup...?
Edit: app saying, binary is missing..! Did you try to delete "su" from xbin..?

UdayaKudulla said:
How can u get into the development reboot? Btw the the su app says su binary is missing.
Click to expand...
Click to collapse
Yeah my bad. Autocorrect got me there. It's developer settings. And also don't worry about binary missing. Just do full unroot. Then reboot
---------- Post added at 07:03 AM ---------- Previous post was at 06:56 AM ----------
__Madddy said:
He meant to say,
Disable Root access from Development settings,
Flash SuperSU latest ZIP 2.78 SR5,
Turn on device,
Open SuperSU ->settings -> full unroot
Reboot,
Then you can install magisk,
Always take backup...?
Edit: app saying, binary is missing..! Did you try to delete "su" from xbin..?
Click to expand...
Click to collapse
I have found that installing SuperSU is not necessary to use app for full unroot. At least in case of cm root

guessingagain said:
Yeah my bad. Autocorrect got me there. It's developer settings. And also don't worry about binary missing. Just do full unroot. Then reboot
---------- Post added at 07:03 AM ---------- Previous post was at 06:56 AM ----------
I have found that installing SuperSU is not necessary to use app for full unroot. At least in case of cm root
Click to expand...
Click to collapse
It took more than half an Hour but the app says uninstalling and nothing's happening.

UdayaKudulla said:
It took more than half an Hour but the app says uninstalling and nothing's happening.
Click to expand...
Click to collapse
It takes some time but that is too long. Is your ROM clean flashed? Also did you provide root access to SuperSU app?

guessingagain said:
It takes some time but that is too long. Is your ROM clean flashed? Also did you provide root access to SuperSU app?
Click to expand...
Click to collapse
Yes. I did a clean flash and even provided root access to the Super SU app.

UdayaKudulla said:
Yes. I did a clean flash and even provided root access to the Super SU app.
Click to expand...
Click to collapse
Have you provided root access to any other app? Tell me exactly what you did.
As an alternative Also if this doesn't work try going to TWRP and deleting system/xbin/su and /system/bin/su? To see if that will help?

guessingagain said:
Have you provided root access to any other app? Tell me exactly what you did.
As an alternative Also if this doesn't work try going to TWRP and deleting system/xbin/su and /system/bin/su? To see if that will help?
Click to expand...
Click to collapse
Thanks mate! It worked through full unroot(SuperSU)..I had to disable root access for other app.(didn't notice,greenify was given root access)

super su

Anyone know why it wont stay

Ssys no batty

Says no binary installed

pbedard said:
Says no binary installed
Click to expand...
Click to collapse
1st, did you flash the SU file? 2nd, what rom are you on?

Yes 5 times 2 im using dev digitals rom im on sprint

pbedard said:
Yes 5 times 2 im using dev digitals rom im on sprint
Click to expand...
Click to collapse
The latest SU File? which is SR3 2.79? if it didnt work try the Unsu.zip file to remove SU and then flash the SU file again. see if that works.

Devdigital help me thanks

pbedard said:
Devdigital help me thanks
Click to expand...
Click to collapse
did you flashed the unsu file then flashed the Su file?

Devdigital tols me replash the rom cause ite not using super su its using majiskSU

pbedard said:
Devdigital tols me replash the rom cause ite not using super su its using majiskSU
Click to expand...
Click to collapse
AAhh i see. Now i know where you are standing at. you are using magisk. But do you have magisksu ? or keep having supersu as main root but magisk installed? . What i mean to say is, when you go into the magisk app, in the 2nd box of the main screen, does it shows supersu as root method? or magisksu? if it is magisksu then you dont need supersu, now, if it does says supersu, then you do have to fix the issue of supersu to unroot by using supersu function and then go directly into recovery mode and flash magisksu once again.

It says majisksu

pbedard said:
It says majisksu
Click to expand...
Click to collapse
then you dont need su (unless you want it). It is because you already have magisksu (which is pretty much doing the same as su). one overrides the other and then one gets thrown out. Usually to install magisk manually, one does as follows:
1) install magisk app from playstore
2) give supersu access (granted to magisk su)
3) use unroot function in supersu
4) flash magisk zip in recovery mode.
Now, there are other methods to achieve magisksu but the point is that maisksu has changed the binary (which is what SuperSU is telling you that you dont have).But that doesnt mean you are not rooted. you are already rooted with magisk and can achieve pretty much anything that you could achieve with supersu. (it will ask you for prompts asking you whether you want to give su access to "x" or "y" app. etc... Now, if you want SuperSU, you could try to flash the magisk uninstaller. Then do the process of rooting that has been specified for your phone. That should return the SU binary to normality . (this assuming you try to unroot and then flash SU back but didnt work)

hey guys bought my ls997 used. has root because i get the flash screen (untrusted)and twrp is installed and working. how do i find out which to flash ? any advantages to use supersu over magisk ?
i installed magisk manager and it states no root found.

Majisk u have to turn root access on majisk works alot better

@pbedard
Did the help @jinkerz9430 gave work for you?

Yws

SuperSU error: SU Binaries occupied

SuperSU updated yesterday like normal, required updating binaries and I used TRWP. I updated the app with my Titanium Backup. Another app updated today but when I tried to back it up Titanium had lost root. Opened SuperSU and got SU Binaries occupied. Later today, I powered up again, SuperSU and Titanium both had new updates. I thought the problem was reported and fixed but it still does the same thing! :crying: Anybody??
EDIT: A known issue, https://forum.xda-developers.com/ap...6-09-01supersu-v2-78-release-t3452703/page165

I had the same problem as well after SuperSU binary update
SuperSU 2.82 no loger have ability to replace Kingoroot and now it says "SU Binaries occupied". Really Chainfire?
SuperSU 2.79 was the best version.

evildog1 said:
I had the same problem as well after SuperSU binary update
SuperSU 2.82 no loger have ability to replace Kingoroot and now it says "SU Binaries occupied". Really Chainfire?
SuperSU 2.79 was the best version.
Click to expand...
Click to collapse
Got this error too after installing 2.82. What I did was to Reinstall ("Cleanup to reinstall from Google Play" option in Settings) and then installed the 2.79 apk I have as backup. Got a prompt that SU binaries needed to be updated and so I did. Update was successful and seemed to do the trick since I'm not receiving the error and still have root.

evildog1 said:
I had the same problem as well after SuperSU binary update
SuperSU 2.82 no loger have ability to replace Kingoroot and now it says "SU Binaries occupied". Really Chainfire?
SuperSU 2.79 was the best version.
Click to expand...
Click to collapse
I am also having the same problem...
Now what to do...?

ashesall said:
Got this error too after installing 2.82. What I did was to Reinstall ("Cleanup to reinstall from Google Play" option in Settings) and then installed the 2.79 apk I have as backup. Got a prompt that SU binaries needed to be updated and so I did. Update was successful and seemed to do the trick since I'm not receiving the error and still have root.
Click to expand...
Click to collapse
I have staright talk stylo 2 lgl82vl 5.1.1 lollipop think thats issue? I cant really find info on my stylo 2 version.. Rooted phone with kingroot 4.6 and reboots itself and losses root within minutes of completing root. Any help for this rookie tech. Guy...thanks

ashesall said:
Got this error too after installing 2.82. What I did was to Reinstall ("Cleanup to reinstall from Google Play" option in Settings) and then installed the 2.79 apk I have as backup. Got a prompt that SU binaries needed to be updated and so I did. Update was successful and seemed to do the trick since I'm not receiving the error and still have root.
Click to expand...
Click to collapse
No... It doesnt work... Failed to update binaries... And asks to update the app...

yashasvi.malik said:
No... It doesnt work... Failed to update binaries... And asks to update the app...
Click to expand...
Click to collapse
The last SuperSU version I had before updating to 2.82 was 2.79. I was lucky I turned off automatic updates because the next SuperSU versions after 2.79 were buggy based on reviews. I updated to 2.82 because I thought bugs were already ironed out. It was a bad decision because I started having "SU Binaries occupied" error popping up. I solved this by reinstalling the 2.79 apk I had as backup.
Maybe you updated from a different SuperSU version that's why it didn't work. Make sure that you reinstalled the SuperSU apk version you were using before you upgraded to 2.82.
I've been reading the reviews and the most common reply by support is to flash the SuperSU binaries that corresponds to version 2.82. You can try that. Visit the XDA thread of SuperSU for the flashable zip.
If all things fail with SuperSU, you can try phh's Superuser as an alternative.
---------- Post added at 05:55 PM ---------- Previous post was at 05:32 PM ----------
JGene1983 said:
I have staright talk stylo 2 lgl82vl 5.1.1 lollipop think thats issue? I cant really find info on my stylo 2 version.. Rooted phone with kingroot 4.6 and reboots itself and losses root within minutes of completing root. Any help for this rookie tech. Guy...thanks
Click to expand...
Click to collapse
Sorry, I'm not an expert with these kinds of things. However, you can try visiting the XDA thread of SuperSU and ask for help there.
And also, I'll stay away from Kingroot if I were you. Search for "Kingroot malware/adware" on XDA for more information.
You can try 'phh's Superuser' as an alternative. You can also ask help there.

Install SuperSU 2.65 and update binary, then reboot, and update from Play Store, then update binary again (using "normal" option).

evildog1 said:
I had the same problem as well after SuperSU binary update
SuperSU 2.82 no loger have ability to replace Kingoroot and now it says "SU Binaries occupied". Really Chainfire?
SuperSU 2.79 was the best version.
Click to expand...
Click to collapse
This works for me:
1° Root using Kingoroot
2° Install Supersu
2° Install link2sd
3° open link2sd and found in the list Supersu, press continuolsy (not simple click) and Click "convert to system app"
4° Remove Kingoroot supersu and Kingoroot
5° Reset device
6° Open Supersu and apply binaires!

lucasgabmoreno said:
This works for me:
1° Root using Kingoroot
2° Install Supersu
2° Install link2sd
3° open link2sd and found in the list Supersu, press continuolsy (not simple click) and Click "convert to system app"
4° Remove Kingoroot supersu and Kingoroot
5° Reset device
6° Open Supersu and apply binaires!
Click to expand...
Click to collapse
this solved for me, thanks a lot!

For me root works, but SuperSU SU Binaries are still "occupied" Device: Huawei y540

for me it helped to:
* install version 2.79
* run it and follow instructions
* update to 2.82
* reboot
* 2.82 works!

delete this please

super su binaries occupied
wptski said:
SuperSU updated yesterday like normal, required updating binaries and I used TRWP. I updated the app with my Titanium Backup. Another app updated today but when I tried to back it up Titanium had lost root. Opened SuperSU and got SU Binaries occupied. Later today, I powered up again, SuperSU and Titanium both had new updates. I thought the problem was reported and fixed but it still does the same thing! :crying: Anybody??
EDIT: A known issue, https://forum.xda-developers.com/ap...6-09-01supersu-v2-78-release-t3452703/page165
Click to expand...
Click to collapse
this worked for me. https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip?retrieve_file=1. I installed the update zip from the sd card

lucasgabmoreno said:
This works for me:
1° Root using Kingoroot
2° Install Supersu
2° Install link2sd
3° open link2sd and found in the list Supersu, press continuolsy (not simple click) and Click "convert to system app"
4° Remove Kingoroot supersu and Kingoroot
5° Reset device
6° Open Supersu and apply binaires!
Click to expand...
Click to collapse
do we need to unroot the device for this first?????

akshayrrrb said:
do we need to unroot the device for this first?????
Click to expand...
Click to collapse
No.
You need to root your mobile first. Kingroot works for me.

Root Method

Beginning - 1. Step First Unlock Your Bootloader, and Flash TWRP recovery! 2. Step Boot in to recovery and Flash SU 2.62v systemless mode,(Search in google for it)
3. Step Wipe Cache, reboot. Update Superuser to lastest start app and Update Su binary, reboot 4. Step Now start app And Make sure You still have root, if not, start from 2 step.
Reboot in recovery and wipe Danvik/Cache!
End! Enjoy System less root glitch, but at some point you will lose it! Don't reboot too much!
Only works on Huawei P8 lite ALE -L21
(P.s if You want you can use my moded SU.zip file, it has SuPro 2.82v but don't worry, it has 2,62v su files)
Best Regards!

I prefer Magisk, because it includes other useful features, such as modules and Magisk Hide

RootingPro-18 said:
Beginning - 1. Step First Unlock Your Bootloader, and Flash TWRP recovery! 2. Step Boot in to recovery and Flash SU 2.62v systemless mode,(Search in google for it)
3. Step Wipe Cache, reboot. Update Superuser to lastest start app and Update Su binary, reboot 4. Step Now start app And Make sure You still have root, if not, start from 2 step.
Reboot in recovery and wipe Danvik/Cache!
End! Enjoy System less root glitch, but at some point you will lose it! Don't reboot too much!
Only works on Huawei P8 lite ALE -L21
(P.s if You want you can use my moded SU.zip file, it has SuPro 2.82v but don't worry, it has 2,62v su files)
Best Regards!
Click to expand...
Click to collapse
Can you explain why are you using too old zip from 2015 (v2.62) instead of recent like v2.82?
Are you having issues with v2.82?
Your modded zip is Chainfire work, are you playing with "fire"?

kilroystyx said:
Can you explain why are you using too old zip from 2015 (v2.62) instead of recent like v2.82?
Are you having issues with v2.82?
Your modded zip is Chainfire work, are you playing with "fire"?
Click to expand...
Click to collapse
Huawei P8 ALE-L21 do not like system mode root, it creates bootloop and i made SuperUser Apk mod for Pro version and changed Root mode detention to think You are Using System Mode root! It took a month to make it work, and now i succeed and shared it here! If You Have other question's, PM me!?

JpegXguy said:
I prefer Magisk, because it includes other useful features, such as modules and Magisk Hide
Click to expand...
Click to collapse
What is that? Can i get it on Huawei P8 Lite?

RootingPro-18 said:
What is that? Can i get it on Huawei P8 Lite?
Click to expand...
Click to collapse
The beta works well on our phone and it has the latest features so I'll point you to that. Just flash the zip through TWRP. To uninstall flash the uninstaller zip.

RootingPro-18 said:
Huawei P8 ALE-L21 do not like system mode root, it creates bootloop and i made SuperUser Apk mod for Pro version and changed Root mode detention to think You are Using System Mode root! It took a month to make it work, and now i succeed and shared it here! If You Have other question's, PM me!
Click to expand...
Click to collapse
To me takes 1 minutes to root with SuperSu Systemless mode (no issues with bootloops), downloaded from official site, and 30 seconds install SuperSu Pro apk via google play. If I understood well you find a workaround to install SuperSu Pro apk, right?

kilroystyx said:
To me takes 1 minutes to root with SuperSu Systemless mode (no issues with bootloops), downloaded from official site, and 30 seconds install SuperSu Pro apk via google play. If I understood well you find a workaround to install SuperSu Pro apk, right?
Click to expand...
Click to collapse
With System less mofe root, does not create bootloop but i require boot img, soo! You understand my point!

Working BusyBox for Oreo

I did a semi search on how to get busybox working on Oreo, found chatter of using this app for busybox but for a different phone. I figured it wouldn't hurt to try. I needed BusyBox for Cerberus app to work and block the status bar access.
I downloaded this app https://play.google.com/store/apps/details?id=ru.meefik.busybox
Go to it's settings and change your install path *if your using supersu like I am path is:
/sbin
After you set your path, install. Then reboot.
After boot the BusyBox app used states that busybox wasn't installed but when I used a BusyBox checker app it's installed and working. My Cerberus app works too and blocks the status bar from locked screen. Busybox has been working after reboots. It sticks
Anyways, busybox is working on Oreo ver.11

Question: Now that you've installed that, can you still boot TWRP on your device and have it still ask to decrypt your file system? I've attempted 3 times with different types of busybox install locations, and each time I install it to anywhere in /system/, TWRP no longer prompts for the decryption key or password to access the file system.

ToolB0x said:
Question: Now that you've installed that, can you still boot TWRP on your device and have it still ask to decrypt your file system? I've attempted 3 times with different types of busybox install locations, and each time I install it to anywhere in /system/, TWRP no longer prompts for the decryption key or password to access the file system.
Click to expand...
Click to collapse
I boot to TWRP using fastboot boot TWRP.img it works for me. I still get the decryption prompt. I didn't install in system/
I installed in /sbin
Please look at pic

Rooted?
Sent from my Pixel XL using Tapatalk
---------- Post added at 05:26 PM ---------- Previous post was at 05:25 PM ----------
I mean do you have root after boot? What version of su are you using?
Sent from my Pixel XL using Tapatalk

Does this Busybox/method make V4A work on Oreo? Anyone with any success?

I think this is the best busybox. It does not break Root. Flash in recovery.

Tulsadiver said:
I think this is the best busybox. It does not break Root. Flash in recovery.
Click to expand...
Click to collapse
Full thread?

sliding_billy said:
Full thread?
Click to expand...
Click to collapse
This is where it came from but I wouldn't flash the latest. Stick with this one for now.
https://forum.xda-developers.com/and...archs-t3348543

Tulsadiver said:
This is where it came from but I wouldn't flash the latest. Stick with this one for now.
https://forum.xda-developers.com/and...archs-t3348543
Click to expand...
Click to collapse
That link doesn't work.

sliding_billy said:
That link doesn't work.
Click to expand...
Click to collapse
Try this one.
https://forum.xda-developers.com/android/software-hacking/tool-busybox-flashable-archs-t3348543

That worked. Thanks.

Thanks, this thing worked, just make sure to mount system first before flashing=)

Stericson Busybox has been updated and is in the Play Store. Installs to the default location. All works after install and after reboot including root (I am using SuperSU 2.82 SR4), suhide and Adaway. Patience pays off in this case. I have always had the best luck with this dev's work.

sliding_billy said:
Stericson Busybox has been updated and is in the Play Store. Installs to the default location. All works after install and after reboot including root (I am using SuperSU 2.82 SR4), suhide and Adaway. Patience pays off in this case. I have always had the best luck with this dev's work.
Click to expand...
Click to collapse
Been waiting for this. Thanks for the update cuz it made my day... And if all my Fantasy teams and the Vikings win...that will really make my day. Lol
Sent from my Pixel XL using Tapatalk

I just updated to Stericson Busybox. I Installed to /sbin/supersu/xbin and all functioning as expected. Even after re-boot.

Deleted: nevermind, good to go now

Did this, lost root. Re-Flashing Su does not work (no root no su app) Cannot uninstall busybox due to lack of root.
Any suggestions on how to fix this?

I've had success installing busybox via the Magisk Manager as they have it as a module you can install. It was as easy as installing Magisk, choosing their BusyBox module, and restarting my phone. Now I can use Lucky Patcher / any other app that requires it without a problem, Systemless-ly rooted, no custom recovery or kernels.

Any update!??

Its called osm0sis BusyBox for ndk