Develop Bugs

[Q] Evo Won't charge, see sdcard or be seen by pc

Originally posted in general. Sorry.
My Evo won't charge unless it is turned off. When the phone is on, the usb won't give me any mode option. Phone doesn't see the sdcard. I've tried three different cards. PC won't see the phone. I have usb debugging checked. Device manager gives me three qualcomm CDMA Technologies and can't find drivers. Downloaded qualcomm drivers. Device manager now shows them as samsung items. Everything on the phone works except for apps using the sdcard. With the vol down and power the phone will read the PC36IMG.zip of the sdcard and load and run it. After rebooting it still doesn't recognize the sdcard. Using fastboot the device manager gives me Android Devices, but I can't use adb commands. I get and error device not found. Any help?

it should charge anyway, even without the drivers...but, sounds like you need 'em to me. they're in the forums...somewhere...or, you could just get the most recent sdk, and update the drivers using devmgmt.msc (i'm assuming you're on windows)

this happen to me yesterday, i was able to fix it... i have to find the steps

airauto said:
Originally posted in general. Sorry.
My Evo won't charge unless it is turned off. When the phone is on, the usb won't give me any mode option. Phone doesn't see the sdcard. I've tried three different cards. PC won't see the phone. I have usb debugging checked. Device manager gives me three qualcomm CDMA Technologies and can't find drivers. Downloaded qualcomm drivers. Device manager now shows them as samsung items. Everything on the phone works except for apps using the sdcard. With the vol down and power the phone will read the PC36IMG.zip of the sdcard and load and run it. After rebooting it still doesn't recognize the sdcard. Using fastboot the device manager gives me Android Devices, but I can't use adb commands. I get and error device not found. Any help?
Click to expand...
Click to collapse
here you go
http://forum.xda-developers.com/showthread.php?t=695243

The phone only charges when the phone is off. I've downloaded the latest sdk drivers. I tried the SD Card Fix, but I can't get to an ADB shell.

The phone worked great for a couple of weeks, but when I was using Rom Manager to load a rom, I got an error and a red triangle. I pulled the battery and started the phone. It couldn't load the sdcard, it wouldn't give me usb options. It did give me a short battery life and no way to use ADB commands. I can't use rom manager or titanium backup or nand to restore backups. I really need help please!

airauto said:
The phone only charges when the phone is off. I've downloaded the latest sdk drivers. I tried the SD Card Fix, but I can't get to an ADB shell.
Click to expand...
Click to collapse
if you can't get to a shell, that probably means that an adb devices command is not seeing the device.
i'll refer you to the earlier statement about you not having the drivers.

I checked and I have downloaded android-sdk_r06-windows.zip. I believe these are the latest drivers. They worked fine until it crashed while I was using rom manager to load a different rom. It seems strange that everything works except for charging while on, usb and the sdcard.

airauto said:
I checked and I have downloaded android-sdk_r06-windows.zip. I believe these are the latest drivers. They worked fine until it crashed while I was using rom manager to load a different rom. It seems strange that everything works except for charging while on, usb and the sdcard.
Click to expand...
Click to collapse
just having the sdk doesn't enable drivers. if you are on windows, in the 'search' field (or in a cmd shell) type
devmgmt.msc
there, you will probably see a device , i think it will have a yellow triangle and an exclamation point. right click on that device, choose the option that allows you to install drivers. then, browse for drivers (make sure you have the option to include subfolders checkmarked). the drivers are located in the 'usb drivers' folder in the sdk folder. once you have the 'usb drivers' folder highlighted, just choose 'okay', and it will search that folder and subfolders for the appropriate driver.

I've done that. When I use devmgmt.msc and I connect my phone it gives me three unknowns called Qualcomm CDMA Technologies MSM. I point these to the drivers folder and it doesn't recognize them. I downloaded qualcomm drivers and it recognized them as samsung devices and these don't work. When I hook up usb while in fastboot devmgmt.msc gets one device called android devices, but it still will not recognize the sdk drivers. Something happened when the phone crashed. Is there a way to do anything with hboot or fast boot or the other items in that menu to get the phone to recognize adb commands. The phone does load and install PC36IMG.zip, but the phone still acts the same, no sdcard, no usb and no charge.

