Develop Bugs

ADB commands not working

So i rooted my desire using the modaco r6 root.
I'm using defrost 1.0 atm and when I'm entering recovery i cant use any adb command, except for devices which show my desire in recovery mode.
all other commands return an error like:
su:
/sbin/sh: su: not found
logcat:
/sbin/sh: exec: line 1: logcat: not found
install
/sbin/sh: pm: not found
just to name a few.
i just got it so i don't know if they worked before.
however i did get one boot loop due to flashing the circle battery mode.
after which i recovered the nandroid backup.
If you need more info tell me what to do im clueless, im prolly just doing something very stupid.
Thanks in advance.

Go into partitions menu and mount /system then try.

No go doesn't even change the error.

so no ideas? i got no wifi or 3g connectivity atm so you guys are my last resort.
just some updates i flashed mcr 3.1 and it change in addition htc sync doesn't recognize my desire now.

you've cd to your android sdk tools folder right?
and youve typed in 'adb shell'?
when writing commands there should be a hash before the command?

Can you not boot into fastboot. Volume down and power. Then go to recovery. Then hold volume up and power. Select wipe data and wipe cache. Wouldn't that solve your wifi issues etc?

Wait...if you're using root r6 then your using fake flash aren't you? Try looking for r5 and use pauls recovery or look for amskghs recovery and use that. Pretty sure adb stuff doesn't work easily with fake-flash.

cgrec92 said:
you've cd to your android sdk tools folder right?
and youve typed in 'adb shell'?
when writing commands there should be a hash before the command?
Click to expand...
Click to collapse
yea i'm in the sdk tools folder when i'm typing commands otherwise the
"adb devices" wont work and it does.
i typed adb shell.
sorry about this but what is hash? :S
ephumuris
i tried using amghskmod recovery and it doesn't work as well, the errors are a bit different.
its just saying su not found instead of the whole /sbin/sh thing.

Hash = #
What exact commands are you doing and what are you trying to achieve?
I really want to help

