Develop Bugs

"Not Found" error message when attempting to push file via ADB

I'm using Cyanogen Mod 6, the most recent nightly build. I want to push the Sense UI notification sounds to the android notifications folder. I attempted to do this via terminal emulator via the following:
Code:
$ adb push /sdcard/HTC_Audio_Files/notifications/Ascend.mp3 /system/media/audio/notifications.mp3
When I did that, I get a "not found" error. I was thinking I didn't have permissions, so I did:
Code:
$ su
# adb push /sdcard/HTC_Audio_Files/notifications/Ascend.mp3 /system/media/audio/notifications.mp3
I got the same error.
Then, I decided to copy the files I wanted to push into the tools folder on my computer, in the Android SDK. I did the adb devices command, and I saw my device listed. I did the same code as above, and still get the "Not Found" error. I'm sure it's something very simple that I'm missing. I made sure the directories are correct, even making sure everything was case-sensitive.

tokuzumi said:
I'm using Cyanogen Mod 6, the most recent nightly build. I want to push the Sense UI notification sounds to the android notifications folder. I attempted to do this via terminal emulator via the following:
Code:
$ adb push /sdcard/HTC_Audio_Files/notifications/Ascend.mp3 /system/media/audio/notifications.mp3
When I did that, I get a "not found" error. I was thinking I didn't have permissions, so I did:
Code:
$ su
# adb push /sdcard/HTC_Audio_Files/notifications/Ascend.mp3 /system/media/audio/notifications.mp3
I got the same error.
Then, I decided to copy the files I wanted to push into the tools folder on my computer, in the Android SDK. I did the adb devices command, and I saw my device listed. I did the same code as above, and still get the "Not Found" error. I'm sure it's something very simple that I'm missing. I made sure the directories are correct, even making sure everything was case-sensitive.
Click to expand...
Click to collapse
You're entering the wrong command(s).
Place your notification sound into your AndroidSDK\tools folder, then run:
Code:
adb push name-of-soundbite.mp3 /system/media/audio/notifications/
This will place a .mp3 called "name-of-soundbite" into your notifications folder. You then need to reboot your phone in order for it to work.

Thanks for the help. I was still having the "not found" error, after your instructions. I figured it out, though. I had to run the "adb remount" command, to make the system partition writable. After I was finished, I ran the remount command again, to make it read only.
So, for anyone who has this error later here's the code I used (I did not need to go into the adb shell to do this):
Code:
adb remount
adb push name-of-soundbyte.mp3 /system/media/audio/notifications/
adb remount

tokuzumi said:
Thanks for the help. I was still having the "not found" error, after your instructions. I figured it out, though. I had to run the "adb remount" command, to make the system partition writable. After I was finished, I ran the remount command again, to make it read only.
So, for anyone who has this error later here's the code I used (I did not need to go into the adb shell to do this):
Code:
adb remount
adb push name-of-soundbyte.mp3 /system/media/audio/notifications/
adb remount
Click to expand...
Click to collapse
Oh? I apologize, I thought you already knew to run that.

pseudoremora said:
Oh? I apologize, I thought you already knew to run that.
Click to expand...
Click to collapse
It's fine. I'm a newb/noob, so my adb skills are almost non-existant, but I when I saw the error about the system partition being readonly, that triggered something I read in the adb wiki. I found the remount code there, which paved the way for my success.

Rooting with Gfree HELP!

Okay, I'm a complete noob and I'm following these instructions (http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Rooting_the_G2) using Gfree I believe.
I finished downloading the SDK File Manager and all the .zip folders that were mentioned on the site. However, I am stuck at the first temp root step. It says I can either enter in the command via cmd window or a different terminal. I chose a cmd window because I already have that and know how to use.
I run Windows 7, so I simply type cmd in the search bar to pull up a cmd window. I then "cd desktop" and then "cd gfree_temp-root" because it says to navigate to that folder. However, when I enter in the first command, my cmd window tells me this "adb is not recognized as an internal or external command, operable program or batch file". Does anyone know what I have to do?
Also, do I have to install Eclipse and an ADT plug-in to root my phone? And is anyone available right now to chat and walk this complete noob through this????

