Database Info

Unroot from Super OneClick

Alright guys....Need help. How do I unroot from Super OneClick. I have the official TMobile 2.2 ROM as OTA..however it's failing because its checking to see if its rooted. Pleasant. So If someone could point me in the right direction it would be appreciated.

you sure its 2.2? OTA?

Yup. 100% Sure. 112MB file download. File is called Blur_Version.3.6.360.MB525.T-Mobile.en.US.zip with a Blur_Version.3.6.360.MB525.T-Mobile.en.US.crc file as well. Build.prop indicates that it is 2.2.1 /3.4.2-107-JDN-9/34.4.9. Getting completely hung up on this Status 7 error though. It is picky as hell, and I don't have a out of the box backup I can use to try as stock. It is definitely checking files though. It's like christmas and staring at your presents knowing what it is, but you can't unwrap it. Uggh!!

Root can't be your problem. I've updated to that release; Android 2.2.1, Blur 34.4.9, Build # 3.4.2.107_IDN-9, while my system was rooted. My phone was quite customized (Go Launcher with some "foreign" widgets and no Blur apps/widgets except for the Email app to get at my work e-mail) and everything came up OK. I was rather surprized how smoothly it all went. All my data (seemed to be mostly e-mail) had to be re-synched (this happened automatically), and it took one reboot to clear a message about non-Moto battery that was displayed after the first boot. Basically it all is where it was, except, of course, for root (I tried the latest, 1.7, SuperOneClick but it's looping no matter what I do).
Good luck.
[Added]
Well, well. It turned out that even though it seemed that SuperOneClick was failing (looping at trying to mount a partition R/O) it actually it did it's job! I just fired up RootExplorer and lo and behold a confirmation from Superuser for root popped up, got accepted, and I can start renaming the bloatware again. Woo hoo!

For me it ended up being the root. I was able to unroot with Z4root, and as soon as I did no more issues. I ended up saying screw it and wiped my phone all the way back to factory. Figure it's just better to rebuild it all cleanly and be done with it. I'm just happy its an official rom now.

mind posting a nandroid back up please?

It's really insane to sanction against rooting a phone. I can't image a computer denying me administrator's rights.

runeblade said:
How do I unroot from Super OneClick.
Click to expand...
Click to collapse
You can simply do it manually using Root Explorer. delete followings AS ROOT USER and reboot. that's all!
1. /data/data/com.noshufou.android.su
2. /system/app/superuser.apk
3. /system/bin/su & busybox
Also, it can be done via adb connection.
adb shell
$ su
# mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
# rm -r /data/data/com.noshufou.android.su
# rm /system/app/superuser.apk
# rm /system/bin/su
# rm /system/bin/busybox
# reboot

I second this.
jboogie3 said:
mind posting a nandroid back up please?
Click to expand...
Click to collapse

Easy root method (Triumph is Factory rooted)

Found this over at SDX Developers
It's so easy a caveman can do it.
http://forum.sdx-developers.com/index.php?topic=17172.0

Be aware that if you do this you have no control over what has root and what doesn't. The "gingerbreak" way, along with the Android SU, does.

couldn't a person just install superuser?

Intercepter said:
couldn't a person just install superuser?
Click to expand...
Click to collapse
yes you can.... ive tested all of the ways of rooting this phone and this one is the easiest! after you do it just install superuser from the market and your all good.

Hey that's my post lol! Yeah well the thing about malware and root access that no one hardly knows is that all these apps that use root exploits to cause harm, they never request su permissions because they use there own exploit to gain root. So superuser wouldn't prompt you on an exploit root being ran. Superuser just prompts when some app requests /system/bin/su or /system/xbin/su. If you want to keep your phone safe its a mater of knowing what you install on your phone. Even with superuser your not safe from root exploit attacks!
Me personally I like nit having to allow everytime I install a new root app. And I know what I install so I never worry about malware.
Sent from my MOTWX435KT using Tapatalk

I noticed that his fix is to basically link su to sudo, which allows "root" programs to run the included superuser applet.
So does this mean someone could just install the SuperUser app without going through the usual rooting process? Is Gingerbreaking unnecessary then?
what concerns me is that if these phones ship with sudo enabled and no root password, then any app can get root without any special effort. That means the Triump is VERY insecure. I'm wondering if we can safely remove sudo and solve that particular problem.

Maybe they did that to make fixing them easier, for when a phone got sent in they could gain root and do whatever they need in it, then turn it back off real quick. This is kinda like the tether menu being hidden but not removed on the OV. How stupid do they think people are?

