Database Info

Sending back to Tmobile, Unroot Q

I have rooted my G2X and since changing roms didn't do anything to help fix the rebooting issues I've decided to send it back for a different one. I just want to make sure that I won't have a problem once they get my phone. I followed the instructions at http://forum.xda-developers.com/showthread.php?p=14159600#post14159600 but for some reason when I click unroot it seems to get stuck at a certain point.
I did make a backup of the ROM that came with the phone, but i also tried a few custom ROMs as well as trying the LG updated ROM. Currently if I open Android Terminal Emulator and type 'su' it gives me a permission denied error. If I try the 'Root Checker" app under basic it will say the phone isn't rooted and busybox isn't installed but when I go under advanced half the time I click verify it'll say it's not rooted and other times it will say it is rooted... so it's confusing me. Advanced still shows busybox as not installed, so it's just root that changes between rooted and not rooted under advanced in root checker.
Root Checker Basic > "Sorry, you don't have root access. For detailed output, please use the advanced mode" - It will say that EVERY time I try.
Root Checker Advanced >
Root Access is not properly configured or was not granted.
Superuser.apk - com.noshufou.android.su - is not installed!
The application Superuser is recommended as it provides basic security and is available for free in the android market.
Standard su binary location:
/system/bin/su: No such file or directory
Standard su binary location:
/system/xbin/su: No such file or directory
Alternate su binary location: /sbin/su: Permission denied
SU binary not found in the system declared PATH
Then if I hit Verify Root again it may show the above a few times, but eventually (sometimes 1 click after) it will show:
Congratulations! You have root access!
Superuser.apk - com.noshufou.android.su - is not installed!
The application Superuser is recommended as it provides basic security and is available for free in the Android Market
Standard su binary location:
/system/bin/su: No such file or directory
Standard su binary location:
/system/xbin/su: No such file or directory
Alternate su binary location:
/sbin/su: Permission denied
Root user id:
Root not properly returning its user id
Root group id:
Root not properly returning its group id
So I guess I'm wondering why it's showing as not rooted EVERY time under basic, but showing rooted and unrooted under advanced. If terminal emulator is giving su a permission denied error instead of a # doesn't that mean it's not rooted? Sorry for the long post, but I can't take the chance of sending the phone back rooted. Also, when I used the LG Update it updated my baseband to July 15th which isn't the one that came with the phone or the one that was with the stock rom i'm using now... could that be an issue? If anyone can help me I'd really appreciate it, thanks!

Also, since when I used the LG update it updated my baseband is it possible to revert it back to the stock baseband that was on it when I purchased the phone?

since you already did the LG update it seems like with the new baseband- why not use the stock 2.3.3 rom found here:
http://forum.xda-developers.com/showthread.php?t=1196019
i believe that after you flash this rom you will lose root- so you should be able to send back to tmobile with no prob- just make sure to flash back to stock recovery.

thanks for the reply, was actually in the process of doing that as you posted lol... thanks again, appreciate the help, at least now i know i'm going in the right direction ^_^

I installed 2.3.3, flashed back to stock recovery... terminal emulator still gives permission denied when i type 'su' and root checker still says not rooted for basic and switches between rooted and not rooted under advanced... is there a way to verify my phone isn't rooted besides root checker? I don't want to send back a rooted phone and the root checker is giving me mixed results under advanced so i don't know what to do at this point

Urgent: I cannot unroot!

The SU Binary file is corrupted on my device, from trying to replace it with another. Shortly after replacing the SU file, I was unable to open SuperUser.apk. I reset my phone, hoping this would unroot my device. I was WRONG. My device is now currently rooted, with a corrupted SU file, so i can't even unroot via SuperSU Application. I've also tried terminal commands to remove the SU file, but it needs root access, which i cannot access due to the SU file! HOW CAN I UNROOT MY PHONE , THUS GETTING RID OF /SYSTEM/BIN/SU , SO I CAN SUCCESSFULLY RE-ROOT MY PHONE?
PLEASE LEAVE A SUGGESTION, OR LINK ME TO SOME UNROOTING SOFTWARE, I'M IN DESPERATE NEED OF HELP
Device: Kyocera Rise
Model: C5155
OS: 4.0.4 (ICS)
Kernel: 3.0.8-perf
Build: IML77

[Q] Loaded Clockworkmod Superuser Update - Lost Root - Note N7000

Hi All.
Sorry about the noob question, I am not a developer at all, and the only reason I rooted my Galaxy Note N7000 was so that I can update the ROM to the newest version of KitKat once the ROM is stable.
The problem is that last week I flashed the PhilZ-cwm6-XXLT4-OXA-4.93.6-signed file to the phone and it rooted successfully (Superclean asked for root access, I allowed it, and it appeared in the log of Superuser)
The problem happened last night when there was an OTA update for superuser, it said Su Binary needs updating, and I hit yes. I then lost root access as per Titanium backup.
I did a search and someone suggested removing and reloading the original superuser APK but that did nothing.
It seems the binary update pooched the root. Anyone successful in getting it back, or knowing how to?

