SM-910G Manual root 5.1.1 - Galaxy Note 4 Q&A, Help & Troubleshooting

How can i manually root my device running on 5.1.1 via adb
I tried to push the SU but i got permission denied several times? Anyone know how?

Related

345 not fully Rooted?????

I cannot gain SU access on ADB Shell after performing the flashable root zip suggested in the update.pkg thread.
Sure root and superuser work on the phone itself. But i got no ADB Shell powers.
anyone else have luck with this?
I get permission denied
It appears my flashable root got messed up by trying to fix permissions in streakmod recovery. Just reflashed and i believe it should work now.
Sent from my Dell Streak
works on mine perfectly.
I did have to install Busybox system/bin .
it works fine
it appears that everytime I flash a clockworkable zip with streakmod it breaks my root.
The only way to get it back is to reflash the root zip. This isn't good.
Same here, fixing permissions screwed up my root. I'm back on 319 until a better root comes along (if it ever does)
Krad said:
I cannot gain SU access on ADB Shell after performing the flashable root zip suggested in the update.pkg thread.
Sure root and superuser work on the phone itself. But i got no ADB Shell powers.
anyone else have luck with this?
I get permission denied
Click to expand...
Click to collapse
I downloaded busybox from the market and installed the 1.17.1 and it worked fine after that.
Goodluck

[Q] ADB No Su?

So I'm learning how to ADB because I bought a G2, but it's on Gingerbread OTA. SO it can't be rooted. I can only root by using the downgrade method which requires ADB. I wanna know how to do it perfectly on my G1 before i brick my G2 Xo. I just can't seem to get SU permissions. Isn't just (adb #su *enter*)? Then the phones ask for SU permission the you get ($). Idk what I'm doing wrong Xo do I need a special file for ADB to do that?

[Q] Why no su access after it's rooted?

I rooted my Nexus 7 a few days ago and was able to replace bootanimation. But now I want to replace my new version of bootanimation using Root Explorer, I found I have no super user access (the terminal prompt does not change from $ to # when I type su at the adb shell). The /system is mounted as r/o. I also have the busybox and supersu zip files on the sdcard. Can anyone please tell me what happen here and help me back to su mode? Thanks in advance!!
KJTseng said:
I rooted my Nexus 7 a few days ago and was able to replace bootanimation. But now I want to replace my new version of bootanimation using Root Explorer, I found I have no super user access (the terminal prompt does not change from $ to # when I type su at the adb shell). The /system is mounted as r/o. I also have the busybox and supersu zip files on the sdcard. Can anyone please tell me what happen here and help me back to su mode? Thanks in advance!!
Click to expand...
Click to collapse
I can't see any reason why you'd become unrooted unless you either replace the system partition (via an update or rom change or fastboot flash or whatever) or delete the binary yourself. If you didn't do either of those it could be either a problem with supersu, a problem with the binary, or a problem with your kernel. Try putting the root binary (su) back on the phone and trying again, and if that fails try using SuperUser instead of Supersu. If neither work you may need to do a factory reset and try again.
did you upgrade to 4.1.2? You must have lost root during the process. Just re-root it. I used the toolkit.
cooljais said:
did you upgrade to 4.1.2? You must have lost root during the process. Just re-root it. I used the toolkit.
Click to expand...
Click to collapse
oh, yes!!!! I just upgraded a couple of days ago from JRO03D to JZO54K. THANK YOU!!
I tried re-rooting again (w/o flashing custom recovery) after I upgrade Nexus Root Toolkit to v1.5.4 t support 4.1.2, But get stuck at the message "waiting for your device to finish booting back up." Nexus 7 is at the TWRP mode and can't get out of it. So I reboot to bootloader mode and eventually the toolkit tells me to run SuperSU and Busybox. Still doesn't work since I still don't have super user access. What shall I do next? I know there are still few more steps after the TWRP.

There is no SU binary installed, and SuperSU cannot install it

Greetings Folks!!!
I am on CM12.1 Lollipop 5.1.1 Nightly, and ROOT access was working fine on my phone so far. When I launched Thunderzap today, I noticed that the app was waiting on "Requesting ROOT Privileges" for over 2 mins, and also the SuperSU app was missing from the app drawer. Thunderzap had been recently updated, and I suspect that might have triggered the root access to be requested again, but it wasn't given root access for some reason, and I never got a prompt to grant it root access. However, my other apps like ROOT Explorer, Shell Terminal Emulator etc, which weren't updated off lately, worked fine with root access. Not sure why now, but I thought reinstalling SuperSU-v2.46 might be a good idea at that time, and I flashed that file. And ever since I have completely lost my root access. When I launch the SuperSU app now, i get an error saying:- "There is no SU binary installed, and SuperSU cannot install it"
Some help would be appreciated. Screenshots attached.
I've managed to fix the issue. I just re-flashed the CM-Update file (located in the pone's internal memory), and got some ROOT access prompt while trying to open Thunderzap again. Thereafter, I installed SuperSU from the Playstore and got my binary updated through it. :good:
acemccloud1 said:
I've managed to fix the issue. I just re-flashed the CM-Update file (located in the pone's internal memory), and got some ROOT access prompt while trying to open Thunderzap again. Thereafter, I installed SuperSU from the Playstore and got my binary updated through it. :good:
Click to expand...
Click to collapse
can you please share the method u used to flash back CM?
i am unable to re root

SuperSU error

Their is no SU binary installed, and SU cannot install it. This is a problem.
If you just upgraded to 5.0 you need to manually re root consult the relevent forums for your device.
Im on 6.0.1.
I got this error after like 5 weeks when i first rooted it.

Categories

Resources