Database Users

not able to root the 4.4

I've recently installed kitkat 4.4 on my nexus 4 with twrp recovery
I tried to flash the UPDATE-SuperSU-v1.69.zip using the recovery
the phone finish the proccess and reboot but there is still no root permission or superuser app
any help?

YTayyar said:
I've recently installed kitkat 4.4 on my nexus 4 with twrp recovery
I tried to flash the UPDATE-SuperSU-v1.69.zip using the recovery
the phone finish the proccess and reboot but there is still no root permission or superuser app
any help?
Click to expand...
Click to collapse
open the supersu app, check if it asks you to update your binaries.

simms22 said:
open the supersu app, check if it asks you to update your binaries.
Click to expand...
Click to collapse
but the supersu doesn't exist in my drawer at all

YTayyar said:
but the supersu doesn't exist in my drawer at all
Click to expand...
Click to collapse
go to the play store, download supersu, then open it after install. when it asks you to update your binaries, do it. or, try downloading supersu again(maybe it was a bad download), and flash it again.

simms22 said:
go to the play store, download supersu, then open it after install. when it asks you to update your binaries, do it. or, try downloading supersu again(maybe it was a bad download), and flash it again.
Click to expand...
Click to collapse
seems to be working,,, thanks
btw I discovered that the supersu was there in the app list in the settings but just not showing in the drawer,, however, installing it from the market solved the issue

YTayyar said:
seems to be working,,, thanks
btw I discovered that the supersu was there in the app list in the settings but just not showing in the drawer,, however, installing it from the market solved the issue
Click to expand...
Click to collapse
sweet

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.

Updated to SuperSU v2.81 and no root... :(

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.

Rooting Android 8.0 Oreo

Anyone found a root solution?

Wouldn't the latest super su work ?

Hey.. Supersu got installed successfully.. But having problems applying busybox (not successfully installed)

akashkyh said:
Hey.. Supersu got installed successfully.. But having problems applying busybox (not successfully installed)
Click to expand...
Click to collapse
I also got Super Su to work, but can't install BusyBox

Magisk should work perfectly.

puddin007 said:
I also got Super Su to work, but can't install BusyBox
Click to expand...
Click to collapse
Magisk v13.3 + BB module works on my 6P

stoccomatis7 said:
Magisk v13.3 + BB module works on my 6P
Click to expand...
Click to collapse
Can confirm this, all in the shot is working for me

Help with installing Magisk on Verizon Samsung Galaxy Note 3 SM-N900V

I have read many threads and lots of videos and cannot seem to get the Magisk installed.
I have flashed back to stock many times with (N900VVRUEOF1_N900VVZWEOF1_N900VVRUEOF1_HOME.tar.md5) in order to try multiple methods.
Rooted with Arabictoolapp - used rootchecker to verify/application also says true for root
followed: https://forum.xda-developers.com/ve...guide-ob6-of1-root-bootloader-unlock-t3439010
installed SU from playstore to unlock bootloader using the adp method - shows developer mode to verify - using eMMc to verify CID starts with 15
followed: https://forum.xda-developers.com/ve...l/official-note-3-verizon-bootloader-t3359370
installed twrp using official twrp app & also tried ODIN in another trial (picked verizon americas and got twrp-3.2.3-0-hlte.img.tar and twrp-3.2.3-0-hlte.img )
turned phone off and boot into recovery to verify; at this time i created a recovery
using MagiskManager i downloaded the zip (Magisk-v18.1.ip) and flashed using twrp - no errors but when i restart the phone it says Magisk not installed
next attempt was to extract the boot.img from the stock OF1 and then flash the Magisk - no errors but when i restarted the phone it says the same thing - Magisk not installed
another attempt was to patch the boot.img and got a patch_boot.img then using TWRP i flashed the patch_boot.img - restarted and magisk not installed
after further digging, i tried another method which was to unroot using SU, reboot, go into recovery to then install Magisk - magisk not installed
*note each attempt to install Magisk unrooted my phone
*was able to use Magisk-uninstaller-20190204.zip to uninstall Magisk manager from recovery - icon went away
anyways i am completely stuck now. any suggestions or comments on my approach?

jordanfan23 said:
installed SU from playstore to unlock bootloader using the adp method - shows developer mode to verify - using eMMc to verify CID starts with 15
followed:
Click to expand...
Click to collapse
Did you uninstall SU before trying to install magisk. The two together may cause conflict.

cssr said:
Did you uninstall SU before trying to install magisk. The two together may cause conflict.
Click to expand...
Click to collapse
Yes my last attempt i tried.

please help! there has got to be something i am doing wrong or missing. i can flash the uninstall zip and it does uninstall the magisk manager

@cssr any other input or suggestions?

jordanfan23 said:
@cssr any other input or suggestions?
Click to expand...
Click to collapse
Try twrp 2.8.7 hltevzw. You are using the stock ROM which is android 5. Twrp 3.1 and higher is for android 7 and up. I missed that the first time I read your post.

cssr said:
Try twrp 2.8.7 hltevzw. You are using the stock ROM which is android 5. Twrp 3.1 and higher is for android 7 and up. I missed that the first time I read your post.
Click to expand...
Click to collapse
no go =(

@cssr should i try another version of magisk?

jordanfan23 said:
@cssr should i try another version of magisk?
Click to expand...
Click to collapse
Yes. Are you installing Magisk .zip in twrp and installing Magisk Manager APK after normal reboot?

cssr said:
Yes. Are you installing Magisk .zip in twrp and installing Magisk Manager APK after normal reboot?
Click to expand...
Click to collapse
what do you mean after normal reboot? so flash magisk in twrp. reboot. reboot again then install magisk manager? do you know what version of magisk i should run and where i can find the dl link?

What he means is you install the Magisk ZIP via TWRP in Recovery mode, reboot the phone, then you install Magisk Manager via the APK.
Go to magiskmanager dot com website which has the ZIP installer plus the APK for the Manager.

I only just recently tried to tackle this challenge. I also installed 0F1 with Odin, then rooted with Arabic. I was messing with Pokemon go and it wasn't happy I was rooted. I downloaded magisk manager, installed it that way. At reboot, angry message from Verizon that I have custom software and phone won't boot. I assume this is because I didn't install custom recovery.
If you figure a way to get this done, I will be grateful. One thing I don't quite follow. Magisk is a root method...so should we really be rooting the phone prior? Seems redundant and going against the whole point of magisk. Right?
I wanted to play around with spoofing GPS with PGO which requires making a GPS spoofer a system app (need root for that). Is that still possible using magisk?
I'll post any updates I have as well.