Is it needed after kernel and root?
Bump
Related
In my epic i go to use the tether and pops up binary outdated so i go to update it and i get a update failed on it. Any ideas on how to get get it to update ive tried the su fixer but nothing. Thanks
Sent from my MB855 using xda premium
I think for anyone to help you, you need to list:
1) what rom are you running and version number or maybe you are running a stock rom - if stock what version
2) what kernel are you running and version number or maybe you are running stock kernel - if stock what version
3) if you are running other than stock, are you undervolted or overclocked
4) are you themed?
5) what version of Superuser are you on now
6) what Binary are you on now
The above questions will at least help. There was a problem when updating to Superuser 3.0.0 - current version is 3.0.6 and current version of Binary is 3.0.3
Maybe this thread will help? http://forum.xda-developers.com/showthread.php?t=961614&goto=newpost
Good Luck!
First Answer the above, but my two cents is you flashed a rom with an outdated kernel that came preloaded with su in sbin instead of Xbin, thus you'll always get an outdated binary unless you change kernels, you could move su via command prompt, but the kernel will just restore it to its original location unless you recompile a kernel yourself, lol. Best to just go stock, or to another rom altogether with a different kernel.
*slaps op*
Go about 2 pages back, you'll find the answer.
So, the question is simple. I want to flash a custom kernel only, and keep the stock ROM. Is this possible without modifying the flash counter/modified status? Sorry, I'm a complete n00b (kinda) to the Samsung root world. I know a bit about rooting in general, though. Will boot.img via Odin/Mobile Odin work?
hameerabbasi said:
So, the question is simple. I want to flash a custom kernel only, and keep the stock ROM. Is this possible without modifying the flash counter/modified status? Sorry, I'm a complete n00b (kinda) to the Samsung root world. I know a bit about rooting in general, though. Will boot.img via Odin/Mobile Odin work?
Click to expand...
Click to collapse
First you have to root the phone and have CWM recovery that you flash with Odin, if you want to flash a custom kernel (wich is usualy a zip file). This will raise the flash counter. Flashing a kernel from the phone does not raise the counter. You can reset the flash counter with Triangle Away. Here is the link for getting root and cwm https://hotfile.com/dl/176073261/b6acfe6/cwm6-root-n7100-121015.rar.html. Also install busybox (free or paid) from the Play Store. Good luck
A related issue. Those custom kernels like neak or note2core comes with busybox (in /sbin). Mybackup complains that it is outdated. So I installed BusyBox with newest busybox (installed in /system/bin). Obviously I have two busyboxes. I can delete busybox in /sbin but it will come back after reboot. How do solve this issue?
Thanks,
Howard
gee2012 said:
First you have to root the phone and have CWM recovery that you flash with Odin, if you want to flash a custom kernel (wich is usualy a zip file). This will raise the flash counter. Flashing a kernel from the phone does not raise the counter. You can reset the flash counter with Triangle Away. Here is the link for getting root and cwm. Also install busybox (free or paid) from the Play Store. Good luck
Click to expand...
Click to collapse
After rooting the HTC One X (after received OTA JB) I installed custom recovery CWM and SuperSU (not on my phone). Now I need to install busybox, but the ones from Play store does not want to install. Is there any installable zip of last busybox, that I can install through recovery?
Thank you.
Hey guys,
I know there are tons of Superuser apps and root methods such as cf autoroot but I'm hoping someone knows is how to root the S4 (SGH-M919) and have Koush's Superuser.apk be your SU client. I don't want to use Chainfire or SuperSU or anything else. It seems 4.3 for me will only accept SuperSU but I was hoping to use the CWM Superuser as I do on all of my other devices. Would hate to have a different SU just on this one device. Any ideas on how to get superuser.apk working on 4.3 on the S4 (Stock, custom recovery, rooted with SuperSU for now).
T-Mobile Galaxy S4 (SGH-M919)
Android 4.3 (MK2 full with KNOX through ODIN)
Don't care about tripping KNOX
Daistaar said:
Hey guys,
I know there are tons of Superuser apps and root methods such as cf autoroot but I'm hoping someone knows is how to root the S4 (SGH-M919) and have Koush's Superuser.apk be your SU client. I don't want to use Chainfire or SuperSU or anything else. It seems 4.3 for me will only accept SuperSU but I was hoping to use the CWM Superuser as I do on all of my other devices. Would hate to have a different SU just on this one device. Any ideas on how to get superuser.apk working on 4.3 on the S4 (Stock, custom recovery, rooted with SuperSU for now).
T-Mobile Galaxy S4 (SGH-M919)
Android 4.3 (MK2 full with KNOX through ODIN)
Don't care about tripping KNOX
Click to expand...
Click to collapse
Method 1
Use Odin to install a custom recovery of your choice.
Boot to recovery.
Flash any Superuser.apk you want.
Using Odin to install the recovery won't root the current ROM. It will just give you a custom recovery. From the custom recovery you can install anything you want, including the Superuser.apk of your choice.
Method 2
Root it using whatever root method works even if it installs SuperSU.
Uninstall SuperSU through the 1 click feature in the app.
Boot to your custom recovery. (Will NOT be automatically installed with CF Auto Root. You will have to flash a recovery after rooting)
Flash Superuser.
Reboot. Enjoy goodness.
Skipjacks said:
Method 1
Use Odin to install a custom recovery of your choice.
Boot to recovery.
Flash any Superuser.apk you want.
Using Odin to install the recovery won't root the current ROM. It will just give you a custom recovery. From the custom recovery you can install anything you want, including the Superuser.apk of your choice.
Method 2
Root it using whatever root method works even if it installs SuperSU.
Uninstall SuperSU through the 1 click feature in the app.
Boot to your custom recovery. (Will NOT be automatically installed with CF Auto Root. You will have to flash a recovery after rooting)
Flash Superuser.
Reboot. Enjoy goodness.
Click to expand...
Click to collapse
Hey SkipJacks! Thanks for the quick reply. Method 2 seems to be the closest for me but it seems to be a no go with Koush's SuperUser. It looks like it relies on some binaries that never download and it won't use the ones that SuperSU installs. I guess I'm gonna have to use SuperSU for now. Thanks again. I just prefer Koush's to Chains and Chainfires. Everything was working fine on 4.2.2 but from 4.3 on it's only been SuperSU.
I'm beginning to think it's broken as many people are saying the same thing.
Which method do I use for 6.0.1?
I rooted using the old school method with SuperSU 2.52 and a patched kernel and it is working fine. Used this kernel. He always updates to the most recent version very quickly: http://forum.xda-developers.com/nexus-5x/development/kernel-stock-rootable-forceencrypt-t3258352
You could also do the systemless method if you want but I don't know much about it since I have no reason to use it.