LByte said:
yea i'm in the sdk tools folder when i'm typing commands otherwise the
"adb devices" wont work and it does.
i typed adb shell.
sorry about this but what is hash? :S
ephumuris
i tried using amghskmod recovery and it doesn't work as well, the errors are a bit different.
its just saying su not found instead of the whole /sbin/sh thing.
Click to expand...
Click to collapse
I had your same problems and felt retarded too, but it might be something funky with the dos command prompt in windows. Follow these instructions to make adb commands universal so it doesn't matter what directory the dos command prompt thinks you're in (because obviously it didn't actually move you to the tools folder somehow even though you instructed it too):
- Also, Mikey1022 has reminded me to add the "ADB" directory path as a system variable in windows...
To do this right-click on "My Computer" and select Properties. Next select the Advanced tab(Advanced Settings in Vista) then select Environment Variables.
Click "New" under System Variables and add the following:
Variable: adb
Value: C:\android-sdk-windows-1.1_r1\tools
This was found here: sorry can't post link to give proper credit, but do a google search for adb for dummies or adb commands, it's an xda forum post...

The thread looks dead, but im going to post the possible solution anyway.
PM commands like install and uninstall doesnt work in recovery mode, so if you want to use them, run the commands when the phone had booted normally.

i have same problem? anyone help me
adb error /sbin/sh: exec: line 1: logcat: not found

[Q] rooting slide in ubuntu

Hey If anyone can help i have a few questions about rooting the slide in ubuntu
the "loop" script will not run regardless of what i do....also i can't seem to get the phone to show up with adb devices when i am in the bootloader
i can see the phone when it is in the rom but for some reason it won't show in the bootloader
thanks in advance

just type
Code:
adb devices
in terminal, and then when you select recovery and press enter, press "ENTER, UP, ENTER, UP, ENTER, UP...) really fast...and hope it works! if not lather, rinse, repeat...

There are instructions in the rooting thread on making an equivalent script for MacOS (which should work under Linux as well.) If you tried to run a DOS batch file under Linux thinking it would work...well, that's a judgment for another day
-------------------------------------
Sent via the XDA Tapatalk App

The Mac script does not run as a sh script on linux.
(PS: don't for the ./ before adb on a linux term. (./adb etc...))
beartard said:
There are instructions in the rooting thread on making an equivalent script for MacOS (which should work under Linux as well.) If you tried to run a DOS batch file under Linux thinking it would work...well, that's a judgment for another day
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
Sent from my T-Mobile myTouch 3G Slide using Tapatalk

Ive got a loop script for linux that I can send you when I get home. And like Indikut said, don't forget to add "./" before adb.

chrisinaz said:
Ive got a loop script for linux that I can send you when I get home. And like Indikut said, don't forget to add "./" before adb.
Click to expand...
Click to collapse
No need for the ./ if you added the sdk tools folder to your PATH.

Why that MacOS script doesn't work in bash on Ubuntu is beyond me. It looks to be formatted correctly.
Code:
#!/bin/sh
while [ 1 ]; do
adb devices;
sleep .25;
done
You could always use the following equivalent:
Code:
#!/bin/sh
watch -n .25 adb devices;
done
Assuming adb is in your path, this would run it every 1/4 second. You could, of course, change it to suit your location for adb (/usr/local/bin/adb or other location).

Cool thanks ..I will try that for the loop script
The other issue I have is that I can't see my phone as a device when I type adb devices in the bootloader ...it works fine when the phone is in the rom tho....I tried searching for the problem but I can't seem to find a solution ....I may just have overlooked it tho

beartard said:
Why that MacOS script doesn't work in bash on Ubuntu is beyond me. It looks to be formatted correctly.
Code:
#!/bin/sh
while [ 1 ]; do
adb devices;
sleep .25;
done
You could always use the following equivalent:
Code:
#!/bin/sh
watch -n .25 adb devices;
done
Assuming adb is in your path, this would run it every 1/4 second. You could, of course, change it to suit your location for adb (/usr/local/bin/adb or other location).
Click to expand...
Click to collapse
thanks again for the help with my problem i have a feeling the macos script would of worked i was using the wrong command i ended up typing "sh loop.sh" and it ran the script ....alltho i don't see it spamming adb devices ...it seems to just output it one time ....
now all i have to do is get the phone to show up when its in the bootloader....off to the search button i go

newspeak said:
thanks again for the help with my problem i have a feeling the macos script would of worked i was using the wrong command i ended up typing "sh loop.sh" and it ran the script ....alltho i don't see it spamming adb devices ...it seems to just output it one time ....
now all i have to do is get the phone to show up when its in the bootloader....off to the search button i go
Click to expand...
Click to collapse
As soon as you hit power to go to recovery either A) Activate the stupid script or B) mash ENTER+UP+ENTER+UP+ENTER until your keys fall off. I only got it to work the latter way.
Also, in Linux I've found that you'll get ???????? NO PERMISSIONS unless you do sudo ./adb devices.

The first time you run adb in a session, it should be started with sudo, since that starts the adb daemon. After that, any normal user's permissions (like running the script) should be ok. Make it easy on yourself and copy the adb executable to some place in your path (I use /usr/local/bin/). That way, you can delete the entire SDK unless you have plans for developing apps for Android.
I tried using my second code snippet above as loop.sh. I didn't go any higher, but it really doesn't have to work really quickly. I went up to .5 (executing "adb devices" twice a second) and it worked fine. You won't see a scrolling output like you would in DOS. The screen just updates if/when new info comes up (like showing the phone offline or in recovery.) When you get to the phone icon with the red triangle, hit VolUp and Power at the same time to get the recovery menu. The rest of the normal root tutorial should work for you.

ok thanks again for the help so far....here is where i am at ...i put adb in /usr/local/bin ...i can use adb devices ....the script is working for me but now when i get to the point where i push over the first file it says permission denied
i make sure to start adb with sudo ....i even tried running everything from a root terminal but i still get the same thing....i have already tried killing the adb server and restarting it with root permissions ...i have tried pushing the file with devices still listed as offline
kind of at a loss
here is what i get btw
"[email protected]:~/androidsdk/tools$ adb push ota.zip /sdcard/update.zip
failed to copy 'ota.zip' to '/sdcard/update.zip': Permission denied
[email protected]:~/androidsdk/tools$
"

