Database Develop

Free Screenshots using Dalvik - not rec my phone?

I tried to follow the steps from androidandme to set up my phone for screen shots. I got java, got the android sdk and unzipped everything (nothing was installed?), changed the path under advanced settings, dowloaded eclipse (why not) and all that jazz - full 9 yards.
However, when I run ddms.bat in the tools folder and Dalvik comes up it never recognizes my phone. I have tried with the g1 mounted, unmounted, usb debugging on/off (which I also do not know what this means).
Anyone have any thoughts? I did not get any prompts about drivers and I am mounted to my computer.

Read the guides on how to install ADB.

for some reason when i ever i use ddms to take screen shots, i can't just go to take a screenshot, i have to run a logcat first, it will bring up a popup that says "failed!" i then close that and it runs a logcat, after i do that, then i can use it to take a screen shot.

^^ not sure how that matters but I double clicked the adb.exe file, a dos prompt ran a lot of info and disappeared. Also, your signature has a link to SDK 1.5, not 1.6?
Tried DDMS again with no luck.
^ I tried to do a logcat, failed, SS with no luck... again though, the issue is that my phone is not being identified - it would make sense that it would not work if it doesnt even know my phone is hooked up.
Perhaps I will sleep on it as work is in a few hours. I would appreciate any help I can get.

s15274n said:
^^ not sure how that matters but I double clicked the adb.exe file, a dos prompt ran a lot of info and disappeared. Also, your signature has a link to SDK 1.5, not 1.6?
Tried DDMS again with no luck.
^ I tried to do a logcat, failed, SS with no luck... again though, the issue is that my phone is not being identified - it would make sense that it would not work if it doesnt even know my phone is hooked up.
Perhaps I will sleep on it as work is in a few hours. I would appreciate any help I can get.
Click to expand...
Click to collapse
Sorry if this is not relevant, but I had a ton of trouble until I had the newest jave runtime installed. I never had trouble, got a new laptop at work and had no clue why it would not run. the newest JRE fixed it right up. Maybe not your problem but...
Also I like the program "droid explorer". It has screenshot built in.
EDIT.
I have one more thought...I (always have one more thought) try starting your phone in fastboot (camera and power) then back button when the skaters come up) and see if it asks for drivers then.

s15274n said:
^^ not sure how that matters but I double clicked the adb.exe file, a dos prompt ran a lot of info and disappeared. Also, your signature has a link to SDK 1.5, not 1.6?
Tried DDMS again with no luck.
^ I tried to do a logcat, failed, SS with no luck... again though, the issue is that my phone is not being identified - it would make sense that it would not work if it doesnt even know my phone is hooked up.
Perhaps I will sleep on it as work is in a few hours. I would appreciate any help I can get.
Click to expand...
Click to collapse
adb.exe is a command line application, it doesn't have a GUI. To use an command line app you have to 'cd' to the directory where it's located and enter valid commands. I think you can type 'adb help' for a full list of commands.
Try reinstalling the drivers, it took me a few tries to get it working right on Vista (interestingly no drivers are needed for OS X )

Let me start very basic. Is there any "installing" of the SPK? Or, do I just extract the files? I extracted them and created a directory in PATH like the site said to do.
If there is no installation... are you saying for me to get in dos and just start keying commands, and not using any of the files from the zip?

There is no installation, but EVERYTHING for the sdk is ran in command prompt. Meaning click start, click run, type in cmd, then type cd path/to/your/toolsfolder/ then type adb remount see if it does, if not you NEED TO FOLLOW THE ADB INSTRUCTIONS FOR INSTALLING DRIVERS.

[Q] Trying to backup my EFS folder with SGS Tools and it fails

Trying to be charitable and cautious, I'm trying to back up my EFS folder before I go messing around and it is consistently failing. I'm using:
SGS Tools Vz 0.5.7
Busy Box Vz1.17.2
On my previous captivate this works just fine. Now I get
"could not create backup folder /sdcard/SGSToolbox/backup (date string)" and then the bluebox saying creating backup. This never goes away and to clear I have to reboot.
Any helpful hints?
I tried to download the latest and greatest SGS Tools but Google knows I have it installed and won't let me get the newest one. Haven't figure out how to get around that unless I just have to un-install my current one.
Rooted 2.2, KB2, running existz KB1 kernel.
Knowing there are no successful backups... just successful restores.

