Need help with my EVO - EVO 4G Q&A, Help & Troubleshooting

Alright so last night i ran the DCupdater and saw the damagecontrol v3.1.2 update. So i downloaded it and tried running that. Thats when my evo started freaking out and the sd card kept getting disconnected. After all that nonsense it got installed. But then as my phone restarted it was in for the loop of watching the HTC EVO 4G logo. Thats when i tried going to one of my backups and that seemed to work. So then after that i when back to damagecontrol v3. But that messed everything up even more because now im stuck on v3 without sd card. When i try going into the bootloader it wont let me. When i hook up the phone to my pc via usb it wont let me see the sd card contents. I tried doing the:
fastboot oem enableqxdm 0
fastboot reboot
but that had no effect and the cmd wouldnt even recognize the command
what do i do?

xarttyx said:
Alright so last night i ran the DCupdater and saw the damagecontrol v3.1.2 update. So i downloaded it and tried running that. Thats when my evo started freaking out and the sd card kept getting disconnected. After all that nonsense it got installed. But then as my phone restarted it was in for the loop of watching the HTC EVO 4G logo. Thats when i tried going to one of my backups and that seemed to work. So then after that i when back to damagecontrol v3. But that messed everything up even more because now im stuck on v3 without sd card. When i try going into the bootloader it wont let me. When i hook up the phone to my pc via usb it wont let me see the sd card contents. I tried doing the:
fastboot oem enableqxdm 0
fastboot reboot
but that had no effect and the cmd wouldnt even recognize the command
what do i do?
Click to expand...
Click to collapse
before you enter those commands you have to hold power and volume down and go into fastboot on the phone - after that connect it to the computer
click start - run - CMD
After that
type cd "location of your android sdk tools folder" - OR cd "drag the folder of your tools folder into the prompt"
THAN
type the commands -
fastboot oem enableqxdm 0
fastboot reboot

mongoose8p said:
before you enter those commands you have to hold power and volume down and go into fastboot on the phone - after that connect it to the computer
click start - run - CMD
After that
type cd "location of your android sdk tools folder" - OR cd "drag the folder of your tools folder into the prompt"
THAN
type the commands -
fastboot oem enableqxdm 0
fastboot reboot
Click to expand...
Click to collapse
where do i find that folder... im sorry i dont really know much of this

i'm assuming you are using windows. it's the location of your \android-sdk-windows\tools\ folder from when you installed the android sdk in order to root in the first place. it is also the location of adb. if need be, do a search for adb.exe and it should point you directly to the location of everything you need.

It keeps saying "the system cannot find the path specified". I dont even know what to do. This sucks.

it might be under a different path, where did u install ur android sdk?

i don't really remember. i found it though searching for adb and i guess i have 2 folders of it... zipped and unzipped... but i tried putting both path names in there and that went nowhere

When you search for adb or your android sdk tools folder, go into that folder and hit Shift+right click and "open command window here" then use your commands.

awesomeindeed said:
When you search for adb or your android sdk tools folder, go into that folder and hit Shift+right click and "open command window here" then use your commands.
Click to expand...
Click to collapse
that option does not pop up.. im running xp if that helps

im still having trouble figuring out what to do.

xarttyx said:
that option does not pop up.. im running xp if that helps
Click to expand...
Click to collapse
copy the path of the folder with adb.exe in it - start - run cmd - command "cd path of adb folder" - then follow the instructions above

Related

Need Help Entering Commands