Anyone can help on this?
It appears from the comments in Google Play that many people that were prompted to update the binary from superuser were left without root.

I lost root access on apps once.
All I did was:
1. re-install "superuser" from Google Play.
2. when opening "superuser" app, it asked to update the SU Binary.. and I allowed it to do so through recovery (TWRP/CWM). (I use CWM).
3. the phone will restart into recovery mode automatically, updating the SU Binary, then phone will restart again back into the OS.
This is all it took for myself to gain SU access again.
This should work if the ROM you're using truly does allow SU access.
OTHERWISE.
You could get the latest Super User.zip for your phone, and run it yourself through TWRP/CWM.
Hope this helps, or at least leads you to an answer.

new su binary is the culprit
Hello,
I too lost root after the su update - Superuser would not prompt any more, and all requests are denied after a timeout. Tried deleting Superuser data, deinstalling and reinstalling Superuser, same with some of the apps, but no avail. Then I noticed that sometimes after reboot /system/xbin/su worked when in android debug bridge shell, so I could get root. Then I replaced the su binary with a copy (in my case of OTA rootkeeper), and all started to work again.
Steps to replace:
1. become root in ADB shell using existing su binary
2. remounting system rw
3. bring replacement su to a ext-fs-partition of your device (needed for setuid)
4. make sure file permissions are set to 06755 (-rwsr-sr-x)
5. exit root
6. become root with newly copied su binary
7. replace defect su with new su
8. remount system ro
Hope koush will stop delivering this defect su soon ... I did mail him already ...

[Resolved] [Q] Help needed rooting G Pro! T_T

*Since this problem can happen to other LG devices, I'm writing here.
-Summarized Question for Busy XDAers-
1.Installed su binary and busybox through Android System Recovery 3e.
2.Can get root access from LG Recovery mode, half access on ordinary boot+adb shell, Permission denied on terminal emulator app. SuperSu not working, and 'root' is granting permission every 5 minutes.
3.HELP PLEASE!
-Full Question-
Maybe it can be a real noobish question, but I need help rooting my G Pro.
LG started Kitkat update a week ago, and G Pro also got Kitkat update.
I tried to root my device using old methods, and new methods for other G devices, but none of them worked.
So! I tried making one for me, using Android System Recovery 3e(maybe it could be a problem?)
I booted my device to recovery using
Code:
'adb reboot recovery'
and sideloaded zip file containing su binary and busybox.
Of course I signed it with testkey, so I could get SuperSu, su binary, and busybox installed on my system.
But, after rebooting my device, I felt something went wrong.
I typed
Code:
'su'
command on terminal enulator, and got
Code:
'Permission Denied'
error.
Assuming it's related to permission and owner of su binary, I tried
Code:
ls -al /system/bin/su
.
Here's the result:
Code:
[email protected]:/ $ su
Permission denied
1|[email protected]:/ $ ls -al /system/bin/su
-rwsr-sr-x root root 85096 2008-08-01 21:00 su
It seems...nothing's wrong!
So I tried with adb, and got # without asking Superuser app.
But I couldn't mount system, as well as other commands require root access.
I removed SuperSu and downloaded Superuser by ChainsDD, but that didn't work.
Instead, I could see on log that 'root' was granting permission every 5 minutes.
Not knowing what the problem is, I rebooted device to LG recovery(diffrent from Android Recovery 3e).
I could access adb from there, and got root access and removed some garbage apps.
Then, it means su binary and busybox is working.
What is the problem??? Please help!
EDIT:It was binary version problem lol

[Q] How to edit camera features file

I want to edit camera_features.xml file but it needs root access, I don't want to root device but I think there is a way through ADB or using some third party apps that uses super user permission to edit root files
Please I'm sure there is way to edit it without rooting device by using special third party apps but I need someone who know how to

Temporarily root Android by putting a suitable su binary into Android's filesystem - preferably /data/loca/temp - and making it executable.
https://forum.xda-developers.com/attachments/su-binaries-zip.5566949/

I don't find the directory data/local
And does it require root to put the su file there

Noticed that I made a spelling mistake:
The directory recommended to copy su binary into is
/data/local/tmp
what exists on all Android versions since beginning and by default is mounted as RW

How can I reach the folder, which app can reach and copy files to root data/local/tmp without rooting device

You use ADB - of course requires USB DEbugging got enabled on device in question.
To clarify things: the su binary is the root functionality you want to add to Android.

I tried to use adb push su data/local/tmp but it doesn't work

xXx yYy said:
You use ADB - of course requires USB DEbugging got enabled on device in question.
To clarify things: the su binary is the root functionality you want to add to Android.
Click to expand...
Click to collapse
I know but I think there is another way using apps that uses system apps permissions
Such as editing root file of the device as official device updater