Database Users

{Behold 2 }[How-to] Root for App's working with Persistent root

First off, I want to say thanks to Kam187 & the Creators of asroot
Okay, Below is the Method I used for getting Root working for my app's.
Even though Shell is running as Root, any Call's made to su trigger's the white List Superuser.apk, So don't think your phone is wide open. G1's & MT3G Setup's are the same regard sh.
I'm not sure is the apk is counted as warez or not, if so I hope a Mod will remove the link to the Apk or let me know to Remove it...
Okay, File's Need to complete the Task is....
Try3 Placed in C:\SDK\tools> found here > File's attached below
SU for /system/bin found here > File's attached below
Superuser app control for our App's found Here > File's attached below
Next, Mount the SDCARD and place the SU file in the root of the sdcard like so ( /sdcard ). This is Important!!!
From here we do the Following.. ( Kam187 script the I edited ).
adb push try3 /data/local
adb shell chmod 0755 /data/local/try3
adb shell
/data/local/try3 /system/bin/sh
mount -o rw,remount /dev/st9 /system
chmod 04755 /system/bin/sh
cat /sdcard/su > /system/bin/su1
cat /sdcard/su > /system/bin/su
chmod 04755 /system/bin/su
su
cat /system/bin/playlogo > /system/bin/playlogo_real
/system/bin/chmod 0755 /system/bin/playlogo_real
echo "#!/system/bin/sh
/data/local/try3 /system/bin/sh
mount -o rw,remount /dev/st9 /system
chmod 04755 /system/bin/sh
cat /system/bin/su1 > /system/bin/su
chmod 04755 /system/bin/su
/system/bin/playlogo_real" > /system/bin/playlogo
Click to expand...
Click to collapse
Once Done, place the Superuser.apk in your SDK tools Directory.
Mine happens to look like this
C:\SDK\tools>
Click to expand...
Click to collapse
Once you have that Copied over, Open a Command prompt and CD to your sdk\tools directory and type the following.
adb install Superuser.apk
Click to expand...
Click to collapse
Once done, do a reboot of the Phone, Once boot up is complete open a Command Prompt ( or app that needs Root ).
For Command Prompt, type:
adb shell
Click to expand...
Click to collapse
su
Click to expand...
Click to collapse
If done correctly you will now see the deny or allow prompt on the Phone, or just open any app that needs root & you will see the same window.
Here's some Picture of it working
SU working with SU apk on Twitpic & SU working with SU apk on Twitpic

Quickboot fix...SU permission issue.

I did this
QUICKBOOT FIX - WORKS
cd C:\android-sdk-windows\tools
adb remount
adb push reboot /system/bin
adb shell
cd /system/bin/
ls **optional...I did this just so I could make sure the reboot file was there**
chmod 755 reboot
chmod 755
when I go into quickboot now and try reboot/recovery/bootload it hangs on the SU permission screen and I get an SU error
any ideas?
Chad

nimitz87 said:
I did this
QUICKBOOT FIX - WORKS
cd C:\android-sdk-windows\tools
adb remount
adb push reboot /system/bin
adb shell
cd /system/bin/
ls **optional...I did this just so I could make sure the reboot file was there**
chmod 755 reboot
chmod 755
when I go into quickboot now and try reboot/recovery/bootload it hangs on the SU permission screen and I get an SU error
any ideas?
Chad
Click to expand...
Click to collapse
did you download the reboot file that was attached?

d1msum4lyfe said:
did you download the reboot file that was attached?
Click to expand...
Click to collapse
yes, it pushed fine, and I see it in system/bin
Chad

nimitz87 said:
I did this
QUICKBOOT FIX - WORKS
cd C:\android-sdk-windows\tools
adb remount
adb push reboot /system/bin
adb shell
cd /system/bin/
ls **optional...I did this just so I could make sure the reboot file was there**
chmod 755 reboot
chmod 755 /system/bin/reboot (y ? quirk )
when I go into quickboot now and try reboot/recovery/bootload it hangs on the SU permission screen and I get an SU error
any ideas?
Chad
Click to expand...
Click to collapse
I missed it, are you doing it from a #?
sdb shell
$su
...reboot...