I'm using a pretty fresh install of Ubuntu Lucid. I haven't messed with my user's groups or anything, so it's still fairly stock.
All I've done is copied adb to /usr/local/bin. The first run of adb (adb devices) is done as root using sudo. You could try running "sudo adb root" to begin with, and see if that makes a difference. After that, I can run any adb push commands as the normal user in GNOME's terminal.
Assuming you're set up like I am, if you're getting a permissions error after doing that, I'd hazard a guess and say the problem is on the phone's side rather than the computer.
Check and make sure USB debugging is checked in your settings. Beyond that, I'm stumped.

Having problems rooting

ADB is not friendly to me. I was able to root my g1 with pure ease. I cant get started with adb, I dont know why I cant get $, I've read several guides and I'm just about to give up. I'm running 2.2 on my g2.
I do have a couple of questions:
Are rooting with rage or visionary 14 the only way to root?
Are there any root guides out there that dont require ADB?
ADB is a ****ing pain in the ass to me, especially since I've tried everything and cant get it to work. Also, the drivers that go on Win7 64bit just dont work.
Also when I do have root, can I get android updates?
Any help would be thankfully appreciated. Sorry if I'm a pain in the ass, but I'd like to know if there is an easier way.

I think you need the q&a section
Sent from my HTC Vision using XDA App

This will help u get adb working...
http://forum.xda-developers.com/showthread.php?t=865685

If you can't figure out adb, you definitely shouldn't be rooting your phone.
Some ROMS disable OTA notifications while others allow it. However, so long as you have a custom recovery, even if you get the notification and download it, you wont be able to flash it.

dictionary said:
If you can't figure out adb, you definitely shouldn't be rooting your phone.
Some ROMS disable OTA notifications while others allow it. However, so long as you have a custom recovery, even if you get the notification and download it, you wont be able to flash it.
Click to expand...
Click to collapse
while my knowledge of adb isnt stellar, I have run into problems using it. I'm going to try this new link to the guide and see if it works.
Still if anyone knows other solutions, chime in.

Try the guide linked above. The drivers in the HTC Sync package (see the guide) definitely do work on Win 7 64-bit.

Clicked on SDK Manager.exe and it gave me the attached message; anti-virus is off and bare ass minimum services are running and I added the line in variables.
Any ideas?

sorry about the ****ty pics

cwis said:
Clicked on SDK Manager.exe and it gave me the attached message; anti-virus is off and bare ass minimum services are running and I added the line in variables.
Any ideas?
Click to expand...
Click to collapse
Did you definitely add it to your path as it is suggesting in that window ? If so, I think you may need to reboot to pick that change up.

I did that just in case.
Actually, that path field was empty. So, I added it as is.

look up droid explorer

I made some leeway:
C:\Program Files (x86)\android-sdk-windows\tools>adb shell
$
$ adb push su /sdcard/su
$ adb push su /sdcard/su
$ adb: permission denied
good grief!!!!!!!

I've completely removed visionary before starting this procedure. Did I need temproot before attempting this?
Downloading and installing Droid Explorer. Thanks!
Also, I'm using this guide: http://forum.xda-developers.com/showthread.php?t=834228

No matter what I've done, permission denied.

The steps you are trying are actually to get temproot (it's an alternate method to Visionary), so you don't need to already be temprooted.
You don't want to run "adb push" commands after you have run "adb shell". ADB commands will no longer work until you exit the shell (simply type exit and hit enter---you'll notice your command prompt will change back to normal). If you are following the guide you linked to, you'll notice adb shell is not run prior to running the first push command.

