Develop Bugs

HELP: I can't push files using ADB!

First, I'm not rooted. I don't need root to push files using ADB though. I'm trying to push a file to "system/app" using ADB but I keep getting "permission denied". I've read countless threads and still cant get it.
I can get everything started,
F:\Android SDK\tools\
F: adb devices
Than it list my devices. Than I type in
F:adb shell and I get a "$" sign.
Anything I type after that I get permission denied.
I tried adb push [insert file here] /system/app I get
"ADB: Permission Denied."
I tried adb remount, I get 'ADB: Permission Denied"
Here is my log:
F:\>adb devices
List of devices attached
HT05CHL02486 device
F:\>adb shell
$ adb push f:\smoothcalendar.apk /system/app
adb push f:\smoothcalendar.apk /system/app
adb: permission denied
$ adb push f:\smoothcalendar.apk \system\app
adb push f:\smoothcalendar.apk \system\app
adb: permission denied
$ adb push f:\smooothcalendar.apk
adb push f:\smooothcalendar.apk
adb: permission denied
$
Click to expand...
Click to collapse
F:\>adb devices
List of devices attached
HT05CHL02486 device
F:\>adb shell
$ adb remount
adb remount
adb: permission denied
$ adb mount
adb mount
adb: permission denied
$ adb devices
adb: permission denied
$
Click to expand...
Click to collapse
Any help

You need full root (root and NAND unlock) to remount /system as rw instead of ro, and therefore write to it.
--Swyped from my EVO using XDA App.

Nice profile pic, though.

I've read that I don't need to be rooted (full rooted) to push a file to my phone, so I gather I do? Is there a root for 2.2 Evo?

Raadius said:
I've read that I don't need to be rooted (full rooted) to push a file to my phone, so I gather I do? Is there a root for 2.2 Evo?
Click to expand...
Click to collapse
Why don't you try reading what I said? You need full root to make /system writable. You can push to /data all you wasn't without root, but not /system. And try using the search, there IS NO WAY TO ROOT THE 2.2 OTA. This is karma for you not searching, reading, and being so compulsive that you just HAD to accept the OTA that everyone warned CANNOT be rooted and WILL break your root.
--Swyped from my EVO using XDA App.

"Cannot be rooted YET." Toast got all up on me for not making that clear in my thread.
http://forum.xda-developers.com/showthread.php?t=747495
And didn't you get the exact same answer in your other thread about accessing /system? I was wondering how you got such a high post count without knowing some general knowledge like this. The old multiple thread trick.

drmacinyasha said:
Why don't you try reading what I said? You need full root to make /system writable. You can push to /data all you wasn't without root, but not /system. And try using the search, there IS NO WAY TO ROOT THE 2.2 OTA. This is karma for you not searching, reading, and being so compulsive that you just HAD to accept the OTA that everyone warned CANNOT be rooted and WILL break your root.
--Swyped from my EVO using XDA App.
Click to expand...
Click to collapse
Wow. Someone's having a bad day. Is it really that hard for people to just give a simple answer without flaming the hell out of everyone? He did say that he "READ" that he didn't need root to push files, which you clarified in a pretty hostile manner. If you're gonna get pissed off everytime you read a post you don't like, why bother even being on this forum. I get tired of seeing questions that have been answered a million times but I'm not gonna go frickin postal on someone. Be mature and ignore it. Oh, and its IMPULSIVE, not COMPULSIVE!
[EDIT] Guess I'm kinda doin the same thing.
Sent from my FROYO'D EVO using xda app

drmacinyasha said:
Why don't you try reading what I said? You need full root to make /system writable. You can push to /data all you wasn't without root, but not /system. And try using the search, there IS NO WAY TO ROOT THE 2.2 OTA. This is karma for you not searching, reading, and being so compulsive that you just HAD to accept the OTA that everyone warned CANNOT be rooted and WILL break your root.
--Swyped from my EVO using XDA App.
Click to expand...
Click to collapse
No, I didn't read what you said, on purpose. I posted my reply on purpose to piss you off. I know there isn't root access for 2.2 but I asked on purpose just so you can secrete your panties. Happy? Now go fall off a cliff.

drmacinyasha said:
You need full root (root and NAND unlock) to remount /system as rw instead of ro, and therefore write to it.
--Swyped from my EVO using XDA App.
Click to expand...
Click to collapse
i've rooted my x8 but i still get "permision denied" while pushing file to system via adb,and i dont get confirmation screen to allow accessing system in superuser permision,any idea?

