Related
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
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!
Download THIS file.
Extract the things inside it and put them in your adb folder.
push it.
Code:
adb push be_photo /system/etc
adb push be_movie /system/etc
now pull the build.prop file
Code:
adb pull /system/build.prop
go to adb folder and open the buid.prop file with notepad. add this to the end of it:
Code:
ro.service.swiqi.supported=true
persist.service.swiqi.enable=1
save and push it back in:
Code:
adb push build.prop /system
now go to terminal emulator on your phone and type this in:
Code:
su
busybox chmod 0755 /system/etc/be_photo
busybox chmod 0755 /system/etc/be_movie
busybox chown 0.0 /system/etc/be_photo
busybox chown 0.0 /system/etc/be_movie
reboot the phone and have happy times with the bravia engine >
i got this information from Kabir Saini on facebook. I didnt do any of this work myself
i tried it on my phone and i think there is a slight improvement...
PersianSphinx said:
Download THIS file.
Extract the things inside it and put them in your adb folder.
push it.
Code:
adb push be_photo /system/etc
adb push be_movie /system/etc
now pull the build.prop file
Code:
adb pull /system/build.prop
go to adb folder and open the buid.prop file with notepad. add this to the end of it:
Code:
ro.service.swiqi.supported=true
persist.service.swiqi.enable=1
save and push it back in:
Code:
adb push build.prop /system
now go to terminal emulator on your phone and type this in:
Code:
su
busybox chmod 0755 /system/etc/be_photo
busybox chmod 0755 /system/etc/be_movie
busybox chown 0.0 /system/etc/be_photo
busybox chown 0.0 /system/etc/be_movie
reboot the phone and have happy times with the bravia engine >
i got this information from Kabir Saini on facebook. I didnt do any of this work myself
i tried it on my phone and i think there is a slight improvement...
Click to expand...
Click to collapse
Are you sure that it work buddy? I want mean, not necessary other files like framework or libraries?
How system knows that are 2 new files in /system only editing build.prop?
there's already an another thread about it.. :/
-tapatalked by RnB
i_rnb said:
there's already an another thread about it.. :/
-tapatalked by RnB
Click to expand...
Click to collapse
sorry, but i searched for it and couldnt find anything!
denzel09 said:
Are you sure that it work buddy? I want mean, not necessary other files like framework or libraries?
How system knows that are 2 new files in /system only editing build.prop?
Click to expand...
Click to collapse
apparently it will work. im not 100% but i think it will.
anyways, its only 2KB your adding, so big deal right?
PersianSphinx said:
sorry, but i searched for it and couldnt find anything!
Click to expand...
Click to collapse
u had to search a lil bit longer ..
http://forum.xda-developers.com/showthread.php?p=19597041
-tapatalked by RnB
Hi i have problem with Kindle Fire,
i changed permissions folder system/app with app Root explorer and then I restart Kindle Fire and now dont want start. I think this is problem permissons for this directory.
Pleas can you send me setting permissions folder APP and how i can change it by ADB SHELL?
I have tried:
adb shell
su
chmod 644 app
Unable to chmod app: Read-only file system
THX very much .-(
Sory my english is very bad.
adb shell
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
chmod 755 /system/app
or look here:
http://forum.xda-developers.com/showthread.php?t=1356257
guys please use the search function !
I have tried it but:
$ mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
mount: Operation not permitted
$ chmod 755 /system/app
chmod 755 /system/app
Unable to chmod /system/app: Read-only file system
THX I'm a little desperate
pitrsonek said:
I have tried it but:
$ mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
mount: Operation not permitted
$ chmod 755 /system/app
chmod 755 /system/app
Unable to chmod /system/app: Read-only file system
THX I'm a little desperate
Click to expand...
Click to collapse
you need root before you can do any of those (i.e. su)
But i think i have root because I install Google market and other app. Or how i can check if i have root?
THX!
c:\Program Files (x86)\Android\android-sdk\platform-tools>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
4D1A002600000001 device
c:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell
$ ls
ls
config
dropbox
cache
sdcard
acct
mnt
vendor
d
etc
ueventd.rc
ueventd.omap4430.rc
ueventd.goldfish.rc
system
sys
sbin
proc
init.rc
init.omap4430.rc
init.goldfish.rc
init
default.prop
data
root
dev
$
at the $ prompt type
su
should turn to # instead of $
Then you are Root.
krelvinaz said:
at the $ prompt type
su
should turn to # instead of $
Then you are Root.
Click to expand...
Click to collapse
Yes, what he said...you're confusing having root on the command line for "I installed su and superuser to their correct locations"
adb shell
$ su
su
[1] + Stopped (signal) su
$ su
su
[2] + Stopped (signal) su
[1] Segmentation fault su
$
I have try install root by this manual: http://rootkindlefire.com/kindle-fire-root/how-to-root-kindle-fire/
I see device when i write: adb devices
I have executed runme.bat
but SU dont go
pitrsonek said:
adb shell
$ su
su
[1] + Stopped (signal) su
$ su
su
[2] + Stopped (signal) su
[1] Segmentation fault su
$
I have try install root by this manual: http://rootkindlefire.com/kindle-fire-root/how-to-root-kindle-fire/
I see device when i write: adb devices
I have executed runme.bat
but SU dont go
Click to expand...
Click to collapse
Something is wrong with your device then.
as a first step look if you have superuser.apk in \system\app\
Ho i dont have Superuser.apk in /system/app/
b63 said:
as a first step look if you have superuser.apk in \system\app\
Click to expand...
Click to collapse
Doesn't really matter if su is not working. Superuser.apk is just a wrapper for su and he's trying to do things on the command line so su is what he's calling to, not SuperUser.apk.
He either didnt root correctly to begin with or he did something after that messed things up. Temp rooting with zergRush and redoing things is most likely what he needs to do.
Is ther somebody who can help me online on gtalk? I will pay you by PayPal. If anybody has freetime send me PM. THX
Ther is content dir app:
c:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell
$ ls /system/app
ls /system/app
-------------------------------------------------------------------------
ATVAndroidClient.apk
AccountAndSyncSettings.apk
AmazonVenezia.apk
ApplicationsProvider.apk
AudibleAndroidApplication-venezia.apk
CSApp-unsigned.apk
CalendarProvider.apk
CertInstaller.apk
Cloud9-unsigned.apk
Cloud9SystemBrowserProvider-unsigned.apk
Contacts.apk
ContactsProvider.apk
DefaultContainerService.apk
DownloadProvider.apk
DownloadProviderUi.apk
DrmProvider.apk
Email.apk
Facebook.apk
Gallery3D.apk
HTMLViewer.apk
IMDb-2.3.apk
KindleForOtter.apk
LatinIME.apk
Launcher.apk
LiveWallpapers.apk
LiveWallpapersPicker.apk
MagicSmokeWallpapers.apk
MarketIntentProxy.apk
MediaProvider.apk
MyAccount-unsigned.apk
OOBE-unsigned.apk
OTASilentInstall.apk
OtterAppManager.apk
OtterTutorial.apk
PackageInstaller.apk
PicoTts.apk
Provision.apk
Pulse-amazon.apk
QuickSearchBox.apk
QuickSettings.apk
Quickoffice_AMAZON_4.1.408_VC.apk
Settings.apk
SettingsProvider.apk
SystemUI.apk
TtsService.apk
UserDictionaryProvider.apk
VisualizationWallpapers.apk
VpnServices.apk
Windowshop.apk
air_runtime.apk
amazonmp3-unsigned.apk
com.amazon.dcp.apk
oem_install_flash_player_signed.apk
Superuser.apk
Vending.apk
$
agree - but it's an indication that his device is not rooted
i would suggest to install superoneclick to the computer and root again
all you need is here : http://forum.xda-developers.com/showpost.php?p=19789892&postcount=35
pitrsonek said:
Is ther somebody who can help me online on gtalk? I will pay you by PayPal. If anybody has freetime send me PM. THX
$
Click to expand...
Click to collapse
Maybe on Thursday I can. Busy until then.
I just run SuperOneClick and there is log http://jsfiddle.net/tVnDv/ from this program.
Kindle Fire is Back
Jupiiie Kindle Fire is back.
So first i try SuperOneClikck install root, but this code doesnt go:
adb shell
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
chmod 755 /system/app
Then i tried unroot and this code go?
How my Kindle Fire start ,-) Its crazy but true.
Thank you very much guys...
glad to help ...
pitrsonek said:
Jupiiie Kindle Fire is back.
So first i try SuperOneClikck install root, but this code doesnt go:
adb shell
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
chmod 755 /system/app
Then i tried unroot and this code go?
How my Kindle Fire start ,-) Its crazy but true.
Thank you very much guys...
Click to expand...
Click to collapse
I'm having the same issue, but when I go to change the mount permissions I get permission denied. Anyone care to give me some insight on how to fix it?
you have the $ prompt !!!
type su - the prompt has to change to #
then do the commands ...
I'm trying to push some shared libraries to the /system/lib folder but this is what I get;
[email protected]:~/Downloads/openni_binary$ adb devices
List of devices attached
365426350c09263 device
[email protected]:~/Downloads/openni_binary$ adb shell
$ su
# mount -o remount rw /system
# exit
$ exit
[email protected]:~/Downloads/openni_binary$ adb push system/lib/libOpenNI.so /system/lib
failed to copy 'system/lib/libOpenNI.so' to '/system/lib/libOpenNI.so': Permission denied
how can I get acces to push files to that folder?
By the way: adb push=copy? can I copy .os files into the /system/lib folder using root explorer?
Thanks in advance
Sent from my A500 using XDA Premium HD app
N.Miranda said:
Well, I need to push some libraries via adb, but I can't remount the /system folder with rw permisions, it appear the next message
$mount -o remount rw /system
mount: Operation not allowed
Click to expand...
Click to collapse
Based on the prompt ($) that does not look like a root shell, a regular user is not allowed to do that. You must have root shell or use sudo.
N.Miranda said:
Should I have to create a new rule file to use the adb?
Click to expand...
Click to collapse
Based on what you have written you are already connected usign adb, so I don't really understand the question.
eppeP said:
Based on the prompt ($) that does not look like a root shell, a regular user is not allowed to do that. You must have root shell or use sudo.
Based on what you have written you are already connected usign adb, so I don't really understand the question.
Click to expand...
Click to collapse
ok this is my problem:
[email protected]:~/Downloads/openni_binary$ adb push system/lib/libOpenNI.so /system/lib
failed to copy 'system/lib/libOpenNI.so' to '/system/lib/libOpenNI.so': Permission denied
how can I set the /system folder to rw?
N.Miranda said:
ok this is my problem:
[email protected]iranda-HP-Mini-110-3700:~/Downloads/openni_binary$ adb push system/lib/libOpenNI.so /system/lib
failed to copy 'system/lib/libOpenNI.so' to '/system/lib/libOpenNI.so': Permission denied
how can I set the /system folder to rw?
Click to expand...
Click to collapse
It might help to know what rom you have installed..
It seems you either have a fully rooted rom where deliberately is not root by default (run 'adb root' then all subsequent adb commands will run as root until you reboot the tab)
Or (more likely as those instructions are likely in the op of any such rom) a rooted stock rom where adb can't be root because it was not unlocked in the ramdisk (except you can call su. Once you connect)
Regardless
run: adb root
If it is successful to push a file to system:
>run 'adb remount' to remount system to read write if its not already
>run 'adb push <local file> /system/<system file>
If it fails: we need to manually move it to system
>run 'adb push <local file> /data/local/tmp/<filename>'
>run 'adb shell's
>run 'mount -o remount,rw /system /system'
>run 'cat /data/local/tmp/<filename> > /system/<system file>'
>run 'rm /data/local/temporary/<filename>'
If busybox is installed busybox mv can be used to transfer the file to system rather than cat/rm.. busybox also has the cp command unlike true stock android. And the busybox mount will assume remount only needs a target and not a for show source as well.
It ought to be noted the adb commands are system independent.
SOLVED! I changed the permissions of the /system/lib folder with Root Explorer and then push the files using adb push ;-)
Sent from my A500 using XDA Premium HD app