I don't think it's a question of stupidity - it's more one of knowledge. They don't anticipate the run-of-the-mill user to be digging through the file structure of the phone for something they have no idea of what it does or how it works.
And I'd have to agree - the non-technical people have no desire to start digging through the phone, but rather, to use it as is.

Therefore......
So if this could be made a script. Then we could un-root just as easily for protection. I only need it for barnacle.
root
--------
sudo
ln -s /system/xbin/sudo /system/xbin/su
ln -s /system/xbin/sudo /system/bin/su
unroot
-------
sudo
rm /system/xbin/su
rm /system/bin/su
RIGHT?

Edit: the "shebang" line needs to be changed. Not sure to what. You may be better off just typing in the commands yourself.
Not tested, but this should work.
The root script:
Code:
#!/bin/sh
#filename: rootme
echo "Rooting Device"
sudo
ln -s /system/xbin/sudo /system/xbin/su
ln -s /system/xbin/sudo /system/bin/su
echo 'Root has been achieved'
The unroot script:
Code:
#!/bin/sh
#filename: unrootme
echo "Un-rooting Device"
sudo
rm /system/xbin/sudo /system/xbin/su
rm /system/xbin/sudo /system/bin/su
echo 'Un-root has been achieved'
Make these files somewhere and *cd* to that directory. Type either
Code:
./rootme
or
Code:
./unrootme
Hope this helps someone.

TomXP411 said:
I noticed that his fix is to basically link su to sudo, which allows "root" programs to run the included superuser applet.
So does this mean someone could just install the SuperUser app without going through the usual rooting process? Is Gingerbreaking unnecessary then?
what concerns me is that if these phones ship with sudo enabled and no root password, then any app can get root without any special effort. That means the Triump is VERY insecure. I'm wondering if we can safely remove sudo and solve that particular problem.
Click to expand...
Click to collapse
Yes, that is true that an app could very easily gain root access on the triumph. HOWEVER, as pointed out by b_randon14 above, practically all malware apps use a root exploit to gain root priveliges. This means that even an unrooted device is susceptible. As an example, take a stock samsung captivate. It has no root, and no way to gain root, without flashing a custom rom/kernel. However, if an app used the psneuter exploit, it could still gain root access. (Btw, that is how I originally rooted my captivate, using super one click with the psneauter exploit)
So really, the triumph is no less secure than any other android device. Plus, the triumph is the only android device, aside from dev phones such as the nexus one/nexus s that come pre-rooted. So a triumph specific malware app would have to be written.
Personaly, I like the su+superuser.apk method of rooting, but that is because it is the only method I have ever used. And remember, if you prefer to have su+superuser.apk, you either use gingerbreak, or just use this trick and then install superuser.apk.
Sent from my SAMSUNG-SGH-I897

Yeah and plus an app has to be designed to gain root its not like any old app can just up and decide to request root and start destroying! And stock without any root(I.e. my method or gingerbreak) an app doesn't call /system/xbin/sudo it would call /system/bin/su or /system/xbin/su. Plus I mean if you used gingerbreak you should realize that an app can get root without going through superusrr or calling on su. I mean how else do you think gingrrbreak app gets root in the first place to copy su and superuser? Through the gingerbreak root exploit!!
Sent from my OC'ed Triumph!

The concept of an app being able to gain root makes it just as dangerous as a malignant virus for Android. The only difference is, it's not a virus. It's a nice, helpful, and otherwise very good program. Lucky for us.
I'm working on a batch script that does the same thing as these instructions, anybody vaguely interested in using it (should it be put out)?

primetechv2 said:
The concept of an app being able to gain root makes it just as dangerous as a malignant virus for Android. The only difference is, it's not a virus. It's a nice, helpful, and otherwise very good program. Lucky for us.
I'm working on a batch script that does the same thing as these instructions, anybody vaguely interested in using it (should it be put out)?
Click to expand...
Click to collapse
I wrote one and posted on xda, I think, but the shebang line needs some adjustment to find sh. Hope that helps.
Sent from my rooted Moto Triumph

Why is this not working for me? I downloaded terminal emulator from the market, typed: "sudo" and get:
sudo: permission denied
$

tsac said:
Why is this not working for me? I downloaded terminal emulator from the market, typed: "sudo" and get:
sudo: permission denied
$
Click to expand...
Click to collapse
Did they patch it? These two lines of code run from ADB should "root" the device... and sudo is just there.
adb -d shell sudo ln ln -s /system/xbin/sudo /system/xbin/su
adb -d shell sudo ln ln -s /system/xbin/sudo /system/bin/su
Now you may not be able to run "sudo" alone, you may need to specify a command with it too? Unfortunately I can't try it again, because all of my phones are rooted now
In the event this didn't work, GingerBreak should work regardless.

