Tried just about everything. I have root so I don't see the problem.
Just noticed that in ADB shell when trying to run the "su" command it doesn't even do anything.
Related
well one my friend have problem with his HTC Tattoo while he was trying to delete a font from font folder he accidentally deleted the FONT FOLDER now his phone is not working...
is there anyway to fix this problem ?
I suppose that usb connection works, so he can push them to device via adb.
Here is the fonts folder.
Or he can use Android commander: http://forum.xda-developers.com/showthread.php?t=628138 to push them in system with an easier way.
can u pls explain how i can do it via ADB ?
Sorry, I'm not a linux expert and I don't know exactly which commands you must give. For this I suggested Android commander, cause you can drag & drop the folder to device's system folder like you do in windows file explorer.
You can also push the folder along with files with the Android SDK... It's easier as it is GUI based...
rre_za said:
can u pls explain how i can do it via ADB ?
Click to expand...
Click to collapse
1. Unpack the zip file into a folder
2. Connect Tattoo via USB, start recovery, open a terminal and type adb start-server
3. cd into the fontfolder: cd fontfolder
3. PATH\TO\adb push . /system/fonts (please note the DOT!!!! sign)
You're done.
What prob with my tattoo?
I used root1click tool
And I installed Enable Market >>>>> My phone's rooted
but when I try to push font in /system/fonts
ADB say : Permission Denied
Please Help
You need to remount the filesystem with the read-write permission.
Before typing "PATH\TO\adb push . /system/fonts" you need to execute "PATH\TO\adb remount"
I tried
adb remount
adb say:
remount failed: operation not permitted
what prob?
If you type
adb shell
Do you see a # or a $ ? (if you see a $ something has gone wrong with the root)
I believe you cannot remount via adb with stock (didn't try)...install Root Explorer and then try to remount from phone side (there is a button on the upper side saying: Mount RW)
Else do it manually and open adb shell and type:
1. su
2. insmod /data/local/bin/tattoo-hack.ko
3. mount -o rw,remount /dev/block/mtdblock5 /data
4. mount -o rw,remount /dev/block/mtdblock3 /system
Hi,
I have rooted Nexus One which runs on GingerBread. I can open 'adb shell' and then execute 'su' there.
But when I try to 'adb remount', it fails.
Code:
$ adb root
adbd cannot run as root in production builds
$ adb remount
remount failed: Operation not permitted
Basically, I want to copy a file from my Desktop (MacOSX) to /system/bin on the device, is there anyway to do that on my Nexus One?
You rooted a stock OS - it doesn't have insecure boot, so ADB doesn't allow remount and other root commands.
hap497 said:
Hi,
I have rooted Nexus One which runs on GingerBread. I can open 'adb shell' and then execute 'su' there.
But when I try to 'adb remount', it fails.
Code:
$ adb root
adbd cannot run as root in production builds
$ adb remount
remount failed: Operation not permitted
Basically, I want to copy a file from my Desktop (MacOSX) to /system/bin on the device, is there anyway to do that on my Nexus One?
Click to expand...
Click to collapse
It seems like you are trying a bunch of things without reading beforehand, and understanding what you are doing. As has been said to you before, you cannot use the adb remount command with a secure boot image. If you want read/write access to the /system partition, you need to do the following:
adb shell
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
Now you have read/write access to the /system partition. No you can copy files from your sdcard to the system partition if you want. When you are finished with whatever you have to do, don't forget to issue the following command:
mount -o remount,ro -t yaffs2 /dev/block/mtdblock3 /system
There you have it. However, if you would have read a bit, instead of starting a new thread for each question you had, you would already have found what to do...
I have a v6 stock phone, no root, no cwm. Thought I would run through the ADB manual method of root to see what happens. I get to this point...
Code:
>adb devices (verifies you are connected)
>adb push rageagainstthecage-arm5.bin /data/local/temp/rage
(if the above command fails due to read-only, type 'adb usb' then 'adb root' to validate root status, then 'adb devices' again to verify connection)
>adb push su /data/local/temp/su
>adb shell chmod 777 /data/local/temp/rage
>adb shell ./data/local/temp/rage
When I try to do the SU because I get the $ I get Permissions denied.
I know that this method does not work but I wanted to see where it fails. It appears that they may have fixed the glitch that allowed the rage exploit to work.
I also tried cubes other way and it failed as well.
Code:
Open ADB shell
Your command prompt should be "$"
Run
kill `busybox pidof adbd`
Re-run ADB shell, your command prompt should change to "#"
Just thought I would toss this out there in case someone wanted to know...
Thanks for the heads up on this good info to know when I get my rev on Saturday
Sent from my SHIFTAO5P using XDA Premium App
Haxcid said:
I have a v6 stock phone, no root, no cwm. Thought I would run through the ADB manual method of root to see what happens. I get to this point...
Just thought I would toss this out there in case someone wanted to know...
Click to expand...
Click to collapse
Mm, I went through that last night, then downgraded to the V4 software as shown by the other post - still, none of it worked for me.
Pull your SDcard out when trying to root after the downgrade. Or format the SD card. It should work then.
Hi,
my ADB doesn't work correctly. I plug the phone into the pc with USB Debugging enabled (stock V20m 2.3.4) and run adb.
I can type su and the phone shows shell was given su rights, so the connection must be ok.
But I can't give any command. When I type in adb remount it says permission denied. The same problem with any other command like adb pull /system/app/Camera.apk
Everytime comes permission denied.
What can I do? Please help me.
You're running a kernel which doesn't enable the adb remount option (or rather default.prop in the ramdisk doesn't). To get around it:
Code:
adb shell
su
mount -o remount,rw /dev/block/mmcblk0p1 /system
...this basically does the same thing. There may be something else wrong though, as pulling an app from /system/app should work without it.
EDIT: Make sure you're not in the adb shell when running adb commands. Pull and push commands for example must be run in the computer-shell, not the adb shell.
Thank you very much!
TrymHansen said:
EDIT: Make sure you're not in the adb shell when running adb commands. Pull and push commands for example must be run in the computer-shell, not the adb shell.
Click to expand...
Click to collapse
That was the solution for the problem with pull/push files.
I have searched but haven't been able to find a solution to my problem.
I am on the latest CM9 nightly and I have installed ADB on my Windows 7 64bit computer and it seems to be working but when I try and use the 'push' command, I get this "C:\android-sdk-windows\platform-tools>adb push Trebuchet.apk /system/app
failed to copy 'Trebuchet.apk' to '/system/app/Trebuchet.apk' : Read-only file system"
I have tried the 'Remount' command, but that just throws back "Remount failed: Operation not permitted"
Any help is much appreciated.
You need to change permissions on the system folder
C:\android-sdk-windows\platform-tools>adb remount
then
C:\android-sdk-windows\platform-tools>adb push Trebuchet.apk /system/app
Didn't see that you had tried this !!
if you have root explorer or such navigate to system directory and change permissions to r/w...
otherwise...
adb shell
su
#mount -o rw,remount /dev/block/mtdblock3
Thank you for the help, however it still isn't working. I used the commands;
adb shell
su
#mount -o rw,remount /dev/block/mtdblock3
and it didn't throw me an error, but then when I tried to push the Trebuchet.apk it says the say as before. "failed to copy 'Trebuchet.apk' to '/system/app/Trebuchet.apk' : Read-only file system" "
Try
adb root
It could also be your version of busybox...
running out of ideas but one more...
Actually try this reboot into recovery (I presume you have some type installed), if you have an option to 'mount system' select it and then push the file...
Sent using my fingers and some technology from my HD2
Thank for your help! In the end it was my bad.
I didn't realise that on CM9 nightlies you have to go to Settings > Developer Options > Root Access > Apps and ADB.
Bling