alharun said:
i've rooted my x8 but i still get "permision denied" while pushing file to system via adb,and i dont get confirmation screen to allow accessing system in superuser permision,any idea?
Click to expand...
Click to collapse
Maybe try posting in the forum for your device and not resurrect a dead thread for the wrong device?
Welcome to XDA.

Quick ADB Question

I have ADB installed and working, just really new to it. Can someone help me understand how to:
Mount /system as r/w with root explorer.
Really appreciate it.

If you're using Root Explorer you don't need adb to write to system. Just navigate to system and press the r/w button on the top right of the screen. What are you trying to do in system?
Sent from my FROYO'D EVO using xda app

If you have root
Code:
adb remount
adb shell
I hope that is what you are asking for. Not really clear.
(This is for removing apps with adb)

Thanks for the responses. I was a little confused. I am trying to do the 2.2 dialing fix and transfer the old espt onto my phone so I can do manual prl updates.

rafroehlich2 said:
If you have root
Code:
adb remount
adb shell
I hope that is what you are asking for. Not really clear.
(This is for removing apps with adb)
Click to expand...
Click to collapse
this doesnt work always and if it doesnt, this most definitely does
Code:
adb shell
mount /dev/block/mtdblock4 /system
cd /system/app

t3project said:
this doesnt work always and if it doesnt, this most definitely does
Code:
adb shell
mount /dev/block/mtdblock4 /system
cd /system/app
Click to expand...
Click to collapse
Got it working. Appreciate it everyone.

[MOD] 3-Click QuickTempRoot TerminalMOD :/

Alright all,
I know there's another thread about "easier" method, but this is easiest for me. 3-Clicks after installation.
I was really tired of typing the same crap over and over after rebooting just to get my temproot back to do more testing/playing.
So I redeveloped this to be quicker/easier upon reboot. Mainly I altered the Term app to be have a scripted start-up on the 1st 3 launches.
I also updated the su/Superuser combo with ChainDD's latest stuff.
Here's how it works, after it's installed.
3ClickTempRooter said:
1) You run the terminal app once, wait a few seconds and it disappears.
2) You run the terminal again, wait for it to FC.
3) You run the terminal a final time and receive root.
Click to expand...
Click to collapse
Now on each reboot, it will be simply 3-clicks (running terminal app 3 times).
Finally ... any executable script placed in /data/local/tmp will be in the path of the new terminal mod. This makes running other scripts very easy.
Installation
Download the attached QuickTempRooter.zip and place it in a directory and unpack it.
Turn on USB debugging and install through adb ...
Here's the adb installation snippet ...
Code:
adb kill-server
adb push su /sdcard/su
adb push Superuser.apk /sdcard/Superuser.apk
adb push busybox /data/local/tmp/busybox
adb push rage /data/local/tmp/rage
adb push root /data/local/tmp/root
adb shell chmod 0755 /data/local/tmp/busybox
adb shell chmod 0755 /data/local/tmp/rage
adb shell chmod 0755 /data/local/tmp/root
adb shell 'pm uninstall com.android.term'
adb install Term.apk
Has made my life wayyy easier when playing with this phone while we wait for the real-deal!!!
Hope you enjoy!
NOTES
If you get a permission denied on the ''adb shell 'pm uninstall com.android.term' '' ... this is normal if you don't have a terminal already installed or have an alternate terminal app (using a namespace other than com.android.term.
If you have another Terminal App installed, you may want to uninstall it first, to avoid confusion.
Also, you may need to reboot after the initial installation for it to work properly!

ummmmm.....Enomther??
Did you get a G2 already?
Great to see you helping out with this

Great to see you here man! Trying this now can't wait to get themes rolling once we get permanent root!
Sent from my T-Mobile G2 using XDA App

I get a permission denied response when running "adb shell 'pm uninstall com.android.term'"

burton14e7 said:
I get a permission denied response when running "adb shell 'pm uninstall com.android.term'"
Click to expand...
Click to collapse
If you didn't already have a terminal app installed that error is normal. Also you may need to reboot once after the initial installation for it to work properly.
~enom~

Thank you sir. Appreciate the goodness.

damn i wish i could hit the thanks button

Thanks man good to have you on the G2 too
Sent from my T-Mobile G2

enomther said:
If you didn't already have a terminal app installed that error is normal. Also you may need to reboot once after the initial installation for it to work properly.
~enom~
Click to expand...
Click to collapse
good to see you on this side.... i have terminal app installed rebooted but still get this denied when running adb shell 'pm uninstall com.android.term
Edit: fixed it uninstalled the Android Terminal E,ulator and just ran the setup now have root thanks