You're fine, just make sure your android sdk with adb is in your system path, in Win7 find it in ctrl panel/sys and security/system -> advanced system settings on the left, then advanced tab, environment variables at the bottom. In there in the bottom text window, find Path, edit it, go to the end of the path line and if there isnt already add a ; to the end of the line then paste in the full path to your android sdk where adb is - for me someandroidsdkpath\platform-tools

Alright, bumping into a new problem. I found an alternative way to run adb through another guide on the forum. Downloaded adb.exe and this is what I do.
Pull up a cmd window and then cd to the folder that contains the adb.exe, and then I copied all the files that needed to be push on the wiki page that needed to be push into that same folder. Howeverr, I am getting permission denied.
I got adb to recognize my device and all, but don't understand why permission is being denied.
EDIT: While I am waiting for a reply, I went ahead and did what the previous user told me to do. Now I can use adb through my cmd window. I navigate to the window of the file but I still get permission denied. What's going on?

LGS1231 said:
Alright, bumping into a new problem. I found an alternative way to run adb through another guide on the forum. Downloaded adb.exe and this is what I do.
Pull up a cmd window and then cd to the folder that contains the adb.exe, and then I copied all the files that needed to be push on the wiki page that needed to be push into that same folder. Howeverr, I am getting permission denied.
I got adb to recognize my device and all, but don't understand why permission is being denied.
EDIT: While I am waiting for a reply, I went ahead and did what the previous user told me to do. Now I can use adb through my cmd window. I navigate to the window of the file but I still get permission denied. What's going on?
Click to expand...
Click to collapse
Hmmm, are you in adb shell running the commands? ie a $ prompt?
the prompt at the point you send the push command would look like (for Windows): c:\myrootfileshere> adb push somefiles /sdcard/wherever

No, I am in a cmd window.
This what is looks like:
C:\User\XXXX\Desktop\gfree_temp-root> adb push su /sdcard/su ... I would then get "failed to copy 'su' to '/sdcard/su': Permission denied
Even if I wanted to use adb shell, I would get this:
C:\User\XXXX\Desktop\gfree_temp-root>adb shell
$ adb push su /sdcard/su
adb: permission denied

LGS1231 said:
No, I am in a cmd window.
This what is looks like:
C:\User\XXXX\Desktop\gfree_temp-root> adb push su /sdcard/su ... I would then get "failed to copy 'su' to '/sdcard/su': Permission denied
Even if I wanted to use adb shell, I would get this:
C:\User\XXXX\Desktop\gfree_temp-root>adb shell
$ adb push su /sdcard/su
adb: permission denied
Click to expand...
Click to collapse
Alrighty then try adb devices (not in the shell) and just verify it actually shows your phone, it won't show 'PHONE' but it's either going to show something or not.
Next, make sure the sdcard is mounted for the phone and not usb disk mode for the pc
Another thought, make sure there isnt a loose 'adb.exe' in the folder, we want to use the one ref'd from androidsdk\platform-tools
All of that failing, mount the SD card.. copy/paste the file(s) to to SD card.. unmount SD card.. continue as if you pushed it to the SD card

WHOOHOOO! I am rooted! I had to turn off the USB transfer thing and it all worked!!!! THANKS SO MUCH!

Nice bro! If I helped at all and if you wouldn't mind, hit the thanks

No problem!

thanks and happy flashing!

[Q] How do I use adb in a linux terminal?

Hello all,
I want to know how to use adb.
It seems pretty easy but I just can't get it to work. I'm using Ubuntu... I've already installed the android sdk.
So where do I go from here.
## WHAT I WANT TO KNOW IS THIS: ##
I want to (among other things) push a new boot animation to my phone from my Ubuntu laptop...
____Of course I could flash it but I want to learn how to push____
I have the "bootanimation.zip" on the root of my SD card.
NOW WHAT? In terminal?
Thanks

