Database Info

Android-Wifi-Tether on Sprint 2.1 RUU

I went from a stock 1.5 to 2.1 using the Sprint 2.1 RUU and all is well. I understand it's a dev build and as such is already root but when I trying installing android-wifi-tether (both 2.0 and 1.6) it all looks well except when I touch the icon to start and it fails. The 1.6 version did report I didn't have root.
What do I need to do in ADB/shell to ensure the proper permissions are there for AWT? This is the last thing I want to get working and I'm happy.
Do I need to remount the filesystem as rw? Add superuser? Not sure what's needed.
Please help.

mobilehavoc said:
I went from a stock 1.5 to 2.1 using the Sprint 2.1 RUU and all is well. I understand it's a dev build and as such is already root but when I trying installing android-wifi-tether (both 2.0 and 1.6) it all looks well except when I touch the icon to start and it fails. The 1.6 version did report I didn't have root.
What do I need to do in ADB/shell to ensure the proper permissions are there for AWT? This is the last thing I want to get working and I'm happy.
Do I need to remount the filesystem as rw? Add superuser? Not sure what's needed.
Please help.
Click to expand...
Click to collapse
is busy box installed?
is SU working?

feefeeboomboom said:
is busy box installed?
is SU working?
Click to expand...
Click to collapse
I haven't done anything since flashing the 2.1 RUU. What steps do I need to do to get busybox and su working?

if you installed the RUU that was just 'leaked' (from what i understood our 2.1 builds are based off this ruu already). The build does not include busy box or anything for that matter that is required for wireless tether-
damageless said:
Here is a link to the latest RUU from Sprint.
You cannot simply extract it. This still has root since it is a test release. I recommend just doing an adb pull of your system directory after you flash it. Don't do this when the final one comes out or else you might be stuck without root.
You will need to add busybox, patch sh and su, and make sure that you do another recovery image and such. I also recommend adding Superuser.apk and stuff. If you use the Desire build.prop, you can get most of the protected apps working.
Enjoy.
http://dl.damagedroms.com/2.0/RUU_Hero_C_Sprint_2.20.651.1_signed_test.exe
Leak, I know who you are.
Click to expand...
Click to collapse
http://benno.id.au/blog/2007/11/14/android-busybox
Busy Box link for you, I'm not really sure how to get it working but it's a start, alot of results come up if you google "busybox for android", so I hope that helps ya out bud

mobilehavoc said:
I went from a stock 1.5 to 2.1 using the Sprint 2.1 RUU and all is well. I understand it's a dev build and as such is already root but when I trying installing android-wifi-tether (both 2.0 and 1.6) it all looks well except when I touch the icon to start and it fails. The 1.6 version did report I didn't have root.
What do I need to do in ADB/shell to ensure the proper permissions are there for AWT? This is the last thing I want to get working and I'm happy.
Do I need to remount the filesystem as rw? Add superuser? Not sure what's needed.
Please help.
Click to expand...
Click to collapse
Add SU and make sure you have USB debugging on (Menu/Settings/Applications/Development/USB Debugging). This is needed so when you try to start the WIfi Tether app that is says do you allow root permissions.

dwertz said:
Add SU and make sure you have USB debugging on (Menu/Settings/Applications/Development/USB Debugging). This is needed so when you try to start the WIfi Tether app that is says do you allow root permissions.
Click to expand...
Click to collapse
How do I add su? Any guides on here. Don't understand why busy box is required for wifi tether.

mobilehavoc said:
I went from a stock 1.5 to 2.1 using the Sprint 2.1 RUU and all is well. I understand it's a dev build and as such is already root
Click to expand...
Click to collapse
Who told you that the RUU was rooted already? It's not. Why would it be? Sprint has no interest in you being root.
As for why do you have to install busybox? Because the application requires it.

It's rooted because it's a dev release. It just doesn't appear to have busybox or superuser installed

mobilehavoc said:
How do I add su? Any guides on here. Don't understand why busy box is required for wifi tether.
Click to expand...
Click to collapse
Here is the superuser.apk You have to have root.
Put superuser.apk in your C:\AndroidSDK\Tools\
adb remount
adb push superuser.apk /system/app/

