Related
Hi there,
i'm actually trying to do the wimax backup found here:
http://forum.xda-developers.com/showthread.php?t=887900
I went through all of this trouble trying to install busybox until I found out that Titanium backup already installed 1.16 on my phone. However I can't seem to find where it was installed to and the,
busybox sed -n '/BEGIN CERTIFICATE/,$p' /dev/mtd/mtd0 > /sdcard/rsa_OEM.key
command isn't working. Any thoughts? Sorry if this is the wrong spot to post. I'm still getting the hang of this forum.
I have the same problem. I think I'm getting this error in the terminal emulator because I don't have the system Busybox installed, just Titanium's app busybox, which is apparently different?. When I try to run Busybox installer, it errors saying I'm possibly not nand unlocked... I used UR3 and UR forever, and can confirm that I am S-Off. Doesn't S-Off = nand-unlock?
I haven't played too much with busybox to know much of its capabilities, but if you want to know the directory it is located in, run this from Terminal Emulator, or adb.
find -iname "*busybox*"
that will get you any and all file listings with busybox in it.
says denied, so I typed su, and get the #
then I type the find command, and tells me that 'find' is not found.
topdawgn8 said:
I haven't played too much with busybox to know much of its capabilities, but if you want to know the directory it is located in, run this from Terminal Emulator, or adb.
find -iname "*busybox*"
that will get you any and all file listings with busybox in it.
Click to expand...
Click to collapse
greyopaque said:
says denied, so I typed su, and get the #
then I type the find command, and tells me that 'find' is not found.
Click to expand...
Click to collapse
you should be able to run find without a hitch. I have had issues running a find while executing a remove, but find had always worked...
try remounting the system:
Code:
su
remount rw
find -iname "*busybox*"
Edit: I just ran find with only SU. What rom and kernel are you running? The only two things I can think of are:
1: The dev removed it from the rom
2: User error-- ensure the commands are lower case, there is a space where appropriate (denoted by ">")
Code:
find>-iname>"*busybox*"
The busy box that tb installs doesn't have all the commands. I had to install from the market to get all the commands.
Sent from my PC36100 using XDA App
its in system/bin most of the time but can be in different spots
Usually you can find busybox in /system/xbin
OMG... I feel stupid... I had install location set for SDCard. That's why busybox installer was failing. I changed it back to auto, and installed busybox, and now everything is working!
Don't waste your time with the rsa keys backup. You'll never be able to restore them.
Use the recovery (amon's 2.2.x) to make a backup of the entire wimax partition. Should the need arise, recovery will be easy. To date, i've yet to see instructions how to restore just the keys.
That's exactly what I did. Thanx!
gpz1100 said:
Don't waste your time with the rsa keys backup. You'll never be able to restore them.
Use the recovery (amon's 2.2.x) to make a backup of the entire wimax partition. Should the need arise, recovery will be easy. To date, i've yet to see instructions how to restore just the keys.
Click to expand...
Click to collapse
Hello there,
I just flashed a new ROM (Gingerbread 2.3.7) last night. After signing in the Google account everything is great; the old apps got redownloaded and all. I noticed that there is no apps listed in the superuser. I tried 'su' command in the emulator terminal & I got permission denied.
Luckily all the apps are working in perfect harmony. However, how do I get the superuser permission back? It seems like my device is not rooted. Do I need to root my phone again? Fingers crossed I don't.
Initially, I tried to flash the Ice Cream Sandwich. I tried multiple times but to no avail. I even tried to change the HBOOT (from CM7 > downgrader > Stock HBOOT) but the process failed. I afraid that this might be the cause my root access got lost. Anyone can verify this?
Thanks!
Su app will be built into the ROM so you should still rooted. Sounds like Su settings are just defaulting to deny. Open Su, menu > settings and check its set at prompt (safer than allow). After flashing new Rom you'll need to launch apps that require root access to allow them permission again. You might need to update the Su app or binaries if permissions don't stick.
Sent from my HTC Desire using Tapatalk 2
beachcomber said:
Su app will be built into the ROM so you should still rooted. Sounds like Su settings are just defaulting to deny. Open Su, menu > settings and check its set at prompt (safer than allow). After flashing new Rom you'll need to launch apps that require root access to allow them permission again. You might need to update the Su app or binaries if permissions don't stick.
Sent from my HTC Desire using Tapatalk 2
Click to expand...
Click to collapse
beachcomber,
1. my Superuser is set at prompt.
2. I am not sure which app that require root access. Could you give me some examples so that I can run them?
3. I tried to update the su binaries, but I got this:
" checking current install path...FAIL!"
" failed to find currently installed su binary. Update cannot continue."
Therefore, what do you suggest?
Thanks.
xuminarc said:
beachcomber,
1. my Superuser is set at prompt.
2. I am not sure which app that require root access. Could you give me some examples so that I can run them?
3. I tried to update the su binaries, but I got this:
" checking current install path...FAIL!"
" failed to find currently installed su binary. Update cannot continue."
Therefore, what do you suggest?
Thanks.
Click to expand...
Click to collapse
Take a backup. Download this. Flash it through recovery. Reboot and check if it works.
Alaa said:
Take a backup. Download this. Flash it through recovery. Reboot and check if it works.
Click to expand...
Click to collapse
Thank you! It works!
I rooted my kindle fire using kindle fire utility 0.9.6 (after the rooting superuser wasn't installed on my kindle), downloaded twrp, flashed hashcode jelly bean ROM from this link
http://forum.xda-developers.com/showthread.php?t=1766829
and then flashed Superuser-3.1.3-x86-signed.zip which I downloaded from this link
http://androidsu.com/superuser/
but superuser won't work, when I check the root explorer in ES file explorer it tells me that this feature can't work on ur phone
Please I'm really dying out here
Someone Help Pleeeeeeeeeeeeeeeeeease !!!!!
You need the su binary installed as well. But with that being said, why don't you just install the Superuser.apk?
[Edit:] It's late and I'm not paying attention for some reason. Custom ROMs come pre-rooted and you have Jelly Bean installed. Perhaps there's a problem with ES File Explorer?
soupmagnet said:
You need the su binary installed as well. But with that being said, why don't you just install the Superuser.apk?
Click to expand...
Click to collapse
Thank you for replying so fast
how can I install su binary? and about the superuser.apk isn't that what i flashed into my device i have a superuser icon on my desktop but it just won't add any apps to its list.
Thanks again
At the Superuser website, there are three zip files. One is Superuser, one is the su binary, and the other should be both. Not that it matters at this point.
soupmagnet said:
At the Superuser website, there are three zip files. One is Superuser, one is the su binary, and the other should be both. Not that it matters at this point.
Click to expand...
Click to collapse
what do you mean by not that it matters at this point?
can't I just download the zip and flash it?
soupmagnet said:
You need the su binary installed as well. But with that being said, why don't you just install the Superuser.apk?
[Edit:] It's late and I'm not paying attention for some reason. Custom ROMs come pre-rooted and you have Jelly Bean installed. Perhaps there's a problem with ES File Explorer?
Click to expand...
Click to collapse
Maybe you missed this
soupmagnet said:
Maybe you missed this
Click to expand...
Click to collapse
I tried another app called copy paste it and when I try to use it this message appears:
"Your Phone does not appear to be rooted or has not been given root privileges. to use this application please provide root privileges to this applications"
what should I do?
[Edit] ok now i know my device is certainly not rooted i tried orbot, market enabler and market unlocker they all dispatch the same message your device isn't rooted.
can anyone tell me how to root it?
Scarfacew said:
I tried another app called copy paste it and when I try to use it this message appears:
"Your Phone does not appear to be rooted or has not been given root privileges. to use this application please provide root privileges to this applications"
what should I do?
[Edit] ok now i know my device is certainly not rooted i tried orbot, market enabler and market unlocker they all dispatch the same message your device isn't rooted.
can anyone tell me how to root it?
Click to expand...
Click to collapse
I too used the KFU to supposedly root my KF, but when I tried to install Titanium Backup, it gave me the same error message saying that my phone did not have root privileges... I wonder if there is something not installing correctly when using KFU...
"Root" consists of the su binary, which the system uses to give the user root permissions, and Superuser.apk, which keeps a database of what programs you allow to have those permissions. With "su" only, you will still have root permission, but only at the level of command line interface and your apps will not be allowed root permissions. Superuser.apk by itself is worthless. Custom ROMS come pre-rooted so the need to re-root is usually unnecessary unless something happens to one of the above mentioned programs. The only way to be sure if/which one is missing is in recovery via the command line because custom recovery will provide temporary root access.
Code:
adb shell ls /system/xbin
...look for su
Code:
adb shell ls /system/app
...look for Superuser.apk
Superuser can be installed from within the ROM using the .apk (at least in earlier versions it was possible), or in recovery using the command line or by flashing the signed .zip from the superuser website . The su binary can only be installed while in recovery.
Of course it all can be fixed by re-flashing your custom ROM.
It may also be necessary to rename the check-rooted executable, but only if you're running the stock Amazon software.
I think that pretty much covers it.
soupmagnet said:
"Root" consists of the su binary, which the system uses to give the user root permissions, and Superuser.apk, which keeps a database of what programs you allow to have those permissions. With "su" only, you will still have root permission, but only at the level of command line interface and your apps will not be allowed root permissions. Superuser.apk by itself is worthless. Custom ROMS come pre-rooted so the need to re-root is usually unnecessary unless something happens to one of the above mentioned programs. The only way to be sure if/which one is missing is in recovery via the command line because custom recovery will provide temporary root access.
Code:
adb shell ls /system/xbin
...look for su
Code:
adb shell ls /system/app
...look for Superuser.apk
Superuser can be installed from within the ROM using the .apk (at least in earlier versions it was possible), or in recovery using the command line or by flashing the signed .zip from the superuser website . The su binary can only be installed while in recovery.
Of course it all can be fixed by re-flashing your custom ROM.
It may also be necessary to rename the check-rooted executable, but only if you're running the stock Amazon software.
I think that pretty much covers it.
Click to expand...
Click to collapse
Ok now things are getting worse I tried to turn the wifi on and it didn't work, I tried to reboot and power off the tablet but it just won't work
{Edit} I want to know that by re-flashing the ROM is there a guarantee that those problems won't happen again.
One more thing is that I deleted the ROM from my kindle I can't transfer it from my laptop because the kindle hasn't been recognized after the jelly bean and I can't downloaded because wifi isn't working so what should I do
Thanks in advance
Scarfacew said:
Ok now things are getting worse I tried to turn the wifi on and it didn't work, I tried to reboot and power off the tablet but it just won't work
I want to know that by re-flashing the ROM is there a guarantee that those problems won't happen again.
Thanks in advance
Click to expand...
Click to collapse
There are never any guarantees when it comes to computers and system software, but the LIKELINESS is very high that the problem will be fixed.
soupmagnet said:
There are never any guarantees when it comes to computers and system software, but the LIKELINESS is very high that the problem will be fixed.
Click to expand...
Click to collapse
One more thing is that I deleted the ROM from my kindle I can't transfer it from my laptop because the kindle hasn't been recognized since I flashed the jelly bean and I can't downloaded because wifi isn't working so what should I do
Thanks in advance
Boot into recovery and "mount" your sdcard to USB. The computer should still recognize it.
soupmagnet said:
Boot into recovery and "mount" your sdcard to USB. The computer should still recognize it.
Click to expand...
Click to collapse
I re-flashed the Rom, wifi is working so I dl ES file explorer and checked Root explorer, but when superuser request popped, I clicked allow but it didn't work it gave me the same message, the new thing is that superuser app added es file explorer to its list but I still can't copy apps in the app/system file.
I know I bored you to death and I'm really thankful for ur help but I really need the root.
Scarfacew said:
I re-flashed the Rom, wifi is working so I dl ES file explorer and checked Root explorer, but when superuser request popped, I clicked allow but it didn't work it gave me the same message, the new thing is that superuser app added es file explorer to its list but I still can't copy apps in the app/system file.
I know I bored you to death and I'm really thankful for ur help but I really need the root.
Click to expand...
Click to collapse
Ok, well try a different ROM. If the problem persists then we can try to think of something.
I flashed the Alien droid ROM it's working fine till now but I need to know how to install an arabic keyboard please
Thanks
Ok, I have a dumb question, but from where do you run the DOS commands from? (ie. what directory?)..
c:\KFU?
Right-click on your KFU folder and select properties to find the folder's path. It may be different depending on wherever you've installed it.
soupmagnet said:
Right-click on your KFU folder and select properties to find the folder's path. It may be different depending on wherever you've installed it.
Click to expand...
Click to collapse
Thanks. but not sure i understand.
Here is what I'm attempting to do.. using the root method described here: http://forum.xda-developers.com/showthread.php?t=1638452 under "Getting to fastboot mode" there are a series of command line examples that seem to start with adb.... (ex. adb shell chmod 755 /data/local/tmp/fbmode).
Under Rooting the stock software, the first step command line is "adb shell mount system"
my question is from where do I start (directory) so that when I enter these commands they work?
Or are you saying that I need to fun all these from the KFU directory? (or KFU/tools) or some other directory..
I appreciate the help and feedback..
:h my::
Wherever adb is...Right-click on that folder to find it's path so you can "cd" or change directories to it. Alternatively, you can Shift + Right-click on that folder and select something like "Open command window here".
Hi,
Last night I installed the latest CDMA version of GBTweaked for my locked R800x. I am running into the standard no wifi issue, however, when I tried to install the wifi modules, I found myself unable to access CWM.... I tried to reinstall CWM with no luck. Flashtool isn't helping much with restoring to a previod nandroid backup either. Help would be greatly appreciated.
Maybe the button assigned to enter cwm has changed?
Last time i use kernel that assign back button for cwm, but since i have cwm on my system that use volume button to enter recovery mode, so the back button function is nullified automatically
Sent from my R800x using xda app-developers app
otonieru said:
Maybe the button assigned to enter cwm has changed?
Last time i use kernel that assign back button for cwm, but since i have cwm on my system that use volume button to enter recovery mode, so the back button function is nullified automatically
Sent from my R800x using xda app-developers app
Click to expand...
Click to collapse
Well, I don't even get the blue light on boot to indicate it is waiting for me to push the button...
Additionally, I keep finding a lot of chmod/rm/ls permission denies whenever I tried to reinstall superuser, or use the PC installer for CWM and Titanium keeps FC whenever I try to start it.
I just ran rootchecker and got this:
Congratulations! You have root access!
Superuser Application Status:
Superuser application - version 3.0.7 - is installed!
System File Properties for Root Access:
Alternative Location
Check Command: ls -l /sbin/su:
Result: exec: ls: permission denied
Analysis: Setuid attribute NOT present and root user ownership is NOT present. Root access is NOT correctly configured for this file!
Standard Location
Check Command: ls -l /system/bin/su:
Result: exec: ls: permission denied
Analysis: Setuid attribute NOT present and root user ownership is NOT present. Root access is NOT correctly configured for this file!
Standard Location
Check Command: ls -l /system/xbin/su:
Result: exec: ls: permission denied
Analysis: Setuid attribute NOT present and root user ownership is NOT present. Root access is NOT correctly configured for this file!
Alternative Location
Check Command: ls -l /system/xbin/sudo:
Result: exec: ls: permission denied
Analysis: Setuid attribute NOT present and root user ownership is NOT present. Root access is NOT correctly configured for this file!
Root User ID and Group ID Status:
Root user id:
uid=0(root)
Root group id:
gid=0(root)
System Environment PATH: /sbin /vendor/bin /system/sbin /system/bin /system/xbin
ADB Shell Default User:
ADB shell setting for standard access, stored in default.prop, is configured as: shell (non root) user - ro.secure=1
Results provided on your R800x device by Root Checker Pro version 1.2.1 from joeykrim in the Android Market -
Any thoughts?
edwinen said:
Hi,
Last night I installed the latest CDMA version of GBTweaked for my locked R800x. I am running into the standard no wifi issue, however, when I tried to install the wifi modules, I found myself unable to access CWM.... I tried to reinstall CWM with no luck. Flashtool isn't helping much with restoring to a previod nandroid backup either. Help would be greatly appreciated.
Click to expand...
Click to collapse
I am assuming you have root access. Download an app called x-parts from the googleplay store that will install the CWM for you. I don't remember how to get into recovery by using the app but I think it is pressing the volume d-rocker down or up. Play with your xperia play buttons a little and you will be able to get into recovery.
chery2k said:
I am assuming you have root access. Download an app called x-parts from the googleplay store that will install the CWM for you. I don't remember how to get into recovery by using the app but I think it is pressing the volume d-rocker down or up. Play with your xperia play buttons a little and you will be able to get into recovery.
Click to expand...
Click to collapse
I do have root, or at least it still seems like I do, with the exception of the errors root checker is giving me. X-parts never worked for me before I changed roms, and it isn't working now. The only way I could get into recovery was by using CWM v. 5.
Whenever I try to install now however, it says it installed, and to reboot, however, when it is rebooting, I never get the blue light like I used to, and when it loads all the way into the system and go back into CWM/x-parts it tells me recovery isn't installed, and that my phone is supported.
edwinen said:
I do have root, or at least it still seems like I do, with the exception of the errors root checker is giving me. X-parts never worked for me before I changed roms, and it isn't working now. The only way I could get into recovery was by using CWM v. 5.
Whenever I try to install now however, it says it installed, and to reboot, however, when it is rebooting, I never get the blue light like I used to, and when it loads all the way into the system and go back into CWM/x-parts it tells me recovery isn't installed, and that my phone is supported.
Click to expand...
Click to collapse
Do not use an auto-installing app for CWM.
If you are on windows, use RecoveryX.
Sent from my Kindle Fire
Sounds like you need to download the su binaries. In the superuser app, go to your settings menu and look for the option to update your su binaries.
lightningdude said:
Sounds like you need to download the su binaries. In the superuser app, go to your settings menu and look for the option to update your su binaries.
Click to expand...
Click to collapse
Hmm.. any way of doing this without an internet connection? Right now I have no wireless functionality, additionally my reception is very minimal here (no 3G atm)
edwinen said:
Hmm.. any way of doing this without an internet connection? Right now I have no wireless functionality, additionally my reception is very minimal here (no 3G atm)
Click to expand...
Click to collapse
yeah, it involves pushing to the su folder via adb, but I don't remember the steps involved. Searching for a manual way to root any phone should turn that bit up.
lightningdude said:
yeah, it involves pushing to the su folder via adb, but I don't remember the steps involved. Searching for a manual way to root any phone should turn that bit up.
Click to expand...
Click to collapse
Yeah... well, whenever I try to do anything with adb shell, i get permission denied, I can't even ls!!!
how about re-flashing kernel? doom kernel should bring along CWM as well...
otonieru said:
how about re-flashing kernel? doom kernel should bring along CWM as well...
Click to expand...
Click to collapse
Hmm.. well looks like my only option is to wait for my bootloader unlock... but I have not heard back from them in about 5 days.
They r quite slow in replying email, contact them via gTalk directly.. or just pay 1st (like what i did), when they receive the money they will feel more responsible to finish the service, LoL
Sent from my R800x using xda app-developers app
---------- Post added at 11:28 PM ---------- Previous post was at 11:27 PM ----------
For now i will suggest to falshback to original stock via flashtool..
Sent from my R800x using xda app-developers app
Well.. ended up unlocking the phone, and been messing with various options. Nothing seems to be working quite well, although it is because I am trying to use CM10 and CM9 which dont seem TOO stable.. but eh... Thanks for all the help everyone!
When i first bought the t989, i rooted the phone manually by flashing cwm and the su.zip file. Everything seem to have worked then. A month or so back I updated the phone to ICS through the Kies Air application. I tried browsing through my root files and found myself unable to do so. I decided to check my superuser application and noticed another su apk. It wasnt the android face but a superman android icon (sua). I updated the binary on the sua and my phone started resetting on its own. I have flashed stock roms of ics and the problem consisted. Eventually fed up of the 4.0.4 version i flashed back to GB which seems better in phone performance.
Back into stock/unrooted T989, i flashed root again. However i used root checker pro and it verifies root access however I find myself unable to browse root files. Is there another possible way to check through? maybe via terminal emulator?
/--edit 10:28 AM----\
So i did some more searching and found the su command in terminal emulator and the "$" symbol changed to "#"
Im guessing I have root but browsing in the rooted files seems disabled in some apps
brion1020 said:
When i first bought the t989, i rooted the phone manually by flashing cwm and the su.zip file. Everything seem to have worked then. A month or so back I updated the phone to ICS through the Kies Air application. I tried browsing through my root files and found myself unable to do so. I decided to check my superuser application and noticed another su apk. It wasnt the android face but a superman android icon (sua). I updated the binary on the sua and my phone started resetting on its own. I have flashed stock roms of ics and the problem consisted. Eventually fed up of the 4.0.4 version i flashed back to GB which seems better in phone performance.
Back into stock/unrooted T989, i flashed root again. However i used root checker pro and it verifies root access however I find myself unable to browse root files. Is there another possible way to check through? maybe via terminal emulator?
/--edit 10:28 AM----\
So i did some more searching and found the su command in terminal emulator and the "$" symbol changed to "#"
Im guessing I have root but browsing in the rooted files seems disabled in some apps
Click to expand...
Click to collapse
I'm having the same issues with 4.0.4. It's getting me pissed and contemplating doing 4.0.3 where I had access to system files via root explorer. I've been going through different ROMs on 4.0.4 to see if that would alleviate the problem. So far, still issues saying something to the affect that I don't have superuser access even though I can run any rooted application.
Here is the results of using root checker pro
Code:
Congratulations! You have root access!
Super User Applications Status: Superuser application - version 3.0.5 - is installed! SuperSU application - is NOT installed.
System File Properties for Root Access: Standard Location Check Command: ls -l /system/xbin/su: Result: lrwxrwxrwx root root 2012-09-29 00:35 su -> /system/bin/su Analysis: File: su is a symbolic link pointing to another file: /system/bin/su
Standard Location Check Command: ls -l /system/bin/su: Result: -rwsr-sr-x root root 22228 2008-08-01 08:00 su Analysis: Setuid attribute present and root user ownership present. Root access is correctly configured for this file! Executing this file can grant root access!
Alternative Location Check Command: ls -l /sbin/su: Result: /sbin/su: Permission denied Analysis: File system permissions restricted and denied access.
Alternative Location Check Command: ls -l /system/xbin/sudo: Result: /system/xbin/sudo: No such file or directory Analysis: File /system/xbin/sudo does not exist.
Root User ID and Group ID Status: Root user id: uid=0(root)
Root group id: gid=0(root)
System Environment PATH: /sbin /vendor/bin /system/sbin /system/bin /system/xbin
ADB Shell Default User: ADB shell setting for standard access, stored in default.prop, is configured as: shell (non root) user - ro.secure=1
Results provided on your SGH-T989 device by
Su or superuser
Are you using Superuser or SuperSu try reinstalling the APP from the market.
if not already a system app use titanium backup to convert to system app.
[email protected] said:
Are you using Superuser or SuperSu try reinstalling the APP from the market.
if not already a system app use titanium backup to convert to system app.
Click to expand...
Click to collapse
I've tried updating superuser from the market, even bought the elite version. Tried SuperSu and thus far, no luck. Tried using titanium just now and it didn't work on superuser.
---------- Post added at 12:14 PM ---------- Previous post was at 12:11 PM ----------
I've even reflashed the su signed efghi 3.0.7 apk.
[email protected] said:
Are you using Superuser or SuperSu try reinstalling the APP from the market.
if not already a system app use titanium backup to convert to system app.
Click to expand...
Click to collapse
Ive tried updating su before and the binary which seem to have no changes. As for making su a system app, when i flashed unroot to root, su appeared without me installing. Also, su doesnt seem to appear in titanium backup
/----Edit----\
I'm returning my phone today to fix the broken power button, the stiffness of the D30 case may have caused this.
Is it possible to direct me to a fully working 100% root?
brion1020 said:
Ive tried updating su before and the binary which seem to have no changes. As for making su a system app, when i flashed unroot to root, su appeared without me installing. Also, su doesnt seem to appear in titanium backup
/----Edit----\
I'm returning my phone today to fix the broken power button, the stiffness of the D30 case may have caused this.
Is it possible to direct me to a fully working 100% root?
Click to expand...
Click to collapse
I'm kind of wondering if flashing back to completely stock via Odin, then trying all over again will do it? I know as soon as I did the Kies update from 4.0.3 to 4.0.4 caused this issue on stock rooted.
Hype As Fruck said:
I'm kind of wondering if flashing back to completely stock via Odin, then trying all over again will do it? I know as soon as I did the Kies update from 4.0.3 to 4.0.4 caused this issue on stock rooted.
Click to expand...
Click to collapse
Just Odin back to stock and then reroot. Its super simple. Maybe if you can get back to you recovery somehow you can just flash another rom and install it where you can have your supersu access back.
Sent from my SGH-T989 using xda app-developers app