Ok so some background, I am running the newest molten and enjoying it thouroughly but just noticed that when i open terminal emulator and type SU to get root access in the terminal it says permission denied and most other commands return same error, i downloaded a differant terminal emulator that checks for the su.bin and it shows no su binary is installed yet when i goto the directory system/bin/ in es file explorer su is indeed there?
Could someone please tell me why none of the terminal emulators are finding the superuser binary? I ve already tried opening superuser app and updating the su binary (it did update and i rebooted after) but it hasnt helped, I also read on other forums that there are multiple su binaries on some phones? could this be the problem and if so where would i find the right binaries?
It just seams odd that terminal emulator would be included in the build if it is completly unusable
su then hit enter
lol, thanks, im not the smartest with linux commands but i know to hit enter.
I tried typing su and hitting enter in 3 differant terminal emulators but keep getting permission denied in all of them
You should get a super user request once you hit enter. Maybe permission was already denied. Try clearing defaults for su.
Sent from my DROID X2 using xda premium
Did you recent apply the 2.3.5 update? When I went from rooted 234 to 235 I lost root privileges even though the superuser app was still there.
Could be your root isnt quite right. What setup do you have. Also try going into your superuser application and see if they are on the not allowed list.
Also should go from a "$" to a "#" sign after you hit enter if su took.
thanks for the ideas, that really narrowed it down, i cleared data for superuser and terminal, reinstalled terminal, still didnt work.....then i realised im a idiot, my keyboards autocap was on and su has to be "su" not "SU"
lol well thanks again for all the help
brilock42 said:
thanks for the ideas, that really narrowed it down, i cleared data for superuser and terminal, reinstalled terminal, still didnt work.....then i realised im a idiot, my keyboards autocap was on and su has to be "su" not "SU"
lol well thanks again for all the help
Click to expand...
Click to collapse
If it is solved then put (solved) in the OP subject line and list what fixed it for you. It can help future users
Pesky case sensitive terminal
Sent from my DROID X2 using xda premium
No SU in SSH
su did not work here as I did use a bad SSH-app.
I now use sshdroid
Related
I have an eris running Zen-EXP Rev 7. Up until a couple of weeks ago, everything was peachy keen, and SU was working fine. A few weeks ago I decided to try flashing a newer version of SU (the one found here on the xda forums), and made a Nand backup before doing so. After flashing the updated SU, it force closed on me any time I tried to open it, and programs were unable to gain root access. So I restored my Nand backup, but now I'm having a new issue.
Basically, SU (the restored old version) opens fine from the programs menu, and programs I have already granted SU access to (SetCPU, for instance) work just fine. However, any time a new program asks for SU access, SU hangs at a black screen, so I'm unable to give any new programs root access.
Is there an easy way to fix this, or am I going to have to totally wipe/reflash my phone? I tried updating SU in a variety of ways and reflashing the rom WITHOUT a wipe, but none of those attempts fixed the problem.
Thanks.
Did you wipe before restoring your nandroid? And you're positive you flashed the right SU? The one meant for froyo? They always release TWO SU's, one for froyo and one not.
I didn't read the entire first post but make sure you have usb debugging mode turned on... My SU was hanging last week until I rechecked that.
theEastonator said:
I have an eris running Zen-EXP Rev 7. Up until a couple of weeks ago, everything was peachy keen, and SU was working fine. A few weeks ago I decided to try flashing a newer version of SU (the one found here on the xda forums), and made a Nand backup before doing so. After flashing the updated SU, it force closed on me any time I tried to open it, and programs were unable to gain root access. So I restored my Nand backup, but now I'm having a new issue.
Basically, SU (the restored old version) opens fine from the programs menu, and programs I have already granted SU access to (SetCPU, for instance) work just fine. However, any time a new program asks for SU access, SU hangs at a black screen, so I'm unable to give any new programs root access.
Is there an easy way to fix this, or am I going to have to totally wipe/reflash my phone? I tried updating SU in a variety of ways and reflashing the rom WITHOUT a wipe, but none of those attempts fixed the problem.
Thanks.
Click to expand...
Click to collapse
Some versions and ROMs require you to do this before you use anything that needs SU:
Install Android SDK if you haven't already.
Plug in the phone to the computer with USB Debugging on.
Open up a command prompt and navigate to your tools folder.
C:\android-sdk-windows\tools> adb shell
#
# su
(type adb shell, press enter, then type su, and press enter).
Your phone should pop up with the REAL allow/deny screen, without it being all black. Just for the first time.
Hit allow always, and move on.
Then when you want to use Root Explorer or SetCPU or anything that needs root permission, you WON'T just get that hanging black screen. It'll work.
Some ROMs and versions of SuperUser (or maybe something in bin/xbin, I'm not sure?) require you to use the SDK to use ADB shell, to get SU permissions, before you let any other apps get it.
Strange, yes.
Hope that helps.
pkopalek said:
Open up a command prompt and navigate to your tools folder.
C:\android-sdk-windows\tools> adb shell
#
# su
(type adb shell, press enter, then type su, and press enter).
Click to expand...
Click to collapse
The command "adb shell" doesn't work at all for me. In PowerShell, it just hangs at "Running script/selection".
Can you help me?
Hey guys
One of the things im working on atm, having a bit of trouble trying to get a sysctl.conf I am working on to be loaded at startup
I've managed to generate the file, edit what i want, gotten it into /etc, but therein lies the problem
when i try to run systl -p, it keeps telling me the following:
sysctl: error setting key <insert sysctl key here>: Permission Denied
How can i overcome this? As soon as ive finished the work on this file, I'll be happy to share it with everyone
so no ideas?
Do you have superuser permissions (su, command prompt #) ?
When trying with this:
-p
Load in sysctl settings from the file specified or /etc/sysctl.conf if none given.
Perhaps this helps ?
-e
Use this option to ignore errors about unknown keys.
I try running su from command prompt
after using adb shell, all i get after running su is this
Brief 5sec delay, and permission denied. Thats what i dont get, I've Rooted the phone using the guide on the forums and everything went to the letter
*Shrugs* I dunno, tried the -p, thats what gives me the error i get.
Nutterpc said:
I try running su from command prompt
after using adb shell, all i get after running su is this
Brief 5sec delay, and permission denied. Thats what i dont get, I've Rooted the phone using the guide on the forums and everything went to the letter
*Shrugs* I dunno, tried the -p, thats what gives me the error i get.
Click to expand...
Click to collapse
Look at your phone to allow Superuser permission after entering su in the terminal or command
Sent from my X10i using XDA App
had a bit more of a fish round the net to see if anyone else ham similar issues
seems i was able to find the eventual root cause of it, was /system/bin/sh was set to secure mode, so i downloaded root explorer and changed the permissions
now the only thing is, how do i actually get the sysctl.conf im working on to be loaded at start, when i turn the phone on?
You might find something useful in this thread:
http://forum.xda-developers.com/showthread.php?t=523707
Hello,
When I run adb shell, it reports back with a "$,"even though I do have root. I'm running JoeyKrim Stock With Root ROM. Odexed...
I do have superuser installed with the latest binary, and latest official busybox. Terminal emulator even detects that I have root.
Basically everything works as it should, except adb. Anybody know what's going on?
Rydah805 said:
Hello,
When I run adb shell, it reports back with a "$,"even though I do have root. I'm running JoeyKrim Stock With Root ROM. Odexed...
I do have superuser installed with the latest binary, and latest official busybox. Terminal emulator even detects that I have root.
Basically everything works as it should, except adb. Anybody know what's going on?
Click to expand...
Click to collapse
When you type adb shell, does it immediately report back with a $, or does it pause for a few and then report back with a $? If it pauses for a few seconds, look down at your phone during that time. You may be being prompted with the super user request prompt, where you need to hit allow. I'm not sure why you need to do this sometimes, but I've had it happen before. If you don't look at the phone and hit 'allow', then it times out and doesn't give you root access. So type 'adb shell', check out your phone and see if your prompted, if so allow it, and you should be good. If that is not the case, then I'm unsure what could be causing it.
k2buckley said:
When you type adb shell, does it immediately report back with a $, or does it pause for a few and then report back with a $? If it pauses for a few seconds, look down at your phone during that time. You may be being prompted with the super user request prompt, where you need to hit allow. I'm not sure why you need to do this sometimes, but I've had it happen before. If you don't look at the phone and hit 'allow', then it times out and doesn't give you root access. So type 'adb shell', check out your phone and see if your prompted, if so allow it, and you should be good. If that is not the case, then I'm unsure what could be causing it.
Click to expand...
Click to collapse
Thanks, I'll test that out. I have a pin set on superuser. Maybe that's the issue.
Just checked, and it does it right away, and does not prompt... Sigh...
Rydah805 said:
Just checked, and it does it right away, and does not prompt... Sigh...
Click to expand...
Click to collapse
Very strange. I'm not sure. Has it happened on all roms, or just the one you're currently on?
Sent from my PG86100 using Tapatalk
Rydah805 said:
Just checked, and it does it right away, and does not prompt... Sigh...
Click to expand...
Click to collapse
The first time you type su from adb shell, Superuser will display a prompt on the screen to accept or deny the request. If you don't accept the request, in adb shell it will display, "Permission denied".
On the Superuser prompt, if you select deny, when typing su in adb shell the result will always be "Permission denied" until going into the Superuser app and changing "Unknown" to Allow. Not sure why the Superuser app labels adb shell as "Unknown".
Another option, inside the Superuser app, on the Settings tab, at the very bottom there is an option, update su binary. Sometimes using this update feature will resolve permission/installation issues with the su binary.
If you wanted to verify the installation of both Superuser and root as having been done properly, my free app Root Check from the market works well. Advanced Mode should provide all the details we'd need to troubleshoot further.
Hope that helps and appreciate your support!
joeykrim said:
The first time you type su from adb shell, Superuser will display a prompt on the screen to accept or deny the request. If you don't accept the request, in adb shell it will display, "Permission denied".
On the Superuser prompt, if you select deny, when typing su in adb shell the result will always be "Permission denied" until going into the Superuser app and changing "Unknown" to Allow. Not sure why the Superuser app labels adb shell as "Unknown".
Another option, inside the Superuser app, on the Settings tab, at the very bottom there is an option, update su binary. Sometimes using this update feature will resolve permission/installation issues with the su binary.
If you wanted to verify the installation of both Superuser and root as having been done properly, my free app Root Check from the market works well. Advanced Mode should provide all the details we'd need to troubleshoot further.
Hope that helps and appreciate your support!
Click to expand...
Click to collapse
Yep that does work on his rom the "type su" thing and thanks for your root check app Joey it's been super useful in trying to figure out stuff lately on the photon.... really appreciate all your contributions
joeykrim said:
The first time you type su from adb shell, Superuser will display a prompt on the screen to accept or deny the request. If you don't accept the request, in adb shell it will display, "Permission denied".
On the Superuser prompt, if you select deny, when typing su in adb shell the result will always be "Permission denied" until going into the Superuser app and changing "Unknown" to Allow. Not sure why the Superuser app labels adb shell as "Unknown".
Hope that helps and appreciate your support!
Click to expand...
Click to collapse
Got it! Thanks! Any idea why I had to do that with your rom though? On others, I didn't need to type Su and grant it. (Doesn't bother me though.)
Rydah805 said:
Got it! Thanks! Any idea why I had to do that with your rom though? On others, I didn't need to type Su and grant it. (Doesn't bother me though.)
Click to expand...
Click to collapse
Short answer: Since Superuser.apk is another developer's software, I didn't include it in my ROM as I didn't have his permission. I provide the superuser apk market link in my ROM OP for users. Instead of packaging Superuser apk, I used the su binary provided in AOSP as its source code is public and publically available for android usage.
Long answer: There is a free version of Superuser available thru the market and figured that would be the best way to load the Superuser apk. From personal experience as an android developer, when an app is provided with a ROM, it doesn't appear in the developer's market statistics and essentially is "off the radar". Which makes it more difficult to track which devices have loaded the software, which versions of android, etc and makes it more difficult to prioritize software upgrades to the application.
Hope I was able to explain and it helps!
joeykrim said:
Short answer: Since Superuser.apk is another developer's software, I didn't include it in my ROM as I didn't have his permission. I provide the superuser apk market link in my ROM OP for users. Instead of packaging Superuser apk, I used the su binary provided in AOSP as its source code is public and publically available for android usage.
Long answer: There is a free version of Superuser available thru the market and figured that would be the best way to load the Superuser apk. From personal experience as an android developer, when an app is provided with a ROM, it doesn't appear in the developer's market statistics and essentially is "off the radar". Which makes it more difficult to track which devices have loaded the software, which versions of android, etc and makes it more difficult to prioritize software upgrades to the application.
Hope I was able to explain and it helps!
Click to expand...
Click to collapse
Gotcha, I'm not complaining, just wondering why. I've always loved your roms over any others. Any way I can easily set it to use the superuser app binary over aosp binary?
ADB starting with root depends on the ro.secure property; if you type "getprop ro.secure" it should show either 0 meaning ADB keeps root or 1 meaning you have to use su for root. Just about all custom kernels/ROMs use unsecured boot.imgs but you can always change it yourself by modifying the default.prop file packed in the boot.img.
This is also what people are referring to when they say the kernel/boot.img/rom is secured or unsecured.
Rydah805 said:
Got it! Thanks! Any idea why I had to do that with your rom though? On others, I didn't need to type Su and grant it. (Doesn't bother me though.)
Click to expand...
Click to collapse
xHausx said:
ADB starting with root depends on the ro.secure property; if you type "getprop ro.secure" it should show either 0 meaning ADB keeps root or 1 meaning you have to use su for root. Just about all custom kernels/ROMs use unsecured boot.imgs but you can always change it yourself by modifying the default.prop file packed in the boot.img.
This is also what people are referring to when they say the kernel/boot.img/rom is secured or unsecured.
Click to expand...
Click to collapse
Rydah805 said:
Gotcha, I'm not complaining, just wondering why. I've always loved your roms over any others. Any way I can easily set it to use the superuser app binary over aosp binary?
Click to expand...
Click to collapse
Ah! Your question in the first quote above could be intrepreted two different ways. I provided one answer for one intrepretation and Haus provided the other answer for a different intrepretation!
I'll try and bring both together. There are two primary ways to access the shell interface on an android device.
1) Via adb shell. When typing adb shell and it opens the connection to the device, by android standard, it drops you to a shell with non root access reflected with the $ prompt. As Haus articulated above, this can be modified in the /default.prop file inside the ramdisk of the boot.img file. There are two options, have adb shell drop to root access or have adb shell drop to non root access. Many custom kernels modify this option so the user drops to root access.
In my kernel I'm using a non-modified stock kernel so it drops to non root access. I prefer to have to type su, once in the shell, to elevate to root access. Mainly because most functions I perform in adb shell I don't want root access for.
2) Via terminal emulator/connectbot. When accessing the shell directly on the device thru one of the common android applications, these generally open up a standard "sh" or non root shell. Then by typing "su" the user can elevate to root access (if the device has the su binary, etc.).
There are two main options for how to handle the "su" command inside a shell on the android device.
1) Superuser.apk - this application provides its own su binary, which hooks into the android application. Whenever su is called, the Superuser application is therefore called and allows the user to accept/deny root access requests.
2) su binary - from aosp or busybox. this is a version of the su binary more common to android developers in aosp, or the busybox version is more common to a generic linux version. the aosp version of su will grant any user/application root access. the busybox version will grant any user/application root access but does rely on an /etc/passwd and /etc/group file for permissions.
To answer your previous question, why you haven't had to type su on other custom ROMs, as Haus explained, they probably modified adb shell access in the /defult.prop file to automatically elevate adb shell to root priviledges.
To answer your last question regarding Superuser.apk and aosp su. Once you install the Superuser.apk file and it properly installs its own version of the su binary, it has now overwrite the previous aosp su binary. Superuser will now control all root access requests. Once you grant an application, adb shell, titantium backup, root explorer, or whatever application root access with Superuser, it will not prompt again and will handle every future request with the default action (grant/deny) provided.
Hope the extra details help!
Thanks, wasn't trying to be a pest. Just curious. The info in this thread is a nice thing to know.
I recently won this developer tablet and I can't seem to get on-device root access. It came with su binaries installed. (very old ones but I updated it) It also has an unsecured kernel because ADB always runs as root. However I installed superuser and it can't get root access and when other apps attempt root access something seems to be denying access before the superuser prompt is even able to come up. Just curious if anyone has any ideas??
JBO1018 said:
I recently won this developer tablet and I can't seem to get on-device root access. It came with su binaries installed. (very old ones but I updated it) It also has an unsecured kernel because ADB always runs as root. However I installed superuser and it can't get root access and when other apps attempt root access something seems to be denying access before the superuser prompt is even able to come up. Just curious if anyone has any ideas??
Click to expand...
Click to collapse
This may seem like a stupid suggestion but I suppose you could try uninstalling the superuser app and use Chainfire's Super SU app to see if that might make any difference.
Tried that too lol. I was even able to go into old su app and toggle permission for super su to allowed and it still said fail when it tried to update binary. Thanks for the suggestion though. It seems to me the problem is that the chown and chmod commands are not sticking on the su binary. They appear to work but the actual ownership and permissions of the file don't change. Even when I do adb remount first.
I figured it out. For some reason I had to put the su binary in /system/bin instead of xbin. Which is strange because all my other device it went in xbin. Also the reason the chmod and chown commands were not working properly is because I forgot to do adb remount. (duh!) In case anyone is wondering this thing is a beast. I just wish I could figure out a way to get my Gameloft games to work. I (mainly modern combat 3 and nova3)
JBO1018 said:
I figured it out. For some reason I had to put the su binary in /system/bin instead of xbin. Which is strange because all my other device it went in xbin. Also the reason the chmod and chown commands were not working properly is because I forgot to do adb remount. (duh!) In case anyone is wondering this thing is a beast. I just wish I could figure out a way to get my Gameloft games to work. I (mainly modern combat 3 and nova3)
Click to expand...
Click to collapse
One way to get your games to work would be try side loading the Modern Combat 3 and Nova 3 APK's onto the device and installing them manually that way. Another way if that doesn't work is you could try modifying your build.prop and changing your product id to match the galaxy nexus that way the play store will think your on a galaxy nexus and it should say that the games are compatible then.
JBO1018 said:
I figured it out. For some reason I had to put the su binary in /system/bin instead of xbin. Which is strange because all my other device it went in xbin. Also the reason the chmod and chown commands were not working properly is because I forgot to do adb remount. (duh!) In case anyone is wondering this thing is a beast. I just wish I could figure out a way to get my Gameloft games to work. I (mainly modern combat 3 and nova3)
Click to expand...
Click to collapse
I know this is an older post but I'm at the same point where I can't figure out how to allow superuser access. I'm using the 8064 for research and I need the root access but can't seem to figure out how to update the SU. Any tips?
mcforan said:
I know this is an older post but I'm at the same point where I can't figure out how to allow superuser access. I'm using the 8064 for research and I need the root access but can't seem to figure out how to update the SU. Any tips?
Click to expand...
Click to collapse
Do you have the Superuser.apk app installed along with the SU binary in the correct place /system/bin as mentioned by JBO1018? If you already had working root access before on the device and just need to update the SU binary you can open the Superuser app, then go under the info tab and tap on the SU binary version number this should then check for updates and then ask you if you want to install any found updates.
shimp208 said:
Do you have the Superuser.apk app installed along with the SU binary in the correct place /system/bin as mentioned by JBO1018? If you already had working root access before on the device and just need to update the SU binary you can open the Superuser app, then go under the info tab and tap on the SU binary version number this should then check for updates and then ask you if you want to install any found updates.
Click to expand...
Click to collapse
I have both the Superuser.apk and SU binary in the right place. Each time I open up an app that needs root access a toast message pops saying that the app has been denied Superuser permissions. I tried restarting both apps but its not working.
mcforan said:
I have both the Superuser.apk and SU binary in the right place. Each time I open up an app that needs root access a toast message pops saying that the app has been denied Superuser permissions. I tried restarting both apps but its not working.
Click to expand...
Click to collapse
Try going into the Superuser app and under settings and then security the default behavior is set to prompt not deny.
Sent from my SCH-I535 using xda premium
join have a tablet TIR 8960 is preloaded with windows rt, tablet says about the problems of the system,
hey guys i need some help plz!!!
i had rooted my asus prime.......and my bootloader was still locked, after i rooted my device i also had rootkeeper to protect it incase i update.....to make a long story short, i was so anxious when jelly bean was released i wasnt thinking so i proceeded without temp unroot first before i did the update......so after everything completed i went to restore my root access and it was gone..........was so pissed off, so now from every research i did it says that there is no current root options for the prime jelly bean, anybody knows how to get it back or a way to root again.....im willing to downgrade if i can to get back my root access. please help!!!
You can't downgrade without using the ASUS unlocker tool. Yeah, I know... shocked me too....
There isnt a working root method working as of yet if you are certain you have lost root access.
Some people report having partial root and even having some apps that still retained root. If none of that applies to you then your screwed with the rest of us.
hx4700 Killer said:
You can't downgrade without using the ASUS unlocker tool. Yeah, I know... shocked me too....
There isnt a working root method working as of yet if you are certain you have lost root access.
Some people report having partial root and even having some apps that still retained root. If none of that applies to you then your screwed with the rest of us.
Click to expand...
Click to collapse
yea thanks for replying tho, as far as the partial root goes.....im not sure if im that lucky and i checked system/bin there is no su file and also when i enter adb shell command then su i got the $ sign instead of the #.........but i still have superuser app !
weakenfalls said:
yea thanks for replying tho, as far as the partial root goes.....im not sure if im that lucky and i checked system/bin there is no su file and also when i enter adb shell command then su i got the $ sign instead of the #.........but i still have superuser app !
Click to expand...
Click to collapse
If you don't get # you don't have root.
I actually had an SU in xbin but it wasnt owned by root.
hx4700 Killer said:
If you don't get # you don't have root.
I actually had an SU in xbin but it wasnt owned by root.
Click to expand...
Click to collapse
I get # in ADB but not using Terminal Emulator. What does this mean?
Restorer said:
I get # in ADB but not using Terminal Emulator. What does this mean?
Click to expand...
Click to collapse
Hmmm I will have to try in ADB and see what happens.
If your prompt changes to # in ADB then that means you should have root access. With that you can restore full root properly to your device. You may be one of the lucky ones that just needs to uninstall and reinstall Superuser.
hx4700 Killer said:
If your prompt changes to # in ADB then that means you should have root access. With that you can restore full root properly to your device. You may be one of the lucky ones that just needs to uninstall and reinstall Superuser.
Click to expand...
Click to collapse
Well it did give me hope when I saw that but I can't get past stage 11 in this guide . I just cannot get ADB to mount /system as RW . Also entering su in Terminal Emulator gets "permission denied" and Superuser itself "fails" at updating binary.
Restorer said:
Well it did give me hope when I saw that but I can't get past stage 11 in this guide . I just cannot get ADB to mount /system as RW . Also entering su in Terminal Emulator gets "permission denied" and Superuser itself "fails" at updating binary.
Click to expand...
Click to collapse
What is the error when you issue the remount command? if I type remount I get: "remount: not found"
There is also an executeable that came with one of the 10000 root packages I have tried called fsrw. Pushing it to /data/local/tmp with ADB then running it via the adb shell out of that path should try to perform the remount.
If you are getting "operation denied" then you don't really have root =/
hx4700 Killer said:
What is the error when you issue the remount command? if I type remount I get: "remount: not found"
There is also an executeable that came with one of the 10000 root packages I have tried called fsrw. Pushing it to /data/local/tmp with ADB then running it via the adb shell out of that path should try to perform the remount.
If you are getting "operation denied" then you don't really have root =/
Click to expand...
Click to collapse
I get:
"mount: Operation not permitted" .
There you go, you are not really root
Curious that you get the # logo though. I had an SU in xbin but got no # prompt because its ownership was screwed up.
hx4700 Killer said:
There you go, you are not really root
Curious that you get the # logo though. I had an SU in xbin but got no # prompt because its ownership was screwed up.
Click to expand...
Click to collapse
Sorry, just tried again and now stage 11 is working! But then when I try 12 I get:
"r.apk of=/system/app/Superuser.apk
/data/local/tmp/Superuser.apk:cannot open for read: No such file or directory
1:[email protected]:/#"
re root jellybean
hi, to all those other rookies, i did a bit of reading and finally decided to update to JB from stock ICS .28 which was unlocked and rooted.
As i expected i lost root and have just manged to get it back, i first installed twrp for JB using fastboot method.
http://forum.xda-developers.com/showthread.php?t=1615990
then after trying [ROOT][TOOL]Debugfs automated root [09/18/2012] and SparkyRoot Apk having read this can possible restore root although not in my case, for me i uninstalled super user and re-flashed via twrp,
(version Superuser-3.2-arm-signed.zip from thread http://forum.xda-developers.com/showthread.php?t=1911024)
Then when i rebooted i noticed luckypatcher app requested SU and root access was now working
hx4700 Killer said:
There you go, you are not really root
Curious that you get the # logo though. I had an SU in xbin but got no # prompt because its ownership was screwed up.
Click to expand...
Click to collapse
Whooo! Just got my root back. I hadn't realised there are a couple of typos in the guide there and I was copying and pasting the long lines!
Big thanks to hx4700 Killer for making me wonder I must be doing something wrong :laugh:.
tomtomxp said:
hi, to all those other rookies, i did a bit of reading and finally decided to update to JB from stock ICS .28 which was unlocked and rooted.
As i expected i lost root and have just manged to get it back, i first installed twrp for JB using fastboot method.
http://forum.xda-developers.com/showthread.php?t=1615990
then after trying [ROOT][TOOL]Debugfs automated root [09/18/2012] and SparkyRoot Apk having read this can possible restore root although not in my case, for me i uninstalled super user and re-flashed via twrp,
(version Superuser-3.2-arm-signed.zip from thread http://forum.xda-developers.com/showthread.php?t=1911024)
Then when i rebooted i noticed luckypatcher app requested SU and root access was now working
Click to expand...
Click to collapse
Well.. I believe that everyone who'd not consider unlocking their tablets before the JB update would not unlock after losing root just because of the warranty, probably not because they don't know how but because about half of the forumers don't think it's worth the risk considering the hardware instabilities like the green camera module, light bleed etc.
And since you've already flashed a custom recovery you've unlocked more than just root, why not try a custom ROM based on stock JB?