willy900wonka said:
I missed it, are you doing it from a #?
sdb shell
$su
...reboot...
Click to expand...
Click to collapse
I don't understand what your saying Willy...I'm pretty new to all this
I just realized however SU permissions isn't working at all now for any apps.
Chad

turn usb debugging on

Have you set debug mode ?
menu>setting>application>development>usb debugging (check)

HTC hero Owner running Linux OS

Looking for assitance installing HTC hero drivers and Devtool ( adb shell ) on a Linux OS based laptop
I have Jolicloud ( Ubuntu base OS for netbooks ) (sudo commands)
if someone could provide a guide or assitance..

The drivers are there already
as for dev tools that pretty easy
download the sdk, extract it to a folder in ~/bin, run
Code:
cd ~/bin
chown +x *
then edit ~/.bashrc and add the line PATH="$HOME/bin:$PATH"
should do it for ya, now you just run adb by putting adb in the terminal

Vrekk said:
The drivers are there already
as for dev tools that pretty easy
download the sdk, extract it to a folder in ~/bin, run
Code:
cd ~/bin
chown +x *
then edit ~/.bashrc and add the line PATH="$HOME/bin:$PATH"
should do it for ya, now you just run adb by putting adb in the terminal
Click to expand...
Click to collapse
thanks but i am having problems moving it to the bin folder ..gives permission denied

whast the line comand to extract file to bin folder?
never mind i got it
sudo mv android-sdk-linux_86