If you're willing to use your computer and can get the Android SDK and ADB going, just get into a command prompt in the ADB directory and type "adb pull /efs". That will back it up to your computer.

Or you could open a file explorer and copy the directory from there to your sd card

You could use an app called nitrality
Sent from my SGH-I897 using XDA App

Try to update your su binary, the simpliest way is use Root Explorer to backup whatever u want

Well just to be daring, I tried to install the ADB tools. Had to install the Java development software first. After I installed what I thought was the ADB suite, I can't seem to find the place to type in commands, dumb as that sounds. I may not have gotten the right package. Going to tinker with it though.
My SU is up to date.
I can see the folder with Super Manager so I guess I'll just copy with that. Interesting though I can't see anything in the /efs directory. Probably just something else I don't understand.
Still curious though as to why SGS Tools is failing... part of my nature.
Thanks to all that replied.

Make a note of where adb is installed (e.g. c:\users\person\Android-sdk-windows\platform-tools). Then hit the windows key and R, and type cmd. Once in the prompt, type CD (directory from before, no parentheses) and hit enter. From there, type your adb commands.

Ahhhh.... I get it. Was expecting something a bit more elegant. Gotta love DOS commands.

Well..there are a couple more elegant ways to do it.
Open up a new note in NotePad, just type:
Cmd
Exit
And save, but instead of a .txt file extension save it as a .bat, now drop that into your adb directoty, then just double click on that to open a prompt in that directory, so you don't have to do the cd command every time.
Or..the most elegant way is to add adb to your environmental variables so you can enter adb commands from anywhere

That's a good solution. I've got a set of files put into my C:\Users\(my username) folder called "adb", "adbr" (adb reboot), "adbrd" (adb reboot download), and "adbrr" (adb reboot recovery).
Each of these is a .bat file with a version of this text in it:
@ echo off
cd "C:\Users\(me)\Other\tools\android-sdk-windows\platform-tools"
adb reboot
That way, all I have to do is hit Win-R and type one of those file names and it does that command for me. Or, I can type cmd, then adb, and automatically be where adb is installed without cd'ing through a long file list.

My suggestion is Root Explorer. I was able to backup the EFS directory without problems also create a .tar file.

I used root explorer to do my backups, another option is the explorer inside the rom tollbox aplication its also very good

Now I have another adb question...
First off, now I'm just trying to learn and get better. I've built my bat files and I can get adb working. Thanks to those that helped with that. When I tried to pull the /efs folder it said there was no device recognized. I was in "mass storage" mode at the time.
Whenever I've seen people talk about using adb, I don't recall anything being said about if it should be in Download, debug or what. One of those assumed knowledge things.
So what do I have to do to the phone to let adb recognize it?
gnawing on the bone....
I'm also thinking of pulling a logcat or something when SGS tools fails... just to see. That's my next step.

Enable usb debugging in settings> applications> development

SGS Toolbox doesn't work with efs backups. Are there easier ways to do the backup?

Adb or root explorer.

I did both... just to say I did it and finally got adb working.

[Q] ADB Sideload isn't working for me!

Hello there
I am stuck without a ROM and without a ROM zip file anywhere on the internal device that I can use TWRP to install. The only option I have at the moment is to use adb sideload, and this is my first time doing so.
I downloaded this:
adt-bundle-windows-x86_64-20130522
Anyway, I am trying to follow this tutorial but it's not working out for me:
http://forum.xda-developers.com/showthread.php?t=2317986
It looks simple and easy, but this is the problem I am facing:
"I changed directories to where the adb.exe is (inside platform-tools) and ADB Sideload is already started in TWRP. However, whenever I type "adb devices" it only says "List of attached devices" and nothing under it. Whenever I try flashing the ROM, it says error: device not found. What am I doing wrong here? I even changed the name of the ROM to rom.zip to make it shorter as per a suggestion in the first page of the thread, but that didn't work either."
Can someone please help me and tell me how to make it work? I have been without a ROM for hours waiting for the SDK to download this my internet is pretty slow. Thanks a lot!