Thank You..
Enom.. (sigh)
Welcome Home..

thank u so much now i can wireless tether. easiest root ever

Sorry, this is my first Android. I came from WM and I was pretty good with it.
I've searched XDA, Youtube, and web to ADB and SDK. I've downloaded it and it's installed. The only thing I don't get is when you said to
"Download the attached QuickTempRooter.zip and place it in a directory and unpack it."
You mean place the extracted files into the sd card correct? That's why the command is "adb push su /sdcard/su".

ddgarcia05 said:
Sorry, this is my first Android. I came from WM and I was pretty good with it.
I've searched XDA, Youtube, and web to ADB and SDK. I've downloaded it and it's installed. The only thing I don't get is when you said to
"Download the attached QuickTempRooter.zip and place it in a directory and unpack it."
You mean place the extracted files into the sd card correct? That's why the command is "adb push su /sdcard/su".
Click to expand...
Click to collapse
No, he means on your PC. You are running adb to push files contained in the zip to your phone.

HamNCheese said:
No, he means on your PC. You are running adb to push files contained in the zip to your phone.
Click to expand...
Click to collapse
So they go into the tools folder? Damn. I think I've in over my head here.
Like this?

If you have better terminal, you can also add the rage and root to specific keys.

At this command I'm getting told "failed to copy 'su' to '/sdcard/su': Read-only file system"
adb push su /sdcard/su

kevdawg said:
At this command I'm getting told "failed to copy 'su' to '/sdcard/su': Read-only file system"
adb push su /sdcard/su
Click to expand...
Click to collapse
Unplug then plug ur phone back in then try again also make sure u are in usb debug mode

Good work, Temp root in like 5 seconds

Quick question, ok I was able to get root for a few mins, then it went away I guess I have to have the terminal always open or ignore so my taskiller doesnt terminated it?

Don't use task killers. (IMHO)
But I tend to have to reboot every once in a while to keep root in tacked within terminal but all my apps seem to stay with su permissions until reboot (or sometimes 12 hours)

[Q] Permission denied to push vending.apk

Last night I tried to root a Fire (6.3.1) for the first time using KFU and briefly saw something flash by about a problem with check_rooted. Someone on the KFU thread mentioned this also. Does this mean the rooting process is incomplete?
Proceeding further, I attempted to install the optional apps and received permission denied errors when abd went to push the vending GoogleCalendarSyncAdapter and GoogleContactsSyncAdapter apk files to /system/app.
Reading further on the KFU thread, someone else suggested sideloading superuser. I did this and still was unable to manually push the files (following the batch file as a model to mount read/write, push the apps, then mount read-only).
The goal was to add access to Google Play to an otherwise stock 6.3.1 operating system. Short of loading a new rom, is there something else I might try?

SLOmtb said:
Last night I tried to root a Fire (6.3.1) for the first time using KFU and briefly saw something flash by about a problem with check_rooted. Someone on the KFU thread mentioned this also. Does this mean the rooting process is incomplete?
This is typically nothing to worry about. You will receive an error if the "check_rooted" folder didn't exist to begin with. Normal
Proceeding further, I attempted to install the optional apps and received permission denied errors when abd went to push the vending GoogleCalendarSyncAdapter and GoogleContactsSyncAdapter apk files to /system/app.
Reading further on the KFU thread, someone else suggested sideloading superuser. I did this and still was unable to manually push the files (following the batch file as a model to mount read/write, push the apps, then mount read-only).
Click to expand...
Click to collapse
The method for doing this is
Code:
adb root
adb remount
adb push ≤filename1≥ /system/app
adb push ≤filename2≥ /system/app
...when finished...
Code:
adb remount
adb kill-server
The goal was to add access to Google Play to an otherwise stock 6.3.1 operating system. Short of loading a new rom, is there something else I might try?
Click to expand...
Click to collapse
To make things simple, the MoDaCo rom has the exact same interface as stock, except it comes pre rooted with all of the Google apps and services already installed. No work is necessary.

Wow! I'll give it a try tonight. Thanks!

soupmagnet said:
The method for doing this is
Code:
adb root
adb remount
adb push ≤filename1≥ /system/app
adb push ≤filename2≥ /system/app
...when finished...
Code:
adb remount
adb kill-server
To make things simple, the MoDaCo rom has the exact same interface as stock, except it comes pre rooted with all of the Google apps and services already installed. No work is necessary.
Click to expand...
Click to collapse
Well, darn. I tried "adb root" and it says: "adbd cannot run as root in production builds." So I guess it isn't really rooted, after all.
Maybe the MoDaCo rom is the way to go, after all. Thanks, anyway!

