Hey guys!
I'm completely new to android (Finally jumped on board the smartphone boat!), however I have a pretty knowledgeable background in programming (web developer by trade)
I was just curious what goes into a ROM that allows ADBD to run as root on the phone so that when I do "adb shell" I'm logged in as root. I noticed that when I first installed the superuser binary on my phones stock ROM just after S-OFFing that when I opend up a shell through adb I still had to su to root.
Is the change part of the kernel? Or is it a setting in the ROM?
This isn't a problem I'm having, just curious what has to be done to a stock ROM for ADBD to run as root, looking to get into ROM customization pretty soon =)
Related
Hi Guys I'm a Noob
My phone is XT910 and it has several problem so i'm going to service center.
The problem is; I cannot unroot.
I updated recently after root.
After upgrading, I can't use apps that acquire root authority.
also unrooting is impossible. I mean I cannot remove SU so I cannot go to svc center.
S/W version is 65.3.106.XT910K.KT.en.KR
Is there any solution?
and I think it's impossible, but can I downgrade?
thx for reading this.
have you checked adb shell?
is superuser unable to detect root? is superuser still on your phone after the update?
have you try to reinstall superuser or superuser update fixer from the market?
yyhd said:
have you checked adb shell?
is superuser unable to detect root? is superuser still on your phone after the update?
Click to expand...
Click to collapse
I had to replace my XT910 logicboard because I dropped it in water and couldn't repair. The new motherboard comes with a rooted OS, system setting version reading 67.145.910.XT910.ChinaRetail.en.CN. I absolutely know nothing about rooting and have never tried it, and I don't know anything about the terms used in rooting. I want to un-root my device, but I do not know how to do that. I tried DooMLoRD, but it did not work (according to what I am being informed by Voodoo OTA RootKeepr, which says super user installed, device rooted, root permission granted, /system supports root protection protocol su available.)
How can I unroot my device?
Thank you
Unrooting can be achieved easily if you're not concerned about losing data on the phone. RSDlite (5.7) back to stock with the appropriate SBF Fastboot file (can't help with locating the appropriate SBF for international; you'll have to do some sniffing around). Then you can run an OTA if you need to, and you'll be back to 100% stock with none of the previous stock rom alterations (root, etc.) remaining.
EDIT
Check HERE; you may be able to locate the proper SBF.
Hi, sorry I have really tried before asking, I am at a complete loss as to what to do.
I have used HTC Desire X All-In-One Toolkit V2.0 [1-1-2013] from http://forum.xda-developers.com/showthread.php?t=1943822
I unlocked the bootloader, and the boot menu shows the phone as 'unlocked'.
I then tried running permroot, which installed superuser, but when I try to check if my phone is rooted, (Using droidwall : I am trying to enable the firewall).
I get the message that I need a rooted phone to run droidwall .
and 'if this phone is already rooted make sure droidwall has enough permissions to execute the 'su' command'.
How do I know if my phone is rooted?
Thanks - this has been most frustrating, my backspace key has also bombed out. haha
Hello,
Try this app: https://play.google.com/store/apps/details?id=com.joeykrim.rootcheck&hl=en download it from the store and run it it will say is your phone rooted or not.
Bensmom said:
How do I know if my phone is rooted?
Click to expand...
Click to collapse
You should have a su binary residing in /system/bin/ and some sort of control app in your app drawer (probably Superuser). If you don't have these then you aren't rooted.
If you have them, an easy way to test is to use a terminal app , type 'su' and the control app should pop up asking if you want to give root privileges to terminal.
If you are having trouble getting root to work using the toolkit, try doing it manually by following nloooo's tutorial.
Ok, you all forgot about flashing recovery first.
I know that not many people may be able to help as this is a long story but here it goes:
I had used a root toolkit (I know that I will receive hate) to root my kyocera rise as rooting by hand has become a pain. Anyways, I had run into an issues where my phone would not run properly (possibly due to malware or the likes) and as such I reset it back to factory data. For months after I had assumed that I did not have root anymore because I had lost the supersu app (stupid me forgot to check root). Recently I realized that in one of my apps that could use root, it was using root and I did not even know it.
Seeing that this would cause some security issues, I quickly installed super su and updated the binaries. From then on, whenever an app tried to request root permission, it would then freeze. I then uninstalled super su and did the unroot setting from software and then planned to reinstall it. When I reinstalled supersu, It complained that it could not install binaries and this was bad (lol).
Anyways, the kyocera rise has a locked bootloader that prevents me from completely flashing over a new copy of the os, which sucks, and now I feel like I am stuck with an unrootable device because I can't seem to reinstall the binaries to allow super su or any other superuser program to work properly. Any Help would be appreciated. FYI, this is just stock android, nothing fancy about it.
-Fishwithadeagle
i have the same problem
i may have to say am also facing a similar problem. i mistakenly permanent unroot my phone with my binary su. now all my apps that needs root aint functioning. i tried to re-install the binarySU but jux couldn't. i have also tried using gingerbreak to start all over again just to get my phone rooted. it simply cant.....please i need help..... i want to root my phone again
Try this tutorial...
http://forum.xda-developers.com/showthread.php?t=2307306
Sent From Tweaked Kyocera
I've done quite a bit of searching over the past couple days but can't quite seem to find what I'm looking for.
I'm trying to root my Azpen A700 tablet manually. I've managed to load ChainsDD's Superuser.apk and su binary to the device in the appropriate locations. I've run all the chmods on them and can use ChainsDD's su binary when I run adb shell. I know I did this backward, but I'm really just playing with this thing, flying somewhat blind, and I don't much care if I brick it, so sue me.
So I tried to run 'fastboot oem unlock' just to see what it would do/if it would work. I loaded the latest ADB Composite Driver. I think the problem is that I can't get this POS to boot into the bootloader. It only wants to boot into recovery. If I run 'adb reboot-bootloader' or 'adb reboot bootloader' it always boots up into Android. I've tried using every volume/power button combo I can think of, and no dice. I really have no idea if the bootloader can even be unlocked. Does anyone have any ideas as to how to make this work?
By the way, I also tried SuperOneClick. It warned me that my device was already rooted, I'm guessing because it knows the su binary, and asked me if I wanted to root it anyway. I said Yes, and got the "failed to set prot mask" error on Step 4.
LeonardHatred said:
I've done quite a bit of searching over the past couple days but can't quite seem to find what I'm looking for.
I'm trying to root my Azpen A700 tablet manually. I've managed to load ChainsDD's Superuser.apk and su binary to the device in the appropriate locations. I've run all the chmods on them and can use ChainsDD's su binary when I run adb shell. I know I did this backward, but I'm really just playing with this thing, flying somewhat blind, and I don't much care if I brick it, so sue me.
So I tried to run 'fastboot oem unlock' just to see what it would do/if it would work. I loaded the latest ADB Composite Driver. I think the problem is that I can't get this POS to boot into the bootloader. It only wants to boot into recovery. If I run 'adb reboot-bootloader' or 'adb reboot bootloader' it always boots up into Android. I've tried using every volume/power button combo I can think of, and no dice. I really have no idea if the bootloader can even be unlocked. Does anyone have any ideas as to how to make this work?
By the way, I also tried SuperOneClick. It warned me that my device was already rooted, I'm guessing because it knows the su binary, and asked me if I wanted to root it anyway. I said Yes, and got the "failed to set prot mask" error on Step 4.
Click to expand...
Click to collapse
Why do you think you need to get into the bootloader? The device already has root access through ADB. Just open an ADB shell and replace the su binary with one that doesn't restrict user gaining root.
BLuFeNiX said:
Why do you think you need to get into the bootloader? The device already has root access through ADB. Just open an ADB shell and replace the su binary with one that doesn't restrict user gaining root.
Click to expand...
Click to collapse
Well, that's what I thought I did. I have the ChainsDD su binary in /system/xbin with a symlink, /system/bin/su, that points to it. I ran 'chmod 06755 /system/xbin/su' on it so the setuid and setgid are applied, just like the stock su binary. But if I run Titanium Backup, it says it can't get root through /system/bin/su. And if I run su through a Terminal Emulator on the device, I get an error "explosion" of permissions errors. Is there another su binary I should be using instead? Or maybe there's something that Superuser.apk needs to do that I'm missing?
I guess the reason I'm trying to get into the bootloader is so I can unlock it and try rooting the easy way, to see what's different from what I've done so far. I didn't really understand why I needed to get into the bootloader if I was so easily able to replace the su binary, but I figured maybe there was something that needed to be done with file permissions that couldn't be done if, say, /system was mounted, or something like that. Does that idea hold any water?
Maybe using the su binary I have I can modify permissions on files where needed?
Thanks for the help!
LeonardHatred said:
Well, that's what I thought I did. I have the ChainsDD su binary in /system/xbin with a symlink, /system/bin/su, that points to it. I ran 'chmod 06755 /system/xbin/su' on it so the setuid and setgid are applied, just like the stock su binary. But if I run Titanium Backup, it says it can't get root through /system/bin/su. And if I run su through a Terminal Emulator on the device, I get an error "explosion" of permissions errors. Is there another su binary I should be using instead? Or maybe there's something that Superuser.apk needs to do that I'm missing?
I guess the reason I'm trying to get into the bootloader is so I can unlock it and try rooting the easy way, to see what's different from what I've done so far. I didn't really understand why I needed to get into the bootloader if I was so easily able to replace the su binary, but I figured maybe there was something that needed to be done with file permissions that couldn't be done if, say, /system was mounted, or something like that. Does that idea hold any water?
Maybe using the su binary I have I can modify permissions on files where needed?
Thanks for the help!
Click to expand...
Click to collapse
Do it again, but us the su binary found here: https://plus.google.com/103583939320326217147/posts/4FemP5ACLSn
BLuFeNiX said:
Do it again, but us the su binary found here:
Click to expand...
Click to collapse
That did it, thanks!
Maybe now I'll root my Nexus 4 this way...
LeonardHatred said:
That did it, thanks!
Maybe now I'll root my Nexus 4 this way...
Click to expand...
Click to collapse
No problem.
I'v ran through all root methods (that i know of) for this phone (4.4.4) and none of them work. at all. Whats the point of a root dir if its impossible to access? Seems to be limited info on a root method for this phone. Is it root proof?
dunnothename said:
I'v ran through all root methods (that i know of) for this phone (4.4.4) and none of them work. at all. Whats the point of a root dir if its impossible to access? Seems to be limited info on a root method for this phone. Is it root proof?
Click to expand...
Click to collapse
For now because of the locked bootloader
Root Achieved!!
UPDATE
I got Kingroot to root the zte speed!!!
but it doesnt keep root for very long. usually only stays rooted for a matter of minutes, and you have to reroot it everytime you reboot
I had to install "certificate installer" from google play and install a root certificate.
now im just trying to figure out how to keep it rooted
me to i cant get root to stay there maybe the kingroot guys can fix that in a updat.
dunnothename said:
UPDATE
I got Kingroot to root the zte speed!!!
but it doesnt keep root for very long. usually only stays rooted for a matter of minutes, and you have to reroot it everytime you reboot
I had to install "certificate installer" from google play and install a root certificate.
now im just trying to figure out how to keep it rooted
Click to expand...
Click to collapse
vv
Wanted to post update on this thread for people who come by via Google wanting to root that zte speed, as I was sick of coming by this thread as seeing no answer from the search results.
I did the following and was able to get permanent root with SuperSU
Source/Inspiration for this guide (thank you hroark13): androidforums / zte-speed-n9130-permanent-root-achieved.1061137
With ADB enabled and hooked up, run " adb shell reboot disemmcwp "from your PC. This helps to unlock some key parts for Kingroot to work much quicker and persist. That was the secret sauce that was not known in 2015 when everyone was trying to root this at first.
I used Kingroot 5.3.8 from APK mirror as that was easiest (no need to install the Kingroot application on PC just downloading the APK is enough to the phone). I was also running AnTuTu Benchmark Stress Test at the same time as running Kingroot, but this might not be necessary.
I installed Busy Box, and got the SuperSU downloaded ahead of time from the play store as well. I had tried to run Super SU but it couldn't replace the binary, so:
Finally, replace Kingroot with SuperSU by using the Super-Sume Pro app, pretty much just follow through the prompts in the app, but before you start be sure to disable Auto Updates in Kingroot first to prevent a possible conflict. The app will prompt you to reboot, which you can do.
Should have permanent root on your ZTE speed now, you can skip the last step if you like the Kingroot manager but generally people like Super SU better so I changed it to that (less janky).
Warning, if you screw any of this up there is no way to recover your ZTE speed so therefore you could end up with $20 brick.
Thank you, hope this helps someone out who has one of these in their junk drawer.