Hi folks!
Need some advice, before i invent the wheel again for myself.Learning by trying, but where to go or what to check from here...?
Busy with rooting an tablet, yes tried many apps, only kingroot works..What do i see, my system is only write protected and stays that way.
Made boot.img, ro secure=0(was=1),ro debugging=1(was=0),adb service=mtp/adb(was nothing).
Offcourse still no root, adb is now always root, and i can get su also.
So i thought what could be next..I checked for selinux, but cant find anything in the rom, inside when extracted, my last idea....Would be that.
Yesterday i tried Tsparky root script what installs busybox and supersu, same thing happens...No writing allowed, and offcourse no supersu found....While it was installed true the google play way...But adb was running in root..Uhm...????
So tonight i will try my last effort, in placing supersu in the system.img....I only sometimes think to straight, must i remove the other su..?And sometimes they change su in supersu...Got me confused alittle bit, i already read the supersu config file and i will try to place them and give them permissions...
But i have the feeling after reading other forums and peeps with the same issue that maybe....It will still not update the binary..
If my last effort doesn't work, what or where can i go further in rooting the tablet...Because its so difficult i learn a lot...But now...I really dont know what could be next! Read something about maybe there are ''flags'' in the system..How 2 check, can i remove them...
I hope its clear where i am at, and where i wane go, but what bump is still there in the system, some advice please.
Thanks
Erik
Related
I just saw this!
http://twitter.com/unrevoked
They're currently working on one that will write to /system.
Stay tuned!
Thanks guys! Awesome work!
VoXHTC said:
I just saw this!
http://twitter.com/unrevoked
I downloaded an .apk file and I'm staring at it now..
Click to expand...
Click to collapse
I'm not very happy with installing and running things on my phone without knowing quite what they do. you go first
Yeah, report back if it breaks anything. I wanna root mine and this way seems easy.
LOL no way.. u 1st.
It worked, but unfortunately it has to be applied on each reboot. not a sticky root. I know my low post count will make you sketchy of this point. all I can say is that it is true. dropped it on my SD, used astro to access it, installed, and it worked just like blackrain, one click. except not sticky.
works great. gotta do it every boot.
Yep me to tried it and worked so how would this work on installing toms though since a reboot get rid of the root?
Oh my god i wanna do it. Its gotta be legit.. Right?
jachase42 said:
It worked, but unfortunately it has to be applied on each reboot. not a sticky root. I know my low post count will make you sketchy of this point. all I can say is that it is true. dropped it on my SD, used astro to access it, installed, and it worked just like blackrain, one click. except not sticky.
Click to expand...
Click to collapse
Well it got rooted, going to reboot and see
Hmmm. So if its not sticky, its pretty much pointless to me. Gonna way for the real Root to come. I mean the phone just came out so it shouldnt be long.
I'm still showing sudo permissions on reboot, going to test a few things. like the overclock app, and terminal access.
EDIT: Confirmed, SetCPU for Root cannot request permission. not a sticky root, just as it says.
so what does this do for me, i did it but i can't get into where all the apps i've downloaded are and stuff, i'm confused. what can i do with this root?
can you write to system from within android? if so root explorer will let you easily remove stock apps
no you can't due to current limitations
There is no rw for /system currently. < this should be written in bold and stickied.
I find their lack of information disturbing. If it really needs to be run every boot, why don't they say that? Their site doesn't have a single bit of info on it.
Well there is the long shell way.
Can I use this to create a perfect backup of my phone so I can restore it at any time?
actually when you do it on the phone it tells you that it needs to be run every reboot. so we can't get rid of sprint applications through the phone because of a lack RW for the system, but can we do this pc side???
i'm in boot mode what do i do so i can get rid of sprint apps and what not, how do i do a nandroid, and how can i back up all of my aps.
Anyone know what this means?
Root protip: bind mounts are your friend: busybox touch /data/local/blank; mount -o bind /data/local/blank /system/app/Sprint_NFL.apk
Hey,
As the title suggested, and the phone is a Galaxy S Fascinate.
I rooted using a technique which did what this does, with some info from here as well.
Arg, it won't let me post URL's, retarded...wow, can't even edit it because that counts as my '5 minute cooldown' between posts...anyway, after 5 minutes, remove the spaces at the beginning to get them to work..
Link 1: http : // rootzwiki.com/index.php/Smartphones/Samsung-Group/Fascinate.html
Link 2: http : // droidforums.net/forum/rescue-squad-guides/80208-multiple-phones-root-them-unroot-them.html
I'd like to unroot my phone manually, but I don't have enough knowledge of how the root actually works to do so. From what I hear, the word on the street is to just reflash with Odin using the OEM platform/application image. I'm not to keen on reflashing.
So I'm trying to figure out a bit more about how the root works, so I can unroot it via command line. (No, I don't want to be pointed in the direction of one-click root/unrooters, been there, done that, got the t-shirt, was pretty damn pissed about it)
So there's 4 elements that go phone side
- su binary
- busybox binary
- Superuser.apk package
- rage image
So first, there's su, the binary most likely already exists on the phone, which means if I'd like to unroot, I'd need the OEM version of the su binary, is this correct?
Same can possibly go for busybox, assuming if it was there. If busybox didn't come on the phone, then there's no need and you can just remove it.
Now from what I understand about the Superuser package, is it isn't quite an application...but it is, or something. It can probably be removed via uninstall, but I'd need somebody to verify that who knows what Superuser actually is.
Now this is where things get really hazy, the actual exploit, the rage binary. Depending on what this does, it may or may not be a complete pain to get it back to the OEM state. Does anybody have any info or know about the actual binary itself, how it works, etc.? I'm assuming if it just replaces a certain piece of a binary, that piece can be put back in there, but with the root the binary is RAN, not dropped in, so it obviously does something more...and I can't seem to figure out what nor how nor why, etc.
Synopsis:
I'm trying to unroot manually and am not sure about a bunch of specifics regarding the root.
I'd definitely appreciate any info on this...and PLEASE don't just say "search" - because while the root aspect has been covered many times, the specifics haven't..
TIA!!
PS:
Reason I want to unroot is b/c my camera is hosed and I need to take it back to the VZW store for replacing..
Bump?
This might be a dumb Q, but is the rage bin src open?
Hello xda, I have a bit of a problem:
I have a Samsung Exhibit which I rooted using the zergRush method found here on the forums. At first everything worked fine. But recently I was trying to push a modified system app to my phone using adb and it told me the action wasn't permitted. Checking the shell, and terminal emulator on my phone to see if I had superuser permissions failed. So I went about trying to root my phone again, which according to the zergRush script said was successfull, but checking the shell once again showed that I still did not have superuser permissions. I did a factory wipe of my phone in hopes of trying to get it to root again with no success. But here's the weird part, although it doesn't appear I have root access all my apps that require root access (titanium backup, my screenshot app, and some of widgetlocker's features) still fully function.....
Does anyone have any idea what's going on here? I would love my system folder access back
Thanks in advance.
Dumb question, but your H-Boot shows S-Off? Just covering the bases... Also, do you have Super User installed and functional?
To be honest... I don't know what H-Boot or S-Off means. Pretty new to all of this. Mind giving me a walkthrough? I have superuser installed yes. It's granting programs superuser permissions. But I can't access su in terminal emulator or in the shell.
Well, I'm not the top tier technical person here, so I'm not exactly sure on how to get your problem resumed, since I've not heard of that. On the other hand, there might be a different way to accomplish what you are trying to do.
What are you trying to achieve, pushing a modified system app to do what and where? My suggestion, might be to just put it on your phone through USB to the root folder and then move it in ES File manager, or w/e you use. If all you are doing is pushing.
Obviously ADB shell detects your device, but I'm not sure why it is saying it doesn't have SU access. My other suggestion is to redo the ADB/Android SDK installs. I had a problem where I installed them wrong, by installing too much and ADB did not work properly. So, there might be a chance your phone is fine, but the ADB/SDK are not proper, somehow.
Let me know.
If that were the case, and my phone was fine, wouldn't I be able to access super user through terminal emulator on my phone? Right now when typing su in terminal emulator, the pop up to grant superuser permissions appears but when you allow it to have su permission the # doesn't turn to a $ like it should. The more I think about it the more I think it's a problem with superuser. I've seen people talking about an update to superuser that can break your root? Mehhhh.
Seems like other have had this problem too... Not sure if a nandroid recovery will fix this, otherwise you might have to try to unroot, and then reroot.
Sorry, just might have to do a little more digging than I was able to. Good luck
[Hopefully I didn't miss this being covered somewhere else, as I am much the same as many of you and get beyond irritated with endless repeat questions. I searched using the best keywords I could think of for the issue, but to no avail. Apologies in advance if this has been covered!]
Alrighty. I've got a TF101, rooted it myself (thank you XDA), running 8.6.5.1.9 i believe, stock rom just with root. Used nvflash and Razorclaw. Worked like a charm.
It's been fine for the last 6 months, no issues. However, I decided to update busybox using its internal updater as I have before with no problems. I noticed I accidentally told it to install to /system/bin instead of /system/xbin, and the only reason I even knew about that was due to having to configure an app to find busybox in /xbin instead of /bin.
Now there's a problem. I can still access the internal virtual sd card, but that's about it. The device can't seem to read or write to the main directory (although it can deal with going DIRECTLY to /mnt/sdcard). Ghost commander can't view the main directory, but ESFile explorer _can_, although root browsing in ESFile Explorer is UNchecked. It shouldn't be able to do what it's doing, and it's only doing it in one of two apps.
As a result, I've got no access to any root apps obviousy, but the wifi is having issues as well, it tries connecting but it can't complete the connection.
I'm toying with just wiping and flashing a new rom entirely, but figured I'd ask before I jump in the deep end of things. I keep backups of stuff, but it's still such a pain in the ass reinstalling things.
Any suggestions? I have a feeling it's something "simple", a link file or ... something which linux gurus would know about and I would not, not being a guru or disciple myself.
Thanks in advance!
If only you have working CWM installed. You could just flash this Superuser3.0.7.
Ah, but the plot thickens. I had superuser on there. I even uninstalled and reinstalled it. No dice.
Update: I said fuggit and did a factory reset. However, my wifi is still not fully connecting to my network although it has no problem finding it. I don't have a recovery image on the external SD and unless i get the network working, will have to wait until tomorrow to get a working microsd->usb adapter to put it on there.
I CAN still get into CWM, thank god.
Current rom is stock 8.6.6.19
Razorclaw gives an error when trying to root.
Also, when trying to moust USB from the recovery menu. it fails, saying "E:unable to upen ums lunfile (no such file or directory).
I am hoping this will magically get fixed after re-installing stock from the SD card ... and that my device isn't somehow crippled.
Sorry for the massive details, but more data = better.
It will magically get fixed
I recommend you flash any Totally stock ota. Then upgrade to the latest OTA, then use my tool PERI (or another) to install recovery and root. Then you should be all fixed up.
Well, it looks like I did get things back on track, but oddly enough, neither of the standard OR modified for root stock ROMs would work. One just wouldn't install, another failed halfway through. MD5s checked out and everything. I had put Revolver 4 beta on there sort of as a "just in case", and that one installed fine (and I was pleased when it displayed "installing Busybox symlinks").
Phew. CLose close call. Now to deal with the bull**** of setting stuff back up again.
However, the question remains: I'm assuming this whole thing happened because of the busybox update and me accidentally installing it to /bin instead of /xbin, and I think it "cleaned up" its own symlinks or something.
I'm not saying don't update your busybox, although I'm sticking with what works and **** upgrading anymore, just be careful...
Thanks for the help!
Recently I used the busybox installer to update my busybox version and it went through great... but after reboot it reverted back to the old version.. And I never touch it since.. don't want to take the hassle further..
There are certain 'plague' versions of busybox that simply don't work. I'd find that list of working BBs and STICK with one that's good. I'm still on 1.63 or someat like that.
Mangraa said:
[Hopefully I didn't miss this being covered somewhere else, as I am much the same as many of you and get beyond irritated with endless repeat questions. I searched using the best keywords I could think of for the issue, but to no avail. Apologies in advance if this has been covered!]
Alrighty. I've got a TF101, rooted it myself (thank you XDA), running 8.6.5.1.9 i believe, stock rom just with root. Used nvflash and Razorclaw. Worked like a charm.
It's been fine for the last 6 months, no issues. However, I decided to update busybox using its internal updater as I have before with no problems. I noticed I accidentally told it to install to /system/bin instead of /system/xbin, and the only reason I even knew about that was due to having to configure an app to find busybox in /xbin instead of /bin.
Now there's a problem. I can still access the internal virtual sd card, but that's about it. The device can't seem to read or write to the main directory (although it can deal with going DIRECTLY to /mnt/sdcard). Ghost commander can't view the main directory, but ESFile explorer _can_, although root browsing in ESFile Explorer is UNchecked. It shouldn't be able to do what it's doing, and it's only doing it in one of two apps.
As a result, I've got no access to any root apps obviousy, but the wifi is having issues as well, it tries connecting but it can't complete the connection.
I'm toying with just wiping and flashing a new rom entirely, but figured I'd ask before I jump in the deep end of things. I keep backups of stuff, but it's still such a pain in the ass reinstalling things.
Any suggestions? I have a feeling it's something "simple", a link file or ... something which linux gurus would know about and I would not, not being a guru or disciple myself.
Thanks in advance!
Click to expand...
Click to collapse
You may have been hit with a bug I introduced.
There was a bug with version 8.0 of my application.
There is not an issue with Busybox V1.20.1.
I apologize for this bug, the application symlinked all applets to Busybox and on some devices there are applets which are unique to the device and should not be replaced by those offered by Busybox.
A simple way to fix this is to simply reflash your rom. You do not need to wipe or clear any data. This will fix the issue and you can update Busybox normally with my application as long as it is version 8.1 or higher.
I apologize for the frustration I have caused, please let me know if I can do anything to help you further. I am trying to find people who were affected to see if I can help rectify the situation.
yeah me too
I guess I should have done a more recent backup. I tell you, there is a reason i have 38 updates waiting, everytime I start going through them, boom blows up in my face
Hello! So this should be an interesting first post. First, a little background:
I'm relatively new to this, and I've been trying to root my NEC Terrain for a little while now. I've followed the instructions on numerous pages in order to understand how to do things. And now I have been able to rip any partition from the phone. I've looked through everything I could in both the boot and recovery partitions but I haven't found anything I can use (I also explored /system but there doesn't seem to be anything in there either). Also, I tried to do everything on this page: http://forum.xda-developers.com/showthread.php?t=2337642 but I can't get SuperSU or TiBu to work. (As an aside, if anybody can point me in the right direction for the most recent su binary, that would be awesome). SuperSU wants to update the binary but fails. I would assume it's because it tries to install it directly into /system/bin, which isn't writable. If I could make it install it into /data/sbin, it might work, but that's off topic right now.
I would like to explore more of the partitions to understand what they are and what they do (I can't seem to find much information about them anywhere). I'm hoping to find something in the code to give a hint as to how to get into the bootloader. So, I have things like "aboot", "firmware", "MM", and "GROW", among others. Is there any way to decode or decompile those images so I can see what coding goes into them? Am I going about this the wrong way?
Thanks in advance to anyone that can help!
Maybe this will help you
In this post by E:V:A you can find some information about partitions and links to more!
I think latest SuperSU should be with latest SU binary (I can be wrong about this), so you could download "CWM / TWRP / MobileODIN installable ZIP" from this post and take one from "x86" folder.
Good luck.
Thanks for the links! Some of these may be very helpful. However, the su binary I got from that link was much older than the other most recent I had. It's a version 2.0 and they're up to at least 3.2 (I'll check the link again to see if I missed something). Also, for these phones, if anybody is wondering, they are ARM, not x86.
There seems to be only one direction I can go with this: Find an exploit that can run at boot that will interrupt it at the right time and allow editing of the /system partition. I can get a root shell with that script and a bind mount, but it's not enough to get anything else to work (ro.secure is still active, so there's no way to change it after the system is booted). Root is granted to root, and that's all. Any app requesting root does not get it.
The guys on that other thread said they got SuperSU and TiBu to work, but they provided very limited information and I can't seem to make them work. I wonder though, if that would matter as long as ro.secure is still enabled.