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!

Adb in TWRP recovery

I have always been able to get ADB working over USB in Clockwork Recovery. Recently I tried out TWRP as an alternative, and I really like it, but I couldn't get ADB to work. Is that just not available in TWRP, or are there other drivers I need to install? Or is there an option I need to enable?
Sent from my Galaxy Nexus using Tapatalk 2

cmstlist said:
I have always been able to get ADB working over USB in Clockwork Recovery. Recently I tried out TWRP as an alternative, and I really like it, but I couldn't get ADB to work. Is that just not available in TWRP, or are there other drivers I need to install? Or is there an option I need to enable?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
It should work... What driver are you using?

Mount /data?
Make sure your pushing to /data/media?
Is adb not working period like adb devices returns nothing or it won't push?
Sent from my Galaxy Nexus

Also could you do adb devices? This will show if the adb detects your phone or not. If you see a serial number, then the adb recognizes your phone and you're doing something wrong ( such as wrong command or won't directory)
Swyped on my Galaxy Nexus running AOKP with Franco Kernel

ADB devices works when booted into the OS, and works from CWM. I get nothing listed under ADB devices when in TWRP.
I'm using whatever drivers I installed when I first bought my GNex.
It's TWRP v 2.3.1.0, installed from the Goo Manager app.
EDIT: Odd, I unplugged/replugged the phone and now it does show up in recovery. Maybe it doesn't click in if I reboot with the phone attached.

Let me further amend... it does not appear on adb devices until I open up Windows Device Manager and tell it to scan for hardware changes. Then after about a minute the phone appears in adb devices.
With CWM it appears instantly in adb devices, no delay.

well, post your issue in TWRP [email protected] section

bk201doesntexist said:
well, post your issue in TWRP [email protected] section
Click to expand...
Click to collapse
Where is that thread? I'm also facing the same issue in my ZTE V970M...
Nevermind, sorry for the necroposting. I solved it by installing ZTE Composite ADB Device in the C:\Program Files\ZTE <whatever>\Driver\amd64 folder. Using Win8 x64 btw.

[q] SOLVED: ADB ROM PUSH ERROR: DEVICE NOT FOUND

EDIT:
I was trying to reflash JB 4.3 because of storage issues but unfortunately I accidentally deleted and formatted internal and sd storage, so Im left with no OS on my Gnex but I can boot on recovery and fastboot. Also before I deleted the internal I did not enable usb debugging yet at that time. Is there a way I can flash a stock image by just using toolkit? ty
I tried pushing through fastboot mode but it says error: device not found. I only have the platform tools on my pc.
UPDATE:
Finally got the file pushed into the sd card doing via recovery. Since I am using TWRP recevery it was not too obvious how to do it unlike CWRM which I used to use. I spent more than 24 hours looking for the right solution that would work for me and funny thing was I finally got the right way to one of the first threads i looked into but just didnt pay much attention to it which was here http://forum.xda-developers.com/showthread.php?t=1667929
"Boot your phone into Recovery and select the "Mounts & Storage" screen
- Plug your phone into your computer using USB Data Transfer Cable
- Ensure in Recovery that your phone shows "Unmount /sdcard/" and "Unmount /system/" (If they do not show this automatically, just press each one once respectively as pressing just toggles Mount and Unmount)
- Open Command Prompt on your computer by doing Start -> Run -> cmd
- In Command Prompt, type "cd c:\AndroidSDK\tools" replacing AndroidSDK\tools with wherever your adb and ROM are located.
- This is probably the most important part - Still in Command Prompt, type "adb push ROM.zip /sdcard/ROM.zip" replacing ROM with the EXACT name of the ROM file and including the .zip piece on both ends. This may take a minute or two...or four, but you will see a message in Command Prompt saying something like <12345678kb to 1234567kb>. That is just telling you that the file was pushed properly. (I did not include that message in the picture below)"
lastforone said:
Instead of using a toolkit, just push a rom to ur sdcard using adb and flash it via recovery.. Or you can download the official image, boot into fastboot and flash it..
-
L4.1
Click to expand...
Click to collapse
You were right on spot unfortunately I didnt know how to do it. Thank you anyways...:highfive::highfive::highfive:
Ty for all those who tried to help me, thank you for the effort, well it was indeed a learning experience... ahihihihi

Instead of using a toolkit, just push a rom to ur sdcard using adb and flash it via recovery.. Or you can download the official image, boot into fastboot and flash it..
-
L4.1

lastforone said:
Instead of using a toolkit, just push a file to ur sdcard using adb and flash it... Or you can download the official image, boot into fastboot and flash it..
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
well then i need to download sdk first ty anyways