mobilehavoc said:
It's rooted because it's a dev release. It just doesn't appear to have busybox or superuser installed
Click to expand...
Click to collapse
It has no reason to have either one. As for whether or not it's rooted... when you connect to it with adb, what do you get?

posguy99 said:
It has no reason to have either one. As for whether or not it's rooted... when you connect to it with adb, what do you get?
Click to expand...
Click to collapse
Not sure what you mean but I was able to push a new build prop onto the phone using adb with no issues.

posguy99 said:
It has no reason to have either one. As for whether or not it's rooted... when you connect to it with adb, what do you get?
Click to expand...
Click to collapse
The leak actually is rooted. It's an engineering leak, so root can work his magic- but only from the adb shell.

why do you need superuser?
superuser requires root, if you had root, you wouldnt need it.
you can just dl the wifi tether for root from the market
program and it would work right?

10 chars and a poke

I need "su" and "superuser.apk" to get root apps to work

but where the fugg is "su".
I pushed superuser.apk no prblem but were is this extensionless su app??
Reason:
I rooted my gf's hero and need to run titanium to backup all her apps before I flash Fresh 2.1.2 to it. After lots of searching I se I need to put SU on it. Can soeone shed some light...?

scirio said:
but where the fugg is "su".
I pushed superuser.apk no prblem but were is this extensionless su app??
Reason:
I rooted my gf's hero and need to run titanium to backup all her apps before I flash Fresh 2.1.2 to it. After lots of searching I se I need to put SU on it. Can soeone shed some light...?
Click to expand...
Click to collapse
hmm.. you could just use another backup program that doesnt need root. i personally use astro to back up my apps.
assuming that just pushing superuser.apk works, then you should get a prompt when you try to use titanium back up that asks for root access.

su should be in /system/bin and I believe /system/xbin. I had to cp su /system/xbin for Metamorph to work a while ago...
Code:
adb shell
cd /system/bin
ls
see if su is in this folder. if it is then
Code:
cp su /system/xbin
But wait till someone else confirms this...
Also, if you are getting the black super user request screen make sure that you have USB Debugging turned on. Settings>Applications>Development>USB Debugging Mode

"su" is not an app.. "su" is command for "super user"..
"su" is root access.. If the rom you are using is not rooted it will never have "su".. Because the rom will not allow sudo access
*search for appsaver to get the apps from an unrooted rom..

azyouthinkeyeiz said:
"su" is not an app..
"su" is root access.. If the rom you are using is not rooted it will never have "su"..
Click to expand...
Click to collapse
Have to kind of disagree with you here.
he is refering to the SU file that lives in //bin/
Which is technically "executable" when setting suid bits.
But you are correct in that the rom should have that. And if it doesn't...she's not rooted...and you'll need more than just SU eventually...you should go ahead and get busy box installed for TIbackup to use.

Kcarpenter said:
Have to kind of disagree with you here.
he is refering to the SU file that lives in //bin/
Which is technically "executable" when setting suid bits.
But you are correct in that the rom should have that. And if it doesn't...she's not rooted...and you'll need more than just SU eventually...you should go ahead and get busy box installed for TIbackup to use.
Click to expand...
Click to collapse
The su file that lives in //bin/ allows the rom to interact with busybox and supermissions.. It is not an APP just a directory file.. That's like saying on a PC that the DLL files for each program is a program.. It does "execute" but there is not a single file on your computer that isn't "executable" in someway.. I was just saying in layman's terms that he can't do what he wants..
You can't just install that on a Sprint Rom.. He cannot just push busybox into his rom because it is lacking the su file.. And it cannot interact with the Sprint Rom even if you did get it installed somehow...
Yes he rooted the phone, but the ROM is still locked in by sprint until you flash a custom rom.. You have to repackage the rom and reflash it to get those parts into the rom.. Which would not help this guy with what he wants..
*again.. Search for appsaver.. it is the easiest solution for you OP