I was trying this thread
http://forum.xda-developers.com/showthread.php?t=695243
How do you Run from a terminal emulator in Android since I don't have ADB?

airauto said:
I was trying this thread
http://forum.xda-developers.com/showthread.php?t=695243
How do you Run from a terminal emulator in Android since I don't have ADB?
Click to expand...
Click to collapse
you have to get a terminal emulator. and, you have to have downloaded those files to your sdcard. you also have to be rooted already.

OK, I have the two files extracted and on the sdcard. I called up the terminal emulator and typed
su
cat /sdcard/flash_image > /data/flash_image
at this point I get an error message /sdcard/flash_image: No such file or directory
at one time my phone was rooted, but I no longer have the Superuser Permissions.
help some more?
Edit/Delete Message

Ok thanks, I finally got it all working. After a week of learning about ADB, Terminal and Fastboot commands not to mention the structure of the Evo file system, charging, usb and sdcard are all working thanks to everyone contributing to the forum.

airauto said:
Ok thanks, I finally got it all working. After a week of learning about ADB, Terminal and Fastboot commands not to mention the structure of the Evo file system, charging, usb and sdcard are all working thanks to everyone contributing to the forum.
Click to expand...
Click to collapse
could you provide a step by step to how you got this issue resolved?
my brother's phone is experiencing the exact same symptoms you described.
we have been at it for a week.
we too cannot get the "adb shell" command to work when trying to use SDK.
we get the error "device not found" after typing "adb shell".
Im not sure its being done correctly either.
please assist, your help is greatly appreciated.

I used this thread:
http://forum.xda-developers.com/showthread.php?t=695243
Read through the whole thread and download the files. Install them on the root directory of your sdcard with a card reader/writer. Put the sdcard back in your phone.
Now to use the thread you have to get into recovery.
Hold vol down and press power on your phone.
Plug in the usb, and open device manager on your PC.
Choose recovery and make sure Android USB Devices show up in device manger
On the PC, get to a DOS prompt and change dir to where you have adb and fastboot and follow the thread for SD Card Fix and USB Fix exactly.
Good Luck!
And thank you to Calkulin for the thread!

airauto said:
I used this thread:
http://forum.xda-developers.com/showthread.php?t=695243
Read through the whole thread and download the files. Install them on the root directory of your sdcard with a card reader/writer. Put the sdcard back in your phone.
Now to use the thread you have to get into recovery.
Hold vol down and press power on your phone.
Plug in the usb, and open device manager on your PC.
Choose recovery and make sure Android USB Devices show up in device manger
On the PC, get to a DOS prompt and change dir to where you have adb and fastboot and follow the thread for SD Card Fix and USB Fix exactly.
Good Luck!
And thank you to Calkulin for the thread!
Click to expand...
Click to collapse
Yeah I had found that thread as well, I get all the way up to the adb commands.
when I type adb shell, I get "device not found".
also, just to verify, I boot the phone down and turn it on using "down volume" and "power".
when the "HBOOT" screen shows up and the scan finds nothing, I select "fastboot", and leave it there.
then back to the pc:
before I type "adb shell', I point to the directory "c:/users/desktop/android-sdk-windows/tools".
once the directory is pointed to "c:/users/desktop/android-sdk-windows/tools", I input "adb shell" command.
Is this correct?
That is the procedure I follow and I keep getting "device not found", and yes my sdk is fully updated.

Yes, but don't do ADB shell. In HBOOT hit the vol down button to highlight recovery. Hit the power button to select recovery and let it sit there. Go to your pc check your device manager. Then change dir to where you have ADB. Fastboot is also there
Fastboot is an executable program same as ADB. At the prompt just type the commands for the sdcard fix. ie:
fastboot oem enableqxdm 0
fastboot reboot
Your sdcard should be recognized. For the next section you will need to get the Android Terminal Emulator from the Android Market and enter the commands in it.
Have fun!

