[Q] ADB: not found .. - Wildfire Q&A, Help & Troubleshooting

Hey
I've got a problem with ADB.
When I try to push HTCAlbum.apk in /system/app
Code:
adb shell
su
adb push HTCAlbum.apk /system/app
I get this error :
Code:
adb: not found
Things I done ..
> Installed Java JDK successfully.
> Installed HTC Sync & drivers successfully.
> Installed the Android SDK successfully .
> Installed every 'Available Packages' in SDK Manager successfully .
> I edited the 'Path' in Environmental Variables (;C:\android-sdk-windows\platform-tools) successfully, and it works.
> Enabled USB Debugging on my HTC.
Extra info?
> Running Windows 7.
> HTCAlbum.apk is in the same map as adb (C:\android-sdk-windows\platform-tools).
> Before I started with the adb push, I changed system r/o to r/w with RootExplorer.
But when I try to push HTCAlbum.apk to /sdcard/ it does work..
Code:
adb shell
su
adb push HTCAlbum.apk /sdcard/
Btw adb devices also works..
So why do I get this error :
Code:
adb: not found
?
Anyone can help me? If u need more information or w/e, just post it in a reply here.
Thanks in advance
-Sorry for my bad English / I'm Dutch so that's why -

If you are using your PC's Android SDK, dont bother with ADB Shells. Just browse to the tools folder of your SDK (Make sure HTCAlbum.apk is placed there), then, simply type
adb push HTCAlbum.apk /system/app
Also, if you are not S-OFF, then Connect your Wildfire to your PC, Reboot into Clockworkmod Recovery, Go to Mounts and Storage, and Select Mount /system. Then perform the above procedure.

3xeno said:
If you are using your PC's Android SDK, dont bother with ADB Shells. Just browse to the tools folder of your SDK (Make sure HTCAlbum.apk is placed there), then, simply type
adb push HTCAlbum.apk /system/app
Also, if you are not S-OFF, then Connect your Wildfire to your PC, Reboot into Clockworkmod Recovery, Go to Mounts and Storage, and Select Mount /system. Then perform the above procedure.
Click to expand...
Click to collapse
I am actually S-OFF, but that method worked (then Connect your Wildfire to your PC, Reboot into Clockworkmod Recovery, Go to Mounts and Storage, and Select Mount /system. Then perform the above procedure.)
Thanks man

Related

[Q] Gingerbread ASOP mms.apk

