adb remount, need root? - Desire General

I don't know if this is the place to ask, I guess so. If not, move this, and sorry.
I'm trying to adb push an app to my Desire and after adb remount I get a message: remount failed: operation not permitted.
Do I need a rooted phone to do this?
I am trying to install/push an apk file since it can't be installed any other way... don't ask me why, I'm kinda noob
I got Failure [INSTALL-PARSE-FAILED-NO-CERTIFICATES] so I'm trying
Adb remount
Adb push xxx.apk /system/app
Thanks.
EDIT: Already know... I need root.

Are you in Recovery?
You can't remount system as read/write while running Android, it has to be done in Recovery.

Rudolfje said:
Are you in Recovery?
You can't remount system as read/write while running Android, it has to be done in Recovery.
Click to expand...
Click to collapse
thanks.. was trying to do basically the exact same thing.. <3 you and google! =]

Related

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.

[Q] ADB PUSH : Permission Denied (AlphaRevX Rooted)

Hi Guys,
I have rooted my Wildfire with AlphaRevX long time back and i tried many different ROMs.
Currently i have installed JokerDroid4.2 ROM.
When i start adb shell its going to normal user($) but not root(#) and when i type su in the shell its going to root(#).
So, when i want to push files to /system/app using adb push its throwing exception of permission denied.
I have seen many threads regarding this problem but couldnot find proper answer to my problem.
Workaround im using is pusing my files to /data/local and after getting root access using adb shell and su im moving it to /system/app
(OfCourse throughout the process /system is mounted as re-write)
Please solve my problem..
EDIT : I allowed the superuser to give permission to adb shell when i typed su command but when i use adb push its not asking me for permission from superuser.
Thanks,
Sandeep
You need to set permision /rw ,to system folder via root explore,then do adb push
bittu4u4ever said:
Hi Guys,
I have rooted my Wildfire with AlphaRevX long time back and i tried many different ROMs.
Currently i have installed JokerDroid4.2 ROM.
When i start adb shell its going to normal user($) but not root(#) and when i type su in the shell its going to root(#).
So, when i want to push files to /system/app using adb push its throwing exception of permission denied.
I have seen many threads regarding this problem but couldnot find proper answer to my problem.
Workaround im using is pusing my files to /data/local and after getting root access using adb shell and su im moving it to /system/app
(OfCourse throughout the process /system is mounted as re-write)
Please solve my problem..
EDIT : I allowed the superuser to give permission to adb shell when i typed su command but when i use adb push its not asking me for permission from superuser.
Thanks,
Sandeep
Click to expand...
Click to collapse
Sent from my Wildfire using XDA App
luxandroid said:
You need to set permision /rw ,to system folder via root explore,then do adb push
Sent from my Wildfire using XDA App
Click to expand...
Click to collapse
(OfCourse throughout the process /system is mounted as re-write)
Click to expand...
Click to collapse
As mentioned in my question i hav permission of rw(read-write) already throught the process..
I am using hell fire,pushed or pulled files but not as root user,just went to my tools folder where adb is and did adb push,try like that...
Sent from my Wildfire using XDA App
Have you already tried "adb remount"?
cobje said:
Have you already tried "adb remount"?
Click to expand...
Click to collapse
This should indeed solve all your problems. Just type that command, wait for the "remount succeeded" notification and than try to write in your system folders.
The reason is that your /system is not mounted as read/write (r/w) when you boot your phone, but as read-only (r/o). So afther the remount command /systemfiles will stay r/w, but when you reboot your phone, it will return r/o again.
Erwin

[Q] adb remount

Rooted with this method completely stock kernel...
Ok I am new to Samsung but not new to rooting and using adb. I have been searching and maybe I missed something but I can not get adb working properly on my phone and pc. adb remount does not work so I can not push any files over. I have tried all the methods with mount -o rw,remount -t yaffs2 ... etc...
I can get su permissions on the phone but it will not allow me to transfer any files over at all. I even tried to r/w permission with Root Explorer while connected to phone through cmd window and nada. I am not running CWM so I would like to push files over if I can. I have done it the root explorer way of copy and paste its just that way seems so sloppy to me.
Any help would be appreciated since I cant seem to find a method on the web that works for me
Thanks guys
How are you typing the push command? Remember there are 2 sdcards on this phone.
For the internal sdcard
Code:
adb push c:\this\place /sdcard
for the external sdcard
Code:
adb push c:\this\place /sdcard/external_sd
You *shouldn't* have to use mnt/sdcard/external_sd but give it a shot just to be sure.
Doesn't this phone have to be on for ADB to work? I thought I read that. Obviously that seems a bit odd since most have to be in recovery. Or am I wrong about the on part?
Lastly, if you can run 'adb shell' then use the 'cp' or 'mv' commands to get the files on there.
EDIT: Ok, I completely just misread your post. You're trying to write to the /system? Try mount -o remount,rw /system
I don't know why everyone uses the yaffs, mmcblk, and all the other craziness. You still mount /system just with more typing. Let me know if it works.
KCRic said:
How are you typing the push command? Remember there are 2 sdcards on this phone.
For the internal sdcard
Code:
adb push c:\this\place /sdcard
for the external sdcard
Code:
adb push c:\this\place /sdcard/external_sd
You *shouldn't* have to use mnt/sdcard/external_sd but give it a shot just to be sure.
Doesn't this phone have to be on for ADB to work? I thought I read that. Obviously that seems a bit odd since most have to be in recovery. Or am I wrong about the on part?
Lastly, if you can run 'adb shell' then use the 'cp' or 'mv' commands to get the files on there.
Click to expand...
Click to collapse
tried cp and mv still gave me problems moving file. I forget the error message I got. Also I know the proper push commands I used to do it with my Evo all the time. Its just that this phone wont let me mount system. What do you mean be on ADB?
playya said:
tried cp and mv still gave me problems moving file. I forget the error message I got. Also I know the proper push commands I used to do it with my Evo all the time. Its just that this phone wont let me mount system. What do you mean be on ADB?
Click to expand...
Click to collapse
I meant the phone needs to be on (with debugging selected) in order to use ADB and write to it. At least that's what I think I remember seeing. Could be wrong since I haven't used ADB with this phone yet.
KCRic said:
I meant the phone needs to be on (with debugging selected) in order to use ADB and write to it. At least that's what I think I remember seeing. Could be wrong since I haven't used ADB with this phone yet.
Click to expand...
Click to collapse
correct all that has been done... all the basics you can think of have been done but it just keeps failing on adb remount
adb shell
$ su
#
no problem now, at first yes but I still cant mount system... driving me nuts since I dont use Clockwork right now I want to push files over... and my software on my pc AndroidCommander says NORoot has been obtained....
I'm probably as new to this phone as you are. Mostly just dealt with HTC. Past this point I have no idea what's going on. I can write to my /system - no problem. Hopefully one of the more seasoned guys will jump in here soon. Sorry I'm not much more of a help.
KCRic said:
I'm probably as new to this phone as you are. Mostly just dealt with HTC. Past this point I have no idea what's going on. I can write to my /system - no problem. Hopefully one of the more seasoned guys will jump in here soon. Sorry I'm not much more of a help.
Click to expand...
Click to collapse
what method did you use to root with... Is it the same as what I used the deoxeded stock method I posted above
Did u try with the Odin method? way easier.
Sent from my Galaxy SII √Epic4G Touch
skykc0401 said:
Did u try with the Odin method? way easier.
Sent from my Galaxy SII √Epic4G Touch
Click to expand...
Click to collapse
Odin method to do what? root? If so that is how I rooted thanks
I downloaded an app on the market that fix it.. thanks guys

[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

Categories

Resources