jdr6382 said:
Yeah I had found that thread as well, I get all the way up to the adb commands.
when I type adb shell, I get "device not found".
also, just to verify, I boot the phone down and turn it on using "down volume" and "power".
when the "HBOOT" screen shows up and the scan finds nothing, I select "fastboot", and leave it there.
then back to the pc:
before I type "adb shell', I point to the directory "c:/users/desktop/android-sdk-windows/tools".
once the directory is pointed to "c:/users/desktop/android-sdk-windows/tools", I input "adb shell" command.
Is this correct?
That is the procedure I follow and I keep getting "device not found", and yes my sdk is fully updated.
Click to expand...
Click to collapse
airauto said:
I used this thread:
http://forum.xda-developers.com/showthread.php?t=695243
Read through the whole thread and download the files. Install them on the root directory of your sdcard with a card reader/writer. Put the sdcard back in your phone.
Now to use the thread you have to get into recovery.
Hold vol down and press power on your phone.
Plug in the usb, and open device manager on your PC.
Choose recovery and make sure Android USB Devices show up in device manger
On the PC, get to a DOS prompt and change dir to where you have adb and fastboot and follow the thread for SD Card Fix and USB Fix exactly.
Good Luck!
And thank you to Calkulin for the thread!
Click to expand...
Click to collapse
That was it!! once we got the files on the SD card through my phone, and put it back in his phone, we did the commands and it worked!! good stuff, mad appreciation given here.

Congratulations. You got your EVO back better than ever!

G2 root problem - rage

trying to root using this methods:
http://forum.xda-developers.com/wik...cess_.28Permanent_Root_.2F_.22Permaroot.22.29
I start doing the temp root as it explains to do first. on the first command (adb push su /sdcard/su) i get "permission denied".
I have the sd card mounted to my phone not the computer. I appreciate your help.

Are you sure that ADB is working in general? What happens when you enter the command "adb devices"?
All that command is doing is copying a file from your computer to the root of the SD card, most of the time the SD card will be formatted with FAT32 and there aren't even any security settings for that.
You could use other methods to get the files from your PC to your phone but I'd be concerned you have an ADB problem.

raitchison said:
Are you sure that ADB is working in general? What happens when you enter the command "adb devices"?
All that command is doing is copying a file from your computer to the root of the SD card, most of the time the SD card will be formatted with FAT32 and there aren't even any security settings for that.
You could use other methods to get the files from your PC to your phone but I'd be concerned you have an ADB problem.
Click to expand...
Click to collapse
I see a device listed there which matches my phones s/n.
I agree, i would like to see ADB working properly. Any suggestions are very welcome. Thanks.

OK so let's assume that ADB is working then, I wonder if something strange is going on with your SD card, do you have another card you can use for testing, take a card (even an old 1GB card will do), format for FAT32, put in the device and try again.
Can you copy ANY file to your SD card?
Test by copying any file to the SD card, I'd probably create a small text file and then run:
adb push test.txt /sdcard/test.txt
Click to expand...
Click to collapse
Assumes the file you are using is named "test.txt" of course.
Also make sure the folder you run your ADB commands from is the folder that contains the files you want to push, if you have ADB files in your path you can run the ADB commands from whichever folder you downloaded the files to. Otherwise copy the files to the folder where ADB lives.

I think i have a spare card somewhere, i will look for it when i get home.
I know i can copy stuff to my sd card using windows explorer when i "turn on usb storage"
I tried using a test text file i created, no dice. I put the files in the same place as adb, and additionally tried using the absolute path.
Also, i tried running the command: adb push rage /data/local/tmp/rage
which i believe is copying the built in memory and not the sdcard, this also gave me "permission denied"

Did you enable USB debugging on your phone?

ianmcquinn said:
Did you enable USB debugging on your phone?
Click to expand...
Click to collapse
Yes
Sent from my T-Mobile G2 using XDA App

And you typed in no other commands prior (e.g., no "adb shell" or anything like that)? What OS are you using? Also, can you post what all you are seeing on the screen (i.e., what you typed in and what got returned) or even a screenshot?

How did the fresh/formatted MicroSD card change things?
Also can you "ADB Pull" files from your phone to your PC?

ianmcquinn said:
And you typed in no other commands prior (e.g., no "adb shell" or anything like that)? What OS are you using? Also, can you post what all you are seeing on the screen (i.e., what you typed in and what got returned) or even a screenshot?
Click to expand...
Click to collapse
Well i typed in "adb shell" to get into the console