Is it possible for me to just take the mms.apk from a gb rom and install it on my current asop rom without any issues ?
My current rom doesnt use the asop mms.apk and I want to go back to it
Also if its possible and someone has that mms.apk can you please post it
Here You go! The file's attached. I recommend it to install it with ADB. You may also use (I think) something like Root Explorer, which I don't use, because it is a paid app Here I present you a free way to do it.
How to do it? Here (I'm assuming you use Windows):
1) First make sure You install Your phone's USB drivers in your system
2) Then download Android's SDK:
http://developer.android.com/sdk/index.html
3) Don't really remember how it went after Installation, but you should have an "android-sdk-windows" folder (assuming you use Windows). Put it on your Desktop.
4) Enable USB Debugging in your phone (Under Applicaions -> Development in Settings). Then connect your phone to PC via USB
5) Do a WinKey+R combo. "Run" window should appear. Type
Code:
cmd
and hit Enter.
6) A black console should appear. Type:
Code:
cd Desktop
cd android-sdk-windows
cd platform-tools
dir
you should be able to do a bunch of files, including adb.exe. If you don't, you either messed up folder names or didn't put android sdk folder in your Desktop.
7) Now (in normal Windows Explorer) move Mms.apk to your platform-tools folder inside android-sdk-windows.
8) Now, in console do:
Code:
adb start-server
adb remount (if at this point it says "no device found" you either screwed up your phone's USB drivers, or USB connection, or something else, no idea)
adb shell
9) Now type:
Code:
cd /system/app
cp Mms.apk Mms.apk.bak (to backup your current messaging app, in case something goes wrong, you just do the opposite - cp Mms.apk.bak Mms.apk)
exit
10) Now type:
Code:
adb push Mms.apk /system/app/Mms.apk (should say it's fine)
adb kill-server
Remove your phone from USB, reboot it. Should be done just fine.
Thanks so much warnec!
Im hoping this solves my delayed sms problem with htc messaging app.
Also, i installed this on my Incredible S with revolution hd 2.3.3, and sometimes it force closes, is this normal?
Regards

[Q] Moving new hosts into /system/etc

This is a copy post from here when I realised it was in the wrong spot.
I have a rooted Desire using unrevoked and am trying to use AdFree on 2.2 but I am told that the hosts file I need to block ads cannot be written to /system while Android is running. I did some searching but, alas, no luck on an answer.
I do not know how to get to a command prompt to follow the instructions in this thread and have looked in the ClockworkMod Recovery mode for something similar.
Anyone have an idea?
edit:
I also got Root Explorer off the market (which cannot simply copy the hosts file into /system/etc/ as it does not have access whilst Android is running) and I think the command prompt I need is the pc cmd prompt when the device is plugged into USB, but I am unsure which drivers I need. The ones mention in Toastcfh's guide is for the EVO, not the Desire.
edit 2:
I got the Android SDK with adb and made progress, but still stumped.
I connect the Desire to the PC and with the Desire in recovery mode with ClockworkMod I run adb with:
Code:
adb shell
# mount /system
# exit
adb push hosts /system/etc
adb reboot
Following the example from here but it's a different device and dunno what to put for the first argument in '# mount /dev/block/mtdblock4 /system'. Any help at all would be much appreciated.
The symlink option in adfree should work for S-on devices.
If it doesn't try this:
Code:
adb remount
adb push hosts /system/etc
adb reboot
If that doesn't work flash this.

[Q] Installing DSP Manager to Oxygen

I've got a few problems getting DSP Manager to work on Oxygen.
I try and install the DSPManager.apk file and just get a tick with "Application not installed" next to it.
That's a little confusing since the tick suggests it installed - the "Application not installed" and lack of app says otherwise.
I'm running Oxygen 2.2 but I also got this error on 2.1.6.
Any ideas?
Thanks.
push it via adb (I'm gonna assume you have android-sdk)
put the .apk in your c:\ and reboot into recovery
Code:
cd c:\android-sdk/platform-tools
adb shell
mount /system
exit
adb push c:\DSPManager.apk /system/app/DSPManager.apk
bortak said:
push it via adb (I'm gonna assume you have android-sdk)
put the .apk in your c:\ and reboot into recovery
Code:
cd c:\android-sdk/platform-tools
adb shell
mount /system
exit
adb push c:\DSPManager.apk /system/app/DSPManager.apk
Click to expand...
Click to collapse
That works.
Thanks a bunch mate.

[GUIDE] Mini guide to root Gnex manually

1. Download and install Samsung_USB_Driver_for_Moblie_Phones_v1_4_6_0.exe
Link to download: http://www.multiupload.co.uk/YXE6FWLFAR
2. Download and install Android SDK (http://dl.google.com/android/android-sdk_r16-windows.zip)
3. With the phone turned OFF, hold VOLUME UP + VOLUME DOWN and power the phone on. This will put you in bootloader mode
4. Using windows/cmd go to the folder where Android SDK was installed (make sure that the folder android-sdk/platform-tools/ contains fastboot.exe and adb.exe etc....
5. using windows/cmd go to the folder /android-sdk/platform-tools
From this folder try the command "fastboot devices" (do not include ") which should list the device connected to your PC.
6. First we have to unlock bootloader,
use this command to unlock bootloader > fastboot oem unlock
(warning.. you will loose all data)
After the bootloader is unlocked the device will reboot normally.
7. Once normally booted from the command prompt issue the commands given below (after each command press enter button)
Note: you need su and superuse.apk (which can be downloaded from here: https://rapidshare.com/files/1319181583/su.zip)
unzip the downloaded file in the same folder where fastboot.exe exist i.e /android-sdk/platform-tools/
adb root
adb remount
adb push su /system/bin
adb push Superuser.apk /system/app
adb shell chmod 06755 /system/bin/su
adb shell chmod 06755 /system/app/Superuser.apk
adb reboot
Done!... your device is now rooted.
it would be good to note that many people have issues with the initial android driver installation.
if you install the drivers, but the phone doesn't show up after a period of time, open control panel -> system -> device manager and look for any devices that have a yellow triangle error (no driver). right click and open properties, and manually select the driver, not auto! the next screen will give you an option to 'select from a list', do this, and find SAMSUNG, then select the latest drivers.
after this, it can still take a minute or two the first time for drivers to install properly, you usually can see the status of this in the usb system tray icon.
if you rebooted to the bootloader (power vol(+) vol(-)), from the command line, if you type "fastboot devices" it should list a device and serial number. if not, you need to go check your drivers, something is missing. also, don't forget how magical a windows reboot can be at times : )
cancerouspete said:
it would be good to note that many people have issues with the initial android driver installation.
if you install the drivers, but the phone doesn't show up after a period of time, open control panel -> system -> device manager and look for any devices that have a yellow triangle error (no driver). right click and open properties, and manually select the driver, not auto! the next screen will give you an option to 'select from a list', do this, and find SAMSUNG, then select the latest drivers.
after this, it can still take a minute or two the first time for drivers to install properly, you usually can see the status of this in the usb system tray icon.
if you rebooted to the bootloader (power vol(+) vol(-)), from the command line, if you type "fastboot devices" it should list a device and serial number. if not, you need to go check your drivers, something is missing. also, don't forget how magical a windows reboot can be at times : )
Click to expand...
Click to collapse
Hi
Thanks for this note which would help many users.
Hi, noob here.
First of all, thanks for the guide.
I have already unlocked the bootloader about a month ago (up to step 6), but would like to root.
Will my phone lose all data again if I root the phone now? I'm not even sure what this actually does, but would like to learn and mess around with it.
You will not loose data. Rooting gets access your system folders by pushing su and superuser through adb.
Hope it helps.
Sent from my Galaxy Nexus using xda premium
smohanv said:
Note: you need su and superuse.apk (which can be downloaded from here: https://rapidshare.com/files/1319181583/su.zip)
unzip the downloaded file in the same folder where fastboot.exe exist i.e /android-sdk/platform-tools/
adb root
adb remount
adb push su /system/bin
adb push Superuser.apk /system/app
adb shell chmod 06755 /system/bin/su
adb shell chmod 06755 /system/app/Superuser.apk
adb reboot
Done!... your device is now rooted.
Click to expand...
Click to collapse
Did you actually test that with a stock rom?
Because adb root will not work with ITL41F at least.
Code:
./adb root
adbd cannot run as root in production builds
Furthermore the chmod for Superuser.apk is totally bogus. No need to mess with it's permissions.
i think a better way is get su and SuperUser.apk from the developers (ChainsDD) site and install it with a temporary boot CWM to install it.
(these instructions are also from memory And i rooted my one from source, but that's a bit involved)
this would mean instead of step 7 do.
7. Download CWM into the same directory as fastboot
http://download.clockworkmod.com/recoveries/recovery-clockwork-5.5.0.4-toro.img (Verizon)
or
http://download.clockworkmod.com/recoveries/recovery-clockwork-5.5.0.2-maguro.img (GSM)
Make sure to get the right version for your device.
8. download http://downloads.androidsu.com/superuser/Superuser-3.0.7-efghi-signed.zip
onto the internal storage of the phone( "sdcard" )
9. With the phone turned OFF, hold VOLUME UP + VOLUME DOWN and power the phone on. This will put you in bootloader mode
10. again using windows/cmd go to the folder /android-sdk/platform-tools
From this folder try the command "fastboot devices" (do not include ") which should list the device connected to your PC.
11. Start CWM (without installing it)
fastboot boot recovery-clockwork-XXX-XXX.img
(use the right filename from step 7)
12. choose install update and select the zip from step 8.
You need to use volume up/down to navigate and power to select.

[ADB GUIDE] How to use ADB. (Noob edition)

ADB
Android Debug Bridge
Very useful program made itself by Google for Programmers and developers. Its based on command line and basically communicates with your Android to respond to certain commands. There is vast amount of knowledge about adb but its most useful commands limit to getting:-
Logcat:-
A real time log of what is happening in background of our devices. It is really useful for developers to see which component has malfunctioned and helps to narrow down their search for what failed and what needs to be fixed. Several times users are asked to give logcats of their devices which are giving errors. We will go in detail that how to get logcats in every and easiest way possible.
App Installation and Management:-
adb proves really handy if you want to install apks directly from your PC or want to batch install or delete them.
Shell Execution:-
You must have heard of Terminal Emulator. It is an app for android to execute shell commands(linux commands) which are basically present as applets in /system/bin, /system/sbin or /system/xbin(in our case) folders. A very imporant applet called busybox is installed there mainly used for execution of basic commands during root browsing or ROM installation. Many times updater script of ROMs use busybox commands to install it. Well, these commands can be initiated from your device too but they can be initiated from adb also making it easy for programmers.
Pushing and Pulling:-
Most used commands of adb. adb makes it a piece of cake for new device developers to get an ideo of structure and basic knowledge of devices by pulling command. We can pull out i.e copy any files or folders from our devices to our PC, even the root directories without rooting the devices. It help rooters and ROM chefs of new devices to get an idea and implement their mods on them. Pushing is also very useful command. It copies your files and folders from PC to your device. Very useful in pushing some /system apps and other things
Remounting and setting permissions
Basic commands:-
Of-course basic commands such as reooting and rebooting in recovery ode and download mode are supported.
Others:-
There are several other features of adb such as fastboot, aapt, etc
Setting up ADB
Pre Requirements:-
A little amount of brain
PC(This is a windows guide, if asked I will add linux and mac guide later)
Java Runtime environment or Java Developing kit
Your Device Drivers
An Android Device
USB Debugging MUST be turned ON in the device for ADB to see it & Developer options is hidden in Android 4.2 and
above, Hitting Build number 10 times in
About Phone/Tablet reveals the menu (Thanks lilHermit for reminding me to add it)
Assuming you all these ready and working properly, we continue
If you are having trouble completing Pre-Requisites, there are several guides featuring them too
Start
1. First Download Android SDK. Roughly about 70 MB
2. There may be any compressed zip file or exe file
If zip file, then extract it to C:\android-sdk
If exe file then double click on it and install it in C:\ Drive(or any other drive you want)
3. Now to get adb and other tools, you need to download 'Platform Tools'
To download them, go to the android-sdk folder and double click on SDK Manager
It will ask you which package to download? However, it is your choice which package to Download, but here, we will only talk about platform
Tools. So, simply tick on Platform Tools and click on install. Once you have done it. Go to the platform-tools folder in the directory where you installed android-sdk. You will find several files there like adb, fastboot, aapt, etc
4. Now, you can backup the whole folder of android-sdk to any external storage that will make you not download package
again if you want to. You can have it placed in any computer and run it as it does not require registry to work
5. Now, you are just one step away from using adb. Next step is SKIPPING SETTING ENVIRONMENT VARIABLE (If you however want to set environment variables.)
We can easily append the sdk platform-tools and tools folder to your systems environmental path variable directly from command line(cmd) by simply issuing one command and performing a system reboot:
Code:
SETX PATH "%PATH%;SDK_Install_Path\platform-tools;SDK_Install_Path\android-sdk-windows\tools" -m
Just replace the "SDK_Install_Path" in the above with the proper path of your SDK installation. Example: C:\android-sdk-windows
Many guides on internet say that it is to be done for making it easy for users and if you have some basic knowledge of Command Prompt,
you will know that to execute any application with command prompt, you first need to change the directory to the one where application is
placed. And to skip changing the directories every time you open CMD, you need to put that application is environment variable. Howeve, we will not do so.
6. Type cmd in the search bar. Copy cmd.exe from there. Go to the directory where you have installed android-sdk. Go to platform-tools folder. Paste cmd there, right click on it and in the settings, select Run as Administrator.
7. You are done. Now what to do in it?
ADB Commands
Type adb in command prompt. And several commands will show up on your screen. It is very difficult to analyse these all commands, so we will only talk about most used and important commands
Connect your device via USB cable
And open the CMD in platform-tools folder(Make a shortcut of it on desktop). And type the suitable commands
Code:
adb devices
Will show the list of devices attached to the PC andtheir serial numbers. If this shows up correctly on your PC, then it means that everything is fine for continuing.
Logcat
Code:
adb logcat
It will display the real time log of your device
Best time to do it is when your device boots up
Now, many users ask me how to copy the logcat and upload it from CMD
There are several methods:-
1. Right click on the Title Bar of Command Prompt. Hover the cursor over edit and select mark. Select all the things you want to copy and then click enter. All the things will be copied to clipboard.
2. This is the correct way of getting logcat saved.
Code:
adb logcat > logcat.txt
This command will create a logcat.txt document in platform-tools folder with the complete logcat of the device. Ofcourse you can type any name instead of logcat.txt
3. I prefer taking logcat this way as it neatly compiles logs of different time
Code:
adb logcat -v long > logcat.txt
This is a very nice way to get logcat.
Installing Apps
Code:
adb install %PATH OF APK%
This will install an app on your Android
For example, if my app AreeB.apk is in G:\ drive (G:\AreeB.apk)
Then I will type
Code:
adb install G:\AreeB.apk
Be sure your apk is not in a folder that has space in its name, else the command will break at space bar.
For eg:-
G:\Program Files\AreeB.apk
Note:
If you have spaces in path of apk, you can execute the command without breakage if you include the path inside quotes. (Thanks to etcman)
Eg:-
Code:
adb install "G:\Program Files\AreeB.apk"
Mounting
However, I never found any problem in tweaking with system files with adb, but some users said that they couldn't do it, so the problem was that their system partition was mounted as Read Only(R/O)
So, it is necessary now to tell how to mount system partition as Read Write(R/W)
Code:
adb remount
It is easiest way to do so, if it does not work then
There is another method that we will discuss in ADB Shell commands section
Pushing and Pulling
For pushing,
Type
Code:
adb push %PATH TO BE PUSHED% %PATH WHERE TO BE PUSHED%
Suppose I have an app named SystemUI.apk(PATH = G:\SystemUI.apk) which I want to push in /system/app/ on my android(or in other words, install an app as a system app). Then I would type
Code:
adb push G:\SystemUI.apk /system/app/
More examples
G:\Dance.txt file to be pushed in Dance folder in sdcard
Code:
adb push G:\Dance.txt /sdcard/Dance/
OR
Code:
adb push G:\Dance.txt /mnt/sdcard/Dance/
G:\Movies folder to be transferred in SDCARD in Videos Folder
Code:
adb push G:\Movies /sdcard/Videos/
G:\system\framework\framework-res.apk to be pushed in /system/framework/
Code:
adb push G:\system\framework\framework-res.apk /system/framework/
For pulling,
push command replaces with pull and paths are swapped
Code:
adb pull %PATH TO BE PULLED FROM% %PATH TO PLACE PULLED FILE%
Example,
All system apps are to be pulled to G:\ROM\system\app
Code:
adb pull /system/app G:\ROM\system\app\
build.prop to be extracted to desktop
Code:
adb pull /system/build.prop C:\Users\Areeb\Desktop\
However, if a folder is in platform-tools folder, you don't need to type full path
Suppose if I type
Code:
adb pull /system/ system
Then a folder named system will be created inside platform-tools with all the files in system in it
If a file is in platform-tools folder, then also no need to type full path
For example,
There is an app name DeskClock.apk in this folder then, to push it to /system/app, type
Code:
adb push DeskClock.apk /system/app/
ADB Shell Commands
This mode of adb allows you to execute linux shell commands from your PC
These commands can aldo be executed through the mobile using Terminal Emulator
To initiate shell mode
Type
Code:
adb shell
You will get an prompt like this
sh-3.2#
Now you are in shell mode
adb commands won't work here and a new set of commands will work here. But we will only go in a little detail here.
Assuming you are in adb shell mode, I will only type commands that will work on shell. Note:- These commands won't work if you type them alone on cmd. But, these command will directly work on your mobile's Terminal Emulator
As these commands can also work on mobile, I am going to tell you a way of taking logcat on mobile
Type
Code:
logcat
You will see log of your device
To save this
Type
Code:
logcat > /sdcard/log.txt
A file named log.txt will be generated in sdcard
Uninstalling Applications
Code:
cd /data/app
This will change the directory to /data/app
Code:
ls
This will show the list of files in there
Suppose, there is an app named com.opera.browser (Opera Mobile) you want to uninstall it
Type
Code:
rm -r com.opera.browser
This will uninstall the app
Mounting Command:-
Code:
mount -o rw,remount /dev/block/mtdblock3 /system
Miscellanous commands:-
su: Initiates root request
du: Shows file foldrs and size
date: Shows todays date
ls: Shows list of directory
cd: Changes working directory
rm: Removes the file
logcat: Displays logcat
mount: Mounts the partition
busybox: Busybox Applets
Forgot next ones, will write later
All credits go to
iamareebjamal
For writing this up.

Categories

Resources