generalExpert said:
Hello all,
I want to know how to use adb.
It seems pretty easy but I just can't get it to work. I'm using Ubuntu... I've already installed the android sdk.
So where do I go from here.
## WHAT I WANT TO KNOW IS THIS: ##
I want to (among other things) push a new boot animation to my phone from my Ubuntu laptop...
____Of course I could flash it but I want to learn how to push____
I have the "bootanimation.zip" on the root of my SD card.
NOW WHAT? In terminal?
Thanks
Click to expand...
Click to collapse
First, put bootanimation.zip in the same directory as ADB
su
cd <enter directory with ADB here>
./adb remount
./adb push ./bootanimation.zip /system/media
And you should have your new boot animation.

EndlessDissent said:
First, put bootanimation.zip in the same directory as ADB
su
cd <enter directory with ADB here>
./adb remount
./adb push ./bootanimation.zip /system/media
And you should have your new boot animation.
Click to expand...
Click to collapse
Ok, after I enter "su" it asks for my pass and then says "su: Authentication Failure"
Is there another way like with sudo perhaps?

Ok, I did "sudo su" to become root... I think..
Then did "./adb remount" and it spit out "error: insufficient permissions for device"
Then i did "./adb devices" and it said "???????????? no permissions"
Any Ideas?
My EVO is connected via usb and I have usb debugging on and USB storage ON.

when you do the "su" command, you will need to allow superuser permission on your phone

"sudo su" first in ubuntu

in fact, ive pushed many files to my phone using ubuntu without running as root. if you are new to linux though, be advised the characters will not show as you enter your password, but dont worry, they're there... oh and what he said, you need to be rooted and make sure you can gain root access on the phone, type "./adb shell" and you should see a # sign; meaning you have root. if you see a $ sign you do not have root access. also you can type "./adb devices" to see if you device is 'online' with your computer

can not mount system in read-write mode using adb without recovery mode

I wanted to change my device model, so I copied build.prop from another mobile to my mobile. I am already rooted. But unfortunately I did not change the o.s. from gingerbread to froyo in build.prop ( I have android 2.2 FROYO) When I rebooted, there were many errors. It is now showing no sim card. Mobile network search gives error. Effectively, I can not use the mobile. Terminal emulator, X-plore etc. stopped working. Only Rom toolkit free version works and astro file manager works. Other programs are forcefully closed. Needles to say, I must replace new build.prop with new one.
Using adb I can only pull files but can not write as it is in read only mode.
adb root and adb remount works only if you are in recovery mode ? Y mobile does not have any custom recovery so when I boot in recovery mode it hangs.
Superuser has installed su in system\bin directory. But from adb shell I can use su also. It gives permission denied error. Hence I can not remount the system.
I have read similar threads and found that on some mobiles adb root or adb shell su works but on some not.
I am using Vista 32 bit with admin rights, still can not use root in adb.
Please tell me, how can I mount system read-write. I can not install root explore as google play and even internet is not working.
Please help.

maheshchavan said:
Using adb I can only pull files but can not write as it is in read only mode.
Click to expand...
Click to collapse
activate USB debugging then in console
Code:
adb shell
su
mount -o rw,remount /dev/block/mmcblk0p1 /system
adb push build.prop /system/build.prop
check where is your build.prop