azyouthinkeyeiz said:
The su file that lives in //bin/ allows the rom to interact with busybox and supermissions.. It is not an APP just a directory file.. That's like saying on a PC that the DLL files for each program is a program.. It does "execute" but there is not a single file on your computer that isn't "executable" in someway.. I was just saying in layman's terms that he can't do what he wants..
You can't just install that on a Sprint Rom.. He cannot just push busybox into his rom because it is lacking the su file.. And it cannot interact with the Sprint Rom even if you did get it installed somehow...
Yes he rooted the phone, but the ROM is still locked in by sprint until you flash a custom rom.. You have to repackage the rom and reflash it to get those parts into the rom.. Which would not help this guy with what he wants..
*again.. Search for appsaver.. it is the easiest solution for you OP
Click to expand...
Click to collapse
I knew it wasn't an "app" but I also figured you guys were smart enough not to hassle me about symantics
Ended up just flashing Fresh 2.1.2 and to hell with her apps.

scirio said:
to hell with her apps.
Click to expand...
Click to collapse
I tell ya what, every time I wipe my wifes phone and wipe out that "My Days" app. She wants to kill me. You'd think she has that schedule memorized...lord knows I do.

RESOLVED:Rooted but getting Permission Denied from ADB Shell?

ADB Shell connects just fine, but I cannot SU into it. I am rooted and have the latest SuperUser installed... In addition, I have USB debugging enabled, the LG drivers, and Root Explorer works perfectly.
RESOLVED:
You must have SuperUser OPEN while trying to SU from ADB. I don't remember this being needed on my Nexus One, but it's working now. I will keep this up for others that might need it....

Sceencast in droid explorer isnt working for me.rooted g2x. Maybe ill reinstall it after i get home from work. Is yours working?

Do you have SuperUser OPEN while trying to use it? Seems that it's not running persistently like it did on my N1

momentarylapseofreason said:
Do you have SuperUser OPEN while trying to use it? Seems that it's not running persistently like it did on my N1
Click to expand...
Click to collapse
just got home from work. gonna try it now.
nope, no screencast even with super user running. just rebooted. gonna try again. logcat seems to be going nuts though.

I was going crazy about this and asked Chris Soyars because I have never had to do this either. This is what he said:
"You can just type 'su' while in an adb shell, and it should drop you down to root. You won't get adb providing root until you have a boot image flashed that isn't running in secure mode.... -Chris Soyars"

wewoapsiak said:
I was going crazy about this and asked Chris Soyars because I have never had to do this either. This is what he said:
"You can just type 'su' while in an adb shell, and it should drop you down to root. You won't get adb providing root until you have a boot image flashed that isn't running in secure mode.... -Chris Soyars"
Click to expand...
Click to collapse
First you need to go to settings developer options and root access and check apps and ADB
Then you might have to do the CHMOD -R 777 /directorynameyouaretryingtoaccess

Guys. I am assuming the su in adb shell is preceded by an adb remount? By default system is ro not rw.
Sent from my LG-P999 using xda app-developers app

[Q] Superuser permissions

Hello
Have unlocked the phone and installed custom android OS a while ago, but then all of a sudden i do not have root access anymore, even tryed to reinstall the phone. Though i do have a bad feeling about it wasn't needed
My problems is that im unable to give programs root access, it looks like the phone is not rooted acording to the programs.
Also if i try the following:
adb shell
su
then i get "permission denied"
Can't seem to figure out where my flaw is. Even tryed to
Anyone got an idea to what the problem might be? Have looked through the nexus s forum for clues but no luck.
/Fonain

fonain said:
Hello
Have unlocked the phone and installed custom android OS a while ago, but then all of a sudden i do not have root access anymore, even tryed to reinstall the phone. Though i do have a bad feeling about it wasn't needed
My problems is that im unable to give programs root access, it looks like the phone is not rooted acording to the programs.
Also if i try the following:
adb shell
su
then i get "permission denied"
Can't seem to figure out where my flaw is. Even tryed to
Anyone got an idea to what the problem might be? Have looked through the nexus s forum for clues but no luck.
/Fonain
Click to expand...
Click to collapse
Most likely the permissions on the su binary are f'd up (assuming it's present). The easiest fix is just to reflash the su binary (mount /system first) through CWM.

do you by any chance have a guide to do that? or a link to one?

