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

Issue with version of su files

Hello,
I update my asus last week but i forgot that i have install root in April to do some stuff during this time...
so i 'm not any more root i reinstall today motochopper to have last version of root install spent well.
but when i launch super user it told me that the binary su is not updated.
So i will move the su present in motochopper.zip to sbin/system,,, but i can't because
adb shell tell me permission denied and when i enter "su" i have always $ and not the # ...
So i'm a little lost how to delete the old file su in sbin and put the newest .. i test "mount -o rw,remount ...
but nothing works always issue with permission.
android v4.2.1
kernel : 3.1.10-g89b05a
build : JIP40D
Thanks a lot
Best Regards

reikanou said:
Hello,
I update my asus last week but i forgot that i have install root in April to do some stuff during this time...
so i 'm not any more root i reinstall today motochopper to have last version of root install spent well.
but when i launch super user it told me that the binary su is not updated.
So i will move the su present in motochopper.zip to sbin/system,,, but i can't because
adb shell tell me permission denied and when i enter "su" i have always $ and not the # ...
So i'm a little lost how to delete the old file su in sbin and put the newest .. i test "mount -o rw,remount ...
but nothing works always issue with permission.
android v4.2.1
kernel : 3.1.10-g89b05a
build : JIP40D
Thanks a lot
Best Regards
Click to expand...
Click to collapse
Hi, i am a new tf300t user. It seems that nobody can root latest stock 4.2 with motochopper and i read that all failed with rootkeeper as well. I bought my tf a week ago and it was with the latest update, so i coundt root it. I downloaded from asus website the previous stock firmware (V10.6.1.15.3 for WW SKU which is my tablet), extracted it to internal and i got a notification for downgrade. I did it and 10 min later i rooted with motochopper. Then i opened su and updated binaries. Installed voodoo ota rootkeeper, backed up root and temporarly unrooted. I then updated again via OTA notification (only 50mb) to latest fw and i ota rootkeeper managed to restore root successfully. So im on latest with root access.

H,
Thanks for you reply i will try this and if it doesn't work i forgot root it was just to recover a file and application to recover need to be root.
Thanks again.
Bregards

[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 ...

SU request hangs after root attempt

Hello world,
I try to make something useful out of my Samsung Galaxy Note 10.1 (GT-n8020), so I've started with reinitializing the device with kies, which got me a fresh android kitkat 4.4.2 rom (build: KOT49H.N8020XXUDNI2). After that, I wanted to flash supersu, of course - I've used chainfires cf-autoroot (CF-Auto-Root-p4notelte-p4noteltexx-gtn8020.zip - cant post links, sorry)
I've also flashed philz recovery which works quite well, over odin.
The problem for now is, I cant use the super user binary:
1. The binary was successfully flashed via odin on the device, like the supersu apk. Opening the app just displays a missing su binary, any other app which requires root cant locate or call the file...
2. The following permissions are set on the su file
[email protected]:/ $ ls -la /system/xbin/su
-rwsr-sr-x root root 96144 2015-09-15 14:44 su
3. I've enabled usb debugging because people like to use magic even if this has nothing to do with the main problem
4. I've tried to execute su via adb shell, but it just hangs.
So if anyone could help, I'd be pretty happy - if not, I'm going to throw this f*ck!ng piece of plastic into the woods.

Alright, using N8020-CWM-6.0.2.8-Darkman.tar.md5 as recovery and CF-Auto-Root-p4notelte-p4noteltexx-gtn8020.tar.md5 as root finally worked.

Unrooting Androidx-86

I naturally can't access apps which require the device to be unrooted in my androidx-86. Can anyone help me out?
version - 9

Android is got rooted if su binary is present in Android's /system/bin and/or /system/xbin directory.
To unroot Android simply locate the su binary and delete it. Take note doing so you loose root access forever.
Also uninstall the SuperUser.apk if present.