ruscan.calin said:
activate USB debugging then in console
Code:
adb shell
su
mount -o rw,remount /dev/block/mmcblk0p1 /system
adb push build.prop /system/build.prop
check where is your build.prop
Click to expand...
Click to collapse
OMG ruscan.calin i COULD KISS YOU! I had tried to change my OG EVO 4G's buildprop file to another phone so that I could purchase & download an incompatible Google Play app. However after I restarted the phone wouldn't start! It would boot into my rooted HTC EVO 4G Android 2.3.3 and HTC Sense 2.1 but it would get stuck on the wallpaper with just the notification bar at the top and all buttons would be frozen. However I noticed when I plugged in my phone to my computer via usb the computer recognized it. I always keep my phone with USB debugging enabled so I thought I should be good right? I have spent the last 4 hours trying to install and setup adb with no real previous experience with it. I am familiar with dos from years ago and that helped me as it's basic procedure, commands, etc. Then I found out how to install the HTC drivers which I needed and then download the Android SDK with adb that's included which many guides show easily. I started the command prompt (cmd), typed my adb devices command and hurray it showed my phone! I connected and quickly navigated to the build.prop system folder! Luckily when I changed the file I made a bak backup and left it in the same folder. Now the main issue was figuring out how to change the naming of the files which I did via usual adb commands (mv build.prop.bak build.prop). But then to no avail I couldn't get it to write due to it being a system read only folder! Arg! Then I found your post on here, above, and typed it in simply leaving out the adb push portion and replacing that with the mv file command instead and first changing the name of the bad file and then replacing the bak file as the good copy! I exited back to the adb main and unplugged my phone. Moment of truth and man was everything flashing through my head at once! I booted up and YESSSSSSSSSSSSSS, it worked! I went back into root explorer and got rid of the offending leftovers and I've learned my lesson! I just don't want to think about what would have happened if I hadn't found this post. Thank you and if anyone else makes this hug mistake let me know and maybe I can help. Moral of the story don't mess with the build.prop or any system folder unless you know what you're doing! Thanks again!
Quick Guide to Fix Android "build.prop" Issues:
1. Find and download USB drivers for your phone by model or type (HTC EVO 4G's HTC Fastboot drivers): http://downloads.unrevoked.com/HTCDriver3.0.0.007.exe
2. Download and install Android SDK and choose adb: http://developer.android.com/sdk/index.html
Guide: http://htcevohacks.com/htc-evo-hacks/how-to-install-android-sdk-and-adb-drivers-for-htc-evo-4g/
3. Run a command prompt from the "c:/program files/android/android-sdk/platform-tools/" directory. I had to copy the command prompt to get it to open there but sometimes a right-click action will do it. The guide below will help just navigate down to "Using ADB" and skip the rest.
Guide: http://www.howtogeek.com/114667/how...y-default-move-almost-any-app-to-the-sd-card/
4. Once you open the command prompt and you're in the "c:/program files/android/android-sdk/platform-tools/" foler type "adb devices" and your device should appear. If it does move on to next step.
5. Then type adb shell and use the ls command to see directories. Then you'll need to navigate to the system folder by typing "cd system" and then type "ls" to look around in the directory (similar to "dir" in DOS). You should now see the bad build.prop file.
6. You'll need to rename the file or push a correct version. First you need to use the "adb shell" command again and then "su" and finally "mount -o rw,remount /dev/block/mmcblk0p1 /system" to make the directory writable (see ruscan.calin post above for additional info).
Note: I only had to rename my build.prop as I already had my old one in the same system folder. You may have to copy the bad build.prop to your computer, edit it and then push it back to the same system directory. These directions are only for renaming files in the same folder. For the info on how to copy the file to your computer and push it back to your phone go to step *10 below or use the guide below it.
7. I already had the bad build.prop in the system directory with my old one which I had named build.prop.bak. If you have this too simply rename by changing the name first of the bad file to anything by typing "mv build.prop build.prop.bad" or similar.
8. Next rename the build.prop.bak to build.prop by typing "mv build.prop.bak build.prop". Everything should go smoothly and move onto the next step.
9. Finally, If no error messages are found, simply type "adb reboot" or "adb shell reboot" (Depending which version of ADB you have). You should be done, your phone will reboot like normal (working, lol) and everything should be working again! YAY!
*10. To copy the build.prop to your phone type "adb pull /system/build.prop c:\" and the file should be placed in the main c:/ directory on your computer. Navigate to the root (c:/) directory and then right click and "open with" the "build.prop" file using a notepad or other file editor. Then use the text editor (Notepad, etc) to change back what you originally changed to mess everything up. There is tons of stuff on the net to let you know what to fill back in depending on your phone model/type. Or it's possible to get a previous version from an old Nandroid backup or similar. Save the changed text file and make sure its named the same "build.prop" and make sure it's still in the root directory (If you're having issues on this step or just want more insight check out the guides and threads below for more help).
Guide 1: http://androidforums.com/admire-all...p-computer-not-phone-using-root-explorer.html
Guide 2: http://www.modaco.com/topic/328943-quick-guide-to-modifying-buildprop-with-adb/
Guide 3: http://forums.androidcentral.com/sp...-replaced-build-prop-phone-wont-start-up.html
*11. We've already made the directory writable in step 6 so we simply need to push the file back to the phone. If any error message appear re-do step 6 to make writable again. Otherwise push the modified file back to the phone by typing "adb push c:\build.prop /system/". Back to step 9 above! Yay!
If anyone wants to help cleanup this quick guide or make any changes feel free. I just wanted something so that if anyone else has this issue they won't have to worry or search forever to find a solution. OMG it's 2:30AM, to bed... I ride! LOL
Enjoy,
5th :highfive:

THANK YOU!!! Totally saved me today.
One thing that I noticed. After pushing the correct build.prop, I had to fully power down, then turn back on my Razr for it to load up the fixed build.prop.

error message,Help please
Hello, when i am going to mount and change the permission i am getting constant error od device not found or sh:not found.
What to do?Help me please?

jigarpattani said:
Hello, when i am going to mount and change the permission i am getting constant error od device not found or sh:not found.
What to do?Help me please?
Click to expand...
Click to collapse
What step are you on? What phone do you have? More info please?

i am have problem whit my pantech flex i need to use the build.prop.bak but when i type the su it stay in blank do nothing any ideas pls help

ehy there hope someone can help me...i have an archos 97b platinum, messed up with build.prop. So i pulled out and restored but can't push in any way. I have a cwm installed, tablet rooted but i alwais got "permission denied" at push command. Other error is operation not permitted" if i try remount command from adb. i can do mount -o rw,remount /dev/block/mtdblock7 /system but after that push still give me permission denied.
any suggestion?
http://imgur.com/FDLp4fl
i open a 2nd cmd, give the mount -o rw,remount /dev/block/mtdblock7 /system , and system is now rw, but from the first cmd when i give "push build.prop /system (or /system/build.prop) it will always return me permission denied
help

dev.block
i want to view to dev/block using adb shell #
eg . what block is boot.img
what block is recovery.img
what block is system.img
what block is cache.ing
adb shell getprop mtd is not work . Pls Help Me & sent to mail [email protected]

[Q] Having Trouble with adb

I am running Linux Mint 15 on my compute and want to use adb for rooting/reflashing purposes. I downloaded and ran the script from: https://code.google.com/p/adb-fastboot-install/
I used it several weeks ago without any issues. In the instructions it says to rename a file and put it in the Android-tools folder, then change to that directory and then use: adb push filename.zip /sdcard/.
I used adb several weeks ago and don't remember putting the file anywhere special, simply changing to the directory it is in (android-tools)
or specifying the path of the file I wan't to push to the Android SD card. I looked and can't find any folders named "android-tools."
If I run the command adb devices (with the phone connected via USB) I see that the command runs and it finds the device. However, if I then do the command adb push PC36.zip to /sdcard I get an error stating: "cannot stat 'PC36IMG.zip No such file or directory."
What am I doing wrong???

Never Mind
Never mind!
It was getting late so instead of typing the command "adb reboot bootloader" I thought if I just copied and pasted it from the instructions I was using that I would would avoid typos due to being tired. However, I found the my problem was due to my instructions saying to use the command "ADB reboot bootloader."