b1ackhawk said:
Well i typed in "adb shell" to get into the console
Click to expand...
Click to collapse
That's the problem then. ADB push/pull commands cannot be done from within the ADB shell command prompt. ADB shell is the equivalent of running Terminal on your phone itself. Do not start with ADB shell and you should be fine (none of the guides say to run the "adb shell" command first either).

raitchison said:
How did the fresh/formatted MicroSD card change things?
Also can you "ADB Pull" files from your phone to your PC?
Click to expand...
Click to collapse
havent found my spare card yet. although i cant push system memory either, which needs to be solved.
adb pull also gives me "permission denied"

ianmcquinn said:
That's the problem then. ADB push/pull commands cannot be done from within the ADB shell command prompt. ADB shell is the equivalent of running Terminal on your phone itself. Do not start with ADB shell and you should be fine (none of the guides say to run the "adb shell" command first either).
Click to expand...
Click to collapse
DOH! I knew it was going to be some stupid step i did wrong. Ive done this before, but obviously too long ago (tmo G1)... Huge thanks for being able to deconstruct my backwards thinking.

[Q] htc desire drivers.

Hi guys what is the easiest way to check if i have installed the adb drivers or something like that.Thx

open console ('cmd' in windows) and type 'adb', while your phone is plugged to computer. If it'll write many lines of help about adb you have it installed. And then plug your phone and typa 'adb devices' if it'll write 'list of devices attached'
and your phone serial number, you've got htc drivers installed.

StylishPirat said:
open console ('cmd' in windows) and type 'adb', while your phone is plugged to computer. If it'll write many lines of help about adb you have it installed. And then plug your phone and typa 'adb devices' if it'll write 'list of devices attached'
and your phone serial number, you've got htc drivers installed.
Click to expand...
Click to collapse
If your computer is like mine, cmd will want adb.exe and adbwinapi.dll in the path you are using.
e.g. If adb is setup in
Code:
c:/android-sdk/tools
and your cmd path is (what it often is)
Code:
c:\users\username
then it will not work, so you have to specify the correct path using
Code:
cd [path for adb.exe]

Unless you add it to your windows environment variables first
Sent from my HTC Desire using Tapatalk

Forgot to transfer ROM

I tried to root my Nexus to get Jellybean...all went well till I realized I forgot to get the ROM onto the phone.
I made a backup onto the computer but didn't do it after I booted into clockwork mod. I wiped the cache etc. and installed the Gapps and that is when I realised the ROM wasn't on the phone. My phone wont connect to the computer and the only backup I have is on my computer.
Is there a way to get the stock ICS on the phone or somehow get the JB ROM onto my phone?

Not an expert, but fastboot and flash stock???
Sent from my Galaxy Nexus using Tapatalk 2

If your phone is recognized by the PC, push the ROM with ADB. You can then flash it.
Code:
adb push rom-file.zip /sdcard/
Alternatively if you just want to return to stock, flash the images via fastboot: http://forum.xda-developers.com/showthread.php?t=1626895

martonikaj said:
If your phone is recognized by the PC, push the ROM with ADB. You can then flash it.
Code:
adb push rom-file.zip /sdcard/
Alternatively if you just want to return to stock, flash the images via fastboot: http://forum.xda-developers.com/showthread.php?t=1626895
Click to expand...
Click to collapse
Phone is not recognized by the computer. It tries to install the driver then says it can't.

adb push it.
You can adb push from a custom recovery (CWM)

Jubakuba said:
adb push it.
You can adb push from a custom recovery (CWM)
Click to expand...
Click to collapse
I can't find the AndroidSDK folder on my computer at all...
edit-
downloaded and installed Android SDK.
edit-
got to cmd....I get to the point where I need to adb push but I get this message: 'adb' is not recognized as an internal or external command, operable program or batch file.
and on cwm, I can't toggle the /sdcard to unmount. It stays on mount.

