Hey guys! I accidentally "forgotten" access to the ADB Shell on my Super SU. I am really scared now. How do I manually re-enable it? I don't want to flash my phone and stuff if possible.
P.S. If this is the wrong topic/thread please feel free to direct me to the proper area.
zeron824 said:
Hey guys! I accidentally "forgotten" access to the ADB Shell on my Super SU. I am really scared now. How do I manually re-enable it? I don't want to flash my phone and stuff if possible.
P.S. If this is the wrong topic/thread please feel free to direct me to the proper area.
Click to expand...
Click to collapse
Regranting su access is an extremely quick and simple process. All you have to do to be able to use root from adb shell is to start and and shell on the device again, call su and grant root from the SuperSU access prompt that will appear on the device, regranting access to apps is simple too, simply open the app and when it calls for su, SuperSU will bring up the access prompt for any app/uid that it hasn't got any stored settings for already
mmonaghan34 said:
Regranting su access is an extremely quick and simple process. A you have to do to be able to use root from adb shell is to start and and shell on the device again, call su and grant root from the SuperSU access prompt that will appear on the device, regranting access to apps is simple too, simply open the app and when it calls for sure, SuperSU will bring up the access prompt for any app/uid that it hasn't got any stored settings for already
Click to expand...
Click to collapse
Thank you very much!
Related
I have completed my Tattoo M7 root however applications say it is not rooted.
basically if i do ADB SHELL and then SU i get the root console but can not write to /system folder via adb push since i get permisison denied which means i always have to adb shell and su.
I believe this is somehow creating problems also to applications (i am testing Titanium Backup) which require root permissions and say i am not.
Anyone can help understanding why i can su only in console or terminal emultor but cannot use apps requiring root permissions.
Dude, you have to remount EVERY TIME /system and /data if you reboot, otherwise it says permission denied because system is read only...
Get RootExplorer, there is a little button which lets you remount partitions with one tap...
pardol said:
I have completed my Tattoo M7 root however applications say it is not rooted.
basically if i do ADB SHELL and then SU i get the root console but can not write to /system folder via adb push since i get permisison denied which means i always have to adb shell and su.
I believe this is somehow creating problems also to applications (i am testing Titanium Backup) which require root permissions and say i am not.
Anyone can help understanding why i can su only in console or terminal emultor but cannot use apps requiring root permissions.
Click to expand...
Click to collapse
hi
as ur question in the related thread
see link : http://forum.xda-developers.com/showthread.php?t=637927
CLOSED
Ive had the hero for a while now and now feel its time to root it since there doesnt look like there will be anymore major updates.
I had first tried to root it through the unrevoked method and couldnt get passed code #8: su
It just kept saying that su wasnt a valid code or something like that. so after a couple other tries i scrapped it. eventually found the 1-click way and did that on my phone. But nothing seems to have changed. The frst thing i wanted to do was uninstall the useless sprint apps such as sprint tv etc... but was unsuccessful in finding a way.
If you guy could give me a little insight on what i need to do or point me in the right direction i would appreciate it.
there is just so much info on this site that it makes it a littl overwhelming for somebody just getting into the game.
best way to test if you have root is open terminal emulator and type su if you get a # in the prompt you have root.
Or from adb try
adb remount
adb shell and if you have a # instead of a $ in the prompt you have root.
If that works then to remove the crappy sprint apps open a cmd and type
adb remount
adb shell
cd system/apps
ls
then look through and find the ones you dont want and type this
rm my_bloat_app.apk (replace my_bloat_app with the app you don't want)
and hit y to comfirm and its gone.
madeSICC said:
...The frst thing i wanted to do was uninstall the useless sprint apps such as sprint tv etc... but was unsuccessful in finding a way.
Click to expand...
Click to collapse
Titanium Backup can do it. Download it and learn how to use it. It will become your friend.
If it can't do it, you still aren't rooted!
Alright, so I've used the SuperOneClick application to root my phone, which tells me was done successfully, however, I don't seem to be able to access files in the system folder through adb.
Is there some way I can positively confirm whether my phone is or isn't actually rooted? Like I said I was using adb to push a file into the system folder, and was given a permission denied message. At this time the only thing I'm attempting to do to the phone is this:
/showthread.php?t=820749&page=3
It seems pretty basic and it's my first android phone, so I'm starting off small here..
Using the leaked 2.2 FW, other than the being rooted (attempted), the phone is stock 2.2..
cryo.burned said:
Alright, so I've used the SuperOneClick application to root my phone, which tells me was done successfully, however, I don't seem to be able to access files in the system folder through adb.
Is there some way I can positively confirm whether my phone is or isn't actually rooted? Like I said I was using adb to push a file into the system folder, and was given a permission denied message. At this time the only thing I'm attempting to do to the phone is this:
/showthread.php?t=820749&page=3
It seems pretty basic and it's my first android phone, so I'm starting off small here..
Using the leaked 2.2 FW, other than the being rooted (attempted), the phone is stock 2.2..
Click to expand...
Click to collapse
Do you have the "superuser" app on your phone?
cryo.burned said:
Alright, so I've used the SuperOneClick application to root my phone, which tells me was done successfully, however, I don't seem to be able to access files in the system folder through adb.
Is there some way I can positively confirm whether my phone is or isn't actually rooted? Like I said I was using adb to push a file into the system folder, and was given a permission denied message. At this time the only thing I'm attempting to do to the phone is this:
/showthread.php?t=820749&page=3
It seems pretty basic and it's my first android phone, so I'm starting off small here..
Using the leaked 2.2 FW, other than the being rooted (attempted), the phone is stock 2.2..
Click to expand...
Click to collapse
If you type:
adb shell
su (after hitting enter, you should get a popup on your phone asking for superuser permission, click allow)
If you see this:
C:\Users\*yournamehere*>adb shell
$ su
su
#
Then you have root permissions.
TheRomero09 said:
Do you have the "superuser" app on your phone?
Click to expand...
Click to collapse
Yes, I have it on my phone
miztaken1312 said:
If you type:
adb shell
su (after hitting enter, you should get a popup on your phone asking for superuser permission, click allow)
If you see this:
C:\Users\*yournamehere*>adb shell
$ su
su
#
Then you have root permissions.
Click to expand...
Click to collapse
I have the app on my phone, but when I try this, I do not get a prompt for super user permissions, and the CL shell returns permission denied
EDIT: I was going to look at the superuser app to see what was in it to give you more info, but it the "app" that I assume is actually my computer had denied permissions. After changing it back to allow, the shell returns
Code:
su
#
I hope I'm not just being an idiot here, but I am having a lot of trouble with adb shell right now.
When starting the shell, instead of starting in $ it defaults to #.
However, whenever I attempt to use 'su', I receive an access denied error. I am not receiving any prompt on the device as I normally would.
At first I thought this was just related to CM7, but even flashed back to rooted 1.0.1 I am getting this issue.
Can anyone offer some insight?
Thanks
Edit: Damn, forgot to add [Q] to the title. Sorry!
I have install the Superuser-3.1.3-arm-signed on my phone,but how do i flashing the superSu
I did this
You should have root access but lets just be sure anyways. Go to C:/android and Shift, right click to Open Command Window here.
Type in adb.exe shell and press enter
You should get $ meaning adb has connected to your phone.
Next, type in su. If you obtain #, this means you have root access.
And this worked on my Phone
I have not put in the new mod yet,i will do this now
Factasy said:
I have install the Superuser-3.1.3-arm-signed on my phone,but how do i flashing the superSu
I did this
You should have root access but lets just be sure anyways. Go to C:/android and Shift, right click to Open Command Window here.
Type in adb.exe shell and press enter
You should get $ meaning adb has connected to your phone.
Next, type in su. If you obtain #, this means you have root access.
And this worked on my Phone
I have not put in the new mod yet,i will do this now
Click to expand...
Click to collapse
To flash super user. -
Download the SuperUser and copy to your SD.
Then flash it thru recovery.
Now. if you have already installed Super User. Check if you have the root access to make sure you have the root access for your phone.
Download "Root Checker" from play store.
mafie said:
To flash super user. -
Download the SuperUser and copy to your SD.
Then flash it thru recovery.
Now. if you have already installed Super User. Check if you have the root access to make sure you have the root access for your phone.
Download "Root Checker" from play store.
Click to expand...
Click to collapse
I have install the new mode now and its works great,thanks for your help,you have been so kind.