[Q] ADB fails to copy - Xperia Tablet Z Q&A, Help & Troubleshooting

I am trying to get Chrome to come up in desktop mode permanently. Multiple sources tell me that on an un-rooted device I need to use ADB to copy a file containing the line:
chrome --user-agent="Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.1 (KHTML, like Gecko) Chrome/22.0.1207.1 Safari/537.1"
to the /data/local directory.
So I dropped that line into a file (called chrome-command-line) on the root of my c: drive and run ADB like so:
c:\Android-SDK\sdk\platform-tools>adb push /chrome-command-line /data/local/chrome-command-line
It immediately fails with the following message:
failed to copy '/chrome-command-line' to '/data/local/chrome-command-line': Permission denied
Any idea how I can perform this ADB copy operation without rooting?
Thanks!

Related

[Q] Mounting RW

I am trying to install TapNTap keyboard in Vegan Ginger. (yeah, I know but I want to anyway). I need to copy two files to /system/app and system/lib. I presently have the files stored in /mnt/sdcard/download. I have terminal emulator installed and when I su I appear to get root (prompt changes to #). I was able to create an empty directory in /. When I try to copy the file to /system/app I get a message that it is a Read-only file system. When I do an ls -l the permissions show drwxr-xr-x for the directory. The owner is root and the group is root. It would seem that as su I should be able to copy the file there. Possibly it is mounted as RO. I tried to use a remount command but it failed. I'm not well versed in that so I may have done something wrong. Long and short - how do I get the file copied into the directory?
http://lmgtfy.com/?q=remount+system+rw+android

[Q] How to I split a boot.img on my Android phone using Terminal Emulator?

Anyone knows how to split a boot.img file using Terminal Emulator directly on the phone Android system without using a PC? Or is this possible?
There is a "split_bootimg.pl" script in the forums and wiki page but whenever I run this on Terminal Emulator it gives me either "permission denied" or "not found" error... Changing permissions for the files also does not help.
Here's what I did:
1) Copy boot.img and split_bootimg.pl into a temp folder
2) Enter su (Gives me Terminal Emulator has been granted super user permissions...)
3) cd /temp folder
4) enter "./split_bootimg.pl boot.img"
5) Gives error "split_bootimg.pl: permission denied"

USB transfer workaround

For the past couple of days I have issues with transferring files over usb as no support is built into to the ics kernel for the usb transfer unless a physical sdcard is detected. I tried the mtp, thing and for some reason that wont show the files. Here is what I found that works best for transferring files rather than installing sketchy Chinese programs.
Note all commands are in quotes, do not type the quotes
Setting up and checking files in directories​
1. Install androidsdk
2. open a command prompt and cd to where your adb tools are. They are typically in C:\android-sdk-windows\platform-tools
3. "cd C:\android-sdk-windows\platform-tools" after you download the pack through the platform tools pack through the sdk manager. Yours may be in a different place depending on install. If you have set the system variable for adb skip to step 4.
4. Set your touchpad to go into android debugging mode when plugged in, under developers options
5. Type in "adb devices" to make sure your touchpad is seen by computer
6. Now access your devices by typing "adb shell" (if you have the ghost emulator 5554, use adb -d shell)
7. From there type "cd /sdcard/"
8. Type "ls" to receive a list of all files on your touchpad (note l is an L)
9. From there simply use the cd command to get in and out of directories
Transferring Files​
When you want to transfer files to and from the touchpad, open a new command prompt and get back to the location with your adb files.
To copy to touchpad
Use the adb push command, example of adb push:
"adb push C:\users\stephen\downloads\example.apk /sdcard/"
The format is adb push local directory to remote directory.
To pull from touchpad
To pull something from your touchpad use adb pull command. The format is adb pull remote directory to local directory.
Example: "adb pull /sdcard/getjar.apk c:\users\stephen\desktop"
I installed DroidSSHd for root GUI. and for GUI file transfer/install I use AirDriod.
edit: course, all this is done on the air.

[Q] How to copy rsync binary to Android PATH.

Experienced Linux user, Android noob.
I'd like to be able to use rsync to transfer files from my Linux desktop to my Sony Xperia Tablet Z and initiate the transfers from my Linux desktop.
A blog explained how to do it by first installing an SSH app, which I have done. It works fine, I can now SSH from my Linux desktop to the tablet.
Now I need to copy the rsync binary to the tablet and to make sure it's in the PATH and has "755" permissions set. Over SSH I was able to see what my PATH is, but I can't copy the rsync binary to anywhere in the PATH as I run into permission denied problems.
How do I copy the rsync binary to within my PATH and set 755 permissions? I really do not want to ROOT my device.
Thanks all.
PS. I don't want to use "rsync backup for Android" as the rsync commands can only be run from the Android device.

Minami M-750 stuck on boot - need expert help

Hi, I have been using Rom toolbox Lite for a while now and never had a problem, untill I got the "not so great" idea to change the heapsize in build.prop - after reboot the tablet is stuck on Loading - screenshot http://imageshack.com/a/img924/2306/BJbCT1.png
I have tried to reset, reset to factory default, to push back an old build.prop by ADB from prompt, tried the same from QtADB(0.8.0(newer 32bit not availble) - seems I have full access to all folders), even tried modifying the build.prop as root and start QtADB as root then copy it back - nothing has helped.
I have a complete backup(rom dump) made with uberizer, but since I'm not using windows anymore but instead Peach OSI(heavily modified Xubuntu). I'm not really sure what to do now.
My Minami M-750 DualCore A20(allwinner) tablets info is uploaded at specdevice long time ago as I were trying to find others with the same tablet:
http://specdevice.com/showspec.php?id=e5ba-9ce5-0033-c58700000000
It doesn't have custom Rom or custom recovery, but do have an option in recovery to update from external storage(where I can access internal sdcard and external sd) - update from ADB - update from cache.
Anyone have any suggestions?
With kind regards
JBJ
EDIT: Thanks to this article below the problem is now solved.
Note: Step 1 . instead of Eclipse ADT download SDK command line tools https://dl.google.com/android/android-sdk_r24.4.1-linux.tgz
Follow this guide on how to install the SDK: https://androidonlinux.wordpress.com/2013/05/12/setting-up-adb-on-linux/
Step 3. Open a Terminal and shoot this command: —–Note: The “Android” in the command is the folder in which we extracted the SDK in.
cd ~/Android/sdk/platform-tools/
Edit build.prop using ADB
by Louis Matthijssen · July 26, 2014
There are many reasons why you may like to edit your build.prop file. I always edit it in order to lower my DPI, resulting in a bigger looking screen.
You can edit it on the device itself using a file manager or a build.prop editor but it may be more convenient to edit the file using a PC.
Please note that your device has to be rooted to edit the build.prop file.
Download and unzip the Eclipse ADT
Make sure your device has USB debugging enabled
Open a command prompt or terminal and cd to the platform-tools directory:
cd C:\adt-bundle-windows\sdk\platform-tools
Check if your device is recognized:
If it’s not you may install the Google USB driver and try again
adb devices
The device may ask you if the computer is trusted, choose yes
Restart ADB as root:
adb root
Remount /system as rw (read-write):
adb remount
Download build.prop to your pc:
adb pull /system/build.prop
Now you can edit build.prop using your favorite editor
Important: use a plain text editor! I recommend Notepad++ for Windows and Geany for Linux
Upload build.prop to your device:
adb push build.prop /system/build.prop
Fix permissions:
adb shell chmod 644 /system/build.prop
Reboot your device:
adb reboot

Categories

Resources