lolobabes said:
well then i need to download sdk first ty anyways
Click to expand...
Click to collapse
You do not need the whole sdk package. Just the adb + fastboot and few required files ... You can find the zip in erants guide..
Sent from my Galaxy Nexus using xda app-developers app

when i tried to push error device not found lol

lolobabes said:
when i tried to push error device not found lol
Click to expand...
Click to collapse
Use adb sideload from twrp and send the zip from your PC to your phone.
Sent from my Galaxy Nexus using xda app-developers app

lolobabes said:
when i tried to push error device not found lol
Click to expand...
Click to collapse
Go into your device manager if you have windows, and see if you have any errors.
If you do, you might have an exclamation mark for the device: Galaxy. You can manually install the drivers from here, point it to your toolkit, I guess, since you downloaded it already.

If he reads efrant's "android 101" -which is STICKIED ON GENERAL forum- just the first post, he'll know everything and downloaded everything he needs to know and have to interact with his device.
a manta wrote this.

Beauenheim said:
Go into your device manager if you have windows, and see if you have any errors.
If you do, you might have an exclamation mark for the device: Galaxy. You can manually install the drivers from here, point it to your toolkit, I guess, since you downloaded it already.
Click to expand...
Click to collapse
When I am on recovery yes theres an exclamation on samsung mtp device but in fastboot mode the samsung mtp does not appear but when I do fastboot devices there appears a device number so I thought I can do it on fastboot. thank you.
beekay201 said:
If he reads efrant's "android 101" -which is STICKIED ON GENERAL forum- just the first post, he'll know everything and downloaded everything he needs to know and have to interact with his device.
a manta wrote this.
Click to expand...
Click to collapse
I have read that already however I was hoping to just flash a file to the sdcard if is even possible considering I have formatted both internal and sdcard. I am very new to adb so its an easier way for me. But it seems then I will ave to do it the hard way. Thanks
PS
Not sure if this has any bearing but when I accidentally formated internal and sdcard it was a fresh 4.3 install and so android debugging was not enabled. Thanks

lolobabes said:
PS
Not sure if this has any bearing but when I accidentally formated internal and sdcard it was a fresh 4.3 install and so android debugging was not enabled. Thanks
Click to expand...
Click to collapse
Doesn't matter because if you reboot in bootloader you can use fastboot(if drivers are installed properly), fastboot always works, you don't need to enable anything for it.

sui785 said:
Doesn't matter because if you reboot in bootloader you can use fastboot(if drivers are installed properly), fastboot always works, you don't need to enable anything for it.
Click to expand...
Click to collapse
So meaning I can use fastboot to just push file to sdcard right? Tried to look for the right command but I cant seem to find the right one that works for me. Thank you.

tried doing this in fastboot "adb push romname.zip /sdcard/ROM/" had this error: device not found

lolobabes said:
tried doing this in fastboot "adb push romname.zip /sdcard/ROM/" had this error: device not found
Click to expand...
Click to collapse
Take it out of a USB 3.0 port.

lolobabes said:
tried doing this in fastboot "adb push romname.zip /sdcard/ROM/" had this error: device not found
Click to expand...
Click to collapse
lolobabes said:
So meaning I can use fastboot to just push file to sdcard right? Tried to look for the right command but I cant seem to find the right one that works for me. Thank you.
Click to expand...
Click to collapse
no, there's no ADB interface on FASTBOOT interface. You'll never be able to push anything through ADB in FASTBOOT interface. Please read the thread i talked about earlier, and this one too -> http://forum.xda-developers.com/showthread.php?t=1626895 - Just the first post of each will do.
Beauenheim said:
Take it out of a USB 3.0 port.
Click to expand...
Click to collapse
*EPIC*
*facedesk*
*grows more white hair*

xD I actually had this issue a few days ago, had issues for 4 hours, realized I had my cord plugged in a 3.0 port.
Really dumb noob moment.