Hi Guys,
I am new to this stuff and I am having problems with entering commands for certain stuff.
So, I rooted my Desire and I wanna change the virgin mobile boot image that comes up after the white HTC screen during the booting process and I found the info on the forums here but I am just not getting the last part.
I get into the recovery and all that but where do I type in this command? I tried using the run function on my PC and typed in cmd to open a Command Prompt but after that if I type that stuff in, it doesn't work.
I'd really appreciate if someone can help because it seems like this typing command stuff seems necessary in a lot of the things that I'd like to do with my phone.
Thnx in advance
--------------
How to change boot animation
1. You need to have HTC Sync and Android SDK installed
2. Copy bootanimation.zip to SD Card
3. Turn off Desire and then turn it on while holding back button to enter bootloader(white screen)
4. Once in "white screen" press power button again to enter bootloader
5. Connect Desire with PC
6. Press Volume Down and than Power to enter Recovery
7. Open Command prompt/Terminal and type
Code:
adb shell mount /system
adb push C:\bootanimation.zip /data/local
adb reboot
-----------------
Try the following, may be easier for you:
get adb running (download & extract the sdk, it will be in the tools folder)
the full path will be C:\android-sdk-windows\tools
add adb to path
put bootanimation.zip into the same folder as the adb app (e.g. in the tools folder of the sdk)
open cmd & navigate to the tools folder
adb push bootanimation.zip /data/local
Hey man,
I really appreciate it but I guess I am just not as advanced as some of you guys and your instructions are still not too clear for me. I tried to do what you told me but no luck, so I am guessing I am obviously not doing something right.
Ok, so I got the SDK and extracted but I am not sure what you mean by "Get adb running". Are you referring to the adb.exe file in the tools folder?
And, when I am following your instructions, what stage my phone should be on? In the recovery with the triangle and the ! or just turned on normally?
Sorry for all the hassle man but I really appreciate your help. I am just trying to get a hang of this.
Dodolom said:
Hey man,
I really appreciate it but I guess I am just not as advanced as some of you guys and your instructions are still not too clear for me. I tried to do what you told me but no luck, so I am guessing I am obviously not doing something right.
Ok, so I got the SDK and extracted but I am not sure what you mean by "Get adb running". Are you referring to the adb.exe file in the tools folder?
And, when I am following your instructions, what stage my phone should be on? In the recovery with the triangle and the ! or just turned on normally?
Sorry for all the hassle man but I really appreciate your help. I am just trying to get a hang of this.
Click to expand...
Click to collapse
No, the phone does not need to be in recovery but it needs to be turned on and connected via USB
Open command prompt and type cd C:\android-sdk-windows\tools, hit enter.
Next, type adb, hit enter.
Now, having placed the bootanimation.zip file in the adb SDK tools directory, push it to the phone:
Type adb push bootanimation.zip /data/local in command prompt.
Note: Make sure USB Debugging is enabled on your phone:
Go to Settings on your phone > Select Applications > Select Development > Make sure 'USB Debugging' is checked
thank you so much man. Worked like a charm.
No problem man, its only easy when you know how
Regards,
Mas.
-------------------------------------
Sent via the XDA Tapatalk App
Can be better for all user create the bootanimation.zip inside a update.zip for only flash it. Users not asking, users without problems

[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!

can someone help me with adb

ive tried many guides on trying to install adb. i have the drivers installed but nothing is happening when i try to use sdk tools. can anyone help me?
It doesn't really "install," it just resides in a folder on your computer. When you want to use ADB, you just pass the commands through your Windows command prompt (assuming you're using Windows).
Put the Android SDK file in the root of your C: drive. In fact, make it easy and rename it "androidsdk." Inside that is the "tools" folder. Now hit Start - Run - cmd and it will start your command prompt. Then enter "cd c:\androidsdk\tools" (no quotes) and hit enter. Now you're in the ADB directory, just start running ADB commands.
Right?
whatever command i try to type in says its not a recognized internal or external command.
Can you run throught the steps you took?
These are mine:
1. Connect phone and select HTC Sync
2. Make sure you know the location patch to the android-sdk-windows(if you're using windows) folder.
3. Press start........run........then type cmd to open command prompt
4. Type cd C:\android-sdk-windows\tools(my location, yours will be wherever you extracted the zip file to)
5. Press enter
6. Type adb devices to confirm it sees your phone
7. Type adb shell and you should see a flashing # symbol
8. Start typing commands.
when i connect my phone and try to sync using htc sync it cant find it on my comp.
Do you have USB Debugging turned on?
And by the way, you don't need to set it to HTC Sync. You may have to make sure the drivers are installed correctly (I suggest TheBiles' Idiot-Proof rooting guide for that), but after that it will connect as long as you have debugging mode turned on, even if your phone is set to "Charge Only." I never put mine in "Disk Drive" mode unless I want to drag a file to my SD card, and I've never ONCE used HTC Sync.
ok thank you, so far so good. im busy doing some other work but the adb shell seems to be working. will edit later.
Edit: nvm that.

[Q] sdk device not found