Okay now I realize my device isn't actually recognized, although it works fine with fastboot usb.
What do I do? I tried having windows automatically search for drivers but it didn't find anything.

Okay after doing some more reading I realized I never actually opened SDK Manager, and when I try, it just opens a black command prompt window and then shuts down. I then came across this article and realized I need Java JDK drivers before I can actually run SDK Manager and then follow the rest of the tutorial. Maybe that is the problem??

You need HTC drivers , if you didn't install HTC SYNC, open "virtual CD", that appears at connection of phone with PC and you will see folders with drivers for different OS.

Thanks, mate. I already fixed the problem but I forgot to update this thread. You are right, I did not have the proper drivers, so I downloaded and installed HTC Sync Manager and then everything went great.

I had the same problem last night trying to flash my first rom ever, but thankfully i had a usb otg cable that I used to put the rom zip in my flash drive and flash it into the phone

TarekElsakka said:
Hello there
I am stuck without a ROM and without a ROM zip file anywhere on the internal device that I can use TWRP to install. The only option I have at the moment is to use adb sideload, and this is my first time doing so.
I downloaded this:
adt-bundle-windows-x86_64-20130522
Anyway, I am trying to follow this tutorial but it's not working out for me:
http://forum.xda-developers.com/showthread.php?t=2317986
It looks simple and easy, but this is the problem I am facing:
"I changed directories to where the adb.exe is (inside platform-tools) and ADB Sideload is already started in TWRP. However, whenever I type "adb devices" it only says "List of attached devices" and nothing under it. Whenever I try flashing the ROM, it says error: device not found. What am I doing wrong here? I even changed the name of the ROM to rom.zip to make it shorter as per a suggestion in the first page of the thread, but that didn't work either."
Can someone please help me and tell me how to make it work? I have been without a ROM for hours waiting for the SDK to download this my internet is pretty slow. Thanks a lot!
Click to expand...
Click to collapse
Just get the all in one tool, ins;tall the relevant drivers and then go to recovery and select sideload a rom, go to the all in one toolkit and select sideload a rom, then choose the rom, simples
Sent from my Transformer Prime TF201 using xda premium

Thanks, guys. I ordered an OTG USB cable this morning just to avoid any future problems.

[Q] Boot loop and ADB push problems. Please help.

Ok there is a lot info about this however I have a few issues that makes it difficult for me to get past.
I unlocked and rooted just fine. No issues.
I flashed the elemental kernel as I wanted the knock on feature. That was when I ran into problems and my backup doesn't work.
I started getting the "com.htc.htcdailer" isn't responding issue. Then the phone reboots. I am not up long enough to load a rom to flash either.
When I try to sideload anything it doesn't work. I did update all the SDK files like I found in some searches. No go.
I am at a loss now what to do. Any thoughts?
Thanks