UPDATE:
Finally got the file pushed into the sd card doing via recovery. Since I am using TWRP recevery it was not too obvious how to do it unlike CWRM which I used to use. I spent more than 24 hours looking for the right solution that would work for me and funny thing was I finally got the right way to one of the first threads i looked into but just didnt pay much attention to it which was here http://forum.xda-developers.com/showthread.php?t=1667929
"Boot your phone into Recovery and select the "Mounts & Storage" screen
- Plug your phone into your computer using USB Data Transfer Cable
- Ensure in Recovery that your phone shows "Unmount /sdcard/" and "Unmount /system/" (If they do not show this automatically, just press each one once respectively as pressing just toggles Mount and Unmount)
- Open Command Prompt on your computer by doing Start -> Run -> cmd
- In Command Prompt, type "cd c:\AndroidSDK\tools" replacing AndroidSDK\tools with wherever your adb and ROM are located.
- This is probably the most important part - Still in Command Prompt, type "adb push ROM.zip /sdcard/ROM.zip" replacing ROM with the EXACT name of the ROM file and including the .zip piece on both ends. This may take a minute or two...or four, but you will see a message in Command Prompt saying something like <12345678kb to 1234567kb>. That is just telling you that the file was pushed properly. (I did not include that message in the picture below)"
lastforone said:
Instead of using a toolkit, just push a rom to ur sdcard using adb and flash it via recovery.. Or you can download the official image, boot into fastboot and flash it..
-
L4.1
Click to expand...
Click to collapse
You were right on spot unfortunately I didnt know how to do it. Thank you anyways...:highfive::highfive::highfive:
Ty for all those who tried to help me, thank you for the effort, well it was indeed a learning experience... ahihihihi

lolobabes said:
UPDATE:
Finally got the file pushed into the sd card doing via recovery. Since I am using TWRP recevery it was not too obvious how to do it unlike CWRM which I used to use. I spent more than 24 hours looking for the right solution that would work for me and funny thing was I finally got the right way to one of the first threads i looked into but just didnt pay much attention to it which was here http://forum.xda-developers.com/showthread.php?t=1667929
"Boot your phone into Recovery and select the "Mounts & Storage" screen
- Plug your phone into your computer using USB Data Transfer Cable
- Ensure in Recovery that your phone shows "Unmount /sdcard/" and "Unmount /system/" (If they do not show this automatically, just press each one once respectively as pressing just toggles Mount and Unmount)
- Open Command Prompt on your computer by doing Start -> Run -> cmd
- In Command Prompt, type "cd c:\AndroidSDK\tools" replacing AndroidSDK\tools with wherever your adb and ROM are located.
- This is probably the most important part - Still in Command Prompt, type "adb push ROM.zip /sdcard/ROM.zip" replacing ROM with the EXACT name of the ROM file and including the .zip piece on both ends. This may take a minute or two...or four, but you will see a message in Command Prompt saying something like <12345678kb to 1234567kb>. That is just telling you that the file was pushed properly. (I did not include that message in the picture below)"
You were right on spot unfortunately I didnt know how to do it. Thank you anyways...:highfive::highfive::highfive:
Ty for all those who tried to help me, thank you for the effort, well it was indeed a learning experience... ahihihihi
Click to expand...
Click to collapse
I'm glad you sorted it out, that's the thing instead of teaching you step by step just left a hint on what you should do, helps you learn to do it on your own..
Peace,
L4.1

Thanks
Thanks for this. Was stuck with no factory image because had to wipe data because of encryption. Then was in dilemma of how to load the ZIP to sdcard without having to reflash the stock all over. This saved me the time. Thanks again

adb issues. tough case.

ok, I am really in dead end here. I think I spent on it more than 4 days, trying to figure it out. No luck, hopefully someone here can help.
My One isn't recognized under adb fastboot. And what I mean: under device managers it shows that the device is installed fine ( no yellow exclamation marks ). But when I try to adb, no luck. No devices recognized.
wait.. before you refer me to gadzillions of links - I've been there, seen them. What I did so far:
1) Installed linux ( live cd and normal ). When in the OS, I can browse my sd card. Once I reboot into fastboot, adb devices returns empty list.
2) installed htc drivers, naked drivers, universaladb drivers, intel usb3 drivers ( tried on both usb2 and usb3 ports )
3) various laptops and pcs
no luck. I am running out of ideas. What am I missing ? pliz help, I am desperate to adb to update recovery.
PS. Tried that on windows 7, 8, 8.1 and linux

If your just trying to update your recovery you can use flashify from the playstore.
https://play.google.com/store/apps/details?id=com.cgollner.flashify&hl=en

mercer24 said:
If your just trying to update your recovery you can use flashify from the playstore.
https://play.google.com/store/apps/details?id=com.cgollner.flashify&hl=en
Click to expand...
Click to collapse
checking it right now. thank you

ah, didn't work. But thank you for help. Returning the phone to the store today.. ehhh..

pRuben said:
ah, didn't work. But thank you for help. Returning the phone to the store today.. ehhh..
Click to expand...
Click to collapse
I don't recall seeing it mentioned in any of the recipes, cookbooks or how-to postings, but I found that in Linux, you should run your adb and fastboot instructions either logged in as root, or using sudo.