adb devices
list of device attached
5A5A5A5A5A5A..... (NOT CORRECT)
adb shell
[email protected]
adb push flash_image /dev/
failed .... permission denied
adb push recovery.img /dev/
failed .... permission denied
what should I do ?

sabithpkcmnr said:
adb devices
list of device attached
5A5A5A5A5A5A..... (NOT CORRECT)
adb shell
[email protected]
adb push flash_image /dev/
failed .... permission denied
adb push recovery.img /dev/
failed .... permission denied
what should I do ?
Click to expand...
Click to collapse
The which system version?
Sent from my XT894 using Tapatalk

sd_shadow said:
The which system version?
Sent from my XT894 using Tapatalk
Click to expand...
Click to collapse
Thanks for interesting ,,
I am on leave for many days over my exam fear ..
any way , I am having Android 4.1.1 JB tablet

sabithpkcmnr said:
Thanks for interesting ,,
I am on leave for many days over my exam fear ..
any way , I am having Android 4.1.1 JB tablet
Click to expand...
Click to collapse
That's Android version, not system version
Sent from my XT907 using Tapatalk

[Q] Copying files to /system | S-ON | HTC One X

I have rooted my HTC One X and want to copy files in /system/xbin folder. My phone shows S-ON. And Eclipse is not able to copy files to /system and adb push from shell is also not working. Is there a way I can copy files to /system/xbin?
I am running stock ROM.
My phone is NOT associated with any vendor.

adb remount
adb push filename /system/xbin
Sent from my HTC One X

You can also use es file explorer and go into the options tick up to root and the request root and then tick mount as r/w.
Then just move files as you will.
Sent from my HTC One X using XDA Premium HD app

realunited123 said:
adb remount
adb push filename /system/xbin
Sent from my HTC One X
Click to expand...
Click to collapse
The above way does not seem to work. Whenever I use adb remount(or adb mount) it says operation not permitted and I am trying to this from root privileges
My OS is :- Ubuntu 12.04
ADB(platform-tools) -> Rev 20
If you need anything more please ask me .

Additional Question
treebill said:
You can also use es file explorer and go into the options tick up to root and the request root and then tick mount as r/w.
Then just move files as you will.
Sent from my HTC One X using XDA Premium HD app
Click to expand...
Click to collapse
First of all thanx it worked. I think I will have to live with this way A ADB/Eclipse based would have been cool
Will the files moved from SDcard to phones root in anyway lose and privileges(like losing executable)? If yes, please suggest a way to restore it.

KillerTheLord said:
The above way does not seem to work. Whenever I use adb remount(or adb mount) it says operation not permitted and I am trying to this from root privileges
My OS is :- Ubuntu 12.04
ADB(platform-tools) -> Rev 20
If you need anything more please ask me .
Click to expand...
Click to collapse
When doing adb shell su do you get any toast notification on your phone? Or does it just say denied ?
Strange it works perfectly here Also are you using SuperSU or any other superuser app?
---------- Post added at 03:37 PM ---------- Previous post was at 03:36 PM ----------
KillerTheLord said:
First of all thanx it worked. I think I will have to live with this way A ADB/Eclipse based would have been cool
Will the files moved from SDcard to phones root in anyway lose and privileges(like losing executable)? If yes, please suggest a way to restore it.
Click to expand...
Click to collapse
Yes you need to change the permissions after moving from sdcard. Use Root Explorer(Long press on the file--> Change permissions)

realunited123 said:
When doing adb shell su do you get any toast notification on your phone? Or does it just say denied ?
Strange it works perfectly here Also are you using SuperSU or any other superuser app?
---------- Post added at 03:37 PM ---------- Previous post was at 03:36 PM ----------
Yes you need to change the permissions after moving from sdcard. Use Root Explorer(Long press on the file--> Change permissions)
Click to expand...
Click to collapse
I am using SuperSU as Super User App. And I think I am doing something wrong here. You mentioned about adb shell su. I think I might be wrong here. Here is how I tried to execute the command.
[email protected]: <path to platformtools> ./adb remount
remount failed: Operation not permitted
do I have to raise ADB shell to SU level. If yes, how?