Well I want to command my htc desire from cmd but I am not beeing successful.
I type/get (phone in Fastboot mode):
c:\Program Files\Android\android-sdk\platform-tools>adb devices
List of devices attached
c:\Program Files\Android\android-sdk\platform-tools>adb shell
error: device not found
This what I have in Windows "Device Manager" ADB Interface (Installed correctly did not have any "Yellow exlamation icon"):
"Android Bootloader Interface"
any ideas?
Yes, ignore that as mine too said the same. Here's my instructions that I recorded so that I can remember (old age) :-
Put phone into fastboot mode (back button + power)
In CMD, go to dir C:\Android\android-sdk\Tools
Type: path C:\Android\android-sdk\Platform-tools)
Click to expand...
Click to collapse
Note that mine is not located in the 'Program Files' directory so you will need to change that to suit. From there you should be able to run fastboot commands. The 'path' command I had to set due to ADB being in a different directory to Fastboot so running any fastboot commands failed as it was looking to use ADB which doesn't reside in the same directory.
If you are using fastboot, you want to type
Code:
fastboot devices
rather than adb devices. ADB is for use when the phone is normally booted rather than in bootloader/fastboot.
parva, i tried that but nothing changed
C:\sdk\tools>fastboot reboot-bootloader
< waiting for device >
C:\sdk\tools>fastboot devices
and nothing... happens ... My device is there! (Android Bootloader Interface)
more ideas?
Try a different USB cable?
Or another usb port. And make sure you installed all necessary drivers correctly.
Sent from my HTC Desire using XDA App
Why should i try another cable if with this cable I transfer files, windows check all drivers etc... already tried in another pc -.-
what should i see on device manager for the htcdesire device when it is on fastboot?
maybe try using safe mode (if using windows) it could be a firewall or a program blocking the connection
but tell me what should I see on device manager when my htc is on fastboot
portelaux said:
parva, i tried that but nothing changed
C:\sdk\tools>fastboot reboot-bootloader
< waiting for device >
C:\sdk\tools>fastboot devices
and nothing... happens ... My device is there! (Android Bootloader Interface)
more ideas?
Click to expand...
Click to collapse
Are you sure that everything is in that directory? Only by default it installs to 'C:\Program Files\Android', I simply removed the 'Program Files' directory but you haven't even got an 'Android' directory now. Reinstall it and start again maybe, using defaults. You're directory structure may or may not be the issue here but we could be here until this time next year fixing something that is unrelated.
Reinstall the SDK and only remove the 'Progam Files' part of the directory then follow my instructions again.
portelaux said:
but tell me what should I see on device manager when my htc is on fastboot
Click to expand...
Click to collapse
If all is well, when you type "fastboot devices" in your terminal window , you should see something of this format, meaning your connection is good.
"fastboot H3567FYH5577"
Copy the content of Platform-tools to tools. And try ADB that way - if the drivers are correctly installed it should work.
And you must have the USB Debugging option enabled (settings> applications> developement).
Well thanks you all anyway...
My sdk device control started working ^^ ... i dont know why but if already find devices etc
thanks you all
portelaux said:
Well thanks you all anyway...
My sdk device control started working ^^ ... i dont know why but if already find devices etc
thanks you all
Click to expand...
Click to collapse
Please add "[SOLVED]" to topic's title, to help other users.

Wiped Phone Now Can't See SD Card On Lappy, PLEASE HELP

I used Team win Recovery Project to wipe my phone Galaxy Nexus, and now when I plug the phone in to the lappy it doesn't show the sd card. Freaking out here cause I can't copy over a zip file to flash a ROM... please help...
The GNEX doesn't have an actual sdcard, so when you wiped the phone i'm guessing you wiped the virtual sd card.
You will have to adb push a rom to your phone.
One the top of the first Q&A page jubakuba has a guide that has a panic section in it.
The guide also shows how to install adb/fastboot and gives you the commands.
try flash the stock img via fastboot using the following line to avoid wiping ur sdcard
fastboot update ***.zip
then wipe data via CWM and enjoy
xskordeal said:
try flash the stock img via fastboot using the following line to avoid wiping ur sdcard
fastboot update ***.zip
then wipe data via CWM and enjoy
Click to expand...
Click to collapse
sorry, complete DOLT here. Where would I input the command?
If you don't know about adb/fastboot, do as suggested in first post. All is explained in the guide.
How to get to a MS-DOS prompt or Windows command line
TheDodgey said:
sorry, complete DOLT here. Where would I input the command?
Click to expand...
Click to collapse
Click Start.
Click Run.
Type cmd or command and press enter.
gpfnzl said:
If you don't know about adb/fastboot, do as suggested in first post. All is explained in the guide.
Click to expand...
Click to collapse
ok, following your instructions, and the instructions of the link, I have install ADB and can use cmd, however when I type adb shell, I get an error returning "device not found"
I see a lot of threads stating to make sure usb debugging is on, it was before I wiped the phone, but obviously I cant get to any settings at the moment.
on the verge of crying now, and noone likes to see a grown man cry
FIXED
I ran the push command whilst in recovery and it worked
not sure that it mattered, but I did change the zip file name to ROM.zip, and whilst in recovery, ran the comand "adb push ROM.zip /sdcard/ROM.zip
Just thought I would put that in there for other dopes like me that might come across this problem
Thanks to all for your help!
LOL
Normally if you can't see your device listed you haven't installed the drivers correctly.(or the correct drivers)
Also you have to open a command prompt window in the same folder as fastboot.exe and adb.exe
To do this in Windows 7:
Click the windows start button (bottom left hand corner)
In the search bar at the bottom type: cmd
At the top of the search list you will see the program cmd.exe right click and copy it.
Paste it into the same folder that has fastboot.exe and adb.exe
Now you can open the cmd window and type the command:
adb devices
Hit ENTER and if you have installed drivers correctly, the serial number of your phone will be listed.
If not, uninstall the drivers, download a new set of drivers from jubakuba or efrants guide and reinstall.
---------- Post added at 11:58 AM ---------- Previous post was at 11:53 AM ----------
TheDodgey said:
FIXED
I ran the push command whilst in recovery and it worked
not sure that it mattered, but I did change the zip file name to ROM.zip, and whilst in recovery, ran the comand "adb push ROM.zip /sdcard/ROM.zip
Just thought I would put that in there for other dopes like me that might come across this problem
Thanks to all for your help!
Click to expand...
Click to collapse
didn't need to change the name of the rom zip. Just needed to type the full name of the .zip file.
Good to see it worked, and the tears have stopped

Categories

Resources