Make sure you don't have any phone software installed on the computer as well. HTC sync and Kies can cause problems with adb. Also make sure that adb debugging is turned on in developer settings. You probably already did that, but ya never know, I overlook the simple stuff all the time.

did you take 4.3 update
If you did I have same issue with adb but fastboot options work just fine as long as your s-off if you need any help let me know i went and reloaded hboot and a cwm and also wrote my cid to super and unlocked through htc dev then changed my cid back to verizons

thanks guys, yep, HTC sync manager was installed /uninstalled. Not sure what what's kies. Also I executed sudo on linux. Nothing freaken works. I am s-off unlocked via sonic. Drives me insanely mad. Seems like this phone just refuse to work with me.

I know this might seem like a dumb idea but have you tried a different cable? Are you using the one that came with the phone?

I don't know you so forgive me if what follows is too simplistic or unrelated to your issue. Just trying to help.
You mentioned your phone is not recognized "under adb fastboot." Do you mean under neither adb nor fastboot?
Are you trying to use adb from the bootloader? The reason I ask is you mentioned that after you "reboot to fastboot," adb devices comes up empty. I assume "reboot to fastboot" means reboot to bootloader, in which case adb commands will not work. Did you try fastboot devices instead?
You also mentioned wanting to get adb working to update recovery, but again this would require fastboot, not adb.
Hope this is the problem as it's an easy fix!
Sent from my HTC6500LVW using xda app-developers app

xenakis said:
I don't know you so forgive me if what follows is too simplistic or unrelated to your issue. Just trying to help.
You mentioned your phone is not recognized "under adb fastboot." Do you mean under neither adb nor fastboot?
Are you trying to use adb from the bootloader? The reason I ask is you mentioned that after you "reboot to fastboot," adb devices comes up empty. I assume "reboot to fastboot" means reboot to bootloader, in which case adb commands will not work. Did you try fastboot devices instead?
You also mentioned wanting to get adb working to update recovery, but again this would require fastboot, not adb.
Hope this is the problem as it's an easy fix!
Sent from my HTC6500LVW using xda app-developers app
Click to expand...
Click to collapse
Once in a while I get humbling experience, that reminds me that simple solutions are right in the front of me Xenakis. You are correct, I was trying to get adb under fastboot, which didn't return anything. Fastboot devices did. From there it was all straight up road to what I needed. Sorry to bother you guys with this, I though it was more complicated that this. It just appears like my ignorance of basic adb commands got the best of me. Thank you for helping me out.
Merry Christmas

HELP - full wiped my phone

_-_

phunkie123 said:
I have the latest version of twrp installed in my phone and thats about it.
I am s-off'd and unlocked.
verizion htc one
ran a full system wipe and that wiped out my .zip rom file along with it.
can someone please help me?
Click to expand...
Click to collapse
You can use adb to push a rom file to you phone storage. I found this link that should help you http://htconeroot.com/htc-one-tutorials/how-to-copy-files-to-htc-one-using-twrp-mount-and-adb/

_-_

adb
phunkie123 said:
i can access the TWRP recovery and also the fastboot. however, when trying to run ADB in my computer the device is not listed.
when running the command "adb devices". nothing gets found.
EDIT - also when i get into the ADB sideload section of TWRP, my device stays stuck at "starting ADB sideload feature..."
Click to expand...
Click to collapse
What is your PC's OS.. Where did you get adb and fastboot??

_-_

Fastboot/adb
phunkie123 said:
My PC's OS is windows 7 home premium service pack 1. the fastboot was unlocked through the firewater method. if you mean the android-sdk tools i got them here
developer.android.com/sdk/index.html?utm_source=weibolife
the fastboot still seems to work as i tried re-flashing TWRP. it was successful. but it still just seems to stay stuck at "Starting ADB sideload feature..."
Click to expand...
Click to collapse
Ok do this move everything from the folder platform-tools should be fastboot.exe and adb.exe and a few other files to the root of your c drive....
than open your CMD window as admin... make sure you open as admin... than type
Code:
cd /
to move to the root of you c dirve and then type
Code:
adb
let me know the out come of that....

_-_

phunkie123 said:
sorry for all your trouble! the reason behind my problems was that my computer needed to be restarted to refresh my drivers. i was then able to mount and push my rom through ADB. whew! thanks so much people! im booting up already. no bricks here! thanks to all of you guys!!
Click to expand...
Click to collapse
Great.... Hate to see anyone have trouble with there m7....Thx lj