KillerTheLord said:
I am using SuperSU as Super User App. And I think I am doing something wrong here. You mentioned about adb shell su. I think I might be wrong here. Here is how I tried to execute the command.
[email protected]: <path to platformtools> ./adb remount
remount failed: Operation not permitted
do I have to raise ADB shell to SU level. If yes, how?
Click to expand...
Click to collapse
Strange. Are you using the stock kernel ? If that is the case then it does not have insecure adbd (ro.secure=0) so remount will not work. Try a custom kernel.
Does adb has SU permissions from recovery ? Try booting into recovery, mounting the system partitions and try to push something from adb. Check the SuperSU app to update binary but that should not be a problem.

realunited123 said:
Strange. Are you using the stock kernel ? If that is the case then it does not have insecure adbd (ro.secure=0) so remount will not work. Try a custom kernel.
Does adb has SU permissions from recovery ? Try booting into recovery, mounting the system partitions and try to push something from adb. Check the SuperSU app to update binary but that should not be a problem.
Click to expand...
Click to collapse
Yes I have rooted the phone but the ROM is stock(I was thinking to put in CM9 Alpha).
About the second thing. I know how to boot my phone into recovery(Vol Down + Power -> From Screen -> Recovery(ClockwerkMod))
But about the rest I don't know.
Sorry about my annoying questions this is my first time I am dealing with rooting and stuff.

KillerTheLord said:
Yes I have rooted the phone but the ROM is stock(I was thinking to put in CM9 Alpha).
About the second thing. I know how to boot my phone into recovery(Vol Down + Power -> From Screen -> Recovery(ClockwerkMod))
But about the rest I don't know.
Sorry about my annoying questions this is my first time I am dealing with rooting and stuff.
Click to expand...
Click to collapse
I guess you are using stock kernel then. Try franco's or faux's kernel.
adb remount wont work from os on stock boot.img.
After rebooting into recovery go to mounts and storage-->mount /system and then push something from adb. See if that works.

KillerTheLord said:
Yes I have rooted the phone but the ROM is stock(I was thinking to put in CM9 Alpha).
About the second thing. I know how to boot my phone into recovery(Vol Down + Power -> From Screen -> Recovery(ClockwerkMod))
But about the rest I don't know.
Sorry about my annoying questions this is my first time I am dealing with rooting and stuff.
Click to expand...
Click to collapse
I think this app does exactly what you want :
http://forum.xda-developers.com/showthread.php?t=1687590

realunited123 said:
I guess you are using stock kernel then. Try franco's or faux's kernel.
adb remount wont work from os on stock boot.img.
After rebooting into recovery go to mounts and storage-->mount /system and then push something from adb. See if that works.
Click to expand...
Click to collapse
Well this didn't work either. I hope to switch to some other ROM in future(I hate HTC Sense ). But as of now Root Explorer did the job. I mounted my sdcard and copied files to it and used Root Explorer to move files to /system and then changed permissions.
Thanks for help it really made it easy .

make sure your path devs are oke for su.
in terminal run:
sudo su
adb kill-server
adb devices
you should see your HOX HTxxxxx nr.
and here you should be able to connect eclipse to HOX by adb.

NikMel said:
make sure your path devs are oke for su.
in terminal run:
sudo su
adb kill-server
adb devices
you should see your HOX HTxxxxx nr.
and here you should be able to connect eclipse to HOX by adb.
Click to expand...
Click to collapse
The problem was not accessing the device using ADB. The problem was I was not able to write to root system. ES Explorer and Root Explorer both did the job for me. I will be putting the final instructions for the process(detailed ones) soon.

Instructions onw how to copy files to root file system on HTC One X with S-ON
1) Unlock and Root your phone. Follow instructions below
http://www.youtube.com/watch?v=gIeq8Jx28cs
and then
http://www.youtube.com/watch?v=80lMHUgxwww
2) Install ES Explorer(File Manager) Link :- https://play.google.com/store/apps/details?id=com.estrongs.android.pop&hl=en
3) Connect device to computer(even if it is not recognized by ADB/Computer)
4) In Phone select Disk drive option. Now the phone's storage will be mounted on your computer as removable device.
5) Copy the files you want to send to phone's root system to any folder here.
6) Change phone's mode to charge only and wait for 2-3 secs(let phone remount sdcard)
7) Open ES Explorer and open menu(those 3 dots at bottom and select Settings)
8) Tick the following options
Up to Root
Root Explorer
Mount File System
9) A dialog box for permission will open Grant it.
10) Now copy files from /sdcard/<Folder where u put files> to where ever you want o copy files to.
11) Long press on file to change permissions and stuff.
Post here if you are stuck someone will surely help you.