rgildoss said:
whast the line comand to extract file to bin folder?
Click to expand...
Click to collapse
Sorry I was cleaning up. Make sure you are extracting it to the bin folder in your home, NOT THE ROOT ONE. If the folder doesn't exist create it
I realized that the first thing I told you to do was wrong, we want the stuff in the tools folder NOT everthing in the sdk, cd into the folder the android sdk is in and run this: (skip the chmod +x step above, I moved it to down here
command:
Code:
tar -xzf android-sdk_r05-linux_86.tgz
chmod +x android-sdk-linux_86/tools/*
cd -r android-sdk-linux_86/tools/* ~/bin
rm -r android-sdk-linux_86 'this will remove anything you don't need Optional
If you get an error saying that ~/bin dosn't exist, run
Code:
mkdir ~/bin
then edit the .bashrc like described in my first post
EDIT:If should not have needed sudo if you moved it to /home/rgildoss/bin only if you moved it to /bin should it have caused problems. You don't want it in /bin

that cd -r gives me an error
bash: cd -r: invalid option
cd: usage: cd [-L|-P]..[dir]

Oops! typo! try cp no cd lol

Vrekk said:
Oops! typo! try cp no cd lol
Click to expand...
Click to collapse
LOL
okay that worked
one last thing
chown +x * also gives error
chown: invalid user: `+x'
also tried
chown +x*
chown: missing operand after `+x*'

It shouldn't have to be in bin unless you're going to need access to the executable from anywhere in the directory tree. I run mine out of ~/android/ and it's fine. As far as permissions go, chown changes the owner of the file, chmod changes the permissions. If you're the only user on the machine, change the permissions with the octal: chmod 777 path/to/files/*

rgildoss said:
LOL
okay that worked
one last thing
chown +x * also gives error
chown: invalid user: `+x'
also tried
chown +x*
chown: missing operand after `+x*'
Click to expand...
Click to collapse
damn I really off my game tonight, should be chmod not chown

okay everything is good except for the last step:
then edit ~/.bashrc and add the line PATH="$HOME/bin:$PATH"
how do i edit this ? and were is the file at?
im sorry about all the question, its been over 4 years sisnce i used linux ( ubuntu ) and i wasnt very good at then either...lol
HELP!
lol
EDIT: my files are in [email protected]:/home/rico/bin#

rgildoss said:
okay everything is good except for the last step:
then edit ~/.bashrc and add the line PATH="$HOME/bin:$PATH"
how do i edit this ? and were is the file at?
im sorry about all the question, its been over 4 years sisnce i used linux ( ubuntu ) and i wasnt very good at then either...lol
HELP!
lol
EDIT: my files are in root@mini:/home/rico/bin#
Click to expand...
Click to collapse
One thing, why are you loged in as root?
and nano ~/.bashrc should do it
or gedit ~.bashrc if you like gui better

rgildoss said:
okay everything is good except for the last step:
then edit ~/.bashrc and add the line PATH="$HOME/bin:$PATH"
how do i edit this ? and were is the file at?
Click to expand...
Click to collapse
A user specific .bashrc doesn't exist by default in most Ubuntu based distros. Create it with...
Code:
touch ~/.bashrc
...and add the path statement. There should also be a systemwide bashrd located at /etc/bash.bashrc

Vrekk said:
One thing, why are you loged in as root?
and nano ~/.bashrc should do it
or gedit ~.bashrc if you like gui better
Click to expand...
Click to collapse
force of habit from old days ....

rgildoss said:
thanks but i am having problems moving it to the bin folder ..gives permission denied
Click to expand...
Click to collapse
If you want to send to /bin or /usr/bin, you'll need superuser access:
Command is: sudo su
Then type your password.
What was recommended was creating a bin directory in your home directory. Then edit your .bashrc to include the new bin directory.

[email protected]:~$ adb devices
List of devices attached
???????????? no permissions
[email protected]:~$
did i do something wrong?

comintern said:
A user specific .bashrc doesn't exist by default in most Ubuntu based distros. Create it with...
Code:
touch ~/.bashrc
Click to expand...
Click to collapse
I forgot that, been so long sence the last time I booted up anything ubuntu based or even
rgildoss said:
force of habit from old days ....
Click to expand...
Click to collapse
did it work? You will need to reopen a terminal in order for it to use the new file, but then you should be able to use adb like any other linux command
EDIT: you answered my question before I posted it, nice
Hmm, I don't know what to do about that part, when ever I get an error like I can't get it to go away

rgildoss said:
[email protected]:~$ adb devices
List of devices attached
???????????? no permissions
[email protected]:~$
did i do something wrong?
Click to expand...
Click to collapse
1. Try adb kill-server first, then rerun the command.
2. If that doesn't work, run as superuser...see if that fixes it.

tkirton said:
1. Try adb kill-server first, then rerun the command.
2. If that doesn't work, run as superuser...see if that fixes it.
Click to expand...
Click to collapse
nope
wtf....
lol

[email protected]:~$ adb kill-server
[email protected]:~$ adb devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
???????????? no permissions
[email protected]:~$

Help with installing a theme! Kinda urgent...

Im hoping to get some help to get a theme installed on my phone.
It is rooted successfully, busybox is installed successfully also.
Im trying to put the Minimal Matte theme on my phone, but no success. Actually, I managed to make my Contacts disappear...
So, I would greatly appreciate help! I don't know why the adb commands are not working that are given here:
Code:
adb shell mount -o remount,rw /dev/block/stl16 /system
adb push Contacts.apk /system/app/
adb push DialerTabActivity.apk /system/app/
adb push Settings.apk /system/app/
adb push framework-res.apk /system/framework/
adb push twframework-res.apk /system/framework/
If I try it like that, the mounting does not work cuz it says "not permitted". So then I try like this and I get this. So it is not working. How do I fix this and how do I get the theme into my phone? Thank you for help,
Here's what I tried:
Code:
c:\>adb shell
$ su
su
# mount -o remount,rw /dev/block/stl16 /system
mount -o remount,rw /dev/block/stl16 /system
# push Contacts.apk /system/app/
push Contacts.apk /system/app/
push: not found
#

Hey Polar, your commands when you're saying "push Contacts.apk /system/app/" is actually running inside the adb shell.
To do what you did, try this:
Code:
adb shell
su
mount -o remount,rw /dev/block/stl16 /system
exit
exit
adb push Contacts.apk /system/app/
Let me know if this works!
Also, if you downloaded version 1.3, you can always use the automated bat file! Or did that fail for you too?

Please note that your phone must be rooted! Your phone is rooted right?

barqers said:
Hey Polar, your commands when you're saying "push Contacts.apk /system/app/" is actually running inside the adb shell.
To do what you did, try this:
Code:
adb shell
su
mount -o remount,rw /dev/block/stl16 /system
exit
exit
adb push Contacts.apk /system/app/
Let me know if this works!
Also, if you downloaded version 1.3, you can always use the automated bat file! Or did that fail for you too?
Click to expand...
Click to collapse
Let me try this...
Im very new to all this, so I'd like to learn the tricks manually so I have a better understanding.
barqers said:
Please note that your phone must be rooted! Your phone is rooted right?
Click to expand...
Click to collapse
As stated in the first post, it is rooted and busybox is installed. Now..let me try your tips. I will report back.

Hmm..still facing the "permission denied" with these commands:
Code:
c:\>adb shell
$ su
su
# mount -o remount,rw /dev/block/stl16 /system
mount -o remount,rw /dev/block/stl16 /system
# exit
exit
$ exit
exit
c:\>adb push Contacts.apk /system/app/
failed to copy 'Contacts.apk' to '/system/app//Contacts.apk': Permission denied

Okay, let's try it with a different partition used to remount. Try this out
Code:
adb kill server
adb shell mount -o remount,rw /dev/block/stl9 /system
adb push Contacts.apk /system/app/
If this doesn't work, try rebooting your phone and trying again.
I hope this works, cause I only have 21 minutes left on my laptop battery life

barqers said:
Okay, let's try it with a different partition used to remount. Try this out
Code:
adb kill server
adb shell mount -o remount,rw /dev/block/stl9 /system
adb push Contacts.apk /system/app/
If this doesn't work, try rebooting your phone and trying again.
I hope this works, cause I only have 21 minutes left on my laptop battery life
Click to expand...
Click to collapse
Tried this, but it seems I have to reboot since it did not work.
It does not let me use "adb shell mount -o remount,rw /dev/block/stl9 /system" when I try it. Only when I do the "su" first and then try that...
Now let me try again after reboot.

Still no dice...
Code:
c:\>adb shell
$ su
su
# mount -o remount,rw /dev/block/stl9 /system
mount -o remount,rw /dev/block/stl9 /system
# exit
exit
$ exit
exit
c:\>adb push Contacts.apk /system/app/
failed to copy 'Contacts.apk' to '/system/app//Contacts.apk': Permission denied

Okay here are a couple things I've noticed before in the past.
1. The phone could "successfully" be rooted, but not actually work. In this case it's best to re-root your phone. The superoneclick method works well.
2. Maybe adb is just fussing over nothing, so you could try this:
Code:
adb shell
su
mount -o remount,rw /dev/block/stl16 /system
exit
exit
adb push Contacts.apk /sdcard/
adb push /sdcard/Contacts.apk /system/app/
My primary guess though is that rooting isn't working properly.

barqers said:
Okay here are a couple things I've noticed before in the past.
1. The phone could "successfully" be rooted, but not actually work. In this case it's best to re-root your phone. The superoneclick method works well.
2. Maybe adb is just fussing over nothing, so you could try this:
Code:
adb shell
su
mount -o remount,rw /dev/block/stl16 /system
exit
exit
adb push Contacts.apk /sdcard/
adb push /sdcard/Contacts.apk /system/app/
My primary guess though is that rooting isn't working properly.
Click to expand...
Click to collapse
Well, when I go and click the superuser app and all, I can see stuff happening there. Also, it has asked for permission before for adb when I first used it and I gave it. Now it appears on the list there...so it seems to be working correctly, no? And I did it with the superoneclick and it ran through it smoothly as ever. Now let me try if adb is being fussy.

Now what the heck... It pushed the Contacts.apk on the sdcard, but then this...
Code:
c:\>adb push Contacts.apk /sdcard/
3170 KB/s (3284674 bytes in 1.011s)
c:\>adb push /sdcard/Contacts.apk /system/app/
cannot stat '/sdcard/Contacts.apk': No such file or directory
And I can clearly see the file in the sdcard...

PolarSoul said:
Now what the heck... It pushed the Contacts.apk on the sdcard, but then this...
Code:
c:\>adb push Contacts.apk /sdcard/
3170 KB/s (3284674 bytes in 1.011s)
c:\>adb push /sdcard/Contacts.apk /system/app/
cannot stat '/sdcard/Contacts.apk': No such file or directory
And I can clearly see the file in the sdcard...
Click to expand...
Click to collapse
ADB is being truly fussy! Do you have root explorer? Here is my best guess for you. Move the Contacts.apk to the /system/app/ folder manually with Root Explorer, then follow this guide to give the app root permissions:
http://francoforr.blogspot.com/2010/12/cant-reinstall-apks-easy-fix.html

Have to go find Root Explorer.

PolarSoul said:
Have to go find Root Explorer.
Click to expand...
Click to collapse
Root explorer is a paid app. But maybe ES File Manager or Astro File Manager will give you root capabilities too!

I tried this to go there with root explorer, gave the right permissions..copied the file and navigated to system/apps. Hit paste..and it tells me "not enough space". What to do now? Getting a little desperate here.

PolarSoul said:
I tried this to go there with root explorer, gave the right permissions..copied the file and navigated to system/apps. Hit paste..and it tells me "not enough space". What to do now? Getting a little desperate here.
Click to expand...
Click to collapse
There you go! That's the problem. First check this, does Contacts.apk already exist in /system/app/? If so, use these codes:
Code:
adb shell
su
mount -o remount,rw /dev/block/stl16 /system
exit
exit
adb rm /system/app/Contacts.apk
adb push Contacts.apk /system/app/
Repeat for each apk file you want to copy over.
Or alternatively you could just use root explorer, delete Contacts.apk and then move over your Contacts.apk from the sdcard. OR You can uninstall some apps and give yourself some available memory in your /system/app/ folder.
You'll need at least 15mb of free space in /system/app/

barqers said:
There you go! That's the problem. First check this, does Contacts.apk already exist in /system/app/? If so, use these codes:
Code:
adb shell
su
mount -o remount,rw /dev/block/stl16 /system
exit
exit
adb rm /system/app/Contacts.apk
adb push Contacts.apk /system/app/
Repeat for each apk file you want to copy over.
Or alternatively you could just use root explorer, delete Contacts.apk and then move over your Contacts.apk from the sdcard. OR You can uninstall some apps and give yourself some available memory in your /system/app/ folder.
You'll need at least 15mb of free space in /system/app/
Click to expand...
Click to collapse
I will go try these, starting from the adb commands. If I finally get this all to work and I have your pretty theme running, we need to go have a beer you and I. For all the help you've given me today.

PolarSoul said:
I will go try these, starting from the adb commands. If I finally get this all to work and I have your pretty theme running, we need to go have a beer you and I. For all the help you've given me today.
Click to expand...
Click to collapse
No problem~! Haha, yes we do But I think Finland is far from Canada!
I'm hoping it works for you!

It's not looking good still... *sigh* Still says not enough space. I tried both adb and manual with the same results. What can I do?

PolarSoul said:
It's not looking good still... *sigh* Still says not enough space. I tried both adb and manual with the same results. What can I do?
Click to expand...
Click to collapse
If you check settings -> SD card and storage. How much memory does it say you have? If you have less then 10mb either move some apps to the sd card or uninstall some!

[Q] Running shell scripts on Defy+

I'm trying to automate some things I do after upgrading nightlies using a shell script. The system seems to execute the shell script (shows messages informing granting of root privileges and successful completion of the script), but the script does not seem to run, ie the changes do not occur. Here's the script if it's of any help :
Code:
#!/system/bin/mksh
# Gain root access
su -
# Replace baseband
rm /system/etc/motorola/bp_nvm_default/*
cp /mnt/sdcard/Download/bp_nvm_default/* /system/etc/motorola/bp_nvm_default/
chown root:root /system/etc/motorola/bp_nvm_default/*
chmod 644 /system/etc/motorola/bp_nvm_default/*
# Make Apex Launcher system app
cp /mnt/sdcard/Download/ApexLauncher.apk /system/app/
chown root:root /system/app/ApexLauncher.apk
chmod 644 /system/app/ApexLauncher.apk
# Move Marimba ringtone to phone
cp /mnt/sdcard/Download/Marimba.ogg /system/media/audio/ringtones/
chown root:root /system/media/audio/ringtones/Marimba.ogg
chmod 644 /system/media/audio/ringtones/Marimba.ogg

I'm amazed there are no replies to this thread.
No one ever tried running a shell script on their rooted phone?

S_xda said:
I'm amazed there are no replies to this thread.
No one ever tried running a shell script on their rooted phone?
Click to expand...
Click to collapse
What did you tried to run the script??, use the terminal or the SManager.

SManager works fine to me

Questions go in the Q&A section