ianmcquinn said:
The steps you are trying are actually to get temproot (it's an alternate method to Visionary), so you don't need to already be temprooted.
You don't want to run "adb push" commands after you have run "adb shell". ADB commands will no longer work until you exit the shell (simply type exit and hit enter---you'll notice your command prompt will change back to normal). If you are following the guide you linked to, you'll notice adb shell is not run prior to running the first push command.
Click to expand...
Click to collapse
^^^^ what he said.
You are trying to run adb on your phone there, which isn't right. That's your phone's command prompt, the "$". "adb" is something totally different on your phone. You need to run the adb commands on your PC. That's why "adb shell" worked (because you ran it on your PC), then "adb push" didn't (because you tried to run it on your phone).

steviewevie said:
^^^^ what he said.
You are trying to run adb on your phone there, which isn't right. That's your phone's command prompt, the "$". "adb" is something totally different on your phone. You need to run the adb commands on your PC. That's why "adb shell" worked (because you ran it on your PC), then "adb push" didn't (because you tried to run it on your phone).
Click to expand...
Click to collapse
I did run the commands from my pc. But still permission denied.

cwis said:
I did run the commands from my pc. But still permission denied.
Click to expand...
Click to collapse
"permission denied" is a message from your phone, not your PC.
The $ prompt that you copied and pasted up shows that you were running the commands on your phone. As soon as you do "adb shell", then any commands you are entering after that are going on your phone, even though they're physically being typed on your PC - because your PC has started a command prompt on your phone, as shown by the $ prompt.

cwis said:
I did run the commands from my pc. But still permission denied.
Click to expand...
Click to collapse
Basically, don't start by typing adb shell. The instructions you are trying to follow don't even say to do that anywhere. I highly recommend you reread the instructions very carefully and follow them exactly. Rooting this phone is actually pretty simple if you just do exactly as the guide states. If you don't know what you are doing and mistype something in some of the later steps though, you can seriously screw up your phone...

I think part of the confusion is that the commands listed on the guide all have "$" at the beginning of them, probably because whoever wrote that was using a Linux PC or maybe a Mac. You are actually executing these commands from your Windows command shell so they will look more like:
D:\Android SDK\platform-tools>adb push su /sdcard/su
Click to expand...
Click to collapse
(depending on where you have the SDK installed)
instead of:
$ adb push su /sdcard/su
Click to expand...
Click to collapse
but of course you only need to type:
adb push su /sdcard/su
Click to expand...
Click to collapse
Again these are typed from your windows command shell.

[Q] Temporary Nand Unlock

How do you gain temporary nand unlock? All i wanted to do is copy 2 files into the /system/xbin/bb which doesnt seem to work with root explorer despite super user permission, copy paste just wont work.
Any ideas how to copy paste these 2 files without going to full s-off? Would the adb method work? or any other apk that can do the job?
Thanks in advance for those who can help and any tips is very much appreciated.

In recovery with adb.

TheGhost1233 said:
In recovery with adb.
Click to expand...
Click to collapse
any links to it? a guide perhaps? thanks for the tip.

Make a nandroid before messing with the system partition.
Then:
Code:
adb remount
adb push <file_name> /system/xbin/bb
This is what i think it is just looking at the basic adb commands, here is some more info about moving stuff to the system partition.

TheGhost1233 said:
Make a nandroid before messing with the system partition.
Then:
Code:
adb remount
adb push <file_name> /system/xbin/bb
This is what i think it is just looking at the basic adb commands, here is some more info about moving stuff to the system partition.
Click to expand...
Click to collapse
btw, how do i get to adb with recovery?

You do know that adb is part of the android sdk and not some function/app on the phone?
To get adb working (i hope you already installed it) just boot in to recovery, connect the usb cable, and launch adb via command prompt or terminal.

TheGhost1233 said:
You do know that adb is part of the android sdk and not some function/app on the phone?
To get adb working (i hope you already installed it) just boot in to recovery, connect the usb cable, and launch adb via command prompt or terminal.
Click to expand...
Click to collapse
many thanks! i will try this tommorow.

Use the update.zip I attached in this thread, you don't need to worry about adb then.
http://forum.xda-developers.com/showthread.php?t=885506&page=2
Sent from my HTC Desire using XDA App