I'll give it a try when my phone finishes charging.....Thank you

tsac said:
I'll give it a try when my phone finishes charging.....Thank you
Click to expand...
Click to collapse
Sure. although I would still recommend Gingerbreak instead...it's more complete and contains Superuser as an extra security measure.
Sent from my MOTWX435KT using Tapatalk

Never got to try anything....Phones screen is dead. You know how people describe the flashing screen when turned on and off? Well mine flashed once and it has not worked since... Hopefully virgin mobile will honor the 1 year factory warranty. I did absolutely nothing to this phone. It just took a crap. Removal of battery does nothing. Phone will receive calls but there is nothing but a backlight. Tried several different methods. Horrible phone....Should be recalled
Thanks for your trying to help me.
Sent from my reliable homebuilt gaming rig using FireFox

rooted my dad's triumph...question though...couldn't I flash clockworkmod via rom manager or do I have to go the long way?
edit: nvm, i see rom manager doesn't support the triumph

[Q] My phone obviously has root... but not according to the shell. Need some help!

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

How do I unroot WITHOUT factory restore?

Hello everyone! I have a really stupid question, but here it goes... I have crappy hearing so I can't use my nexus 4 with its factory volume. I figured out how to increase the volume with a simple build.prop edit. My question is how can I simply unroot the device after making my edits without restoring back to stock. I don't like to leave that security door hanging wide open. All my search results about unrooting seem to be for prepping a device for a warranty return or just going full stock. Before anyone says "just run cm10" since it has a toggle and its better anyway, let me say that I don't want to for this device. I run and love cm on my gs3 and n7, but I want my n4 to be stock so it gets the new software updates from Google. My gs3 is my main phone, the n4 is my toy.
Sent from my Nexus 7 using Tapatalk 2

I really do not think you can unroot WITHOUT factory restore.

Madalinsuny said:
I really do not think you can unroot WITHOUT factory restore.
Click to expand...
Click to collapse
of course you can, either use the easy way of opening supersu going to settings and picking full unroot or by issuing these commands from a terminal with adb:
adb shell su -c "mount -o rw,remount /system"
adb shell su -c "rm /system/bin/su"
adb shell su -c "rm /system/app/Superuser.apk"

Dude that's awesome, thank you. I had doubts that unroot to work because, well how can a running program completely remove itself. Removing superuser via titanium backup crossed my mind, but then again I just wasn't sure it would fully clear it out. I well def be using your adb recommended commands. Thanks again!
Sent from my Nexus 7 using Tapatalk 2

Rooting my New (New) Note Edge ... the hard way

I'd like some input...
I have already killed, bricked, destroyed one Note Edge., maybe two but shh.... the first one wouldn't even power on, so we won't say anything about that one. (http://forum.xda-developers.com/note-edge/general/dead-jim-sm-n915p-rom-downgrade-failure-t3155303) I got that one replaced and promptly killed it trying to root.
I have a Galaxy Note Edge, SM-N915P version 5.1.1. I want to root the phone, but the last CF Auto root I used caused a boot loop, and once I do that, I don't have the stock recovery which makes it hard to do any further updates. Sprint was nice enough to cover the first one under warranty, but I doubt they will be so understanding if I brick this one as well.
I have been doing some searching on the Google machine, and I thought I had found a safe way to root the phone. I started by using an adb pushed and pushed the su and busybox to /data/local/tmp and then issued a chmod so that I could execute them. Then I tried to issue
su that I could get temporary access to root, and use busybox to remout the /system/bin so that it was read-write, but that isn't working.
I have tried two different SU binaries, issuing the command /data/local/tmp/su busybox mount -o rw,remount /system. With one SU file, I get no response, just a return to the cmd line. The other I get "only position independent executables (PIE) are supported" .
I guess my first question: Is my methodology sound? I suppose I could be using outdated, or incompatible SU binary file. Should what I am trying work? If not, what is another way to gain root, without using CF Autoroot and tripping the knox counter and risking a boot loop. I would rather not have to pay $40 to one click root either. However that is far cheaper then a new phone.
Thanks for the input.

No root for 5.1 yet
Sent from my SM-N915P

No root for 5.1.1 Yet?? Well that would explain the boot loop. :sigh:

Root for 5.1
Any word on this yet? I also have the "only position independent executables*( PIE) are supported" error. Thanks