mothmansound said:
Ok there is a lot info about this however I have a few issues that makes it difficult for me to get past.
I unlocked and rooted just fine. No issues.
I flashed the elemental kernel as I wanted the knock on feature. That was when I ran into problems and my backup doesn't work.
I started getting the "com.htc.htcdailer" isn't responding issue. Then the phone reboots. I am not up long enough to load a rom to flash either.
When I try to sideload anything it doesn't work. I did update all the SDK files like I found in some searches. No go.
I am at a loss now what to do. Any thoughts?
Thanks
Click to expand...
Click to collapse
Boot into TWRP, download this driver:
http://www.koushikdutta.com/post/universal-adb-driver
Connect it to your PC in TWRP mode to your computer and Windows Device Manager, update the driver pointing to the one downloaded.
It should install with out an issue and the device should be detected thru ADB. Now all you need to do is push the rom via ADB. I recommend Cyanogenmod as its very small to push. I cannot quite remember the command to push a file as it can be complicated in the folder parts, but use this to push easily:
http://skipsoft.net/download/toolkit/nexus7toolkit/Google_Nexus_7_ToolKit_v5.0.0.exe
Ignore the fact that it's for the Nexus 7. Once it's installed, navigate to My Computer, click your hard drive and you should see a folder called Nexus 7 toolkit or similar (if not there check in Program Files). Look for an exe called "tkmain" and create a shortcut of it on your desktop. Keep that folder section open for now. Double click it. MAKE SURE YOU CAN SEE YOUR DEVICE SERIAL ON TOP TO ASSURE ITS CONNECTED. Now go to the same folder you saw the tkmain.exe and you should see a folder that says "Put Files to Push here". Drop the rom in there. I recommend naming it something short like "cyanogen.zip" for example. Now back on the toolkit, select the option that says Push file (I think it's option 13), answer Yes to the insecure boot image question, when it says select a file to push you should see the name of the rom zip , type it exactly as its name/you renamed it. When it says select a location, select /sdcard/ and proceed with the rest. It may seem like nothing is going on, and it may say something about "failed: success" beforehand, but trust me it's pushing, once it says complete, your ready to flash the rom.
Remember that if your S-Off, you need to flash the boot.img seperately via fastboot.

Crossvxm said:
Boot into TWRP, download this driver:
http://www.koushikdutta.com/post/universal-adb-driver
Connect it to your PC in TWRP mode to your computer and Windows Device Manager, update the driver pointing to the one downloaded.
It should install with out an issue and the device should be detected thru ADB. Now all you need to do is push the rom via ADB. I recommend Cyanogenmod as its very small to push. I cannot quite remember the command to push a file as it can be complicated in the folder parts, but use this to push easily:
http://skipsoft.net/download/toolkit/nexus7toolkit/Google_Nexus_7_ToolKit_v5.0.0.exe
Ignore the fact that it's for the Nexus 7. Once it's installed, navigate to My Computer, click your hard drive and you should see a folder called Nexus 7 toolkit or similar (if not there check in Program Files). Look for an exe called "tkmain" and create a shortcut of it on your desktop. Keep that folder section open for now. Double click it. MAKE SURE YOU CAN SEE YOUR DEVICE SERIAL ON TOP TO ASSURE ITS CONNECTED. Now go to the same folder you saw the tkmain.exe and you should see a folder that says "Put Files to Push here". Drop the rom in there. I recommend naming it something short like "cyanogen.zip" for example. Now back on the toolkit, select the option that says Push file (I think it's option 13), answer Yes to the insecure boot image question, when it says select a file to push you should see the name of the rom zip , type it exactly as its name/you renamed it. When it says select a location, select /sdcard/ and proceed with the rest. It may seem like nothing is going on, and it may say something about "failed: success" beforehand, but trust me it's pushing, once it says complete, your ready to flash the rom.
Remember that if your S-Off, you need to flash the boot.img seperately via fastboot.
Click to expand...
Click to collapse
Thank you very much for the help.
When I get to the point of typing which file to push the application cannot find the file.
I have been flashing roms for a while since the OG Droid and I can't understand why this has happened. I'm close to being beat.

mothmansound said:
Thank you very much for the help.
When I get to the point of typing which file to push the application cannot find the file.
I have been flashing roms for a while since the OG Droid and I can't understand why this has happened. I'm close to being beat.
Click to expand...
Click to collapse
The ROM must be in the folder that says "put files to push here" (make sure its that folder as I remember that another one seems similarly worded) from the toolkit program directory. You have to manually place your file there. If anything, close the toolkit and reopen it (remember, tkmain, the other section of the program is all Nexus related) and try again. Remember also to shorten the name so you don't have to type it in completely. Somewhere above where your supposed to type the file name you should see your ROM file. That's when you type it in exactly as you see it, for example, "rom.zip" you will type it in exactly like that.

Crossvxm said:
The ROM must be in the folder that says "put files to push here" (make sure its that folder as I remember that another one seems similarly worded) from the toolkit program directory. You have to manually place your file there. If anything, close the toolkit and reopen it (remember, tkmain, the other section of the program is all Nexus related) and try again. Remember also to shorten the name so you don't have to type it in completely. Somewhere above where your supposed to type the file name you should see your ROM file. That's when you type it in exactly as you see it, for example, "rom.zip" you will type it in exactly like that.
Click to expand...
Click to collapse
Yessir I double and triple checked that, I can't get it to find the file. I did rename a couple of different ways and tried with and without the".zip" part. No luck. I do appreciate the help.

mothmansound said:
Yessir I double and triple checked that, I can't get it to find the file. I did rename a couple of different ways and tried with and without the".zip" part. No luck. I do appreciate the help.
Click to expand...
Click to collapse
Do you have an adb/fastboot folder set up? If so, time for some manual method. Grab the ROM zip and put it in the same folder as your ADB and fastboot folder. Start adb thru command prompt then type in:
Code:
adb push ROM.zip /storage/sdcard
Hopefully I remembered it correctly. Should be that way.

Crossvxm said:
Do you have an adb/fastboot folder set up? If so, time for some manual method. Grab the ROM zip and put it in the same folder as your ADB and fastboot folder. Start adb thru command prompt then type in:
Code:
adb push ROM.zip /storage/sdcard
Hopefully I remembered it correctly. Should be that way.
Click to expand...
Click to collapse
Its saying device not found and doesn't seem to push.

Crossvxm said:
Do you have an adb/fastboot folder set up? If so, time for some manual method. Grab the ROM zip and put it in the same folder as your ADB and fastboot folder. Start adb thru command prompt then type in:
Code:
adb push ROM.zip /storage/sdcard
Hopefully I remembered it correctly. Should be that way.
Click to expand...
Click to collapse
Its saying device not found and doesn't seem to push.

I finally got the RUU to work. What a week and seems fine now.
Last piece of advice hopefully. All I want is the tap to wake feature. Stock is fine.
What is the best way to do that? When I tried using other kernals is when I ran into problems.
Thanks for the help.

mothmansound said:
I finally got the RUU to work. What a week and seems fine now.
Last piece of advice hopefully. All I want is the tap to wake feature. Stock is fine.
What is the best way to do that? When I tried using other kernals is when I ran into problems.
Thanks for the help.
Click to expand...
Click to collapse
Lol i misread that disregard the rest. What custom kernel are you trying to use? Remember each device is the same but also different. I had 2 LG G2s that would not double tap to wake, but would double tap to sleep. All the rest of them worked perfectly. Have also came across friends with G2s that wouldnt work

mothmansound said:
I finally got the RUU to work. What a week and seems fine now.
Last piece of advice hopefully. All I want is the tap to wake feature. Stock is fine.
What is the best way to do that? When I tried using other kernals is when I ran into problems.
Thanks for the help.
Click to expand...
Click to collapse
Best way is to flash the kernel in my signature. After you flash it, double tap to wake should be working automatically.

How to update firmware to support newer ROM

HI..I'm a complete noob when it comes to this. Somebody helped me install an older ROM 4.1.2, sense 5, 1.31.651.2 to use on another network and I want to install a newer ROM with better firmware...mostly because 3g is really slow here, sometimes doesnt even register and I think the radio can be better.
Can i use TWRP thats on my phone to flash a newer firmware before I flash the ROM? If so, do i have to wipe before I do that? How else may I update the firmware?
Thanks for your help.

You should always wipe before flashing a new ROM, but you only need to wipe system, data and cache (dalvik cache as wll if you have that option) - NEVER wipe internal storage or you will lose the rom file and likely have to RUU.
Here http://forum.xda-developers.com/showthread.php?t=2795856 is a link to the most recent firmware which comes with a brief tutorial as to how to flash the firmware using fastboot. If you are a noob, you will want the one that says "modified firmware with hboot and recovery removed" since you want to keep TWRP.
You will need to connect your phone to your pc while it is in the bootloader. You can get into the bootloader by turning your phone off, then holding volume down and the power key until a while screen comes up that says "Hboot" near the top. If you don't have ADB and/or the android sdk on your computer, you will need to get that first and then you will need to open a command prompt in the same folder where "fastboot.exe" is after installing the android sdk.
So again, you will download the extracted firmware, and also download the android sdk. Once android sdk is installed, navigate to the folder on your computer called "adb" and ensure that you can find "fastboot.exe". Once you have found this folder, copy the firmware file into the adb folder and rename it "firmware". Then hold shift and right click in the folder and select "open a command prompt here". After that, reboot your phone to the bootloader and plug in your phone to your computer. Then follow the instructions for flashing firmware at the link I posted.
You do not need to wipe prior to installing firmware. You should flash the new firmware before you flash a new rom since the firmware will work with any rom but the new roms only work with the new firmware. Wouldn't want to install a new rom only to find out you can't figure out how to install firmware.

Thank you very much for your reply The_mamba. I appreciate the time you took to write that all out. Can't wait to give it a shot.

[email protected] said:
Thank you very much for your reply The_mamba. I appreciate the time you took to write that all out. Can't wait to give it a shot.
Click to expand...
Click to collapse
No problem, I wouldn't know what I know if not for people taking the time to explain it. Let me know if you run into any problems or you need me to elaborate on any instructions.

The_mamba said:
No problem, I wouldn't know what I know if not for people taking the time to explain it. Let me know if you run into any problems or you need me to elaborate on any instructions.
Click to expand...
Click to collapse
So I downloaded adb, found fastboot.exe and tried following the directions but once I typed the command it just said "waiting on device". I extracted and renamed the folder and even tried it compressed...reason being the directions said to rename it firmware.zip but after it was extracted it's not a zip file anymore. I don't even know if that's the issue just something I wanted to bring up.
I also made sure my device said fastboot usb as well.
Other notes
I didn't download sdk, just an abbreviated adb. My computer says it doesn't recognize the device as soon as I get to fastboot usb. Under file name it says compressed file then .zip...can the command be wrong? Lastly, I hold shift and open a command within the folder that houses fastboot.exe and firmware among a few other files correct?

[email protected] said:
So I downloaded adb, found fastboot.exe and tried following the directions but once I typed the command it just said "waiting on device". I extracted and renamed the folder and even tried it compressed...reason being the directions said to rename it firmware.zip but after it was extracted it's not a zip file anymore. I don't even know if that's the issue just something I wanted to bring up.
I also made sure my device said fastboot usb as well.
Other notes
I didn't download sdk, just an abbreviated adb. My computer says it doesn't recognize the device as soon as I get to fastboot usb. Under file name it says compressed file then .zip...can the command be wrong? Lastly, I hold shift and open a command within the folder that houses fastboot.exe and firmware among a few other files correct?
Click to expand...
Click to collapse
Couple things: The abridged adb should be fine, it sounds like your computer is not recognizing the phone. Things to try for that is use a different USB port (sounds stupid but this often works) and make sure you have the most updated HTC drivers for the phone installed on your computer. You may want to ensure that your abridged ADB came with the adb and fastboot drivers as well. Also, you do not need to extract the firmware zip file that you download, just rename it. Literally just copy the downloaded firmware to the adb folder, rename it, and flash. You are correct about the command prompt window, you just want to open the command prompt from that folder so you don't have to navigate to the adb folder once in command prompt. As long as you open the command prompt from the folder it should say something like "C:\adb>" with a blinking underscore. Obviously if you didn't install adb to the root of your C:/ drive then it will say wherever you installed it.
Commands in order (once phone is in fastboot mode and recognized) should be:
fastboot oem rebootRUU (this will reboot the phone to a black screen with silver htc logo)
fastboot flash zip firmware.zip
(then it will run several lines of code and hopefully say "Success!")
fastboot reboot
Be cognizant of spaces and such.
Let me know if you still can't get it to work.

The_mamba said:
Couple things: The abridged adb should be fine, it sounds like your computer is not recognizing the phone. Things to try for that is use a different USB port (sounds stupid but this often works) and make sure you have the most updated HTC drivers for the phone installed on your computer. You may want to ensure that your abridged ADB came with the adb and fastboot drivers as well. Also, you do not need to extract the firmware zip file that you download, just rename it. Literally just copy the downloaded firmware to the adb folder, rename it, and flash. You are correct about the command prompt window, you just want to open the command prompt from that folder so you don't have to navigate to the adb folder once in command prompt. As long as you open the command prompt from the folder it should say something like "C:\adb>" with a blinking underscore. Obviously if you didn't install adb to the root of your C:/ drive then it will say wherever you installed it.
Commands in order (once phone is in fastboot mode and recognized) should be:
fastboot oem rebootRUU (this will reboot the phone to a black screen with silver htc logo)
fastboot flash zip firmware.zip
(then it will run several lines of code and hopefully say "Success!")
fastboot reboot
Be cognizant of spaces and such.
Let me know if you still can't get it to work.
Click to expand...
Click to collapse
Hey. Thanks for the last reply. I did everything you recommended but it still didn't work. I used two different usb cables, 3 different ports, and I keep getting the message I attached. However, htc sync worked albeit it gave me a warning message and said I needed a different driver and it downloaded it before it registered. Do you think my version is too outdated to be supported? I tried this HTC-Mobile-Driver_v4.16.0.001.exe and HTC-Mobile-Driver-v4.17.0.001 (1).zip and a website recommended this HTC_BMP_USB_Driver_x64_1.0.5375.msi but none helped.
I do get a noise every time I plug in and unplug the usb, so that seems to be working. USB debugging should be enabled correct?
Lastly and hopefully this is the main problem: when I turn off the phone and plug it in to the computer, I receive a message that say "The connected charger will take longer to charge. To charge faster, use the original charger and cable that were provided with this phone." I'm not sure if that's because its low voltage being delivered from the usb or the cable is actually not adequate, I will google that.
Also failed to mention my computer is running on Windows 10

[email protected] said:
Hey. Thanks for the last reply. I did everything you recommended but it still didn't work. I used two different usb cables, 3 different ports, and I keep getting the message I attached. However, htc sync worked albeit it gave me a warning message and said I needed a different driver and it downloaded it before it registered. Do you think my version is too outdated to be supported? I tried this HTC-Mobile-Driver_v4.16.0.001.exe and HTC-Mobile-Driver-v4.17.0.001 (1).zip and a website recommended this HTC_BMP_USB_Driver_x64_1.0.5375.msi but none helped.
I do get a noise every time I plug in and unplug the usb, so that seems to be working. USB debugging should be enabled correct?
Lastly and hopefully this is the main problem: when I turn off the phone and plug it in to the computer, I receive a message that say "The connected charger will take longer to charge. To charge faster, use the original charger and cable that were provided with this phone." I'm not sure if that's because its low voltage being delivered from the usb or the cable is actually not adequate, I will google that.
Click to expand...
Click to collapse
Hmmmm, interesting. Are you using usb ports on the front of the computer or the back? Sometimes the ones on the front aren't as good as the ones directly on the mainboard so if you haven't already then you could try the back ones. Also, despite using two cables, I guess there is still a chance that your cables are to blame. It concerns me that you are still getting driver errors even after updating sync so you may want to keep trying to solve the driver aspect. Here is an excerpt from a post on another forum I found that may be relevant:
"If you have the full AndroidSDK installed, check your device manager for an unknown device. If you find one that's supposed to be your phone, update the driver and use the driver in SDK directory\extras\google\usb_driver . If that still doesn't work, make sure you don't have HTC Sync running on your computer. It will hose the entire deal."
So try checking out your device manager regarding the driver and also be sure to close HTC sync completely (including the system tray icon if applicable) before plugging your phone in with bootloader up.
Check out the whole tread in general for some good tips: http://forums.androidcentral.com/rezound-rooting-roms-hacks/209934-stuck-waiting-device-after-fastboot-command.html
Keep me posted, I'm invested now, haha.