Ghettonine said:
many thanks! i will try this tommorow.
Click to expand...
Click to collapse
Ok I did my best, read alot about adb and followed some tips but I just cant seem to get these things working. I need a DETAILED step by step procedure.
I feel such a noob today, can anyone please help?
Basically, I just wanted to copy "ifconfig" and "route" from "/system/xbin" to "system/xbin/bb" and thats it! Im s-on by the way and dont want a full s-off just to copy paste 2 files.
I tried rebooting in recovery with adb and run some commands on "adb shell", many things came out and I have no idea what it ment.

Well many things came out is not such a great description. So i have no idea if something is wrong or something happened which you did not expect.
Boot again in to recovery and connect adb.
The type "adb devices" this should output something like:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
HT##########
If this does not happen you don't have a connection and most likely have driver issues (only if you are on windows). If you do get a connection next thing to do is mount the system partition as read/write. To do this type "adb remount".
The output should be "remount succeeded"
Next type "adb shell"
This should give "#" as output .
Since you know where the files are and where you want them to go type "mv /system/xbin/ifconfig /system/xbin/bb" and hit enter, you don't get any conformation about this. Next type "mv /system/xbin/route /system/xbin/bb"
To check if they go moved correctly type " ls /system/xbin/bb", now you should see the files listed.
Next type "exit" to end the adb shell.
Then type "adb reboot".
If this doesn't work you need to give more info about the errors you get or maybe someone else has a better description.
A completly other method is, if you are able to copy the files to your computer, useing the .zip mercianary linked to, just make sure the system/app folder is empty and that you make the system/xbin/bb folder and place the files in there. Then just follow the instructions.

Stuck in recovery with no Rom

To make it short, I got downloaded a corrupted ROM (only one on the phone), and with no nandroid. Is there any other way to access my "sd" card on my phone to put another ROM in? Is flashing a stock img the only way to get it back to work without losing my pictures? Thanks..

If its recognized by the computer, just "adb push" the ROM file (and anything else you need) to your phone.

martonikaj said:
If its recognized by the computer, just "adb push" the ROM file (and anything else you need) to your phone.
Click to expand...
Click to collapse
This.
Problem sorted.

Thanks for the suggestion, but can you provide some commands to push this file through adb?

if you are not familiar with adb commands, use Android Commander. Saves alot of time.

I'm a bit more familiar with adb, it's just need the to be directed to the right path with the specific command to push a rom to my phone. Does anyone know?
i tried
adb push "filename"/sdcard/"filename" but it's not giving me any response.

Deekayy said:
I'm a bit more familiar with adb, it's just need the to be directed to the right path with the specific command to push a rom to my phone. Does anyone know?
i tried
adb push "filename"/sdcard/"filename" but it's not giving me any response.
Click to expand...
Click to collapse
Is your ROM file in the Android>Platform Tools folder?
adb push rom.zip /sdcard/
You need the extension (.zip) as well.
Edit: does adb devices indicate you're connected?

Deekayy said:
I'm a bit more familiar with adb, it's just need the to be directed to the right path with the specific command to push a rom to my phone. Does anyone know?
i tried
adb push "filename"/sdcard/"filename" but it's not giving me any response.
Click to expand...
Click to collapse
you just need:
Code:
adb push ROMname.zip /sdcard/
Assuming you put "ROMname.zip" in your platform-tools folder, or another folder you're running ADB out of.

Keep in mind, not any response, aka, just hanging, means it is still working. ADB transfers are slow, so big files will take a little bit.

Nevermind.

martonikaj said:
you just need:
Code:
adb push ROMname.zip /sdcard/
Assuming you put "ROMname.zip" in your platform-tools folder, or another folder you're running ADB out of.
Click to expand...
Click to collapse
Yes I did that, and now for some reason my sdk is not recognizing my phone (funny cause i tried flashing a new recovery.img). Now i'm re-installing sdk tools.
adrynalyne said:
Keep in mind, not any response, aka, just hanging, means it is still working. ADB transfers are slow, so big files will take a little bit.
Click to expand...
Click to collapse
Thanks, gotta fix the first problem though.