Well guys i used a 1 click root to root my lg esteem from metropcs.
Worked perfect, than an update came and the phone become unrooted.
So i changed the permission of su in system/bin/su
It worked! my phone was un rooted again
Than this is my fault and the part iam stuck on -.-
I used root explorer and changed the permission of Su to match the other files.
I restarted and lost root! crap
Now whats even worse is, i cant use SU in adb shell any more
I just get the $ symbol everything i enter the su command under the adb shell and it wont give me root access to even changes the permissions back.
So now what i do, i cant use one click root anymore, and i cant get root with adb shell:
HELPPPPPPP
XD
I can see it is a real complicated situation and no doubt you messed up everthing. Maybe hard to find someone can help here. Give us the solution when you get it. Thanks.
I have heard of people using the lg recovery tool to recover bricked phones,
when it detects your phone isnt booting correctly it re flashes it.
But the problem is, my boots perfectly , so it just tells me my phone is up to date.
There has got to be a way to trick it some how....
Anyway off topic, how do i get my root back XD
Install root binary again.
Accidentally sent from my Google Nexus S using XDA Premium
You mean re install Su binary file to bin and xbin folders?
Or am i missing something?
ok i was able to change the permissions back on the system/bin/su file
Now things get werid,
I still cant run su command in adb shell as root
I checked the permissions of system/bin/su
i set chmod to 6755
Thats right isnt it?
The permissions DID CHANGES
so i dont get why root checker is telling me i dont have permission still......
I got it working i re installed binary 3.0.3 and i had root access again.
Than right after i set chmod to 6777 on /system/bin/su
i lost root again, what does this mean?
Related
Edit: Im stuck. I cannot root my phone because something is wrong with Superuser.apk, and I can't uninstall superuser because I can't get root. And if I try to install Superuser it just fails because it's already in there. So I have no idea what to do now, I need to return this phone to the Verizon store and I can't get the Superuser app off the phone. Any ideas?
http://ip208-100-42-21.static.xda-developers.com/showthread.php?p=6978379
should work. I did this to upgrade from market the version that came with the lag fix from the market.
I couldn't get that to work..
What happens when you adb shell into the device, and do 'su'. If you get a # prompt, you have root.
You don't need Superuser.apk to have root access. You can always run the rage.bin process to get a root shell. From there you should be able to at least rename Superuser.apk to something like Superuser.apk.old.
Yeah, I can type su and get the # prompt. Is this what runs the rage.bin:
adb shell
cd /data/local/tmp
chmod 0755 rage.bin
./rage.bin
?
Sorry, Im new to the ADB process. How would I go about renaming? I wanted to use something like root explorer to find the file and remove or rename it, but I can't get any root apps to work. Obviously because Superuser doesnt function I don't get permission prompt. Root explorer either crashes or says to restart to get the permission prompt.
GHII said:
Yeah, I can type su and get the # prompt. Is this what runs the rage.bin:
adb shell
cd /data/local/tmp
chmod 0755 rage.bin
./rage.bin
?
Sorry, Im new to the ADB process. How would I go about renaming? I wanted to use something like root explorer to find the file and remove or rename it, but I can't get any root apps to work. Obviously because Superuser doesnt function I don't get permission prompt. Root explorer either crashes or says to restart to get the permission prompt.
Click to expand...
Click to collapse
If you can do "su" and get the # prompt, forget about rage.bin. You have root access, it's just Superuser that's screwed up.
go to your # prompt and do the following
cd /system/app
mv Superuser.apk Superuser.apk.old
See if that gets you any further as far as being able to re-install
I appreciate your help more than you know, really, thanks. I tried that and I get 'failed on 'Superuser.apk' - No such file or directory. Can it be installed anywhere else, like in a temporary directory?
When I try adb install Superuser.apk it starts to then says:
pkg: /data/local/tmp/Superuser.apk
Failure [INSTALL_FAILED_ALREADY_EXISTS]
So I tried what you just mentioned but using the above directory:
#
cd /data/local/tmp
mv Superuser.apk Superuser.apk.old
and it didn't give me any errors, just the #..but when I went and tried to install Superuser again I got the same error as above.
Ok, new update! I remember someone asking me to do ls in adb shell to get a list of what's in there..so, I did that with /system/app and I got a list...at the very bottom of the list was superuser.apk..this whole time i've been messing with Superuser.apk, a capital S. So, I used your mv method on the lower case version, seemed to work..but when I did adb install Superuser.apk I get Failure [INSTALL_FAILED_UPDATE_INCOMPATIBLE]
Didn't work but I feel Im getting closer
Wow, i just happen to look and the superuser app was no longer showing up in my apps..problem solved. Thanks again for everyone's help in this thread and others.
Just wanted to share that I lost root with installing this OTA update. I used the Photon Torpedo method and still have the scripts, I can get root on console but unless I'm already root if i run "su" I get permission denied. The permission denied is in the log for superuser however the prompt doesn't show up.
I probably won't have time to dig into this further until the weekend but wanted to have a thread for others who are wondering..
stever5 said:
Just wanted to share that I lost root with installing this OTA update. I used the Photon Torpedo method and still have the scripts, I can get root on console but unless I'm already root if i run "su" I get permission denied. The permission denied is in the log for superuser however the prompt doesn't show up.
I probably won't have time to dig into this further until the weekend but wanted to have a thread for others who are wondering..
Click to expand...
Click to collapse
You are suppose to lose root when you apply an official OTA root. Just re-root it using the Photon Torpedo method. I am confused where you are lost at.
ericdabbs said:
You are suppose to lose root when you apply an official OTA root. Just re-root it using the Photon Torpedo method. I am confused where you are lost at.
Click to expand...
Click to collapse
$ /system/bin/su
Permission denied
$ su
Permission denied
rerun (I don't have ADB to copy/paste on this computer):
$ cd /data/tmp
$ ./photon-torpedo.sh
.... the usual... end result..
[email protected]:/data/tmp# ./install-su.sh
[email protected]:/data/tmp#
Note: no errors, also did this manually to make sure..
exit / rerun terminal (or anything else requiring root)
$ su
Permission denied
Those steps worked on previous updates however don't work with this update. Not having ADB I'm unable to type a lot of commands easily to diagnose further..
I used the one click root and have no issues at this point. SU running ok
- Installed Update
- Ran Torpedo like before
- Root Access
Case Closed
Update superuser
Sent from my MB855 using XDA App
$ cd /data/tmp
$ ./photon-torpedo.sh
[email protected]:/data/tmp# /system/bin/mount -o remount,rw /system
[email protected]:/data/tmp# chmod 4775 /system/bin/su
Do this if updating superuser fails
what's new in this version? work with the unlocked bootloader
I know with the previous OTA update, we had to flash back to stock, or some people were having issues with it. Is that the case with this one as well? I have a feeling I answered my own question, but I am not sure I am correct on the above information. So if anyone has any info, I'd really appreciate it. Thanks.
ok guys so i wanted to post this because ive been sitting here for two days trying to regain root on my prime after doing a factory reset to speed it up! It was pretty damn slow so i bit the bullet and its much faster now but unfortunately no root I tried to use the debugfs root method and it wasnt working multiple errors and still no root. Now a few things first i had used voodoo in the past to protect root, it sorta worked, voodoo stated my device had root but no program could actually get root. Also like i said the debugfs method was a no go and a few other options i tried. Im currently locked and rooted with full permissions. These are not my instructions but they solved my problem way too easily so i had to share. I found this over in the tf300 forums at this thread Nooktablets tf300 rooting thread i dont know if this will work if u have never rooted or never once backed up.. But i was having problems with errors in other methods so try it out and let me know how it works..
directions:
1) Download the unsure su from here and put it somewhere on your C Drive. It will be used in the following push step (Assuming windows) (This is a WIDE OPEN su without any controls). (sparky root i believe?)
https://www.dropbox.com/sh/jcpilpgoeta516e/tCB-Ep-3YQ
2) start a CMD window and logon to adb
3) su -
4) verify you have root:
id
uid=0(root) gid=0(root)........
If you don't you can try these instead of 'su':
"/system/su-backup" or "/system/su_backup"
5) remount system as RW:
mount -o remount,rw /dev/block/mmcblk0p1 /system
6) make a backup of current su just in case in adb
cat /system/bin/su > /system/bin/su1
7) open a new CMD window and push the su binary from step 1 to the sdcard using the path from where ever you put it.
adb push c:\<some path>\su /sdcard/
8) Then copy it to /system/bin from the adb session where you su'd.
cat /sdcard/su > /system/bin/su
9) Change permissions for SU
chmod 6755 /system/bin/su
10) download superuser (NOT SUPERSU) from play store if you do not have it already.
11) have superuser upgrade the su binary. It may fail to remount system as RO. Just rerun the update in superuser and it will work the 2nd time. You don't need to remount system as RO manually since superuser update of SU will do that for you.
12) congrats. your now rerooted.
13) remove the backup after you know your OKAY.
mount -o remount,rw /dev/block/mmcblk0p1 /system
rm /system/bin/su1
mount -o remount,ro /dev/block/mmcblk0p1 /system
franky_402 said:
ok guys so i wanted to post this because ive been sitting here for two days trying to regain root on my prime after doing a factory reset to speed it up! It was pretty damn slow so i bit the bullet and its much faster now but unfortunately no root I tried to use the debugfs root method and it wasnt working multiple errors and still no root. Now a few things first i had used voodoo in the past to protect root, it sorta worked, voodoo stated my device had root but no program could actually get root. Also like i said the debugfs method was a no go and a few other options i tried. Im currently locked and rooted with full permissions. These are not my instructions but they solved my problem way too easily so i had to share. I found this over in the tf300 forums at this thread Nooktablets tf300 rooting thread i dont know if this will work if u have never rooted or never once backed up.. But i was having problems with errors in other methods so try it out and let me know how it works..
directions:
1) Download the unsure su from here and put it somewhere on your C Drive. It will be used in the following push step (Assuming windows) (This is a WIDE OPEN su without any controls). (sparky root i believe?)
https://www.dropbox.com/sh/jcpilpgoeta516e/tCB-Ep-3YQ
2) start a CMD window and logon to adb
3) su -
4) verify you have root:
id
uid=0(root) gid=0(root)........
If you don't you can try these instead of 'su':
"/system/su-backup" or "/system/su_backup"
5) remount system as RW:
mount -o remount,rw /dev/block/mmcblk0p1 /system
6) make a backup of current su just in case in adb
cat /system/bin/su > /system/bin/su1
7) open a new CMD window and push the su binary from step 1 to the sdcard using the path from where ever you put it.
adb push c:\<some path>\su /sdcard/
8) Then copy it to /system/bin from the adb session where you su'd.
cat /sdcard/su > /system/bin/su
9) Change permissions for SU
chmod 6755 /system/bin/su
10) download superuser (NOT SUPERSU) from play store if you do not have it already.
11) have superuser upgrade the su binary. It may fail to remount system as RO. Just rerun the update in superuser and it will work the 2nd time. You don't need to remount system as RO manually since superuser update of SU will do that for you.
12) congrats. your now rerooted.
13) remove the backup after you know your OKAY.
mount -o remount,rw /dev/block/mmcblk0p1 /system
rm /system/bin/su1
mount -o remount,ro /dev/block/mmcblk0p1 /system
Click to expand...
Click to collapse
This procedure worked for my TF201 with partial root after updating to 4.1.1. The only issue was step 11, the forced update of Superuser's su binary. The message was “Making sure new su works..." but the result after several minutes was still "Waiting....". Should I rerun the forced su update? Despite this Vodoo OTA Rootkeeper did restore root without problem and Root Checker says thumbs up.
At this point, is there anything to do like switching to SuperSU that would make the root more future-proof?
Thank You! I have been trying to regain root after jellybean ota on my Motorola Atrix HD for the last week and a half. Finally success . I cant thank you enough!
After I upgraded ota to jb. Su ceased to work entirely the binary would not update. and all root apps were no longer working. i did have a su-backup but was getting nowhere in my attempts to use the app. i was only able to invoke a root prompt. i looked all over the internet not just the xda forums. i tried mattigriffs root restore. i typed into a command prompt for several hours each day.. all i ever got was a root prompt in adb shell. no prompt on the phone emulator. this is the only page that has worked for me. i noticed right away that the code was written differently than any other that i tried. also the su used is different(it is described as wide open) any way because of this i felt that others who were /are in the same boat. no root. may be able to get root back. I hope that answers your question. have a great day! .
You should be able to switch to a different root app. Never used this method but I have switched from superuser to supersu. Install superuser and run the binary update. Should tell you your binary is out of date with the name of the binary for the other root app. Update and reboot, then go back to superuser and check the binary update again. If it says it's up to date, uninstall the old root app and move superuser to /system/app. Reboot and you're good to go!
Sent from my Atrix HD MAXX
i think i tried that. istalling and uninstalling and subdstituting su and supersu. was not updating no matter what. also my adb push was not working so i copy pasted the su with my laptop while in adb shell. also updated su binary while in shell. it was already a system app from my previous attempts. anyway im good now
any one get it to work with no root/first time root? my prime wouldnt update via ota once on ics so i had to use the sd card update method to update. and from then on i never rooted again i then updated to jb and until 2 days ago i wanted to reroot but noticed there was no root method for jb yet. voodo root keeper just has super user app installed and ./system supports root protection both checked.
I'm in the same situation as fcortes626, I had to upgrade via sdcard method, and voodoo root keeper didn't maintain the root. I can't find any su backup in my filesystem.
I wonder if we can downgrade using the sd card update then root and go on from there........?
Sent from my SGH-T999 using xda app-developers app
I'm new here but have been messing around with android for awhile. I spent all afternoon searching for an answer but haven't been able to find anything. I had rooted my prime but not unlocked it while it was on ics, I used ota rootkeeper to keep root when I upgraded to jb but i think when asus sent out another update i forgot to save root. I still have su in /system/bin and superuser installed but it won't prompt me to give any programs root access. I typed in su in a terminal emulator and it said permission denied. so my question is, how do I get root back without unlocking?
Does this thread help ? http://forum.xda-developers.com/showthread.php?t=1911261&highlight=partial+root
I was able to get root back back doing something similar. Somehow the permissions got messed up for su. I went into adb and got root permission through CD/ system then ./usr/we-need-root/su-backup; su. Then I pushed new su, busybox, and superuser.apk files and fixed the permissions and changed the owner of su using chown and chmod.
peterk-1 said:
Does this thread help ? http://forum.xda-developers.com/showthread.php?t=1911261&highlight=partial+root
Click to expand...
Click to collapse
Here's my situation...I had 2 rezounds...One perfectly OK, rooted and Titanium backed up, but my kids poured milk into it...yaay. The 2nd rezound which was my wife's seems to have something physically wrong with it where I can't connect to it with fastboot (but adb works ok when the phone is fully booted), which means I can't dev unlock it, or apply most of the root methods out there...
So I decided to try some other things...
I downloaded the Cydia Impactor...
Drop Su didn't work
but,
start telnetd as root on port 22 did work!
so I then went in and remounted /system as RW
and copied su to /system/bin and the Superuser.apk to /bin/apps.
I then performed a echo ro.kernel.qemu=1 >/data/local.prop.
Now when I reboot, I get the root shell if I adb in to my phone...
But, on the screen only the status bar at the top comes up and if I try to swipe down, I get
"Unfortunately, System UI has stopped".
After this, I went into adb shell and noticed the su was gone from /system/bin...So this time I pushed it to /system/xbin, changed to root owner and chmod'd it to 06755..I removed the local.prop since I think that was causing the problem with the launch screen.
After rebooting, the Rezound had deleteed the su again, but the launcher comes up OK.
So I'm thinking, maybe I need to name the su something else...nope that won't work.
I guess for now I can be happy I can get temp root...
1. Run Cydia Impactor and select start telnetd as root on port 22.
2. copy su to /system/xbin and chmod 06755 /system/xbin/su
3. Run Titanium backup, and allow SU access.
works until phone reboot when su is removed by something.
Any ideas for next steps anyone?
Thanks,
Scott