fonain said:
do you by any chance have a guide to do that? or a link to one?
Click to expand...
Click to collapse
There are several rooting guides here if you do not have CWM installed:
http://forum.xda-developers.com/showthread.php?t=1067813
They will go over quite a few things. However, if you are unlocked and have fastboot set up it's as simple as downloading the recovery image, and then using fastboot to flash the recovery (fastboot flash recovery recovery.image.name.img)
Once CWM is installed boot into recovery and flash the su binary here:
http://forum.xda-developers.com/showthread.php?t=682828

well the funny thing is that i already have 2.3.6.1 installed, but i still dont have su rights.
When i try to follow the buttom guide where to install superuser. where it states that i should write "adb remount". Then i get the message back where it says "Operation not allowed", or when i type su i get the message "permission denied".
I seriously don't understand what i have done wrong :S
/Fonain

krohnjw said:
Most likely the permissions on the su binary are f'd up (assuming it's present). The easiest fix is just to reflash the su binary (mount /system first) through CWM.
Click to expand...
Click to collapse
Thanks for this, solved my issue

thanks figured it out
/Fonain

Sorry to bring back an old topic, but Ive petty much done everything and still the SU no permission no root access for everything occurs. NO TIT backup, no rommanager, no nothing T_T, why???

try chmod the folder/file or using sudo

james7132 said:
try chmod the folder/file or using sudo
Click to expand...
Click to collapse
Can you elaborate please. Whats chmod or sudo and how do I go about doing them?

[Q] Removing /system/xbin/.tmpsu

Good morning everyone!
I need some help in removing the file /system/xbin/.tmpsu I found on my nexus 5 after removing SuperSU.
I have to send my phone back for warranty because of broken usb port (so no fastboot, adb...).
Analyzing the file, I found that it'is a normal su executable (correct me if I'm wrong), probably used by SuperSU itself to clean its stuff during removal: so I tried in terminal emulator to gain su privileges with .tmpsu, remount /system as rw and remove .tmpsu, but it's a no-win... Any other idea?
Additional info: the phone now is completely stock (ready for warranty), so no cwm or twrp... everything ok apart of that executable, and I'm worried they will complain about it
Thank you!!!
PS: everyone of us rooted and on stock should have that file on his phone; you can use "strings .tmpsu" and see it really is the normal su executable by chainfire...!

vaccaaa said:
Good morning everyone!
I need some help in removing the file /system/xbin/.tmpsu I found on my nexus 5 after removing SuperSU.
I have to send my phone back for warranty because of broken usb port (so no fastboot, adb...).
Analyzing the file, I found that it'is a normal su executable (correct me if I'm wrong), probably used by SuperSU itself to clean its stuff during removal: so I tried in terminal emulator to gain su privileges with .tmpsu, remount /system as rw and remove .tmpsu, but it's a no-win... Any other idea?
Additional info: the phone now is completely stock (ready for warranty), so no cwm or twrp... everything ok apart of that executable, and I'm worried they will complain about it
Thank you!!!
PS: everyone of us rooted and on stock should have that file on his phone; you can use "strings .tmpsu" and see it really is the normal su executable by chainfire...!
Click to expand...
Click to collapse
If you have removed both SuperSU AND the su binary, there is nothing you can do now.
Although they're not...
1) going to look for these files.
2) reject warranty for a hardware issue not related to root anyway

all the above, except:
- you should be able to install supersu from playstore, then enable root
- you could use adb via wifi

kendong2 said:
all the above, except:
you should be able to install supersu from playstore
Click to expand...
Click to collapse
Yes
kendong2 said:
all the above, except:
then enable root
Click to expand...
Click to collapse
No, not if the SU binary was removed. Otherwise we'd all be rooting our Nexus 5 this way
kendong2 said:
all the above, except:
- you could use adb via wifi
Click to expand...
Click to collapse
But without root, this is useless. What will it achieve?

rootSU said:
No, not if the SU binary was removed. Otherwise we'd all be rooting our Nexus 5 this way
Click to expand...
Click to collapse
if we all had a hidden file /system/xbin/.tmpsu then we would all be rooting our nex's this way, yes
rootSU said:
But without root, this is useless. What will it achieve?
Click to expand...
Click to collapse
after installing supersu from playstore there will be root again.

kendong2 said:
if we all had a hidden file /system/xbin/.tmpsu then we would all be rooting our nex's this way, yes
Click to expand...
Click to collapse
Oh I see what you're saying. Sorry