cwpmz3 said:
I can't find the AndroidSDK folder on my computer at all...
edit-
downloaded and installed Android SDK.
edit-
got to cmd....I get to the point where I need to adb push but I get this message: 'adb' is not recognized as an internal or external command, operable program or batch file.
and on cwm, I can't toggle the /sdcard to unmount. It stays on mount.
Click to expand...
Click to collapse
You need to be in the sdk folder where the adb.exe is located, and the file you want to push must be in the same folder aswell.
Swype'ed on my CM10 Galaxy Nexus

cwpmz3 said:
I can't find the AndroidSDK folder on my computer at all...
edit-
downloaded and installed Android SDK.
edit-
got to cmd....I get to the point where I need to adb push but I get this message: 'adb' is not recognized as an internal or external command, operable program or batch file.
and on cwm, I can't toggle the /sdcard to unmount. It stays on mount.
Click to expand...
Click to collapse
Open the directory where you put the adb.exe file. Shift+Right Click the blank screen. Click Run Command Prompt Here. Now you should be able to use adb and all its commands when your phone is in recovery mode and connected to computer. Just to make sure, you can always do "adb devices" to check it the phone is recognized.
Also make sure that the ROM you want to transfer is in the same directory as adb.exe.
After you've done that, do "adb push NAME OF THE ROM.zip /sdcard/"
Now use CWM to flash that zip file and you're good to go.

Thanks everyone! Got it working!
Definitely made my heartdrop before haha but man I learned a lot haha again, Thanks!:good:

[Q] Code?

My KF is bricked. It has TWRP on it but it has been wiped clean and my pc will not recognize it. It does in ADB, I keep seeing write the CODE: then stuff. I was told I could to where I needed to write this code by right clicking on the KFU Tools folder. I then get C:\android\Kindle Fire Utility>
Now that being said.. where do I begin to type the fastboot -i Ox1949 and so on. Sure do need some much appreciated help assistance.

Boot into TWRP and then do what Josepho1997 said. Then you can just flash the rom.
The "Rom.zip" would be the file path to wherever the rom is saved on your computer.

Where can I write the tag
Josepho1997 said:
So you just have no OS?
Boot into TWRP. Then Download and transfer the ROM via adb
Code:
adb push Rom.zip /sdcard
Then flash the ROM.
Sent from my Kindle Fire
Click to expand...
Click to collapse
But where do I code?

adb in cmd not recognized as a command
Josepho1997 said:
In cmd. Open up cmd, run adb, and then type that code. And remember what veeman said. When I say Rom.zip, you must put both the correct name and directory applicable to you. (Ex. C:\AlienDroid.zip)
Sent from my Kindle Fire
Click to expand...
Click to collapse
in cmd, adb is not recognized as a internal or external command, operable program or batch file.
Know how long it's been since I used cmd. Help me out please.

You need to open the cmd window when you are in the directory that contains the adb.exe file. Usually this is in C:/kfu/tools directory. The easiest way to do that is to use windows explorer and navigate to that directory then press shift and right click your mouse then select the option "open command window here". You should now be able to issue adb commands.
Sent from my Amazon Kindle Fire using Tapatalk 2

nacraracer said:
in cmd, adb is not recognized as a internal or external command, operable program or batch file.
Know how long it's been since I used cmd. Help me out please.
Click to expand...
Click to collapse
Easiest way is to download the Kindle Fire Utility and then navigate to the tools directory in the command line. Then you can run adb and fastboot commands.

Still won't communicate
veeman said:
Easiest way is to download the Kindle Fire Utility and then navigate to the tools directory in the command line. Then you can run adb and fastboot commands.
Click to expand...
Click to collapse
I have tried everything to get the computer to see the kindle. adb commands are not working. Just says waiting on device, tried to adb push a rom and it just said device not found.
I was able to bring up a fastboot menu one time but once there it wouldn't respond.
Any ideas please.
I am looking at the TWRP v2.2.0 screen. It will not mount either

nacraracer said:
I have tried everything to get the computer to see the kindle. adb commands are not working. Just says waiting on device, tried to adb push a rom and it just said device not found.
I was able to bring up a fastboot menu one time but once there it wouldn't respond.
Any ideas please.
I am looking at the TWRP v2.2.0 screen. It will not mount either
Click to expand...
Click to collapse
Have you installed the drivers?

veeman said:
Have you installed the drivers?
Click to expand...
Click to collapse
I did install the google drivers at the fire tool kit